[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: RFS: Sabacc



Hi Joel

On Tue, Jan 13, 2009 at 07:33:13PM -0600, Joel Cross wrote:
> I am looking for a sponsor for my package "sabacc".

IANADD and can't upload for you, but while you're looking for a sponsor
you need to address these problems with your package:

Your version number will cause you problems later on - presumably at
some point 1.0-beta1-1 will become 1.0-1, but as far as dpkg is
concerned this is lower and it will whinge. As you are also upstream
this is less of a problem, because you can change the upstream number
yourself, to 1.0~beta1 (so then your Debian version becomes
1.0~beta1-1).

Lintian is quite vocal too:

I: sabacc source: debian-watch-file-is-missing
W: sabacc source: out-of-date-standards-version 3.7.3 (current is 3.8.0)
E: sabacc source: missing-python-build-dependency
I: sabacc source: build-depends-without-arch-dep python-lxml
W: sabacc: extra-license-file usr/share/doc/sabacc/COPYING.gz
W: sabacc: package-contains-upstream-install-documentation usr/share/doc/sabacc/INSTALL
E: sabacc: package-section-games-but-contains-no-game
I: sabacc: desktop-entry-contains-encoding-key
/usr/share/applications/sabacc.desktop:2 Encoding
W: sabacc: new-package-should-close-itp-bug
W: sabacc: wrong-bug-number-in-closes l3:#nnnn

Full lintian output is attached.

I haven't looked in much more details, have a go at these and if you need 
help ask, and we can see what kind of shape it's in after that.


-- 
Jonathan Wiltshire

PGP/GPG: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3  A903 CA6B EA3E DB80 0B52
I: sabacc source: debian-watch-file-is-missing
N:
N:   This source package is not Debian-native but it does not have a
N:   debian/watch file. This file is used for automatic detection of new
N:   upstream versions by the Debian External Health Status project and
N:   other project infrastructure. If this package is maintained upstream,
N:   please consider adding a debian/watch file to detect new releases.
N:   
N:   If the package is not maintained upstream or if upstream uses a
N:   distribution mechanism that cannot be meaningfully monitored by uscan
N:   and the Debian External Health Status project, please consider adding
N:   a debian/watch file containing only comments documenting the
N:   situation.
N:   
N:   Refer to Policy Manual, section 4.11 and the uscan(1) manual page for
N:   details.
N:
W: sabacc source: out-of-date-standards-version 3.7.3 (current is 3.8.0)
N:
N:   The source package refers to a Standards-Version older than the one
N:   that was current at the time the package was created (according to the
N:   timestamp of the latest debian/changelog entry). Please consider
N:   updating the package to current Policy and setting this control field
N:   appropriately.
N:   
N:   If the package is already compliant with the current standards, you
N:   don't have to re-upload the package just to adjust the
N:   Standards-Version control field. However, please remember to update
N:   this field next time you upload the package.
N:
E: sabacc source: missing-python-build-dependency
N:
N:   The package appears to use Python as part of its build process in
N:   debian/rules but doesn't depend on Python.
N:   
N:   Normally, packages that use Python as part of the build process should
N:   build-depend on one of python, python-all, python-dev, or
N:   python-all-dev depending on whether they support multiple versions of
N:   Python and whether they're building modules or only using Python as
N:   part of the package build process. Packages that depend on a specific
N:   version of Python may build-depend on the appropriate pythonX.Y or
N:   pythonX.Y-dev package instead.
N:   
N:   Refer to Policy Manual, section 4.2 for details.
N:
I: sabacc source: build-depends-without-arch-dep python-lxml
N:
N:   The control file lists the given package in Build-Depends, but no
N:   architecture-dependent packages are built. If all the packages built
N:   are architecture-independent, the only packages that should be listed
N:   in Build-Depends are those required to run the clean target (such as
N:   debhelper if you use dh_clean). Other build dependencies should be
N:   listed in Build-Depends-Indep instead.
N:   
N:   Refer to Policy Manual, section 7.7 for details.
N:
W: sabacc: extra-license-file usr/share/doc/sabacc/COPYING.gz
N:
N:   All license information should be collected in the debian/copyright
N:   file. This usually makes it unnecessary for the package to install
N:   this information in other places as well.
N:   
N:   Refer to Policy Manual, section 12.5 for details.
N:
W: sabacc: package-contains-upstream-install-documentation usr/share/doc/sabacc/INSTALL
N:
N:   Binary packages do not need to contain the instructions for building
N:   and installing the package as this info is not needed by package
N:   users. If the info contained is important for configuration perhaps it
N:   could be summarized in README.Debian, otherwise an override may be
N:   added.
N:   
N:   Refer to Policy Manual, section 12.3 for details.
N:
E: sabacc: package-section-games-but-contains-no-game
N:
N:   This package is marked as part of the section games, but doesn't
N:   contain files in /usr/games. Binaries of games must be installed in
N:   /usr/games.
N:   
N:   Refer to Policy Manual, section 11.11 for details.
N:
I: sabacc: desktop-entry-contains-encoding-key /usr/share/applications/sabacc.desktop:2 Encoding
N:
N:   The Encoding key is now deprecated by the FreeDesktop standard and all
N:   strings are required to be encoded in UTF-8. This desktop entry
N:   explicitly specifies an Encoding of UTF-8, which is harmless but no
N:   longer necessary.
N:   
N:   Refer to
N:   http://standards.freedesktop.org/desktop-entry-spec/1.0/apc.html for
N:   details.
N:
W: sabacc: new-package-should-close-itp-bug
N:
N:   This package appears to be the first packaging of a new upstream
N:   software package (there is only one changelog entry and the Debian
N:   revision is 1), but it does not close any bugs. The initial upload of
N:   a new package should close the corresponding ITP bug for that package.
N:   
N:   This warning can be ignored if the package is not intended for Debian
N:   or if it is a split of an existing Debian package.
N:   
N:   Refer to Developers Reference, section 5.1 for details.
N:
W: sabacc: wrong-bug-number-in-closes l3:#nnnn
N:
N:   Bug numbers can only contain digits.
N:   
N:   Refer to Policy Manual, section 4.4 for details.
N:

Attachment: signature.asc
Description: Digital signature


Reply to: