Bug#1036869: marked as done (ghostscript: Needs commitment for Debian downstream maintenance)

2024-01-05 Thread Debian Bug Tracking System
Your message dated Sat, 06 Jan 2024 07:51:41 + with message-id and subject line Bug#1036869: fixed in ghostscript 10.02.1~dfsg-2 has caused the Debian Bug report #1036869, regarding ghostscript: Needs commitment for Debian downstream maintenance to be marked as done. This means that you

Bug#1055550: Removal of Python3 package of redland-bindings breaks mozilla-devscripts

2024-01-05 Thread Andreas Tille
Hi Doko, thanks for working on the QA upload to fix #100 and #1056518 of redland-bindings by simply removing the Python3 support. Unfortunately it breaks mozilla-devscripts and thus it cant migrate to testing[1]. Kind regards Andreas. [1]

Bug#1052724: marked as done (u-boot: FTBFS: cc1: error: ‘-fcf-protection=full’ is not supported for this target)

2024-01-05 Thread Debian Bug Tracking System
Your message dated Sat, 06 Jan 2024 03:08:28 + with message-id and subject line Bug#1052724: fixed in u-boot 2024.01~rc6+dfsg-1 has caused the Debian Bug report #1052724, regarding u-boot: FTBFS: cc1: error: ‘-fcf-protection=full’ is not supported for this target to be marked as done. This

Bug#1059657: circuits: autopkgtest failure with Python 3.12

2024-01-05 Thread Yogeswaran Umasankar
Hi, Made a patch to fix the autopkgtest issue with Py 3.12. Attaching the debdiff file. Cheers! diff -Nru circuits-3.2.2/debian/changelog circuits-3.2.2/debian/changelog --- circuits-3.2.2/debian/changelog 2022-12-14 16:15:09.0 + +++ circuits-3.2.2/debian/changelog 2024-01-06

Bug#1057929: marked as done (buildbot: FTBFS: locale.Error: unsupported locale setting)

2024-01-05 Thread Debian Bug Tracking System
Your message dated Sat, 06 Jan 2024 01:16:30 + with message-id and subject line Bug#1057929: fixed in buildbot 3.10.1-1 has caused the Debian Bug report #1057929, regarding buildbot: FTBFS: locale.Error: unsupported locale setting to be marked as done. This means that you claim that the

Processed: tagging 1060105, tagging 1058997

2024-01-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1060105 + sid trixie Bug #1060105 [src:pcl] pcl: FTBFS on i386: failed tests Added tag(s) trixie and sid. > tags 1058997 + sid trixie Bug #1058997 [src:flask-autoindex] flask-autoindex is incompatible with Py3.12 Added tag(s) sid and trixie.

Processed: Re: cmake ftbfs on ppc64el (and ppc64)

2024-01-05 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #1057717 [src:cmake] cmake ftbfs on ppc64el (and ppc64) Severity set to 'normal' from 'serious' > affects -1 + src:cmake Bug #1057717 [src:cmake] cmake ftbfs on ppc64el (and ppc64) Added indication that 1057717 affects src:cmake > reassign -1

Bug#1057717: cmake ftbfs on ppc64el (and ppc64)

2024-01-05 Thread Timo Röhling
Control: severity -1 normal Control: affects -1 + src:cmake Control: reassign -1 libuv1 1.46.0-2 The ppc64 related segfaults seems to have suddenly vanished again with libuv1 1.46.0-3. After some discussion and bug hunting with upstream [1], which could not reproduce the bug on their end, I

Bug#1060107: urweb: FTBFS: http.c:119:32: error: pointer ‘buf’ may be used after ‘realloc’

2024-01-05 Thread Sebastian Ramacher
Source: urweb Version: 20170720+dfsg-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=urweb=ppc64el=20170720%2Bdfsg-2%2Bb1=1704495164=0 /bin/bash

Processed: found 1059869 in 0.5.1-2, notfound 1059869 in 5.0.1-2

2024-01-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1059869 0.5.1-2 Bug #1059869 [src:plakativ] autopkgtest fails Marked as found in versions plakativ/0.5.1-2. > notfound 1059869 5.0.1-2 Bug #1059869 [src:plakativ] autopkgtest fails The source 'plakativ' and version '5.0.1-2' do not appear

