Bug#975129: qwt: FTBFS: qwt_painter_command.h:85:22: error: field ‘clipPath’ has incomplete type ‘QPainterPath’

Hi On Sunday, 13 December 2020 18:06:22 CET you wrote: > Please go ahead, I have been sponsoring QWT and even made the latest > binNMU, and we can't risk this many packages being removed just now. > Ping me if you need help! Sorry, I won't have any time until at least from now. Please go ahead.

Processed: reopening 972921 (Was: shasta: binary-all FTBFS)

Processing control commands: > tags -1 moreinfo Bug #972921 {Done: Nilesh Patra } [src:shasta] shasta: binary-all FTBFS Added tag(s) moreinfo. -- 972921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972921 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#972921: reopening 972921 (Was: shasta: binary-all FTBFS)

Control: tags -1 moreinfo Hi Adrian, On Tue, Dec 08, 2020 at 12:12:31PM +, Debian Bug Tracking System wrote: > Please contact me if you need assistance. I think I need assistance. The Auto-Building page[1] shows green for all, amd64 and arm64 and

Processed: libstatgen: FTBFS on arm64: E: Build killed with signal TERM after 150 minutes of inactivity

Processing commands for cont...@bugs.debian.org: > severity 976570 normal Bug #976570 [src:libstatgen] libstatgen: FTBFS on arm64: E: Build killed with signal TERM after 150 minutes of inactivity Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you

Bug#976570: libstatgen: FTBFS on arm64: E: Build killed with signal TERM after 150 minutes of inactivity

severity 976570 normal thanks Hi, arm64 is not on the architecture list for libstatgen, so I decrease the severity of the bug. Best, Dylan

Bug#977407: marked as done (jitterdebugger-utils: missing Breaks+Replaces: jitterdebugger (<< 0.3.1+git20200117.b90ff3a-2))

Your message dated Tue, 15 Dec 2020 06:18:41 + with message-id and subject line Bug#977407: fixed in jitterdebugger 0.3.1+git20200117.b90ff3a-3 has caused the Debian Bug report #977407, regarding jitterdebugger-utils: missing Breaks+Replaces: jitterdebugger (<< 0.3.1+git20200117.b90ff3a-2)

Bug#912880: gprename ported to GTK3

Hey. Seems gprename has been ported to GTK3... would be awesome if this could find it's way back into Debian :-) https://sourceforge.net/p/gprename/bugs/18/ Cheers, Chris.

Processed: tagging 962203

Processing commands for cont...@bugs.debian.org: > tags 962203 + patch Bug #962203 [debdelta] DeprecationWarning: isAlive() is deprecated, use is_alive() instead Bug #954420 [debdelta] Python deprecation warning Added tag(s) patch. Added tag(s) patch. > thanks Stopping processing here. Please

Processed: forcibly merging 962203 954420

Processing commands for cont...@bugs.debian.org: > forcemerge 962203 954420 Bug #962203 [debdelta] DeprecationWarning: isAlive() is deprecated, use is_alive() instead Bug #954420 [debdelta] Python deprecation warning Severity set to 'grave' from 'minor' Merged 954420 962203 > thanks Stopping

Bug#977423: marked as done (maintainer address bounces)

Your message dated Tue, 15 Dec 2020 02:49:47 +0100 with message-id and subject line Re: maintainer address bounces has caused the Debian Bug report #977423, regarding maintainer address bounces to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#977397: uim-el: missing *-uim in input-method-alist on Emacs 27

