vcswatch reports that
this package seems to have new commits in its VCS but has
not yet updated debian/changelog. You should consider updating
the Debian changelog and uploading this new version into the archive.
Here are the relevant commit logs:
commit 31b9054d3c42040ebf026eaf3c375e7e33525bc0
Author: Michael Prokop <mika@debian.org>
Date: Tue Jul 16 19:45:36 2019 +0200
pbuilder-hookdir/B90lintian: support execution on source files + improve error handling
If we find the Debian source package files, then execute lintian
also on the *.dsc file, allowing us to combine lintian execution
of source + binary jobs within one single step. This makes sense
esp. when we want to execute lintian from the actual build
environment/target.
lintian doesn't always return with exit code on execution errors (see
e.g. #932215 - "lintian: wrong exit code if specified profile does not
exist"). We also need to run it under bash with pipefail, otherwise
piping to tee(1) hides execution errors.
Development sponsored by Sipwise GmbH, recorded as
TT#15150 in customers' ticket system.
commit ee404c27bf49958364ad7b6f0c1d43ae7387bba5
Author: Michael Prokop <mika@debian.org>
Date: Tue Jul 16 18:40:35 2019 +0200
build-and-provide-package: ensure to set ADDITIONAL_BUILDRESULTS from within cowbuilder_run
Fixup for commit c79eb1581, we need to add ADDITIONAL_BUILDRESULTS also
when actually executing cowbuilder, not only during its initial setup.
Development sponsored by Sipwise GmbH, recorded as
TT#15150 in customers' ticket system.
commit 75988c695a723d59334ce932e31c8d58d63988fe
Author: Michael Prokop <mika@debian.org>
Date: Tue Jul 16 17:41:34 2019 +0200
Bump Standards-Version to 4.4.0
commit c79eb1581c52c5ba67123e955c44b61b3bfdb6b4
Author: Michael Prokop <mika@debian.org>
Date: Tue Jul 16 17:34:41 2019 +0200
build-and-provide-package: set ADDITIONAL_BUILDRESULTS also in custom pbuilderrc
If LINTIAN=yes is set, to run lintian from inside the build environment,
we need to make sure the ADDITIONAL_BUILDRESULTS reaches pbuilder.
Ad least when using a custom pbuilderrc (like
PBUILDER_CONFIG=/etc/jenkins/pbuilderrc inside /etc/jenkins/debian_glue)
then we need to make sure it's also part of the runtime pbuilderrc.
Development sponsored by Sipwise GmbH, recorded as
TT#15150 in customers' ticket system.
commit fc819c3a5025c5447254f92ae5973486973529c0
Merge: d6c58cf 8d9de8a
Author: Michael Prokop <mika@debian.org>
Date: Tue Jul 16 17:19:52 2019 +0200
Merge remote-tracking branch 'origin/pr/224'
commit 8d9de8a2e47615f921e9a00bd1cd837b1e423449
Author: Guillem Jover <gjover@sipwise.com>
Date: Thu Jul 4 18:25:06 2019 +0200
Bump Standards-Version to 4.3.0
commit 18671c6692f373c061602cffc7c0c29b2b415b86
Author: Guillem Jover <gjover@sipwise.com>
Date: Thu Jul 4 18:24:01 2019 +0200
debian: Namespace debhelper fragment file
Unnamespaced debhelper fragment files are deprecated, as they get used
only by the first binary package stanza in debian/control which is
rather confusing. Make this explicit.
commit d6c58cfc8ac004b6e6d3d1bc1d11d62748429efc
Author: Michael Prokop <mika@debian.org>
Date: Thu Apr 4 12:02:02 2019 +0200
puppet: fix broken user setup with recent Jenkins versions
If no user setup is present Jenkins handles this via
/var/lib/jenkins/secrets/initialAdminPassword and its setup wizard
nowadays. That's something we'd might want to skip, since we provide the
user password on the command line and provide the plugins we need via
our puppet setup.
Jenkins versions >2.138.4 migrate the user records to a
slightly different storage format that uses a central index to map user
IDs to directory names, also see https://jenkins.io/doc/upgrade-guide/2.138/
Closes: https://github.com/mika/jenkins-debian-glue/issues/223
commit aa23145fc534391a9394e0a0827ef3dae10262ac
Author: Michael Prokop <mika@debian.org>
Date: Thu Apr 4 08:51:07 2019 +0200
puppet: ensure puppet/facter from and on Debian works
Fixes:
| Error: Evaluation Error: Operator '[]' is not applicable to an Undef Value.
This is caused by different output from `facter os`.
Recent facter packages from puppetlabs behaves on Debian as follows:
| $ /opt/puppetlabs/bin/facter --version
| 3.11.8 (commit eb5f71136af5012f3a7169ed3a77a111c1e4d765)
| $ /opt/puppetlabs/bin/facter os
| {
| architecture => "amd64",
| distro => {
| codename => "stretch",
| description => "Debian GNU/Linux 9.8 (stretch)",
| id => "Debian",
| release => {
| full => "9.8",
| major => "9",
| minor => "8"
| }
| },
| family => "Debian",
| hardware => "x86_64",
| name => "Debian",
| release => {
| full => "9.8",
| major => "9",
| minor => "8"
| },
| selinux => {
| enabled => false
| }
| }
While the facter package from and on Debian/stretch behaves as follows:
| $ apt-cache policy facter
| facter:
| Installed: 2.4.6-1
| Candidate: 2.4.6-1
| Version table:
| *** 2.4.6-1 500
| 500 http://cdn-aws.deb.debian.org/debian stretch/main amd64 Packages
| 100 /var/lib/dpkg/status
| $ facter os
| {"name"=>"Debian", "family"=>"Debian", "release"=>{"major"=>"9", "minor"=>"8", "full"=>"9.8"}, "lsb"=>{"distcodename"=>"stretch", "distid"=>"Debian", "distdescription"=>"Debian GNU/Linux 9.8 (stretch)", "distrelease"=>"9.8", "majdistrelease"=>"9", "minordistrelease"=>"8"}}
| $ facter --json os
| {
| "os": {
| "name": "Debian",
| "family": "Debian",
| "release": {
| "major": "9",
| "minor": "8",
| "full": "9.8"
| },
| "lsb": {
| "distcodename": "stretch",
| "distid": "Debian",
| "distdescription": "Debian GNU/Linux 9.8 (stretch)",
| "distrelease": "9.8",
| "majdistrelease": "9",
| "minordistrelease": "8"
| }
| }
| }
Output from facter on Ubuntu/bionic:
| $ facter --version
| 3.10.0
| $ facter os
| {
| architecture => "amd64",
| distro => {
| codename => "bionic",
| description => "Ubuntu 18.04.2 LTS",
| id => "Ubuntu",
| release => {
| full => "18.04",
| major => "18.04"
| }
| },
| family => "Debian",
| hardware => "x86_64",
| name => "Ubuntu",
| release => {
| full => "18.04",
| major => "18.04"
| },
| selinux => {
| enabled => false
| }
| }
We need this workaround for Ubuntu/bionic, as its openjdk-11-jre package
(that's the one being pulled in by default-jre-headless, providing Java
v10) still doesn't seem to work with Jenkins LTS versions.
commit ce32bfe1b041bb959843e0b69cf7b187aa121b19
Merge: f705382 b02b435
Author: Michael Prokop <mika@debian.org>
Date: Thu Apr 4 13:27:08 2019 +0200
Merge remote-tracking branch 'origin/pr/221'
commit f705382d92f5f688335020441238b1bffe38e755
Merge: 629746a ebdff00
Author: Michael Prokop <mika@debian.org>
Date: Thu Apr 4 11:37:27 2019 +0200
Merge remote-tracking branch 'origin/pr/222'
commit ebdff0077a9d4c7f49f22daab13ae7fade312b8c
Author: Victor Seva <linuxmaniac@torreviejawireless.org>
Date: Mon Mar 25 11:42:19 2019 +0100
piuparts_wrapper: enable --mirror parameter
We can't rely on what's defined in the base tgz file, since the environment might still refer to
a mirror that no longer exists as such. For example with current wheezy repository (that has been
moved to archive.debian.org) piuparts runs might fail with:
| W: Failed to fetch http://deb.debian.org/debian/dists/wheezy/main/binary-i386/Packages 404 Not Found
| [...]
| E: Some index files failed to download. They have been ignored, or old ones used instead.
commit b02b43587dd2e6c2a074397fdecba67233cb305e
Author: Kienan Stewart <kienan@koumbit.org>
Date: Fri Mar 22 13:52:42 2019 -0400
Remove usage of SUDO_CMD from generate-reprepro-codename
The script generate-reprepro-codename is already called by SUDO_CMD (so,
as the reprepro user if necessary) from build-and-provide-package.
Fixes #220
commit 629746ae15a177020766bb8ad16b2f630b7b02a9
Author: Michael Prokop <mika@debian.org>
Date: Tue Mar 5 11:25:35 2019 +0100
perlcritic_tap: properly fail if provided file can't be read
Make behavior consistent with the other tap scripts.
Otherwise we'll report a failing test instead of exiting early:
| % tap/perlcritic_tap /doesnotexist
| 1..26
| not ok 1 No such file or directory: '/doesnotexist'
| not ok 2 Usage:
| not ok 3 perlcritic [-12345 | --brutal | --cruel | --harsh | --stern | --gentle]
| not ok 4 [--severity number | name] [{-p | --profile} file | --noprofile]
| not ok 5 [--top [ number ]] [--theme expression] [--include pattern]
| not ok 6 [--exclude pattern] [{-s | --single-policy} pattern]
| not ok 7 [--only | --noonly] [--profile-strictness {warn|fatal|quiet}]
| [...]
Development sponsored by Sipwise GmbH, recorded as
TT#29615 in customers' ticket system.
commit ebb7c31326c78158cee26b2cf46ae912f27c0bff
Author: Michael Prokop <mika@debian.org>
Date: Thu Feb 28 10:15:48 2019 +0100
remove-reprepro-codename: also get rid of package indices files
Quoting the "clearvanished" section of reprepro(1):
| Do not forget to remove all exported package indices manually"
If we don't manually remove them, files like those will persist:
| mprokop@jenkins2 /srv/mirror/autobuild/dists % find gerrit_TT53525_review27568
| gerrit_TT53525_review27568
| gerrit_TT53525_review27568/Release
| gerrit_TT53525_review27568/Release.gpg
| gerrit_TT53525_review27568/InRelease
| gerrit_TT53525_review27568/main
| gerrit_TT53525_review27568/main/source
| gerrit_TT53525_review27568/main/source/Release
| gerrit_TT53525_review27568/main/source/Sources.gz
| gerrit_TT53525_review27568/main/debian-installer
| gerrit_TT53525_review27568/main/debian-installer/binary-i386
| gerrit_TT53525_review27568/main/debian-installer/binary-i386/Packages
| gerrit_TT53525_review27568/main/debian-installer/binary-i386/Packages.gz
| gerrit_TT53525_review27568/main/debian-installer/binary-amd64
| gerrit_TT53525_review27568/main/debian-installer/binary-amd64/Packages
| gerrit_TT53525_review27568/main/debian-installer/binary-amd64/Packages.gz
| gerrit_TT53525_review27568/main/binary-i386
| gerrit_TT53525_review27568/main/binary-i386/Release
| gerrit_TT53525_review27568/main/binary-i386/Packages
| gerrit_TT53525_review27568/main/binary-i386/Packages.gz
| gerrit_TT53525_review27568/main/binary-amd64
| gerrit_TT53525_review27568/main/binary-amd64/Release
| gerrit_TT53525_review27568/main/binary-amd64/Packages
| gerrit_TT53525_review27568/main/binary-amd64/Packages.gz
Development sponsored by Sipwise GmbH, recorded as
TT#53758 in customers' ticket system.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/j/jenkins-debian-glue.png){kind=link}