Processed: Bug #919103 in libreoffice marked as pending

Processing control commands: > tag -1 pending Bug #919103 [libreoffice-kde5] libreoffice-kde5: failure to upgrade from stretch: soffice.odg also in libreoffice-kde Added tag(s) pending. -- 919103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919103 Debian Bug Tracking System Contact

Bug#919103: Bug #919103 in libreoffice marked as pending

Control: tag -1 pending Hello, Bug #919103 in libreoffice 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#914632: uw-imap: CVE-2018-19518

Hi Magnus, On Fri, Dec 28, 2018 at 10:22:53AM +0100, Moritz Mühlenhoff wrote: > On Wed, Dec 26, 2018 at 05:20:40PM +0100, Magnus Holmgren wrote: > > > CVE-2018-19518[0]: > > > | University of Washington IMAP Toolkit 2007f on UNIX, as used in > > > | imap_open() in PHP and other products, launches

Bug#912633: Status Update

Any idea when the new version that fixes this bug will be released? -- Soren Stoutner Small Business Tech Solutions so...@smallbusinesstech.net 623-262-6169

Bug#895039: marked as done (ido: deprecated in Debian, switch over to ayatana-ido)

Your message dated Sun, 13 Jan 2019 05:12:47 + with message-id and subject line Bug#919129: Removed package(s) from unstable has caused the Debian Bug report #895039, regarding ido: deprecated in Debian, switch over to ayatana-ido to be marked as done. This means that you claim that the

Processed: Re: xnbd FTBFS with glibc 2.28

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

Bug#916002: xnbd FTBFS with glibc 2.28

Control: tags -1 patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * d/p/glibc-2.28.patch: Fix FTBFS against glibc 2.28. Thanks for considering the patch. Logan Rosen -- System Information: Debian Release: buster/sid APT prefers cosmic-updates

Bug#919139: cli-common: Invalid maintainer email address

Package: cli-common Version: 0.9+nmu3 Severity: serious Justification: Policy 3.3 This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:

Bug#905674: parallel citation-begging issue

Hi Rogerio, I am writing in support of the recent patch to remove the citation message from Debian's version of GNU Parallel. This citation solicitation is actually quite troubling from an academic perspective, not just from a licensing standpoint. The assertion of Mr. Tange, the upstream

Bug#917761: marked as done (php-monolog: FTBFS: PHP Fatal error: Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in /<>/tests/Monolog/ErrorHandlerTest.php:16)

Your message dated Sun, 13 Jan 2019 02:45:49 + with message-id and subject line Bug#917761: fixed in php-monolog 1.24.0-1 has caused the Debian Bug report #917761, regarding php-monolog: FTBFS: PHP Fatal error: Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in

Bug#875404: gridengine and java

Control: tag -1 + help status update on this bug: I tried to get the build working months ago with the java10 branch on Salsa [1]. The current issue is an error when trying to use jemalloc, which I've reported upstream [2]. the error is [java] [java]

Processed: gridengine and java

Processing control commands: > tag -1 + help Bug #875404 [src:gridengine] FTBFS with Java 9: sun.rmi.server Added tag(s) help. -- 875404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: limit source to php-monolog, tagging 917761

Processing commands for cont...@bugs.debian.org: > limit source php-monolog Limiting to bugs with field 'source' containing at least one of 'php-monolog' Limit currently set to 'source':'php-monolog' > tags 917761 + pending Bug #917761 [src:php-monolog] php-monolog: FTBFS: PHP Fatal error:

Bug#918916: Unicorn not reporting proper version for gemfile?

Package: unicorn Version: 5.4.1-1 Followup-For: Bug #918916 For reference: As a workaround, changing _both_ versions in the shipped gemspec and the version in the filename from 0 to 5.4.1 fixes packages which depend on this, e.g. gitlab. Detailed steps: 1. Edit

Bug#916606: Possible cause

On Mon, 7 Jan 2019 08:59:30 +0100 Stephen Kitt wrote: > On Sat, Jan 05, 2019 at 03:32:02AM -0500, Full Name wrote: > > A similar problem occurs in DOSBox. I'm not sure if this is a bug in xorg > > or SDL. > > > > What is happening is that when you unpause, lbreakout2 tries to fence the > >

