Bug#905335: botan: Incomplete debian/copyright?

Hi László, > > I just ACCEPTed botan from NEW but noticed it was missing attribution > > in debian/copyright for at least a pcks11 code copy and (possibly?) a > > curve25519 code copy. > > I've update the package to its 2.8.0 version and it's in the NEW > queue with corrected debian/copyright. >

Bug#907414: marked as done (twitter-bootstrap3: CVE-2018-14040 CVE-2018-14041 CVE-2018-14042)

Your message dated Fri, 04 Jan 2019 07:07:40 + with message-id and subject line Bug#907414: fixed in twitter-bootstrap3 3.4.0+dfsg-1 has caused the Debian Bug report #907414, regarding twitter-bootstrap3: CVE-2018-14040 CVE-2018-14041 CVE-2018-14042 to be marked as done. This means that you

Processed: reassign 918121 to src:gazebo, tagging 918121, block 917323 with 918121, merging 918121 918128

Processing commands for cont...@bugs.debian.org: > reassign 918121 src:gazebo Bug #918121 [libgazebo9-dev] libgazebo9-dev: gazebo.pc has broken link flags Bug reassigned from package 'libgazebo9-dev' to 'src:gazebo'. No longer marked as found in versions gazebo/9.4.1+dfsg-1. Ignoring request to

Processed: Re: Bug#914640: supercollider FTBFS on amd64/i386 with boost 1.67

Processing control commands: > tags -1 + fixed-upstream patch Bug #914640 [src:supercollider] supercollider FTBFS on amd64/i386 with boost 1.67 Added tag(s) patch and fixed-upstream. -- 914640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914640 Debian Bug Tracking System Contact

Processed: affects 918188

Processing commands for cont...@bugs.debian.org: > affects 918188 + release.debian.org Bug #918188 [src:linux] linux: FTBFS on arm64 Added indication that 918188 affects release.debian.org > thanks Stopping processing here. Please contact me if you need assistance. -- 918188:

Bug#918188: linux: FTBFS on arm64

Source: linux Version: 4.9.144-1 Severity: serious Justification: FTBFS For tracking the issue: 4.9.144-1 FTBFS on arm64: > LD vmlinux.o > MODPOST vmlinux.o > GEN .version > CHK include/generated/compile.h > UPD include/generated/compile.h > CC init/version.o >

Bug#911832: polyfill should be dropped

