Bug#898593: xpn: Intent to remove from Debian

Please go ahead. Thank you, David Il Lun 14 Mag 2018, 02:39 Jeremy Bicha ha scritto: > Source: xpn > Version: 1.2.6-5.1 > Severity: serious > User: pkg-gnome-maintain...@lists.alioth.debian.org > Usertags: oldlibs pygtk > Tags: sid buster > > xpn depends on the unmaintained

Bug#886065: Bug#732011: O: gyrus -- GNOME tool for Cyrus-IMAP servers administration

hi Jeremy,, Yes I am converting it to Gsettings. Gtk3 not yet on my prio-list. Greetings, Willem On Sun, 2018-05-13 at 21:18 -0400, Jeremy Bicha wrote: > Willem, gyrus was removed from Debian Testing 3 months ago because it > depends on gconf. > > It has also been abandoned upstream. > > Do

Bug#886065: Bug#732011: O: gyrus -- GNOME tool for Cyrus-IMAP servers administration

hi Jeremy,, Yes I am converting it to Gsettings. Gtk3 not yet on my prio-list. Greetings, Willem On Sun, 2018-05-13 at 21:18 -0400, Jeremy Bicha wrote: > > Willem, gyrus was removed from Debian Testing 3 months ago because > > it > > depends on gconf. > > > > It has also been abandoned

Bug#886382: fixed in amd64-microcode 3.20171205.1

On Sun, 13 May 2018, Andreas Ziegler wrote: > this bug's severity is marked "grave" but the changes haven't been > backported to stable or oldstable yet. > > Is there a valid reason? Sure. Nobody ever tell us it worked, so we don't fasttrack, which means it will wait at *least* a couple months.

Bug#898598: jack-mixer: Depends on gconf

Source: jack-mixer Version: 10-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs gconf Tags: sid buster Your package depends or build-depends on gconf, but gconf will be removed from Debian soon. gconf's last release was about 5 years ago. It has been

Bug#886065: O: gyrus -- GNOME tool for Cyrus-IMAP servers administration

Willem, gyrus was removed from Debian Testing 3 months ago because it depends on gconf. It has also been abandoned upstream. Do you intend to at least port it away from gconf? It would be helpful if you ported it to gtk3 also. Otherwise, I think it would be better if we remove gyrus from

Bug#898593: xpn: Intent to remove from Debian

Source: xpn Version: 1.2.6-5.1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster xpn depends on the unmaintained pygtk which the Debian GNOME team is trying to remove from Debian. It looks like xpn itself is unmaintained. Therefore, I

Processed: Re: Bug#869191: pristine-tar: pristine-xz failed to reproduce build of ../util-linux_2.30.1.orig.tar.xz

Processing control commands: > severity -1 important Bug #869191 [pristine-tar] pristine-tar: pristine-xz failed to reproduce build of ../util-linux_2.30.1.orig.tar.xz Severity set to 'important' from 'grave' -- 869191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869191 Debian Bug

Bug#869191: pristine-tar: pristine-xz failed to reproduce build of ../util-linux_2.30.1.orig.tar.xz

Control: severity -1 important On Sun, May 13, 2018 at 03:00:44PM +0200, Alf Gaida wrote: > Control: severity -1 grave > > can confirm that the patch work fine. sure, thanks for testing. I have applied the patch to the git repository, and it will be available in the next upload. However this

Bug#898591: lptools: Intent to remove from Debian

Source: lptools Version: 0.2.0-2 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster X-Debbugs-CC: x...@debian.org, jel...@debian.org lptools depends on the unmaintained pygtk which the Debian GNOME team is trying to remove from Debian.

Bug#869191: pristine-tar: pristine-xz failed to reproduce build of ../util-linux_2.30.1.orig.tar.xz

Only a remark - i'm not interested in severeties of bugs. But xz is a common compression format - and one of the favoured in debian iirc. So if a tool break the workflow for a common compression format i would see this as serious or grave, what ever make it unfit for release and is a RC bug. ymmv.

Bug#898589: yorick-yao: Intent to remove from Debian

Source: yorick-yao Version: 5.4.0-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster yorick-yao depends on the unmaintained pygtk which the Debian GNOME team is trying to remove from Debian. It looks like yorick-yao itself is

