Processed: apt-show-source: diff for NMU version 0.10+nmu5
Processing control commands: > tags 831917 + pending Bug #831917 [src:apt-show-source] apt-show-source: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute Added tag(s) pending. -- 831917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#831917: apt-show-source: diff for NMU version 0.10+nmu5
Control: tags 831917 + pending I've prepared an NMU for apt-show-source (versioned as 0.10+nmu5) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer or remove it. -- bye, pabs https://wiki.debian.org/PaulWise diff -Nru apt-show-source-0.10+nmu4/debian/changelog apt-show-source-0.10+nmu5/debian/changelog --- apt-show-source-0.10+nmu4/debian/changelog 2015-12-28 03:03:31.0 +0800 +++ apt-show-source-0.10+nmu5/debian/changelog 2016-10-24 14:49:40.0 +0800 @@ -1,3 +1,10 @@ +apt-show-source (0.10+nmu5) unstable; urgency=medium + + * Non-maintainer upload. + * Add patch by Santiago Vila to fix `debuild -A` (Closes: #831917) + + -- Paul Wise Mon, 24 Oct 2016 14:49:40 +0800 + apt-show-source (0.10+nmu4) unstable; urgency=medium * Non-maintainer upload. diff -Nru apt-show-source-0.10+nmu4/debian/rules apt-show-source-0.10+nmu5/debian/rules --- apt-show-source-0.10+nmu4/debian/rules 2015-12-28 04:39:07.0 +0800 +++ apt-show-source-0.10+nmu5/debian/rules 2016-10-24 14:48:47.0 +0800 @@ -53,12 +53,12 @@ $(MAKE) pure_install DESTDIR=$(PWD)/debian/apt-show-source; \ fi -# Build architecture-independent files here. -binary-indep: build install +# Build architecture-dependent files here. +binary-arch: # We have nothing to do by default. -# Build architecture-dependent files here. -binary-arch: build install +# Build architecture-independent files here. +binary-indep: build install # dh_testversion dh_testdir dh_testroot signature.asc Description: This is a digitally signed message part
Processed: limit source to debdry, tagging 805195
Processing commands for cont...@bugs.debian.org: > limit source debdry Limiting to bugs with field 'source' containing at least one of 'debdry' Limit currently set to 'source':'debdry' > tags 805195 + pending Bug #805195 [src:debdry] debdry: FTBFS: ImportError: No module named 'apt_pkg' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 805195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*
On 2016-10-24 00:11, Pietro Battiston wrote: > Package: ardour > Version: 1:5.4.0~dfsg-1 > Severity: grave > > Ardour 1:4.7~dfsg-2 works great. If instead I upgrade to 1:5.3~dfsg-1 (current > unstable) or 1:5.4.0~dfsg-1 (current testing), I get a segfault when I try to > load any project. thanks for your bugreport. is it possible to try the ardour5 binary provided by upstream [1] and see whether the problem persists? fgmasdr IOhannes [1] https://community.ardour.org/download > > I am attaching a gdb run (from 1:5.4.0~dfsg-1). > > > > -- System Information: > Debian Release: stretch/sid > APT prefers testing > APT policy: (650, 'testing'), (600, 'unstable'), (600, 'stable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) > Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages ardour depends on: > ii ardour-data 1:4.2~dfsg-5 > ii jackd 5 > ii libarchive13 3.2.1-4 > ii libasound21.0.29-1 > ii libatk1.0-0 2.18.0-1 > ii libatkmm-1.6-1v5 2.24.2-1 > ii libaubio4 0.4.1-2+b3 > ii libbluetooth3 5.33-1 > ii libc6 2.24-3 > ii libcairo2 1.14.2-2 > ii libcairomm-1.0-1v51.12.0-1 > ii libcurl3-gnutls 7.45.0-1 > ii libcwiid1 0.6.00+svn201-3.2 > ii libfftw3-single3 3.3.5-1 > ii libflac8 1.3.1-4 > ii libfluidsynth11.1.6-3 > ii libfontconfig12.11.0-6.3 > ii libfreetype6 2.6-2 > ii libgcc1 1:5.2.1-22 > ii libgdk-pixbuf2.0-02.36.0-1 > ii libglib2.0-0 2.50.0-1 > ii libglibmm-2.4-1v5 2.50.0-1 > ii libgtk2.0-0 2.24.28-1 > ii libgtkmm-2.4-1v5 1:2.24.5-1 > ii libjack-jackd2-0 [libjack-0.116] 1.9.10+20150825git1ed50c92~dfsg-1 > ii liblilv-0-0 0.24.0~dfsg0-1 > ii liblo70.28-5 > ii liblrdf0 0.4.0-5 > ii libltc11 1.1.4-1 > ii libogg0 1.3.2-1 > ii libpango-1.0-01.38.0-3 > ii libpangocairo-1.0-0 1.38.0-3 > ii libpangoft2-1.0-0 1.38.0-3 > ii libpangomm-1.4-1v52.40.1-3 > ii librubberband21.8.1-6+b1 > ii libsamplerate00.1.8-8 > ii libserd-0-0 0.24.0~dfsg0-1 > ii libsigc++-2.0-0v5 2.10.0-1 > ii libsndfile1 1.0.25-9.1 > ii libsord-0-0 0.16.0~dfsg0-1 > ii libsratom-0-0 0.4.6~dfsg0-1 > ii libstdc++66.2.0-6 > ii libsuil-0-0 0.8.2~dfsg0-1 > ii libtag1v5 1.9.1-2.4 > ii libvamp-hostsdk3v52.6~repack0-2 > ii libvamp-sdk2v52.6~repack0-2 > ii libx11-6 2:1.6.3-1 > ii libxml2 2.9.2+zdfsg1-4 > > Versions of packages ardour recommends: > ii ardour-video-timeline 1:5.4.0~dfsg-1 > ii chromium [www-browser] 50.0.2661.94-1 > ii epiphany-browser [www-browser] 3.18.0-1+b1 > ii firefox-esr [www-browser] 45.0.1esr-1 > ii iceweasel 45.3.0esr-1 > ii links [www-browser] 2.12-1 > ii w3m [www-browser] 0.5.3-25 > > Versions of packages ardour suggests: > pn jamin > ii qjackctl 0.4.0-1 > > -- no debconf information > > > > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintain...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers >
Bug#839931: [Pkg-freeradius-maintainers] Bug#839931: freeradius-config: fails to upgrade from 'sid' - trying to overwrite /etc/freeradius/clients.conf
I think the issue is that the file(s) in question (e.g. /etc/freeradius/hints) are marked as conffiles in freeradius 2.2.8+dfsg-0.1+b3: # grep hints /var/lib/dpkg/info/freeradius.* /var/lib/dpkg/info/freeradius.conffiles:/etc/freeradius/hints /var/lib/dpkg/info/freeradius.list:/etc/freeradius/hints /var/lib/dpkg/info/freeradius.postinst: /etc/freeradius/hints \ /var/lib/dpkg/info/freeradius.prerm: /etc/freeradius/hints \ When updating, the entry vanishes from freeradius.conffiles, but stays in freeradius.list: # dpkg -i freeradius-common_3.0.12+dfsg-1_all.deb freeradius_3.0.12+dfsg-1_amd64.deb libfreeradius3_3.0.12+dfsg-1_amd64.deb freeradius-config_3.0.12+dfsg-1_amd64.deb (Reading database ... 24462 files and directories currently installed.) Preparing to unpack freeradius-common_3.0.12+dfsg-1_all.deb ... Unpacking freeradius-common (3.0.12+dfsg-1) over (3.0.12+dfsg-1) ... Preparing to unpack freeradius_3.0.12+dfsg-1_amd64.deb ... Unpacking freeradius (3.0.12+dfsg-1) over (2.2.8+dfsg-0.1+b3) ... dpkg: warning: unable to delete old directory '/etc/freeradius/sites-enabled': Directory not empty dpkg: warning: unable to delete old directory '/etc/freeradius/sites-available': Directory not empty dpkg: warning: unable to delete old directory '/etc/freeradius/modules': Directory not empty dpkg: warning: unable to delete old directory '/etc/freeradius/certs': Directory not empty dpkg: warning: unable to delete old directory '/etc/freeradius': Directory not empty Preparing to unpack libfreeradius3_3.0.12+dfsg-1_amd64.deb ... Unpacking libfreeradius3 (3.0.12+dfsg-1) over (3.0.12+dfsg-1) ... Preparing to unpack freeradius-config_3.0.12+dfsg-1_amd64.deb ... Unpacking freeradius-config (3.0.12+dfsg-1) ... dpkg: error processing archive freeradius-config_3.0.12+dfsg-1_amd64.deb (--install): trying to overwrite '/etc/freeradius/hints', which is also in package freeradius 3.0.12+dfsg-1 Setting up freeradius-common (3.0.12+dfsg-1) ... dpkg: dependency problems prevent configuration of freeradius: freeradius depends on freeradius-config; however: Package freeradius-config is not installed. dpkg: error processing package freeradius (--install): dependency problems - leaving unconfigured Setting up libfreeradius3 (3.0.12+dfsg-1) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for systemd (229-1) ... Errors were encountered while processing: freeradius-config_3.0.12+dfsg-1_amd64.deb freeradius # grep hints /var/lib/dpkg/info/freeradius.* /var/lib/dpkg/info/freeradius.list:/etc/freeradius/hints /var/lib/dpkg/info/freeradius.postinst: /etc/freeradius/mods-config/preprocess/hints \ /var/lib/dpkg/info/freeradius.prerm: /etc/freeradius/mods-config/preprocess/hints \ anbe, do you know how this situation should be properly handled? Do I need to use rm_conffiles in the maintscripts? Thanks! On Sat, Oct 15, 2016 at 3:15 PM, Andreas Beckmann wrote: > Followup-For: Bug #839931 > Control: found -1 3.0.12+dfsg-1 > > Hi, > > there are still file overwrite problems in the latest version: > > Preparing to unpack .../07-freeradius_3.0.12+dfsg-1_amd64.deb ... > Unpacking freeradius (3.0.12+dfsg-1) over (2.2.8+dfsg-0.1+b3) ... > dpkg: warning: unable to delete old directory > '/etc/freeradius/sites-enabled': > Directory not empty > dpkg: warning: unable to delete old directory > '/etc/freeradius/sites-available': > Directory not empty > dpkg: warning: unable to delete old directory '/etc/freeradius/modules': > Directory not empty > dpkg: warning: unable to delete old directory '/etc/freeradius/certs': > Directory not empty > dpkg: warning: unable to delete old directory '/etc/freeradius': > Directory not empty > Selecting previously unselected package freeradius-config. > Preparing to unpack .../08-freeradius-config_3.0.12+dfsg-1_amd64.deb ... > Unpacking freeradius-config (3.0.12+dfsg-1) ... > dpkg: error processing archive /tmp/apt-dpkg-install-5B7fDA/ > 08-freeradius-config_3.0.12+dfsg-1_amd64.deb (--unpack): >trying to overwrite '/etc/freeradius/hints', which is also in package > freeradius 3.0.12+dfsg-1 > > > Andreas > > ___ > Pkg-freeradius-maintainers mailing list > pkg-freeradius-maintain...@lists.alioth.debian.org > https://lists.alioth.debian.org/mailman/listinfo/pkg- > freeradius-maintainers > -- Best regards, Michael
Bug#840699: ninix-aya: does not work with ruby-gnome2 3.0.9-1
Hi Higuchi, I believe that the upstream has already fixes this issue. In upstream's release notes: 開発環境を Ruby 2.x & Gtk+3 に移行した安定版第2版です。 Ruby-GNOME2 3.0に対応しました。 動作させるには3.0.9以降のRuby/GTK3が必要です。 (2.2.5では動作しなくなっています。) So I'll take some time to see if I can upload it to experimental. But it seems to me that this is not a blocker for you to upload ruby-gnome2 directly to unstable. Yours Sincerely, Paul -- PaulLiu (劉穎駿) E-mail: Ying-Chun Liu (PaulLiu) signature.asc Description: OpenPGP digital signature
Bug#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*
Il giorno lun, 24/10/2016 alle 09.31 +0200, IOhannes m zmölnig ha scritto: > [...] > is it possible to try the ardour5 binary provided by upstream [1] and > see whether the problem persists? > I just did (with the "Free/Demo" version), and it works perfectly (with the same session/jack configuration). However, experimenting a bit more... the packaged ardour5 works too. But if I downgrade to 4.7, it will now segfault :-) So I understood what's going on (but now why): if you install the package for version 4 or 5, it will work. But if you upgrade/downgrade from a version 4 to 5 or vice-versa, the folder in /usr/share (e.g. /usr/share/ardour4) will keep its name, with the result that the new version will not find the required files. For instance, I now have a version 4.7 installed with a /usr/share/ardour5 folder (not appearing in the output of "dpkg -L ardour", by the way). Uninstalling and reinstalling the desired version "fixes" the issue. Pietro
Bug#837582: yabause: FTBFS with bindnow and PIE enabled
On Mon, Sep 12, 2016 at 04:43:31PM +0200, Balint Reczey wrote: > src/gtk/CMakeFiles/yabause-gtk.dir/build.make:713: recipe for target > 'src/gtk/yabause-gtk' failed > make[3]: *** [src/gtk/yabause-gtk] Error 1 > ... 08:36 < Zhenech> Guillaume, debian enabled PIE and bindnow for all builds 08:36 < Zhenech> and yabause fails now :( 08:36 < Zhenech> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837582 08:37 < Guillaume> ah yeah 08:37 < Guillaume> you need to disable the dynarec 08:37 < Guillaume> -DSH2_DYNAREC=OFF 08:37 < Zhenech> also happens with .15 (tried yesterday) 08:38 < Zhenech> what is dynarec? :) 08:38 < Guillaume> the dynamic recompiler version of SH2 08:38 < Guillaume> faster, but... 08:39 < Guillaume> not maintained 08:39 < Guillaume> and it's using a hardcoded pointer
Bug#841904: swift: FTBFS (failing tests)
Package: src:swift
Version: 2.10.0-3
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
[...]
debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
debian/rules:59: warning: overriding recipe for target 'gen-init-configurations'
/usr/share/openstack-pkg-tools/pkgos.make:19: warning: ignoring old recipe for
target 'gen-init-configurations'
debian/rules:69: warning: overriding recipe for target
'override_dh_systemd_enable'
/usr/share/openstack-pkg-tools/pkgos.make:52: warning: ignoring old recipe for
target 'override_dh_systemd_enable'
debian/rules:75: warning: overriding recipe for target 'override_dh_installinit'
/usr/share/openstack-pkg-tools/pkgos.make:55: warning: ignoring old recipe for
target 'override_dh_installinit'
dh build-indep --buildsystem=python_distutils --with python2,sphinxdoc,systemd
dh_testdir -i -O--buildsystem=python_distutils
dh_update_autotools_config -i -O--buildsystem=python_distutils
[... snipped ...]
test_version_manifest_utf8_object
(test.unit.proxy.test_server.TestSocketObjectVersions) ... ok
test_version_manifest_utf8_version_container
(test.unit.proxy.test_server.TestSocketObjectVersions) ... ok
test_version_manifest_utf8_version_container_utf_object
(test.unit.proxy.test_server.TestSocketObjectVersions) ... ok
test_registered_defaults (test.unit.proxy.test_server.TestSwiftInfo) ... ok
test_PUT_sysmeta_then_GET (test.unit.proxy.test_sysmeta.TestObjectSysmeta) ...
ok
test_PUT_sysmeta_then_HEAD (test.unit.proxy.test_sysmeta.TestObjectSysmeta) ...
ok
test_sysmeta_not_updated_by_POST
(test.unit.proxy.test_sysmeta.TestObjectSysmeta) ... ok
test_sysmeta_not_updated_by_POST_as_copy
(test.unit.proxy.test_sysmeta.TestObjectSysmeta) ... ok
test_sysmeta_replaced_by_PUT (test.unit.proxy.test_sysmeta.TestObjectSysmeta)
... ok
test_sysmeta_updated_by_COPY (test.unit.proxy.test_sysmeta.TestObjectSysmeta)
... ok
test_sysmeta_updated_by_COPY_from
(test.unit.proxy.test_sysmeta.TestObjectSysmeta) ... ok
test_transient_sysmeta_replaced_by_PUT_or_POST
(test.unit.proxy.test_sysmeta.TestObjectSysmeta) ... ok
test_transient_sysmeta_replaced_by_PUT_or_POST_as_copy
(test.unit.proxy.test_sysmeta.TestObjectSysmeta) ... ok
test_translations (test.unit.test_locale.test_locale.TestTranslations) ... ok
==
FAIL: test_hash_suffix_one_reclaim_tombstone_with_hash_pkl
(test.unit.obj.test_diskfile.TestSuffixHashes)
--
Traceback (most recent call last):
File "/<>/test/unit/obj/test_diskfile.py", line 5485, in
test_hash_suffix_one_reclaim_tombstone_with_hash_pkl
self.assertGreater(os.stat(hash_file).st_mtime, hash_timestamp)
AssertionError: 1477294357.0770822 not greater than 1477294357.0770822
"""Fail immediately, with the given message."""
>> raise self.failureException('1477294357.0770822 not greater than
>> 1477294357.0770822')
>> begin captured logging <<
root: ERROR: Quarantined /tmp/tmpaBgQRG/node/sda1/objects/0/.lock to
/tmp/tmpaBgQRG/node/quarantined/objects/0 because it is not a directory
Traceback (most recent call last):
File "/<>/swift/obj/diskfile.py", line 922, in _hash_suffix_dir
ondisk_info = self.cleanup_ondisk_files(hsh_path, reclaim_age)
File "/<>/swift/obj/diskfile.py", line 877, in
cleanup_ondisk_files
files = listdir(hsh_path)
File "/<>/swift/common/utils.py", line 3079, in listdir
return os.listdir(path)
OSError: [Errno 20] Not a directory: '/tmp/tmpaBgQRG/node/sda1/objects/0/.lock'
- >> end captured logging << -
--
Ran 4813 tests in 97.635s
FAILED (failures=1)
debian/rules:34: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
I'm attaching the full build log.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the page for this package.
If you could not reproduce this using sbuild on a single CPU virtual machine
(as I did),
please do not downgrade or mark as unreproducible, I would then consider giving
you access
to a virtual machine on w
Processed: Re: Bug#841904: swift: FTBFS (failing tests)
Processing control commands: > severity -1 normal Bug #841904 [src:swift] swift: FTBFS (failing tests) Severity set to 'normal' from 'serious' -- 841904: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841904 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841904: swift: FTBFS (failing tests)
Control: severity -1 normal Please ignore this report for now, I have to triple check.
Processed: Re: Bug#841906: neutron: FTBFS (failing tests)
Processing control commands: > severity -1 normal Bug #841906 [src:neutron] neutron: FTBFS (failing tests) Severity set to 'normal' from 'serious' -- 841906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841906 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841906: neutron: FTBFS (failing tests)
Control: severity -1 normal Please ignore this report for now, I have to triple check. More than one package FTBFS for me today, but they also fail in reproducible builds with semaphore errors, and I'm not completely sure that the package is to blame. [ If, however, it's cheap in terms of human time to trigger a rebuild in a testing chroot and see what happens, feel free of course ]. [ My personal feeling is that the OpenStack transition has not completely finished yet, but I'm not sure about that ]. Thanks.
Processed: Sort out 840989
Processing commands for cont...@bugs.debian.org:
> package dgit
Limiting to bugs with field 'package' containing at least one of 'dgit'
Limit currently set to 'package':'dgit'
> fixed 840989 1.4
Bug #840989 {Done: Ian Jackson } [dgit] dgit
clone dpkg fails
Marked as fixed in versions dgit/1.4.
> found 840989 2.0
Bug #840989 {Done: Ian Jackson } [dgit] dgit
clone dpkg fails
Marked as found in versions dgit/2.0.
> --
Stopping processing here.
Please contact me if you need assistance.
--
840989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Sort out #841867
Processing commands for cont...@bugs.debian.org:
> fixed 841867 1.4
Bug #841867 {Done: Ian Jackson } [dgit] dgit
cannot cope with some patches because it uses gbp-pq
Marked as fixed in versions dgit/1.4.
> found 841867 2.0
Bug #841867 {Done: Ian Jackson } [dgit] dgit
cannot cope with some patches because it uses gbp-pq
Marked as found in versions dgit/2.0.
> --
Stopping processing here.
Please contact me if you need assistance.
--
841867: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#840974: samtools: FTBFS: configure.ac:69: error: macro PKG_CHECK_EXISTS is not defined; is a m4 file missing?
On Sun, Oct 23, 2016 at 04:12:14PM +0200, Sascha Steinbiss wrote: > > > > I've now further tweaked test/test.pl's pty setup to skip the tests instead > > of aborting with this message. So you may wish to pull this in as a patch > > as well as fixing /dev inside your chroot :-) > > > > https://github.com/samtools/samtools/commit/ce4a601a0859bc9ccfcf000dddf0ac77e7d576b3 > > Thanks. This has fixed the problem for me. Is this solution OK for everyone? Fine for me Andreas. -- http://fam-tille.de
Bug#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*
On 2016-10-24 10:38, Pietro Battiston wrote: > Il giorno lun, 24/10/2016 alle 09.31 +0200, IOhannes m zmölnig ha > scritto: >> [...] >> is it possible to try the ardour5 binary provided by upstream [1] and >> see whether the problem persists? >> > > I just did (with the "Free/Demo" version), and it works perfectly (with > the same session/jack configuration). > > However, experimenting a bit more... the packaged ardour5 works too. > But if I downgrade to 4.7, it will now segfault :-) thanks for the additional info. so we have an upgrade problem (and luckily we only need to resolve the upgrade but not the downgrade part :-)) would it be possible for you to (privately) send me a segfaulting project (without the data files), so that i have a known-to-fail project for testing? gmasdr IOhannes
Bug#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*
On 2016-10-24 11:51, IOhannes m zmölnig (Debian/GNU) wrote: > would it be possible for you to (privately) send me a segfaulting > project (without the data files), so that i have a known-to-fail project > for testing? i think i have found the culprit. i will upload a hopefully-fixed package soon (so no need to create send me a known-to-fail project right now) gfmasdr IOhannes
Bug#841868: marked as pending
tag 841868 pending thanks Hello, Bug #841868 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://git.debian.org/?p=pkg-multimedia/ardour.git;a=commitdiff;h=4cb88a6 --- commit 4cb88a6fb7a833536f5cf0ee9e9862fff859d4f7 Author: IOhannes m zmölnig Date: Mon Oct 24 12:05:47 2016 +0200 Ready for upload to unstable. diff --git a/debian/changelog b/debian/changelog index 19eaf2c..e02ea77 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +ardour (1:5.4.0~dfsg-2) unstable; urgency=medium + + * Versioned dependency on ardour-data (Closes: #841868) + + -- IOhannes m zmölnig (Debian/GNU) Mon, 24 Oct 2016 12:05:06 +0200 + ardour (1:5.4.0~dfsg-1) unstable; urgency=medium * New upstream version 5.4.0
Processed: Bug#841868 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 841868 pending Bug #841868 [ardour] Segfault in Gtk::Widget::show() since upgrading to 5.* Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 841868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*
It's just a wild guess, but this Pietro Battiston wrote: > Package: ardour > Version: 1:5.4.0~dfsg-1 [...] > ii ardour-data 1:4.2~dfsg-5 just doesn't seem corect to me! - Fabian
Processed: forwarded 841596 https://github.com/sqlobject/sqlobject/issues/128
Processing commands for cont...@bugs.debian.org: > forwarded 841596 https://github.com/sqlobject/sqlobject/issues/128 Bug #841596 [src:sqlobject] sqlobject: FTBFS: tests failed Set Bug forwarded-to-address to 'https://github.com/sqlobject/sqlobject/issues/128'. > tags 841596 +upstream Bug #841596 [src:sqlobject] sqlobject: FTBFS: tests failed Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 841596: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841596: Tests fail with sqlite 3.15 (upstream bug)
This is due to a change in sqlite 3.15 which breaks a incorrect, but previously harmless, assumption made by sqlobject. A possible fix has been submitted upstream.
Bug#840699: ninix-aya: does not work with ruby-gnome2 3.0.9-1
Control: severity -1 important Control: tags -1 - experimental Thank you for your checking. I will upload ruby-gnome2 3.0.9-2 to unstable. -- Regards, dai GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E signature.asc Description: PGP signature
Processed: Re: ninix-aya: does not work with ruby-gnome2 3.0.9-1
Processing control commands: > severity -1 important Bug #840699 [ninix-aya] ninix-aya: does not work with ruby-gnome2 3.0.9-1 Severity set to 'important' from 'serious' > tags -1 - experimental Bug #840699 [ninix-aya] ninix-aya: does not work with ruby-gnome2 3.0.9-1 Ignoring request to alter tags of bug #840699 to the same tags previously set -- 840699: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#806000: marked as done (brickos: FTBFS when built with dpkg-buildpackage -A (No such file or directory))
Your message dated Mon, 24 Oct 2016 10:52:42 + with message-id and subject line Bug#806000: fixed in brickos 0.9.0.dfsg-12.1 has caused the Debian Bug report #806000, regarding brickos: FTBFS when built with dpkg-buildpackage -A (No such file or directory) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 806000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806000 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:brickos Version: 0.9.0.dfsg-12 User: sanv...@debian.org Usertags: binary-indep Severity: important Dear maintainer: I tried to build this package with "dpkg-buildpackage -A" (i.e. only architecture-independent packages), and it failed: [...] fakeroot debian/rules binary-indep dh binary-indep dh_testroot -i dh_prep -i dh_installdirs -i debian/rules override_dh_auto_install make[1]: Entering directory '/<>' # Install the package into debian/brickos. /usr/bin/make install docs-install inst_prefix=/usr prefix=/<>/debian/brickos/usr mandir=/<>/debian/brickos/usr/share/man make[2]: Entering directory '/<>' make[3]: Entering directory '/<>/util' make[4]: Entering directory '/<>/util/dll-src' cp -f ../dll /<>/debian/brickos/usr/bin/dll cp: cannot create regular file '/<>/debian/brickos/usr/bin/dll': No such file or directory Makefile:57: recipe for target 'install-stamp' failed make[4]: *** [install-stamp] Error 1 make[4]: Leaving directory '/<>/util/dll-src' Makefile:28: recipe for target 'install' failed make[3]: *** [install] Error 2 make[3]: Leaving directory '/<>/util' Makefile:34: recipe for target 'install' failed make[2]: *** [install] Error 2 make[2]: Leaving directory '/<>' debian/rules:35: recipe for target 'override_dh_auto_install' failed make[1]: *** [override_dh_auto_install] Error 2 make[1]: Leaving directory '/<>' debian/rules:13: recipe for target 'binary-indep' failed make: *** [binary-indep] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit status 2 Sorry not to have a fix, as I am reporting many bugs similar to this one, but I can give some general hints: * If all the arch-independent packages are dummy transitional packages released with jessie, the easy fix is to drop them now. * If not, debian/rules should be modified so that the binary-indep target works in all cases, even when binary-arch is not used (this is what the "Architecture: all" autobuilder does). For that: * If you are using debhelper, you might want to use options -a and -i for dh_* commands so that they do not act on packages they do not have to act. * Also, if you are using dh, the (independently) optional targets override_dh_foo-arch and override_dh_foo-indep (for several values of "foo") may be useful to write a debian/rules which behaves exactly as desired. After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work properly, this package will be suitable to be uploaded in source-only form if you wish (you might want to try it). Thanks. --- End Message --- --- Begin Message --- Source: brickos Source-Version: 0.9.0.dfsg-12.1 We believe that the bug you reported is fixed in the latest version of brickos, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 806...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen (supplier of updated brickos package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Oct 2016 07:45:48 + Source: brickos Binary: brickos brickos-doc Architecture: source Version: 0.9.0.dfsg-12.1 Distribution: unstable Urgency: medium Maintainer: Michael Tautschnig Changed-By: Petter Reinholdtsen Description: brickos- alternative OS for LEGO(r) Mindstorms RCX. Supports devel. in C/C brickos-doc - documentation for brickOS an Alternative OS for the RCX Closes: 806000 Changes: brickos (0.9.0.dfsg-12.1) unstable; urgency=medium . * Non-maintainer upload. * Fixed arch independent build problem (Clo
Bug#837490: marked as done (libpapyrus3-dev: Please build libPapyrus3.a with -fPIC)
Your message dated Mon, 24 Oct 2016 11:05:11 + with message-id and subject line Bug#837490: fixed in papyrus 3.7.1+dfsg-1 has caused the Debian Bug report #837490, regarding libpapyrus3-dev: Please build libPapyrus3.a with -fPIC to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 837490: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837490 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libpapyrus3-dev Version: 3.7.1-1 Severity: important User: bal...@balintreczey.hu Usertags: pie-bindnow-20160906 Justification: makes gdcm FTBFS with extra hardening Affects: gdcm Dear Maintainers, During a rebuild of all packages in sid, gdcm failed to build on amd64 with patched GCC and dpkg. The root cause seems to be that libPapyrus3.a is shipped as a non-PIC library. The rebuild tested if packages are ready for a transition enabling PIE and bindnow for amd64 (and selected architectures). For more information about the changes to sid's dpkg and GCC please visit: https://wiki.debian.org/Hardening/PIEByDefaultTransition Relevant part of gdcm's build log: ... /usr/bin/c++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror= format-security -Wdate-time -D_FORTIFY_SOURCE=2-Wl,-z,relro -Wl,-z,now -Wl,--as-needed CMakeFiles/ gdcmpap3.dir/gdcmpap3.cxx.o -o ../../bin/gdcmpap3 -rdynamic ../../bin/libgdcmMSFF.so.2.6.5 -Wl,-Bstat ic -lPapyrus3 -Wl,-Bdynamic ../../bin/libgdcmDICT.so.2.6.5 ../../bin/libgdcmIOD.so.2.6.5 ../../bin/lib gdcmDSED.so.2.6.5 ../../bin/libgdcmCommon.so.2.6.5 -Wl,-rpath-link,/<>/obj-x86_64-linux-g nu/bin /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/6/../../../../lib/libPapyrus3.a(PapyError3.c.o): relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a shared object; recompile with -fPI C ... The full build log is available from: https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/gdcm_2.6.5-2_amd64.build.gz Thanks, Balint --- End Message --- --- Begin Message --- Source: papyrus Source-Version: 3.7.1+dfsg-1 We believe that the bug you reported is fixed in the latest version of papyrus, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 837...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated papyrus package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Oct 2016 12:29:54 +0200 Source: papyrus Binary: libpapyrus3-dev Architecture: source amd64 Version: 3.7.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: libpapyrus3-dev - DICOM compatible file format library Closes: 837490 Changes: papyrus (3.7.1+dfsg-1) unstable; urgency=medium . * Move packaging to Git since several files need to be excluded from upstream tarball * Add myself to Uploaders since Mathieu left the team * cme fix dpkg-control * cme fix dpkg-copyright * Build-Depends: cmake * hardening=-pie Closes: #837490 Checksums-Sha1: 19c2f31e958c9972a900a839ddb622a9dd935143 1965 papyrus_3.7.1+dfsg-1.dsc ff471deb64da48a71b286b3186964bbd76e3bdc5 624928 papyrus_3.7.1+dfsg.orig.tar.xz b21f159160ad210568008883f5f5dd23c35cbfa6 11624 papyrus_3.7.1+dfsg-1.debian.tar.xz 2c4e8409ead81ab776797e460e86cb035eda4e9a 240212 libpapyrus3-dev_3.7.1+dfsg-1_amd64.deb Checksums-Sha256: c9fb555f53daa63466ad6b32032c69c8124ed342de885a04ebd21169e7b3c06e 1965 papyrus_3.7.1+dfsg-1.dsc a0af8cd9144d4527c27782084f82551a7aa5ba57fc0e277b191ba513e4789edc 624928 papyrus_3.7.1+dfsg.orig.tar.xz baed709cf742010bc483beb83e138f5ef3f63d2e8c78533846e2fa01609f461c 11624 papyrus_3.7.1+dfsg-1.debian.tar.xz 32d11fc7e6912801e279ab38c1107343f79a94a3603d56ef9094ba114642c977 240212 libpapyrus3-dev_3.7.1+dfsg-1_amd64.deb Files: e9c217e42933dcce64648751a726d9dc 1965 libdevel optional papyrus_3.7.1+dfsg-1.dsc 941419c192ea4de6bf144557bf46afb9 624928 libdevel optional papyrus_3.7.1+dfsg.orig.tar.xz 10df48529e07092dfc81e2310c96264d 11624 libdevel optional papyrus_3.7.1+dfsg-1.debian.tar.xz 3e70be8b84e2b823aa36bc97aff38449 240212 libdevel optional libpap
Bug#837683: marked as done (opt: Please build libopt.a with -fPIC)
Your message dated Mon, 24 Oct 2016 11:05:01 + with message-id and subject line Bug#837683: fixed in opt 3.19-1.3 has caused the Debian Bug report #837683, regarding opt: Please build libopt.a with -fPIC to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 837683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837683 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: opt Version: 3.19-1.2 Severity: important User: bal...@balintreczey.hu Usertags: pie-bindnow-20160906 Justification: makes proftmb FTBFS with extra hardening Affects: proftmb Dear Maintainers, During a rebuild of all packages in sid, proftmb failed to build on amd64 with patched GCC and dpkg. The root cause seems to be that libopt.a is shipped as a non-PIC library. The rebuild tested if packages are ready for a transition enabling PIE and bindnow for amd64 (and selected architectures). For more information about the changes to sid's dpkg and GCC please visit: https://wiki.debian.org/Hardening/PIEByDefaultTransition Relevant part of proftmb's build log: ... g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -o proftmb proftmb.o libhmm.a -lgsl -lgslcblas -lm -lopt /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/6/../../../../lib/libopt.a(opt_proc.o): relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC ... The full build log is available from: https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/proftmb_1.1.12-6_amd64.build.gz Thanks, Balint --- End Message --- --- Begin Message --- Source: opt Source-Version: 3.19-1.3 We believe that the bug you reported is fixed in the latest version of opt, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 837...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated opt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Oct 2016 11:09:31 +0200 Source: opt Binary: opt Architecture: source amd64 Version: 3.19-1.3 Distribution: unstable Urgency: medium Maintainer: Patrick Ouellette Changed-By: Andreas Tille Description: opt- Options Parsing Tool library Closes: 837683 Changes: opt (3.19-1.3) unstable; urgency=medium . * Non-maintainer upload. * Inject package into collab-maint Git * hardening=-pie Closes: #837683 * delete irrelevant README.debian * delete unneeded prerm * source format 3.0 * cme fix dpkg-control Checksums-Sha1: 5294524afcabfac83f6378ed58f11bb203921d99 1710 opt_3.19-1.3.dsc 854e5ff2b0a9b1a5a3300f5a38cf813be4da8735 3509 opt_3.19-1.3.diff.gz 2d8dfad021491e6f3eb10c66af70cd0231fb312d 43528 opt_3.19-1.3_amd64.deb Checksums-Sha256: 49da482c985f50076ca1edf07855ec048a1b2ef6c9ceebb0a0d0b778d6acce66 1710 opt_3.19-1.3.dsc ba0422670b04467803d4a037a46513d94a6513d102d17dc11b81d16ad9d742f4 3509 opt_3.19-1.3.diff.gz 5e77bd1bd223323ccc546cd9027155048406b3509fec07daa9791409bbaefa8d 43528 opt_3.19-1.3_amd64.deb Files: e0096aa56da9ad233c0ac086ab530389 1710 devel optional opt_3.19-1.3.dsc 7aef906ea75a2fc742c7d069cc2811a3 3509 devel optional opt_3.19-1.3.diff.gz 55c0e7c91cbf0c5384b4f411d3f3b422 43528 devel optional opt_3.19-1.3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJYDdGoAAoJEFeKBJTRxkbRJKYQAJmVCI4eUV1MZjiGnQ1kN+Es 2OlRxMFExV9NXFU/S/h9z0tQfu8924W3/kusdlLcQYUmWOz64nNU9X7Ho7bPLsl5 6d5eQkNHuMSskDT3i6RrtCo00HeE2LmubObcE8wFN/aEwtZiC0UbsAlJpQZfj5W8 Olx8uyATuNXMHyjzfc71tCxzDD1CqXhfRnQz79UVW1cEg8SjGKrmKnklMjziHzLU lUw8eni3IpCoKRPJv5IEy9KPrXDFo4uMMwzhxgOQUfGefj9aNt5na3gW6dEoBBAn y4Hf2LcoPLoijHlLdvwUOzbplKj2Zl/v9UqsQu6xSQbzjtUErOGzTKCFxk6AanEe gl7wwdz+xtOu1hXAL8R7Ci4336Ja40foRIZwpWMYDvfVd1ki4oexghLXm7H+3Lc8 1++mUYc//HQaX4NA62e/kMGdIZ7w43IXRuDMs6VAgTxh1zGBLc2jAHpmlfheEs0a xSez96c0Acu+SsDE3eSbiegxNJ04sYUQLyHlcsPV7EzEDWgbiqV/IBQHqWNR/sBz vye/JPTGOQuNx2eWbKERgm3sBeMCj1aDJVbY2qctnPEH5dj8rHF2iAt2puQoo/tk QTGaujcsDtfvO82Fqsv5bBp8YvRHt6zn1GVi5BJM2cdn1joGVXQB6jOTLJFmXn5g ys8pvd2X6siDDnV7ob6U =sriv -END PGP SIGNATURE End Message ---
Bug#803059: marked as done (sensors-applet: FTBFS with gnome-common 3.18: cannot open gnome-doc-utils.make)
Your message dated Mon, 24 Oct 2016 11:08:55 + with message-id and subject line Bug#803059: fixed in sensors-applet 3.0.0+git6-0.1 has caused the Debian Bug report #803059, regarding sensors-applet: FTBFS with gnome-common 3.18: cannot open gnome-doc-utils.make to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 803059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803059 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sensors-applet Version: 3.0.0+git5-0.1 Severity: important Tags: fixed-upstream Dear Maintainer, sensors-applet FTBFS with gnome-common 3.18 from experimental: dh_autoreconf --as-needed ./autogen.sh -- --version /usr/bin/gnome-autogen.sh ... automake: error: cannot open < gnome-doc-utils.make: No such file or directory autoreconf: automake failed with exit status: 1 dh_autoreconf: ./autogen.sh --version returned exit code 1 debian/rules:27: recipe for target 'override_dh_autoreconf' failed This was fixed upstream in this commit: https://sourceforge.net/p/sensors-applet/code/ci/148c624f77106c14/ -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: sensors-applet Source-Version: 3.0.0+git6-0.1 We believe that the bug you reported is fixed in the latest version of sensors-applet, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 803...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Shachnev (supplier of updated sensors-applet package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Oct 2016 13:07:40 +0300 Source: sensors-applet Binary: sensors-applet libsensors-applet-plugin0 libsensors-applet-plugin-dev Architecture: source Version: 3.0.0+git6-0.1 Distribution: unstable Urgency: medium Maintainer: Sam Morris Changed-By: Dmitry Shachnev Description: libsensors-applet-plugin-dev - Create plugins for the 'sensors-applet' package libsensors-applet-plugin0 - Library for plugins for the 'sensors-applet' package sensors-applet - Display readings from hardware sensors in your Gnome panel Closes: 803059 Changes: sensors-applet (3.0.0+git6-0.1) unstable; urgency=medium . * Non-maintainer upload. * New snapshot from upstream Git repository (commit 07284262768e3a70). - Ported to new documentation system (closes: #803059). - Applet ported to in-process for compatibility with libpanel-applet2. * Build-depend on yelp-tools. * Bump libgtk-3-dev build-dependency to 3.4.0, following configure.ac. * Update debian/sensors-applet.install for the in-process switch. Checksums-Sha1: 0b4bc6c37d0186fdd6c679de5df100f7e71e37bc 2388 sensors-applet_3.0.0+git6-0.1.dsc 4ca03475e49a317cc2b85fcd23bcdfb009988988 103636 sensors-applet_3.0.0+git6.orig.tar.xz 2bd5ec8eaeea353109f2a6793ef26eabe0b2ec2a 14156 sensors-applet_3.0.0+git6-0.1.debian.tar.xz Checksums-Sha256: 83908cf10306d2459099f6f0dc087b246473210cc20bbc665943542f28b01124 2388 sensors-applet_3.0.0+git6-0.1.dsc 069ea1a7c622ccdb9a4a63ef7b3f26124e179ed23b0d4c4dca1dce7752367469 103636 sensors-applet_3.0.0+git6.orig.tar.xz 6763554a4d15394943daea7dccadf626d5817a52efbb666ae5d0cc9793c29a08 14156 sensors-applet_3.0.0+git6-0.1.debian.tar.xz Files: 2cf38cfd754835a22ed77cdce624cf9d 2388 gnome optional sensors-applet_3.0.0+git6-0.1.dsc 960d3ff7e8e29906e83034b7097eb668 103636 gnome optional sensors-applet_3.0.0+git6.orig.tar.xz 051378bb76be8c7a9bf9e874f8748136 14156 gnome optional sensors-applet_3.0.0+git6-0.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIwBAEBCAAaBQJYDd21ExxtaXR5YTU3QGRlYmlhbi5vcmcACgkQ1v5xA2P4XdP/ QQ/+OvwF3CCCU+cZTrfJCYL1tIcPJuKa+hS/iPlTYomJcCInZRJiVygndaB2R2q4 8AmSS9xwtqmtSX86jeaRL4rywb0Bk2KPXsDWfhVgkIoAlbtZgqlW+JC+CoisiRCS HsUUBUyJijflFqC5dW5cwI9vk8qAxi6xjIITKP0uAQJvr4V7kjD5UFTtKbTyfEjZ S6vBjzoEkeRR/+yx7TNKQct9HEJjqaQQiS12WguwC8xLJBvmEuDk1pgc8PCAogBk yJl3d2LUnweiYjm2BBA44ZULW4cMvbprPLvefR9JAMoMxCpIbYmWHopV9BZHcx2Y xAeDKAyWw53KuCMjv6zKiUhFSsXIwNc4USIUfuCErwlooIq0BzbudNGAQO6KKDaO R2DWUpvURLQ+0x7u/LhFg5dCtte5yYwiJ+hn1hI7e8JWERwpK9vm8mAOBiG21r08 Gmnh3mhB2vm2YqXEUV4CDCuKWnONAA6dVkKFjJjImKb8ulMSiee
Bug#837561: marked as done (kvmtool: FTBFS with bindnow and PIE enabled)
Your message dated Mon, 24 Oct 2016 11:42:08 + with message-id and subject line Bug#837545: fixed in kvmtool 0.20161024-1 has caused the Debian Bug report #837545, regarding kvmtool: FTBFS with bindnow and PIE enabled to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 837545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kvmtool Version: 0.20160419-1 Severity: important User: bal...@balintreczey.hu Usertags: pie-bindnow-20160906 Justification: FTBFS on amd64 with extra hardening Hi, During a rebuild of all packages in sid, your package failed to build on amd64 with patched GCC and dpkg. The rebuild tested if packages are ready for a transition enabling PIE and bindnow for amd64. For more information about the changes to sid's dpkg and GCC please visit: https://wiki.debian.org/Hardening/PIEByDefaultTransition Relevant part (hopefully): ... CC x86/bios.o In file included from x86/bios.c:9:0: x86/bios/bios-rom.h:12:27: error: ISO C99 requires whitespace after the macro name [-Werror] #define BIOS_OFFSETx86.get_pc_thunk.bx 0x02ea ^ cc1: all warnings being treated as errors Makefile:426: recipe for target 'x86/bios.o' failed ... The full build log is available from: https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/kvmtool_0.20160419-1_amd64.build.gz Thanks, Balint --- End Message --- --- Begin Message --- Source: kvmtool Source-Version: 0.20161024-1 We believe that the bug you reported is fixed in the latest version of kvmtool, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 837...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Riku Voipio (supplier of updated kvmtool package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Oct 2016 10:09:40 + Source: kvmtool Binary: kvmtool Architecture: source Version: 0.20161024-1 Distribution: sid Urgency: medium Maintainer: Riku Voipio Changed-By: Riku Voipio Description: kvmtool- Native Linux KVM TOOL Closes: 837545 837561 Changes: kvmtool (0.20161024-1) sid; urgency=medium . * Disable PIE for the bios blob, closes: 837561, 837545 * CI - kvmtool snapshot: - repository: git://git.kernel.org/pub/scm/linux/kernel/git/will/kvmtool.git - commit: 0093df8 - build: https://ci.linaro.org/jenkins/job/build-kvmtool/88/ . - debian/ repository: git://anonscm.debian.org/collab-maint/kvmtool.git - debian/ commit: ab02560 Checksums-Sha1: 90bfbc683a223664cbd6f09c2b23851703472ab3 2167 kvmtool_0.20161024-1.dsc b8ed9ff708df2b544cc84fcc4f6a2b37fb376fd8 192544 kvmtool_0.20161024.orig.tar.xz 627574a21a8a4cff37d04a68c934d131d1770087 2940 kvmtool_0.20161024-1.debian.tar.xz Checksums-Sha256: 8f0becaf85912df9b9f8f00e6fc4aea3747d51fa72612f5770e409883081e9da 2167 kvmtool_0.20161024-1.dsc d285bf32e9d578a4b8248ec9c2b462e37eab36127d0c55d4eb5c5a92d8b5fd9a 192544 kvmtool_0.20161024.orig.tar.xz 00956f37be93ac3e142dbc4e74d5dfb11a4ae51034c88995db0ccb145a983f10 2940 kvmtool_0.20161024-1.debian.tar.xz Files: 35c4188682bfbe272e2884a2b3b24e13 2167 kernel optional kvmtool_0.20161024-1.dsc 693d2c4669583b0e7cdbabfafd1e38e1 192544 kernel optional kvmtool_0.20161024.orig.tar.xz 17eb4fe9c8b98929deb1bc98ea067f94 2940 kernel optional kvmtool_0.20161024-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIVAwUBWA3ibLRIkN7ePJvAAQjM2Q/7BOCZJdUba2k5j1bK8bCsix5t0uO7l9Y9 Wl5boLRW1VCxj4patwoYAsAd/dmUB+ZyLbEYmQv5LQwrIatb/q5uSYAWxRibF0e4 xVDmPDqzmZmPMFLjltdOOD3lgfH1TcaygAuJitp3TLnv43ilD0T/xaMZEAJKiq1N S+reutLGbJtI7IDDG3IPL8hetUaMw8zuCmnoe1gV0gRoqM5IpLoq201p/Y3SnAlM vC74H89G42AFLeFp9dS2n5rM90kKklBmoylJ6IDzeGAEndsBtuwsOhwv+Ti9G8zC wMlH34eimvRqQiCVrifQyf5b4meLx2ZUkXg5iMITioc0Rgd62loWuaiL0nsp94JF zms0isfItyDvDuS/z/wwljeZljm3QlpGus9TcaTnNbDOUfZeLHZZKXds4Gv28NVO cOky6Hj/BnE9eisNB8rlYrNJrSST5bGPofdaKcXmQaRkyIwZakQusy74pKlpOfKe e/9tQR+AVzF8L0O9Zg/rVftNLAHY2mNxgCRZlWkORS9Y0rEaGxQc+0+LsU+YU3wJ IOhWBNcYWNZNo7UobOjVctLseTi8A6sD/D1EcCeXfmYOyewojJmoN6KJqVIRKwJe yBrKEbMZWIuiJKYk+IMQGI/5hHiSGGsjVnW/9PoVtpOQgA6oPazDH
Bug#837545: marked as done (kvmtool: FTBFS with bindnow and PIE enabled)
Your message dated Mon, 24 Oct 2016 11:42:08 + with message-id and subject line Bug#837545: fixed in kvmtool 0.20161024-1 has caused the Debian Bug report #837545, regarding kvmtool: FTBFS with bindnow and PIE enabled to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 837545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kvmtool Version: 0.20160419-1 Severity: important User: bal...@balintreczey.hu Usertags: pie-bindnow-20160906 Justification: FTBFS on amd64 with extra hardening Hi, During a rebuild of all packages in sid, your package failed to build on amd64 with patched GCC and dpkg. The rebuild tested if packages are ready for a transition enabling PIE and bindnow for amd64. For more information about the changes to sid's dpkg and GCC please visit: https://wiki.debian.org/Hardening/PIEByDefaultTransition Relevant part (hopefully): ... CC x86/bios.o In file included from x86/bios.c:9:0: x86/bios/bios-rom.h:12:27: error: ISO C99 requires whitespace after the macro name [-Werror] #define BIOS_OFFSETx86.get_pc_thunk.bx 0x02ea ^ cc1: all warnings being treated as errors Makefile:426: recipe for target 'x86/bios.o' failed make[1]: *** [x86/bios.o] Error 1 make[1]: Leaving directory '/<>' dh_auto_build: make -j1 returned exit code 2 debian/rules:3: recipe for target 'build' failed make: *** [build] Error 2 ... The full build log is available from: https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/kvmtool_0.20160419-1_amd64.build.gz Thanks, Balint --- End Message --- --- Begin Message --- Source: kvmtool Source-Version: 0.20161024-1 We believe that the bug you reported is fixed in the latest version of kvmtool, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 837...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Riku Voipio (supplier of updated kvmtool package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Oct 2016 10:09:40 + Source: kvmtool Binary: kvmtool Architecture: source Version: 0.20161024-1 Distribution: sid Urgency: medium Maintainer: Riku Voipio Changed-By: Riku Voipio Description: kvmtool- Native Linux KVM TOOL Closes: 837545 837561 Changes: kvmtool (0.20161024-1) sid; urgency=medium . * Disable PIE for the bios blob, closes: 837561, 837545 * CI - kvmtool snapshot: - repository: git://git.kernel.org/pub/scm/linux/kernel/git/will/kvmtool.git - commit: 0093df8 - build: https://ci.linaro.org/jenkins/job/build-kvmtool/88/ . - debian/ repository: git://anonscm.debian.org/collab-maint/kvmtool.git - debian/ commit: ab02560 Checksums-Sha1: 90bfbc683a223664cbd6f09c2b23851703472ab3 2167 kvmtool_0.20161024-1.dsc b8ed9ff708df2b544cc84fcc4f6a2b37fb376fd8 192544 kvmtool_0.20161024.orig.tar.xz 627574a21a8a4cff37d04a68c934d131d1770087 2940 kvmtool_0.20161024-1.debian.tar.xz Checksums-Sha256: 8f0becaf85912df9b9f8f00e6fc4aea3747d51fa72612f5770e409883081e9da 2167 kvmtool_0.20161024-1.dsc d285bf32e9d578a4b8248ec9c2b462e37eab36127d0c55d4eb5c5a92d8b5fd9a 192544 kvmtool_0.20161024.orig.tar.xz 00956f37be93ac3e142dbc4e74d5dfb11a4ae51034c88995db0ccb145a983f10 2940 kvmtool_0.20161024-1.debian.tar.xz Files: 35c4188682bfbe272e2884a2b3b24e13 2167 kernel optional kvmtool_0.20161024-1.dsc 693d2c4669583b0e7cdbabfafd1e38e1 192544 kernel optional kvmtool_0.20161024.orig.tar.xz 17eb4fe9c8b98929deb1bc98ea067f94 2940 kernel optional kvmtool_0.20161024-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIVAwUBWA3ibLRIkN7ePJvAAQjM2Q/7BOCZJdUba2k5j1bK8bCsix5t0uO7l9Y9 Wl5boLRW1VCxj4patwoYAsAd/dmUB+ZyLbEYmQv5LQwrIatb/q5uSYAWxRibF0e4 xVDmPDqzmZmPMFLjltdOOD3lgfH1TcaygAuJitp3TLnv43ilD0T/xaMZEAJKiq1N S+reutLGbJtI7IDDG3IPL8hetUaMw8zuCmnoe1gV0gRoqM5IpLoq201p/Y3SnAlM vC74H89G42AFLeFp9dS2n5rM90kKklBmoylJ6IDzeGAEndsBtuwsOhwv+Ti9G8zC wMlH34eimvRqQiCVrifQyf5b4meLx2ZUkXg5iMITioc0Rgd62loWuaiL0nsp94JF zms0isfItyDvDuS/z/wwljeZljm3QlpGus9TcaTnNbDOUfZeLHZZKXds4Gv28NVO cOky6Hj/BnE9eisNB8rlYrNJrSST5bGPofdaKcXmQaRkyIwZakQusy74pKlp
Processed (with 1 error): Re: Bug#841906: neutron: FTBFS randomly (failing tests)
Processing control commands: > severity -1 serious Bug #841906 [src:neutron] neutron: FTBFS (failing tests) Severity set to 'serious' from 'normal' > retitle neutron: FTBFS randomly (failing tests) Unknown command or malformed arguments to command. -- 841906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841906 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#837561: marked as done (kvmtool: FTBFS with bindnow and PIE enabled)
Your message dated Mon, 24 Oct 2016 11:42:08 + with message-id and subject line Bug#837561: fixed in kvmtool 0.20161024-1 has caused the Debian Bug report #837561, regarding kvmtool: FTBFS with bindnow and PIE enabled to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 837561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kvmtool Version: 0.20160419-1 Severity: important User: bal...@balintreczey.hu Usertags: pie-bindnow-20160906 Justification: FTBFS on amd64 with extra hardening Hi, During a rebuild of all packages in sid, your package failed to build on amd64 with patched GCC and dpkg. The rebuild tested if packages are ready for a transition enabling PIE and bindnow for amd64. For more information about the changes to sid's dpkg and GCC please visit: https://wiki.debian.org/Hardening/PIEByDefaultTransition Relevant part (hopefully): ... CC x86/bios.o In file included from x86/bios.c:9:0: x86/bios/bios-rom.h:12:27: error: ISO C99 requires whitespace after the macro name [-Werror] #define BIOS_OFFSETx86.get_pc_thunk.bx 0x02ea ^ cc1: all warnings being treated as errors Makefile:426: recipe for target 'x86/bios.o' failed ... The full build log is available from: https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/kvmtool_0.20160419-1_amd64.build.gz Thanks, Balint --- End Message --- --- Begin Message --- Source: kvmtool Source-Version: 0.20161024-1 We believe that the bug you reported is fixed in the latest version of kvmtool, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 837...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Riku Voipio (supplier of updated kvmtool package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Oct 2016 10:09:40 + Source: kvmtool Binary: kvmtool Architecture: source Version: 0.20161024-1 Distribution: sid Urgency: medium Maintainer: Riku Voipio Changed-By: Riku Voipio Description: kvmtool- Native Linux KVM TOOL Closes: 837545 837561 Changes: kvmtool (0.20161024-1) sid; urgency=medium . * Disable PIE for the bios blob, closes: 837561, 837545 * CI - kvmtool snapshot: - repository: git://git.kernel.org/pub/scm/linux/kernel/git/will/kvmtool.git - commit: 0093df8 - build: https://ci.linaro.org/jenkins/job/build-kvmtool/88/ . - debian/ repository: git://anonscm.debian.org/collab-maint/kvmtool.git - debian/ commit: ab02560 Checksums-Sha1: 90bfbc683a223664cbd6f09c2b23851703472ab3 2167 kvmtool_0.20161024-1.dsc b8ed9ff708df2b544cc84fcc4f6a2b37fb376fd8 192544 kvmtool_0.20161024.orig.tar.xz 627574a21a8a4cff37d04a68c934d131d1770087 2940 kvmtool_0.20161024-1.debian.tar.xz Checksums-Sha256: 8f0becaf85912df9b9f8f00e6fc4aea3747d51fa72612f5770e409883081e9da 2167 kvmtool_0.20161024-1.dsc d285bf32e9d578a4b8248ec9c2b462e37eab36127d0c55d4eb5c5a92d8b5fd9a 192544 kvmtool_0.20161024.orig.tar.xz 00956f37be93ac3e142dbc4e74d5dfb11a4ae51034c88995db0ccb145a983f10 2940 kvmtool_0.20161024-1.debian.tar.xz Files: 35c4188682bfbe272e2884a2b3b24e13 2167 kernel optional kvmtool_0.20161024-1.dsc 693d2c4669583b0e7cdbabfafd1e38e1 192544 kernel optional kvmtool_0.20161024.orig.tar.xz 17eb4fe9c8b98929deb1bc98ea067f94 2940 kernel optional kvmtool_0.20161024-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIVAwUBWA3ibLRIkN7ePJvAAQjM2Q/7BOCZJdUba2k5j1bK8bCsix5t0uO7l9Y9 Wl5boLRW1VCxj4patwoYAsAd/dmUB+ZyLbEYmQv5LQwrIatb/q5uSYAWxRibF0e4 xVDmPDqzmZmPMFLjltdOOD3lgfH1TcaygAuJitp3TLnv43ilD0T/xaMZEAJKiq1N S+reutLGbJtI7IDDG3IPL8hetUaMw8zuCmnoe1gV0gRoqM5IpLoq201p/Y3SnAlM vC74H89G42AFLeFp9dS2n5rM90kKklBmoylJ6IDzeGAEndsBtuwsOhwv+Ti9G8zC wMlH34eimvRqQiCVrifQyf5b4meLx2ZUkXg5iMITioc0Rgd62loWuaiL0nsp94JF zms0isfItyDvDuS/z/wwljeZljm3QlpGus9TcaTnNbDOUfZeLHZZKXds4Gv28NVO cOky6Hj/BnE9eisNB8rlYrNJrSST5bGPofdaKcXmQaRkyIwZakQusy74pKlpOfKe e/9tQR+AVzF8L0O9Zg/rVftNLAHY2mNxgCRZlWkORS9Y0rEaGxQc+0+LsU+YU3wJ IOhWBNcYWNZNo7UobOjVctLseTi8A6sD/D1EcCeXfmYOyewojJmoN6KJqVIRKwJe yBrKEbMZWIuiJKYk+IMQGI/5hHiSGGsjVnW/9PoVtpOQgA6oPazDH
Bug#837545: marked as done (kvmtool: FTBFS with bindnow and PIE enabled)
Your message dated Mon, 24 Oct 2016 11:42:08 + with message-id and subject line Bug#837561: fixed in kvmtool 0.20161024-1 has caused the Debian Bug report #837561, regarding kvmtool: FTBFS with bindnow and PIE enabled to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 837561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kvmtool Version: 0.20160419-1 Severity: important User: bal...@balintreczey.hu Usertags: pie-bindnow-20160906 Justification: FTBFS on amd64 with extra hardening Hi, During a rebuild of all packages in sid, your package failed to build on amd64 with patched GCC and dpkg. The rebuild tested if packages are ready for a transition enabling PIE and bindnow for amd64. For more information about the changes to sid's dpkg and GCC please visit: https://wiki.debian.org/Hardening/PIEByDefaultTransition Relevant part (hopefully): ... CC x86/bios.o In file included from x86/bios.c:9:0: x86/bios/bios-rom.h:12:27: error: ISO C99 requires whitespace after the macro name [-Werror] #define BIOS_OFFSETx86.get_pc_thunk.bx 0x02ea ^ cc1: all warnings being treated as errors Makefile:426: recipe for target 'x86/bios.o' failed make[1]: *** [x86/bios.o] Error 1 make[1]: Leaving directory '/<>' dh_auto_build: make -j1 returned exit code 2 debian/rules:3: recipe for target 'build' failed make: *** [build] Error 2 ... The full build log is available from: https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/kvmtool_0.20160419-1_amd64.build.gz Thanks, Balint --- End Message --- --- Begin Message --- Source: kvmtool Source-Version: 0.20161024-1 We believe that the bug you reported is fixed in the latest version of kvmtool, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 837...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Riku Voipio (supplier of updated kvmtool package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Oct 2016 10:09:40 + Source: kvmtool Binary: kvmtool Architecture: source Version: 0.20161024-1 Distribution: sid Urgency: medium Maintainer: Riku Voipio Changed-By: Riku Voipio Description: kvmtool- Native Linux KVM TOOL Closes: 837545 837561 Changes: kvmtool (0.20161024-1) sid; urgency=medium . * Disable PIE for the bios blob, closes: 837561, 837545 * CI - kvmtool snapshot: - repository: git://git.kernel.org/pub/scm/linux/kernel/git/will/kvmtool.git - commit: 0093df8 - build: https://ci.linaro.org/jenkins/job/build-kvmtool/88/ . - debian/ repository: git://anonscm.debian.org/collab-maint/kvmtool.git - debian/ commit: ab02560 Checksums-Sha1: 90bfbc683a223664cbd6f09c2b23851703472ab3 2167 kvmtool_0.20161024-1.dsc b8ed9ff708df2b544cc84fcc4f6a2b37fb376fd8 192544 kvmtool_0.20161024.orig.tar.xz 627574a21a8a4cff37d04a68c934d131d1770087 2940 kvmtool_0.20161024-1.debian.tar.xz Checksums-Sha256: 8f0becaf85912df9b9f8f00e6fc4aea3747d51fa72612f5770e409883081e9da 2167 kvmtool_0.20161024-1.dsc d285bf32e9d578a4b8248ec9c2b462e37eab36127d0c55d4eb5c5a92d8b5fd9a 192544 kvmtool_0.20161024.orig.tar.xz 00956f37be93ac3e142dbc4e74d5dfb11a4ae51034c88995db0ccb145a983f10 2940 kvmtool_0.20161024-1.debian.tar.xz Files: 35c4188682bfbe272e2884a2b3b24e13 2167 kernel optional kvmtool_0.20161024-1.dsc 693d2c4669583b0e7cdbabfafd1e38e1 192544 kernel optional kvmtool_0.20161024.orig.tar.xz 17eb4fe9c8b98929deb1bc98ea067f94 2940 kernel optional kvmtool_0.20161024-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIVAwUBWA3ibLRIkN7ePJvAAQjM2Q/7BOCZJdUba2k5j1bK8bCsix5t0uO7l9Y9 Wl5boLRW1VCxj4patwoYAsAd/dmUB+ZyLbEYmQv5LQwrIatb/q5uSYAWxRibF0e4 xVDmPDqzmZmPMFLjltdOOD3lgfH1TcaygAuJitp3TLnv43ilD0T/xaMZEAJKiq1N S+reutLGbJtI7IDDG3IPL8hetUaMw8zuCmnoe1gV0gRoqM5IpLoq201p/Y3SnAlM vC74H89G42AFLeFp9dS2n5rM90kKklBmoylJ6IDzeGAEndsBtuwsOhwv+Ti9G8zC wMlH34eimvRqQiCVrifQyf5b4meLx2ZUkXg5iMITioc0Rgd62loWuaiL0nsp94JF zms0isfItyDvDuS/z/wwljeZljm3QlpGus9TcaTnNbDOUfZeLHZZKXds4Gv28NVO cOky6Hj/BnE9eisNB8rlYrNJrSST5bGPofdaKcXmQaRkyIwZakQusy74pKlp
Bug#841868: marked as done (Segfault in Gtk::Widget::show() since upgrading to 5.*)
Your message dated Mon, 24 Oct 2016 11:41:20 + with message-id and subject line Bug#841868: fixed in ardour 1:5.4.0~dfsg-2 has caused the Debian Bug report #841868, regarding Segfault in Gtk::Widget::show() since upgrading to 5.* to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 841868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ardour Version: 1:5.4.0~dfsg-1 Severity: grave Ardour 1:4.7~dfsg-2 works great. If instead I upgrade to 1:5.3~dfsg-1 (current unstable) or 1:5.4.0~dfsg-1 (current testing), I get a segfault when I try to load any project. I am attaching a gdb run (from 1:5.4.0~dfsg-1). -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (600, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ardour depends on: ii ardour-data 1:4.2~dfsg-5 ii jackd 5 ii libarchive13 3.2.1-4 ii libasound21.0.29-1 ii libatk1.0-0 2.18.0-1 ii libatkmm-1.6-1v5 2.24.2-1 ii libaubio4 0.4.1-2+b3 ii libbluetooth3 5.33-1 ii libc6 2.24-3 ii libcairo2 1.14.2-2 ii libcairomm-1.0-1v51.12.0-1 ii libcurl3-gnutls 7.45.0-1 ii libcwiid1 0.6.00+svn201-3.2 ii libfftw3-single3 3.3.5-1 ii libflac8 1.3.1-4 ii libfluidsynth11.1.6-3 ii libfontconfig12.11.0-6.3 ii libfreetype6 2.6-2 ii libgcc1 1:5.2.1-22 ii libgdk-pixbuf2.0-02.36.0-1 ii libglib2.0-0 2.50.0-1 ii libglibmm-2.4-1v5 2.50.0-1 ii libgtk2.0-0 2.24.28-1 ii libgtkmm-2.4-1v5 1:2.24.5-1 ii libjack-jackd2-0 [libjack-0.116] 1.9.10+20150825git1ed50c92~dfsg-1 ii liblilv-0-0 0.24.0~dfsg0-1 ii liblo70.28-5 ii liblrdf0 0.4.0-5 ii libltc11 1.1.4-1 ii libogg0 1.3.2-1 ii libpango-1.0-01.38.0-3 ii libpangocairo-1.0-0 1.38.0-3 ii libpangoft2-1.0-0 1.38.0-3 ii libpangomm-1.4-1v52.40.1-3 ii librubberband21.8.1-6+b1 ii libsamplerate00.1.8-8 ii libserd-0-0 0.24.0~dfsg0-1 ii libsigc++-2.0-0v5 2.10.0-1 ii libsndfile1 1.0.25-9.1 ii libsord-0-0 0.16.0~dfsg0-1 ii libsratom-0-0 0.4.6~dfsg0-1 ii libstdc++66.2.0-6 ii libsuil-0-0 0.8.2~dfsg0-1 ii libtag1v5 1.9.1-2.4 ii libvamp-hostsdk3v52.6~repack0-2 ii libvamp-sdk2v52.6~repack0-2 ii libx11-6 2:1.6.3-1 ii libxml2 2.9.2+zdfsg1-4 Versions of packages ardour recommends: ii ardour-video-timeline 1:5.4.0~dfsg-1 ii chromium [www-browser] 50.0.2661.94-1 ii epiphany-browser [www-browser] 3.18.0-1+b1 ii firefox-esr [www-browser] 45.0.1esr-1 ii iceweasel 45.3.0esr-1 ii links [www-browser] 2.12-1 ii w3m [www-browser] 0.5.3-25 Versions of packages ardour suggests: pn jamin ii qjackctl 0.4.0-1 -- no debconf information (gdb) r Starting program: /usr/lib/ardour5/ardour-5.4.0 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Cannot find ArdourMono TrueType font bind txt domain [gtk2_ardour5] to /usr/share/ardour5/locale Ardour5.4.0 (built using 1:5.4.0~dfsg-1 and GCC version 6.2.0 20161010) ardour: [INFO]: Your system is configured to limit Ardour to only 65.536 open files ardour: [INFO]: Loading system configuration file /etc/ardour5/system_config ardour: [INFO]: Loading user configuration file /home/pietro/.config/ardour5/config [New Thread 0x7fffd942d700 (LWP 27425)] ardour: [INFO]: CPU vendor: Ge
Bug#841098: not fixed in rygel 0.32.1-1
Hello Santiago Vila. Thanks for the backtrace, it's helpful. On Fri, Oct 21, 2016 at 01:16:20PM +0200, Santiago Vila wrote: > The package FTBFS (sometimes) because rygel-media-engine-test segfaults. > > Here is a backtrace: > > (gdb) bt > #0 0x7f1a1a4b3fdf in raise () from /lib/x86_64-linux-gnu/libc.so.6 > #1 0x7f1a1a4b540a in abort () from /lib/x86_64-linux-gnu/libc.so.6 > #2 0x7f1a1af8a4f5 in g_assertion_message () from > /lib/x86_64-linux-gnu/libglib-2.0.so.0 This is not a segfault though, but an assertion failure. > #3 0x7f1a1af8a58a in g_assertion_message_expr () from > /lib/x86_64-linux-gnu/libglib-2.0.so.0 > #4 0x55597c5578bd in __lambda19_ (_data3_=) at > rygel-media-engine-test.c:2035 [...] ^^^ hint on where the failing assertion can be found. (Please note that the source is vala so you'll need to translate this to the applicable lambda in the vala source.) > #5 ___lambda19__gsource_func (self=0x7f19f4001410) at > rygel-media-engine-test.c:2047 > #6 0x7f1a1af6368a in g_main_context_dispatch () from > /lib/x86_64-linux-gnu/libglib-2.0.so.0 > #7 0x7f1a1af63a40 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 > #8 0x7f1a1af63d62 in g_main_loop_run () from > /lib/x86_64-linux-gnu/libglib-2.0.so.0 > #9 0x55597c559688 in rygel_data_source_test_test_stop_start > (error=0x7ffe67fae238, self=0x55597df7e4e0) > at rygel-media-engine-test.c:2116 > #10 rygel_data_source_test_run (self=0x55597df7e4e0) at > rygel-media-engine-test.c:2717 > #11 0x55597c55a310 in rygel_data_source_test_main (args=, > args_length1=) > at rygel-media-engine-test.c:2996 > #12 0x7f1a1a4a12b1 in __libc_start_main () from > /lib/x86_64-linux-gnu/libc.so.6 > #13 0x55597c556f4a in _start () > > It could be, of course, that my autobuilder is misconfigured, but the > same segfault happened several times in buildd.debian.org in the past. You're more than welcome to dive deep into this issue. Patches are always welcome. Claiming this is RC is a bit over the top though. If you're only out to ride the policy train without actually wanting to debug it yourself then I'll be forced to simply disable the testsuite. In my opinion the testsuite exists to raise the quality of what we produce and to *save* us time. If it becomes to time-consuming to maintain I'll do without it. Disabling failing tests-suites is something I know from personal experience that several release team members have a strong opinion against. Disabling it for a extremely rare occational failure is something I imagine they would be even more opposed to. If you're strongly attached to (cluttering up my maintainer view and) tracking every issue in the debian bug tracking system (I'd instead recommend you use the upstream bug tracker), then I'd welcome a bug report with severity minor. Minor is in my opinion the correct severity for such an issue. Regards, Andreas Henriksson
Bug#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*
Il giorno lun, 24/10/2016 alle 12.06 +0200, Fabian Greffrath ha scritto: > It's just a wild guess, but this > > Pietro Battiston wrote: > > > > Package: ardour > > Version: 1:5.4.0~dfsg-1 > [...] > > > > ii ardour-data 1:4.2~dfsg-5 > > just doesn't seem corect to me! > Oooohhh... right. This explains everything. Package "ardour" should probably depend on the same exact version of package "ardour-data". Pietro
Processed: Re: Bug#841906: neutron: FTBFS randomly (failing tests)
Processing commands for cont...@bugs.debian.org: > retitle 841906 neutron: FTBFS randomly (failing tests) Bug #841906 [src:neutron] neutron: FTBFS (failing tests) Changed Bug title to 'neutron: FTBFS randomly (failing tests)' from 'neutron: FTBFS (failing tests)'. > End of message, stopping processing here. Please contact me if you need assistance. -- 841906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841906 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#840698: xnetcardconfig: does not work with ruby-gnome2 3.0.9-1
Control: tags -1 - experimental I uploaded ruby-gnome2 3.0.9-2 to unstable. -- Regards, dai GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E signature.asc Description: PGP signature
Processed: Re: xnetcardconfig: does not work with ruby-gnome2 3.0.9-1
Processing control commands: > tags -1 - experimental Bug #840698 [xnetcardconfig] xnetcardconfig: does not work with ruby-gnome2 3.0.9-1 Ignoring request to alter tags of bug #840698 to the same tags previously set -- 840698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840698 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#840974: samtools: FTBFS: configure.ac:69: error: macro PKG_CHECK_EXISTS is not defined; is a m4 file missing?
Hi. [...] >> Thanks. This has fixed the problem for me. Is this solution OK for everyone? > > Fine for me OK, I'll upload later. Cheers Sascha
Processed: Re: alfa: build-depends on libcfitsio3-dev
Processing commands for cont...@bugs.debian.org: > severity 841658 serious Bug #841658 [alfa] alfa: build-depends on libcfitsio3-dev Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 841658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#812532: files with the same name installed in / and /usr
On Sun, Oct 23, 2016 at 02:06:29AM +0200, Marco d'Itri wrote: > On Oct 23, Mark Brown wrote: > > I'd have expected to at least have seen something going round saying > > that the transition was mostly complete and that there were only a few > > packages blocking it prior to just dumping a new version of deboostrap > > in unstable and rendering everything instabuggy. Most similar > I did this in *february* for the other packages, but not this one since > you had recently suggested that it was not ready anyway. Telling other package maintainers doesn't help me know that this is a transition that's actually happening, and one of the things that would tell me that there might be some sense of urgency would be an indication that the transition was actually happening. I do remember you asking me about my plans to fix it but there was no context that this was anything more than a "hey, it'd be nice sometime". For things like this even if people aren't working on something now if there's a bigger picture it's good to tell people about it, something like "OK, but please note that we're actively working on this transition and expect it to be done for stretch" would've really helped here in avoiding surprise with sudden RC bugs out of nowhere. > > I didn't ask for help because I just don't care about this transition, > > in part because as I indicated there's no way to really use yp-tools at > > present so it's the least of anyone's worries so when I'm spending time > Maybe then the package should not be in testing anyway? It's not impossible that someone could use it, it's just not as useful as it could be. signature.asc Description: PGP signature
Bug#841511: python-bitbucket-api, python-bitbucket: error when trying to install together
I think python-bitbucket can be removed. Its functionality is quite limited. Regards El vie., 21 oct. 2016 a las 18:28, ChangZhuo Chen () escribió: > On Fri, Oct 21, 2016 at 11:42:03AM +0200, Andreas Beckmann wrote: > > This is a serious bug as it makes installation fail, and violates > > sections 7.6.1 and 10.1 of the policy. An optimal solution would > > consist in only one of the packages installing that file, and renaming > > or removing the file in the other package. Depending on the > > circumstances you might also consider Replace relations or file > > diversions. If the conflicting situation cannot be resolved then, as a > > last resort, the two packages have to declare a mutual > > Conflict. Please take into account that Replaces, Conflicts and > > diversions should only be used when packages provide different > > implementations for the same functionality. > > I has checked the code, and these two packages provide very different > implementation of bitbucket API. So I think the solution is mutual > Conflict. > > Another solution is removing python-bitbucket-api since I only need > python3-bitbucket-api for git-repo (#840371), and it is Python3 only. > Not sure if that is a good solution, but it can solve the problem too. > > > -- > ChangZhuo Chen (陳昌倬) > Debian Developer (https://nm.debian.org/public/person/czchen) > Key fingerprint = EC9F 905D 866D BE46 A896 C827 BE0C 9242 03F4 552D > BA04 346D C2E1 FE63 C790 8793 CC65 B0CD EC27 5D5B >
Bug#838112: marked as done (uctodata: fails to upgrade from 'jessie' - trying to overwrite /etc/ucto/es.abr)
Your message dated Mon, 24 Oct 2016 12:54:34 + with message-id and subject line Bug#838112: fixed in uctodata 0.2-1 has caused the Debian Bug report #838112, regarding uctodata: fails to upgrade from 'jessie' - trying to overwrite /etc/ucto/es.abr to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 838112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: uctodata Version: 0.1.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'jessie'. It installed fine in 'jessie', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package uctodata. Preparing to unpack .../uctodata_0.1.1-1_all.deb ... Unpacking uctodata (0.1.1-1) ... dpkg: error processing archive /var/cache/apt/archives/uctodata_0.1.1-1_all.deb (--unpack): trying to overwrite '/etc/ucto/es.abr', which is also in package ucto 0.5.3-3.1+b1 Errors were encountered while processing: /var/cache/apt/archives/uctodata_0.1.1-1_all.deb cheers, Andreas ucto=0.5.3-3.1+b1_uctodata=0.1.1-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: uctodata Source-Version: 0.2-1 We believe that the bug you reported is fixed in the latest version of uctodata, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 838...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Maarten van Gompel (supplier of updated uctodata package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 18 Oct 2016 14:25:00 +0200 Source: uctodata Binary: uctodata Architecture: source Version: 0.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Maarten van Gompel Description: uctodata - Data files for Ucto Closes: 838112 Changes: uctodata (0.2-1) unstable; urgency=medium . * New upstream * debian/control: cleanup, whitespace * debian/control: bumped compat level/debhelper to 10, fixed Vcs-git, pointed to wrong package * debian/control: Added replaces+breaks for older pre-split ucto versions (Closes: #838112), thanks to Andreas Beckmann * debian/control: added Multi-Arch: foreign * debian/copyright: ordering fixes, symlink fix * d/uctodata.lintian-overrides: obsolete, removed (Thanks to Mattia Rizzolo for pointing out most of the above) Checksums-Sha1: 4adf1e36ca8986236e38d778a4c6dcc712fd358e 1988 uctodata_0.2-1.dsc 85962f9be81741db8f2540224f07d2d6aa508ebf 88991 uctodata_0.2.orig.tar.gz 664f51e781b9650884b6868c443792c03af72722 2172 uctodata_0.2-1.debian.tar.xz Checksums-Sha256: 79adbc024585322202dbb75aa153d3c422ffb8a478e8e08501856d71110d23c3 1988 uctodata_0.2-1.dsc 5ab98efefdee0f2afce0af4c96247c3f49b07ea4e5ee2930bb22d311b3a747a1 88991 uctodata_0.2.orig.tar.gz e727d39e937db467e7cc5f8034dbb64f5e5ccf7910d5f194225dda328155d99e 2172 uctodata_0.2-1.debian.tar.xz Files: afedb70c5d3c6e827f3c59eefcd57351 1988 science extra uctodata_0.2-1.dsc 0aad6fa5afe5b4d3255a2e9c7ddb14b1 88991 science extra uctodata_0.2.orig.tar.gz 36eb04f122c6f3d619182f7e478fa493 2172 science extra uctodata_0.2-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYDf17AAoJEAgWueGMdiutgWgQAKgAxF4ZkyhzejDdQwRD5tOu vy4Spupixy+0sg/pEpNK84I6ch0WjdPgys8Uz7uArgcRvJA7OS5ijncWSZuEyK0/ Tv+krh7AahZsz1gOHsDKV4uIg8Hhwo5mvOW5kPnD0HtctqyjqSCIYqDM2YGYAL/u 2Ybb32li2tDlK96svlDoT0ikhcI+w37RTb44C/96NPyXA5v+bTeatPJ04c35t/WM 8Oryi7aQc6ELz9sS+n19iTTUCx1wovd2jCF/JII4r4H8d2QaUynAf63fiWWMYQdA lwG4BK5XrEW/9KD6XM5LZ3fZxugdp0w5OpY6AGMi0GqO8nLp+T7qXey4Ob58/0cN Lds5vGpIwMGSdKPCsQ3DbMqOcbs5vzrL3yvtyWlgtGMI6I1P2iJGLm2Sh4u0AqNC LxotrDk6T3hULndZdbz4Wg6GVX8SH3SzjRDWUOw1/SU0gQb/txbMYZYdDMueSMCl Hm2i3XVAdTeVr3+5O0e3rTjTQ/lQo3PzzD6DSPTQgzxpZZSrbY0viKyUChihfnhB 0j7C5mPiCMmxtuxVf3dUJs0mnPPKZDQd/1jm+cL/w/IK
Processed: nmu: binutils_2.27-9
Processing control commands: > block 837350 by -1 Bug #837350 [src:binutils] binutils: Please build libbfd.a with -fPIC 837350 was not blocked by any bugs. 837350 was blocking: 837359 Added blocking bug(s) of 837350: 841921 -- 837350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837350 841921: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841921 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Bug#841736: lilypond in Testing?
Processing control commands: > forcemerge -1 746005 Bug #841736 [lilypond] lilypond in Testing? Bug #746005 [lilypond] lilypond: please migrate to guile-2.0 Unset Bug forwarded-to-address Severity set to 'normal' from 'serious' Failed to forcibly merge 841736: Not altering archived bugs; see unarchive. -- 746005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746005 841736: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841098: not fixed in rygel 0.32.1-1
On Mon, Oct 24, 2016 at 01:45:24PM +0200, Andreas Henriksson wrote: > If you're strongly attached to (cluttering up my maintainer view and) > tracking every issue in the debian bug tracking system (I'd instead > recommend you use the upstream bug tracker), then I'd welcome > a bug report with severity minor. Minor is in my opinion the correct > severity for such an issue. I'm only attached to ensuring that Debian packages build ok and without failures (release policy), so I have to decline your suggestion to use the upstream bug tracker, as that will not make the Debian package to build ok 100% of the time again. If you think this is not RC, you can always ask for permission to use sarge-ignore here (you could ask in the same report if it's ok for them to disable the test). IMO, disabling the test would be just a way to follow release policy, which says "packages must build without failures". If you plan to downgrade instead, please consider these two bugs as well: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839444 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811068 The three bugs are FTBFS which happen randomly. The package usually builds fine in the official autobuilders (but not always), and the FTBFS problem could be avoided trivially by disabling one or more tests. It would be really strange to downgrade one of those bugs and not the others. Before doing so, please try to reach a consensus inside the GNOME team about what should be done with all those bugs. Thanks.
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 841691 + pending Bug #841691 [sabnzbdplus] sabnzbdplus: uninstallable with libjs-jquery 3.1.1-1 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 841691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#837823: fprintd: diff for NMU version 0.6.0-2.1
Control: tags 837823 + patch Control: tags 837823 + pending Dear maintainer, I've prepared an NMU for fprintd (versioned as 0.6.0-2.1) I'm looking for and sponsor, then I'll upload it to DELAYED/5. Please feel free to tell me if I should delay it longer. After the package reach the archive I'll upload to the git repo Regards. -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: https://keybase.io/gfa diff -Nru fprintd-0.6.0/debian/changelog fprintd-0.6.0/debian/changelog --- fprintd-0.6.0/debian/changelog 2016-06-09 03:32:03.0 +0800 +++ fprintd-0.6.0/debian/changelog 2016-10-24 20:40:42.0 +0800 @@ -1,3 +1,11 @@ +fprintd (0.6.0-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add intltool to build-dep, preparing for the deprecation of gnome-common, +Fixes FTBFS. (Closes: #837823). + + -- gustavo panizzo Mon, 24 Oct 2016 20:40:42 +0800 + fprintd (0.6.0-2) unstable; urgency=medium [ Santiago Vila ] diff -Nru fprintd-0.6.0/debian/control fprintd-0.6.0/debian/control --- fprintd-0.6.0/debian/control 2016-06-09 03:31:31.0 +0800 +++ fprintd-0.6.0/debian/control 2016-10-24 20:33:56.0 +0800 @@ -9,6 +9,7 @@ libdbus-glib-1-dev, libpolkit-gobject-1-dev, gtk-doc-tools, + intltool, libpam0g-dev Standards-Version: 3.9.8 Homepage: http://www.freedesktop.org/wiki/Software/fprint/fprintd signature.asc Description: PGP signature
Processed: fprintd: diff for NMU version 0.6.0-2.1
Processing control commands: > tags 837823 + patch Bug #837823 [src:fprintd] fprintd: FTBFS due to undeclared build dependencies Added tag(s) patch. > tags 837823 + pending Bug #837823 [src:fprintd] fprintd: FTBFS due to undeclared build dependencies Added tag(s) pending. -- 837823: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: nmu: check_0.10.0-3
Processing control commands: > block 837445 by -1 Bug #837445 [src:check] check: Please build libcheck.a with -fPIC Bug #841757 [src:check] mpc: FTBFS: relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC 837445 was not blocked by any bugs. 837445 was not blocking any bugs. Added blocking bug(s) of 837445: 841927 841757 was not blocked by any bugs. 841757 was not blocking any bugs. Added blocking bug(s) of 841757: 841927 -- 837445: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837445 841757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841757 841927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#837350: Only a binNMU is required for binutils
Control: retitle -1 binutils needs PIE binNMU A binNMU is sufficient to fix this, and already requested. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#837823: fprintd: diff for NMU version 0.6.0-2.1
Previous patch has urgency=medium, this patch has urgency=low. I plan to upload this patch Apologizes for the noise -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: https://keybase.io/gfa diff -Nru fprintd-0.6.0/debian/changelog fprintd-0.6.0/debian/changelog --- fprintd-0.6.0/debian/changelog 2016-06-09 03:32:03.0 +0800 +++ fprintd-0.6.0/debian/changelog 2016-10-24 20:40:42.0 +0800 @@ -1,3 +1,11 @@ +fprintd (0.6.0-2.1) unstable; urgency=low + + * Non-maintainer upload. + * Add intltool to build-dep, preparing for the deprecation of gnome-common, +Fixes FTBFS. (Closes: #837823). + + -- gustavo panizzo Mon, 24 Oct 2016 20:40:42 +0800 + fprintd (0.6.0-2) unstable; urgency=medium [ Santiago Vila ] diff -Nru fprintd-0.6.0/debian/control fprintd-0.6.0/debian/control --- fprintd-0.6.0/debian/control 2016-06-09 03:31:31.0 +0800 +++ fprintd-0.6.0/debian/control 2016-10-24 20:33:56.0 +0800 @@ -9,6 +9,7 @@ libdbus-glib-1-dev, libpolkit-gobject-1-dev, gtk-doc-tools, + intltool, libpam0g-dev Standards-Version: 3.9.8 Homepage: http://www.freedesktop.org/wiki/Software/fprint/fprintd signature.asc Description: PGP signature
Processed: Only a binNMU is required
Processing control commands: > retitle -1 check needs PIE binNMU Bug #837445 [src:check] check: Please build libcheck.a with -fPIC Bug #841757 [src:check] mpc: FTBFS: relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC Changed Bug title to 'check needs PIE binNMU' from 'check: Please build libcheck.a with -fPIC'. Changed Bug title to 'check needs PIE binNMU' from 'mpc: FTBFS: relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC'. -- 837445: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837445 841757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#837445: Only a binNMU is required
Control: retitle -1 check needs PIE binNMU A binNMU is sufficient to fix this, and already requested. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: Only a binNMU is required for binutils
Processing control commands: > retitle -1 binutils needs PIE binNMU Bug #837350 [src:binutils] binutils: Please build libbfd.a with -fPIC Changed Bug title to 'binutils needs PIE binNMU' from 'binutils: Please build libbfd.a with -fPIC'. -- 837350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*
On 2016-10-24 13:48, Pietro Battiston wrote: > Il giorno lun, 24/10/2016 alle 12.06 +0200, Fabian Greffrath ha > scritto: >> It's just a wild guess, but this >> >> Pietro Battiston wrote: >>> >>> Package: ardour >>> Version: 1:5.4.0~dfsg-1 >> [...] >>> >>> ii ardour-data 1:4.2~dfsg-5 >> >> just doesn't seem corect to me! >> > > Oooohhh... > right. > This explains everything. > > Package "ardour" should probably depend on the same exact version of > package "ardour-data". this is the fix i uploaded today with 1:5.4.0~dfsg-2 fgasdr IOhannes
Bug#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*
Il giorno lun, 24/10/2016 alle 16.28 +0200, IOhannes m zmölnig (Debian/GNU) ha scritto: > > On 2016-10-24 13:48, Pietro Battiston wrote: > > > > Il giorno lun, 24/10/2016 alle 12.06 +0200, Fabian Greffrath ha > > scritto: > > > > > > It's just a wild guess, but this > > > > > > Pietro Battiston wrote: > > > > > > > > > > > > Package: ardour > > > > Version: 1:5.4.0~dfsg-1 > > > [...] > > > > > > > > > > > > ii ardour-data 1:4.2~dfsg-5 > > > > > > just doesn't seem corect to me! > > > > > > > Oooohhh... > > right. > > This explains everything. > > > > Package "ardour" should probably depend on the same exact version > > of > > package "ardour-data". > > this is the fix i uploaded today with 1:5.4.0~dfsg-2 Yep, I replied before seeing it! Thank you very much, Pietro
Processed: No patch required
Processing commands for cont...@bugs.debian.org: > tags 837350 -patch Bug #837350 [src:binutils] binutils needs PIE binNMU Removed tag(s) patch. > tags 837445 -patch Bug #837445 [src:check] check needs PIE binNMU Bug #841757 [src:check] check needs PIE binNMU Removed tag(s) patch. Removed tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 837350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837350 837445: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837445 841757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: nmu: jack-audio-connection-kit_1:0.125.0-1+b1
Processing control commands: > block 837423 by -1 Bug #837423 [src:jack-audio-connection-kit] jack-audio-connection-kit: Please build libjack.a with -fPIC 837423 was not blocked by any bugs. 837423 was not blocking any bugs. Added blocking bug(s) of 837423: 841930 -- 837423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837423 841930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#837423: Only a binNMU is required
Control: retitle -1 jack-audio-connection-kit needs PIE binNMU Control: tags -1 -patch A binNMU is sufficient to fix this, and already requested. Building static libraries with PIC is not permitted by policy. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: Only a binNMU is required
Processing control commands: > retitle -1 jack-audio-connection-kit needs PIE binNMU Bug #837423 [src:jack-audio-connection-kit] jack-audio-connection-kit: Please build libjack.a with -fPIC Changed Bug title to 'jack-audio-connection-kit needs PIE binNMU' from 'jack-audio-connection-kit: Please build libjack.a with -fPIC'. > tags -1 -patch Bug #837423 [src:jack-audio-connection-kit] jack-audio-connection-kit needs PIE binNMU Removed tag(s) patch. -- 837423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libctl binnmu blocks 837568
Processing commands for cont...@bugs.debian.org:
> block 837568 by 841929
Bug #837568 {Done: Thorsten Alteholz } [libctl-dev]
libctl-dev: Please build libctlgeom.a with -fPIC
837568 was not blocked by any bugs.
837568 was not blocking any bugs.
Added blocking bug(s) of 837568: 841929
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
837568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#840827: lucene-solr: FTBFS (failing tests, no route to host)
Hi Santiago, I got a look at this issue and it seems the failing tests are setting up a local RMI server but the subsequent connections do not work. I don't know why it fails with your machines but if I'm not mistaken local connections are allowed during the build. Is the IP you redacted the one from the machine building the package, or another machine on your network? Is it possible that the tests hit a TCP connection limit on the host? Emmanuel Bourg
Bug#840847: (no subject)
Any chance this fix can get uploaded soon-ish? gtimelog build depends on it so it's marked for autoremoval because of this bug. Thanks!
Processed: nmu: ocaml_4.02.3-7
Processing control commands: > block 837359 by -1 Bug #837359 [src:ocaml] ocaml: Please build libasmrun.a and libcamlrun.a with -fPIC 837359 was blocked by: 837350 837359 was not blocking any bugs. Added blocking bug(s) of 837359: 841938 -- 837359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837359 841938: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841938 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#837359: Only a binNMU is required
Control: retitle -1 ocaml needs PIE binNMU Control: tags -1 -patch A binNMU is sufficient to fix this, and already requested. Policy does not permit building static libraries with PIC unless there is a special reason. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: Only a binNMU is required
Processing control commands: > retitle -1 ocaml needs PIE binNMU Bug #837359 [src:ocaml] ocaml: Please build libasmrun.a and libcamlrun.a with -fPIC Changed Bug title to 'ocaml needs PIE binNMU' from 'ocaml: Please build libasmrun.a and libcamlrun.a with -fPIC'. > tags -1 -patch Bug #837359 [src:ocaml] ocaml needs PIE binNMU Removed tag(s) patch. -- 837359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Also block the binNMU requests
Processing control commands: > block -1 by 841921 837350 Bug #841938 [release.debian.org] nmu: ocaml_4.02.3-7 841938 was not blocked by any bugs. 841938 was blocking: 837359 Added blocking bug(s) of 841938: 837350 and 841921 -- 841938: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841938 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841709: [uscan] missing package parameter at call of debian/repack.sh
control: severity -1 normal Hi, On Sat, Oct 22, 2016 at 04:19:29PM +0200, Jörg Frings-Fürst wrote: > Package: devscripts > Version: 2.16.8 > Severity: grave ^ Please read the policy. > at download a new release with uscan the repack failed. > > At the call of debian/repack.sh the parameter $3 is missing: Ok. Please show me your debian/watch file. If you are using uscan with version=4 watch file, $3 should not be there. Please describe exact way for me to reproduce your problem. Osamu
Processed: Re: Bug#841709: [uscan] missing package parameter at call of debian/repack.sh
Processing control commands: > severity -1 normal Bug #841709 [devscripts] [uscan] missing package parameter at call of debian/repack.sh Severity set to 'normal' from 'grave' -- 841709: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841709 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Patch from Ubuntu for the flint-arb PIE FTBFS
Processing control commands: > tags -1 +patch Bug #837454 [src:flint-arb] flint-arb: FTBFS with bindnow and PIE enabled Added tag(s) patch. -- 837454: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837454 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#837454: Patch from Ubuntu for the flint-arb PIE FTBFS
Control: tags -1 +patch The patch I found in Ubuntu for this bug is attached, cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed Description: invoke cc with just -r to fix FTBFS with PIE enabled Author: Logan Rosen Forwarded: no Last-Update: 2016-05-07 --- This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ --- a/Makefile.subdirs +++ b/Makefile.subdirs @@ -52,7 +52,7 @@ $(QUIET_CC) $(CC) $(CFLAGS) $(INCS) -c $< -o $@ -MMD -MP -MF "$(BUILD_DIR)/$(MOD_DIR)_$*.d" -MT "$(BUILD_DIR)/$(MOD_DIR)_$*.d" -MT "$@" $(MOD_LOBJ): $(LOBJS) - $(QUIET_CC) $(CC) $(ABI_FLAG) -Wl,-r $^ -o $@ -nostdlib + $(QUIET_CC) $(CC) $(ABI_FLAG) -r $^ -o $@ -nostdlib -include $(LOBJS:.lo=.d)
Bug#840827: lucene-solr: Network tests are performed using public IP instead of 127.0.0.1
retitle 840827 lucene-solr: Network tests are performed using public IP instead of 127.0.0.1 severity 840827 normal thanks On Mon, Oct 24, 2016 at 05:08:39PM +0200, Emmanuel Bourg wrote: > I got a look at this issue and it seems the failing tests are setting up > a local RMI server but the subsequent connections do not work. > > I don't know why it fails with your machines but if I'm not mistaken > local connections are allowed during the build. > > Is the IP you redacted the one from the machine building the package, or > another machine on your network? Big ooops! Sorry. That was why it failed. Not all my machines have a fixed IP, and I made the mistake of putting the public IP of the day in /etc/hosts instead of 127.0.1.1. I've triggered rebuilds on the machines where it previously failed and now it does not fail, so there is no FTBFS bug anymore. But I have still to "redact" the build logs in case the tests fail. Would not be better to do the tests by connecting to localhost or 127.0.0.1 instead of the machine name? I think this would even simplify the code, as you could use always "localhost" instead of having to guess the real hostname first. Thanks a lot.
Processed: lucene-solr: Network tests are performed using public IP instead of 127.0.0.1
Processing commands for cont...@bugs.debian.org: > retitle 840827 lucene-solr: Network tests are performed using public IP > instead of 127.0.0.1 Bug #840827 [src:lucene-solr] lucene-solr: FTBFS (failing tests, no route to host) Changed Bug title to 'lucene-solr: Network tests are performed using public IP instead of 127.0.0.1' from 'lucene-solr: FTBFS (failing tests, no route to host)'. > severity 840827 normal Bug #840827 [src:lucene-solr] lucene-solr: Network tests are performed using public IP instead of 127.0.0.1 Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 840827: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: nmu: ocamlgraph_1.8.6-1
Processing control commands: > block 837456 by -1 Bug #837456 [src:frama-c] frama-c: FTBFS with bindnow and PIE enabled 837456 was not blocked by any bugs. 837456 was not blocking any bugs. Added blocking bug(s) of 837456: 841939 -- 837456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837456 841939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): ocamlgraph needs PIE binNMU
Processing control commands: > rassagn -1 src:ocamlgraph Unknown command or malformed arguments to command. > affects -1 src:frama-c Bug #837456 [src:frama-c] frama-c: FTBFS with bindnow and PIE enabled Added indication that 837456 affects src:frama-c > retitle -1 ocamlgraph needs PIE binNMU Bug #837456 [src:frama-c] frama-c: FTBFS with bindnow and PIE enabled Changed Bug title to 'ocamlgraph needs PIE binNMU' from 'frama-c: FTBFS with bindnow and PIE enabled'. -- 837456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837456 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#837456: ocamlgraph needs PIE binNMU
Control: rassagn -1 src:ocamlgraph Control: affects -1 src:frama-c Control: retitle -1 ocamlgraph needs PIE binNMU A binNMU is sufficient to fix this, and already requested. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: Mark as forwarded
Processing commands for cont...@bugs.debian.org: > forwarded 837480 https://github.com/constabulary/gb/issues/607 Bug #837480 [src:gb] gb: FTBFS with bindnow and PIE enabled Set Bug forwarded-to-address to 'https://github.com/constabulary/gb/issues/607'. > thanks Stopping processing here. Please contact me if you need assistance. -- 837480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Reassign with correct syntax
Processing commands for cont...@bugs.debian.org: > reassign 837456 src:ocamlgraph Bug #837456 [src:frama-c] ocamlgraph needs PIE binNMU Bug reassigned from package 'src:frama-c' to 'src:ocamlgraph'. No longer marked as found in versions frama-c/20151002+magnesium+dfsg-1. Ignoring request to alter fixed versions of bug #837456 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 837456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837456 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: nmu: mlton_20100608-5.1
Processing control commands: > block 837567 by -1 Bug #837567 [src:mlton] mlton: FTBFS with bindnow and PIE enabled 837567 was not blocked by any bugs. 837567 was not blocking any bugs. Added blocking bug(s) of 837567: 841941 -- 837567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837567 841941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Only a binNMU should be required
Processing control commands: > retitle -1 mlton needs PIE binNMU Bug #837567 [src:mlton] mlton: FTBFS with bindnow and PIE enabled Changed Bug title to 'mlton needs PIE binNMU' from 'mlton: FTBFS with bindnow and PIE enabled'. -- 837567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#837567: Only a binNMU should be required
Control: retitle -1 mlton needs PIE binNMU A binNMU should be sufficient to fix this, and already requested. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#837569: Only a binNMU should be required
Control: retitle -1 psicode needs PIE binNMU A binNMU should be sufficient to fix this, and is already requested. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: nmu: psicode_3.4.0-6
Processing control commands: > block 837569 by -1 Bug #837569 [libpsi3-dev] libpsi3-dev Please build static libraries with -fPIC 837569 was not blocked by any bugs. 837569 was not blocking any bugs. Added blocking bug(s) of 837569: 841942 -- 837569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837569 841942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841721: marked as done (lxqt-l10n: Debian changelog is incomplete)
Your message dated Mon, 24 Oct 2016 17:24:43 + with message-id and subject line Bug#841721: fixed in lxqt-l10n 0.11.0-19-g717bd7e-5 has caused the Debian Bug report #841721, regarding lxqt-l10n: Debian changelog is incomplete to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 841721: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841721 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lxqt-l10n Version: 0.11.0-19-g717bd7e-3 Severity: serious https://tracker.debian.org/media/packages/l/lxqt-l10n/changelog-0.11.0-19-g717bd7e-3 There are versions missing that are part of the history of this version. Please do not ever remove items from the Debian changelog. One effect of this bad practice is that version tracking thinks that #824825 is still present in the version in unstable, which would ensure that your package will not be part of stretch. Please add the missing changelog items (at least 0.11.0-19-g717bd7e-1 and 0.11.0-19-g717bd7e-2) back to the Debian changelog. --- End Message --- --- Begin Message --- Source: lxqt-l10n Source-Version: 0.11.0-19-g717bd7e-5 We believe that the bug you reported is fixed in the latest version of lxqt-l10n, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 841...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alf Gaida (supplier of updated lxqt-l10n package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 24 Oct 2016 18:18:04 +0200 Source: lxqt-l10n Binary: compton-conf-l10n libfm-qt-l10n liblxqt-l10n lximage-qt-l10n lxqt-about-l10n lxqt-admin-l10n lxqt-config-l10n lxqt-globalkeys-l10n lxqt-notificationd-l10n lxqt-openssh-askpass-l10n lxqt-panel-l10n lxqt-policykit-l10n lxqt-powermanagement-l10n lxqt-runner-l10n lxqt-session-l10n lxqt-sudo-l10n obconf-qt-l10n pavucontrol-qt-l10n pcmanfm-qt-l10n qterminal-l10n Architecture: source Version: 0.11.0-19-g717bd7e-5 Distribution: unstable Urgency: medium Maintainer: LXQt Packaging Team Changed-By: Alf Gaida Description: compton-conf-l10n - Language package for compton-conf libfm-qt-l10n - Language package for libfm-qt liblxqt-l10n - Language package for liblxqt lximage-qt-l10n - Language-package for lximage-qt lxqt-about-l10n - Language package for lxqt-about lxqt-admin-l10n - Language package for lxqt-admin lxqt-config-l10n - Language package for lxqt-config lxqt-globalkeys-l10n - Language package for lxqt-globalkeys lxqt-notificationd-l10n - Language package for lxqt-notificationd lxqt-openssh-askpass-l10n - Language package for lxqt-openssh-askpass lxqt-panel-l10n - Language package for lxqt-panel lxqt-policykit-l10n - Language package for lxqt-policykit lxqt-powermanagement-l10n - Language package for lxqt-powermanagement lxqt-runner-l10n - Language package for lxqt-runner lxqt-session-l10n - Language package for lxqt-session lxqt-sudo-l10n - Language package for lxqt-sudo obconf-qt-l10n - Language package for obconf-qt pavucontrol-qt-l10n - Language package for pavucontrol-qt pcmanfm-qt-l10n - Language package for pcmanfm-qt qterminal-l10n - Language package for qterminal Closes: 841721 Changes: lxqt-l10n (0.11.0-19-g717bd7e-5) unstable; urgency=medium . * Really close 841721 ((Closes: #841721) * Follow the multiarch hinter and mark the l10n-packages foreign Checksums-Sha1: 6b89cafe815688fb68d171c87438b7bfa7986fe0 3153 lxqt-l10n_0.11.0-19-g717bd7e-5.dsc 9f9729265a40a7f9c932fb20d691ca3241759cca 6112 lxqt-l10n_0.11.0-19-g717bd7e-5.debian.tar.xz Checksums-Sha256: 1d2b30f166cdef74a64eabd6d8a8cca8b4934bd3f3afe6c8cd2c241ce92d2052 3153 lxqt-l10n_0.11.0-19-g717bd7e-5.dsc 2d34343019fb96e5f42a7430055fbfb002c4991fb436f29e2a12ad359c193581 6112 lxqt-l10n_0.11.0-19-g717bd7e-5.debian.tar.xz Files: 9771d47da62849b681f59ed82f731dc5 3153 utils optional lxqt-l10n_0.11.0-19-g717bd7e-5.dsc ee40ea3402ed1f9593e220de74e0fa55 6112 utils optional lxqt-l10n_0.11.0-19-g717bd7e-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQEcBAEBCgAGBQJYDje8AAoJEM0oCgtNcoJ8g9gH/0LzR9iunVUcyt5YWjLRTlhL tl1aHRmUhMie1Hyn1qO73bfiafqVMv21X3qy8ceIAAEbdzEVujbwTgAnSZT2dEmx p1uT7oPQxoGtKsTZODnI5GhVsC7cONe
Processed: Only a binNMU should be required
Processing control commands: > retitle -1 psicode needs PIE binNMU Bug #837569 [libpsi3-dev] libpsi3-dev Please build static libraries with -fPIC Changed Bug title to 'psicode needs PIE binNMU' from 'libpsi3-dev Please build static libraries with -fPIC'. -- 837569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837569 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package python-pyhsm
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package python-pyhsm > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #834066 (http://bugs.debian.org/834066) > # Bug title: python-pyhsm: ships > /usr/lib/python2.7/dist-packages/test/__init__.py > # * https://github.com/Yubico/python-pyhsm/issues/11 > # * remote status changed: open -> closed > # * closed upstream > tags 834066 + fixed-upstream Bug #834066 [python-pyhsm] python-pyhsm: ships /usr/lib/python2.7/dist-packages/test/__init__.py Added tag(s) fixed-upstream. > usertags 834066 - status-open Usertags were: status-open. Usertags are now: . > usertags 834066 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 834066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Patch from Ubuntu for the sbcl PIE FTBFS
Processing control commands: > tags -1 +patch Bug #837576 [src:sbcl] sbcl: FTBFS with bindnow and PIE enabled Added tag(s) patch. -- 837576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#837576: Patch from Ubuntu for the sbcl PIE FTBFS
Control: tags -1 +patch The patch I found in Ubuntu for this bug is attached, cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed Author: Steve Beattie Subject: make -no-pie arguments consistent with upstream GCC Bug: https://bugs.launchpad.net/ubuntu/+source/sbcl/+bug/1576871 SBCL fails to build when gcc is configure to generate Position Independent Binaries. The runtime configs for SBCL in sbcl/src/runtime/Config.x86-linux and sbcl/src/runtime/Config.x86-64-linux attempt to take this into account via detecting and adding the -nopie flag. However, upstream gcc has standardized on the -no-pie flag (note embedded hyphen): https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/doc/invoke.texi;h=515d948ce710a2fba98c586ea2efa05d4cf60979;hb=HEAD#l10620 as of upstream commit: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=e9abca4f4a48fa8b1fd9778f6a3cd748e099e3bb This causes SBCL to FTBFS in Ubuntu 16.10 on amd64 where -pie is enabled by default in gcc. Signed-off-by: Steve Beattie --- src/runtime/Config.x86-64-linux |6 +++--- src/runtime/Config.x86-linux|6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) Index: b/src/runtime/Config.x86-64-linux === --- a/src/runtime/Config.x86-64-linux +++ b/src/runtime/Config.x86-64-linux @@ -47,10 +47,10 @@ CFLAGS += -fno-omit-frame-pointer GC_SRC = gencgc.c # Hardened GCC enables PIE by default -ifneq ($(shell $(CC) -dumpspecs 2>/dev/null | grep -e nopie),) +ifneq ($(shell $(CC) -dumpspecs 2>/dev/null | grep -e no-pie),) CFLAGS += -fno-pie -LINKFLAGS += -nopie -LDFLAGS += -nopie +LINKFLAGS += -no-pie +LDFLAGS += -no-pie endif # Nothing to do for after-grovel-headers. Index: b/src/runtime/Config.x86-linux === --- a/src/runtime/Config.x86-linux +++ b/src/runtime/Config.x86-linux @@ -43,10 +43,10 @@ ifdef LISP_FEATURE_SB_CORE_COMPRESSION endif # Hardened GCC enables PIE by default -ifneq ($(shell $(CC) -dumpspecs 2>/dev/null | grep -e nopie),) +ifneq ($(shell $(CC) -dumpspecs 2>/dev/null | grep -e no-pie'),) CFLAGS += -fno-pie -LINKFLAGS += -nopie -LDFLAGS += -nopie +LINKFLAGS += -no-pie +LDFLAGS += -no-pie endif GC_SRC = gencgc.c
Bug#841883: linux-image-4.7.0-1-686: cannot boot with 4.7.8-1, stuck at loading initrd
On Mon, 24 Oct 2016 14:14:18 +0800 sharuzzaman wrote: [...] > with previous version of linux-image-4.7.0-1-686, I'm able to boot my laptop > with no issue. > > yesterday, I update the kernel to version 4.7.8-1 from debian repository > using aptitude upgrade, then after reboot, the laptop is not able to boot up > > the screeen just went blank and blinking cursor shown after loading initrd > ramdisk > > I rebooted the laptop and select kernel 4.6, and the laptop boots up just fine > > I have run update-initramfs for kernel 4.7, but still not able to boot after > that > > I also have run aptitude reinstall for kernel 4.7, but still not able to boot > after that > > I'm sure this is not a problem with my laptop, but something is wrong with > the kernel and/or initrd image Hello, I am another user bitten by the same bug on an i386 machine (but everything seems to be fine on amd64 machines). I experience the same exact misbehavior (version 4.7.8-1 fails to boot: stuck while loading initrd); I have tried the same things to no avail. I have currently altered GRUB_DEFAULT in /etc/default/grub, in order to force the machine to automatically boot the previous kernel version (4.6.4-1). I hope the bug may be fixed soon. Thanks to the Debian Kernel Team for any help they may provide. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpnuff9ZAXEH.pgp Description: PGP signature
Bug#811996: Fixing the ptlib FTBFS will also fix the t38modem FTBFS
reassign 811996 src:ptlib reassign 837577 src:ptlib forcemerge 811996 837577 affects 811996 src:t38modem thanks Strictly speaking the ptlib build failure is unrelated to the t38modem build failure, but a ptlib binNMU is not possible due to the ptlib FTBFS, and any new ptlib upload will automatically be built with PIE. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#811068: libgda5: Patch to disable the failing tests
Dear GNOME maintainers: Based on the comments by Andreas in the rygel bug, I could understand your desire to do the "right thing" and fix the failing tests, but it surely would take time and effort, and nobody can really force you to do that. If you decide to disable the tests, I'm attaching a patch to make it easy. I've actually tested it (by diffing build logs), and it does what it says it does. Thanks a lot. diff -Nru libgda5-5.2.4/debian/changelog libgda5-5.2.4/debian/changelog --- libgda5-5.2.4/debian/changelog 2016-09-23 10:22:18.0 +0200 +++ libgda5-5.2.4/debian/changelog 2016-10-24 16:35:54.0 +0200 @@ -1,3 +1,10 @@ +libgda5 (5.2.4-3) unstable; urgency=medium + + * Disable check_data_proxy and check_vcnc, as they fail randomly +and make the package to FTBFS (Closes: #811068, #839444). + + -- Andreas Henriksson Mon, 24 Oct 2016 16:35:54 +0200 + libgda5 (5.2.4-2) unstable; urgency=medium * Team upload. diff -Nru libgda5-5.2.4/debian/patches/disable-randomly-failing-tests.patch libgda5-5.2.4/debian/patches/disable-randomly-failing-tests.patch --- libgda5-5.2.4/debian/patches/disable-randomly-failing-tests.patch 1970-01-01 01:00:00.0 +0100 +++ libgda5-5.2.4/debian/patches/disable-randomly-failing-tests.patch 2016-10-24 16:34:01.0 +0200 @@ -0,0 +1,16 @@ +From: Santiago Vila +Subject: Disable check_data_proxy and check_vcnc, known to fail randomly, until we know why they fail +Bug-Debian: https://bugs.debian.org/811068 +Bug-Debian: https://bugs.debian.org/839444 + +--- libgda5-5.2.4.orig/tests/data-models/Makefile.am libgda5-5.2.4/tests/data-models/Makefile.am +@@ -9,7 +9,7 @@ AM_CPPFLAGS = \ + + TESTS_ENVIRONMENT = GDA_TOP_SRC_DIR="$(abs_top_srcdir)" GDA_TOP_BUILD_DIR="$(abs_top_builddir)" + check_PROGRAMS = check_model_import check_virtual check_data_proxy check_model_copy check_pmodel check_empty_rs check_model_errors check_vcnc check_pivot +-TESTS = check_model_import check_virtual check_data_proxy check_model_copy check_pmodel check_empty_rs check_model_errors check_vcnc check_pivot ++TESTS = check_model_import check_virtual check_model_copy check_pmodel check_empty_rs check_model_errors check_pivot + + common_sources = \ + ../test-errors.h \ diff -Nru libgda5-5.2.4/debian/patches/series libgda5-5.2.4/debian/patches/series --- libgda5-5.2.4/debian/patches/series 2016-09-23 09:56:32.0 +0200 +++ libgda5-5.2.4/debian/patches/series 2016-10-24 16:32:41.0 +0200 @@ -1,2 +1,3 @@ 01-link-sqlite-provider-against-sqlite3.patch Accept-SQLITE_INDEX_CONSTRAINT_LIKE-from-sqlite.patch +disable-randomly-failing-tests.patch
Processed (with 1 error): This is the same bug
Processing commands for cont...@bugs.debian.org: > reassign 837659 src:ocaml Bug #837659 [ocaml-nox] hivex: FTBFS with bindnow and PIE enabled Bug reassigned from package 'ocaml-nox' to 'src:ocaml'. Ignoring request to alter found versions of bug #837659 to the same values previously set Ignoring request to alter fixed versions of bug #837659 to the same values previously set > forcemerge 837359 837659 Bug #837359 [src:ocaml] ocaml needs PIE binNMU Bug #837659 [src:ocaml] hivex: FTBFS with bindnow and PIE enabled 837659 was not blocked by any bugs. 837659 was not blocking any bugs. Added blocking bug(s) of 837659: 841938 837659 was blocked by: 841938 837659 was not blocking any bugs. Added blocking bug(s) of 837659: 837350 Removed indication that 837659 affects src:hivex Added indication that 837659 affects camlp5,ara,ocaml-data-notation,tyxml,js-of-ocaml,ocamlgraph,ocamlmod,ocurl,dose3,ocaml-fileutils,why3,atdgen,ben,ocaml-zarith,ocaml-re,alt-ergo,pcre-ocaml,mingw-ocaml,findlib,supermin,optcomp,ocaml-expect,scilab,marionnet,approx,extlib,sexplib310,misery,variantslib,pagodacf,type-conv,janest-core-extended,camlimages,oasis,caml-crush,ocsigenserver,advi,obus,gmetadom,ocaml-batteries,fieldslib,coccinelle,jsonm,lambda-term,laby,ocaml-sqlite3,janest-core-kernel,janest-core,nss-passwords,ocaml-sqlexpr,ocamlgsl,virt-top,camomile,ocaml-textutils,orpie,cryptokit,enumerate,libguestfs,cppo,omake,ocamldsort,ocaml-base64,ocamlnet,mtasc,ocaml-csv,ppx-sexp-conv,confluence,camlmix,postgresql-ocaml,pipebang,yojson,uuidm,utop,monotone-viz,coinst,spamoracle,xml-light,custom-printf,xmlm,coq,ocamlcreal,ocamlrss,pdfsandwich,biniou,comparelib,botch,pa-test,ocaml-estring,menhir,wyrd,ocaml-res,galax,ocaml-gettext,pa-ounit,ocaml-benchmark,ocaml-ipaddr,cduce,pa-bench,ocaml-atd,ppx-core,ocaml-extunix,ocaml-melt,mlgmp,liquidsoap,pa-structural-sexp,haxe,zed,ppx-type-conv,ocaml-reins,ocaml-re2,freetennis,kalzium,opam,ocamlviz,herelib,ocamlbricks,ocp-indent,ocaml-libvirt,typerep,js-build-tools,mlpost,perl4caml,cudf,unison,ppx-driver,prooftree,eliom,ocaml-deriving-ocsigen,matita,ounit,caml2html,geneweb,pgocaml,ppx-optcomp,dochelp,ocaml-usb,ppx-deriving,bin-prot Marked as found in versions ocaml/4.02.3-7. Bug #837659 [src:ocaml] hivex: FTBFS with bindnow and PIE enabled Unable to complete merge on previous attempt; trying again (retry: 2) Bug #837659 [src:ocaml] hivex: FTBFS with bindnow and PIE enabled Unable to complete merge on previous attempt; trying again (retry: 3) Bug #837659 [src:ocaml] hivex: FTBFS with bindnow and PIE enabled After four attempts, the following changes were unable to be made: blockedby of #837659 is '841938 837350' not '837350 841938' Failed to forcibly merge 837359: Unable to modify bugs so they could be merged. > affects 837359 src:hivex Bug #837359 [src:ocaml] ocaml needs PIE binNMU Added indication that 837359 affects src:hivex > thanks Stopping processing here. Please contact me if you need assistance. -- 837359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837359 837659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837659 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 841741 grave Bug #841741 [grub-common] grub-probe fails to find GRUB drive Severity set to 'grave' from 'normal' > retitle 841741 grub-probe fails to find GRUB drive, makes system unbootable Bug #841741 [grub-common] grub-probe fails to find GRUB drive Changed Bug title to 'grub-probe fails to find GRUB drive, makes system unbootable' from 'grub-probe fails to find GRUB drive'. > End of message, stopping processing here. Please contact me if you need assistance. -- 841741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841741 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#806107: marked as done (signond: FTBFS when built with dpkg-buildpackage -A (No such file or directory))
Your message dated Mon, 24 Oct 2016 18:04:49 + with message-id and subject line Bug#806107: fixed in signond 8.59-1 has caused the Debian Bug report #806107, regarding signond: FTBFS when built with dpkg-buildpackage -A (No such file or directory) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 806107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:signond Version: 8.57+20150423-3 User: sanv...@debian.org Usertags: binary-indep Severity: important Dear maintainer: I tried to build this package with "dpkg-buildpackage -A" (i.e. only architecture-independent packages), and it failed: [...] fakeroot debian/rules binary-indep /usr/bin/make -f debian/rules dhmk_run_build-indep_commands DHMK_TARGET="build-indep" make[1]: Entering directory '/<>/signond-8.57+20150423' dh_testdir # [-i] # Running override target (override_dh_auto_build) test -z "`ls debian/*.debhelper.log 2>/dev/null`" || sed -i '/^override_dh_auto_build[[:space:]]/d' debian/*.debhelper.log /usr/bin/make -f debian/rules override_dh_auto_build DH_INTERNAL_OVERRIDE="dh_auto_build" # [-i] make[2]: Entering directory '/<>/signond-8.57+20150423' QT_SELECT=qt4 dh_auto_build -Bbuild/qt4 make -j1 make[3]: Entering directory '/<>/signond-8.57+20150423/build/qt4' cd lib/ && make -f Makefile make[4]: Entering directory '/<>/signond-8.57+20150423/build/qt4/lib' cd signond/ && make -f Makefile make[5]: Entering directory '/<>/signond-8.57+20150423/build/qt4/lib/signond' cd SignOn/ && make -f Makefile make[6]: Entering directory '/<>/signond-8.57+20150423/build/qt4/lib/signond/SignOn' make -f Makefile.SignOnExtension make[7]: Entering directory '/<>/signond-8.57+20150423/build/qt4/lib/signond/SignOn' make[7]: Nothing to be done for 'first'. make[7]: Leaving directory '/<>/signond-8.57+20150423/build/qt4/lib/signond/SignOn' make[6]: Leaving directory '/<>/signond-8.57+20150423/build/qt4/lib/signond/SignOn' [... snipped ...] dh_auto_install -Bbuild/qt4 -plibsignon-qt-dev dh_auto_install: No packages to build. mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake/SignOnQt debian/tmp/usr/lib/x86_64-linux-gnu/cmake/SignOnQt4 mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/cmake/SignOnQt': No such file or directory debian/rules:39: recipe for target 'override_dh_auto_install' failed make[2]: *** [override_dh_auto_install] Error 1 make[2]: Leaving directory '/<>/signond-8.57+20150423' /usr/share/pkg-kde-tools/qt-kde-team/2/dhmk.mk:97: recipe for target 'pre_install-indep_dh_auto_install' failed make[1]: *** [pre_install-indep_dh_auto_install] Error 2 make[1]: Leaving directory '/<>/signond-8.57+20150423' /usr/share/pkg-kde-tools/qt-kde-team/2/dhmk.mk:110: recipe for target 'debian/dhmk_install-indep' failed make: *** [debian/dhmk_install-indep] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit status 2 Sorry not to have a fix, as I am reporting many bugs similar to this one, but I can give some general hints: * If all the arch-independent packages are dummy transitional packages released with jessie, the easy fix is to drop them now. * If not, debian/rules should be modified so that the binary-indep target works in all cases, even when binary-arch is not used (this is what the "Architecture: all" autobuilder does). For that: * If you are using debhelper, you might want to use options -a and -i for dh_* commands so that they do not act on packages they do not have to act. * Also, if you are using dh, the (independently) optional targets override_dh_foo-arch and override_dh_foo-indep (for several values of "foo") may be useful to write a debian/rules which behaves exactly as desired. After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work properly, this package will be suitable to be uploaded in source-only form if you wish (you might want to try it). Thanks. --- End Message --- --- Begin Message --- Source: signond Source-Version: 8.59-1 We believe that the bug you reported is fixed in the latest version of signond, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 806...@bugs.debian.org, and the maintainer will reopen
Processed: nmu: libint_1.1.6-2
Processing control commands: > block 837686 by -1 Bug #837686 [libint-dev] libint-dev: Please build static libraries with -fPIC 837686 was not blocked by any bugs. 837686 was not blocking any bugs. Added blocking bug(s) of 837686: 841946 -- 837686: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837686 841946: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841946 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841947: libboost-*1.61-dev: Please build static libs with -fPIC
Source: boost1.61 Version: 1.61.0+dfsg-3 Severity: serious Justification: make other packages FTBFS -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, When rebuilding the psi4 package on amd6', it FTBFS with: [100%] Linking CXX executable ../../../bin/psi4 cd /<>/builddir/src/bin/psi4 && /usr/bin/cmake -E cmake_link_script CMakeFiles/psi4.dir/link.txt --verbose=1 /usr/bin/c++ -DRESTRICT=__restrict__ -Xlinker -export-dynamic -fPIC -std=c++11 -fopenmp -O2 -g -DNDEBUG CMakeFiles/psi4_objlib.dir/export_psio.cc.o CMakeFiles/psi4_objlib.dir/export_mints.cc.o CMakeFiles/psi4_objlib.dir/psi_stop.cc.o CMakeFiles/psi4_objlib.dir/export_functional.cc.o CMakeFiles/psi4_objlib.dir/export_oeprop.cc.o CMakeFiles/psi4_objlib.dir/export_plugins.cc.o CMakeFiles/psi4_objlib.dir/export_blas_lapack.cc.o CMakeFiles/psi4_objlib.dir/export_benchmarks.cc.o CMakeFiles/psi4_objlib.dir/export_efp.cc.o CMakeFiles/psi4_objlib.dir/export_cubeprop.cc.o CMakeFiles/psi4_objlib.dir/clean.cc.o CMakeFiles/psi4_objlib.dir/create_new_plugin.cc.o CMakeFiles/psi4_objlib.dir/script.cc.o CMakeFiles/psi4_objlib.dir/set_memory.cc.o CMakeFiles/psi4_objlib.dir/read_options.cc.o CMakeFiles/psi4_objlib.dir/export_libparallel.cc.o CMakeFiles/versioned_code.dir/version.cc.o CMakeFiles/versioned_code.dir/python.cc.o CMakeFiles/versioned_code.dir/psi_start.cc.o CMakeFiles/versioned_code.dir /psi4.cc.o -o ../../../bin/psi4 -rdynamic -lutil -lm -lrt -ldl -lpython2.7 -Wl,--whole-archive ../../../lib/libadc.a ../../../lib/libccdensity.a ../../../lib/libccenergy.a ../../../lib/libcceom.a ../../../lib/libcchbar.a ../../../lib/libcclambda.a ../../../lib/libccresponse.a ../../../lib/libccsort.a ../../../lib/libcctransort.a ../../../lib/libcctriples.a ../../../lib/libdcft.a ../../../lib/libdetci.a ../../../lib/libdfmp2.a ../../../lib/libdfocc.a ../../../lib/libefp.a ../../../lib/libfindif.a ../../../lib/libfisapt.a ../../../lib/libfnocc.a ../../../lib/libmcscf.a ../../../lib/libmints_wrapper.a ../../../lib/libmrcc.a ../../../lib/libocc.a ../../../lib/liboptking.a ../../../lib/libpsimrcc.a ../../../lib/libsapt.a ../../../lib/libscf.a ../../../lib/libscfgrad.a ../../../lib/libthermo.a ../../../lib/libtransqt2.a ../../../lib/libdmrg.a ../../../lib/lib3index.a ../../../lib/libciomr.a ../../../lib/libdiis.a ../../../lib/libdisp.a ../../../lib/libdpd.a ../../../lib/libefp_solver.a . ./../../lib/libfock.a ../../../lib/libfunctional.a -Wl,--whole-archive ../../../lib/libiwl.a -Wl,--no-whole-archive ../../../lib/libmints.a ../../../lib/libmoinfo.a ../../../lib/liboptions.a ../../../lib/libparallel.a ../../../lib/libparallel2.a ../../../lib/libplugin.a ../../../lib/libsapt_solver.a ../../../lib/libscf_solver.a ../../../lib/libthce.a ../../../lib/libtrans.a ../../../lib/libpsi4util.a ../../../lib/libpsio.a ../../../lib/libPsiUtil.a ../../../lib/libqt.a ../../../lib/libcubeprop.a ../../../lib/libinterface_libefp.a -Wl,--no-whole-archive -Wl,-Bstatic -lboost_filesystem -lboost_python -lboost_regex -lboost_serialization -lboost_system -lboost_timer -lboost_chrono -lboost_thread -lboost_date_time -lboost_atomic -Wl,-Bdynamic -lpthread -llapack -lblas -lpython2.7 -lblas -llapack -lint -lderiv -lutil -ldl -lrt -lm /usr/lib/x86_64-linux-gnu/libchemps2.so -lchemps2 /usr/lib/x86_64-linux-gnu/hdf5/serial/lib/libhdf5.so -lsz -lz -lpthread -lm -lpython2.7 -ldl -Wl,-rpath,/usr/l ib/x86_64-linux-gnu/hdf5/serial/lib /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_filesystem.a(operations.o): relocation R_X86_64_32S against symbol `_ZN5boost6detail15sp_counted_base7destroyEv' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_filesystem.a(path.o): relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python.a(list.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python.a(dict.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python.a(tuple.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python.a(str.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python.a(from_python.o): relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a shared object; re
Processed: Only a binNMU should be required
Processing control commands: > retitle -1 libint needs PIE binNMU Bug #837686 [libint-dev] libint-dev: Please build static libraries with -fPIC Changed Bug title to 'libint needs PIE binNMU' from 'libint-dev: Please build static libraries with -fPIC'. -- 837686: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837686 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
