Processed: forcibly merging 977876 973506

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 977876 973506 Bug #977876 {Done: Matthias Klumpp } [packagekit] packagekit-offline-update.service not enabled, not offline updates applied Bug #973506 [packagekit] packagekit: offline system update don't work after upgrading from

Bug#977901: chromium: Inconsistent SEGV

2020-12-22 Thread Boyd Stephen Smith Jr.
On Tuesday, December 22, 2020 10:47:31 PM CST Boyd Stephen Smith Jr. wrote: > All my extensions were pulled down during the Google Sync and ran fine on 87 > for roughly an hour -- that's twice as long as my longest browser session > for version 87 on the old profile. > > I still convinced this is

Bug#977901: chromium: Inconsistent SEGV

2020-12-22 Thread Boyd Stephen Smith Jr.
On Tuesday, December 22, 2020 5:26:04 PM CST Boyd Stephen Smith Jr. wrote: > On Tue, 22 Dec 2020 23:43:23 +0100 Michel Le Bihan wrote: > > I was not able to reproduce those crashes. > > That's unfortunate. I'm up to 50 just today. I'm probably going to have to > downgrade to 83 at least until

Bug#957037: biboumi: ftbfs with GCC-10

2020-12-22 Thread Vasudev Kamath
Michel Le Bihan writes: > Le mardi 22 décembre 2020 à 17:35 +0530, Vasudev Kamath a écrit : >> Jonas Smedegaard writes: >> >> > Quoting Michel Le Bihan (2020-12-20 17:15:29) >> > > Le dimanche 20 décembre 2020 à 16:50 +0100, Jonas Smedegaard a >> > > écrit : >> > > > Quoting Michel Le Bihan

Bug#976731: marked as done (firefox: FTBFS on arm64 (explicit specialization in non-namespace scope ‘class js::wasm::BaseRegAlloc’))

2020-12-22 Thread Debian Bug Tracking System
Your message dated Wed, 23 Dec 2020 12:34:27 +0900 with message-id <20201223033427.gpy6we6mysc2v...@glandium.org> and subject line Re: Bug#976731: firefox: FTBFS on arm64 (explicit specialization in non-namespace scope ‘class js::wasm::BaseRegAlloc’) has caused the Debian Bug report #976731,

Bug#975455: devtodo: failing autopkgtests with grep 3.6

2020-12-22 Thread Carlos Henrique Lima Melara
Hi, Adrian. On Sun, Dec 20, 2020 at 06:35:57PM +0200, Adrian Bunk wrote: > On Sun, Nov 22, 2020 at 03:20:04PM -0300, Carlos Henrique Lima Melara wrote: > >... > > Thanks to let me know. I did see this problem yesterday but didn't have > > time to fix. > > > > I'll be fixing it today and

Bug#977901: chromium: Inconsistent SEGV

2020-12-22 Thread David Purton
I can confirm that this bug is affecting me since upgrading to 87.0.4280.88-0.2 in Testing today. David -- David Purton :email: dcpur...@marshwiggle.net :phone: 0413 626 862

Bug#973677: libkscreenlocker5: No login dialog is shown, user cannot unlock session

2020-12-22 Thread Norbert Preining
tags 973677 + unreproducible moreinfo severity 973677 normal thanks On Tue, 03 Nov 2020, Mikko Korhonen wrote: > but happens every time and at any unlock, not just on dehibernation and with > a > single monitor: only the cursor is shown on a black screen and there is no > way to login. > As a

Processed: your mail

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 977927 grave Bug #977927 [mitmproxy] DistributionNotFound: 'hyperframe>=6.0' due to missing dependencies Severity set to 'grave' from 'important' > merge 977926 977927 Bug #977926 [mitmproxy] Missing required dependencies Bug #977927

Processed (with 1 error): your mail

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 977926 977927 Bug #977926 [mitmproxy] Missing required dependencies Unable to merge bugs because: severity of #977927 is 'important' not 'grave' Failed to merge 977926: Did not alter merged bugs. > End of message, stopping processing here.

Bug#977926: Missing required dependencies

2020-12-22 Thread Faidon Liambotis
Package: mitmproxy Version: 5.3.0-1 Severity: grave Installing mitmproxy in a clean sid chroot, and running it (with no arguments) results into a large backtrace that ends with... pkg_resources.DistributionNotFound: The 'hyperframe>=6.0' distribution was not found and is required by mitmproxy

