Same here. But I have some different conclusions after fixing my
machine.
Before my machine becoming unable to boot, the last apt log involves
Start-Date: 2023-09-05 00:09:00
Commandline: apt upgrade
Requested-By: lumin (1000)
Upgrade: libimath-3-1-29:amd64 (3.1.9-2, 3.1.9-3),
Control: severity 891197 normal
u...@debian.org (Aaron M. Ucko) writes:
> For the time being, we can switch to an embedded copy of classic PCRE by
> dropping the build dependency on libpcre3-dev; that's of course not a
> proper fix, but should at least let us downgrade this bug's severity.
Done
Processing control commands:
> severity 891197 normal
Bug #891197 [ncbi-blast+] Please switch to pcre2
Severity set to 'normal' from 'serious'
--
891197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Tue, 05 Sep 2023 12:35:21 +
with message-id
and subject line Bug#1051156: fixed in seqan-raptor 3.0.1+ds-4
has caused the Debian Bug report #1051156,
regarding FTBFS with doxygen 1.9.8
to be marked as done.
This means that you claim that the problem has been dealt with.
If
On Tue, Sep 05, 2023 at 04:19:01PM +0200, Miguel A. Vallejo wrote:
> Package: grub2
> Version: 2.12~rc1-7
> Severity: critical
>
> This morning I noticed an apt upgrade in Debian unstable/Sid upgraded
> grub-common, grub2-common, grub-efi-amd64 and grub-efi-amd64-bin. The
> upgrade went normally
Control: retitle -1 asmjit: FTBFS on armel and armhf
Hi Andrius,
On 2023-08-28 07:42, Andrius Merkys wrote:
> On Wed, 16 Aug 2023 14:29:10 +0200 Emanuele Rocca wrote:
> > asmjit does not build correctly on the following architectures:
> > armel, armhf, mips64el, mipsel, s390x.
>
> Does this
Processing control commands:
> retitle -1 asmjit: FTBFS on armel and armhf
Bug #1049872 [src:asmjit] FTBFS on multiple release architectures
Changed Bug title to 'asmjit: FTBFS on armel and armhf' from 'FTBFS on multiple
release architectures'.
--
1049872:
Package: src:pytorch
Version: 2.0.1+dfsg-1
Severity: serious
Tags: sid trixie
pytorch2 ftbfs on ppc64el:
https://buildd.debian.org/status/fetch.php?pkg=pytorch=ppc64el=2.0.1%2Bdfsg-1=1693903013=0
[...]
FAILED:
El mar, 5 sept 2023 a las 17:21, Agustin Martin
() escribió:
>
> On Tue, Sep 05, 2023 at 04:19:01PM +0200, Miguel A. Vallejo wrote:
> > Package: grub2
> > Version: 2.12~rc1-7
> > Severity: critical
> >
> > This morning I noticed an apt upgrade in Debian unstable/Sid upgraded
> > grub-common,
M. Zhou wrote:
> But after that I noticed that the most important
> package grub-efi-amd64-signed:amd64 (1+2.06+13,
> 1+2.12~rc1+7) was not upgraded along with the other
> grub packages.
You are right. I revised apt log and grub-efi-amd64-signed was NOT
updated, in fact, the version I have
Processing control commands:
> block -1 by 1050989
Bug #890601 [firmware-linux-free] firmware-linux-free uses prebuilt blobs
instead of building from source
890601 was blocked by: 994625
890601 was not blocking any bugs.
Added blocking bug(s) of 890601: 1050989
--
890601:
Your message dated Tue, 05 Sep 2023 10:28:00 +
with message-id
and subject line Bug#1031747: fixed in python-socks 2.3.0-2
has caused the Debian Bug report #1031747,
regarding python-socks: autopkgtest regression
to be marked as done.
This means that you claim that the problem has been dealt
Package: grub2
Version: 2.12~rc1-7
Severity: critical
This morning I noticed an apt upgrade in Debian unstable/Sid upgraded
grub-common, grub2-common, grub-efi-amd64 and grub-efi-amd64-bin. The
upgrade went normally and no errors were shown. Then I turned the
computer off and after a few hours I
Your message dated Tue, 05 Sep 2023 19:52:02 +
with message-id
and subject line Bug#1042520: fixed in jabberd2 2.7.0-4.1
has caused the Debian Bug report #1042520,
regarding jabberd2: build dependency missing in testing: libgsasl7-dev
to be marked as done.
This means that you claim that the
Your message dated Tue, 05 Sep 2023 19:52:02 +
with message-id
and subject line Bug#1051175: fixed in jabberd2 2.7.0-4.1
has caused the Debian Bug report #1051175,
regarding jabberd2: build-depends on old libgsasl7-dev
to be marked as done.
This means that you claim that the problem has been
Control: tags 1037606 + patch
Hello. Patch attached which seems to solve the above FTBFS with gcc-13.
patch1.debdiff
Description: Binary data
Processing control commands:
> tags 1037606 + patch
Bug #1037606 [src:clog] clog: ftbfs with GCC-13
Added tag(s) patch.
--
1037606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1051271 in grub2 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:
Processing control commands:
> tag -1 pending
Bug #1051271 [grub2] GRUB2 2.12~rc1-7 prevent machine to boot
Added tag(s) pending.
--
1051271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Dear maintainer,
I've prepared an NMU for jabberd2 (versioned as 2.7.0-4.1) and
uploaded it.
Regards.
diff -Nru jabberd2-2.7.0/debian/changelog jabberd2-2.7.0/debian/changelog
--- jabberd2-2.7.0/debian/changelog 2022-06-06 14:08:22.0 +0200
+++ jabberd2-2.7.0/debian/changelog
Control: tag 1051258 +fixed-upstream +patch
Applying the change from the upstream commit:
https://github.com/pytorch/pytorch/commit/0c4fa0229625ccc6fcb9ae2867e98ce285e78946
fixes the FTBFS on ppc64el. This was verified using a schroot build on
the platti.debian.org porterbox.
Link to patch:
Processing control commands:
> tag 1051258 +fixed-upstream +patch
Bug #1051258 [src:pytorch] pytorch2 ftbfs on ppc64el
Added tag(s) fixed-upstream.
Bug #1051258 [src:pytorch] pytorch2 ftbfs on ppc64el
Added tag(s) patch.
--
1051258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051258
On Tue, Sep 05, 2023 at 08:32:39PM +0200, Agustin Martin wrote:
> On Tue, Sep 05, 2023 at 07:34:13PM +0200, Julian Andres Klode wrote:
> > On Tue, Sep 05, 2023 at 12:26:56PM -0400, M. Zhou wrote:
> > > I am able to boot with 2.12~rc1-7 now. And my currrent status is
> > >
> > >
Your message dated Tue, 5 Sep 2023 21:24:16 +0200
with message-id <16a03897-b7f2-4c42-a4e3-3899f9446...@thykier.net>
and subject line Re: debianutils: fails to reinstall / will fail to install 5.11
has caused the Debian Bug report #1050784,
regarding debianutils: fails to reinstall
to be marked as
Source: scap-security-guide
Version: 0.1.65-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertag: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting issues with your packages. Normally your build
dependencies shouldn't be removed from testing without removal
Hello
Just for your information.
I managed to get all grub packages
grub2-common
grub-common
grub-efi-amd64
grub-efi-amd64-bin
grub-efi-amd64-signed
updated to 2.12~rc1-7 and the system DOES NOT BOOT.
I downgraded all those grub packages to 2.06-3~deb11u5 (the one found
in stable) and it
Processing commands for cont...@bugs.debian.org:
> fixed 965612 kmfl-keyboards-mywin/2.3.3-2
Bug #965612 {Done: Adrian Bunk } [src:kmfl-keyboards-mywin]
kmfl-keyboards-mywin: Removal of obsolete debhelper compat 5 and 6 in bookworm
Marked as fixed in versions kmfl-keyboards-mywin/2.3.3-2.
>
End
Source: rocfft
Version: 5.5.0-4
Severity: grave
Justification: Can crash the host
autopkgtests for rocfft triggered a soft lockup when run with an 6500 XT
(gfx1034, Navi24).
This is very probably a kernel issue, but I'm filing this bug here until
we have actually identified the root cause, after
Your message dated Tue, 05 Sep 2023 21:13:22 +
with message-id
and subject line Bug#1051006: fixed in smuxi 1.1-1.3
has caused the Debian Bug report #1051006,
regarding smuxi: useless empty package
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Processing commands for cont...@bugs.debian.org:
> affects 1050676 enblend-enfuse
Bug #1050676 [graphviz] enblend-enfuse: FTBFS: dot: maze.c:311: chkSgraph:
Assertion `np->cells[0]' failed.
Added indication that 1050676 affects enblend-enfuse
> thanks
Stopping processing here.
Please contact me
Processing control commands:
> clone -1 -2
Bug #1042041 {Done: Claudius Heine } [python3-tpm2-pytss]
tpm2-pkcs11: FTBFS: gcc: error: unrecognized command-line option '-V'
Bug 1042041 cloned as bug 1051284
> reassign -2 src:tpm2-tss 4.0.1-1
Bug #1051284 {Done: Claudius Heine }
Control: clone -1 -2
Control: reassign -2 src:tpm2-tss 4.0.1-1
Control: retitle -2 ABI breakage without SONAME bump
Hi,
On 05/09/2023 20.40, Bastian Germann wrote:
This regularly suggests that a package broke their ABI without a
SONAME bump.
Yes. It is tpm2-tss version 4.0.1-1 that broke its
Processing commands for cont...@bugs.debian.org:
> reopen 1051284
Bug #1051284 {Done: Claudius Heine } [src:tpm2-tss] ABI breakage
without SONAME bump
Bug reopened
Ignoring request to alter fixed versions of bug #1051284 to the same values
previously set
> thanks
Stopping processing here.
On Tue, Sep 05, 2023 at 08:32:39PM +0200, Agustin Martin wrote:
> On Tue, Sep 05, 2023 at 07:34:13PM +0200, Julian Andres Klode wrote:
> > On Tue, Sep 05, 2023 at 12:26:56PM -0400, M. Zhou wrote:
> > > I am able to boot with 2.12~rc1-7 now. And my currrent status is
> > >
> > >
Processing control commands:
> close -1 1.1.5-1
Bug #1051286 [src:avfs] src:avfs: fails to migrate to testing for too long:
FTBFS on armel
Marked as fixed in versions avfs/1.1.5-1.
Bug #1051286 [src:avfs] src:avfs: fails to migrate to testing for too long:
FTBFS on armel
Marked Bug as done
--
Source: avfs
Version: 1.1.4-2
Severity: serious
Control: close -1 1.1.5-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as
Source: farpd
Version: 0.2-11.3
Severity: serious
farpd FTBFS on i386. This is a consequence of fixing #999882
without adjusting the $host part in the configure patch.
Source: fwupd
Version: 1.9.4-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=fwupd=armel=1.9.4-2%2Bb1=1693947882=0
---
env[PKG_CONFIG_PATH]:
Package: zabbix-proxy-sqlite3
Version: 1:4.0.4+dfsg-1+deb10u2
Tags: buster
Severity: grave
Justification: renders package unusable
Hello,
The 1:4.0.4+dfsg-1+deb10u2 version of the SQLite variant of the Zabbix
proxy comes with a regression making it fail to start. Upon starting,
the following
Your message dated Tue, 05 Sep 2023 22:20:28 +
with message-id
and subject line Bug#1051158: fixed in aseba 1.6.99+dfsg-8
has caused the Debian Bug report #1051158,
regarding aseba: FTBFS: error: ‘uint16_t’ does not name a type
to be marked as done.
This means that you claim that the problem
Control: tag -1 unreproducible
On Tue, Sep 05, 2023 at 04:19:01PM +0200, Miguel A. Vallejo wrote:
> Package: grub2
> Version: 2.12~rc1-7
> Severity: critical
>
> This morning I noticed an apt upgrade in Debian unstable/Sid upgraded
> grub-common, grub2-common, grub-efi-amd64 and
Processing control commands:
> tag -1 unreproducible
Bug #1051271 [grub2] GRUB2 2.12~rc1-7 prevent machine to boot
Added tag(s) unreproducible.
--
1051271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> reassign -1 graphviz 2.42.2-7
Bug #1050676 [src:enblend-enfuse] enblend-enfuse: FTBFS: dot: maze.c:311:
chkSgraph: Assertion `np->cells[0]' failed.
Bug reassigned from package 'src:enblend-enfuse' to 'graphviz'.
No longer marked as found in versions
Control: reassign -1 graphviz 2.42.2-7
On 2023-08-27 Aurelien Jarno wrote:
> Source: enblend-enfuse
> Version: 4.2-10
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> Dear maintainer,
> enblend-enfuse fails to build from
On Tue, Sep 05, 2023 at 12:26:56PM -0400, M. Zhou wrote:
> On Tue, 5 Sep 2023 18:11:55 +0200 "Miguel A. Vallejo"
> wrote:
> > M. Zhou wrote:
> >
> > > But after that I noticed that the most important
> > > package grub-efi-amd64-signed:amd64 (1+2.06+13,
> > > 1+2.12~rc1+7) was not upgraded along
Hi Bastian,
On Thu, 27 Jul 2023 00:01:52 +0200 Bastian Germann wrote:
ImportError: /usr/lib/python3/dist-packages/tpm2_pytss/_libtpm2_pytss.abi3.so: undefined symbol:
Tss2_MU_TPMS_ALGORITHM_DESCRIPTION_Marshal
This regularly suggests that a package broke their ABI without a SONAME
bump.
> On Tue, Sep 05, 2023 at 07:34:13PM +0200, Julian Andres Klode wrote:
> I wrote
> > If /boot/efi is not mounted I get for new versions
>
> Well that's *your problem*, sorry. Mounting /boot/efi is mandatory,
> you can't just go unmount it. By the same argument unmounting /boot
> (if a separate
Your message dated Tue, 05 Sep 2023 21:43:15 +
with message-id
and subject line Bug#1051177: fixed in pokerth 1.1.2-3
has caused the Debian Bug report #1051177,
regarding pokerth: build-depends on old libgsasl7-dev
to be marked as done.
This means that you claim that the problem has been
Just after sending my previous message I noticed the following
versions were available after an apt upgrade:
grub2-common 2.12~rc1-9
grub-common 2.12~rc1-9
grub-efi-amd64 2.12~rc1-9
grub-efi-amd64-bin 2.12~rc1-9
grub-efi-amd64-signed 2.12~rc1-7
so I bit the bullet and made an upgrade.
It works.
Your message dated Tue, 05 Sep 2023 17:19:50 +
with message-id
and subject line Bug#1051271: fixed in grub2 2.12~rc1-8
has caused the Debian Bug report #1051271,
regarding GRUB2 2.12~rc1-7 prevent machine to boot
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> # 1.76.2-4 isn't an descendant of 1.74.3-1 so the bts doesn't know it's
> fixed 1041306 1.76.2-4
Bug #1041306 {Done: Paul Gevers } [src:gjs] src:gjs: fails
to migrate to testing for too long: autopkgtest regression
Marked as fixed in versions
Am 05.09.23 um 20:17 schrieb Paul Gevers:
Hi Bastian,
On Thu, 27 Jul 2023 00:01:52 +0200 Bastian Germann wrote:
ImportError: /usr/lib/python3/dist-packages/tpm2_pytss/_libtpm2_pytss.abi3.so: undefined symbol:
Tss2_MU_TPMS_ALGORITHM_DESCRIPTION_Marshal
This regularly suggests that a package
Your message dated Tue, 05 Sep 2023 20:40:18 +
with message-id
and subject line Bug#1051291: fixed in farpd 0.2-11.3
has caused the Debian Bug report #1051291,
regarding farpd: FTBFS on i386, uses GNU host to find libevent.a
to be marked as done.
This means that you claim that the problem
I have caused this, so I am uploading a NMU to fix this.
The debdiff is attached.diff -Nru smuxi-1.1/debian/changelog smuxi-1.1/debian/changelog
--- smuxi-1.1/debian/changelog 2023-08-04 21:42:26.0 +0200
+++ smuxi-1.1/debian/changelog 2023-09-05 22:27:06.0 +0200
@@ -1,3 +1,11 @@
On Tue, 5 Sep 2023 18:11:55 +0200 "Miguel A. Vallejo"
wrote:
> M. Zhou wrote:
>
> > But after that I noticed that the most important
> > package grub-efi-amd64-signed:amd64 (1+2.06+13,
> > 1+2.12~rc1+7) was not upgraded along with the other
> > grub packages.
>
> You are right. I revised apt
Your message dated Tue, 05 Sep 2023 17:50:26 +
with message-id
and subject line Bug#1051271: fixed in grub2 2.12~rc1-9
has caused the Debian Bug report #1051271,
regarding GRUB2 2.12~rc1-7 prevent machine to boot
to be marked as done.
This means that you claim that the problem has been dealt
On Tue, Sep 05, 2023 at 07:34:13PM +0200, Julian Andres Klode wrote:
> On Tue, Sep 05, 2023 at 12:26:56PM -0400, M. Zhou wrote:
> > I am able to boot with 2.12~rc1-7 now. And my currrent status is
> >
> > grub-common/unstable,now 2.12~rc1-7 amd64 [installed]
> > grub-efi-amd64-bin/unstable,now
I am uploading a NMU to fix this. The debdiff is attached.diff -Nru farpd-0.2/debian/changelog farpd-0.2/debian/changelog
--- farpd-0.2/debian/changelog 2023-08-18 00:18:37.0 +0200
+++ farpd-0.2/debian/changelog 2023-09-05 22:05:19.0 +0200
@@ -1,3 +1,10 @@
+farpd (0.2-11.3)
Your message dated Tue, 05 Sep 2023 21:39:22 +
with message-id
and subject line Bug#1051176: fixed in jreen 1.2.0+ds-2
has caused the Debian Bug report #1051176,
regarding jreen: build-depends on old libgsasl7-dev
to be marked as done.
This means that you claim that the problem has been
Processing control commands:
> affects -1 + pike8.0-pcre
Bug #1051287 [pike8.0-core] pike8.0-core: undeclared file conflict with former
pike8.0-pcre
Added indication that 1051287 affects pike8.0-pcre
--
1051287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051287
Debian Bug Tracking
Package: pike8.0-core
Version: 8.0.1738-1.1
Severity: serious
Control: affects -1 + pike8.0-pcre
User: debian...@lists.debian.org
Usertags: fileconflict
pike8.0-core now installs /usr/lib/pike8.0/modules/_Regexp_PCRE.pmo and
/usr/lib/pike8.0/modules/Regexp_PCRE.so. These files happen to also
On Sun, 3 Sep 2023, Paolo Greppi wrote:
Package: wxpython-tools
Version: 4.2.1+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the
past)
X-Debbugs-Cc: paolo.gre...@libpf.com
While preparing to upload doxygen 1.9.8, I did a partial
Em sábado, 2 de setembro de 2023, às 03:45:24 -03, Christian Marillat
escreveu:
>
> I noticed that you have filed a bug 1050591 to backport cahnges added in
> 7.8-4 to bulleye. May be you can do the same for bookworm ?
>
Yes of course.
My idea is to fix the bullseye [1] and bookworm [2], as
This appears to be a bug in libxmlb-dev, it's missing a dependency
on libzstd-dev.
Processing control commands:
> tags 1037692 + patch
Bug #1037692 [src:horizon-eda] horizon-eda: ftbfs with GCC-13
Added tag(s) patch.
--
1037692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037692
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags 1037692 + patch
Hi, patch attached for the above bug.
patch.debdiff
Description: Binary data
Source: xandikos
Version: 0.2.8-1
Severity: serious
Hello, for some reasons, new dulwich regressed xandikos autopkgtests:
https://ci.debian.net/data/autopkgtest/testing/amd64/x/xandikos/37481831/log.gz
67s autopkgtest [19:11:41]: test litmus: [---
67s ++ dirname
Source: sarsen
Version: 0.9.3+ds-2
Severity: serious
Hello, looks like something (new python-xarray?) broke autopkgtests for this
package:
https://ci.debian.net/data/autopkgtest/unstable/amd64/s/sarsen/37316930/log.gz
63s autopkgtest [23:46:19]: test python3: [---
63s
On 05 sept. 2023 17:11, Lourisvaldo Figueredo Junior
wrote:
[...]
>> I noticed that you have filed a bug 1050591 to backport cahnges added in
>> 7.8-4 to bulleye. May be you can do the same for bookworm ?
>>
>
> Yes of course.
> My idea is to fix the bullseye [1] and bookworm [2], as you
Your message dated Tue, 05 Sep 2023 09:50:00 +
with message-id
and subject line Bug#1051097: fixed in cyrus-imapd 3.8.0-5
has caused the Debian Bug report #1051097,
regarding cyrus-imapd: autopkgtest failure because package is not installable
to be marked as done.
This means that you claim
Package: milkytracker
Version: 1.04.00+dfsg-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
spawning milkytracker.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Entered the command :
Your message dated Tue, 05 Sep 2023 07:37:12 +
with message-id
and subject line Bug#1051246: fixed in php8.2 8.2.10-2
has caused the Debian Bug report #1051246,
regarding php8.2: ftbfs on some architectures: Cannot find sys/sdt.h which is
required for DTrace support
to be marked as done.
Your message dated Tue, 5 Sep 2023 08:45:16 +0200
with message-id <68b2ba4b-6e8e-e8e6-9c23-d43bcea9b...@web.de>
and subject line Re: Bug#1051144: reportbug: tex-common fails to install due to
fmtutil error
has caused the Debian Bug report #1051144,
regarding reportbug: tex-common fails to install
Your message dated Tue, 5 Sep 2023 08:45:16 +0200
with message-id <68b2ba4b-6e8e-e8e6-9c23-d43bcea9b...@web.de>
and subject line Re: Bug#1051144: reportbug: tex-common fails to install due to
fmtutil error
has caused the Debian Bug report #1051144,
regarding texlive-binaries: Failed tex-common
Control: tag -1 pending
Hello,
Bug #1031747 in python-socks 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:
Processing control commands:
> tag -1 pending
Bug #1031747 [src:python-socks] python-socks: autopkgtest regression
Added tag(s) pending.
--
1031747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
76 matches
Mail list logo