Bug#896071: debootstrap fails to retrive Release file over https

Hideki, On 4/24/18 3:29 PM, Raphael Hertzog wrote: > On Mon, 23 Apr 2018, Hideki Yamane wrote: >> On Sun, 22 Apr 2018 09:40:54 +1000 >> David Margerison wrote: "$@" is extracted as '' and wget tries to fetch it and fails, then returns 1. >>> >>> Regarding

Bug#897975: [gdm3] Same here, more info

Package: gdm3 Version: 3.28.1-1 I have this same problem since about ten days. This weekend I decided to do a clean install and found that I was unable: I deleted the system partition, booted an USB with debian netinst version, installed stable with just gnome shell, and everything worked

Bug#897536: mustache.js: FTBFS: make[1]: rake: Command not found

Le vendredi 11 mai 2018 à 12:12:44+0200, Jonas Meurer a écrit : > Control: tag -1 +moreinfo > > Hello, > > I just tried to reproduce the FTBFS and failed. rake is defined as > build-dependency and correctly pulled in according to linked the build logs. > > My best guess is that rake 12.3.1-2

Processed: found 846938 in 6.10.1-1

Processing commands for cont...@bugs.debian.org: > # Since upstream fixed it in > https://roy.marples.name/git/dhcpcd.git/commit/?id=93f3066bb0bc0974eab1943543205312a6b512ad > two days after the upstream release of 6.10.1 and debian has no other > patches than spelling fixes in 6.10.1-1, it

Processed: tagging 846938

Processing commands for cont...@bugs.debian.org: > # Fixed in > https://roy.marples.name/git/dhcpcd.git/commit/?id=93f3066bb0bc0974eab1943543205312a6b512ad > which has been committed two days after the upstream release of 6.10.1 which > is the current upstream version in Debian (while the

Bug#898581: Remove pike7.8 from Debian?

Source: pike7.8 Version: 7.8.866-8.1 Severity: serious Tags: buster sid Debian 9 "Stretch" has both pike7.8 and pike8.0. In general, we try not to have duplicate packages in Debian. Is there any reason we shouldn't remove pike7.8 from Debian unstable now? Thanks, Jeremy Bicha

Bug#887856: Intel helding spectre microcode updates back

Hi all, I found that (all) the Intel Microcode Update packages from 2018 don't contain the fixed version for my CPU Celeron N3450 (and others with same CPUID 506c9: N3350 N4200 J3455 J4205). It doesn't benefit from new commands IBRS/IBPB which indeed is reported so by spectre-meltdown-checker.sh

Processed: bug 898578 is forwarded to https://github.com/RexOps/Rex/issues/1197

Processing commands for cont...@bugs.debian.org: > forwarded 898578 https://github.com/RexOps/Rex/issues/1197 Bug #898578 [src:rex] libyaml-perl/1.25-1 breaks rex/1.6.0-1 test suite (FTBFS and autopkgtest failure) Set Bug forwarded-to-address to 'https://github.com/RexOps/Rex/issues/1197'. >

Processed: affects 898561

Processing commands for cont...@bugs.debian.org: > affects 898561 + src:libyaml-perl Bug #898561 [src:libmarc-transform-perl] libmarc-transform-perl: FTBFS with libyaml-perl >= 1.25-1 (test failures) Added indication that 898561 affects src:libyaml-perl > thanks Stopping processing here. Please

Processed: libyaml-perl/1.25-1 breaks rex/1.6.0-1 test suite (FTBFS and autopkgtest failure)

Processing control commands: > affects -1 src:libyaml-perl Bug #898578 [src:rex] libyaml-perl/1.25-1 breaks rex/1.6.0-1 test suite (FTBFS and autopkgtest failure) Added indication that 898578 affects src:libyaml-perl -- 898578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898578 Debian

Bug#898578: libyaml-perl/1.25-1 breaks rex/1.6.0-1 test suite (FTBFS and autopkgtest failure)

