Bug#872528: marked as done (golang-github-grpc-ecosystem-grpc-gateway FTBFS: test failure)

Your message dated Sun, 17 Sep 2017 13:49:34 +0800 with message-id and subject line Re: golang-github-grpc-ecosystem-grpc-gateway FTBFS: test failure has caused the Debian Bug report #872528, regarding

Bug#862431: marked as done (m4/python.m4 should list recent python3.x versions)

Your message dated Sun, 17 Sep 2017 04:19:14 + with message-id and subject line Bug#872052: fixed in automake-1.15 1:1.15.1-3 has caused the Debian Bug report #872052, regarding m4/python.m4 should list recent python3.x versions to be marked as done. This

Bug#875995: sump-logicanalyzer: missing B-D: ant

Source: sump-logicanalyzer Version: 0.8-1 Severity: serious Justification: fails to build from source Hi, sump-logicanalyzer cannot be built in experimental any more: fakeroot debian/rules clean dh clean dh: Compatibility levels before 9 are deprecated (level 8 in use) dh_auto_clean

Bug#875993: yamcha: FTBFS with GCC 7

Package: yamcha Version: 0.33-1 Severity: serious Justification: fails to build from source (but built successfully in the past) yamcha cannot be built any longer in experimental: In file included from param.cpp:32:0: param.cpp: In member function 'bool YamCha::Param::open(const char*, const

Processed: notfixed 820416 in 17.0~beta5+dfsg1-4, fixed 820416 in 2:17.0~beta5+dfsg1-4, fixed 502180 in 3.14.1-2 ...

Processing commands for cont...@bugs.debian.org: > # fixing up bug metadata to allow archival > notfixed 820416 17.0~beta5+dfsg1-4 Bug #820416 {Done: Santiago Vila } [src:kodi] kodi: FTBFS in testing (Segmentation fault) The source 'kodi' and version '17.0~beta5+dfsg1-4' do not

Bug#875992: haskell-lens: unsatisfiable B-D: libghc-vector-dev (< 0.12) but 0.12.0.1-1 is to be installed

Source: haskell-lens Version: 4.15.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) haskell-lens connot be built in sid any more, blocking the ongoing ghc transition. Andreas

Bug#875991: fast5: FTBFS: debian/python-fast5-bin/usr/bin/ is not a directory

Source: fast5 Version: 0.6.2-4 Severity: serious Justification: fails to build from source (but built successfully in the past) Greetings. Builds of fast5 covering only its architecture-dependent binary packages (as on the autobuilders, or with dpkg-buildpackage -B) have been failing:

Bug#871116: marked as done (libgoogle-gson-java: FTBFS: ERROR Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:3.0.2:jar (default) on project gson: You ha

Your message dated Sat, 16 Sep 2017 22:20:40 +0200 with message-id <01925417-dc1e-b213-4db3-84d953473...@apache.org> and subject line has caused the Debian Bug report #871116, regarding libgoogle-gson-java: FTBFS: ERROR Failed to execute goal

Bug#874693: Is this still an issue?

I see that gjs 1.50 has been released. Is this bug still applicable?

Bug#875690: Fixed in FreeXL 1.0.4

Hi Salvatore, On 09/13/2017 07:27 PM, Bas Couwenberg wrote: > Should be fixed in the new upstream release: > > https://groups.google.com/forum/m/#!topic/spatialite-users/Wpj62XSzcZY > > I'm not able to work on this until I return from VAC. I've cherry-picked the changes from 1.0.4 and prepared

Bug#849122: Please adjust the BTS version tracking info

