Bug#936857: marked as done (libfreenect: Python2 removal in sid/bullseye)

Your message dated Thu, 09 Apr 2020 05:18:29 + with message-id and subject line Bug#936857: fixed in libfreenect 1:0.5.3-2 has caused the Debian Bug report #936857, regarding libfreenect: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Processed: libfreenect: diff for version 1:0.5.3-2

Processing control commands: > tags 936857 + patch Bug #936857 [src:libfreenect] libfreenect: Python2 removal in sid/bullseye Added tag(s) patch. -- 936857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#936857: libfreenect: diff for version 1:0.5.3-2

Control: tags 936857 + patch Dear maintainer, I've prepared an upload for libfreenect (versioned as 1:0.5.3-2). The diff is attached to this message. Regards. diff -Nru libfreenect-0.5.3/debian/changelog libfreenect-0.5.3/debian/changelog --- libfreenect-0.5.3/debian/changelog 2016-01-01

Bug#956260: bkchem: should this package be removed?

Package: bkchem Severity: serious Tags: bullseye, sid Hello, i think this pacakge should be removed from debian: * python2-only * dead upstream (last release in 2010) * relatively low pop-con * keeps in the archive at least 1 package that could be removed if we remove bkchem if I dont

Bug#938719: marked as done (trash-cli: Python2 removal in sid/bullseye)

Your message dated Thu, 09 Apr 2020 04:03:32 + with message-id and subject line Bug#938719: fixed in trash-cli 0.17.1.14-3 has caused the Debian Bug report #938719, regarding trash-cli: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Processed: Re: Bug#953367: geneweb-gui binary package might need to be removed for Bullseye

Processing commands for cont...@bugs.debian.org: > severity 953367 normal Bug #953367 [geneweb-gui] geneweb-gui binary package might need to be removed for Bullseye Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. --

Bug#954506: marked as done (ttyrec: FTBFS: ttyrec.c:60:10: fatal error: stropts.h: No such file or directory)

Your message dated Thu, 09 Apr 2020 01:04:36 + with message-id and subject line Bug#954506: fixed in ttyrec 1.0.8-5.1 has caused the Debian Bug report #954506, regarding ttyrec: FTBFS: ttyrec.c:60:10: fatal error: stropts.h: No such file or directory to be marked as done. This means that

Bug#954525: marked as done (nis: FTBFS: log_msg.c:35:1: error: static declaration of ‘gettid’ follows non-static declaration)

Your message dated Thu, 09 Apr 2020 00:20:00 + with message-id and subject line Bug#954525: fixed in nis 3.17.1-4 has caused the Debian Bug report #954525, regarding nis: FTBFS: log_msg.c:35:1: error: static declaration of ‘gettid’ follows non-static declaration to be marked as done. This

Bug#954311: Not just rendering issues...

Thanks for the information, I appreciate it. Apparently I missed the transition from intel_drv to modesetting_drv. After switching to modesetting (instead of intel) and purging xserver-xorg-video-intel, the workaround in /etc/drirc is no longer needed. Best regards, -Pascal -- Homepage

Bug#946853: marked as done (Fails to build with glibc 2.30)

Your message dated Wed, 08 Apr 2020 23:18:43 + with message-id and subject line Bug#946853: fixed in ace 6.4.5+dfsg-1.1 has caused the Debian Bug report #946853, regarding Fails to build with glibc 2.30 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#952066: marked as done (jag: FTBFS: SDL_mixer.h:25:10: fatal error: SDL_stdinc.h: No such file or directory)

Your message dated Wed, 08 Apr 2020 23:03:36 + with message-id and subject line Bug#952066: fixed in jag 0.3.6-1 has caused the Debian Bug report #952066, regarding jag: FTBFS: SDL_mixer.h:25:10: fatal error: SDL_stdinc.h: No such file or directory to be marked as done. This means that you

Bug#953487: marked as done (runescape: binaries for non-free not auto-built)

Your message dated Wed, 08 Apr 2020 22:20:28 + with message-id and subject line Bug#953487: fixed in runescape 0.7-1 has caused the Debian Bug report #953487, regarding runescape: binaries for non-free not auto-built to be marked as done. This means that you claim that the problem has been