Bug#917700: dimbl: FTBFS: build-dependency not installable: libtimbl4-dev

Package: dimbl Followup-For: Bug #917700 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu disco ubuntu-patch Hello, FWIW, no new upstream version is required in order to fix this build failure, it's a trivial change to debian/control to drop the versioned -dev package names leaving

Bug#918260: ruby-protected-attributes: Depends: ruby-activemodel (< 2:5.0) but 2:5.2.0+dfsg-2 is to be installed

On Fri, 04 Jan 2019 22:00:09 +0200 Adrian Bunk wrote: > Source: ruby-protected-attributes > Version: 1.1.4-2 > Severity: serious > > The following packages have unmet dependencies: > ruby-protected-attributes : Depends: ruby-activemodel (< 2:5.0) but > 2:5.2.0+dfsg-2 is to be installed > > Sent

Processed: Sorry, wrong bug number

Processing commands for cont...@bugs.debian.org: > severity 827832 serious Bug #827832 [src:python-pytc] python-shade: Improvement of error message when failing to build on small machines (?) Severity set to 'serious' from 'minor' > retitle 827832 python-pytc: FTBFS: /bin/sh: 3:

Processed: Re: Investigation results

Processing commands for cont...@bugs.debian.org: > severity 918751 minor Bug #918751 [src:python-shade] python-shade: FTBFS in sid Severity set to 'minor' from 'serious' > retitle 918751 python-shade: Improvement of error message when failing to > build on small machines (?) Bug #918751

Bug#918751: Investigation results

severity 918751 minor retitle 918751 python-shade: Improvement of error message when failing to build on small machines (?) thanks Sorry, this was my fault. Here is the reason why it failed for me: This package (version 1.7.0) used to need 200 MB of RAM to build, and I was using a small

Bug#919002: marked as done (CVE's for systemd vulnerabilities CVE-2018-16864, CVE-2018-16865 and CVE-2018-16866)

Your message dated Sat, 12 Jan 2019 23:16:47 + with message-id and subject line Bug#918841: fixed in systemd 240-4 has caused the Debian Bug report #918841, regarding CVE's for systemd vulnerabilities CVE-2018-16864, CVE-2018-16865 and CVE-2018-16866 to be marked as done. This means that

Bug#918841: marked as done (systemd: CVE-2018-16864)

Your message dated Sat, 12 Jan 2019 23:16:47 + with message-id and subject line Bug#918841: fixed in systemd 240-4 has caused the Debian Bug report #918841, regarding systemd: CVE-2018-16864 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#918322: marked as done (4.19.0-1-amd64 kernel fails to boot with "Gave up waiting for root file system device")

Your message dated Sat, 12 Jan 2019 23:16:47 + with message-id and subject line Bug#917607: fixed in systemd 240-4 has caused the Debian Bug report #917607, regarding 4.19.0-1-amd64 kernel fails to boot with "Gave up waiting for root file system device" to be marked as done. This means that

Bug#918848: marked as done (systemd: CVE-2018-16865)

Your message dated Sat, 12 Jan 2019 23:16:47 + with message-id and subject line Bug#918848: fixed in systemd 240-4 has caused the Debian Bug report #918848, regarding systemd: CVE-2018-16865 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#919031: marked as done (libmono-system4.0-cil: not installable on amd64)

Your message dated Sat, 12 Jan 2019 23:15:49 + with message-id and subject line Bug#919031: fixed in mono 5.16.0.220+dfsg3-2 has caused the Debian Bug report #919031, regarding libmono-system4.0-cil: not installable on amd64 to be marked as done. This means that you claim that the problem

Bug#918751: Investigation results

severity 827832 minor retitle 827832 python-shade: Improvement of error message when failing to build on small machines (?) thanks Sorry, this was my fault. Here is the reason why it failed for me: This package (version 1.7.0) used to need 200 MB of RAM to build, and I was using a small

Processed: Re: Investigation results

Processing commands for cont...@bugs.debian.org: > severity 827832 minor Bug #827832 [src:python-pytc] python-pytc: FTBFS: /bin/sh: 3: pythonpython2.7-dbg: not found Severity set to 'minor' from 'serious' > retitle 827832 python-shade: Improvement of error message when failing to > build on