Gevers <elb...@debian.org> To: libyaml-p...@packages.debian.org, r...@packages.debian.org Subject: libyaml-perl/1.25-1 breaks rex/1.6.0-1 autopkgtest in testing Date: Sun, 13 May 2018 19:29:44 +0100 Dear maintainers, [This e-mail is automatically sent. V3.1 (20180513)] tl;dr: libyaml-perl/1.25-

Bug#872894: marked as done (node-policyfile: autopkgtests fail with nodejs 6)

Your message dated Sun, 13 May 2018 20:57:59 + with message-id and subject line Bug#872894: fixed in node-policyfile 0.0.6+ds-1 has caused the Debian Bug report #872894, regarding node-policyfile: autopkgtests fail with nodejs 6 to be marked as done. This

Bug#898076: marked as done (wget: CVE-2018-0494: cookie injection)

Your message dated Sun, 13 May 2018 20:53:18 + with message-id and subject line Bug#898076: fixed in wget 1.16-1+deb8u5 has caused the Debian Bug report #898076, regarding wget: CVE-2018-0494: cookie injection to be marked as done. This means that you

Bug#896869: marked as done (bijiben FTBFS with meson 0.46.0)

Your message dated Sun, 13 May 2018 20:56:04 + with message-id and subject line Bug#896869: fixed in bijiben 3.28.2-1 has caused the Debian Bug report #896869, regarding bijiben FTBFS with meson 0.46.0 to be marked as done. This means that you claim that

Bug#893668: marked as done (adminer: CVE-2018-7667)

Your message dated Sun, 13 May 2018 20:51:51 + with message-id and subject line Bug#893668: fixed in adminer 3.3.3-1+deb8u1 has caused the Debian Bug report #893668, regarding adminer: CVE-2018-7667 to be marked as done. This means that you claim that the

Bug#898076: marked as done (wget: CVE-2018-0494: cookie injection)

Your message dated Sun, 13 May 2018 20:51:09 + with message-id and subject line Bug#898076: fixed in wget 1.18-5+deb9u2 has caused the Debian Bug report #898076, regarding wget: CVE-2018-0494: cookie injection to be marked as done. This means that you

Bug#898577: pytables: FTBFS - 56 tests fail with 'TypeError: a float is required'

Source: pytables Version: 3.4.3-1 Severity: serious Justification: FTBFS -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, pytables FTBFS on unstable during the tests step. 56 tests fail with errors like: == ERROR:

Bug#895246: gconf: Intent to Adopt

On Sun, May 13, 2018 at 1:54 PM, Adrian Bunk wrote: > On Mon, Apr 30, 2018 at 06:47:41PM -0400, Jeremy Bicha wrote: >> Why? Basically there are only two things left in Buster that depend on >> gconf: eclipse and pulseaudio. > > Plus ~ 50 more in unstable. > >> Please be more

Processed: fixed 878999 in 3.5.2-2

Processing commands for cont...@bugs.debian.org: > fixed 878999 3.5.2-2 Bug #878999 {Done: Andres Salomon } [src:protobuf] protobuf FTBFS on armhf/i386: testMergeFrom (google.protobuf.internal.message_test.Proto3Test) ... Segmentation fault Marked as fixed in versions

Processed: forcibly merging 893138 898570

Processing commands for cont...@bugs.debian.org: > forcemerge 893138 898570 Bug #893138 [jabref] jabref: fails to build and start with openjdk-9 Bug #893138 [jabref] jabref: fails to build and start with openjdk-9 Marked as found in versions jabref/3.8.1+ds-3. Added tag(s) buster and sid. Bug

Bug#898524: marked as done (FTBFS: unsatisfiable dependencies)

Your message dated Sun, 13 May 2018 18:21:02 + with message-id and subject line Bug#898524: fixed in stylish-haskell 0.9.2.0-1 has caused the Debian Bug report #898524, regarding FTBFS: unsatisfiable dependencies to be marked as done. This means that you

Bug#895246: gconf: Intent to Adopt

On Mon, Apr 30, 2018 at 06:47:41PM -0400, Jeremy Bicha wrote: > On Sun, Apr 8, 2018 at 3:19 PM, Adrian Bunk wrote: > > Sorry for not replying more promptly. > > > I hereby declare my intent to adopt gconf. > > Why? Basically there are only two things left in Buster that depend