Processed: tagging 1059671

2024-01-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1059671 + sid trixie Bug #1059671 [python3-capstone] python3-capstone: Python 3.12 has no module named 'distutils' Added tag(s) trixie and sid. > found 1059671 4.0.2-5 Bug #1059671 [python3-capstone] python3-capstone: Python 3.12 has no

Processed: tagging 1060076, tagging 1060067, tagging 1059842, tagging 1059802

2024-01-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1060076 + sid trixie Bug #1060076 [src:alberta] alberta: FTBFS on ppc64el: error: incompatible function pointer types passing 'int (char *, char *, int)' to parameter of type 'int (*)(void *, void *, int)' Added tag(s) sid and trixie. >

Processed: tagging 1058997

2024-01-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1058997 + help Bug #1058997 [src:flask-autoindex] flask-autoindex is incompatible with Py3.12 Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058997:

Processed: severity of 1058997 is serious

2024-01-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1058997 serious Bug #1058997 [src:flask-autoindex] flask-autoindex is incompatible with Py3.12 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1058997:

Bug#1060106: astc-encoder: FTBFS on i386: failed tests

2024-01-05 Thread Sebastian Ramacher
Source: astc-encoder Version: 4.5.0+ds-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=astc-encoder=i386=4.5.0%2Bds-2%2Bb1=1704479091=0

Bug#1060105: pcl: FTBFS on i386: failed tests

2024-01-05 Thread Sebastian Ramacher
Source: pcl Version: 1.13.0+dfsg-3 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=pcl=i386=1.13.0%2Bdfsg-3%2Bb1=1704477640=0 Total Test time (real) =

Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)

2024-01-05 Thread Sebastian Ramacher
Source: dcmtk Version: 3.6.7-9 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=dcmtk=armel=3.6.7-9%2Bb1=1704494616=0 [ 90%] Building CXX object

Bug#1060102: boost1.74: do not release with trixie

2024-01-05 Thread Sebastian Ramacher
Source: boost1.74 Version: 1.74.0+ds1-23 Severity: serious X-Debbugs-Cc: sramac...@debian.org With boost 1.83 now as default, let's release trixie without boost 1.74. The current list of blockers is: Checking reverse dependencies... # Broken Depends: cctbx: libcctbx0 [amd64 arm64 ppc64el s390x]

Bug#1060101: boost1.81: do not release with trixie

2024-01-05 Thread Sebastian Ramacher
Source: boost1.81 Version: 1.81.0-7 Severity: serious X-Debbugs-Cc: sramac...@debian.org With boost 1.83 now as the default, let's try get boost 1.81 out of trixie. Current blockers are: Checking reverse dependencies... # Broken Depends: r-cran-bh: r-cran-bh # Broken Build-Depends: filezilla:

Processed: closing 1054676

2024-01-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # benchmark fixed, ros2-performance-test-fixture binNMUed > close 1054676 Bug #1054676 [src:ros2-performance-test-fixture] ros2-rosidl: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libperformance_test_fixture.so.0d: undefined reference to

Bug#1060099: telegram-desktop: FTBFS on mips64el: ./obj-mips64el-linux-gnuabi64/Telegram/./obj-mips64el-linux-gnuabi64/Telegram/gen/scheme.cpp:16435:(.text+0x1600a0): relocation truncated to fit: R_MI

2024-01-05 Thread Sebastian Ramacher
Source: telegram-desktop Version: 4.13.1+ds-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=telegram-desktop=mips64el=4.13.1%2Bds-1=1703877441=0 100%]

Bug#1060100: r-cran-rstanarm: FTBFS: Error: segfault from C stack overflow

2024-01-05 Thread Sebastian Ramacher
Source: r-cran-rstanarm Version: 2.26.1-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=r-cran-rstanarm=mips64el=2.26.1-2=1704150178=0

Processed: Re: Bug#1059801: click: autopkgtests are failing

