Processed: control

2019-02-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 921305 important Bug #921305 [zfs-dkms] zfs-dkms: fails to upgrade from stretch Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 921305:

Bug#922936: Acknowledgement (ganeti: KVM/QEMU Virtual machines won't start after the last qemu-system-x86_64 update.)

2019-02-21 Thread Apollon Oikonomopoulos
Control: tags -1 + upstream fixed-upstream - newcomer Hi and thanks for the report! On 02:30 Fri 22 Feb , Paul Parsons wrote: > I can confirm, altering the following file, compiling it and restarting the > ganeti service restores functionality :- > >

Processed: Re: Bug#922936: Acknowledgement (ganeti: KVM/QEMU Virtual machines won't start after the last qemu-system-x86_64 update.)

2019-02-21 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + upstream fixed-upstream - newcomer Bug #922936 [ganeti] ganeti: KVM/QEMU Virtual machines won't start after the last qemu-system-x86_64 update. Added tag(s) fixed-upstream and upstream. Bug #922936 [ganeti] ganeti: KVM/QEMU Virtual machines won't start

Processed: tagging 922936

2019-02-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 922936 + pending Bug #922936 [ganeti] ganeti: KVM/QEMU Virtual machines won't start after the last qemu-system-x86_64 update. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 922936:

Bug#922936: Acknowledgement (ganeti: KVM/QEMU Virtual machines won't start after the last qemu-system-x86_64 update.)

2019-02-21 Thread Paul Parsons
I can confirm, altering the following file, compiling it and restarting the ganeti service restores functionality :- /usr/share/ganeti/2.16/ganeti/hypervisor/hv_kvm/__init__.py Ln1286 - kvm_cmd.extend(["*-device", "virtio-balloon*"]) On Fri, 22 Feb 2019 at 01:30, Debian Bug Tracking System <

Bug#905309: nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing

2019-02-21 Thread Allan Wind
nvidia-driver 390.87 crashes the kernel on the host where I had this issue, so I think the technical correct answer is "unknown". This is an intermittent issue, at times minutes apart, but mostly weeks or months. Is the required hard reboot that really makes this awful. If it helps, I can

Bug#905309: nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing

2019-02-21 Thread Andreas Beckmann
Control: tag -1 moreinfo upstream On 2018-08-03 02:25, Allan Wind wrote: > Package: nvidia-driver > Version: 384.130-1 > I noticed the fan on my laptop was spinning at full speed which > signifies heavy load.  Screens suspended, and they don't unsuspend when > I pressed the keyboard.  I ssh into

Processed: Re: Bug#905309: nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing

2019-02-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 moreinfo upstream Bug #905309 [nvidia-driver] nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x); continuing Added tag(s) upstream and moreinfo. -- 905309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905309 Debian Bug Tracking

Bug#922936: ganeti: KVM/QEMU Virtual machines won't start after the last qemu-system-x86_64 update.

2019-02-21 Thread Paul Parsons
Package: ganeti Version: 2.16.0-4 Severity: grave Tags: newcomer Justification: renders package unusable Dear Maintainer, After performing the usual apt upgrade on my system, I found Ganeti was unable to start my virtual machines. The error message, from qemu, was that -balloon was an invalid

Bug#922497: BUG: unable to handle kernel paging request at ffff9b30a7cb488

2019-02-21 Thread Allan Wind
Thanks Andreas. I doubt NVIDIA will spend any cycles on troubleshooting issues with an older driver. About a year ago I reported #905309 to the forum that NVIDIA says is the official support channel for Linux driver issues. I never heard back. The main reason why I filed the bug report

Bug#875358: Powermock RC #875358

2019-02-21 Thread Markus Koschany
Hi, powermock has been failing to build from source since we introduced OpenJDK 9 to Debian. It has not been removed yet because several packages build-depend on it. reverse-depends -b libpowermock-java Reverse-Build-Depends-Indep === * jline2 Reverse-Build-Depends

Processed: Re: Bug#922497: BUG: unable to handle kernel paging request at ffff9b30a7cb488

2019-02-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 upstream Bug #922497 [nvidia-driver] BUG: unable to handle kernel paging request at 9b30a7cb488 Added tag(s) upstream. -- 922497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922497 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#922497: BUG: unable to handle kernel paging request at ffff9b30a7cb488

2019-02-21 Thread Andreas Beckmann
Control: tag -1 upstream On 2019-02-17 07:40, Allan Wind wrote: > The stable release 9.8 contained an upgrade of nvidia-drivers from > 384.130-1 to 390.87-8~deb9u1 which caused my system hang during > subsequent boots.  The release also contains a linux-image update, and I > installed a known

Bug#922878: Upstream fixes available

2019-02-21 Thread Kjetil Kjernsmo
Hi all! So, I gotta admit as upstream dev of two of the modules that failed, that this is partly my fault. And I am happy to report that I have fixed it upstream for two packages. The root cause is that librdf-ns-perl is based on a crowd-sourced database, and sometimes crowd-sourced things

Bug#859553: pidentd: Please migrate to openssl1.1 in buster

2019-02-21 Thread Moritz Muehlenhoff
On Thu, Feb 21, 2019 at 11:37:02PM +0100, Sebastian Andrzej Siewior wrote: > On 2019-02-21 23:18:33 [+0100], Moritz Muehlenhoff wrote: > > On Thu, Feb 21, 2019 at 08:56:14PM +0100, Sebastian Andrzej Siewior wrote: > > > Its popcon is dropping. It will not be part of Buster. So either RM it > > >

Bug#859553: pidentd: Please migrate to openssl1.1 in buster

2019-02-21 Thread Sebastian Andrzej Siewior
On 2019-02-21 23:18:33 [+0100], Moritz Muehlenhoff wrote: > On Thu, Feb 21, 2019 at 08:56:14PM +0100, Sebastian Andrzej Siewior wrote: > > Its popcon is dropping. It will not be part of Buster. So either RM it > > or > > I have no use it for, I was just looking at it because it's one of the >

Bug#859553: pidentd: Please migrate to openssl1.1 in buster

2019-02-21 Thread Moritz Muehlenhoff
On Thu, Feb 21, 2019 at 08:56:14PM +0100, Sebastian Andrzej Siewior wrote: > Its popcon is dropping. It will not be part of Buster. So either RM it > or I have no use it for, I was just looking at it because it's one of the five packages blocking the removal of src:openssl1.0, from my PoV it can

Bug#922928: cyrus-common: /usr/share/man/man8/restore.8.gz is already provided by the dump package

2019-02-21 Thread Andreas Beckmann
Package: cyrus-common Version: 3.0.8-2 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 without declaring a Breaks+Replaces relation. See policy 7.6

Bug#922927: embree-tools: /usr/bin/convert is already provided by graphicsmagick-imagemagick-compat

2019-02-21 Thread Andreas Beckmann
Package: embree-tools Version: 3.5.0+dfsg-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 to the bottom...):

Bug#922926: commit-patch: fails to install along xemacs21: Invalid read syntax: "Weird old-backquote syntax"

2019-02-21 Thread Andreas Beckmann
Package: commit-patch Version: 2.6-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the

Processed: tagging 922390, tagging 922773, reassign 919928 to src:python-pysam, fixed 919928 in 0.15.2+ds-2 ...

2019-02-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 922390 + sid buster Bug #922390 [src:hydroffice.bag] hydroffice.bag: FTBFS (Could not import extension sphinx.ext.pngmath) Added tag(s) sid and buster. > tags 922773 + sid buster Bug #922773 [src:adequate] FTBFS since the acl/attr uploads

Processed (with 1 error): forcibly merging 761672 761670

2019-02-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 761672 761670 Bug #761672 {Done: Laszlo Boszormenyi (GCS) } [node-utilities] node-utilities build-depends on itself Bug #761670 {Done: Xavier } [node-utilities] impossible to bootstrap build of node-jake and node-utilities:

Bug#922739: marked as done (r-cran-vegan: autopkgtest regression)

