Bug#971783: mate-volume-control-status-icon dies here too

2021-11-18 Thread Maxime G.
Hi Mike. Thanks for your reply about 1.26. But it seems that the project don't want to take on this. https://github.com/mate-desktop/mate-media/issues/159 https://github.com/mate-desktop/mate-media/issues/167 https://github.com/mate-desktop/mate-media/issues/109

Processed: Re: debootstrap: --no-merged-usr became a no-op

2021-11-18 Thread Debian Bug Tracking System
Processing control commands: > affects -1 mmdebstrap Bug #998867 [debootstrap] debootstrap: --no-merged-usr became a no-op Added indication that 998867 affects mmdebstrap -- 998867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998867 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#998867: debootstrap: --no-merged-usr became a no-op

2021-11-18 Thread Johannes Schauer Marin Rodrigues
Control: affects -1 mmdebstrap Hi, Quoting Dimitri John Ledkov (2021-11-15 14:54:36) > > Please point out what you plan to do about this change in debootstrap so > > that I can adapt the mmdebstrap autopkgtest accordingly. > > I did notice the mmdebstrap autopkgtest regression. [...] this bug

Processed: Re: prototypejs: FTBFS

2021-11-18 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #993301 [src:prototypejs] prototypejs: FTBFS Severity set to 'normal' from 'serious' -- 993301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#993301: prototypejs: FTBFS

2021-11-18 Thread Andreas Beckmann
Control: severity -1 normal On 18/11/2021 20.24, Bastien ROUCARIES wrote: The source is https://github.com/prototypejs/prototype/tree/master and I can rebuild prototypejs/1.7.1-3.1 in sid and bullseye without problems. What errors do you encounter? Yes but this not prefered source of

Processed: Re: mate-volume-control-status-icon dies here too

2021-11-18 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #971783 [mate-media] mate-media: volume-control-applet dies often Severity set to 'serious' from 'normal' -- 971783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971783 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1000178: llvmlite: FTBFS with Python 3.10

2021-11-18 Thread Graham Inggs
Source: llvmlite Version: 0.37.0-1 Severity: serious User: debian-pyt...@lists.debian.org Usertags: python3.10 Hi Maintainer llvmlite FTBFS with Python 3.10 as a supported version [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1]

Bug#1000163: phast FTBFS: pcre.h: No such file or directory

2021-11-18 Thread Andreas Tille
Hi Adrian, Am Thu, Nov 18, 2021 at 11:13:33PM +0200 schrieb Adrian Bunk: > Source: phast > Version: 1.6+dfsg-2 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/logs.php?pkg=phast=1.6%2Bdfsg-2 > > ... > /<>/src/../include/phast/stringsplus.h:27:10: fatal error: > pcre.h:

Bug#999367: marked as done (py-postgresql ftbfs with Python 3.10 (test failures))

2021-11-18 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 03:35:08 + with message-id and subject line Bug#999367: fixed in py-postgresql 1.2.1+git20180803.ef7b9a9-4 has caused the Debian Bug report #999367, regarding py-postgresql ftbfs with Python 3.10 (test failures) to be marked as done. This means that you

Bug#997719: libvirt-python: FTBFS: ERROR: failed virDomainGetMessages

2021-11-18 Thread Stefano Rivera
Hi Lucas (2021.10.24_07:40:18_-0400) Looks like a mismatch between libvirt-python and libvirt itself, that would be resolved by upgrading it to version 7.6.0 (or later). SR

Bug#997363: libtorrent-rasterbar: FTBFS: configure: error: *** A compiler with support for C++17 language features is required.

2021-11-18 Thread Stefano Rivera
Presumably resolved in 2.0.0 in NEW, that doesn't use autoconf any more. SR

Bug#984256: nextepc: ftbfs with GCC-11

2021-11-18 Thread Steve Langasek
Package: nextepc Version: 0.3.10+nods-4.1 Followup-For: Bug #984256 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy ubuntu-patch Control: tags -1 patch Hi Ruben, Please find attached a patch for this issue. It has been uploaded to Ubuntu to fix the build failure there. --

Processed: Re: nextepc: ftbfs with GCC-11

2021-11-18 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #984256 [src:nextepc] nextepc: ftbfs with GCC-11 Added tag(s) patch. -- 984256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1000175: python3-lz4tools is empty

