On 2023-02-15 13:17:38 -0700, Sam Hartman wrote:
> > "Theodore" == Theodore Ts'o writes:
> the answer to your "how long" is that packages
> >> should also work with the kernel from the previous and the kernel
> >> from the next Debian release.
>
> Theodore> This isn't a problem w
Package: supertuxkart
Version: testing
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: rishincutc...@gmail.com
Dear Maintainer,
* What led up to the situation?
Attempted to backport package to stable. Installed build-d
Package: supertuxkart
Version: testing
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: rishincutc...@gmail.com
Dear Maintainer,
* What led up to the situation?
Attempting to backport supertuxkart, necessary to backport
Package: icingaweb2-module-pdfexport
Version: 0.10.2+dfsg1-1
Severity: grave
The current version of icingaweb2-module-pdfexport depends on chromium.
icingaweb2 is a web service. Depending on a graphical browser in a web
server component is not at all reasonable.
--
Steve Langasek
Processing commands for cont...@bugs.debian.org:
> reassign 1028714 python-mox3
Bug #1028714 [src:nsscache] nsscache: FTBFS: FileNotFoundError: [Errno 2] No
such file or directory
Bug reassigned from package 'src:nsscache' to 'python-mox3'.
No longer marked as found in versions nsscache/0.42-2.
I
Processing commands for cont...@bugs.debian.org:
> fixed 1031336 3.11.2-2
Bug #1031336 {Done: Matthias Klose } [python3-distutils]
python3-distutils is not installable
Marked as fixed in versions python3-stdlib-extensions/3.11.2-2.
> thanks
Stopping processing here.
Please contact me if you need
Processing commands for cont...@bugs.debian.org:
> reassign 1028714 src:python-mox3
Bug #1028714 [python-mox3] nsscache: FTBFS: FileNotFoundError: [Errno 2] No
such file or directory
Bug reassigned from package 'python-mox3' to 'src:python-mox3'.
Ignoring request to alter found versions of bug #1
Processing commands for cont...@bugs.debian.org:
> forwarded 1030407 https://github.com/HenriWahl/Nagstamon/issues/907
Bug #1030407 [src:nagstamon] nagstamon: FTBFS:
pkg_resources.extern.packaging.version.InvalidVersion: Invalid version:
'3.10.1.debianunknown'
Set Bug forwarded-to-address to
'h
Control: tags -1 confirmed
On 13-02-2023 20:45, Andreas Beckmann wrote:
src:nvidia-graphics-drivers recently moved from non-free to
non-free-firmware since the firmware-nvidia-gsp binary package was moved
to that section, too.
Ack.
Tracker reports
autopkgtest for nvidia-graphics-drivers/n/
Processing control commands:
> tags -1 confirmed
Bug #1031238 [debci] debci: fails for source packages in non-free-firmware
Added tag(s) confirmed.
--
1031238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Thu, 16 Feb 2023 10:17:05 +
with message-id
and subject line Bug#1027013: fixed in llvm-toolchain-14 1:14.0.6-11
has caused the Debian Bug report #1027013,
regarding llvm-toolchain-14 autopkg test fails
to be marked as done.
This means that you claim that the problem has be
Hi Helge,
On Thu, 12 Jan 2023 07:36:33 +0100 Helge Kreutzmann
wrote:
I expect upstream to release "this weekend" - but this might be
actually next monday/tuesday.
Then I might take a day or two to package this for unstable.
I think this happened in version 4.17.0-1 and 2. The latter migrate
Your message dated Thu, 16 Feb 2023 10:49:51 +
with message-id
and subject line Bug#1026713: fixed in apache-directory-server 2.0.0~M26-1
has caused the Debian Bug report #1026713,
regarding apache-directory-server: FTBFS due to compatibility issue with mina
2.2
to be marked as done.
This me
Your message dated Thu, 16 Feb 2023 12:12:55 +0100
with message-id <55ab1bc2-7bc8-0b64-c9e3-89fd05474...@gmail.com>
and subject line closing bug
has caused the Debian Bug report #1030601,
regarding findent: autopkgtest regression: original program does not compile
to be marked as done.
This means
* Sebastian Ramacher [Thu Feb 16, 2023 at 09:09:08AM +0100]:
> On 2023-02-15 13:17:38 -0700, Sam Hartman wrote:
> > But for example you're not leaving a lot of time for asking programs
> > like vmdb2 or fai-diskimage to adjust how they call fsck.
> > If you made this change a few months ago, it wo
> The current version of icingaweb2-module-pdfexport depends on chromium.
All versions are like thes.
> icingaweb2 is a web service. Depending on a graphical browser in a web
> server component is not at all reasonable.
I know, but upstream considers this to be the best possible way to solve
th
Package: dm-writeboost-dkms
Version: 2.2.15-1
Followup-For: Bug #1029261
Dear Maintainer,
there is a new version - 2.2.16 - available:
https://github.com/akiradeveloper/dm-writeboost/archive/refs/tags/v2.2.16.tar.gz
Regards,
Matthias
NB: Apparently at present the watch line of uscan doesn't mat
Control: severity wishlist
Hi Rishi,
On Thu, 16 Feb 2023 00:25:54 -0800, Rishi Cutchin
wrote:
>* What led up to the situation?
> Attempted to backport package to stable. Installed build-dependencies
> with mk-build-deps --install --remove
>
>* What exactly did you do (or not do) that w
Control: severity normal
Hi Rishi,
On Thu, 16 Feb 2023 00:29:33 -0800, Rishi Cutchin
wrote:
>* What led up to the situation?
> Attempting to backport supertuxkart, necessary to backport glslang
> aswell.
>
>* What exactly did you do (or not do) that was effective (or
> ineffective)
Processing commands for cont...@bugs.debian.org:
> severity 1031387 normal
Bug #1031387 [supertuxkart] supertuxkart: Fails to compile due to inescaped +,
bug in shaderc
Severity set to 'normal' from 'serious'
> severity 1031386 wishlist
Bug #1031386 [supertuxkart] supertuxkart: Depends on newer v
Package: libsnappy1v5
Version: 1.1.8-1
Severity: grave
Tags: patch
Dear Laszlo,
During my tests with Ceph, I noticed a grave regression: Ceph OSD (the process
that does the actual storage for Ceph) cannot use Snappy anymore, because it
can't find one symbole related to RTTI.
The consequence is t
Package: tzdata
Version: 2022g-3
Severity: critical
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
in version 2022g-3, the /etc/timezone file has been removed and gets purged
from user's computers. This makes unrelated software break that relies on this
file. Examples are samizdat and ruby-
Processing commands for cont...@bugs.debian.org:
> severity 1031396 serious
Bug #1031396 [gnome] Unable to upgrade to *gnome* 1:43+1 with `apt full-upgrade`
Severity set to 'serious' from 'normal'
> affects 1031396 src:pipewire
Bug #1031396 [gnome] Unable to upgrade to *gnome* 1:43+1 with `apt ful
Your message dated Thu, 16 Feb 2023 13:19:17 +
with message-id
and subject line Bug#1030407: fixed in nagstamon 3.10.1+ds1-4
has caused the Debian Bug report #1030407,
regarding nagstamon: FTBFS:
pkg_resources.extern.packaging.version.InvalidVersion: Invalid version:
'3.10.1.debianunknown'
t
Hi,
it seems to me that in postinst, instead of
if $do_systemd
then
systemctl start pmcd.service >/dev/null
systemctl start pmlogger.service >/dev/null
elif which invoke-rc.d >/dev/null 2>&1
then
invoke-rc.d pmcd start
invoke-rc.d pmlogger start
else
/etc/init.d/pmcd start
Package: rsyslog
Version: 8.2212.0-1
Severity: serious
Hi,
When removing the systemv init scripts from rsyslog (which can be
managed by orphan-sysvinit-scripts), the following was also removed from
/usr/lib/rsyslog/rsyslog-rotate:
else
invoke-rc.d rsyslog rotate > /dev/null
This means on
Hello Paul,
On Thu, Feb 16, 2023 at 11:20:18AM +0100, Paul Gevers wrote:
> On Thu, 12 Jan 2023 07:36:33 +0100 Helge Kreutzmann
> wrote:
> > I expect upstream to release "this weekend" - but this might be
> > actually next monday/tuesday.
> >
> > Then I might take a day or two to package this for
> "Sebastian" == Sebastian Ramacher writes:
Sebastian> To better understand the impact of this change, I was
Sebastian> wondering which tools / image builders in the archive
Sebastian> would be affected by this change. I've cloned the bug to
Sebastian> vmdb2, but what about o
I came across this bug from Wookey linking to it from the debian-arm
mailing list. I also ran into this bug in Guix and I managed to track
down an upstream bug report about it¹. Short version is that upstream
now knows about it, and tar-1.35 will default to enabling 64-bit time_t.
¹ https://lists
Hi Helge,
On 16-02-2023 15:54, Helge Kreutzmann wrote:
There is one small issue left, so I probably will issue another
backport upload this weekend, but otherwise - this is (hopefully)
completely resolved.
This bug is currently marked RC and hence it showed up on my radar. If
you fix RC issue
Your message dated Thu, 16 Feb 2023 16:21:59 +0100
with message-id <20230216152159.GA24101@Debian-50-lenny-64-minimal>
and subject line Re: Bug#1028233: xz-utils: tries to overwrite files in
manpages-fr (4.16.0-3~bpo11+1)
has caused the Debian Bug report #1028233,
regarding xz-utils: tries to over
Hi Adrian,
Thanks for that. I was reading up on this 'source only' uploads. In general I
agree with the idea, however for cmucl when a new major version gets released
the rebuilding of the new version using the old version is non-trivial and not
automated.
So for major releases I do the rebuil
On Wed, Feb 15, 2023 at 07:39:28PM -0800, Russ Allbery wrote:
> It had never occurred to me before that the version of the system on which
> I run mke2fs would matter as long as I didn't pick a newer file system
> type (ext5 or something). Now I know! Until today, I had no idea ext4
> even *had*
On Thu, Feb 16, 2023 at 04:36:33PM +0100, Peter Van Eynde wrote:
> Hi Adrian,
Hi Peter,
> Thanks for that. I was reading up on this 'source only' uploads. In general I
> agree with the idea, however for cmucl when a new major version gets released
> the rebuilding of the new version using the o
On Wed, Feb 15, 2023 at 12:05:41AM +0100, Daniel Leidert wrote:
>...
> Reasons:
>...
> - - the change makes it impossible to create filesystems with this version of
> e2fsprogs and then run a grub-install from a target system that does not
> cope
> with that feature; basically breaking the deb
Hello.
I'm not a trac user myself, but I've noticed that trac has just been
removed from testing today.
AFAIK, the main reason trac was not ready for Debian 12 was the
problems with python3, but those in theory have been fixed
by version 1.5.4-1 (bug #1030413).
Therefore: Should not this bug (#
Am Donnerstag, dem 16.02.2023 um 18:37 +0200 schrieb Adrian Bunk:
> On Wed, Feb 15, 2023 at 12:05:41AM +0100, Daniel Leidert wrote:
> > ...
> > Reasons:
> > ...
> > - - the change makes it impossible to create filesystems with this version
> > of
> > e2fsprogs and then run a grub-install from a
Sorry. I said:
Therefore: Should not this bug (#1024647) be closed accordingly?
I really meant *this* bug, #988462, i.e. "trac: not ready for Debian 12".
(But while we are at it, the other bug is fixed but not closed and maybe
it should be closed as well).
Thanks.
On Thu, Feb 16, 2023 at 05:48:22PM +0100, Daniel Leidert wrote:
> Am Donnerstag, dem 16.02.2023 um 18:37 +0200 schrieb Adrian Bunk:
> > On Wed, Feb 15, 2023 at 12:05:41AM +0100, Daniel Leidert wrote:
> > > ...
> > > Reasons:
> > > ...
> > > - - the change makes it impossible to create filesystems w
> "Adrian" == Adrian Bunk writes:
Adrian> On Thu, Feb 16, 2023 at 05:48:22PM +0100, Daniel Leidert wrote:
>> Am Donnerstag, dem 16.02.2023 um 18:37 +0200 schrieb Adrian Bunk:
>> > On Wed, Feb 15, 2023 at 12:05:41AM +0100, Daniel Leidert wrote:
>> > > ... > > Reasons: > > ...
Hello,
On Sun 01 Jan 2023 at 05:15PM +01, Paul Gevers wrote:
> Hi Sean,
>
> On Mon, 22 Aug 2022 14:29:56 -0700 Sean Whitton
> wrote:
>> control: severity 1017906 wishlist
>
>> > Is there ftp team consensus that either or both of these issues are RC?
>> #1017892 is wishlist or not a bug. [...]
>
Am Donnerstag, dem 16.02.2023 um 20:10 +0200 schrieb Adrian Bunk:
[..]
> I am currently spending time trying to summarize the situation and open
> questions, and I am a bit underwhelmed by the inaccuracies and lack of
> technical detail in your emails.
Well, I didn't have weeks to prepare. I had
On 2023-02-16 17:44, Santiago Vila wrote:
> AFAIK, the main reason trac was not ready for Debian 12 was the
> problems with python3, but those in theory have been fixed
1.5.x is the development branch of Trac and I would like to wait for the
official 1.6 release. It probably comes to late for De
Your message dated Thu, 16 Feb 2023 19:19:53 +
with message-id
and subject line Bug#1031223: fixed in python-streamz 0.6.4-1
has caused the Debian Bug report #1031223,
regarding python-streamz: FTBFS (failing tests)
to be marked as done.
This means that you claim that the problem has been dea
Processing control commands:
> tags -1 +moreinfo
Bug #1031394 [libsnappy1v5] Please re-enable RTTI support in Sid/Bookworm,
needed by at least Ceph
Added tag(s) moreinfo.
--
1031394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031394
Debian Bug Tracking System
Contact ow...@bugs.debian.o
Control: tags -1 +moreinfo
Dear Thomas,
On Thu, Feb 16, 2023 at 1:51 PM Thomas Goirand wrote:
> During my tests with Ceph, I noticed a grave regression: Ceph OSD (the process
> that does the actual storage for Ceph) cannot use Snappy anymore, because it
> can't find one symbole related to RTTI.
Sam Hartman writes:
> * Anyone could prepare patches to image building software to use mkfs
> options that will work with bullseye. You could also try to prepare
> patches to run mkfs out of a chroot or container of the guest OS for
> the image. I appreciate Russ strongly favors this solu
On Thu, Feb 16, 2023 at 08:02:11PM +0100, Daniel Leidert wrote:
>...
> Most server providers have exctly *one*
> rescue system from where I can do a clean installation with deboostrap
> (and that even usually is a Debian). I cannot choose to use one that
> hasn't an e2fsprogs that has this breaking
Your message dated Thu, 16 Feb 2023 20:52:02 +0100
with message-id
and subject line Accepted git 1:2.39.2-1 (source) into unstable
has caused the Debian Bug report #1031310,
regarding git: CVE-2023-22490 CVE-2023-23946
to be marked as done.
This means that you claim that the problem has been deal
Disclaimer:
Like everyone else except Sebastian who commented in this bug so far,
I am not a member of the release team.
Below is my attempt to give an overview of the situation,
feel free to amend/correct if anything is missing or wrong.
1. Image creation tools need special cases for older dist
Replying off list, because I don't think it matters much for the RT
discussion.
> "Russ" == Russ Allbery writes:
Russ> Yes, I'm probably understating the difficulty of making this
Russ> change in practice inside image building software as it's
Russ> currently constructed.
R
On Thu, Feb 16, 2023 at 12:45:20PM +0100, David Kunz wrote:
> > The current version of icingaweb2-module-pdfexport depends on chromium.
> All versions are like thes.
icingaweb2-module-pdfexport 0.9.1-2 did not have such a dependency.
> > icingaweb2 is a web service. Depending on a graphical bro
> "Adrian" == Adrian Bunk writes:
Adrian> Below is my attempt to give an overview of the situation,
Adrian> feel free to amend/correct if anything is missing or wrong.
I believe your summary is correct and includes the issues I am aware of.
I believe I am following things enough tha
Processing control commands:
> severity -1 wishlist
Bug #1031399 [rsyslog] rsyslog: Log rotation broken on non-systemd systems
Severity set to 'wishlist' from 'serious'
> retitle -1 document log rotation on non-default inits
Bug #1031399 [rsyslog] rsyslog: Log rotation broken on non-systemd system
Control: severity -1 wishlist
Control: retitle -1 document log rotation on non-default inits
Am 16.02.23 um 15:41 schrieb Matthew Vernon:
Package: rsyslog
Version: 8.2212.0-1
Severity: serious
Hi,
When removing the systemv init scripts from rsyslog (which can be
managed by orphan-sysvinit-scri
Your message dated Thu, 16 Feb 2023 20:42:52 +
with message-id
and subject line Bug#1031394: fixed in snappy 1.1.9-3
has caused the Debian Bug report #1031394,
regarding Please re-enable RTTI support in Sid/Bookworm, needed by at least Ceph
to be marked as done.
This means that you claim that
On Wed, Feb 15, 2023 at 12:05:41AM +0100, Daniel Leidert wrote:
>...
> Instead, turning on this feature should be postponed for the next release
> cycle
> where a proper transition can be done.
>...
On Thu, Feb 16, 2023 at 08:02:11PM +0100, Daniel Leidert wrote:
>...
> You completely miss the poi
The issue is a failing test in test/run_tests.bash:
head fish1.png > ${tmpdir}/fake.png
"$pdiff" --verbose fish1.png ${tmpdir}/fake.png 2>&1 | grep -q 'Failed to
load'
rm -f ${tmpdir}/fake.png
Here it's making sure that we are able to detect a corrupt .png file,
and to throw an error. The
Processing control commands:
> found -1 clinfo/3.0.23.01.25-1
Bug #1031414 [src:clinfo, src:libgpuarray] clinfo breaks libgpuarray
autopkgtest on i386: numerical deltas
Marked as found in versions clinfo/3.0.23.01.25-1.
> found -1 libgpuarray/0.7.6-13
Bug #1031414 [src:clinfo, src:libgpuarray] cl
Source: clinfo, libgpuarray
Control: found -1 clinfo/3.0.23.01.25-1
Control: found -1 libgpuarray/0.7.6-13
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of clinfo the autopkgtest of libgpuarray fails i
On 2023-02-16 12:24:01 +0100, Michael Prokop wrote:
> * Sebastian Ramacher [Thu Feb 16, 2023 at 09:09:08AM +0100]:
> > On 2023-02-15 13:17:38 -0700, Sam Hartman wrote:
>
> > > But for example you're not leaving a lot of time for asking programs
> > > like vmdb2 or fai-diskimage to adjust how they
On 2023-02-16 07:54:52 -0700, Sam Hartman wrote:
> > "Sebastian" == Sebastian Ramacher writes:
>
> Sebastian> To better understand the impact of this change, I was
> Sebastian> wondering which tools / image builders in the archive
> Sebastian> would be affected by this change. I'
Control: clone -1 -2
Control: reassign -2 fai 6.0
Control: clone -1 -3
Control: reassign -3 grml-debootstrap 0.102
On 2023-02-15 21:04:36 +0100, Sebastian Ramacher wrote:
> Control: clone -1 -2
> Control: reassign -2 vmdb2 0.26-2
>
> On 2023-02-14 01:01:38 +0100, Daniel Leidert wrote:
> > Hi Stev
Processing control commands:
> clone -1 -2
Bug #1030939 [e2fsprogs] e2fsprogs: generates filesystems that grub-install
doesn't recognize
Bug 1030939 cloned as bug 1031415
> reassign -2 fai 6.0
Bug #1031415 [e2fsprogs] e2fsprogs: generates filesystems that grub-install
doesn't recognize
Bug reass
Control: tag -1 pending
Hello,
Bug #1031395 in tzdata 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/glibc-team/tzdata/-/commit/0a5dcdee0e45c5eb9276112925b3e5c
Processing control commands:
> tag -1 pending
Bug #1031395 [tzdata] tzdata 2022g-3 removes /etc/timezone while other packages
depend on it, breaking these packages
Added tag(s) pending.
--
1031395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031395
Debian Bug Tracking System
Contact ow..
Package: python3-zstandard
Followup-For: Bug #1031293
X-Debbugs-Cc: b...@debian.org, gregory.sz...@gmail.com
Hi Adrian, Gregory,
Reading the comment above the version check, it seems to indicate that Gregory
isn't particularly enthusiastic to provide support for environments where
there's a misma
Control: reassign -1 src:pocl,src:libgpuarray
Control: found -1 pocl/3.1-3
Control: found -1 libgpuarray/0.7.6-13
Control: retitle -1 libgpuarray: i386 test fail with new pocl
The trigger is probably pocl, not clinfo. I don't yet know whether the
bug is in pocl or libgpuarray.
Your message dated Thu, 16 Feb 2023 21:49:40 +
with message-id
and subject line Bug#1031395: fixed in tzdata 2022g-6
has caused the Debian Bug report #1031395,
regarding tzdata 2022g-3 removes /etc/timezone while other packages depend on
it, breaking these packages
to be marked as done.
This
Processing control commands:
> reassign -1 src:pocl,src:libgpuarray
Bug #1031414 [src:clinfo, src:libgpuarray] clinfo breaks libgpuarray
autopkgtest on i386: numerical deltas
Bug reassigned from package 'src:clinfo, src:libgpuarray' to
'src:pocl,src:libgpuarray'.
No longer marked as found in ver
Your message dated Thu, 16 Feb 2023 21:35:48 +
with message-id
and subject line Bug#1030767: fixed in imagemagick 8:6.9.11.60+dfsg-1.6
has caused the Debian Bug report #1030767,
regarding imagemagick: CVE-2022-44267 CVE-2022-44268
to be marked as done.
This means that you claim that the probl
On 2023-02-16 11:44:25 -0700, Sam Hartman wrote:
> > "Adrian" == Adrian Bunk writes:
>
> Adrian> On Thu, Feb 16, 2023 at 05:48:22PM +0100, Daniel Leidert wrote:
> >> Am Donnerstag, dem 16.02.2023 um 18:37 +0200 schrieb Adrian Bunk:
> >> > On Wed, Feb 15, 2023 at 12:05:41AM +0100,
On Thu, Feb 16, 2023 at 11:45:23AM -0800, Russ Allbery wrote:
>
> Yes, I'm probably understating the difficulty of making this change in
> practice inside image building software as it's currently constructed.
>
> My concern about changing mkfs options is that I worry that this would be
> a const
Control: forwarded -1 https://github.com/pocl/pocl/issues/1176
@elbrus: Why does britney try to migrate clinfo together with pocl?
IMO clinfo should be able to migrate on its own without causing new
regressions in testing. It does not have any (transitive) dependency on
pocl.
On Thu, 16 Feb 2
Processing control commands:
> forwarded -1 https://github.com/pocl/pocl/issues/1176
Bug #1031414 [src:pocl,src:libgpuarray] libgpuarray: i386 test fail with new
pocl
Set Bug forwarded-to-address to 'https://github.com/pocl/pocl/issues/1176'.
--
1031414: https://bugs.debian.org/cgi-bin/bugrepor
Hi,
Thanks for the patch!
This has been fixed in Debian testing and sid. However, stable is still
affected. I believe it would make sense to port the patch to stable and
allocate a CVE for this.
Regards,
Gabriel
"Theodore Ts'o" writes:
> As a long-term solution, one could image changing the various image
> creation tools to do something like "mfks.ext4 -T grub2_dumbdown
> /dev/XXX", and then have something like the following in
> /etc/mke2fs.conf:
> [fs_types]
> grub2_dumbdown = {
> features
Your message dated Thu, 16 Feb 2023 23:20:04 +
with message-id
and subject line Bug#1031271: fixed in glib2.0 2.75.3-2
has caused the Debian Bug report #1031271,
regarding glib2.0 [experimental]: 2.75.3 FTBFS on big-endian
to be marked as done.
This means that you claim that the problem has b
On Thu, Feb 16, 2023 at 05:24:04PM -0500, Theodore Ts'o wrote:
>...
> and that moving forward, we make it the image building tools
> problem if they want to support this highly dubious practice of using
> Debian N+X's mkfs to build images for Debian N.
>...
That's what they already have to do for
Processing commands for cont...@bugs.debian.org:
> severity 1030869 important
Bug #1030869 {Done: Markus Koschany } [tomcat10] tomcat10:
Catalina won't deploy applications missing class
jakarta.websocket.DeploymentException
Severity set to 'important' from 'grave'
> thanks
Stopping processing he
Source: debian-installer-netboot-images
Version: 20220917+rebuild1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part
Source: mediaelement
Version: 2.15.1+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> mak
Source: conda-package-handling
Version: 2.0.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully
Source: python-inotify
Version: 0.2.10-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/ru
Source: ubuntu-dev-tools
Version: 0.192
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> mak
Source: diffoscope
Version: 235
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Enter
Source: pandas
Version: 1.5.3+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully
Source: gcc-sh-elf
Version: 4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[6]: Enter
Source: open-vm-tools
Version: 2:12.1.5-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: ruby-github-api
Version: 0.19.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/
Source: gnustep-base
Version: 1.28.1+really1.28.0-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully
Source: qca2
Version: 2.3.5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Enter
Source: poetry
Version: 1.3.2+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/ru
Source: camv-rnd
Version: 1.1.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully
Source: lomiri-ui-toolkit
Version: 1.3.5000+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully
Source: python-zstandard
Version: 0.19.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> mak
Source: ffmpeg
Version: 7:5.1.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> gcc -I. -I
Source: fwupd
Version: 1.8.10-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/ld: /
Source: python-scrapy
Version: 2.8.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully
Source: gearmand
Version: 1.1.19.1+ds-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /bin/b
1 - 100 of 149 matches
Mail list logo