2019-02-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Feb 2019 20:39:24 + with message-id and subject line Bug#922739: fixed in r-cran-vegan 2.5-4+dfsg-3 has caused the Debian Bug report #922739, regarding r-cran-vegan: autopkgtest regression to be marked as done. This means that you claim that the problem has been

Bug#776246: Processed: severity of 776246 is grave

2019-02-21 Thread Valentin Vidic
On Tue, Feb 19, 2019 at 10:26:09AM +0100, Christoph Martin wrote: > What can we do to not loose these packages (burp in my case)? > > librsync 2.0.2-1~exp1 was uploaded to experimental three days ago. csync2 seems to build fine with librsync2 from experimental so if you can upload that to

Processed: unblock 919048 with 920953

2019-02-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unblock 919048 with 920953 Bug #919048 {Done: Cédric Boutillier } [ruby-haml-rails] ruby-haml-rails: Depends: ruby-haml (< 5.0) but 5.0.4-1 is to be installed 919048 was blocked by: 920953 919048 was not blocking any bugs. Removed blocking

Bug#919048: fixed in unstable : should postpone autoremoval from testing

2019-02-21 Thread Cédric Boutillier
Hi, This bug has been fixed with 1.0.0-1. ruby-haml-rails is flagged for autoremoval in 19 hours. Hoping that writing to this bug will postpone the autoremoval to let the package from unstable migrate to testing in time. Cédric

Bug#859553: pidentd: Please migrate to openssl1.1 in buster

2019-02-21 Thread Sebastian Andrzej Siewior
On 2019-02-20 23:09:11 [+0100], Moritz Mühlenhoff wrote: > On Wed, Feb 20, 2019 at 08:51:16AM +0100, Moritz Muehlenhoff wrote: > > On Wed, Feb 20, 2019 at 12:28:48AM +0100, Sebastian Andrzej Siewior wrote: > > > On 2017-10-12 23:44:37 [+0200], To 859...@bugs.debian.org wrote: > > > > this is a

Bug#922256: marked as done (nitime: FTBFS (Could not import extension sphinx.ext.pngmath))

2019-02-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Feb 2019 19:20:05 + with message-id and subject line Bug#922256: fixed in nitime 0.7-2 has caused the Debian Bug report #922256, regarding nitime: FTBFS (Could not import extension sphinx.ext.pngmath) to be marked as done. This means that you claim that the problem

Bug#922739: fixed in r-cran-vegan 2.5-4+dfsg-2

2019-02-21 Thread Paul Gevers
Control: reopen -1 On Wed, 20 Feb 2019 10:34:34 + Andreas Tille wrote: > r-cran-vegan (2.5-4+dfsg-2) unstable; urgency=medium > . >* Fix and enhance autopkgtest > Closes: #922739 Enhanced, maybe, but the autopkgtest is not fixed yet on the ci.d.n interface: Paul

Processed: Re: Bug#922739: fixed in r-cran-vegan 2.5-4+dfsg-2

2019-02-21 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #922739 {Done: Andreas Tille } [src:r-cran-vegan] r-cran-vegan: autopkgtest regression 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer

Bug#922457: marked as done (fonts-roboto-hinted: update broke reverse-dependencies without notice)

2019-02-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Feb 2019 18:34:17 + with message-id and subject line Bug#922457: fixed in fonts-roboto 2:0~20170802-2 has caused the Debian Bug report #922457, regarding fonts-roboto-hinted: update broke reverse-dependencies without notice to be marked as done. This means that you

Processed: retitle 922503 to espeakup 0.80+deb9u2 is damaged

2019-02-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 922503 espeakup 0.80+deb9u2 is damaged Bug #922503 {Done: Samuel Thibault } [espeakup] espeakup 0.80+deb9u3 is damaged Changed Bug title to 'espeakup 0.80+deb9u2 is damaged' from 'espeakup 0.80+deb9u3 is damaged'. > thanks Stopping

Bug#922457: Bug #922457 in fonts-roboto marked as pending

2019-02-21 Thread Andrej Shadura
Control: tag -1 pending Hello, Bug #922457 in fonts-roboto 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 #922457 in fonts-roboto marked as pending

