Control: clone -1 -2
Control: reassign -2 libncurses-dev 6.2+20200912-1
Control: retitle -2 dpkg and zsh FTBFS: KEY_EVENT undeclared
Control: severity -1 normal
Control: tags -2 - ftbfs
On 2020-09-18 19:29 +0200, Guillem Jover wrote:
> On Fri, 2020-09-18 at 18:26:34 +0200, Sven Joachim wrote:
>>
Processing control commands:
> clone -1 -2
Bug #970545 [src:dpkg] dpkg FTBFS: KEY_EVENT undeclared
Bug 970545 cloned as bug 970577
> reassign -2 libncurses-dev 6.2+20200912-1
Bug #970577 [src:dpkg] dpkg FTBFS: KEY_EVENT undeclared
Bug reassigned from package 'src:dpkg' to 'libncurses-dev'.
No long
Control: tag -1 pending
Hello,
Bug #970577 in ncurses 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/ncurses/-/commit/2d6ac0aae872eacba1c6052543303774ac
Processing control commands:
> tag -1 pending
Bug #970577 [libncurses-dev] dpkg and zsh FTBFS: KEY_EVENT undeclared
Added tag(s) pending.
--
970577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> tags 962692 + pending
Bug #962692 [facter] puppet: Crashes due to "missing" facts.d directories
Bug #962784 [facter] facter aborts with free(): invalid pointer
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.
Please
Your message dated Sat, 19 Sep 2020 17:12:47 +0900
with message-id <20200919081247.ga1215...@lilith.infoblue.home>
and subject line Re: rabbit: autopkgtest fails with ruby-karmdown 2.x in
experimental
has caused the Debian Bug report #966021,
regarding rabbit: autopkgtest fails with ruby-karmdown
Processing commands for cont...@bugs.debian.org:
> tags 970408 + pending
Bug #970408 [src:facter] facter: FTBFS: cc1plus: all warnings being treated as
errors
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
970408: https://bugs.debian.org/cg
Package: licenseutils
Version: 0.0.9-3+b1:
Severity: grave
I want to work out the different tools checking the license for
packaging as described at
https://wiki.debian.org/CopyrightReviewTools
At the first start I got
licensing gpl: got unexpected response code 302 from
www.gnu.org/licenses/gp
Your message dated Sat, 19 Sep 2020 09:47:08 +
with message-id
and subject line Bug#960650: fixed in inspircd 2.0.27-1+deb10u1
has caused the Debian Bug report #960650,
regarding InspIRCd Security Advisories 2019-02 and 2020-01
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> severity 970536 important
Bug #970536 [src:linux] linux-image-5.8.0-1-amd64: ethernet (dhcp) fails to
work after reboot
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
970
Processing commands for cont...@bugs.debian.org:
> tags 956523 + pending
Bug #956523 [mousetweaks] mousetweaks ends with segmentation fault
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
956523: https://bugs.debian.org/cgi-bin/bugreport.cgi?
Processing commands for cont...@bugs.debian.org:
> close 944573
Bug #944573 [src:thrift] thrift: FTBFS with phpunit 8.4.3-1
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
944573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944573
Debian B
Could severity be downgraded?
(The build on s390x seems to use a newer compiler.
The failure may be a compiler bug, but similar to
the RISC-V bug I can't investigate as I never got
access to porter boxes.)
On Thu, 17 Sep 2020 15:05:16 +0200 Andreas Tille wrote:
> Control: tags -1 normal
>
>
Hi Martin
On Sat, 19 Sep 2020 at 13:51, Uecker, Martin
wrote:
> Could severity be downgraded?
The severity on this bug can be downgraded, however the FTBFS on s390x
remains a release critical bug, since s390x is a release architecture.
Either the FTBFS gets fixed, or removal of the s390x binari
Your message dated Sat, 19 Sep 2020 21:09:28 +0900
with message-id <20200919210928.5eaa8559885004c1c98ce...@xdump.org>
and subject line src:libhinawa: fails to migrate to testing for too long:
reverse-dependency not ready yet
has caused the Debian Bug report #970101,
regarding src:libhinawa: fails
Hi Graham,
Am Samstag, den 19.09.2020, 14:04 +0200 schrieb Graham Inggs:
> On Sat, 19 Sep 2020 at 13:51, Uecker, Martin
> wrote:
> > Could severity be downgraded?
>
> The severity on this bug can be downgraded, however the FTBFS on s390x
> remains a release critical bug, since s390x is a release
Processing control commands:
> tag 958614 + pending
Bug #958614 [src:nyancat] nyancat: Build-Depends on deprecated dh-systemd which
is going away
Ignoring request to alter tags of bug #958614 to the same tags previously set
--
958614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958614
Deb
Processing control commands:
> tag 958614 + pending
Bug #958614 [src:nyancat] nyancat: Build-Depends on deprecated dh-systemd which
is going away
Added tag(s) pending.
--
948536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948536
958614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=9
Control: tag 958614 + pending
Dear Adrian, dear Jonathan,
[JFTR: I'm not the maintainer, just someone who was about to NMU
nyancat due to #958614, too.]
Adrian Vondendriesch wrote:
> Tags: patch pending
^^^
Hmmm, this NMU never seems to have made it through (in case it ever
Package: virtualbox-6.1
Severity: grave
Tags: a11y
Justification: renders package unusable
Dear Maintainer,
after installing the latest updates for debian testing, the package
virtualbox-6.1 got removed by apt. Reinstallation of the package fails with:
virtualbox-6.1: depends on: python (<2.8) b
Processing control commands:
> block -1 by 970134
Bug #966535 [release.debian.org] transition: pipewire 0.3
966535 was blocked by: 969612 969613 954022 969614
966535 was not blocking any bugs.
Added blocking bug(s) of 966535: 970134
--
966535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=96
Hi Martin,
On Sat, Sep 19, 2020 at 01:15:47PM +, Uecker, Martin wrote:
> > The severity on this bug can be downgraded, however the FTBFS on s390x
> > remains a release critical bug, since s390x is a release architecture.
> >
> > Either the FTBFS gets fixed, or removal of the s390x binaries ca
The libaccounts-glib package does not seem to be getting maintained in Debian,
it has had a rc bug (deprecated declarations
and -Werror) for 8 months with no maintainer response and has recently picked
up a second one (unversioned python removal).
It has not had an upload for 3 years.
Both of t
Processing commands for cont...@bugs.debian.org:
> close 942514
Bug #942514 [src:pam-python] pam-python: CVE-2019-16729: local root escalation
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
942514: https://bugs.debian.org/cgi-bin/bugreport.cgi?
Package: nuspell
Severity: serious
Version: 3.0.0-1
nuspell is currently uninstallable on amd64:
# apt install nuspell
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible
Package: goaccess
Version: 1:1.4-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
As described on the upstream bug report
(https://github.com/allinurl/goaccess/issues/1918) version 1.4 will exit
with an error message stating the GeoIP database is unreadabl
The debian python maintainers are trying to phase out python 2.
python 2 has been granted a stay of execution as some important software
requires it to build. However we should still
be attempting to get rid of use at runtime if at all possible. Also the "unversioned
python" packages have been
Hello,
Just had an idea, and had another look, and it seems, I did spot something:
Both the 1.4 version from bullseye, and the 1.4 upstream (actually meant
for buster seem to be built with --enable-geoip=mmdb; whereas the 1.2
official is using --enable-geoip=legacy.
See
https://salsa.debian.org/
Furthermore it seems to me, that all versions (buster, bullseye,
buster-backports) of the geoip-database and geoip-database-extra are using
the legacy format.
On Sat, 19 Sep 2020 at 18:17, Dániel Fancsali wrote:
> Hello,
>
> Just had an idea, and had another look, and it seems, I did spot someth
Am Samstag, den 19.09.2020, 17:09 +0200 schrieb Andreas Tille:
> Hi Martin,
>
> On Sat, Sep 19, 2020 at 01:15:47PM +, Uecker, Martin wrote:
> > > The severity on this bug can be downgraded, however the FTBFS on s390x
> > > remains a release critical bug, since s390x is a release architecture.
Processing commands for cont...@bugs.debian.org:
> tags 925781 +patch +pending
Bug #925781 [src:mozjs52] mozjs52: ftbfs with GCC-9
Added tag(s) patch.
Bug #925781 [src:mozjs52] mozjs52: ftbfs with GCC-9
Added tag(s) pending.
> tags 967177 +patch +pending
Bug #967177 [src:mozjs52] mozjs52: Unversio
tags 925781 +patch +pending
tags 967177 +patch +pending
thanks
I have decided to take the Ubuntu fixes for mozjs52 and turn them into a NMU. I
also ran into some issues
with the clean target while preparing the NMU so I fixed those too.
mozjs52 has only one reverse-dependency: cjs which in turn
Confirmed: built from source with --enable-geoip=legacy and the issue is
gone.
On Sat, 19 Sep 2020 at 18:36, Dániel Fancsali wrote:
> Furthermore it seems to me, that all versions (buster, bullseye,
> buster-backports) of the geoip-database and geoip-database-extra are using
> the legacy format.
Hi maintainers,
On Sat, 4 Jul 2020 20:26:11 +0200 Paul Gevers wrote:
> This bug will trigger auto-removal when appropriate. As with all new
> bugs, there will be at least 30 days before the package is auto-removed.
rust-ppv-lite86 is not eligible for autoremoval, so that's not going to
"fix" the
Source: openjdk-15
Version: 15+36-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: timeout
Dear maintainers, Matthias,
For a long time, the autopkgtests of openjdk-* have been failing on the
ci.debian.net infrastructure and
Processing control commands:
> close -1 6.7.0.1-1
Bug #970609 [src:cl-sql] src:cl-sql: fails to migrate to testing for too long:
maintainer built arch:all binaries
Marked as fixed in versions cl-sql/6.7.0.1-1.
Bug #970609 [src:cl-sql] src:cl-sql: fails to migrate to testing for too long:
maintai
Source: cl-sql
Version: 6.7.0-1.1
Severity: serious
Control: close -1 6.7.0.1-1
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing
Source: coreutils
Version: 8.30-3
Severity: serious
Control: close -1 8.32-3
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 966449
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-syn
Processing control commands:
> close -1 8.32-3
Bug #970608 [src:coreutils] src:coreutils: fails to migrate to testing for too
long: FTBFS on arm64
Marked as fixed in versions coreutils/8.32-3.
Bug #970608 [src:coreutils] src:coreutils: fails to migrate to testing for too
long: FTBFS on arm64
Mar
Source: cl-kmrcl
Version: 1.109-1
Severity: serious
Control: close -1 1.110-1
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing a
Processing control commands:
> close -1 1.110-1
Bug #970610 [src:cl-kmrcl] src:cl-kmrcl: fails to migrate to testing for too
long: maintainer built arch:all binairies
Marked as fixed in versions cl-kmrcl/1.110-1.
Bug #970610 [src:cl-kmrcl] src:cl-kmrcl: fails to migrate to testing for too
long:
Source: barrier
Version: 2.3.2+dfsg-1
Severity: serious
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 d
Source: golang-github-fogleman-gg
Version: 1.3.0-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
You recently added an autopkgtest to your package
golang-github-fogleman-gg, great. However, it fails on arm64.
Your message dated Sat, 19 Sep 2020 22:32:16 +0200
with message-id <20200919203216.gm2020...@mapreri.org>
and subject line Re: Bug#970593: virtualbox-6.1: package cannot be installed on
current debian testing
has caused the Debian Bug report #970593,
regarding virtualbox-6.1: package cannot be ins
Processing control commands:
> retitle -1 text installer: unable to switch keyboard layouts - kbd_mode broken
Bug #969965 [installation-reports] Installation of Debian 11 mostly successfully
Changed Bug title to 'text installer: unable to switch keyboard layouts -
kbd_mode broken' from 'Installat
Processing control commands:
> severity -1 important
Bug #969806 [src:cadubi] cadubi: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969806
Debian Bug Tracking System
Contact ow...@bugs.debian.org w
Processing control commands:
> severity -1 important
Bug #969800 [src:android-platform-frameworks-native]
android-platform-frameworks-native: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969800
D
Processing control commands:
> severity -1 important
Bug #969828 [src:fwlogwatch] fwlogwatch: autopkgtest should be marked
superficial
Severity set to 'important' from 'serious'
--
969828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969828
Debian Bug Tracking System
Contact ow...@bugs.deb
Processing control commands:
> severity -1 important
Bug #969822 [src:dyndns] dyndns: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969822
Debian Bug Tracking System
Contact ow...@bugs.debian.org w
Processing control commands:
> severity -1 important
Bug #969854 [src:pyavm] pyavm: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969854
Debian Bug Tracking System
Contact ow...@bugs.debian.org wit
Processing control commands:
> severity -1 important
Bug #969857 [src:python-axolotl] python-axolotl: autopkgtest should be marked
superficial
Severity set to 'important' from 'serious'
--
969857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969857
Debian Bug Tracking System
Contact ow...@
Processing control commands:
> severity -1 important
Bug #969856 [src:pysvn] pysvn: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969856
Debian Bug Tracking System
Contact ow...@bugs.debian.org wit
Processing control commands:
> severity -1 important
Bug #969855 [src:pylast] pylast: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969855
Debian Bug Tracking System
Contact ow...@bugs.debian.org w
Control: severity -1 important
--
Hi,
As discussed on debian-devel, I am reducing the severity to important.
Ref: https://lists.debian.org/debian-devel/2020/09/msg00266.html
--
Regards
Sudip
Processing control commands:
> severity -1 important
Bug #969802 [src:apachetop] apachetop: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969802
Debian Bug Tracking System
Contact ow...@bugs.debian
Processing control commands:
> severity -1 important
Bug #969846 [src:mp3diags] mp3diags: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969846
Debian Bug Tracking System
Contact ow...@bugs.debian.o
Processing control commands:
> severity -1 important
Bug #969833 [src:hostsed] hostsed: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969833
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Processing control commands:
> severity -1 important
Bug #969831 [src:glyr] glyr: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing control commands:
> severity -1 important
Bug #969801 [src:android-platform-system-core] android-platform-system-core:
autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969801
Debian Bug Tr
Processing control commands:
> severity -1 important
Bug #969847 [src:music123] music123: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969847
Debian Bug Tracking System
Contact ow...@bugs.debian.o
Processing control commands:
> severity -1 important
Bug #969799 [src:android-platform-external-libunwind]
android-platform-external-libunwind: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969799
Processing control commands:
> severity -1 important
Bug #969805 [src:btcheck] btcheck: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969805
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Processing control commands:
> severity -1 important
Bug #969816 [src:cupp] cupp: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing control commands:
> severity -1 important
Bug #969798 [src:android-platform-external-libselinux]
android-platform-external-libselinux: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=9697
Processing control commands:
> severity -1 important
Bug #969859 [src:python-mido] python-mido: autopkgtest should be marked
superficial
Severity set to 'important' from 'serious'
--
969859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969859
Debian Bug Tracking System
Contact ow...@bugs.d
Processing control commands:
> severity -1 important
Bug #969827 [src:fuzz] fuzz: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing control commands:
> severity -1 important
Bug #969858 [src:python-jack-client] python-jack-client: autopkgtest should be
marked superficial
Severity set to 'important' from 'serious'
--
969858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969858
Debian Bug Tracking System
Contac
Processing control commands:
> severity -1 important
Bug #969851 [src:nftables] nftables: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969851
Debian Bug Tracking System
Contact ow...@bugs.debian.o
Processing control commands:
> severity -1 important
Bug #969860 [src:python-pydub] python-pydub: autopkgtest should be marked
superficial
Severity set to 'important' from 'serious'
--
969860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969860
Debian Bug Tracking System
Contact ow...@bugs
Processing control commands:
> severity -1 important
Bug #969836 [src:kickpass] kickpass: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969836
Debian Bug Tracking System
Contact ow...@bugs.debian.o
Processing control commands:
> severity -1 important
Bug #969853 [src:pudb] pudb: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing control commands:
> severity -1 important
Bug #969838 [src:linux-show-player] linux-show-player: autopkgtest should be
marked superficial
Severity set to 'important' from 'serious'
--
969838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969838
Debian Bug Tracking System
Contact
Processing control commands:
> severity -1 important
Bug #969829 [src:fzf] fzf: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with pr
Processing control commands:
> severity -1 important
Bug #969796 [src:afterstep] afterstep: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969796
Debian Bug Tracking System
Contact ow...@bugs.debian
Processing control commands:
> severity -1 important
Bug #969818 [src:discus] discus: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969818
Debian Bug Tracking System
Contact ow...@bugs.debian.org w
Processing control commands:
> severity -1 important
Bug #969873 [src:twython] twython: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969873
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Processing control commands:
> severity -1 important
Bug #969865 [src:rss2email] rss2email: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969865
Debian Bug Tracking System
Contact ow...@bugs.debian
Processing control commands:
> severity -1 important
Bug #969876 [src:virt-top] virt-top: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969876
Debian Bug Tracking System
Contact ow...@bugs.debian.o
Processing control commands:
> severity -1 important
Bug #969874 [src:vifm] vifm: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing control commands:
> severity -1 important
Bug #969866 [src:rtv] rtv: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with pr
Processing control commands:
> severity -1 important
Bug #969883 [src:yowsup] yowsup: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969883
Debian Bug Tracking System
Contact ow...@bugs.debian.org w
Processing control commands:
> severity -1 important
Bug #969861 [src:rdist] rdist: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969861
Debian Bug Tracking System
Contact ow...@bugs.debian.org wit
Processing control commands:
> severity -1 important
Bug #969878 [src:virt-what] virt-what: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969878
Debian Bug Tracking System
Contact ow...@bugs.debian
Processing control commands:
> severity -1 important
Bug #969864 [src:rover] rover: autopkgtest should be marked superficial
Severity set to 'important' from 'serious'
--
969864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969864
Debian Bug Tracking System
Contact ow...@bugs.debian.org wit
Your message dated Sat, 19 Sep 2020 20:41:06 +
with message-id
and subject line Bug#970567: fixed in pyzmq 17.1.2-2+deb10u1
has caused the Debian Bug report #970567,
regarding pyzmq: TestAsyncioAuthentication::test_blacklist hanging after
CVE-2020-15166 bugfix for zeromq3
to be marked as done
tags 970258 fixed-upstream
thanks
On Wed, Sep 16, 2020 at 09:27:30AM +0200, Malte Eggers wrote:
> I'm (unsurprisingly) experiencing the same problem on sid. This appears to be
> the relevant section of the make.log
Indeed, this is not surprising -- the patches for kernel 5.8 compatibility
haven'
Processing commands for cont...@bugs.debian.org:
> tags 970258 fixed-upstream
Bug #970258 [openafs-modules-dkms] openafs-modules-dkms: Does not build on
bullseye with kernel 5.8.7
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
970258
Your message dated Sat, 19 Sep 2020 21:50:06 +
with message-id
and subject line Bug#961584: fixed in lxc 1:4.0.4-2
has caused the Debian Bug report #961584,
regarding lxc-stop fails with exit code 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Hi,
Am Samstag, 19. September 2020 schrieb Holger Wansing:
> I boiled that down to the latest version of kbd, which breaks console-setup
> run
> with mutiple error messages like this:
>
>
> /bin/setupcon:
> line 105:
> kbd_mode: not found
>
> The images from https://d-i.deb
Hi,
Am Samstag, 19. September 2020 schrieb Holger Wansing:
> I boiled that down to the latest version of kbd, which breaks console-setup
> run
> with mutiple error messages like this:
>
>
> /bin/setupcon:
> line 105:
> kbd_mode: not found
>
> The images from https://d-i.deb
Your message dated Sat, 19 Sep 2020 22:04:16 +
with message-id
and subject line Bug#970600: fixed in nuspell 3.0.0-2
has caused the Debian Bug report #970600,
regarding nuspell: Uninstallable on amd64: Depends on no more existing
libboost-locale1.67.0, needs rebuild
to be marked as done.
Thi
Hi Peter,
thanks for bringing this up.
Am Samstag, 19. September 2020 schrieb peter green:
> The libaccounts-glib package does not seem to be getting maintained in
> Debian, it has had a rc bug (deprecated declarations
> and -Werror) for 8 months with no maintainer response and has recently pick
Your message dated Sun, 20 Sep 2020 03:11:48 +
with message-id
and subject line Bug#969608: fixed in ncbi-blast+ 2.10.1-1
has caused the Debian Bug report #969608,
regarding ncbi-blast+: regressions on armhf
to be marked as done.
This means that you claim that the problem has been dealt with.
93 matches
Mail list logo