On Sat, 9 Sep 2017 19:17:12 +0200 Francesco Poli wrote: > On Sat, 1 Jul 2017 23:32:28 +0200 Francesco Poli wrote: > > > Dear Debian wpasupplicant Maintainers, > > I noticed that these 3 RC bugs (#849122, #849077, #849875) are marked > > as found in wpa/2.6-2, which is now superseded by versions

Bug#853560: marked as done (mp4v2: ftbfs with GCC-7)

Your message dated Sat, 16 Sep 2017 21:50:34 + with message-id and subject line Bug#853560: fixed in mp4v2 2.0.0~dfsg0-6 has caused the Debian Bug report #853560, regarding mp4v2: ftbfs with GCC-7 to be marked as done. This means that you claim that the

Bug#853560: marked as pending

tag 853560 pending thanks Hello, Bug #853560 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://anonscm.debian.org/git/pkg-multimedia/mp4v2.git/commit/?id=c9c4347 --- commit

Processed: Bug#853560 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 853560 pending Bug #853560 [src:mp4v2] mp4v2: ftbfs with GCC-7 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 853560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853560 Debian Bug

Bug#874521: fwupd segfaults at start

Currently, this bug is keeping fwupd 0.9.7 from migrating to testing. Is this crash new with fwupd 0.9 or can you also reproduce it with testing's 0.8.2-2? Also, if you aren't subscribed to the bug, see Mario's response at https://bugs.debian.org/874521 Thanks, Jeremy Bicha

Bug#875982: RM: obsolete with current Perl?

Package: libsub-current-perl Version: 0.03-2 Severity: serious Justification: obsolete with perl >= 5.16.0 libsub-current-perl 0.03 added a note to its POD explaining that from perl 5.16.0, the built-in __SUB__ can be used instead via the pragma use feature 'current_sub';

Bug#868073: bioperl-run: FTBFS: t/Bowtie.t failure

control: forwarded -1 https://github.com/bioperl/bioperl-run/issues/52 control: tags -1 upstream I have forwarded the issue upstream. I think the issue occures since there is no such executable bowtie-align any more. The executables that are shipped with bowtie are named bowtie-align-l or

Processed: Re: Bug#868073: bioperl-run: FTBFS: t/Bowtie.t failure

Processing control commands: > forwarded -1 https://github.com/bioperl/bioperl-run/issues/52 Bug #868073 [bioperl-run] bioperl-run: FTBFS: t/Bowtie.t failure Set Bug forwarded-to-address to 'https://github.com/bioperl/bioperl-run/issues/52'. > tags -1 upstream Bug #868073 [bioperl-run]

Bug#810694: marked as done (west-chamber-dkms: does not clean after module build)

Your message dated Sat, 16 Sep 2017 19:35:00 + with message-id and subject line Bug#810694: fixed in west-chamber 20100405+svn2007.r124-8 has caused the Debian Bug report #810694, regarding west-chamber-dkms: does not clean after module build to be

Bug#875980: kodi-pvr-vuplus: PVR addon not compatible with Kodi from same Debian release

Package: kodi-pvr-vuplus Version: 2.4.4+git20160820-2 Severity: grave Justification: renders package unusable Dear Maintainer, The Vuplus PVR addon can be installed, configured and generally works until next Kodi start. After next Kodi start a message box comes up stating that the Vu+/Enigma

Processed: Re: Bug#875975: kmod FTBFS: subprocess.CalledProcessError: Command '['/usr/bin/pkg-config', '--variable=prefix', 'glib-2.0']' returned non-zero exit status 1

Processing commands for cont...@bugs.debian.org: > reassign 875975 gtk-doc 1.26-1 Bug #875975 [src:kmod] kmod FTBFS: subprocess.CalledProcessError: Command '['/usr/bin/pkg-config', '--variable=prefix', 'glib-2.0']' returned non-zero exit status 1 Bug reassigned from package 'src:kmod' to

Processed (with 1 error): Re: Bug#875975: kmod FTBFS: subprocess.CalledProcessError: Command '['/usr/bin/pkg-config', '--variable=prefix', 'glib-2.0']' returned non-zero exit status 1

Processing control commands: > reassign -1 gtk-doc/1.26-1 Unknown command or malformed arguments to command. > affects -1 kmod Bug #875975 [src:kmod] kmod FTBFS: subprocess.CalledProcessError: Command '['/usr/bin/pkg-config', '--variable=prefix', 'glib-2.0']' returned non-zero exit status 1

Bug#875975: kmod FTBFS: subprocess.CalledProcessError: Command '['/usr/bin/pkg-config', '--variable=prefix', 'glib-2.0']' returned non-zero exit status 1

Control: reassign -1 gtk-doc/1.26-1 Control: affects -1 kmod Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=787768 Hi, On 16/09/17 20:42, Helmut Grohne wrote: > Source: kmod > Version: 24-1 > Severity: serious > > kmod fails to build from source in unstable. The tail of the

Processed: tagging 874365, tagging 875929

Processing commands for cont...@bugs.debian.org: > tags 874365 - stretch Bug #874365 {Done: HIGUCHI Daisuke (VDR dai) } [ruby-gdk3] ruby-gdk3: Typelib file for namespace 'Gdk' (any version) not found (GLib::Error) Removed tag(s) stretch. > tags 875929 + sid buster Bug #875929

Bug#875975: kmod FTBFS: subprocess.CalledProcessError: Command '['/usr/bin/pkg-config', '--variable=prefix', 'glib-2.0']' returned non-zero exit status 1

Source: kmod Version: 24-1 Severity: serious kmod fails to build from source in unstable. The tail of the build log is: | cd html && gtkdoc-mkhtml $mkhtml_options --path=/<>/build-deb/../libkmod/docs/doc --path=/<>/build-deb/libkmod/docs/doc libkmod ../libkmod-docs.xml | Computing chunks... |

Bug#875957: marked as done (camlidl: uninstallable in sid)

Your message dated Sat, 16 Sep 2017 19:38:31 +0200 with message-id <20170916173830.43y5tagqqefzn...@seneca.home.org> and subject line Re: Bug#875957: camlidl: uninstallable in sid has caused the Debian Bug report #875957, regarding camlidl: uninstallable in sid to be marked as done. This means

Bug#819715: marked as done (node-starttls: FTBFS: Uncaught Error: unable to get local issuer certificate)

Your message dated Sat, 16 Sep 2017 17:35:02 + with message-id and subject line Bug#819715: fixed in node-starttls 1.0.1-2 has caused the Debian Bug report #819715, regarding node-starttls: FTBFS: Uncaught Error: unable to get local issuer certificate to

Bug#875396: haskell-vector: FTBFS on any-i386

Hello, Samuel Thibault, on lun. 11 sept. 2017 10:02:12 +0200, wrote: > In case you have not noticed, the haskell-vector fails the tests on i386 > ports (at least i386 and hurd-i386 failed, kfreebsd-i386 hasn't tried > yet). This is confirmed on kfreebsd-i386. Samuel

Bug#875683: nvidia-graphics-drivers: libGL.so.1 missing with libglvnd libs

On Fri, 2017-09-15 at 02:45 +0200, Andreas Beckmann wrote: > On 15.09.2017 01:30, Luca Boccassi wrote: > > > Is it because libgl1-glvnd-nvidia-glx declares a conflict with > > > libgl1, > > > which libgl1-mesa-glx provides perhaps? > > That's the most likely case. > > I tried a hack (r7481) s.t.

Bug#853559: mozjs24: ftbfs with GCC-7

https://github.com/uhulinux/ub-dev/commit/22ddd3bb42c4b8fb43f7c7263acf86900ea97b2c -- R.

Bug#875945: fixed in at-spi2-core 2.26.0-2

Hello, Jeremy Bicha, on sam. 16 sept. 2017 11:31:48 -0400, wrote: > I added the dependency because it was required for at-spi2-core to > build when I packaged 2.25.90 or .91 but the dependency was correctly > made optional again before 2.26.0 with this commit: > >

Bug#875970: ruby-fog-aws: FTBFS in experimental - test failures

Source: ruby-fog-aws Version: 1.4.1-1 Severity: serious Justification: fails to build from source Hi, the last upload of ruby-fog-aws to experimental did FTBFS: https://buildd.debian.org/status/fetch.php?pkg=ruby-fog-aws=all=1.4.1-1=1505064095=0 ++ Compute::AWS | parsers |

Bug#852591: marked as done (flashcache: Update udevadm path)

Your message dated Sat, 16 Sep 2017 16:31:28 + with message-id and subject line Bug#875682: Removed package(s) from unstable has caused the Debian Bug report #852591, regarding flashcache: Update udevadm path to be marked as done. This means that you

Bug#875969: libopenshot: FTBFS: Timeline_Tests.cpp:158:1: error: Failure in Timeline_Check_Two_Track_Video

Package: libopenshot Version: 0.1.7+ds1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, libopenshot FTBFS on amd64 with test failures: https://buildd.debian.org/status/fetch.php?pkg=libopenshot=amd64=0.1.7%2Bds1-1%2Bb1=1502819536=0

Bug#875967: publicsuffix: FTBFS - UnicodeDecodeError during tests

Source: publicsuffix Version: 20170828.2009-1 Severity: serious Justification: fails to build from source Hi, the last upload of publicsuffix did FTBFS: https://buildd.debian.org/status/fetch.php?pkg=publicsuffix=all=20170828.2009-1=1504820937=0 dpkg-buildpackage: info: source package

Bug#875965: ruby-net-ssh: FTBFS - test failures

Source: ruby-net-ssh Version: 1:4.2.0-1 Severity: serious Justification: fails to build from source Hi, the last upload of ruby-net-ssh does FTBFS: https://buildd.debian.org/status/fetch.php?pkg=ruby-net-ssh=all=1%3A4.2.0-1=1505233484=0

Bug#875945: fixed in at-spi2-core 2.26.0-2

I'm attaching a different way of fixing this issue. I added the dependency because it was required for at-spi2-core to build when I packaged 2.25.90 or .91 but the dependency was correctly made optional again before 2.26.0 with this commit:

Bug#875963: python-azure: ships /usr/lib/python2.7/dist-packages/tests/__init__.py

Package: python-azure Version: 20170915+git-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, /usr/lib/python2.7/dist-packages/test/__init__.py is a way too generic name that shouldn't be used by any python module, since it can easily lead to file conflicts between

Bug#875962: python-oauth2client: ships /usr/lib/python2.7/dist-packages/tests/__init__.py

Package: python-oauth2client Version: 3.0.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, /usr/lib/python2.7/dist-packages/test/__init__.py is a way too generic name that shouldn't be used by any python module, since it can easily lead to file conflicts between

Bug#875929: acetoneiso: should it be removed from Debian

Hi Mattia, The program is dead upstream and I have been maintainting (the bare minimum) on my own. I just saw that some months ago, people from Redhat ported it to Qt5. I'll see what I can get from there, in order to include in a new upload. For these reasons, I would prefer if the package is

Bug#873374: marked as done (libtsk13 4.4.2-1 crash in the dfvfs test suite)

Your message dated Sat, 16 Sep 2017 15:07:50 + with message-id and subject line Bug#873374: fixed in pytsk 20170802-2 has caused the Debian Bug report #873374, regarding libtsk13 4.4.2-1 crash in the dfvfs test suite to be marked as done. This means that

Bug#875881: linux: CVE-2017-1000251

2017-09-15 21:03 GMT+02:00 Christoph Anton Mitterer : > On Fri, 2017-09-15 at 19:18 +0100, Ben Hutchings wrote: > > Probably less critical than you think, since we enable > > CONFIG_CC_STACKPROTECTOR. > > Well... yes, but it wouldn't be the first time in history, that such

Processed: severity of 875958 is normal, tagging 875958

Processing commands for cont...@bugs.debian.org: > severity 875958 normal Bug #875958 [sa-compile] sa-compile: The package fails to run sa-compile Severity set to 'normal' from 'grave' > tags 875958 + unreproducible Bug #875958 [sa-compile] sa-compile: The package fails to run sa-compile Added

Bug#875958: sa-compile: The package fails to run sa-compile

Package: sa-compile Version: 3.4.1-6 Severity: grave Justification: renders package unusable The only purpose of the package is to run the program sa-compile. For this is contains a single command line in postint (post installation scripts) like: su - debian-spamd -c sa-compile The program line

Bug#875957: camlidl: uninstallable in sid

Package: camlidl Version: 1.05-15 Severity: serious Affects: src:plplot Dear maintainer, camlidl is currently not installable in sid, due to an unresolved dependency: # apt install camlidl [...] The following packages have unmet dependencies: camlidl : Depends: ocaml-nox-4.02.3 but it is not

Bug#875948: doxia-sitetools: FTBFS due to missing build dependencies

Control: tags -1 patch see the attached patch. ...and if I actually attach it this time, this might help even more :) -- mvh / best regards Hans Joachim Desserud http://desserud.orgdiff --git a/debian/control b/debian/control index 3b2ae09..edb91cd 100644 --- a/debian/control +++

Processed: Re: doxia-sitetools: FTBFS due to missing build dependencies

Processing control commands: > tags -1 patch Bug #875948 [src:doxia-sitetools] doxia-sitetools: FTBFS due to missing build dependencies Added tag(s) patch. -- 875948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875948 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#875952: moon-lander: contains unlicensed images (and perhaps sounds)

Package: moon-lander Version: 1:1.0-5+b1 Severity: serious Justification: Policy 2.2.1 Dear Maintainer, images/backgrounds contains NASA photos which aren’t DFSG-free AFAIK. The sound files in sounds don’t have a documented origin. Regards, Stephen -- System Information: Debian Release: 9.1

Bug#853559: mozjs24: ftbfs with GCC-7

Simply replace '\0' with NULL in js/src/shell/jsoptparse.cpp:256. -- R.

Bug#875948: doxia-sitetools: FTBFS due to missing build dependencies

Source: doxia-sitetools Version: 1.7.4-2 Severity: serious Tag: patch Dear Maintainer, doxia-sitetools currently fails to build from source with the following error message: [ERROR] Failed to execute goal on project doxia-doc-renderer: Could not resolve dependencies for project

Bug#875897: marked as done (Could not find gem 'sass-listen (~> 4.0.0)', which is required by gem 'sass (~>3.1)', in any of the sources)

Your message dated Sat, 16 Sep 2017 12:37:01 + with message-id and subject line Bug#875897: fixed in ruby-sass 3.5.1-2 has caused the Debian Bug report #875897, regarding Could not find gem 'sass-listen (~> 4.0.0)', which is required by gem 'sass

Bug#875818: dbusada: FTBFS on arm* and alpha: Class_va_list undeclared

Package: src:dbusada Followup-For: Bug #875818 Hello. The attached patch fixes both issues, and removes the now unused stdarg_h.ads. It compiles on amd64, i386 and armel. From: Nicolas Boulenguez Subject: Remove dangling references from g++ generated code. Closes: #875818.

Bug#872874: marked as done (libxkbcommon-x11-dev: Missing depends on libxkbcommon-dev)

Your message dated Sat, 16 Sep 2017 12:04:56 + with message-id and subject line Bug#872874: fixed in libxkbcommon 0.7.1-2 has caused the Debian Bug report #872874, regarding libxkbcommon-x11-dev: Missing depends on libxkbcommon-dev to be marked as done.

Bug#873374: libtsk13 4.4.2-1 crash in the dfvfs test suite

* Eriberto Mota: > Control: reassign 873374 python-tsk > > After a conversation with upstream[1] and several tests, I can confirm > the problem is being caused by python-tsk package. Rebuilding the > package will solve the problem. Thank you for doing the testing and getting to the root of this!

Bug#875945: libatspi0-udeb: uninstallable, depends on libxkbcommon-x11-0

Samuel Thibault (2017-09-16): > Cyril Brulebois, on sam. 16 sept. 2017 13:21:53 +0200, wrote: > > Both your libatspi0-udeb and at-spi2-core-udeb binaries now depend on a > > package which isn't a udeb: libxkbcommon-x11-0; > > Mmm, looking at it, it seems spurious actually:

Bug#875945: marked as done (libatspi0-udeb: uninstallable, depends on libxkbcommon-x11-0)

Your message dated Sat, 16 Sep 2017 11:49:00 + with message-id and subject line Bug#875945: fixed in at-spi2-core 2.26.0-2 has caused the Debian Bug report #875945, regarding libatspi0-udeb: uninstallable, depends on libxkbcommon-x11-0 to be marked as

Bug#875945: libatspi0-udeb: uninstallable, depends on libxkbcommon-x11-0

Control: tags -1 + pending Hello, Cyril Brulebois, on sam. 16 sept. 2017 13:21:53 +0200, wrote: > Both your libatspi0-udeb and at-spi2-core-udeb binaries now depend on a > package which isn't a udeb: libxkbcommon-x11-0; Mmm, looking at it, it seems spurious actually: libxkbcommon-x11.so.0 (it

Processed: Re: Bug#875945: libatspi0-udeb: uninstallable, depends on libxkbcommon-x11-0

Processing control commands: > tags -1 + pending Bug #875945 [libatspi0-udeb] libatspi0-udeb: uninstallable, depends on libxkbcommon-x11-0 Added tag(s) pending. -- 875945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875945 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#875945: libatspi0-udeb: uninstallable, depends on libxkbcommon-x11-0

Package: libatspi0-udeb Version: 2.26.0-1 Severity: serious Tags: d-i Justification: not installable [X-D-Ccing debian-boot@ and debian-x@ for information.] Hi, Both your libatspi0-udeb and at-spi2-core-udeb binaries now depend on a package which isn't a udeb: libxkbcommon-x11-0; I'm filing

Bug#870363: not fixed by 868308

I am not trying to install sane-backends. I am just trying to do aptitude full-upgrade without any error messages. This is the only package on the entire Debian that is making such error messages.

Bug#870363: not fixed by 868308

Please tell me what steps will make the error messages go away.

Bug#868308: marked as done (file conflict with libsane)

Your message dated Sat, 16 Sep 2017 11:23:23 +0200 with message-id <1505553803.9909.6.ca...@jff-webhosting.net> and subject line Re: Bug#870363: not fixed by 868308 has caused the Debian Bug report #870363, regarding file conflict with libsane to be marked as done. This means that you claim that

Bug#870363: marked as done (libsane : Depends: libsane-common (= 1.0.26~git20151121-1) but 1.0.27-1~experimental1 is to be installed)

Your message dated Sat, 16 Sep 2017 11:23:23 +0200 with message-id <1505553803.9909.6.ca...@jff-webhosting.net> and subject line Re: Bug#870363: not fixed by 868308 has caused the Debian Bug report #870363, regarding libsane : Depends: libsane-common (= 1.0.26~git20151121-1) but

Bug#870363: not fixed by 868308

Hello Dan, thank you for spending your time helping to make Debian better with this bug report. Am Samstag, den 16.09.2017, 02:50 +0800 schrieb 積丹尼 Dan Jacobson: > Note all these problems are still currently present: > > The following packages have unmet dependencies: > libsane1 : Breaks:

Bug#784509: marked as done ([postbooks-updater] Qt4's WebKit removal)

Your message dated Sat, 16 Sep 2017 08:53:19 + with message-id and subject line Bug#784509: fixed in postbooks-updater 2.4.0-5 has caused the Debian Bug report #784509, regarding [postbooks-updater] Qt4's WebKit removal to be marked as done. This means

Bug#875875: marked as done (gr-fcdproplus: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/pkgconfig/gnuradio-fcdproplus.pc)

Your message dated Sat, 16 Sep 2017 08:51:14 + with message-id and subject line Bug#875875: fixed in gr-fcdproplus 3.7.25.4b6464b-5 has caused the Debian Bug report #875875, regarding gr-fcdproplus: fails to upgrade from 'stable' to 'sid' - trying to

Bug#875787: marked as done (libgnuradio-iqbalance3.7.11: fails to upgrade from 'stretch' - trying to overwrite /usr/lib/x86_64-linux-gnu/pkgconfig/gnuradio-iqbalance.pc)

Your message dated Sat, 16 Sep 2017 08:51:20 + with message-id and subject line Bug#875787: fixed in gr-iqbal 0.37.2-10 has caused the Debian Bug report #875787, regarding libgnuradio-iqbalance3.7.11: fails to upgrade from 'stretch' - trying to overwrite

Bug#875930: arc-gui-clients: should it be removed from Debian?

Source: arc-gui-clients Version: 0.4.6-3 Severity: serious Hi, arc-gui-clients missed the last stable release (stretch) due to its RC bugs, which have received no input from the maintainer for 9+ months. Also considering the very low popcon, I believe this package in the current state should be

Bug#875929: acetoneiso: should it be removed from Debian

Source: acetoneiso Version: 2.4-2 Severity: serious Hi, this package has long standing RC bugs (even if only recently rised to RC level), without any input from the maintainer for years. Also, it hasn't seen an upload in the last 3 years, that —whilst being no indicator as is— feels kind of

Processed: fixed 874068 in 1.13-0.2

Processing commands for cont...@bugs.debian.org: > fixed 874068 1.13-0.2 Bug #874068 {Done: Sébastien Villemot } [src:ffcall] ABI breakage without shared library renaming Marked as fixed in versions ffcall/1.13-0.2. > thanks Stopping processing here. Please contact me if

Processed: reassign 874068 to src:ffcall

Processing commands for cont...@bugs.debian.org: > reassign 874068 src:ffcall 1.13-0.1 Bug #874068 {Done: Sébastien Villemot } [libffcall1] ABI breakage without shared library renaming Bug reassigned from package 'libffcall1' to 'src:ffcall'. No longer marked as found in

Bug#872496: marked as done (vdr-plugin-xineliboutput FTBFS with vdr 2.3.8)

Your message dated Sat, 16 Sep 2017 07:34:42 + with message-id and subject line Bug#872496: fixed in vdr-plugin-xineliboutput 2.0.0-1 has caused the Debian Bug report #872496, regarding vdr-plugin-xineliboutput FTBFS with vdr 2.3.8 to be marked as done.

Bug#816804: [Pkg-crosswire-devel] Bug#816804: Qt5 version released upstream

I am working on this, time permitting, plus circumstances permitting. On Sat, 16 Sep 2017 at 07:09 Scott Kitterman wrote: > This and #874831 would be resolved if someone would package the new > upstream > release. > > Scott K > >