Bug#977901: chromium: Inconsistent SEGV

2020-12-22 Thread Boyd Stephen Smith Jr.
On Tue, 22 Dec 2020 23:43:23 +0100 Michel Le Bihan wrote: > Installing `chromium-dbgsym` should be enough. Please run Chromium with > the `--debug` flag like: `chromium --debug`. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963711#10 Chromium crashes on startup if I use the "-g" or

Bug#943462: [polkit-kde-agent-1] Fails to start with elogind

2020-12-22 Thread Norbert Preining
Hi Alex, On Fri, 25 Oct 2019, Alex Volkov wrote: > Version: 4:5.14.5-1 > Severity: serious This is for a very old version of Plasma. Could you please try the current 5.20.4 from unstable. We can surely not debug this for stable. Thanks Norbert -- PREINING Norbert

Bug#942078: [high quality bug] baloo crash, can't recover; forced reindex does not fix; unusable via dolphin C-f

2020-12-22 Thread Norbert Preining
Hi Nicholas, On Wed, 09 Oct 2019, Nicholas D Steeves wrote: > Version: 5.54.0-1 > Severity: serious > Justification: poor experience will cause user to give up on baloo; worse > than GNOME Can you reproduce this with current frameworks 5.77 in unstable? Does it always crash at the same file

Bug#972070: marked as done (bluez-obexd: Failure to browse files, Failed to execute program org.bluez.obex: No such file or directory)

2020-12-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Dec 2020 23:00:11 + with message-id and subject line Bug#972070: fixed in bluez 5.55-2 has caused the Debian Bug report #972070, regarding bluez-obexd: Failure to browse files, Failed to execute program org.bluez.obex: No such file or directory to be marked as

Bug#976887: marked as done (texlive-base: Should not migrate to testing for now.)

2020-12-22 Thread Debian Bug Tracking System
Your message dated Wed, 23 Dec 2020 07:54:19 +0900 with message-id and subject line Re: Bug#976887: texlive-base: Should not migrate to testing for now. has caused the Debian Bug report #976887, regarding texlive-base: Should not migrate to testing for now. to be marked as done. This means that

Bug#977901: chromium: Inconsistent SEGV

2020-12-22 Thread Michel Le Bihan
Hello, Installing `chromium-dbgsym` should be enough. Please run Chromium with the `--debug` flag like: `chromium --debug`. You can mix it with your other flags like `chromium --debug --incognito`. In the GDB shell, please enter `run`. Chromium should start then. You can then use Chromium, but it

Bug#977918: vm: Package vm prevents clean emacs27 start

2020-12-22 Thread Dirk Eddelbuettel
Package: vm Version: 8.2.0b-6 Severity: serious Using the (awesome !!) newer emacs 27.1, I am having issues with package vm. One issue is that on startup, a message 'Package cl is deprecated' is shown. Startup appears to finish in interactive, but does not in daemon

Bug#977921: boost1.74: context asm files not built on mipsel

2020-12-22 Thread Adrian Bunk
Source: boost1.74 Version: 1.74.0-3 Severity: serious Tags: ftbfs Control: affects -1 src:nix libboost-coroutine1.74.0 libboost-fiber1.74.0 https://buildd.debian.org/status/fetch.php?pkg=nix=mipsel=2.3.7%2Bdfsg1-1%2Bb1=1608526707=0 ... /usr/bin/ld: src/libutil/serialise.o: in function

Processed: boost1.74: context asm files not built on mipsel

2020-12-22 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:nix libboost-coroutine1.74.0 libboost-fiber1.74.0 Bug #977921 [src:boost1.74] boost1.74: context asm files not built on mipsel Added indication that 977921 affects src:nix, libboost-coroutine1.74.0, and libboost-fiber1.74.0 -- 977921:

Bug#977920: python3-distutils and python3-lib2to3 depend on unavailable version of python3:any

2020-12-22 Thread Aurelien Jarno
Source: python3-stdlib-extensions Version: 3.9.1-1 Severity: serious | # apt-get install python3-distutils | 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

Processed: your mail

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 977901 grave Bug #977901 [chromium] chromium: Inconsistent SEGV Severity set to 'grave' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 977901:

Bug#977502: marked as done (podman,golang-github-containers-common: both ship /usr/share/man/man5/containers-mounts.conf.5.gz)

2020-12-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Dec 2020 22:03:56 + with message-id and subject line Bug#977502: fixed in libpod 2.1.1+dfsg1-3 has caused the Debian Bug report #977502, regarding podman,golang-github-containers-common: both ship /usr/share/man/man5/containers-mounts.conf.5.gz to be marked as

Bug#977502: marked as pending in libpod

2020-12-22 Thread Reinhard Tartler
Control: tag -1 pending Hello, Bug #977502 in libpod 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#977502 marked as pending in libpod

2020-12-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #977502 [podman,golang-github-containers-common] podman,golang-github-containers-common: both ship /usr/share/man/man5/containers-mounts.conf.5.gz Added tag(s) pending. -- 977502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977502 Debian

Processed: Bug#977502 marked as pending in libpod

2020-12-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #977502 [podman,golang-github-containers-common] podman,golang-github-containers-common: both ship /usr/share/man/man5/containers-mounts.conf.5.gz Ignoring request to alter tags of bug #977502 to the same tags previously set -- 977502:

Bug#977502: marked as pending in libpod

2020-12-22 Thread Reinhard Tartler
Control: tag -1 pending Hello, Bug #977502 in libpod 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#977919: vm: Mail quoting no longer works in emacs27

2020-12-22 Thread Dirk Eddelbuettel
Package: vm Version: 8.2.0b-6 Severity: serious As per the previous bug report emacs27 and vm are having some issues. Another wart is that mail replies no longer work. Hitting 'F' for a quoted reply inserts the full email including headers _unquoted_ and _unindented_ with an error message

Bug#977103: marked as done (chromium: FTBFS on armhf: error: write to reserved register 'R7')

2020-12-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Dec 2020 22:45:59 +0100 with message-id and subject line Re: Bug#977103: chromium: FTBFS on armhf: error: write to reserved register 'R7' has caused the Debian Bug report #977103, regarding chromium: FTBFS on armhf: error: write to reserved register 'R7' to be marked

Bug#977918: vm: Package vm prevents clean emacs27 start

2020-12-22 Thread Dirk Eddelbuettel
Package: vm Version: 8.2.0b-6 Severity: serious Using the (awesome !!) newer emacs 27.1, I am having issues with package vm. One issue is that on startup, a message 'Package cl is deprecated' is shown. Startup appears to finish in interactive, but does not in daemon mode which is how I used to

Bug#969372: INFO: Bug#969372: uwsgi-emperor: SysV init script does nothing

2020-12-22 Thread Rens Houben
Okay, this is quick-and-dirty because I didn't have a great deal of time and I'm not /that/ great with systemd service files to begin with. --- [Unit] Description=uWSGI Emperor After=syslog.target [Service] ExecStart=/usr/bin/uwsgi --ini /etc/uwsgi-emperor/emperor.ini RuntimeDirectory=uwsgi

Bug#977876: marked as done (packagekit-offline-update.service not enabled, not offline updates applied)

2020-12-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Dec 2020 21:35:31 + with message-id and subject line Bug#977876: fixed in packagekit 1.2.2-2 has caused the Debian Bug report #977876, regarding packagekit-offline-update.service not enabled, not offline updates applied to be marked as done. This means that you

Bug#957082: marked as done (cfengine3: ftbfs with GCC-10)

2020-12-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Dec 2020 22:21:25 +0100 with message-id <60cbae9d-5aca-53f6-ed8a-598a00f17...@debian.org> and subject line Re: cfengine3: ftbfs with GCC-10 has caused the Debian Bug report #957082, regarding cfengine3: ftbfs with GCC-10 to be marked as done. This means that you claim

Bug#958880: marked as done (mplayer: package neglected)

2020-12-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Dec 2020 22:22:07 +0100 with message-id <3246ee46-4227-3992-e7fb-e52001514...@debian.org> and subject line Re: mplayer: package neglected has caused the Debian Bug report #958880, regarding mplayer: package neglected to be marked as done. This means that you claim that

Bug#943462: [polkit-kde-agent-1] Fails to start with elogind

2020-12-22 Thread Paul Gevers
Hi all, On Fri, 25 Oct 2019 07:04:40 +0500 Alex Volkov wrote: > I'm using elogind 239.3+20190131-1+debian1 and the agent fails to start > at the kde launch with the following diagnostics: Any progress on this? The bullseye freeze is approaching. Paul OpenPGP_signature Description: OpenPGP

Bug#942078: [high quality bug] baloo crash, can't recover; forced reindex does not fix; unusable via dolphin C-f

2020-12-22 Thread Paul Gevers
Hi all, On Wed, 09 Oct 2019 18:53:25 -0400 Nicholas D Steeves wrote: > Recently baloo has been crashing whenever I log in. Today I decided it > was a persistent and serious enough problem that a serious bug was > warranted. I've attached the backtrace produced by drkonqi. Here is > some

Processed: r-cran-arsenal: autopkgtest failure on several architectures

2020-12-22 Thread Debian Bug Tracking System
Processing control commands: > block 975859 by -1 Bug #975859 {Done: Paul Gevers } [src:r-cran-haplo.stats] src:r-cran-haplo.stats: fails to migrate to testing for too long: Depends on non-migrating package 975859 was not blocked by any bugs. 975859 was not blocking any bugs. Added blocking

Bug#976891: fastboot exits with "fake placeholder until fastboot builds" message

2020-12-22 Thread Hans-Christoph Steiner
Thanks for jumping in Roger! I reviewed it with cdesai, and we thought those libraries were not used on the "host" version, only when built as part of Android OS. I do think libfec would be useful if someone wants to package adbd for Debian. The Google Android Tools builds do not include

Bug#977915: r-cran-arsenal: autopkgtest failure on several architectures

2020-12-22 Thread Adrian Bunk
Source: r-cran-arsenal Version: 3.5.0-2 Severity: serious Control: block 975859 by -1 https://tracker.debian.org/pkg/r-cran-arsenal Issues preventing migration: autopkgtest for r-cran-arsenal/3.5.0-2: amd64: Pass, arm64: Regression ♻ , armhf: Pass, i386: Regression ♻ , ppc64el: Regression ♻

Processed: tagging 956762

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 956762 + pending Bug #956762 [autokey-gtk] autokey-gtk: Depends on deprecated libappindicator Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 956762:

Processed: tagging 974207

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 974207 + upstream Bug #974207 [src:psi-plus] psi-plus: FTBFS with Qt 5.15 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 974207:

Processed: tagging 956772

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 956772 + pending Bug #956772 [src:hime] hime: Depends on deprecated libappindicator Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 956772:

Processed: tagging 956782

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 956782 + pending Bug #956782 [src:zeal] zeal: Build-Depends (unnecessarily?) on deprecated libappindicator Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 956782:

Processed: tagging 956774

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 956774 + pending Bug #956774 [src:kylin-burner] kylin-burner: Depends on deprecated libappindicator Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 956774:

Bug#934242: crystalhd: unusable without (available and properly working) firmware

2020-12-22 Thread Paul Gevers
affects 934242 src:kylin-video user release.debian@packages.debian.org usertag 934242 bullseye-will-remove Hi, On 21-12-2020 23:32, Jonas Smedegaard wrote: > Yes, there are still packages depending on it: Someone needs to work > actively with those still believing the library is more than

Processed (with 5 errors): Re: crystalhd: unusable without (available and properly working) firmware

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 934242 src:kylin-video Bug #934242 [src:crystalhd] crystalhd: unusable without (available and properly working) firmware Added indication that 934242 affects src:kylin-video > user release.debian@packages.debian.org Setting user to

Processed: tagging 956778

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 956778 + pending Bug #956778 [src:parcellite] parcellite: Depends on deprecated libappindicator Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 956778:

Bug#956766: gcin: Build-Depends (unnecessarily?) on deprecated libappindicator

2020-12-22 Thread Adrian Bunk
On Wed, Apr 15, 2020 at 09:23:06AM +0100, Simon McVittie wrote: > Source: gcin > Version: 2.8.8+dfsg1-1 > Tags: sid bullseye > Severity: important > Control: block 895037 by -1 > User: pkg-ayatana-de...@lists.alioth.debian.org > Usertags: ayatana-appindicator > > This package Build-Depends on

Bug#976846: marked as done (python3-stdlib-extensions build depends on non-default python3 version)

2020-12-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Dec 2020 20:18:36 + with message-id and subject line Bug#976846: fixed in python3-stdlib-extensions 3.9.1-1 has caused the Debian Bug report #976846, regarding python3-stdlib-extensions build depends on non-default python3 version to be marked as done. This means

