Your message dated Sat, 19 Nov 2022 07:49:19 +
with message-id
and subject line Bug#1023662: fixed in adv-17v35x 5.0.6.0-4
has caused the Debian Bug report #1023662,
regarding adv-17v35x-dkms: module fails to build for Linux 6.0
to be marked as done.
This means that you claim that the
Your message dated Sat, 19 Nov 2022 06:35:11 +
with message-id
and subject line Bug#1024315: fixed in stopt 5.1+dfsg-6
has caused the Debian Bug report #1024315,
regarding stopt: b-d on python3-all-dev, but not built for all supported
Python3 versions
to be marked as done.
This means that
Hi,
On Sat, Nov 19, 2022 at 02:06:04AM +0200, Adrian Bunk wrote:
Control: tags -1 fixed-upstream
On Sun, Nov 13, 2022 at 10:04:04AM +0200, Stefano Rivera wrote:
Hi Helmut (2022.11.04_11:36:41_+0200)
> And no, updating it to 3.4 does not fix the ftbfs.
Updating it to 3.4.1 might. It includes
Processing control commands:
> tags -1 fixed-upstream
Bug #1022526 [src:python-ssdeep] python-ssdeep: FTBFS:
distutils.errors.DistutilsClassError: command class must subclass Command
Added tag(s) fixed-upstream.
--
1022526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022526
Debian Bug
Control: tags -1 fixed-upstream
On Sun, Nov 13, 2022 at 10:04:04AM +0200, Stefano Rivera wrote:
> Hi Helmut (2022.11.04_11:36:41_+0200)
> > And no, updating it to 3.4 does not fix the ftbfs.
>
> Updating it to 3.4.1 might. It includes this commit:
>
Your message dated Fri, 18 Nov 2022 23:50:58 +
with message-id
and subject line Bug#1019663: fixed in ruby-ronn 0.9.1-3
has caused the Debian Bug report #1019663,
regarding ruby-ronn: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
to be marked as done.
This means that you claim that the
Processing control commands:
> tag -1 pending
Bug #1019663 [src:ruby-ronn] ruby-ronn: FTBFS with ruby3.1: ERROR: Test
"ruby3.1" failed.
Added tag(s) pending.
--
1019663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 pending
Hello,
Bug #1019663 in ruby-ronn 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:
Andrea Pappacoda, le sam. 19 nov. 2022 00:21:08 +0100, a ecrit:
> Anyway, would you simply suggest to drop the `u` shell option?
I'd say so. Here the preinst script definitely is expected to see either
$2 set or not.
Samuel
Hello,
On Sat 19 Nov 2022 at 06:50AM +09, Tatsuya Kinoshita wrote:
> On 2022-11-18 at 11:44 -0700, Sean Whitton wrote:
>> I can't reproduce this locally, and looking at the package tracker for a
>> few of those packages you've listed, piuparts is now passing
>
> The piuparts tests with the
Hi Samuel, thank you very much for the report.
On Fri, 18 Nov 2022 09:40:11 +0100 Samuel Thibault
wrote:
> Version 0.7.3-1 of opensysusers made it uninstallable:
>
> (Reading database ... 936343 files and directories currently
installed.)
> Preparing to unpack
Control: tags 983815 + pending
Dear maintainer,
I've prepared an NMU for python-crc32c (versioned as 2.3-1.1) and
uploaded it to DELAYED/4. Please feel free to tell me if I should
cancel it.
cu
Adrian
diff -Nru python-crc32c-2.3/debian/changelog python-crc32c-2.3/debian/changelog
---
Processing control commands:
> tags 983815 + pending
Bug #983815 {Done: Adrian Bunk } [src:python-crc32c]
python-crc32c: Baseline violation on amd64/arm64/i386 and FTBFS on armhf if
built on 64bit hardware
Bug #1023959 {Done: Adrian Bunk } [src:python-crc32c]
python-crc32c ftbfs on arm64
Added
Your message dated Sat, 19 Nov 2022 00:04:08 +0100
with message-id <87iljblv9z@hands.com>
and subject line shepherd excised, for now
has caused the Debian Bug report #1009711,
regarding openqa: block migration to testing (awaiting availability of packaged
shepherd.js)
to be marked as done.
Your message dated Fri, 18 Nov 2022 22:49:22 +
with message-id
and subject line Bug#1013480: fixed in hyperkitty 1.3.6-1
has caused the Debian Bug report #1013480,
regarding hyperkitty: FTBFS: TypeError: __init__() got an unexpected keyword
argument 'providing_args'
to be marked as done.
Processing control commands:
> tags 880943 + pending
Bug #880943 [pink-pony-data] pink-pony-data: GL shader error when using fancy
water
Ignoring request to alter tags of bug #880943 to the same tags previously set
> tags 1024000 + patch
Bug #1024000 [src:pink-pony] pink-pony: FTBFS: OSError:
Processing control commands:
> tags 880943 + pending
Bug #880943 [pink-pony-data] pink-pony-data: GL shader error when using fancy
water
Added tag(s) pending.
> tags 1024000 + patch
Bug #1024000 [src:pink-pony] pink-pony: FTBFS: OSError: 'pkg-config IlmBase
--cflags --libs' exited 1
Added
Control: tags 880943 + pending
Control: tags 1024000 + patch
Control: tags 1024000 + pending
Dear maintainer,
I've prepared an NMU for pink-pony (versioned as 1.4.1-3.1) and uploaded
it to DELAYED/4. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru
downgrading to 1+2.06+3~deb11x
grub-common grub-efi grub-efi-amd64 grub-efi-amd64-bin
grub-efi-amd64-signed grub2-common shim-helpers-amd64-signed
fix the error.
However the mokutils --list-enrolled command is still void.
-- eric
Your message dated Fri, 18 Nov 2022 22:04:17 +
with message-id
and subject line Bug#1013500: fixed in django-mailman3 1.3.8-1
has caused the Debian Bug report #1013500,
regarding django-mailman3: FTBFS: TypeError: __init__() got an unexpected
keyword argument 'providing_args'
to be marked as
dpkg -s shim-signed
Package: shim-signed
Status: install ok installed
Priority: optional
Section: utils
Installed-Size: 937
Maintainer: Debian EFI Team
Architecture: amd64
Multi-Arch: same
Source: shim-signed (1.38)
Version: 1.38+15.4-7
Depends: shim-signed-common (>= 1.38+15.4-7),
On 2022-11-18 at 11:44 -0700, Sean Whitton wrote:
> I can't reproduce this locally, and looking at the package tracker for a
> few of those packages you've listed, piuparts is now passing
The piuparts tests with the listed pacakges may succeed when emacs
(or emacs{-gtk,-lucid,-nox}) isn't
Processing control commands:
> tags -1 + patch
Bug #1023738 [src:orthanc-dicomweb] orthanc-dicomweb FTBFS with node-axios 1.1
Added tag(s) patch.
--
1023738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + patch
Hi Sébastien,
orthanc-dicomweb is currently affected by a failure to build
from source (Bug#1023738). I took the liberty to have a look,
and it seems that since axios 1.0 the dist/axios.map file is not
provided anymore. This is causing the following cmake error:
Processing control commands:
> tag -1 pending
Bug #1013500 [src:django-mailman3] django-mailman3: FTBFS: TypeError:
__init__() got an unexpected keyword argument 'providing_args'
Added tag(s) pending.
--
1013500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013500
Debian Bug Tracking
Control: tag -1 pending
Hello,
Bug #1013500 in django-mailman3 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:
Your message dated Fri, 18 Nov 2022 21:07:46 +
with message-id
and subject line Bug#1022412: fixed in nncp 8.8.2-1
has caused the Debian Bug report #1022412,
regarding nncp: FTBFS: make[1]: *** [debian/rules:19: override_dh_auto_build]
Error 25
to be marked as done.
This means that you
Processing control commands:
> tag -1 pending
Bug #1024043 [src:python-cassandra-driver] python-cassandra-driver FTBFS with
Python 3.11 as supported version
Added tag(s) pending.
--
1024043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024043
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #1024043 in python-cassandra-driver 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:
Your message dated Fri, 18 Nov 2022 22:59:16 +0200
with message-id
and subject line rust-serial-test-derive 0.9.0 is now in unstable
has caused the Debian Bug report #1024360,
regarding rust-serial-test: build-depends on missing package
librust-serial-test-derive-0.9+default-dev
to be marked as
Your message dated Fri, 18 Nov 2022 20:38:14 +
with message-id
and subject line Bug#1024400: fixed in net-luminis-build-plugin 0.2.0-5
has caused the Debian Bug report #1024400,
regarding net-luminis-build-plugin: broken maintainer field
to be marked as done.
This means that you claim that
Your message dated Fri, 18 Nov 2022 20:34:59 +
with message-id
and subject line Bug#1024390: fixed in dracut 057+157-2
has caused the Debian Bug report #1024390,
regarding dracut-core,dracut-network: both ship
usr/lib/dracut/modules.d/95virtfs/{module-setup,mount-virtfs,parse-virtfs}.sh
to
Your message dated Sat, 19 Nov 2022 04:57:27 +0900
with message-id <20221118195727.w2d6jrsrgsxzg...@glandium.org>
and subject line Re: Bug#1024351: firefox 107.0-1 fails, requiring old libnss3
(version `NSS_3.80' not found)
has caused the Debian Bug report #1024351,
regarding firefox 107.0-1
Hi Oswald,
Bastian Germann wrote on 12/11/2022 at 16:46:44+0100:
> I see that in git there is now LicenseRef-isync-GPL-exception applied to
> mbsync.
Would you agree to release isync 1.4.5 or do I need to import your
license exception?
Cheers!
--
PEB
signature.asc
Description: PGP
Source: net-luminis-build-plugin
Version: 0.2.0-4
Severity: serious
X-Debbugs-Cc: ta...@debian.org
Hi,
The upload of net-luminis-build-plugin which orphaned it appears to
have generated a broken Maintainer field:
Package: net-luminis-build-plugin
Binary: libnet-luminis-build-plugin-java
Am Donnerstag, dem 17.11.2022 um 13:52 + schrieb Amr Ibrahim:
> On Sat, 24 Sep 2022 21:37:45 +0200 Guillem Jover wrote:
>
> > I've kept the package on hold since, but try to upgrade from time to
> > time to see whether its fixed. Last time I did with the latest version
> > currently in sid,
Processing control commands:
> reopen -1
Bug #1020258 {Done: Sean Whitton } [emacs] emacs:
elpa-*: fails to install: libgccjit.so: error: error invoking gcc driver
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to
control: reopen -1
control: notfixed -1 1:28.2+1-5
Hello,
On Fri 18 Nov 2022 at 11:44AM -07, Sean Whitton wrote:
>> elpa-treemacs-magit=2.8-2
>> elpa-use-package-chords=2.4.1-1
>> elpa-weechat=0.5.0-5
>>
>> I cannot reproduce this in testing (which still has emacs 1.27),
>> so this seems to
Your message dated Fri, 18 Nov 2022 11:44:19 -0700
with message-id <875yfcm7b0@melete.silentflame.com>
and subject line Re: Bug#1020258: elpa-*: fails to install: libgccjit.so:
error: error invoking gcc driver
has caused the Debian Bug report #1020258,
regarding emacs: elpa-*: fails to
IMHO this should be considered a bug in imath, which has taken over
libilmbase-dev with a Provides: (and ilmbase has been removed from the
archive), but does not provide all the interfaces necessary to actually be
compatible.
--
Steve Langasek Give me a lever long enough and a
So apparently the keys is still there but mokutil does not see it.
Strange!
-- eric
Package: grub-efi-amd64-bin
Version: 1+2.06+5
Severity: grave
Tags: security
Justification: user security hole
X-Debbugs-Cc: Debian Security Team
After upgrade to 2.06-5, I get an error message "prohibited by secure boot
policy" and it boot
with a strange look with \xe7caracaters instead of
Processing control commands:
> severity -1 serious
Bug #1023624 [src:pytoml] RM: pytoml -- ROM; obsoleted by upstream;
alternatives exist
Severity set to 'serious' from 'normal'
--
1023624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023624
Debian Bug Tracking System
Contact
Control: severity -1 important
On Fri, Nov 18, 2022 at 12:51 PM Andreas Beckmann wrote:
> Package: libtepl-6-1
> Version: 6.2.0-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package fails to upgrade from
>
Processing control commands:
> severity -1 important
Bug #1024388 [libtepl-6-1] libtepl-6-1: missing (unversioned) Breaks+Replaces:
libtepl-6-0
Severity set to 'important' from 'serious'
--
1024388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024388
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> close 1023995 1.3.10+dfsg-1
Bug #1023995 [src:starpu-contrib] starpu-contrib: requires rebuild for freeglut
transition
Marked as fixed in versions starpu-contrib/1.3.10+dfsg-1.
Bug #1023995 [src:starpu-contrib] starpu-contrib: requires rebuild
Processing control commands:
> tags 1024048 + patch
Bug #1024048 [src:pyliblo] pyliblo FTBFS with Python 3.11 as supported version
Added tag(s) patch.
> tags 1024048 + pending
Bug #1024048 [src:pyliblo] pyliblo FTBFS with Python 3.11 as supported version
Added tag(s) pending.
--
1024048:
Control: tags 1024048 + patch
Control: tags 1024048 + pending
Dear maintainer,
I've prepared an NMU for pyliblo (versioned as 0.10.0-5.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
SR
diff -Nru pyliblo-0.10.0/debian/changelog
Processing control commands:
> clone -1 -2
Bug #1024391 [src:gtk4] gtk4: FTBFS on big-endian: some dependency made
border-image-excess-size reftest regress
Bug 1024391 cloned as bug 1024392
> retitle -2 gtk+3.0: FTBFS on big-endian: some dependency made
> border-image-excess-size reftest
Source: gtk4
Version: 4.8.2+ds-1
Severity: serious
Tags: ftbfs help
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-s...@lists.debian.org, debian-powe...@lists.debian.org
Control: clone -1 -2
Control: retitle -2 gtk+3.0: FTBFS on big-endian: some
Your message dated Fri, 18 Nov 2022 18:05:41 +
with message-id
and subject line Bug#1024301: fixed in redland-bindings 1.0.17.1+dfsg-4
has caused the Debian Bug report #1024301,
regarding redland-bindings: b-d on python3-all-dev, but not built for all
supported Python3 versions
to be marked
Processing commands for cont...@bugs.debian.org:
> affects 1024008 + src:guiqwt
Bug #1024008 [python3-spyder] python3-spyder is not installable
Added indication that 1024008 affects src:guiqwt
> tags 1024008 + ftbfs
Bug #1024008 [python3-spyder] python3-spyder is not installable
Added tag(s)
Processing commands for cont...@bugs.debian.org:
> tags 1024148 + ftbfs
Bug #1024148 [python3-coverage] python3-coverage: Python 3.11 support
incomplete due to ignored error during build
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Package: dracut-core,dracut-network
Version: 057+157-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
>From the attached log (scroll to the
Package: libtepl-6-1
Version: 6.2.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other
Processing commands for cont...@bugs.debian.org:
> severity 1024248 serious
Bug #1024248 [python3.11] [python3.11] platform.python_version() returns wrong
value
Severity set to 'serious' from 'important'
> tags 1024248 + ftbfs
Bug #1024248 [python3.11] [python3.11] platform.python_version()
Package: python3-pastedeploy-tpl
Version: 3.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to
Processing control commands:
> found -1 1.0.1.0.0.git.3011926+ds-2
Bug #1023807 {Done: Michael R. Crusoe } [seqan-needle]
seqan-needle: /usr/bin/needle is already shipped by emboss
Marked as found in versions seqan-needle/1.0.1.0.0.git.3011926+ds-2; no longer
marked as fixed in versions
Followup-For: Bug #1023807
Control: found -1 1.0.1.0.0.git.3011926+ds-2
Something didn't work with the moving of the binary to /usr/lib/debian-med/bin
...
drwxr-xr-x root/root 0 2022-11-16 17:00 ./
drwxr-xr-x root/root 0 2022-11-16 17:00 ./usr/
drwxr-xr-x root/root 0
Your message dated Fri, 18 Nov 2022 17:15:30 +
with message-id
and subject line Bug#1023951: fixed in python-pyscss 1.4.0-3
has caused the Debian Bug report #1023951,
regarding python-pyscss FTBFS with Python 3.11 as supported version
to be marked as done.
This means that you claim that the
Your message dated Fri, 18 Nov 2022 17:14:15 +
with message-id
and subject line Bug#1024207: fixed in beancount 2.3.5-2
has caused the Debian Bug report #1024207,
regarding beancount FTBFS with Python 3.11 as supported version
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 18 Nov 2022 16:52:49 +
with message-id
and subject line Bug#1017158: fixed in gimp-gap 2.6.0+dfsg-7
has caused the Debian Bug report #1017158,
regarding gimp-gap: FTBFS: ld: gap_mov_exec.o: undefined reference to symbol
'atan@@GLIBC_2.2.5'
to be marked as done.
This
Your message dated Fri, 18 Nov 2022 16:56:15 +
with message-id
and subject line Bug#1024088: fixed in pycxx 7.1.7-2
has caused the Debian Bug report #1024088,
regarding pycxx needs a source-only upload to add support for Python 3.11
to be marked as done.
This means that you claim that the
Processing control commands:
> tag -1 pending
Bug #1023951 [src:python-pyscss] python-pyscss FTBFS with Python 3.11 as
supported version
Added tag(s) pending.
--
1023951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 pending
Hello,
Bug #1023951 in python-pyscss 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:
Control: tag -1 pending
Hello,
Bug #1024088 in pycxx 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 #1024088 [src:pycxx] pycxx needs a source-only upload to add support for
Python 3.11
Added tag(s) pending.
--
1024088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing commands for cont...@bugs.debian.org:
> close 1023707 62
Bug #1023707 [src:cross-toolchain-base] src:cross-toolchain-base: unsatisfied
build dependency in testing: linux-source-5.19
Marked as fixed in versions cross-toolchain-base/62.
Bug #1023707 [src:cross-toolchain-base]
Processing control commands:
> tags 1020527 + patch
Bug #1020527 [pam-p11] pam-p11: upcoming FTBFS
Added tag(s) patch.
> tags 1020527 + pending
Bug #1020527 [pam-p11] pam-p11: upcoming FTBFS
Added tag(s) pending.
--
1020527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020527
Debian Bug
Control: tags 1020527 + patch
Control: tags 1020527 + pending
Dear maintainer,
I've prepared an NMU for pam-p11 (versioned as 0.3.1-1.2) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru pam-p11-0.3.1/debian/changelog
Processing control commands:
> retitle -1 pythonmagick: only default python3 version extension is published
> in deb
Bug #1024299 [src:pythonmagick] pythonmagick: b-d on python3-all-dev, but not
built for all supported Python3 versions
Changed Bug title to 'pythonmagick: only default python3
Control: retitle -1 pythonmagick: only default python3 version extension is
published in deb
Hi Graham (2022.11.17_11:40:02_+0200)
> This package build-depends on python3-all-dev, but does not build
> extensions/libraries for all supported python3 versions.
It was trying to, but they were
Control: tag -1 pending
Hello,
Bug #1024299 in pythonmagick 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 #1024299 [src:pythonmagick] pythonmagick: b-d on python3-all-dev, but not
built for all supported Python3 versions
Added tag(s) pending.
--
1024299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024299
Debian Bug Tracking System
Contact
Hi Christoph,
> when do you plan to upload the fixed version?
> If you need any help, please let us know.
The VM where I was building and testing the amd64 package is
currently broken. I should be able to build the package anyway
on a chroot, but I have no means to test it ATM.
I can build and
Your message dated Fri, 18 Nov 2022 11:37:26 +
with message-id
and subject line Bug#997592: fixed in node-copy-webpack-plugin 11.0.0-1
has caused the Debian Bug report #997592,
regarding node-copy-webpack-plugin: FTBFS: dh_auto_test: error: /bin/sh -ex
debian/tests/pkg-js/test returned exit
Your message dated Fri, 18 Nov 2022 11:24:21 +
with message-id
and subject line Bug#1023914: fixed in urwid 2.1.2-3
has caused the Debian Bug report #1023914,
regarding urwid FTBFS with Python 3.11 as supported version
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 18 Nov 2022 13:19:01 +0200
with message-id <20221118111901.swnuyp5k6nosf...@haydn.kardiogramm.net>
and subject line Re: Bug#998854: undefined symbol:
_PyUnicode_DecodeUnicodeEscape
has caused the Debian Bug report #998854,
regarding undefined symbol:
Your message dated Fri, 18 Nov 2022 11:09:03 +
with message-id
and subject line Bug#1023969: fixed in python3-typed-ast 1.5.4-1
has caused the Debian Bug report #1023969,
regarding python3-typed-ast FTBFS with Python 3.11 as supported version
to be marked as done.
This means that you claim
Your message dated Fri, 18 Nov 2022 11:04:31 +
with message-id
and subject line Bug#1024168: fixed in cruft-ng 0.9.48
has caused the Debian Bug report #1024168,
regarding cruft-ng: autopkgtest failure:
/usr/libexec/cruft/init-system-helpers: 4: file: not found
to be marked as done.
This
Source: game-music-emu
Version: 0.6.3-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
game-music-emu fails to build from source on armel, armhf, i386 and mipsel,
plus various "ports" architectures that are also 32-bit:
>
Your message dated Fri, 18 Nov 2022 10:49:20 +
with message-id
and subject line Bug#1020747: fixed in autoconf-archive 20220903-3
has caused the Debian Bug report #1020747,
regarding autoconf-archive: ax_python_devel serial 32 fails with current Sid
python3
to be marked as done.
This means
Processing control commands:
> tag -1 pending
Bug #1023969 [src:python3-typed-ast] python3-typed-ast FTBFS with Python 3.11
as supported version
Added tag(s) pending.
--
1023969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023969
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Control: tag -1 pending
Hello,
Bug #1023969 in python3-typed-ast 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:
> tags 1023901 + patch
Bug #1023901 [src:python-libtrace] python-libtrace FTBFS with Python 3.11 as
supported version
Added tag(s) patch.
> tags 1023901 + pending
Bug #1023901 [src:python-libtrace] python-libtrace FTBFS with Python 3.11 as
supported version
Added
Control: tags 1023901 + patch
Control: tags 1023901 + pending
Control: forwarded 1023901
https://github.com/nevil-brownlee/python-libtrace/pull/13
Dear maintainer,
I've prepared an NMU for python-libtrace (versioned as 1.6+git20180219-1.1) and
uploaded it to DELAYED/5. Please feel free to tell
Your message dated Fri, 18 Nov 2022 10:19:14 +
with message-id
and subject line Bug#1024349: fixed in diffoscope 227
has caused the Debian Bug report #1024349,
regarding diffoscope -- Fails its autopkgtests blocking testing migration
to be marked as done.
This means that you claim that the
Your message dated Fri, 18 Nov 2022 10:19:14 +
with message-id
and subject line Bug#1024171: fixed in diffoscope 227
has caused the Debian Bug report #1024171,
regarding diffoscope: autopkgtest regression: 'NoneType' object has no
attribute 'add_comment'
to be marked as done.
This means
Source: rust-serial-test
Version: 0.5.1-3
Severity: grave
Tags: ftbfs
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Build-depends on missing package librust-serial-test-derive-0.9+default-dev
-BEGIN PGP SIGNATURE-
Control: tags 1024265 + pending
Dear maintainer,
I've prepared an NMU for opengv (versioned as 1.0+1git91f4b1-6.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
The patch (thanks Tyler!) may not be ideal, it's building the whole of the big
package,
Processing control commands:
> tags 1024265 + pending
Bug #1024265 [src:opengv] opengv: Build for all supported python3 versions or
Build-Depend on python3-dev
Added tag(s) pending.
--
1024265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024265
Debian Bug Tracking System
Contact
Control: tags 1023903 + patch
Control: tags 1023903 + pending
Dear maintainer,
I've prepared an NMU for python-clickhouse-driver (versioned as 0.2.3-2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
SR
diff -Nru
Processing control commands:
> tags 1023903 + patch
Bug #1023903 [src:python-clickhouse-driver] python-clickhouse-driver FTBFS with
Python 3.11 as supported version
Added tag(s) patch.
> tags 1023903 + pending
Bug #1023903 [src:python-clickhouse-driver] python-clickhouse-driver FTBFS with
Just for completeness' sake: The PPC build failure boils down to a GCC
issue, failing to handle "constexpr double double" arithmetic.
See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107745 for details.
s2geometry contains a workaround removing the constexpr optimization
(for now on all
Your message dated Fri, 18 Nov 2022 09:05:33 +
with message-id
and subject line Bug#1024240: fixed in os-autoinst 4.6.1667579802.62acb888-2
has caused the Debian Bug report #1024240,
regarding os-autoinst FTBFS: 29-backend-generalhw.t failure
to be marked as done.
This means that you claim
Hi,
On Fri, Nov 18, 2022 at 4:12 PM David Prévot wrote:
>
> Hi,
>
> Le 18/11/2022 à 06:36, Olly Betts a écrit :
> > On Fri, Nov 18, 2022 at 11:06:07AM +0800, Bo YU wrote:
> >> On Fri, Nov 18, 2022 at 3:34 AM Olly Betts wrote:
>
> […]
> > | I suggest you to pick the current trunk code (r13000),
Package: opensysusers
Version: 0.7.3-1
Severity: grave
Justification: renders package unusable
Hello,
Version 0.7.3-1 of opensysusers made it uninstallable:
(Reading database ... 936343 files and directories currently installed.)
Preparing to unpack .../opensysusers_0.7.3-1_all.deb ...
Adding
Hi,
Le 18/11/2022 à 06:36, Olly Betts a écrit :
On Fri, Nov 18, 2022 at 11:06:07AM +0800, Bo YU wrote:
On Fri, Nov 18, 2022 at 3:34 AM Olly Betts wrote:
[…]
| I suggest you to pick the current trunk code (r13000), it is not a
| release but it is more stable than 20.03
So they're
Hi Sam,
On Thu, Nov 17, 2022 at 01:11:44PM -0700, Sam Hartman wrote:
> > "Salvatore" == Salvatore Bonaccorso writes:
> Salvatore> Thanks for sharing the analysis. Can you prepare debdiff
> Salvatore> for bullseye-security accordingly, so we can release an
> Salvatore> update via
Package: firefox
Version: 107.0-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: domel...@gmail.com
Dear Maintainer,
After 'apt upgrade'-ing my system, I find myself unable to run firefox.
I am on a hybrid testing+unstable Debian, with the following package
versions:
-
100 matches
Mail list logo