2021-11-18 Thread Adrian Bunk
Package: python3-lz4tools Version: 1.3.1.1-4 Severity: grave $ dpkg -L python3-lz4tools /. /usr /usr/share /usr/share/doc /usr/share/doc/python3-lz4tools /usr/share/doc/python3-lz4tools/changelog.Debian.gz /usr/share/doc/python3-lz4tools/copyright $

Bug#999815: cryptsetup - build-depends on removed package.

2021-11-18 Thread Guilhem Moulin
On Thu, 18 Nov 2021 at 23:13:59 +0100, Christian Göttsche wrote: > A quick test build without those two build-dependencies resulted in > identical binary packages. They are currently pulled transitively by libdevmapper-dev, so removing them from the explicit Build-Depends doesn't yield a

Bug#998455: regina-normal: b-d on python3-all-dev, but not built for all supported Python3 versions

2021-11-18 Thread Benjamin Burton
Thanks - there is a new upstream release coming hopefully within the next month, and I will update the build-depends when I push that through. - Ben.

Bug#998443: marked as done (sugar-datastore: b-d on python3-all-dev, but not built for all supported Python3 versions)

2021-11-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 22:05:11 + with message-id and subject line Bug#998443: fixed in sugar-datastore 0.118-3 has caused the Debian Bug report #998443, regarding sugar-datastore: b-d on python3-all-dev, but not built for all supported Python3 versions to be marked as done.

Bug#995980: marked as done (assimp FTCBFS: very wrong python dependency and more issues)

2021-11-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 22:03:38 + with message-id and subject line Bug#995980: fixed in assimp 5.0.1~ds0-4 has caused the Debian Bug report #995980, regarding assimp FTCBFS: very wrong python dependency and more issues to be marked as done. This means that you claim that the

Bug#998442: marked as done (link-grammar: b-d on python3-all-dev, but not built for all supported Python3 versions)

2021-11-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 21:50:09 + with message-id and subject line Bug#998442: fixed in link-grammar 5.10.2~dfsg-2 has caused the Debian Bug report #998442, regarding link-grammar: b-d on python3-all-dev, but not built for all supported Python3 versions to be marked as done.

Bug#1000169: gufw: Does not start

2021-11-18 Thread Witold Baryluk
Package: gufw Version: 20.04.1-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: witold.bary...@gmail.com It is broken: root@debian:~# gufw /usr/bin/gufw: line 2: [: =: unary operator expected ls: cannot access '/usr/lib/python*/site-packages/gufw/gufw.py': No such file or

Bug#995843: abook: complete d/copyright file

2021-11-18 Thread Jochen Sprickerhof
Hi Rhonda, I've seen that you pushed some commits to your repo and Salsa, great :). Do you still plan to upload them to Debian (tesing removal would be tomorrow)? I've also seen that you force pushed away some commits.. just wondering. And yes I would be happy if you add me to the repo

Bug#997399: marked as done (caja-admin: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --l

2021-11-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 21:33:51 + with message-id and subject line Bug#997399: fixed in caja-admin 0.0.5-1 has caused the Debian Bug report #997399, regarding caja-admin: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload

Bug#1000165: xdmf FTBFS with more than one supported python3 version

2021-11-18 Thread Adrian Bunk
Source: xdmf Version: 3.0+git20190531-8 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=xdmf=3.0%2Bgit20190531-8%2Bb1 ... dh_missing -a -O--buildsystem=cmake dh_missing: warning: usr/lib/python3.10/xdmf/Xdmf.py exists in debian/tmp but is not installed to anywhere

Bug#984201: marked as done (libosl: ftbfs with GCC-11)

2021-11-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 21:19:31 + with message-id and subject line Bug#984201: fixed in libosl 0.8.0-4 has caused the Debian Bug report #984201, regarding libosl: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1000163: phast FTBFS: pcre.h: No such file or directory

2021-11-18 Thread Adrian Bunk
Source: phast Version: 1.6+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=phast=1.6%2Bdfsg-2 ... /<>/src/../include/phast/stringsplus.h:27:10: fatal error: pcre.h: No such file or directory 27 | #include | ^~~~ compilation terminated.

Bug#999409: marked as done (jpy ftbfs with Python 3.10)

2021-11-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 21:05:59 + with message-id and subject line Bug#999409: fixed in jpy 0.9.0-4 has caused the Debian Bug report #999409, regarding jpy ftbfs with Python 3.10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#997877:

2021-11-18 Thread Michael Hudson-Doyle
I think an update to 3.3.5 will fix this. I have no idea how hard mailman3 upstream updates are :)

Processed: raise severity of python3.10 bugs

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 995980 serious Bug #995980 [src:assimp] assimp FTCBFS: very wrong python dependency and more issues Ignoring request to change severity of Bug 995980 to the same value. > severity 998395 serious Bug #998395 [src:google-auth-httplib2]

Processed: severity of 995980 is serious

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 995980 serious Bug #995980 [src:assimp] assimp FTCBFS: very wrong python dependency and more issues Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 995980:

Bug#1000162: ima-evm-utils: FTBFS with no internet connection

2021-11-18 Thread Bastian Germann
Source: ima-evm-utils Severity: serious Version: 1.3.2-2.1 Hey, Your package fails to build from scratch in an environment with no internect connection. Please check the buildd logs for this. Thanks, Bastian

Bug#999632: r-bioc-isoformswitchanalyzer FTBFS: ERROR: dependencies ‘DRIMSeq’, ‘tximeta’ are not available

2021-11-18 Thread Steffen Möller
On 14.11.21 08:47, Andreas Tille wrote: Control: blocked -1 by 995252 Hi Steffen ERROR: dependencies ‘DRIMSeq’, ‘tximeta’ are not available for package ‘IsoformSwitchAnalyzeR’ r-bioc-tximeta is in Debian and just needs to be mentioned in Build-Depends. However, Git seems not to be up to

Processed: Re: vtk7: ftbfs with GCC-11

2021-11-18 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #984401 [src:vtk7] vtk7: ftbfs with GCC-11 Added tag(s) patch. -- 984401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#984401: vtk7: ftbfs with GCC-11

2021-11-18 Thread Steve Langasek
Package: vtk7 Version: 7.1.1+dfsg2-10 Followup-For: Bug #984401 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy ubuntu-patch Control: tags -1 patch Please find attached a patch which has been uploaded to Ubuntu to fix this build failure. -- Steve Langasek

Bug#995999: marked as done (FTBFS: FAIL: TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks)

2021-11-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 19:37:19 + with message-id and subject line Bug#995999: fixed in prometheus 2.31.1+ds1-1 has caused the Debian Bug report #995999, regarding FTBFS: FAIL: TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks to be marked as done. This means that you claim

Bug#993301: prototypejs: FTBFS

2021-11-18 Thread Bastien ROUCARIES
Le mer. 17 nov. 2021 à 13:02, Andreas Beckmann a écrit : > Control: tag -1 moreinfo > > On Mon, 30 Aug 2021 12:23:22 + "=?utf-8?q?Bastien_Roucari=C3=A8s?=" > wrote: > > Source: prototypejs > > Severity: serious > > Justification: 4 > > > > Dear Maintainer, > > > > The source is

Bug#1000157: pampi FTBFS: pyuic5: No such file or directory