Bug#898572: wrong term in debian/copyright

Package: keepass2-plugin-keepasshttp Version: XXX Severity: serious thanks As the license of this software is just GPL-3, please remove the term "or (at your option) any later version." from your debian/copyright. Thanks! Thorsten

Bug#898374: marked as done (gcc-8-cross: file conflicts with {gcc,g++,...}-8 on /usr/bin/-*-8)

Your message dated Sun, 13 May 2018 17:50:03 + with message-id and subject line Bug#898374: fixed in gcc-8-cross 14 has caused the Debian Bug report #898374, regarding gcc-8-cross: file conflicts with {gcc,g++,...}-8 on /usr/bin/-*-8 to be marked as done.

Bug#898374: marked as done (gcc-8-cross: file conflicts with {gcc,g++,...}-8 on /usr/bin/-*-8)

Your message dated Sun, 13 May 2018 17:50:12 + with message-id and subject line Bug#898374: fixed in gcc-8-cross 15 has caused the Debian Bug report #898374, regarding gcc-8-cross: file conflicts with {gcc,g++,...}-8 on /usr/bin/-*-8 to be marked as done.

Processed: affects 898501

Processing commands for cont...@bugs.debian.org: > affects 898501 + debci Bug #898501 [fonts-font-awesome] Broken symlinks Added indication that 898501 affects debci > thanks Stopping processing here. Please contact me if you need assistance. -- 898501:

Bug#867256: marked as done (monitoring-plugins-basic: fails to install: Error: The new file apt.cfg does not exist!)

Your message dated Sun, 13 May 2018 17:37:46 + with message-id and subject line Bug#867256: fixed in monitoring-plugins 2.2-4 has caused the Debian Bug report #867256, regarding monitoring-plugins-basic: fails to install: Error: The new file apt.cfg does

Bug#898501: Broken symlinks

On Sat, 12 May 2018 12:39:50 -0700 Sean Whitton wrote: > Package: fonts-font-awesome > Version: 5.0.10-1 > Severity: grave > Control: affects -1 cider > > Dear maintainer, > > The latest upload introduces some new broken symlinks: > > fonts-font-awesome:

Bug#898374: marked as done (gcc-8-cross: file conflicts with {gcc,g++,...}-8 on /usr/bin/-*-8)

Your message dated Sun, 13 May 2018 17:19:39 + with message-id and subject line Bug#898374: fixed in gcc-8-cross 13 has caused the Debian Bug report #898374, regarding gcc-8-cross: file conflicts with {gcc,g++,...}-8 on /usr/bin/-*-8 to be marked as done.

Processed: affects 898501

Processing commands for cont...@bugs.debian.org: > affects 898501 src:goaccess Bug #898501 [fonts-font-awesome] Broken symlinks Added indication that 898501 affects src:goaccess > thanks Stopping processing here. Please contact me if you need assistance. -- 898501:

Processed: block 894159 with 888908

Processing commands for cont...@bugs.debian.org: > block 894159 with 888908 Bug #894159 [release.debian.org] transition: icu 894159 was blocked by: 898369 898465 894159 was not blocking any bugs. Added blocking bug(s) of 894159: 888908 > thanks Stopping processing here. Please contact me if you

Processed: block 891515 with 880003

Processing commands for cont...@bugs.debian.org: > block 891515 with 880003 Bug #891515 [node-colormin] node-colormin : Depends: node-has (>= 1.0.1) but it is not installable 891515 was not blocked by any bugs. 891515 was not blocking any bugs. Added blocking bug(s) of 891515: 880003 > thanks

Processed: Re: Bug#898556: [kwin-wayland] Closing windows in Plasma Wayland crashes the entire session

Processing control commands: > severity -1 important Bug #898556 [kwin-wayland] [kwin-wayland] Closing windows in Plasma Wayland crashes the entire session Severity set to 'important' from 'grave' -- 898556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898556 Debian Bug Tracking System

Bug#898556: [kwin-wayland] Closing windows in Plasma Wayland crashes the entire session

