Hi Santiago,
On Mon, 2 Sep 2024 19:35:50 +0200 Santiago Vila wrote:
> Note: It is possible and likely that the reason it fails for me
> is different than the reason in the original report,
> i.e. java.io.IOException: Mount point not found.
>
> For simplicity I decided to raise this one because i
Package: libpam-ssh
Version: 2.3+ds-7
Severity: serious
Justification: introduces aliased files
File: /lib/x86_64-linux-gnu/security/pam_ssh.so
X-Debbugs-Cc: z...@debian.org
Hi Jerome,
your 2.3+ds-7 upload reverts Chris earlier NMU 2.3+ds-6.1. That NMU
moved the module from /lib to /usr/lib in or
Your message dated Wed, 04 Sep 2024 04:40:49 +
with message-id
and subject line Bug#1080050: Removed package(s) from unstable
has caused the Debian Bug report #999554,
regarding mbdyn: FTBFS: ISO C++17 does not allow dynamic exception
specifications
to be marked as done.
This means that you
Your message dated Wed, 04 Sep 2024 04:43:51 +
with message-id
and subject line Bug#1080310: Removed package(s) from unstable
has caused the Debian Bug report #1078015,
regarding gnome-shell-mailnag: works poorly
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 04 Sep 2024 04:41:46 +
with message-id
and subject line Bug#1080080: Removed package(s) from unstable
has caused the Debian Bug report #997106,
regarding aiorwlock: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.9 returned exit code 13
to be marked
Your message dated Wed, 04 Sep 2024 04:41:18 +
with message-id
and subject line Bug#1080052: Removed package(s) from unstable
has caused the Debian Bug report #1005940,
regarding node-lockfile: Abandoned upstream
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 04 Sep 2024 04:39:07 +
with message-id
and subject line Bug#1079993: Removed package(s) from unstable
has caused the Debian Bug report #914801,
regarding evqueue-core: modifies conffiles (policy 10.7.3): /etc/evqueue.conf
to be marked as done.
This means that you claim
Your message dated Wed, 04 Sep 2024 04:40:08 +
with message-id
and subject line Bug#107: Removed package(s) from unstable
has caused the Debian Bug report #1067940,
regarding FTBFS: error: implicit declaration of function
‘mono_profiler_install’; did you mean ‘mono_profiler_startup’?
to b
Your message dated Wed, 04 Sep 2024 04:39:07 +
with message-id
and subject line Bug#1079993: Removed package(s) from unstable
has caused the Debian Bug report #1079773,
regarding Should evqueue-core be removed from unstable?
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 04 Sep 2024 04:40:08 +
with message-id
and subject line Bug#107: Removed package(s) from unstable
has caused the Debian Bug report #1068135,
regarding gtk-sharp3: arch:all package depends on pre-t64 library
to be marked as done.
This means that you claim that the p
Your message dated Wed, 04 Sep 2024 04:40:08 +
with message-id
and subject line Bug#107: Removed package(s) from unstable
has caused the Debian Bug report #1017897,
regarding Ships autogenerated files that can't be renegerated with the code in
Debian main
to be marked as done.
This means
Your message dated Wed, 04 Sep 2024 04:39:07 +
with message-id
and subject line Bug#1079993: Removed package(s) from unstable
has caused the Debian Bug report #187,
regarding evqueue-core: depends on obsolete pcre3 library
to be marked as done.
This means that you claim that the problem h
Your message dated Wed, 04 Sep 2024 04:36:58 +
with message-id
and subject line Bug#1079990: Removed package(s) from unstable
has caused the Debian Bug report #944499,
regarding FTBFS: IndexError: list index out of range
to be marked as done.
This means that you claim that the problem has bee
Your message dated Wed, 04 Sep 2024 04:37:27 +
with message-id
and subject line Bug#1079991: Removed package(s) from unstable
has caused the Debian Bug report #944542,
regarding aws-shell: prompt_toolkit 3.x support
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Wed, 04 Sep 2024 04:36:30 +
with message-id
and subject line Bug#1079988: Removed package(s) from unstable
has caused the Debian Bug report #897707,
regarding arrayfire: ftbfs with GCC-8
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Wed, 04 Sep 2024 04:36:30 +
with message-id
and subject line Bug#1079988: Removed package(s) from unstable
has caused the Debian Bug report #892288,
regarding arrayfire FTBFS on i386: test segfaults
to be marked as done.
This means that you claim that the problem has been d
Your message dated Wed, 04 Sep 2024 04:36:30 +
with message-id
and subject line Bug#1079988: Removed package(s) from unstable
has caused the Debian Bug report #1061920,
regarding arrayfire: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 04 Sep 2024 04:37:27 +
with message-id
and subject line Bug#1079991: Removed package(s) from unstable
has caused the Debian Bug report #1050402,
regarding aws-shell: build-depends on obsolete version of awscli
to be marked as done.
This means that you claim that the pr
Your message dated Wed, 04 Sep 2024 04:35:18 +
with message-id
and subject line Bug#1079968: Removed package(s) from unstable
has caused the Debian Bug report #985522,
regarding zeek-aux: broken symlink: /usr/bin/bro-cut -> zeek-wrapper
to be marked as done.
This means that you claim that the
Your message dated Wed, 04 Sep 2024 04:33:49 +
with message-id
and subject line Bug#1079940: Removed package(s) from unstable
has caused the Debian Bug report #1079916,
regarding unarr: Keep the package out of trixie
to be marked as done.
This means that you claim that the problem has been de
Your message dated Wed, 04 Sep 2024 04:34:51 +
with message-id
and subject line Bug#1079959: Removed package(s) from unstable
has caused the Debian Bug report #1017747,
regarding imdbpy: autopkgtest regression: KeyError: 'top 1000 voters'
to be marked as done.
This means that you claim that t
Your message dated Wed, 04 Sep 2024 04:31:46 +
with message-id
and subject line Bug#1079905: Removed package(s) from unstable
has caused the Debian Bug report #978012,
regarding xsddiagram: No diagram is shown
to be marked as done.
This means that you claim that the problem has been dealt wit
Your message dated Wed, 04 Sep 2024 04:31:13 +
with message-id
and subject line Bug#1079901: Removed package(s) from unstable
has caused the Debian Bug report #1079901,
regarding RM: libwcat1 -- RoQA; dead upstream, obsolete
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 04 Sep 2024 04:30:43 +
with message-id
and subject line Bug#1079900: Removed package(s) from unstable
has caused the Debian Bug report #1079900,
regarding RM: libapache2-mod-watchcat -- RoQA; dead upstream, obsolete
to be marked as done.
This means that you claim that
Your message dated Wed, 04 Sep 2024 04:30:46 +
with message-id
and subject line Bug#1079900: Removed package(s) from unstable
has caused the Debian Bug report #1078461,
regarding libapache2-mod-watchcat: depends on to be removed watchcatd
to be marked as done.
This means that you claim that t
Your message dated Wed, 04 Sep 2024 04:30:13 +
with message-id
and subject line Bug#1079899: Removed package(s) from unstable
has caused the Debian Bug report #1052886,
regarding boogie: FTBFS:BigDecTests.cs(2,7): error CS0246: The type or
namespace name `NUnit' could not be found. Ar
Your message dated Wed, 04 Sep 2024 04:24:16 +
with message-id
and subject line Bug#1079841: Removed package(s) from unstable
has caused the Debian Bug report #987819,
regarding mate-optimus: Program is broken on Debian as prime-select doesn't
exist
to be marked as done.
This means that you
Your message dated Wed, 04 Sep 2024 04:24:54 +
with message-id
and subject line Bug#1079845: Removed package(s) from unstable
has caused the Debian Bug report #953226,
regarding vagrant-bindfs: autopkgtest failure: cannot load such file --
/tmp/<...>/src/spec/vagrantfile_helper
to be marked a
Your message dated Wed, 04 Sep 2024 04:26:19 +
with message-id
and subject line Bug#1079879: Removed package(s) from unstable
has caused the Debian Bug report #1070859,
regarding npgsql: CVE-2024-32655
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Your message dated Wed, 04 Sep 2024 04:17:06 +
with message-id
and subject line Bug#1079770: Removed package(s) from unstable
has caused the Debian Bug report #820091,
regarding Switch from php-mongo to php-mongodb is needed
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 04 Sep 2024 04:18:18 +
with message-id
and subject line Bug#1079816: Removed package(s) from unstable
has caused the Debian Bug report #1074813,
regarding antennavis: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Wed, 04 Sep 2024 04:10:48 +
with message-id
and subject line Bug#1079690: Removed package(s) from unstable
has caused the Debian Bug report #907974,
regarding perl-doc-html: Should be updated to 5.28 at the point of the
transition
to be marked as done.
This means that you
Your message dated Wed, 04 Sep 2024 04:12:07 +
with message-id
and subject line Bug#1079694: Removed package(s) from unstable
has caused the Debian Bug report #923330,
regarding jajuk: Fails to start with Java Runtime Environment 1.7 minimum
required. You use a JVM ext.JVM@23fc625e
to be mark
Your message dated Wed, 04 Sep 2024 04:12:40 +
with message-id
and subject line Bug#1079695: Removed package(s) from unstable
has caused the Debian Bug report #919037,
regarding xmms2-scrobbler: Non-working maintainer address
to be marked as done.
This means that you claim that the problem ha
Your message dated Wed, 04 Sep 2024 04:12:40 +
with message-id
and subject line Bug#1079695: Removed package(s) from unstable
has caused the Debian Bug report #798099,
regarding Do not work after last.fm made upgrades
to be marked as done.
This means that you claim that the problem has been d
Your message dated Wed, 04 Sep 2024 04:12:07 +
with message-id
and subject line Bug#1079694: Removed package(s) from unstable
has caused the Debian Bug report #1071796,
regarding jajuk: FTBFS:
src/main/java/org/jajuk/ui/helpers/PlaylistRepositoryTableModel.java:101:
error: is not
abstract
Your message dated Wed, 04 Sep 2024 04:06:02 +
with message-id
and subject line Bug#1076310: Removed package(s) from unstable
has caused the Debian Bug report #949603,
regarding boinc-app-eah-brp should not use the private binutils shared libraries
to be marked as done.
This means that you cl
Your message dated Wed, 04 Sep 2024 04:06:02 +
with message-id
and subject line Bug#1076310: Removed package(s) from unstable
has caused the Debian Bug report #887880,
regarding boinc-app-eah-brp: non-standard gcc/g++ used for build (gcc-5)
to be marked as done.
This means that you claim that
Your message dated Wed, 04 Sep 2024 04:06:02 +
with message-id
and subject line Bug#1076310: Removed package(s) from unstable
has caused the Debian Bug report #1079777,
regarding Should boinc-app-eah-brp be removed from unstable?
to be marked as done.
This means that you claim that the proble
Your message dated Tue, 03 Sep 2024 23:36:27 +
with message-id
and subject line Bug#1080421: fixed in qt6-declarative 6.7.2+dfsg-5
has caused the Debian Bug report #1080421,
regarding libqt6quickcontrols2-6 has an undeclared file conflict on
/usr/lib/x86_64-linux-gnu/libQt6QuickControls2Impl.
Your message dated Tue, 03 Sep 2024 23:22:14 +
with message-id
and subject line Bug#1080424: fixed in libpod 5.2.1+ds1-3
has caused the Debian Bug report #1080424,
regarding podman: /etc/profile.d/podman-docker.sh breaks docker, should not be
shipped in the podman binary package
to be marked
Your message dated Wed, 04 Sep 2024 00:37:12 +0200
with message-id
and subject line Close #1080197
has caused the Debian Bug report #1080197,
regarding med-fichier: autopkgtest regressions with mpich as default provider
on 32 bit architectures
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> found 988477 4.17.3+10-g091466ba55-1~deb12u1
Bug #988477 [src:xen] xen-hypervisor-4.14-amd64: xen dmesg shows (XEN) AMD-Vi:
IO_PAGE_FAULT on sata pci device
Marked as found in versions xen/4.17.3+10-g091466ba55-1~deb12u1.
> severity 988477 critic
Processing control commands:
> found -1 2.8.0-2
Bug #1064670 [src:nut] nut: flaky autopkgtest: Test daemons using PID files ...
FAIL
Marked as found in versions nut/2.8.0-2.
--
1064670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064670
Debian Bug Tracking System
Contact ow...@bugs.debia
Control: found -1 2.8.0-2
While I don't have the full logs, it seems the debci failures date back
at least to 2.8.0-2 on armel, so it's not a recent regression from what
I can see.
Thus updating the version information accordingly.
On Sun, 25 Feb 2024 20:38:41 +0100 Paul Gevers wrote:
Sour
Processing control commands:
> tag -1 pending
Bug #1080424 [podman] podman: /etc/profile.d/podman-docker.sh breaks docker,
should not be shipped in the podman binary package
Added tag(s) pending.
--
1080424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080424
Debian Bug Tracking System
Co
Control: tag -1 pending
Hello,
Bug #1080424 in libpod 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:
https://salsa.debian.org/debian/libpod/-/commit/fe0ce17dd1f040be77182f8b5a5c884c49d
Your message dated Tue, 03 Sep 2024 21:34:02 +
with message-id
and subject line Bug#1074830: fixed in autolog 0.42.1-2
has caused the Debian Bug report #1074830,
regarding autolog: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Tue, 03 Sep 2024 21:37:08 +
with message-id
and subject line Bug#1075353: fixed in osmo-iuh 1.6.0+dfsg1-2
has caused the Debian Bug report #1075353,
regarding osmo-iuh: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Processing control commands:
> tag -1 pending
Bug #1074830 {Done: Sven Geuer } [src:autolog] autolog: ftbfs
with GCC-14
Added tag(s) pending.
--
1074830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1074830 in autolog 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:
https://salsa.debian.org/pkg-security-team/autolog/-/commit/e8235d334df4d4f17a40ee
Your message dated Tue, 03 Sep 2024 21:21:56 +
with message-id
and subject line Bug#1071724: fixed in transmissionrpc 7.0.5-1
has caused the Debian Bug report #1071724,
regarding transmissionrpc: FTBFS: ModuleNotFoundError: No module named 'pytz'
to be marked as done.
This means that you clai
Your message dated Tue, 03 Sep 2024 21:19:01 +
with message-id
and subject line Bug#1080110: fixed in gmime 3.2.15+dfsg-1
has caused the Debian Bug report #1080110,
regarding gmime: FTBFS: error: operator '&&' has no right operand
to be marked as done.
This means that you claim that the probl
Processing commands for cont...@bugs.debian.org:
> fixed 1080197 4.1.0+repack-5
Bug #1080197 [src:med-fichier] med-fichier: autopkgtest regressions with mpich
as default provider on 32 bit architectures
Marked as fixed in versions med-fichier/4.1.0+repack-5.
> thanks
Stopping processing here.
Pl
Your message dated Tue, 03 Sep 2024 20:59:58 +
with message-id
and subject line Bug#1080396: fixed in python-pbcore 2.1.2+dfsg-8
has caused the Debian Bug report #1080396,
regarding python-pbcore: FTBFS: failing tests
to be marked as done.
This means that you claim that the problem has been d
Processing control commands:
> tag -1 pending
Bug #1069968 [src:ruby3.2] ruby3.2: CVE-2024-27282
Ignoring request to alter tags of bug #1069968 to the same tags previously set
--
1069968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069968
Debian Bug Tracking System
Contact ow...@bugs.debi
Control: tag -1 pending
Hello,
Bug #1069968 in ruby 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:
https://salsa.debian.org/ruby-team/ruby/-/commit/1d93af962602ed7c3156a6cc1db4fa71bf24
Processing control commands:
> tag -1 pending
Bug #1069968 [src:ruby3.2] ruby3.2: CVE-2024-27282
Added tag(s) pending.
--
1069968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069968
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tag -1 pending
Bug #1069968 [src:ruby3.2] ruby3.2: CVE-2024-27282
Ignoring request to alter tags of bug #1069968 to the same tags previously set
--
1069968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069968
Debian Bug Tracking System
Contact ow...@bugs.debi
Control: tag -1 pending
Hello,
Bug #1069968 in ruby 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:
https://salsa.debian.org/ruby-team/ruby/-/commit/2db7ceaec39b70069b7a4154e642e2d90db6
Control: tag -1 pending
Hello,
Bug #1069968 in ruby 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:
https://salsa.debian.org/ruby-team/ruby/-/commit/c507264176db4ef4680eb4c2517c912cb168
Processing control commands:
> tag -1 pending
Bug #1069968 [src:ruby3.2] ruby3.2: CVE-2024-27282
Ignoring request to alter tags of bug #1069968 to the same tags previously set
--
1069968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069968
Debian Bug Tracking System
Contact ow...@bugs.debi
Control: tag -1 pending
Hello,
Bug #1069966 in ruby 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:
https://salsa.debian.org/ruby-team/ruby/-/commit/1d93af962602ed7c3156a6cc1db4fa71bf24
Control: tag -1 pending
Hello,
Bug #1069968 in ruby 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:
https://salsa.debian.org/ruby-team/ruby/-/commit/2a4748cd80f9db3c66f9cc47c9adac0e5729
Processing control commands:
> tag -1 pending
Bug #1069966 [src:ruby3.1] ruby3.1: CVE-2024-27280: Buffer overread
vulnerability in StringIO
Ignoring request to alter tags of bug #1069966 to the same tags previously set
--
1069966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069966
Debian
Processing control commands:
> tag -1 pending
Bug #1069966 [src:ruby3.1] ruby3.1: CVE-2024-27280: Buffer overread
vulnerability in StringIO
Added tag(s) pending.
--
1069966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with p
Control: tag -1 pending
Hello,
Bug #1069966 in ruby 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:
https://salsa.debian.org/ruby-team/ruby/-/commit/2a4748cd80f9db3c66f9cc47c9adac0e5729
Hi.
You need the attached patch at least.
(Explanation: Because the string has a comma and the new
autoconf is more nitpicky about quoting, you need an extra "["
and "]" to quote the string).
(I know this by pure chance, because a similar problem was fixed
in another package).
Note that after
Hi Alex,
before reassigning the bug to autoconf, I wanted to check if my analysis _might_
be correct and to check how to fix it. Unfortunately I don't have much
experience with autoconf.
To me it seems, autoconf 2.72 produces an invalid ./configure for gstreamermm
while autoconf 2.71 produce
Processing control commands:
> tag -1 pending
Bug #1080396 [src:python-pbcore] python-pbcore: FTBFS: failing tests
Added tag(s) pending.
--
1080396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1080396 in python-pbcore 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:
https://salsa.debian.org/med-team/python-pbcore/-/commit/10b3d4aaa271148fd56
Your message dated Tue, 03 Sep 2024 19:49:02 +
with message-id
and subject line Bug#905417: fixed in ants 2.4.3+dfsg-1
has caused the Debian Bug report #905417,
regarding ants: broken symlink: /usr/bin/jointfusion -> ../lib/ants/jointfusion
to be marked as done.
This means that you claim that
Your message dated Tue, 03 Sep 2024 19:49:02 +
with message-id
and subject line Bug#909833: fixed in ants 2.4.3+dfsg-1
has caused the Debian Bug report #909833,
regarding ants FTBFS with gcc 8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Tue, 03 Sep 2024 19:49:02 +
with message-id
and subject line Bug#884710: fixed in ants 2.4.3+dfsg-1
has caused the Debian Bug report #884710,
regarding ants: FTBFS: URL using bad/illegal format or missing URL
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 03 Sep 2024 19:49:02 +
with message-id
and subject line Bug#872741: fixed in ants 2.4.3+dfsg-1
has caused the Debian Bug report #872741,
regarding ants: frequent test failures on amd64
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Tue, 03 Sep 2024 19:34:24 +
with message-id
and subject line Bug#1079745: fixed in guessit 3.8.0-3
has caused the Debian Bug report #1079745,
regarding setuptools test command is removed
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Processing commands for cont...@bugs.debian.org:
> found 1080424 5.2.1+ds1-2
Bug #1080424 [podman] podman: /etc/profile.d/podman-docker.sh breaks docker,
should not be shipped in the podman binary package
Marked as found in versions libpod/5.2.1+ds1-2.
> thanks
Stopping processing here.
Please c
Package: podman
Version: 5.2.2+ds1-1
Severity: critical
Justification: breaks unrelated software
/etc/profile.d/podman-docker.sh is currently shipped in the podman
binary. If one also has docker installed, the DOCKER_HOST variable set
there makes docker try to connect to the podman daemon which is
Control: tag -1 pending
Hello,
Bug #1079745 in guessit 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:
https://salsa.debian.org/python-team/packages/guessit/-/commit/4f141b3d9ddba6afb0f
Your message dated Tue, 03 Sep 2024 17:49:12 +
with message-id
and subject line Bug#1079928: fixed in gpgme1.0 1.23.2-2
has caused the Debian Bug report #1079928,
regarding gpgme1.0: FTFBFS with python3-setuptools 73.0.1-1
to be marked as done.
This means that you claim that the problem has b
Processing control commands:
> tag -1 pending
Bug #1079745 [src:guessit] setuptools test command is removed
Ignoring request to alter tags of bug #1079745 to the same tags previously set
--
1079745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079745
Debian Bug Tracking System
Contact ow..
Your message dated Tue, 03 Sep 2024 17:34:17 +
with message-id
and subject line Bug#1079928: fixed in gpgme1.0 1.18.0-6
has caused the Debian Bug report #1079928,
regarding gpgme1.0: FTFBFS with python3-setuptools 73.0.1-1
to be marked as done.
This means that you claim that the problem has b
Processing control commands:
> tag -1 pending
Bug #1079745 [src:guessit] setuptools test command is removed
Added tag(s) pending.
--
1079745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079745
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1079745 in guessit 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:
https://salsa.debian.org/python-team/packages/guessit/-/commit/39d74d55aaa990ab483
Your message dated Tue, 03 Sep 2024 17:02:57 +
with message-id
and subject line Bug#1080158: fixed in calamares-settings-debian
12.0.9-1+deb12u2
has caused the Debian Bug report #1080158,
regarding calamares writes wrong space_cache mount option in fstab during btrfs
install
to be marked as
Your message dated Tue, 03 Sep 2024 16:47:08 +
with message-id
and subject line Bug#1078883: fixed in diffoscope 240+deb12u1
has caused the Debian Bug report #1078883,
regarding diffoscope: FTBFS: failing tests
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Tue, 03 Sep 2024 16:36:15 +
with message-id
and subject line Bug#1077977: fixed in octave 9.2.0-3
has caused the Debian Bug report #1077977,
regarding JVM detection is incorrect on archs where the default is the "zero"
JVM
to be marked as done.
This means that you claim th
Hello,
I have faced the same issue dor several days.
It seems it due to the introduction of follow_pfn in kernel dev. (see
https://github.com/NVIDIA/open-gpu-kernel-modules/issues/642)
To solve it have applied the patches given by nvidia the 21 of July
here :
https://forums.developer.nvidia.com/t/
On Tue, Sep 03 2024, Colin Watson wrote:
> I had a brief look at this and noticed that this package was
> previously ported to pypdf, but that the port was reverted in
> https://salsa.debian.org/freexian-team/packages/odoo/-/commit/d68da30bd5746f41e33c19ba5c2b8bc0f100e4d6.
>
> CCing Sébastien - was
Control: tag -1 pending
Hello,
Bug #1077977 in octave 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:
https://salsa.debian.org/pkg-octave-team/octave/-/commit/9ebc88791743960d311c8b4901
Processing control commands:
> tag -1 pending
Bug #1077977 [octave] JVM detection is incorrect on archs where the default is
the "zero" JVM
Added tag(s) pending.
--
1077977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077977
Debian Bug Tracking System
Contact ow...@bugs.debian.org with p
On Fri, Mar 29, 2024 at 12:09:31PM -0400, Scott Kitterman wrote:
> On Sun, 21 Jan 2024 12:17:53 -0500 Scott Kitterman
> wrote:
> > I've recently adopted pypdf and pypdf2 into the Debian Python Team in
> > response to an RFA for both packages. As these are somewhat security
> > sensitive packag
Processing commands for cont...@bugs.debian.org:
> tags 1071119 + pending
Bug #1071119 [snapd] snapd: move files to /usr for DEP17
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1071119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071
Processing commands for cont...@bugs.debian.org:
> # Just confirmed the patch from the previous mail, so tagging accordingly.
> tags 1078408 + patch
Bug #1078408 [src:autofs] autofs: FTBFS: cyrus-sasl.c:112:25: error:
initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void
Hi Colin,
While working on this issue in parallel for Ubuntu, I noticed that
setup.py contains a "test_suite" argument that affects the build. I have
not noticed an actual issue due to that, only non-fatal errors in the
build log.
I've opened a PR upstream:
https://github.com/byllyfish/precis_i18
Your message dated Tue, 03 Sep 2024 15:07:33 +
with message-id
and subject line Bug#1080391: fixed in kakoune 2024.05.18-2
has caused the Debian Bug report #1080391,
regarding kakoune: FTBFS: dh_installalternatives: error: Alternative
"/usr/bin/kak" for "editor" in debian/kakoune.alternatives
Package: python3-sepolicy
Version: 3.7-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + policycoreutils-gui
python3-sepolicy has an undeclared file conflict. This may result in an
unpack error from dpkg.
The files
* /usr/lib/python3/dist-packages/
Package: libqt6quickcontrols2-6
Version: 6.7.2+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libqt6quickcontrols2impl6
libqt6quickcontrols2-6 has an undeclared file conflict. This may result
in an unpack error from dpkg.
The file /usr/lib/x
Processing control commands:
> affects -1 + libqt6quickcontrols2impl6
Bug #1080421 [libqt6quickcontrols2-6] libqt6quickcontrols2-6 has an undeclared
file conflict on /usr/lib/x86_64-linux-gnu/libQt6QuickControls2Impl.so.6
Added indication that 1080421 affects libqt6quickcontrols2impl6
--
108042
Processing control commands:
> affects -1 + policycoreutils-gui
Bug #1080420 [python3-sepolicy] python3-sepolicy has an undeclared file conflict
Added indication that 1080420 affects policycoreutils-gui
--
1080420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080420
Debian Bug Tracking Sys
1 - 100 of 149 matches
Mail list logo