Bug#953714: marked as done (src:runescape: fails to migrate to testing for too long)

Your message dated Wed, 08 Apr 2020 22:20:28 + with message-id and subject line Bug#953714: fixed in runescape 0.7-1 has caused the Debian Bug report #953714, regarding src:runescape: fails to migrate to testing for too long to be marked as done. This means that you claim that the problem

Bug#890931: marked as done (golang-github-gopherjs-gopherjs FTBFS with golang-1.10-go: undefined: ___GOPHERJS_REQUIRES_GO_VERSION_1_9___)

Your message dated Wed, 8 Apr 2020 22:18:59 +0200 (CEST) with message-id and subject line closing this bug has caused the Debian Bug report #890931, regarding golang-github-gopherjs-gopherjs FTBFS with golang-1.10-go: undefined: ___GOPHERJS_REQUIRES_GO_VERSION_1_9___ to be marked as done. This

Processed: Re: [Pkg-javascript-devel] Bug#956238: npm: autopkgtest failures in arm64 and ppc64el

Processing control commands: > severity -1 important Bug #956238 [src:npm] npm: autopkgtest failures in arm64 and ppc64el Severity set to 'important' from 'serious' -- 956238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956238 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#956238: [Pkg-javascript-devel] Bug#956238: npm: autopkgtest failures in arm64 and ppc64el