2024-01-05 Thread Debian Bug Tracking System
Processing control commands: > tags -1 ftbfs trixie sid Bug #1059801 [src:click] click: autopkgtests are failing Added tag(s) trixie, sid, and ftbfs. > severity -1 serious Bug #1059801 [src:click] click: autopkgtests are failing Severity set to 'serious' from 'important' -- 1059801:

Bug#1060098: qbs: FTBFS on mips64el: FAIL! : TestBlackbox::pluginDependency() qbs did not run correctly

2024-01-05 Thread Sebastian Ramacher
Source: qbs Version: 2.1.2-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=qbs=mips64el=2.1.2-2=1704035753=0 3: QDEBUG :

Bug#1060097: pytorch: FBFS: /<>/aten/src/ATen/native/quantized/cpu/qlinear_prepack.cpp:249:103: error: cannot convert ‘dnnl::memory::data_type’ to ‘const ideep::dims&’ {aka ‘const std::ve

2024-01-05 Thread Sebastian Ramacher
Source: pytorch Version: 2.0.1+dfsg-5 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=pytorch=amd64=2.0.1%2Bdfsg-5%2Bb1=1704146824=0 [589/1843]

Bug#1060096: hiredes: FTBFS: #118 Returns I/O error on socket timeout: ␛[0;32mPAShiredis-test: test.c:2199: test_async_polling: Assertion `c->err == 0' failed.

2024-01-05 Thread Sebastian Ramacher
Source: hiredis Version: 1.2.0-5 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=hiredis=amd64=1.2.0-5=1704389545=0 Testing against Unix socket

Processed: Bug#1058286 marked as pending in ncrack

2024-01-05 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058286 [src:ncrack] ncrack: FTBFS: configure: error: *** zlib too old - check config.log *** Added tag(s) pending. -- 1058286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058286 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1058286: marked as pending in ncrack

2024-01-05 Thread Peter Wienemann
Control: tag -1 pending Hello, Bug #1058286 in ncrack 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: Re: gtkextra: unmaintained upstream since 2018

2024-01-05 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #967851 [src:gtkextra] gtkextra: unmaintained upstream since 2018 Severity set to 'serious' from 'important' -- 967851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967851 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#877016: Time to drop cpufrequtils?

2024-01-05 Thread Moritz Mühlenhoff
Am Fri, Jan 05, 2024 at 12:08:54PM +0100 schrieb Chris Hofstaedtler: > On Sun, Sep 03, 2023 at 08:26:00PM +0200, Moritz Mühlenhoff wrote: > > severity 877016 serious > > thanks > > > > Am Thu, Sep 28, 2017 at 06:51:30AM -0700 schrieb Mattia Dongili: > > > On Wed, Sep 27, 2017 at 03:16:52PM -0400,

Bug#1058448: marked as done (xphyle: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

2024-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jan 2024 17:54:40 + with message-id and subject line Bug#1058448: fixed in xphyle 4.4.4-1 has caused the Debian Bug report #1058448, regarding xphyle: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

Bug#1057573: linpac: FTBFS: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’}

2024-01-05 Thread Dave Hibberd
The patch is only on git - no one has yet uploaded it to the archive to formally resolve the bug yet.Before January 16 it needs to be uploaded. I can probably mark it as hold on the bug tracker when I have my reference for tags at home.Between us we should be able to manage! Either I’ll pull

Bug#1057573: linpac: FTBFS: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’}

2024-01-05 Thread David Ranch
Hello Dave, I received the following email yesterday which gives me the impression that your patch wasn't accepted. What needs to be done here by Jan 16th? -- linpac 0.28-2 is marked for autoremoval from testing on 2024-01-16 It is affected by these RC bugs: 1057573: linpac: FTBFS: error:

Bug#1060061: marked as done (grub-efi-amd64-bin: out of memory when loading initial ramdisk)

2024-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 5 Jan 2024 18:33:02 +0100 with message-id and subject line Re: Bug#1060061: grub-efi-amd64-bin: out of memory when loading initial ramdisk has caused the Debian Bug report #1060061, regarding grub-efi-amd64-bin: out of memory when loading initial ramdisk to be marked as

Bug#1059237: dde-store: FTBFS: error: ‘const class AppStream::Component’ has no member named ‘developerName’; did you mean ‘developer’?

