Your message dated Fri, 22 Oct 2021 06:03:55 +
with message-id
and subject line Bug#984375: fixed in uhd 3.15.0.0-5
has caused the Debian Bug report #984375,
regarding uhd: 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 t
Your message dated Fri, 22 Oct 2021 06:03:55 +
with message-id
and subject line Bug#984375: fixed in uhd 3.15.0.0-5
has caused the Debian Bug report #984375,
regarding gnss-sdr: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Fri, 22 Oct 2021 06:03:55 +
with message-id
and subject line Bug#984157: fixed in uhd 3.15.0.0-5
has caused the Debian Bug report #984157,
regarding uhd: 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 t
Your message dated Fri, 22 Oct 2021 06:03:55 +
with message-id
and subject line Bug#984157: fixed in uhd 3.15.0.0-5
has caused the Debian Bug report #984157,
regarding gnss-sdr: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing commands for cont...@bugs.debian.org:
> fixed 984246 1:2.2.0-2
Bug #984246 {Done: José Luis Blanco Claraco }
[src:mrpt] mrpt: ftbfs with GCC-11
Marked as fixed in versions mrpt/1:2.2.0-2.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
984246:
Hi Aaron,
Am Thu, Oct 21, 2021 at 04:21:26PM -0400 schrieb Aaron M. Ucko:
>
> No, because std::byte supports far too few operations [1]. Instead, I'd
> suggest encouraging upstream to rename their type, and meanwhile locally
> patching source/uchime_src/makefile to add -std=c++14 to CXXFLAGS,
>
Processing control commands:
> severity -1 serious
Bug #983254 [src:openorienteering-mapper] openorienteering-mapper: FTBFS with
PROJ 8.0.0
Severity set to 'serious' from 'important'
--
983254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983254
Debian Bug Tracking System
Contact ow...@bug
Processing control commands:
> severity -1 serious
Bug #983253 [src:ncl] ncl: FTBFS with PROJ 8.0.0
Severity set to 'serious' from 'important'
--
983253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> severity -1 serious
Bug #983236 [src:magics++] magics++: FTBFS with PROJ 8.0.0
Severity set to 'serious' from 'important'
--
983236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> severity -1 serious
Bug #983230 [src:xygrib] xygrib: FTBFS with PROJ 8.0.0
Severity set to 'serious' from 'important'
--
983230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> severity -1 serious
Bug #983224 [src:sosi2osm] sosi2osm: FTBFS with PROJ 8.0.0
Severity set to 'serious' from 'important'
--
983224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> severity -1 serious
Bug #983229 [src:survex] survex: FTBFS with PROJ 8.0.0
Severity set to 'serious' from 'important'
--
983229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Fri, 22 Oct 2021 02:33:47 +
with message-id
and subject line Bug#996241: fixed in glm 0.9.9.8+ds-2
has caused the Debian Bug report #996241,
regarding glm: FTBFS with GCC-11 (test-core_func_integer)
to be marked as done.
This means that you claim that the problem has been d
Your message dated Fri, 22 Oct 2021 01:03:38 +
with message-id
and subject line Bug#996517: fixed in ruby-tty-command 0.10.1-1
has caused the Debian Bug report #996517,
regarding ruby-tty-command: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
ArgumentError:
to be marked as done.
Th
The package libssh2 1.10.0-2 has successfully migrated to testing so I
believe this bug is fixed now
Your message dated Thu, 21 Oct 2021 22:35:54 +
with message-id
and subject line Bug#984290: fixed in pentobi 18.3-2
has caused the Debian Bug report #984290,
regarding pentobi: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Processing commands for cont...@bugs.debian.org:
> block 994910 with 984372
Bug #994910 [tripwire] tripwire segfaults while reading files in /etc
994910 was not blocked by any bugs.
994910 was not blocking any bugs.
Added blocking bug(s) of 994910: 984372
> thanks
Stopping processing here.
Please
Hi Andreas,
Andreas Tille, on 2021-10-21:
> In file included from addtargets2.cpp:3:
> myutils.h:176:1: error: reference to 'byte' is ambiguous
Since C++ 2017, the std::byte type is defined:
> 176 | byte *ReadAllStdioFile(FILE *f, off_t &FileSize);
> | ^~~~
> In file included from /usr/i
Your message dated Thu, 21 Oct 2021 22:04:45 +
with message-id
and subject line Bug#984177: fixed in holotz-castle 1.3.14-12
has caused the Debian Bug report #984177,
regarding holotz-castle: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt wit
Your message dated Thu, 21 Oct 2021 21:50:26 +
with message-id
and subject line Bug#984254: fixed in netpanzer 0.8.7+ds-4
has caused the Debian Bug report #984254,
regarding netpanzer: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Source: dolfinx
Version: 2019.2.0~git20210130.c14cb0a-5
Severity: serious
Tags: sid bookworm ftbfs
X-Debbugs-Cc: sramac...@debian.org
dolfinx build-depends on missing:
- python3-ffcx:amd64 (< 2019.3)
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
Control: tag -1 pending
Hello,
Bug #984254 in netpanzer 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/games-team/netpanzer/-/commit/5dec369542041e8349de4bd706
Source: pbdagcon
Version: 0.3+git20180411.c14c422+dfsg-3
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
pbdagcon is unable to migrate due to an autopkgtest regression:
/tmp/autopkgtest-lxc.d4k06k9b/downtmp/build.abl/src/debian/tests/run-unit-test:
line 18: rangen: command not found
See
htt
Processing control commands:
> tag -1 pending
Bug #984254 [src:netpanzer] netpanzer: ftbfs with GCC-11
Added tag(s) pending.
--
984254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Thu, 21 Oct 2021 21:35:52 +
with message-id
and subject line Bug#996722: fixed in python-volatile 2.1.0-4
has caused the Debian Bug report #996722,
regarding src:python-volatile: fails to migrate to testing for too long:
uploader built arch:all binaries
to be marked as done
Control: tag -1 pending
Hello,
Bug #947900 in chemical-mime-data 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/debichem-team/chemical-mime-data/-/commit/3b73e
Processing control commands:
> tag -1 pending
Bug #947900 [chemical-mime-data] chemical-mime-data: build-depends on
unmaintained gnome-mime-data
Ignoring request to alter tags of bug #947900 to the same tags previously set
--
947900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947900
Debi
Hi Paul
Paul Gevers writes:
> Hi Nicolas,
>
> Thanks you, but as I detect these issues in an automatic way without
> much manual labor, I don't need the credits :). And I uploaded to
> DELAYED exactly to give others the opportunity to fix it before me, so
> uploading to DELAYED in my opinion *al
Your message dated Thu, 21 Oct 2021 20:34:45 +
with message-id
and subject line Bug#984051: fixed in esys-particle 2.3.5+dfsg2-3
has caused the Debian Bug report #984051,
regarding esys-particle: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt
Steffen Möller writes:
> My C++ skills are a bit rosty but would removing the typedef for byte
> solve the problem?
No, because std::byte supports far too few operations [1]. Instead, I'd
suggest encouraging upstream to rename their type, and meanwhile locally
patching source/uchime_src/makefil
On 10/19/21 8:07 PM, Tianon Gravi wrote:
> Hey Rod, this is an interesting one -- looking at the definitions of
> the "EFI_DEVICE_PATH_UTILITIES_PROTOCOL" typedef in both refind's code
> and grub-efi's, they appear to be compatible to me (which makes sense,
> probably from the same original source?
Em 21/10/2021 16:30, Antonio Terceiro escreveu:
did you forget to push to git?
https://salsa.debian.org/ruby-team/ruby-ftw/-/commits/master does not
have any recent commits.
Sorry, yes, I forgot to git push the changes. Done now.
--
Lucas Kanashiro
On Wed, Oct 20, 2021 at 06:28:09PM -0300, Lucas Kanashiro wrote:
> I just uploaded version 0.0.44-2 to unstable and it built fine against both,
> ruby2.7 and ruby3.0. Build log attached.
did you forget to push to git?
https://salsa.debian.org/ruby-team/ruby-ftw/-/commits/master does not
have any r
Your message dated Thu, 21 Oct 2021 19:18:59 +
with message-id
and subject line Bug#984018: fixed in clonalorigin 1.0-6
has caused the Debian Bug report #984018,
regarding clonalorigin: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If
On 21.10.21 20:21, Étienne Mollier wrote:
Hi Andreas,
Andreas Tille, on 2021-10-21:
In file included from addtargets2.cpp:3:
myutils.h:176:1: error: reference to 'byte' is ambiguous
Since C++ 2017, the std::byte type is defined:
176 | byte *ReadAllStdioFile(FILE *f, off_t &FileSize);
Source: vtk6
Severity: serious
vtk has now 3 versions in archive: vtk6, vtk7 and vtk9.
Intention is to remove older unsupported versions in favour of cyrrent vtk9.
Your message dated Thu, 21 Oct 2021 18:48:41 +
with message-id
and subject line Bug#996956: fixed in benchmark 1.6.0-2
has caused the Debian Bug report #996956,
regarding libbenchmark-dev: libbenchmark_main.a has no actual object code
to be marked as done.
This means that you claim that the p
Package: mariadb-server
Followup-For: Bug #996028
Hi,
I've been brought to this bug by apt-listbugs while doing upgrades
on my buster install, warning me of a grave bug.
I have not attempted the upgrade yet, since, after reading this bug, I
see a risk of data corruption and I would like to avoid
Processing commands for cont...@bugs.debian.org:
> tags 996951 + upstream
Bug #996951 [src:linux] linux-image-5.14.0-3-amd64: iouring looses requests
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
996951: https://bugs.debian.org/cgi-bin/bug
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:python-django,
> src:django-ldapdb
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-b
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:transmission
> # 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.or
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:ptl
> # 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
Setting
Your message dated Thu, 21 Oct 2021 16:00:12 +
with message-id
and subject line Bug#984325: fixed in rocksdb 6.25.3-1
has caused the Debian Bug report #984325,
regarding rocksdb: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing commands for cont...@bugs.debian.org:
> unarchive 980292
Bug #980292 {Done: Kurt Kremitzki } [freecad] freecad:
starts with empty main window
Unarchived Bug 980292
> forcemerge 980292 976661
Bug #980292 {Done: Kurt Kremitzki } [freecad] freecad:
starts with empty main window
Bug #9766
Your message dated Thu, 21 Oct 2021 14:38:42 +
with message-id
and subject line Bug#996509: fixed in ruby-slop 4.9.1-1
has caused the Debian Bug report #996509,
regarding ruby-slop: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
ArgumentError: wrong number of arguments (given 2, expected 1
Processing control commands:
> tags -1 upstream
Bug #996541 [racon] racon: FTBFS when rebuilt against libedlib1
Added tag(s) upstream.
> forwarded -1 https://github.com/lbcb-sci/racon/issues/59
Bug #996541 [racon] racon: FTBFS when rebuilt against libedlib1
Set Bug forwarded-to-address to 'https:/
Control: tags -1 upstream
Control: forwarded -1 https://github.com/lbcb-sci/racon/issues/59
Argh, I simply missed to test the build before uploading libedlib1. :-(
I hope upstream has some solution.
Kind regards
Andreas.
--
http://fam-tille.de
Control: tags -1 help
Hi,
I've solved one gcc-11 issue that was mentioned in this bug report but
now there are other gcc-11 issues that go beyond my C++ knowledge:
...
g++ -g -O2 -ffile-prefix-map=/build/mothur-1.46.1=. -fstack-protector-strong
-Wformat -Werror=format-security -O3 -std=c++11 -p
Processing control commands:
> tags -1 help
Bug #984243 [src:mothur] mothur: ftbfs with GCC-11
Added tag(s) help.
--
984243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi Evgeny.
I've missed your first reply somehow, sorry. I'll happily do NMU on the
weekend.
On Thu, Oct 21, 2021, 16:44 Evgeny Golyshev wrote:
> Hi Sergei
>
> If you don't have time to do the NMU, tell me and I will upload the
> package applying your patch.
>
> --
> Evgeny
>
> On Mon, 18 Oct 20
Hi Sergei
If you don't have time to do the NMU, tell me and I will upload the package
applying your patch.
--
Evgeny
On Mon, 18 Oct 2021 at 14:25, Evgeny Golyshev wrote:
> Hello Sergei
>
> Thank you for the patch you prepared. It's well done. Feel free to do a
> NMU.
>
> --
> Evgeny
>
Processing control commands:
> reopen -1
Bug #994443 {Done: Andreas Tille } [src:r-bioc-deseq2]
r-bioc-deseq2: autopkgtest regression
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longe
Control: reopen -1
r-bioc-deseq2's autopkgtests started to again pass in testing on
2021-09-29, once r-bioc-tximportdata migrated.
However, the autopkgtests in stable continue to fail [1].
I think you are doing something wrong if a change in a package in
unstable affects a package in testing and
Your message dated Thu, 21 Oct 2021 13:03:28 +
with message-id
and subject line Bug#996895: fixed in hypre 2.22.1-3
has caused the Debian Bug report #996895,
regarding hypre: autopkgtest regression on armhf and i386
to be marked as done.
This means that you claim that the problem has been dea
Source: scipy
Version: 1.7.1-1
Severity: serious
Tags: ftbfs
Hi Maintainer
Sometime between 2021-08-18 and 2021-10-16, scipy 1.7.1-1 started to
FTBFS in unstable [1]. I've copied what I hope is the relevant part
of the log below.
Regards
Graham
[1] https://tests.reproducible-builds.org/debian
retested 5.14.14. Sorry not fixed there yet. Guess this is going upstream.
few other fixes to try:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/log/?h=io_uring-5.15
$ uname -a
Linux impish 5.14.14-051414-generic #202110201037 SMP Wed Oct 20
11:04:11 UTC 2021 x86_64 x86_64
Processing commands for cont...@bugs.debian.org:
> severity 947878 serious
Bug #947878 [src:gnome-mime-data] gnome-mime-data: unmaintained upstream for
over a decade
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
947878
Processing control commands:
> tags 947900 + pending
Bug #947900 [chemical-mime-data] chemical-mime-data: build-depends on
unmaintained gnome-mime-data
Added tag(s) pending.
--
947900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947900
Debian Bug Tracking System
Contact ow...@bugs.debian.
Control: tags 947900 + pending
Dear maintainer,
I've prepared an NMU for chemical-mime-data (versioned as 0.1.94-7.2)
and uploaded it to DELAYED/2. Please feel free to tell me if I should
delay it longer.
I'll update
https://salsa.debian.org/debichem-team/chemical-mime-data/-/merge_requests/1
to
On Thursday, 21 October 2021 12:41:34 CEST Salvatore Bonaccorso wrote:
> On Thu, Oct 21, 2021 at 09:38:00AM +, Daniel Black wrote:
> > Package: src:linux
> > Version: 5.14.12-1
> > The good news is I've validated that the linux mainline 5.14.14 build
> > from https://kernel.ubuntu.com/~kernel-p
Processing commands for cont...@bugs.debian.org:
> severity 938628 serious
Bug #938628 [src:taskd] taskd: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
938628: https://bugs.debian.org/cgi-bi
On Thu, 21 Oct 2021 12:37:55 +0200 Timo =?utf-8?Q?R=C3=B6hling?=
wrote:
-add_cxx_compiler_flag(-flto)
+add_cxx_compiler_flag(-ffat-lto-objects)
I just saw https://salsa.debian.org/science-team/benchmark/-/merge_requests/2
Reading the documentation again, I think *both* options are
req
Control: tags -1 + moreinfo
Hi Daniel,
On Thu, Oct 21, 2021 at 09:38:00AM +, Daniel Black wrote:
> Package: src:linux
> Version: 5.14.12-1
> Severity: grave
> Justification: causes non-serious data loss
> X-Debbugs-Cc: dan...@mariadb.org
>
> Dear Maintainer,
>
> MariaDB has been investigati
Processing control commands:
> tags -1 + moreinfo
Bug #996951 [src:linux] linux-image-5.14.0-3-amd64: iouring looses requests
Added tag(s) moreinfo.
--
996951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: libbenchmark-dev
Version: 1.6.0-1
Severity: serious
Tag: patch
Dear maintainer,
the latest version of libbenchmark-dev has a regression that breaks the
libbenchmark_main.a static library for users who do not use
link-time-optimzation. This is very similar to bug #968461:
https://bugs.de
Source: hypre
Followup-For: Bug #996895
The changelog for 2.22.1-1exp1 gives a clue,
"provide 64-bit only on arches where libblas64-dev, liblapack64-dev
are available"
Looks like debian/tests didn't receive the memo...
Package: src:libkolabxml
Version: 1.2.0-2
Severity: serious
Tags: sid bookworm patch
libkolabxml ftbfs with GCC 11, two more symbols need marking as optional.
patch at
http://launchpadlibrarian.net/564865144/libkolabxml_1.2.0-2build1_1.2.0-2ubuntu1.diff.gz
Source: hypre
Followup-For: Bug #996895
Weird. How could they have gone missing? Will have to track them done.
Drew
Package: src:linux
Version: 5.14.12-1
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: dan...@mariadb.org
Dear Maintainer,
MariaDB has been investigating a 10.6+ related problem for a while
https://jira.mariadb.org/browse/MDEV-26674
https://jira.mariadb.org/browse/MDEV-26
Your message dated Thu, 21 Oct 2021 09:18:42 +
with message-id
and subject line Bug#996146: fixed in r-cran-maotai 0.2.1-2
has caused the Debian Bug report #996146,
regarding r-cran-maotai FTBFS: dependencies 'labdsv', 'shapes', 'dbscan',
'RcppDist' are not available
to be marked as done.
Th
Processing control commands:
> retitle -1 llvm-toolchain-12: FTBFS on s390x since 1:12.0.1-10 and armhf
> since 1:12.0.1-11: Cannot find builtins library for the target architecture
Bug #996802 [src:llvm-toolchain-12] llvm-toolchain-12: FTBFS on s390x since
1:12.0.1-10: Cannot find builtins libr
Control: retitle -1 llvm-toolchain-12: FTBFS on s390x since 1:12.0.1-10 and
armhf since 1:12.0.1-11: Cannot find builtins library for the target
architecture
On Mon, 18 Oct 2021 at 22:43:35 +0100, Simon McVittie wrote:
> The restructuring in 1:12.0.1-10 seems to have caused a regression on s390x
Source: llvm-toolchain-12
Version: 1:12.0.1-11
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-12&arch=armel&ver=1%3A12.0.1-11&stamp=1634667108&raw=0
https://buildd.debian.org
Package: freeipa-server
Version: 4.9.7-1
Severity: serious
Justification: RT
This is a placeholder bug preventing migration to testing, until the root cause
of server
setup failing randomly is found. Seems to be related to slapd and pki-tomcatd;
in some
cases it doesn't trust it's own certificat
Package: luarocks
Version: 3.7.0+dfsg1-1
Followup-For: Bug #996781
The tree below /usr/local is luarocks' default and intended for
system-wide use of third-party modules or for users who want to share
rocks locally, setting this up is the whole point of the postinst
script. I've never used it and
Source: jupyter-console
Version: 6.4.0-1
Severity: serious
Control: close -1 6.4.0-2
X-Debbugs-CC: jel...@debian.org
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between t
Processing control commands:
> close -1 6.4.0-2
Bug #996945 [src:jupyter-console] src:jupyter-console: fails to migrate to
testing for too long: uploader built arch:all binaries
Marked as fixed in versions jupyter-console/6.4.0-2.
Bug #996945 [src:jupyter-console] src:jupyter-console: fails to mi
Your message dated Thu, 21 Oct 2021 07:48:41 +
with message-id
and subject line Bug#995185: fixed in flint-arb 1:2.21.1-1
has caused the Debian Bug report #995185,
regarding flint-arb FTBFS on 32bit: gamma_fmpq test fails
to be marked as done.
This means that you claim that the problem has be
Your message dated Thu, 21 Oct 2021 07:03:58 +
with message-id
and subject line Bug#987257: fixed in unixcw 3.6.0-3
has caused the Debian Bug report #987257,
regarding libcw{7,-dev}: removal of libcw{7,-dev} makes files disappear from
libcw6{,-dev}
to be marked as done.
This means that you c
Hi Nicolas,
On 21-10-2021 02:17, Nicholas D Steeves wrote:
> I will of course credit you for identifying this issue and taking the
> initiative to fix it, and will upload without delay once I receive your
> ACK (please CC me).
Thanks you, but as I detect these issues in an automatic way without
m
80 matches
Mail list logo