Bug#905443: marked as done (ball: FTBFS - test failures)

Your message dated Sat, 12 Jan 2019 23:00:12 + with message-id and subject line Bug#905443: fixed in ball 1.5.0+git20180813.37fc53c-1 has caused the Debian Bug report #905443, regarding ball: FTBFS - test failures to be marked as done. This means that you claim that the problem has been

Bug#784451: marked as done ([ball] Qt4's WebKit removal)

Your message dated Sat, 12 Jan 2019 23:00:12 + with message-id and subject line Bug#784451: fixed in ball 1.5.0+git20180813.37fc53c-1 has caused the Debian Bug report #784451, regarding [ball] Qt4's WebKit removal to be marked as done. This means that you claim that the problem has been

Processed: Re: Investigation results

Processing commands for cont...@bugs.debian.org: > owner 918751 sanv...@debian.org Bug #918751 [src:python-shade] python-shade: FTBFS in sid Owner changed from Stewart Ferguson to sanv...@debian.org. > thanks Stopping processing here. Please contact me if you need assistance. -- 918751:

Bug#918751: Investigation results

owner 918751 sanv...@debian.org thanks I believe this problem is not directly related with the number of CPUs. Will do some additional tests and will probably downgrade this myself if I confirm my current suspicious. Thanks.

Bug#904404: marked as done (liece-dcc: fails to install with emacs25)

Your message dated Sat, 12 Jan 2019 22:06:15 + with message-id and subject line Bug#904404: fixed in liece 2.0+0.20030527cvs-12 has caused the Debian Bug report #904404, regarding liece-dcc: fails to install with emacs25 to be marked as done. This means that you claim that the problem has

Bug#918733: marked as done (googletest FTBFS on mips/mipsel: out of memory)

Your message dated Sat, 12 Jan 2019 22:06:08 + with message-id and subject line Bug#918733: fixed in googletest 1.8.1-3 has caused the Debian Bug report #918733, regarding googletest FTBFS on mips/mipsel: out of memory to be marked as done. This means that you claim that the problem has been

Bug#912969: marked as done (gecode: FTBFS on mips and mipsel)

Your message dated Sat, 12 Jan 2019 22:05:59 + with message-id and subject line Bug#912969: fixed in gecode 6.1.0-2 has caused the Debian Bug report #912969, regarding gecode: FTBFS on mips and mipsel to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#885742: linsmith: GTK+ 3 / GooCanvas port may be available upstream

On Wed, 09 Jan 2019 07:24:00 +0200, Jeremy Bicha wrote: > We'd like to remove those libraries soon, but I am willing to wait a > bit longer for someone to port linsmith to gtk3. JFTR, I don't intend to work on this package. I don't have time at the moment, but more importantly I don't have the

Bug#741464: grub-pc-bin: hangs after displaying boot menu

Control: tag -1 +patch On Mon, 29 Oct 2018 00:36:00 +0100, Colin Watson wrote: > > On Sun, Feb 01, 2015 at 11:16:59PM +0100, Marco Gamberoni wrote: > > I see this same at_keyboard behaviour: working in VirtualBox, delivering > > garbage on this real hardware: > > - an HP Proliant DL380 Gen5

Processed: Re: Bug#741464: grub-pc-bin: hangs after displaying boot menu

Processing control commands: > tag -1 +patch Bug #741464 [grub-pc-bin] grub-pc-bin: freezes after "terminal_input at_keyboard" Added tag(s) patch. -- 741464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#918439: cockpit: FTBFS (failing tests)

On Sat, Jan 12, 2019 at 09:41:49PM +0100, Andreas Henriksson wrote: > It might be a good idea to first just test if all problems vanishes > if builting in a less network restricted environment, [...] I guess not, because I'm using plain sbuild on a stretch machine, which AFAIK does not have (by

Processed: gnome-phone-manager: diff for NMU version 0.69-2.1

Processing control commands: > tags 899530 + patch Bug #899530 [src:gnome-phone-manager] gnome-phone-manager: Invalid maintainer address pkg-bluetooth-maintain...@lists.alioth.debian.org Added tag(s) patch. > tags 899530 + pending Bug #899530 [src:gnome-phone-manager] gnome-phone-manager:

