Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debian package rules need improvement (need Debian package expert) #604

Closed
gdha opened this issue Jun 18, 2015 · 2 comments
Closed

Debian package rules need improvement (need Debian package expert) #604

gdha opened this issue Jun 18, 2015 · 2 comments
Labels
bug The code does not do what it is meant to do enhancement Adaptions and new features
Milestone

Comments

@gdha
Copy link
Member

gdha commented Jun 18, 2015

Noticed during OBS builds the following errors/warnings for Debian 7 (or 8):

[   65s] dpkg-buildpackage: binary and diff upload (original source NOT included)
[   65s] Running lintian
[   65s] + lintian -i /usr/src/packages/SOURCES.DEB/rear_1.17.0-0git201506171717.dsc
[   70s] E: rear source: build-info-in-binary-control-file-section Package rear
[   70s] N: 
[   70s] N:    The control file has a Build-Depends, Build-Depends-Indep,
[   70s] N:    Build-Conflicts, or Build-Conflicts-Indep field in a binary section.
[   70s] N:    These specify source package relationships, and should be in the source
[   70s] N:    section of the control file.
[   70s] N:    
[   70s] N:    Refer to Debian Policy Manual section 5.2 (Source package control files
[   70s] N:    -- debian/control) for details.
[   70s] N:    
[   70s] N:    Severity: serious, Certainty: certain
[   70s] N:    
[   70s] N:    Check: control-file, Type: source
[   70s] N: 
[   70s] W: rear source: package-depends-on-hardcoded-libc rear depends
[   70s] N: 
[   70s] N:    The given package declares a dependency on libc directly instead of
[   70s] N:    using ${shlibs:Depends} in its debian/control stanza.
[   70s] N:    
[   70s] N:    Severity: normal, Certainty: certain
[   70s] N:    
[   70s] N:    Check: control-file, Type: source
[   70s] N: 
[   70s] W: rear source: debhelper-but-no-misc-depends rear
[   70s] N: 
[   70s] N:    The source package uses debhelper, but it does not include
[   70s] N:    ${misc:Depends} in the given binary package's debian/control entry. Any
[   70s] N:    debhelper command may add dependencies to ${misc:Depends} that are
[   70s] N:    required for the work that it does, so recommended best practice is to
[   70s] N:    always add ${misc:Depends} to the dependencies of each binary package if
[   70s] N:    debhelper is in use.
[   70s] N:    
[   70s] N:    Refer to the debhelper(7) manual page for details.
[   70s] N:    
[   70s] N:    Severity: normal, Certainty: possible
[   70s] N:    
[   70s] N:    Check: debhelper, Type: source
[   70s] N: 
[   70s] W: rear source: debhelper-compat-file-is-missing
[   70s] N: 
[   70s] N:    The package uses debhelper but does not ship a compat file. This is
[   70s] N:    deprecated and eventaully cause the package to FTBFS.
[   70s] N:    
[   70s] N:    Please refer to the dehelper documentation on how to create the compat
[   70s] N:    file and the differences between each compat level.
[   70s] N:    
[   70s] N:    Refer to
[   70s] N:    http://packages.qa.debian.org/d/debhelper/news/20120115T191738Z.html and
[   70s] N:    the debhelper(7) manual page for details.
[   70s] N:    
[   70s] N:    Severity: normal, Certainty: certain
[   70s] N:    
[   70s] N:    Check: debhelper, Type: source
[   70s] N: 
[   71s] W: rear source: changelog-should-mention-nmu
[   71s] N: 
[   71s] N:    When you NMU a package, that fact should be mentioned on the first line
[   71s] N:    in the changelog entry. Use the words "NMU" or "Non-maintainer upload"
[   71s] N:    (case insensitive).
[   71s] N:    
[   71s] N:    Maybe you didn't intend this upload to be a NMU, in that case, please
[   71s] N:    doublecheck that the most recent entry in the changelog is byte-for-byte
[   71s] N:    identical to the maintainer or one of the uploaders. If this is a local
[   71s] N:    package (not intended for Debian), you can suppress this warning by
[   71s] N:    putting "local" in the version number or "local package" on the first
[   71s] N:    line of the changelog entry.
[   71s] N:    
[   71s] N:    Refer to Debian Developer's Reference section 5.11.3 (Using the DELAYED/
[   71s] N:    queue) for details.
[   71s] N:    
[   71s] N:    Severity: normal, Certainty: certain
[   71s] N:    
[   71s] N:    Check: nmu, Type: source
[   71s] N: 
[   71s] W: rear source: source-nmu-has-incorrect-version-number 1.17.0-0git201506171717
[   71s] N: 
[   71s] N:    A source NMU should have a Debian revision of "-x.x" (or "+nmuX" for a
[   71s] N:    native package). This is to prevent stealing version numbers from the
[   71s] N:    maintainer.
[   71s] N:    
[   71s] N:    Maybe you didn't intend this upload to be a NMU, in that case, please
[   71s] N:    doublecheck that the most recent entry in the changelog is byte-for-byte
[   71s] N:    identical to the maintainer or one of the uploaders. If this is a local
[   71s] N:    package (not intended for Debian), you can suppress this warning by
[   71s] N:    putting "local" in the version number or "local package" on the first
[   71s] N:    line of the changelog entry.
[   71s] N:    
[   71s] N:    Refer to Debian Developer's Reference section 5.11.2 (NMUs and
[   71s] N:    debian/changelog) for details.
[   71s] N:    
[   71s] N:    Severity: normal, Certainty: certain
[   71s] N:    
[   71s] N:    Check: nmu, Type: source
[   71s] N: 
[   71s] W: rear source: debian-rules-sets-DH_COMPAT line 12
[   71s] N: 
[   71s] N:    As of debhelper version 4, the DH_COMPAT environment variable is only to
[   71s] N:    be used for temporarily overriding debian/compat. Any line in
[   71s] N:    debian/rules that sets it globally should be deleted and a separate
[   71s] N:    debian/compat file created if needed.
[   71s] N:    
[   71s] N:    Refer to the debhelper(7) manual page for details.
[   71s] N:    
[   71s] N:    Severity: normal, Certainty: certain
[   71s] N:    
[   71s] N:    Check: rules, Type: source
[   71s] N: 
[   71s] W: rear source: debian-rules-missing-recommended-target build-arch
[   71s] N: 
[   71s] N:    The debian/rules file for this package does not provide one of the
[   71s] N:    recommended targets. All of build-arch and build-indep should be
[   71s] N:    provided, even if they don't do anything for this package. If this
[   71s] N:    package does not currently split building of architecture dependent and
[   71s] N:    independent packages, the following rules may be added to fall back to
[   71s] N:    the build target:
[   71s] N:    
[   71s] N:      build-arch: build
[   71s] N:      build-indep: build
[   71s] N:    
[   71s] N:    Note that the following form is recommended however:
[   71s] N:    
[   71s] N:      build: build-arch build-indep
[   71s] N:      build-arch: build-stamp
[   71s] N:      build-indep: build-stamp
[   71s] N:      build-stamp:
[   71s] N:    build here
[   71s] N:    
[   71s] N:    These targets will be required by policy in the future, so should be
[   71s] N:    added to prevent future breakage.
[   71s] N:    
[   71s] N:    Refer to Debian Policy Manual section 4.9 (Main building script:
[   71s] N:    debian/rules) for details.
[   71s] N:    
[   71s] N:    Severity: normal, Certainty: certain
[   71s] N:    
[   71s] N:    Check: rules, Type: source
[   71s] N: 
[   71s] W: rear source: debian-rules-missing-recommended-target build-indep
[   71s] W: rear source: no-debian-copyright
[   71s] N: 
[   71s] N:    Every package must include the file /usr/share/doc/<pkg>/copyright. A
[   71s] N:    copy of this file should be in debian/copyright in the source package.
[   71s] N:    
[   71s] N:    Refer to Debian Policy Manual section 12.5 (Copyright information) for
[   71s] N:    details.
[   71s] N:    
[   71s] N:    Severity: minor, Certainty: certain
[   71s] N:    
[   71s] N:    Check: source-copyright, Type: source
[   71s] N: 
[   71s] E: rear source: no-standards-version-field
[   71s] N: 
[   71s] N:    The source package does not have a Standards-Version control field.
[   71s] N:    Please update your package to latest Policy and set this control field
[   71s] N:    appropriately.
[   71s] N:    
[   71s] N:    Refer to Debian Policy Manual section 5.6.11 (Standards-Version) for
[   71s] N:    details.
[   71s] N:    
[   71s] N:    Severity: important, Certainty: certain
[   71s] N:    
[   71s] N:    Check: standards-version, Type: source
@gdha gdha added the enhancement Adaptions and new features label Jun 18, 2015
@gdha
Copy link
Member Author

gdha commented Aug 3, 2015

Might be related with issue #629 - still looking for a Debian package expert

@gdha gdha added the bug The code does not do what it is meant to do label Aug 3, 2015
@gdha gdha added this to the 1.17.2 milestone Aug 3, 2015
gdha added a commit that referenced this issue Aug 3, 2015
@gdha
Copy link
Member Author

gdha commented Aug 3, 2015

good news- it builds now for Debian 7 and 8

@gdha gdha closed this as completed Aug 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The code does not do what it is meant to do enhancement Adaptions and new features
Projects
None yet
Development

No branches or pull requests

1 participant