close 1058426 src:ruby-rugged/1.7.1+ds-1
thanks
This has been fixed with the upload of ruby-rugged 1.7.1+ds-1.
Processing commands for cont...@bugs.debian.org:
> found 1059054 2:3.94-1
Bug #1059054 {Done: Mike Hommey } [src:nss] nss:
CVE-2023-6135
Marked as found in versions nss/2:3.94-1.
> tags 1059054 + upstream
Bug #1059054 {Done: Mike Hommey } [src:nss] nss:
CVE-2023-6135
Added tag(s) upstream.
>
Hi Santiago and Lucas,
You have filed bug reports against octave-netcdf (Bug#1057590) and
octave-ncarray (Bug#1057589 and Bug#1058281). These packages FTBFS due to
an issue in the netcdf package (Bug#1058281), which has been fixed
thanks to the recent upload of version 4.9.2-3.
Would it be
Please ignore the part of the bug report claiming that the deb file
hosted in the experimental repository was corrupted. That was due to an
ftp error on my side. The remainder of the bug report, and its severity
level, remain.
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595
Package: whizzytex
Version: 1.3.7-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: boruch_b...@gmx.com
Dear Maintainer,
1) The apt-get install process for whizzytex v1.3.7 {bookworm,trixie}
occurs without incident, but the package is unusable.
2) The developer website
Your message dated Wed, 20 Dec 2023 03:20:03 +
with message-id
and subject line Bug#135: fixed in ezquake 3.6.4-1
has caused the Debian Bug report #135,
regarding ezquake: depends on obsolete pcre3 library
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 19 Dec 2023 21:51:13 -0500
with message-id
and subject line fixed
has caused the Debian Bug report #1055002,
regarding shaarli: FTBFS: dh_auto_test: error: make -j8 test returned exit code
2
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 20 Dec 2023 11:43:11 +0900
with message-id <20231220024311.tqemujh2fyw7a...@glandium.org>
and subject line Re: Bug#1059054: nss: CVE-2023-6135
has caused the Debian Bug report #1059054,
regarding nss: CVE-2023-6135
to be marked as done.
This means that you claim that the
Here is the patch.
It's just about hacking out the referencesto python3-future.
Greetings
python-lzstring $ git diff
diff --git a/debian/control b/debian/control
index 727100d..1d1d4aa 100644
--- a/debian/control
+++ b/debian/control
@@ -8,7 +8,6 @@ Build-Depends: debhelper-compat (= 13),
On Mon, 18 Dec 2023 at 18:31, Sudip Mukherjee
wrote:
> > However I haven't so far worked out why the man3 sections are being
> > included in the main package installer.
> > (the commands in man3 are only of interest to developers)
>
> From
>
Processing commands for cont...@bugs.debian.org:
> notfixed 1057405 2.18+ds-1
Bug #1057405 {Done: Bo YU } [src:nauty] pynormaliz ftbfs
with Python 3.12
Bug #1057412 {Done: Bo YU } [src:nauty] pynormaliz: FTBFS
in testing and unstable
The source 'nauty' and version '2.18+ds-1' do not appear to
Processing control commands:
> fixed -1 2.8.8+ds-2~exp1
Bug #1057405 {Done: Bo YU } [src:nauty] pynormaliz ftbfs
with Python 3.12
Bug #1057412 {Done: Bo YU } [src:nauty] pynormaliz: FTBFS
in testing and unstable
Marked as fixed in versions nauty/2.8.8+ds-2~exp1.
Marked as fixed in versions
Control: fixed -1 2.8.8+ds-2~exp1
On Wed 20 Dec 2023 12:33:04 AM GMT, "Debian Bug Tracking System"
wrote:
Processing control commands:
fixed -1 2.88+ds-2~exp1
Bug #1057405 {Done: Bo YU } [src:nauty] pynormaliz
ftbfs with Python 3.12
Bug #1057412 {Done: Bo YU } [src:nauty]
pynormaliz: FTBFS
Processing control commands:
> fixed -1 2.88+ds-2~exp1
Bug #1057405 {Done: Bo YU } [src:nauty] pynormaliz ftbfs
with Python 3.12
Bug #1057412 {Done: Bo YU } [src:nauty] pynormaliz: FTBFS
in testing and unstable
The source 'nauty' and version '2.88+ds-2~exp1' do not appear to match any
binary
Control: fixed -1 2.88+ds-2~exp1
nauty's reversed dependencies are still marked as AUTORM because of this
bug, possibly because it is marked as fixed in a pynormaliz version which
islower than the nauty version?
I'm updating the "fixed" version to 2.8.8+ds-2~exp1, which just entered
Source: gpac
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerabilities were published for gpac.
CVE-2023-48958[0]:
| gpac 2.3-DEV-rev617-g671976fcc-master contains memory leaks in
| gf_mpd_resolve_url media_tools/mpd.c:4589.
Source: nss
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerability was published for nss.
CVE-2023-6135[0]:
| Multiple NSS NIST curves were susceptible to a side-channel attack
| known as "Minerva". This attack could potentially allow an attacker
|
Your message dated Tue, 19 Dec 2023 22:09:51 +0100
with message-id
and subject line Re: Bug#1058921: ceph: loss of ceph-volume@.service
has caused the Debian Bug report #1058921,
regarding ceph: loss of ceph-volume@.service
to be marked as done.
This means that you claim that the problem has
On Mon, 4 Dec 2023 02:26:37 +0100 Alexandre Detiste
wrote:
I've import 3.6.4 on Salsa
It does not build. Please fix it:
dh binary
dh_update_autotools_config
dh_autoreconf
create-stamp debian/debhelper-build-stamp
dh_prep
rm -f -- debian/ezquake.substvars
rm -fr
Your message dated Tue, 19 Dec 2023 20:34:24 +
with message-id
and subject line Bug#1057728: fixed in binutils-mingw-w64 11.2
has caused the Debian Bug report #1057728,
regarding binutils-mingw-w64 FTBFS: test failures
to be marked as done.
This means that you claim that the problem has been
Impossible to install: Depends on missing package
librust-ego-tree-0.6+default-dev
rust-ego-tree was uploaded but rejected.
https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2023-December/037170.html
Quoting Peter Green (2023-12-19 20:46:56)
> tags 105121 +patch
> thanks
>
> > rust-palette is unable to migrate to Testing because its
> > autopkgtests are failing.
>
> I prepared a fix for the autopkgtest issues. While I was at
> it I also bumped the clap dev-dependency and the associated
>
tags 105121 +patch
thanks
rust-palette is unable to migrate to Testing because its
autopkgtests are failing.
I prepared a fix for the autopkgtest issues. While I was at
it I also bumped the clap dev-dependency and the associated
build and test dependencies to version 4 as we would like
to
Package: munge
Version: 0.5.15-3
Severity: serious
Tags: patch
Hello, if libsystemd-dev is installed (or something similar, didn't dig too
much into this), the package FTBFS due to service file not being installed from
debian/tmp
checking for systemdunitdir... ${prefix}/lib/systemd/system
Am Tue, Dec 19, 2023 at 08:03:56PM +0100 schrieb Rene Engelhard:
> LibreOffice builds (patch available), but doesn't yet build with 2.12.
"... but doesn't yet succeed the tests with 2.12"
> S=/home/rene/LibreOffice/git/libreoffice-24-2 && I=$S/instdir && W=$S/workdir
> && /usr/bin/ccache
Package: libxml2
Version: 2.12.3+dfsg-0exp1
Severity: serious
Dear Maintainer,
Hi,
LibreOffice builds (patch available), but doesn't yet build with 2.12.
But that is not the point of this issue.
While test building current 24.2 snapshot which will become 24.2 rc1
later this week I get
[build
Your message dated Tue, 19 Dec 2023 19:05:31 +
with message-id
and subject line Bug#1058398: fixed in ros-rosdep 0.22.2-3
has caused the Debian Bug report #1058398,
regarding ros-rosdep: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.12 3.11" returned exit
Processing control commands:
> tags -1 - bookworm bullseye
Bug #925657 [src:condor] condor: ftbfs with GCC-9
Removed tag(s) bookworm and bullseye.
> tags 936323 - bookworm bullseye
Bug #936323 [src:condor] condor: Python2 removal in sid/bullseye
Removed tag(s) bullseye and bookworm.
> tags 966726
Control: tags -1 - bookworm bullseye
Control: tags 936323 - bookworm bullseye
Control: tags 966726 - bookworm bullseye
The package was not released with bookworm or bullseye.
Your message dated Tue, 19 Dec 2023 17:49:28 +
with message-id
and subject line Bug#1059033: fixed in asterisk 1:20.5.1~dfsg+~cs6.13.40431414-1
has caused the Debian Bug report #1059033,
regarding asterisk: CVE-2023-49786
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 19 Dec 2023 16:51:46 +
with message-id
and subject line Bug#1058411: fixed in python-pykmip 0.10.0-6
has caused the Debian Bug report #1058411,
regarding python-pykmip: FTBFS: AttributeError: does not have the attribute 'wrap_socket'
to be marked as done.
This means
Processing control commands:
> tag -1 pending
Bug #1058411 [src:python-pykmip] python-pykmip: FTBFS: AttributeError: does not have the attribute
'wrap_socket'
Added tag(s) pending.
--
1058411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058411
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #1058411 in python-pykmip reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Your message dated Tue, 19 Dec 2023 17:32:36 +0100
with message-id <170300355607.5338.10750264136065412...@auryn.jones.dk>
and subject line Re: Bug#1036697: asterisk: CVE-2023-27585
has caused the Debian Bug report #1036697,
regarding asterisk: CVE-2023-27585
to be marked as done.
This means that
There is a newer image in backports, I installed version:
# apt list --installed | grep linux-image.*back
linux-image-6.5.0-0.deb12.4-amd64/stable-backports,now 6.5.10-1~bpo12+1
amd64 [installed]
After reboot version changed:
# uname -a
Linux P7730 6.5.0-0.deb12.4-amd64 #1 SMP PREEMPT_DYNAMIC
Your message dated Tue, 19 Dec 2023 17:29:01 +0100
with message-id <170300334140.5338.8172443677664721...@auryn.jones.dk>
and subject line Re: Bug#1032092: asterisk: CVE-2022-23537 CVE-2022-23547
CVE-2022-39269
has caused the Debian Bug report #1032092,
regarding asterisk: CVE-2022-23537
Processing control commands:
> tag -1 pending
Bug #1058269 [src:python-pylxd] python-pylxd: FTBFS: failed tests
Added tag(s) pending.
--
1058269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1058269 in python-pylxd 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:
Package: debian-live
Severity: grave
X-Debbugs-Cc: jsb...@mimuw.edu.pl
Trying to boot Debian Live 12.4.0 amd 64 Gnome I get the black screen
with a large cursor.
Some info about the computer:
ASRock B360M-ITX/AC
Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz 3.19 GHz
Actually the installed
Source: mdevctl
Version: 1.2.0-5
Severity: serious
Tags: ftbfs
mdevctl fails to build from source when building with the nocheck build
profile. Since trixie, such a failure is considered release critical by
the release team. A build log ends as follows:
|dh_auto_install
Processing commands for cont...@bugs.debian.org:
> forwarded 1059031 https://github.com/qbittorrent/qBittorrent/issues/20149
Bug #1059031 [qbittorrent] qbittorrent: Crash when starting download with new
torrent
Set Bug forwarded-to-address to
On 19 déc. 2023 10:12, Boyuan Yang wrote:
> Package: qbittorrent
> Version: 4.6.2-1
> Severity: grave
> X-Debbugs-CC: maril...@debian.org
>
> Dear Debian qbittorrent maintainers,
>
> Current qbittorrent in Debian Sid will crash when a new download task is
> initiated and started with a torrent
Package: librust-scraper-dev
Version: 0.18.1-1
Severity: grave
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Impossible to install: Depends on missing package
librust-ego-tree-0.6+default-dev
-BEGIN PGP SIGNATURE-
Source: asterisk
Version: 1:20.5.0~dfsg+~cs6.13.40431414-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for asterisk.
CVE-2023-49786[0]:
| Asterisk is an open source private branch exchange and
Package: qbittorrent
Version: 4.6.2-1
Severity: grave
X-Debbugs-CC: maril...@debian.org
Dear Debian qbittorrent maintainers,
Current qbittorrent in Debian Sid will crash when a new download task is
initiated and started with a torrent file.
Steps to reproduce:
(1) Open an arbitrary torrent
Processing commands for cont...@bugs.debian.org:
> # bts housekeeping
> tags 1031024 + sid trixie
Bug #1031024 {Done: Matthias Geiger }
[src:trompeloeil-cpp] trompeloeil-cpp: FTBFS (The value requires a
positive integer argument.)
Added tag(s) sid and trixie.
> reopen 1010421
Bug #1010421
Hi Helmut
On 12/19/23 15:13, Helmut Grohne wrote:
Based on the work on molly-guard, I'm ataching an updated patch and it
really is a copy of the one on bfh-container #1055509, so see there for
the why its done the way its done.
great, thanks!
I'll test it tomorrow and upload.
Regards,
Daniel
On Wed, Nov 08, 2023 at 08:07:29PM +0100, Helmut Grohne wrote:
> I'm proposing the attached patch to implement DEP17 mitigation M18. I
> caution that the patch is untested, because piuparts failed for
> unrelated reasons. open-infrastructure-compute-tools.postinst and
> sudo.prerm fail inside
Processing control commands:
> tags -1 + patch
Bug #1055511 [progress-linux-container] progress-linux-container: diversions
need to be updated to deal with DEP17 P3
Added tag(s) patch.
--
1055511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055511
Debian Bug Tracking System
Contact
Control: tags -1 + patch
On Wed, Nov 08, 2023 at 08:45:55PM +0100, Helmut Grohne wrote:
> I'm attaching a patch. I don't have high confidence, because it fails
> piuparts with left-over files. Given the mess in piuparts, I have no
> intentions to further test this. You may use the patch as a
Source: elogind
Version: 252.9-1debian2
Severity: serious
Tags: ftbfs trixie sid
elogind fails to build from source with the nocheck build profile. Note
that since trixie such a failure is considered release critical by the
release team. The relevant part of the build log is:
| Found pkg-config:
Source: libfprint
Version: 1:1.94.6-2
Severity: serious
Tags: ftbfs
libfprint fails to build from source when built with the nocheck build
profile. Note that this is considered a release critical bug since
trixie by the release team. Here is the relevant part of the build log:
| Program
Processing control commands:
> severity -1 important
Bug #1058991 [firmware-misc-nonfree] firmware-misc-nonfree: Possible missing
firmware for module nouveau, kernel crash in nouveau
Severity set to 'important' from 'grave'
> tag -1 moreinfo
Bug #1058991 [firmware-misc-nonfree]
Control: severity -1 important
Control: tag -1 moreinfo
On Tuesday, 19 December 2023 13:57:51 CET Vincent Lefevre wrote:
> Another piece of information: this is a regression.
>
> With the 6.1.0-16-amd64 kernel from stable, "journalctl -b -g ga107"
> gives
>
> Dec 19 04:57:07 qaa kernel: nouveau
Another piece of information: this is a regression.
With the 6.1.0-16-amd64 kernel from stable, "journalctl -b -g ga107"
gives
Dec 19 04:57:07 qaa kernel: nouveau :01:00.0: NVIDIA GA107 (b77000a1)
Dec 19 04:57:07 qaa kernel: nouveau :01:00.0: firmware: failed to load
Your message dated Tue, 19 Dec 2023 12:52:20 +
with message-id
and subject line Bug#54: fixed in squeak-vm 1:4.10.2.2614+20120917~dfsg-2
has caused the Debian Bug report #54,
regarding squeak-vm: depends on obsolete pcre3 library
to be marked as done.
This means that you claim that
On 2023-12-19 04:32:02 +0100, Vincent Lefevre wrote:
> firmware-misc-nonfree triggers the following warnings:
>
> update-initramfs: Generating /boot/initrd.img-6.5.0-5-amd64
[...]
> W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_ahesasc.bin
> for module nouveau
[...]
> while
Your message dated Tue, 19 Dec 2023 12:12:49 +
with message-id
and subject line Bug#1058429: fixed in textdistance 4.6.0-1
has caused the Debian Bug report #1058429,
regarding textdistance: FTBFS: FAILED
tests/test_external.py::test_list_of_numbers[Hamming] - RuntimeError: ...
to be marked
Empty Message
Your message dated Tue, 19 Dec 2023 12:07:44 +
with message-id
and subject line Bug#1057058: fixed in liquidsoap 2.2.2-2
has caused the Debian Bug report #1057058,
regarding liquidsoap-doc: missing Breaks+Replaces: liquidsoap (<< 2.2.2)
to be marked as done.
This means that you claim that
Your message dated Tue, 19 Dec 2023 12:08:13 +
with message-id
and subject line Bug#1057921: fixed in offlineimap3
0.0~git20231218.d29a4dc+dfsg-1
has caused the Debian Bug report #1057921,
regarding offlineimap: NameError: name 'fcntl' is not defined
to be marked as done.
This means that
Hi again, Yavor,
Quoting Yavor Doganov (2023-12-19 12:35:06)
> Jonas Smedegaard wrote:
> > Quoting Yavor Doganov (2023-12-19 11:21:34)
> > > Please find attached a patch;
> >
> > Is it a patch that you composed yourself, or did you work based off
> > of some upstream changeset.
>
> The former.
Hi Tobias,
Quoting Tobias Pape (2023-12-19 12:02:56)
> > On 19. Dec 2023, at 11:53, Jonas Smedegaard wrote:
> > Quoting Yavor Doganov (2023-12-19 11:21:34)
> >> Please find attached a patch; unfortunately I could not find a way
> >> to test it.
> >
> > Thanks for the patch.
> >
> > Is it a
Hi,
On Tue, Dec 19, 2023 at 12:41:24PM +0100, Friedhelm Mehnert wrote:
> This is to report, that even with this kernel,
>
> > 2023-12-19T11:19:09.704363+01:00 m2 kernel: [0.00]
> > Linux version 6.1.0-16-amd64 (debian-kern
> > e...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0,
>
This is to report, that even with this kernel,
> 2023-12-19T11:19:09.704363+01:00 m2 kernel: [0.00]
> Linux version 6.1.0-16-amd64 (debian-kern
> e...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0,
> GNU ld (GNU Binutils for Debian) 2.40) #1 SMP
> PREEMPT_DYNAMIC Debian 6.1.67-1
Source: lomiri
Version: 0.1.3-1
Severity: serious
Tags: ftbfs
lomiri fails to build from source in unstable on amd64. A non-parallel
build ends as follows:
| make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
| [ 29%] Building CXX object
Your message dated Tue, 19 Dec 2023 11:42:40 +
with message-id
and subject line Bug#1058274: fixed in wcslib 8.2.2+ds-1
has caused the Debian Bug report #1058274,
regarding wcslib: FTBFS: ld: final link failed: bad value
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> tag -1 pending
Bug #1058429 [src:textdistance] textdistance: FTBFS: FAILED
tests/test_external.py::test_list_of_numbers[Hamming] - RuntimeError: ...
Added tag(s) pending.
--
1058429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058429
Debian Bug Tracking
Control: tag -1 pending
Hello,
Bug #1058429 in textdistance reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Your message dated Tue, 19 Dec 2023 11:39:30 +
with message-id
and subject line Bug#1058751: fixed in r-cran-rcppparallel 5.1.7+dfsg-2
has caused the Debian Bug report #1058751,
regarding r-cran-rcppparallel: broken symlinks:
/usr/lib/R/site-library/RcppParallel/lib/libtbb*.so.*.8 ->
Jonas Smedegaard wrote:
> Quoting Yavor Doganov (2023-12-19 11:21:34)
> > Please find attached a patch;
>
> Is it a patch that you composed yourself, or did you work based off of
> some upstream changeset.
The former. I checked the new upstream release (downloaded with
uscan) and also checked
Processing control commands:
> tag -1 pending
Bug #1057058 [liquidsoap-doc] liquidsoap-doc: missing Breaks+Replaces:
liquidsoap (<< 2.2.2)
Added tag(s) pending.
--
1057058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 pending
Hello,
Bug #1057058 in liquidsoap 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:
Hi
> On 19. Dec 2023, at 11:53, Jonas Smedegaard wrote:
>
> Hi Yavor,
>
> Quoting Yavor Doganov (2023-12-19 11:21:34)
>> Please find attached a patch; unfortunately I could not find a way to
>> test it.
>
> Thanks for the patch.
>
> Is it a patch that you composed yourself, or did you work
Hi Yavor,
Quoting Yavor Doganov (2023-12-19 11:21:34)
> Please find attached a patch; unfortunately I could not find a way to
> test it.
Thanks for the patch.
Is it a patch that you composed yourself, or did you work based off of
some upstream changeset.
I ask because it is helpful to know how
Processing control commands:
> tag -1 pending
Bug #1058303 [src:sphinx] sphinx: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) pending.
--
1058303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058303
Debian
Control: tag -1 pending
Hello,
Bug #1058303 in sphinx reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tags -1 + patch
Please find attached a patch; unfortunately I could not find a way to
test it.
Description: Port to PCRE2.
Bug-Debian: https://bugs.debian.org/54
Author: Yavor Doganov
Forwarded: no
Last-Update: 2023-12-19
---
--- squeak-vm.orig/platforms/unix/CMakeLists.txt
+++
Processing control commands:
> tags -1 + patch
Bug #54 [src:squeak-vm] squeak-vm: depends on obsolete pcre3 library
Added tag(s) patch.
--
54: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=54
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: hime
Version: 0.9.11+dfsg-2
Severity: serious
Tags: trixie, sid
Justification: rc-policy - packages must be buildable within the same release.
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Hime build-depends on libayatana-indicator-dev which is no longer built
by the
Your message dated Tue, 19 Dec 2023 08:40:55 +
with message-id
and subject line Bug#1057728: fixed in binutils-mingw-w64 11.1
has caused the Debian Bug report #1057728,
regarding binutils-mingw-w64 FTBFS: test failures
to be marked as done.
This means that you claim that the problem has been
Control: tags -1 + patch
https://github.com/cfengine/core/pull/5391
OpenPGP_signature.asc
Description: OpenPGP digital signature
Processing control commands:
> tags -1 + patch
Bug #161 [src:cfengine3] cfengine3: depends on obsolete pcre3 library
Added tag(s) patch.
--
161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=161
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
83 matches
Mail list logo