Processed: tagging 972767

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 972767 + patch Bug #972767 [src:frr] frr ftbfs with python3.9 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 972767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972767 Debian Bug

Processed: severity of 921005 is serious

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 921005 serious Bug #921005 [gcin] Missing manual dependency for package gcin on libappindicator3-1 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 921005:

Processed: Workaround for the BTS not yet properly handling bookworm

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 954812 important Bug #954812 [src:pythonmagick] pythonmagick: autopkgtest regression: cannot import name '_PythonMagick' Severity set to 'important' from 'serious' > severity 975926 important Bug #975926 [enigmail] enigmail should not

Processed: block 974546 with 974856

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 974546 with 974856 Bug #974546 [src:klatexformula] klatexformula FTBFS: error: invalid use of incomplete type ‘class QPainterPath’ 974546 was not blocked by any bugs. 974546 was not blocking any bugs. Added blocking bug(s) of 974546:

Processed: tagging 975823

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 975823 + upstream Bug #975823 [src:rally-openstack] rally-openstack: FTBFS: AttributeError: module 'kubernetes.client.api_client' has no attribute 'models' Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you

Processed: retitle 975822 to pyramid-jinja2: Missing build dependency on python3-webtest

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 975822 pyramid-jinja2: Missing build dependency on python3-webtest Bug #975822 [src:pyramid-jinja2] pyramid-jinja2: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.9" returned exit code 13 Changed Bug title to

Processed: bug 975817 is forwarded to https://github.com/oVirt/mom/commit/655d6b36f9f80ced1e411bc8504110a261939808

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 975817 > https://github.com/oVirt/mom/commit/655d6b36f9f80ced1e411bc8504110a261939808 Bug #975817 [src:mom] mom: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 Set Bug forwarded-to-address to

Processed: tagging 975810

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 975810 + upstream Bug #975810 [src:fonts-pecita] fonts-pecita: FTBFS: Error: Validation error Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 975810:

Processed: tagging 975801

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 975801 + upstream Bug #975801 [src:python-aioxmpp] python-aioxmpp: FTBFS: TypeError: 'Lock' object is not iterable Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 975801:

Processed: Fixed in 10.5.0

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 975790 fixed-upstream Bug #975790 [src:ironic-inspector] ironic-inspector: FTBFS: sqlalchemy.exc.ArgumentError: column object 'temp_started_at' already assigned to table 'nodes' Added tag(s) fixed-upstream. > thanks Stopping processing

Processed: Move where the problem is

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 975747 android-libbacktrace 1:10.0.0+r36-1~stage1 Bug #975747 [src:android-platform-build] android-platform-build: FTBFS: ld: /usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined reference to

Processed: tagging 975753

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 975753 + fixed Bug #975753 {Done: Sylvestre Ledru } [src:rust-universal-hash] rust-universal-hash: FTBFS: build-dependency not installable: librust-generic-array-0.12+default-dev Added tag(s) fixed. > thanks Stopping processing here.

Bug#977912: fdroidserver: autopkgtest regression in testing: symbol lookup error

2020-12-22 Thread Paul Gevers
Source: fdroidserver Version: 1.1.10-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent change in testing the autopkgtest of your package started to fail. I copied some of the output at the bottom

Processed: bug 975789 is forwarded to https://github.com/go-acme/lego/pull/1176

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 975789 https://github.com/go-acme/lego/pull/1176 Bug #975789 [src:golang-github-xenolf-lego] golang-github-xenolf-lego: FTBFS: src/github.com/go-acme/lego/providers/dns/inwx/inwx.go:85:6: assignment mismatch: 1 variable but

Processed: retitle 975787 to golang-github-howeyc-fsnotify: Frequent FTBFS due to flaky test

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 975787 golang-github-howeyc-fsnotify: Frequent FTBFS due to flaky test Bug #975787 [src:golang-github-howeyc-fsnotify] golang-github-howeyc-fsnotify: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4

Bug#977911: debian-archive-keyring: bullseye archive signing key

2020-12-22 Thread Adam D. Barratt
Source: debian-archive-keyring Version: 2019.1 Severity: serious X-Debbugs-Cc: ftpmas...@debian.org, debian-rele...@lists.debian.org Hi, We need a new archive signing key for bullseye, so that we can include it in the release. Regards, Adam

Bug#977910: debian-archive-keyring: bullseye SRM key