2019-02-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #922457 [fonts-roboto-hinted] fonts-roboto-hinted: update broke reverse-dependencies without notice Added tag(s) pending. -- 922457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922457 Debian Bug Tracking System Contact

Bug#922457: [Pkg-fonts-devel] Bug#922457: fonts-roboto-hinted: update broke reverse-dependencies without notice

2019-02-21 Thread Jonas Smedegaard
Quoting Andrej Shadura (2019-02-21 18:58:22) > Hi, > > On Sat, 16 Feb 2019 12:53:58 +0100 Markus Koschany wrote: > > Dear maintainer, > > > > the recent upload of fonts-roboto broke reverse-dependencies like > > renpy because you removed or renamed previously installed files in > >

Processed: tagging 920442

2019-02-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 920442 + ftbfs Bug #920442 [libcaca] libcaca FTBFS in unstable Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 920442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920442 Debian Bug

Processed: #919356 is pending

2019-02-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 919356 + pending Bug #919356 [dwarves-dfsg] dwarves-dfsg: Copyright/licensing is unclear Added tag(s) pending. > -- Stopping processing here. Please contact me if you need assistance. -- 919356:

Bug#922878: marked as done (librdf-ns-perl: 20181102-1 breaks at least 3 reverse dependencies)

2019-02-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Feb 2019 18:04:24 + with message-id and subject line Bug#922878: fixed in librdf-ns-perl 20181102-2 has caused the Debian Bug report #922878, regarding librdf-ns-perl: 20181102-1 breaks at least 3 reverse dependencies to be marked as done. This means that you claim

Bug#922457: fonts-roboto-hinted: update broke reverse-dependencies without notice

2019-02-21 Thread Andrej Shadura
Hi, On Sat, 16 Feb 2019 12:53:58 +0100 Markus Koschany wrote: > Dear maintainer, > > the recent upload of fonts-roboto broke reverse-dependencies like > renpy because you removed or renamed previously installed files in > fonts-roboto-hinted. I find that less than optimal given that we have >

Bug#922878: Bug #922878 in librdf-ns-perl marked as pending

2019-02-21 Thread Jonas Smedegaard
Control: tag -1 pending Hello, Bug #922878 in librdf-ns-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug #922878 in librdf-ns-perl marked as pending

2019-02-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #922878 [librdf-ns-perl] librdf-ns-perl: 20181102-1 breaks at least 3 reverse dependencies Added tag(s) pending. -- 922878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922878 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#922453: fixed in cernlib 20061220+dfsg3-4.4

2019-02-21 Thread Gilles Filippini
Hi Andreas, Andreas Beckmann a écrit le 21/02/2019 à 17:09 : > if I understand this bug correctly, now paw still needs to be binNMUed > against the fixed cernlib since it is linked statically. Yep, I've filed #922484 to binnmu paw, mclibs and geant321. > Also, does this bug affect stretch, too?

Bug#922878: librdf-ns-perl: 20181102-1 breaks at least 3 reverse dependencies

2019-02-21 Thread gregor herrmann
Package: librdf-ns-perl Version: 20181102-1 Severity: serious Justification: breaks other packages -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As first seen on ci.d.n, the new librdf-ns-perl 20181102-1 breaks the testsuite of at least 3 packages:

Bug#922453: fixed in cernlib 20061220+dfsg3-4.4

2019-02-21 Thread Andreas Beckmann
Hi Gilles, if I understand this bug correctly, now paw still needs to be binNMUed against the fixed cernlib since it is linked statically. Also, does this bug affect stretch, too? (I have no idea how to check this.) Andreas

Bug#915805: Should this package be removed?

2019-02-21 Thread Mattia Rizzolo
Hi, On Thu, Feb 21, 2019 at 10:02:01AM +, Kevin Smith wrote: > The packages are with mattia for uploading, but I know he’s very busy > so hasn’t looked at them yet. Should we go another way to get them > checked and uploaded? Sorry for waiting so long, it slipped through a few craks… I just

Bug#922869: FTBFS: test failures / newly created file is older than distributed files