Bug#899530: gnome-phone-manager: diff for NMU version 0.69-2.1

Control: tags 899530 + patch Control: tags 899530 + pending Dear maintainer, I've prepared an NMU for gnome-phone-manager (versioned as 0.69-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan

Bug#918119: marked as done (bugwarrior: Python 3.7: configparser: TypeError: option values must be strings)

Your message dated Sat, 12 Jan 2019 21:19:30 + with message-id and subject line Bug#918119: fixed in bugwarrior 1.6.0-1 has caused the Debian Bug report #918119, regarding bugwarrior: Python 3.7: configparser: TypeError: option values must be strings to be marked as done. This means that

Processed: Fwd: Claiming bug 827832

Processing commands for cont...@bugs.debian.org: > owner 827832 ! Bug #827832 [src:python-pytc] python-pytc: FTBFS: /bin/sh: 3: pythonpython2.7-dbg: not found Owner recorded as Stewart Ferguson . > End of message, stopping processing here. Please contact me if you need assistance. -- 827832:

Processed: Move to the package where it was fixed

Processing commands for cont...@bugs.debian.org: > reassign 916710 src:glew Bug #916710 {Done: Alastair McKinstry } [src:info-beamer] info-beamer FTBFS with glew 2.1.0 Bug reassigned from package 'src:info-beamer' to 'src:glew'. No longer marked as found in versions

Bug#918841: Bug #918841 in systemd marked as pending

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

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

Processing control commands: > tag -1 pending Bug #917607 [udev] udev 240 Makes System Unbootable; rootfs Not Found Bug #918096 [udev] linux-image-4.19.0-1-amd64: disk and keyboard do not work - unusable even in recovery mode Bug #918322 [udev] 4.19.0-1-amd64 kernel fails to boot with "Gave up

Processed: Bug #918848 in systemd marked as pending

Processing control commands: > tag -1 pending Bug #918848 [src:systemd] systemd: CVE-2018-16865 Added tag(s) pending. -- 918848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#917607: Bug #917607 in systemd marked as pending

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

Processing control commands: > tag -1 pending Bug #918841 [src:systemd] systemd: CVE-2018-16864 Bug #919002 [src:systemd] CVE's for systemd vulnerabilities CVE-2018-16864, CVE-2018-16865 and CVE-2018-16866 Added tag(s) pending. Added tag(s) pending. -- 918841:

Bug#873016: [Pkg-javascript-devel] Bug#873016: node-lodash-packages: not preferred form for source: Should be built from node-lodash

Quoting Ivo De Decker (2019-01-12 17:18:02) > On Wed, Aug 23, 2017 at 11:41:28PM +0530, Pirate Praveen wrote: > > On ബുധന്‍ 23 ആഗസ്റ്റ് 2017 11:33 വൈകു, Jonas Smedegaard wrote: > > > Package: node-lodash-packages > > > Severity: serious > > > Justification: Policy 2.1 > > > > I do not think the

Bug#907015: [Pkg-openssl-devel] Bug#907015: marked as done (openssl version 1.1.1 breaks multiple reverse dependencies; versioned Breaks needed)

On 2019-01-12 15:51:03 [+], Debian Bug Tracking System wrote: > Paul just told me this should be ok now, so closing. Okay. We have one additional breaks in git. If anyone needs more, I don't mind adding them later if it helps… > Ivo Sebastian

Bug#917199: pivy, unbuildable on mips* due to testsuite failures in patchelf.

Control: reassign -1 src:pyside2 Control: retitle -1 pyside2 should build without patchelf also on mips+mipsel Control: affects -1 src:pivy On Sun, Dec 23, 2018 at 11:47:26PM +, peter green wrote: > Package: pivy > Version: 0.6.4-1 > Severity: serious > > pivy cannot be built on mips/mipsel

Bug#915290: marked as done (strace FTBFS with glibc 2.28)

Your message dated Sat, 12 Jan 2019 20:52:26 + with message-id and subject line Bug#915290: fixed in strace 4.26-0.1 has caused the Debian Bug report #915290, regarding strace FTBFS with glibc 2.28 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#918779: marked as done (r10k: uninitialized constant Cri::Error)

