Bug#689109: Bug#685540: asterisk-flite, asterisk-espeak: binnmu required
Hi Jonas, On Wed, Nov 14, 2012 at 12:33:26PM +0100, Jonas Smedegaard wrote: Quoting Tzafrir Cohen (2012-11-13 18:00:30) Indeed this is fixable through a binNMU. Yes, but release managers disapprove of simple binNMUs covering over the underlying problem, as I wrote earlier: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685540#20 The proper fix is this combo: 1) File bugreport against asterisk-dev about broken/missing hints about shared library. 2) Fix bug filed in 1). Asterisk now provides asterisk-hash-of-build-options. This includes the version. A module can safely depend on those (but it should be updated on backporting). Would you mind fixing the packages (asterisk-flite, and asterisk-espeak)? Would you like me to? The new upstream release also fixes building with asterisk-11 and asterisk-13 (a separate bug filed). -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 765681 to libqtcore4-perl
Processing commands for cont...@bugs.debian.org: reassign 765681 libqtcore4-perl Bug #765681 [libqtgui4-perl] libqtgui4-perl: QtGui4 module cannot be imported Bug reassigned from package 'libqtgui4-perl' to 'libqtcore4-perl'. No longer marked as found in versions qt4-perl/4.8.4-1.1. Ignoring request to alter fixed versions of bug #765681 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 765681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765681 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: affects 767411, affects 767411
Processing commands for cont...@bugs.debian.org: affects 767411 + src:openmpi Bug #767411 [src:torque] torque: should not be released with jessie Added indication that 767411 affects src:openmpi affects 767411 + src:pbs-drmaa Bug #767411 [src:torque] torque: should not be released with jessie Added indication that 767411 affects src:pbs-drmaa thanks Stopping processing here. Please contact me if you need assistance. -- 767411: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767411 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#767230: libotr transition started by mistake :-/ [Was: Bug#767230: bitlbee-plugin-otr: bitlbee no longer starts: libotr API version 4.1.0 incompatible with actual version 4.0.0]
On 2014-10-31 00:41, Ian Goldberg wrote: On Thu, Oct 30, 2014 at 11:05:20PM +0100, Niels Thykier wrote: Control: severity 767230 serious On 2014-10-29 17:09, intrigeri wrote: Hi Sebastian, hi release team, [...] Looking through the diff between the version of libotr in testing vs. the version in sid. I saw no obvious ABI / API breakage myself - that said I would certainly would not mind a second (third?) reviewer reviewing this assertion though. Preferably one who knows the C ABI rules by heart. Hi Ian, For the record, the difference between the APIs of libotr 4.0.0 and libotr 4.1.0 is that two functions that existed in 4.0.0 but were not contained in the .h files (and thus could not appear in applications) were added to the .h files in 4.1.0. Actually, the deciding factor is whether they were exported by the shared library[0]. If they were exported, then an external program could use them regardless of whether they appeared in a header file of libotr[1]. This also implies that the functions would already have been a part of the ABI. In summary, if libotr exported those functions in 4.0.0 *and* broke their ABI as well, libotr would have broken its ABI in 4.1.0 and would require a SONAME bump. Otherwise, I think we are good. So if an application uses those functions, it would require to be built against libotr 4.1.0. Any application compiled against 4.0.0 will work with 4.1.0, but not vice versa (because of those two new functions). That's the reason for the minor version number change, and the corresponding libtool version 6:0:1. It's also why if you build against the 4.1.0 header files, it wants you to have at least 4.1.0 at runtime. - Ian Certainly. In Debian, we use shlib or symbols file to declare such changes and our build tools will compute the necessary dependency automatically. Assuming these files were correct in the 4.1.0 upload, this would not be an issue for any Debian maintained reverse dependency. As noted above, it might /not/ be a mistake if these files are identical to the ones in 4.0.0 (assuming 4.0.0 already exported the symbols). ~Niels [0] I know of several people (upstream and debian maintainers alike) that were surprised by a library exporting what they thought were internal functions. As I recall, C static functions are never exported. Others usually need explicit symbol hiding or a symbol file to declare them as private. I believe readelf -Ws path/to/libotr.so will tell you what is exported (and what is imported). I sadly don't remember the relevant grep -v magic to filter out all the parts you don't need. [1] E.g. the reverse dependency could declare the function themselves without ever implementing a la: extern int * unmentioned_libotr_function(void *arg1, size_t arg2, ...); -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 765681 is forwarded to https://bugs.kde.org/show_bug.cgi?id=340518
Processing commands for cont...@bugs.debian.org: forwarded 765681 https://bugs.kde.org/show_bug.cgi?id=340518 Bug #765681 [libqtcore4-perl] libqtgui4-perl: QtGui4 module cannot be imported Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=340518'. thanks Stopping processing here. Please contact me if you need assistance. -- 765681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765681 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#765681: libqtgui4-perl: QtGui4 module cannot be imported
There are fixes required for both QtCore4.pm and QtGui4.pm (my reassign was a
tad quick, but it doesn't really matter too much).
The fix for QtCore4.pm (backported from a later upstream release) is attached.
A partial fix for QtGui4.pm is available in the Red Hat bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1136340
As can be seen from the forwarded information in the bug now, I also filed a
bug upstream for this.
That's about as far as I think I can take this.
Scott K--- a/QtCore4.pm2012-02-29 17:56:20.0 -0500
+++ b/QtCore4.pm 2013-11-02 14:10:01.0 -0400
@@ -1417,9 +1420,9 @@
my $signals = $meta-{signals};
my $slots = $meta-{slots};
-@{$classinfos} = () if !defined @{$classinfos};
-@{$signals} = () if !defined @{$signals};
-@{$slots} = () if !defined @{$slots};
+@{$classinfos} = () if !defined $classinfos;
+@{$signals} = () if !defined $signals;
+@{$slots} = () if !defined $slots;
# Each entry in 'stringdata' corresponds to a string in the
# qt_meta_stringdata_classname structure.
Bug#764930: beignet: FTBFS - uses versioned llvm commands, but unversioned build dependency
On 2014-10-30 21:10, Rebecca N. Palmer wrote: If you're offering to NMU this, it would be a good idea to put back the patch description header I accidentally deleted, and to do #767387 at the same time. I've imported the packaging history into git and prepared the new upstream there, too. This should solve all the llvm related issues. anonscm.debian.org/pkg-opencl/beignet.git I could NMU, but Rebecca filed another RC bug yesterday ... :-) Please check whether this updated packaging really solves all the current issues (and whether the non-free bits are still present - reply to the relevant bug, not here). Please send updated patches against the git repo, not the old 0.8 packages ... Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767210: marked as done (matplotlib: FTBFS on kfreebsd-i386 and s390x)
Your message dated Fri, 31 Oct 2014 07:49:25 + with message-id e1xk6xz-0002pz...@franck.debian.org and subject line Bug#767210: fixed in matplotlib 1.4.2-3 has caused the Debian Bug report #767210, regarding matplotlib: FTBFS on kfreebsd-i386 and s390x 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.) -- 767210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: matplotlib Version: 1.4.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, your package no longer builds on the kfreebsd-i386 and s390x buildds: Build killed with signal TERM after 150 minutes of inactivity See the logs at https://buildd.debian.org/status/logs.php?pkg=matplotlibver=1.4.2-1suite=sid Cheers, Julien signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: matplotlib Source-Version: 1.4.2-3 We believe that the bug you reported is fixed in the latest version of matplotlib, 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 767...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi mo...@debian.org (supplier of updated matplotlib 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: Thu, 30 Oct 2014 23:31:03 + Source: matplotlib Binary: python-matplotlib python3-matplotlib python-matplotlib-data python-matplotlib-doc python-matplotlib-dbg python3-matplotlib-dbg Architecture: source all amd64 Version: 1.4.2-3 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi mo...@debian.org Changed-By: Sandro Tosi mo...@debian.org Description: python-matplotlib - Python based plotting system in a style similar to Matlab python-matplotlib-data - Python based plotting system (data package) python-matplotlib-dbg - Python based plotting system (debug extension) python-matplotlib-doc - Python based plotting system (documentation package) python3-matplotlib - Python based plotting system in a style similar to Matlab (Python python3-matplotlib-dbg - Python based plotting system (debug extension, Python 3) Closes: 767210 Changes: matplotlib (1.4.2-3) unstable; urgency=medium . * debian/patches/test_backend_with_timeout.patch - fixed patch to correctly terminating run-away processes during backend checks; Closes: #767210 Checksums-Sha1: 07e6e23d5e2e1bbd8fb00af9ef8719cdcaaa3c54 2757 matplotlib_1.4.2-3.dsc d02d1d16ce1f0b27c5cd5e3061366154a4123059 26052 matplotlib_1.4.2-3.debian.tar.xz 9f87ac34732ad98ad8bcd77bdea2fd8a9bcb8653 3039468 python-matplotlib-data_1.4.2-3_all.deb 2bde6e423efb0ba7a511c018d1d37c2b5f881453 73990626 python-matplotlib-doc_1.4.2-3_all.deb 8ed46349aeb7e3f64ae1be95bdfbd069d68c442a 3778174 python-matplotlib_1.4.2-3_amd64.deb ec1ecf86807f3b8bee805ce294aeff4d72ccb361 3742420 python3-matplotlib_1.4.2-3_amd64.deb 8a9fecfc2ab842e31f14e903bcb66ddaf61d 8593308 python-matplotlib-dbg_1.4.2-3_amd64.deb 7ac24128f8ebce89f2c5847116142c70a80ad837 832236 python3-matplotlib-dbg_1.4.2-3_amd64.deb Checksums-Sha256: e0a80471121633cfaed0b92c5218532260d1bc86846554ccdd8d5d959fe4a902 2757 matplotlib_1.4.2-3.dsc dac2ce8bb2f18daca416c42024180ff74db21c78b2f50099285f39ddcbcf2def 26052 matplotlib_1.4.2-3.debian.tar.xz ff46f9b7c107b71dd0c52aeabe760843e4c1b461301b72048aeba8421d3558f9 3039468 python-matplotlib-data_1.4.2-3_all.deb ed6d2fee04204c80732770c8516cc49e55cf2e46b52aa7b7c6d05403d432ed0f 73990626 python-matplotlib-doc_1.4.2-3_all.deb c08dd912ba5bf06d802ee7cd2bda605a678250291761fdbdbf605f0196b4 3778174 python-matplotlib_1.4.2-3_amd64.deb d1661c9a6cd71bc32d33d6566aadcd4dc83237aa7a6e735c3557e78fbb0b50c6 3742420 python3-matplotlib_1.4.2-3_amd64.deb ee8f3dc7e068230c2ac6a719cf9868bda66759ec473296b15acbb69832f09ca5 8593308 python-matplotlib-dbg_1.4.2-3_amd64.deb 0fe7358ca439904326be475dbab8c498c46029ea56e877f570ddbec34a04b564 832236 python3-matplotlib-dbg_1.4.2-3_amd64.deb Files: de7d97bf7aaf4f97f6ee0c7bc99d19b9 2757 python optional matplotlib_1.4.2-3.dsc 3c02431b1b9fddb580a581f121018642 26052 python optional
Bug#727149: linux-image-3.10-3-amd64: Network adapter (Intel 82579V) hangs during TX, causing reset and undetected data corruption at the other side
On Sun, 14 Sep 2014 00:52:55 +0200 Balint Reczey bal...@balintreczey.hu wrote: Control: tags -1 moreinfo Hi, On Wed, 23 Oct 2013 18:06:03 +0200 T.A. van Roermund t...@van-roermund.nl wrote: On 22-10-2013 20:02, T.A. van Roermund wrote: In the mean time I have found a solution to this problem: if I disable TCP segmentation offload using the command 'ethtool -K eth2 tso off', the problem does no longer occur. By the way: I found the solution here: https://bbs.archlinux.org/viewtopic.php?id=162841 Is this problem still present with latest kernel from Jessie? Forgot copying submitter, now fixing my mistake. Cheers, Balint -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767460: php-htmlpurifier: Missing versioned dependency on dpkg
Package: php-htmlpurifier Version: 4.6.0-1 Severity: serious Hi, When installing php-htmlpurifier on a testing system, I get the folowing error messages: , | Selecting previously unselected package php-htmlpurifier. | Preparing to unpack .../php-htmlpurifier_4.6.0-1_all.deb ... | dpkg-maintscript-helper: error: original symlink target is not an absolute path | dpkg: error processing archive /var/cache/apt/archives/php-htmlpurifier_4.6.0-1_all.deb (--unpack): | subprocess new pre-installation script returned error exit status 1 | dpkg-maintscript-helper: error: original symlink target is not an absolute path | dpkg: error while cleaning up: | subprocess new post-removal script returned error exit status 1 ` Indeed, the debian/maintscript involves relative symlinks. However, according to dpkg's changelog, such relative symlinks have only been supported since 1.17.14. So the php-htmlpurifier currently in testing can't be installed by the dpkg currently in testing. I guess a simple versioned dependency would fix that (alternatively, a rewrite of the maintscript to use absolute targets for the symlinks). Thanks, Roland. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages php-htmlpurifier depends on: ii dpkg 1.17.21 ii php5-common 5.6.2+dfsg-1 php-htmlpurifier recommends no packages. php-htmlpurifier suggests no packages. -- no debconf information -- Roland Mas La menace de la baffe pèse plus lourd que la baffe elle-même. -- in Sri Raoul le petit yogi (Gaudelette) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766195: [PATCH] ipv6: reuse ip6_frag_id from ip6_ufo_append_data
On 30.10.2014 20:00, Ben Hutchings wrote: [...] Yes, I can see how this (disabling virtio features) would prevent live migration from old to new host kernels. You will probably need a one-time reboot of the guest when migrating to the new host kernel. We could either mention this in the DSA text, or keep UFO enabled even though it doesn't work correctly (in practice, we sort of have to do that as the tap device's feature flags aren't respected by guests - which I think is a QEMU bug). Please let us know whether live migration between two hosts running the new kernel version does work (I think it will). I confirm that. Although I did not exactly test this because of some constraints. I tested with virsh save/restore which uses the same codepaths as virsh migrate I think. This cold migration spewed out the same error messages as written earlier when migrating from old to new. And it went fine from new to new. BTW I use a patched qemu-kvm because of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724758. So maybe there are only a few wheezy users doing live migrations. Cheers Harry -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764930: beignet: FTBFS - uses versioned llvm commands, but unversioned build dependency
Just want to mention, the beignet version 1.0 will be released within two weeks, if everything is ok. And all the known copyright issue will be solved before that. Thanks, Zhigang Gong. On Fri, Oct 31, 2014 at 3:37 PM, Andreas Beckmann a...@debian.org wrote: On 2014-10-30 21:10, Rebecca N. Palmer wrote: If you're offering to NMU this, it would be a good idea to put back the patch description header I accidentally deleted, and to do #767387 at the same time. I've imported the packaging history into git and prepared the new upstream there, too. This should solve all the llvm related issues. anonscm.debian.org/pkg-opencl/beignet.git I could NMU, but Rebecca filed another RC bug yesterday ... :-) Please check whether this updated packaging really solves all the current issues (and whether the non-free bits are still present - reply to the relevant bug, not here). Please send updated patches against the git repo, not the old 0.8 packages ... Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 767355 important Bug #767355 [hexbox] System.EntryPointNotFoundException: CreateCaret Severity set to 'important' from 'grave' End of message, stopping processing here. Please contact me if you need assistance. -- 767355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767355 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#767387: beignet: Non-free files in test suite
Control: forwarded -1 http://lists.freedesktop.org/archives/beignet/2014-October/004343.html I have reported this upstream; they have agreed it's a problem and are in the process of removing the first group and investigating the second. To deal with this problem in the meantime, we will need to repack the orig tarball (which the version just added to Alioth does _not_ do); the new version would then conventionally be called 0.8+dfsg1-0.1 or 0.9.3+dfsg1-0.1. Also note that as the first group is undistributable (not just non-DFSG), creating an Alioth repository that includes the previous versions may not be a good idea. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Bug#767387: beignet: Non-free files in test suite
Processing control commands: forwarded -1 http://lists.freedesktop.org/archives/beignet/2014-October/004343.html Bug #767387 [beignet] beignet: Non-free files in test suite Set Bug forwarded-to-address to 'http://lists.freedesktop.org/archives/beignet/2014-October/004343.html'. -- 767387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767387 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#760476: concerning 760476
Hi, I've thought of an alternative path that doesn't require changes into applications that close all descriptors but uses some heuristics to check whether the descriptor is still open (and the same type). If that looks reasonable I plan to include it in the next release of gnutls. https://www.gitorious.org/gnutls/gnutls/commit/684b825f5f78cc7ad1f61be232fd20ee0bc5b56f https://www.gitorious.org/gnutls/gnutls/commit/e8ffb7944037a45e6f2436a3906ce37e5ea97e3e On Wed, Oct 29, 2014 at 1:02 PM, Didier 'OdyX' Raboud o...@debian.org wrote: Hi Nikos, hi Andreas, On Tue, 28 Oct 2014 19:11:28 +0100 Andreas Metzler wrote: On 2014-10-28 Nikos Mavrogiannopoulos n...@gnutls.org wrote: I think that the issue should be reassigned to cups and it should be modified to close the known file descriptors (stdin/stdout/stderr) instead of all open descriptors. Thanks for the explanation. re-assigning. (I will subscribe to the bug-report to keep me updated) Thanks to you two for the investigation; I've brought the issue back up to CUPS's bugtracker, where Michael Sweet wrote on https://www.cups.org/str.php?L4484 : So it looks like you also need to fix GNU TLS to only open /dev/urandom when gnutls_global_init() is called and not before. It appears there's a disagreement between CUPS and GnuTLS on how the file descriptors should be managed. It would be nice if one of you could have the conversation with Michael directly on the CUSP tracker, without me playing the messenger. Nikos: would that be imaginable? TIA, cheers, OdyX -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764162: linux-image-3.16-2-kirkwood: [regression 3.14-3.16] file data corruption, via network
On Sun, 2014-10-19 at 14:27 +0100, Ian Campbell wrote: You could inactivate this feature manually with: ethtool -K eth0 tso off I'm in contact with the developer of this feature. Tell me if this command resolve your problem Excellent, please let us know how you get on (feel free to CC the bug too if you want). Did you make any progress with the developer? In the changes to this driver since v3.16 I see commit 817dbfa5d1bc276a72c1a577310382008e8aca0a Author: Vlad Yasevich vyasev...@gmail.com Date: Mon Aug 25 10:34:54 2014 -0400 mvneta: Fix TSO and checksum for non-acceleration vlan traffic which might be potentially interesting, except no one on this bug has mentioned VLANs at any point. I don't see anything else of interest. Ian. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685540: asterisk-flite, asterisk-espeak: binnmu required
Hi Tzafrir, Quoting Tzafrir Cohen (2014-10-31 07:36:44) On Wed, Nov 14, 2012 at 12:33:26PM +0100, Jonas Smedegaard wrote: Quoting Tzafrir Cohen (2012-11-13 18:00:30) Indeed this is fixable through a binNMU. Yes, but release managers disapprove of simple binNMUs covering over the underlying problem, as I wrote earlier: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685540#20 The proper fix is this combo: 1) File bugreport against asterisk-dev about broken/missing hints about shared library. 2) Fix bug filed in 1). Asterisk now provides asterisk-hash-of-build-options. This includes the version. A module can safely depend on those (but it should be updated on backporting). Would you mind fixing the packages (asterisk-flite, and asterisk-espeak)? Would you like me to? The new upstream release also fixes building with asterisk-11 and asterisk-13 (a separate bug filed). Please feel free to NMU asterisk-flite and asterisk-espeak, or even to take over maintenance of those packages. If you do choose to take over maintenance but want me as co-maintainer, then please do continue to use CDBS for the packaging. Else please remove me as uploader, as I am not comfortable maintaining packages which uses the short-form dh sequencer. I do still have interest in these packages, just find too little time to nurse them properly at the moment. Therefore, if you loose interest in maintaining them then please do not drop them (as happened long time ago with libsrtp¹) but pass them back to me. Same goes for libsrtp. Kind regards, - Jonas ¹ I don't hold a grudge - am just stating as quite related fact -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#767465: Installed Debian Jessie fails to recognize USB flash drive upon reboot
Package: Installation-reports Severity: Serious After successful installation using the USB thumb drive method, the installed OS fails to recognize the same USB drive. Boot method: USB flash drive Image version: Beta 2 installer amd64 DVD1 (burned the ISO to USB stick) Date: Oct 2014 Machine: DIY Partitions: Entire disk drive Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot:[o ] Detect network card:[o ] Configure network: [o ] Detect CD:[o ] Load installer modules:[o ] Clock/timezone setup: [o ] User/password setup: [o ] Detect hard drives: [o ] Partition hard drives:[o ] Install base system: [o ] Install tasks: [ ] Install boot loader: [o ] Overall install: [E ] Comments/Problems: Although I burned the Debian Jessie beta 2 DVD-1 to a USB flash drive, during the installation process, I chose to do a base/net install only as I wanted to install only the packages that I needed. I did not wish to have the full Gnome, KDE, LXDE desktop environments. Upon reboot, I was presented with a black-background console, tty1, and typed in my login username and password. I proceeded to sudo apt-get install xorg gnome-core and failed, the reason being the CDROM was missing. Well, I re-inserted the USB flash drive and re-typed the same command. Again the machine responded with the CDROM was missing. I have been told that the above problem has existed since the days of pre-Debian Wheezy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: jessie
Processing commands for cont...@bugs.debian.org:
tags 765681 + sid jessie
Bug #765681 [libqtcore4-perl] libqtgui4-perl: QtGui4 module cannot be imported
Added tag(s) sid and jessie.
tags 763602 + sid jessie
Bug #763602 {Done: Simon McVittie s...@debian.org} [gtk+2.0] mirage: Attempt
to unlock mutex that was not locked
Added tag(s) sid and jessie.
tags 763625 + sid jessie
Bug #763625 {Done: Simon McVittie s...@debian.org} [gtk+2.0] keepnote fails
with Attempt to unlock mutex that was not locked
Added tag(s) sid and jessie.
tags 767411 + jessie
Bug #767411 [src:torque] torque: should not be released with jessie
Added tag(s) jessie.
End of message, stopping processing here.
Please contact me if you need assistance.
--
763602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763602
763625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763625
765681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765681
767411: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767411
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#747908: [libtuxcap] [transition blocker] Please allow to compile with imagemagick/experimental
Control: tag -1 patch
Control: user ubuntu-de...@lists.ubuntu.com
Control: usertag -1 ubuntu-patch vivid
On Fri, Sep 12, 2014 at 01:14:47PM +0200, Markus Koschany wrote:
On Mon, 12 May 2014 21:33:52 + bastien ROUCARIES
roucaries.bast...@gmail.com wrote:
Please allow libtuxcap to compile with newer imagemagick.
I have a patch to test but due to cmake bug I could not yet test.
Hi,
I have just tested your patch. Unfortunately libtuxcap still FTBFS in
the configure step.
Here's a simpler patch that gets the job done. I effectively replaced
the existing cmake_imagemagick.patch rather than creating too much
patch-on-patch spaghetti there.
* Use pkg-config to get ImageMagick build flags.
diff -u libtuxcap-1.4.0.dfsg2/debian/patches/cmake_imagemagick.patch
libtuxcap-1.4.0.dfsg2/debian/patches/cmake_imagemagick.patch
--- libtuxcap-1.4.0.dfsg2/debian/patches/cmake_imagemagick.patch
+++ libtuxcap-1.4.0.dfsg2/debian/patches/cmake_imagemagick.patch
@@ -1,19 +1,56 @@
-Description: cmake's ImageMagick module seems to have changed and now looks
- for the executables, while we only need the libs here
+Description: Use pkg-config to get ImageMagick build flags
Origin: vendor
-Bug-Debian: http://bugs.debian.org/674369
+Bug-Debian: https://bugs.debian.org/747908
Forwarded: no
-Author: gregor herrmann gre...@debian.org
-Last-Update: 2012-06-07
+Author: Colin Watson cjwat...@ubuntu.com
+Last-Update: 2014-10-31
+Index: b/tuxcap/CMakeLists.txt
+===
--- a/tuxcap/CMakeLists.txt
+++ b/tuxcap/CMakeLists.txt
-@@ -16,7 +16,7 @@
+@@ -16,10 +16,10 @@
Find_Package ( SDL REQUIRED )
Find_Package ( SDL_mixer REQUIRED )
-Find_Package ( ImageMagick REQUIRED )
-+Find_Package ( ImageMagick COMPONENTS Magick++ MagickWand MagickCore REQUIRED
)
Find_Package ( OpenGL REQUIRED )
- FIND_PACKAGE(ImageMagickLib)
+-FIND_PACKAGE(ImageMagickLib)
++FIND_PACKAGE(PkgConfig REQUIRED)
++PKG_CHECK_MODULES(IMAGEMAGICK REQUIRED Magick++ MagickWand MagickCore)
+
+ FIND_PACKAGE(AudiereLib)
+ IF(AUDIERELIB_FOUND)
+@@ -31,8 +31,7 @@
+${SDL_LIBRARY}
+${SDLMIXER_LIBRARY}
+${OPENGL_LIBRARIES}
+- ${IMAGEMAGICKLIB_LIBRARIES}
+- ${IMAGEMAGICKLIB_CXX_LIBRARIES}
++ ${IMAGEMAGICK_LIBRARIES}
+ )
+
+ IF (PYTHON_LIBRARIES)
+@@ -76,11 +75,7 @@
+ MESSAGE(FATAL_ERROR libSDL requested but not found.)
+ ENDIF(SDL_FOUND)
+
+-IF(IMAGEMAGICKLIB_FOUND)
+-MESSAGE(lib ImageMagick found. ${IMAGEMAGICKLIB_INCLUDE_DIR}
${IMAGEMAGICKLIB_LIBRARIES} ${IMAGEMAGICKLIB_CXX_LIBRARIES})
+-ELSE(IMAGEMAGICKLIB_FOUND)
+-MESSAGE(FATAL_ERROR lib ImageMagick requested but not found.)
+-ENDIF(IMAGEMAGICKLIB_FOUND)
++MESSAGE(lib ImageMagick found. ${IMAGEMAGICK_INCLUDE_DIRS}
${IMAGEMAGICK_LIBRARIES})
+
+ IF(SDLMIXER_FOUND)
+ MESSAGE(libSDL_mixer found. ${SDLMIXER_INCLUDE_DIR} ${SDLMIXER_LIBRARY})
+@@ -96,7 +91,7 @@
+
+ SET ( MY_INCLUDE_DIRS
+ #/usr/include/swfdec-0.5 /usr/include/glib-2.0 /usr/lib/glib-2.0/include
+-{SDL_INCLUDE_DIR} ${IMAGEMAGICKLIB_INCLUDE_DIR} ${SDLMIXER_INCLUDE_DIR}
${OPENGL_INCLUDE_DIR} ${PYTHON_INCLUDE_PATH} )
++{SDL_INCLUDE_DIR} ${IMAGEMAGICK_INCLUDE_DIRS} ${SDLMIXER_INCLUDE_DIR}
${OPENGL_INCLUDE_DIR} ${PYTHON_INCLUDE_PATH} )
+ IF(AUDIERELIB_FOUND)
+ SET ( MY_INCLUDE_DIRS ${MY_INCLUDE_DIRS} ${AUDIERELIB_INCLUDE_DIR} )
+ ENDIF(AUDIERELIB_FOUND)
Thanks,
--
Colin Watson [cjwat...@ubuntu.com]
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 2 errors): Re: Bug#747908: [libtuxcap] [transition blocker] Please allow to compile with imagemagick/experimental
Processing control commands: tag -1 patch Bug #747908 [libtuxcap] [libtuxcap] [transition blocker] Please allow to compile with imagemagick/experimental Added tag(s) patch. user ubuntu-de...@lists.ubuntu.com Unknown command or malformed arguments to command. usertag -1 ubuntu-patch vivid Unknown command or malformed arguments to command. -- 747908: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747908 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#767477: safe-rm: fails to install
Package: safe-rm Version: 0.11-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package safe-rm. (Reading database ... 7386 files and directories currently installed.) Preparing to unpack .../safe-rm_0.11-1_all.deb ... Unpacking safe-rm (0.11-1) ... Can't locate Env.pm in @INC (you may need to install the Env module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.1 /usr/local/share/perl/5.20.1 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl) at /usr/bin/rm line 6. BEGIN failed--compilation aborted at /usr/bin/rm line 6. dpkg: error while cleaning up: subprocess rm cleanup returned error exit status 2 Setting up safe-rm (0.11-1) ... cheers, Holger Start: 2014-10-28 12:52:45 UTC Package: safe-rm Version: 0.11-1 Installed-Size: 83 Maintainer: Francois Marier franc...@debian.org Architecture: all Depends: debconf (= 0.5) | debconf-2.0 Pre-Depends: debconf Description: wrapper around the rm command to prevent accidental deletions Homepage: https://launchpad.net/safe-rm Description-md5: b63e9c6ece66f1ccdb308c0826be4649 Tag: implemented-in::perl, interface::commandline, role::program, scope::utility, use::checking Section: utils Priority: optional Filename: pool/main/s/safe-rm/safe-rm_0.11-1_all.deb Size: 19056 MD5sum: d0242802682791cae606bc7974d0fdd8 SHA1: 9737ba1e21388c8818612d8cc313ce475f113298 SHA256: 24668b8c5284ad471d2a877d6148ddf687ad0fc96f1fecb1ae30f4cb29263ae6 Executing: sudo env PYTHONPATH=/srv/piuparts.debian.org/lib/python2.7/dist-packages timeout -s INT -k 5m 35m /srv/piuparts.debian.org/sbin/piuparts --skip-logrotatefiles-test --warn-on-others --scriptsdir /etc/piuparts/scripts --no-eatmydata --allow-database --warn-on-leftovers-after-purge --mirror 'http://mirror.bm.debian.org/debian/ main' --tmpdir /srv/piuparts.debian.org/tmp --arch amd64 -b /srv/piuparts.debian.org/slave/basetgz/jessie_amd64.tar.gz -d jessie --no-upgrade-test --apt safe-rm=0.11-1 0m0.0s INFO: -- 0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of this logfile. 0m0.0s INFO: FAQ available at https://wiki.debian.org/piuparts/FAQ 0m0.0s INFO: The FAQ also explains how to contact us in case you think piuparts is wrong. 0m0.0s INFO: -- 0m0.0s INFO: piuparts version 0.61~201410261922~0.59-22-g69325c0 starting up. 0m0.0s INFO: Command line arguments: /srv/piuparts.debian.org/sbin/piuparts --skip-logrotatefiles-test --warn-on-others --scriptsdir /etc/piuparts/scripts --no-eatmydata --allow-database --warn-on-leftovers-after-purge --mirror 'http://mirror.bm.debian.org/debian/ main' --tmpdir /srv/piuparts.debian.org/tmp --arch amd64 -b /srv/piuparts.debian.org/slave/basetgz/jessie_amd64.tar.gz -d jessie --no-upgrade-test --apt safe-rm=0.11-1 0m0.0s INFO: Running on: Linux piu-slave-bm-a 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2 x86_64 0m0.0s DEBUG: Created temporary directory /srv/piuparts.debian.org/tmp/tmpHnPk53 0m0.0s DEBUG: Unpacking /srv/piuparts.debian.org/slave/basetgz/jessie_amd64.tar.gz into /srv/piuparts.debian.org/tmp/tmpHnPk53 0m0.0s DEBUG: Starting command: ['tar', '-C', '/srv/piuparts.debian.org/tmp/tmpHnPk53', '-zxf', '/srv/piuparts.debian.org/slave/basetgz/jessie_amd64.tar.gz'] 0m2.1s DEBUG: Command ok: ['tar', '-C', '/srv/piuparts.debian.org/tmp/tmpHnPk53', '-zxf', '/srv/piuparts.debian.org/slave/basetgz/jessie_amd64.tar.gz'] 0m2.1s DEBUG: Starting command: ['chroot', '/srv/piuparts.debian.org/tmp/tmpHnPk53', 'mount', '-t', 'proc', 'proc', '/proc'] 0m2.1s DEBUG: Command ok: ['chroot', '/srv/piuparts.debian.org/tmp/tmpHnPk53', 'mount', '-t', 'proc', 'proc', '/proc'] 0m2.1s DEBUG: sources.list: deb http://mirror.bm.debian.org/debian/ jessie main 0m2.1s DEBUG: Created policy-rc.d and chmodded it. 0m2.1s DEBUG: Starting command: ['chroot', '/srv/piuparts.debian.org/tmp/tmpHnPk53', 'apt-get', 'update'] 0m6.5s DUMP: Get:1 http://mirror.bm.debian.org jessie InRelease [191 kB] Get:2 http://mirror.bm.debian.org jessie/main amd64 Packages [6781 kB] Get:3 http://mirror.bm.debian.org jessie/main Translation-en [4600 kB] Fetched 11.6 MB in 2s (4525 kB/s) Reading package lists... 0m6.5s DEBUG: Command ok: ['chroot', '/srv/piuparts.debian.org/tmp/tmpHnPk53', 'apt-get', 'update'] 0m6.5s DEBUG: Starting command: ['chroot', '/srv/piuparts.debian.org/tmp/tmpHnPk53', 'apt-get', '-yf', 'dist-upgrade'] 0m7.1s DUMP: Reading package lists... Building dependency tree... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Bug#763769: marked as done (glabels exists with Abort when creating a new document)
Your message dated Fri, 31 Oct 2014 10:48:54 + with message-id e1xk9lg-0001ml...@franck.debian.org and subject line Bug#763769: fixed in glabels 3.0.1-4.1 has caused the Debian Bug report #763769, regarding glabels exists with Abort when creating a new document 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.) -- 763769: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: glabels Version: 3.0.1-4+b1 Severity: grave Justification: renders package unusable Dear Maintainer, The problem is simple. From the command line I run glabels. The main window appears. I click on the button to create a new document and glabels abort. This is warning displayed on the console. The only think that is unsual about my installation is that I'm using xfce4 with awsome as window manager. I'm happy to provide more details if needed. pietro $glabels-3 (glabels-3:9747): GLib-GObject-WARNING **: The property GtkSettings:gtk-menu-images is deprecated and shouldn't be used anymore. It will be removed in a future version. (glabels-3:9747): GLib-GObject-WARNING **: The property GtkImageMenuItem:always-show-image is deprecated and shouldn't be used anymore. It will be removed in a future version. (glabels-3:9747): GLib-GObject-WARNING **: The property GtkImage:stock is deprecated and shouldn't be used anymore. It will be removed in a future version. (glabels-3:9747): GLib-GObject-WARNING **: The property GtkButton:xalign is deprecated and shouldn't be used anymore. It will be removed in a future version. (glabels-3:9747): GLib-GObject-WARNING **: The property GtkAlignment:left-padding is deprecated and shouldn't be used anymore. It will be removed in a future version. (glabels-3:9747): GLib-GObject-WARNING **: The property GtkToolButton:stock-id is deprecated and shouldn't be used anymore. It will be removed in a future version. (glabels-3:9747): GLib-GObject-WARNING **: The property GtkContainer:resize-mode is deprecated and shouldn't be used anymore. It will be removed in a future version. (process:9747): GLib-GObject-WARNING (recursed) **: The property GtkButton:use-stock is deprecated and shouldn't be used anymore. It will be removed in a future version.Aborted -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages glabels depends on: ii dpkg 1.17.13 ii glabels-data 3.0.1-4 ii libc62.19-11 ii libcairo21.12.16-5 ii libebook-1.2-14 3.12.6-1 ii libebook-contacts-1.2-0 3.12.6-1 ii libedataserver-1.2-183.12.6-1 ii libgdk-pixbuf2.0-0 2.30.8-1+b1 ii libglib2.0-0 2.42.0-1 ii libgtk-3-0 3.14.1-1 ii libiec16022-00.2.4-1.1 ii libpango-1.0-0 1.36.7-1 ii libpangocairo-1.0-0 1.36.7-1 ii libqrencode3 3.4.3-1 ii librsvg2-2 2.40.4-1 ii libxml2 2.9.1+dfsg1-4 Versions of packages glabels recommends: ii evince 3.14.0-2 Versions of packages glabels suggests: pn evolution-data-server none -- no debconf information ---End Message--- ---BeginMessage--- Source: glabels Source-Version: 3.0.1-4.1 We believe that the bug you reported is fixed in the latest version of glabels, 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 763...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen ben...@debian.org (supplier of updated glabels 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, 31 Oct 2014 10:00:59 +0100 Source: glabels Binary: glabels glabels-data glabels-dev Architecture: source all amd64 Version: 3.0.1-4.1 Distribution: unstable Urgency: medium Maintainer: Hilko Bengen ben...@debian.org Changed-By: Hilko Bengen ben...@debian.org
Bug#767248: dbconfig-common: removes any permissions from generated include files on upgrade
I think this patch doesn't work when installing a new package (it does work on upgrades). So I think the two added lines need to be within an 'if [ -e $outputfile ] ; then' statement. I figured that and re-created the patch - apparently, I uploaded the old one :(. Turns out it is not enough either. Attached is (the only) working patch, which leaves anything but the contents of any existing file intact. DO NOT UPLOAD the previous patch, as it indeed breaks another code flow. -nik -- Dominik George (Vorstandsvorsitzender, Pädagogischer Leiter) Teckids e.V. - Erkunden, Entdecken, Erfinden. https://www.teckids.org diff -Nru dbconfig-common-1.8.47+nmu2/dbconfig-generate-include dbconfig-common-1.8.47+nmu3/dbconfig-generate-include --- dbconfig-common-1.8.47+nmu2/dbconfig-generate-include 2014-10-13 21:05:57.0 +0200 +++ dbconfig-common-1.8.47+nmu3/dbconfig-generate-include 2014-10-31 12:32:40.0 +0100 @@ -408,7 +408,7 @@ ucf --debconf-ok $tmpout $outputfile 2 rm -f $tmpout else - mv $tmpout $outputfile + cat $tmpout $outputfile fi check_permissions [ $owner ] chown $owner $outputfile diff -Nru dbconfig-common-1.8.47+nmu2/debian/changelog dbconfig-common-1.8.47+nmu3/debian/changelog --- dbconfig-common-1.8.47+nmu2/debian/changelog2014-10-13 21:31:13.0 +0200 +++ dbconfig-common-1.8.47+nmu3/debian/changelog2014-10-29 16:43:27.0 +0100 @@ -1,3 +1,11 @@ +dbconfig-common (1.8.47+nmu3) unstable; urgency=medium + + * Non-maintainer upload. + * Do not remove permissions from include files on upgrade, +thanks to Simon Bruder. (Closes: #767248) + + -- Dominik George n...@naturalnet.de Wed, 29 Oct 2014 16:38:19 +0100 + dbconfig-common (1.8.47+nmu2) unstable; urgency=low * Non-maintainer upload. signature.asc Description: OpenPGP digital signature
Bug#767240: Three security bug in imagemagick
Hi Bastien, On Wed, Oct 29, 2014 at 03:22:24PM +0100, Bastien ROUCARIES wrote: package: imagemagick version: 8:6.6.0.4-3 severity: serious control: tag -1 + security This is a bug for tracking : TEMP-000-77B6EF buffer overflow in PCX and DCM coder TEMP-000-3CE5AC Off-by-one count when parsing an 8BIM profile TEMP-000-1800A5 Don't clone a 0x0 image breaking some assumption As we both agreed: These issues look like low-impact and thus no-dsa (no DSA planned for them), but woul be great to have them fixed trough a stable-proposed-update for Wheezy. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767248: dbconfig-common: removes any permissions from generated include files on upgrade
On 31-10-14 12:35, Dominik George wrote: I think this patch doesn't work when installing a new package (it does work on upgrades). So I think the two added lines need to be within an 'if [ -e $outputfile ] ; then' statement. I figured that and re-created the patch - apparently, I uploaded the old one :(. Turns out it is not enough either. Attached is (the only) working patch, which leaves anything but the contents of any existing file intact. DO NOT UPLOAD the previous patch, as it indeed breaks another code flow. Very interesting, as this is exactly something that I came up with as an alternative, indeed to prevent issues were e.g. the maintainer had made the configuration file a symlink. I was wondering though, if that would not leave a very short time where the file may have too little permission restrictions. mktemp is supposed to be secure, catting into a yet non-existing file may not. Paul signature.asc Description: OpenPGP digital signature
Bug#759934: Doxygen-Starvation FTBFS
Downstream packages (like ivtools, ahem) don't care about the documentation, just the ACE libraries proper. So could I suggest disabling doxygen-generated documentation and uploading a version that doesn't use doxygen at all in the build process? Just as an interim measure until the doxygen issue is solved, of course. Once this is done, the present bug could be marked wishlist and ACE could migrate to testing, followed by its downstream packages like ducklings in a row. Yours Truly, --Barak. (ivtools maintainer) -- Barak A. Pearlmutter Hamilton Institute Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland http://www.bcl.hamilton.ie/~barak/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767248: dbconfig-common: removes any permissions from generated include files on upgrade
mktemp is supposed to be secure, catting into a yet non-existing file may not. Paul mktemp is safe in that it uses unique file names. Apart from that it adheres to the effective user and effective umask, making it no more and no less safe than any other operation creating files. -nik -- Dominik George (Vorstandsvorsitzender, Pädagogischer Leiter) Teckids e.V. - Erkunden, Entdecken, Erfinden. https://www.teckids.org signature.asc Description: OpenPGP digital signature
Bug#767248: dbconfig-common: removes any permissions from generated include files on upgrade
The issue with the --reference solution is that it will still remove Posix ACLs, xattrs, etc. and we cannot replicate everything. Not touching file metadata (except for mtime) resolves that and thus is the only universal solution. -nik -- Dominik George (Vorstandsvorsitzender, Pädagogischer Leiter) Teckids e.V. - Erkunden, Entdecken, Erfinden. https://www.teckids.org signature.asc Description: OpenPGP digital signature
Bug#767248: Bug#767390: Bug#767248: dbconfig-common: removes any permissions from generated include files on upgrade
On Fri, Oct 31, 2014 at 12:59:06 +0100, Dominik George wrote: mktemp is supposed to be secure, catting into a yet non-existing file may not. Paul mktemp is safe in that it uses unique file names. Apart from that it adheres to the effective user and effective umask, making it no more and no less safe than any other operation creating files. That's not true. It creates files 0600 (minus umask). Pretty much any other operation creating files uses 0666 (minus umask). Cheers, Julien signature.asc Description: Digital signature
Bug#766832: marked as done (metview: FTBFS on mipsel: libMagWrapper.a: error adding symbols: Bad value (recompile with -fPIC))
Your message dated Fri, 31 Oct 2014 12:19:14 + with message-id e1xkbag-0006sb...@franck.debian.org and subject line Bug#766832: fixed in magics++ 2.22.7.dfsg.1-4 has caused the Debian Bug report #766832, regarding metview: FTBFS on mipsel: libMagWrapper.a: error adding symbols: Bad value (recompile with -fPIC) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 766832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: metview Version: 4.4.8+dfsg.1-7 Severity: serious Hi, Your package FTBFS on mipsel with the following error: libtool: link: g++ -O2 -fPIC -Dlinux -DUSE_NEW_IO -fno-gnu-keywords -Wno-deprecated [...] /usr/bin/ld: /usr/lib/mipsel-linux-gnu/libMagWrapper.a(MagPlus.cc.o): relocation R_MIPS_HI16 against `__gnu_local_gp' can not be used when making a shared object; recompile with -fPIC /usr/lib/mipsel-linux-gnu/libMagWrapper.a: error adding symbols: Bad value collect2: error: ld returned 1 exit status make[6]: *** [bin/uPlotBatch] Error 1 Makefile:1215: recipe for target 'bin/uPlotBatch' failed make[6]: Leaving directory '/«BUILDDIR»/metview-4.4.8+dfsg.1/src/uPlot' Since it built in mipsel in the past, this is considered a serious regression and will prevent migration to testing. ~Niels ---End Message--- ---BeginMessage--- Source: magics++ Source-Version: 2.22.7.dfsg.1-4 We believe that the bug you reported is fixed in the latest version of magics++, 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 766...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry mckins...@debian.org (supplier of updated magics++ 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, 30 Oct 2014 19:17:49 + Source: magics++ Binary: libmagplus3 libmagics++-dev magics++ python-magics++ libmagics++-data libmagics++-metview-dev Architecture: source amd64 all Version: 2.22.7.dfsg.1-4 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry mckins...@debian.org Changed-By: Alastair McKinstry mckins...@debian.org Description: libmagics++-data - Data files needed for magics++ library libmagics++-dev - Development files for ECMWF plotting software MAGICS++ libmagics++-metview-dev - Libraries needed for building MetView libmagplus3 - ECMWF meteorological plotting software library magics++ - Executables for the magics++ library python-magics++ - python support for Magics++ Closes: 766832 Changes: magics++ (2.22.7.dfsg.1-4) unstable; urgency=medium . * Build -fPIC for mipsel. Closes: #766832 Checksums-Sha1: 061bad5f34a2e07a623a2cfcad345095118276e0 2500 magics++_2.22.7.dfsg.1-4.dsc c219f4a04fe97907bd60750585e7a2ce28cba28e 98652 magics++_2.22.7.dfsg.1-4.debian.tar.xz e80036dad0c086d946dbaba46ac6c83ebbbc9fef 2843648 libmagplus3_2.22.7.dfsg.1-4_amd64.deb 091b7368e9dff402b1c9c55985e20c8f24fbf846 4737030 libmagics++-dev_2.22.7.dfsg.1-4_amd64.deb 2f7e0af56af4dc6605738b81bff1c19ef66e36ad 40004 magics++_2.22.7.dfsg.1-4_amd64.deb 8b43c7b1a30521e45c31cfb2b0e32e614f4533e2 55846 python-magics++_2.22.7.dfsg.1-4_amd64.deb 5880ea1ee3ea47d5583ec087b531bd9a74ddf055 27578834 libmagics++-data_2.22.7.dfsg.1-4_all.deb 8bf964cfde6206d55a21fd7c4548d25aa673b984 705894 libmagics++-metview-dev_2.22.7.dfsg.1-4_amd64.deb Checksums-Sha256: c21800f4cc7cbc895e822f48f09cf983cb5f42a0a6c20bd094056e0c5f45f99e 2500 magics++_2.22.7.dfsg.1-4.dsc 36d361bd5528e99edbae9edec15e6573dcb72ccc65c5c8a9b2f75fb36bf32d48 98652 magics++_2.22.7.dfsg.1-4.debian.tar.xz 601c20d055efa89de856fcde440e3e6ab08a9774978dbd70e818d6c8fe6d3f74 2843648 libmagplus3_2.22.7.dfsg.1-4_amd64.deb 271cc48549ede95dff5cb3638a20d860a68d881fab6d15907bf3577f0dfb16a6 4737030 libmagics++-dev_2.22.7.dfsg.1-4_amd64.deb ea1a6a6632759159c8b1cb94ea8216a1321e98f9dd5a7fd6f311056b90f012cf 40004 magics++_2.22.7.dfsg.1-4_amd64.deb 4ef6a73dce52f51f29364959b7df9f707c882db3999b14ad75b03c91e72db5fa 55846 python-magics++_2.22.7.dfsg.1-4_amd64.deb bb69c80b871a5b6a767062067aad5b40d316fe5dcc5fad2bddaeccd5e50128aa 27578834 libmagics++-data_2.22.7.dfsg.1-4_all.deb
Bug#767411: Aw: Bug#767411: torque: should not be released with jessie
Hello, Von: Dominique Belhachemi domi...@debian.org I agree that the 2.4 branch is completely outdated. We should switch to a newer branch. The 2.5 and 4.1 branches are not suitable for Debian due to licensing issues. But the 4.2 branch is licensed under the same license as the 2.4 branch, so I suggest we upload the 4.2.9 release to unstable. I agree. You? Me? I am too busy for the upcoming weeks, sadly. Best, Steffen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767411: torque: should not be released with jessie
On Thu, Oct 30, 2014 at 22:27:53 +0100, Salvatore Bonaccorso wrote: pbs-drmaa as reverse dependency of torque is easy as it is a leaf package. The more complicated one would be openmpi which would need to drop the build dependency on libtorque2-dev. The reason for this dependency was in https://bugs.debian.org/592887 , which needs to be dropped again. There's two solutions here. One is to drop torque support from openmpi; the other is to keep the torque source package but only build the libtorque library, as I'm assuming the security issues are on the torque server side. Though that's only useful is that library can still talk to newer torque version. Cheers, Julien signature.asc Description: Digital signature
Bug#764162: linux-image-3.16-2-kirkwood: [regression 3.14-3.16] file data corruption, via network
Le vendredi 31 octobre 2014 à 09:50 +, Ian Campbell a écrit : On Sun, 2014-10-19 at 14:27 +0100, Ian Campbell wrote: You could inactivate this feature manually with: ethtool -K eth0 tso off I'm in contact with the developer of this feature. Tell me if this command resolve your problem Excellent, please let us know how you get on (feel free to CC the bug too if you want). Did you make any progress with the developer? In the changes to this driver since v3.16 I see commit 817dbfa5d1bc276a72c1a577310382008e8aca0a Author: Vlad Yasevich vyasev...@gmail.com Date: Mon Aug 25 10:34:54 2014 -0400 mvneta: Fix TSO and checksum for non-acceleration vlan traffic which might be potentially interesting, except no one on this bug has mentioned VLANs at any point. I don't see anything else of interest. Ian. I don't have more information. They seems not to understand why there are data corrupt with this soc. The only solution at this time is to inactivate tso or apply this patch, which makes TSO disabled by default: diff --git a/drivers/net/ethernet/marvell/mv643xx_eth.c b/drivers/net/ethernet/marvell/mv643xx_eth.c index 693b5b5..8e6df75 100644 --- a/drivers/net/ethernet/marvell/mv643xx_eth.c +++ b/drivers/net/ethernet/marvell/mv643xx_eth.c @@ -3113,11 +3113,11 @@ static int mv643xx_eth_probe(struct platform_device *pdev) dev-watchdog_timeo = 2 * HZ; dev-base_addr = 0; - dev-features = NETIF_F_SG | NETIF_F_IP_CSUM | NETIF_F_TSO; + dev-features = NETIF_F_SG | NETIF_F_IP_CSUM; dev-vlan_features = dev-features; dev-features |= NETIF_F_RXCSUM; - dev-hw_features = dev-features; + dev-hw_features = dev-features | NETIF_F_TSO; dev-priv_flags |= IFF_UNICAST_FLT; dev-gso_max_segs = MV643XX_MAX_TSO_SEGS; I CC my contact Julien D'Ascenzio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764162: linux-image-3.16-2-kirkwood: [regression 3.14-3.16] file data corruption, via network
Le vendredi 31 octobre 2014 à 09:50 +, Ian Campbell a écrit : On Sun, 2014-10-19 at 14:27 +0100, Ian Campbell wrote: You could inactivate this feature manually with: ethtool -K eth0 tso off I'm in contact with the developer of this feature. Tell me if this command resolve your problem Excellent, please let us know how you get on (feel free to CC the bug too if you want). Did you make any progress with the developer? In the changes to this driver since v3.16 I see commit 817dbfa5d1bc276a72c1a577310382008e8aca0a Author: Vlad Yasevich vyasev...@gmail.com Date: Mon Aug 25 10:34:54 2014 -0400 mvneta: Fix TSO and checksum for non-acceleration vlan traffic which might be potentially interesting, except no one on this bug has mentioned VLANs at any point. I don't see anything else of interest. Ian. An other thread about this bug: http://archlinuxarm.org/forum/viewtopic.php?f=9t=7692 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767498: aces3: FTBFS on several architectures
package: aces3 version: 3.0.8-1 severity: serious Hi, The latest upload of aces3 fails on a number of architectures, but it built fine before. This prevents migration to testing. https://buildd.debian.org/status/package.php?p=aces3 Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 766195, retitle 766195 to linux: Network-related panic in Linux 3.2.63 (CVE-2014-7207)
Processing commands for cont...@bugs.debian.org: tags 766195 + security Bug #766195 [src:linux] linux: Network-related panic in Linux 3.2.63 Added tag(s) security. retitle 766195 linux: Network-related panic in Linux 3.2.63 (CVE-2014-7207) Bug #766195 [src:linux] linux: Network-related panic in Linux 3.2.63 Changed Bug title to 'linux: Network-related panic in Linux 3.2.63 (CVE-2014-7207)' from 'linux: Network-related panic in Linux 3.2.63' thanks Stopping processing here. Please contact me if you need assistance. -- 766195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766195 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#767498: [Debichem-devel] Bug#767498: aces3: FTBFS on several architectures
Hi, On Fri, Oct 31, 2014 at 02:36:35PM +0100, Ivo De Decker wrote: package: aces3 version: 3.0.8-1 severity: serious Hi, The latest upload of aces3 fails on a number of architectures, but it built fine before. This prevents migration to testing. Yeah, I noticed. The problem is that 3.0.8 has introduced some rather large auto-generated source files for additional features, which our slower and/or more obscure architecture seem not to be able to handle, all failures are in those (root*.F) files. On arm64/armhf one solution could be to drop back to -O1/-O0, I will try that on a porterbox once I find the time. The mipsel failure looks like the box is just not able to compile that huge file in time, maybe a different box would cope and/or -O1/-O0 will make it easier. The s390x is in the same ballpark, but IME s390x is fast enough that this might be a genuine compiler hang or so. Will try to reproduce on a porterbox as well. Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: NVIDIA non-free driver may break gdm3
Processing control commands: tags 761001 moreinfo Bug #761001 [gdm3] gdm3: No way to log in Added tag(s) moreinfo. severity 761001 important Bug #761001 [gdm3] gdm3: No way to log in Severity set to 'important' from 'serious' -- 761001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761001 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#767504: mpd: licence clash with libmp4v2 (MPL) and mpd GPL-+2
Package: mpd Version: 0.19.1-1 Severity: serious Dear Maintainer, You can't link GPL packages against MPL packages. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.16-3-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mpd depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.21 ii libadplug-2.2.1-0 2.2.1+dfsg3-0.1 ii libao41.1.0-3 ii libasound21.0.28-1 ii libaudiofile1 0.3.6-2 ii libavahi-client3 0.6.31-4 ii libavahi-common3 0.6.31-4 ii libavcodec56 6:11-2 ii libavformat56 6:11-2 ii libavutil54 6:11-2 ii libbz2-1.01.0.6-7 ii libc6 2.19-12 ii libcdio-cdda1 0.83-4.2 ii libcdio-paranoia1 0.83-4.2 ii libcdio13 0.83-4.2 ii libcurl3-gnutls 7.38.0-2 ii libdbus-1-3 1.8.8-2 ii libexpat1 2.1.0-6 ii libfaad2 2.7-8 ii libflac8 1.3.0-2 ii libfluidsynth11.1.6-2 ii libgcc1 1:4.9.1-16 ii libglib2.0-0 2.42.0-2 ii libgme0 0.5.5-2 ii libicu52 52.1-6 ii libid3tag00.15.1b-11 ii libiso9660-8 0.83-4.2 ii libjack-jackd2-0 [libjack-0.116] 1.9.10+20140719git3eb0ae6a~dfsg-2 ii libmad0 0.15.1b-8 ii libmikmod33.3.7-1 ii libmms0 0.6.2-4 ii libmodplug1 1:0.8.8.4-4.1 ii libmp3lame0 3.99.5+repack1-5 ii libmp4v2-22.0.0~dfsg0-3 ii libmpcdec62:0.1~r459-4.1 ii libmpdclient2 2.9-1 ii libmpg123-0 1.20.1-2 ii libnfs4 1.9.5-2 ii libogg0 1.3.2-1 ii libopenal11:1.15.1-5 ii libopus0 1.1-2 ii libpulse0 5.0-13 ii libresid-builder0c2a 2.1.1-14 ii libroar2 1.0~beta11-1 ii libsamplerate00.1.8-8 ii libshout3 2.3.1-3 ii libsidplay2 2.1.1-14 ii libsidutils0 2.1.1-14 ii libsmbclient 2:4.1.13+dfsg-2 ii libsndfile1 1.0.25-9 ii libsoxr0 0.1.1-1 ii libsqlite3-0 3.8.7-1 ii libstdc++64.9.1-16 ii libsystemd0 215-5+b1 ii libupnp6 1:1.6.17-1.2 ii libvorbis0a 1.3.2-1.5 ii libvorbisenc2 1.3.2-1.5 ii libvorbisfile31.3.2-1.5 ii libwavpack1 4.70.0-1 ii libwildmidi1 0.3.7-1 ii libwrap0 7.6.q-25 ii libyajl2 2.1.0-2 ii libzzip-0-13 0.13.62-3 ii lsb-base 4.1+Debian13+nmu1 ii zlib1g1:1.2.8.dfsg-2 mpd recommends no packages. Versions of packages mpd suggests: pn avahi-daemon none pn icecast2 none pn mpd-clientnone pn pulseaudionone -- 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#761001: NVIDIA non-free driver may break gdm3
control: tags 761001 moreinfo control: severity 761001 important Hi, Since I do not have NVIDIA GPU on my system, I removed all its non-free drivers from my system. Then my problem is gone. For my case, non-free NVIDIA software seems to be interfering with the GPU detection for GLX on Intel integrated GPU which then caused gdm3 and GNOME desktop to crash. I doubt this is a bug for gdm3. Instead, this should be bug on NVIDIA code breaking GLX. The breakage of gdm3 and GNOME can happen due to these reasons. Unless Kurt can provide sufficient evidence that his breakage report is caused by the bug in gdm3, having RC bug report here serves no use. Kurt, can you provide log file for failed gdm3? Kurt, can you check your GPU drivers? Regards, Osamu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767248: dbconfig-common: removes any permissions from generated include files on upgrade
Hi Dominik, I have some time (while baby-sitting) to look into the code of dbconfig-common and I don't understand why the code we are discussing here is relevant at all. dbconfig-generate-include should be called by dpkg/common on line 547 with the -U option, so the path should be the ucf path. While I was thinking about it I believe that indeed all the configuration files which are not conffiles should be handled by ucf, because that is supposed to do-the-right-thing. Do you know if roundcube-core is calling dbconfig-generate-include directly? Paul signature.asc Description: OpenPGP digital signature
Bug#767248: dbconfig-common: removes any permissions from generated include files on upgrade
Hi, Do you know if roundcube-core is calling dbconfig-generate-include directly? Not as far as I can see ... -nik -- Dominik George (Vorstandsvorsitzender, Pädagogischer Leiter) Teckids e.V. - Erkunden, Entdecken, Erfinden. https://www.teckids.org signature.asc Description: OpenPGP digital signature
Processed: severity of 767331 is grave, found 767331 in 2.82-2 ...
Processing commands for cont...@bugs.debian.org: severity 767331 grave Bug #767331 [get-iplayer] get-iplayer: shows pseudo-programme “BBC iPlayer Feeds” at index 1 because of wrong usage of BBC API Severity set to 'grave' from 'normal' found 767331 2.82-2 Bug #767331 [get-iplayer] get-iplayer: shows pseudo-programme “BBC iPlayer Feeds” at index 1 because of wrong usage of BBC API Marked as found in versions get-iplayer/2.82-2. forwarded 767331 http://lists.infradead.org/pipermail/get_iplayer/2014-October/006240.html Bug #767331 [get-iplayer] get-iplayer: shows pseudo-programme “BBC iPlayer Feeds” at index 1 because of wrong usage of BBC API Set Bug forwarded-to-address to 'http://lists.infradead.org/pipermail/get_iplayer/2014-October/006240.html'. retitle 767331 get-iplayer: useless after BBC API changes Bug #767331 [get-iplayer] get-iplayer: shows pseudo-programme “BBC iPlayer Feeds” at index 1 because of wrong usage of BBC API Changed Bug title to 'get-iplayer: useless after BBC API changes' from 'get-iplayer: shows pseudo-programme “BBC iPlayer Feeds” at index 1 because of wrong usage of BBC API' thanks Stopping processing here. Please contact me if you need assistance. -- 767331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767331 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#767505: zotero-standalone: Broken with Iceweasel 33
Package: zotero-standalone Version: 4.0.22-1~bpo70+1 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, latest version of Zotero (4.0.22-1) doesn't work with Iceweasel 33. I tested the version in backports, but I assume the same thing happens in Jessie. The simplest solution would be to modify accordingly application.ini in MaxVersion string: I have already verified that so it works. Best whishes, Domenico Cufalo -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages zotero-standalone depends on: ii iceweasel 33.0-2~bpo70+1 zotero-standalone recommends no packages. zotero-standalone 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#767387: beignet: Non-free files in test suite
On 2014-10-31 10:23, Rebecca N. Palmer wrote: I have reported this upstream; they have agreed it's a problem and are in the process of removing the first group and investigating the second. Good news! To deal with this problem in the meantime, we will need to repack the orig tarball (which the version just added to Alioth does _not_ do); the new version would then conventionally be called 0.8+dfsg1-0.1 or 0.9.3+dfsg1-0.1. Repacked in git, deleting all files you mentioned in this bug report. Now it FTBFS (it was working before the dfsg changes), tail of buildlog: [ 9%] Built target gbeinterp make -f src/CMakeFiles/cl.dir/build.make src/CMakeFiles/cl.dir/depend make[3]: Entering directory '/tmp/buildd/beignet-0.9.3~dfsg/obj-x86_64-linux-gnu' /usr/bin/cmake -E cmake_progress_report /tmp/buildd/beignet-0.9.3~dfsg/obj-x86_64-linux-gnu/CMakeFiles [ 9%] Generating ../../src/kernels/cl_internal_built_in_kernel_str.c cd /tmp/buildd/beignet-0.9.3~dfsg/obj-x86_64-linux-gnu/src rm -rf /tmp/buildd/beignet-0.9.3~dfsg/src/kernels//cl_internal_built_in_kernel_str.c cd /tmp/buildd/beignet-0.9.3~dfsg/obj-x86_64-linux-gnu/src OCL_PCM_PATH=/tmp/buildd/beignet-0.9.3~dfsg/obj-x86_64-linux-gnu/backend/src/beignet.bc:/usr/lib/beignet//beignet.bc OCL_PCH_PATH=/tmp/buildd/beignet-0.9.3~dfsg/obj-x86_64-linux-gnu/backend/src/usr/lib/beignet/ocl_stdlib.h.local.pch:/usr/lib/beignet//ocl_stdlib.h.pch LD_LIBRARY_PATH=/tmp/buildd/beignet-0.9.3~dfsg/obj-x86_64-linux-gnu/backend/src /tmp/buildd/beignet-0.9.3~dfsg/obj-x86_64-linux-gnu/backend/src/gbe_bin_generater -s /tmp/buildd/beignet-0.9.3~dfsg/src/kernels//cl_internal_built_in_kernel.cl -o/tmp/buildd/beignet-0.9.3~dfsg/src/kernels//cl_internal_built_in_kernel_str.c /bin/sh: 1: OCL_PCM_PATH=/tmp/buildd/beignet-0.9.3~dfsg/obj-x86_64-linux-gnu/backend/src/beignet.bc:/usr/lib/beignet//beignet.bc: not found src/CMakeFiles/cl.dir/build.make:232: recipe for target '../src/kernels/cl_internal_built_in_kernel_str.c' failed make[3]: *** [../src/kernels/cl_internal_built_in_kernel_str.c] Error 127 make[3]: Leaving directory '/tmp/buildd/beignet-0.9.3~dfsg/obj-x86_64-linux-gnu' CMakeFiles/Makefile2:297: recipe for target 'src/CMakeFiles/cl.dir/all' failed make[2]: *** [src/CMakeFiles/cl.dir/all] Error 2 make[2]: Leaving directory '/tmp/buildd/beignet-0.9.3~dfsg/obj-x86_64-linux-gnu' Makefile:140: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/tmp/buildd/beignet-0.9.3~dfsg/obj-x86_64-linux-gnu' dh_auto_build: make -j1 returned exit code 2 debian/rules:8: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 (git-buildpackage --git-no-pristine-tar) Also note that as the first group is undistributable (not just non-DFSG), creating an Alioth repository that includes the previous versions may not be a good idea. Looks I'll have to rewrite/cripple/prune that part of the history ... but first lets use that git repo to get 0.9.3~dfsg working ... Andreas PS: the typo fixing patch is now available in a separate branch for-upstream for submitting/cherry-picking upstream -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767395: marked as done (python-gitlab: dist-packages/tests/__init__.py conflict)
Your message dated Fri, 31 Oct 2014 15:22:01 + with message-id e1xke1z-00085c...@franck.debian.org and subject line Bug#767395: fixed in pyapi-gitlab 6.2.3-2 has caused the Debian Bug report #767395, regarding python-gitlab: dist-packages/tests/__init__.py conflict 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.) -- 767395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767395 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-gitlab Version: 6.2.3-1 Severity: serious Justification: Policy 6.6 (4) python-gitlab and python3-gitlab respectively ship the overly generic paths /usr/lib/python2.7/dist-packages/tests/__init__.py and /usr/lib/python3/dist-packages/tests/__init__.py, leading to de facto conflicts with similarly broken packages. Please either install these tests somewhere less likely to cause trouble or omit them altogether. Thanks! ---End Message--- ---BeginMessage--- Source: pyapi-gitlab Source-Version: 6.2.3-2 We believe that the bug you reported is fixed in the latest version of pyapi-gitlab, 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 767...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Benjamin Drung benjamin.dr...@profitbricks.com (supplier of updated pyapi-gitlab 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, 31 Oct 2014 15:03:35 +0100 Source: pyapi-gitlab Binary: python-gitlab python3-gitlab Architecture: source all Version: 6.2.3-2 Distribution: unstable Urgency: medium Maintainer: Benjamin Drung benjamin.dr...@profitbricks.com Changed-By: Benjamin Drung benjamin.dr...@profitbricks.com Description: python-gitlab - Python wrapper for the GitLab API (Python 2) python3-gitlab - Python wrapper for the GitLab API (Python 3) Closes: 767395 Changes: pyapi-gitlab (6.2.3-2) unstable; urgency=medium . * Remove tests directory. The name is too generic and will clash with other Python modules. (Closes: #767395) Checksums-Sha1: e2ab7e39a927971ab0180fc9ccd791f17e800f22 2045 pyapi-gitlab_6.2.3-2.dsc 1f1f6f75eee56ed4e5d271bf524c8806584744a7 1672 pyapi-gitlab_6.2.3-2.debian.tar.xz e5773ee392403d8ae5d14ca6d99072a465f855fb 9760 python-gitlab_6.2.3-2_all.deb 9a692267fac8684904d303cbdb7d9660492d35eb 9836 python3-gitlab_6.2.3-2_all.deb Checksums-Sha256: 91cd969dd9490ad3b7ef958c1970a85a2a99f7d85eaa798d4145c53f8fe73b2d 2045 pyapi-gitlab_6.2.3-2.dsc 12ae1560933961e57a6ecb73396b6426124437d219b19a52971e1c9e07860a93 1672 pyapi-gitlab_6.2.3-2.debian.tar.xz 5d006fae0ed705784d8de70bbc999e7ffa999de180603294f6ef5ee7d5cd12d0 9760 python-gitlab_6.2.3-2_all.deb 95217efd1735f0a8583ece437fc7011f9d5c1acc4a1a9582c98b2be7b960 9836 python3-gitlab_6.2.3-2_all.deb Files: ec906bc841f6cef776ca6edf64a87533 2045 python optional pyapi-gitlab_6.2.3-2.dsc 3e9f1721fc54a81cb8e8620fb96a8d78 1672 python optional pyapi-gitlab_6.2.3-2.debian.tar.xz dd298a24e04aa548f0c59a547d356445 9760 python optional python-gitlab_6.2.3-2_all.deb 3fcb0258cb6c33e935b69f3b8056beb6 9836 python optional python3-gitlab_6.2.3-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUU5cOAAoJEN2M1aXejH56I+8P/0bgDk2dK7DY5zuAsENeZpXo Qi70eGGf76O6fB7X0IGFglUPfQIy/fnEWiGiXqZWZa5CtUFgxHKX/XJDuTEJkshk PGO3MYPEOOuk8YwLUEYV5Yxo+If8rYibLw27UZLXYVO90mv/xYsnvJTPobn5vu/Z YBf+rIukuErGQrFMm5QjydL/jiUz+lw/cVgH7E2TXm7BClVueE4EgMue9TkSMGVz TEopc4WQLWa9PMW+1LtrF7QnAQ+vQYB5yk+8IiYOwU0w0vn5un9iI829DZkuRBgB COsG9WYmRTzppGkVWn5tgh4oLULDEmVniNTuXW39AEd05uYn26KtrJCxx2hwoApF npc3bzfX3QzhcbBC8lrxIjNaFEgkQkTj4nvHuiHTIM95uRx2/4YytYdIpMw20IrN l/uEpwUqnUGf31WSEOmnCAiCgwMphr6WUaR5eOWl+IPdGJUGCWV/uzkI9ds99DWs CaZC+vxZpNHlS8wnSeq5LxvrGetcpR7ENRlPGQBJyWYuVNzjJS412vnX+BZzaBkw m8gsh1Ow9DVoUsCz5U8Ytb6+AtG15Hiaan14+Y+fu+Fo3dqvnAAx/niusk5pxZd8 kwOw/IGT3V0TQMI8b/iQEXH8YZ8h8cX0ifGrbKwR5fhZgkE+sv9JM7ATj6aqWlBL juQhASetQt4ixNPsKln/ =tWgR -END PGP SIGNATUREEnd Message---
Bug#767504: [Pkg-mpd-maintainers] Bug#767504: mpd: licence clash with libmp4v2 (MPL) and mpd GPL-+2
On Fri, Oct 31, 2014 at 03:27:47PM +0100, grossepoube...@free.fr wrote: You can't link GPL packages against MPL packages. Interesting. Can you explain in a bit more detail? IANAL, but I read in MPL1.1 section 6.2 that I can choose to use the code under a newer version of the license, such as MPL2.0 which is deemed compatible with the GPL by the FSF. This upgrade option is made even more explicit in section 3.1 of the MPL1.1 which says The Source Code version of Covered Code may be distributed only under the terms of this License or a future version of this License [...] Florian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767248: ucf and file permissions/ownership
Hi Manoj, Recently I created an RC bug (the bug, not the report) with an NMU of dbconfig-common. The package dbconfig-common uses ucf to handle updates of the content of configuration files. To prevent the need to implement logic in dbconfig-common to preserve local changes in permissions and ownership I thought I could just let ucf handle the situation, but I am quite surprised to now see the following in the manual: As far as possible, ucf attempts to preserve the ownership and permission of the New file as it is copied to the new location. Can you please explain the logic of why ucf does that instead of maintaining the ownership and permissions of the original file? Because that means that every package that uses ucf has to make sure itself that the ownership and permissions are first copied from the old file to the new file, or else it would be violating Policy 10.7.3, the exact reason why ucf exists. Paul PS: I don't believe the current understanding in bug 767248 is correct, I think it is ucf that is doing the copying of the ownership/permissions, so I think actually the bug should be reassigned to it. signature.asc Description: OpenPGP digital signature
Bug#767504: [Pkg-mpd-maintainers] Bug#767504: mpd: licence clash with libmp4v2 (MPL) and mpd GPL-+2
On Fri, Oct 31, 2014 at 03:27:47PM +0100, grossepoube...@free.fr wrote: You can't link GPL packages against MPL packages. [Resent, I forgot the BTS] Interesting. Can you explain in a bit more detail? Nothing new here. Fabian Greffrath's replied the same when someone asked to link mediatomb against mp4v2 : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696551#19 IANAL, but I read in MPL1.1 section 6.2 that I can choose to use the code under a newer version of the license, such as MPL2.0 which is deemed compatible with the GPL by the FSF. This upgrade option is made even more explicit in section 3.1 of the MPL1.1 which says IANAL too, but you can find several pages saying that MPL isn't compatible with GPL like this one : http://www.tomhull.com/ocston/docs/mozgpl.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767460: [pkg-php-pear] Bug#767460: php-htmlpurifier: Missing versioned dependency on dpkg
Hi Roland, Le 31/10/2014 04:20, Roland Mas a écrit : Package: php-htmlpurifier Version: 4.6.0-1 Severity: serious Indeed, the debian/maintscript involves relative symlinks. However, according to dpkg's changelog, such relative symlinks have only been supported since 1.17.14. It worked before: I just successfully upgraded php-htmlpurifier using dpkg 1.17.10. Looking closer at dpkg changelog, the regression seems to have been introduced in dpkg 1.17.13: * Fix dpkg-maintscript-helper symlink_to_dir to assure absolute pathnames arguments. And then, fixed in dpkg 1.17.14: * Add support for relative symlinks to dpkg-maintscript-helper symlink_to_dir command. Suggested by Don Armstrong d...@debian.org. So the php-htmlpurifier currently in testing can't be installed by the dpkg currently in testing. I guess a simple versioned dependency would fix that (alternatively, a rewrite of the maintscript to use absolute targets for the symlinks). I’d rather reassign this bug to dpkg 1.17.13 and close it with dpkg 1.17.14 (php-htmlpurifier is not the only package relying on symlink_to_dir. As documented on dpkg-maintscript-helper(1), the old-target must be provided, and such target are often relatives, as expected by the policy). Regards David signature.asc Description: OpenPGP digital signature
Bug#766195: [PATCH] ipv6: reuse ip6_frag_id from ip6_ufo_append_data
On Fri, 2014-10-31 at 09:13 +0100, Harald Staub wrote: On 30.10.2014 20:00, Ben Hutchings wrote: [...] Yes, I can see how this (disabling virtio features) would prevent live migration from old to new host kernels. You will probably need a one-time reboot of the guest when migrating to the new host kernel. We could either mention this in the DSA text, or keep UFO enabled even though it doesn't work correctly (in practice, we sort of have to do that as the tap device's feature flags aren't respected by guests - which I think is a QEMU bug). Please let us know whether live migration between two hosts running the new kernel version does work (I think it will). I confirm that. [...] Thanks. We're going to document the live migration issue rather than fixing it. Ben. -- Ben Hutchings The world is coming to an end. Please log off. signature.asc Description: This is a digitally signed message part
Bug#767460: [pkg-php-pear] Bug#767460: php-htmlpurifier: Missing versioned dependency on dpkg
David Prévot, 2014-10-31 12:24:05 -0400 : [...] However, according to dpkg's changelog, such relative symlinks have only been supported since 1.17.14. It worked before: I just successfully upgraded php-htmlpurifier using dpkg 1.17.10. Looking closer at dpkg changelog, the regression seems to have been introduced in dpkg 1.17.13: Oh. Sorry then. [...] I’d rather reassign this bug to dpkg 1.17.13 and close it with dpkg 1.17.14 (php-htmlpurifier is not the only package relying on symlink_to_dir. As documented on dpkg-maintscript-helper(1), the old-target must be provided, and such target are often relatives, as expected by the policy). Fair enough. In this case, feel free to reassign/downgrade. I worked around the problem by upgrading dpkg by hand, and I guess it'll fix itself when dpkg migrates to testing anyway. Roland. -- Roland Mas Sauvez les castors, tuez les bûcherons. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 756588
Processing commands for cont...@bugs.debian.org: tags 756588 + pending Bug #756588 [viewpdf.app] [i386] Crash in -[CenteringClipView constrainScrollPoint:] when opening a PDF file Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 756588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756588 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#767475: Old version - please verify
The current version of lava-server in unstable and in testing is 2014.09.1-1 but this bug (which is fixed in 2014.09.1-1) was filed today against 2014.09-1 which is no longer in the archive. The bug was spotted upstream and no bug had been reported in Debian before the upload of the fix on Mon, 20 Oct 2014 17:19:17. -- Neil Williams = http://www.linux.codehelp.co.uk/ pgpYXFAoTEz8X.pgp Description: OpenPGP digital signature
Bug#767519: solr-jetty: update the path of dpkg-statoverride in the postrm script
Package: solr-jetty Version: 3.6.2+dfsg-4 Severity: serious The postrm script of solr-jetty checks the existence of /usr/sbin/dpkg-statoverride, but this path no longer exists since dpkg/1.17.0. When solr-jetty is removed along jetty8 this brings dpkg in a state where new installs fail because the statoverride file references an unknown jetty user. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767387: [Pkg-opencl-devel] Bug#767387: beignet: Non-free files in test suite
*mandelbrot* were included in this report by mistake, and are actually OK to keep. Now it FTBFS (it was working before the dfsg changes), tail of buildlog: I get the same error with git-buildpackage, but success with dpkg-buildpackage (as root in cowbuilder --login chroot; not cowbuilder --build because I wanted the test suite)...not sure what to make of that (are the quotes around OCL_PCM_PATH relevant? I don't have them:) [ 8%] Generating ../../src/kernels/cl_internal_built_in_kernel_str.c cd /home/rnpalmer/Debian/builds/stackbuild/beignet/obj-x86_64-linux-gnu/src rm -rf /home/rnpalmer/Debian/builds/stackbuild/beignet/src/kernels//cl_internal_built_in_kernel_str.c cd /home/rnpalmer/Debian/builds/stackbuild/beignet/obj-x86_64-linux-gnu/src OCL_PCM_PATH=/home/rnpalmer/Debian/builds/stackbuild/beignet/obj-x86_64-linux-gnu/backend/src/beignet.bc:/usr/lib/beignet//beignet.bc OCL_PCH_PATH=/home/rnpalmer/Debian/builds/stackbuild/beignet/obj-x86_64-linux-gnu/backend/src/usr/lib/beignet/ocl_stdlib.h.local.pch:/usr/lib/beignet//ocl_stdlib.h.pch LD_LIBRARY_PATH=/home/rnpalmer/Debian/builds/stackbuild/beignet/obj-x86_64-linux-gnu/backend/src /home/rnpalmer/Debian/builds/stackbuild/beignet/obj-x86_64-linux-gnu/backend/src/gbe_bin_generater -s /home/rnpalmer/Debian/builds/stackbuild/beignet/src/kernels//cl_internal_built_in_kernel.cl -o/home/rnpalmer/Debian/builds/stackbuild/beignet/src/kernels//cl_internal_built_in_kernel_str.c /usr/bin/cmake -E cmake_progress_report /home/rnpalmer/Debian/builds/stackbuild/beignet/obj-x86_64-linux-gnu/CMakeFiles 2 The attached patch disables the removed tests, but that's only required if you actually want to run the others, which our normal build doesn't. debian/source/include-binaries probably shouldn't be there, but removing it doesn't help. Description: Skip deleted tests Parts of the test suite are omitted from this package because they are not DFSG-free. Skip those parts to allow running the rest. Author: Rebecca Palmer rebecca_pal...@zoho.com Bug-Debian: https://bugs.debian.org/767387 diff --git a/utests/CMakeLists.txt b/utests/CMakeLists.txt index 9c531de..43965ac 100644 --- a/utests/CMakeLists.txt +++ b/utests/CMakeLists.txt @@ -22,12 +22,8 @@ set (utests_sources utest_error.c compiler_basic_arithmetic.cpp compiler_displacement_map_element.cpp - compiler_shader_toy.cpp compiler_mandelbrot.cpp compiler_mandelbrot_alternate.cpp - compiler_box_blur_float.cpp - compiler_box_blur_image.cpp - compiler_box_blur.cpp compiler_insert_to_constant.cpp compiler_argument_structure.cpp compiler_arith_shift_right.cpp
Bug#737030: libgcrypt uses processor features not allowed for armhf (and i386?)
Control: tags -1 moreinfo Hi Matthias, On Wed, 29 Jan 2014 16:09:38 +0100 Matthias Klose d...@debian.org wrote: hmm, looking further into the code, it looks like libgcrypt implements it's own way to detect hw features. But maybe somebody could confirm this. If the library did indeed use such processor features on i386(/armhf) many users would have experienced actual crashes. This bug seems human performed static analysis false positive. Please check if the bug is valid, since it is currently an RC bug without any observable problem. Cheers, Balint -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: libgcrypt uses processor features not allowed for armhf (and i386?)
Processing control commands: tags -1 moreinfo Bug #737030 [libgcrypt20] libgcrypt uses processor features not allowed for armhf (and i386?) Added tag(s) moreinfo. -- 737030: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737030 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#767523: wmweather+: Does not download weather information anymore
Package: wmweather+ Version: 2.13-1 Severity: grave Justification: renders package unusable Hi, wmweather+ 2.13 is not downloading weather information from weather.noaa.gov anymore. Thus, no weather conditions are displayed and the program is pretty much useless. Upstream version 2.15 works fine and thus presumably fixes the underlying issue. Please package 2.15. Regards, Martin -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.16-2-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wmweather+ depends on: ii libc62.19-11 ii libcurl3-gnutls 7.38.0-2 ii libpcre3 1:8.35-3 ii libwraster3 0.95.5-2 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.2-1 ii libxpm4 1:3.5.11-1 wmweather+ recommends no packages. Versions of packages wmweather+ suggests: ii kde-window-manager [x-window-manager] 4:4.11.12-1 ii metacity [x-window-manager]1:3.12.0-2 ii mutter [x-window-manager] 3.14.0-1 ii openbox [x-window-manager] 3.5.2-7 ii xfwm4 [x-window-manager] 4.10.1-2 pn xless none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767387: beignet: Non-free files in test suite
On 2014-10-31 18:26, Rebecca N. Palmer wrote: (are the quotes around OCL_PCM_PATH relevant? I don't have them:) Good catch :-) Probably cmake adds these as guards because of the ~ in the path. So I'm using env now :-) Reworking the git repository now ... expect a new version later tonight. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764930: [Pkg-opencl-devel] Bug#764930: beignet: FTBFS - uses versioned llvm commands, but unversioned build dependency
You have my blessing to change the maintainer field if you like, as I won't be able to do as much as is needed in the next days. It would probably make sense for the pkg-opencl-devel list to own this package; I'm willing to be named as uploader, but will need a sponsor to actually upload anything. There is a regression in the last NMU: Ubuntu LLVM has a different epoch, Not any more: https://launchpadlibrarian.net/188131885/buildlog_ubuntu-vivid-amd64.beignet_0.8-1.1_FAILEDTOBUILD.txt.gz (FTBFS with this bug, not BD-Uninstallable) There's two Ubuntu bugs that are fixed in 0.9.3: LP#1372889 and LP#1350773. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: eagle: don't depend on libjpeg62 nor libpng anymore
Processing commands for cont...@bugs.debian.org: severity 767379 serious Bug #767379 [src:eagle] libjpeg62-turbo provides libjpeg62, but no version for it Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 767379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767379 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#767379: eagle: don't depend on libjpeg62 nor libpng anymore
severity 767379 serious thanks In testing/sid: eagle depends on libjpeg62-dev which is now a virtual package. Also, libpng-dev dependency can be dropped as well. In wheezy, the dependency on libjpeg62 was deprecated, so you're right - that warning/error doesn't matter for stable and the programs should work normally. Also there are unresolved references to ssl symbols: dpkg-shlibdeps: warning: debian/eagle/usr/lib/eagle/bin/eagle contains an unresolvable reference to symbol DSA_free: it's probably a plugin (and 100+ others)... probably should be cleaned up before release. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747908: [libtuxcap] [transition blocker] Please allow to compile with imagemagick/experimental
On 31.10.2014 11:24, Colin Watson wrote: [...] Here's a simpler patch that gets the job done. I effectively replaced the existing cmake_imagemagick.patch rather than creating too much patch-on-patch spaghetti there. Hi, thanks for the patch. I can't upload the package myself. If you have some spare time left, feel free to do a NMU for libtuxcap. Otherwise I have to find a sponsor first. Regards, Markus signature.asc Description: OpenPGP digital signature
Processed: reassign 767460 to dpkg, closing 767460, affects 767460
Processing commands for cont...@bugs.debian.org:
reassign 767460 dpkg 1.17.13
Bug #767460 [php-htmlpurifier] php-htmlpurifier: Missing versioned dependency
on dpkg
Bug reassigned from package 'php-htmlpurifier' to 'dpkg'.
No longer marked as found in versions php-htmlpurifier/4.6.0-1.
Ignoring request to alter fixed versions of bug #767460 to the same values
previously set
Bug #767460 [dpkg] php-htmlpurifier: Missing versioned dependency on dpkg
Marked as found in versions dpkg/1.17.13.
close 767460 1.17.14
Bug #767460 [dpkg] php-htmlpurifier: Missing versioned dependency on dpkg
There is no source info for the package 'dpkg' at version '1.17.14' with
architecture ''
Unable to make a source version for version '1.17.14'
Marked as fixed in versions 1.17.14.
Bug #767460 [dpkg] php-htmlpurifier: Missing versioned dependency on dpkg
Marked Bug as done
affects 767460 php-htmlpurifier
Bug #767460 {Done: David Prévot taf...@debian.org} [dpkg] php-htmlpurifier:
Missing versioned dependency on dpkg
Added indication that 767460 affects php-htmlpurifier
thanks
Stopping processing here.
Please contact me if you need assistance.
--
767460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767460
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#737030: libgcrypt uses processor features not allowed for armhf (and i386?)
2014-10-31 18:29 GMT+01:00 Balint Reczey bal...@balintreczey.hu: Control: tags -1 moreinfo Hi Matthias, On Wed, 29 Jan 2014 16:09:38 +0100 Matthias Klose d...@debian.org wrote: hmm, looking further into the code, it looks like libgcrypt implements it's own way to detect hw features. But maybe somebody could confirm this. If the library did indeed use such processor features on i386(/armhf) many users would have experienced actual crashes. This bug seems human performed static analysis false positive. Oh, I forgot the :-) here. No offense. :-) -- 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 767075 is serious, block 767075 with 767230
Processing commands for cont...@bugs.debian.org: severity 767075 serious Bug #767075 [pidgin-otr] pidgin-otr: Needs to Depend: libotr5 (= 4.1.0) Severity set to 'serious' from 'important' block 767075 with 767230 Bug #767075 [pidgin-otr] pidgin-otr: Needs to Depend: libotr5 (= 4.1.0) 767075 was not blocked by any bugs. 767075 was not blocking any bugs. Added blocking bug(s) of 767075: 767230 thanks Stopping processing here. Please contact me if you need assistance. -- 767075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767075 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: [pkg-cli-apps-team] Bug#764646: Should this package be removed?
Processing commands for cont...@bugs.debian.org: reassign 764646 ftp.debian.org Bug #764646 [f-spot] Should this package be removed? Bug reassigned from package 'f-spot' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #764646 to the same values previously set Ignoring request to alter fixed versions of bug #764646 to the same values previously set retitle 764646 RM: unmaintained, dead upstream, RC-buggy, depends on obsolete libs Bug #764646 [ftp.debian.org] Should this package be removed? Changed Bug title to 'RM: unmaintained, dead upstream, RC-buggy, depends on obsolete libs' from 'Should this package be removed?' thanks Stopping processing here. Please contact me if you need assistance. -- 764646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764646 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#767477: safe-rm: fails to install
On 2014-10-31 at 11:46:21, Holger Levsen wrote: Can't locate Env.pm in @INC (you may need to install the Env module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.1 /usr/local/share/perl/5.20.1 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl) at /usr/bin/rm line 6. Hm, it looks like that Env module isn't even necessary in the first place... I'll do a new upstream release and get this uploaded to Debian too. Francois -- Francois Marier identi.ca/fmarier http://fmarier.org twitter.com/fmarier -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764646: [pkg-cli-apps-team] Bug#764646: Should this package be removed?
reassign 764646 ftp.debian.org retitle 764646 RM: unmaintained, dead upstream, RC-buggy, depends on obsolete libs thanks On Sun, Oct 12, 2014 at 06:33:10PM +0100, Iain Lane wrote: On Thu, Oct 09, 2014 at 11:22:12PM +0200, Moritz Muehlenhoff wrote: Package: f-spot Severity: serious f-spot is the last package using lcms1 (blocking it's removal), hasn't seen a maintainer upload since 2.5 years and is dead upstream (last upstream release in 2010). Also, there's three RC bugs by now. If you agree with the removal, please assign to ftp.debian.org I think so. Team? Since noone voiced objections, I'm reassigning to ftp.debian.org now. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767248: dbconfig-common: removes any permissions from generated include files on upgrade
Hi Dominik,
As I already stated in my previous mail to this bug, I don't think the
issue is really in the part that you were patching. (At least, when I
installed roundcube-core, that part was not used.) The area that you
were patching is only for manual use, and you can argue that that part
is thus not RC (I don't think it is the best we can do, but let's not
fix that now during the freeze). I believe that ucf should not change
any permissions, but I hope the ucf maintainer can respond to that.
However, apart from that, if you had local changes, ucf will happily
move the $tmpout to ${outputfile}.ucf-dist and I rather have that file
to have the same permissions/ownership. Therefor, I think the following
patch is the best that we can do as it does solve the above issue and
work around the, in my opinion, buggy behavior of ucf. Am I overlooking
something?
Paul
diff --git a/dbconfig-generate-include b/dbconfig-generate-include
index de15752..b21e46f 100755
--- a/dbconfig-generate-include
+++ b/dbconfig-generate-include
@@ -222,6 +222,11 @@ if [ $outputfile ]; then
echo unable to create temporary file $tmpout 2
exit 1
fi
+ if [ -e $outputfile ] ; then
+ # In order to preserve all local attributes of the
+ # original file, copy it, we are filling it from scratch
+ cp --preserve=all $outputfile $tmpout
+ fi
exec $tmpout
fi
signature.asc
Description: OpenPGP digital signature
Bug#767379: marked as done (libjpeg62-turbo provides libjpeg62, but no version for it)
Your message dated Fri, 31 Oct 2014 16:21:00 -0400 with message-id cang8-daswedsf-fnij0xwwbi04ohfve37tafedrcxltc2wc...@mail.gmail.com and subject line Re: eagle: don't depend on libjpeg62 nor libpng anymore has caused the Debian Bug report #767379, regarding libjpeg62-turbo provides libjpeg62, but no version for it 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.) -- 767379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libjpeg62-turbo Version: 1:1.3.1-10 Severity: important I am using EAGLE (package eagle 5.12.0-3 from wheezy), which depends on libjpeg62 (= 6b1). Package libjpeg62-turbo (1:1.3.1-10) provides libjpeg62, but no version, so it doesn't satisfy this dependency. Up to 1.3.1-8 there was a package libjpeg62 which worked for me. Transcript from reinstalling eagle after upgrading: root@antares:/home/markus# dpkg -i debian/eagle5/eagle_5.12.0-3_i386.deb Vormals nicht ausgewähltes Paket eagle wird gewählt. (Lese Datenbank ... 413452 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von .../eagle5/eagle_5.12.0-3_i386.deb ... Entpacken von eagle (5.12.0-3) ... dpkg: Abhängigkeitsprobleme verhindern Konfiguration von eagle: eagle hängt ab von libjpeg62 (= 6b1); aber: Paket libjpeg62 ist nicht installiert. Version von libjpeg62 auf dem System, bereitgestellt von libjpeg62-turbo:i386, ist keine. dpkg: Fehler beim Bearbeiten des Paketes eagle (--install): Abhängigkeitsprobleme - verbleibt unkonfiguriert Obviously EAGLE seem to work in this unconfigured state (and shows JPEG images), so I guess providing a suitable version should fix this for me. (No, upgrading EAGLE is not an option for me.) Thanks and best regards, Markus -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.16-3-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libjpeg62-turbo depends on: ii libc6 2.19-12 libjpeg62-turbo recommends no packages. libjpeg62-turbo suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- fixed 767379 6.3.0-1 thanks Upon further investigation, eagle in unstable and testing does not depend on libjpeg62 nor libpng - this was fixed in 6.3.0-1. Also, the bug mentioned here appears to only occur if someone tries to install the wheezy eagle package on the jessie system system jessie does not have the libjpeg2 library the wheezy eagle package expects. The solution could be to install both the wheezy eagle package and the wheezy libjpeg62 package. However, that may conflict with the jessie libjpeg62-turbo package. Either way, the binary will still work but you may end up with a misconfigured dpkg. The solution to that is to uninstall eagle before upgrading the system, then reinstall. Since Debian doesn't support forward-porting of packages from previous releases, I'm closing the bug.---End Message---
Processed: Re: eagle: don't depend on libjpeg62 nor libpng anymore
Processing commands for cont...@bugs.debian.org: fixed 767379 6.3.0-1 Bug #767379 [src:eagle] libjpeg62-turbo provides libjpeg62, but no version for it Marked as fixed in versions eagle/6.3.0-1. thanks Stopping processing here. Please contact me if you need assistance. -- 767379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767379 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#767248: dbconfig-common: removes any permissions from generated include files on upgrade
Hi, + cp --preserve=all $outputfile $tmpout always use cat there. cp --preserve WILL destroy POSIX ACLs and replace symlinks and the like. -nik -- Dominik George (Vorstandsvorsitzender, Pädagogischer Leiter) Teckids e.V. - Erkunden, Entdecken, Erfinden. https://www.teckids.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767379: eagle: don't depend on libjpeg62 nor libpng anymore
fixed 767379 6.3.0-1 thanks Upon further investigation, eagle in unstable and testing does not depend on libjpeg62 nor libpng - this was fixed in 6.3.0-1. Also, the bug mentioned here appears to only occur if someone tries to install the wheezy eagle package on the jessie system system jessie does not have the libjpeg2 library the wheezy eagle package expects. The solution could be to install both the wheezy eagle package and the wheezy libjpeg62 package. However, that may conflict with the jessie libjpeg62-turbo package. Either way, the binary will still work but you may end up with a misconfigured dpkg. The solution to that is to uninstall eagle before upgrading the system, then reinstall. Since Debian doesn't support forward-porting of packages from previous releases, I'm closing the bug. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767248: dbconfig-common: removes any permissions from generated include files on upgrade
On 31-10-14 21:23, Dominik George wrote: Hi, + cp --preserve=all $outputfile $tmpout always use cat there. cp --preserve WILL destroy POSIX ACLs and replace symlinks and the like. This is the $tmpout file I am talking about. So catting doesn't do what you want. Paul signature.asc Description: OpenPGP digital signature
Bug#762272: doxygen: segfaults when building efl (on ix86 amd amd64)
Hi Helmut,
On Sat, 20 Sep 2014 18:48:36 +0200 Helmut Grohne hel...@subdivi.de wrote:
On Sat, Sep 20, 2014 at 04:56:24PM +0200, Helmut Grohne wrote:
* The bug is reproducible with efl 1.8.6-2 source when reducing the
value of INPUT to @top_srcdir@/src/lib/eina (faster segfault).
Attaching a minimally reproducing sample.
Helmut
Thanks for the sample.
This is the beginning of the endless recursion:
...
#7244 0x005d1892 in recursivelyAddGroupListToTitle (ol=...,
d=0x18, root=false)
at util.cpp:6377
gli = {QListIteratorGroupDef = {QGListIterator = {list =
0x14f7400,
curNode = 0x14f7440}, No data fields},
_vptr.GroupListIterator = 0x825a10 vtable for
GroupListIterator+16}
first = true
groups = 0x1
#7245 0x005d1892 in recursivelyAddGroupListToTitle (ol=...,
d=0x18, root=false)
at util.cpp:6377
gli = {QListIteratorGroupDef = {QGListIterator = {list =
0x14f7480,
curNode = 0x14f74c0}, No data fields},
_vptr.GroupListIterator = 0x825a10 vtable for
GroupListIterator+16}
first = true
groups = 0x1
#7246 0x005d1892 in recursivelyAddGroupListToTitle (ol=...,
d=0x18, d@entry=0x14fa160,
root=false, root@entry=true) at util.cpp:6377
gli = {QListIteratorGroupDef = {QGListIterator = {list =
0x14f7400,
curNode = 0x14f7440}, No data fields},
_vptr.GroupListIterator = 0x825a10 vtable for
GroupListIterator+16}
first = true
groups = 0x1
#7247 0x005d1a8a in addGroupListToTitle (ol=...,
d=d@entry=0x14fa160) at util.cpp:6396
No locals.
#7248 0x0045fb50 in GroupDef::writeDocumentation
(this=0x14fa160, ol=...) at groupdef.cpp:943
lang = optimized out
eli = {QGListIterator = {list = 0x1503350,
curNode = 0x7f49617ebeb0 __GI___libc_malloc+96}, No data
fields}
#7249 0x00439321 in generateGroupDocs () at doxygen.cpp:8963
No locals.
#7250 generateOutput () at doxygen.cpp:11383
generateMan = 192
serverBasedSearch = false
thisDir = {_vptr.QDir = 0x14f3100, dPath = {static null = {No
data fields}, d = 0x0,
static shared_null = 0x1407f00}, fList = 0x0, fiList = 0x0,
nameFilt = {
static null = {No data fields}, d = 0x14f5700, static
shared_null = 0x1407f00},
filtS = QDir::All, sortS = QDir::IgnoreCase, dirty = 1,
allDirs = 0}
searchEngine = true
#7251 0x0040907e in main (argc=1, argv=0x7fffb1835c38) at
main.cpp:38
No locals.
(gdb) quit
The trace can be reproducer by running doxygen the following way:
doxy$ ls
input.h
Doxyfile
doxy$ ulimit -s 1024
doxy$ doxygen
...
Segmentation fault (core dumped)
doxy$ (echo -e file doxygen\ncore core\nbt full) | gdb gdb.log
Cheers,
Balint
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710590: ufraw: Same error with RAF in standalone tool
Hello Hubert, It's fixed with the new version! Many thanks! --thomas On 10/31/2014 10:24 PM, Hubert Chathi wrote: On Fri, 24 Oct 2014 20:04:50 +0200, Thomas Imbreckx zi...@member.fsf.org said: Trying to load RAF files from my Fuji X20 fail with errors : Procedure 'file-ufraw-load' returned no return values with Gimp plugin, or 'Segmentation fault' with stand-alone ufraw tool. I have uploaded a RAF file with public access if it helps: https://flagg.iozero.be/owncloud/public.php?service=filest=eee1ffb5fe78d51c40aa6e45553e773a Hi Thomas, Please try upgrading to the latest version (0.20-1), as that version has some Fuji-related fixes. I tried that image on my system, and it was able to load and convert the picture. -- thomas -- 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 740034 is serious
Processing commands for cont...@bugs.debian.org: # arm64 is now in the archive, so this can break real Debian systems severity 740034 serious Bug #740034 [lshw] lshw can crash arm64 systems Severity set to 'serious' from 'wishlist' thanks Stopping processing here. Please contact me if you need assistance. -- 740034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740034 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#765681: libqtgui4-perl: QtGui4 module cannot be imported: 2nd patch
Looks like the 2nd part of the problem is solved there: https://bugs.kde.org/show_bug.cgi?id=340518#c1 or https://projects.kde.org/projects/kde/kdebindings/perl/perlqt/repository/revisions/1b665848e178301344386717c658386d160d222a HTH -- https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767519: marked as done (solr-jetty: update the path of dpkg-statoverride in the postrm script)
Your message dated Fri, 31 Oct 2014 22:04:55 + with message-id e1xkkjt-0001kf...@franck.debian.org and subject line Bug#767519: fixed in lucene-solr 3.6.2+dfsg-5 has caused the Debian Bug report #767519, regarding solr-jetty: update the path of dpkg-statoverride in the postrm script 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.) -- 767519: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767519 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: solr-jetty Version: 3.6.2+dfsg-4 Severity: serious The postrm script of solr-jetty checks the existence of /usr/sbin/dpkg-statoverride, but this path no longer exists since dpkg/1.17.0. When solr-jetty is removed along jetty8 this brings dpkg in a state where new installs fail because the statoverride file references an unknown jetty user. ---End Message--- ---BeginMessage--- Source: lucene-solr Source-Version: 3.6.2+dfsg-5 We believe that the bug you reported is fixed in the latest version of lucene-solr, 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 767...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg ebo...@apache.org (supplier of updated lucene-solr 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, 31 Oct 2014 19:28:25 +0100 Source: lucene-solr Binary: liblucene3-java liblucene3-contrib-java liblucene3-java-doc libsolr-java solr-common solr-tomcat solr-jetty Architecture: source all Version: 3.6.2+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Emmanuel Bourg ebo...@apache.org Description: liblucene3-contrib-java - Full-text search engine library for Java - additional libraries liblucene3-java - Full-text search engine library for Java - core library liblucene3-java-doc - Documentation for Lucene libsolr-java - Enterprise search server based on Lucene - Java libraries solr-common - Enterprise search server based on Lucene3 - common files solr-jetty - Enterprise search server based on Lucene3 - Jetty integration solr-tomcat - Enterprise search server based on Lucene3 - Tomcat integration Closes: 701876 752547 767519 767525 Changes: lucene-solr (3.6.2+dfsg-5) unstable; urgency=medium . * Team upload. * Fixed the deployment with Jetty 8 (Closes: #752547, #767525) * Enable the symbolic links with Jetty (Closes: #701876) * Fixed the path to dpkg-statoverride in solr-jetty.postrm (Closes: #767519) Checksums-Sha1: 573df3adf7dc50851408579570ce11ee3d93c499 3179 lucene-solr_3.6.2+dfsg-5.dsc ce48524fcc4ec815d6d7cb97bc2e6524f5f11cd1 47296 lucene-solr_3.6.2+dfsg-5.debian.tar.xz e0dd730b33d34b0ce3c2822a330aae59cccdafe2 1503892 liblucene3-java_3.6.2+dfsg-5_all.deb b76593eed562b471270d6a025697425589b1be04 10896848 liblucene3-contrib-java_3.6.2+dfsg-5_all.deb 763fb4a609e0415799f57c48c3eb790ec315ef75 4833220 liblucene3-java-doc_3.6.2+dfsg-5_all.deb 74642440c7abae5e629b83607206722574717a46 1965182 libsolr-java_3.6.2+dfsg-5_all.deb ed8f5cb1342db05815295011ea5bc09c6f378dcf 144422 solr-common_3.6.2+dfsg-5_all.deb f7ac027a4c66983a59dde16492c87df7eb482f21 8598 solr-tomcat_3.6.2+dfsg-5_all.deb feb7b6f72464e779f7a446ea9bde0ddb5218d1d6 8304 solr-jetty_3.6.2+dfsg-5_all.deb Checksums-Sha256: ee55cbd58ec4480e7a8708c537c126e26fb130b936a0d4fb3b50fe1b0e3965f9 3179 lucene-solr_3.6.2+dfsg-5.dsc ee37274b48751bf51764a19dd70e14ba9f4bf85406bedebbdb29a98dbd67d5c8 47296 lucene-solr_3.6.2+dfsg-5.debian.tar.xz d5e3d48882f26bb2de9145347d496d4da58669dd300c27417d0ff246af87bf3a 1503892 liblucene3-java_3.6.2+dfsg-5_all.deb e0c195cfe4f27cb1a505312097d992e7c9ecad30e23cdb45877f32875d0caac5 10896848 liblucene3-contrib-java_3.6.2+dfsg-5_all.deb d7f60dafefdb31b0e4e5c84267488eeb5737f8f21031d20840f09e5d290050bb 4833220 liblucene3-java-doc_3.6.2+dfsg-5_all.deb b6c9083eba64d010a129627d12267de915841168cb7112a17f78418e27fb649c 1965182 libsolr-java_3.6.2+dfsg-5_all.deb 74f553bce3648b73c397a3f3a59fe8d2a82cca4cc2366acff34bd90e5d87ecd2 144422 solr-common_3.6.2+dfsg-5_all.deb 5035dfd6dfa0de303982f9b51f0edc90ffcbdf946aea42f153b29f157ac78cd2
Bug#740034: lshw can crash arm64 systems
The problem is not actually restricted to arm64 - I would expect it will also effect all other non-x86 platforms. The attached patch disables the memory scanning for all architectures other than i386 and x86_64, and enables it for all UEFI architectures that provide an SMBIOS entry point address in /sys/firmware/efi/systab. smbios-noscan.patch Description: Binary data
Bug#727149: linux-image-3.10-3-amd64: Network adapter (Intel 82579V) hangs during TX, causing reset and undetected data corruption at the other side
I don't know, because until now I have been using the workaround (i.e. always disable TSO). I just re-enabled it to see if this error will still occur with the latest kernel. I'll report again in a week or so whether it is stable now. Cheers, Timo - Message from Balint Reczey bal...@balintreczey.hu - Date: Fri, 31 Oct 2014 09:17:50 +0100 From: Balint Reczey bal...@balintreczey.hu Subject: Re: linux-image-3.10-3-amd64: Network adapter (Intel 82579V) hangs during TX, causing reset and undetected data corruption at the other side To: 727...@bugs.debian.org, T.A. van Roermund t...@van-roermund.nl On Sun, 14 Sep 2014 00:52:55 +0200 Balint Reczey bal...@balintreczey.hu wrote: Control: tags -1 moreinfo Hi, On Wed, 23 Oct 2013 18:06:03 +0200 T.A. van Roermund t...@van-roermund.nl wrote: On 22-10-2013 20:02, T.A. van Roermund wrote: In the mean time I have found a solution to this problem: if I disable TCP segmentation offload using the command 'ethtool -K eth2 tso off', the problem does no longer occur. By the way: I found the solution here: https://bbs.archlinux.org/viewtopic.php?id=162841 Is this problem still present with latest kernel from Jessie? Forgot copying submitter, now fixing my mistake. Cheers, Balint - End message from Balint Reczey bal...@balintreczey.hu - -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764930: beignet: FTBFS - uses versioned llvm commands, but unversioned build dependency
On 2014-10-31 19:12, Rebecca N. Palmer wrote: It would probably make sense for the pkg-opencl-devel list to own this That's what I wanted to do anyway :-) package; I'm willing to be named as uploader, Great! Done :-) but will need a sponsor to actually upload anything. That can be managed :-) There is a regression in the last NMU: Ubuntu LLVM has a different epoch, Not any more: Good, didn't touch the B-Ds There's two Ubuntu bugs that are fixed in 0.9.3: LP#1372889 and LP#1350773. closing, too, thanks Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710590: ufraw: Same error with RAF in standalone tool
On Fri, 24 Oct 2014 20:04:50 +0200, Thomas Imbreckx zi...@member.fsf.org said: Trying to load RAF files from my Fuji X20 fail with errors : Procedure 'file-ufraw-load' returned no return values with Gimp plugin, or 'Segmentation fault' with stand-alone ufraw tool. I have uploaded a RAF file with public access if it helps: https://flagg.iozero.be/owncloud/public.php?service=filest=eee1ffb5fe78d51c40aa6e45553e773a Hi Thomas, Please try upgrading to the latest version (0.20-1), as that version has some Fuji-related fixes. I tried that image on my system, and it was able to load and convert the picture. -- Hubert Chathi uho...@debian.org -- Jabber: hub...@uhoreg.ca PGP/GnuPG key: 1024D/124B61FA http://www.uhoreg.ca/ Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA -- 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#767051: libjinput-java: uninstallable on kfreebsd
Processing control commands: severity -1 normal Bug #767051 [libjinput-java] libjinput-java: uninstallable on kfreebsd Severity set to 'normal' from 'serious' -- 767051: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767051 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#767051: libjinput-java: uninstallable on kfreebsd
Control: severity -1 normal On Tue, 28 Oct 2014 11:05:11 + Steven Chamberlain ste...@pyro.eu.org wrote: Hi, On 28/10/14 03:16, Michael Gilbert wrote: This package currently depends on libjinput-jni, which is currently not build on the kfreebsds (#657771), so the libjinput-java is uninstallable on those architectures. Not a bug? I think it is a bug because we want jinput to be available on all supported architectures. However the severity should be normal. libjinput-java is an Arch: all package. I assume it's actually okay that it is uninstallable on some arches; FTP master can't very well remove it from those and not the others. src:jinput does also build libjinput-jni which is Arch: any, but that FTBFS on kfreebsd on sid/jessie: https://buildd.debian.org/status/package.php?p=jinputsuite=unstable I don't think it has ever built before on kfreebsd so, I don't think that could be an RC bug either? https://buildd.debian.org/status/logs.php?pkg=jinputarch=kfreebsd-amd64 Agreed. The package never built on kfreebsd-*, so this is not RC in my opinion. Regards, Markus signature.asc Description: Digital signature
Bug#764930: beignet: FTBFS - uses versioned llvm commands, but unversioned build dependency
On 2014-10-31 09:29, Zhigang Gong wrote: Just want to mention, the beignet version 1.0 will be released within two weeks, if everything is ok. And all the known copyright issue will be solved before that. Good to know, but it will be a bit too late for inclusion in Debian 8.0. So I'll try to get a fixed 0.9.3 in there instead. The Debian packaging is now available in git git://anonscm.debian.org/pkg-opencl/beignet.git and contains 2 patches from me that should go upstream: debian/patches/000*.patch Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763211: libappindicator: FTBFS: src/app-indicator.c:480: Error: AppIndicator: multiple @arg1 parameters for identifier AppIndicator::new-label:
Hi David, On Sun, 28 Sep 2014 18:47:01 +0200 David =?iso-8859-1?Q?Su=E1rez?= david.sephi...@gmail.com wrote: ... Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/libdbusmenu-gtk3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libindicator3-0.4 -Wall -Werror -DG_LOG_DOMAIN=\libappindicator\ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o libappindicator3_la-app-indicator.lo `test -f 'app-indicator.c' || echo '../../src/'`app-indicator.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/libdbusmenu-gtk3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libindicator3-0.4 -Wall -Werror -DG_LOG_DOMAIN=\libappindicator\ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c ../../src/app-indicator.c -fPIC -DPIC -o .libs/libappindicator3_la-app-indicator.o ../../src/app-indicator.c: In function 'app_indicator_set_property': ../../src/app-indicator.c:902:6: error: 'gtk_status_icon_set_title' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkstatusicon.h:143) [-Werror=deprecated-declarations] gtk_status_icon_set_title(priv-status_icon, priv-title ? priv-title : ); ... I have uploaded a fixed version to DELAYED/5. Please see the debdiff attached. Cheers, Balint diff -u libappindicator-0.4.92/debian/changelog libappindicator-0.4.92/debian/changelog --- libappindicator-0.4.92/debian/changelog +++ libappindicator-0.4.92/debian/changelog @@ -1,3 +1,11 @@ +libappindicator (0.4.92-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Don't treat deprecated API usage as error during the build to fix FTBFS +(Closes: #763211) + + -- Balint Reczey bal...@balintreczey.hu Fri, 31 Oct 2014 21:38:56 +0100 + libappindicator (0.4.92-3) unstable; urgency=medium * Team upload. diff -u libappindicator-0.4.92/debian/rules libappindicator-0.4.92/debian/rules --- libappindicator-0.4.92/debian/rules +++ libappindicator-0.4.92/debian/rules @@ -8,6 +8,9 @@ export MONO_SHARED_DIR=$(CURDIR) export CSC=/usr/bin/mono-csc + +CFLAGS = $(shell dpkg-buildflags --get CFLAGS) -Wno-error=deprecated-declarations + include /usr/share/cdbs/1/rules/patchsys-quilt.mk include /usr/share/cdbs/1/rules/autoreconf.mk include /usr/share/cdbs/1/rules/debhelper.mk @@ -64,12 +67,13 @@ binary-install/libappindicator1:: install-stamp install-stamp-gtk3 dh_makeshlibs -plibappindicator1 + configure-stamp-gtk3: : # configure for GTK+ 3.0 rm -rf build-gtk3; \ mkdir build-gtk3; \ cd build-gtk3; \ - $(DEB_CONFIGURE_SCRIPT_ENV) ../configure --with-gtk=3 \ + $(DEB_BUILD_MAINT_OPTIONS) CFLAGS=$(CFLAGS) ../configure --with-gtk=3 \ $(filter-out --enable-gtk-doc, $(filter-out --srcdir=%, $(DEB_CONFIGURE_NORMAL_ARGS) $(DEB_CONFIGURE_EXTRA_FLAGS))) \ --enable-gtk-doc=no; \ cd ..;
Bug#766966: marked as done (g++-4.9-arm-linux-gnueabihf: Cannot install package due to conflict with debian's gcc-4.9-base-4.9.1-19)
Your message dated Fri, 31 Oct 2014 23:46:04 + with message-id 20141031234604.gg28...@stoneboat.aleph1.co.uk and subject line Cannot install package due to conflict with debian's gcc-4.9-base-4.9.1-19 has caused the Debian Bug report #766966, regarding g++-4.9-arm-linux-gnueabihf: Cannot install package due to conflict with debian's gcc-4.9-base-4.9.1-19 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.) -- 766966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: g++-4.9-arm-linux-gnueabihf Severity: grave Justification: renders package unusable Dear Maintainer, I cannot install gnueabihf for armhf toolchain on amd64 platform. g++-4.9-arm-linux-gnueabihf : Depends: gcc-4.9-base (= 4.9.1-18) but 4.9.1-19 is to be installed Depends: cpp-4.9-arm-linux-gnueabihf (= 4.9.1-18) but it is not going to be installed Depends: gcc-4.9-arm-linux-gnueabihf (= 4.9.1-18) but it is not going to be installed Depends: libstdc++-4.9-dev:armhf (= 4.9.1-18) but it is not going to be installed E: Unable to correct problems, you have held broken packages. I believe this is because current gcc-4.9-base in Debian is 4.9.1-19 which is in conflict with 4.9.1-18, and there is no existing package of gcc-4.9-base-4.9.1-18 for amd64 architecture in any repository. Solution would probably to update packages. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 armhf Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- A new version of this package has been uploaded, built against gcc-4.9 4.9.1-19 So it is installable again. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/---End Message---
Bug#750857: NMU debdiff for mod-gnutls_0.6-1.1
Hi, I'm temporarily removing mod-gnutls from Jessie so that the transitions it is blocking can be completed before the freeze begins. I'll happily grant mod-gnutls a freeze exception so it can re-enter testing if this bug can be fixed within 14 days of the freeze beginning. Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Bug#767397: marked as done (python-sphinx-testing: dist-packages/tests/__init__.py conflict)
Your message dated Sat, 01 Nov 2014 00:49:05 + with message-id e1xkmsl-td...@franck.debian.org and subject line Bug#767397: fixed in sphinx-testing 0.6.0-2 has caused the Debian Bug report #767397, regarding python-sphinx-testing: dist-packages/tests/__init__.py conflict 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.) -- 767397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-sphinx-testing Version: 0.6.0-1 Severity: serious Justification: Policy 6.6 (4) python-sphinx-testing and python3-sphinx-testing respectively ship the overly generic paths /usr/lib/python2.7/dist-packages/tests/__init__.py and /usr/lib/python3/dist-packages/tests/__init__.py, leading to de facto conflicts with similarly broken packages. Please either install these tests somewhere less likely to cause trouble or omit them altogether. Thanks! ---End Message--- ---BeginMessage--- Source: sphinx-testing Source-Version: 0.6.0-2 We believe that the bug you reported is fixed in the latest version of sphinx-testing, 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 767...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kouhei Maeda mkou...@palmtb.net (supplier of updated sphinx-testing 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, 31 Oct 2014 11:23:50 +0900 Source: sphinx-testing Binary: python-sphinx-testing python3-sphinx-testing Architecture: source all Version: 0.6.0-2 Distribution: unstable Urgency: medium Maintainer: Kouhei Maeda mkou...@palmtb.net Changed-By: Kouhei Maeda mkou...@palmtb.net Description: python-sphinx-testing - testing utility for Sphinx extensions python3-sphinx-testing - testing utility for Sphinx extensions for Python3 Closes: 767397 Changes: sphinx-testing (0.6.0-2) unstable; urgency=medium . * Fixed dist-packages/tests/__init__.py conflict (Closes: #767397) - debian/rules * Appdended override_dh_python3, override_dh_python2. - Thanks for report Aaron M. Ucko u...@debian.org Checksums-Sha1: ac3ad64bb6695eb0c7e7619fe661d753b15eabb0 2124 sphinx-testing_0.6.0-2.dsc ef0e344ba8aaa7be72acd1a5bad03c216849a50e 2536 sphinx-testing_0.6.0-2.debian.tar.xz 4e016ccc41f3e786538b7bde32d5718d18e43fce 7126 python-sphinx-testing_0.6.0-2_all.deb 3263a7b818947847953feecb43dcfa2e769331fa 6890 python3-sphinx-testing_0.6.0-2_all.deb Checksums-Sha256: 5c85918fe6b8e5043e8ec2c93af6fe6a0da3a391e2acf26421c3a5e2fb19835e 2124 sphinx-testing_0.6.0-2.dsc e4ae549b08038e8799707aa19e7e017acae442a8fdda552d55287f4fc1e7b044 2536 sphinx-testing_0.6.0-2.debian.tar.xz b5d374c9822a366d9862b99fd21c89f50261aa99a99dadf05077d0a1f53a8a6e 7126 python-sphinx-testing_0.6.0-2_all.deb 910c80c3cca16734efa65796dff5c8dd6b3d03f5a78cafbe02d13a2ae00f80f1 6890 python3-sphinx-testing_0.6.0-2_all.deb Files: 687e3d6b86ecd78a6b2ef834f9d74aa2 2124 python optional sphinx-testing_0.6.0-2.dsc d29db4e3fd660406016fbb19ebc0d649 2536 python optional sphinx-testing_0.6.0-2.debian.tar.xz 9ea87b796964d7f6ca7e3e135903590b 7126 python optional python-sphinx-testing_0.6.0-2_all.deb 831b833370771be25672f4527ef054b0 6890 python optional python3-sphinx-testing_0.6.0-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUVCqbAAoJEDIkf7tArR+mMWUP/39W+VwdwhCJ+8eQpGGGY0ZN yqG8tq4Plc0dWJEapqcbRhSrpFdHV5n56zHe1hgwKhqKUjodCC3aRigRs7cDTZSp MF2yAuy5wsuoJiYZDWFmrWwnzIieIO0zeZ/dP6UR0tbLcg75WhE0RRa1skbDf8bv zhZxtwzdj62wPMt7lKG+Y16Lp11zKkqKKgzP4sbEdmZS/zqnoAyyJXqIhGf6jJXn 1W+eXyTDCC0qVFhkMx2P2FU1BPoUmoNBpu2MAlxy6r3Eo8S60pdJcZZbvII3R8RE 0QyBkZ4FyEhp6MmWo00K4hC2khqhg934dpr1T84AP5xszGDzJGpCCdyjzbpOh9CW FmEdeqY5anIycUaBa1kyuiYYHSOU5oDXRuqC2npblqMRtUA6Tj7syv7HlUD7C9uf HYiEYr+CwsZtfIWRr6GeNgrVCShsCRevn/bcLFWvKMghtwkoXTDEOHlVjErlRN4e luklserKF0CE1P5OPvdNV9txV4aX3PMF5XE2bwriIT8F8hz0PtLU1+lvSaLmE++v itnPc0R9Ggvt2cJEUEMMvB/dVbmMyhQRTVCqI9CR3SG38nbig1s2EIEb7ru0NWeM EOYAL91vm38sTuHYybpdwgsDXmNc97sBHesf1xDAVqpsyBRhDbLyHXPLynMfk75z 0253zcZz+lqN6CGwjCF/ =fUHU -END PGP SIGNATUREEnd Message---
Bug#751233: missing licenses in debian/copyright
Hi Daniele (2014.08.16_08:02:21_-0700) Thanks for looking at this. I think we can do slightly better, by using uscan's built-in repacking support. Like so. I'll request an unblock. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 461 1230 C: +27 72 419 8559 Index: debian/changelog === --- debian/changelog(revision 30261) +++ debian/changelog(working copy) @@ -1,3 +1,16 @@ +python-virtualenv (1.11.6+ds-1) unstable; urgency=medium + + [ Daniele Tricoli ] + * Repack source package to remove embedded copy of python-pip-whl and +python-setuptools-whl (Closes: #751233) + * debian/rules: +- Don't override dh_auto_configure to remove embedded wheels since + they are removed from source package + * debian/watch: +- Add dversionmangle option + + -- Stefano Rivera stefa...@debian.org Fri, 31 Oct 2014 17:59:34 -0700 + python-virtualenv (1.11.6-2) unstable; urgency=medium * d/patches/use-wheels.patch: Ignore EEXIST when creating the Index: debian/copyright === --- debian/copyright(revision 30261) +++ debian/copyright(working copy) @@ -1,7 +1,11 @@ Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: virtualenv Source: https://github.com/pypa/virtualenv + The pristine upstream source contains convenience copies of python-pip-whl and + python-setuptools-whl. +Files-Excluded: virtualenv_support/*.whl + Files: * Copyright: 2007, Ian Bicking and Contributors, 2009, Ian Bicking, The Open Planning Project, @@ -16,15 +20,7 @@ 2012 Barry Warsaw ba...@python.org License: Expat -Files: virtualenv_support/pip-* -Copyright: 2008-2013 The pip developers License: Expat - -Files: virtualenv_support/setuptools-* -Copyright: Phillip J. Eby -License: PSF-2 or Zope-2.1 - -License: Expat Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the Software), to deal in the Software without restriction, including @@ -43,94 +39,3 @@ LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. - -License: PSF-2 - 1. This LICENSE AGREEMENT is between the Python Software Foundation - (PSF), and the Individual or Organization (Licensee) accessing and - otherwise using Python 2.3 software in source or binary form and its - associated documentation. - . - 2. Subject to the terms and conditions of this License Agreement, PSF - hereby grants Licensee a nonexclusive, royalty-free, world-wide - license to reproduce, analyze, test, perform and/or display publicly, - prepare derivative works, distribute, and otherwise use Python 2.3 - alone or in any derivative version, provided, however, that PSF's - License Agreement and PSF's notice of copyright, i.e., Copyright (c) - 2001, 2002 Python Software Foundation; All Rights Reserved are - retained in Python 2.3 alone or in any derivative version prepared by - Licensee. - . - 3. In the event Licensee prepares a derivative work that is based on - or incorporates Python 2.3 or any part thereof, and wants to make - the derivative work available to others as provided herein, then - Licensee hereby agrees to include in any such work a brief summary of - the changes made to Python 2.3. - . - 4. PSF is making Python 2.3 available to Licensee on an AS IS - basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR - IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND - DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS - FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 2.3 WILL NOT - INFRINGE ANY THIRD PARTY RIGHTS. - . - 5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON - 2.3 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS - A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 2.3, - OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. - . - 6. This License Agreement will automatically terminate upon a material - breach of its terms and conditions. - . - 7. Nothing in this License Agreement shall be deemed to create any - relationship of agency, partnership, or joint venture between PSF and - Licensee. This License Agreement does not grant permission to use PSF - trademarks or trade name in a trademark sense to endorse or promote - products or services of Licensee, or any third party. - . - 8. By copying, installing or otherwise using Python 2.3, Licensee - agrees to be bound by the terms and conditions of this License - Agreement. - -License: Zope-2.1 - A copyright notice accompanies this license document that - identifies the copyright holders. - . - This license has been certified as open source. It has also - been
Processed: your mail
Processing commands for cont...@bugs.debian.org: tag 751233 + pending Bug #751233 [python-virtualenv] missing licenses in debian/copyright Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 751233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751233 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: python-persistent and python-zodb: error when trying to install together
Processing control commands: found -1 1:3.9.7-2 Bug #767554 [python-persistent,python-zodb] python-persistent and python-zodb: error when trying to install together There is no source info for the package 'python-persistent' at version '1:3.9.7-2' with architecture '' Marked as found in versions zodb/1:3.9.7-2. -- 767554: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767554 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#767554: python-persistent and python-zodb: error when trying to install together
Package: python-persistent,python-zodb Version: 4.0.8-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 1:3.9.7-2 Architecture: amd64 Distribution: jessie Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package python-zodb. Preparing to unpack .../python-zodb_1%3a3.9.7-2_amd64.deb ... Unpacking python-zodb (1:3.9.7-2) ... dpkg: error processing archive /var/cache/apt/archives/python-zodb_1%3a3.9.7-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/python2.7/dist-packages/persistent/wref.py', which is also in package python-persistent 4.0.8-1 Errors were encountered while processing: /var/cache/apt/archives/python-zodb_1%3a3.9.7-2_amd64.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/lib/python2.7/dist-packages/persistent/__init__.py usr/lib/python2.7/dist-packages/persistent/cPersistence.h usr/lib/python2.7/dist-packages/persistent/dict.py usr/lib/python2.7/dist-packages/persistent/interfaces.py usr/lib/python2.7/dist-packages/persistent/list.py usr/lib/python2.7/dist-packages/persistent/mapping.py usr/lib/python2.7/dist-packages/persistent/ring.h usr/lib/python2.7/dist-packages/persistent/tests/__init__.py usr/lib/python2.7/dist-packages/persistent/tests/test_list.py usr/lib/python2.7/dist-packages/persistent/tests/test_mapping.py usr/lib/python2.7/dist-packages/persistent/tests/test_wref.py usr/lib/python2.7/dist-packages/persistent/tests/utils.py usr/lib/python2.7/dist-packages/persistent/wref.py This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. python-persistent=4.0.8-1_python-zodb=1%3.9.7-2.log.gz Description: application/gzip
Bug#767460: [pkg-php-pear] Bug#767460: php-htmlpurifier: Missing versioned dependency on dpkg
Control: severity -1 wishlist Hi! On Fri, 2014-10-31 at 12:24:05 -0400, David Prévot wrote: Le 31/10/2014 04:20, Roland Mas a écrit : Package: php-htmlpurifier Version: 4.6.0-1 Severity: serious Once reassigned this does not deserve to be serious any longer, see below; but this might actually need to be reassigned back. Indeed, the debian/maintscript involves relative symlinks. However, according to dpkg's changelog, such relative symlinks have only been supported since 1.17.14. It worked before: I just successfully upgraded php-htmlpurifier using dpkg 1.17.10. Looking closer at dpkg changelog, the regression seems to have been introduced in dpkg 1.17.13: * Fix dpkg-maintscript-helper symlink_to_dir to assure absolute pathnames arguments. It didn't work before, it just did not check for (and abort on) the bogus invocation. And then, fixed in dpkg 1.17.14: * Add support for relative symlinks to dpkg-maintscript-helper symlink_to_dir command. Suggested by Don Armstrong d...@debian.org. This was adding the actual support that had never been present before. So the php-htmlpurifier currently in testing can't be installed by the dpkg currently in testing. I guess a simple versioned dependency would fix that (alternatively, a rewrite of the maintscript to use absolute targets for the symlinks). I’d rather reassign this bug to dpkg 1.17.13 and close it with dpkg 1.17.14 (php-htmlpurifier is not the only package relying on symlink_to_dir. As documented on dpkg-maintscript-helper(1), the old-target must be provided, and such target are often relatives, as expected by the policy). In principle, packages that where using the unsupported interface, should do the actual conversion once installed with a new enough dpkg. But if those packages get upgraded first before dpkg, then they will be left w/o the conversion, so thinking about it, you might need to add a Pre-Depends on the dpkg version introducing that support, depending on the requirements of the conversion. Thanks, Guillem -- 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#767460: [pkg-php-pear] Bug#767460: php-htmlpurifier: Missing versioned dependency on dpkg
Processing control commands:
severity -1 wishlist
Bug #767460 {Done: David Prévot taf...@debian.org} [dpkg] php-htmlpurifier:
Missing versioned dependency on dpkg
Severity set to 'wishlist' from 'serious'
--
767460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767460
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
