[Debian-pan-maintainers] Packaging pytango 9.2.0

PICCA Frederic-Emmanuel frederic-emmanuel.picca at synchrotron-soleil.fr
Tue Aug 30 07:43:14 BST 2016


Hello Sandor


I sent an email on debian-python in order to check what is the proper way to fix the pytango / tango issue.

for now let's see the lintian of pytango :)).


picca at mordor:~/Debian/pytango$ lintian -EviI pytango_9.2.0-1_i386.changes

I think that we should upload into experimental for now. so

9.2.0-1 -> 9.2.0-1~exp1

N: Using profile debian/main.
N: Setting up lab in /tmp/temp-lintian-lab-uNqUByvHmX ...
N: Unpacking packages in group pytango/9.2.0-1
N: ----
N: Processing changes file pytango (version 9.2.0-1, arch source i386 all) ...
N: ----
N: Processing source package pytango (version 9.2.0-1, arch source) ...
W: pytango source: changelog-should-mention-nmu
N: 
N:    When you NMU a package, that fact should be mentioned on the first line
N:    in the changelog entry. Use the words "NMU" or "Non-maintainer upload"
N:    (case insensitive).
N:    
N:    Maybe you didn't intend this upload to be a NMU, in that case, please
N:    double-check that the most recent entry in the changelog is
N:    byte-for-byte identical to the maintainer or one of the uploaders. If
N:    this is a local package (not intended for Debian), you can suppress this
N:    warning by putting "local" in the version number or "local package" on
N:    the first line of the changelog entry.
N:    
N:    Refer to Debian Developer's Reference section 5.11.3 (Using the DELAYED/
N:    queue) for details.
N:    
N:    Severity: normal, Certainty: certain
N:    
N:    Check: nmu, Type: source
N: 

In order to avoid this you can add yourself to the Uploaders in d/control if you are ok to become co-maintainer with me in the Debian-Science team.

But you should become also a member of Debian-science :)

I: pytango source: unused-file-paragraph-in-dep5-copyright paragraph at line 6
N: 
N:    The Files paragraph in debian/copyright is superfluous as it is never
N:    used to match any files. You should be able to safely remove it.
N:    
N:    Refer to
N:    https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ for
N:    details.
N:    
N:    Severity: minor, Certainty: possible
N:    
N:    Check: source-copyright, Type: source
N: 
N: ----
N: Processing binary package python3-tango-dbgsym (version 9.2.0-1, arch i386) ...
N: ----
N: Processing binary package python3-pytango (version 9.2.0-1, arch i386) ...
N: ----
N: Processing binary package python-tango (version 9.2.0-1, arch i386) ...


please update the copyright file (this is important because we will have to pass thr new process due to the binary package name change).

N: Processing binary package python-tango-doc (version 9.2.0-1, arch all) ...
E: python-tango-doc: privacy-breach-uses-embedded-file usr/share/doc/python-tango-doc/html/index.html You may use libjs-jquery package. (http://code.jquery.com/jquery-1.9.1.min.js)
N: 
N:    This package creates a potential privacy breach by fetching data from an
N:    external website at runtime. Please remove these scripts or external
N:    HTML resources.
N:    
N:    Instead you can use the Debian package indicated in the hint, if it is
N:    compatible.
N:    
N:    Severity: important, Certainty: possible
N:    
N:    Check: files, Type: binary, udeb
N: 
N: ----

Usually this is fixed by using --with sphinxdoc

I need to investigate to understand.


Cheers


Frederic




More information about the Debian-pan-maintainers mailing list