Hi, On 1/3/19 6:57 PM, David Prévot wrote: > Le 04/01/2019 à 12:50, Kunal Mehta a écrit : >> This patch adds overrides for all symfony/polyfill-* packages to >> pkg-php-tools itself, so all packages will automatically use it and no >> longer automatically depend upon php-symfony-polyfill-* (and

Bug#918187: fai - hook error handling completely broken

Source: fai Version: 5.7.2 Severity: grave There seems to be no way to make hooks abort the run. I explicitely made a hook always fail and it always continued: | partition.GRUB_CLOUD_AMD64 FAILED with exit code 1. | Skipping task_partition | Calling hook: mountdisks.CLOUD | No fstab file

Processed: bug 917654 is forwarded to https://github.com/latex3/latex2e/issues/106

Processing commands for cont...@bugs.debian.org: > forwarded 917654 https://github.com/latex3/latex2e/issues/106 Bug #917654 [src:bacula-doc] bacula-doc: FTBFS (LaTeX Error: Missing begin{document}) Bug #917735 [src:bacula-doc] bacula-doc: FTBFS: ! LaTeX Error: Missing \begin{document}. Set Bug

Bug#916415: marked as done (nocache broken with glibc 2.28: several programs just hang in call to futex(..., FUTEX_WAIT_PRIVATE, 2, NULL))

Your message dated Fri, 04 Jan 2019 04:04:21 + with message-id and subject line Bug#916415: fixed in nocache 1.1-1 has caused the Debian Bug report #916415, regarding nocache broken with glibc 2.28: several programs just hang in call to futex(..., FUTEX_WAIT_PRIVATE, 2, NULL) to be marked as

Bug#911832: polyfill should be dropped

Hi, Le 04/01/2019 à 12:50, Kunal Mehta a écrit : > This patch adds overrides for all symfony/polyfill-* packages to > pkg-php-tools itself, so all packages will automatically use it and no > longer automatically depend upon php-symfony-polyfill-* (and will cover > all current dependencies).

Bug#906863: marked as done (xul-ext-personasplus no longer works with firefox-esr 60)

Your message dated Fri, 04 Jan 2019 02:56:06 + with message-id and subject line Bug#918174: Removed package(s) from unstable has caused the Debian Bug report #906863, regarding xul-ext-personasplus no longer works with firefox-esr 60 to be marked as done. This means that you claim that the

Bug#892358: marked as done (xul-ext-gnome-keyring: Don't depend on libgnome-keyring)

Your message dated Fri, 04 Jan 2019 02:55:33 + with message-id and subject line Bug#918173: Removed package(s) from unstable has caused the Debian Bug report #892358, regarding xul-ext-gnome-keyring: Don't depend on libgnome-keyring to be marked as done. This means that you claim that the

Bug#881506: marked as done (xul-ext-gnome-keyring doesn't work with firefox >=57)

Your message dated Fri, 04 Jan 2019 02:55:33 + with message-id and subject line Bug#918173: Removed package(s) from unstable has caused the Debian Bug report #881506, regarding xul-ext-gnome-keyring doesn't work with firefox >=57 to be marked as done. This means that you claim that the

Bug#913445: marked as done (Broken with Thunderbird 60)

Your message dated Fri, 04 Jan 2019 02:52:33 + with message-id and subject line Bug#918159: Removed package(s) from unstable has caused the Debian Bug report #913445, regarding Broken with Thunderbird 60 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#906834: marked as done (xul-ext-password-editor no longer works with firefox-esr 60)

Your message dated Fri, 04 Jan 2019 02:53:14 + with message-id and subject line Bug#918170: Removed package(s) from unstable has caused the Debian Bug report #906834, regarding xul-ext-password-editor no longer works with firefox-esr 60 to be marked as done. This means that you claim that

Bug#906644: marked as done (conkeror: not compatible with firefox >= 57)

Your message dated Fri, 04 Jan 2019 02:49:21 + with message-id and subject line Bug#918071: Removed package(s) from unstable has caused the Debian Bug report #906644, regarding conkeror: not compatible with firefox >= 57 to be marked as done. This means that you claim that the problem has

Bug#906859: marked as done (xul-ext-dom-inspector no longer works with firefox-esr 60)

Your message dated Fri, 04 Jan 2019 02:48:31 + with message-id and subject line Bug#918065: Removed package(s) from unstable has caused the Debian Bug report #906859, regarding xul-ext-dom-inspector no longer works with firefox-esr 60 to be marked as done. This means that you claim that the

Bug#906847: marked as done (xul-ext-adblock-plus no longer works with firefox-esr 60)

Your message dated Fri, 04 Jan 2019 02:47:24 + with message-id and subject line Bug#918063: Removed package(s) from unstable has caused the Debian Bug report #906847, regarding xul-ext-adblock-plus no longer works with firefox-esr 60 to be marked as done. This means that you claim that the

Bug#906868: marked as done (xul-ext-toggle-proxy no longer works with firefox-esr 60)

Your message dated Fri, 04 Jan 2019 02:48:00 + with message-id and subject line Bug#918064: Removed package(s) from unstable has caused the Debian Bug report #906868, regarding xul-ext-toggle-proxy no longer works with firefox-esr 60 to be marked as done. This means that you claim that the

Bug#917837: marked as done (clutter-gesture: Intent to remove from Debian)

Your message dated Fri, 04 Jan 2019 02:46:17 + with message-id and subject line Bug#918041: Removed package(s) from unstable has caused the Debian Bug report #917837, regarding clutter-gesture: Intent to remove from Debian to be marked as done. This means that you claim that the problem has

Bug#906832: marked as done (xul-ext-kwallet5 no longer works with firefox-esr 60)

Your message dated Fri, 04 Jan 2019 02:46:51 + with message-id and subject line Bug#918062: Removed package(s) from unstable has caused the Debian Bug report #906832, regarding xul-ext-kwallet5 no longer works with firefox-esr 60 to be marked as done. This means that you claim that the

Bug#908947: youtube-dl: backport youtube-dl to recent version for stretch

P.S. I didn't mean to not include the original reporter, Thierry, in my email. I didn't realize there were multiple parties complaining about the same issue. No offense was intended. On Thu, Jan 3, 2019 at 9:14 PM Jeffrey Abbinante wrote: > On Tue, 1 Jan 2019 17:42:40 +0100 Christoph Pfister <

Bug#908947: youtube-dl: backport youtube-dl to recent version for stretch

On Tue, 1 Jan 2019 17:42:40 +0100 Christoph Pfister < christophpfis...@gmail.com> wrote: > Any news on this issue? (Like other people, I also needed to work around it.) > > Thanks, (and happy New Year!) > > Christoph > > Hello all, I can confirm I am affected by the issues Christoph has described

Bug#911832: polyfill should be dropped

On 1/2/19 11:57 PM, Kunal Mehta wrote: > I'm not sure how exactly the best way to remove the dependency is since > it's automatically generated from composer.json. We could update > pkg-php-tools to modify php-symfony-polyfill-* dependencies?

Bug#899595: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org

Hi, With Bugs search "Cleaner view", I've found those bugs are not closed in unstable but are done in experimental. Do you have a plan to put them into unstable, or just apply only those fixes to current unstable packages? I know xfce4.13 series are development release, but some projects

Bug#918068: closed by Tobias Hansen (Bug#918068: fixed in sagemath 8.4-4)

Thanks Tobias! Best wishes, Julian On Thu, Jan 03, 2019 at 11:39:03AM +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the sagemath package: > > #918068: sagemath: still not building on unstable :-( > > It has

Bug#918161: marked as done (ros-image-common: stop depending on yaml-cpp0.3)

Your message dated Thu, 03 Jan 2019 23:34:42 + with message-id and subject line Bug#918161: fixed in ros-image-common 1.11.13-3 has caused the Debian Bug report #918161, regarding ros-image-common: stop depending on yaml-cpp0.3 to be marked as done. This means that you claim that the problem

Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging

On Thu, 03 Jan 2019 22:04:48 +0200, Otto Kekäläinen wrote: > Just checking: are you Georg or Gregor currently working on this > issue, and do you have any estimate when we could expect either a > patch to MariaDB Connector C or a new upload of DBD-mysql so this > issue would be resolved? I had a

Bug#917904: marked as done (tightvncserver does not ask for password set by vncpasswd)

Your message dated Fri, 4 Jan 2019 00:13:50 +0100 with message-id and subject line Re: Bug#917904: tightvncserver does not ask for password set by vncpasswd has caused the Debian Bug report #917904, regarding tightvncserver does not ask for password set by vncpasswd to be marked as done. This

Bug#906863: xul-ext-personasplus no longer works with firefox-esr 60

On Sat, Nov 10, 2018 at 11:21:34PM +0100, Moritz Mühlenhoff wrote: > On Tue, Aug 21, 2018 at 09:17:28PM +0300, Adrian Bunk wrote: > > Package: xul-ext-personasplus > > Version: 1.7.8-1 > > Severity: serious > > > > XUL addons are no longer supported. > > > > If it is confirmed that this package

Processed: found 918164 in 0.5-4

Processing commands for cont...@bugs.debian.org: > found 918164 0.5-4 Bug #918164 [xul-ext-timeline] Broken with Thunderbird 60 Marked as found in versions timeline/0.5-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 918164:

Processed: found 918167 in 2.1.0-3

Processing commands for cont...@bugs.debian.org: > found 918167 2.1.0-3 Bug #918167 [xul-ext-compactheader] Broken in stable Marked as found in versions compactheader/2.1.0-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 918167:

Bug#918153: lnav: FTBFS (failing test)

On Fri, Jan 04, 2019 at 12:13:20AM +0200, Adrian Bunk wrote: > The failures all make sense if the result is > $(currentyear)-11-03 09:23:38.000 > and this is compared with > 2018-11-03 09:23:38.000 > > The upstream fix might not work for the complete lifetime of buster... >

Bug#881506: xul-ext-gnome-keyring doesn't work with firefox >=57

On Sun, Dec 23, 2018 at 11:21:32PM -0500, Jeremy Bicha wrote: > On Mon, Nov 19, 2018 at 5:20 PM Moritz Mühlenhoff wrote: > > On Mon, Nov 19, 2018 at 07:22:11AM -0500, Jeremy Bicha wrote: > > > > Given that Xul is still supported in Thunderbird, let maybe drop the > > > > support for > > > >

Bug#913346: libsane1: Cannot update libsane1

Control: tags -1 +patch This issue is more serious for Ubuntu which will need to keep a libsane1 transitional package around until after 20.04 LTS. I am attaching the patch I applied in Ubuntu for this issue. Please consider applying it in Debian too. Thanks, Jeremy Bicha From

Processed: Re: libsane1: Cannot update libsane1

Processing control commands: > tags -1 +patch Bug #913346 [sane-backends] libsane1: Cannot update libsane1 Added tag(s) patch. -- 913346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#918171: Broken with Thunderbird 60

Package: xul-ext-colorediffs Version: 0.6.2012.01.27.14.07.45-1 Severity: grave The plugin is broken with Thunderbird 60 in stretch and sid, after installation it's disabled and only prints "Colored Diffs is incompatible with Thunderbird 60.4". TB 60 was uploaded to stretch over two months ago

Bug#917904: tightvncserver does not ask for password set by vncpasswd

Hi, I checked using another testing installation, and that asked for a password upon connecting. I realized the problem was that I have used the vinagre client in the past to connect to a VNC server on the same target machine, with the same password. So vinagre had the password still stored

Bug#911285: Current version is incompatible with Thunderbird 60

On Thu, Oct 18, 2018 at 09:38:55AM +0200, Bastian Venthur wrote: > Package: xul-ext-gcontactsync > Version: 2.0.13-1 > Severity: grave > > The version of gcontactsync in unstable is incompatible with the Thunderbird > version in unstable. > > A new upstream version exists, that should be

Bug#906834: xul-ext-password-editor no longer works with firefox-esr 60

On Tue, Aug 21, 2018 at 07:55:19PM +0300, Adrian Bunk wrote: > On Tue, Aug 21, 2018 at 07:28:32PM +0300, Adrian Bunk wrote: > > Package: xul-ext-password-editor > > Version: 2.10.3-1 > > Severity: serious > > > > XUL addons are no longer supported. > > If it is confirmed that this package works

Bug#918167: Broken in stable

Package: xul-ext-compactheader Version: 2.1.6-1 Severity: grave The plugin is broken with Thunderbird 60 in stretch and sid, after installation it's disabled and only prints "CompactHeader is incompatible with Thunderbird 60.4". Either the version from sid could be backported or alternatively the

Bug#918166: Broken with Thunderbird 60

Package: xul-ext-google-tasks-sync Version: 0.5.3-1 Severity: grave Per the upstream homepage xul-ext-google-tasks-sync is incompatible with Thunderbird. In fact, when installing the package it's not even listed in the addon manager. Cheers, Moritz

Processed: notfound 917513 in 0.4.0+ds-2, found 917513 in 0.4.0+ds-4, found 917165 in 2.7.2 ..., tagging 917968 ...

Processing commands for cont...@bugs.debian.org: > notfound 917513 0.4.0+ds-2 Bug #917513 {Done: Jerome Benoit } [recommonmark-scripts] recommonmark-scripts: trying to overwrite '/usr/share/man/man1/cm2html.1.gz', which is also in package python-recommonmark 0.4.0+ds-2 No longer marked as found

Bug#914153: Update to version 2.3.0-3 breaks Megaglest

According to https://release.debian.org/buster/freeze_policy.html: 2019-01-12 - Transition freeze Is there still time yet to get a fix in, or is it FUBAR already? Frank

Bug#918165: Broken with Thunderbird 60

Package: xul-ext-quotecolors Version: 0.3-5 Severity: grave The plugin is broken with Thunderbird 60 in stretch and sid, after installation it's disabled and only prints "Quote Colors is incompatible with Thunderbird 60.4". TB 60 was uploaded to stretch over two months ago (and three months ago

Bug#734101: marked as done (libjs-jquery-mobile: New Release)

Your message dated Thu, 03 Jan 2019 22:20:36 + with message-id and subject line Bug#734101: fixed in jquery-mobile 1.4.5+dfsg-1 has caused the Debian Bug report #734101, regarding libjs-jquery-mobile: New Release to be marked as done. This means that you claim that the problem has been dealt

Bug#918164: Broken with Thunderbird 60

Package: xul-ext-timeline Version: 0.5-5 Severity: grave The plugin is broken with Thunderbird 60 in stretch and sid, after installation it's disabled and only prints "Timeline is incompatible with Thunderbird 60.4". TB 60 was uploaded to stretch over two months ago (and three months ago to

Bug#918163: Broken in Stretch

Package: xul-ext-sieve Version: 0.2.3h+dfsg-1 Severity: grave The plugin is broken with Thunderbird 60 in stretch, after installation it's disabled and only prints "Sieve is incompatible with Thunderbird 60.4". TB 60 was uploaded to stretch over two months ago, given that noone filed a bug so

Processed: Re: Bug#918153: lnav: FTBFS (failing test)

Processing control commands: > tags -1 -help Bug #918153 [src:lnav] lnav: FTBFS (failing test) Removed tag(s) help. -- 918153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#918162: Broken with Thunderbird 60

Package: xul-ext-exteditor Version: 1.0.2-2 Severity: grave The plugin is broken with Thunderbird 60 in stretch and sid, after installation it's disabled and only prints "External Editor is incompatible with Thunderbird 60.4". TB 60 was uploaded to stretch over two months ago (and three months

Bug#918153: lnav: FTBFS (failing test)

Control: tags -1 -help On Thu, Jan 03, 2019 at 10:24:50PM +0100, Santiago Vila wrote: > Note: I triggered rebuilds on reproducible-builds and now the failures > on testing/amd64 and unstable/amd64 are both as follows: > > -2018-11-03 09:23:38.000 > -2018-11-03 09:23:38.000 > -2018-11-03

Processed: severity of 910627 is serious

Processing commands for cont...@bugs.debian.org: > severity 910627 serious Bug #910627 [xul-ext-nostalgy] xul-ext-nostalgy: Please update to upstream 0.2.36 to be compatible with TB 60+ Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need

Bug#870344: [Pkg-mozext-maintainers] Bug#870344: New upstream release supporting Firefox 57+

On Tue, Aug 01, 2017 at 10:02:39AM -0400, Sean Whitton wrote: > Hello Damyan, > > On Tue, Aug 01, 2017 at 08:58:38AM +, Damyan Ivanov wrote: > > When firefox hits unstable (probably towards the end of this year) this > > bug will become grave. > > I think that it will only become grave once

Bug#918161: ros-image-common: stop depending on yaml-cpp0.3

Package: ros-image-common Version: 1.11.13-2 Severity: serious Dear maintainer, Your package is the only reverse-dependency left of yaml-cpp0.3, which I intend to remove after this bug is fixed. Your package builds successfully with yaml-cpp, please switch to it. I'm filing as serious because

Processed: affects 918157

Processing commands for cont...@bugs.debian.org: > affects 918157 src:med-fichier Bug #918157 [src:openmpi] openmpi seems broken on 32 bits architectures Added indication that 918157 affects src:med-fichier > thanks Stopping processing here. Please contact me if you need assistance. -- 918157:

Bug#914556: marked as done (linux: FTBFS on arm64: changed ABI)

Your message dated Thu, 03 Jan 2019 21:47:17 + with message-id and subject line Bug#914556: fixed in linux 4.9.144-1 has caused the Debian Bug report #914556, regarding linux: FTBFS on arm64: changed ABI to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#896230: marked as done (python-gpod: gpod fails to import)

Your message dated Thu, 03 Jan 2019 21:47:16 + with message-id and subject line Bug#896230: fixed in libgpod 0.8.3-8.2+deb9u1 has caused the Debian Bug report #896230, regarding python-gpod: gpod fails to import to be marked as done. This means that you claim that the problem has been dealt

Bug#913005: marked as done (ruby-rack: CVE-2018-16471: Possible XSS vulnerability in Rack)

Your message dated Thu, 03 Jan 2019 21:47:19 + with message-id and subject line Bug#913005: fixed in ruby-rack 1.6.4-4+deb9u1 has caused the Debian Bug report #913005, regarding ruby-rack: CVE-2018-16471: Possible XSS vulnerability in Rack to be marked as done. This means that you claim that

Bug#864546: marked as done (sympa: shipped file missing after upgrade from jessie to stretch: /etc/sympa/sympa.conf-smime.in)

Your message dated Thu, 03 Jan 2019 21:47:19 + with message-id and subject line Bug#864546: fixed in sympa 6.2.16~dfsg-3+deb9u2 has caused the Debian Bug report #864546, regarding sympa: shipped file missing after upgrade from jessie to stretch: /etc/sympa/sympa.conf-smime.in to be marked as

Bug#863701: marked as done (sympa: insists that cookie has changed when it hasn't)

Your message dated Thu, 03 Jan 2019 21:47:19 + with message-id and subject line Bug#863701: fixed in sympa 6.2.16~dfsg-3+deb9u2 has caused the Debian Bug report #863701, regarding sympa: insists that cookie has changed when it hasn't to be marked as done. This means that you claim that the

Bug#918153: lnav: FTBFS (failing test)

On Thu, Jan 03, 2019 at 10:22:34PM +0100, Salvatore Bonaccorso wrote: > Something recent must have now caused that lnav FTBFS, My guess would be that the test is not well designed and it fails on certain dates (for example, "at the end or beginning of the year"). Maybe this theory could be

Bug#918157: openmpi seems broken on 32 bits architectures

Source: openmpi Version: 3.1.3-7 Severity: grave Justification: renders package unusable on 32 bits architectures -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, The last med-fichier upload FTBFS on 32 bits architectures[1] with this error: Launching filterBlockOfentities with 2 processes

Bug#918153: lnav: FTBFS (failing test)

Note: I triggered rebuilds on reproducible-builds and now the failures on testing/amd64 and unstable/amd64 are both as follows: -2018-11-03 09:23:38.000 -2018-11-03 09:23:38.000 -2018-11-03 09:23:38.000 +2020-11-03 09:23:38.000 +2020-11-03 09:23:38.000 +2020-11-03 09:23:38.000 Sorry, I

Bug#917956: marked as done (libpillowfight: Incomplete debian/copyright?)

Your message dated Thu, 03 Jan 2019 21:22:52 + with message-id and subject line Bug#917956: fixed in libpillowfight 0.2.4-2 has caused the Debian Bug report #917956, regarding libpillowfight: Incomplete debian/copyright? to be marked as done. This means that you claim that the problem has

Bug#917987: marked as done (libpillowfight: FTBFS (missing build-depends on cmake))

Your message dated Thu, 03 Jan 2019 21:22:52 + with message-id and subject line Bug#917987: fixed in libpillowfight 0.2.4-2 has caused the Debian Bug report #917987, regarding libpillowfight: FTBFS (missing build-depends on cmake) to be marked as done. This means that you claim that the

Bug#918153: lnav: FTBFS (failing test)

Control: tags -1 + confirmed help Hi Santiago, On Thu, Jan 03, 2019 at 09:06:05PM +, Santiago Vila wrote: > Package: src:lnav > Version: 0.8.4-4 > Severity: serious > Tags: ftbfs > > Hello Salvatore. > > I tried to build this package in buster but it failed: > >

Processed: Re: Bug#918153: lnav: FTBFS (failing test)

Processing control commands: > tags -1 + confirmed help Bug #918153 [src:lnav] lnav: FTBFS (failing test) Added tag(s) confirmed and help. -- 918153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#816640: Bug #816640 in ruby-eventmachine marked as pending

* Hideki Yamane [190103 03:40]: > On Fri, 16 Feb 2018 13:48:16 + z...@debian.org wrote: > > Bug #816640 in ruby-eventmachine 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#918153: lnav: FTBFS (failing test)

Package: src:lnav Version: 0.8.4-4 Severity: serious Tags: ftbfs Hello Salvatore. I tried to build this package in buster but it failed: [...] debian/rules binary-arch dh binary-arch dh_update_autotools_config

Bug#910292: transition: libsrtp0-rm

Quoting Bernhard Schmidt (2019-01-03 19:12:38) > Hi, > > > Considering that your rdep is indirectly kde-standard, you should imho > > ask for removal from testing only once kopete is fixed… > > FTR, kopete is fixed and I've filed Bug#918136 for the removal of > src:srtp from testing. Great! -

Bug#916305: Workaround

I don't fully understand what is broken with the file, but a temporary workaround is to comment out the last elif statement in the file /usr/share/twms/tools/compile_correction.py and then rerun the upgrade. YMMV.

Processed: severity of 918146 is important

Processing commands for cont...@bugs.debian.org: > severity 918146 important Bug #918146 [src:yaml-cpp0.3] yaml-cpp0.3: CVE-2018-20574: Stack Overflow in SingleDocParser::HandleFlowMap() Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need

Bug#917638: marked as done (infnoise: Job dev-infnoise.device/start failed with result 'timeout')

Your message dated Thu, 3 Jan 2019 21:14:56 +0100 with message-id <20190103211456.144f5...@heffalump.sk2.org> and subject line Re: SOLVED. I am awfully sorry (Was: Bug#917638: infnoise: Job dev-infnoise.device/start failed with result 'timeout') has caused the Debian Bug report #917638, regarding

Processed: severity of 918145 is important

Processing commands for cont...@bugs.debian.org: > severity 918145 important Bug #918145 [src:yaml-cpp] yaml-cpp: CVE-2018-20574: Stack Overflow in SingleDocParser::HandleFlowMap() Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need

Bug#918145: yaml-cpp: CVE-2018-20574: Stack Overflow in SingleDocParser::HandleFlowMap()

Source: yaml-cpp Version: 0.5.3-0.2 Severity: grave Tags: security Forwarded: https://github.com/jbeder/yaml-cpp/issues/654 Control: clone -1 -2 Control: reassign -2 src:yaml-cpp0.3 0.3.0-1.2 Control: retitle -2 yaml-cpp0.3: CVE-2018-20574: Stack Overflow in SingleDocParser::HandleFlowMap() Hi,

Processed: yaml-cpp: CVE-2018-20574: Stack Overflow in SingleDocParser::HandleFlowMap()

Processing control commands: > clone -1 -2 Bug #918145 [src:yaml-cpp] yaml-cpp: CVE-2018-20574: Stack Overflow in SingleDocParser::HandleFlowMap() Bug 918145 cloned as bug 918146 > reassign -2 src:yaml-cpp0.3 0.3.0-1.2 Bug #918146 [src:yaml-cpp] yaml-cpp: CVE-2018-20574: Stack Overflow in

Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging

Just checking: are you Georg or Gregor currently working on this issue, and do you have any estimate when we could expect either a patch to MariaDB Connector C or a new upload of DBD-mysql so this issue would be resolved? It is currently the only thing left that stops the migration of

Bug#918144: Goopg API Error

Package: goopg Severity: serious thanks Goopg Gmail API calls are failing, returning a 400 code. e.g, 2019-01-03 14:43:12,509:INFO:Gmail:getting message #msg-a:r-505788724173301 2019-01-03

Bug#887601: marked as done (libcamlimages-ocaml: Detect freetype using pkg-config)

Your message dated Thu, 03 Jan 2019 19:34:11 + with message-id and subject line Bug#887601: fixed in camlimages 1:4.2.6-1 has caused the Debian Bug report #887601, regarding libcamlimages-ocaml: Detect freetype using pkg-config to be marked as done. This means that you claim that the problem

Bug#918140: linux-image-4.19.0-1-amd64: Samsung PM951 SSD in Dell XPS 15 9550 goes read-only

Package: src:linux Version: 4.19.12-1 Severity: critical Tags: upstream Justification: breaks the whole system Dear Maintainer, Submitting a bug report wherein after a kernel upgrade my laptop's SSD will, during use or idle, go into read-only mode after minutes or hours of uptime. It seems this

Processed: found 918012 in 1.21.0-3

Processing commands for cont...@bugs.debian.org: > found 918012 1.21.0-3 Bug #918012 [docker-compose] docker-compose: invalid version of python3-docker dependency Marked as found in versions docker-compose/1.21.0-3. > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: notfound 917968 in 4.2-1.1

Processing commands for cont...@bugs.debian.org: > notfound 917968 4.2-1.1 Bug #917968 [emms] emms: relies on default-major-mode (replaced by major-mode in emacs 26) No longer marked as found in versions emms/4.2-1.1. > thanks Stopping processing here. Please contact me if you need assistance.

Processed: found 917968 in 5.0-1

Processing commands for cont...@bugs.debian.org: > found 917968 5.0-1 Bug #917968 [emms] emms: relies on default-major-mode (replaced by major-mode in emacs 26) Marked as found in versions emms/5.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 917968:

Bug#910292: transition: libsrtp0-rm

Hi, > Considering that your rdep is indirectly kde-standard, you should imho > ask for removal from testing only once kopete is fixed… FTR, kopete is fixed and I've filed Bug#918136 for the removal of src:srtp from testing. Bernhard

Bug#912324: BleachBit causing error since updating Firefox to Firefox Quantum 60.0 ESR Fixed ?

Hi Hugo, I just tested bleachbit (2.0-2) on my Debian testing/sid and it is perfectly working (I got no error messages). I am using Firefox-ESR 60.4.0esr-1 from testing/main. So, as described in the bleachbit issue (See [1]), I think Firefox ESR 60 broke bleachbit. Regards, Jean-Marc

Bug#852199: Nix and non-standard-toplevel-dir

On Wed, 2 Jan 2019 at 20:28, Russ Allbery wrote: > If anything, they probably already know > how Nix works and are expecting it to use those paths. There doesn't seem > to be much drawback in this carefully-chosen lack of compliance with the > FHS. > > I don't think it's worth writing an

Processed: bug 917524 is not forwarded, tagging 917524

Processing commands for cont...@bugs.debian.org: > notforwarded 917524 Bug #917524 [initramfs-tools-core] initramfs-tools: Upgrade from initramfs-tools package fails Unset Bug forwarded-to-address > tags 917524 - fixed-upstream Bug #917524 [initramfs-tools-core] initramfs-tools: Upgrade from

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

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

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

Processed: gazebo: autopkgtest fails due to invalid gazebo.pc

Processing control commands: > block 917323 by -1 Bug #917323 [release.debian.org] transition: gdal 917323 was not blocked by any bugs. 917323 was not blocking any bugs. Added blocking bug(s) of 917323: 918128 -- 917323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917323 918128:

Bug#918128: gazebo: autopkgtest fails due to invalid gazebo.pc

Source: gazebo Version: 9.4.1+dfsg-1 Severity: serious Tags: patch Justification: makes the package in question unusable or mostly so Control: block 917323 by -1 Dear Maintainer, The autopkgtest for gazebo is failing due to an invalid gazebo.pc: autopkgtest [12:48:58]: test build:

Bug#917808: marked as done (mit-scheme: FTBFS when built with dpkg-buildpackage -A)

Your message dated Thu, 03 Jan 2019 16:21:09 + with message-id and subject line Bug#917808: fixed in mit-scheme 10.1.3-2 has caused the Debian Bug report #917808, regarding mit-scheme: FTBFS when built with dpkg-buildpackage -A to be marked as done. This means that you claim that the problem

Bug#918088: Acknowledgement (autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)")

Maybe the backtrace with libkrb5-dbg installed may provider more clues: root@dagon:~# gdb /usr/sbin/automount /core GNU gdb (Debian 8.2-1) 8.2 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software:

Bug#918060: marked as done (iwyu FTBFS on armel: undefined reference to symbol '__atomic_load_4@@LIBATOMIC_1.0')

Your message dated Thu, 03 Jan 2019 15:34:47 + with message-id and subject line Bug#918060: fixed in iwyu 7.0-3 has caused the Debian Bug report #918060, regarding iwyu FTBFS on armel: undefined reference to symbol '__atomic_load_4@@LIBATOMIC_1.0' to be marked as done. This means that you

Bug#825501: CVE-2016-4434

Hi everyone, Security team: thanks for your input. PuppetDB/Clojure maintainers: draft plan in this mail, feedback welcome. Moritz Mühlenhoff (2018-12-31): > On Mon, Dec 31, 2018 at 08:04:18AM +0100, Salvatore Bonaccorso wrote: > > Furthermore if we only update to 1.13 there are likely some of

Bug#918005: marked as done (gforth binary-all FTBFS: dh_missing failure)

Your message dated Thu, 03 Jan 2019 15:19:30 + with message-id and subject line Bug#918005: fixed in gforth 0.7.3+dfsg-9 has caused the Debian Bug report #918005, regarding gforth binary-all FTBFS: dh_missing failure to be marked as done. This means that you claim that the problem has been

Processed: your mail

Processing commands for cont...@bugs.debian.org: > clone 915112 -1 Bug #915112 {Done: Alastair McKinstry } [src:glew] pymol: FTBFS with glew 2.1 Bug 915112 cloned as bug 918123 915481 was blocked by: 915112 915481 was not blocking any bugs. Added blocking bug(s) of 915481: 918123 > reassign -1

Bug#918121: libgazebo9-dev: gazebo.pc has broken link flags

Package: libgazebo9-dev Version: 9.4.1+dfsg-1 Severity: serious Hi, libgazebo9-dev 9.4.1+dfsg-1+b2 (rebuilt for the gdal transition, though this breakage may or may not be related to gdal) ships a broken gazebo.pc: Libs: -Wl,-rpath,${prefix}/lib/x86_64-linux-gnu/gazebo-9/plugins -L${libdir}

Bug#918119: bugwarrior: Python 3.7: configparser: TypeError: option values must be strings

Package: bugwarrior Version: 1.5.1-2 Severity: grave Tags: upstream patch Justification: renders package unusable As reported [1] upstream, the bug makes bugwarrior crash at the very beginning with an error in 'configparser' used to parse the application configuration file because of empty

  1   2   >