Control: tag -1 patch fixed-upstream On Tue, Dec 15, 2020 at 02:31:46AM +0900, Nobuhiro Ban wrote: > I used the japanese-anthy-utf8-uim input-method on my Debian Emacs 26 env. > But after upgrading Emacs 27, > I cannot set input-method to japanese-anthy-utf8-uim. > > (Same cause as #977257) > >

Processed: Re: Bug#977397: uim-el: missing *-uim in input-method-alist on Emacs 27

Processing control commands: > tag -1 patch fixed-upstream Bug #977397 [uim-el] uim-el: missing *-uim in input-method-alist on Emacs 27 Added tag(s) fixed-upstream. -- 977397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977397 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: Re: Bug#977257: uim-el: "Active processes exist" prompt upon exiting emacs

Processing control commands: > tags -1 confirmed Bug #977257 [uim-el] uim-el: "Active processes exist" prompt upon exiting emacs Added tag(s) confirmed. > block -1 by 977397 Bug #977257 [uim-el] uim-el: "Active processes exist" prompt upon exiting emacs 977257 was not blocked by any bugs. 977257

Processed: Re: This package only builds Arch:all binary packages

Processing control commands: > severity -1 normal Bug #976548 [src:akuma] akuma: FTBFS on arm64,ppc64el (arch:all-only src pkg): dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven

Bug#976548: This package only builds Arch:all binary packages

Control: severity -1 normal The package is arch:all and builds fine on amd64 but FTBFS on other supported architectures. Apparently one or two arch-dependent tests fail which is the root cause of this failure. I'm downgrading the severity to normal as discussed on the debian-java list. This is

Bug#977108: marked as done (ruby-gollum-rugged-adapter, autopkgtest failure with ruby-rugged 1.1.0)

Your message dated Tue, 15 Dec 2020 00:49:35 + with message-id and subject line Bug#977108: fixed in ruby-gollum-rugged-adapter 0.4.4.3~gitlab.1-1 has caused the Debian Bug report #977108, regarding ruby-gollum-rugged-adapter, autopkgtest failure with ruby-rugged 1.1.0 to be marked as done.

Bug#976915: marked as done (service-wrapper-java: FTBFS on ppc64el: [exec] wrapper.c:(.text+0x3598): undefined reference to `pow')

Your message dated Tue, 15 Dec 2020 00:49:40 + with message-id and subject line Bug#976915: fixed in service-wrapper-java 3.5.30-3 has caused the Debian Bug report #976915, regarding service-wrapper-java: FTBFS on ppc64el: [exec] wrapper.c:(.text+0x3598): undefined reference to `pow' to

Bug#976915: marked as pending in service-wrapper-java

Control: tag -1 pending Hello, Bug #976915 in service-wrapper-java 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#976915 marked as pending in service-wrapper-java

Processing control commands: > tag -1 pending Bug #976915 [src:service-wrapper-java] service-wrapper-java: FTBFS on ppc64el: [exec] wrapper.c:(.text+0x3598): undefined reference to `pow' Added tag(s) pending. -- 976915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976915 Debian Bug

Bug#977423: maintainer address bounces

Hi, On Tue, 15 Dec 2020 00:36:23 +0100 Michael Biebl wrote: > I just tried to file a bug report against apt-listchanges and got this > reply > > Reporting-MTA: dns;VI1EUR04HT091.mail.protection.outlook.com > Received-From-MTA: dns;DBAPR01MB7126.eurprd01.prod.exchangelabs.com > Arrival-Date: Mon,

Bug#973848: chromium: Unsupported version, many security bugs unfixed

Hello, > I suspect that debian's libvpx might need to be build with experimental features enabled (similar to a previous bug report), in order to include the absent header files. This will build the lib, but the header isn't correctly exported. They don't export the header file for that and the

Bug#975533: [Pkg-privacy-maintainers] Bug#975533: mat2's autopkg tests fail with Python 3.9

Hi nicoo, On 20-12-14 15:57:10, nicoo wrote: > There doesn't seem to be anyone else handling the mat2 RC bug (FTBFS & > autopkgtest failure) so I will do it. I'm well aware and will handle this accordingly once there is a new upstream release, which should happen soon. Cheers, Georg

Bug#971713: sysstat: init or systemd file has overlapping runlevels

Trek pisze: Hi, > > so the fix would be like the one attached to this mail I've tried this update-rc.d -f sysstat command manually, and then I run 'apt install --reinstall sysstat', and as the result the warning about default stop level is fixed, but the original warning about overlapping

Bug#971713: sysstat: init or systemd file has overlapping runlevels

On Mon, 14 Dec 2020 03:54:28 +0100 Lorenzo wrote: > if you are searching in the source under /debian directory, the code > that you are looking for will be written by dh-installinit in place of > the #DEBHEPLER# placeholder, during the build of the package. @Lorenzo oh yeah, many thanks :) so

Bug#977423: maintainer address bounces

Source: apt-listchanges Severity: serious I just tried to file a bug report against apt-listchanges and got this reply Reporting-MTA: dns;VI1EUR04HT091.mail.protection.outlook.com Received-From-MTA: dns;DBAPR01MB7126.eurprd01.prod.exchangelabs.com Arrival-Date: Mon, 14 Dec 2020 23:33:24 +

Processed: rust-sha1collisiondetection: FTBFS on architectures with unsigned char

Processing control commands: > forwarded -1 https://gitlab.com/sequoia-pgp/sha1collisiondetection/-/issues/1 Bug #977421 [rust-sha1collisiondetection] rust-sha1collisiondetection: FTBFS on architectures with unsigned char Warning: Unknown package 'rust-sha1collisiondetection' Set Bug

Bug#977421: rust-sha1collisiondetection: FTBFS on architectures with unsigned char

Package: rust-sha1collisiondetection Version: 0.2.2-1 Severity: critical Control: forwarded -1 https://gitlab.com/sequoia-pgp/sha1collisiondetection/-/issues/1 Looks like rust-sha1collisiondetection code isn't as portable as upstream expected it to be. It is failing on platforms with an

Processed: Re: Bug#976653: dfwinreg FTBFS: missing: pycreg

Processing control commands: > tags -1 + patch Bug #976653 [src:dfwinreg] dfwinreg FTBFS: missing: pycreg Added tag(s) patch. -- 976653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976653 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#976653: dfwinreg FTBFS: missing: pycreg

Control: tags -1 + patch On Sunday, December 06 2020, Adrian Bunk wrote: > https://buildd.debian.org/status/fetch.php?pkg=dfwinreg=all=20201006-1=1607180871=0 > > ... >debian/rules override_dh_auto_test > make[1]: Entering directory '/<>' > python3 run_tests.py > Using Python version 3.9.1rc1

Processed: Re: nomacs: "charset=Ascii" appears before the comment of the image

Processing control commands: > retitle -1 nomacs uses internal libexiv2 functions to get the user comment Bug #974616 [nomacs] nomacs: "charset=Ascii" or "charset=Unicode" appears before the "User Comment" metadata of the image Changed Bug title to 'nomacs uses internal libexiv2 functions to get

Processed: Re: gthumb uses internal libexiv2 functions

Processing control commands: > retitle -1 gthumb uses internal libexiv2 functions to get the user comment Bug #974608 [gthumb] gthumb: "charset=Ascii" appears before the comment of the image Changed Bug title to 'gthumb uses internal libexiv2 functions to get the user comment' from 'gthumb:

Bug#974608: gthumb uses internal libexiv2 functions

Control: retitle -1 gthumb uses internal libexiv2 functions to get the user comment The bug should be retitled accordingly. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC

Processed: gthumb uses internal libexiv2 functions

Processing control commands: > severity -1 serious Bug #974608 [gthumb] gthumb: "charset=Ascii" appears before the comment of the image Severity set to 'serious' from 'normal' -- 974608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974608 Debian Bug Tracking System Contact

Bug#962203: NMU

I have prepared an NMU for this package. It is currently at https://mentors.debian.net/package/debdelta/ . While I need a sponsor to get it into Debian, I am now reaching out to ment...@lists.debian.org to see if I can expedite the process. signature.asc Description: This is a digitally signed

Bug#973033: marked as done (python-molotov's autopkg tests are failing with python3.9)

Your message dated Mon, 14 Dec 2020 22:18:54 + with message-id and subject line Bug#973033: fixed in python-molotov 2.1-1 has caused the Debian Bug report #973033, regarding python-molotov's autopkg tests are failing with python3.9 to be marked as done. This means that you claim that the

Bug#976535: marked as done (nickle: FTBFS: latex errors)

Your message dated Mon, 14 Dec 2020 22:06:40 + with message-id and subject line Bug#976535: fixed in nickle 2.88 has caused the Debian Bug report #976535, regarding nickle: FTBFS: latex errors to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#956776: marked as done (osdlyrics: Depends on deprecated libappindicator)

Your message dated Mon, 14 Dec 2020 22:06:47 + with message-id and subject line Bug#956776: fixed in osdlyrics 0.5.5~rc2+dfsg1-2 has caused the Debian Bug report #956776, regarding osdlyrics: Depends on deprecated libappindicator to be marked as done. This means that you claim that the

Bug#977349: marked as done (Current package does not ensure a smooth upgrade from stable due to breakage of past config and new binary modules.)

Your message dated Mon, 14 Dec 2020 22:00:14 + with message-id and subject line Bug#977349: fixed in proftpd-dfsg 1.3.7a+dfsg-3 has caused the Debian Bug report #977349, regarding Current package does not ensure a smooth upgrade from stable due to breakage of past config and new binary

Bug#957378: isoqlog: diff for NMU version 2.2.1-9.1

Control: tags 957378 + patch Control: tags 957378 + pending -- Dear maintainer, I've prepared an NMU for isoqlog (versioned as 2.2.1-9.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru isoqlog-2.2.1/debian/changelog

Processed: isoqlog: diff for NMU version 2.2.1-9.1

Processing control commands: > tags 957378 + patch Bug #957378 [src:isoqlog] isoqlog: ftbfs with GCC-10 Added tag(s) patch. > tags 957378 + pending Bug #957378 [src:isoqlog] isoqlog: ftbfs with GCC-10 Added tag(s) pending. -- 957378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957378

Bug#936604: marked as done (getmail: Python2 removal in sid/bullseye)

Your message dated Mon, 14 Dec 2020 21:39:05 + with message-id and subject line Bug#977291: Removed package(s) from unstable has caused the Debian Bug report #936604, regarding getmail: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#974061: marked as done (postgresql-12 should not be part of the next release, remove from testing)

Your message dated Mon, 14 Dec 2020 21:38:29 + with message-id and subject line Bug#977289: Removed package(s) from unstable has caused the Debian Bug report #974061, regarding postgresql-12 should not be part of the next release, remove from testing to be marked as done. This means that

Bug#975548: marked as done (mariadb-10.3_10.3.27-1~exp1_all.changes REJECTED])

Your message dated Mon, 14 Dec 2020 21:38:03 + with message-id and subject line Bug#977254: Removed package(s) from unstable has caused the Debian Bug report #975548, regarding mariadb-10.3_10.3.27-1~exp1_all.changes REJECTED] to be marked as done. This means that you claim that the problem

Bug#961982: marked as done (node-request-promise: deprecated upstream: should not be part of next stable Debian release)

Your message dated Mon, 14 Dec 2020 21:36:01 + with message-id and subject line Bug#977059: Removed package(s) from unstable has caused the Debian Bug report #961982, regarding node-request-promise: deprecated upstream: should not be part of next stable Debian release to be marked as done.

Bug#925546: marked as done (panic: Can't find the package clause)

Your message dated Mon, 14 Dec 2020 21:34:11 + with message-id and subject line Bug#976642: Removed package(s) from unstable has caused the Debian Bug report #925546, regarding panic: Can't find the package clause to be marked as done. This means that you claim that the problem has been

Bug#954180: marked as done (pillow-python2: has failing autopkgtests for python3)

Your message dated Mon, 14 Dec 2020 21:27:51 + with message-id and subject line Bug#971746: Removed package(s) from unstable has caused the Debian Bug report #954180, regarding pillow-python2: has failing autopkgtests for python3 to be marked as done. This means that you claim that the

Bug#953220: marked as done (pillow-python2: Python2 removal in sid/bullseye)

Your message dated Mon, 14 Dec 2020 21:27:51 + with message-id and subject line Bug#971746: Removed package(s) from unstable has caused the Debian Bug report #953220, regarding pillow-python2: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#952969: marked as done (pillow-python2: d/copyright issues)

Your message dated Mon, 14 Dec 2020 21:27:51 + with message-id and subject line Bug#971746: Removed package(s) from unstable has caused the Debian Bug report #952969, regarding pillow-python2: d/copyright issues to be marked as done. This means that you claim that the problem has been dealt

Bug#977185: nheko: switch to Boost 1.74

On Sat, 12 Dec 2020 09:42:27 +0100, Sebastian Ramacher said: > nheko currently hardcodes its boost build dependencies with an > explicit version. Since the default boost version is now 1.74 and we > are trying to remove boost 1.71 before the release of bullseye, please > switch to 1.74 or to

Processed: fbxkb: diff for NMU version 0.6-2.1

Processing control commands: > tags 975673 + patch Bug #975673 [src:fbxkb] fbxkb: requires gdk-pixbuf-xlib-2.0.pc but does not build-depend on a package containing it Ignoring request to alter tags of bug #975673 to the same tags previously set > tags 975673 + pending Bug #975673 [src:fbxkb]

Bug#975673: fbxkb: diff for NMU version 0.6-2.1

Control: tags 975673 + patch Control: tags 975673 + pending Control: tags 975771 + patch Control: tags 975771 + pending -- Dear maintainer, I've prepared an NMU for fbxkb (versioned as 0.6-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip

Processed: fbxkb: diff for NMU version 0.6-2.1

Processing control commands: > tags 975673 + patch Bug #975673 [src:fbxkb] fbxkb: requires gdk-pixbuf-xlib-2.0.pc but does not build-depend on a package containing it Added tag(s) patch. > tags 975673 + pending Bug #975673 [src:fbxkb] fbxkb: requires gdk-pixbuf-xlib-2.0.pc but does not

Bug#976830: marked as done (src:mia: invalid maintainer address)

Your message dated Mon, 14 Dec 2020 21:04:31 + with message-id and subject line Bug#976830: fixed in mia 2.4.7-4 has caused the Debian Bug report #976830, regarding src:mia: invalid maintainer address to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#977408: libstdc++-11-doc: missing Conflicts: libstdc++-10-doc

Followup-For: Bug #977408 Add libgccjit-11-doc which misses a Conflicts: libgccjit-10-doc to the list. There are file conflicts on .png files with very generic names: usr/share/info/factorial.png usr/share/info/factorial1.png usr/share/info/libgccjit.info.gz usr/share/info/sum-of-squares.png

Bug#977409: libgm2-17: contains only libraries with SOVERSION 15

Package: libgm2-17 Version: 11-20201208-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships -rw-r--r-- root/root 31064 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2cor.so.15.0.0 -rw-r--r-- root/root

Processed: diff NMU for anytun_0.3.7-1.3

Processing commands for cont...@bugs.debian.org: > tags 977219 +pending +patch Bug #977219 [src:anytun] anytun: FTBFS with boost 1.74 Added tag(s) pending. Bug #977219 [src:anytun] anytun: FTBFS with boost 1.74 Added tag(s) patch. > user team+bo...@tracker.debian.org Setting user to

Bug#977219: diff NMU for anytun_0.3.7-1.3

tags 977219 +pending +patch user team+bo...@tracker.debian.org usertag 977219 +boost174 thanks Dear maintainer, I have prepared an NMU (versioned as 0.3.7-1.3) and uploaded to DELAYED/5. Please feel free to tell me if I should delay it longer, cancel or reschedule. Diff is attached. Best

Bug#900821: workaround confirmed

Hi all, we were experiencing this bug in a debian 10.4 docker container (FROM php:apache) it only happens with plain http not with https. I can confirm that workaround from Stefan Fritsch by turning EnableMMAP off is working for us! Cheers, Florian

Bug#977408: libstdc++-11-doc: missing Conflicts: libstdc++-10-doc

Package: libstdc++-11-doc Version: 11-20201208-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

Bug#976900: marked as done (pyside2 hard-codes Python 3.8 in it's install files)

Your message dated Mon, 14 Dec 2020 20:37:02 + with message-id and subject line Bug#976900: fixed in pyside2 5.15.0-6 has caused the Debian Bug report #976900, regarding pyside2 hard-codes Python 3.8 in it's install files to be marked as done. This means that you claim that the problem has

Bug#976561: marked as done (sword-text-web: FTBFS: Binary files engWEB2015eb/nt.bzs and modules/texts/ztext/engWEB2015eb/nt.bzs differ)

Your message dated Mon, 14 Dec 2020 20:37:17 + with message-id and subject line Bug#976561: fixed in sword-text-web 353.0-1 has caused the Debian Bug report #976561, regarding sword-text-web: FTBFS: Binary files engWEB2015eb/nt.bzs and modules/texts/ztext/engWEB2015eb/nt.bzs differ to be

Bug#977407: jitterdebugger-utils: missing Breaks+Replaces: jitterdebugger (<< 0.3.1+git20200117.b90ff3a-2)

Package: jitterdebugger-utils Version: 0.3.1+git20200117.b90ff3a-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because

Processed: Re: Bug#976487: grpc-java: FTBFS: CensusStatsModule.java:21: error: cannot find symbol

Processing control commands: > tag -1 confirmed Bug #976487 [src:grpc-java] grpc-java: FTBFS: CensusStatsModule.java:21: error: cannot find symbol Added tag(s) confirmed. -- 976487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976487 Debian Bug Tracking System Contact

Bug#976487: grpc-java: FTBFS: CensusStatsModule.java:21: error: cannot find symbol

Control: tag -1 confirmed Thank you for the bug report! I am able to replicate this locally. It looks like this was caused by a recent upload of opencensus-java that removed two symbols. I am working on an upload of an updated grpc-java package that no longer requires those symbols. -Olek

Bug#977348: ulfius: missing runtime zlib dependency?

On Mon, 14 Dec 2020 10:53:53 +0100 Gianfranco Costamagna wrote: Hello, looks like the new ulfius version is missing a zlib1g-dev dependency on the -dev package, leading to reverse-dependencies FTBFS in tests (e.g. in src:iddawc) Indeed, I missed that one, thanks!

Bug#976561: uploaded

Thanks for the fix. That is great. The package was built, reviewed and uploaded.

Bug#977405: libgtkdatabox-dev,libgtkdatabox-doc: both ship /usr/share/doc/libgtkdatabox-dev/{AUTHORS,README}

Package: libgtkdatabox-dev,libgtkdatabox-doc Version: 1:0.9.3.1-1.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll

Bug#976943: golang-github-seccomp-libseccomp-golang: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 github.com/seccomp/libsec

> === RUN TestRuleAddAndLoad > seccomp_test.go:588: Syscall should have returned error code! > --- FAIL: TestRuleAddAndLoad (0.00s) Source code is here: https://sources.debian.org/src/golang-github-seccomp-libseccomp-golang/0.9.1-2/seccomp_test.go/#L529-L589 This test is basically

Bug#976831: marked as done (src:amide: invalid maintainer address)

Your message dated Mon, 14 Dec 2020 18:18:30 + with message-id and subject line Bug#976831: fixed in amide 1.0.5-15 has caused the Debian Bug report #976831, regarding src:amide: invalid maintainer address to be marked as done. This means that you claim that the problem has been dealt with.

Bug#977354: marked as done (libmagics++-dev: Invalid dependency on "i" package)

Your message dated Mon, 14 Dec 2020 18:05:07 + with message-id and subject line Bug#977354: fixed in magics++ 4.5.2-2 has caused the Debian Bug report #977354, regarding libmagics++-dev: Invalid dependency on "i" package to be marked as done. This means that you claim that the problem has

Bug#977246: lutris should depend on python3-dbus

Hi, thanks for discovering this missing dependency. Since I closely follow the upstream Debian sources, I created a PR there: https://github.com/lutris/lutris/pull/3349 Depending on the schedule for a new release I will either backport this or wait for the new release. Kinda depends on how

Bug#977308: shasta: hardcoded dependencies on boost 1.71

Hi Shayan, did you had some reasons to add this hardcoded dependency? Kind regards Andreas. On Sun, Dec 13, 2020 at 10:15:44PM +0200, Graham Inggs wrote: > Source: shasta > Version: 0.6.0-4 > Severity: serious > Tags: ftbfs > > Hi Maintainer > > Binary package shasta has a hardcoded

Processed: Bug#976516 marked as pending in pyside2

Processing control commands: > tag -1 pending Bug #976516 [src:pyside2] pyside2: FTBFS: ValueError: At least one failure was not blacklisted and met the criterion 'FAIL! >= 3' Added tag(s) pending. -- 976516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976516 Debian Bug Tracking System

Bug#976516: marked as pending in pyside2

Control: tag -1 pending Hello, Bug #976516 in pyside2 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#977397: uim-el: missing *-uim in input-method-alist on Emacs 27

Package: uim-el Version: 1:1.8.8-6.1+b2 Severity: grave Justification: renders package unusable Tags: patch Dear Maintainer, I used the japanese-anthy-utf8-uim input-method on my Debian Emacs 26 env. But after upgrading Emacs 27, I cannot set input-method to japanese-anthy-utf8-uim. (Same cause

Processed: [bts-link] source package scapy

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package scapy > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting

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

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:firefox > # 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:odoo

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:odoo > # 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: Re: Bug#974940 closed by Paul Gevers (src:xserver-xorg-video-ati: fails to migrate to testing for too long: FTBFS on mips*el)

Processing control commands: > reopen -1 Bug #974940 {Done: Paul Gevers } [src:xserver-xorg-video-ati] src:xserver-xorg-video-ati: fails to migrate to testing for too long: FTBFS on mips*el 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be

Bug#974940: closed by Paul Gevers (src:xserver-xorg-video-ati: fails to migrate to testing for too long: FTBFS on mips*el)

Control: reopen -1 Hi Paul, On Mon, Nov 16, 2020 at 08:21:05PM +, Debian Bug Tracking System wrote: > It has been closed by Paul Gevers . I fail to understand why you closed this bug. As of today, builds for mipsel and mips64el are still missing. A local cross build for mips64el fails in

Bug#975863: marked as done (leatherman: /usr/include/boost/nowide/ are shipped by boost_1.74)

Your message dated Mon, 14 Dec 2020 17:05:19 + with message-id and subject line Bug#975863: fixed in leatherman 1.12.1+dfsg-1.1 has caused the Debian Bug report #975863, regarding leatherman: /usr/include/boost/nowide/ are shipped by boost_1.74 to be marked as done. This means that you claim

Bug#973848: chromium: Unsupported version, many security bugs unfixed

Hello, My work is in this repo: https://salsa.debian.org/mimi8/chromium/-/tree/master I'm updating the commit every time I make a change. Making a new commit for each file doesn't really make sense, since those are separate files anyway. There is another repo from another person that also

Processed: tagging 921339, reassign 972422 to libarcus3, fixed 972422 in 4.7.1-2, affects 972422, tagging 972333

Processing commands for cont...@bugs.debian.org: > tags 921339 + sid bullseye Bug #921339 [psensor] Please switch to Ayatana AppIndicator Added tag(s) bullseye and sid. > reassign 972422 libarcus3 4.7.1-1 Bug #972422 {Done: Christoph Berg } [cura-engine] cura-engine: Segfault if using CuraEngine

Bug#973848: chromium: Unsupported version, many security bugs unfixed

On Sat, 12 Dec 2020 19:47:32 +0100 Michel Le Bihan wrote: > Hello, > > Thank you for your reply. libvpx got updated in Debian, but I can't use > it because it's missing a lib. I also had issues with harfbuzz, so I'm > using bundled versions of those libs as you are. I also used your ozone >

Bug#977390: src:vtk7: invalid maintainer address

Source: vtk7 Version: 7.1.1+dfsg2-5 Severity: serious X-Debbugs-Cc: Gianfranco Costamagna The maintainer address is invalid, see below. Ansgar Forwarded Message Subject: Mail delivery failed: returning message to sender Date: Fri, 11 Dec 2020 22:07:20 + > This message

Bug#977348: marked as done (ulfius: missing runtime zlib dependency?)

Your message dated Mon, 14 Dec 2020 16:38:44 + with message-id and subject line Bug#977348: fixed in ulfius 2.7.0-3 has caused the Debian Bug report #977348, regarding ulfius: missing runtime zlib dependency? to be marked as done. This means that you claim that the problem has been dealt

Processed: tagging 973033

Processing commands for cont...@bugs.debian.org: > tags 973033 + pending Bug #973033 [src:python-molotov] python-molotov's autopkg tests are failing with python3.9 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 973033:

Bug#976549: marked as done (golang-github-robertkrimen-otto: FTBFS on arm64,ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 github.com/robert

Your message dated Mon, 14 Dec 2020 15:22:33 + with message-id and subject line Bug#976549: fixed in golang-github-robertkrimen-otto 0.0~git20200922.ef014fd-1 has caused the Debian Bug report #976549, regarding golang-github-robertkrimen-otto: FTBFS on arm64,ppc64el (arch:all-only src pkg):

Bug#975533: mat2's autopkg tests fail with Python 3.9

Hi, There doesn't seem to be anyone else handling the mat2 RC bug (FTBFS & autopkgtest failure) so I will do it. AFAICT this is only a matter of importing the right upstream commit (62ec8f6c1efc06364eb5f8c3d81e1b5dbcfc6e64) as a Debian patch. Best, nicoo On Mon, Nov 23, 2020 at 11:15:06AM

Bug#976902: marked as done (topydo: provides /usr/bin/todo with incompatible interface compared to devtodo)

Your message dated Mon, 14 Dec 2020 09:51:44 -0500 with message-id and subject line has caused the Debian Bug report #976902, regarding topydo: provides /usr/bin/todo with incompatible interface compared to devtodo to be marked as done. This means that you claim that the problem has been

Bug#973171: marked as pending in scapy

Control: tag -1 pending Hello, Bug #973171 in scapy 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#973171 marked as pending in scapy

Processing control commands: > tag -1 pending Bug #973171 [python3-scapy] dhcpcanon: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13 Added tag(s) pending. -- 973171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973171 Debian

Processed: Re: Bug#976552: dune-localfunctions: FTBFS: tests failed

Processing control commands: > severity -1 minor Bug #976552 [src:dune-localfunctions] dune-localfunctions: FTBFS on arm64,ppc64el (arch:all-only src pkg): tests failed Severity set to 'minor' from 'serious' -- 976552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976552 Debian Bug

Bug#976552: dune-localfunctions: FTBFS: tests failed

Control: severity -1 minor On Sat, 2020-12-05 at 14:22 +0100, Lucas Nussbaum wrote: > > 28/32 Test #28: test-orthonormal4 ***Failed [...] > > i = 115, j = 124: 1.33896e-09 > > i = 124, j = 115: 1.33896e-09 > >    FAILED ! These should be 0, but the epsilon for comparison seems to

Bug#976916: dune-functions: FTBFS on ppc64el (arch:all-only src pkg): Dune reported error: Dune::Exception [testScalarBasisConst:/<>/dune/functions/functionspacebases/test/gridviewfunctio

Control: severity -1 minor On Wed, 2020-12-09 at 09:58 +0100, Lucas Nussbaum wrote: > > Error: integral value is wrong! Probably some difference in floating-point arithmetic between amd64 and ppc64el. Given the error is only in a test and on ppc64el where Debian doesn't build arch:all packages,

Processed: Re: Bug#976916: dune-functions: FTBFS on ppc64el (arch:all-only src pkg): Dune reported error: Dune::Exception [testScalarBasisConst:/<>/dune/functions/functionspacebases/test/

Processing control commands: > severity -1 minor Bug #976916 [src:dune-functions] dune-functions: FTBFS on ppc64el (arch:all-only src pkg): Dune reported error: Dune::Exception [testScalarBasisConst:/<>/dune/functions/functionspacebases/test/gridviewfunctionspacebasistest.cc:233]: Error:

Bug#973848: chromium: Unsupported version, many security bugs unfixed

Hallo everybody, I have done some of the work as well since I have not seen your message about your efforts. I have uploaded a working build for unstable to mentors including updated version of the patches: https://mentors.debian.net/package/chromium/ This version is using the vendor-shipped

Bug#977357: libgdf ftbfs on s390x (test failures)

Package: src:libgdf Version: 0.1.3-6 Severity: serious Tags: sid bullseye see https://buildd.debian.org/status/fetch.php?pkg=libgdf=s390x=0.1.3-6=1606417737=0 stalls migration to testing. [...] 43% tests passed, 4 tests failed out of 7 Total Test time (real) = 0.04 sec The following tests

Bug#957003: marked as done (aqemu: ftbfs with GCC-10)

Your message dated Mon, 14 Dec 2020 11:03:33 + with message-id and subject line Bug#957003: fixed in aqemu 0.9.2-3 has caused the Debian Bug report #957003, regarding aqemu: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#977354: libmagics++-dev: Invalid dependency on "i" package

Package: libmagics++-dev Version: 4.5.2-1 Severity: grave Justification: renders package unusable I was alerted by a strange log in the package tracker: /usr/lib/python3/dist-packages/debian/deb822.py:1403: UserWarning: cannot parse package relationship "i", returning it raw I looked up what

  1   2   >