[Bug 1560315] Re: [needs packaging] juju2 beta is not in xenial
Adam Stokes
adam.stokes at canonical.com
Tue Mar 22 17:07:55 UTC 2016
For completeness this is the lintian output in all its glory:
E: juju2 changes: bad-distribution-in-changes-file xenial-amd64
N:
N: You've specified an unknown target distribution for your upload in the
N: debian/changelog file. It is possible that you are uploading for a
N: different distribution than the one Lintian is checking for. In that
N: case, passing --profile $VENDOR may fix this warning.
N:
N: Note that the distributions non-free and contrib are no longer valid.
N: You'll have to use distribution unstable and Section: non-free/xxx or
N: Section: contrib/xxx instead.
N:
N: Refer to Debian Policy Manual section 5.6.14 (Distribution) for details.
N:
N: Severity: important, Certainty: certain
N:
N: Check: changes-file, Type: changes
N:
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju ang and
N:
N: Lintian found a spelling error in the given binary. Lintian has a list
N: of common misspellings that it looks for. It does not have a dictionary
N: like a spelling checker does.
N:
N: If the string containing the spelling error is translated with the help
N: of gettext or a similar tool, please fix the error in the translations
N: as well as the English text to avoid making the translations fuzzy. With
N: gettext, for example, this means you should also fix the spelling
N: mistake in the corresponding msgids in the *.po files.
N:
N: You can often find the word in the source code by running:
N:
N: grep -rw <word> <source-tree>
N:
N: This tag may produce false positives for words that contain non-ASCII
N: characters due to limitations in strings.
N:
N: Severity: minor, Certainty: wild-guess
N:
N: Check: binaries, Type: binary, udeb
N:
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju Succesfully Successfully
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju enviroment environment
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju specifed specified
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju transfered transferred
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju reenabled re-enabled
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju intial initial
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju reenable re-enable
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju ommitted omitted
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju precendence precedence
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju allows to allows one to
E: juju2: embedded-library usr/lib/juju-2.0-beta2/bin/juju: libyaml
N:
N: The given ELF object appears to have been statically linked to a
N: library. Doing this is strongly discouraged due to the extra work needed
N: by the security team to fix all the extra embedded copies or trigger the
N: package rebuilds, as appropriate.
N:
N: If the package uses a modified version of the given library it is highly
N: recommended to coordinate with the library's maintainer to include the
N: changes on the system version of the library.
N:
N: Refer to Debian Policy Manual section 4.13 (Convenience copies of code)
N: for details.
N:
N: Severity: serious, Certainty: possible
N:
N: Check: binaries, Type: binary, udeb
N:
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-metadata ang and
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-metadata enviroment environment
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-metadata specifed specified
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-metadata arbitary arbitrary
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-metadata precendence precedence
E: juju2: embedded-library usr/lib/juju-2.0-beta2/bin/juju-metadata: libyaml
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-restore ang and
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-restore specifed specified
E: juju2: embedded-library usr/lib/juju-2.0-beta2/bin/juju-restore: libyaml
W: juju2: hardening-no-relro usr/lib/juju-2.0-beta2/bin/juju-restore
N:
N: This package provides an ELF binary that lacks the "read-only
N: relocation" link flag. This package was likely not built with the
N: default Debian compiler flags defined by dpkg-buildflags. If built using
N: dpkg-buildflags directly, be sure to import LDFLAGS.
N:
N: Refer to https://wiki.debian.org/Hardening for details.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: binaries, Type: binary, udeb
N:
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-upgrade-mongo ang and
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-upgrade-mongo specifed specified
E: juju2: unstripped-binary-or-object usr/lib/juju-2.0-beta2/bin/juju-upgrade-mongo
N:
N: The package installs an unstripped binary or object file.
N:
N: Please note, that shared libraries have to be stripped with the
N: --strip-unneeded option.
N:
N: Refer to Debian Policy Manual section 10.1 (Binaries) and Debian Policy
N: Manual section 10.2 (Libraries) for details.
N:
N: Severity: important, Certainty: certain
N:
N: Check: binaries, Type: binary, udeb
N:
E: juju2: embedded-library usr/lib/juju-2.0-beta2/bin/juju-upgrade-mongo: libyaml
W: juju2: hardening-no-relro usr/lib/juju-2.0-beta2/bin/juju-upgrade-mongo
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/jujud ang and
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/jujud Succesfully Successfully
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/jujud enviroment environment
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/jujud specifed specified
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/jujud addreses addresses
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/jujud overriden overridden
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/jujud precendence precedence
E: juju2: embedded-library usr/lib/juju-2.0-beta2/bin/jujud: libyaml
W: juju2: debian-news-entry-has-unknown-version 1.13.1-0ubuntu1
N:
N: The version number of the most recent NEWS.Debian entry does not match
N: any of the version numbers in the changelog file for this package. This
N: usually means the version in NEWS.Debian needs to be updated to match a
N: change to package version that happened after the NEWS.Debian entry was
N: written.
N:
N: Severity: normal, Certainty: possible
N:
N: Check: changelog-file, Type: binary
N:
E: juju2: copyright-file-contains-full-apache-2-license
N:
N: The copyright file /usr/share/doc/<pkg>/copyright contains the complete
N: text of the Apache 2.0 license. It should refer to the file
N: /usr/share/common-licenses/Apache-2.0 instead.
N:
N: Refer to Debian Policy Manual section 12.5 (Copyright information) for
N: details.
N:
N: Severity: important, Certainty: certain
N:
N: Check: copyright-file, Type: binary
N:
W: juju2: rc-version-greater-than-expected-version 2.0-beta2 > 2.0 (consider using 2.0~beta2)
N:
N: The package appears to be a release candidate or preview release, but
N: the version sorts higher than the expected final release.
N:
N: Note this check is limited to new upstream releases of non-native
N: packages.
N:
N: Refer to Debian Policy Manual section 5.6.12 (Version) for details.
N:
N: Severity: normal, Certainty: possible
N:
N: Check: fields, Type: binary, udeb, source
N:
I: juju2: conflicts-with-version juju (<< 0.7-0ubuntu1~)
N:
N: An earlier-than version clause is normally an indication that Breaks
N: should be used instead of Conflicts. Breaks is a weaker requirement that
N: provides the package manager more leeway to find a valid upgrade path.
N: Conflicts should only be used if two packages can never be unpacked at
N: the same time, or for some situations involving virtual packages (where
N: a version clause is not appropriate). In particular, when moving files
N: between packages, use Breaks plus Replaces, not Conflicts plus Replaces.
N:
N: Refer to Debian Policy Manual section 7.4 (Conflicting binary packages -
N: Conflicts) for details.
N:
N: Severity: normal, Certainty: wild-guess
N:
N: Check: fields, Type: binary, udeb, source
N:
W: juju2: package-installs-into-obsolete-dir etc/bash_completion.d/ : ^etc/bash_completion.d/ -> usr/share/bash-completion/completions (see also https://bugs.debian.org/776954)
N:
N: The package installs files to an obsolete directory. Please use a newer
N: path.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: files, Type: binary, udeb
N:
W: juju2: package-installs-into-obsolete-dir etc/bash_completion.d/juju2 : ^etc/bash_completion.d/ -> usr/share/bash-completion/completions (see also https://bugs.debian.org/776954)
W: juju2: binary-without-manpage usr/bin/juju2
N:
N: Each binary in /usr/bin, /usr/sbin, /bin, /sbin or /usr/games should
N: have a manual page
N:
N: Note that though the man program has the capability to check for several
N: program names in the NAMES section, each of these programs should have
N: its own manual page (a symbolic link to the appropriate manual page is
N: sufficient) because other manual page viewers such as xman or tkman
N: don't support this.
N:
N: If the name of the man page differs from the binary by case, man may be
N: able to find it anyway; however, it is still best practice to make the
N: case of the man page match the case of the binary.
N:
N: If the man pages are provided by another package on which this package
N: depends, lintian may not be able to determine that man pages are
N: available. In this case, after confirming that all binaries do have man
N: pages after this package and its dependencies are installed, please add
N: a lintian override.
N:
N: Refer to Debian Policy Manual section 12.1 (Manual pages) for details.
N:
N: Severity: normal, Certainty: possible
N:
N: Check: manpages, Type: binary
N:
W: juju2: script-not-executable etc/bash_completion.d/juju2
N:
N: This file starts with the #! sequence that marks interpreted scripts,
N: but it is not executable.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: scripts, Type: binary
N:
I: juju2: unused-override statically-linked-binary usr/lib/juju-2.0-beta2/bin/juju
N:
N: Lintian discovered an unused override entry in its database. Most likely
N: it was used for a false-positive that has been fixed. However, some tags
N: are only triggered in packages built on certain architectures. In this
N: case, the override may need an architecture qualifier.
N:
N: If the override is unused, please remove it from the overrides file.
N:
N: Refer to Lintian User's Manual section 2.4.3 (Architecture specific
N: overrides) for details.
N:
N: Severity: wishlist, Certainty: certain
N:
I: juju2: unused-override statically-linked-binary usr/lib/juju-2.0-beta2/bin/juju-metadata
I: juju2: unused-override statically-linked-binary usr/lib/juju-2.0-beta2/bin/juju-restore
I: juju2: unused-override statically-linked-binary usr/lib/juju-2.0-beta2/bin/jujud
I: juju2: unused-override unstripped-binary-or-object usr/lib/juju-2.0-beta2-gcc/bin/juju
I: juju2: unused-override unstripped-binary-or-object usr/lib/juju-2.0-beta2-gcc/bin/juju-metadata
I: juju2: unused-override unstripped-binary-or-object usr/lib/juju-2.0-beta2-gcc/bin/juju-restore
I: juju2: unused-override unstripped-binary-or-object usr/lib/juju-2.0-beta2-gcc/bin/jujud
N: 4 tags overridden (4 errors)
** Bug watch added: Debian Bug tracker #776954
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776954
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1560315
Title:
[needs packaging] juju2 beta is not in xenial
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1560315/+subscriptions
More information about the Ubuntu-server-bugs
mailing list