Bug#978957: marked as done (gvmd: Version in testing FTBFS against libgvm-dev in sid manage.c:4179:16: error: too few arguments to function 'osp_target_new')

2020-12-31 Thread Debian Bug Tracking System
Your message dated Fri, 1 Jan 2021 08:09:55 +0100 with message-id and subject line Re: Bug#978957: gvmd: Version in testing FTBFS against libgvm-dev in sid manage.c:4179:16: error: too few arguments to function 'osp_target_new' has caused the Debian Bug report #978957, regarding gvmd: Version

Bug#978957: gvmd: Version in testing FTBFS against libgvm-dev in sid manage.c:4179:16: error: too few arguments to function 'osp_target_new'

2020-12-31 Thread Andreas Metzler
Package: gvmd Version: 9.0.1-4.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hello, this is mainly a tracking bug for other people wondering about failing CI in testing. - I will do a versioned close, once I have a bugnumber. gvmd

Processed: tagging 978952, severity of 978952 is normal

2020-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 978952 + moreinfo Bug #978952 [wsjtx] wsjtx: No audio on transmit Added tag(s) moreinfo. > severity 978952 normal Bug #978952 [wsjtx] wsjtx: No audio on transmit Severity set to 'normal' from 'grave' > thanks Stopping processing here.

Bug#978952: wsjtx: No audio on transmit

2020-12-31 Thread tony mancill
On Fri, Jan 01, 2021 at 04:08:57AM +, Hilary Snaden wrote: > Package: wsjtx > Version: 2.3.0~rc2+repack-1+b1 > Severity: grave > Justification: renders package unusable > > There is no audio output to any of the listed devices (I have tried them > all). This was also the case with version

Bug#978954: pepperflashplugin-nonfree: should not be part of next stable Debian release

2020-12-31 Thread Ying-Chun Liu (PaulLiu)
Package: pepperflashplugin-nonfree Version: 1.8.7 Severity: grave Justification: renders package unusable Dear Maintainer, flash has been EOL today. Browsers are starting to block flash. I think we should block this package goes into next release? Yours, Paul -- System Information: Debian

Bug#974546: marked as done (klatexformula FTBFS: error: invalid use of incomplete type ‘class QPainterPath’)

2020-12-31 Thread Debian Bug Tracking System
Your message dated Fri, 01 Jan 2021 02:19:02 + with message-id and subject line Bug#974546: fixed in klatexformula 4.1.0-1 has caused the Debian Bug report #974546, regarding klatexformula FTBFS: error: invalid use of incomplete type ‘class QPainterPath’ to be marked as done. This means

Bug#960454: chromium: Make Chromium ask before downloading and enabling DRM

2020-12-31 Thread Christoph Anton Mitterer
Hey. Just wondered: 1) Since this is a binary blob who, by it's nature, is made for surveillance, it's IMO more a rather serious security issue than just a DFSG-policy problem. No one really knows what exactly Google ships there. So maybe people should be told about this more actively in a

Processed: tagging 974546, tagging 974856

2020-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 974546 + pending Bug #974546 [src:klatexformula] klatexformula FTBFS: error: invalid use of incomplete type ‘class QPainterPath’ Added tag(s) pending. > tags 974856 + pending Bug #974856 [sponsorship-requests] RFS: klatexformula/4.1.0-1

Bug#957320: marked as done (gtkpod: ftbfs with GCC-10)

2020-12-31 Thread Debian Bug Tracking System
Your message dated Fri, 01 Jan 2021 01:18:55 + with message-id and subject line Bug#957320: fixed in gtkpod 2.1.5-8 has caused the Debian Bug report #957320, regarding gtkpod: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#978325: marked as done (libgit-repository-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2)

2020-12-31 Thread Debian Bug Tracking System
Your message dated Fri, 01 Jan 2021 00:34:19 + with message-id and subject line Bug#978325: fixed in libgit-repository-perl 1.324-2 has caused the Debian Bug report #978325, regarding libgit-repository-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 to be

Bug#978375: marked as done (gkdebconf: FTBFS: error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.19 but the autoconf macros are from gettext version 0.20)

2020-12-31 Thread Debian Bug Tracking System
Your message dated Fri, 01 Jan 2021 00:33:23 + with message-id and subject line Bug#978375: fixed in gkdebconf 2.1.1 has caused the Debian Bug report #978375, regarding gkdebconf: FTBFS: error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.19 but the autoconf