2020-12-22 Thread Adam D. Barratt
Source: debian-archive-keyring Version: 2019.1 Severity: serious X-Debbugs-Cc: debian-rele...@lists.debian.org Hi, We need an SRM key for bullseye, so that we can include it in the release. Regards, Adam

Bug#939527: marked as done (vcdimager contains one file with different license)

2020-12-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Dec 2020 18:38:29 + with message-id and subject line Bug#939527: fixed in vcdimager 2.0.1+dfsg-4 has caused the Debian Bug report #939527, regarding vcdimager contains one file with different license to be marked as done. This means that you claim that the problem

Bug#976886: movim: diff for NMU version 0.17.1-1.1

2020-12-22 Thread Robin Gustafsson
Control: tags 976886 + patch Control: tags 976886 + pending Dear maintainer, I've prepared an NMU for movim (versioned as 0.17.1-1.1). The diff is attached to this message. I require a sponsor to have it uploaded. Regards. diff -Nru movim-0.17.1/debian/autoload.php

Bug#976891: fastboot exits with "fake placeholder until fastboot builds" message

2020-12-22 Thread Roger Shimizu
I'm trying to restore fastboot back to build for 1:10.0.0+r36-1~stage1.3 however, seems there're a few new dependencies. one is android-libfec inside src:android-platform-system-extras I already uploaded to NEW queue. another two is: - https://android.googlesource.com/platform/external/avb -

Bug#977906: marked as done (libcollada-parser1d: missing Breaks+Replaces: libcollada-parser-dev (<< 1.12.13-2))

2020-12-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Dec 2020 18:04:21 + with message-id and subject line Bug#977906: fixed in ros-collada-urdf 1.12.13-3 has caused the Debian Bug report #977906, regarding libcollada-parser1d: missing Breaks+Replaces: libcollada-parser-dev (<< 1.12.13-2) to be marked as done. This

Bug#977905: marked as done (librosbag-storage4d: missing Breaks+Replaces: librosbag-storage-dev (<< 1.15.9+ds1-5))

2020-12-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Dec 2020 18:04:26 + with message-id and subject line Bug#977905: fixed in ros-ros-comm 1.15.9+ds1-6 has caused the Debian Bug report #977905, regarding librosbag-storage4d: missing Breaks+Replaces: librosbag-storage-dev (<< 1.15.9+ds1-5) to be marked as done. This

Bug#959905: marked as done (ydotool: FTBFS: relocation R_X86_64_PC32 against symbol `_ZTISt13runtime_error@@GLIBCXX_3.4' can not be used when making a shared object; recompile with -fPIC)

2020-12-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Dec 2020 18:04:37 + with message-id and subject line Bug#959905: fixed in ydotool 0.1.8-3 has caused the Debian Bug report #959905, regarding ydotool: FTBFS: relocation R_X86_64_PC32 against symbol `_ZTISt13runtime_error@@GLIBCXX_3.4' can not be used when making a

Bug#977908: mk-configure: Fails with 'Settings for gcc-10.2.1 is not available'

2020-12-22 Thread Robert Luberda
Package: mk-configure Version: 0.35.0-1 Severity: serious Justification: causes FTBFS of libmaa It looks like mk-configure fails to recognize gcc-10.2.1 (which migrated to testing almost a week ago), what causes my libmaa package to FTBFS, see:

Bug#977890: libcinnamon-menu-3-0: Upgrade 4.6.1-1->4.8.2-2 causes segfault when launching any application

2020-12-22 Thread Julio C. Ortega
Package: gir1.2-cmenu-3.0 Followup-For: Bug #977890 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgraded libcinnamon-menu-3-0 and gir1.2-cmenu-3.0 4.6.1-1->4.8.2-2 and cinnamon-l10n from 4.6.2-1->4.8.2-2

Bug#977906: libcollada-parser1d: missing Breaks+Replaces: libcollada-parser-dev (<< 1.12.13-2)

2020-12-22 Thread Andreas Beckmann
Package: libcollada-parser1d Version: 1.12.13-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to

Bug#975372: minidlna: "rm: cannot remove '/var/log/minidlna': Is a directory" on purge