2024-01-05 Thread Jeremy Bícha
Control: forwarded -1 https://github.com/UbuntuDDE/dde-store/pull/33 Control: tags -1 +patch + uptream Ubuntu has cherry-picked the upstream pull request to fix this issue. Thank you, Jeremy Bícha

Processed (with 1 error): Re: dde-store: FTBFS: error: ‘const class AppStream::Component’ has no member named ‘developerName’; did you mean ‘developer’?

2024-01-05 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/UbuntuDDE/dde-store/pull/33 Bug #1059237 [src:dde-store] dde-store: FTBFS: error: ‘const class AppStream::Component’ has no member named ‘developerName’; did you mean ‘developer’? Set Bug forwarded-to-address to

Bug#1060076: alberta: FTBFS on ppc64el: error: incompatible function pointer types passing 'int (char *, char *, int)' to parameter of type 'int (*)(void *, void *, int)'

2024-01-05 Thread Sebastian Ramacher
Source: alberta Version: 3.0.3-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=alberta=ppc64el=3.0.3-1%2Bb1=1703410988=0 libtool: compile: clang

Bug#1059983: marked as done (gnome-software FTBFS with nocheck profile: ERROR: Program 'appstreamcli' not found or not executable)

2024-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jan 2024 16:50:06 + with message-id and subject line Bug#1059983: fixed in gnome-software 45.3-1 has caused the Debian Bug report #1059983, regarding gnome-software FTBFS with nocheck profile: ERROR: Program 'appstreamcli' not found or not executable to be marked

Bug#1059819: marked as done (g2clib/experimental FTBFS: Could NOT find libaec)

2024-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jan 2024 16:49:52 + with message-id and subject line Bug#1059819: fixed in g2clib 1.8.0-2 has caused the Debian Bug report #1059819, regarding g2clib/experimental FTBFS: Could NOT find libaec to be marked as done. This means that you claim that the problem has been

Bug#1056177: marked as done (librust-tikv-jemalloc-ctl-dev: depends on missing packages)

2024-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 5 Jan 2024 18:35:23 +0200 with message-id and subject line Re: Bug#1056177: librust-tikv-jemalloc-ctl-dev: depends on missing packages has caused the Debian Bug report #1056177, regarding librust-tikv-jemalloc-ctl-dev: depends on missing packages to be marked as done.

Bug#1060072: RM: fheroes2-pkg -- RoQA; Replaced by DFSG-free fheroes2

2024-01-05 Thread Bastian Germann
Source: fheroes-pkg Severity: serious Please file a removal bug for fheroes2-pkg. The fheroes2 package has just entered Debian main and should be considered the successor of this package. If nobody acts or comments on this suggestion, I am going to file a RM bug as soon as fheroes2-pkg is

Bug#1059970: fitspng: autopkgtest regression in testing

2024-01-05 Thread Filip Hroch
Dear Graham, I think the fail is result of linking of different versions of zlib via dependent libraries. Correct me, if I'm wrong, fitspng has the dependences: Build-Depends: debhelper-compat (= 13), libcfitsio-dev, libpng-dev zlib is indirectly linked via both libraries. Currently, in

Bug#1013584: octave-iso2mesh: FTBFS: dh_missing: error: missing files, aborting

2024-01-05 Thread Yue Gui
Source: octave-iso2mesh Version: 1.9.6+ds-7 Severity: serious Justification: FTBFS Tags: sid ftbfs Dear octave-iso2mesh Maintainer, About the issue reported, there is a solution that add "not-installed" file to /debian. This solution refers to Bug Report #964666. More details can be found in

Processed: Bug#1059983 marked as pending in gnome-software

2024-01-05 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1059983 [src:gnome-software] gnome-software FTBFS with nocheck profile: ERROR: Program 'appstreamcli' not found or not executable Added tag(s) pending. -- 1059983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059983 Debian Bug Tracking

Bug#1059983: marked as pending in gnome-software

2024-01-05 Thread Jeremy Bicha
Control: tag -1 pending Hello, Bug #1059983 in gnome-software 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: severity of 1055999 is grave