Bug#976910: marked as done (python-blosc: FTBFS on ppc64el: KeyError: 'flags')

2020-12-31 Thread Debian Bug Tracking System
Your message dated Fri, 01 Jan 2021 00:34:24 + with message-id and subject line Bug#976910: fixed in python-blosc 1.9.2+ds1-3 has caused the Debian Bug report #976910, regarding python-blosc: FTBFS on ppc64el: KeyError: 'flags' to be marked as done. This means that you claim that the problem

Processed: Bug#978325 marked as pending in libgit-repository-perl

2020-12-31 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #978325 [src:libgit-repository-perl] libgit-repository-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Added tag(s) pending. -- 978325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978325 Debian Bug

Bug#957912: marked as done (vinagre: ftbfs with GCC-10)

2020-12-31 Thread Debian Bug Tracking System
Your message dated Fri, 01 Jan 2021 00:20:09 + with message-id and subject line Bug#957912: fixed in vinagre 3.22.0-8 has caused the Debian Bug report #957912, regarding vinagre: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#978622: marked as done (src:libcrypt-des-ede3-perl: invalid maintainer address)

2020-12-31 Thread Debian Bug Tracking System
Your message dated Fri, 01 Jan 2021 00:18:44 + with message-id and subject line Bug#978622: fixed in libcrypt-des-ede3-perl 0.01-2 has caused the Debian Bug report #978622, regarding src:libcrypt-des-ede3-perl: invalid maintainer address to be marked as done. This means that you claim that

Bug#978325: marked as pending in libgit-repository-perl

2020-12-31 Thread gregor herrmann
Control: tag -1 pending Hello, Bug #978325 in libgit-repository-perl 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:

Bug#978935: [Pkg-utopia-maintainers] Bug#978935: network-manager: disconnect on upgrade

2020-12-31 Thread Vincent Lefevre
On 2020-12-31 20:22:56 +0100, Michael Biebl wrote: > Am 31.12.20 um 18:37 schrieb Vincent Lefevre: > > During the upgrade, network-manager disconnected, so that I completely > > lost the network connection. Fortunately, I was in front of my machine, > > but this means that a remote upgrade can

Processed: Bug#957912 marked as pending in vinagre

2020-12-31 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #957912 [src:vinagre] vinagre: ftbfs with GCC-10 Added tag(s) pending. -- 957912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#957912: marked as pending in vinagre

2020-12-31 Thread Andreas Henriksson
Control: tag -1 pending Hello, Bug #957912 in vinagre 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:

Bug#964690: marked as done (signon-plugin-oauth2: FTBFS: oauth1plugin.cpp:147:51: error: ‘void QUrl::addQueryItem(const QString&, const QString&)’ is deprecated [-Werror=deprecated-declarations])

2020-12-31 Thread Debian Bug Tracking System
Your message dated Fri, 01 Jan 2021 00:04:20 + with message-id and subject line Bug#964690: fixed in signon-plugin-oauth2 0.25-1 has caused the Debian Bug report #964690, regarding signon-plugin-oauth2: FTBFS: oauth1plugin.cpp:147:51: error: ‘void QUrl::addQueryItem(const QString&, const

Bug#976477: marked as pending in jruby

2020-12-31 Thread Louis-Philippe Véronneau
Control: tag -1 pending Hello, Bug #976477 in jruby 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:

Processed: tagging 964690

2020-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 964690 + pending Bug #964690 [src:signon-plugin-oauth2] signon-plugin-oauth2: FTBFS: oauth1plugin.cpp:147:51: error: ‘void QUrl::addQueryItem(const QString&, const QString&)’ is deprecated [-Werror=deprecated-declarations] Added tag(s)

Processed: Bug#976477 marked as pending in jruby

2020-12-31 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #976477 [src:jruby] jruby: FTBFS: cp: cannot stat '/usr/lib/ruby/vendor_ruby/rake*': No such file or directory Added tag(s) pending. -- 976477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976477 Debian Bug Tracking System Contact

Bug#967159: marked as done (libaccounts-glib: Unversioned Python removal in sid/bullseye)

2020-12-31 Thread Debian Bug Tracking System
Your message dated Thu, 31 Dec 2020 21:18:40 + with message-id and subject line Bug#967159: fixed in libaccounts-glib 1.25-1 has caused the Debian Bug report #967159, regarding libaccounts-glib: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that