Control: severity -1 important ¡Hola Alexander! El 2018-05-13 a las 17:09 +0300, Alexander Kernozhitsky escribió: Package: kwin-wayland Version: 4:5.12.5-1 Severity: grave I tried Plasma session on Wayland today. Closing a window in it crashes the session and returns me back to SDDM. I'm

Bug#897529: installation-guide is marked for autoremoval from testing

Hi, Holger Wansing (2018-05-10): > Debian testing autoremoval watch wrote: > > installation-guide 20170614 is marked for autoremoval from testing on > > 2018-05-31 > > > > It is affected by these RC bugs: > > 897529: installation-guide:

Bug#897568: 4.16 breakage

ZoL only breaks on kernel updates when the kernel changes the API/structures that it uses. ZFS 0.7.9 is released and fully supports all current kernels, and has some good bug fixes and feature upgrades.

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

Processing commands for cont...@bugs.debian.org: > forwarded 898561 https://rt.cpan.org/Ticket/Display.html?id=125307 Bug #898561 [src:libmarc-transform-perl] libmarc-transform-perl: FTBFS with libyaml-perl >= 1.25-1 (test failures) Set Bug forwarded-to-address to

Bug#894290: gradle should raise the source/target level to the minimum supported by the default JDK

Control: reassign -1 gradle-debian-helper 1.6 I would say this is not the fault of Gradle itself, but it the tricks can be provided by `gradle-debian-helper`. We shouldn't modify the behavior of the build tools too much. Let's keep the severity as is for now, as FTBFS is quite serious indeed.

Processed: Re: gradle should raise the source/target level to the minimum supported by the default JDK

Processing control commands: > reassign -1 gradle-debian-helper 1.6 Bug #894290 [gradle] gradle should raise the source/target level to the minimum supported by the default JDK Bug reassigned from package 'gradle' to 'gradle-debian-helper'. No longer marked as found in versions gradle/3.4.1-3.

Bug#898561: libmarc-transform-perl: FTBFS with libyaml-perl >= 1.25-1 (test failures)

Source: libmarc-transform-perl Version: 0.003006-2 Severity: serious Tags: upstream buster sid Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 libmarc-transform-perl's testsuite fails, both during build and autopkgtest, with libyaml-perl >= 1.25-1:

Bug#898542: qt4-x11: FTBFS with libicu60

El dom., 13 de may. de 2018 10:51, John Paul Adrian Glaubitz < glaub...@physik.fu-berlin.de> escribió: > Control: tags 898542 +patch > > On 05/13/2018 03:35 PM, John Paul Adrian Glaubitz wrote: > > openSUSE seems to have a patch [1] we can use that is also already used > > in Fedora. I'll test

Processed: Re: h5py: FTBFS with HDF5 1.10.2

Processing control commands: > severity -1 serious Bug #898526 [src:h5py] h5py: FTBFS with HDF5 1.10.2 Severity set to 'serious' from 'normal' > retitle -1 h5py: FTBFS - FAIL: test_out_of_order_offsets Bug #898526 [src:h5py] h5py: FTBFS with HDF5 1.10.2 Changed Bug title to 'h5py: FTBFS - FAIL:

Processed: ICU transition: ICU version is part of the boost ABI

Processing control commands: > reassign 898465 src:icu 60.1-1 Bug #898465 [src:icu] ICU must not migrate to testing before the boost ABI breakage is resolved Ignoring request to reassign bug #898465 to the same package Bug #898465 [src:icu] ICU must not migrate to testing before the boost ABI

Processed: ICU transition: ICU version is part of the boost ABI

Processing control commands: > reassign 898465 src:icu 60.1-1 Bug #898465 [viking] symbol lookup error: /usr/lib/libmapnik.so.3.0: undefined symbol Bug reassigned from package 'viking' to 'src:icu'. No longer marked as found in versions viking/1.6.2-3. Ignoring request to alter fixed versions of

Bug#898556: [kwin-wayland] Closing windows in Plasma Wayland crashes the entire session

Package: kwin-wayland Version: 4:5.12.5-1 Severity: grave I tried Plasma session on Wayland today. Closing a window in it crashes the session and returns me back to SDDM. --- System information. --- Architecture: Kernel: Linux 4.16.0-1-amd64 Debian Release: buster/sid 990 testing

