Bug#766795: afterstep binnmu related issues
On 2015-01-09 23:22, Robert Luberda wrote:
Niels Thykier writes:
[...]
* The maintainer of the afterstep package blamed debhelper and
reassigned and merged my bug.
Yes, as there were no such problems with the first binNMU of afterstep
(2.2.12+b1), the conclusion was quite obvious to me: it was debhelper
that caused the afterstep's installation failure by introducing
backward-incompatible change.
I strongly suspect the change that you consider backwards incompatible
would be this one:
https://anonscm.debian.org/cgit/debhelper/debhelper.git/commit/?id=f7324fa4c4fd41f8727e74bc0d5ef40b624ce878
dh_installdocs: When doc dirs are symlinked make the dependency
versioned per policy. Closes: #676777
Prior to that commit, debhelper would make unversioned dependencies,
which are not policy compliant.
For reference, the version chosen back then does have its issues. In
the first upload for stretch debhelper will be using ${binary:Version}
instead. See #747141.
[...]
* jcristau (who I assume was wearing a release team hat) declared that
this workaround was unacceptable and that the package must be fixed to
not use link-doc between arch dependent and arch independent packages.
The afterstep maintainer did not appear to respond to this.
Yes, sorry, I must have missed the mail of Julien. I've just read it on
BTS web page, and noticed that it does contain no explanation why the
work-around was unacceptable. Please note that the issue had came up a
week or so before the freeze, and in my opinion implementing the
work-around was the best action I could take at that moment.
... while keeping --link-doc. For reference, we are debating a disk
cost of 1.3Mb right now.
* the debehlper maintainers declared that link-doc between arch any and
arch all packages was unsupported and took steps to explicitly block
such binnmus.
As I explained above (2.2.12+b1 case) debhelper actually used to support
this.
No, it made dependencies that were not compliant. You happened to have
a additional dependency that mostly covered the issue.
* There were some problems with the blocking code and it was reverted.
Was the change that broke backward compatibility (the one which touches
${misc:Depends}) reverted as well?
No, that cannot be reverted as it would break policy compliance. It was
altered to use ${binary:Version} instead - but it will not help your case.
Indeed. Note that the blocking code is still enabled for compat 10
and debhelper will emit warnings at compat 9 (and earlier) when using
--link-doc between arch:all and arch:any pacakges. The only reason for
not completely rejecting them now is that too many packages are using
them (incorrectly) already now and binNMUs are not frequent enough to
warrant that many FTBFS now.
Please correct me if I'm wrong, but this all means that those `too many
packages' that depend on previous behaviour of debhelper cannot be
safely binNMU-ed in jessie.
Yes. Note that the bug was tagged jessie-ignore (until it was umerged
and ping-pong'ed between afterstep and debhelper).
In theory it might happen that e.g. security
upgrade of some package will require rebuild of all it dependencies, I
guess.
If that happens they can be manually uploaded to fix the issue. That
said, it is unlikely for Debian to accept such changes in stable
releases, since binNMUs are most often used for ABI changes - a thing
not done lightly in a stable release.
I believe it is an RC bug in afterstep that does not comply with the
policy.
I disagree it does not comply with the policy, see my other mails for
reasoning.
Robert seems to disagree having reassigned this back to
debhelper, reopened #766711 and opened #767839.
It was Peter who reopened 767839, re-assigning was done by me.
I said you reopened #766711, not #767839, and reassigned #767839 back to
debhelper. Right now debhelper has both #766711 and #767839 - it is not
clear to be that they are distinct bugs. I will probably merge this one
into the other.
thanks to the work-around afterstep *is* currently binNMU safe.
However this is
only `work-around', which means that even me is not fully glad of this
solution, and I promise to fix it one way or another for jessie+1.
Regards,
Robert
Ok.
~Niels
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775044: openjdk-7: FTBFS: java.lang.RuntimeException: time is more than 10 years from present: 1104530400000
Source: openjdk-7 Version: 7u71-2.5.3-2 Severity: serious From my pbuilder build log (on amd64): ... rm -f /tmp/buildd/openjdk-7-7u71-2.5.3/build/openjdk.build-boot/lib/currency.data /tmp/buildd/openjdk-7-7u71-2.5.3/build/bootstrap/jdk1.6.0/bin/java -XX:-PrintVMOptions -XX:+UnlockDiagnosticVMOptions -XX:-LogVMOutput -Xmx512m -Xms512m -XX:PermSize=32m -XX:MaxPermSize=160m -jar /tmp/buildd/openjdk-7-7u71-2.5.3/build/openjdk.build-boot/btjars/generatecurrencydata.jar -o /tmp/buildd/openjdk-7-7u71-2.5.3/build/openjdk.build-boot/lib/currency.data.temp \ ../../../src/share/classes/java/util/CurrencyData.properties Error: time is more than 10 years from present: 110453040 java.lang.RuntimeException: time is more than 10 years from present: 110453040 at build.tools.generatecurrencydata.GenerateCurrencyData.makeSpecialCaseEntry(GenerateCurrencyData.java:285) at build.tools.generatecurrencydata.GenerateCurrencyData.buildMainAndSpecialCaseTables(GenerateCurrencyData.java:225) at build.tools.generatecurrencydata.GenerateCurrencyData.main(GenerateCurrencyData.java:154) Makefile:345: recipe for target '/tmp/buildd/openjdk-7-7u71-2.5.3/build/openjdk.build-boot/lib/currency.data' failed make[6]: *** [/tmp/buildd/openjdk-7-7u71-2.5.3/build/openjdk.build-boot/lib/currency.data] Error 1 make[6]: Leaving directory '/tmp/buildd/openjdk-7-7u71-2.5.3/build/openjdk-boot/jdk/make/java/java' Makefile:63: recipe for target 'all' failed make[5]: *** [all] Error 1 make[5]: Leaving directory '/tmp/buildd/openjdk-7-7u71-2.5.3/build/openjdk-boot/jdk/make/java' Makefile:253: recipe for target 'all' failed make[4]: *** [all] Error 1 make[4]: Leaving directory '/tmp/buildd/openjdk-7-7u71-2.5.3/build/openjdk-boot/jdk/make' make/jdk-rules.gmk:92: recipe for target 'jdk-build' failed make[3]: *** [jdk-build] Error 2 make[3]: Leaving directory '/tmp/buildd/openjdk-7-7u71-2.5.3/build/openjdk-boot' Makefile:251: recipe for target 'build_product_image' failed make[2]: *** [build_product_image] Error 2 make[2]: Leaving directory '/tmp/buildd/openjdk-7-7u71-2.5.3/build/openjdk-boot' Makefile:2301: recipe for target 'stamps/icedtea-boot.stamp' failed make[1]: *** [stamps/icedtea-boot.stamp] Error 2 make[1]: Leaving directory '/tmp/buildd/openjdk-7-7u71-2.5.3/build' debian/rules:1308: recipe for target 'stamps/build' failed make: *** [stamps/build] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 (If I divide that number by 1000, it becomes Fri Dec 31 22:00:00 UTC 2004. So I'm not sure where the number comes from, but it appears to be off by a factor of 1000.) -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774788: [PKG-Openstack-devel] Bug#774788: neutron-metadata-agent overwrites config on update
Hi Thomas
I currently not able to imagine where it reads the config file. (Sorry
;(). Especially I cannot understand why it does eg not change the region
which seems to me like equivalent configured.
The values are read from within the pkgos_read_admin_creds function of
openstack-pkg-tools. The function is called this way in the
debian/neutron-metadata-agent.config.in:
pkgos_read_admin_creds ${META_AGNT_CONF} DEFAULT neutron-metadata
Ok I found this one. the function pkgos_read_admin_creds() in postinst
script is never run. instead the one in config is used.
(Probably we should delete the
pkgos_read_admin_creds() definition in postinst, since it is never used
there.)
Anyway. I understood the function itself.
And I found the bug !
The function looks for the config parameter
auth_host, which is not defined in metadata_agent.ini (it is in
neutron.conf)
It then overwrites the auth_url parameter.
But actually it should look first at auth_url, extract auth_host from
there and then write auth_url again.
If I define auth_host in metadata_agent.ini file, you're script seems to
work (this is a workaround for the problem).
But according to openstack code auth_host is not a defined configuration
option in metadata_agent.ini file.
I can imagine the following solutions:
- rewrite pkgos_read_admin_creds() to use auth_url values (and this
without braking other invocations of this function !)
- define pkgos_read_admin_creds_metadata_only() function as a
replacement in metadata-agent.
- introduce debconf neutron-metadata/auth_url and remove
neutron-metadata/auth_host and change the scripts accordingly.
I'm currently not capable of implementing any of these three solutions.
Any other ideas ?
Cheers
Benedikt Trefzer
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775022: Important security update
Package: openssl Version: 1.0.1e-2+deb7u13 Severity: critical There is currently a really important security update out [0]. Please provide Debian stable with this security fix. The most important fixes (although the developers tagged them as low severity) are: - CVE-2014-3572 - CVE-2015-0204 - CVE-2015-0205 As this are candidates to completely weaken the encrypted connections that should be fixed pretty soon. Again to say, the developers are absolutely wrong with the severity. This bugs have a critical severity! [0] https://www.openssl.org/news/secadv_20150108.txt -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to de_DE) Shell: /bin/sh linked to /bin/dash Versions of packages openssl depends on: ii libc62.13-38+deb7u6 ii libssl1.0.0 1.0.1e-2+deb7u13 ii zlib1g 1:1.2.7.dfsg-13 openssl recommends no packages. Versions of packages openssl suggests: ii ca-certificates 20130119+deb7u1 -- Configuration Files: /etc/ssl/openssl.cnf changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764162: Regression with kernel 3.16.7-ckt2-1
On Sat, 2015-01-03 at 09:54 -0200, Rogério Brito wrote: [...] Thanks for the info. Since I can't reproduce it would be useful if you could take this issue to the upstream developers who were involved in the original bug report and work with them directly to find a cure. I may try, but I am not confident that I will have any success. :( The upstream kirkwood maintainers are very responsive and helpful IME. (NB: I'm not asking you to fix the issue yourself, but rather to work directly with those who can instead of having me act as a middleman) Ian. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774917: [Pkg-nagios-devel] Bug#774917: icinga-idoutils: fails to upgrade squeeze - wheezy - jessie: ERROR: syntax error at or near EXISTS LINE 1: ALTER TABLE icinga_comments DROP CONSTRAINT IF
On Sat, 10 Jan 2015, Andrey Rahmatullin wrote: On Fri, Jan 09, 2015 at 03:39:51AM +0100, Andreas Beckmann wrote: error encountered processing /usr/share/dbconfig-common/data/icinga-idoutils/upgrade/pgsql/1.10.1-1: ERROR: syntax error at or near EXISTS LINE 1: ALTER TABLE icinga_comments DROP CONSTRAINT IF EXISTS uq_com... ^ DROP CONSTRAINT IF EXISTS was added in PostgreSQL 9.0, which version is used on the machine? probably the 8.4 from squeeze. The package doesn't support a direct update from squeeze without updating the postgresql version. And tbh I don't think we should support that. We shouldn't expect outdated database versions. Any other oppinions? Alex pgp7iQfKxzkuT.pgp Description: PGP signature
Bug#770864: marked as done (rails-timeago does not ship any assets)
Your message dated Sat, 10 Jan 2015 12:04:24 + with message-id e1y9umg-0005mq...@franck.debian.org and subject line Bug#770864: fixed in ruby-rails-timeago 2.11.1-2 has caused the Debian Bug report #770864, regarding rails-timeago does not ship any assets 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.) -- 770864: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770864 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: ruby-rails-timeago version: 2.11.1-1 severity: grave ** Execute assets:precompile rake aborted! Sprockets::FileNotFound: couldn't find file 'rails-timeago' signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- Source: ruby-rails-timeago Source-Version: 2.11.1-2 We believe that the bug you reported is fixed in the latest version of ruby-rails-timeago, 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 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen prav...@debian.org (supplier of updated ruby-rails-timeago 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: Sat, 10 Jan 2015 15:12:51 +0530 Source: ruby-rails-timeago Binary: ruby-rails-timeago Architecture: source all Version: 2.11.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Pirate Praveen prav...@debian.org Description: ruby-rails-timeago - Rails Helper to create time tags usable for jQuery Timeago plugin Closes: 770864 Changes: ruby-rails-timeago (2.11.1-2) unstable; urgency=medium . * Copy lib/assets to /usr/share (Closes: #770864) * Bump standards version to 3.9.6 (no changes) * Add ruby-rspec to test depends * Add a simple load test Checksums-Sha1: feffb06c37e121d652cd926f35366047eff8759b 2243 ruby-rails-timeago_2.11.1-2.dsc 49b6016ae4edee08f9646c197e6de51b65a23509 2832 ruby-rails-timeago_2.11.1-2.debian.tar.xz 9bf8effb8c2ee0d7b8985b9c9d6e6d1e6de3c963 15996 ruby-rails-timeago_2.11.1-2_all.deb Checksums-Sha256: d05a068c1b6e1d4818f85c07a2f101a577354f96d5aeb3dcb975281b222bcb9d 2243 ruby-rails-timeago_2.11.1-2.dsc 115bdc056e832873bac6a7ae83b5e28b677ab7a66a414a225daef79361d2dd50 2832 ruby-rails-timeago_2.11.1-2.debian.tar.xz 44369f5e4e4a848c5e5ae30bde70521491a13cafbeac5672ecb666291adc5f8a 15996 ruby-rails-timeago_2.11.1-2_all.deb Files: 024694c11799d3c310e73a868d54d77b 2243 ruby optional ruby-rails-timeago_2.11.1-2.dsc e1e5802baef055572a8c219cdc5cd224 2832 ruby optional ruby-rails-timeago_2.11.1-2.debian.tar.xz a83196f583c942ebe05c46e3e776697d 15996 ruby optional ruby-rails-timeago_2.11.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUsPRdAAoJEM4fnGdFEsIqkRQP/1HK8u/6I66gBFN7pnVKlpjw y5lmuLxsQvElm8EXo/7SVeAtVkVnAKgKqs85g4hx/zzG0YYg7v7yCWRLDlazan5o UGEbv4Beg2VMNkdWZgiwpk0rNJ98v4tHaMpKxQMK9DNmrBTKg0rMvtbIJghTgm91 rcu/fdFwxhbG8KhcAM5r0yfhPZ+fzJN1g2azkUXoGVH949xdmMhBe1SdztcCPCG2 MNZcALPfz1N3R/wg+wZjVW81x5TZfZA10qPNdqP1lh9IorwV+8+3jCYWB+sh59H1 fQzgbsoF2nUuIEnMVICkYQdWyYf9k6Z8BWQiC0xPRuFhpNA9p8hIxPQBnZ+AxiYE sNtIGiyDxkpzU1817Q6lLSi0bSvpMrj9PqvUzJ8CQycaavfvSNkshfYS/FAEonyo OXUpUoie0rn4n46UeDFbFzUc4aY+tCXrWrRLMP7dt1MFLadNNj8w5Pe1PDIV2knA kOwiZ64GK5g5K2NAJpXBJDqhabTseaN64gppM5tR3a+BO+b75rYxelSROOk/u8/1 MuiW3+9ErdL5POEEiBEwwZk5Dm4tFk+XUhzbhP7bkq/G5DxHOmAhSJFsLb42ubVd 6HlcgyKJUIRyrO5+FgeEquxYEtyTlr50gxQf3OG7baT6xAfRtLqoTR/pi0DuT60u mGH7RqePkOgHW309Sqk1 =LuSH -END PGP SIGNATUREEnd Message---
Bug#707831: UUID detection code broken, wrongly uses UUID
This bug affects wheezy as well. I just had trouble booting a wheezy system after adding a second Physical Volume to my LVM setup. The workaround is setting GRUB_DISABLE_LINUX_UUID=true in /etc/default/grub That will make boot again as it will use the root=/dev/mapper/nameofrootlv for the kernel cmdline in /boot/grub/grub.cfg I'm still getting those errors when doing an update-grub: physical volume pv0 not found (many of them) Not using the workaround in advance will kill remote servers, if you don't have access to a KVM console, spice or anything to fix the kernel cmdline in grub's boot menu manually, though. The machine affected is a KVM/quemu VM instance. That machine is using virtio disks, thus I'm having /dev/vda, /dev/vdb and so on. I've noticed that udev does not generate devices nodes for virtio disks in /dev/disk/by-id nor /dev/disk/by-uuid . Perhaps this is why grub is having trouble finding those disks. Additionally, this might be a corner case when one is using a complete unpartitioned disk as LVM Physical Volume, as the second PV I've added to the system is an unpartitioned virtio disk. Strangely enough, on another KVM/qemu VM running unstable (acutally running on the same host as the wheezy VM), but having a similar virtio disk setup, everything is fine. I'm seeing the virtio disk nodes in /dev/disk/by-id and grub is not complaining about not having found PVs, either. I'd likt to ask to re-open this bug, as this still affects wheezy. I'd kindly request a fix backported to wheezy, as well. Thank you. Regards, Dominik Bódi signature.asc Description: OpenPGP digital signature
Bug#775027: crashes with utf-8 (fixed upstream)
Package: irker Severity: serious Please upgrade to 2.12, it fixes important UTF-8 issues making irker crash. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: apport: FTBFS on arch-only builds
Processing control commands: found -1 apport/2.14.2-2 Bug #775034 [src:apport] apport: FTBFS on arch-only builds Marked as found in versions apport/2.14.2-2. -- 775034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775034: apport: FTBFS on arch-only builds
Source: apport Version: 2.15.1-1 Severity: serious Tags: patch Justification: fails to build from source Control: found -1 apport/2.14.2-2 Hi, apport fails to build in arch-only builds (debian/rules build-arch), as done e.g. on buildds [1]. This happens because python(3)-distutils and python(3)-apt seem to be mandatory when building, and they are pulled as Build-Depends-Indep, so not when doing arch-only builds. Furthermore, the dh_install override edits files of arch:all binaries, which are not available in arch-only builds. The attached patch fixes these issues: - python-distutils-extra, python-apt, python3-distutils-extra, and python3-apt are now Build-Depends - apport-retrace and apport-kde are edited only when building their binaries [1] https://buildd.debian.org/status/logs.php?pkg=apportver=2.15.1-1 Thanks, -- Pino --- a/debian/control +++ b/debian/control @@ -9,11 +9,12 @@ Build-Depends: debhelper (= 7.0.50~), net-tools, xauth, python-all, - python3-all -Build-Depends-Indep: python-distutils-extra (= 2.24~), - python3-distutils-extra (= 2.24~), + python3-all, + python-distutils-extra (= 2.24~), python-apt (= 0.7.9), + python3-distutils-extra (= 2.24~), python3-apt (= 0.7.9), +Build-Depends-Indep: intltool, xvfb, python-mock, --- a/debian/rules +++ b/debian/rules @@ -34,12 +34,16 @@ override_dh_install: dh_install -X.pyc -X.egg-info --list-missing pod2man -c Debhelper -r $(DEB_VERSION) debian/debhelper/dh_apport debian/debhelper/dh_apport.1 +ifneq (, $(filter apport-retrace, $(shell dh_listpackages))) # apport-retrace needs python-launchpadlib, which is not yet available # # for Python 3; so switch back to Python 2 sed -i '1 s/python3.*$$/python/' debian/apport-retrace/usr/bin/apport-retrace +endif +ifneq (, $(filter apport-kde, $(shell dh_listpackages))) # Same applies for KDE4... sed -i '1 s/python3.*$$/python/' debian/apport-kde/usr/share/apport/apport-kde +endif override_dh_python3: dh_python3 --skip-private
Bug#722465: marked as done (qtsmbstatus-server: fails to install due to insserv rejecting the script header)
Your message dated Sat, 10 Jan 2015 16:18:35 + with message-id e1y9ykf-00050e...@franck.debian.org and subject line Bug#722465: fixed in qtsmbstatus 2.2.1-3 has caused the Debian Bug report #722465, regarding qtsmbstatus-server: fails to install due to insserv rejecting the script header 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.) -- 722465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: qtsmbstatus-server Version: 2.2.1-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install due to insserv rejecting the script header. Some notes are available from at http://wiki.debian.org/LSBInitScripts From the attached log (scroll to the bottom...): Selecting previously unselected package qtsmbstatus-server. (Reading database ... 8866 files and directories currently installed.) Unpacking qtsmbstatus-server (from .../qtsmbstatus-server_2.2.1-2_amd64.deb) ... Setting up qtsmbstatus-server (2.2.1-2) ... insserv: Service samba has to be enabled to start service qtsmbstatusd insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing qtsmbstatus-server (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: qtsmbstatus-server This problem was observed during an install test in jessie. cheers, Andreas qtsmbstatus-server_2.2.1-2.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: qtsmbstatus Source-Version: 2.2.1-3 We believe that the bug you reported is fixed in the latest version of qtsmbstatus, 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 722...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann a...@debian.org (supplier of updated qtsmbstatus 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: Sat, 10 Jan 2015 16:44:03 +0100 Source: qtsmbstatus Binary: qtsmbstatus-language qtsmbstatus-light qtsmbstatus-client qtsmbstatus-server Architecture: source all Version: 2.2.1-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Andreas Beckmann a...@debian.org Description: qtsmbstatus-client - GUI (graphical user interface) for smbstatus (client) qtsmbstatus-language - QtSmbstatus languages package qtsmbstatus-light - GUI (graphical user interface) for smbstatus qtsmbstatus-server - GUI (graphical user interface) for smbstatus (server) Closes: 722465 Changes: qtsmbstatus (2.2.1-3) unstable; urgency=medium . * QA upload. * Switch qtsmbstatusd.init from 'Required-Start: samba' to 'Should-Start: smbd samba-ad-dc' to restore installability with current samba packages. No warranty that qtsmbstatusd is working properly! (Closes: #722465) * Update Vcs-* URLs. * Switch to debhelper compat level 9. * Switch to copyright-format 1.0. Checksums-Sha1: 773f7e54a48f1e6d17e42122f9be7e84e62a373e 2099 qtsmbstatus_2.2.1-3.dsc 516fa5c41d22ff2b0cb5b5764b0b77beff32d92d 4632 qtsmbstatus_2.2.1-3.debian.tar.xz 91027618ea486425f90ed801c405a03c46f1de89 27044 qtsmbstatus-language_2.2.1-3_all.deb Checksums-Sha256: c3bea69e09a7b8e9873e610bece641103a897e4743dea942a1cb5eaea1310343 2099 qtsmbstatus_2.2.1-3.dsc c3241cf0b416d6d0794dbe050df071b1ce3c69d30a002843326cd8793f6ced90 4632 qtsmbstatus_2.2.1-3.debian.tar.xz 9c303e3f93ac9eb8baaa82485ab38426f645a2ab22f67bcaa509925dd42c28f5 27044 qtsmbstatus-language_2.2.1-3_all.deb Files: 09149a34cc88bfb3af86f336b279376e 2099 net optional qtsmbstatus_2.2.1-3.dsc ee85c2101a7e9d77ca79c666357541a2 4632 net optional qtsmbstatus_2.2.1-3.debian.tar.xz cafcaa1d730209455521a711026bd770 27044 net optional qtsmbstatus-language_2.2.1-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUsUnPAAoJEF+zP5NZ6e0IBF8P/iYfst0Hex5iOZ0YaT6YL1hv +S06Mp3Tb8dBCM1rb085whyUq6URh6XrBFzpAAYNsdNfA17I4BB7HMXykZgX1y19
Bug#774924: apt: Jessie version cannot find upgrade path (but Wheezy version can)
Control: found -1 0.9.16
Control: tags -1 patch
On Fri, Jan 09, 2015 at 04:00:10PM +0100, David Kalnischkies wrote:
In the meantime, I hopefully figure out what is the meaningful
difference between wheezy and jessie score keeping here. I remember
a few changes, but they should actually help in these cases rather than
making it fail spectacularly…
(Assuming you implement them correctly of course…)
Commit 9ec748ff103840c4c65471ca00d3b72984131ce4 from Feb 23 last year
adds a version check after 8daf68e366fa9fa2794ae667f51562663856237c
added 8 days earlier negative points for breaks/conflicts with the
intended that only dependencies which are satisfied propagate points
(aka: old conflicts do not).
The implementation was needlessly complex and flawed through preventing
positive dependencies from gaining points like they did before these
commits making library transitions harder instead of simpler. It worked
out anyhow most of the time out of pure 'luck' (and other ways of
gaining points) or got miss attributed to being a temporary hick-up.
(Changing the priorities would still be a good idea anyhow)
Best regards
David schrödinbug Kalnischkies
commit 77b6f202e1629b7794a03b6522d636ff1436d074
Author: David Kalnischkies da...@kalnischkies.de
Date: Sat Jan 10 12:31:18 2015 +0100
award points for positive dependencies again
Commit 9ec748ff103840c4c65471ca00d3b72984131ce4 from Feb 23 last year
adds a version check after 8daf68e366fa9fa2794ae667f51562663856237c
added 8 days earlier negative points for breaks/conflicts with the
intended that only dependencies which are satisfied propagate points
(aka: old conflicts do not).
The implementation was needlessly complex and flawed through preventing
positive dependencies from gaining points like they did before these
commits making library transitions harder instead of simpler. It worked
out anyhow most of the time out of pure 'luck' (and other ways of
gaining points) or got miss attributed to being a temporary hick-up.
Closes: 774924
diff --git a/apt-pkg/algorithms.cc b/apt-pkg/algorithms.cc
index 608ec7f..b838310 100644
--- a/apt-pkg/algorithms.cc
+++ b/apt-pkg/algorithms.cc
@@ -468,7 +468,7 @@ void pkgProblemResolver::MakeScores()
if (D-Version != 0)
{
pkgCache::VerIterator const IV = Cache[T].InstVerIter(Cache);
- if (IV.end() == true || D.IsSatisfied(IV) != D.IsNegative())
+ if (IV.end() == true || D.IsSatisfied(IV) == false)
continue;
}
Scores[T-ID] += DepMap[D-Type];
diff --git a/test/integration/test-allow-scores-for-all-dependency-types b/test/integration/test-allow-scores-for-all-dependency-types
index a5c98f3..d60cb8d 100755
--- a/test/integration/test-allow-scores-for-all-dependency-types
+++ b/test/integration/test-allow-scores-for-all-dependency-types
@@ -32,6 +32,11 @@ insertpackage 'multipleyes' 'foo' 'amd64' '2.2' 'Conflicts: bar (= 3)'
# having foo multiple times as conflict is a non-advisable hack in general
insertpackage 'multipleyes' 'bar' 'amd64' '2.2' 'Conflicts: foo (= 3), foo (= 3)'
+#774924 - slightly simplified
+insertpackage 'jessie' 'login' 'amd64' '2' 'Pre-Depends: libaudit1 (= 0)'
+insertpackage 'jessie' 'libaudit1' 'amd64' '2' 'Depends: libaudit-common (= 0)'
+insertpackage 'jessie' 'libaudit-common' 'amd64' '2' 'Breaks: libaudit0, libaudit1 ( 2)'
+
cp rootdir/var/lib/dpkg/status rootdir/var/lib/dpkg/status-backup
setupaptarchive
@@ -142,3 +147,26 @@ Inst foo [1] (2 versioned [amd64])
Inst baz (2 versioned [amd64])
Conf foo (2 versioned [amd64])
Conf baz (2 versioned [amd64])' aptget install baz -st versioned
+
+# recreating the exact situation is hard, so we pull tricks to get the score
+cp -f rootdir/var/lib/dpkg/status-backup rootdir/var/lib/dpkg/status
+insertinstalledpackage 'gdm3' 'amd64' '1' 'Depends: libaudit0, libaudit0'
+insertinstalledpackage 'login' 'amd64' '1' 'Essential: yes'
+insertinstalledpackage 'libaudit0' 'amd64' '1'
+testequal 'Reading package lists...
+Building dependency tree...
+The following packages will be REMOVED:
+ gdm3 libaudit0
+The following NEW packages will be installed:
+ libaudit-common libaudit1
+The following packages will be upgraded:
+ login
+1 upgraded, 2 newly installed, 2 to remove and 0 not upgraded.
+Remv gdm3 [1]
+Remv libaudit0 [1]
+Inst libaudit-common (2 jessie [amd64])
+Conf libaudit-common (2 jessie [amd64])
+Inst libaudit1 (2 jessie [amd64])
+Conf libaudit1 (2 jessie [amd64])
+Inst login [1] (2 jessie [amd64])
+Conf login (2 jessie [amd64])' aptget dist-upgrade -st jessie
signature.asc
Description: Digital signature
Processed: Re: Bug#774924: apt: Jessie version cannot find upgrade path (but Wheezy version can)
Processing control commands: found -1 0.9.16 Bug #774924 [apt] apt: Jessie version cannot find upgrade path (but Wheezy version can) Marked as found in versions apt/0.9.16. tags -1 patch Bug #774924 [apt] apt: Jessie version cannot find upgrade path (but Wheezy version can) Added tag(s) patch. -- 774924: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773085: Regression in escaped url handling with patch applied for #773085
❦ 8 janvier 2015 08:50 +0100, Vincent Bernat ber...@debian.org : Per, I see that you committed to git yesterday. Would you take the patch as is or do you want me to do an NMU? I have just uploaded an NMU to delayed/2. Works for me. -- Zounds! I was never so bethumped with words since I first called my brother's father dad. -- William Shakespeare, Kind John signature.asc Description: PGP signature
Processed: found 581407 in 2.9.9.4-1, bug 581407 is forwarded to http://sourceforge.net/p/dansguardian/bugs/65/ ...
Processing commands for cont...@bugs.debian.org: found 581407 2.9.9.4-1 Bug #581407 [dansguardian] dansguardian - problem accessing ssl-pages without appropriate exceptions Marked as found in versions dansguardian/2.9.9.4-1. forwarded 581407 http://sourceforge.net/p/dansguardian/bugs/65/ Bug #581407 [dansguardian] dansguardian - problem accessing ssl-pages without appropriate exceptions Set Bug forwarded-to-address to 'http://sourceforge.net/p/dansguardian/bugs/65/'. reassign 698375 gfs2-utils 3.1.3-1 Bug #698375 [gfs2-utils,redhat-cluster-suite] gfs2-utils: fails to upgrade from wheezy: insserv: script gfs2-utils: service gfs2 already provided! Bug reassigned from package 'gfs2-utils,redhat-cluster-suite' to 'gfs2-utils'. No longer marked as found in versions redhat-cluster/3.1.8-1.2, redhat-cluster/3.1.8-1.1, and gfs2-utils/3.1.3-1.1. Ignoring request to alter fixed versions of bug #698375 to the same values previously set Bug #698375 [gfs2-utils] gfs2-utils: fails to upgrade from wheezy: insserv: script gfs2-utils: service gfs2 already provided! Marked as found in versions gfs2-utils/3.1.3-1. affects 698375 + redhat-cluster-suite system-config-cluster Bug #698375 [gfs2-utils] gfs2-utils: fails to upgrade from wheezy: insserv: script gfs2-utils: service gfs2 already provided! Added indication that 698375 affects redhat-cluster-suite and system-config-cluster tags 698375 + patch Bug #698375 [gfs2-utils] gfs2-utils: fails to upgrade from wheezy: insserv: script gfs2-utils: service gfs2 already provided! Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 581407: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581407 698375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774917: icinga-idoutils: fails to upgrade squeeze - wheezy - jessie: ERROR: syntax error at or near EXISTS LINE 1: ALTER TABLE icinga_comments DROP CONSTRAINT IF EXISTS uq_com... ^
On Fri, Jan 09, 2015 at 03:39:51AM +0100, Andreas Beckmann wrote: error encountered processing /usr/share/dbconfig-common/data/icinga-idoutils/upgrade/pgsql/1.10.1-1: ERROR: syntax error at or near EXISTS LINE 1: ALTER TABLE icinga_comments DROP CONSTRAINT IF EXISTS uq_com... ^ DROP CONSTRAINT IF EXISTS was added in PostgreSQL 9.0, which version is used on the machine? -- WBR, wRAR signature.asc Description: Digital signature
Bug#775041: samba: add Breaks: qtsmbstatus-server ( 2.2.1-3~)
Package: samba Version: 2:4.1.13+dfsg-2 Severity: serious Tags: patch Hi, samba needs to break the wheezy version of qtsmbstatus-server due to initscript incompatibility (see #722465 for details). There is no qtsmbstatus-server in jessie. Attached is a patch, I verified that this actually solves the problem. I do not intend to NMU samba. Andreas diff -Nru samba-4.1.13+dfsg/debian/changelog samba-4.1.13+dfsg/debian/changelog --- samba-4.1.13+dfsg/debian/changelog 2014-12-10 19:14:10.0 +0100 +++ samba-4.1.13+dfsg/debian/changelog 2015-01-10 16:56:29.0 +0100 @@ -1,3 +1,13 @@ +samba (2:4.1.13+dfsg-4.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * samba: Add Breaks: qtsmbstatus-server ( 2.2.1-3~) since +/etc/init.d/samba is no longer activated by default, but the +/etc/init.d/qtsmbstatusd from wheezy needs it. See #722465 for details. +(Closes: #xx) + + -- Andreas Beckmann a...@debian.org Sat, 10 Jan 2015 15:55:34 +0100 + samba (2:4.1.13+dfsg-4) unstable; urgency=medium * Revert previous patch, since ldb has an active module version check. diff -Nru samba-4.1.13+dfsg/debian/control samba-4.1.13+dfsg/debian/control --- samba-4.1.13+dfsg/debian/control 2014-12-10 19:14:10.0 +0100 +++ samba-4.1.13+dfsg/debian/control 2015-01-10 16:06:23.0 +0100 @@ -92,6 +92,7 @@ smbldap-tools, winbind Enhances: bind9, ntp +Breaks: qtsmbstatus-server ( 2.2.1-3~), Replaces: libsamdb0 ( 4.0.0~alpha17~), python-samba ( 2:4.1.4+dfsg-3), samba-ad-dc,
Processed: tagging 774918
Processing commands for cont...@bugs.debian.org: tags 774918 + patch Bug #774918 [cups-pdf] cups-pdf: copyright file missing after upgrade (policy 12.5) Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 774918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698375: gfs2-utils: fails to upgrade from wheezy: insserv: script gfs2-utils: service gfs2 already provided!
Followup-For: Bug #698375
Hi,
adjusted Salvatore's patch to also run
dpkg-maintscript-helper rm_conffile on initial package install.
Verified that the upgrade path works.
NMU uploaded to DELAYED/2.
Andreas
diff -Nru gfs2-utils-3.1.3/debian/changelog gfs2-utils-3.1.3/debian/changelog
--- gfs2-utils-3.1.3/debian/changelog 2013-01-11 19:18:10.0 +0100
+++ gfs2-utils-3.1.3/debian/changelog 2015-01-10 12:21:37.0 +0100
@@ -1,3 +1,20 @@
+gfs2-utils (3.1.3-1.2) unstable; urgency=low
+
+ [ Salvatore Bonaccorso ]
+ * Remove old conffile /etc/init.d/gfs2-tools from gfs2-tools package.
+Add a Pre-Depends on dpkg to use dpkg-maintscript-helper. Add
+${misc:Pre-Depends} to Pre-Depends control file field.
+Add debian/gfs2-utils.maintscript containing the rm_conffile command to
+remove /etc/init.d/gfs2-tools init script from superseeded gfs2-tools
+package. (Closes: #698375)
+
+ [ Andreas Beckmann ]
+ * Non-maintainer upload.
+ * Trick dpkg-maintscript-helper to also run on initial install.
+ * Do not pass obsolete 'start' arguments to update-rc.d
+
+ -- Andreas Beckmann a...@debian.org Sat, 10 Jan 2015 12:21:37 +0100
+
gfs2-utils (3.1.3-1.1) unstable; urgency=low
* Non-maintainer upload.
diff -Nru gfs2-utils-3.1.3/debian/control gfs2-utils-3.1.3/debian/control
--- gfs2-utils-3.1.3/debian/control 2013-01-11 19:18:10.0 +0100
+++ gfs2-utils-3.1.3/debian/control 2015-01-10 11:49:29.0 +0100
@@ -10,6 +10,7 @@
Package: gfs2-utils
Architecture: any
+Pre-Depends: ${misc:Pre-Depends}
Depends: ${misc:Depends}, ${shlibs:Depends}, gfs2-cluster (= ${binary:Version}), psmisc, cman
Replaces: gfs2-tools (= 3.0.17)
Conflicts: gfs2-tools (= 3.0.17)
diff -Nru gfs2-utils-3.1.3/debian/gfs2-utils.maintscript gfs2-utils-3.1.3/debian/gfs2-utils.maintscript
--- gfs2-utils-3.1.3/debian/gfs2-utils.maintscript 1970-01-01 01:00:00.0 +0100
+++ gfs2-utils-3.1.3/debian/gfs2-utils.maintscript 2015-01-10 12:21:30.0 +0100
@@ -0,0 +1,2 @@
+# HACK: trick dpkg-maintscript-helper to also do the rm_conffile on initial install by always giving a not-empty old version argument
+rm_conffile /etc/init.d/gfs2-tools 3.1.3-1.2~ gfs2-tools -- $@ 0
diff -Nru gfs2-utils-3.1.3/debian/rules gfs2-utils-3.1.3/debian/rules
--- gfs2-utils-3.1.3/debian/rules 2013-01-11 19:18:10.0 +0100
+++ gfs2-utils-3.1.3/debian/rules 2015-01-10 12:16:52.0 +0100
@@ -31,8 +31,7 @@
dh_install --list-missing
override_dh_installinit:
- dh_installinit -p gfs2-utils --no-start --no-restart-on-upgrade -- start 65 S . start 2 0 6 .
- dh_installinit -p gfs2-cluster --no-start --no-restart-on-upgrade -- start 65 S . start 2 0 6 .
+ dh_installinit --no-start --no-restart-on-upgrade
override_dh_auto_clean:
dh_auto_clean
Bug#773170: [Pkg-sysvinit-devel] Bug#773170: insserv: refuses to start postfix at boot because dnsmasq is disabled
severity 773170 important -- On Wed, Dec 17, 2014 at 09:33:16AM +0100, Yves-Alexis Perez wrote: On Tue, 16 Dec 2014 09:58:09 +0100 Petter Reinholdtsen p...@hungry.com wrote: Well, postfix uses Required-start: $named because it needs name resolution. And I guess dnsmasq provides $named by default, but that's actually not the case in Salvo system. Not sure what's the correct way to fix this. A quick way would be to remove the Provide: $named, when configuring dnsmasq to not be be used as a name resolution daemon, but that can't really be done automatically. Postfix does, indeed REQUIRE that name resolution work on the machine. Therefore, $named is the correct thing to require. My next bit of investigation will be to look into what Provides: $named when dnsmasq is NOT installed. lamont -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#773170: [Pkg-sysvinit-devel] Bug#773170: insserv: refuses to start postfix at boot because dnsmasq is disabled
Processing commands for cont...@bugs.debian.org: severity 773170 important Bug #773170 [postfix] insserv: refuses to start postfix at boot because dnsmasq is disabled Severity set to 'important' from 'critical' -- Stopping processing here. Please contact me if you need assistance. -- 773170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#770009: fixed in imagemagick 8:6.8.9.9-5
Processing control commands:
reopen -1
Bug #770009 {Done: Bastien Roucariès roucaries.bastien+deb...@gmail.com}
[imagemagick] Imagemagick FTBFS on mips on mips-aql-* not on ball
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions imagemagick/8:6.8.9.9-5.
--
770009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770009: fixed in imagemagick 8:6.8.9.9-5
Control: reopen -1 Hi, On Mon, Jan 05, 2015 at 10:04:18PM +, Bastien Roucariès wrote: * Workarround Imagemagick FTBFS on mips on mips-aql-* not on ball. Do not execute testsuite if FPU is not present. Security team want this bug fixed in order to ease it work, thanks to Ivo De Decker (Closes: #770009). It still fails on mips. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746543: nmu: pinba-engine-mysql-5.5_1.0.0-4 (was: Re: pinba-engine-mysql-5.5: uninstallable: depends on obsolete version of mysql-5.5)
reassign 746543 release.debian.org retitle 746543 nmu: pinba-engine-mysql-5.5_1.0.0-4 user release.debian@packages.debian.org usertag 746543 binnmu severity 746543 normal thanks On Thu, 1 May 2014 09:11:45 +0200 Ivo De Decker ivo.dedec...@ugent.be wrote: The upload of mysql-5.5 5.5.37-1 makes pinba-engine-mysql-5.5 uninstallable in sid, as it depends on an older version. Either a new upload or a binnmu is necessary. and now we have mysql-5.5 5.5.40-1 in sid ... so finally do a binNMU (testbuild succeeded on amd64) nmu pinba-engine-mysql-5.5_1.0.0-4 . ALL . -m Rebuild against mysql-5.5 5.5.40 Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: nmu: pinba-engine-mysql-5.5_1.0.0-4 (was: Re: pinba-engine-mysql-5.5: uninstallable: depends on obsolete version of mysql-5.5)
Processing commands for cont...@bugs.debian.org: reassign 746543 release.debian.org Bug #746543 [pinba-engine-mysql-5.5] pinba-engine-mysql-5.5: uninstallable: depends on obsolete version of mysql-5.5 Bug reassigned from package 'pinba-engine-mysql-5.5' to 'release.debian.org'. No longer marked as found in versions pinba-engine-mysql/1.0.0-4. Ignoring request to alter fixed versions of bug #746543 to the same values previously set retitle 746543 nmu: pinba-engine-mysql-5.5_1.0.0-4 Bug #746543 [release.debian.org] pinba-engine-mysql-5.5: uninstallable: depends on obsolete version of mysql-5.5 Changed Bug title to 'nmu: pinba-engine-mysql-5.5_1.0.0-4' from 'pinba-engine-mysql-5.5: uninstallable: depends on obsolete version of mysql-5.5' user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was a...@debian.org). usertag 746543 binnmu There were no usertags set. Usertags are now: binnmu. severity 746543 normal Bug #746543 [release.debian.org] nmu: pinba-engine-mysql-5.5_1.0.0-4 Severity set to 'normal' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 746543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746543 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759530: CPU info?
On Thu, Jan 01, 2015 at 10:09:58PM +0100, Yves-Alexis Perez wrote: I'm not experiencing that bug, but maybe it'd help if the submitters would provide their /proc/cpuinfo and maybe try to get a clue about where the segfault happens (maybe with coredumps)? /proc/cpuinfo from Bernd Zeimetz (he was reporting segfaults as well): processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz stepping: 7 microcode : 0x29 cpu MHz : 813.769 cache size : 3072 KB physical id : 0 siblings: 4 core id : 1 cpu cores : 2 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid bogomips: 4983.78 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: [TLS1.2] gnutls only likes SHA1 and SHA256 certificates
Processing commands for cont...@bugs.debian.org:
reopen 737921
Bug #737921 {Done: Debian FTP Masters ftpmas...@ftp-master.debian.org}
[gnutls26] [TLS1.2] gnutls only likes SHA1 and SHA256 certificates
Bug #740160 {Done: Debian FTP Masters ftpmas...@ftp-master.debian.org}
[gnutls26] gnutls unusable with cacert SHA2-512 sigs
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 2.12.23-17+rm.
No longer marked as fixed in versions 2.12.23-17+rm.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
737921: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737921
740160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740160
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: forcibly merging 774461 775059
Processing commands for cont...@bugs.debian.org: forcemerge 774461 775059 Bug #774461 [src:linux] linux-image-3.2.0-4-amd64: suspend triggers reboot Bug #774436 [src:linux] linux-image-3.2.0-4-amd64: suspend to ram regression in 3.2.65-1 Bug #774526 [src:linux] linux-image-3.2.0-4-amd64: system crash with sudden reboot when hotplugging a CPU - suspend functionality broken Bug #775059 [src:linux] linux-image-3.2.0-4-amd64: kernel update broke suspend to ram - system crashes instead Severity set to 'serious' from 'important' Added indication that 775059 affects release.debian.org Bug #774436 [src:linux] linux-image-3.2.0-4-amd64: suspend to ram regression in 3.2.65-1 Bug #774526 [src:linux] linux-image-3.2.0-4-amd64: system crash with sudden reboot when hotplugging a CPU - suspend functionality broken Merged 774436 774461 774526 775059 thanks Stopping processing here. Please contact me if you need assistance. -- 774436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774436 774461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774461 774526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774526 775059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775059 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775067: systemd: journald doesn't forward messages to syslog w/o CAP_SYS_ADMIN (LXC)
Package: systemd
Version: 215-8
Severity: grave
Tags: upstream patch
Justification: causes non-serious data loss
Dear Maintainer,
when using LXC containers without CAP_SYS_ADMIN, journald fails to
forward any messages to syslog by default. Since the journal is not
persistent by default, no logs are stored at all, hence the
classification as 'data loss'. Also, this is a regression from Wheezy,
where a container without CAP_SYS_ADMIN and syslog did indeed store
persistent logs in /var/log/{syslog,messages,...}.
Note that there is NO other problem with systemd related to missing
CAP_SYS_ADMIN in a container (that I have found so far), provided all
required (pseudo-) file systems are mounted beforehand (which can be
done by configuration with Jessie's LXC version). I do know that
upstream claims that CAP_SYS_ADMIN-less containers are currently not
really supported, but they do intend to work towards that, and, from
what I can tell, apart from this journald problem, I have found no
issue whatsoever with a missing CAP_SYS_ADMIN (it actually works even
better than under sysvinit because it doesn't try to do some stuff
it's not supposed to do in containers that cause error messages with
sysvinit) - and since these kinds of containers were working in
Wheezy with its default init, I think this should be supported in
Jessie, too, especially if the fix is really easy, see below.
This bug is independent of the syslog implementation used, because no
syslog implementation in Jessie supports reading directly from the
journal, as far as I can tell (syslog-ng is too old, rsyslog is built
without imjournal support), so all rely on ForwardToSyslog=yes.
The reason why this problem occurs is that journald tries to fake
SCM_CREDENTIALS before sending a packet to the syslog daemon. With
CAP_SETUID and CAP_SETGID, faking uid/gid is not a problem, but to fake
the pid in struct ucred, one needs CAP_SYS_ADMIN (according to current
kernel source).
Also note that without activating debugging in journald, this problem
can not be diagnosed easily (it took me a while with strace to find the
problem).
Note, however, two things:
- journald does (and can) not guarantee that it can fake the pid,
because the process could have already exited. If you look at the
source, in case ESRCH is returned, it just fakes uid/gid and uses
its own pid
- both rsyslog and syslog-ng (haven't tried anything else yet) don't
rely on SCM_CREDENTIAL's pid anyway in their default configuration,
so at least in the default configuration there's no reason to fail
in that case.
I have created (and tested) an absolutely trivial patch that fixes this
by not only checking for ESRCH but also EPERM and then avoid faking the
pid.
I have tested this with both rsyslog and syslog-ng and it works and
both store (the same ;-)) persistent log messages in
/var/log/{messages,syslog,...}.
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii acl 2.2.52-2
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-58
ii libacl1 2.2.52-2
ii libaudit1 1:2.4-1+b1
ii libblkid1 2.25.2-4
ii libc6 2.19-13
ii libcap2 1:2.24-6
ii libcap2-bin 1:2.24-6
ii libcryptsetup4 2:1.6.6-4
ii libgcrypt20 1.6.2-4+b1
ii libkmod218-3
ii liblzma55.1.1alpha+20120614-2+b3
ii libpam0g1.1.8-3.1
ii libselinux1 2.3-2
ii libsystemd0 215-8
ii mount 2.25.2-4
ii sysv-rc 2.88dsf-58
ii udev215-8
ii util-linux 2.25.2-4
Versions of packages systemd recommends:
ii dbus1.8.12-3
ii libpam-systemd 215-8
Versions of packages systemd suggests:
pn systemd-ui none
-- no debconf information
Description: Make journald syslog fwd'ing work w/o CAP_SYS_ADMIN
In case CAP_SYS_ADMIN is missing, one cannot fake pid in struct ucred
(uid/gid are find if CAP_SETUID/CAP_SETGID are present), which is the
case in some container setups.
.
This patch makes sure that journald will try again to forward the
messages to syslog, without faking the SCM_CREDENTIALS pid this time
(which isn't guaranteed anyway, since it also does the same thing if
the process has already exited).
.
With this patch, journald will no longer silently discard messages
that are supposed to be sent to syslog in these situations.
Author: Christian Seiler christ...@iwakd.de
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
Index: systemd-215/src/journal/journald-syslog.c
===
--- systemd-215.orig/src/journal/journald-syslog.c
+++ systemd-215/src/journal/journald-syslog.c
@@ -85,12 +85,12 @@ static
Bug#775053: debbugs: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/debbugs/examples/config
Package: debbugs Version: 2.4.1 Severity: serious Tags: wheezy-ignore squeeze-ignore User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package uses files from /usr/share/doc in its maintainer scripts which is a violation of Policy 12.3: Packages must not require the existence of any files in /usr/share/doc/ in order to function. https://www.debian.org/doc/debian-policy/ch-docs.html#s12.3 These files must be moved to /usr/share/$PACKAGE and may be symlinked from /usr/share/doc/$PACKAGE. This piuparts test prevents the installation of (most) files into /usr/share/doc with 'dpkg --path-exclude=...'. From the attached log (scroll to the bottom...): Selecting previously unselected package debbugs. (Reading database ... 9350 files and directories currently installed.) Preparing to unpack .../archives/debbugs_2.4.1_all.deb ... Unpacking debbugs (2.4.1) ... Setting up debbugs (2.4.1) ... cp: cannot stat '/usr/share/doc/debbugs/examples/config': No such file or directory No such file or directory at /usr/sbin/debbugsconfig line 75. dpkg: error processing package debbugs (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: debbugs Cheers, Andreas debbugs_2.4.1.log.gz Description: application/gzip
Processed: affects 774526
Processing commands for cont...@bugs.debian.org: affects 774526 + release.debian.org Bug #774526 [src:linux] linux-image-3.2.0-4-amd64: system crash with sudden reboot when hotplugging a CPU - suspend functionality broken Bug #774436 [src:linux] linux-image-3.2.0-4-amd64: suspend to ram regression in 3.2.65-1 Bug #774461 [src:linux] linux-image-3.2.0-4-amd64: suspend triggers reboot Added indication that 774526 affects release.debian.org Added indication that 774436 affects release.debian.org Added indication that 774461 affects release.debian.org thanks Stopping processing here. Please contact me if you need assistance. -- 774436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774436 774461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774461 774526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775056: python3-llfuse: package unusable due to non-existent module dependency 'Queue'
Package: python3-llfuse Version: 0.37.1-2 Severity: grave Justification: renders package unusable Dear Maintainer, apparently, the package wants to import the 'Queue' python module, which seems to have been renamed to 'queue' in python3. Attempting to use the llfuse module fails like this: $ python3 -c 'import llfuse' Traceback (most recent call last): File string, line 1, in module File llfuse.pyx, line 76, in init llfuse (src/llfuse.c:24898) ImportError: No module named Queue -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python3-llfuse depends on: ii libc6 2.13-38+deb7u6 ii libfuse2 2.9.0-2+deb7u1 ii python3 3.2.3-6 python3-llfuse recommends no packages. Versions of packages python3-llfuse suggests: pn python-llfuse-doc none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#766749: Fixed upstream, patch included
Processing control commands: severity -1 serious Bug #766749 [mate-power-manager] mate-power-manager: brightness is not shown while changing brightness using hardware keys Severity set to 'serious' from 'important' -- 766749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772611: horae: build-depend on libpod-latex-perl to fix FTBFS
Hi Logan: It will be fixed in the next release On Tue, 9 Dec 2014, Logan Rosen wrote: Package: horae Version: 071~svn537-1 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu vivid ubuntu-patch Dear Maintainer, horae currently FTBFS on amd64 (and presumably i386 as well) due to a missing build dependency on libpod-latex-perl. Here is the relevant extract from the build log: # Generate man pages for artemis only cd lib/Ifeffit/lib/artemis.doc ; ./make_doc --man Can't locate Pod/LaTeX.pm in @INC (you may need to install the Pod::LaTeX module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.1 /usr/local/share/perl/5.20.1 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at ./make_doc line 93. BEGIN failed--compilation aborted at ./make_doc line 93. debian/rules:29: recipe for target 'build-stamp' failed In Ubuntu, the attached patch was applied to achieve the following: * Build-depend on libpod-latex-perl to fix FTBFS. Thanks for considering the patch. Logan Rosen -- System Information: Debian Release: jessie/sid APT prefers vivid-updates APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), (100, 'vivid-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-25-generic (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Carlo U. Segre -- Duchossois Leadership Professor of Physics Director, Center for Synchrotron Radiation Research and Instrumentation Illinois Institute of Technology Voice: 312.567.3498Fax: 312.567.3494 se...@iit.edu http://phys.iit.edu/~segre se...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772611: marked as done (horae: build-depend on libpod-latex-perl to fix FTBFS)
Your message dated Sat, 10 Jan 2015 21:19:05 + with message-id e1ya3r3-0006z1...@franck.debian.org and subject line Bug#772611: fixed in horae 071~svn537-2 has caused the Debian Bug report #772611, regarding horae: build-depend on libpod-latex-perl to fix FTBFS 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.) -- 772611: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: horae Version: 071~svn537-1 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu vivid ubuntu-patch Dear Maintainer, horae currently FTBFS on amd64 (and presumably i386 as well) due to a missing build dependency on libpod-latex-perl. Here is the relevant extract from the build log: # Generate man pages for artemis only cd lib/Ifeffit/lib/artemis.doc ; ./make_doc --man Can't locate Pod/LaTeX.pm in @INC (you may need to install the Pod::LaTeX module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.1 /usr/local/share/perl/5.20.1 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at ./make_doc line 93. BEGIN failed--compilation aborted at ./make_doc line 93. debian/rules:29: recipe for target 'build-stamp' failed In Ubuntu, the attached patch was applied to achieve the following: * Build-depend on libpod-latex-perl to fix FTBFS. Thanks for considering the patch. Logan Rosen -- System Information: Debian Release: jessie/sid APT prefers vivid-updates APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), (100, 'vivid-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-25-generic (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru horae-071~svn537/debian/control horae-071~svn537/debian/control --- horae-071~svn537/debian/control 2014-11-27 00:45:07.0 -0500 +++ horae-071~svn537/debian/control 2014-12-09 01:41:19.0 -0500 @@ -4,7 +4,7 @@ Maintainer: Carlo Segre se...@debian.org Build-Depends: debhelper (= 7) Build-Depends-Indep: perl (= 5.6.0-16), libchemistry-elements-perl, - perl-tk (= 804), libifeffit-perl + perl-tk (= 804), libifeffit-perl, libpod-latex-perl Homepage: http://cars9.uchicago.edu/~ravel/software/Welcome.html Standards-Version: 3.9.6 ---End Message--- ---BeginMessage--- Source: horae Source-Version: 071~svn537-2 We believe that the bug you reported is fixed in the latest version of horae, 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 772...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Carlo Segre se...@debian.org (supplier of updated horae 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: Sat, 10 Jan 2015 14:53:11 -0600 Source: horae Binary: horae Architecture: source all Version: 071~svn537-2 Distribution: unstable Urgency: medium Maintainer: Carlo Segre se...@debian.org Changed-By: Carlo Segre se...@debian.org Description: horae - interactive graphical processing and analysis of EXAFS data Closes: 772611 Changes: horae (071~svn537-2) unstable; urgency=medium . * Add Build-Depends on libpod-latex-perl (Closes: #772611) Checksums-Sha1: 4fbf6f7f0a4f262c10c18f85f79016fc843a559a 1856 horae_071~svn537-2.dsc 391d031c461bd5c5111f14d0c13a51ee5e641bfb 16840 horae_071~svn537-2.debian.tar.xz ee63b6d07ae05e40c50670b9e4cb9fc42c2a77ee 4870952 horae_071~svn537-2_all.deb Checksums-Sha256: 80ad57bd86b2f1dae618996bd7d2eb6a43fa4eaf3f31fa30b6984550d5a6e45a 1856 horae_071~svn537-2.dsc 69a51f8c324bed282d5e29d0ef4c4439cd6f19c50045195a62e1098f53340269 16840 horae_071~svn537-2.debian.tar.xz 3f0cd7bdceb3916fec3192703e4d263ebd6c2478ff1b5c7d4f5c6ef3ef8b18e1 4870952 horae_071~svn537-2_all.deb Files: 01e17290c61db6596a418d517cb4b552 1856 contrib/science optional horae_071~svn537-2.dsc 7ab15d7f57e9b89e0ceecb840719497e 16840
Bug#767028: ovirt-guest-agent: fails to install
Hi László, On Freitag, 9. Januar 2015, László Böszörményi (GCS) wrote: Digging deep into this, it seems the problem lies in an other thing. Do you have /proc mounted in your piuparts test environment? since 0.17 piuparts mounts proc inside the tested chroot... :-) so I *suspect* this something else, cc:ing the piuparts lists for further input or investigation. (I wont have much time to look into this for at least the next 4 days probably rather 2 weeks...) This seems to be an udevadm 'bug' instead, it can't handle unreachable /proc/cmdline . Is there any policy that a package should install while /proc is unavailable? packages may be in non working state, but I'd argue that installation itself must still not fail... cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#775052: qmail-run: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/qmail-run/examples/aliases
Package: qmail-run Version: 2.0.2 Severity: serious Tags: wheezy-ignore User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package uses files from /usr/share/doc in its maintainer scripts which is a violation of Policy 12.3: Packages must not require the existence of any files in /usr/share/doc/ in order to function. https://www.debian.org/doc/debian-policy/ch-docs.html#s12.3 These files must be moved to /usr/share/$PACKAGE and may be symlinked from /usr/share/doc/$PACKAGE. This piuparts test prevents the installation of (most) files into /usr/share/doc with 'dpkg --path-exclude=...'. From the attached log (scroll to the bottom...): Selecting previously unselected package qmail-run. (Reading database ... 7981 files and directories currently installed.) Preparing to unpack .../qmail-run_2.0.2_all.deb ... Unpacking qmail-run (2.0.2) ... Setting up qmail-run (2.0.2) ... creating default /etc/aliases... cp: cannot stat '/usr/share/doc/qmail-run/examples/aliases': No such file or directory dpkg: error processing package qmail-run (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: qmail-run Cheers, Andreas qmail-run_2.0.2.log.gz Description: application/gzip
Bug#774861: marked as done (libwine-alsa, libwine-gl: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)
Your message dated Sat, 10 Jan 2015 19:49:18 +
with message-id e1ya22a-0004bn...@franck.debian.org
and subject line Bug#774861: fixed in wine 1.6.2-18
has caused the Debian Bug report #774861,
regarding libwine-alsa, libwine-gl: unhandled symlink to directory conversion:
/usr/share/doc/PACKAGE
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.)
--
774861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libwine-alsa,libwine-gl
Version: 1.6.2-17
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.
This was observed on the following upgrade paths:
wheezy - jessie (package wine, with --install-recommends)
For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
For other overwritten locations anything interesting may happen.
Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase
It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
From the attached log (usually somewhere in the middle...):
4m59.7s ERROR: FAIL: silently overwrites files via directory symlinks:
/usr/share/doc/libwine-alsa/changelog.Debian.gz (libwine-alsa) !=
/usr/share/doc/libwine/changelog.Debian.gz (libwine:i386)
/usr/share/doc/libwine-alsa - libwine
/usr/share/doc/libwine-alsa/copyright (libwine-alsa) !=
/usr/share/doc/libwine/copyright (libwine:i386)
/usr/share/doc/libwine-alsa - libwine
/usr/share/doc/libwine-gl/changelog.Debian.gz (libwine-gl:i386) !=
/usr/share/doc/libwine/changelog.Debian.gz (libwine:i386)
/usr/share/doc/libwine-gl - libwine
/usr/share/doc/libwine-gl/copyright (libwine-gl:i386) !=
/usr/share/doc/libwine/copyright (libwine:i386)
/usr/share/doc/libwine-gl - libwine
cheers,
Andreas
wine_1.6.2-17.log.gz
Description: application/gzip
---End Message---
---BeginMessage---
Source: wine
Source-Version: 1.6.2-18
We believe that the bug you reported is fixed in the latest version of
wine, 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 774...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Gilbert mgilb...@debian.org (supplier of updated wine 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: Sat, 10 Jan 2015 18:40:51 +
Source: wine
Binary: wine wine-binfmt wine32 wine64 wine32-dev-tools wine32-tools
wine64-dev-tools wine64-tools libwine-dev libwine-dbg libwine wine-bin
wine64-bin libwine-alsa libwine-bin libwine-capi libwine-cms libwine-gl
libwine-gphoto2 libwine-ldap libwine-openal libwine-oss libwine-print
libwine-sane
Architecture: source
Version: 1.6.2-18
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party pkg-wine-pa...@lists.alioth.debian.org
Changed-By: Michael Gilbert mgilb...@debian.org
Description:
libwine- Windows API implementation - library
libwine-alsa - Windows API implementation - ALSA sound module
libwine-bin - Windows API implementation - system services
libwine-capi -
Bug#775063: greylistd: fails to install, remove, distupgrade, and install again
Package: greylistd Version: 0.8.8.3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install (in 'wheezy'), remove (but not purge), distupgrade to 'jessie', and install again. Before the second installation the package is in config-files-remaining state. The configuration is remaining from the last version that was successfully configured - which is from the previous release. Like a plain failure on initial install this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package greylistd. Unpacking greylistd (from .../greylistd_0.8.8_all.deb) ... Setting up greylistd (0.8.8) ... Adding system user `greylist' (UID 100) ... Adding new group `greylist' (GID 150) ... Adding new user `greylist' (UID 100) with group `greylist' ... Not creating home directory `/var/lib/greylistd'. Creating directory /var/run/greylistd: Done. Copying /usr/share/doc/greylistd/examples/whitelist-hosts to /etc/greylistd: Done. invoke-rc.d: policy-rc.d denied execution of start. Removing greylistd ... invoke-rc.d: policy-rc.d denied execution of stop. Selecting previously unselected package greylistd. (Reading database ... 8369 files and directories currently installed.) Preparing to unpack .../greylistd_0.8.8.3_all.deb ... Unpacking greylistd (0.8.8.3) ... Setting up greylistd (0.8.8.3) ... insserv: script greylistd: service greylist already provided! insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package greylistd (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: greylistd The fix should be rather simple: the preinst script actions but be performed on both install and upgrade (install will get a second argument if the conffiles from an old version were remaining): [...] case $1 in install|upgrade) [...] cheers, Andreas greylistd_0.8.8.3.log.gz Description: application/gzip
Bug#775062: grok doesn't grok group name ('group name must start with a non-digit')
Package: grok
Version: 1.20110708.1-4
Severity: grave
Justification: renders package unusable
Dear maintainer,
I tried to use the grok examples packaged with grok:
$ grok -f /usr/share/doc/grok/examples/number-predicate2.grok
Failure compiling pattern '%{NUMBER 20}': group name must start with a
non-digit
All groke examples fail with this group name must start with a
non-digit error.
I recompiled grok from source (g...@github.com:jordansissel/grok.git)
and the problem does not appear:
$ ./bin/grok -f /usr/share/doc/grok/examples/number-predicate2.grok
Got number: 33
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (90, 'unstable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages grok depends on:
ii libc6 2.19-13
ii libevent-2.0-52.0.21-stable-2
ii libpcre3 2:8.35-3.3
ii libtokyocabinet9 1.4.48-3
grok recommends no packages.
grok suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775076: adt-setup-vm: sets force-unsafe-io for host dpkg, not guest
Source: autopkgtest
Version: 3.9
Severity: serious
Justification: Unwittingly sets dpkg force-unsafe-io on host
Tags: patch
Hi,
adt-setup-vm creates /etc/dpkg/dpkg.cfg.d/autopkgtest on the host,
instead of in the guest, because the path is missing the $root prefix
pointing to the directory where the guest's root is mounted.
This is very unfortunate, as that file sets force-unsafe-io for dpkg,
so this puts the host at risk to data loss.
Regards,
Christian
From c8e5aac84d1de20028e85ec236a4a998938bd361 Mon Sep 17 00:00:00 2001
From: Christian Kastner c...@kvr.at
Date: Sun, 11 Jan 2015 01:28:36 +0100
Subject: adt-setup-vm: Modify guest's dpkg config, not host's
Add the missing $root prefix (the path to the directory where the guest's root
is mounted) when writing /etc/dpkg/dpkg.conf.d/autopkgtest, otherwise the
host's configuration is modified instead. As force-unsafe-io is being set, this
is very dangerous.
---
tools/adt-setup-vm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/adt-setup-vm b/tools/adt-setup-vm
index cb0c9bb..b2f83d2 100755
--- a/tools/adt-setup-vm
+++ b/tools/adt-setup-vm
@@ -80,7 +80,7 @@ fi
# go-faster apt/dpkg
echo Acquire::Languages \none\; $root/etc/apt/apt.conf.d/90nolanguages
-echo 'force-unsafe-io' /etc/dpkg/dpkg.cfg.d/autopkgtest
+echo 'force-unsafe-io' $root/etc/dpkg/dpkg.cfg.d/autopkgtest
# auto-detect apt-cacher-ng
if [ -z ${ADT_APT_PROXY:-} ]; then
--
2.1.4
Processed: tagging 775022
Processing commands for cont...@bugs.debian.org: tags 775022 + security pending Bug #775022 [openssl] Important security update Added tag(s) security and pending. thanks Stopping processing here. Please contact me if you need assistance. -- 775022: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773829: Bug#773805: liblucene4-java: Incomplete poms installed in /usr/share/maven-repo
On 01/07/2015 10:41 PM, Niels Thykier wrote: On 2015-01-08 05:17, tony mancill wrote: [...] Hello Hilko, Emmanuel, I'm taking a look at this, but in the interest of the jessie release, I wanted to ask Emmanuel whether it would be okay to decrease the severity. We have a number of other packages with missing or incomplete poms, and propose that we discuss maven metadata for all Java library packages as a release goal for jessie + 1. Otherwise, the package will be removed soonish (February 5th). https://tracker.debian.org/pkg/lucene4 Thanks, tony [...] Hi, If the bug is RC on its own, but you believe it is irrelevant for the Jessie release, the correct option would be to have it ignored (please file a bug against release.debian.org for that). Mind you, the assumption is that the bug is in fact RC. If not, the release team will probably recommend downgrading it instead. If the bug only prevents new packages from being build (i.e. packages not already in Jessie/sid), it /sounds/ like it might not be RC after all (maybe important). However, please keep in mind that my answer is solely based on the above mail. Hi Niels, Thank you for the guidance. In the case of #773805 (maven pom), I do believe that it's not RC from a severity standpoint. I think #773829 might fall into the same category, although I do have a patch and will be uploading a new package with just this build change tomorrow morning. Cheers, tony signature.asc Description: OpenPGP digital signature
Bug#775062: Acknowledgement (grok doesn't grok group name ('group name must start with a non-digit'))
I bisected the issue and found it was fixed by this commit:
44ce9372a29319c01d4ac7f24287fb36315e0e34 is the first bad commit
commit 44ce9372a29319c01d4ac7f24287fb36315e0e34
Author: Guillaume Bour gb...@orange-vallee.net
Date: Thu Dec 11 14:07:21 2014 +0100
[fix] grok is not working anymore with PCRE = 8.34 because the
latter does
not allow anymore a group name to start with digits (PCRE Changelog
version 8.34, point 36)
this commit fix the issue by prepending a '_' at the start of group
name.
It remains compatible with older versions of PCRE
Found with:
~~~sh
git bisect origin/master 11942705515393ef12a5ed438abff0fe7b3ca232
git run test.sh
~~~
with test.sh:
~~~sh
#!/bin/sh
main() {
set -e
export PREFIX=temp
make clean
make
make install
cd temp
./bin/grok -f /usr/share/doc/grok/examples/numberpredicate.grok
}
if main; then false ; else true ; fi
~~~
-- Gabriel
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775076: adt-setup-vm: sets force-unsafe-io for host dpkg, not guest
On Sun, 11 Jan 2015 02:12:25 +0100 Christian Kastner deb...@kvr.at wrote:
adt-setup-vm creates /etc/dpkg/dpkg.cfg.d/autopkgtest on the host,
instead of in the guest, because the path is missing the $root
prefix pointing to the directory where the guest's root is mounted.
This is very unfortunate, as that file sets force-unsafe-io for
dpkg, so this puts the host at risk to data loss.
This was introduced by the following commit,
Regards,commit 86c333020caa05bcd6f964ef5fdcf2c8594065a1
Author: Martin Pitt martin.p...@ubuntu.com
Date: Thu Oct 9 13:09:25 2014 +0200
tools/adt-setup-vm: Add setup steps that adt-buildvm-ubuntu-cloud does
So that vmdebootstrap generated VMs are functionally on par with the Ubuntu
cloud images: Set up serial console, dpkg unsafe-io, install some additional
packages, remove unnecessary packages, bump vmalloc on i386.
so it entered Jessie.
I have attached a debdiff for the version in Jessie which includes the
bugfix from my earlier patch, and adds a postinst in which the offending
file is removed.
If there's anything else I can do to help, please let me know.
Regards,
Christian
diff -Nru autopkgtest-3.6/debian/changelog autopkgtest-3.6+nmu1/debian/changelog
--- autopkgtest-3.6/debian/changelog2014-10-16 16:36:18.0 +0200
+++ autopkgtest-3.6+nmu1/debian/changelog 2015-01-11 02:44:56.0
+0100
@@ -1,3 +1,16 @@
+autopkgtest (3.6+nmu1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * adt-setup-vm: Add the missing $root prefix (the mountpoint of the guest's
+root directory) when creating /etc/dpkg/dpkg.cfg.d/autopkgtest, otherwise
+it sets unforce-safe-io on the host instead, putting it at risk of data
+loss. Closes: #775076.
+ * Create debian/postinst and remove the file /etc/dpkg/dpkg.cfg.d/autopkgtest
+if its contents are just force-unsafe-io, indicating that this file was
+generated by the above bug.
+
+ -- Christian Kastner deb...@kvr.at Sun, 11 Jan 2015 02:04:19 +0100
+
autopkgtest (3.6) unstable; urgency=medium
[ Antonio Terceiro ]
diff -Nru autopkgtest-3.6/debian/postinst autopkgtest-3.6+nmu1/debian/postinst
--- autopkgtest-3.6/debian/postinst 1970-01-01 01:00:00.0 +0100
+++ autopkgtest-3.6+nmu1/debian/postinst2015-01-11 02:34:02.0
+0100
@@ -0,0 +1,17 @@
+#!/bin/sh
+
+set -e
+
+if [ $1 != configure ]; then
+ exit 0
+fi
+
+# If this file exists and its only content is force-unsafe-io, then it was
+# generated by #775076 and must be removed.
+if [ -e /etc/dpkg/dpkg.cfg.d/autopkgtest ]; then
+ if [ `cat /etc/dpkg/dpkg.cfg.d/autopkgtest` = force-unsafe-io ];
then
+ rm -f /etc/dpkg/dpkg.cfg.d/autopkgtest
+ fi
+fi
+
+#DEBHELPER#
diff -Nru autopkgtest-3.6/tools/adt-setup-vm
autopkgtest-3.6+nmu1/tools/adt-setup-vm
--- autopkgtest-3.6/tools/adt-setup-vm 2014-10-16 16:36:18.0 +0200
+++ autopkgtest-3.6+nmu1/tools/adt-setup-vm 2015-01-11 01:58:38.0
+0100
@@ -74,7 +74,7 @@
# go-faster apt/dpkg
echo Acquire::Languages \none\; $root/etc/apt/apt.conf.d/90nolanguages
-echo 'force-unsafe-io' /etc/dpkg/dpkg.cfg.d/autopkgtest
+echo 'force-unsafe-io' $root/etc/dpkg/dpkg.cfg.d/autopkgtest
# auto-detect apt-cacher-ng
if [ -z ${ADT_APT_PROXY:-} ]; then
Bug#774838: weboob: insecure keyring handling
Hi, and sorry for the lag, been busy with some offline things. Romain Bignon rom...@symlink.me (2015-01-08): On 08/Jan - 11:11, Cyril Brulebois wrote: I would expect the Debian packages to contain some kind of trust chain to bootstrap the keyring handling, and weboob to abort instead of “blindly accepting” in other cases. You're right we should have the official keyring distributed in the Debian package, but in case the user adds a new repository, we shouldn't reject it but ask him to accept (like ssh)? yes, that looks like a sane thing to do (possibly pointing to some instructions on how to check the trust chain). I'm going to send a patch on the package this week. Great, thanks. Mraw, KiBi. signature.asc Description: Digital signature
Processed: tagging 773829, owner 773829
Processing commands for cont...@bugs.debian.org: tags 773829 + pending Bug #773829 [src:lucene4] lucene4: JavaCC parsers are not generated during the build Added tag(s) pending. owner 773829 tmanc...@debian.org Bug #773829 [src:lucene4] lucene4: JavaCC parsers are not generated during the build Owner recorded as tmanc...@debian.org. thanks Stopping processing here. Please contact me if you need assistance. -- 773829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: user debian...@lists.debian.org, tagging 698375, tagging 767820, fixed 712699 in 0.999-1 ...
Processing commands for cont...@bugs.debian.org:
user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
tags 698375 + pending
Bug #698375 [gfs2-utils] gfs2-utils: fails to upgrade from wheezy: insserv:
script gfs2-utils: service gfs2 already provided!
Added tag(s) pending.
tags 767820 + pending
Bug #767820 [flextra] flextra: leaves alternatives after purge: /usr/bin/flextra
Added tag(s) pending.
fixed 712699 0.999-1
Bug #712699 {Done: Lionel Elie Mamane lmam...@debian.org} [libsqliteodbc]
SQLDisconnect does not propagate SQLITE_BUSY return value
Marked as fixed in versions sqliteodbc/0.999-1.
tags 712699 + pending
Bug #712699 {Done: Lionel Elie Mamane lmam...@debian.org} [libsqliteodbc]
SQLDisconnect does not propagate SQLITE_BUSY return value
Added tag(s) pending.
tags 774880 + experimental
Bug #774880 {Done: Niels Thykier ni...@thykier.net} [release.debian.org] nmu:
maya-calendar_0.3-1~experimental1
Added tag(s) experimental.
unarchive 655835
Bug #655835 {Done: Michael Meskes mes...@debian.org} [citadel-server]
postinst thinks server is not running although it is
Unarchived Bug 655835
notfound 655835 debbugs/2.4.1
Bug #655835 {Done: Michael Meskes mes...@debian.org} [citadel-server]
postinst thinks server is not running although it is
The source debbugs and version 2.4.1 do not appear to match any binary packages
No longer marked as found in versions debbugs/2.4.1.
notfound 655835 debbugs/2.4.2~exp1
Bug #655835 {Done: Michael Meskes mes...@debian.org} [citadel-server]
postinst thinks server is not running although it is
No longer marked as found in versions debbugs/2.4.2~exp1.
notfixed 717967 2.4.2~exp1
Bug #717967 [debbugs-web] debbugs-web: fails to upgrade from 'sid' - trying to
overwrite /etc/debbugs/html/server-control.html.in
No longer marked as fixed in versions 2.4.2~exp1.
unarchive 661013
Bug #661013 {Done: Gerrit Pape p...@smarden.org} [qmail] qmail: fails to purge
Bug #640593 {Done: Gerrit Pape p...@smarden.org} [qmail] qmail: package purge
(after dependencies removal) fails
Unarchived Bug 661013
Unarchived Bug 640593
notfound 661013 qmail-run/2.0.2
Bug #661013 {Done: Gerrit Pape p...@smarden.org} [qmail] qmail: fails to purge
Bug #640593 {Done: Gerrit Pape p...@smarden.org} [qmail] qmail: package purge
(after dependencies removal) fails
No longer marked as found in versions qmail-run/2.0.2.
No longer marked as found in versions qmail-run/2.0.2.
found 773494 2014.1.1-1
Bug #773494 {Done: Thomas Goirand z...@debian.org} [keystone] keystone:
cronjob exits with error after package removal
Marked as found in versions keystone/2014.1.1-1.
found 773494 2014.2.1-1
Bug #773494 {Done: Thomas Goirand z...@debian.org} [keystone] keystone:
cronjob exits with error after package removal
Marked as found in versions keystone/2014.2.1-1 and reopened.
tags 772973 + wontfix
Bug #772973 [src:nvidia-graphics-drivers-legacy-173xx]
src:nvidia-graphics-drivers*: CVE-2014-8298: GLX-INDIRECT (Including
CVE-2014-8093, CVE-2014-8098)
Added tag(s) wontfix.
tags 772972 + wontfix
Bug #772972 [src:nvidia-graphics-drivers-legacy-96xx]
src:nvidia-graphics-drivers*: CVE-2014-8298: GLX-INDIRECT (Including
CVE-2014-8093, CVE-2014-8098)
Added tag(s) wontfix.
tags 768243 + patch
Bug #768243 {Done: Jelmer Vernooij jel...@debian.org} [heimdal-clients]
heimdal-clients: leaves alternatives after purge: rcp, rsh, telnet
Added tag(s) patch.
clone 685185 -1
Bug #685185 [openjdk-6-jre] openjdk-6-jre: leaves broken alternatives: javaws,
pluginappletviewer
Bug 685185 cloned as bug 775072
reassign -1 openjdk-7-jre
Bug #775072 [openjdk-6-jre] openjdk-6-jre: leaves broken alternatives: javaws,
pluginappletviewer
Bug reassigned from package 'openjdk-6-jre' to 'openjdk-7-jre'.
No longer marked as found in versions openjdk-6/6b24-1.11.5-1 and
openjdk-6/6b24-1.11.3-2.
Ignoring request to alter fixed versions of bug #775072 to the same values
previously set
retitle -1 openjdk-7-jre: cleanup broken alternatives left by openjdk-6-jre:
javaws, pluginappletviewer
Bug #775072 [openjdk-7-jre] openjdk-6-jre: leaves broken alternatives: javaws,
pluginappletviewer
Changed Bug title to 'openjdk-7-jre: cleanup broken alternatives left by
openjdk-6-jre: javaws, pluginappletviewer' from 'openjdk-6-jre: leaves broken
alternatives: javaws, pluginappletviewer'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
640593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640593
655835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655835
661013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661013
685185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685185
698375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698375
712699: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712699
717967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717967
767820: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767820
768243:
Processed: your mail
Processing commands for cont...@bugs.debian.org: # only affects stable, not jessie/sid fixed 775056 0.40-2 Bug #775056 [python3-llfuse] python3-llfuse: package unusable due to non-existent module dependency 'Queue' Marked as fixed in versions python-llfuse/0.40-2. End of message, stopping processing here. Please contact me if you need assistance. -- 775056: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775056 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