Bug#949177: marked as done (libaccounts-glib: FTBFS: -Werror + -Wdeprecated-declarations)

2020-12-31 Thread Debian Bug Tracking System
Your message dated Thu, 31 Dec 2020 21:18:40 + with message-id and subject line Bug#949177: fixed in libaccounts-glib 1.25-1 has caused the Debian Bug report #949177, regarding libaccounts-glib: FTBFS: -Werror + -Wdeprecated-declarations to be marked as done. This means that you claim that

Bug#978616: marked as done (mediastreamer2: doesn't build correct libraries with cmake?)

2020-12-31 Thread Debian Bug Tracking System
Your message dated Thu, 31 Dec 2020 21:05:03 + with message-id and subject line Bug#978616: fixed in mediastreamer2 1:4.4.21-3 has caused the Debian Bug report #978616, regarding mediastreamer2: doesn't build correct libraries with cmake? to be marked as done. This means that you claim that

Bug#978357: marked as done (gnome-todo: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --l

2020-12-31 Thread Debian Bug Tracking System
Your message dated Thu, 31 Dec 2020 21:03:27 + with message-id and subject line Bug#978357: fixed in gnome-todo 3.28.1-6 has caused the Debian Bug report #978357, regarding gnome-todo: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload

Bug#978357: marked as pending in gnome-todo

2020-12-31 Thread Andreas Henriksson
Control: tag -1 pending Hello, Bug #978357 in gnome-todo 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:

Processed: Bug#978357 marked as pending in gnome-todo

2020-12-31 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #978357 [src:gnome-todo] gnome-todo: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu

Processed: tagging 936841, tagging 949177, tagging 953769, tagging 967159

2020-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 936841 + pending Bug #936841 [src:libaccounts-glib] libaccounts-glib: Python2 removal in sid/bullseye Added tag(s) pending. > tags 949177 + pending Bug #949177 [src:libaccounts-glib] libaccounts-glib: FTBFS: -Werror +

Bug#978356: marked as done (libcxx-serial: FTBFS: dh_missing: error: missing files, aborting)

2020-12-31 Thread Debian Bug Tracking System
Your message dated Thu, 31 Dec 2020 20:34:01 + with message-id and subject line Bug#977844: fixed in libcxx-serial 1.2.1-4.1 has caused the Debian Bug report #977844, regarding libcxx-serial: FTBFS: dh_missing: error: missing files, aborting to be marked as done. This means that you claim

Bug#977844: marked as done (src:libcxx-serial: libcxx-serial FTBFS with new catkin (patch attached))

2020-12-31 Thread Debian Bug Tracking System
Your message dated Thu, 31 Dec 2020 20:34:01 + with message-id and subject line Bug#977844: fixed in libcxx-serial 1.2.1-4.1 has caused the Debian Bug report #977844, regarding src:libcxx-serial: libcxx-serial FTBFS with new catkin (patch attached) to be marked as done. This means that you

Bug#976546: marked as done (libmiglayout-java: FTBFS on arm64,ppc64el (arch:all-only src pkg): [ERROR] /<>/swt/src/main/java/net/miginfocom/swt/MigLayout.java:[527,33] cannot find symbol)

2020-12-31 Thread Debian Bug Tracking System
Your message dated Thu, 31 Dec 2020 19:48:55 + with message-id and subject line Bug#976546: fixed in libmiglayout-java 5.1-3 has caused the Debian Bug report #976546, regarding libmiglayout-java: FTBFS on arm64,ppc64el (arch:all-only src pkg): [ERROR]

Processed: Re: [Pkg-utopia-maintainers] Bug#978935: network-manager: disconnect on upgrade

2020-12-31 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + moreinfo Bug #978935 [network-manager] network-manager: disconnect on upgrade Added tag(s) moreinfo. -- 978935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#978935: [Pkg-utopia-maintainers] Bug#978935: network-manager: disconnect on upgrade

2020-12-31 Thread Michael Biebl
Control: tags -1 + moreinfo Am 31.12.20 um 18:37 schrieb Vincent Lefevre: Package: network-manager Version: 1.28.0-1+b1 Severity: serious During the upgrade, network-manager disconnected, so that I completely lost the network connection. Fortunately, I was in front of my machine, but this

Bug#978939: zeekctl: missing Breaks+Replaces: broctl (<< 2)

2020-12-31 Thread Andreas Beckmann
Package: zeekctl Version: 2.2.0+ds1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries

Processed: bug 978936 is forwarded to https://github.com/darktable-org/darktable/issues/7583

2020-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 978936 https://github.com/darktable-org/darktable/issues/7583 Bug #978936 [darktable] darktable: FTBFS on arm64 Set Bug forwarded-to-address to 'https://github.com/darktable-org/darktable/issues/7583'. > thanks Stopping processing

Bug#978936: darktable: FTBFS on arm64

2020-12-31 Thread David Bremner
Package: darktable Version: 3.4.0-1 Severity: serious Tags: upstream Justification: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Control: -1 forwarded https://github.com/darktable-org/darktable/issues/7583 The new release requires xmmintrin.h in several places, and that include file is

Bug#978739: chardet: Upgrading python3-chardet breaks many packages

2020-12-31 Thread Daniele Tricoli
Hello Sebastiaan, On Thu, Dec 31, 2020 at 04:28:40PM +0100, Sebastiaan Couwenberg wrote: > Thanks for quickly acting on this, but the problem is not limited to > python3-requests. Several other reverse dependencies need to be updated > for the new chardet as well. The autopkgtest failures include

Processed: [bts-link] source package src:apertium-br-fr

2020-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:apertium-br-fr > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user

Processed: [bts-link] source package src:pylint

2020-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:pylint > # 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

Processed: [bts-link] source package src:apertium-eo-ca

2020-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:apertium-eo-ca > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user

Bug#978749: marked as done (bound on python3-chardet < 3.1.0 prevents install & build)

2020-12-31 Thread Debian Bug Tracking System
Your message dated Thu, 31 Dec 2020 17:35:50 + with message-id and subject line Bug#978749: fixed in requests 2.25.1+dfsg-2 has caused the Debian Bug report #978749, regarding bound on python3-chardet < 3.1.0 prevents install & build to be marked as done. This means that you claim that the

Bug#978935: network-manager: disconnect on upgrade

2020-12-31 Thread Vincent Lefevre
Package: network-manager Version: 1.28.0-1+b1 Severity: serious During the upgrade, network-manager disconnected, so that I completely lost the network connection. Fortunately, I was in front of my machine, but this means that a remote upgrade can make the machine unavailable! In the journalctl

Bug#969372: Missing After=network-online.target

2020-12-31 Thread Thomas Goirand
Hi, The above .service file looks ok, though it's missing this: After=network-online.target Cheers, Thomas Goirand (zigo)

Bug#976891: Unable to find next sigaction in signal chain