2021-11-18 Thread Adrian Bunk
Source: pampi Version: 1.1+dfsg1-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=pampi=all=1.1%2Bdfsg1-2=1637082767=0 ... make[3]: Entering directory '/<>/pampi/libs' pyuic5 main.ui -o ui_main.py make[3]: pyuic5: No such file or directory make[3]: *** [Makefile:11:

Bug#998156: contains non-DFSG-free files

2021-11-18 Thread Ryan Kavanagh
On Thu, Nov 18, 2021 at 12:44:21PM -0600, Henry Cejtin wrote: > Has there ben any progress on getting MLton packaged for Debian? Yes. The sticking point is that mlton requires itself or smlnj to compile itself. The current version of mlton in the archives has been uninstallable for years, so I've

Bug#998156: contains non-DFSG-free files

2021-11-18 Thread Henry Cejtin
Has there ben any progress on getting MLton packaged for Debian? Is there anything I can do to help? I haven't seen anything since Matthew Fluet's response. On Sat, Oct 30, 2021 at 10:39 PM Ryan Kavanagh wrote: > > Package: mlton > Version: 20100608-5.1 > Severity: serious > Tags: upstream >

Bug#999348: marked as done (gtk-d: FTBFS with ldc 1.28.0)

2021-11-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 18:33:41 + with message-id and subject line Bug#999348: fixed in gtk-d 3.10.0-1 has caused the Debian Bug report #999348, regarding gtk-d: FTBFS with ldc 1.28.0 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: [bts-link] source package redmine

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package redmine > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: Re: Bug#1000140: Acknowledgement (ruby-moneta: FTBFS: mysqld fails to start)

2021-11-18 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 ruby-moneta: FTBFS: mysqld fails to start on tmpfs Bug #1000140 [src:ruby-moneta] ruby-moneta: FTBFS: mysqld fails to start Changed Bug title to 'ruby-moneta: FTBFS: mysqld fails to start on tmpfs' from 'ruby-moneta: FTBFS: mysqld fails to start'. >

Bug#1000140: Acknowledgement (ruby-moneta: FTBFS: mysqld fails to start)

2021-11-18 Thread Antonio Terceiro
Control: retitle -1 ruby-moneta: FTBFS: mysqld fails to start on tmpfs Control: severity -1 important I perceived that this is triggered by my sbuild/schroot setup building packages with a tmpfs overlay (union-overlay-directory=/dev/shm), so this does not happen always. I'm thus downgrading the

Bug#999364: marked as done (libseccomp ftbfs with Python 3.10)

2021-11-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 17:05:05 + with message-id and subject line Bug#999364: fixed in libseccomp 2.5.3-2 has caused the Debian Bug report #999364, regarding libseccomp ftbfs with Python 3.10 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#999815: marked as done (cryptsetup - build-depends on removed package.)

2021-11-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 16:48:38 + with message-id and subject line Bug#999815: fixed in cryptsetup 2:2.4.2-1 has caused the Debian Bug report #999815, regarding cryptsetup - build-depends on removed package. to be marked as done. This means that you claim that the problem has

Bug#993196: Stackpath

2021-11-18 Thread Elena Williams
Hi, We have a list of Stackpath users with complete contacts if interested let me know so that we can send you count, cost and more info of deliver of data GD-PR etc.. Regards, Elena Williams

Processed: tagging 999398

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 999398 + bookworm sid Bug #999398 [src:zodbpickle] zodbpickle ftbfs with Python 3.10 (test failures) Added tag(s) bookworm and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 999398:

Processed: severity of 999398 is serious

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 999398 serious Bug #999398 [src:zodbpickle] zodbpickle ftbfs with Python 3.10 (test failures) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999398:

Processed: severity of 999395 is serious

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 999395 serious Bug #999395 [src:python-zstd] python-zstd ftbfs with Python 3.10 (test failures) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999395:

Processed: tagging 999385

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 999385 + bookworm sid Bug #999385 [src:python-pyalsa] python-pyalsa ftbfs with Python 3.10 Added tag(s) bookworm and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 999385:

Processed: severity of 999385 is serious

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 999385 serious Bug #999385 [src:python-pyalsa] python-pyalsa ftbfs with Python 3.10 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999385:

Processed: tagging 999380

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 999380 + bookworm sid Bug #999380 [src:python-lzo] python-lzo ftbfs with Python 3.10 (test failures) Added tag(s) bookworm and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 999380:

Processed: severity of 999380 is serious

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 999380 serious Bug #999380 [src:python-lzo] python-lzo ftbfs with Python 3.10 (test failures) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999380:

Processed: severity of 999373 is serious

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 999373 serious Bug #999373 [src:python-dmidecode] python-dmidcode ftbfs with Python 3.10 (test failures) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: tagging 999370

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 999370 + bookworm sid Bug #999370 [src:pystemd] pystemd ftbfs with Python 3.10 Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 999370:

Processed: severity of 999367 is serious

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 999367 serious Bug #999367 [src:py-postgresql] py-postgresql ftbfs with Python 3.10 (test failures) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999367:

Processed: severity of 999370 is serious

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 999370 serious Bug #999370 [src:pystemd] pystemd ftbfs with Python 3.10 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999370:

Processed: severity of 999364 is serious

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 999364 serious Bug #999364 [src:libseccomp] libseccomp ftbfs with Python 3.10 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999364:

Processed: severity of 999374 is serious

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 999374 serious Bug #999374 [src:python-gammu] python-gammu ftbfs with Python 3.10 (test failures) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999374:

Processed: tagging 999376

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 999376 + bookworm sid Bug #999376 [src:python-gmpy2] python-gmpy2 ftbfs with Python 3.10 Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 999376:

Processed: severity of 999376 is serious

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 999376 serious Bug #999376 [src:python-gmpy2] python-gmpy2 ftbfs with Python 3.10 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999376:

Bug#999751: marked as done (di-netboot-assistant: please drop shellcheck autopkgtest)

2021-11-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 16:03:30 + with message-id and subject line Bug#999751: fixed in di-netboot-assistant 0.72 has caused the Debian Bug report #999751, regarding di-netboot-assistant: please drop shellcheck autopkgtest to be marked as done. This means that you claim that the

Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32

2021-11-18 Thread Alejandro Colomar
Package: cppcheck Version: 2.6-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: colomar.6@gmail.com Dear Maintainer, I installed and run cppcheck on a system which I had not used for half a year. For that reason, many of its packages were outdated. glibc was on

Processed: bug 995779 is forwarded to https://gitlab.com/mailman/mailman/-/issues/845

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 995779 https://gitlab.com/mailman/mailman/-/issues/845 Bug #995779 [mailman3] autopkgtest fails with sqlalchemy 1.4.23+ds1 Set Bug forwarded-to-address to 'https://gitlab.com/mailman/mailman/-/issues/845'. > thanks Stopping processing

Processed: bug 1000138 is forwarded to https://savannah.gnu.org/bugs/?61504

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1000138 https://savannah.gnu.org/bugs/?61504 Bug #1000138 [screen] /usr/bin/screen: command arguments beyond 62 silently discarded Set Bug forwarded-to-address to 'https://savannah.gnu.org/bugs/?61504'. > thanks Stopping processing

Bug#1000140: ruby-moneta: FTBFS: mysqld fails to start

2021-11-18 Thread Antonio Terceiro
Source: ruby-moneta Version: 1.0.0-9 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs X-Debbugs-CC: debian-r...@lists.debian.org Hi, ruby-moneta fails to build from source. This is a recurring problem. We have a ton of scritps to start mysql for running tests, they are all

Processed: Re: Bug#1000138: command arguments beyond 62 silently discarded

2021-11-18 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1000138 [screen] /usr/bin/screen: command arguments beyond 62 silently discarded Added tag(s) patch. -- 1000138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1000138: command arguments beyond 62 silently discarded

2021-11-18 Thread Ian Jackson
Control: tags -1 + patch I grepped for MAXARGS and arranged for screen to crash rather than silently ignoring arguments. I think this is much better, although it doesn't fully fix the bug. Confusingly, the source uses MAXARGS both for the maximum number of arguments for a shell command, and for

Bug#983996: marked as done (blist: ftbfs with GCC-11)

2021-11-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 14:34:16 + with message-id and subject line Bug#983996: fixed in blist 1.3.6-8 has caused the Debian Bug report #983996, regarding blist: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Processed: bug 996235 is forwarded to https://gitlab.com/gitlab-org/gitlab-fog-azure-rm/-/issues/1

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 996235 https://gitlab.com/gitlab-org/gitlab-fog-azure-rm/-/issues/1 Bug #996235 [src:ruby-gitlab-fog-azure-rm] ruby-gitlab-fog-azure-rm: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: tried to create Proc object

Bug#997135: abydos: FTBFS: You must configure the bibtex_bibfiles setting

2021-11-18 Thread Julian Gilbey
On Sat, Oct 23, 2021 at 08:56:35PM +0200, Lucas Nussbaum wrote: > Source: abydos > Version: 0.5.0+git20201231.344346a-3 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. Ah, and

Bug#983996: marked as pending in blist

2021-11-18 Thread Stefano Rivera
Control: tag -1 pending Hello, Bug #983996 in blist 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:

Processed: Bug#983996 marked as pending in blist

2021-11-18 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #983996 [src:blist] blist: ftbfs with GCC-11 Added tag(s) pending. -- 983996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#998600: marked as done (mdevctl: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101)

2021-11-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 13:34:08 + with message-id and subject line Bug#998600: fixed in mdevctl 1.1.0-1 has caused the Debian Bug report #998600, regarding mdevctl: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101 to be marked as done. This

Bug#1000138: Acknowledgement (/usr/bin/screen: command arguments beyond 62 silently discarded)

2021-11-18 Thread Ian Jackson
Also, it has a problem with long arguments: $ cat t.sh #!/bin/sh all="$*" echo $# ${#all} sleep 5 $ ./t.sh a "$(yes | head -1)" b 3 20003 $ screen ./t.sh a "$(yes | head -1)" b [ displays "3 20003", pauses 5 seconds, exits ] $ screen screen ./t.sh a "$(yes | head -1)" b [ displays "1

Processed (with 3 errors): Confirmed and fix verified

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 998600 + confirmed fixed pending Bug #998600 [src:mdevctl] mdevctl: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101 Added tag(s) pending, fixed, and confirmed. > I was able to confirm the FTBFS and also

Bug#998600: Confirmed and fix verified

2021-11-18 Thread Christian Ehrhardt
tags 998600 + confirmed fixed pending I was able to confirm the FTBFS and also that the 1.1.0-1 that I prepared has fixed it. I'll mark it in the changelog and upload it later. -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd

Bug#1000138: /usr/bin/screen: command arguments beyond 62 silently discarded

2021-11-18 Thread Ian Jackson
Package: screen Version: 4.8.0-7 Severity: serious File: /usr/bin/screen Tags: upstream Justification: data loss X-Debbugs-Cc: t...@womack.net Steps to reproduce and observed behaviour: $ cat t.sh #!/bin/sh echo $# sleep 5 $ ./t.sh {0..999} 1000 $ screen ./t.sh {0..999} [

Processed: tbb 21.03 required for GCC 11

2021-11-18 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #987689 [libtbb2] Upgrade to 2021.03 Severity set to 'serious' from 'important' > tags -1 + sid bookworm Bug #987689 [libtbb2] Upgrade to 2021.03 Added tag(s) sid and bookworm. -- 987689:

Bug#998483: marked as done (ruby-adsf: FTBFS: ERROR: Test "ruby3.0" failed: LoadError: Couldn't find handler for: puma, thin, falcon, webrick.)

2021-11-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 12:52:40 + with message-id and subject line Bug#998483: fixed in ruby-adsf 1.4.5+dfsg1-2 has caused the Debian Bug report #998483, regarding ruby-adsf: FTBFS: ERROR: Test "ruby3.0" failed: LoadError: Couldn't find handler for: puma, thin, falcon, webrick.

Bug#996125: marked as done (ruby-arbre: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError:)

2021-11-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 12:52:46 + with message-id and subject line Bug#996125: fixed in ruby-arbre 1.2.1-5~exp1 has caused the Debian Bug report #996125, regarding ruby-arbre: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: to be marked as done. This means that

Processed: tagging 999397

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 999397 + bookworm sid Bug #999397 [src:siphashc] siphashc ftbfs with Python 3.10 (test failures) Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 999397:

Processed: severity of 999381 is serious

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 999381 serious Bug #999381 [src:python-pairix] python-pairix ftbfs with Python 3.10 (test failures) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999381:

Processed: severity of 999397 is serious

2021-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 999397 serious Bug #999397 [src:siphashc] siphashc ftbfs with Python 3.10 (test failures) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999397:

Processed: Bug#998483 marked as pending in ruby-adsf

2021-11-18 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #998483 [src:ruby-adsf] ruby-adsf: FTBFS: ERROR: Test "ruby3.0" failed: LoadError: Couldn't find handler for: puma, thin, falcon, webrick. Added tag(s) pending. -- 998483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998483 Debian Bug

Bug#998483: marked as pending in ruby-adsf

2021-11-18 Thread Cédric Boutillier
Control: tag -1 pending Hello, Bug #998483 in ruby-adsf 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:

Bug#998600: Ack

2021-11-18 Thread Christian Ehrhardt
Thanks for the rebuild report Lucas, I'll have a look. I was working on 1.1.0 anyway and thereby should be able to resolve this. -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd

Bug#999860: marked as done (python3-cylc fails to install)

2021-11-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 11:03:42 + with message-id and subject line Bug#999860: fixed in cylc-flow 8.0~b3-2 has caused the Debian Bug report #999860, regarding python3-cylc fails to install to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: libpython3.10-stdlib,python3-gdbm: both ship /usr/lib/python3.10/lib-dynload/_dbm.cpython-310-x86_64-linux-gnu.so

2021-11-18 Thread Debian Bug Tracking System
Processing control commands: > found -1 3.10.0-5 Bug #12 [libpython3.10-stdlib,python3-gdbm] libpython3.10-stdlib,python3-gdbm: both ship /usr/lib/python3.10/lib-dynload/_dbm.cpython-310-x86_64-linux-gnu.so There is no source info for the package 'python3-gdbm' at version '3.10.0-5' with

Bug#999912: libpython3.10-stdlib,python3-gdbm: both ship /usr/lib/python3.10/lib-dynload/_dbm.cpython-310-x86_64-linux-gnu.so

2021-11-18 Thread Andreas Beckmann
Package: libpython3.10-stdlib,python3-gdbm Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 3.10.0-5 Control: found -1 3.10.0~b1-3 Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package

Bug#999908: python3-celery-haystack-ng: missing Breaks+Replaces: python3-django-celery-haystack (<< 0.20)

2021-11-18 Thread Andreas Beckmann
Package: python3-celery-haystack-ng Version: 0.20.post2-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 without declaring a Breaks+Replaces

Bug#996386: marked as done (ruby-sham-rack: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick/httputils)

2021-11-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 10:35:49 + with message-id and subject line Bug#996386: fixed in ruby-sham-rack 1.4.1-3 has caused the Debian Bug report #996386, regarding ruby-sham-rack: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick/httputils to be

Processed: Re: Bug#999904: Uncoordinated split of debugedit package out of src:rpm

2021-11-18 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + confirmed pending Bug #04 [src:debugedit,src:rpm] Uncoordinated split of debugedit package out of src:rpm Added tag(s) pending and confirmed. -- 04: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=04 Debian Bug Tracking System Contact

Bug#999904: Uncoordinated split of debugedit package out of src:rpm

2021-11-18 Thread Peter Pentchev
control: tag -1 + confirmed pending On Thu, Nov 18, 2021 at 09:45:06AM +0100, Laurent Bigonville wrote: > Source: debugedit,rpm > Severity: serious > Tags: sid bookworm > > Hello, > > debugedit has been split out of the src:rpm package, but src:rpm is > still building the package as well. > >

Bug#999907: libglobalarrays-dev,libga-dev: both ship /usr/lib/x86_64-linux-gnu/libga.a

2021-11-18 Thread Andreas Beckmann
Package: libglobalarrays-dev,libga-dev Severity: serious Tags: sid bookworm User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 5.7.2-2 Control: found -1 1:2.4.7-5 Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their

Processed: libglobalarrays-dev,libga-dev: both ship /usr/lib/x86_64-linux-gnu/libga.a

2021-11-18 Thread Debian Bug Tracking System
Processing control commands: > found -1 5.7.2-2 Bug #07 [libglobalarrays-dev,libga-dev] libglobalarrays-dev,libga-dev: both ship /usr/lib/x86_64-linux-gnu/libga.a There is no source info for the package 'libga-dev' at version '5.7.2-2' with architecture '' Marked as found in versions

Bug#996386: marked as pending in ruby-sham-rack

2021-11-18 Thread Cédric Boutillier
Control: tag -1 pending Hello, Bug #996386 in ruby-sham-rack 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:

Bug#999903: [Pkg-matrix-maintainers] Bug#999903: python3-olm: python import fails undefined symbol: olm_account_fallback_key

2021-11-18 Thread Jonas Smedegaard
Control: tags -1 +unreproducible +moreinfo Control: severity -1 important Hi Kyle, Quoting Kyle Robbertze (2021-11-18 09:39:57) > Package: python3-olm > Version: 3.2.1~dfsg-7 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > Applications are unable to import

Processed: Bug#996386 marked as pending in ruby-sham-rack

2021-11-18 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996386 [src:ruby-sham-rack] ruby-sham-rack: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick/httputils Added tag(s) pending. -- 996386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996386 Debian Bug

Processed: Re: [Pkg-matrix-maintainers] Bug#999903: python3-olm: python import fails undefined symbol: olm_account_fallback_key

2021-11-18 Thread Debian Bug Tracking System
Processing control commands: > tags -1 +unreproducible +moreinfo Bug #03 [python3-olm] python3-olm: python import fails undefined symbol: olm_account_fallback_key Added tag(s) unreproducible. Bug #03 [python3-olm] python3-olm: python import fails undefined symbol:

Bug#999862: marked as done (sso.debian.org: SSO no longer seems to work)

2021-11-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 09:45:32 + with message-id and subject line Re: Bug#999862: sso.debian.org: SSO no longer seems to work has caused the Debian Bug report #999862, regarding sso.debian.org: SSO no longer seems to work to be marked as done. This means that you claim that the

  1   2   >