jenkins-debian-glue (0.23.6)
[PTS] [DDPO]
COMMITS: VCS has seen 7 commits since the v0.23.6 tag
- Git: https://github.com/mika/jenkins-debian-glue.git
-
- Branch: master
- Path: debian/changelog
- Repo size: 540672
- Browser: https://github.com/mika/jenkins-debian-glue
- Last scan: 2026-03-10 07:10:09+00
- Next scan: 2026-03-11 05:22:00+00
- Debian changelog in Git:
jenkins-debian-glue (0.23.6) unstable; urgency=medium
[ Guillem Jover ]
* [52c40f3] build: Mark all current targets as .PHONY
* [a7e6ca4] build: Split the test suite into its own check target
* [9552ba2] build: Do not remove Debian packaging artifacts from the
clean target
* [389076c] build: Remove target dependency on shell glob pattern
* [94d8184] build: Use GNU Make wildcard function instead of a raw shell
glob pattern
* [4a3f89a] build: For correctness make install and deploy depend on the
build target
Those changes fix the FTBFS with the nocheck build profile
(Closes: #1116758)
-- Michael Prokop <mika@debian.org> Fri, 03 Oct 2025 13:42:03 +0200
- This branch is 7 commits ahead of tag v0.23.6
- Git log:
commit 29ccbab6fac0e62eb7b084ef4c42ab1a56128ac6
Merge: a251392 22fee1f
Author: Michael Prokop <115592+mika@users.noreply.github.com>
Date: Mon Feb 9 18:16:44 2026 +0100
Merge pull request #253 from guillemj/pu/pycodestyle-fixes
Fix pycodestyle issues
commit 22fee1f773c6ed270b9c1881a80bde1ffc9a7ab1
Author: Guillem Jover <gjover@sipwise.com>
Date: Fri Feb 6 17:21:41 2026 +0100
Fix pycodestyle issues
- Add pyproject.toml and tox.ini with consistent black and pycodestyle
settings.
- Run black for consistent coding style.
- Manually fix remaining issues:
+ Shorten comment lines and remove initial excess hash character.
+ Do not import multiple modules at the same time.
Warned-by: pycodestyle
Change-Id: I4e79c09a41ce1f7111a0d905110acd4cf9abd613
commit a251392ee91c53db0d0d5e41f4bf07f2fc7dcc69
Merge: d718db0 2cf878f
Author: Victor Seva <linuxmaniac@torreviejawireless.org>
Date: Tue Jan 13 10:20:47 2026 +0100
Merge pull request #252 from mika/mika/wrap
debian/control: wrap-and-sort -sat
commit 2cf878fedbf676e6a267d509498f9176ab2cb66c
Author: Michael Prokop <mika@jenkins-debian-glue.org>
Date: Tue Jan 13 10:10:16 2026 +0100
debian/control: wrap-and-sort -sat
wrap-and-sort has a new sorting behavior
commit d718db0b49979ec01b10e225d287348acf2d92ad
Author: Michael Prokop <mika@jenkins-debian-glue.org>
Date: Tue Jan 13 09:45:46 2026 +0100
Revert "build-and-provide-package: support usage of Debian packages without Priority field with bookworm and older"
This reverts commit f1eb26d9b955aa647e83b32a753d0c8c8bc68742.
Packages without the `Priority` field need to be built in environments
with Debian trixie and newer, do not work around this problem in
reprepro.
See https://github.com/mika/jenkins-debian-glue/pull/251 for further
information.
Thanks: Guillem Jover
commit 72e6ad9c98c84b4bdf56cf449665e6825de73780
Merge: bc4c414 f1eb26d
Author: Michael Prokop <115592+mika@users.noreply.github.com>
Date: Mon Jan 12 12:21:19 2026 +0100
Merge pull request #251 from mika/mika/priority
build-and-provide-package: support usage of Debian packages without Priority field with bookworm and older
commit f1eb26d9b955aa647e83b32a753d0c8c8bc68742
Author: Michael Prokop <mika@jenkins-debian-glue.org>
Date: Mon Jan 12 11:58:24 2026 +0100
build-and-provide-package: support usage of Debian packages without Priority field with bookworm and older
The «Priority: optional» field is the default nowadays with
Debian/trixie, so it might not be present explicitly in the Debian
package any longer.
Building packages for Debian/trixie and newer works fine,
though when building packages for Debian/bookworm and older,
their inclusion might fail in reprepro repositories with:
| + sudo reprepro -b /srv/mirror/autobuild -v --waitforlock 1000 --ignore=wrongdistribution --ignore=uploaders --ignore=surprisingbinary include internal-bookworm [snip]_amd64.changes
| .changes put in a distribution not listed within it!
| Ignoring as --ignore=wrongdistribution given.
| No priority specified for '/var/lib/jenkins/workspace/[snip]-repos/binaries/[snip]_amd64.changes'!
| There have been errors!
Work around this issue, by explicitly setting --priority=optional in the
`reprepro ... [include|copymatched|processincoming]` command lines.
FTR, quoting from reprepro(1):
| -P, --priority priority
| Overrides the priority of inclusions. (Also override possible override files
So this potentially might have side-effects in certain configurations,
but the inclusion failure so far turned out to be more pressing.
Development sponsored by Sipwise GmbH, recorded as
MT#64075 in customers' ticket system.