Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
Control: block 1067439 with -1
Control: affects -1 + src:cpu
[ Reason ]
The last QA upload four years ago fixed a FTBFS (multiple definitions of
a global variable) by replacing tha
Processing control commands:
> block 1067439 with -1
Bug #1067439 {Done: Andreas Beckmann } [cpu] cpu: undefined
symbol globalLdap in libcpu_ldap.so on Debian 12
1067439 was not blocked by any bugs.
1067439 was not blocking any bugs.
Added blocking bug(s) of 1067439: 1069880
> affects -1 + src:cp
Fellow Developers,
you are probably aware of the time_t-64bit migration :-)
However, this does not magically transition all data formats to 64bit
times. One such instance is the set of utmp/wtmp and lastlog files.
Thorsten Kukuk and others have been working on replacements for the
existing file f
Processing control commands:
> affects -1 + src:ansible
Bug #1069891 [release.debian.org] bookworm-pu: package
ansible/7.7.0+dfsg-3+deb12u1
Added indication that 1069891 affects src:ansible
--
1069891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069891
Debian Bug Tracking System
Contact
> "Chris" == Chris Hofstaedtler writes:
Chris> Fellow Developers,
Chris> you are probably aware of the time_t-64bit migration :-)
Chris> However, this does not magically transition all data formats to 64bit
Chris> times. One such instance is the set of utmp/wtmp and lastlog fi
On Fri, 26 Apr 2024 15:05:00 +0200 Lee Garrett wrote:
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: ansi...@packages.debian.org, deb...@rocketjump.eu
Control: affects -1 + src:ansible
Hi,
I'm requesting to bu
On Fri, 26 Apr 2024 at 12:30, Chris Hofstaedtler wrote:
>
> Fellow Developers,
>
> you are probably aware of the time_t-64bit migration :-)
> However, this does not magically transition all data formats to 64bit
> times. One such instance is the set of utmp/wtmp and lastlog files.
>
> Thorsten Kuk
Hi,
I'm not sure how we reached this situation but there are a bunch of
packages in trixie that are not in a suitable state. To reproduce, a
simple `debootstrap trixie /tmp/trixie` on amd64 is sufficient.
Note: I've limited my exploration to amd64, which kept me busy already…
An obvious first pr
Cyril Brulebois (2024-04-26):
> Anyway, I wanted to see if suggesting (I wouldn't go as far as requesting
> because I'm really not sure this would be the right course of action, more
> details below) a new binNMU of coreutils within testing would be
> sufficient to make trixie debootstrap-able aga
Hi
we've been made aware on #d-release that my hints broke debootstrap. I
am working through the remaining packages that are relevant for
debootstrap, but it takes some time.
On 2024-04-26 18:35:59 +0200, Cyril Brulebois wrote:
> I'm not sure how we reached this situation but there are a bunch of
Processing commands for cont...@bugs.debian.org:
> block 1054631 by 1068954
Bug #1054631 [libnvme1] random memory corruption with some NVMe devices
1054631 was not blocked by any bugs.
1054631 was not blocking any bugs.
Added blocking bug(s) of 1054631: 1068954
> thanks
Stopping processing here.
Processing control commands:
> affects -1 + src:kimageannotator
Bug #1069919 [release.debian.org] transition: kimageannotator
Added indication that 1069919 affects src:kimageannotator
--
1069919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069919
Debian Bug Tracking System
Contact ow...@b
Package: release.debian.org
Control: affects -1 + src:kimageannotator
X-Debbugs-Cc: kimageannota...@packages.debian.org couc...@debian.org
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: by...@debian.org
Severity: normal
I would like to initiate the following listed
13 matches
Mail list logo