Bug#898369: ICU transition: ICU version is part of the boost ABI

Control: reassign 898465 src:icu 60.1-1 Control: retitle 898369 boost: ICU version used is part of the ABI Control: retitle 898465 ICU must not migrate to testing before the boost ABI breakage is resolved Control: affects 898369 libmapnik3.0 viking Control: block 898465 by 898369 Control: block

Processed: ICU transition: ICU version is part of the boost ABI

Processing control commands: > reassign 898465 src:icu 60.1-1 Bug #898465 [src:icu] ICU must not migrate to testing before the boost ABI breakage is resolved Ignoring request to reassign bug #898465 to the same package Bug #898465 [src:icu] ICU must not migrate to testing before the boost ABI

Bug#886382: fixed in amd64-microcode 3.20171205.1

Hi, this bug's severity is marked "grave" but the changes haven't been backported to stable or oldstable yet. Is there a valid reason? Regards Andreas On Wed, 10 Jan 2018 10:04:16 + Henrique de Moraes Holschuh wrote: > Source: amd64-microcode > Source-Version:

Processed: Re: Bug#898542: qt4-x11: FTBFS with libicu60

Processing control commands: > tags 898542 +patch Bug #898542 [src:qt4-x11] qt4-x11: FTBFS with libicu60 Added tag(s) patch. -- 894159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894159 898542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898542 Debian Bug Tracking System Contact

Bug#898542: qt4-x11: FTBFS with libicu60