Your message dated Sat, 12 Jan 2019 20:50:54 + with message-id and subject line Bug#918779: fixed in r10k 3.1.0-1 has caused the Debian Bug report #918779, regarding r10k: uninitialized constant Cri::Error to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Re: Bug#917199: pivy, unbuildable on mips* due to testsuite failures in patchelf.

Processing control commands: > reassign -1 src:pyside2 Bug #917199 [pivy] pivy, unbuildable on mips* due to testsuite failures in patchelf. Bug reassigned from package 'pivy' to 'src:pyside2'. No longer marked as found in versions 0.6.4-1. Ignoring request to alter fixed versions of bug #917199

Bug#907277: autoconf: AC_SEARCH_LIBS with AC_LANG([C++]) broken when using gcc 8

Hi, autoconf developers, Debian gcc maintainers, In Debian there is a bug [1] reported on the autoconf package which relates to a change in gcc 8. After looking into the issue it's not completely clear to me what the best solution should be. The autoconf function AC_SEARCH_LIBS check the

Processed: Move to the source package so that the BTS knows it is fixed

Processing commands for cont...@bugs.debian.org: > reassign 874727 src:coin3 Bug #874727 {Done: Kurt Kremitzki } [libcoin80v5] libcoin80v5: Program using libcoin80v5 and any other library that uses lebexpat1 segfaults. Bug reassigned from package 'libcoin80v5' to 'src:coin3'. No longer marked

Bug#918439: cockpit: FTBFS (failing tests)

Hello, On Sun, Jan 06, 2019 at 12:55:49AM +, Santiago Vila wrote: > Package: src:cockpit > Version: 184-1 > Severity: serious > Tags: ftbfs [...] > > Testsuite summary for Cockpit 184 >

Bug#919095: marked as done (Please remove (build-)dependency on mongodb for buster)

Your message dated Sat, 12 Jan 2019 20:42:50 + with message-id and subject line Bug#919095: fixed in apache-log4j2 2.11.1-2 has caused the Debian Bug report #919095, regarding Please remove (build-)dependency on mongodb for buster to be marked as done. This means that you claim that the

Bug#919092: Bug#919095: Bug#919092: fixed in mongo-java-driver 3.6.3-2