2019-02-21 Thread Vincent Lefevre
Source: libtool Version: 2.4.6-10 Severity: serious I got the following error: ## - ## ## Test results. ## ## - ## ERROR: 150 tests were run, 15 failed (4 expected failures). 20 tests were skipped. ## ## ## Summary of the failures. ## ##

Bug#921801: marked as done (packaging-tutorial: FTBFS (LaTeX error))

2019-02-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Feb 2019 14:50:23 + with message-id and subject line Bug#921801: fixed in packaging-tutorial 0.22 has caused the Debian Bug report #921801, regarding packaging-tutorial: FTBFS (LaTeX error) to be marked as done. This means that you claim that the problem has been

Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?

2019-02-21 Thread Ian Jackson
Steve McIntyre writes ("Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?"): > There is a deeper worry about builds that may be done against the > "weak" background. Although buildd chroots are easily fixed up, > there's going to be a (small, but unknown) set of

Bug#922863: tomcat8: post-installation script subprocess failed during upgrade

2019-02-21 Thread Vincent Lefevre
Package: tomcat8 Version: 8.5.38-1 Severity: grave Justification: renders package unusable During upgrade: [...] Setting up tomcat8 (8.5.38-1) ... [ ok ] Stopping Tomcat servlet engine: tomcat8. [FAIL] Starting Tomcat servlet engine: tomcat8 failed! invoke-rc.d: initscript tomcat8, action

Bug#922831: marked as done (Uninstallable build dependencies)

2019-02-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Feb 2019 13:35:15 + with message-id and subject line Bug#922831: fixed in node-es6-promise 4.2.5-2 has caused the Debian Bug report #922831, regarding Uninstallable build dependencies to be marked as done. This means that you claim that the problem has been dealt

Bug#922288: ruby-rails-assets-chartjs: doesn't build from upstream source

2019-02-21 Thread Pirate Praveen
On Mon, 18 Feb 2019 19:09:53 +0530 Pirate Praveen wrote: > It was originally packaged for gitlab and since we could not complete > packaging all dependencies of gitlab, this was not a priority for > buster. I was intending to get gitlab back in main including fix for > this in time for bullseye.

Bug#922730: cannot browse anything

2019-02-21 Thread Alberto Garcia
On Wed, Feb 20, 2019 at 07:00:07AM +0800, 積丹尼 Dan Jacobson wrote: > Package: epiphany-browser > Version: 3.31.91-2 > Severity: grave > > $ mkdir /tmp/p > $ HOME=/tmp/p epiphany /etc/motd > > ** (epiphany:11842): WARNING **: 06:53:40.412: Web process crashed If the web process crashed then it

Bug#916606: marked as done (lbreakout2: randomly pauses ingame without external actions)

2019-02-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Feb 2019 12:34:09 + with message-id and subject line Bug#916606: fixed in lbreakout2 2.6.5-2 has caused the Debian Bug report #916606, regarding lbreakout2: randomly pauses ingame without external actions to be marked as done. This means that you claim that the

Bug#916606: Maintaining lbreakout2 in Debian Games team (Was: Bug#916606: Possible cause)

2019-02-21 Thread Andreas Tille
Hi Colin, On Thu, Feb 21, 2019 at 10:37:03AM +, Colin Tuckley wrote: > On 21/02/2019 07:51, Andreas Tille wrote: > > > I will apply the patch and do a team upload. Since I can not see any > > activity of Colin Tuckley I think it might be a good idea to move the > > package to Debian Games

Bug#919714: marked as done (satpy build depends on python3-h5netcdf that is currently not in buster)

2019-02-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Feb 2019 11:49:22 + with message-id and subject line Bug#919714: fixed in satpy 0.12.0-1 has caused the Debian Bug report #919714, regarding satpy build depends on python3-h5netcdf that is currently not in buster to be marked as done. This means that you claim

Bug#922537: closing 922537

2019-02-21 Thread Salvatore Bonaccorso
close 922537 2.7.7+dfsg-1 thanks Fixed with new upstream version 2.7.7.

Processed: closing 922537