2024-01-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1055999 grave Bug #1055999 [src:python-asyncssh] python-asyncssh: CVE-2023-46446 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1055999:

Bug#1060067: fuse3: FTBFS: dh_missing: error: missing files, aborting

2024-01-05 Thread Aurelien Jarno
Package: fuse3 Version: 3.14.0-4 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, fuse3 fails to build with error in dh_missing. From my build log on amd64: | dh_fixperms | chmod a-x

Processed: Re: gnome-software FTBFS with nocheck profile: ERROR: Program 'appstreamcli' not found or not executable

2024-01-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1059983 45.1-1 Bug #1059983 [src:gnome-software] gnome-software FTBFS with nocheck profile: ERROR: Program 'appstreamcli' not found or not executable Marked as found in versions gnome-software/45.1-1. > End of message, stopping processing

Bug#1060063: pysph: autopkgtest failure with Python 3.12

2024-01-05 Thread Graham Inggs
Source: pysph Version: 1.0~b1-7 Severity: serious User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer pysph's autopkgtests fail with Python 3.12 [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1]

Bug#963777: marked as done (condor: CVE-2019-18823)

2024-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#963777: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #963777, regarding condor: CVE-2019-18823 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#966726: marked as done (condor: Unversioned Python removal in sid/bullseye)

2024-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#966726: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #966726, regarding condor: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#936323: marked as done (condor: Python2 removal in sid/bullseye)

2024-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#936323: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #936323, regarding condor: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#925657: marked as done (condor: ftbfs with GCC-9)

2024-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#925657: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #925657, regarding condor: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1008634: marked as done (condor: CVE-2022-26110 / HTCONDOR-2022-0003)

2024-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#1008634: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #1008634, regarding condor: CVE-2022-26110 / HTCONDOR-2022-0003 to be marked as done. This means that you claim that the problem has

Bug#1002540: marked as done (condor: CVE-2021-45101)

2024-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#1002540: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #1002540, regarding condor: CVE-2021-45101 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1000130: marked as done (condor: depends on obsolete pcre3 library)

2024-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#1000130: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #1000130, regarding condor: depends on obsolete pcre3 library to be marked as done. This means that you claim that the problem has been

Bug#1060061: grub-efi-amd64-bin: out of memory when loading initial ramdisk

2024-01-05 Thread Morten Hein Tiljeset
Package: grub-efi-amd64-bin Version: 2.06-3~deb11u6 Severity: critical Tags: upstream Justification: breaks the whole system X-Debbugs-Cc: mtilje...@uber.com Dear Maintainer, On certain system, in this case an Ice Lake based server running an AMI bios (version 3219BS01.021), GRUB will

Bug#999989: poco 1.2 uses PCRE2, Mumble 1.5 depends on poco

2024-01-05 Thread Jochen Sprickerhof
* Chris Knadle [2024-01-02 16:53]: The way to orphan a package is to do an upload and setting the maintainer to be . Until that's done the package ends up in maintainership limbo. See the bottom of Policy 3.3, and Developer's Reference section 5.9.4. Agreed but I think that is something for

Bug#1056031: marked as done (rust-rstest-test: autopkgtest failure)

2024-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 5 Jan 2024 07:11:06 -0500 with message-id and subject line Fixed in 0.11.0-2 has caused the Debian Bug report #1056031, regarding rust-rstest-test: autopkgtest failure to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1037606: clog: diff for NMU version 1.3.0-1.1

2024-01-05 Thread Sudip Mukherjee
Control: tags 1037606 + pending Dear maintainer, I've prepared an NMU for clog (versioned as 1.3.0-1.1) and uploaded it to DELAYED/1. Please feel free to tell me if I should delay it longer. Regards. -- Sudip diff -Nru clog-1.3.0/debian/changelog clog-1.3.0/debian/changelog ---

Processed: clog: diff for NMU version 1.3.0-1.1

2024-01-05 Thread Debian Bug Tracking System
Processing control commands: > tags 1037606 + pending Bug #1037606 [src:clog] clog: ftbfs with GCC-13 Added tag(s) pending. -- 1037606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#877016: Time to drop cpufrequtils?