On Sat, Jan 12, 2019 at 09:21:51PM +0100, Ivo De Decker wrote: > Hi Emmanuel, > > On Sat, Jan 12, 2019 at 07:35:09PM +, Emmanuel Bourg wrote: > >* Removed the unused build dependency on mongodb-server (Closes: #919092) > > Thanks for the quick fix. > > Does this mean #919095 can just be

Bug#905254: update of libphp-phpmailer to 6.0

Hi all, On Mon, 10 Dec 2018 12:03:04 +0100 Cyrille Bollu wrote: > Cacti: > > > Latest version of cacti upstream still uses PHPMailer 5.2.x. > > I've created a bug upstream: https://github.com/Cacti/cacti/issues/2206 Cacti upstream release a new version with phpmailer 6 embedded. I need

Processed: Investigation results

Processing commands for cont...@bugs.debian.org: > noowner 827832 Bug #827832 [src:python-pytc] python-pytc: FTBFS: /bin/sh: 3: pythonpython2.7-dbg: not found Removed annotation that Bug was owned by Stewart Ferguson . > thank you Stopping processing here. Please contact me if you need

Processed: closing 915574

Processing commands for cont...@bugs.debian.org: > close 915574 3.6.1+dfsg-5 Bug #915574 [libsimbody3.6] libsimbody3.6: missing Breaks+Replaces: libsimbody3.5v5 Marked as fixed in versions simbody/3.6.1+dfsg-5. Bug #915574 [libsimbody3.6] libsimbody3.6: missing Breaks+Replaces: libsimbody3.5v5

Bug#918751: Investigation results

noowner 827832 thank you The interesting part of the reporter's logs suggest that the following test fails: shade.tests.unit.test_object.TestObjectUploads.test_object_segment_retry_failure The failure is caused by a thread failing to spawn due to resource limitations on the reporter's machine.

Bug#919092: fixed in mongo-java-driver 3.6.3-2

Hi Emmanuel, On Sat, Jan 12, 2019 at 07:35:09PM +, Emmanuel Bourg wrote: >* Removed the unused build dependency on mongodb-server (Closes: #919092) Thanks for the quick fix. Does this mean #919095 can just be closed? apache-log4j2 only (build-)depends on libmongodb-java, not (directly)

Bug#919113: buildbot-doc: missing Breaks+Replaces: buildbot (<< 1.7.0)

Package: buildbot-doc Version: 1.7.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite other

Bug#919031: libmono-system4.0-cil: not installable on amd64

Another reason this bug makes no sense is there's no 5.18 references at all in src:mono, and it doesn't depend on anything externally which could add it.  I'll try a no-change version bump on another computer. On 12/01/2019 09:42, Ingo Saitz wrote: > On Fri, Jan 11, 2019 at 09:52:46PM -0500,

Bug#919081: kio-gdrive: Unable to create io-slave. klauncher said: error loading gdrive.so

Control: tags -1 unreproducible moreinfo Control: severity -1 important Hi Benoît! On Sat, Jan 12, 2019 at 03:45:30PM +0100, Benoît Merlet wrote: > > Dear Maintainer, > > After installing kio-gdrive and configuring a Google account in > systemsettings5, > I cannot connect to my Google Drive:

Processed: Re: Bug#919081: kio-gdrive: Unable to create io-slave. klauncher said: error loading gdrive.so

Processing control commands: > tags -1 unreproducible moreinfo Bug #919081 [kio-gdrive] kio-gdrive: Unable to create io-slave. klauncher said: error loading gdrive.so Added tag(s) unreproducible and moreinfo. > severity -1 important Bug #919081 [kio-gdrive] kio-gdrive: Unable to create io-slave.

Processed: tagging 919091

Processing commands for cont...@bugs.debian.org: > tags 919091 + buster sid Bug #919091 [loofah] Please remove (build-)dependency on mongodb for buster Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 919091:

Bug#912069: marked as done (flask-wtf FTBFS: FAIL: test_i18n_enabled (tests.test_i18n.TestI18NCase))

Your message dated Sat, 12 Jan 2019 19:49:08 + with message-id and subject line Bug#912069: fixed in flask-wtf 0.14.2-3 has caused the Debian Bug report #912069, regarding flask-wtf FTBFS: FAIL: test_i18n_enabled (tests.test_i18n.TestI18NCase) to be marked as done. This means that you claim

Bug#919092: marked as done (Please remove (build-)dependency on mongodb for buster)

Your message dated Sat, 12 Jan 2019 19:35:09 + with message-id and subject line Bug#919092: fixed in mongo-java-driver 3.6.3-2 has caused the Debian Bug report #919092, regarding Please remove (build-)dependency on mongodb for buster to be marked as done. This means that you claim that the

Processed: owner 919095

Processing commands for cont...@bugs.debian.org: > owner 919095 tmanc...@debian.org Bug #919095 [apache-log4j2] Please remove (build-)dependency on mongodb for buster Owner recorded as tmanc...@debian.org. > thanks Stopping processing here. Please contact me if you need assistance. -- 919095:

Processed: Bug 827832 fixed, but needs upload

Processing commands for cont...@bugs.debian.org: > tags 827832 + pending Bug #827832 [src:python-pytc] python-pytc: FTBFS: /bin/sh: 3: pythonpython2.7-dbg: not found Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 827832:

Processed: Bug #919092 in mongo-java-driver marked as pending

Processing control commands: > tag -1 pending Bug #919092 [mongo-java-driver] Please remove (build-)dependency on mongodb for buster Added tag(s) pending. -- 919092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919092 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#919092: Bug #919092 in mongo-java-driver marked as pending

Control: tag -1 pending Hello, Bug #919092 in mongo-java-driver 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#915834: marked as done (Breaks SSH connections, listens on \0)

Your message dated Sat, 12 Jan 2019 18:50:15 + with message-id and subject line Bug#915834: fixed in irqbalance 1.5.0-2 has caused the Debian Bug report #915834, regarding Breaks SSH connections, listens on \0 to be marked as done. This means that you claim that the problem has been dealt

Bug#918435: libgit-raw-perl: FTBFS (failing tests)

On Sun, Jan 06, 2019 at 12:14:33AM +, Santiago Vila wrote: > Package: src:libgit-raw-perl > Version: 0.79-5 > Severity: serious > Tags: ftbfs > Test Summary Report > --- > t/33-worktree.t (Wstat: 512 Tests: 11 Failed: 0) > Non-zero exit status: 2 > Parse errors:

Bug#919001: emacs-gtk: fails to upgrade to 1.26.1+1-3

Pavel Kreuzt writes: > Package: emacs-gtk > Version: 1:25.2+1-11 > Severity: important > > Dear Maintainer, > > when trying to upgrade emacs to 1.26.1+1-3, some installation script fails > with following error: I think it's very likely that this isn't a bug in emacs, but rather one of the

Bug#919000: spyder: 1

On 2019-01-12 10:08, Adrian Bunk wrote: https://www.debian.org/Bugs/Developer#severities "serious" is the severity that is commonly used for missing dependencies. "Grave" could also be justified, "makes the package mostly unusable". Drew

Processed: Re: ruby-factory-girl-rails: installs files with generic names in /usr/bin

Processing control commands: > clone -1 -2 Bug #910930 [ruby-factory-girl-rails] ruby-factory-girl-rails: installs files with generic names in /usr/bin Bug 910930 cloned as bug 919104 > reassign -2 ruby-factory-bot-rails 4.11.1-1 Bug #919104 [ruby-factory-girl-rails] ruby-factory-girl-rails:

Bug#918435: marked as done (libgit-raw-perl: FTBFS (failing tests))

Your message dated Sat, 12 Jan 2019 18:24:54 + with message-id and subject line Bug#918435: fixed in libgit-raw-perl 0.79-6 has caused the Debian Bug report #918435, regarding libgit-raw-perl: FTBFS (failing tests) to be marked as done. This means that you claim that the problem has been

Bug#910930: ruby-factory-girl-rails: installs files with generic names in /usr/bin

Followup-For: Bug #910930 Control: clone -1 -2 Control: reassign -2 ruby-factory-bot-rails 4.11.1-1 Control: retitle -2 ruby-factory-bot-rails: installs file with generic name: /usr/bin/setup ... and another one was hit ... Andreas

Bug#918583: marked as done (libc6: version in nocache Breaks is incorrect)

Your message dated Sat, 12 Jan 2019 18:20:59 + with message-id and subject line Bug#918583: fixed in glibc 2.28-5 has caused the Debian Bug report #918583, regarding libc6: version in nocache Breaks is incorrect to be marked as done. This means that you claim that the problem has been dealt

Bug#867140: marked as done (cqrlog: Please migrate to openssl1.1 in Buster)

Your message dated Sat, 12 Jan 2019 18:19:41 + with message-id and subject line Bug#867140: fixed in cqrlog 2.3.0-1 has caused the Debian Bug report #867140, regarding cqrlog: Please migrate to openssl1.1 in Buster to be marked as done. This means that you claim that the problem has been

Bug#919103: libreoffice-kde5: failure to upgrade from stretch: soffice.odg also in libreoffice-kde

Package: libreoffice-kde5 Version: 1:6.1.4-3 Severity: serious Justification: failure to install/upgrade Hi, Testing the upgrade path from stretch to buster for various desktop tasks, I've noticed the following issue: Unpacking libreoffice-kde5 (1:6.1.4-3+b1) ... dpkg: error processing

Processed: Bug #918435 in libgit-raw-perl marked as pending

Processing control commands: > tag -1 pending Bug #918435 [src:libgit-raw-perl] libgit-raw-perl: FTBFS (failing tests) Added tag(s) pending. -- 918435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#918435: Bug #918435 in libgit-raw-perl marked as pending

Control: tag -1 pending Hello, Bug #918435 in libgit-raw-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:

Bug#916567: marked as done (golang-github-juju-testing-dev: depends on the removed golang-github-juju-utils-dev)

Your message dated Sat, 12 Jan 2019 18:10:10 + with message-id and subject line Bug#916567: fixed in golang-github-juju-utils 0.0~git20171220.f38c0b0-5 has caused the Debian Bug report #916567, regarding golang-github-juju-testing-dev: depends on the removed golang-github-juju-utils-dev to

Bug#899943: marked as done (thin-provisioning-tools: Invalid maintainer address pkg-lvm-maintain...@lists.alioth.debian.org)

Your message dated Sat, 12 Jan 2019 18:07:54 + with message-id and subject line Bug#899943: fixed in thin-provisioning-tools 0.7.6-1 has caused the Debian Bug report #899943, regarding thin-provisioning-tools: Invalid maintainer address pkg-lvm-maintain...@lists.alioth.debian.org to be

Bug#915630: marked as done (simbody: tests fail on several architectures)

Your message dated Sat, 12 Jan 2019 18:07:12 + with message-id and subject line Bug#915630: fixed in simbody 3.6.1+dfsg-5 has caused the Debian Bug report #915630, regarding simbody: tests fail on several architectures to be marked as done. This means that you claim that the problem has been

Bug#918671: marked as done (python-shade: Incomplete debian/copyright?)

Your message dated Sat, 12 Jan 2019 18:03:49 + with message-id and subject line Bug#918671: fixed in python-shade 1.30.0-2 has caused the Debian Bug report #918671, regarding python-shade: Incomplete debian/copyright? to be marked as done. This means that you claim that the problem has been

Processed: Claiming an issue

Processing commands for cont...@bugs.debian.org: > owner 918751 ! Bug #918751 [src:python-shade] python-shade: FTBFS in sid Owner recorded as Stewart Ferguson . > owner 918761 ! Bug #918761 [abcde] abcde: glyrc and recode required Owner recorded as Stewart Ferguson . > End of message, stopping

Bug#917251: marked as done (eas4tbsync: Incomplete debian/copyright?)

Your message dated Sat, 12 Jan 2019 17:52:15 + with message-id and subject line Bug#917251: fixed in eas4tbsync 0.7.20-2 has caused the Debian Bug report #917251, regarding eas4tbsync: Incomplete debian/copyright? to be marked as done. This means that you claim that the problem has been

Bug#904592: predict-gsat: No executable is included

On Sat, 12 Jan 2019 16:02:02 +0100 Christoph Berg wrote: > Maitland, can we remove predict? > > Christoph Yes... Certainly predict-gsat is obsolete and unmaintained - and gpredict is the logical successor. But... There might be curses interface fans who would mourn its removal, but the

Bug#918447: working on these Pelican bugs

user debian-rele...@lists.debian.org usertags -1 + bsp-2019-01-nl-venlo thank you One is about a new release, the other python3. And 918447 is a FTBFS Context https://wiki.debian.org/BSP/2019/01/nl/Venlo Groeten Geert Stappers -- Leven en laten leven signature.asc Description: PGP

Processed: Tagging bug 827832

Processing commands for cont...@bugs.debian.org: > user debian-rele...@lists.debian.org Setting user to debian-rele...@lists.debian.org (was s...@ferg.aero). > usertags 827832 + bsp-2019-01-nl-venlo Usertags were: bsp-2019-01-nl-venlo. Usertags are now: bsp-2019-01-nl-venlo. > owner 827832 ! Bug

Processed: Claiming bug 827832

Processing commands for cont...@bugs.debian.org: > owner 827832 ! Bug #827832 [src:python-pytc] python-pytc: FTBFS: /bin/sh: 3: pythonpython2.7-dbg: not found Owner recorded as Stewart Ferguson . > End of message, stopping processing here. Please contact me if you need assistance. -- 827832:

Bug#917249: marked as done (dav4tbsync: Incomplete debian/copyright?)

Your message dated Sat, 12 Jan 2019 16:19:28 + with message-id and subject line Bug#917249: fixed in dav4tbsync 0.10-2 has caused the Debian Bug report #917249, regarding dav4tbsync: Incomplete debian/copyright? to be marked as done. This means that you claim that the problem has been dealt

Bug#873016: [Pkg-javascript-devel] Bug#873016: node-lodash-packages: not preferred form for source: Should be built from node-lodash

Hi, On Wed, Aug 23, 2017 at 11:41:28PM +0530, Pirate Praveen wrote: > On ബുധന്‍ 23 ആഗസ്റ്റ് 2017 11:33 വൈകു, Jonas Smedegaard wrote: > > Package: node-lodash-packages > > Severity: serious > > Justification: Policy 2.1 > > I do not think the root issue is serious, but only important. > > > The

  1   2   3   >