* Yves-Alexis Perez [2025-07-22 08:04]:
On Mon, 2025-07-21 at 18:55 +0200, Jochen Sprickerhof wrote:
> So, it seems to work on Bookworm -> Trixie but won't that mean we'll have
> the
> same problem again (for those installs) in Trixie -> Forky if I remove the
> alternate dependency at that poin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2025-07-21 at 18:55 +0200, Jochen Sprickerhof wrote:
> > So, it seems to work on Bookworm -> Trixie but won't that mean we'll have
> > the
> > same problem again (for those installs) in Trixie -> Forky if I remove the
> > alternate dependency
Control: retitle -1 devscripts: test_debsign fails when aspcud resolver is used
to determine build dependencies
On Mon, Jul 21, 2025 at 11:16:53PM +0200, Yadd wrote:
On 7/21/25 23:03, James McCoy wrote:
On Mon, Jul 21, 2025 at 02:43:21AM +0200, Yadd wrote:
On 7/21/25 02:20, Yadd wrote:
On 7/
Processing control commands:
> retitle -1 devscripts: test_debsign fails when aspcud resolver is used to
> determine build dependencies
Bug #1109607 [devscripts] devscripts: GPG part of tests starting to fail
Changed Bug title to 'devscripts: test_debsign fails when aspcud resolver is
used to de
Processing commands for cont...@bugs.debian.org:
> tags 1105124 + trixie-ignore
Bug #1105124 {Done: Paul Gevers } [src:jsonnet] src:jsonnet:
fails to migrate to testing for too long
Added tag(s) trixie-ignore.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
11051
Source: golang-github-mitchellh-hashstructure
Severity: serious
Version: 2.0.2-1
Hi, the github.com/mitchellh/hashstructure go package exists twice in
Debian, under the names golang-github-mitchellh-hashstructure and
golang-github-mitchellh-hashstructure-v2. Regardless of the name, they
both s
Processing commands for cont...@bugs.debian.org:
> severity 1104638 normal
Bug #1104638 {Done: Colin Watson } [python3-icalendar]
python3-icalendar: Depends on a transitional package
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance
On Mon, Jul 21, 2025 at 10:05:52PM +0100, Colin Watson wrote:
> I think the python-icalendar change was correct: python-icalendar doesn't
> really need pytz any more (it just has some affordances for the case where
> pytz is installed), and the cases that broke all imported pytz directly.
Ok, I t
On 7/21/25 23:03, James McCoy wrote:
On Mon, Jul 21, 2025 at 02:43:21AM +0200, Yadd wrote:
On 7/21/25 02:20, Yadd wrote:
On 7/20/25 20:47, Yadd wrote:
Starting from today, test_mkorigtargz, test_debsign and some
test_uscan*
fail due to some gpg errors:
- short keyid looks forbidden now
- $GPG
Processing control commands:
> severity -1 important
Bug #1108038 [glx-diversions] sddm does not start after trixie upgrade
Severity set to 'important' from 'grave'
> retitle -1 glx-diversions: libgl.so.1 symlink may disappear if installed
> without nvidia driver
Bug #1108038 [glx-diversions] sdd
Control: severity -1 important
Control: retitle -1 glx-diversions: libgl.so.1 symlink may disappear if
installed without nvidia driver
On 7/21/25 19:52, Rainer Dorsch wrote:
Note: I accidentally installed the glx-alternative packages, I don't have any
nvidia hardware. Thus I removed these packa
Your message dated Mon, 21 Jul 2025 22:05:52 +0100
with message-id
and subject line Re: python3-icalendar: Depends on a transitional package
has caused the Debian Bug report #1104638,
regarding python3-icalendar: Depends on a transitional package
to be marked as done.
This means that you claim th
On Mon, Jul 21, 2025 at 02:43:21AM +0200, Yadd wrote:
On 7/21/25 02:20, Yadd wrote:
On 7/20/25 20:47, Yadd wrote:
Starting from today, test_mkorigtargz, test_debsign and some test_uscan*
fail due to some gpg errors:
- short keyid looks forbidden now
- $GPGHOME should be chmod 700
- even after t
Processing commands for cont...@bugs.debian.org:
> # not 100% fixed yet and the current partial fix breaks other packages
> reopen 1104638
Bug #1104638 {Done: Colin Watson } [python3-icalendar]
python3-icalendar: Depends on a transitional package
'reopen' may be inappropriate when a bug has been
Hi Andreas,
thanks for following-up.
Am Montag, 21. Juli 2025, 11:48:22 Mitteleuropäische Sommerzeit schrieb
Andreas Beckmann:
> On Thu, 26 Jun 2025 17:40:36 +0200 Jochen Sprickerhof
>
> wrote:
> > Control: reassign -1 glx-diversions
> >
> > * Rainer Dorsch [2025-06-23 23:27]:
> > >I found a
Paul,
On Mon, Jul 21, 2025 at 06:27:33PM +0200, Paul Gevers wrote:
> If the timestamp is put in the (far) future, the action you want to trigger
> might not happen. What is the timestamp used for?
To filter the list of systemd units that are reprocessed: only those modified
more
recently than th
* Yves-Alexis Perez [2025-07-21 18:50]:
On Mon, 2025-07-21 at 18:42 +0200, Yves-Alexis Perez wrote:
> If both should be in trixie I would say:
>
> Package: strongswan
> Depends: charon-systemd | strongswan-charon, strongswan-swanctl
Ah, good point, that might work, let's try that. I'll repor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2025-07-21 at 18:42 +0200, Yves-Alexis Perez wrote:
> > If both should be in trixie I would say:
> >
> > Package: strongswan
> > Depends: charon-systemd | strongswan-charon, strongswan-swanctl
>
> Ah, good point, that might work, let's try
retitle 1109499 bacula-common: preinst intentionally aborts unattended upgrade
of bacula-director
Hi,
first off: let's be clear as to what is happening. We aren't
"intentionally break"ing upgrades.
Paul Gevers writes:
> On Sun, 20 Jul 2025 12:27:53 +0200 Niels Thykier wrote:
>> Perharps deb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2025-07-21 at 18:40 +0200, Jochen Sprickerhof wrote:
> > strongswan-charon is the "historical" (legacy) charon daemon, which is
> > beeing
> > phased out in favor of charon-systemd. That's why we updated the
> > dependency
> > for the strongs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2025-07-21 at 18:12 +0200, Jochen Sprickerhof wrote:
> > I have no idea why apt doesn't want to 'change charon-systemd:amd64'.
>
> The problem is that bookworm apt prefers keeping strongswan-charon
> installed over other solutions. This is
Hi,
On 21-07-2025 13:54, Mark Hindley wrote:
I did think about it when I first used that path: only the mtime of the .stamp
file is used (passed to find's -ctime option). I couldn't think of an adverse
security implication. Although, maybe I am not sufficiently imaginative? What
have I missed or
Hi Yves-Alexis,
* Yves-Alexis Perez [2025-07-20 16:29]:
I'm still not sure it's the right solution but I tried to add:
Package: charon-systemd
[...]
Replaces: strongswan-charon (<< 6.0.1-1~)
But I still get the same during the upgrade:
Investigating (0) strongswan:amd64 < 5.9.8-5+deb12u1 ->
Processing commands for cont...@bugs.debian.org:
> reopen 1109561
Bug #1109561 {Done: Jérémy Lal } [src:receptor] receptor:
flaky autopkgtest: panic: Fail in goroutine after TestTCPProxyServiceOutbound
has completed
'reopen' may be inappropriate when a bug has been closed with a version;
all fix
Your message dated Mon, 21 Jul 2025 14:48:58 +
with message-id
and subject line Bug#1109454: fixed in cdebootstrap 0.7.9
has caused the Debian Bug report #1109454,
regarding cdebootstrap: autopkgtest regression: Couldn't download Release!
to be marked as done.
This means that you claim that t
Paul,
Thanks for this.
On Sat, Jul 19, 2025 at 10:58:02AM +0200, Paul Gevers wrote:
> On Sat, 12 Jul 2025 15:38:41 +0100 Mark Hindley wrote:
> > + # Remove any timestamp to force regeneration of all scripts.
> > + rm -f /var/tmp/${DPKG_MAINTSCRIPT_PACKAGE}.stamp
>
> This is a very predictab
Your message dated Mon, 21 Jul 2025 11:49:55 +
with message-id
and subject line Bug#1109561: fixed in receptor 1.5.5-2
has caused the Debian Bug report #1109561,
regarding receptor: flaky autopkgtest: panic: Fail in goroutine after
TestTCPProxyServiceOutbound has completed
to be marked as don
Processing control commands:
> tag -1 pending
Bug #1109561 [src:receptor] receptor: flaky autopkgtest: panic: Fail in
goroutine after TestTCPProxyServiceOutbound has completed
Added tag(s) pending.
--
1109561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109561
Debian Bug Tracking System
Control: tag -1 pending
Hello,
Bug #1109561 in receptor reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/receptor/-/commit/b7ec813f983b594d3463d
Your message dated Mon, 21 Jul 2025 10:19:46 +
with message-id
and subject line Bug#1109174: fixed in openfst 1.8.4-3
has caused the Debian Bug report #1109174,
regarding libfst-dev: fails to upgrade from bookworm because of libfst26
to be marked as done.
This means that you claim that the pr
On Thu, 26 Jun 2025 17:40:36 +0200 Jochen Sprickerhof
wrote:
Control: reassign -1 glx-diversions
* Rainer Dorsch [2025-06-23 23:27]:
>I found a workaround to make my system work again:
>
>root@h370:/usr/lib/x86_64-linux-gnu# ln -s libGL.so libGL.so.1
>root@h370:/usr/lib/x86_64-linux-gnu# ln -s
So are these the right patches? It seems both
golang-github-golang-protobuf-1-3 and golang-github-golang-protobuf-1-5
uses Conflicts and needs to be modified. The first patch below is for
1-3 and the last one for 1-5. I have limited time so if anyone has time
to test, revise patches and do the u
Your message dated Mon, 21 Jul 2025 09:02:06 +
with message-id
and subject line Bug#1109228: Removed package(s) from unstable
has caused the Debian Bug report #1108471,
regarding libitext1-java: very old, long EOLed, should not be in trixie
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> severity 1108992 normal
Bug #1108992 [src:opendnssec] opendnssec: OpenDNSSEC is (almost) End-of-Life
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1108992: https://bugs.debi
I'll try to work on this bug this week, but IMO, it'd be valid to add a
trixie-ignore tag here.
Cheers,
Thomas Goirand (zigo)
Processing commands for cont...@bugs.debian.org:
> merge 1109655 1109513 1109514 1109515 1109516 1109517
Bug #1109655 [src:golang-github-golang-protobuf-1-5] Must use Breaks/Replaces
instead of Conflicts to allow smooth transition
Bug #1109513 [src:golang-github-golang-protobuf-1-5]
golang-githu
Processing commands for cont...@bugs.debian.org:
> reassign 1109513 src:golang-github-golang-protobuf-1-5
Bug #1109513 [golang-github-golang-protobuf-1-5]
golang-github-denverdino-aliyungo-dev: fails to dist-upgrade from bookworm to
trixie
Bug reassigned from package 'golang-github-golang-protob
Processing commands for cont...@bugs.debian.org:
> reassign 1109513 golang-github-golang-protobuf-1-5
Bug #1109513 [golang-github-denverdino-aliyungo-dev]
golang-github-denverdino-aliyungo-dev: fails to dist-upgrade from bookworm to
trixie
Bug reassigned from package 'golang-github-denverdino-al
Processing commands for cont...@bugs.debian.org:
> merge 1109655 1109513 1109514 1109515 1109516 1109517
Bug #1109655 [src:golang-github-golang-protobuf-1-5] Must use Breaks/Replaces
instead of Conflicts to allow smooth transition
Unable to merge bugs because:
package of #1109515 is 'golang-githu
Source: golang-github-golang-protobuf-1-5
Version: 1.5.4-1
Followup-For: Bug #1109655
Also, the `Conflicts: protoc-gen-go` will be an issue, for the same reason.
-- System Information:
Debian Release: 13.0
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'unstable'),
severity 1108992 normal
thanks
Bastian Germann writes:
> I have already filed bug#1109540 (unblock:
> golang-github-containers-ocicrypt/1.1.10-3)
It seems the autoremoval is more aggresive than the override permission,
with autoremoval removing a lot of packages tomorrow that (indirectly)
depe
Source: golang-github-golang-protobuf-1-5
Version: 1.5.4-1
Severity: serious
As can be seen below, the use of "Conflicts" does not allow for a smooth
transition.
This is policy 7.6.1 - Breaks/Replaces is the normal mecanism for packages
overwriting files of other packages.
Le lun. 21 juil. 20
Control: tag -1 pending
Hello,
Bug #1109470 in ceph reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/ceph-team/ceph/-/commit/7b5ea6c8500ea7676780a572f65751af8121
Processing control commands:
> tag -1 pending
Bug #1109470 [src:ceph] ceph: CVE-2025-52555 regression
Added tag(s) pending.
--
1109470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
44 matches
Mail list logo