Bug#752605: udev: luks/lvm not detected rendering system unbootable
Am 25.06.2014 07:56, schrieb Ben Caradoc-Davies: Package: udev Version: 204-11 Severity: critical Justification: breaks the whole system Dear Maintainer, after the following dist-upgrade to udev 204-11, there was no offer to unlock luks on /dev/sda2, rendering the system unbootable. May be the same as #752591 (/dev/sda* not created) but with different symptoms as /root is on a luks/lvm volume. If you downgrade again to 204-10 and rebuild the initrd, does the system boot successfully? The only changes that were made to udev in 204-11 are [1] and [2] If so, could you both try to revert those two patches one by one, rebuild the initrd and see if that makes a change [1] http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=commitdiff;h=f11a2ddeb6a43f99179f2f9d322ee08cb41db5b0 [2] http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=commitdiff;h=abe17ab78dbf4c9fc6577492cc5b112e83a45d70 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#752605: Acknowledgement (udev: luks/lvm not detected rendering system unbootable)
Note that the affected initrd is initrd.img-3.14-1-amd64; this report references 3.13 because that is my latest bootable initrd! -- Ben Caradoc-Davies ben.caradoc-dav...@csiro.au Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752605: udev: luks/lvm not detected rendering system unbootable
Am 25.06.2014 08:21, schrieb Michael Biebl: Am 25.06.2014 07:56, schrieb Ben Caradoc-Davies: Package: udev Version: 204-11 Severity: critical Justification: breaks the whole system Dear Maintainer, after the following dist-upgrade to udev 204-11, there was no offer to unlock luks on /dev/sda2, rendering the system unbootable. May be the same as #752591 (/dev/sda* not created) but with different symptoms as /root is on a luks/lvm volume. If you downgrade again to 204-10 and rebuild the initrd, does the system boot successfully? The only changes that were made to udev in 204-11 are [1] and [2] If so, could you both try to revert those two patches one by one, rebuild the initrd and see if that makes a change Since Russel expects a timing related issue, you might also try with the rootdelay= boot parameter and setting that to something like 30 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#752605: udev: luks/lvm not detected rendering system unbootable
On 25/06/14 14:21, Michael Biebl wrote: If you downgrade again to 204-10 and rebuild the initrd, does the system boot successfully? Success! After downgrading to 204-10 with the following command (which triggers update-initramfs), the system became bootable again: dpkg -i udev_204-10_amd64.deb libudev1_204-10_amd64.deb libudev1_204-10_i386.deb The only changes that were made to udev in 204-11 are [1] and [2] If so, could you both try to revert those two patches one by one, rebuild the initrd and see if that makes a change I will try this next. Kind regards, -- Ben Caradoc-Davies ben.caradoc-dav...@csiro.au Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752605: udev: luks/lvm not detected rendering system unbootable
On 25/06/14 14:38, Ben Caradoc-Davies wrote:
The only changes that were made to udev in 204-11 are [1] and [2]
If so, could you both try to revert those two patches one by one,
rebuild the initrd and see if that makes a change
I will try this next.
Michael, manually reverting your [1] and running update-initramfs -u
allowed me to boot with udev 204-11:
[1]
http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=commitdiff;h=f11a2ddeb6a43f99179f2f9d322ee08cb41db5b0
I did not test your [2] as I do not think we are that unlucky. :-)
Kind regards,
Ben.
# dpkg -l udev libudev1
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==---=
ii libudev1:amd64 204-11 amd64libudev shared library
ii libudev1:i386 204-11 i386 libudev shared library
ii udev 204-11 amd64/dev/ and hotplug
management daem
# diff -Naur udev/80-drivers.rules /lib/udev/rules.d/80-drivers.rules
--- udev/80-drivers.rules 2014-06-25 14:43:18.856941146 +0800
+++ /lib/udev/rules.d/80-drivers.rules 2014-06-25 14:44:15.002258945 +0800
@@ -9,6 +9,6 @@
SUBSYSTEM==i2o, RUN{builtin}=kmod load i2o_block
SUBSYSTEM==module, KERNEL==parport_pc, RUN{builtin}=kmod load ppdev
KERNEL==mtd*ro, ENV{MTD_FTL}==smartmedia, RUN{builtin}=kmod load
sm_ftl
-SUBSYSTEM==scsi, ENV{DEVTYPE}==scsi_device, TEST!=[module/sg],
RUN{builtin}=kmod load sg
+SUBSYSTEM==scsi, ENV{DEVTYPE}==scsi_device, TEST!=[module/sg],
RUN+=kmod sg
LABEL=drivers_end
--
Ben Caradoc-Davies ben.caradoc-dav...@csiro.au
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752605: udev: luks/lvm not detected rendering system unbootable
Martin, could you have a look at this?
This was one of the patches you merged over from Ubuntu and it seems
that loading the sg module does break luks+crypt.
Do you remember why that patch was needed in the first place?
Am 25.06.2014 08:54, schrieb Ben Caradoc-Davies:
On 25/06/14 14:38, Ben Caradoc-Davies wrote:
The only changes that were made to udev in 204-11 are [1] and [2]
If so, could you both try to revert those two patches one by one,
rebuild the initrd and see if that makes a change
I will try this next.
Michael, manually reverting your [1] and running update-initramfs -u
allowed me to boot with udev 204-11:
[1]
http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=commitdiff;h=f11a2ddeb6a43f99179f2f9d322ee08cb41db5b0
I did not test your [2] as I do not think we are that unlucky. :-)
Kind regards,
Ben.
# dpkg -l udev libudev1
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==---=
ii libudev1:amd64 204-11 amd64libudev shared library
ii libudev1:i386 204-11 i386 libudev shared library
ii udev 204-11 amd64/dev/ and hotplug
management daem
# diff -Naur udev/80-drivers.rules /lib/udev/rules.d/80-drivers.rules
--- udev/80-drivers.rules2014-06-25 14:43:18.856941146 +0800
+++ /lib/udev/rules.d/80-drivers.rules2014-06-25 14:44:15.002258945
+0800
@@ -9,6 +9,6 @@
SUBSYSTEM==i2o, RUN{builtin}=kmod load i2o_block
SUBSYSTEM==module, KERNEL==parport_pc, RUN{builtin}=kmod load ppdev
KERNEL==mtd*ro, ENV{MTD_FTL}==smartmedia, RUN{builtin}=kmod load
sm_ftl
-SUBSYSTEM==scsi, ENV{DEVTYPE}==scsi_device, TEST!=[module/sg],
RUN{builtin}=kmod load sg
+SUBSYSTEM==scsi, ENV{DEVTYPE}==scsi_device, TEST!=[module/sg],
RUN+=kmod sg
LABEL=drivers_end
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Bug#752605: udev: luks/lvm not detected rendering system unbootable
Russel, can you confirm that that reverting the kmod load sg patch
also fixes your problem?
Am 25.06.2014 08:54, schrieb Ben Caradoc-Davies:
On 25/06/14 14:38, Ben Caradoc-Davies wrote:
The only changes that were made to udev in 204-11 are [1] and [2]
If so, could you both try to revert those two patches one by one,
rebuild the initrd and see if that makes a change
I will try this next.
Michael, manually reverting your [1] and running update-initramfs -u
allowed me to boot with udev 204-11:
[1]
http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=commitdiff;h=f11a2ddeb6a43f99179f2f9d322ee08cb41db5b0
I did not test your [2] as I do not think we are that unlucky. :-)
Kind regards,
Ben.
# dpkg -l udev libudev1
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==---=
ii libudev1:amd64 204-11 amd64libudev shared library
ii libudev1:i386 204-11 i386 libudev shared library
ii udev 204-11 amd64/dev/ and hotplug
management daem
# diff -Naur udev/80-drivers.rules /lib/udev/rules.d/80-drivers.rules
--- udev/80-drivers.rules2014-06-25 14:43:18.856941146 +0800
+++ /lib/udev/rules.d/80-drivers.rules2014-06-25 14:44:15.002258945
+0800
@@ -9,6 +9,6 @@
SUBSYSTEM==i2o, RUN{builtin}=kmod load i2o_block
SUBSYSTEM==module, KERNEL==parport_pc, RUN{builtin}=kmod load ppdev
KERNEL==mtd*ro, ENV{MTD_FTL}==smartmedia, RUN{builtin}=kmod load
sm_ftl
-SUBSYSTEM==scsi, ENV{DEVTYPE}==scsi_device, TEST!=[module/sg],
RUN{builtin}=kmod load sg
+SUBSYSTEM==scsi, ENV{DEVTYPE}==scsi_device, TEST!=[module/sg],
RUN+=kmod sg
LABEL=drivers_end
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Bug#752610: lynx: Can connect to CVE-2014-1959 test site
Package: lynx-cur, libgnutls26 Severity: serious Tags: security Hi, There is a test site for checking the gnutls bug: https://gnutls.notary.icsi.berkeley.edu/ I can connect to it and get the message: If you see this without getting a certificate error you are vulnerable against the GnuTLS bug I can reproduce this with the following combinations: stable: ii libgnutls26:amd64 2.12.20-8+deb7u2 ii lynx-cur 2.8.8dev.12-2 And testing: ii libgnutls26:amd64 2.12.23-16 ii lynx-cur 2.8.8pre5-1 Using gnutls-bin gnutls-bin 3.0.22-3+really2.12.20-8+deb7u2 I also get: $ gnutls-cli -p 443 gnutls.notary.icsi.berkeley.edu --x509cafile /etc/ssl/certs/ca-certificates.crt Processed 159 CA certificate(s). Resolving 'gnutls.notary.icsi.berkeley.edu'... Connecting to '192.150.187.13:443'... *** Verifying server certificate failed... *** Fatal error: Error in the certificate. *** Handshake has failed GnuTLS error: Error in the certificate. While with 3.3.2-2 I get: $ gnutls-cli -p 443 gnutls.notary.icsi.berkeley.edu --x509cafile /etc/ssl/certs/ca-certificates.crt Processed 168 CA certificate(s). Resolving 'gnutls.notary.icsi.berkeley.edu'... Connecting to '192.150.187.13:443'... - Certificate type: X.509 - Got a certificate list of 2 certificates. - Certificate[0] info: - subject `CN=gnutls.notary.icsi.berkeley.edu,OU=ICSI GnuTLS Crt,O=ICSI GnuTLS Test Cert.', issuer `C=US,ST=Arizona,L=Scottsdale,O=GoDaddy.com\, Inc.,OU=http://certificates.godaddy.com/repository,CN=Go Daddy Secure Certification Authority,serialNumber=07969287', RSA key 2048 bits, signed using RSA-SHA1, activated `2010-08-28 14:51:35 UTC', expires `2015-08-28 14:51:35 UTC', SHA-1 fingerprint `b20c942cd0dd72cd5a02b697ba6862064727f3d9' Public Key ID: c9952718d6b2c42cd432b9d8c0f0730ab3286c9d Public key's random art: +--[ RSA 2048]+ | .o ..=o. | | .o =.*o.. | | o o+.*.o+ .| |...+o+o..o o | |oo.E. S| |o| | | | | | | +-+ - Certificate[1] info: - subject `C=US,ST=Arizona,L=Scottsdale,O=GoDaddy.com\, Inc.,OU=http://certificates.godaddy.com/repository,CN=Go Daddy Secure Certification Authority,serialNumber=07969287', issuer `C=US,O=The Go Daddy Group\, Inc.,OU=Go Daddy Class 2 Certification Authority', RSA key 2048 bits, signed using RSA-SHA1, activated `2006-11-16 01:54:37 UTC', expires `2026-11-16 01:54:37 UTC', SHA-1 fingerprint `7c4656c3061f7f4c0d67b319a855f60ebc11fc44' - Status: The certificate is NOT trusted. The certificate issuer is not a CA. *** PKI verification of server certificate failed... *** Fatal error: Error in the certificate. *** Handshake has failed GnuTLS error: Error in the certificate. The 3.3.2-2 version is linked to libgnutls28 of course. Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752605: udev: luks/lvm not detected rendering system unbootable
I restored /lib/udev/rules.d/80-drivers.rules to that shipped with 204-11 and tried rootdelay=30 on the command line; this had no effect other than introducing a delay in the boot process. There was still no passphrase prompt. On 25/06/14 14:39, Michael Biebl wrote: Since Russel expects a timing related issue, you might also try with the rootdelay= boot parameter and setting that to something like 30 -- Ben Caradoc-Davies ben.caradoc-dav...@csiro.au Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749974: I would like to renew my request to delay the removal of maitreya from testing.
[Cc-ing #749974 since that's the relevant bug] Thanks for your work on this, Paul. On Wed, Jun 25, 2014 at 12:40:15AM -0500, Paul Elliott wrote: BUT! I have just checked packages.debian.org and I find that libwxsqlite3-3.0-dev which the new version of maitreya will depend on is still in experimental! Uploading libwxsqlite3 to unstable would start the transition, so we're currently waiting for the reverse dependencies to be ready. Since codelite has been ready for while, that means we're waiting for guayadeque and ... you. There's a partial patch from dmn for guayadeque, but no maintainer response so far. Even if it were released to unstable immeadiately, it would take at least 10 days, by my understanding, for it to reach testing, and then 10 days for maitreya to follow. As Niels says, the default urgency is now medium, which means 5 days, and both packages could age concurrently rather than consecutively, so it could actually just be 5 days if both were uploaded simultaneously. As he also says, the timer gets reset if you post a status update to the ticket. I plan to grab the source for libwxsqlite3-3.0-dev from testing and see if I can get it to build under unstable. ^experimental? You should just be able to build maitreya in an unstable chroot set up to use experimental for packages which can't be provided by unstable (due to a versioned BD or unstable not having the package). Exactly how to set that up depends on what tool you're using to do the building in a clean chroot. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752605: udev: luks/lvm not detected rendering system unbootable
Russell, for your convenience I have attached the patch as a file to
prevent line wrapping (or patch may reject it). You can apply it with:
cd /
patch -p0 /path/to/where/you/save/80-drivers.rules.patch
update-initramfs -u
Kind regards,
Ben.
On 25/06/14 15:02, Michael Biebl wrote:
Russel, can you confirm that that reverting the kmod load sg patch
also fixes your problem?
--
Ben Caradoc-Davies ben.caradoc-dav...@csiro.au
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
--- udev.broken/80-drivers.rules 2014-06-25 14:43:18.856941146 +0800
+++ /lib/udev/rules.d/80-drivers.rules 2014-06-25 15:00:04.024702481 +0800
@@ -9,6 +9,6 @@
SUBSYSTEM==i2o, RUN{builtin}=kmod load i2o_block
SUBSYSTEM==module, KERNEL==parport_pc, RUN{builtin}=kmod load ppdev
KERNEL==mtd*ro, ENV{MTD_FTL}==smartmedia, RUN{builtin}=kmod load sm_ftl
-SUBSYSTEM==scsi, ENV{DEVTYPE}==scsi_device, TEST!=[module/sg], RUN{builtin}=kmod load sg
+SUBSYSTEM==scsi, ENV{DEVTYPE}==scsi_device, TEST!=[module/sg], RUN+=kmod sg
LABEL=drivers_end
Bug#752605: udev: luks/lvm not detected rendering system unbootable
Am 25.06.2014 07:56, schrieb Ben Caradoc-Davies:
Package: udev
Version: 204-11
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
after the following dist-upgrade to udev 204-11, there was no offer to unlock
luks on /dev/sda2, rendering the system unbootable. May be the same as #752591
(/dev/sda* not created) but with different symptoms as /root is on a luks/lvm
volume.
FYI, I've just setup a test-VM with luks/lvm and was not able to
reproduce the problem, so I'm a bit stuck with debugging this further.
Ben, could you include your /etc/{fstab,crypttab}
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Bug#752605: udev: luks/lvm not detected rendering system unbootable
On 25/06/14 15:21, Michael Biebl wrote:
Ben, could you include your/etc/{fstab,crypttab}
Attached.
It is also worth noting that I am running sysvinit with systemd-shim.
Note sure how this changes the contents of initrd.
Kind regards,
--
Ben Caradoc-Davies ben.caradoc-dav...@csiro.au
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
/dev/mapper/vg-root / ext4noatime,errors=remount-ro
0 1
/dev/sda1 /boot ext4noatime,errors=remount-ro
0 2
/dev/mapper/vg-home /home ext4noatime,errors=remount-ro
0 2
LABEL=Backup/media/backup ext4
noatime,noauto,user,errors=remount-ro 0 0
LABEL=Thumb /media/thumbvfat
noatime,noauto,user,uid=1000,gid=1000,umask=007,utf8,flush0 0
LABEL=Android /media/android vfat
noatime,noauto,user,uid=1000,gid=1000,umask=007,utf8,flush0 0
LABEL=Debian/media/debian vfat
noatime,noauto,user,uid=1000,gid=1000,umask=007,utf8,flush0 0
sdb2_crypt UUID=24ebefb2-cda5-4d72-a90a-5f95ee091410 none luks
Bug#752605: udev: luks/lvm not detected rendering system unbootable
forcemerge 752591 752605 severity 752591 critical thanks Am 25.06.2014 09:21, schrieb Michael Biebl: Am 25.06.2014 07:56, schrieb Ben Caradoc-Davies: Package: udev Version: 204-11 Severity: critical Justification: breaks the whole system Dear Maintainer, after the following dist-upgrade to udev 204-11, there was no offer to unlock luks on /dev/sda2, rendering the system unbootable. May be the same as #752591 (/dev/sda* not created) but with different symptoms as /root is on a luks/lvm volume. FYI, I've just setup a test-VM with luks/lvm and was not able to reproduce the problem, so I'm a bit stuck with debugging this further. Some progress: Could reproduce the issue on another system, physical hardware. It's not using luks/lvm, so this is a general issue. I was dropped into the rescue shell and same as Russel, I had no /dev/sda devices. I noticed that the sd_mod module, the SCSI disk driver module, was not loaded. Manually loading that allowed me to successfully boot. So it looks like manually loading the sg module from within the 80-drivers.rules udev rule under certain circumstances prevents sd_mod from being loaded. As no /dev/sd* devices then show up, that would also explain why you never see the luks unlock prompt. I'm pretty sure it's the same bug, so I'm going the merge the two. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#752605: udev: luks/lvm not detected rendering system unbootable
Processing commands for cont...@bugs.debian.org: forcemerge 752591 752605 Bug #752591 [udev] udev: initrd fails to create /dev/sda* after udev upgrade Bug #752605 [udev] udev: luks/lvm not detected rendering system unbootable Severity set to 'important' from 'critical' Merged 752591 752605 severity 752591 critical Bug #752591 [udev] udev: initrd fails to create /dev/sda* after udev upgrade Bug #752605 [udev] udev: luks/lvm not detected rendering system unbootable Severity set to 'critical' from 'important' Severity set to 'critical' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 752591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752591 752605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752605 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#750233: Upload of python-networkx 1.9
Hi, As per #750233, I have uploaded python-networkx 1.9 in the DELAYED/2 queue. Considering the currently opened RC bug (ie: #750233), I couldn't wait for too long, otherwise risking AUTORM of some of my packages. The changelog is as follow: * Team upload. * New upstream release (Closes: #750233). * Ran wrap-and-sort. * debian/copyright in parseable format 1.0. * Added extend-diff-ignore = ^[^/]*[.]egg-info/ in d/source/options, and removed the clean of the egg-info folder. * Refreshed/rebased 10_doc_relocation, 20_example_dirs_remove and 30_use_local_objects.inv patches. * Removed 50_force_ordering_in_dict_to_numpy_array_functions.patch 55_fixups_to_numpy_array_functions_patch.patch 60_fix_tests_failure_due_to_py3.3_hash_randomization.patch applied upstream. * debian/control: removed python-support and added dh-python as build-dep. * Added python-3.4.patch (comes from the Ubuntu package). * Removed 40_no_setuptools_in_requires.txt (there's no setup_egg.py anymore in upstream source code). * Also cleans networkx/version.py, which is generated. * Also cleans test.*, doc/source/templates/gallery.html and fontList.cache. * Added do-not-use-sphinx_rtd_theme.patch. * debian/rules: do not use setup_egg.py, it's gone from upstream source. * Move all the doc generation stuff into the override_dh_sphinxdoc. * Removed obsolete XS-Python-Version: = 2.6 X-Python3-Version: = 3.2. * Adds using-local-mathjax.js.patch to avoid privacy breach in the doc. * Added missing --with python2. * Added debian/rules get-orig-src target to generate the orig.tar.xz file. * Added missing build-depends: python-decorator and python-numpydoc (needed for building docs). * Fixed watch file to handle the +dfsg1 mangling. I first tried to make the changes minimal, but it simply wasn't possible in this case. There was just too many things to do to have a working package. I tested building in a cowbuilder and it went fine. I also tested rebuilding some of the reverse dependencies that I knew were unit testing with networkx, and it went fine too. Note that since the pypi tarball was huge for no reason (it contained generated files from the documentation build process, leading to 35 MB of stuff instead of less than 1), so I used the git tag from github instead, to generate the orig.tar.xz. In the process I also cleaned some non-free files (minimized javascript). The process is now documented in debian/rules. [It would probably be best to have it done in a debian/repack file, using the watch file though, but I have no time for that yet.] If anyone opposes to this upload, it can be reverted/dcut. The diff of the debian folder is attached (missing the watch file fixes for the +dfsg1 handling). Cheers, Thomas Goirand (zigo) diff -u -N -r python-networkx-1.8.1/debian/changelog trunk/debian/changelog --- python-networkx-1.8.1/debian/changelog 2014-01-18 11:26:50.0 + +++ trunk/debian/changelog 2014-06-23 12:05:18.0 + @@ -1,3 +1,35 @@ +python-networkx (1.9+dfsg1-1) unstable; urgency=medium + + * Team upload. + * New upstream release. + * Ran wrap-and-sort. + * debian/copyright in parseable format 1.0. + * Added extend-diff-ignore = ^[^/]*[.]egg-info/ in d/source/options, and +removed the clean of the egg-info folder. + * Refreshed/rebased 10_doc_relocation, 20_example_dirs_remove and +30_use_local_objects.inv patches. + * Removed 50_force_ordering_in_dict_to_numpy_array_functions.patch +55_fixups_to_numpy_array_functions_patch.patch +60_fix_tests_failure_due_to_py3.3_hash_randomization.patch applied +upstream. + * debian/control: removed python-support and added dh-python as build-dep. + * Added python-3.4.patch (comes from the Ubuntu package). + * Removed 40_no_setuptools_in_requires.txt (there's no setup_egg.py anymore +in upstream source code). + * Also cleans networkx/version.py, which is generated. + * Also cleans test.*, doc/source/templates/gallery.html and fontList.cache. + * Added do-not-use-sphinx_rtd_theme.patch. + * debian/rules: do not use setup_egg.py, it's gone from upstream source. + * Move all the doc generation stuff into the override_dh_sphinxdoc. + * Removed obsolete XS-Python-Version: = 2.6 X-Python3-Version: = 3.2. + * Adds using-local-mathjax.js.patch to avoid privacy breach in the doc. + * Added missing --with python2. + * Added debian/rules get-orig-src target to generate the orig.tar.xz file. + * Added missing build-depends: python-decorator and python-numpydoc (needed +for building docs). + + -- Thomas Goirand z...@debian.org Sun, 22 Jun 2014 07:11:42 + + python-networkx (1.8.1-1) unstable; urgency=low [ Jakub Wilk ] diff -u -N -r python-networkx-1.8.1/debian/control trunk/debian/control --- python-networkx-1.8.1/debian/control 2014-01-18 11:18:01.0 + +++ trunk/debian/control 2014-06-23 11:53:41.0 + @@ -4,10 +4,29 @@ Maintainer: Debian Python Modules Team python-modules-t...@lists.alioth.debian.org Uploaders:
Processed: cloning 728196, reassign -1 to smarty3 ..., reassign -2 to moodle ..., reassign -3 to php-net-ipv4 ...
Processing commands for cont...@bugs.debian.org: clone 728196 -1 -2 -3 -4 -5 Bug #728196 [src:php-gearman] php-gearman is licensed under the PHP license, and is not PHP Bug 728196 cloned as bugs 752614-752618 reassign -1 smarty3 Bug #752614 [src:php-gearman] php-gearman is licensed under the PHP license, and is not PHP Bug reassigned from package 'src:php-gearman' to 'smarty3'. Ignoring request to alter found versions of bug #752614 to the same values previously set Ignoring request to alter fixed versions of bug #752614 to the same values previously set retitle -1 smarty3 is licensed under the PHP license and is not PHP Bug #752614 [smarty3] php-gearman is licensed under the PHP license, and is not PHP Changed Bug title to 'smarty3 is licensed under the PHP license and is not PHP' from 'php-gearman is licensed under the PHP license, and is not PHP' reassign -2 moodle Bug #752615 [src:php-gearman] php-gearman is licensed under the PHP license, and is not PHP Bug reassigned from package 'src:php-gearman' to 'moodle'. Ignoring request to alter found versions of bug #752615 to the same values previously set Ignoring request to alter fixed versions of bug #752615 to the same values previously set retitle -2 moodle is licensed under the PHP license and is not PHP Bug #752615 [moodle] php-gearman is licensed under the PHP license, and is not PHP Changed Bug title to 'moodle is licensed under the PHP license and is not PHP' from 'php-gearman is licensed under the PHP license, and is not PHP' reassign -3 php-net-ipv4 Bug #752616 [src:php-gearman] php-gearman is licensed under the PHP license, and is not PHP Bug reassigned from package 'src:php-gearman' to 'php-net-ipv4'. Ignoring request to alter found versions of bug #752616 to the same values previously set Ignoring request to alter fixed versions of bug #752616 to the same values previously set retitle -3 php-net-ipv4 is licensed under the PHP license and is not PHP Bug #752616 [php-net-ipv4] php-gearman is licensed under the PHP license, and is not PHP Changed Bug title to 'php-net-ipv4 is licensed under the PHP license and is not PHP' from 'php-gearman is licensed under the PHP license, and is not PHP' reassign -4 php-html-common Bug #752617 [src:php-gearman] php-gearman is licensed under the PHP license, and is not PHP Bug reassigned from package 'src:php-gearman' to 'php-html-common'. Ignoring request to alter found versions of bug #752617 to the same values previously set Ignoring request to alter fixed versions of bug #752617 to the same values previously set retitle -4 php-html-common is licensed under the PHP license and is not PHP Bug #752617 [php-html-common] php-gearman is licensed under the PHP license, and is not PHP Changed Bug title to 'php-html-common is licensed under the PHP license and is not PHP' from 'php-gearman is licensed under the PHP license, and is not PHP' reassign -5 php-numbers-words Bug #752618 [src:php-gearman] php-gearman is licensed under the PHP license, and is not PHP Bug reassigned from package 'src:php-gearman' to 'php-numbers-words'. Ignoring request to alter found versions of bug #752618 to the same values previously set Ignoring request to alter fixed versions of bug #752618 to the same values previously set retitle -5 php-numbers-words is licensed under the PHP license and is not PHP Bug #752618 [php-numbers-words] php-gearman is licensed under the PHP license, and is not PHP Changed Bug title to 'php-numbers-words is licensed under the PHP license and is not PHP' from 'php-gearman is licensed under the PHP license, and is not PHP' thanks Stopping processing here. Please contact me if you need assistance. -- 728196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728196 752614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752614 752615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752615 752616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752616 752617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752617 752618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752618 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#752615: PHP Licensed files...
# grep -r PHP License . ./lib/pear/HTML/QuickForm/DHTMLRulesTableless.php: * the PHP License and are unable to obtain it through the web, please ./lib/pear/HTML/QuickForm/DHTMLRulesTableless.php: * @license http://www.php.net/license/3_01.txt PHP License 3.01 ./lib/pear/HTML/QuickForm/DHTMLRulesTableless.php: * @license http://www.php.net/license/3_01.txt PHP License 3.01 ./lib/pear/HTML/QuickForm/Renderer/Tableless.php: * the PHP License and are unable to obtain it through the web, please ./lib/pear/HTML/QuickForm/Renderer/Tableless.php: * @license http://www.php.net/license/3_01.txt PHP License 3.01 ./lib/pear/HTML/QuickForm/Renderer/Tableless.php: * @license http://www.php.net/license/3_01.txt PHP License 3.01 O. -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752591: Bug#752605: udev: luks/lvm not detected rendering system unbootable
Some updates after more debugging.
The original rule was
SUBSYSTEM==scsi, ENV{DEVTYPE}==scsi_device, TEST!=[module/sg], \
RUN+=/sbin/modprobe -b sg
and was added to fix [1].
Apparently this didn't cause any issues so far.
This was then modified to use the kmod load builtin in 204-11.
This is a new facility which is much faster. So this changed the timing
when loading the module.
We suspect, that loading sg *before* the SCSI subsystem has finished
doing the probing and detection and is what's causing the sd_mod to not
be loaded.
Reverting back to modprobe would be a possible workaround, as this would
change back the timing to the old behaviour.
We still would have a race, though, but apparently more unlikely to
cause any issues.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657948
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Bug#752591: Bug#752605: udev: luks/lvm not detected rendering system unbootable
Hello all,
Michael Biebl [2014-06-25 9:01 +0200]:
This was one of the patches you merged over from Ubuntu and it seems
that loading the sg module does break luks+crypt.
Do you remember why that patch was needed in the first place?
No, it didn't come from Ubuntu, but this has been a Debian specific
udev rule for years. It came from https://bugs.debian.org/657948 to
support tape drives with sd and sg built as modules, as done by the
Debian kernel. (FTR, Ubuntu's kernel has both built in and doesn't
need any of this).
E. g. in wheezy the rule looked like
SUBSYSTEM==scsi, ENV{DEVTYPE}==scsi_device, TEST!=[module/sg],
RUN+=/sbin/modprobe -b sg
So the main change was that we now use the kmod builtin instead of
calling modprobe. The latter is much slower, and thus I suppose this
delayed sg long enough for the sd module to actually detect and grab
the SCSI disks. From that POV it's rather curious that this never led
to boot problems before (or at least not up to the point where people
filed bugs).
So I propose for now to go back to modprobe. It's a disaster waiting
to happen, but apparently it has worked for many years so let's go
back to a known-working state. I'll do that change in git now.
Thanks, and sorry for the trouble! (Yay race conditions)
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
Bug#752591: Bug#752605: udev: luks/lvm not detected rendering system unbootable
On Wed, 25 Jun 2014 09:02:59 Michael Biebl wrote: Russel, can you confirm that that reverting the kmod load sg patch also fixes your problem? It seems to. Booted once since applying it and it worked. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/ signature.asc Description: This is a digitally signed message part.
Bug#744708: [Pkg-graphite-maint] Bug#744708: graphite-web removed from testing
Hello, yes, but I'm very busy with my day job. It's on my todo list, will do it asap. OK. I understand, this is sometimes hard to keep a package up to date and RC-free. I have added the missing sources of ExtJS. I can't use the extjs package that is available in the archive, because it's a different version. Now only the sources of ace is missing. I did not figure out, which version is used. I will try it and also write the original committer of ACE a mail to ask him. Greets, Jonas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 752591
Processing commands for cont...@bugs.debian.org: tags 752591 + pending Bug #752591 [udev] udev: initrd fails to create /dev/sda* after udev upgrade Bug #752605 [udev] udev: luks/lvm not detected rendering system unbootable Added tag(s) pending. Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 752591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752591 752605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752605 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#752591: Bug#752605: udev: luks/lvm not detected rendering system unbootable
Am 25.06.2014 10:20, schrieb Martin Pitt:
E. g. in wheezy the rule looked like
SUBSYSTEM==scsi, ENV{DEVTYPE}==scsi_device, TEST!=[module/sg],
RUN+=/sbin/modprobe -b sg
So the main change was that we now use the kmod builtin instead of
calling modprobe. The latter is much slower, and thus I suppose this
delayed sg long enough for the sd module to actually detect and grab
the SCSI disks. From that POV it's rather curious that this never led
to boot problems before (or at least not up to the point where people
filed bugs).
So I propose for now to go back to modprobe. It's a disaster waiting
to happen, but apparently it has worked for many years so let's go
back to a known-working state. I'll do that change in git now.
Ben, Russel: I'm about to make the upload with the change Martin
mentioned, but it would be great if you can confirm that using
SUBSYSTEM==scsi, ENV{DEVTYPE}==scsi_device, TEST!=[module/sg],
RUN+=/sbin/modprobe -b sg
actually works for you as well.
Can you please re-add above rule to 80-drivers.rule and test again.
Thanks,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Bug#752591: Bug#752605: udev: luks/lvm not detected rendering system unbootable
On 25/06/14 17:00, Michael Biebl wrote:
Ben, Russel: I'm about to make the upload with the change Martin
mentioned, but it would be great if you can confirm that using
SUBSYSTEM==scsi, ENV{DEVTYPE}==scsi_device, TEST!=[module/sg],
RUN+=/sbin/modprobe -b sg
actually works for you as well.
Can you please re-add above rule to 80-drivers.rule and test again.
Michael,
I can confirm that this variant works for me as well.
Kind regards,
--
Ben Caradoc-Davies ben.caradoc-dav...@csiro.au
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739664: marked as done (libavg: FTBFS with libav 10)
Your message dated Wed, 25 Jun 2014 09:35:53 +
with message-id e1wzjcp-0002af...@franck.debian.org
and subject line Bug#739664: fixed in libavg 1.8.1-1
has caused the Debian Bug report #739664,
regarding libavg: FTBFS with libav 10
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.)
--
739664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: libavg
Version: 1.8.0-1
Severity: important
Tags: sid jessie
User: j...@debian.org
Usertags: libav10
libavg fails to build from source gainst libav 10 (currently available
in experimental):
| In file included from AudioDecoderThread.cpp:24:0:
| AudioDecoderThread.h:72:9: error: 'ReSampleContext' does not name a type
| ReSampleContext * m_pResampleContext;
| ^
| AudioDecoderThread.cpp: In constructor
'avg::AudioDecoderThread::AudioDecoderThread(avg::WorkerThreadavg::AudioDecoderThread::CQueue,
avg::AudioMsgQueue, avg::VideoMsgQueue, AVStream*, const avg::AudioParams)':
| AudioDecoderThread.cpp:49:7: error: class 'avg::AudioDecoderThread' does not
have any field named 'm_pResampleContext'
|m_pResampleContext(0),
|^
| AudioDecoderThread.cpp: In destructor 'virtual
avg::AudioDecoderThread::~AudioDecoderThread()':
| AudioDecoderThread.cpp:64:9: error: 'm_pResampleContext' was not declared in
this scope
| if (m_pResampleContext) {
| ^
| AudioDecoderThread.cpp:65:48: error: 'audio_resample_close' was not declared
in this scope
| audio_resample_close(m_pResampleContext);
| ^
| AudioDecoderThread.cpp: In member function 'void
avg::AudioDecoderThread::decodePacket(AVPacket*)':
| AudioDecoderThread.cpp:133:43: error: 'avcodec_decode_audio3' was not
declared in this scope
| bytesDecoded, pTempPacket);
|^
| AudioDecoderThread.cpp: In member function 'avg::AudioBufferPtr
avg::AudioDecoderThread::resampleAudio(char*, int, int)':
| AudioDecoderThread.cpp:224:10: error: 'm_pResampleContext' was not declared
in this scope
| if (!m_pResampleContext) {
| ^
| AudioDecoderThread.cpp:228:87: error: 'av_audio_resample_init' was not
declared in this scope
| SAMPLE_FMT_S16, (SampleFormat)currentSampleFormat, 16, 10,
0, 0.8);
|
^
| AudioDecoderThread.cpp:237:42: error: 'm_pResampleContext' was not declared
in this scope
| int framesResampled = audio_resample(m_pResampleContext, pResampledData,
| ^
| AudioDecoderThread.cpp:238:48: error: 'audio_resample' was not declared in
this scope
| (short*)pDecodedData, framesDecoded);
| ^
| make[4]: *** [AudioDecoderThread.lo] Error 1
Full build log is available at
http://people.debian.org/~sramacher/logs/libav10/libavg_1.8.0-1_amd64-20140221-0241.log
This bug will become release-critical at some point when the libav10
transition starts. Migration documentation can be found at
https://wiki.libav.org/Migration/10.
Regards
--
Sebastian Ramacher
signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: libavg
Source-Version: 1.8.1-1
We believe that the bug you reported is fixed in the latest version of
libavg, 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 739...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dimitri John Ledkov x...@ubuntu.com (supplier of updated libavg 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: Tue, 24 Jun 2014 20:05:13 +0100
Source: libavg
Binary: python-libavg
Architecture: amd64 source
Version: 1.8.1-1
Distribution: unstable
Urgency: medium
Maintainer: Dimitri John Ledkov x...@debian.org
Changed-By: Dimitri John Ledkov x...@ubuntu.com
Closes: 739664
Description:
python-libavg - High-level development platform for media-centric applications
Changes:
libavg (1.8.1-1) unstable; urgency=medium
.
* New upstream release
Bug#752625: gambas3: combines code released under GPL and GPL-incompatible licenses (PHP license)
Source: gambas3 Version: 3.5.2-2 Severity: serious gambas3 combines code released under the GPL with code released under the PHP license in main/lib/image/image_stat.c. As the GPL and PHP license are incompatible[1], this makes the package not distributable. [1] https://www.gnu.org/licenses/license-list.html#PHP-3.01 Ansgar -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752627: zabbix: combines code released under GPL and GPL-incompatible licenses (PHP license)
Source: zabbix Version: 1:2.2.3+dfsg-1 Severity: serious zabbix combines code released under the GPL with code released under the PHP license in src/libs/zbxsys/mutexs.c. (The PHP license is not included in the header, but somewhere below.) As the GPL and PHP license are incompatible[1], this makes the package not distributable. [1] https://www.gnu.org/licenses/license-list.html#PHP-3.01 Ansgar -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: cloning 728196, reassign -1 to libexpect-php5 ..., reassign -2 to ming ..., reassign -3 to php-auth ...
Processing commands for cont...@bugs.debian.org: clone 728196 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 -14 -15 -16 -17 -18 -19 -20 -21 -22 -23 -24 -25 -26 -27 -28 Bug #728196 [src:php-gearman] php-gearman is licensed under the PHP license, and is not PHP Bug 728196 cloned as bugs 752628-752655 reassign -1 libexpect-php5 Bug #752628 [src:php-gearman] php-gearman is licensed under the PHP license, and is not PHP Bug reassigned from package 'src:php-gearman' to 'libexpect-php5'. Ignoring request to alter found versions of bug #752628 to the same values previously set Ignoring request to alter fixed versions of bug #752628 to the same values previously set retitle -1 libexpect-php5 is licensed under the PHP license and is not PHP Bug #752628 [libexpect-php5] php-gearman is licensed under the PHP license, and is not PHP Changed Bug title to 'libexpect-php5 is licensed under the PHP license and is not PHP' from 'php-gearman is licensed under the PHP license, and is not PHP' reassign -2 ming Bug #752629 [src:php-gearman] php-gearman is licensed under the PHP license, and is not PHP Bug reassigned from package 'src:php-gearman' to 'ming'. Ignoring request to alter found versions of bug #752629 to the same values previously set Ignoring request to alter fixed versions of bug #752629 to the same values previously set retitle -2 ming is licensed under the PHP license and is not PHP Bug #752629 [ming] php-gearman is licensed under the PHP license, and is not PHP Changed Bug title to 'ming is licensed under the PHP license and is not PHP' from 'php-gearman is licensed under the PHP license, and is not PHP' reassign -3 php-auth Bug #752630 [src:php-gearman] php-gearman is licensed under the PHP license, and is not PHP Bug reassigned from package 'src:php-gearman' to 'php-auth'. Ignoring request to alter found versions of bug #752630 to the same values previously set Ignoring request to alter fixed versions of bug #752630 to the same values previously set retitle -3 php-auth is licensed under the PHP license and is not PHP Bug #752630 [php-auth] php-gearman is licensed under the PHP license, and is not PHP Changed Bug title to 'php-auth is licensed under the PHP license and is not PHP' from 'php-gearman is licensed under the PHP license, and is not PHP' reassign -4 php-auth-http Bug #752631 [src:php-gearman] php-gearman is licensed under the PHP license, and is not PHP Bug reassigned from package 'src:php-gearman' to 'php-auth-http'. Ignoring request to alter found versions of bug #752631 to the same values previously set Ignoring request to alter fixed versions of bug #752631 to the same values previously set retitle -4 php-auth-http is licensed under the PHP license and is not PHP Bug #752631 [php-auth-http] php-gearman is licensed under the PHP license, and is not PHP Changed Bug title to 'php-auth-http is licensed under the PHP license and is not PHP' from 'php-gearman is licensed under the PHP license, and is not PHP' reassign -5 php-cache Bug #752632 [src:php-gearman] php-gearman is licensed under the PHP license, and is not PHP Bug reassigned from package 'src:php-gearman' to 'php-cache'. Ignoring request to alter found versions of bug #752632 to the same values previously set Ignoring request to alter fixed versions of bug #752632 to the same values previously set retitle -5 php-cache is licensed under the PHP license and is not PHP Bug #752632 [php-cache] php-gearman is licensed under the PHP license, and is not PHP Changed Bug title to 'php-cache is licensed under the PHP license and is not PHP' from 'php-gearman is licensed under the PHP license, and is not PHP' reassign -6 php-compat Bug #752633 [src:php-gearman] php-gearman is licensed under the PHP license, and is not PHP Bug reassigned from package 'src:php-gearman' to 'php-compat'. Ignoring request to alter found versions of bug #752633 to the same values previously set Ignoring request to alter fixed versions of bug #752633 to the same values previously set retitle -6 php-compat is licensed under the PHP license and is not PHP Bug #752633 [php-compat] php-gearman is licensed under the PHP license, and is not PHP Changed Bug title to 'php-compat is licensed under the PHP license and is not PHP' from 'php-gearman is licensed under the PHP license, and is not PHP' reassign -7 php-config Bug #752634 [src:php-gearman] php-gearman is licensed under the PHP license, and is not PHP Bug reassigned from package 'src:php-gearman' to 'php-config'. Ignoring request to alter found versions of bug #752634 to the same values previously set Ignoring request to alter fixed versions of bug #752634 to the same values previously set retitle -7 php-config is licensed under the PHP license and is not PHP Bug #752634 [php-config] php-gearman is licensed under the PHP license, and is not PHP Changed Bug title to 'php-config is licensed under the PHP license and is not PHP' from 'php-gearman is licensed under the PHP
Bug#750317: marked as done (hyena: FTBFS: Makefile:501: *** missing separator (did you mean TAB instead of 8 spaces?))
Your message dated Wed, 25 Jun 2014 13:29:45 +0300 with message-id 1403692185.23471.6.camel@hunt and subject line Marking #750317 fixed in hyena/0.5-3 has caused the Debian Bug report #750317, regarding hyena: FTBFS: Makefile:501: *** missing separator (did you mean TAB instead of 8 spaces?) 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.) -- 750317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: hyena Version: 0.5-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140601 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[4]: Entering directory '/«PKGBUILDDIR»/build' make[4]: Nothing to be done for 'all-am'. make[4]: Leaving directory '/«PKGBUILDDIR»/build' /usr/bin/mono-csc -out:dll-map-verifier.exe DllMapVerifier.cs /usr/bin/mono-csc -r:System.Xml -out:addin-xml-string-extractor.exe AddinXmlStringExtractor.cs /usr/bin/mono-csc -r:/usr/lib/pkgconfig/../../lib/cli/glib-sharp-2.0/glib-sharp.dll -out:gobject-intptr-ctor-verifier.exe GObjectIntPtrCtorVerifier.cs make[3]: Leaving directory '/«PKGBUILDDIR»/build' Making all in Hyena make[3]: Entering directory '/«PKGBUILDDIR»/Hyena' Makefile:501: *** missing separator (did you mean TAB instead of 8 spaces?). Stop. make[3]: Leaving directory '/«PKGBUILDDIR»/Hyena' make[2]: *** [all-recursive] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/06/01/hyena_0.5-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Version: 0.5-3 I believe this RC bug was fixed in hyena/0.5-3. This is its changelog entry. hyena (0.5-3) unstable; urgency=medium [ Iain Lane ] * [00efaea] Fix syntax error in monodoc source file [ Chow Loong Jin ] * [5b03afe] Patch to fix build failure caused by dnl lines in Makefile * [f73eddf] Use dh-autoreconf * [212c5a4] Drop usage of deprecated cli.make * [a64752c] Update my email address in Uploaders * [5fc3a7d] Bump Standards-Version to 3.9.5 (no changes required) -- Chow Loong Jin hyper...@debian.org Tue, 17 Jun 2014 16:40:13 +0800 Best Regards, Juhani Numminen---End Message---
Processed (with 1 errors): your mail
Processing commands for cont...@bugs.debian.org: forwarded 752625 https://code.google.com/p/gambas/issues/detail?id=531 Bug #752625 [src:gambas3] gambas3: combines code released under GPL and GPL-incompatible licenses (PHP license) Set Bug forwarded-to-address to 'https://code.google.com/p/gambas/issues/detail?id=531'. thanks Unknown command or malformed arguments to command. End of message, stopping processing here. Please contact me if you need assistance. -- 752625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752625 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#751456: monotone: FTBFS on kfreebsd
Control: severity -1 grave Hi, I'm not quite sure what caused the build failures on kFreeBSD and cannot currently reproduce them (kFreeBSD/amd64/sid - neither against liblua5.1.0-dev nor with liblua5.2-dev). The exact same code worked just fine, before (1.1-2), and seems to work again (1.1-4), so at the worst, this is an intermittent issue. Ideally, it magically resolved. Therefore, I'm currently reducing severity to grave. Regards Markus Wanner signature.asc Description: OpenPGP digital signature
Processed: Bug#751456: monotone: FTBFS on kfreebsd
Processing control commands: severity -1 grave Bug #751456 [monotone] monotone: FTBFS on kfreebsd Severity set to 'grave' from 'serious' -- 751456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751456 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: ruby-excon: FTBFS - Protocol not available - setsockopt(2) (Errno::ENOPROTOOPT) (Excon::Errors::SocketError)
Processing control commands: tag -1 confirmed Bug #751037 [ruby-excon] ruby-excon: FTBFS - Protocol not available - setsockopt(2) (Errno::ENOPROTOOPT) (Excon::Errors::SocketError) Added tag(s) confirmed. -- 751037: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751037 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#751037: ruby-excon: FTBFS - Protocol not available - setsockopt(2) (Errno::ENOPROTOOPT) (Excon::Errors::SocketError)
Package: ruby-excon Followup-For: Bug #751037 Control: tag -1 confirmed Hi! I could reproduce the bug: whereas it doesn't appear when I build the package locally on my machine, with either pbuilder or sbuild, it did occur when I tried to build ruby-excon on a porterbox (harris). One may need to deactivate the tests related to the use of local ports. Cheers, Cédric signature.asc Description: Digital signature
Bug#751456: marked as done (monotone: FTBFS on kfreebsd)
Your message dated Wed, 25 Jun 2014 13:47:42 +0200 with message-id 53aab6de.6090...@debian.org and subject line Re: Bug#751456: monotone: FTBFS on kfreebsd has caused the Debian Bug report #751456, regarding monotone: FTBFS on kfreebsd 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.) -- 751456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751456 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: monotone severity: serious version: 1.1-3 Hi, The latest monotone upload FTBFS on kfreebsd, but built fine before: https://buildd.debian.org/status/package.php?p=monotonesuite=unstable Cheers, Ivo ---End Message--- ---BeginMessage--- Version: 1.1-4 On 25/06/14 13:20, Markus Wanner wrote: Control: severity -1 grave Hi, I'm not quite sure what caused the build failures on kFreeBSD and cannot currently reproduce them (kFreeBSD/amd64/sid - neither against liblua5.1.0-dev nor with liblua5.2-dev). The exact same code worked just fine, before (1.1-2), and seems to work again (1.1-4), so at the worst, this is an intermittent issue. Ideally, it magically resolved. Therefore, I'm currently reducing severity to grave. grave serious. Anyway, the failure was with 1.1-3, and 1.1-4 has been uploaded and built fine on kfreebsd-*. So let's close this. Emilio---End Message---
Bug#750351: Looking for sponsor to upload new packages
Hi, I am still looking for a sponsor to upload the new packages which are supposed to fix this bug. See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750592 The new pacakges pyformex-0.9.1-5 are here: http://mentors.debian.net/package/pyformex Benedict -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 752532 to php-geoip is licensed under the PHP license, and is not PHP
Processing commands for cont...@bugs.debian.org: retitle 752532 php-geoip is licensed under the PHP license, and is not PHP Bug #752532 [php-geoip] php-json is licensed under the PHP license, and is not PHP Changed Bug title to 'php-geoip is licensed under the PHP license, and is not PHP' from 'php-json is licensed under the PHP license, and is not PHP' thanks Stopping processing here. Please contact me if you need assistance. -- 752532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752532 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#728196: marked as done (php-gearman is licensed under the PHP license, and is not PHP)
Your message dated Wed, 25 Jun 2014 14:20:15 +0200 with message-id 1403698815.23913.133404977.7c5ea...@webmail.messagingengine.com and subject line Re: Bug#752531: php-json is licensed under the PHP license, and is not PHP has caused the Debian Bug report #728196, regarding php-gearman is licensed under the PHP license, and is not PHP 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.) -- 728196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: php-gearman Severity: serious User: paul...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks From the REJECT faq: / | You have a PHP add-on package (any php script/app/thing, not PHP | itself) and it's licensed only under the standard PHP license. That | license, up to the 3.x which is actually out, is not really usable for | anything else than PHP itself. I've mailed our -legal list about that | and got only one response, which basically supported my view on this. | Basically this license talks only about PHP, the PHP Group, and includes | Zend Engine, so its not applicable to anything else. And even worse, | older versions include the nice ad-clause. | | One good solution here is to suggest a license change to your upstream, | as they clearly wanted a free one. LGPL or BSD seems to be what they | want. \ Sorry this made it through NEW, Hope you're well, and thanks for your work, Paul -- .''`. Paul Tagliamonte paul...@debian.org : :' : Proud Debian Developer `. `'` 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87 `- http://people.debian.org/~paultag signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- JFTR The php-json license is in fact correct since: most of the files are the copied from ext/json. So License of ext/Json still apply. I am closing this bug on php-json in hope that's ok with you... if not please reopen. Ondrej -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server---End Message---
Processed: Fwd: Re: Bug#752531: php-json is licensed under the PHP license, and is not PHP
Processing commands for cont...@bugs.debian.org:
reopen 728196
Bug #728196 {Done: Ondřej Surý ond...@sury.org} [src:php-gearman] php-gearman
is licensed under the PHP license, and is not PHP
Bug reopened
Ignoring request to alter fixed versions of bug #728196 to the same values
previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
728196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728196
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#752531: marked as done (php-json is licensed under the PHP license, and is not PHP)
Your message dated Wed, 25 Jun 2014 14:25:43 +0200 with message-id 1403699143.25581.133407573.4881c...@webmail.messagingengine.com and subject line Fwd: Re: Bug#752531: php-json is licensed under the PHP license, and is not PHP has caused the Debian Bug report #752531, regarding php-json is licensed under the PHP license, and is not PHP 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.) -- 752531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: php-gearman Severity: serious User: paul...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks From the REJECT faq: / | You have a PHP add-on package (any php script/app/thing, not PHP | itself) and it's licensed only under the standard PHP license. That | license, up to the 3.x which is actually out, is not really usable for | anything else than PHP itself. I've mailed our -legal list about that | and got only one response, which basically supported my view on this. | Basically this license talks only about PHP, the PHP Group, and includes | Zend Engine, so its not applicable to anything else. And even worse, | older versions include the nice ad-clause. | | One good solution here is to suggest a license change to your upstream, | as they clearly wanted a free one. LGPL or BSD seems to be what they | want. \ Sorry this made it through NEW, Hope you're well, and thanks for your work, Paul -- .''`. Paul Tagliamonte paul...@debian.org : :' : Proud Debian Developer `. `'` 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87 `- http://people.debian.org/~paultag signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- reopen 728196 thanks And now again to correct address. -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server - Original message - From: Ondřej Surý ond...@sury.org To: 728196-d...@bugs.debian.org, ftpmas...@debian.org Subject: Re: Bug#752531: php-json is licensed under the PHP license, and is not PHP Date: Wed, 25 Jun 2014 14:20:15 +0200 JFTR The php-json license is in fact correct since: most of the files are the copied from ext/json. So License of ext/Json still apply. I am closing this bug on php-json in hope that's ok with you... if not please reopen. Ondrej -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server---End Message---
Bug#746916: NMU debdiff for soprano_2.9.4+dfsg-1.1
debdiff soprano_2.9.4+dfsg-1.dsc soprano_2.9.4+dfsg-1.1.dsc diff -Nru soprano-2.9.4+dfsg/debian/changelog soprano-2.9.4+dfsg/debian/changelog --- soprano-2.9.4+dfsg/debian/changelog 2013-11-04 15:13:52.0 + +++ soprano-2.9.4+dfsg/debian/changelog 2014-06-24 10:47:30.0 +0100 @@ -1,3 +1,13 @@ +soprano (2.9.4+dfsg-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Update symbols file. +Patch by Sphinx Jiang yishan...@gmail.com. +Work done for Debian GSOC2014. +Closes: #746916. + + -- Anibal Monsalve Salazar ani...@debian.org Tue, 24 Jun 2014 10:46:06 +0100 + soprano (2.9.4+dfsg-1) unstable; urgency=low * New upstream release. diff -Nru soprano-2.9.4+dfsg/debian/libsoprano4.symbols soprano-2.9.4+dfsg/debian/libsoprano4.symbols --- soprano-2.9.4+dfsg/debian/libsoprano4.symbols 2013-11-04 15:13:52.0 + +++ soprano-2.9.4+dfsg/debian/libsoprano4.symbols 2014-06-24 09:43:18.0 +0100 @@ -3,8 +3,6 @@ * Build-Depends-Package: libsoprano-dev (optional=external)_Z5qHashRK4QUrl@Base 2.1.67 _ZN7Soprano10BindingSet6insertERK7QStringRKNS_4NodeE@Base 2.1.1 - (optional=private)_ZN7Soprano10BindingSet7PrivateD1Ev@Base 2.7.6 - (optional=private)_ZN7Soprano10BindingSet7PrivateD2Ev@Base 2.7.6 _ZN7Soprano10BindingSet7replaceERK7QStringRKNS_4NodeE@Base 2.2.69 _ZN7Soprano10BindingSet7replaceEiRKNS_4NodeE@Base 2.2.69 _ZN7Soprano10BindingSetC1ERKS0_@Base 2.1.1 @@ -1163,9 +1161,6 @@ _ZN7Soprano5Query20BooleanSetExpression7PrivateD2Ev@Base 2.1.1 _ZN7Soprano5Query20BooleanSetExpressionC1Ev@Base 2.1.1 _ZN7Soprano5Query20BooleanSetExpressionC2Ev@Base 2.1.1 - _ZN7Soprano5Query20BooleanSetExpressionD0Ev@Base 2.7.0 - _ZN7Soprano5Query20BooleanSetExpressionD1Ev@Base 2.7.0 - _ZN7Soprano5Query20BooleanSetExpressionD2Ev@Base 2.7.0 _ZN7Soprano5Query20NumericalGreaterThanC1EPNS0_19NumericalExpressionES3_@Base 2.1.1 _ZN7Soprano5Query20NumericalGreaterThanC2EPNS0_19NumericalExpressionES3_@Base 2.1.1 _ZN7Soprano5Query20NumericalGreaterThanD0Ev@Base 2.7.0 @@ -1196,9 +1191,6 @@ _ZN7Soprano5Query22UnaryBooleanExpression7PrivateD2Ev@Base 2.1.1 _ZN7Soprano5Query22UnaryBooleanExpressionC1EPNS0_17BooleanExpressionE@Base 2.1.1 _ZN7Soprano5Query22UnaryBooleanExpressionC2EPNS0_17BooleanExpressionE@Base 2.1.1 - _ZN7Soprano5Query22UnaryBooleanExpressionD0Ev@Base 2.7.0 - _ZN7Soprano5Query22UnaryBooleanExpressionD1Ev@Base 2.7.0 - _ZN7Soprano5Query22UnaryBooleanExpressionD2Ev@Base 2.7.0 _ZN7Soprano5Query23queryLanguageFromStringERK7QString@Base 2.1.1 _ZN7Soprano5Query24DateTimeGreaterThanEqualC1ERK9QDateTimeS4_@Base 2.1.1 _ZN7Soprano5Query24DateTimeGreaterThanEqualC2ERK9QDateTimeS4_@Base 2.1.1 @@ -1214,9 +1206,6 @@ _ZN7Soprano5Query24UnaryNumericalExpression7PrivateD2Ev@Base 2.1.1 _ZN7Soprano5Query24UnaryNumericalExpressionC1EPNS0_19NumericalExpressionE@Base 2.1.1 _ZN7Soprano5Query24UnaryNumericalExpressionC2EPNS0_19NumericalExpressionE@Base 2.1.1 - _ZN7Soprano5Query24UnaryNumericalExpressionD0Ev@Base 2.7.0 - _ZN7Soprano5Query24UnaryNumericalExpressionD1Ev@Base 2.7.0 - _ZN7Soprano5Query24UnaryNumericalExpressionD2Ev@Base 2.7.0 _ZN7Soprano5Query24UnaryRTermExpressionBase7PrivateC1EPNS0_5RTermE@Base 2.1.1 _ZN7Soprano5Query24UnaryRTermExpressionBase7PrivateC1ERKS2_@Base 2.1.1 _ZN7Soprano5Query24UnaryRTermExpressionBase7PrivateC2EPNS0_5RTermE@Base 2.1.1 @@ -1236,9 +1225,6 @@ _ZN7Soprano5Query25BinaryNumericalExpression9setSecondEPNS0_19NumericalExpressionE@Base 2.1.1 _ZN7Soprano5Query25BinaryNumericalExpressionC1EPNS0_19NumericalExpressionES3_@Base 2.1.1 _ZN7Soprano5Query25BinaryNumericalExpressionC2EPNS0_19NumericalExpressionES3_@Base 2.1.1 - _ZN7Soprano5Query25BinaryNumericalExpressionD0Ev@Base 2.7.0 - _ZN7Soprano5Query25BinaryNumericalExpressionD1Ev@Base 2.7.0 - _ZN7Soprano5Query25BinaryNumericalExpressionD2Ev@Base 2.7.0 _ZN7Soprano5Query25NumericalGreaterThanEqualC1EPNS0_19NumericalExpressionES3_@Base 2.1.1 _ZN7Soprano5Query25NumericalGreaterThanEqualC2EPNS0_19NumericalExpressionES3_@Base 2.1.1 _ZN7Soprano5Query25NumericalGreaterThanEqualD0Ev@Base 2.7.0 @@ -1246,14 +1232,8 @@ _ZN7Soprano5Query25NumericalGreaterThanEqualD2Ev@Base 2.7.0 _ZN7Soprano5Query26UnaryRTermStringExpressionC1EPNS0_5RTermE@Base 2.1.1 _ZN7Soprano5Query26UnaryRTermStringExpressionC2EPNS0_5RTermE@Base 2.1.1 - _ZN7Soprano5Query26UnaryRTermStringExpressionD0Ev@Base 2.7.0 - _ZN7Soprano5Query26UnaryRTermStringExpressionD1Ev@Base 2.7.0 - _ZN7Soprano5Query26UnaryRTermStringExpressionD2Ev@Base 2.7.0 _ZN7Soprano5Query27UnaryRTermBooleanExpressionC1EPNS0_5RTermE@Base 2.1.1 _ZN7Soprano5Query27UnaryRTermBooleanExpressionC2EPNS0_5RTermE@Base 2.1.1 - _ZN7Soprano5Query27UnaryRTermBooleanExpressionD0Ev@Base 2.7.0 - _ZN7Soprano5Query27UnaryRTermBooleanExpressionD1Ev@Base 2.7.0 - _ZN7Soprano5Query27UnaryRTermBooleanExpressionD2Ev@Base 2.7.0 _ZN7Soprano5Query28BinaryRTermBooleanExpression7PrivateC1EPNS0_5RTermES4_@Base 2.1.1
Bug#752667: ldirectord uses inet_ntop without importing it from the Socket library
Package: ldirectord Version: 1:3.9.2-5+deb7u2 Severity: critical Tags: upstream Justification: causes serious data loss Hi, This is easy to fix, but it was hard to troubleshoot. Any load balancer relying on simpletcp checks will fail when upgrade from squeeze to wheezy basically because of this. Other functionalities of ldirectord could be affected (we were hit just by simpletc checks not working anymore). Regards, Juan -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-64-generic (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718272:
For example: if we release Debian Jessie with version 0.8 of bitcoin, and a security bug is found in that version and fixed upstream, the fix may be based on top of version 0.10 and unable to be ported to 0.8. A Debian package is allowed to bump versions for a security fix. Is this any different to the Chromium situation? Chromium-35 is already in wheezy despite only being released one month ago. Similar reasoning; Chromium upstream do not support backported security fixes, they just release a new version. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752673: does not work
Package: festvox-ru Version: 0.5-6 Severity: grave After installing festvox-ru I see the following error message as I try to use it: $ echo Привет. | festival --language russian --tts SIOD ERROR: could not open file /usr/share/festival/voices/russian/msu_ru_nsh_clunits/festvox/msu_ru_nsh_cg.scm Error evaluating default voice: voice_msu_ru_nsh_cg continuing SIOD ERROR: could not open file /usr/share/festival/voices/russian/msu_ru_nsh_clunits/festvox/msu_ru_nsh_cg.scm festival: fatal error exiting. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.14-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages festvox-ru depends on: ii festival 1:2.1~release-8 festvox-ru recommends no packages. festvox-ru 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
Processed: bug 752629 is forwarded to https://github.com/libming/libming/issues/42
Processing commands for cont...@bugs.debian.org: forwarded 752629 https://github.com/libming/libming/issues/42 Bug #752629 [ming] ming is licensed under the PHP license and is not PHP Set Bug forwarded-to-address to 'https://github.com/libming/libming/issues/42'. thanks Stopping processing here. Please contact me if you need assistance. -- 752629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752629 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#751037: [DRE-maint] Bug#751037: ruby-excon: FTBFS - Protocol not available - setsockopt(2) (Errno::ENOPROTOOPT) (Excon::Errors::SocketError)
२०१४-०६-२५ १६:५६ [GMT]+०५:३०, Cédric Boutillier bou...@debian.org: I could reproduce the bug: whereas it doesn't appear when I build the package locally on my machine, with either pbuilder or sbuild, it did occur when I tried to build ruby-excon on a porterbox (harris). One may need to deactivate the tests related to the use of local ports. Cedric, I have made the changes in git to deactivate tests. Can you test it? Praveen -- പ്രവീണ് അരിമ്പ്രത്തൊടിയില് You have to keep reminding your government that you don't get your rights from them; you give them permission to rule, only so long as they follow the rules: laws and constitution. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752673: does not work
severity 752673 wishlist thanks On Wed, Jun 25, 2014 at 06:14:47PM +0400, Dmitry Eremin-Solenikov wrote: After installing festvox-ru I see the following error message Please read the documentation of the package. -- 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#752673: does not work
Processing commands for cont...@bugs.debian.org: severity 752673 wishlist Bug #752673 [festvox-ru] does not work Severity set to 'wishlist' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 752673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752673 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#752673: does not work
Processing commands for cont...@bugs.debian.org: severity 752673 grave Bug #752673 [festvox-ru] does not work Severity set to 'grave' from 'wishlist' thanks Stopping processing here. Please contact me if you need assistance. -- 752673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752673 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#751284: marked as done (torbrowser-launcher: fails to download due to invalid certificate for https://www.torproject.org)
Your message dated Wed, 25 Jun 2014 15:38:00 + with message-id e1wzpgq-uv...@franck.debian.org and subject line Bug#751284: fixed in torbrowser-launcher 0.1.0-1.1 has caused the Debian Bug report #751284, regarding torbrowser-launcher: fails to download due to invalid certificate for https://www.torproject.org 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.) -- 751284: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: torbrowser-launcher Version: 0.0.7-1 Severity: serious Tags: upstream patch fixed-upstream Hi! torbrowser-laucher fails to download the torbrowser, due to invalid certificate for https://www.torproject.org with The SSL certificate served by https://www.torproject.org is invalid! You may be under attack. Upstream has commited https://github.com/micahflee/torbrowser-launcher/commit/70522eff96349b282081e22a9250eb78d3961359 https://github.com/micahflee/torbrowser-launcher/issues/84 to update to the new cert. Thanks for uploading torbrowser-launcher to Debian! Regards, Salvatore ---End Message--- ---BeginMessage--- Source: torbrowser-launcher Source-Version: 0.1.0-1.1 We believe that the bug you reported is fixed in the latest version of torbrowser-launcher, 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 751...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ulrike Uhlig u...@451f.org (supplier of updated torbrowser-launcher 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: Fri, 20 Jun 2014 07:27:25 +0200 Source: torbrowser-launcher Binary: torbrowser-launcher Architecture: source all Version: 0.1.0-1.1 Distribution: unstable Urgency: low Maintainer: Jacob Appelbaum ja...@appelbaum.net Changed-By: Ulrike Uhlig u...@451f.org Description: torbrowser-launcher - helps download, update and run the Tor Browser Bundle Closes: 751284 751366 751452 751773 Changes: torbrowser-launcher (0.1.0-1.1) unstable; urgency=low . [ Ulrike Uhlig ] * Non-maintainer upload in coordination with maintainer. * New upstream version. (Closes: #751284) * debian/control: - Added homepage, Vcs-Git and Vcs-Browser information. - Move to contrib (Closes: #751366) - Suggests: apparmor (Closes: #751452) - Deleted depencies: apparmor-utils, apparmor-profiles, debhelper - debhelper Build-dependency downgraded from 9.20140228 to 7.4.3 (Closes: #751773) * debian/watch added Checksums-Sha1: f6380c7de8bdb977597f4486268bd0ff648e1cbd 1985 torbrowser-launcher_0.1.0-1.1.dsc 1d50ea529b247fa0aaf0de156da1c00f22012fbf 279078 torbrowser-launcher_0.1.0.orig.tar.gz 396104559a52661e51521847861a519a232e26e5 3100 torbrowser-launcher_0.1.0-1.1.debian.tar.xz 5662ece565f35e7597ad89052cb96d108d50eda9 266378 torbrowser-launcher_0.1.0-1.1_all.deb Checksums-Sha256: 41c7847897001618d8e6bd36c186b70b84365d1e1b3fcf888e7738604224c53a 1985 torbrowser-launcher_0.1.0-1.1.dsc b66643d4d86418c2cd61049452eec0f8d8a773bf9869374ab740501b55bdb393 279078 torbrowser-launcher_0.1.0.orig.tar.gz 657218c48705409baa6f930dabfddb090d3f2100f539ebd9995f0a37451ce2be 3100 torbrowser-launcher_0.1.0-1.1.debian.tar.xz 008e0f9a15c2fb77afef0f051683c7365a68bfbc89a5edf7dc7327b938daa43c 266378 torbrowser-launcher_0.1.0-1.1_all.deb Files: 10995df51d3270ae08375cd3a92a9065 266378 contrib/python optional torbrowser-launcher_0.1.0-1.1_all.deb 2991b388261287f06916a49e34f493bf 1985 contrib/python optional torbrowser-launcher_0.1.0-1.1.dsc e9e0a6413543202214e182cef8ddebc4 279078 contrib/python optional torbrowser-launcher_0.1.0.orig.tar.gz 8957a80b04d388b76b86b9af58089300 3100 contrib/python optional torbrowser-launcher_0.1.0-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIVAwUBU6V36wkauFYGmqocAQghxg/+O9cnb1Vp3olb8D6Nqgg7Tf1GNLm3dW2V Yz/kAfTwAa/8otUEBo+wS/lDTOYK06bKOaPFmobDWfjdMz3R2Ft988E2qxhiWwAd dTIttn1YlHnWLhrHQ+54FquUTiL4LQBNupRdK4s/zOzvevtkBhksOgLy5VLAtwVG 4BNosdXjiY6oxB5idq5976ylClTmp8ryLi+Z6nElw9Wwrzxms/zWzxLc+aB9+d4U 3H727lbqX2hrk6Zwf/Dor2KMLD6AZuoPPA9cuUlDOqtasb1/9UDvkDl7jvJKJfKa
Bug#751366: marked as done (torbrowser-launcher: should be in contrib archive area (not main))
Your message dated Wed, 25 Jun 2014 15:38:00 + with message-id e1wzpgq-v2...@franck.debian.org and subject line Bug#751366: fixed in torbrowser-launcher 0.1.0-1.1 has caused the Debian Bug report #751366, regarding torbrowser-launcher: should be in contrib archive area (not main) 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.) -- 751366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: torbrowser-launcher Severity: serious Justification: Policy 2.2.1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, - From its package description, torbrowser-launcher fetches executable code from outside of Debian. That is explicitly disallowed by Debian Policy (version 3.9.5) § 2.2.1, which states that packages in _main_... must not require or recommend a package outside of _main_ for compilation or execution It seems to me, therefore, that this package needs to be moved to contrib. - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQF8BAEBCgBmBQJTmVQDXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0 RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vW33YH/1Z1htY5BJ5M7lEWrd++3uUx n35rqY8abH5pid+pY1WLZMgi7cXUdqamsLbxnofvuQX3COrHTPUGXNwwnnNSutNe f0Bg1cdBtrgCooqjSZOV0WsX4wGaKjGpTmGNaWzg4uJauezv5ty9Mu82P4qflqNm FcPyyjfxsQTACnRdxrrww5XeyGrIXsESj/Q1XR1XvjNDHRHtiV6lHhfuINGjxd0q atlPQlGbMrtHu6K5MAQ4nISJ0e6VA8QqbC8Snzh4l/nLB5P/ug37rWBgS5hwv2DV KM1ttQgwXseR55yFmXs61KpeZJ73p+i3y1NPp7HgOm0o8nRl1nCEaKpjtBG0Iqg= =z1iR -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: torbrowser-launcher Source-Version: 0.1.0-1.1 We believe that the bug you reported is fixed in the latest version of torbrowser-launcher, 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 751...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ulrike Uhlig u...@451f.org (supplier of updated torbrowser-launcher 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: Fri, 20 Jun 2014 07:27:25 +0200 Source: torbrowser-launcher Binary: torbrowser-launcher Architecture: source all Version: 0.1.0-1.1 Distribution: unstable Urgency: low Maintainer: Jacob Appelbaum ja...@appelbaum.net Changed-By: Ulrike Uhlig u...@451f.org Description: torbrowser-launcher - helps download, update and run the Tor Browser Bundle Closes: 751284 751366 751452 751773 Changes: torbrowser-launcher (0.1.0-1.1) unstable; urgency=low . [ Ulrike Uhlig ] * Non-maintainer upload in coordination with maintainer. * New upstream version. (Closes: #751284) * debian/control: - Added homepage, Vcs-Git and Vcs-Browser information. - Move to contrib (Closes: #751366) - Suggests: apparmor (Closes: #751452) - Deleted depencies: apparmor-utils, apparmor-profiles, debhelper - debhelper Build-dependency downgraded from 9.20140228 to 7.4.3 (Closes: #751773) * debian/watch added Checksums-Sha1: f6380c7de8bdb977597f4486268bd0ff648e1cbd 1985 torbrowser-launcher_0.1.0-1.1.dsc 1d50ea529b247fa0aaf0de156da1c00f22012fbf 279078 torbrowser-launcher_0.1.0.orig.tar.gz 396104559a52661e51521847861a519a232e26e5 3100 torbrowser-launcher_0.1.0-1.1.debian.tar.xz 5662ece565f35e7597ad89052cb96d108d50eda9 266378 torbrowser-launcher_0.1.0-1.1_all.deb Checksums-Sha256: 41c7847897001618d8e6bd36c186b70b84365d1e1b3fcf888e7738604224c53a 1985 torbrowser-launcher_0.1.0-1.1.dsc b66643d4d86418c2cd61049452eec0f8d8a773bf9869374ab740501b55bdb393 279078 torbrowser-launcher_0.1.0.orig.tar.gz 657218c48705409baa6f930dabfddb090d3f2100f539ebd9995f0a37451ce2be 3100 torbrowser-launcher_0.1.0-1.1.debian.tar.xz 008e0f9a15c2fb77afef0f051683c7365a68bfbc89a5edf7dc7327b938daa43c 266378 torbrowser-launcher_0.1.0-1.1_all.deb Files: 10995df51d3270ae08375cd3a92a9065 266378 contrib/python optional torbrowser-launcher_0.1.0-1.1_all.deb 2991b388261287f06916a49e34f493bf 1985 contrib/python optional torbrowser-launcher_0.1.0-1.1.dsc e9e0a6413543202214e182cef8ddebc4 279078 contrib/python optional torbrowser-launcher_0.1.0.orig.tar.gz
Processed: Re: hash-slinger: tlsa and openpgpkey scripts break on non-existent files (root.key, dlv.isc.org.key, ca-bundle.crt)
Processing control commands: severity -1 grave Bug #738489 [hash-slinger] hash-slinger: tlsa and openpgpkey scripts break on non-existent files (root.key, dlv.isc.org.key, ca-bundle.crt) Severity set to 'grave' from 'normal' -- 738489: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738489 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#752544: 752544
Control: tags +moreinfo Control: severity -1 normal -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752544: vlc: source package fails to compile
On 24.06.2014 16:51, Jason Pleau wrote: Package: vlc Version: 2.1.4-1+b2 Severity: serious Tags: lfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, vlc-2.1.4-1 currently fails to compile on my amd64 (unstable) system. - To reproduce: 1. download the source package with apt-get source vlc (need build-deps as well) 2. build the package. - Expected outcome: package is built and a .deb is generated - Current outcome: Package fails to build with this error: Making all in bin make[2]: Entering directory '/home/oxez/vlc/vlc-2.1.4/bin' GEN ../modules/plugins.dat /bin/bash: line 4: 17992 Segmentation fault ./vlc-cache-gen ../modules Makefile:1538: recipe for target '../modules/plugins.dat' failed make[2]: *** [../modules/plugins.dat] Error 139 make[2]: Leaving directory '/home/oxez/vlc/vlc-2.1.4/bin' - How to build the package successfully : The package can be built by using first: export LD_PRELOAD=/usr/lib/libgobject-2.0.so.0 More information can also be found at https://bugs.archlinux.org/task/39676 Hi, I now finished build vlc on clean unstable chroot environment and I don't see that bug. It's build fine. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): re: 752544
Processing control commands: tags +moreinfo Unknown command or malformed arguments to command. severity -1 normal Bug #752544 [vlc] vlc: source package fails to compile Severity set to 'normal' from 'serious' -- 752544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752544 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#752673: does not work
Processing commands for cont...@bugs.debian.org: tag 752673 +patch Bug #752673 [festvox-ru] does not work Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 752673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752673 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#752673: does not work
tag 752673 +patch thanks Try to apply provided patch. --- /usr/share/festival/voices/russian/msu_ru_nsh_clunits/festvox/msu_ru_nsh_clunits.scm.orig 2014-06-25 21:05:53.097309896 +0400 +++ /usr/share/festival/voices/russian/msu_ru_nsh_clunits/festvox/msu_ru_nsh_clunits.scm 2014-06-25 21:05:58.641310017 +0400 @@ -263,7 +263,7 @@ 0)) (proclaim_voice - 'msu_ru_nsh_cg + 'msu_ru_nsh_clunits '((language russian) (gender male) (dialect moscow)
Bug#746916: NMU debdiff for soprano_2.9.4+dfsg-1.1
On Wednesday 25 June 2014 22:30:34 Aníbal Monsalve Salazar wrote: debdiff soprano_2.9.4+dfsg-1.dsc soprano_2.9.4+dfsg-1.1.dsc diff -Nru soprano-2.9.4+dfsg/debian/changelog soprano-2.9.4+dfsg/debian/changelog --- soprano-2.9.4+dfsg/debian/changelog 2013-11-04 15:13:52.0 + +++ soprano-2.9.4+dfsg/debian/changelog 2014-06-24 10:47:30.0 +0100 @@ -1,3 +1,13 @@ +soprano (2.9.4+dfsg-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Update symbols file. +Patch by Sphinx Jiang yishan...@gmail.com. +Work done for Debian GSOC2014. +Closes: #746916. This doesn't seems to be a patch generated by pkgkde-symbolshelper. I'm not even sure if it was done with build logs of all archs available or just one arch. Symbols need to be managed differently, it's not just a matter of building in one arch and diffing. You can take a look at [0] [0] http://pkg-kde.alioth.debian.org/symbolfiles.html Even after completing those steps you need to push to the archive and see what FTBFS, as (AFAIU) not all archs have already switched to gcc 4.9. So it's not strange to need more than one upload to fix the issue. I would recommend letting the maintainer solve this with time (maybe even waiting for a new upstream release, except if the package is holding a transition). Kinds regards, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#718272:
Luke-Jr wrote: I agree with Scott's assessment, although I would note that Debian *does* have a suite that addresses the needs of Bitcoin: stable-updates. Mandatory protocol rule changes would seem to fall within the broken by the flow of time category. Thoughts? I agree. Scott Howard wrote: I think this is the way to go once bitcoin version 1.0 (or the equivalent) is released. It requires users to enable the stable-updates repository This is not necessary as the debian-installer already enables stable-updates by default. we should block migration to testing until either upstream supports stable releases or we have a volunteer that works closely enough with upstream code (an upstream developer) that is will to backport security and network- related fixes. Backporting is not necessary. The package can be version bumped for a security update, or version bumped in stable-updates for non-security changes. In the case of Bitcoin, mandatory network changes could arguably be considered security updates if they prevent the bitcoin server from working, because being unable to update the copy of the blockchain would open up additional attack vectors. tor has very similar restrictions (version 1.0, network protocol could change) and yet it is in both stable and testing. Testing already has other software (cgminger, bfgminer) that is reliant on the bitcoin protocol. Given all this, I do not think that the problems presented in this bug are a reason to hold up bitcoin from entering testing or, ultimately, stable. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752673: does not work
Thanks, this make it work On Wed, Jun 25, 2014 at 9:08 PM, Sergey B Kirpichev skirpic...@gmail.com wrote: tag 752673 +patch thanks Try to apply provided patch. -- With best wishes Dmitry -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750338: marked as done (trac: FTBFS: chmod: cannot access 'debian/trac/usr/share/pyshared/trac/admin/templates/deploy_trac.*': No such file or directory)
Your message dated Wed, 25 Jun 2014 17:34:03 + with message-id e1wzr59-0003qt...@franck.debian.org and subject line Bug#750338: fixed in trac 1.0.1-3 has caused the Debian Bug report #750338, regarding trac: FTBFS: chmod: cannot access 'debian/trac/usr/share/pyshared/trac/admin/templates/deploy_trac.*': 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.) -- 750338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: trac Version: 1.0.1-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140601 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/«PKGBUILDDIR»' dh_fixperms find debian/trac/usr/share/pyshared/trac -type f -print0 2/dev/null | xargs -0r chmod 644 chmod 755 debian/trac/usr/share/pyshared/trac/admin/templates/deploy_trac.* chmod: cannot access 'debian/trac/usr/share/pyshared/trac/admin/templates/deploy_trac.*': No such file or directory make[1]: *** [override_dh_fixperms] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/06/01/trac_1.0.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: trac Source-Version: 1.0.1-3 We believe that the bug you reported is fixed in the latest version of trac, 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 750...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Kahn Gillmor d...@fifthhorseman.net (supplier of updated trac 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: Wed, 25 Jun 2014 12:39:22 -0400 Source: trac Binary: trac Architecture: source all Version: 1.0.1-3 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team python-apps-t...@lists.alioth.debian.org Changed-By: Daniel Kahn Gillmor d...@fifthhorseman.net Description: trac - Enhanced wiki and issue tracking system for software development Closes: 750338 Changes: trac (1.0.1-3) unstable; urgency=medium . * clean up build process now that dh_python2 only expects there to be a single version of python 2 installed (Closes: #750338) * override lintian warnings about sourceless javascript, which we had already dealt with by shipping links to the debian packages (and not the minified js) * bump Standards-Version to 3.9.5 (no changes needed) Checksums-Sha1: 800eb995bf3d2a115bbeb6aa25a7bd704411be9d 2203 trac_1.0.1-3.dsc ac3a694f75096a25010139db60ef982cd87ce734 18416 trac_1.0.1-3.debian.tar.xz a9bb6e4d776cb3de388423415c156fc51ff1cc9e 1326328 trac_1.0.1-3_all.deb Checksums-Sha256: 7a081393b7c6a6db69356163e112c12d33bed02f940b253e008f56e40634adbe 2203 trac_1.0.1-3.dsc 5d7fc78ad8c056ef09521dadc42a72277c143bcaa2f87e7046d82551abbf2e26 18416 trac_1.0.1-3.debian.tar.xz e30dd49bad2d8816cbd8c6c0628113c12b2f22b4f05148dca4ece37943a0fe51 1326328 trac_1.0.1-3_all.deb Files: c21ee7341f3626d4f14a97a5724c3e9f 1326328 web optional trac_1.0.1-3_all.deb 9036f7a5b5b49d6c7d946a2e996c6f5a 2203 web optional trac_1.0.1-3.dsc 8127952aee087785693f68ac0b50bb9e 18416 web optional trac_1.0.1-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJTqwNzXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFQjk2OTEyODdBN0FEREUzNzU3RDkxMUVB NTI0MDFCMTFCRkRGQTVDAAoJEKUkAbEb/fpcuk4P/jnfR3PJ0afUQz/bhh3e0Nlj C94P+VCLQcAbHfefsbrVSnaunVnaR5WK6HbyFzY2qixfSQS9c6osg+JRZd6UjGD8 gorRyduYCPo5i/iRwnAPkP0WGHqPy7vTHwI8syRDU1MSfHQlPoo5OpSHKV6z31Lc CMAn/vTo8dByYbAfXE0xgKuwrBU4dtFVH7pqtGpXID5rksu4dLP+jDMpWv4r+P8i
Bug#752636: Only one small file, probably not copyrightable
Hello, Only one file (apc_serializer.h, 80 lines long) is under the PHP license. As this is an header file, I mark this bug as closed. If someone wants to reopen, please explain. Also, as this file comes from php-apc, this bug relates to https://bugs.debian.org/752530. Regards -- Mathieu Parent -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752698: qtdeclarative-opensource-src: FTBFS on mipsel
package: qtdeclarative-opensource-src version: 5.3.0-10 severity: serious Hi, It looks like the symbols file needs to be fixed for mipsel. 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#718272: [Pkg-bitcoin-devel] Bug#718272:
Thank you, Chris. I think you articulated the situation well and the options. On Wed, Jun 25, 2014 at 1:18 PM, Chris Bainbridge chris.bainbri...@gmail.com wrote: This is not necessary as the debian-installer already enables stable-updates by default. stable-updates is enabled by default, but not stable-proposed-updates. That means that users will have to wait on the order of 2 months or more for new versions. security updates are instantaneous and is probably the better way of handling network changes that cannot be delayed. Backporting is not necessary. The package can be version bumped for a security update, or version bumped in stable-updates for non-security changes. In the case of Bitcoin, mandatory network changes could arguably be considered security updates if they prevent the bitcoin server from working, because being unable to update the copy of the blockchain would open up additional attack vectors. I agree mandatory network changes can be argued to be a security update and could be the best way forward, but they do not prevent the bitcoin server from working. It still works and creates a fragmented network with every other non-updated server. That network acts just like the real network and could, in theory, supplant or reject the real network. That's what happened here [1]. It wasn't really a security threat as much as a incompatibility in the protocols with a potential for financial loss. This is a new area for Debian: data loss, corruption, exploitation, unauthorized access are all clearly security bugs, but is potential financial loss from to a working as intended system a security bug? Maybe, we'd need the security team's opinion on that. tor has very similar restrictions (version 1.0, network protocol could change) and yet it is in both stable and testing. Testing already has other software (cgminger, bfgminer) that is reliant on the bitcoin protocol. Given all this, I do not think that the problems presented in this bug are a reason to hold up bitcoin from entering testing or, ultimately, stable. I think it's possible for us to get the package ready for release in jessie if we have a proper management plan. There are 3 possible changes to bitcoin: 1) Security fixes 2) Network protocol changes [2] 3) New features/usability bug fixes We need a plan that allows us to definitely fix 1 and 2 for users in a stable release as needed on short notice. 1) is clearly doable via security updates. 2) is harder. stable-updates takes too long (see above). Protocol changes are not traditional security bugs, but might be classified as one. It's a different situation than tor [3]. 3) doable via stable-updates (or backports) This is my opinion, but if we can get someone from the security team to say that they will accept bitcoin network protocol changes as security bugs, then I think that would be acceptable to do 1 and 2 via security AND also update the package to new versions using stable-updates. This is my opinion, but I think 2 months+ is too long for default users to wait for network protocol changes which sometimes require a response on the order of days or hours. We'd also have to remember to patch both the stable and stable-updates version of the package for each protocol change. As you can see, this gets complicated, and there is much downside if something goes wrong - thus my general uneasiness towards having bitcoin in a stable release. Something to keep in mind: this may be confusing to some users when they are told they must upgrade to version 0.10, and we keep 0.9-2 where our -2 includes the required protocol changes in 0.10, but that isn't that big of a problem and would just require proper communication probably via the debian news and changelog files. In somewhat related news, bitcoin is talking about splitting the wallet out from the node. An SPV wallet will be safe to ship in a stable release, even if the nodes are not. In summary: I think the next step is for someone to contact the security team to see what they think of the situation. Cheers, Scott [1] https://github.com/bitcoin/bips/blob/master/bip-0050.mediawiki [2] cgminer and bfgminer actually don't rely on the bitcoin protocol, they use either JSON RPC commands or the stratum protocol and are independent of the bitcoin protocol. Yes, that interface can (and does) change, but such changes are not as catastrophic as a bitcoin fork and have been backwards compatible in the past. [3] Like tor, if a large percentage of users are using the wrong version of the bitcoin protocol, it is possible that the network will become fragmented. A fragmented bitcoin network could lead to lost transactions for the specific user and damage bitcoin's credibility (leading to large financial losses for every user of the network). I may be wrong, but I believe tor fragmentation is serious, but not as grave (if the tor network fragments due to a non-security based protocol change, all that happens is the network of peers
Bug#752534: Upstream bug#
Control: tag -1 + upstream Control: forwarded -1 https://bugs.php.net/bug.php?id=67517 Hello, I have reported this one upstream: https://bugs.php.net/bug.php?id=67517 Regards -- Mathieu Parent -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750321: marked as done (composite: FTBFS: Configure errors)
Your message dated Wed, 25 Jun 2014 18:48:35 + with message-id e1wzsfh-0003jm...@franck.debian.org and subject line Bug#750321: fixed in composite 0.006.2+dfsg0-4 has caused the Debian Bug report #750321, regarding composite: FTBFS: Configure errors 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.) -- 750321: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: composite Version: 0.006.2+dfsg0-3 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140601 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/«BUILDDIR»/composite-0.006.2+dfsg0' dh_auto_configure -- -DWANT_LRDF=ON \ -DCMAKE_BUILD_TYPE=RelWithDebInfo -- The C compiler identification is GNU 4.8.3 -- The CXX compiler identification is GNU 4.8.3 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Looking for Q_WS_X11 -- Looking for Q_WS_X11 - found -- Looking for Q_WS_WIN -- Looking for Q_WS_WIN - not found -- Looking for Q_WS_QWS -- Looking for Q_WS_QWS - not found -- Looking for Q_WS_MAC -- Looking for Q_WS_MAC - not found -- Found Qt4: /usr/bin/qmake (found suitable version 4.8.6, minimum required is 4.3.0) -- Found PkgConfig: /usr/bin/pkg-config (found version 0.28) -- Found JACK: /usr/lib/x86_64-linux-gnu/libjack.so -- Found FLAC: /usr/lib/x86_64-linux-gnu/libFLAC.so -- Found FLAC++: /usr/lib/x86_64-linux-gnu/libFLAC++.so -- Found LibSndfile: /usr/lib/x86_64-linux-gnu/libsndfile.so -- Found LibTar: /usr/lib/libtar.so -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) CMake Error at /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108 (message): Could NOT find LibArchive (missing: LibArchive_LIBRARIES LibArchive_INCLUDE_DIRS) Call Stack (most recent call first): /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:315 (_FPHSA_FAILURE_MESSAGE) cmake/Modules/FindLibArchive.cmake:17 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) src/Tritium/CMakeLists.txt:74 (find_package) -- Configuring incomplete, errors occurred! See also /«BUILDDIR»/composite-0.006.2+dfsg0/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log. See also /«BUILDDIR»/composite-0.006.2+dfsg0/obj-x86_64-linux-gnu/CMakeFiles/CMakeError.log. dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DWANT_LRDF=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo returned exit code 1 make[1]: *** [override_dh_auto_configure] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/06/01/composite_0.006.2+dfsg0-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: composite Source-Version: 0.006.2+dfsg0-4 We believe that the bug you reported is fixed in the latest version of composite, 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 750...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alessio Treglia ales...@debian.org (supplier of updated composite 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: Wed, 25 Jun 2014 19:32:35 +0100 Source: composite Binary: composite composite-data composite-dbg Architecture: source amd64 all Version: 0.006.2+dfsg0-4 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia
Processed: Upstream bug#
Processing control commands: tag -1 + upstream Bug #752534 [php-memcache] php-memcache is licensed under the PHP license, and is not PHP Added tag(s) upstream. forwarded -1 https://bugs.php.net/bug.php?id=67517 Bug #752534 [php-memcache] php-memcache is licensed under the PHP license, and is not PHP Set Bug forwarded-to-address to 'https://bugs.php.net/bug.php?id=67517'. -- 752534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752534 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#718272: [Pkg-bitcoin-devel] Bug#718272:
On Wed, Jun 25, 2014 at 2:50 PM, Scott Howard showard...@gmail.com wrote: Thank you, Chris. I think you articulated the situation well and the options. one more thing: debian is discussion dropping libdb (the db the node, but not the wallet, uses). That might force our hand as well: either ship and support upstream's included libdb or drop the node and just ship the wallet. libdb long-term security maintenance might be challenging. -- 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 752533 752638
Processing commands for cont...@bugs.debian.org: forcemerge 752533 752638 Bug #752533 [php-imagick] php-imagick is licensed under the PHP license, and is not PHP Bug #752638 [php-imagick] php-imagick is licensed under the PHP license and is not PHP Merged 752533 752638 thanks Stopping processing here. Please contact me if you need assistance. -- 752533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752533 752638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752638 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#718272: [Pkg-bitcoin-devel] Bug#718272:
On Wednesday, June 25, 2014 6:53:57 PM Scott Howard wrote: On Wed, Jun 25, 2014 at 2:50 PM, Scott Howard showard...@gmail.com wrote: Thank you, Chris. I think you articulated the situation well and the options. one more thing: debian is discussion dropping libdb (the db the node, but not the wallet, uses). That might force our hand as well: either ship and support upstream's included libdb or drop the node and just ship the wallet. libdb long-term security maintenance might be challenging. You mean LevelDB? Debian should use the embedded copy regardless, due to the consensus-critical requirements. It is not possible to build BCCore wallets without the node at this time. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752698: qtdeclarative-opensource-src: FTBFS on mipsel
On Wednesday 25 June 2014 20:38:59 Ivo De Decker wrote: package: qtdeclarative-opensource-src version: 5.3.0-10 severity: serious Hi, It looks like the symbols file needs to be fixed for mipsel. Yes, but I'm holding on updating it because this week we should have a new upstream release and we already have 5.3.0 in testing. Of course if this is stopping something else just ping me and I'll fix it. Kinds regards, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#752698: qtdeclarative-opensource-src: FTBFS on mipsel
Processing control commands: tags -1 pending Bug #752698 [qtdeclarative-opensource-src] qtdeclarative-opensource-src: FTBFS on mipsel Added tag(s) pending. -- 752698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752698 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#752698: qtdeclarative-opensource-src: FTBFS on mipsel
Control: tags -1 pending Hi Lisandro, On Wed, Jun 25, 2014 at 04:17:12PM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: It looks like the symbols file needs to be fixed for mipsel. Yes, but I'm holding on updating it because this week we should have a new upstream release and we already have 5.3.0 in testing. That's fine, thanks! Of course if this is stopping something else just ping me and I'll fix it. 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#718272: [Pkg-bitcoin-devel] Bug#718272:
On Wed, Jun 25, 2014 at 3:11 PM, Luke Dashjr l...@dashjr.org wrote: On Wednesday, June 25, 2014 6:53:57 PM Scott Howard wrote: On Wed, Jun 25, 2014 at 2:50 PM, Scott Howard showard...@gmail.com wrote: Thank you, Chris. I think you articulated the situation well and the options. one more thing: debian is discussion dropping libdb (the db the node, but not the wallet, uses). That might force our hand as well: either ship and support upstream's included libdb or drop the node and just ship the wallet. libdb long-term security maintenance might be challenging. You mean LevelDB? Debian should use the embedded copy regardless, due to the consensus-critical requirements. It is not possible to build BCCore wallets without the node at this time. You're right, brain slip: Debian is using the embedded leveldb distributed by bitcoin for the blockchain and have for several months. Berkeley DB is used for wallets. Berkeley DB (libdb) is what is going to be dropped since they were re-licensed AGPL3 (amongst other reasons). Debian has been using Berkeley DB for a while in bitcoin (long before I got involved) with the --with-incompatible-libdb configure flag, so this may cause a problem since BDB has notorious compatibility issues between versions. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750325: Test failures in Template::Plugin::LaTex ?
Hi Chris! On 03/27/2014 05:10 AM, Chris Travers wrote: If any problems are reported on this module, or any of the other LaTeX support modules, let me know. There has been a bug reported in Debian on the package for the Template::Plugin::LaTex module (libtemplate-plugin-latex-perl [1]), failing to build from source (FTBFS) due to test failures. A transcript for the build attempt is included in the bug report, but it appears to be 'Can't exec xelatex'type errors in showing up LaTex.Driver. I hadn't had a chance myself to look at this before but will be doing so now. Also; IIRC, you're now the contact and maintainer for the various LaTex related modules, so I'll at least be updating the package regarding that. RJ Clay j...@rocasa.us [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750325
Bug#751888: [Gluster-devel] Bug#751888: glusterfs-server: creating symlinks generates errors
On 20/06/2014, at 2:32 PM, Matteo Checcucci wrote: On 06/20/2014 03:05 PM, Ravishankar N wrote: Yes, just sent a patch for review on master :http://review.gluster.org/#/c/8135/ Once it gets accepted, will back-port it to the 3.5 branch I am looking forward to seeing it back-ported and integrated in the debian package. Btw, the backport of this was merged into the release-3.5 branch yesterday. It'll be in GlusterFS 3.5.2. Hope that helps. :) Regards and best wishes, Justin Clift -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751037: [DRE-maint] Bug#751037: ruby-excon: FTBFS - Protocol not available - setsockopt(2) (Errno::ENOPROTOOPT) (Excon::Errors::SocketError)
Hi Praveen, On Wed, Jun 25, 2014 at 08:03:58PM +0530, Pirate Praveen wrote: I have made the changes in git to deactivate tests. Can you test it? The build was successful on the porterbox. The FTBFS is thus fixed by skipping the localport reuse test(s). Cheers, Cédric signature.asc Description: Digital signature
Bug#742768: marked as done (cacti: CVE-2014-2326 CVE-2014-2327 CVE-2014-2328)
Your message dated Wed, 25 Jun 2014 21:34:24 + with message-id e1wzupk-0005cr...@franck.debian.org and subject line Bug#742768: fixed in cacti 0.8.8b+dfsg-6 has caused the Debian Bug report #742768, regarding cacti: CVE-2014-2326 CVE-2014-2327 CVE-2014-2328 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.) -- 742768: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: cacti Severity: grave Tags: security Justification: user security hole Hi, please see http://www.securityfocus.com/archive/1/531588 for details. Cheers, Moritz ---End Message--- ---BeginMessage--- Source: cacti Source-Version: 0.8.8b+dfsg-6 We believe that the bug you reported is fixed in the latest version of cacti, 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 742...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers elb...@debian.org (supplier of updated cacti 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: Wed, 25 Jun 2014 22:33:53 +0200 Source: cacti Binary: cacti Architecture: source all Version: 0.8.8b+dfsg-6 Distribution: unstable Urgency: high Maintainer: Cacti Maintainer pkg-cacti-ma...@lists.alioth.debian.org Changed-By: Paul Gevers elb...@debian.org Description: cacti - web interface for graphing of monitoring systems Closes: 742768 744067 752573 Changes: cacti (0.8.8b+dfsg-6) unstable; urgency=high . * Add alternative php5-mysql | php5-mysqlnd (Closes: #744067) * Security update (Closes: #742768, #752573) - CVE-2014-2327 Cross Site Request Forgery Vulnerability - CVE-2014-4002 Cross-Site Scripting Vulnerability Checksums-Sha1: cb0087d5f3770dea819440882c268c754ae0f0e3 1655 cacti_0.8.8b+dfsg-6.dsc 5a34a582d9c8677518a33234a4ad1ac8024ee61a 103284 cacti_0.8.8b+dfsg-6.debian.tar.xz 7b62b650d11502daed7091fbd7985634bfd59f54 1892594 cacti_0.8.8b+dfsg-6_all.deb Checksums-Sha256: f72c1022c8497784322e9bb3db94bff0f72ddbe2f38acfbc9f894236741a86d4 1655 cacti_0.8.8b+dfsg-6.dsc 18433ea70e341eff55c005ff1796018f546fa53ed1159e2cd69ec1c9a96168ec 103284 cacti_0.8.8b+dfsg-6.debian.tar.xz ab5ab0a70f308814acb5f2fdb3b32e398e47567e005065d9fd3d60748470a7aa 1892594 cacti_0.8.8b+dfsg-6_all.deb Files: 0aa31425f144e81ad972e6ec0aff7d9f 1892594 web extra cacti_0.8.8b+dfsg-6_all.deb 6de034dfcb0d7ecf5e6978bf61d9b45c 1655 web extra cacti_0.8.8b+dfsg-6.dsc c06386ec36c90e07234da262dc2136e4 103284 web extra cacti_0.8.8b+dfsg-6.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBCAAGBQJTqzRsAAoJEJxcmesFvXUKseAIAKKzrFxl91WYCof/mF8pxeD9 OjOumQOUH/BSNDfsgou3Vk/hVsiMOZroSaEuTYDznfJPa1ajkFENHL5AySAD44xK sdlHBlpDkp/KexgKBBV+2zxdokjk7BZrfVtJowEkfbVhTOErK+KnUhXmj3sK4tvi sCQQQS4QNL8iRHVnMKuOQge3YKLiM9uWyA/fjS3LRqNCdNasvknWk2r+9xLBx4uK wdmeYubm3oCjc+zWmq9RrhYIYTw0RKyXzk3EqPJHcsGeqsnIk6uYtYch014SRune 3XJWYF3Zj6cShJtFkwyEz/GxesSBs7E5ec/BduJKPzJqb8q24MzYsOtD7jH1AR0= =2G1F -END PGP SIGNATUREEnd Message---
Bug#752573: marked as done (cacti: CVE-2014-4002 Cross-Site Scripting Vulnerability)
Your message dated Wed, 25 Jun 2014 21:34:24 + with message-id e1wzupk-0005d1...@franck.debian.org and subject line Bug#752573: fixed in cacti 0.8.8b+dfsg-6 has caused the Debian Bug report #752573, regarding cacti: CVE-2014-4002 Cross-Site Scripting Vulnerability 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.) -- 752573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752573 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: cacti Version: 0.8.8b+dfsg-5 Severity: grave Tags: security patch upstream pending Justification: user security hole -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Cacti upstream's svn [1] has a fix for CVE-2014-4002. I couldn't find any information yet elsewhere. I can only guess that also the change before this revision is also involved [2]. I will add this to my current update for cacti (in progress). [1] http://svn.cacti.net/viewvc?view=revrevision=7452 [2] http://svn.cacti.net/viewvc?view=revrevision=7451 - -- System Information: Debian Release: 7.5 APT prefers stable APT policy: (500, 'stable'), (99, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.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 Versions of packages cacti depends on: ii dbconfig-common 1.8.47+nmu1 ii debconf [debconf-2.0]1.5.49 ii libapache2-mod-php5 5.4.4-14+deb7u11 ii libphp-adodb 5.15-1 ii mysql-client-5.5 [virtual-mysql-client] 5.5.37-0+wheezy1 ii perl 5.14.2-21+deb7u1 ii php5-cli 5.4.4-14+deb7u11 ii php5-mysql 5.4.4-14+deb7u11 ii php5-snmp5.4.4-14+deb7u11 ii rrdtool 1.4.7-2 ii snmp 5.4.3~dfsg-2.8 ii ucf 3.0025+nmu3 Versions of packages cacti recommends: ii apache2-mpm-prefork [httpd] 2.2.22-13+deb7u1 ii iputils-ping 3:20101006-1+b1 ii libjs-jquery 1.7.2+dfsg-1 ii libjs-jquery-cookie 9-1 ii lighttpd [httpd] 1.4.31-4+deb7u3 ii logrotate3.8.1-4 ii mysql-server 5.5.37-0+wheezy1 Versions of packages cacti suggests: ii moreutils 0.47 pn php5-ldap none - -- debconf information excluded -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBCAAGBQJTqdeoAAoJEJxcmesFvXUKfCsH+waGVLE0MhVourtuswP5Dzmb XNiDG22yZWv2n8l118vK8+5pmY2UsZGDuIOA7vME611flPUa2QhAKuXd9Y4znlg5 LFeMLJ2mSPdSr+YGqly1ToA9iMiYHh44mZIDCiXBdn7wpP1NBkAToZyvN2Etze89 lVfWkTTbWpkU5T3IQLqhZ8reRHWvfex4msjNNfjB+Y4gphd5MTm+tHh+8/YA59LG /L+Dgr25dEMDJG0v47wGqQ9ACRtL5ZtoOzY4R8HY3FO1xY0QIO6qh9ICSG/8O3eb ip8/tNynGcHfGLXVJiRzbxxHnnihwKacKp5gmrgDPmmZhmGduFTy9m3gsEEGdL4= =rPL2 -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: cacti Source-Version: 0.8.8b+dfsg-6 We believe that the bug you reported is fixed in the latest version of cacti, 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 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers elb...@debian.org (supplier of updated cacti 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: Wed, 25 Jun 2014 22:33:53 +0200 Source: cacti Binary: cacti Architecture: source all Version: 0.8.8b+dfsg-6 Distribution: unstable Urgency: high Maintainer: Cacti Maintainer pkg-cacti-ma...@lists.alioth.debian.org Changed-By: Paul Gevers elb...@debian.org Description: cacti - web interface for graphing of monitoring systems Closes: 742768 744067 752573 Changes: cacti (0.8.8b+dfsg-6) unstable; urgency=high . * Add alternative php5-mysql | php5-mysqlnd (Closes: #744067) * Security update (Closes: #742768, #752573) - CVE-2014-2327 Cross Site Request Forgery Vulnerability - CVE-2014-4002 Cross-Site Scripting Vulnerability Checksums-Sha1:
Bug#749061: marked as done (graphviz: Fix typo to ensure autoconf files are updated forbuild)
Your message dated Wed, 25 Jun 2014 21:35:11 +
with message-id e1wzuqv-0006jc...@franck.debian.org
and subject line Bug#749061: fixed in graphviz 2.26.3-17.1
has caused the Debian Bug report #749061,
regarding graphviz: Fix typo to ensure autoconf files are updated forbuild
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.)
--
749061: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: graphviz
Version: 2.26.3-17
Severity: serious
Tags: patch
Justification: fails to build from source
User: debian-...@lists.debian.org
Usertag: arm64
Graphviz now uses dh_autoreconf and has stuff in the rules file to
update all three copies of config.{sub,guess} (hooray!), but a path
mistake meant that the copies in libltld/config were not being
replaced (instead a 4th set was added in the dir above).
This meant that the libltld suddir ./configure on any arch too new for
the shipped config.{sub,guess} failed. This failed on arm64 as they
are too old for that.
A more robust fix for this would probably be to simply use
dh_autotools-dev as well as dh_autoreconf to ensure that all copies
are updated, without having to maintain paths to a list of them in the
rules file. I don't know if the maintainer had a good reason for
trying to avoid the use of that helper?
Attached is the minimal fix that keeps the existing mechanism but I
don't actually think this is better. I'm happy to do a fix using
autotools-dev if the maintainer would prefer (and NMU it).
Graphviz is blocking a lot of package builds on arm64 so I'd
appreciate either an upload or request to NMU reasonably quickly. Cheers.
-- System Information:
Debian Release: 7.5
APT prefers stable
APT policy: (990, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-kvm-i386-20110111 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
diff -Nru graphviz-2.26.3/debian/changelog graphviz-2.26.3/debian/changelog
--- graphviz-2.26.3/debian/changelog 2014-04-20 14:17:40.0 +
+++ graphviz-2.26.3/debian/changelog 2014-05-23 14:26:24.0 +
@@ -1,3 +1,9 @@
+graphviz (2.26.3-17+cfg) unreleased; urgency=low
+
+ * Correct typo in rules so config.{sub,guess} is actually updated.
+
+ -- Wookey woo...@debian.org Fri, 23 May 2014 14:25:42 +
+
graphviz (2.26.3-17) unstable; urgency=medium
* QA upload.
diff -Nru graphviz-2.26.3/debian/rules graphviz-2.26.3/debian/rules
--- graphviz-2.26.3/debian/rules 2014-02-12 02:45:51.0 +
+++ graphviz-2.26.3/debian/rules 2014-05-23 14:24:42.0 +
@@ -35,8 +35,8 @@
RUBY_PACKAGE = $(CURDIR)/debian/libgv-ruby
-CONFIG_SCRIPTS=config/config.guess lib/gd/config/config.guess libltdl/config.guess \
- config/config.sub lib/gd/config/config.sub libltdl/config.sub
+CONFIG_SCRIPTS=config/config.guess lib/gd/config/config.guess libltdl/config/config.guess \
+ config/config.sub lib/gd/config/config.sub libltdl/config/config.sub
# make's $(shell) doesn't use local variables, thus we need to define a
# custom command where DEB_LDFLAGS_MAINT_APPEND is passed.
---End Message---
---BeginMessage---
Source: graphviz
Source-Version: 2.26.3-17.1
We believe that the bug you reported is fixed in the latest version of
graphviz, 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 749...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Wookey woo...@debian.org (supplier of updated graphviz 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: SHA1
Format: 1.8
Date: Fri, 23 May 2014 14:25:42 +
Source: graphviz
Binary: graphviz libgv-guile libgv-lua libgv-perl libgv-php5 libgv-python
libgv-ruby libgv-tcl libgraph4 libcgraph5 libcdt4 libpathplan4 libgvc5
libgvc5-plugins-gtk libgvpr1 libxdot4 libgraphviz-dev graphviz-doc graphviz-dev
Architecture: source all amd64
Version: 2.26.3-17.1
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group packa...@qa.debian.org
Changed-By: Wookey woo...@debian.org
Description:
graphviz - rich set of graph drawing tools
graphviz-dev -
Bug#750904: marked as done (scidavis: FTBFS on arm*: fatal error: sipAPIscidavis.h: No such file or directory)
Your message dated Wed, 25 Jun 2014 21:36:19 +
with message-id e1wzurb-0006j2...@franck.debian.org
and subject line Bug#750904: fixed in scidavis 1.D5-2
has caused the Debian Bug report #750904,
regarding scidavis: FTBFS on arm*: fatal error: sipAPIscidavis.h: 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.)
--
750904: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: scidavis
Version: 1.D5-1
Severity: serious
Justification: FTBFS
Hi,
your package no longer builds on arm*:
| g++ -c -pipe -O2 -D_REENTRANT -Wall -W -DSCRIPTING_CONSOLE -DSCRIPTING_DIALOG
-DSCRIPTING_MUPARSER -DPYTHON_CONFIG_PATH=\/usr/../etc\
-DPYTHON_UTIL_PATH=\/usr/share/scidavis\ -DSCRIPTING_PYTHON -DQT_PLUGIN
-DTS_PATH=\/usr/share/scidavis/translations\
-DDOC_PATH=\/usr/share/doc/scidavis\
-DPLUGIN_PATH=\/usr/lib/scidavis/plugins\ -DLEGACY_CODE_0_2_x -DQT_NO_DEBUG
-DQT_SVG_LIB -DQT_QT3SUPPORT_LIB -DQT3_SUPPORT -DQT_XML_LIB -DQT_OPENGL_LIB
-DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui
-I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtXml
-I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtSvg -I/usr/include/qt4
-I/usr/include/qt4/QtAssistantClient -I/usr/include/qt4/QtAssistant
-I/usr/include/python2.7 -I/usr/include/python2.7 -I/usr/include/qwt-qt4
-I/usr/include/qwtplot3d-qt4 -I/usr/include/muParser -Isrc -Isrc/future
-I/usr/X11R6/include -I/«PKGBU
ILDDIR»/tmp/scidavis -I. -o ../tmp/scidavis/PythonScript.o src/PythonScript.cpp
| src/PythonScript.cpp: In member function 'virtual QVariant
PythonScript::eval()':
| src/PythonScript.cpp:209:45: warning: suggest parentheses around assignment
used as truth value [-Wparentheses]
| } else if (pystring = PyObject_Str(pyret)) {
| ^
| g++ -c -pipe -O2 -D_REENTRANT -Wall -W -DSCRIPTING_CONSOLE -DSCRIPTING_DIALOG
-DSCRIPTING_MUPARSER -DPYTHON_CONFIG_PATH=\/usr/../etc\
-DPYTHON_UTIL_PATH=\/usr/share/scidavis\ -DSCRIPTING_PYTHON -DQT_PLUGIN
-DTS_PATH=\/usr/share/scidavis/translations\
-DDOC_PATH=\/usr/share/doc/scidavis\
-DPLUGIN_PATH=\/usr/lib/scidavis/plugins\ -DLEGACY_CODE_0_2_x -DQT_NO_DEBUG
-DQT_SVG_LIB -DQT_QT3SUPPORT_LIB -DQT3_SUPPORT -DQT_XML_LIB -DQT_OPENGL_LIB
-DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui
-I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtXml
-I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtSvg -I/usr/include/qt4
-I/usr/include/qt4/QtAssistantClient -I/usr/include/qt4/QtAssistant
-I/usr/include/python2.7 -I/usr/include/python2.7 -I/usr/include/qwt-qt4
-I/usr/include/qwtplot3d-qt4 -I/usr/include/muParser -Isrc -Isrc/future
-I/usr/X11R6/include -I/«PKGBU
ILDDIR»/tmp/scidavis -I. -o ../tmp/scidavis/PythonScripting.o
src/PythonScripting.cpp
| src/PythonScripting.cpp:60:28: fatal error: sipAPIscidavis.h: No such file or
directory
| #include sipAPIscidavis.h
| ^
| compilation terminated.
| make[3]: *** [../tmp/scidavis/PythonScripting.o] Error 1
Full build logs:
https://buildd.debian.org/status/fetch.php?pkg=scidavisarch=armhfver=1.D5-1stamp=1401679921
https://buildd.debian.org/status/fetch.php?pkg=scidavisarch=armelver=1.D5-1stamp=1401653966
Mraw,
KiBi.
---End Message---
---BeginMessage---
Source: scidavis
Source-Version: 1.D5-2
We believe that the bug you reported is fixed in the latest version of
scidavis, 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 750...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
georg...@debian.org (supplier of updated scidavis 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: SHA1
Format: 1.8
Date: Wed, 25 Jun 2014 22:48:56 +0200
Source: scidavis
Binary: scidavis
Architecture: source amd64
Version: 1.D5-2
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar georg...@debian.org
Changed-By:
Bug#752724: bashdb: FTBFS: refuses to build with bash = 4.3
Package: bashdb Version: 4.2.0.8-1.1 Severity: serious I just tried to build bashdb to find out whether I can fix #712367. So we have a new bug. The configure script tells me: [...] checking for bash... /bin/bash configure: WARNING: You have Bash GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software; you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. installed. configure: error: This package is only known to work with Bash 4.1 or 4.2. debian/rules:18: recipe for target 'config.status' failed make: *** [config.status] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Cheers, -Hilko -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752591: #752591: udev: initrd fails to create /dev/sda* after udev upgrade
Confirmed fixed in 204-12. Thanks Michael! Kind regards, -- Ben Caradoc-Davies b...@wintersun.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752726: stumpwm: FTBFS - SIGSEGV cannot be cured.
Package: stumpwm Version: 2:0.9.8-1 Severity: serious Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. [...] ;; Compiling file /srv/jenkins-slave/workspace/sid-goto-cc-stumpwm/stumpwm-0.9.8/workarounds.lisp ... WARNING: INTERN(FIRST-ZERO): #PACKAGE XLIB is locked Ignore the lock and proceed WARNING: INTERN(SECOND-ZERO): #PACKAGE XLIB is locked Ignore the lock and proceed WARNING: INTERN(SAVED): #PACKAGE XLIB is locked Ignore the lock and proceed *** - handle_fault error2 ! address = 0x55434f462d6c not in [0xccce8f690,0xccd0ce000) ! SIGSEGV cannot be cured. Fault address = 0x55434f462d6c. GC count: 322 Space collected by GC: 553724984 Run time: 28 145758 Real time: 28 859593 GC time: 4 188248 Permanently allocated: 187488 bytes. Currently in use: 7931696 bytes. Free space: 1618612 bytes. Segmentation fault Makefile:40: recipe for target 'stumpwm.texi' failed I'm not sure whether this is a clisp bug or a problem in stumpwm; the full build log is attached, but please do let me know if the error turns out to be unreproducible. Best, Michael stumpwm-build-log.txt.gz Description: application/gunzip pgpK6AS3SiPA7.pgp Description: PGP signature
Processed: Bug updates
Processing commands for cont...@bugs.debian.org: severity 752690 important Bug #752690 [sponsorship-requests] RFS: ledgersmb/1.3.40-1 [RC] -- financial accounting and ERP program Severity set to 'important' from 'normal' submitter 752690 Robert James Clay j...@rocasa.us Bug #752690 [sponsorship-requests] RFS: ledgersmb/1.3.40-1 [RC] -- financial accounting and ERP program Changed Bug submitter to 'Robert James Clay j...@rocasa.us' from 'RJ Clay j...@rocasa.us' tags 749347 + pending Bug #749347 [ledgersmb] ledgersmb: fails to install Added tag(s) pending. block 749347 by 752690 Bug #749347 [ledgersmb] ledgersmb: fails to install 749347 was not blocked by any bugs. 749347 was not blocking any bugs. Added blocking bug(s) of 749347: 752690 thanks Stopping processing here. Please contact me if you need assistance. -- 749347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749347 752690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752690 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#752725: zatacka: FTBFS - malformed patch 0001-kfreebsd.patch
Package: zatacka
Version: 0.1.8-3
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
I: Running /usr/bin/dpkg-buildpackage -rfakeroot -us -uc ${DEBBUILDOPTS}
dpkg-buildpackage: source package zatacka
dpkg-buildpackage: source version 0.1.8-3
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Alexandre Dantas alex.danta...@gmail.com
dpkg-source --before-build zatacka-0.1.8
dpkg-buildpackage: host architecture amd64
dpkg-source: error: expected ^--- in line 4 of diff
`zatacka-0.1.8/debian/patches/0001-kfreebsd.patch'
dpkg-buildpackage: error: dpkg-source --before-build zatacka-0.1.8 gave error
exit status 25
Indeed 0001-kfreebsd.patch appears to be lacking a newline before the ---.
Best,
Michael
pgpJ0lkyZPMp9.pgp
Description: PGP signature
Bug#752727: yodl: FTBFS - missing build dep on cm-super-minimal
Package: yodl Version: 3.03.0-2 Severity: serious Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. [...] dvips -o yodl.ps yodl.dvi This is dvips(k) 5.994 Copyright 2014 Radical Eye Software (www.radicaleye.com) ' TeX output 2014.06.25:2224' - yodl.ps dvips: ! Couldn't find header file: cm-super-t1.enc system - failure of system call (status 256) system - failure of system call (status 256) debian/rules:60: recipe for target 'build-indep' failed make: *** [build-indep] Error 1 The full build log is attached; I believe the build dependencies need to be adjusted, adding cm-super-minimal. Best, Michael yodl-build-log.txt.gz Description: application/gunzip pgp8w2JDe5uWY.pgp Description: PGP signature
Bug#749944: marked as done (build ogre-1.9 against new boost-defaults 1.55?)
Your message dated Wed, 25 Jun 2014 22:34:46 + with message-id e1wzvma-0005cn...@franck.debian.org and subject line Bug#749944: fixed in ogre-1.9 1.9.0+dfsg1-2 has caused the Debian Bug report #749944, regarding build ogre-1.9 against new boost-defaults 1.55? 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.) -- 749944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ogre-1.9 Severity: wishlist Hello, Ogre-1.9 builds against boost 1.54. Debian just bumped boost-defaults to 1.55. Is it possible to bump debian/control BDs such that it builds against libboost-dev instead of libboost1.54-dev? It will make future transitions easier. Thank you. https://release.debian.org/transitions/html/boost1.55.html https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744171 ~Scott ---End Message--- ---BeginMessage--- Source: ogre-1.9 Source-Version: 1.9.0+dfsg1-2 We believe that the bug you reported is fixed in the latest version of ogre-1.9, 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 749...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Manuel A. Fernandez Montecelo m...@debian.org (supplier of updated ogre-1.9 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: Wed, 25 Jun 2014 21:12:05 +0100 Source: ogre-1.9 Binary: libogre-1.9-dev libogre-1.9.0 libogre-1.9.0-dbg ogre-1.9-doc ogre-1.9-tools blender-ogrexml-1.9 Architecture: source amd64 all Version: 1.9.0+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Manuel A. Fernandez Montecelo m...@debian.org Description: blender-ogrexml-1.9 - Blender Exporter for OGRE libogre-1.9-dev - 3D Object-Oriented Graphics Rendering Engine (development files) libogre-1.9.0 - 3D Object-Oriented Graphics Rendering Engine (libraries) libogre-1.9.0-dbg - 3D Object-Oriented Graphics Rendering Engine (debugging libs) ogre-1.9-doc - 3D Object-Oriented Graphics Rendering Engine (documentation) ogre-1.9-tools - 3D Object-Oriented Graphics Rendering Engine (tools) Closes: 749944 Changes: ogre-1.9 (1.9.0+dfsg1-2) unstable; urgency=medium . * Change dependencies on Boost to the default versions (Closes: #749944) * Bump Standards-Version to 3.9.5 (no changes needed) Checksums-Sha1: 34c9fec40a0d925b9042abfc17a2d5ceb5e76f72 2684 ogre-1.9_1.9.0+dfsg1-2.dsc 190c9763002b1620a5f98fa5aac1e6ed45c2fb36 23304 ogre-1.9_1.9.0+dfsg1-2.debian.tar.xz 0f776f7d021f3140876ba19c7ae32d12322de248 964060 libogre-1.9-dev_1.9.0+dfsg1-2_amd64.deb c9d43d4b70ebe9c306ba773405fbd8a22c09a63f 2835948 libogre-1.9.0_1.9.0+dfsg1-2_amd64.deb afc47d871a3e2bc4e8414ef45b257c5e8dc37656 44458216 libogre-1.9.0-dbg_1.9.0+dfsg1-2_amd64.deb 99554279ed9107213c76a833503a477a1263e43d 16565782 ogre-1.9-doc_1.9.0+dfsg1-2_all.deb bde26bb97c4d1aadc2ecef69f083c4c436ef9720 145716 ogre-1.9-tools_1.9.0+dfsg1-2_amd64.deb 5be9cf14bd538df05239b4dda5bc7ae56e65 165814 blender-ogrexml-1.9_1.9.0+dfsg1-2_all.deb Checksums-Sha256: 6417af45e5bb4942c4367ea92065cd8e75b3ffc59f3c9b12ce331724cbd15956 2684 ogre-1.9_1.9.0+dfsg1-2.dsc c78e719fe5f781f7adeb4b7e072a66e1b0d36ac9482c94ecb677b03869136b85 23304 ogre-1.9_1.9.0+dfsg1-2.debian.tar.xz 5dc7aba1f6e0b8110ec8f470c73856065ea8071562a4ba372ca9bf82de0440ce 964060 libogre-1.9-dev_1.9.0+dfsg1-2_amd64.deb 28ab2ed8eb8061b1ee79e361f9e384583699468d3d462e0b83d8876a6ca71d14 2835948 libogre-1.9.0_1.9.0+dfsg1-2_amd64.deb b50506def61db94bda1c4785fe1a0e562683d7bf31423583b15e0d8f84ade759 44458216 libogre-1.9.0-dbg_1.9.0+dfsg1-2_amd64.deb 410a2e6c80d1591af7e04935f5460118ab1929c95d79a802673cdaada03c4c6a 16565782 ogre-1.9-doc_1.9.0+dfsg1-2_all.deb b9b94ee1713686034645abc26bd1626fbe1e6f332948cf50e9ac758b72ecd975 145716 ogre-1.9-tools_1.9.0+dfsg1-2_amd64.deb 205d74c9ec96214a089235265695719e94b5aa879f2244b6e8ae490f92f36b90 165814 blender-ogrexml-1.9_1.9.0+dfsg1-2_all.deb Files: 7015e2e670656a66a4bcd1344f9db8c0 964060 libdevel optional libogre-1.9-dev_1.9.0+dfsg1-2_amd64.deb 66bb97085a08aaf274cd38a16845dcfd 2835948 libs optional
Bug#751691: marked as done (freeorion: FTBFS - build depends on libboost-all-dev and libogre-1.9-dev)
Your message dated Wed, 25 Jun 2014 22:34:46 + with message-id e1wzvma-0005cn...@franck.debian.org and subject line Bug#749944: fixed in ogre-1.9 1.9.0+dfsg1-2 has caused the Debian Bug report #749944, regarding freeorion: FTBFS - build depends on libboost-all-dev and libogre-1.9-dev 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.) -- 749944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: freeorion Version: 0.4.3+svn7114-2 Severity: serious Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. [...] - Attempting to parse the build-deps - Considering build-dep cmake - Trying cmake - Considering build-dep debhelper (= 9) - Trying debhelper - Considering build-dep dpkg-dev (= 1.17) - Trying dpkg-dev - Considering build-dep libalut-dev - Trying libalut-dev - Considering build-dep libboost-all-dev - Trying libboost-all-dev - Considering build-dep libbullet-dev - Trying libbullet-dev - Considering build-dep libfreetype6-dev - Trying libfreetype6-dev - Considering build-dep libgl1-mesa-dev - Trying libgl1-mesa-dev - Considering build-dep libglu1-mesa-dev - Trying libglu1-mesa-dev - Considering build-dep libjpeg8-dev - Trying libjpeg8-dev - Considering build-dep libltdl-dev - Trying libltdl-dev - Considering build-dep libogg-dev - Trying libogg-dev - Considering build-dep libogre-1.9-dev - Trying libogre-1.9-dev - Cannot install libogre-1.9-dev; apt errors follow: Reading package lists... Building dependency tree... Reading state information... dpkg-dev is already the newest version. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libogre-1.9-dev : Depends: libboost1.54-dev but it is not going to be installed Depends: libboost-thread1.54-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. E: Could not satisfy build-dependency. The problem here is that libboost-all-dev is Boost version 1.55.0.2 now, hence libogre-1.9-dev's firm dependency on version 1.54 cannot be satisfied. It may be the case that libogre-1.9-dev should be ported to Boost version 1.55.0.2, which I cannot judge. Best, Michael pgp1wpIvUMdCj.pgp Description: PGP signature ---End Message--- ---BeginMessage--- Source: ogre-1.9 Source-Version: 1.9.0+dfsg1-2 We believe that the bug you reported is fixed in the latest version of ogre-1.9, 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 749...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Manuel A. Fernandez Montecelo m...@debian.org (supplier of updated ogre-1.9 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: Wed, 25 Jun 2014 21:12:05 +0100 Source: ogre-1.9 Binary: libogre-1.9-dev libogre-1.9.0 libogre-1.9.0-dbg ogre-1.9-doc ogre-1.9-tools blender-ogrexml-1.9 Architecture: source amd64 all Version: 1.9.0+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Manuel A. Fernandez Montecelo m...@debian.org Description: blender-ogrexml-1.9 - Blender Exporter for OGRE libogre-1.9-dev - 3D Object-Oriented Graphics Rendering Engine (development files) libogre-1.9.0 - 3D Object-Oriented Graphics Rendering Engine (libraries) libogre-1.9.0-dbg - 3D Object-Oriented Graphics Rendering Engine (debugging libs) ogre-1.9-doc - 3D Object-Oriented Graphics Rendering Engine (documentation) ogre-1.9-tools - 3D Object-Oriented Graphics Rendering Engine (tools) Closes: 749944 Changes: ogre-1.9 (1.9.0+dfsg1-2) unstable; urgency=medium . * Change dependencies on Boost to the default versions (Closes: #749944) * Bump Standards-Version
Bug#749944: build ogre-1.9 against new boost-defaults 1.55?
Control: forwarded -1 https://ogre3d.atlassian.net/browse/OGRE-420 2014-06-13 6:21 GMT+01:00 Scott Howard showard...@gmail.com: block 744171 by 749944 thanks On Sun, Jun 1, 2014 at 12:29 PM, Manuel A. Fernandez Montecelo manuel.montez...@gmail.com wrote: I don't know if I mention this to them in the past. It happened in a time when development was not very active and the old leader had to retire for some reason, I think. Since then, I submitted bugs that they fixed like inclusion of 3rd party library code, co-installability of different versions, support for new ports, etc. I will forward this to them hopefully soonish (but not now). If somebody beats me to it, I will not complain! :-) Cheers and thanks for your help. Thank you, sounds reasonable. FYI: freeorion FTBFS too. Putting a block on the transition bug so it shows up on their radar too. https://buildd.debian.org/status/package.php?p=freeorion I just uploaded a version depending on libboost*-dev, without versions (and closing this bug report); and forwarded the bug report upstream (URL above) as follow-up action, as per discussed previously. I am aware that setting this as forwarded and closing at the same time is a bit contradictory, but the main issue requested is fixed and I wanted to document the upstream bug somewhere. If from the discussion with upstream this requires a follow up in the mid-long term, I will open another bug report to better track its development. Cheers. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com -- 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#749944: build ogre-1.9 against new boost-defaults 1.55?
Processing control commands:
forwarded -1 https://ogre3d.atlassian.net/browse/OGRE-420
Bug #749944 {Done: m...@debian.org (Manuel A. Fernandez Montecelo)}
[src:ogre-1.9] build ogre-1.9 against new boost-defaults 1.55?
Bug #751691 {Done: m...@debian.org (Manuel A. Fernandez Montecelo)}
[src:ogre-1.9] freeorion: FTBFS - build depends on libboost-all-dev and
libogre-1.9-dev
Set Bug forwarded-to-address to 'https://ogre3d.atlassian.net/browse/OGRE-420'.
Set Bug forwarded-to-address to 'https://ogre3d.atlassian.net/browse/OGRE-420'.
--
749944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749944
751691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751691
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: reassign 752670 to udev, forcibly merging 752591 752670
Processing commands for cont...@bugs.debian.org:
reassign 752670 udev
Bug #752670 [systemd] systemd: breaks USB stick detection and/or cryptsetup
keyscript
Bug reassigned from package 'systemd' to 'udev'.
No longer marked as found in versions systemd/204-11.
Ignoring request to alter fixed versions of bug #752670 to the same values
previously set
forcemerge 752591 752670
Bug #752591 {Done: Michael Biebl bi...@debian.org} [udev] udev: initrd fails
to create /dev/sda* after udev upgrade
Bug #752605 {Done: Michael Biebl bi...@debian.org} [udev] udev: luks/lvm not
detected rendering system unbootable
Bug #752670 [udev] systemd: breaks USB stick detection and/or cryptsetup
keyscript
Severity set to 'critical' from 'important'
Marked Bug as done
Marked as fixed in versions systemd/204-12.
Marked as found in versions systemd/204-11.
Bug #752605 {Done: Michael Biebl bi...@debian.org} [udev] udev: luks/lvm not
detected rendering system unbootable
Merged 752591 752605 752670
thanks
Stopping processing here.
Please contact me if you need assistance.
--
752591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752591
752605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752605
752670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752670
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#752670: systemd: breaks USB stick detection and/or cryptsetup keyscript
Hi Michael. On Wed, 2014-06-25 at 16:15 +0200, Michael Biebl wrote: Looks like a duplicate of #752591/#752605 -12 has been uploaded already. You can either wait for that or apply the fix manually. Please confirm if -12 (or the fix [1]) works for you. Just arrived at home and could verify it... it works again with -12... AFAICS you've already merged it with #752591. Thanks, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#752734: twidge: Segmentation Fault on setup
Package: twidge
Version: 1.1.2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
'twidge setup' results in a segfault and nothing is written tot he config file.
Twidge remains in an unusable state since it's not authentified to twitter.
Debug output:
$ twidge -d setup
CP /home/bsp/.twidgerc exists? True
Welcome to twidge. We will now configure twidge for your
use with Twitter (or a similar service). This will be quick and easy!
Please wait a moment while I query the server...
Trying first signRq2
First signRq2 result: OAuthRequest {unpackRq = ReqHttp {version = HTTP/1.1, ssl
= True, host = api.twitter.com, port = 443, method = GET, reqHeaders =
Authorization=OAuth%20oauth_signature%3D%22LforbyZZHk2YBsNLvX7d6YWANOM%253D%22%2Coauth_consumer_key%3D%22pzWekpM5IRh7HaKc9syEw%22%2Coauth_nonce%3D%22FKfnWVEpTJumxIJqIxLz%252BAzyaLYM94Y%252FefPdZdmd5ks%253D%22%2Coauth_timestamp%3D%221403741035%22%2Coauth_signature_method%3D%22HMAC-SHA1%22%2Coauth_version%3D%221.0%22%2Coauth_callback%3D%22oob%22,
pathComps = [,oauth,request_token], qString = , reqPayload = ,
multipartPayload = []}}
OK, next I need you to authorize Twidge to access your account.
Please cut and paste this URL and open it in a web browser:
https://api.twitter.com/oauth/authorize?oauth_token=REDACTED
Click Allow when prompted. You will be given a numeric
key in your browser window. Copy and paste it here.
(NOTE: some non-Twitter services supply no key; just leave this blank
if you don't get one.)
Authorization key: 2106649
Trying second signRq2
Second signRq2 result: OAuthRequest {unpackRq = ReqHttp {version = HTTP/1.1,
ssl = True, host = api.twitter.com, port = 443, method = GET, reqHeaders =
Authorization=OAuth%20oauth_signature%3D%REDACTED%2Coauth_consumer_key%3D%REDACTED%22%2Coauth_nonce%3D%REDACTED%253D%22%2Coauth_timestamp%3D%221403741063%22%2Coauth_signature_method%3D%22HMAC-SHA1%22%2Coauth_version%3D%221.0%22%2Coauth_verifier%3D%REDACTED%22%2Coauth_token%3D%REDACTED,
pathComps = [,oauth,access_token], qString = , reqPayload = ,
multipartPayload = []}}
Got token: AccessToken Application REDACTED REDACTED oob
user_id=REDACTEDscreen_name=myscreennameoauth_verifier=2106649oauth_token=REDACTEDoauth_token_secret=REDACTEDoauth_callback_confirmed=true
Segmentation fault
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing'), (200, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.14-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages twidge depends on:
ii curl 7.37.0-1+b1
ii libc62.19-3
ii libcurl3-gnutls 7.37.0-1+b1
ii libffi6 3.1-2
ii libgmp10 2:6.0.0+dfsg-4
twidge recommends no packages.
twidge 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#750090: Need more information
Hi, Looking at http://www.gnu.org/software/gettext/manual/html_node/autopoint-Invocation.html it does seem that autopoint could be needed to build shadow, since a AM_GNU_GETTEXT_VERSION does show up in configure.in. The autopoint dependency is probably usually satisfied due to a Recommends in gettext, which in turn shadow does build-dep on. However since it is only a recommends, this won't always be the case. Nevertheless, when I dpkg -r autopoint on a wheezy chroot and build shadow, the package succesfully builds. Thomas, could you please tell us exactly how the build broke for you without autopoint? I.e show us the full build logs. -- 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#750001: freedink-dfarc: Please update to wxwidgets3.0
Processing commands for cont...@bugs.debian.org: # blocks the on-going wxwidgets3.0 transition severity 750001 serious Bug #750001 [freedink-dfarc] freedink-dfarc: Please update to wxwidgets3.0 Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 750001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750001 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: severity of 749861 is serious
Processing commands for cont...@bugs.debian.org: # blocks the on-going wxwidgets3.0 transition severity 749861 serious Bug #749861 [src:qutemol] qutemol: Please update to use wxwidgets3.0 Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 749861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749861 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#752378: marked as done (FTBFS: Missing python libraries in B-D-I)
Your message dated Thu, 26 Jun 2014 03:34:08 + with message-id e1x00rs-0003bw...@franck.debian.org and subject line Bug#752378: fixed in awscli 1.3.18-2 has caused the Debian Bug report #752378, regarding FTBFS: Missing python libraries in B-D-I 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.) -- 752378: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: awscli Severity: serious Tags: patch Hi, the pacakge FTBFS in a Debian Sid clean chroot, please take a look to the patch. There is a missing python libraries in package build depends. == ERROR: awscli.testutils (unittest.loader.ModuleImportFailure) -- Traceback (most recent call last): File /usr/lib/python3.4/unittest/case.py, line 58, in testPartExecutor yield File /usr/lib/python3.4/unittest/case.py, line 577, in run testMethod() File /usr/lib/python3.4/unittest/loader.py, line 32, in testFailure raise exception ImportError: Failed to import test module: awscli.testutils Traceback (most recent call last): File /usr/lib/python3.4/unittest/loader.py, line 312, in _find_tests module = self._get_module_from_name(name) File /usr/lib/python3.4/unittest/loader.py, line 290, in _get_module_from_name __import__(name) File /build/buildd/awscli-1.3.18/.pybuild/pythonX.Y_3.4/build/awscli/testutils.py, line 44, in module import six ImportError: No module named 'six' Cheers, -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru awscli-1.3.18/debian/changelog awscli-1.3.18/debian/changelog --- awscli-1.3.18/debian/changelog 2014-06-22 16:53:48.0 +0200 +++ awscli-1.3.18/debian/changelog 2014-06-23 09:51:16.0 +0200 @@ -1,3 +1,15 @@ +awscli (1.3.18-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add missing Build-Depends-Indep, fix FTBFS: +- python3-six +- python3-botocore +- python3-colorama +- python3-docutils +- python3-bcdoc + + -- Angel Abad an...@debian.org Mon, 23 Jun 2014 09:50:18 +0200 + awscli (1.3.18-1) unstable; urgency=medium * New upstream release (Closes: #744890) diff -Nru awscli-1.3.18/debian/control awscli-1.3.18/debian/control --- awscli-1.3.18/debian/control 2014-01-04 09:19:47.0 +0100 +++ awscli-1.3.18/debian/control 2014-06-23 09:52:01.0 +0200 @@ -6,6 +6,11 @@ Build-Depends: debhelper (= 9) , python3 , python3-setuptools +Build-Depends-Indep: python3-six +, python3-botocore +, python3-colorama +, python3-docutils +, python3-bcdoc Standards-Version: 3.9.5 Homepage: http://aws.amazon.com/cli/ Vcs-Svn: svn://anonscm.debian.org/python-apps/packages/awscli/trunk/ ---End Message--- ---BeginMessage--- Source: awscli Source-Version: 1.3.18-2 We believe that the bug you reported is fixed in the latest version of awscli, 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 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. TANIGUCHI Takaki tak...@debian.org (supplier of updated awscli 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: Thu, 26 Jun 2014 11:12:42 +0900 Source: awscli Binary: awscli Architecture: source all Version: 1.3.18-2 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team python-apps-t...@lists.alioth.debian.org Changed-By: TANIGUCHI Takaki tak...@debian.org Description: awscli - Universal Command Line Environment for AWS Closes: 752378 Changes: awscli (1.3.18-2) unstable; urgency=medium . [ Angel Abad ] * Add missing Build-Depends-Indep, fix FTBFS (Closes: 752378) : - python3-six - python3-botocore - python3-colorama - python3-docutils
Bug#752727: marked as done (yodl: FTBFS - missing build dep on cm-super-minimal)
Your message dated Thu, 26 Jun 2014 04:19:00 + with message-id e1x019i-00017m...@franck.debian.org and subject line Bug#752727: fixed in yodl 3.03.0-3 has caused the Debian Bug report #752727, regarding yodl: FTBFS - missing build dep on cm-super-minimal 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.) -- 752727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: yodl Version: 3.03.0-2 Severity: serious Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. [...] dvips -o yodl.ps yodl.dvi This is dvips(k) 5.994 Copyright 2014 Radical Eye Software (www.radicaleye.com) ' TeX output 2014.06.25:2224' - yodl.ps dvips: ! Couldn't find header file: cm-super-t1.enc system - failure of system call (status 256) system - failure of system call (status 256) debian/rules:60: recipe for target 'build-indep' failed make: *** [build-indep] Error 1 The full build log is attached; I believe the build dependencies need to be adjusted, adding cm-super-minimal. Best, Michael yodl-build-log.txt.gz Description: application/gunzip pgpX_moraUXSP.pgp Description: PGP signature ---End Message--- ---BeginMessage--- Source: yodl Source-Version: 3.03.0-3 We believe that the bug you reported is fixed in the latest version of yodl, 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 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill tmanc...@debian.org (supplier of updated yodl 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: Wed, 25 Jun 2014 20:06:41 -0700 Source: yodl Binary: yodl yodl-doc Architecture: source amd64 all Version: 3.03.0-3 Distribution: unstable Urgency: medium Maintainer: Frank B. Brokken f.b.brok...@rug.nl Changed-By: tony mancill tmanc...@debian.org Description: yodl - Your Own Document Language (Yodl) is a pre-document language yodl-doc - Documenation for Your Own Document Language (Yodl) Closes: 752727 Changes: yodl (3.03.0-3) unstable; urgency=medium . * Add build dependency on cm-super-minimal. (Closes: #752727) - Thank you to Michael Tautschnig for the bug report. * Bump Standards-Version to 3.9.5 * Drop hardening-wrapper; pass CPPFLAGS to build system via CFLAGS. Checksums-Sha1: e7f140b79048ce2b5f5d9533f5b3935aa006a402 2133 yodl_3.03.0-3.dsc e6b004e5987744416daf2b4146b623c122c6a8f6 10336 yodl_3.03.0-3.debian.tar.xz 9d91eca55dc7145391c5016d8bfcbf7863accc59 136576 yodl_3.03.0-3_amd64.deb ede0990228d55a2fad08a97a66e4a1cb47a792ab 1477086 yodl-doc_3.03.0-3_all.deb Checksums-Sha256: 58b1dc0af14179bef982f6df8eee55d9dcfa90fa669a3030ac4fa14e47877ee2 2133 yodl_3.03.0-3.dsc a4ca830339e10bd56bec5c6e641c380eace56d1d6eb0e99779580d89f8efec16 10336 yodl_3.03.0-3.debian.tar.xz 203ac5cd2af774c9fdfb88a1393d4258936bc97c045f86a966b7e1a802372565 136576 yodl_3.03.0-3_amd64.deb 9bd107052439643776e191a27c8fe7448b4ed91d6525b76398403ad010cec5e1 1477086 yodl-doc_3.03.0-3_all.deb Files: 9b35e4c5721f7c6c1dce4935f70967b0 136576 text optional yodl_3.03.0-3_amd64.deb b4c69b3f4c4ccdc2d5c08e699c8ff7db 1477086 doc optional yodl-doc_3.03.0-3_all.deb 03304f6daf62b11241c8feb272d2c57f 2133 text optional yodl_3.03.0-3.dsc b1b63706502409e8d4b9bd8f8fe049cd 10336 text optional yodl_3.03.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJTq5uXAAoJECHSBYmXSz6WaaEP/1Sj/qhTyg9EX/1WePO8VJFZ z2LgMdMn4V7IJKjPogzRL7YBhvwsooxsO7jFQoWe2UmB/cjwJbeXEhR72IyV7c3c HMm9FscAYt+mElBEsZd+j2Dy0GpdWp6DhS6i1gBsEh1cM7b+120DFfeoc9JB3z0N pvY74CWIHrNV+lOhzmNl4tqOu0bFKACTtr6NKNtywRYKzT5Gve389Gr0QaEZj0YM /Rg/d0gAjZfQGp0WQwQBwadBoeiywI/r3v1YhWfVK+MGayzc+1vb+7+T+SFur2UZ fDZOQ+juTK3azbBu7mrXBcY7hF5qJdbh5KwecBTgiQzku7HoxdYf3a/D0uPKevAM NAnvXIOt3vmoawwaFzd6dFk8j8Dtoacgva/i0xEuCqvCLhHpo078DJgsKbkwHN2d sMMd6+gj1Ve8uvA3meF+rtj6nX5cGM0gF5MM1r6OhI4VyvrfXAU+K4AtX2qf8Idc WWs6xq1Hig7+D2kuHYWHuhFrQNLd4m3V1j2aOqaO06gi0ax5G8eBA/ESfbI4d7i6 o9WICwZh0jqYaOwaLgTLkbFD/0vIA6m7bO2NbEFHWJ9e3orzNtUzK2fhi57z73pt