2020-12-31 Thread Hans-Christoph Steiner
Now fastboot and aapt build and link but both report this error: Unable to find next sigaction in signal chain Looks like some dynamically loaded code is missing, the error is in sigchainlib/sigchain.cc: static void lookup_next_symbol(T* output, T wrapper, const char* name) { void*

Bug#978749: requests: circular dependency makes requests unbuildable

2020-12-31 Thread Thomas Goirand
On 12/31/20 4:31 PM, Daniele Tricoli wrote: > Nowadays for > urllib3 upstream uses a range of versions, and I take care of both urllib3 and > requests, so we should not have problems. Oh, it's very nice that upstream changed their mind, after all of this time. Thanks for sharing this info. I can

Processed: closing 978685

2020-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 978685 2.0.235-4 Bug #978685 [libjhlabs-filters-java] libjhlabs-filters-java: tries to overwrite /usr/share/doc-base/doc-base Marked as fixed in versions libjhlabs-filters-java/2.0.235-4; no longer marked as fixed in versions 2.0.235-4.

Bug#978684: marked as done (autopkgtest should test the installed package)

2020-12-31 Thread Debian Bug Tracking System
Your message dated Thu, 31 Dec 2020 16:18:40 + with message-id and subject line Bug#978684: fixed in apk-parser 2.6.10+ds-4 has caused the Debian Bug report #978684, regarding autopkgtest should test the installed package to be marked as done. This means that you claim that the problem has

Bug#978684: autopkgtest should test the installed package

2020-12-31 Thread Roger Shimizu
> As pointed in the see autopkgtest specification [1] linked from the > release team documentation [2] “the tests must test the *installed* > version of the package”. The autopkgtest from this package only uses the > source package, and as such violates the specification. Displaying it as > an

Bug#978749: requests: circular dependency makes requests unbuildable

2020-12-31 Thread Sebastian Ramacher
On 2020-12-31 16:03:48 +0100, Thomas Goirand wrote: > On 12/31/20 1:25 PM, Sebastian Ramacher wrote: > > Hi Thomas > > > > On 2020-12-31 13:06:37 +0100, Thomas Goirand wrote: > >> Hi Sebastian, > >> > >> I'm challenging the fact that a circular dependency is a problem for > >> arch:all packages.

Processed: Re: Bug#978616: mediastreamer2: doesn't build correct libraries with cmake?

2020-12-31 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 > https://github.com/BelledonneCommunications/mediastreamer2/pull/27 Bug #978616 [src:mediastreamer2] mediastreamer2: doesn't build correct libraries with cmake? Set Bug forwarded-to-address to

Bug#978749: requests: circular dependency makes requests unbuildable

2020-12-31 Thread Daniele Tricoli
Hello Thomas, hello Sebastian! Thomas, thanks for always caring about requests! On Thu, Dec 31, 2020 at 04:03:48PM +0100, Thomas Goirand wrote: > If I understand correctly, the issue was that requests had: > > python3-chardet (>= 3.0.2), python3-chardet (<< 3.1.0) > > as (build-)depends,

Bug#978616: mediastreamer2: doesn't build correct libraries with cmake?

2020-12-31 Thread Gianfranco Costamagna
control: forwarded -1 https://github.com/BelledonneCommunications/mediastreamer2/pull/27 thanks G.

Bug#978739: chardet: Upgrading python3-chardet breaks many packages

2020-12-31 Thread Sebastiaan Couwenberg
reopen 978739 thanks On 12/31/20 4:13 PM, Daniele Tricoli wrote: > On Thu, Dec 31, 2020 at 05:55:17AM +0100, Bas Couwenberg wrote: >> Package: chardet >> Version: 4.0.0-1 >> Severity: serious >> Justification: makes the package in question unusable or mostly so >> Control: affects -1 src:requests

Processed: Re: Bug#978739: chardet: Upgrading python3-chardet breaks many packages

2020-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 978739 Bug #978739 {Done: Daniele Tricoli } [chardet] chardet: Upgrading python3-chardet breaks many packages 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to

Bug#978739: marked as done (chardet: Upgrading python3-chardet breaks many packages)

2020-12-31 Thread Debian Bug Tracking System
Your message dated Thu, 31 Dec 2020 16:13:05 +0100 with message-id <20201231151305.ju5ubbcepdwr52h4@mornie> and subject line Re: Bug#978739: chardet: Upgrading python3-chardet breaks many packages has caused the Debian Bug report #978739, regarding chardet: Upgrading python3-chardet breaks many

Bug#978739: chardet: Upgrading python3-chardet breaks many packages

2020-12-31 Thread Daniele Tricoli
Version: 2.25.1+dfsg-1 Hello Bas, thanks for the report! On Thu, Dec 31, 2020 at 05:55:17AM +0100, Bas Couwenberg wrote: > Package: chardet > Version: 4.0.0-1 > Severity: serious > Justification: makes the package in question unusable or mostly so > Control: affects -1 src:requests src:qgis > >

Processed (with 1 error): retitle 978749 bound on python3-chardet < 3.1.0 prevents install & build

2020-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 978749 bound on python3-chardet < 3.1.0 prevents install & build Bug #978749 [src:requests] requests: circular dependency makes requests unbuildable Changed Bug title to 'bound on python3-chardet < 3.1.0 prevents install & build' from

Bug#978749: requests: circular dependency makes requests unbuildable

2020-12-31 Thread Thomas Goirand
On 12/31/20 1:25 PM, Sebastian Ramacher wrote: > Hi Thomas > > On 2020-12-31 13:06:37 +0100, Thomas Goirand wrote: >> Hi Sebastian, >> >> I'm challenging the fact that a circular dependency is a problem for >> arch:all packages. At least, it shouldn't be an RC bug, IMO. > > If packages cannot be

Bug#978616: mediastreamer2: doesn't build correct libraries with cmake?

2020-12-31 Thread Gianfranco Costamagna
On Wed, 30 Dec 2020 17:18:41 +0100 Bernhard Schmidt wrote: > Dear Gianfranco, > > Thanks for filing this bug report. I’m away for the next couple of days and > could not check, but wouldn’t just patching the pkgconfig file (your second > option) be a lot easier? Upstream merged both libraries

Processed: severity of 978753 is normal

2020-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 978753 normal Bug #978753 [src:linux] usercopy: Kernel memory exposure attempt Bug #978752 [src:linux] usercopy: Kernel memory exposure attempt Severity set to 'normal' from 'critical' Severity set to 'normal' from 'critical' > thanks

Bug#978437: geoclue-2.0: regression in 2.5.7-1, no geolocation returned

2020-12-31 Thread gregor herrmann
On Thu, 31 Dec 2020 03:48:25 +0100, Laurent Bigonville wrote: > The following line is actually the real problem, I did all my tests on > laptop with wifi cards, I just tried on my desktop and I get the same error > (and timeout as you) > > (geoclue:10479): Geoclue-WARNING **: 16:26:35.098: Failed

Bug#975793: marked as done (libsignon-glib: FTBFS: make[3]: *** No rule to make target '/usr/share/dbus-1/interfaces/com.google.code.AccountsSSO.SingleSignOn.AuthService.xml', needed by 'sso-auth-serv

2020-12-31 Thread Debian Bug Tracking System
Your message dated Thu, 31 Dec 2020 13:48:36 + with message-id and subject line Bug#975793: fixed in libsignon-glib 1.15-1 has caused the Debian Bug report #975793, regarding libsignon-glib: FTBFS: make[3]: *** No rule to make target

Processed: Re: Bug#978753: usercopy: Kernel memory exposure attempt

2020-12-31 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + moreinfo Bug #978753 [src:linux] usercopy: Kernel memory exposure attempt Bug #978752 [src:linux] usercopy: Kernel memory exposure attempt Added tag(s) moreinfo. Added tag(s) moreinfo. -- 978752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978752

Bug#978753: usercopy: Kernel memory exposure attempt

2020-12-31 Thread Salvatore Bonaccorso
Control: tags -1 + moreinfo Hi Markus, Thanks for your report. On Thu, Dec 31, 2020 at 12:45:47PM +0200, Markus Bäcklund wrote: > Package: src:linux-image-4.19.0-13-amd64 > Version: 4.19.160-2 > Severity: critical > Justification: breaks the whole system > > > > -- Package-specific info: >

Bug#977552: marked as done (gnutls28: Time bomb in testpkcs11.sh triggered)

2020-12-31 Thread Debian Bug Tracking System
Your message dated Thu, 31 Dec 2020 13:19:32 + with message-id and subject line Bug#977552: fixed in gnutls28 3.7.0-5 has caused the Debian Bug report #977552, regarding gnutls28: Time bomb in testpkcs11.sh triggered to be marked as done. This means that you claim that the problem has been

Bug#973651: marked as done (libqb-tools: missing Breaks+Replaces: libqb-dev (<< 2))

2020-12-31 Thread Debian Bug Tracking System
Your message dated Thu, 31 Dec 2020 13:19:44 + with message-id and subject line Bug#973651: fixed in libqb 2.0.2-1 has caused the Debian Bug report #973651, regarding libqb-tools: missing Breaks+Replaces: libqb-dev (<< 2) to be marked as done. This means that you claim that the problem has

Processed: tagging 975793

2020-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 975793 + pending Bug #975793 [src:libsignon-glib] libsignon-glib: FTBFS: make[3]: *** No rule to make target '/usr/share/dbus-1/interfaces/com.google.code.AccountsSSO.SingleSignOn.AuthService.xml', needed by 'sso-auth-service-gen.c'.

Bug#974608: gthumb uses internal libexiv2 functions to get the user comment

2020-12-31 Thread Martin-Éric Racine
Package: gthumb Version: 3:3.8.3-0.1 Followup-For: Bug #974608 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Fixed upstream 1 hour ago: https://gitlab.gnome.org/GNOME/gthumb/-/commit/3bdb4f94ba37b410ac07c25b5c83e587b55482fd See also: https://gitlab.gnome.org/GNOME/gthumb/-/issues/137

Processed: tagging 974608

2020-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 974608 + fixed-upstream Bug #974608 [gthumb] gthumb uses internal libexiv2 functions to get the user comment Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 974608:

Bug#978272: marked as done (python-xopen: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

2020-12-31 Thread Debian Bug Tracking System
Your message dated Thu, 31 Dec 2020 12:39:39 + with message-id and subject line Bug#978272: fixed in python-xopen 1.0.1-2 has caused the Debian Bug report #978272, regarding python-xopen: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 to be marked as

Processed: merge 978752 978753 (duplicate reports)

2020-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 978752 978753 Bug #978752 [src:linux] usercopy: Kernel memory exposure attempt Bug #978753 [src:linux] usercopy: Kernel memory exposure attempt Merged 978752 978753 > thanks Stopping processing here. Please contact me if you need

Processed: Re: Bug#978753: usercopy: Kernel memory exposure attempt

2020-12-31 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:linux 4.19.160-2 Bug #978753 [src:linux-image-4.19.0-13-amd64] usercopy: Kernel memory exposure attempt Warning: Unknown package 'src:linux-image-4.19.0-13-amd64' Bug reassigned from package 'src:linux-image-4.19.0-13-amd64' to 'src:linux'. No

Bug#978753: usercopy: Kernel memory exposure attempt

2020-12-31 Thread Andrei POPESCU
Control: reassign -1 src:linux 4.19.160-2 On Jo, 31 dec 20, 12:45:47, Markus Bäcklund wrote: > Package: src:linux-image-4.19.0-13-amd64 > Version: 4.19.160-2 > Severity: critical > Justification: breaks the whole system > > > > -- Package-specific info: > ** Kernel log: boot messages should be

Bug#978749: requests: circular dependency makes requests unbuildable

2020-12-31 Thread Sebastian Ramacher
Hi Thomas On 2020-12-31 13:06:37 +0100, Thomas Goirand wrote: > Hi Sebastian, > > I'm challenging the fact that a circular dependency is a problem for > arch:all packages. At least, it shouldn't be an RC bug, IMO. If packages cannot be built on the buildds, they are RC-buggy. > > If the

Bug#978753: usercopy: Kernel memory exposure attempt

2020-12-31 Thread Markus Bäcklund
Hello, It probably was src:linux because it was in the original bug report I submitted a couple of minutes earlier. I included everything reportbug wanted me to include in the report. I don't know if I can run the reportbug anymore, since I am now upgrading from 10 to 11. Kind regards,

Bug#976891: update

2020-12-31 Thread Hans-Christoph Steiner
fastboot is getting pretty close to working on amd64: https://salsa.debian.org/eighthave/android-platform-system-core/-/jobs/1297944

Bug#978749: requests: circular dependency makes requests unbuildable

2020-12-31 Thread Thomas Goirand
Hi Sebastian, I'm challenging the fact that a circular dependency is a problem for arch:all packages. At least, it shouldn't be an RC bug, IMO. If the problem is bootstraping (which isn't a problem, since that's arch:all), then a wishlist bug against requests so that it implements the "nodoc"

Bug#978753: usercopy: Kernel memory exposure attempt

2020-12-31 Thread Andrei POPESCU
On Jo, 31 dec 20, 12:45:47, Markus Bäcklund wrote: > Package: src:linux-image-4.19.0-13-amd64 > Version: 4.19.160-2 > Severity: critical > Justification: breaks the whole system Hello, What package did you specify to reportbug? I'm asking because 'src:linux-image-4.19.0-13-amd64' doesn't exist

Processed: affects 978739

2020-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 978739 src:bleachbit src:hdmf src:isbg src:kytos-utils > src:python-discogs-client Bug #978739 [chardet] chardet: Upgrading python3-chardet breaks many packages Added indication that 978739 affects src:bleachbit, src:hdmf, src:isbg,

Processed: tagging 978274

2020-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 978274 + pending Bug #978274 [src:bepasty] bepasty: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#963497: not a bug for that version

2020-12-31 Thread Russell Coker
close 963497 thanks Run "setsebool allow_execmem 1" before running certbot and it will be fine. After running certbot you can run "setsebool allow_execmem 0". Or you could run "setsebool -P allow_execmem 1" to make the change continue to apply after a reboot. The 2:2.20161023.1-9 policy

Bug#963495: not a bug

2020-12-31 Thread Russell Coker
close 963495 thanks Run "setsebool allow_execmem 1" before running certbot and it will be fine. After running certbot you can run "setsebool allow_execmem 0". Or you could run "setsebool -P allow_execmem 1" to make the change continue to apply after a reboot. There is no good solution to

Bug#978753: usercopy: Kernel memory exposure attempt

2020-12-31 Thread Markus Bäcklund
Package: src:linux-image-4.19.0-13-amd64 Version: 4.19.160-2 Severity: critical Justification: breaks the whole system -- Package-specific info: ** Kernel log: boot messages should be attached -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500,

Bug#978752: usercopy: Kernel memory exposure attempt

2020-12-31 Thread Markus Bäcklund
Package: src:linux Version: 4.19.160-2 Severity: critical Justification: breaks the whole system -- Package-specific info: ** Kernel log: boot messages should be attached -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500,

Bug#978640: undefined symbol: _ZTIN3fmt2v612format_errorE

2020-12-31 Thread Utkarsh Gupta
Hi Hubert, On Thu, Dec 31, 2020 at 3:21 AM Hubert Chathi wrote: > binNMU requested at > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978722 > > Apparently waiting for an update to spdlog. Awesome, thanks for processing this! - u

Bug#968413: marked as done (failes to build on ppc64el with binutils 2.35)

2020-12-31 Thread Debian Bug Tracking System
Your message dated Thu, 31 Dec 2020 10:18:27 + with message-id and subject line Bug#968413: fixed in oss4 4.2-build2017-2 has caused the Debian Bug report #968413, regarding failes to build on ppc64el with binutils 2.35 to be marked as done. This means that you claim that the problem has

Processed: Re: Bug#978749: reportbug: Updating python3-chardet to 4.0.0 wants to remove reportbug

2020-12-31 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:requests 2.25.1+dfsg-1 Bug #978749 [reportbug] reportbug: Updating python3-chardet to 4.0.0 wants to remove reportbug Bug reassigned from package 'reportbug' to 'src:requests'. No longer marked as found in versions reportbug/7.9.0. Ignoring request

Processed: found 978071 in 2.9-3, tagging 978071

2020-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 978071 2.9-3 Bug #978071 {Done: Thorsten Alteholz } [src:entropybroker] entropybroker FTBFS with Crypto++ 8.3.0 Marked as found in versions entropybroker/2.9-3. > tags 978071 + sid bullseye Bug #978071 {Done: Thorsten Alteholz }

Processed: affects 975747

2020-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 975747 zipalign Bug #975747 [android-libbacktrace] android-platform-build: FTBFS: ld: /usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined reference to `unwindstack::RemoteMaps::GetMapsFile[abi:cxx11]() const' Added indication

Bug#978518: marked as done (openjdk-14: non-standard gcc/g++ used for build (gcc-9))

2020-12-31 Thread Debian Bug Tracking System
Your message dated Thu, 31 Dec 2020 08:48:58 + with message-id and subject line Bug#978518: fixed in openjdk-14 14.0.2+12-2 has caused the Debian Bug report #978518, regarding openjdk-14: non-standard gcc/g++ used for build (gcc-9) to be marked as done. This means that you claim that the

Processed: upstream only supports x86

2020-12-31 Thread Debian Bug Tracking System
Processing control commands: > severity -1 wishlist Bug #963058 [src:android-platform-art] android-platform-art ftbfs on arm64 Severity set to 'wishlist' from 'serious' > retitle -1 port android-platform-art to ARM, etc. Bug #963058 [src:android-platform-art] android-platform-art ftbfs on arm64

Bug#963058: upstream only supports x86

2020-12-31 Thread Hans-Christoph Steiner
Control: severity -1 wishlist Control: retitle -1 port android-platform-art to ARM, etc.

Bug#963058: [Android-tools-devel] Bug#963058: still ftbfs on arm64

2020-12-31 Thread Hans-Christoph Steiner
It looks like upstream does not support anything but x86, and they've added assembly code. So unless someone steps up to port that to ARM, the ARM binaries will be removed.

Processed: still ftbfs on arm64

2020-12-31 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #963058 {Done: Hans-Christoph Steiner } [src:android-platform-art] android-platform-art ftbfs on arm64 '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

Bug#975747: android/libbacktrace.so.0: undefined reference to `unwindstack::RemoteMaps::GetMapsFile[abi:cxx11]() const'

2020-12-31 Thread Damyan Ivanov
Package: android-libbacktrace Version: 1:10.0.0+r36-1~stage1.3 Followup-For: Bug #975747 Control: affects -1 zipalign This seems to render zipalign unusable: $ zipalign zipalign: symbol lookup error: /usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined symbol:

Bug#963058: still ftbfs on arm64

2020-12-31 Thread Matthias Klose
Control: reopen -1 Control: found -1 10.0.0+r36-1~stage1 still ftbfs everywhere on non-ix86