Processing commands for cont...@bugs.debian.org:
> tags 1061764 + fixed-upstream
Bug #1061764 [src:unattended-upgrades] unattended-upgrades ftbfs with Python
3.12 as default
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1061764:
Package: shim
Followup-For: Bug #1061519
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
shim 15.8 @vathpela vathpela released this 23 Jan 19:01
What's New
* Various CVE fixes:
CVE-2023-40546 mok: fix LogError() invocation
CVE-2023-40547 - avoid incorrectly trusting HTTP headers
Processing commands for cont...@bugs.debian.org:
> reassign 1063668 nvidia-kernel-dkms
Bug #1063668 [src:nvidia-graphics-drivers] linux-image-6.1.0-18-amd64: Nvidia
525.147.05-4 issues
Bug reassigned from package 'src:nvidia-graphics-drivers' to
'nvidia-kernel-dkms'.
Ignoring request to alter
Processing commands for cont...@bugs.debian.org:
> reassign 1063668 src:nvidia-graphics-drivers
Bug #1063668 [linux-image-6.1.0-18-amd64] linux-image-6.1.0-18-amd64: Nvidia
525.147.05-4 issues
Bug reassigned from package 'linux-image-6.1.0-18-amd64' to
'src:nvidia-graphics-drivers'.
No longer
It's been a couple of weeks and no action upstream. I'll plan on uploading
this unless you'd rather I hold off for some reason.
Scott K
On Wed, 24 Jan 2024 16:56:30 -0500 Scott Kitterman
wrote:
> On Tue, 16 Jan 2024 20:41:58 +0100 Lucas Nussbaum wrote:
> > Source: pycountry
> > Version:
Processing commands for cont...@bugs.debian.org:
> owner 1018658 Nick Morrott
Bug #1018658 [src:valinor] valinor: build-depends on python3-nose or uses it
for autopkgtest
Owner recorded as Nick Morrott .
> owner 1018673 Nick Morrott
Bug #1018673 [src:yotta] yotta: build-depends on python3-nose
Your message dated Sun, 11 Feb 2024 01:20:46 +
with message-id
and subject line Bug#1063363: fixed in nvidia-graphics-drivers 535.54.03-1
has caused the Debian Bug report #1063363,
regarding nvidia-graphics-drivers: autopkgtest needs update for new version of
linux
to be marked as done.
Yes. I can see that there are API methods which expose nlohmann::json
(eg,
https://github.com/jupyter-xeus/xeus/blob/ebd21e9e7cfe143b4d0a6783112cc9006b456915/include/xeus/xdebugger.hpp#L55-L60)
so changes the header library are going to cause ABI breakage.
I don't see much choice here but to
Is there a way to help fixing that?
I get that the responsible DD(s) are ovewhelmed and unable to pay
attention to even a grave category bug. Could we somehow lend a hand?
Grigor
Your message dated Sat, 10 Feb 2024 22:05:56 +
with message-id
and subject line Bug#1063607: fixed in igraph 0.10.9+ds-2
has caused the Debian Bug report #1063607,
regarding igraph: FTBFS on i386: test::igraph_hrg (Failed)
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> affects -1 + src:nvidia-graphics-drivers
Bug #1063675 [release.debian.org] bookworm-pu: package
nvidia-graphics-drivers/525.147.05-6~deb12u1
Added indication that 1063675 affects src:nvidia-graphics-drivers
> block 1063363 with -1
Bug #1063363 {Done: Andreas
Your message dated Sat, 10 Feb 2024 21:26:38 +
with message-id
and subject line Bug#1061751: fixed in python-django-debug-toolbar 1:4.3-1
has caused the Debian Bug report #1061751,
regarding python-django-debug-toolbar ftbfs with Python 3.12 as default
to be marked as done.
This means that
Package: wine
Version: 9.0~repack-3
Severity: serious
Forwarded: https://gitlab.winehq.org/wine/wine/-/merge_requests/4928
The current build fail on 32 bit arm architectures with the following
error:
/usr/bin/ld: dlls/ntdll/unix/signal_arm.o: in function
`libunwind_virtual_unwind':
Dear maintainers,
Debian 12.5 stable updated here from the main repo, impossible to
compile nvidia module with dkms on 6.1.0-18.
Same error as everyone else:
ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'__rcu_read_lock'
ERROR: modpost: GPL-incompatible module
Source: adwaita-icon-theme
Version: 46~beta-1
Severity: serious
Tags: pending trixie
I am filing this bug as a duplicate of https://bugs.debian.org/1063640
to prevent adwaita-icon-theme 46~beta-1 from migrating to Testing
until mutter 44.8-3 migrates first.
Thank you,
Jeremy Bícha
Source: gcc-13-cross
Version: 14
Severity: serious
Hi,
there are undeclared file conflicts between gnat-13- and
gnat-{9,10}- in sid. (but not between -9- and -10-).
Maybe it would be sufficient to rebuild the package against gcc-13
13.2.0-13 which had some gnat conflict fixes.
The conflicting
Processing commands for cont...@bugs.debian.org:
> retitle 1061034 lcl-utils-3.0 Missing dependencies for lazbuild
Bug #1061034 [lcl-utils-3.0] c-evo-dh: FTBFS: make[1]: *** [debian/rules:39:
override_dh_auto_build] Error 2
Changed Bug title to 'lcl-utils-3.0 Missing dependencies for lazbuild'
Processing commands for cont...@bugs.debian.org:
> severity 1062582 serious
Bug #1062582 [src:mkdocs-material] mkdocs-material: Files installed under wrong
dir (/usr/lib/python3.11), breaking reverse-deps
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please
Your message dated Sat, 10 Feb 2024 18:23:54 +
with message-id
and subject line Bug#1063640: fixed in mutter 44.8-3
has caused the Debian Bug report #1063640,
regarding adwaita-icon-theme: cursor theme not found
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 10 Feb 2024 18:24:12 +
with message-id
and subject line Bug#1058440: fixed in python-aiosmtpd 1.4.4.post2-1
has caused the Debian Bug report #1058440,
regarding python-aiosmtpd: FTBFS: E: Build killed with signal TERM after 150
minutes of inactivity
to be marked as
Your message dated Sat, 10 Feb 2024 18:24:12 +
with message-id
and subject line Bug#1056454: fixed in python-aiosmtpd 1.4.4.post2-1
has caused the Debian Bug report #1056454,
regarding python-smtpd's autopkg tests fail with Python 3.12
to be marked as done.
This means that you claim that the
Your message dated Sat, 10 Feb 2024 18:22:36 +
with message-id
and subject line Bug#1042992: fixed in micropython 1.22.1+ds-1
has caused the Debian Bug report #1042992,
regarding micropython FTBFS with gcc 13
to be marked as done.
This means that you claim that the problem has been dealt
Processing control commands:
> merge -1 1025545
Bug #1063662 [bleachbit] bleachbit: Depends on transitional policykit-1
Unable to merge bugs because:
severity of #1025545 is 'serious' not 'important'
blocks of #1025545 is '1025540' not ''
done of #1025545 is 'Fabio Fantoni ' not ''
Failed to
[Lucas Nussbaum]
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
Thank you for letting us know. I have tried to figure out what is going wrong,
without success so far. I can reproduce it in my sid chroot.
I tried replacing build dependencies libmlir-14-dev
Your message dated Sat, 10 Feb 2024 17:18:07 +
with message-id
and subject line Bug#1063416: fixed in libgit2 1.1.0+dfsg.1-4+deb11u2
has caused the Debian Bug report #1063416,
regarding libgit2: CVE-2024-24577: Arbitrary code execution due to heap
corruption in `git_index_add`
to be marked
Your message dated Sat, 10 Feb 2024 17:17:18 +
with message-id
and subject line Bug#1063416: fixed in libgit2 1.5.1+ds-1+deb12u1
has caused the Debian Bug report #1063416,
regarding libgit2: CVE-2024-24577: Arbitrary code execution due to heap
corruption in `git_index_add`
to be marked as
Processing commands for cont...@bugs.debian.org:
> reassign 1061034 lcl-utils-3.0
Bug #1061034 [src:c-evo-dh] c-evo-dh: FTBFS: make[1]: *** [debian/rules:39:
override_dh_auto_build] Error 2
Bug reassigned from package 'src:c-evo-dh' to 'lcl-utils-3.0'.
No longer marked as found in versions
While Lazarus release (3.0+dfsg1-6) fixed the immediate problem
of ideconfig.lpk missing, lazbuilds still all fail, now with
"Note: (lazarus) Invalid Package Link: file
"/usr/lib/lazarus/3.0/ide/packages/idedebugger/idedebugger.lpk" does not
exist."
Builds fail on the firts missing (lazarus)
Control: fixed -1 0.7.0-1
On Wed, 7 Feb 2024 14:03:34 +0530 Praveen Arimbrathodiyil
wrote:
Control: severity -1 serious
On Sun, 18 Jun 2023 13:14:21 +0530 Pirate Praveen
wrote:
>
> Since ruby-faraday-middleware is deprecated, we should update to
> graphlient 0.7
ruby-faraday 2 is in
Your message dated Sat, 10 Feb 2024 21:33:44 +0530
with message-id
and subject line Re: ruby-graphlient fails to rebuild after updating
ruby-faraday to upstream
has caused the Debian Bug report #1025084,
regarding ruby-graphlient fails to rebuild after updating ruby-faraday to
upstream
to be
Processing control commands:
> fixed -1 0.7.0-1
Bug #1025084 [ruby-graphlient] ruby-graphlient fails to rebuild after updating
ruby-faraday to upstream
There is no source info for the package 'ruby-graphlient' at version '0.7.0-1'
with architecture ''
Unable to make a source version for version
Processing commands for cont...@bugs.debian.org:
> unarchive 1031888
Bug #1031888 {Done: Sean Whitton } [src:emacs]
emacs-nox: bullseye-security update fails to install on mips64el
Unarchived Bug 1031888
> tags 1031888 + bullseye
Bug #1031888 {Done: Sean Whitton } [src:emacs]
emacs-nox:
Processing control commands:
> affects -1 + src:ruby-graphql-errors
Bug #1063655 [ftp.debian.org] RM: ruby-graphql-errors -- ROM; unmaintained
upstream, incompatible with ruby-graphql 2.x
Added indication that 1063655 affects src:ruby-graphql-errors
> block 1063654 by -1
Bug #1063654
Package: ruby-graphql-errors
Version: 0.4.0-2
Severity: serious
source package has 1 unsatisfiable build dependency
Build dependencies in unstable cannot be satisfied on amd64
because: unsatisfied dependency on ruby-graphql (< 2)
Last commint was 4 years ago and
Your message dated Sat, 10 Feb 2024 15:19:59 +
with message-id
and subject line Bug#1063609: fixed in texstudio 4.7.2+ds-2
has caused the Debian Bug report #1063609,
regarding texstudio_4.7.2+ds-1_all-buildd.changes REJECTED
to be marked as done.
This means that you claim that the problem
Processing control commands:
> tag 1063361 + bookworm
Bug #1063361 {Done: Andreas Beckmann }
[src:nvidia-graphics-drivers-tesla-470] nvidia-graphics-drivers-tesla-470:
autopkgtest needs update for new version of linux
Added tag(s) bookworm.
--
1063361:
Control: tag 1063361 + bookworm
On Sat, Feb 10, 2024 at 03:49:45PM +0100, wrote:
> Control: found 1063361 470.223.02-2~deb12u1
> [...]
> Thus now marking this bug accordingly.
Not quite, but hopefully now.
FWIW, manually adding 0035-fix-build-w-kernel-6.1.76-6.6.15-6.7.3.patch[0]
fixes the
Processing commands for cont...@bugs.debian.org:
> tags 1010120 + experimental
Bug #1010120 [src:thrift] thrift: FTBFS in bullseye (expired certificates in
test suite)
Added tag(s) experimental.
> tags 985725 + trixie experimental
Bug #985725 {Done: Gennaro Oliva } [src:slurm-wlm]
slurm-wlm:
Processing commands for cont...@bugs.debian.org:
> severity 1062932 grave
Bug #1062932 [nvidia-kernel-dkms] nvidia-kernel-dkms: dkms module won't build
against linux-image-6.1.0-18-amd64 (6.1.76-1)
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if
Your message dated Sat, 10 Feb 2024 15:07:12 +
with message-id
and subject line Bug#1063632: fixed in spirv-llvm-translator-17 17.0.0-4
has caused the Debian Bug report #1063632,
regarding spirv-llvm-translator-17 FTBFS: error:
‘CapabilityLongConstantCompositeINTEL’ was not declared in this
Control: found 1063361 470.223.02-2~deb12u1
On Tue, Feb 06, 2024 at 09:18:15PM +0100, Paul Gevers wrote:
> Source: nvidia-graphics-drivers-tesla-470
> Version: 470.223.02-3
> Severity: serious
> X-Debbugs-CC: li...@packages.debian.org
> Tags: sid trixie
> User: debian...@lists.debian.org
>
Processing control commands:
> found 1063361 470.223.02-2~deb12u1
Bug #1063361 {Done: Andreas Beckmann }
[src:nvidia-graphics-drivers-tesla-470] nvidia-graphics-drivers-tesla-470:
autopkgtest needs update for new version of linux
Marked as found in versions
Hi,
I looked at the build log, and the problems look to be disk related?
/usr/bin/ld: final link failed: No space left on device
collect2: error: ld returned 1 exit status
(there follow further ENOSPC and also some No such file or directory
errors, which presumably relate to things not
Processing commands for cont...@bugs.debian.org:
> severity 1062484 important
Bug #1062484 [src:libnma] libnma: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1062484:
Processing commands for cont...@bugs.debian.org:
> reassign 1052763 src:gnuastro 0.20-1
Bug #1052763 {Done: Phil Wyett } [libgnuastro18]
libgnuastro18 has an undeclared file conflict on
/usr/lib/x86_64-linux-gnu/libgnuastro_make.so
Warning: Unknown package 'libgnuastro18'
Bug reassigned from
Processing commands for cont...@bugs.debian.org:
> affects 1063640 src:adwaita-icon-theme
Bug #1063640 [src:mutter] adwaita-icon-theme: cursor theme not found
Added indication that 1063640 affects src:adwaita-icon-theme
>
End of message, stopping processing here.
Please contact me if you need
Your message dated Sat, 10 Feb 2024 13:11:21 +
with message-id
and subject line Bug#1063603: fixed in composer 2.7.1-1
has caused the Debian Bug report #1063603,
regarding composer: CVE-2024-24821
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 10 Feb 2024 13:10:16 +
with message-id
and subject line Bug#1063434: fixed in 389-ds-base 2.4.4+dfsg1-3
has caused the Debian Bug report #1063434,
regarding src:389-ds-base: fails to migrate to testing for too long: FTBFS on
32 bits
to be marked as done.
This means
Your message dated Sat, 10 Feb 2024 13:11:32 +
with message-id
and subject line Bug#1042590: fixed in django-session-security 2.6.7+dfsg-1
has caused the Debian Bug report #1042590,
regarding django-session-security: FTBFS with Sphinx 7.1, docutils 0.20: error:
invalid command 'build_sphinx'
Control: reassign -1 src:mutter 44.8-2
I found some mutter commits to fix this issue and am uploading now.
Thank you,
Jeremy Bícha
Processing control commands:
> tag -1 pending
Bug #1063640 [src:mutter] adwaita-icon-theme: cursor theme not found
Ignoring request to alter tags of bug #1063640 to the same tags previously set
--
1063640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063640
Debian Bug Tracking System
Control: tag -1 pending
Hello,
Bug #1063640 in mutter 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 #1063640 [src:mutter] adwaita-icon-theme: cursor theme not found
Added tag(s) pending.
--
1063640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1063640 in mutter 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:
> reassign -1 src:mutter 44.8-2
Bug #1063640 [adwaita-icon-theme] adwaita-icon-theme: cursor theme not found
Bug reassigned from package 'adwaita-icon-theme' to 'src:mutter'.
No longer marked as found in versions adwaita-icon-theme/46~beta-1.
Ignoring request to alter
Control: tags -1 patch
On 2024-02-07 Andreas Beckmann wrote:
> Package: atm-tools
> Version: 1:2.5.1-5.1~exp1
[...]
> atm-tools/experimental has gained two unexpected files, causing file
> conflicts on upgrades:
[...]
> There is still an libatm1 dependency, and the new libatm1t64 dependency
>
Processing control commands:
> tags -1 patch
Bug #1063401 [atm-tools] atm-tools: has gained
/usr/share/doc/libatm1/changelog.*
Added tag(s) patch.
--
1063401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063401
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: affects -1 src:mutter src:gnome-shell
On Sat, Feb 10, 2024 at 5:51 AM Frederic Peters wrote:
> After upgrading to 46~beta-1 gnome-shell doesn't find a cursor theme
> anymore, I get this line in the journalctl output:
>
> feb 10 11:02:08 stab gnome-shell[999044]: No cursor theme
Processing control commands:
> affects -1 src:mutter src:gnome-shell
Bug #1063640 [adwaita-icon-theme] adwaita-icon-theme: cursor theme not found
Added indication that 1063640 affects src:mutter and src:gnome-shell
--
1063640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063640
Debian Bug
Source: krb5
Version: 1.20.1-5+b1
Severity: serious
Tags: ftbfs
Hi,
there as a binNMU "Rebuild to sync binNMU versions" for krb5 and that
failed for arm64, armel and ppc64el:
https://buildd.debian.org/status/package.php?p=krb5
The error logs look very similar:
making check in lib/rpc...
Source: tix
Version: 8.4.3-11
Severity: serious
Justification: Debian Policy section 4.9
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep
Dear maintainer,
Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by
Source: sysconfig
Version: 0.0.14
Severity: serious
Justification: Debian Policy section 4.9
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep
Dear maintainer,
Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required
Source: atitvout
Version: 0.4-13.2
Severity: serious
Justification: Debian Policy section 4.9
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep
Dear maintainer,
Your package does not include build-arch and/or build-indep targets in
debian/rules. This is
Source: markdown
Version: 1.0.1-12
Severity: serious
Justification: Debian Policy section 4.9
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep
Dear maintainer,
Your package does not include build-arch and/or build-indep targets in
debian/rules. This is
Processing commands for cont...@bugs.debian.org:
> severity 1063640 serious
Bug #1063640 [adwaita-icon-theme] adwaita-icon-theme: cursor theme not found
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1063640:
Processing commands for cont...@bugs.debian.org:
> severity 1061888 important
Bug #1061888 [src:anfo] anfo: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1061920 important
Bug #1061920 [src:arrayfire] arrayfire: NMU diff for 64-bit time_t transition
Processing commands for cont...@bugs.debian.org:
> forwarded 1063607 https://github.com/igraph/igraph/issues/2482
Bug #1063607 [src:igraph] igraph: FTBFS on i386: test::igraph_hrg (Failed)
Set Bug forwarded-to-address to 'https://github.com/igraph/igraph/issues/2482'.
> thanks
Stopping processing
As I've come to understand it... since fwupd is in main and it
recommends a package not in main, then it violates policy 2.2.1
Since this directive is a 'must' I've changed the severity to 'serious'
as per the meanings of those severity levels.
Processing commands for cont...@bugs.debian.org:
> severity 988817 serious
Bug #988817 [fwupd] fwupd: Recommends on nonexistent package secureboot-db
Severity set to 'serious' from 'minor'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
988817:
Processing commands for cont...@bugs.debian.org:
> limit source composer
Limiting to bugs with field 'source' containing at least one of 'composer'
Limit currently set to 'source':'composer'
> tags 1063603 + pending
Bug #1063603 [src:composer] composer: CVE-2024-24821
Added tag(s) pending.
>
Processing commands for cont...@bugs.debian.org:
> severity 1062485 important
Bug #1062485 [src:libnova] libnova: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062742 important
Bug #1062742 [src:libzia] libzia: NMU diff for 64-bit time_t transition
Processing commands for cont...@bugs.debian.org:
> severity 1062572 normal
Bug #1062572 [src:libpqtypes] libpqtypes: NMU diff for 64-bit time_t transition
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1062572:
Processing commands for cont...@bugs.debian.org:
> severity 1062388 normal
Bug #1062388 [src:dsdcc] dsdcc: NMU diff for 64-bit time_t transition
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1062388:
[Petter Reinholdtsen]
> I do not use ssr much myself, and have not had time to test.
I applied the upstream commit in git branch fix-1040375-glinject and
tested it on Bookworm, but alas, the .so file still segfaults with a
useless backtrace. I might have applied the commit incorrectly, as it
did
Processing commands for cont...@bugs.debian.org:
> found 1062033 2.12.0+ds-2
Bug #1062033 [src:c-blosc2] c-blosc2: NMU diff for 64-bit time_t transition
Marked as found in versions c-blosc2/2.12.0+ds-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1062033:
Source: virglrenderer
Version: 1.0.0-1
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=virglrenderer=mips64el=1.0.0-1%2Bb1=1707553944=0
Processing control commands:
> block 1061605 by -1
Bug #1061605 [src:scipy] scipy: tests skipped during build and autopkgtest not
in sync
1061605 was blocked by: 1063527 1063526 1063584
1061605 was not blocking any bugs.
Added blocking bug(s) of 1061605: 1063636
--
1061605:
Control: tag -1 pending
Hello,
Bug #1040375 in simplescreenrecorder 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 #1040375 [simplescreenrecorder-lib]
/usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so: Segmentation
fault when used with anything
Added tag(s) pending.
--
1040375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040375
79 matches
Mail list logo
