Your message dated Thu, 16 Jan 2020 07:49:48 +
with message-id
and subject line Bug#939723: fixed in ratfor 1.03-1
has caused the Debian Bug report #939723,
regarding ratfor FTCBFS: doesn't use debhelper
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Thu, 16 Jan 2020 07:49:48 +
with message-id
and subject line Bug#812169: fixed in ratfor 1.03-1
has caused the Debian Bug report #812169,
regarding ratfor: FTBFS using clang instead of gcc
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Thu, 16 Jan 2020 07:49:48 +
with message-id
and subject line Bug#716285: fixed in ratfor 1.03-1
has caused the Debian Bug report #716285,
regarding [Mayhem] Bug report on ratfor: ratfor crashes with exit status 139
to be marked as done.
This means that you claim that the pr
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-an
Processing commands for cont...@bugs.debian.org:
> severity 936358 normal
Bug #936358 [src:cwiid] cwiid: Python2 removal in sid/bullseye
Bug #942981 [src:cwiid] cwiid: Python2 removal in sid/bullseye
Severity set to 'normal' from 'serious'
Severity set to 'normal' from 'serious'
> severity 938473
5 matches
Mail list logo