2024-01-05 Thread Chris Hofstaedtler
On Sun, Sep 03, 2023 at 08:26:00PM +0200, Moritz Mühlenhoff wrote: > severity 877016 serious > thanks > > Am Thu, Sep 28, 2017 at 06:51:30AM -0700 schrieb Mattia Dongili: > > On Wed, Sep 27, 2017 at 03:16:52PM -0400, Phil Susi wrote: > > > Package: cpufrequtils > > > Version: 008-1 > > ... > > >

Bug#1041814: marked as done (python-mechanicalsoup: CVE-2023-34457)

2024-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jan 2024 10:50:50 + with message-id and subject line Bug#1041814: fixed in python-mechanicalsoup 1.3.0-1 has caused the Debian Bug report #1041814, regarding python-mechanicalsoup: CVE-2023-34457 to be marked as done. This means that you claim that the problem has

Processed: Re: Bug#1060052: cifs-utils: Copy file from same cifs mount to cifs mount --> kernel NULL pointer derefernce

2024-01-05 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #1060052 [cifs-utils] cifs-utils: Copy file from same cifs mount to cifs mount --> kernel NULL pointer derefernce Severity set to 'normal' from 'grave' > merge 1060005 -1 Bug #1060005 [cifs-utils] cifs-utils: Copy file with cp, hangs with a

Bug#1060052: cifs-utils: Copy file from same cifs mount to cifs mount --> kernel NULL pointer derefernce

2024-01-05 Thread Michael Tokarev
Control: severity -1 normal Control: merge 1060005 -1 FWIW, this is kernel bug, not cifs-utils bug, - guess it's 6.1.0-17 regression. /mjt

Bug#1060052: cifs-utils: Copy file from same cifs mount to cifs mount --> kernel NULL pointer derefernce

2024-01-05 Thread Hans66
Package: cifs-utils Version: 2:7.0-2 Severity: grave Justification: renders package unusable Dear Maintainer, * Pristine up2date Bookworm install (no GUI, only SSH, cifs-utils, rsyslog installed) * Mount smb/cifs share (/mnt/truenas) * All works fine if I do same from Win-10 or Win-11 OS * I

Processed: severity of 1059007 is grave

2024-01-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1059007 grave Bug #1059007 [src:python-asyncssh] python-asyncssh: CVE-2023-48795 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1059007:

Bug#1058318: flask-login: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-01-05 Thread Carsten Schoenert
Hello Julian, Am 04.01.24 um 10:23 schrieb Julian Gilbey: ... The build of src:flask is depending on python3-werkzeug >= 3.x, which has itself a dependency on python3-markupsafe, so if you spot a missing direct dependency I'm interested how this comes to play as Markupsafe should be around at

Bug#1059971: marked as done (libgl1-mesa-dri: X doesn't start after mesa upgrade from 23.2.1-1 to 23.3.2-1)

2024-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jan 2024 09:36:39 + with message-id and subject line Bug#1059971: fixed in mesa 23.3.2-2 has caused the Debian Bug report #1059971, regarding libgl1-mesa-dri: X doesn't start after mesa upgrade from 23.2.1-1 to 23.3.2-1 to be marked as done. This means that you

Bug#1060017: marked as done (xvfb: Failed to start)

2024-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jan 2024 09:36:39 + with message-id and subject line Bug#1060017: fixed in mesa 23.3.2-2 has caused the Debian Bug report #1060017, regarding xvfb: Failed to start to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1059971: libgl1-mesa-dri: X doesn't start after mesa upgrade from 23.2.1-1 to 23.3.2-1

2024-01-05 Thread Pierre Erraud
> Pierre Erraud kirjoitti 4.1.2024 klo 11.20: > > Package: libgl1-mesa-dri > > Version: 23.3.2-1 > > Severity: important > > > > After doing my usual `apt-get dist-upgrade` this morning & reboot, > > I could not get into gdm anymore. Downgrading to 23.2.1-1 all the > > mesa packages makes it work

Bug#1058108: marked as done (pokrok: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)

2024-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jan 2024 08:55:44 + with message-id and subject line Bug#1058108: fixed in pokrok 0.2.0-5 has caused the Debian Bug report #1058108, regarding pokrok: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?