2020-12-22 Thread Alexander Gerasiov
On Sun, 20 Dec 2020 11:50:42 +0200 Adrian Bunk wrote: > this is a regression in 1.2.1+dfsg-2 that is currently in both > buster-security (which was done on top of 1.2.1+dfsg-2 that > introduced the regression, not on top of 1.2.1+dfsg-1 in buster) and > in unstable/testing (which currently

Bug#977905: librosbag-storage4d: missing Breaks+Replaces: librosbag-storage-dev (<< 1.15.9+ds1-5)

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

Processed: exaggerated severity and not a bug

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 977603 normal Bug #977603 [g++-10] cc1plus: internal compiler error: in cpp_diagnostic_at, at libcpp/errors.c:41 Severity set to 'normal' from 'grave' > close 977603 Bug #977603 [g++-10] cc1plus: internal compiler error: in

Processed: Re: [pkg-uWSGI-devel] Bug#969372: INFO: Bug#969372: uwsgi-emperor: SysV init script does nothing

2020-12-22 Thread Debian Bug Tracking System
Processing control commands: > tags -1 +help Bug #969372 {Done: Jonas Smedegaard } [uwsgi-emperor] uwsgi-emperor: SysV init script does nothing Added tag(s) help. -- 969372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969372 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#969372: [pkg-uWSGI-devel] Bug#969372: INFO: Bug#969372: uwsgi-emperor: SysV init script does nothing

2020-12-22 Thread Jonas Smedegaard
Control: tags -1 +help Quoting Rens Houben (2020-12-22 10:07:00) > The issue arose because the init script isn't so much a script as it's > a set of variables plugged into the init.d helper scripts, and /those/ > have changed drastically from Jessie to Buster and onwards to call > systemctl --

Bug#969372: INFO: Bug#969372: uwsgi-emperor: SysV init script does nothing

2020-12-22 Thread Thomas Goirand
On 12/22/20 10:07 AM, Rens Houben wrote: > I'm currently writing at least a rudimentary systemd service file for > uwsgi-emperor to see if that makes it work; I can share it once I finish > if you'd like. > > --Rens Houben. Hi Rens, Thanks for your reply and sharing of your investigations.

Bug#977900: node-autoprefixer: FTBFS: ENOENT: no such file or directory, open 'path'

2020-12-22 Thread Andreas Beckmann
Source: node-autoprefixer Version: 10.0.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, node-autoprefixer/experimental recently started to FTBFS: debian/rules binary dh binary dh_update_autotools_config dh_autoreconf dh_auto_configure

Processed: block 976886 with 977898

2020-12-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 976886 with 977898 Bug #976886 [movim] movim: Blocking transition of php-illuminate-database 976886 was not blocked by any bugs. 976886 was not blocking any bugs. Added blocking bug(s) of 976886: 977898 > thanks Stopping processing here.

Bug#977868: marked as done (osmcoastline: FTBFS in bullseye and sid)

2020-12-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Dec 2020 14:39:53 + with message-id and subject line Bug#977868: fixed in osmcoastline 2.2.4-3 has caused the Debian Bug report #977868, regarding osmcoastline: FTBFS in bullseye and sid to be marked as done. This means that you claim that the problem has been

Bug#977890: marked as done (libcinnamon-menu-3-0: Upgrade 4.6.1-1->4.8.2-2 causes segfault when launching any application)

2020-12-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Dec 2020 14:36:01 + with message-id and subject line Bug#977890: fixed in cinnamon-menus 4.8.2-3 has caused the Debian Bug report #977890, regarding libcinnamon-menu-3-0: Upgrade 4.6.1-1->4.8.2-2 causes segfault when launching any application to be marked as done.

Bug#977461: marked as done (gcc-1[01]-offload-amdgcn,gcc-1[01]-hppa64-linux-gnu: shipping unversioned binaries causes file conflicts)

2020-12-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Dec 2020 14:37:32 + with message-id and subject line Bug#977461: fixed in gcc-10 10.2.1-2 has caused the Debian Bug report #977461, regarding gcc-1[01]-offload-amdgcn,gcc-1[01]-hppa64-linux-gnu: shipping unversioned binaries causes file conflicts to be marked as

Processed: movim: diff for NMU version 0.17.1-1.1

2020-12-22 Thread Debian Bug Tracking System
Processing control commands: > tags 976886 + patch Bug #976886 [movim] movim: Blocking transition of php-illuminate-database Ignoring request to alter tags of bug #976886 to the same tags previously set > tags 976886 + pending Bug #976886 [movim] movim: Blocking transition of

Bug#977762: Bug#967027: cinnamon: uses libcroco which is unmaintained upstream

2020-12-22 Thread Norbert Preining
Hi Fabio, I saw your commit. I will do the upload in a minute. Thanks. > @Norbert: unfortunately it is not just a problem of  cinnamon not > installable in testing for a few days, the outdated breaks in > cinnamon-menus cause serious problems to all those who have installed > and updated it :(

Bug#977864: fixed in twitter-bootstrap4 4.5.2+dfsg1-4

2020-12-22 Thread Petter Reinholdtsen
[Xavier] > it is normal to find this issue in version 4.5.2+dfsg1-3 since it has > been fixed in 4.5.2+dfsg1-4! Ah, sorry for the misunderstanding. I assumed the version I was upgrading to was the latest upload in unstable, and did not notice the versions were different. It upgraded just fine

Bug#977762: Bug#967027: cinnamon: uses libcroco which is unmaintained upstream

2020-12-22 Thread Fabio Fantoni
Il 21/12/2020 10:17, Norbert Preining ha scritto: > On Mon, 21 Dec 2020, Fabio Fantoni wrote: >> @Norbert: thanks, unfortunately the migration to testing of some >> components has begun and having made a further upload of cinnamon (with >> medium urgency) will block the completion for another 5

Bug#977890: marked as pending in cinnamon-menus

2020-12-22 Thread Fabio Fantoni
Control: tag -1 pending Hello, Bug #977890 in cinnamon-menus 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#977890 marked as pending in cinnamon-menus

2020-12-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #977890 [libcinnamon-menu-3-0] libcinnamon-menu-3-0: Upgrade 4.6.1-1->4.8.2-2 causes segfault when launching any application Added tag(s) pending. -- 977890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977890 Debian Bug Tracking System

Bug#977397: marked as done (uim-el: missing *-uim in input-method-alist on Emacs 27)

2020-12-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Dec 2020 13:38:54 + with message-id and subject line Bug#977397: fixed in uim 1:1.8.8-7 has caused the Debian Bug report #977397, regarding uim-el: missing *-uim in input-method-alist on Emacs 27 to be marked as done. This means that you claim that the problem has

Bug#973459: marked as done (uim: FAIL: test-composer.scm)

2020-12-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Dec 2020 13:38:54 + with message-id and subject line Bug#973459: fixed in uim 1:1.8.8-7 has caused the Debian Bug report #973459, regarding uim: FAIL: test-composer.scm to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#977833: marked as done (librelaxng-datatype-java: fails to build source package)

2020-12-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Dec 2020 13:29:15 + with message-id <20201222132915.ga3...@layer-acht.org> and subject line Re: Bug#977856: librepository: fails to build source package has caused the Debian Bug report #977833, regarding librelaxng-datatype-java: fails to build source package to be

Bug#977856: marked as done (librepository: fails to build source package)

2020-12-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Dec 2020 13:29:15 + with message-id <20201222132915.ga3...@layer-acht.org> and subject line Re: Bug#977856: librepository: fails to build source package has caused the Debian Bug report #977856, regarding librepository: fails to build source package to be marked as

Bug#977891: opencascade: library package names do not follow SOVERSION

2020-12-22 Thread Andreas Beckmann
Source: opencascade Version: 7.5.0+dfsg1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite

Bug#977890: libcinnamon-menu-3-0: Upgrade 4.6.1-1->4.8.2-2 causes segfault when launching any application

2020-12-22 Thread Jeffrey Ratcliffe
Package: libcinnamon-menu-3-0 Version: 4.8.2-2 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgraded libcinnamon-menu-3-0 and gir1.2-cmenu-3.0

Bug#969372: INFO: Bug#969372: uwsgi-emperor: SysV init script does nothing

2020-12-22 Thread Rens Houben
Hello, I've come across the same bug while trying to set up a new service at work. After some digging (we've currently got a mishmash of Jessie and Buster systems, not all of them have been upgraded yet) I discovered that the init script, such as it is, is identical in all versions, and it is

Bug#977781: marked as done (yarnpkg: fails to download modules)

2020-12-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Dec 2020 12:50:12 + with message-id and subject line Bug#977781: fixed in node-yarnpkg 1.22.10+~cs22.25.14-1 has caused the Debian Bug report #977781, regarding yarnpkg: fails to download modules to be marked as done. This means that you claim that the problem has

  1   2   >