Control: severity -1 important Le 08/04/2020 à 20:18, Gianfranco Costamagna a écrit : > Source: npm > Version: 6.13.4+ds-2 > Severity: serious > > Hello, looks like probably since version 6.x, a new autopkgtest introduced > has been failing on arm64, ppc64el and s390x (this one happens in

Processed: Re: Bug#956245: /etc/kernel/header_postinst.d/dkms: Error! You must be root to use this command.

Processing commands for cont...@bugs.debian.org: > tags 956245 + patch Bug #956245 [dkms] /etc/kernel/header_postinst.d/dkms: Error! You must be root to use this command. Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 956245:

Bug#956245: /etc/kernel/header_postinst.d/dkms: Error! You must be root to use this command.

tags 956245 + patch thanks On Wed, 8 Apr 2020, Thorsten Glaser wrote: > /etc/kernel/header_postinst.d/dkms: > Error! You must be root to use this command. This is caused by line 3178 of /usr/sbin/dkms: ((UID == 0)) && return I am root, but $UID is 1000. Changing the line to… [[ $(id

Bug#956245: /etc/kernel/header_postinst.d/dkms: Error! You must be root to use this command.

Package: dkms Version: 2.6.1-4 Severity: grave Justification: renders package unusable After installing a package that needs DKMS, I also wanted to install the kernel headers, to make it usable. I get: […] Unpacking linux-headers-4.19.0-8-amd64 (4.19.98-1) ... Selecting previously unselected

Processed: Re: Bug#956205: gitlab: Problem installing 12.8.8-6

Processing control commands: > forwarded -1 https://gitlab.com/gitlab-org/gitlab/-/merge_requests/29187 Bug #956205 [gitlab] gitlab: Problem installing 12.8.8-6 Bug #953415 [gitlab] gitlab: Top-level selectors may not contain the parent selector "&" Set Bug forwarded-to-address to

Bug#956205: gitlab: Problem installing 12.8.8-6

Control: forwarded -1 https://gitlab.com/gitlab-org/gitlab/-/merge_requests/29187 On 2020, ഏപ്രിൽ 8 8:08:34 PM IST, Pirate Praveen wrote: >Control: merge 953415 -1 > >On 2020, ഏപ്രിൽ 8 3:59:36 PM IST, David L >wrote: >>rake aborted! >>SassC::SyntaxError: Error: Top-level selectors may not

Processed: tagging 944169 ...

Processing commands for cont...@bugs.debian.org: > tags 944169 + fixed-upstream Bug #944169 [open-ath9k-htc-firmware] open-ath9k-htc-firmware: non-standard gcc/g++ used for build (gcc-8) Added tag(s) fixed-upstream. > forwarded 944169 >

Bug#955295: marked as done (photofilmstrip: incompatible with python 3.8?)

Your message dated Wed, 08 Apr 2020 19:05:02 + with message-id and subject line Bug#955295: fixed in photofilmstrip 3.7.3-1 has caused the Debian Bug report #955295, regarding photofilmstrip: incompatible with python 3.8? to be marked as done. This means that you claim that the problem has

Bug#952048: marked as done (iem-plugin-suite: FTBFS: ../../../resources/Standalone/MyStandaloneFilterWindow.h:132:47: error: cannot convert ‘juce::AudioIODeviceType*’ to ‘std::unique_ptr

Your message dated Wed, 08 Apr 2020 18:48:45 + with message-id and subject line Bug#952048: fixed in iem-plugin-suite 1.11.1-1 has caused the Debian Bug report #952048, regarding iem-plugin-suite: FTBFS: ../../../resources/Standalone/MyStandaloneFilterWindow.h:132:47: error: cannot convert

Bug#955815: marked as done (intel-opencl-clang: requires a source-only upload)

Your message dated Wed, 08 Apr 2020 18:34:41 + with message-id and subject line Bug#955815: fixed in intel-opencl-clang 10.0.0-2 has caused the Debian Bug report #955815, regarding intel-opencl-clang: requires a source-only upload to be marked as done. This means that you claim that the

Bug#955858: gparted: does not start, 'unable to init server', tmp.mount does not exist

Kyle B writes: > (gpartedbin:11049): Gtk-WARNING **: 09:04:39.901: cannot open display: What display server / desktop environment are you using?

Bug#956238: npm: autopkgtest failures in arm64 and ppc64el

Source: npm Version: 6.13.4+ds-2 Severity: serious Hello, looks like probably since version 6.x, a new autopkgtest introduced has been failing on arm64, ppc64el and s390x (this one happens in Ubuntu, but should be reproducible in Debian too).

Bug#952250: marked as done (ecb: FTBFS: mv: cannot stat 'html-help/index.html': No such file or directory)

Your message dated Wed, 08 Apr 2020 17:51:18 + with message-id and subject line Bug#952250: fixed in ecb 2.50+git20170628-1 has caused the Debian Bug report #952250, regarding ecb: FTBFS: mv: cannot stat 'html-help/index.html': No such file or directory to be marked as done. This means that

Bug#952055: paulstretch: FTBFS: XMLwrapper.cpp:32:26: error: invalid use of incomplete type ‘mxml_node_t’ {aka ‘struct _mxml_node_s’}

Hi, I have raised a merge request to fix this issue. This is an issue due to change in mxml. https://salsa.debian.org/multimedia-team/paulstretch/-/merge_requests/1 Note: I could not test it, I am getting segfaults even with 2.2-2-4. -- Regards Sudip

Bug#953952: kmod: libkmod2-udeb contains binary instead of libraries

On 2020-04-05 02:21, Marco d'Itri wrote: > On Mar 15, Aurelien Jarno wrote: > > > The kmod binaries are actually the one being used, so yes please add a > > kmod-udeb. > Does it look good to you? > > https://salsa.debian.org/md/kmod/-/commit/801ce705d39efdae9411192b1c33aee8ad522cc7 > >

Processed: bug 956229 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=132313

Processing commands for cont...@bugs.debian.org: > forwarded 956229 https://rt.cpan.org/Ticket/Display.html?id=132313 Bug #956229 [src:libtickit-widget-floatbox-perl] FTBFS: test failures Set Bug forwarded-to-address to 'https://rt.cpan.org/Ticket/Display.html?id=132313'. > thanks Stopping

Bug#956229: FTBFS: test failures

Source: libtickit-widget-floatbox-perl Version: 0.05-1 Severity: serious Tags: upstream ftbfs sid bullseye Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The package started to fail its test after uploading one of the other Tickit::* packages:

Processed (with 1 error): Re: Bug#940656: [Pkg-privacy-maintainers] Bug#940656: black screen after upgrade

Processing commands for cont...@bugs.debian.org: > close 940656 Bug #940656 [torbrowser-launcher] torbrowser-launcher: Torbrowser downloads but apparmor stops from running, xfce Marked Bug as done > forcemerge 940656 942901 Bug #940656 {Done: Roger Shimizu } [torbrowser-launcher]

Processed (with 1 error): Re: Bug#940656: [Pkg-privacy-maintainers] Bug#940656: black screen after upgrade

Processing control commands: > forcemerge -1 942901 Bug #940656 [torbrowser-launcher] torbrowser-launcher: Torbrowser downloads but apparmor stops from running, xfce Bug #942901 {Done: Roger Shimizu } [torbrowser-launcher] torbrowser-launcher: Tor Browser 9.0 shows only black screens due to no

Processed: tagging 956211

Processing commands for cont...@bugs.debian.org: > tags 956211 + wontfix Bug #956211 [nodejs] nodejs 10 segfaults when running webpack on gitlab 12.9.2 - FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory Added tag(s) wontfix. > thanks

Bug#956152: rabbitmq-server: fails to install reliably on arm64

On 4/7/20 10:35 PM, Paul Gevers wrote: > Package: rabbitmq-server > Version: 3.7.18-1 > Severity: serious > Tags: sid bullseye > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: flaky breaks > Control: affects -1 mcollective > > Dear maintainer(s), > > As

Bug#937602: marked as done (python-bcrypt: Python2 removal in sid/bullseye)

Your message dated Wed, 08 Apr 2020 16:03:49 + with message-id and subject line Bug#937602: fixed in python-bcrypt 3.1.7-3 has caused the Debian Bug report #937602, regarding python-bcrypt: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#956211: [Pkg-javascript-devel] Bug#956211: nodejs 10 segfaults when running webpack on gitlab 12.9.2 - FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap ou

Tags: wontfix Le mer. 8 avr. 2020 à 15:48, Pirate Praveen a écrit : > Package: nodejs > Version: 10.19.0~dfsg-3 > Severity: grave > Control: notfound -1 12.13.1~dfsg-1 > > > nodejs 10 crashed (retried again) and on the same machine nodejs 12 > worked. > This has been working upto gitlab 12.8.8

Bug#939951: Link upstream bug

forwarded 939951 https://github.com/kupferlauncher/keybinder/issues/16 thanks Looks like upstream have committed a fix, but have not confirmed it by closing the issue. Ross

Processed: Link upstream bug

Processing commands for cont...@bugs.debian.org: > forwarded 939951 https://github.com/kupferlauncher/keybinder/issues/16 Bug #939951 [src:keybinder-3.0] keybinder-3.0: fails to build with gtk-doc 1.32 Set Bug forwarded-to-address to 'https://github.com/kupferlauncher/keybinder/issues/16'. >

Processed: Bug#937602 marked as pending in python-bcrypt

Processing control commands: > tag -1 pending Bug #937602 [src:python-bcrypt] python-bcrypt: Python2 removal in sid/bullseye Added tag(s) pending. -- 937602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#937602: marked as pending in python-bcrypt

Control: tag -1 pending Hello, Bug #937602 in python-bcrypt 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: py2removal bugs severity updates - 2020-04-08 15:36:22.582420+00:00

Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See

Bug#948206: mitmproxy incompatible with python3-wsproto=0.15.0-2

On 08/04/2020 16:58, Andrej Shadura wrote: Uploading an NMU to DELAYED/0, including the upstream fix and two clean-up commits from the Janitor. Sorry, I intended to upload it to DELAYED/1 but was hit by an off-by-one error. -- Cheers, Andrej

Bug#952060: libsignon-glib: diff for NMU version 1.12-2.1

Le 07/04/2020 à 09:52, Adrian Bunk a écrit : > Control: tags 952060 + patch > Control: tags 952060 + pending > > Dear maintainer, > > I've prepared an NMU for libsignon-glib (versioned as 1.12-2.1) and > uploaded it to DELAYED/15. Please feel free to tell me if I should > cancel it. Applied

Bug#948206: marked as done (mitmproxy incompatible with python3-wsproto=0.15.0-2)

Your message dated Wed, 08 Apr 2020 15:03:48 + with message-id and subject line Bug#948206: fixed in mitmproxy 4.0.4-6.1 has caused the Debian Bug report #948206, regarding mitmproxy incompatible with python3-wsproto=0.15.0-2 to be marked as done. This means that you claim that the problem

Bug#952064: marked as done (labrea: FTBFS: ../inc/pcaputil.h:18:10: error: conflicting types for ‘pcap_open’)

Your message dated Wed, 08 Apr 2020 15:03:38 + with message-id and subject line Bug#952064: fixed in labrea 2.5-stable-3.1 has caused the Debian Bug report #952064, regarding labrea: FTBFS: ../inc/pcaputil.h:18:10: error: conflicting types for ‘pcap_open’ to be marked as done. This means

Bug#952060: marked as pending in libsignon-glib

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

Processing control commands: > tag -1 pending Bug #952060 [src:libsignon-glib] libsignon-glib: FTBFS: signon-auth-service.c:72:13: error: G_ADD_PRIVATE [-Werror] Ignoring request to alter tags of bug #952060 to the same tags previously set -- 952060:

Bug#948206: mitmproxy incompatible with python3-wsproto=0.15.0-2

On Sun, 05 Jan 2020 11:27:14 +0100 Adrian Vollmer wrote: Package: mitmproxy Version: 4.0.4-6 Severity: grave Tags: newcomer Justification: renders package unusable After upgrading python3-wsproto to version 0.15.0-2, mitmproxy fails immediately with this error message: ImportError: cannot

Bug#954311: Not just rendering issues...

On 8.4.2020 17.15, Pascal Giard wrote: > On Mon, Apr 6, 2020 at 12:05 PM Timo Aaltonen > wrote: > > On 6.4.2020 1.55, Pascal Giard wrote: > > Thanks A LOT for the /etc/drirc trick, it fixed the problem > > detailed below for me. > > Took me over an

Bug#954635: marked as done (CLI binding packages fail to install: Unhandled Exception: System.TypeInitializationException: The type initializer for 'Sys' threw an exception)

Your message dated Wed, 08 Apr 2020 14:47:36 + with message-id and subject line Bug#954635: fixed in mono 6.8.0.105+dfsg-3 has caused the Debian Bug report #954635, regarding CLI binding packages fail to install: Unhandled Exception: System.TypeInitializationException: The type initializer

Bug#956205: gitlab: Problem installing 12.8.8-6

Control: merge 953415 -1 On 2020, ഏപ്രിൽ 8 3:59:36 PM IST, David L wrote: >rake aborted! >SassC::SyntaxError: Error: Top-level selectors may not contain the >parent selector "&". >on line 6:9 of node_modules/@gitlab/ui/src/scss/components.scss It is already known and work around

Bug#891901:

I found this ticket because I have the same issue after 2 years. With the version on sid I had the same problem so I tried with the experimental because is more updated and the one used by debian is very old. I am getting the same errors reported here and Ifixed it as suggested in this ticket and

Processed: Re: Bug#956205: gitlab: Problem installing 12.8.8-6

Processing control commands: > merge 953415 -1 Bug #953415 [gitlab] gitlab: Top-level selectors may not contain the parent selector "&" Bug #956205 [gitlab] gitlab: Problem installing 12.8.8-6 There is no source info for the package 'gitlab' at version '12.8.8-6+fto10+1' with architecture ''

Processed: frobtads: diff for NMU version 1:1.2.4-1.1

Processing control commands: > tags 836934 + pending Bug #836934 [src:frobtads] frobtads: FTBFS with GCC 6: error: exception cleanup for this placement new selects non-placement operator delete Added tag(s) pending. > tags 871215 + pending Bug #871215 [src:frobtads] frobtads: FTBFS with GCC-7:

Bug#954311: Not just rendering issues...

On Mon, Apr 6, 2020 at 12:05 PM Timo Aaltonen wrote: > On 6.4.2020 1.55, Pascal Giard wrote: > > Thanks A LOT for the /etc/drirc trick, it fixed the problem > > detailed below for me. > > Took me over an hour to figure out what was wrong and to end up on this > > bug report. > > > > I have a

Processed: py2removal bugs severity updates - 2020-04-08 13:45:03.681072+00:00

Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See

Processed: Bug#938154 marked as pending in python-sabyenc

Processing control commands: > tag -1 pending Bug #938154 [src:python-sabyenc] python-sabyenc: Python2 removal in sid/bullseye Added tag(s) pending. -- 938154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: nodejs 10 segfaults when running webpack on gitlab 12.9.2 - FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

Processing control commands: > notfound -1 12.13.1~dfsg-1 Bug #956211 [nodejs] nodejs 10 segfaults when running webpack on gitlab 12.9.2 - FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory Ignoring request to alter found versions of bug

Bug#938154: marked as pending in python-sabyenc

Control: tag -1 pending Hello, Bug #938154 in python-sabyenc 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#956211: nodejs 10 segfaults when running webpack on gitlab 12.9.2 - FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

Package: nodejs Version: 10.19.0~dfsg-3 Severity: grave Control: notfound -1 12.13.1~dfsg-1 nodejs 10 crashed (retried again) and on the same machine nodejs 12 worked. This has been working upto gitlab 12.8.8 and the failure appeared when trying to update to 12.9.2 (just installing gitlab

Processed: bug 956084 is forwarded to https://lists.gnu.org/archive/html/bug-inetutils/2020-04/msg00010.html

Processing commands for cont...@bugs.debian.org: > forwarded 956084 > https://lists.gnu.org/archive/html/bug-inetutils/2020-04/msg00010.html Bug #956084 [inetutils-telnetd] inetutils-telnetd: CVE-2020-10188 Set Bug forwarded-to-address to

Bug#956202: gnome-calendar crashes immediately after start

Control: severity -1 important Control: tags -1 + moreinfo On Wed, 08 Apr 2020 at 12:16:47 +0200, Matthias Brennwald wrote: > Running it from the terminal: > >> gnome-calendar > Segmentation fault Does it print any other messages? If you run it with "G_MESSAGES_DEBUG=all gnome-calendar", does

Processed: Re: Bug#956202: gnome-calendar crashes immediately after start

Processing control commands: > severity -1 important Bug #956202 [gnome-calendar] gnome-calendar crashes immediately after start Severity set to 'important' from 'critical' > tags -1 + moreinfo Bug #956202 [gnome-calendar] gnome-calendar crashes immediately after start Added tag(s) moreinfo. --

Bug#937274: marked as done (petit: Python2 removal in sid/bullseye)

Your message dated Wed, 08 Apr 2020 12:51:34 + with message-id and subject line Bug#956132: Removed package(s) from unstable has caused the Debian Bug report #937274, regarding petit: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Processed: labrea: diff for NMU version 2.5-stable-3.1

Processing control commands: > tags 952064 + patch Bug #952064 [src:labrea] labrea: FTBFS: ../inc/pcaputil.h:18:10: error: conflicting types for ‘pcap_open’ Added tag(s) patch. > tags 952064 + pending Bug #952064 [src:labrea] labrea: FTBFS: ../inc/pcaputil.h:18:10: error: conflicting types for

Bug#952064: labrea: diff for NMU version 2.5-stable-3.1

Control: tags 952064 + patch Control: tags 952064 + pending Dear maintainer, I've prepared an NMU for labrea (versioned as 2.5-stable-3.1) and uploaded it to mentors for sponsoring. Please feel free to tell me if I should remove it. -- Regards Sudip diff -u labrea-2.5-stable/debian/changelog

Bug#936546: marked as done (forg: Python2 removal in sid/bullseye)

Your message dated Wed, 08 Apr 2020 12:51:58 + with message-id and subject line Bug#956133: Removed package(s) from unstable has caused the Debian Bug report #936546, regarding forg: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#938614: marked as done (syncthing-gtk: Python2 removal in sid/bullseye)

Your message dated Wed, 08 Apr 2020 12:50:51 + with message-id and subject line Bug#956129: Removed package(s) from unstable has caused the Debian Bug report #938614, regarding syncthing-gtk: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#936343: marked as done (cron-deja-vu: Python2 removal in sid/bullseye)

Your message dated Wed, 08 Apr 2020 12:51:13 + with message-id and subject line Bug#956130: Removed package(s) from unstable has caused the Debian Bug report #936343, regarding cron-deja-vu: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#936819: marked as done (lavapdu: Python2 removal in sid/bullseye)

Your message dated Wed, 08 Apr 2020 12:52:25 + with message-id and subject line Bug#956156: Removed package(s) from unstable has caused the Debian Bug report #936819, regarding lavapdu: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#938233: marked as done (python-typing: Python2 removal in sid/bullseye)

Your message dated Wed, 08 Apr 2020 12:49:58 + with message-id and subject line Bug#947020: Removed package(s) from unstable has caused the Debian Bug report #938233, regarding python-typing: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#937842: marked as done (Should not be released with bullsye: Python2 removal in sid/bullseye)

Your message dated Wed, 08 Apr 2020 12:49:27 + with message-id and subject line Bug#935573: Removed package(s) from unstable has caused the Debian Bug report #937842, regarding Should not be released with bullsye: Python2 removal in sid/bullseye to be marked as done. This means that you

Bug#953367: geneweb-gui binary package might need to be removed for Bullseye

Le mercredi 08 avril 2020 à 08:10 -0400, Guillaume Brochu a écrit : > As I can see, lablgtk2 should be repaired soon: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885677#95 > > My understanding is that geneweb-gui does not depend on the problematic > component (gtksourceview2) of

Bug#955167:

Hi, The autopkgtest regression is now fixed in the new version 0.9-1+dfsg-1 which passes according to debci [1]. BUT, if we look at the log file there are a lot of errors which are not detected (?) by debci [2]. By looking at the history of tests, it seems this behavior was already present in the

Bug#953367: geneweb-gui binary package might need to be removed for Bullseye

Bonjour Sébastien, As I can see, lablgtk2 should be repaired soon: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885677#95 My understanding is that geneweb-gui does not depend on the problematic component (gtksourceview2) of lablgtk2. So I propose to wait for this fix. Then, I might

Bug#956084: inetutils-telnetd: CVE-2020-10188

Hi! On Tue, 2020-04-07 at 13:41:09 +1000, Paul Szabo wrote: > Package: inetutils-telnetd > Severity: critical > Tags: security > Justification: root security hole > Looking in https://security-tracker.debian.org/tracker/CVE-2020-10188 : > > utility.c in telnetd in netkit telnet through 0.17

Bug#947556: marked as done (FTBFS with scons 3.1.2-1)

Your message dated Wed, 08 Apr 2020 10:48:38 + with message-id and subject line Bug#947556: fixed in create-resources 0.1.3-6 has caused the Debian Bug report #947556, regarding FTBFS with scons 3.1.2-1 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#956204: pdftk-java: pdftk Unsupported major.minor version 52.0

Package: pdftk-java Version: 3.0.6-1 Severity: grave Justification: renders package unusable Dear Maintainer, When i use pdftk *** I have this problem pdftk input BonDeCommande-20063569-20200409.pdf BonDeCommande-20064317-20200409.pdf BonDeCommande-20063577-20200409.pdf

Bug#956205: gitlab: Problem installing 12.8.8-6

Package: gitlab Version: 12.8.8-6+fto10+1 Severity: grave Justification: renders package unusable Hi, Gitlab 12.8.8 installation fails. Log: Bundle complete! 198 Gemfile dependencies, 362 gems now installed. Gems in the groups development and test were not installed. Use `bundle info

Bug#947556: marked as pending in create-resources

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

Processing control commands: > tag -1 pending Bug #947556 [src:create-resources] FTBFS with scons 3.1.2-1 Added tag(s) pending. -- 947556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#956202: gnome-calendar crashes immediately after start

Package: gnome-calendar Version: 3.36.0-1 Severity: critical Dear Maintainer, After a recent update to my system, gnome-calendar crashes immediately after staring it. Running it from the terminal: >> gnome-calendar Segmentation fault -- System Information: Debian Release: bullseye/sid APT

Processed (with 1 error): your mail

Processing commands for cont...@bugs.debian.org: > retitle 955316 r-cran-svglite autopkgtest fails: Error: symbol font Bug #955316 [src:r-cran-svglite] r-cran-svglite autopkgtest fails: there is no package called 'xml2' Changed Bug title to 'r-cran-svglite autopkgtest fails: Error: symbol font'

Bug#953367: geneweb-gui binary package might need to be removed for Bullseye

Dear Guillaume, Le dimanche 08 mars 2020 à 11:54 -0400, Guillaume Brochu a écrit : > Package: geneweb-gui > Version: 6.08+git20181019+dfsg-2 > Severity: serious > X-Debbugs-CC: sebast...@debian.org > > geneweb-gui binary package might need to be removed for Bullseye, for > the two following

Processed: tagging 952039

Processing commands for cont...@bugs.debian.org: > tags 952039 + fixed Bug #952039 {Done: Daniel Leidert } [src:ruby-graphviz] ruby-graphviz: FTBFS: ERROR: Test "ruby2.7" failed: /<>/test/output/dot/hello_test.rb:18:in `': undefined method `graph' for nil:NilClass (NoMethodError) Added tag(s)

Bug#956190: dh-python's autopkg tests fail with python3.8 as the only supported python3 version

Package: dh-python Version: 4.20200315 Severity: serious Tags: sid bullseye dh-python's autopkg tests fail with python3.8 as the only supported python3 version.

Processed: tagging 947541

Processing commands for cont...@bugs.debian.org: > tags 947541 + fixed-upstream Bug #947541 [src:viking] viking: build-depends on deprecated gnome-doc-utils Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 947541:

Processed: bug 947541 is forwarded to https://github.com/viking-gps/viking/commit/18d7c02d5829ec796efaa6b0fba0632f478048ba#diff-67e997bcfdac55191033d57a16d1408a

Processing commands for cont...@bugs.debian.org: > forwarded 947541 > https://github.com/viking-gps/viking/commit/18d7c02d5829ec796efaa6b0fba0632f478048ba#diff-67e997bcfdac55191033d57a16d1408a Bug #947541 [src:viking] viking: build-depends on deprecated gnome-doc-utils Set Bug

Processed: tagging 947542

Processing commands for cont...@bugs.debian.org: > tags 947542 + fixed-upstream Bug #947542 [src:xiphos] xiphos: build-depends on deprecated gnome-doc-utils Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 947542:

Processed: tagging 947540

Processing commands for cont...@bugs.debian.org: > tags 947540 + upstream Bug #947540 [src:stardict] stardict: build-depends on deprecated gnome-doc-utils Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 947540:

Bug#953996: [Pkg-julia-devel] Bug#953996: julia: FTBFS on ppc64el

On Wed, 1 Apr 2020 at 09:36, wrote: > Any follow-up/update on this? Looks like 11 April package will be auto- > removed if not fixed? Is this even fixable? I bisected the commits between 1.3.0 and 1.3.1 and found that reverting the following commit allows the build to succeed on ppc64el: ccall:

Processed: bug 947533 is forwarded to https://github.com/kupferlauncher/kupfer/pull/129

Processing commands for cont...@bugs.debian.org: > forwarded 947533 https://github.com/kupferlauncher/kupfer/pull/129 Bug #947533 [src:kupfer] kupfer: build-depends on deprecated gnome-doc-utils Set Bug forwarded-to-address to 'https://github.com/kupferlauncher/kupfer/pull/129'. > thanks

Processed: tagging 947533

Processing commands for cont...@bugs.debian.org: > tags 947533 + fixed-upstream Bug #947533 [src:kupfer] kupfer: build-depends on deprecated gnome-doc-utils Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 947533:

Bug#955456: FTBFS: test file tmp_test_filters.h5 does not exist

Package: bitshuffle Followup-For: Bug #955456 Incidentally, Thorsten, another way of handling h5py and bitshuffle's build against hfd5-mpi is to explicitly access h5py-mpi. That is, patch out bitshuffle to replace import h5py with import h5py._debian_h5py_mpi as h5py (in bitshuffle/h5.pyx

Bug#946853: Upgrade to ACE 6.5.8

Hi, Not a problem, years ago I asked several times whether people could assist me with the process to be allowed to upgrade ACE as part of the release procedure. Currently I upload the packages to github/vanderbilt but also provide them to OpenSuSE Build service, vcpkg, homebrew. Adding an upload