2019-02-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 922537 2.7.7+dfsg-1 Bug #922537 [src:ansible] ansible: CVE-2019-3828 Marked as fixed in versions ansible/2.7.7+dfsg-1. Bug #922537 [src:ansible] ansible: CVE-2019-3828 Marked Bug as done > thanks Stopping processing here. Please contact me

Bug#922772: redmine: start via unicorn fails

2019-02-21 Thread Jörg-Volker Peetz
Dear Maintainer team, for clearness I also append my redmine/config/environment.rb which I modified to run the redmine server in a sub-URI. The problematic line seems to be line 16 RedmineApp::Application.routes.default_scope = { :path => ENV['RAILS_RELATIVE_URL_ROOT'] } before the application

Bug#916606: Maintaining lbreakout2 in Debian Games team (Was: Bug#916606: Possible cause)

2019-02-21 Thread Colin Tuckley
On 21/02/2019 07:51, Andreas Tille wrote: > I will apply the patch and do a team upload. Since I can not see any > activity of Colin Tuckley I think it might be a good idea to move the > package to Debian Games team. Colin, if I do not hear from you I assume > you are OK with this if I put you

Bug#922831: Uninstallable build dependencies

2019-02-21 Thread Sjoerd Simons
Source: node-es6-promise Version: 4.2.5-1 Severity: serious On a buster docker image: ``` # apt-get build-dep node-es6-promise Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an

Bug#915805: Should this package be removed?

2019-02-21 Thread Kevin Smith
On 20 Feb 2019, at 22:19, Moritz Mühlenhoff wrote: > > On Tue, Jan 15, 2019 at 10:31:17AM +, Kevin Smith wrote: >> On 27 Dec 2018, at 22:52, Moritz Mühlenhoff wrote: >>> >>> On Fri, Dec 07, 2018 at 01:41:47PM +, Kevin Smith wrote: Apologies, I’d forgotten that we’d prepared an

Processed: Re: Maintaining lbreakout2 in Debian Games team (Was: Bug#916606: Possible cause)

2019-02-21 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch pending Bug #916606 [lbreakout2] lbreakout2: randomly pauses ingame without external actions Added tag(s) pending. -- 916606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916606 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#916606: Maintaining lbreakout2 in Debian Games team (Was: Bug#916606: Possible cause)

2019-02-21 Thread Andreas Tille
Control: tags -1 patch pending Hi again, as followup to my last mail I have pushed what I'm considering to be ready for Upload to https://salsa.debian.org/games-team/lbreakout2 Colin, if I do not hear from you soon (next 24h) I'll upload to make sure lbreakout2 will make it into Buster

Bug#761670: marked as done (impossible to bootstrap build of node-jake and node-utilities: (build-)dependency loop)

2019-02-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Feb 2019 09:30:10 +0100 with message-id and subject line Closing has caused the Debian Bug report #761670, regarding impossible to bootstrap build of node-jake and node-utilities: (build-)dependency loop to be marked as done. This means that you claim that the problem

Processed: fixed 761670 in 1.0.4-1, found 761670 in 0.0.31-1

2019-02-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 761670 1.0.4-1 Bug #761670 [node-utilities] impossible to bootstrap build of node-jake and node-utilities: (build-)dependency loop Marked as fixed in versions node-utilities/1.0.4-1. > found 761670 0.0.31-1 Bug #761670 [node-utilities]

Processed (with 2 errors): unarchiving 761672, forcibly merging 761672 761670

2019-02-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 761672 > forcemerge 761672 761670 Bug #761672 {Done: Laszlo Boszormenyi (GCS) } [node-utilities] node-utilities build-depends on itself Bug #761670 [node-utilities] impossible to bootstrap build of node-jake and node-utilities:

Processed (with 1 error): unarchiving 761672, forcibly merging 761672 761670

2019-02-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 761672 Bug #761672 {Done: Laszlo Boszormenyi (GCS) } [node-utilities] node-utilities build-depends on itself Unarchived Bug 761672 > forcemerge 761672 761670 Bug #761672 {Done: Laszlo Boszormenyi (GCS) } [node-utilities]