Control: tags 898542 +patch On 05/13/2018 03:35 PM, John Paul Adrian Glaubitz wrote: openSUSE seems to have a patch [1] we can use that is also already used in Fedora. I'll test it. Attaching openSUSE's patch which fixes the problem for me. Adrian -- .''`. John Paul Adrian Glaubitz : :' :

Processed: Re: Bug#898542: qt4-x11: FTBFS with libicu60

Processing control commands: > tags 898542 +patch Bug #898542 [src:qt4-x11] qt4-x11: FTBFS with libicu60 Ignoring request to alter tags of bug #898542 to the same tags previously set -- 898542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898542 Debian Bug Tracking System Contact

Bug#898542: qt4-x11: FTBFS with libicu60

On 05/13/2018 03:08 PM, Lisandro Damián Nicanor Pérez Meyer wrote: > I have not checked if other distros ship a patch for this (or maybe > they switched to the embedded copy, if applicable). I will at some > point but I can't promise being fast here. openSUSE seems to have a patch [1] we can use

Bug#898542: qt4-x11: FTBFS with libicu60

Hi John! This seems to be related to the icu transition, so CCing the bug. On 13 May 2018 at 07:02, John Paul Adrian Glaubitz wrote: > Source: qt4-x11 > Version: 4:4.8.7+dfsg-16 > Severity: serious > Justification: fails to build from source > > Hi! > > qt4-x11

Processed: Re: Bug#869191: pristine-tar: pristine-xz failed to reproduce build of ../util-linux_2.30.1.orig.tar.xz

Processing control commands: > severity -1 grave Bug #869191 [pristine-tar] pristine-tar: pristine-xz failed to reproduce build of ../util-linux_2.30.1.orig.tar.xz Severity set to 'grave' from 'important' -- 869191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869191 Debian Bug Tracking

Bug#897127: psensor FTBFS on i386/armhf: FAIL: test-cppcheck.sh

See bug 898327. Joachim

Processed: found 898369 in 1.62.0+dfsg-5

Processing commands for cont...@bugs.debian.org: > found 898369 1.62.0+dfsg-5 Bug #898369 [src:boost1.62] breaks ncmpcpp Marked as found in versions boost1.62/1.62.0+dfsg-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 898369:

Bug#855251: easytag corrupt ogg files

Hi, On 13/05/18 11:47, Bruno Kleinert wrote: > Hi James, > > unfortunately it doesn't seem fixed to me. I tried the following with > 2.4.3-4: >1. youtube-dl -x -f 'bestaudio' 'https://www.youtube.com/watch?v=ui_odI > vVIBE' >2. Use soundconverter to convert it to Ogg Vorbis >3.

Bug#894642: marked as done (gst-plugins-espeak FTBFS with GStreamer 1.14)

Your message dated Sun, 13 May 2018 11:34:49 + with message-id and subject line Bug#894642: fixed in gst-plugins-espeak 0.4.0-3.1 has caused the Debian Bug report #894642, regarding gst-plugins-espeak FTBFS with GStreamer 1.14 to be marked as done. This

Bug#898549: synergy FTBFS: No SOURCES given to target: gmock

Source: synergy Version: 1.8.8-stable+dfsg.1-1.1 Severity: serious https://buildd.debian.org/status/package.php?p=synergy=sid ... CMake Error at src/test/CMakeLists.txt:22 (add_library): Cannot find source file: /usr/src/gmock/src/gmock-all.cc Tried extensions .c .C .c++ .cc .cpp .cxx

Bug#894642: [Pkg-sugar-devel] Bug#894642: gst-plugins-espeak: diff for NMU version 0.4.0-3.1

On Mon, Apr 30, 2018 at 07:07:26AM +1000, James Cameron wrote: > Will you be sending this upstream? > > https://github.com/sugarlabs/gst-plugins-espeak Not sure about that, they might want to implement an improved regex instead of my simple approach of removing the regex. cu Adrian --

Bug#897519: marked as done (bcron: FTBFS: tests failed)

Your message dated Sun, 13 May 2018 11:19:28 + with message-id and subject line Bug#897519: fixed in bcron 0.11-1.2 has caused the Debian Bug report #897519, regarding bcron: FTBFS: tests failed to be marked as done. This means that you claim that the

Bug#855251: easytag corrupt ogg files

Am Sonntag, den 25.03.2018, 12:55 +0100 schrieb James Cowgill: > Hi, > > On 03/01/18 16:50, James Cowgill wrote: > > On 16/02/17 01:02, Samuele Battarra wrote: > > > Package: easytag > > > Version: 2.4.3-1 > > > Severity: normal > > > > > > Dear Maintainer, > > > I have a ogg file encoded from a

Bug#890307: tortoisehg: needs update for mercurial 4.5

Control: found -1 4.5.3-1 Control: retitle -1 tortoisehg: needs update for mercurial 4.6 On Tue, Feb 13, 2018 at 10:54:42 +0100, Julien Cristau wrote: > Package: tortoisehg > Version: 4.4.1-1 > Severity: serious > X-Debbugs-Cc: mithra...@mithrandi.net > > tortoisehg is uninstallable in sid

Processed: Re: Bug#890307: tortoisehg: needs update for mercurial 4.5

Processing control commands: > found -1 4.5.3-1 Bug #890307 [tortoisehg] tortoisehg: needs update for mercurial 4.5 Marked as found in versions tortoisehg/4.5.3-1. > retitle -1 tortoisehg: needs update for mercurial 4.6 Bug #890307 [tortoisehg] tortoisehg: needs update for mercurial 4.5 Changed

Processed: affects 898535

Processing commands for cont...@bugs.debian.org: > affects 898535 libtinyxml2-6 Bug #898535 [src:tinyxml2] Incompatible ABI change without SONAME bump Added indication that 898535 affects libtinyxml2-6 > thanks Stopping processing here. Please contact me if you need assistance. -- 898535:

Bug#898547: papi-examples is not installable

Package: papi-examples Version: 5.6.0+git22-g4c23d555-1 Severity: serious papi-examples : Depends: libpapi-dev (< 5.6.0+git22-g4c23d555.~) but 5.6.0+git22-g4c23d555-1 is to be installed

Bug#869994: work around solution

Your suggested workaround made me once again have a glimpse on the developer's website and there I found at the top of the FAQ that he meanwhile has a respond to this issue, namely: perl 5.26 @INC error If you get something like this instead of the login screen Can't locate bin/mozilla/login.pl

Processed: Re: Bug#898502: ucommon: Please update symbols for riscv64 and ia64

Processing control commands: > severity -1 normal Bug #898502 [src:ucommon] ucommon: Please update symbols for riscv64 and ia64 Severity set to 'normal' from 'serious' > tags -1 patch Bug #898502 [src:ucommon] ucommon: Please update symbols for riscv64 and ia64 Added tag(s) patch. -- 898502:

Bug#898502: ucommon: Please update symbols for riscv64 and ia64

Control: severity -1 normal Control: tags -1 patch On Sat, May 12, 2018 at 10:00:13PM +0200, Manuel A. Fernandez Montecelo wrote: > Source: ucommon > Version: 7.0.0-12 > Severity: serious > User: debian-ri...@lists.debian.org > Usertags: riscv64 >... > So, conjecturing a bit, to me it seems

Bug#898542: qt4-x11: FTBFS with libicu60

Source: qt4-x11 Version: 4:4.8.7+dfsg-16 Severity: serious Justification: fails to build from source Hi! qt4-x11 fails to build from source due to incompatible changes in libicu60: g++ -c -include .pch/release-shared/QtCore -g -O2 -fdebug-prefix-map=/<>/qt4-x11-4.8.7+dfsg=.

Processed: bug 898535 is forwarded to https://github.com/leethomason/tinyxml2/issues/674

Processing commands for cont...@bugs.debian.org: > forwarded 898535 https://github.com/leethomason/tinyxml2/issues/674 Bug #898535 [src:tinyxml2] Incompatible ABI change without SONAME bump Set Bug forwarded-to-address to 'https://github.com/leethomason/tinyxml2/issues/674'. > thanks Stopping

Bug#898518: marked as done (why silently dropped the ppc64el and s390x builds)

Your message dated Sun, 13 May 2018 09:24:35 + with message-id and subject line Bug#898518: fixed in why 2.40-3 has caused the Debian Bug report #898518, regarding why silently dropped the ppc64el and s390x builds to be marked as done. This means that you

Bug#898327: marked as done (cppcheck: *** stack smashing detected ***: terminated)

Your message dated Sun, 13 May 2018 09:21:31 + with message-id and subject line Bug#898327: fixed in cppcheck 1.83-2 has caused the Debian Bug report #898327, regarding cppcheck: *** stack smashing detected ***: terminated to be marked as done. This

Bug#898327: cppcheck: *** stack smashing detected ***: terminated

Hi Jakub, I confirm that the crash goes away if libtinyxml2-6 is downgraded to 6.0.0+dfsg-1. Thanks for finding the real cause! I've filed bug 898535 against tinyxml2. I've added a versioned Build-Depends to cppcheck as workaround. Joachim

Bug#896860: marked as done (lammps FTBFS with TeX Live 2018)

Your message dated Sun, 13 May 2018 08:57:30 + with message-id and subject line Bug#896860: fixed in lammps 0~20180510.gitaa1d815fe-2 has caused the Debian Bug report #896860, regarding lammps FTBFS with TeX Live 2018 to be marked as done. This means that

Bug#898535: Incompatible ABI change without SONAME bump

Source: tinyxml2 Version: 6.2.0+dfsg-1 Severity: grave Tags: upstream Hi, the layout of tinyxml::XMLDocument has been changed between version 6.0.0 and 6.2.0 (addition of _parsingDepth member). Unfortunately, the SONAME has not been bumped. This can cause applications built against version 6.0.0

Processed: affects 898501

Processing commands for cont...@bugs.debian.org: > affects 898501 src:cider Bug #898501 [fonts-font-awesome] Broken symlinks Added indication that 898501 affects src:cider > thanks Stopping processing here. Please contact me if you need assistance. -- 898501:

Bug#866489: marked as done (twms: depends on obsolete python-imaging (replace with python3-pil or python-pil))

Your message dated Sun, 13 May 2018 07:35:35 + with message-id and subject line Bug#866489: fixed in twms 0.06y-1 has caused the Debian Bug report #866489, regarding twms: depends on obsolete python-imaging (replace with python3-pil or python-pil) to be

Bug#896921: Salt 2017.7.5 has been released

Hi, could the version be bumped, then? Thanks... Dirk -- Dirk Heinrichs GPG Public Key: D01B367761B0F7CE6E6D81AAD5A2E54246986015 Sichere Internetkommunikation: http://www.retroshare.org Privacy Handbuch: https://www.privacy-handbuch.de signature.asc