Bug#774192: marked as done (movabletype-opensource: CVE-2014-9057)
Your message dated Tue, 30 Dec 2014 08:11:00 + with message-id 20141230081059.gm6...@urchin.earth.li and subject line Re: [pkg-mt-om-devel] Bug#774192: CVE-2014-9057 has caused the Debian Bug report #774192, regarding movabletype-opensource: CVE-2014-9057 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.) -- 774192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774192 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: movabletype-opensource Severity: grave Tags: security Hi, please see https://movabletype.org/news/2014/12/6.0.6.html Cheers, Moritz ---End Message--- ---BeginMessage--- On Tue, Dec 30, 2014 at 02:56:31AM +0100, Moritz Muehlenhoff wrote: Source: movabletype-opensource Severity: grave Tags: security Hi, please see https://movabletype.org/news/2014/12/6.0.6.html Hi, This doesn't affect Debian: Note this issue only affects Movable Type versions 6.0.6, 5.2.11 and 5.18. It does not affect versions 6.0.5, 5.2.10, 5.17 and prior versions. Cheers, Dominic.---End Message---
Bug#761170: upstream
Hi Ivo! Ivo De Decker iv...@debian.org writes: On Tue, Nov 25, 2014 at 10:38:44PM +0100, Lucas Nussbaum wrote: Note that the build now fails on i386 too. Trying to reproduce it locally, I run into yet another problem: 1) Failure: repo::iterator::fs_preserves_error [/tmp/libgit2-0.21.1/tests/repo/iterator.c:952] Expected function call to fail: git_iterator_advance(e, i) This problem is only occurs when running is root (the test chmods a file to 000 and checks if accessing it fails). It would probably be a good idea to add another test to check if the test is running as root, and fail in that case (because the tests assume they aren't). Interesting I didn't know that the user running the tests was the problem. Is that a problem with the buildd deployments? Or is it not a requirement that they all run as the same user? I guess what I'm really asking is if I add a test who will fix it when it fails? The failure that happens on the i386 buildd is this one: 1) Failure: clone::nonetwork::local_absolute_path [/«PKGBUILDDIR»/tests/clone/nonetwork.c:91] Function call failed: (git_clone(g_repo, local_src, ./foo, g_options)) error -1 - git_path_direach callback returned -1 I can reproduce this in my test environment on i386 and amd64. It only happens when the builddir and /tmp are on different filesystems. It seems the local clone tries to create a hard link, which fails across filesystems (the fact that this happens without fallback is an error in itself, so the test actually discovered a problem here). When setting the TMPDIR to a directory on the same filesystem, the test doesn't hit this issue, and the build works fine. It's unclear to me why this only happens on i386, but I suspect that the setup of the buildd chroots isn't the same everywhere. Yeah it struck me as odd. This same problem effects kfreebsd too so the change of the tmp dir will fix those builds as well. I'll have go at the running the clone nonetwork test with TMPDIR set to a mounted file system and report a bug upstream. In any case, adding this patch fixes it in my environment. I can do an NMU if necessary. Thanks heaps for the patch, I only yesterday did exactly the same thing. It's included in the yet to be uploaded 0.21.3-1 that will also address the recent CVE. 0. http://anonscm.debian.org/cgit/users/arrsim-guest/libgit2.git/commit/?id=bd3a1fc82c5af703fe061fb22022eb48fb89be50 -- Cheers, Russell -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773343: request-tracker4: fails to upgrade from 'wheezy' if rt4-extension-assettracker is installed
hi, On Sun, Dec 28, 2014 at 11:07 PM, Niko Tyni nt...@debian.org wrote: The attached patch implements this. It's also pushed in the ntyni/bug-773343 branch in the Alioth repository (see the Vcs-Git header.) Great! Thank you fixing it! I've tested 4.2.8-2 (built from your branch), and confirmed with pbuilder that: RT (wheezy) - 4.2.8-1 upgrade succeeds. RT + assettracker (wheezy) - 4.2.8-1 upgrade fails. RT (wheezy) - 4.2.8-2 upgrade succeeds. RT + assettracker (wheezy) - 4.2.8-2 upgrade succeeds. However, I have not actually tested to use RT after the patched upgrade. It would be nice if somebody could do that. I've also applied 4.2.8-2 to my local RT instance and had no problem using it, but from 4.2.8-1, so it's not be useful verification... regards, -- KURASHIKI Satoru -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773818: Crashes on start
Hello Adam Majer!
Stumbled across your bug report while browsing over release-critical ones...
I haven't even looked at the lpe source, but just from looking at the
hunk included as context in your patch it looks like the source
could really use some wider review then just targeted fixes.
On Tue, Dec 23, 2014 at 09:34:20AM -0600, Adam Majer wrote:
[...]
diff -u lpe-1.2.7/src/buffer.c lpe-1.2.7/src/buffer.c
--- lpe-1.2.7/src/buffer.c2014-06-23 22:53:33.582593198 -0500
+++ lpe-1.2.7/src/buffer.c2014-12-23 09:08:54.888625050 -0600
@@ -158,8 +158,8 @@
int (*accept) (buffer *);
Consider the case where strlen(ent-d_name) == basename_len.
if (strlen(ent-d_name) basename_len) {
This should probably use = .
The strlen() function calculates the length of the string s,
=excluding the terminating null byte ('\0').
-basename_len = strlen(ent-d_name) + 1;
-name = realloc(name, (basename-name) + basename_len);
+basename_len = strlen(ent-d_name);
+name = realloc(name, (basename-name) + basename_len + 1);
basename = name + basename_off;
}
strcpy (basename, ent-d_name);
The strcpy() function copies the string pointed to by src,
=including the terminating null byte ('\0'), ...
As mentioned, I haven't looked at the full source so I might very well
be missing something. As I understood it this is the second attempt at
fixing an issue here. Possibly a wider review of how to avoid
off-by-one in the entire source could be useful.
Regards,
Andreas Henriksson
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774194: marked as done (phpmyadmin: CVE-2014-9218 CVE-2014-9219)
Your message dated Tue, 30 Dec 2014 10:04:08 + with message-id e1y5teq-0003yi...@franck.debian.org and subject line Bug#774194: fixed in phpmyadmin 4:4.2.12-2 has caused the Debian Bug report #774194, regarding phpmyadmin: CVE-2014-9218 CVE-2014-9219 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.) -- 774194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: phpmyadmin Severity: grave Tags: security Please see: http://www.phpmyadmin.net/home_page/security/PMASA-2014-17.php http://www.phpmyadmin.net/home_page/security/PMASA-2014-18.php Cheers, Moritz ---End Message--- ---BeginMessage--- Source: phpmyadmin Source-Version: 4:4.2.12-2 We believe that the bug you reported is fixed in the latest version of phpmyadmin, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 774...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michal Čihař ni...@debian.org (supplier of updated phpmyadmin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 30 Dec 2014 10:54:32 +0100 Source: phpmyadmin Binary: phpmyadmin Architecture: source all Version: 4:4.2.12-2 Distribution: unstable Urgency: high Maintainer: Thijs Kinkhorst th...@debian.org Changed-By: Michal Čihař ni...@debian.org Description: phpmyadmin - MySQL web administration tool Closes: 774194 Changes: phpmyadmin (4:4.2.12-2) unstable; urgency=high . * Fix security issues (Closes: #774194). - CVE-2014-9219 / PMASA-2014-18 - XSS vulnerability in redirection. - CVE-2014-9218 / PMASA-2014-17 - DoS vulnerability with long passwords. Checksums-Sha1: 3b872c10a4dc8056889220fe9c30326b132fce5a 1925 phpmyadmin_4.2.12-2.dsc 5050d7290502f9c791f26b4a05c525deb6270a96 49620 phpmyadmin_4.2.12-2.debian.tar.xz cbb594076beccf3d25df6ff7a86f1d7d1531985c 3862078 phpmyadmin_4.2.12-2_all.deb Checksums-Sha256: 24a81f2ef2335656e58ca0ce1f0fcb9ac7d4a9bd8c409c378dc2d8a7f1822c82 1925 phpmyadmin_4.2.12-2.dsc 5230ca896a77f81fa9dfa80d1f1c8adee71bb83d913fd6998090b61c16171c5b 49620 phpmyadmin_4.2.12-2.debian.tar.xz 45f2eb8227a292da9514ba1298ab4a63c65136a3ad11f3c6b6daf958770d44ff 3862078 phpmyadmin_4.2.12-2_all.deb Files: 1f69aaa1dba26087394527de0094dbde 1925 web extra phpmyadmin_4.2.12-2.dsc 1a1b891a54b9d3eee5b0140c56723804 49620 web extra phpmyadmin_4.2.12-2.debian.tar.xz 33ce87def73a5b1418690d42e9882c02 3862078 web extra phpmyadmin_4.2.12-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUonb4AAoJEJwnsxNCt1Edd9wP/iaELM5PyB16GTZ1A1ZlxE0I WMyE/L1nCE+aFb3nR6bSPusMAG/AiXS34qjF9h8DoNkcSVEgUKrmTRP4YlIz6D/E u3Ye+hLRVdbharoJPMUYhrhGAT2n8lOc3cVCKD9lGhph9M7s4aySCmTNJsg1s4Yo JoOe4E1UjQVfcYpMm8GNb2psHb56ZzcozILI8FkGartDKHhBZaNyXxKwTlP1dIv9 0QtY/5aNtOBc1fD/HkUpMar9qp6Ky6TEVbPhuj4d2yt/5nm6I3eYesiUwdtcca8O zt1wqI9vgVd46WQmUW+MkxeJkqLgaXEjh7i9a0xBdhHClKJdHY7VrN2YOmavCAZ1 MMg3UeI7Uz8bC+aTdIDgsIHnnkMixt33zH2ximVOaX2idsxwVGsUNNIb/7JTXtTZ v9UMORXjpF9dLRnsEzksoRml1T4/hLIOrIsDWLK4tT75/Ja1/judFNt6W5CadrP3 e9z0HJKu6/G9k+SpovSNvqFXyXHTe/cmJoLzsYAsIPxwKmcieDbvvaWPhhjMZAul UAVEaUIWRBZn1OL2iAIky+ghXMBJsxyvfvi5ORKIxsBuy4ULU/VbDVriOgb/iwQ2 UO2yLDJyCWZUn6f7j0BC7gdlAO63uKHo97ufl2Kx7Rc8EVA9uj1H54BWjb5xfLCw USa215rKZqjpzz9cLJv+ =xUx8 -END PGP SIGNATUREEnd Message---
Processed (with 1 errors): merge 738119 774121
Processing commands for cont...@bugs.debian.org: tags 774121 help fixed-upstream Bug #774121 [android-tools-adb] adb sideload fails with TWRP 2.8.2.0 Added tag(s) help and fixed-upstream. tags 738119 help fixed-upstream Bug #738119 [src:android-tools] android-tools: new upstream version 4.4.2 is available Added tag(s) help and fixed-upstream. merge 738119 774121 Bug #738119 [src:android-tools] android-tools: new upstream version 4.4.2 is available Unable to merge bugs because: severity of #774121 is 'serious' not 'normal' package of #774121 is 'android-tools-adb' not 'src:android-tools' Failed to merge 738119: Did not alter merged bugs End of message, stopping processing here. Please contact me if you need assistance. -- 738119: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738119 774121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774121 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#771863: [ovs-dev] Bug#771863: [PKG-Openstack-devel] Bug#771863: Bug#771863: Service does not start or parse interfaces correctly
Il 23/12/2014 16:27, Gurucharan Shetty ha scritto:
I tried 2.3.0+git20140819-3 building it in wheezy with kernel 3.16 from
backports but bridge of my test was still not working:
auto xenbr0
allow-ovs xenbr0
iface xenbr0 inet static
address 192.168.1.90
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.200
ovs_type OVSBridge
ovs_ports eth0
auto eth0
You should not be using 'auto' above. eth0 is a port of an OVS bridge
and it should be configured after 'xenbr0' is configured.
allow-xenbr0 eth0
iface eth0 inet manual
ovs_bridge xenbr0
ovs_type OVSPort
auto xenbr1
allow-ovs xenbr1
iface xenbr1 inet static
address 192.168.45.91
netmask 255.255.255.0
network 192.168.45.0
broadcast 192.168.45.255
ovs_type OVSBridge
ovs_ports vlan100
allow-xenbr1 vlan100
iface vlan100 inet manual
ovs_bridge xenbr1
ovs_type OVSIntPort
ovs_options tag=100
ovs_extra set interface ${IFACE} external-ids:iface-id=$(hostname
-s)
Without applying the below mentioned patch, does your problem go away
if you remove all the 'auto' for xenbr0 and xenbr1 also?
Thanks for your reply.
I removed all auto and now works also without backports other patches.
Then ovs networks starts automatically on boot also without auto, is
it correct?
For have it working I had to do service networking restart.
I found probably final solution applying also this patch:
http://git.openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=commitdiff;h=9a8b5cc1a3d941c0e33f3f5b5ac260a35a8130af
The above patch adds the ability to configure OVS with 'auto'
configured and additionally has the following information:
Notes on dependencies:
-
openvswitch-switch depends on $network, $named $remote_fs and $syslog to start.
This creates some startup dependency issues.
* Since openvswitch utilities are placed in /usr and /usr can be mounted
through NFS, openvswitch has to start after it. But if a user uses openvswitch
for all his networking needs and hence to mount NFS, there will be a deadlock.
So, if /usr is mounted through NFS and openvswitch is used for all networking,
the administrator should figure out a way to mount NFS before starting OVS.
One way to do this is in initramfs.
* Since openvswitch starts after $network, $remote_fs and $syslog, any startup
script that depends on openvswitch but starts before it, needs to be changed
to depend on openvswitch-switch too.
* Ideally, an admin should not add openvswitch bridges in the 'auto'
section of the 'interfaces' file. This is because, when ifupdown starts
working on bridges listed in 'auto', openvswitch has not yet started.
But, if the admin wants to go down this route and adds openvswitch bridges
in the 'auto' section, openvswitch-switch will forcefully be started when
ifupdown kicks in. In a case like this, the admin needs to make sure that /usr
has already been mounted and that a remote $syslog (if used) is ready to
receive openvswitch logs.
Even if seems not good in some cases.
Does the above explanation give any hints on why it wouldn't work in some cases?
Yes
I don't know if also Jessie have this problem but probably yes. If yes I
think this bug is only partially solves with 2.3.0+git20140819-3.
I had also another start problem probably not related to this, after some
hours xenbr0 stopped to working.
I not found any useful errors about in logs, only some strange thing, in
ifconfig xenbr0 was without the static ip, in syslog keep tried to acquire
configuration with dhcp failing (dhcp server present and working in lan).
After service networking restart was working again but I not understand
was happen and why :(
Someone have any idea about?
Thanks for any reply and sorry for my bad english.
___
dev mailing list
d...@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773916: libical: Ship different constant values accross builds
Dimitri John Ledkov: If I fail to upload this, please upload it instead of me. Looks like the upload went ok. I am now able to rebuild libical reproducibly. :) Please remember to coordinate with the release team for binNUMs and unblocks. -- Lunar.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Bug#774213: zope2.13: import zope.security._proxy - SystemError: dynamic module not initialized properly
Package: zope2.13 Version: 2.13.22-1 Severity: grave Justification: renders package unusable Dear Maintainer, With zope2.13 I've tried to create a (user) instance and start it, but a `SystemError: dynamic module not initialized properly` is raised while zopectl tries to import zope.security._proxy . The bug could be demonstrated in essence this way: $ /usr/lib/zope2.13/bin/python import zope.security._proxy Traceback (most recent call last): File console, line 1, in module File /usr/lib/zope2.13/lib/python/zope.security-3.7.4.egg/zope/security/__init__.py, line 19, in module from zope.security.management import checkPermission File /usr/lib/zope2.13/lib/python/zope.security-3.7.4.egg/zope/security/management.py, line 23, in module from zope.security.checker import CheckerPublic File /usr/lib/zope2.13/lib/python/zope.security-3.7.4.egg/zope/security/checker.py, line 46, in module from zope.security._proxy import _Proxy as Proxy, getChecker SystemError: dynamic module not initialized properly Full log demonstrating the problem is attached. Thanks, Kirill 8 $ whoami kirr# non-root $ pwd /home/kirr $ rm -rf zope # make sure there are no user instances $ dzhandle -z2.13 make-instance -m all ktest -u user:passwd $ dzhandle -z2.13 list-instances ktest2.13 addon-mode=all addon-technique=tree-linked userfile=inituser purged $ ls zope/instance/zope2.13/ ktest $ dzhandle -z2.13 zopectl ktest start Traceback (most recent call last): File /usr/lib/zope2.13/bin/python, line 78, in module execfile(__file__) File /usr/lib/zope2.13/bin/zopectl, line 6, in module Zope2.Startup.zopectl.run() File /usr/lib/zope2.13/lib/python/Zope2-2.13.22.egg/Zope2/Startup/zopectl.py, line 484, in run exitstatus = main() File /usr/lib/zope2.13/lib/python/Zope2-2.13.22.egg/Zope2/Startup/zopectl.py, line 440, in main options.realize(args) File /usr/lib/zope2.13/lib/python/Zope2-2.13.22.egg/Zope2/Startup/zopectl.py, line 158, in realize ZDOptions.realize(self, *args, **kw) File /usr/lib/zope2.13/lib/python/zdaemon-2.0.7.egg/zdaemon/zdoptions.py, line 290, in realize self.load_schema() File /usr/lib/zope2.13/lib/python/zdaemon-2.0.7.egg/zdaemon/zdoptions.py, line 338, in load_schema self.schema = ZConfig.loadSchema(self.schemafile) File /usr/lib/zope2.13/lib/python/ZConfig-2.9.1.egg/ZConfig/loader.py, line 33, in loadSchema return SchemaLoader().loadURL(url) File /usr/lib/zope2.13/lib/python/ZConfig-2.9.1.egg/ZConfig/loader.py, line 67, in loadURL return self.loadResource(r) File /usr/lib/zope2.13/lib/python/ZConfig-2.9.1.egg/ZConfig/loader.py, line 195, in loadResource schema = ZConfig.schema.parseResource(resource, self) File /usr/lib/zope2.13/lib/python/ZConfig-2.9.1.egg/ZConfig/schema.py, line 27, in parseResource xml.sax.parse(resource.file, parser) File /usr/lib/python2.7/xml/sax/__init__.py, line 33, in parse parser.parse(source) File /usr/lib/python2.7/xml/sax/expatreader.py, line 107, in parse xmlreader.IncrementalParser.parse(self, source) File /usr/lib/python2.7/xml/sax/xmlreader.py, line 123, in parse self.feed(buffer) File /usr/lib/python2.7/xml/sax/expatreader.py, line 210, in feed self._parser.Parse(data, isFinal) File /usr/lib/python2.7/xml/sax/expatreader.py, line 304, in start_element self._cont_handler.startElement(name, AttributesImpl(attrs)) File /usr/lib/zope2.13/lib/python/ZConfig-2.9.1.egg/ZConfig/schema.py, line 103, in startElement getattr(self, start_ + name)(attrs) File /usr/lib/zope2.13/lib/python/ZConfig-2.9.1.egg/ZConfig/schema.py, line 306, in start_import src = self._loader.schemaComponentSource(pkg, file) File /usr/lib/zope2.13/lib/python/ZConfig-2.9.1.egg/ZConfig/loader.py, line 212, in schemaComponentSource __import__(package) File /usr/lib/zope2.13/lib/python/Zope2-2.13.22.egg/ZServer/__init__.py, line 41, in module from HTTPServer import zhttp_server, zhttp_handler File /usr/lib/zope2.13/lib/python/Zope2-2.13.22.egg/ZServer/HTTPServer.py, line 44, in module from HTTPResponse import make_response File /usr/lib/zope2.13/lib/python/Zope2-2.13.22.egg/ZServer/HTTPResponse.py, line 29, in module from ZPublisher.HTTPResponse import HTTPResponse # XXX WTF? File /usr/lib/zope2.13/lib/python/Zope2-2.13.22.egg/ZPublisher/__init__.py, line 20, in module from zExceptions import NotFound, BadRequest, InternalError, Forbidden File /usr/lib/zope2.13/lib/python/zExceptions-2.13.0.egg/zExceptions/__init__.py, line 24, in module from zope.publisher.interfaces import INotFound File /usr/lib/zope2.13/lib/python/zope.publisher-3.12.6.egg/zope/publisher/interfaces/__init__.py, line 26, in module from zope.security.interfaces import IParticipation File
Processed: Re: Bug#715416: python-urlgrabber: Fails to download from https
Processing control commands: severity -1 serious Bug #715416 [python-urlgrabber] python-urlgrabber: Fails to download from https Bug #722191 [python-urlgrabber] yum: CURLOPT_SSL_VERIFYHOST no longer supports 1 as value! Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' -- 715416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715416 722191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722191 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#722191: marked as done (yum: CURLOPT_SSL_VERIFYHOST no longer supports 1 as value!)
Your message dated Tue, 30 Dec 2014 12:34:09 + with message-id e1y5w01-9o...@franck.debian.org and subject line Bug#722191: fixed in urlgrabber 3.9.1-4.1 has caused the Debian Bug report #722191, regarding yum: CURLOPT_SSL_VERIFYHOST no longer supports 1 as value! 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.) -- 722191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: yum Version: 3.4.3-2 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** I was experimenting with building fedora chroots and under certain circumstances yum exits with: File /usr/lib/pymodules/python2.7/urlgrabber/grabber.py, line 1193, in _set_opts self.curl_obj.setopt(pycurl.SSL_VERIFYHOST, opts.ssl_verify_host) pycurl.error: (43, 'CURLOPT_SSL_VERIFYHOST no longer supports 1 as value!') I was using the command: yum --releasever=19 --nogpg -c rootfs/etc/yum.repos.d/fedora.repo --disableplugin='*' --disablerepo='*' --enablerepo=fedora --installroot /tmp/rootfs/ install bash vim-minimal procps-ng yum passwd fedora-release systemd I'll attach the fedora.repo file I was using. I found this forum post which claims that CURLOPT_SSL_VERIFYHOST needs to be 2. http://devot-ee.com/add-ons/support/simple-s3-uploader/viewthread/9731 I had a simple patch which got around the issue for me. In addition to the packages picked up by report bug I think the following are also relevant: python-pycurl 7.19.0-7 libcurl3-gnutls: 7.32.0-1 Diane Trout -- System Information: Debian Release: jessie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (110, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages yum depends on: ii python 2.7.5-4 ii python-libxml2 2.9.1+dfsg1-3 ii python-rpm 4.11.1-2 ii python-sqlite1.0.1-9 ii python-sqlitecachec 1.1.4-1 ii python-urlgrabber3.9.1-4 ii rpm 4.11.1-2 yum recommends no packages. yum suggests no packages. -- no debconf information --- /tmp/yumRepo.py 2013-09-08 14:17:43.692054028 -0700 +++ /usr/lib/python2.7/dist-packages/yum/yumRepo.py 2013-06-26 22:07:25.0 -0700 @@ -504,9 +504,9 @@ 'proxies': self.proxy_dict, 'timeout': self.timeout, 'http_headers': tuple(self.__headersListFromDict(cache=cache)), 'ssl_verify_peer': self.sslverify, - 'ssl_verify_host': 2 if self.sslverify else 0, + 'ssl_verify_host': self.sslverify, 'ssl_ca_cert': self.sslcacert, 'ssl_cert': self.sslclientcert, 'ssl_key': self.sslclientkey, 'user_agent': default_grabber.opts.user_agent, [fedora] name=Fedora $releasever - $basearch failovermethod=priority #baseurl=http://download.fedoraproject.org/pub/fedora/linux/releases/$releasever/Everything/$basearch/os/ mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releaseverarch=$basearch enabled=1 #metadata_expire=7d gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch [fedora-debuginfo] name=Fedora $releasever - $basearch - Debug failovermethod=priority #baseurl=http://download.fedoraproject.org/pub/fedora/linux/releases/$releasever/Everything/$basearch/debug/ mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-debug-$releaseverarch=$basearch enabled=0 metadata_expire=7d gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch [fedora-source] name=Fedora $releasever - Source failovermethod=priority #baseurl=http://download.fedoraproject.org/pub/fedora/linux/releases/$releasever/Everything/source/SRPMS/ mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-source-$releaseverarch=$basearch enabled=0 metadata_expire=7d gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch ---End Message--- ---BeginMessage--- Source: urlgrabber Source-Version: 3.9.1-4.1 We believe that the bug you reported is fixed in the latest
Bug#715416: marked as done (python-urlgrabber: Fails to download from https)
Your message dated Tue, 30 Dec 2014 12:34:09 +
with message-id e1y5w01-9o...@franck.debian.org
and subject line Bug#722191: fixed in urlgrabber 3.9.1-4.1
has caused the Debian Bug report #722191,
regarding python-urlgrabber: Fails to download from https
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.)
--
722191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-urlgrabber
Version: 3.9.1-4
Severity: normal
Dear Maintainer,
python-urlgrabber fails to download from any https
urlgrabber https://www.google.com
Traceback (most recent call last):
File /usr/bin/urlgrabber, line 329, in module
ugc.run()
File /usr/bin/urlgrabber, line 293, in run
f = self.g.urlgrab(url, self.op.outputfile)
File /usr/lib/pymodules/python2.7/urlgrabber/grabber.py, line 982, in
urlgrab
return self._retry(opts, retryfunc, url, filename)
File /usr/lib/pymodules/python2.7/urlgrabber/grabber.py, line 886, in _retry
r = apply(func, (opts,) + args, {})
File /usr/lib/pymodules/python2.7/urlgrabber/grabber.py, line 968, in
retryfunc
fo = PyCurlFileObject(url, filename, opts)
File /usr/lib/pymodules/python2.7/urlgrabber/grabber.py, line 1063, in
__init__
self._do_open()
File /usr/lib/pymodules/python2.7/urlgrabber/grabber.py, line 1350, in
_do_open
self._set_opts()
File /usr/lib/pymodules/python2.7/urlgrabber/grabber.py, line 1193, in
_set_opts
self.curl_obj.setopt(pycurl.SSL_VERIFYHOST, opts.ssl_verify_host)
pycurl.error: (43, 'CURLOPT_SSL_VERIFYHOST no longer supports 1 as value!')
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.9-1-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 python-urlgrabber depends on:
ii python 2.7.5-2
ii python-pycurl 7.19.0-7
ii python-support 1.0.15
python-urlgrabber recommends no packages.
python-urlgrabber suggests no packages.
-- no debconf information
---End Message---
---BeginMessage---
Source: urlgrabber
Source-Version: 3.9.1-4.1
We believe that the bug you reported is fixed in the latest version of
urlgrabber, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 722...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de (supplier of updated
urlgrabber package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 30 Dec 2014 13:13:08 +0100
Source: urlgrabber
Binary: python-urlgrabber
Architecture: source all
Version: 3.9.1-4.1
Distribution: unstable
Urgency: medium
Maintainer: Kevin Coyner kcoy...@debian.org
Changed-By: John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de
Description:
python-urlgrabber - A high-level cross-protocol url-grabber
Closes: 715416 722191
Changes:
urlgrabber (3.9.1-4.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Add debian/patches/https-verifyhost-fix.diff taken from upstream
to fix https connection issues (Closes: #715416, #722191).
Checksums-Sha1:
3798d1ee0a98e51b467910e56e1a1c8e39dbe54b 2069 urlgrabber_3.9.1-4.1.dsc
937c7ad3177539c337d4010e0175b2c7bd874938 72343 urlgrabber_3.9.1.orig.tar.gz
3940e32bf6e0a49791b0c3be0aef3d2dafaf3905 10620
urlgrabber_3.9.1-4.1.debian.tar.xz
5d6a88b3dafb8a1d322756c8389d6852b5c66ae1 45930
python-urlgrabber_3.9.1-4.1_all.deb
Checksums-Sha256:
840a162400d46a31dfce001d3d6560dcfc0b025743e4373c27c85e62ada3046a 2069
urlgrabber_3.9.1-4.1.dsc
4437076c8708e5754ea04540e46c7f4f233734ee3590bb8a96389264fb0650d0 72343
urlgrabber_3.9.1.orig.tar.gz
849b922c792c1daf0d084a9b107387b39dbb769f4bfd75628c0e021611560162 10620
urlgrabber_3.9.1-4.1.debian.tar.xz
7d21f843ad6a7d91e2c9f9aa2b38bd75ab1a8568055add6eee3bf970dc846724 45930
python-urlgrabber_3.9.1-4.1_all.deb
Files:
f9bd663541b5eb5cf5947f757fe76151 2069 python optional urlgrabber_3.9.1-4.1.dsc
00c8359bf71062d0946bacea521f80b4 72343 python optional
urlgrabber_3.9.1.orig.tar.gz
Bug#722191: marked as done (yum: CURLOPT_SSL_VERIFYHOST no longer supports 1 as value!)
Your message dated Tue, 30 Dec 2014 12:34:09 + with message-id e1y5w01-9i...@franck.debian.org and subject line Bug#715416: fixed in urlgrabber 3.9.1-4.1 has caused the Debian Bug report #715416, regarding yum: CURLOPT_SSL_VERIFYHOST no longer supports 1 as value! 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.) -- 715416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: yum Version: 3.4.3-2 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** I was experimenting with building fedora chroots and under certain circumstances yum exits with: File /usr/lib/pymodules/python2.7/urlgrabber/grabber.py, line 1193, in _set_opts self.curl_obj.setopt(pycurl.SSL_VERIFYHOST, opts.ssl_verify_host) pycurl.error: (43, 'CURLOPT_SSL_VERIFYHOST no longer supports 1 as value!') I was using the command: yum --releasever=19 --nogpg -c rootfs/etc/yum.repos.d/fedora.repo --disableplugin='*' --disablerepo='*' --enablerepo=fedora --installroot /tmp/rootfs/ install bash vim-minimal procps-ng yum passwd fedora-release systemd I'll attach the fedora.repo file I was using. I found this forum post which claims that CURLOPT_SSL_VERIFYHOST needs to be 2. http://devot-ee.com/add-ons/support/simple-s3-uploader/viewthread/9731 I had a simple patch which got around the issue for me. In addition to the packages picked up by report bug I think the following are also relevant: python-pycurl 7.19.0-7 libcurl3-gnutls: 7.32.0-1 Diane Trout -- System Information: Debian Release: jessie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (110, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages yum depends on: ii python 2.7.5-4 ii python-libxml2 2.9.1+dfsg1-3 ii python-rpm 4.11.1-2 ii python-sqlite1.0.1-9 ii python-sqlitecachec 1.1.4-1 ii python-urlgrabber3.9.1-4 ii rpm 4.11.1-2 yum recommends no packages. yum suggests no packages. -- no debconf information --- /tmp/yumRepo.py 2013-09-08 14:17:43.692054028 -0700 +++ /usr/lib/python2.7/dist-packages/yum/yumRepo.py 2013-06-26 22:07:25.0 -0700 @@ -504,9 +504,9 @@ 'proxies': self.proxy_dict, 'timeout': self.timeout, 'http_headers': tuple(self.__headersListFromDict(cache=cache)), 'ssl_verify_peer': self.sslverify, - 'ssl_verify_host': 2 if self.sslverify else 0, + 'ssl_verify_host': self.sslverify, 'ssl_ca_cert': self.sslcacert, 'ssl_cert': self.sslclientcert, 'ssl_key': self.sslclientkey, 'user_agent': default_grabber.opts.user_agent, [fedora] name=Fedora $releasever - $basearch failovermethod=priority #baseurl=http://download.fedoraproject.org/pub/fedora/linux/releases/$releasever/Everything/$basearch/os/ mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releaseverarch=$basearch enabled=1 #metadata_expire=7d gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch [fedora-debuginfo] name=Fedora $releasever - $basearch - Debug failovermethod=priority #baseurl=http://download.fedoraproject.org/pub/fedora/linux/releases/$releasever/Everything/$basearch/debug/ mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-debug-$releaseverarch=$basearch enabled=0 metadata_expire=7d gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch [fedora-source] name=Fedora $releasever - Source failovermethod=priority #baseurl=http://download.fedoraproject.org/pub/fedora/linux/releases/$releasever/Everything/source/SRPMS/ mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-source-$releaseverarch=$basearch enabled=0 metadata_expire=7d gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch ---End Message--- ---BeginMessage--- Source: urlgrabber Source-Version: 3.9.1-4.1 We believe that the bug you reported is fixed in the latest
Bug#715416: marked as done (python-urlgrabber: Fails to download from https)
Your message dated Tue, 30 Dec 2014 12:34:09 +
with message-id e1y5w01-9i...@franck.debian.org
and subject line Bug#715416: fixed in urlgrabber 3.9.1-4.1
has caused the Debian Bug report #715416,
regarding python-urlgrabber: Fails to download from https
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.)
--
715416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715416
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-urlgrabber
Version: 3.9.1-4
Severity: normal
Dear Maintainer,
python-urlgrabber fails to download from any https
urlgrabber https://www.google.com
Traceback (most recent call last):
File /usr/bin/urlgrabber, line 329, in module
ugc.run()
File /usr/bin/urlgrabber, line 293, in run
f = self.g.urlgrab(url, self.op.outputfile)
File /usr/lib/pymodules/python2.7/urlgrabber/grabber.py, line 982, in
urlgrab
return self._retry(opts, retryfunc, url, filename)
File /usr/lib/pymodules/python2.7/urlgrabber/grabber.py, line 886, in _retry
r = apply(func, (opts,) + args, {})
File /usr/lib/pymodules/python2.7/urlgrabber/grabber.py, line 968, in
retryfunc
fo = PyCurlFileObject(url, filename, opts)
File /usr/lib/pymodules/python2.7/urlgrabber/grabber.py, line 1063, in
__init__
self._do_open()
File /usr/lib/pymodules/python2.7/urlgrabber/grabber.py, line 1350, in
_do_open
self._set_opts()
File /usr/lib/pymodules/python2.7/urlgrabber/grabber.py, line 1193, in
_set_opts
self.curl_obj.setopt(pycurl.SSL_VERIFYHOST, opts.ssl_verify_host)
pycurl.error: (43, 'CURLOPT_SSL_VERIFYHOST no longer supports 1 as value!')
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.9-1-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 python-urlgrabber depends on:
ii python 2.7.5-2
ii python-pycurl 7.19.0-7
ii python-support 1.0.15
python-urlgrabber recommends no packages.
python-urlgrabber suggests no packages.
-- no debconf information
---End Message---
---BeginMessage---
Source: urlgrabber
Source-Version: 3.9.1-4.1
We believe that the bug you reported is fixed in the latest version of
urlgrabber, 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 715...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de (supplier of updated
urlgrabber package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 30 Dec 2014 13:13:08 +0100
Source: urlgrabber
Binary: python-urlgrabber
Architecture: source all
Version: 3.9.1-4.1
Distribution: unstable
Urgency: medium
Maintainer: Kevin Coyner kcoy...@debian.org
Changed-By: John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de
Description:
python-urlgrabber - A high-level cross-protocol url-grabber
Closes: 715416 722191
Changes:
urlgrabber (3.9.1-4.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Add debian/patches/https-verifyhost-fix.diff taken from upstream
to fix https connection issues (Closes: #715416, #722191).
Checksums-Sha1:
3798d1ee0a98e51b467910e56e1a1c8e39dbe54b 2069 urlgrabber_3.9.1-4.1.dsc
937c7ad3177539c337d4010e0175b2c7bd874938 72343 urlgrabber_3.9.1.orig.tar.gz
3940e32bf6e0a49791b0c3be0aef3d2dafaf3905 10620
urlgrabber_3.9.1-4.1.debian.tar.xz
5d6a88b3dafb8a1d322756c8389d6852b5c66ae1 45930
python-urlgrabber_3.9.1-4.1_all.deb
Checksums-Sha256:
840a162400d46a31dfce001d3d6560dcfc0b025743e4373c27c85e62ada3046a 2069
urlgrabber_3.9.1-4.1.dsc
4437076c8708e5754ea04540e46c7f4f233734ee3590bb8a96389264fb0650d0 72343
urlgrabber_3.9.1.orig.tar.gz
849b922c792c1daf0d084a9b107387b39dbb769f4bfd75628c0e021611560162 10620
urlgrabber_3.9.1-4.1.debian.tar.xz
7d21f843ad6a7d91e2c9f9aa2b38bd75ab1a8568055add6eee3bf970dc846724 45930
python-urlgrabber_3.9.1-4.1_all.deb
Files:
f9bd663541b5eb5cf5947f757fe76151 2069 python optional urlgrabber_3.9.1-4.1.dsc
00c8359bf71062d0946bacea521f80b4 72343 python optional
urlgrabber_3.9.1.orig.tar.gz
Bug#774217: yum: Missing dependency on python-lzma
Package: yum Version: 3.4.3-2 Severity: serious Justification: renders package unusable Hello! yum is missing the dependency on the python-lzma package which is needed to decompress the repository files used in newer Fedora repositories. root@z6:~ yum repolist all rawhide/metalink | 22 kB 00:00 rawhide | 4.2 kB 00:00 rawhide/primary_db | 18 MB 00:00 Error: xz compression not available Manually installing python-lzma fixes the problem. So this should be fixable by just adding python-lzma to the list of dependencies for the yum package. root@z6:~ apt-get install python-lzma Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: python-lzma 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. Need to get 75.1 kB of archives. After this operation, 153 kB of additional disk space will be used. Get:1 http://ftp.debian.org/debian/ unstable/main python-lzma amd64 0.5.3-2+b1 [75.1 kB] Fetched 75.1 kB in 0s (744 kB/s) Selecting previously unselected package python-lzma. (Reading database ... 432421 files and directories currently installed.) Preparing to unpack .../python-lzma_0.5.3-2+b1_amd64.deb ... Unpacking python-lzma (0.5.3-2+b1) ... Setting up python-lzma (0.5.3-2+b1) ... Processing triggers for python-support (1.0.15) ... root@z6:~ yum repolist all updates-testing/metalink | 22 kB 00:00 updates-testing | 4.9 kB 00:00 updates-testing/primary_db | 1.0 MB 00:00 repo id repo name status rawhide Fedora enabled: 43,648 updates-testing Fedora 21 - x86_64 - Test Updates enabled: 1,817 repolist: 45,465 root@z6:~ I am raising the severity of this bug to 'serious' since I think it is important to have this bug fixed for Jessie so that we are shipping a working version of yum in the release. yum is particularly interesting for Jessie as we have systemd-nspawn available which allows one to boot into a Fedora change root with minimal efforts. I would be happy to NMU in any case. Adrian -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing'), (99, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages yum depends on: ii python 2.7.8-2 ii python-libxml2 2.9.1+dfsg1-4 ii python-rpm 4.11.3-1.1 ii python-sqlite1.0.1-11 ii python-sqlitecachec 1.1.4-1 ii python-urlgrabber3.9.1-4 ii rpm 4.11.3-1.1 yum recommends no packages. yum 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#769941: Not because of gstreamer
I often start iceweasel as another user (with sux) and when I load gmail I have this error too: ** (iceweasel:17775): CRITICAL **: gst_app_src_set_size: assertion 'GST_IS_APP_SRC (appsrc)' failed However, iceweasel does not crash. So I think the crash has nothing to do with the assertion failed. I use libgstreamer-plugins-base1.0-0 1.4.4-2 (current unstable). -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773806: [pkg-db-devel] Bug#773806: libdb5.3-java: Pre-installation script fails
Control: severity -1 important
Control: tags -1 + moreinfo
Hi Ulrich,
I can't reproduce the bug and by reading dpkg-maintscript-helper I think
you are mistaken in your diagnosis.
It's the $SYMLINK and not the $SYMLINK_TARGET that has to be absolute
target, see the code.
But it looks like the support for relative symlinks were added in
1.17.14:
dpkg (1.17.14) unstable; urgency=low
[...]
* Add support for relative symlinks to dpkg-maintscript-helper
symlink_to_dir
command. Suggested by Don Armstrong d...@debian.org.
and the ${misc:Pre-Depends} was fixed in 1.17.22:
dpkg (1.17.22) unstable; urgency=low
[...]
* Bump minimal version for dir_to_symlink and symlink_to_dir commands
to 1.17.14 in dpkg-maintscript-helper(1) man page. Closes: #769843
So libdb5.3-java just needs binNMU with dpkg 1.17.22.
Cheers,
Ondrej
On Tue, Dec 23, 2014, at 14:45, Ulrich Klauer wrote:
Package: libdb5.3-java
Version: 5.3.28-7~deb8u1
Severity: grave
Justification: prevents package from being installed/upgraded
Unfortunately, there is another[1] bug in libdb5.3-java.maintscript which
means that the package still can't be installed or, if an earlier version
is present, can't be upgraded. The error message is:
dpkg-maintscript-helper: error: original symlink target is not an absolute
path
So, the target argument to symlink_to_dir must be an absolute path, i.e.
/usr/share/doc/libdb5.3 instead of just libdb5.3. See [2] for an
explanation of why this was changed in dpkg 1.17.13.
Ulrich
[1] http://bugs.debian.org/771877
[2] http://bugs.debian.org/758778
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (990, 'testing'), (800, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-2-amd64 (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 libdb5.3-java depends on:
ii dpkg 1.17.13
ii libdb5.3-java-jni 5.3.28-7~deb8u1
libdb5.3-java recommends no packages.
Versions of packages libdb5.3-java suggests:
pn libdb5.3-java-gcj none
-- no debconf information
___
pkg-db-devel mailing list
pkg-db-de...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-db-devel
--
Ondřej Surý ond...@sury.org
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [pkg-db-devel] Bug#773806: libdb5.3-java: Pre-installation script fails
Processing control commands: severity -1 important Bug #773806 [libdb5.3-java] libdb5.3-java: Pre-installation script fails Severity set to 'important' from 'grave' tags -1 + moreinfo Bug #773806 [libdb5.3-java] libdb5.3-java: Pre-installation script fails Added tag(s) moreinfo. -- 773806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773806 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: dante-client: socksify preloads libdl.so.2 from an incorrect path
Processing control commands: severity -1 grave Bug #656096 [dante-client] dante-client: socksify preloads libdl.so.2 from an incorrect path Severity set to 'grave' from 'normal' -- 656096: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 754218 to ifupdown, closing 754218, forcibly merging 771943 754218
Processing commands for cont...@bugs.debian.org:
reassign 754218 ifupdown
Bug #754218 [systemd] boot hangs forever on LSB job raise network interfaces
Bug reassigned from package 'systemd' to 'ifupdown'.
No longer marked as found in versions systemd/215-7 and systemd/204-14.
Ignoring request to alter fixed versions of bug #754218 to the same values
previously set
close 754218
Bug #754218 [ifupdown] boot hangs forever on LSB job raise network interfaces
Marked Bug as done
forcemerge 771943 754218
Bug #771943 {Done: Andrew Shadura andre...@debian.org} [ifupdown] ifupdown:
boot hangs, interface won't raise
Bug #773832 {Done: Andrew Shadura andre...@debian.org} [ifupdown] systemd:
LSB job raise network interfaces hangs with allow-hotplug and no cable
Bug #754218 {Done: Martin Pitt martin.p...@ubuntu.com} [ifupdown] boot hangs
forever on LSB job raise network interfaces
Severity set to 'serious' from 'important'
Marked as fixed in versions ifupdown/0.7.51.
Marked as found in versions ifupdown/0.7.50.
Bug #773832 {Done: Andrew Shadura andre...@debian.org} [ifupdown] systemd:
LSB job raise network interfaces hangs with allow-hotplug and no cable
Merged 754218 771943 773832
thanks
Stopping processing here.
Please contact me if you need assistance.
--
754218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754218
771943: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771943
773832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773832
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 (with 1 errors): merge 738119 774121
Processing commands for cont...@bugs.debian.org: forcemerge 738119 774121 Bug #738119 [src:android-tools] android-tools: new upstream version 4.4.2 is available Unable to merge bugs because: package of #774121 is 'android-tools-adb' not 'src:android-tools' Failed to forcibly merge 738119: Did not alter merged bugs thanks Stopping processing here. Please contact me if you need assistance. -- 738119: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738119 774121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774121 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: merge 738119 774121
Processing commands for cont...@bugs.debian.org: reassign 774121 src:android-tools Bug #774121 [android-tools-adb] adb sideload fails with TWRP 2.8.2.0 Bug reassigned from package 'android-tools-adb' to 'src:android-tools'. No longer marked as found in versions android-tools/4.2.2+git20130529-5.1. Ignoring request to alter fixed versions of bug #774121 to the same values previously set forcemerge 738119 774121 Bug #738119 [src:android-tools] android-tools: new upstream version 4.4.2 is available Bug #774121 [src:android-tools] adb sideload fails with TWRP 2.8.2.0 Severity set to 'normal' from 'serious' The source android-tools and version 4.2.2+git20130529 do not appear to match any binary packages Marked as found in versions android-tools/4.2.2+git20130529-5.1 and android-tools/4.2.2+git20130529. Merged 738119 774121 thanks Stopping processing here. Please contact me if you need assistance. -- 738119: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738119 774121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774121 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#772868: marked as done (gxine: Trigger cycle causes dpkg to fail processing)
Your message dated Tue, 30 Dec 2014 15:48:35 + with message-id e1y5z2b-0007sx...@franck.debian.org and subject line Bug#772868: fixed in gxine 0.5.908-3.1 has caused the Debian Bug report #772868, regarding gxine: Trigger cycle causes dpkg to fail processing 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.) -- 772868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gxine Version: 2.4.0+dfsg-2 Severity: serious Hi! This package can get involved in a trigger cycle. The problem is that it installs interests on /usr/lib/xine/plugins with files there provided by libxine2-ffmpeg, libxine2-gnome, libxine2-misc-plugins and libxine2-x, which is directly or transitively depended on by gxine itself. A solution to the above is to simply switch the triggers to their noawait variants, in this case from «interest» to «interest-noawait», as long as they are not critical for the activating packages, which might be the case here (?). Otherwise a fix might unfortunatly be more involved. Thanks, Guillem ---End Message--- ---BeginMessage--- Source: gxine Source-Version: 0.5.908-3.1 We believe that the bug you reported is fixed in the latest version of gxine, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 772...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann gre...@debian.org (supplier of updated gxine package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 28 Dec 2014 16:19:25 +0100 Source: gxine Binary: gxine gxineplugin Architecture: source amd64 Version: 0.5.908-3.1 Distribution: unstable Urgency: medium Maintainer: Darren Salt devs...@moreofthesa.me.uk Changed-By: gregor herrmann gre...@debian.org Description: gxine - the xine video player, GTK+/Gnome user interface gxineplugin - the xine video player, GTK+/Gnome; launcher plugin for Mozilla Closes: 772868 Changes: gxine (0.5.908-3.1) unstable; urgency=medium . * Non-maintainer upload. * Fix Trigger cycle causes dpkg to fail processing: switch trigger from interest to interest-noawait, thanks Guillem Jover (Closes: #772868) Checksums-Sha1: d002e2f5bc3da9a097ee93111ce8d69a0f59d3c5 2261 gxine_0.5.908-3.1.dsc 154eada9d3e94a0c641e60fc515a74afb736eb49 12176 gxine_0.5.908-3.1.debian.tar.xz b17aa68bb762c96ebcf62727bafea48e784e9064 391558 gxine_0.5.908-3.1_amd64.deb b962c73639a51a2ce1565bb732a30aa967956bee 6442 gxineplugin_0.5.908-3.1_amd64.deb Checksums-Sha256: a4fda487224286aed9d5434ca9059fcc7ce758bcf6b3ca94dac184adb13ebd88 2261 gxine_0.5.908-3.1.dsc 8bdcf54a0f0907c688756a6681bf0680e6d6d5852cf08946504ae2956d881332 12176 gxine_0.5.908-3.1.debian.tar.xz fa946227e92f9d84bef1839459cf65cce6c6ae2a4609ef0020487d2da493a35d 391558 gxine_0.5.908-3.1_amd64.deb 16dbadb0ac7236fd65375c5e1cbf21c29127f507335e8ad81400f4dc2157da49 6442 gxineplugin_0.5.908-3.1_amd64.deb Files: 715ad9dc68d0c65d3635ae81015e13e4 2261 video optional gxine_0.5.908-3.1.dsc a61c85b5cd28a15dd4e01063eaa98d9b 12176 video optional gxine_0.5.908-3.1.debian.tar.xz 06043677f3c9501fd3d34cb24e30 391558 video optional gxine_0.5.908-3.1_amd64.deb e3356e6ca7a2ccf297c2f508afcd9b71 6442 video optional gxineplugin_0.5.908-3.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJUoCA1XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGmNoP/jdF61d6Pm9QtDx+w7UuJ++n Z4kLSicfMTtIc/Q2WvdggDw4tnQq/5aUWTqegL/cYheuuVR7vVpJAyHjaRUj2NXk EQ87ji3CazjGN18m+bojkWkhGQpa13BVF79JRBli3QkXDLcr27ZeQxuDgDVXRBq5 biAX5LlwlcM5K7NSA3wY/DArQP7Cj8UkdSJpO4s9n/9umHvmu304y0WdyBRDL6JS e/7tr/XX3kCJRGCrNFWdeP1sP3a1QUucbDCTKTRrN8OpsrSK0+hGd3I2jCkBNFLq 6C9ENMPbc5Laejd+Ntmuivi2eT6mwALkuchRh63+toFQXwOlJXiswCRMO9F8jMsw 1MLP5FQP3UrbheaqPKXRJTBMR6ELvip7hk5iSQ1blHxwJlyLQZJM3XEVLR6JNU7d /s/91bQ30kUGKoG3fsNlGhT8r/3LuOi5efOEEYZcCe5OwPs4A031hqlMOcTzEslk 6pKmARGwVChTLku0JP9I7Z8v+SEz9H5zx+cVZyeC8qbGo/sYxUEpRAokLR2q1VmL OOay8tz8jT5pRIf8BNOPOK+v8FMImMlTfVA7Na5Z0EnI23MBvQQEgTTG2F6XBe76
Processed: Re: Bug#773041: Bug#773318: clamav dies/hangs
Processing control commands: tag 773041 + pending Bug #773041 [libmspack0] libmspack: hangs on a crafted CAB file Added tag(s) pending. -- 773041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773041 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#773041: Bug#773318: clamav dies/hangs
Control: tag 773041 + pending Coin, Thanks a lot Andreas. Have a pleasant end of year time. -- Marc Dequènes -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771226: Not currently a problem
notfound 771226 0.4 tag 771226 + moreinfo severity 771226 important tag 771729 + moreinfo severity 771729 important thanks These bugs appear to no longer be present. A clean pbuilder chroot can install the package, as long as the architecture is first added. # dpkg --add-architecture armhf # apt update # apt install gcc-arm-linux-gnueabihf The same works for gcc-mipsel-linux-gnu and gcc-mips-linux-gnu after mips and mipsel are added respectively. Please re-verify and feel free to close these bugs by sending email to 771729-d...@bugs.debian.org or 771226-d...@bugs.debian.org as appropriate. -- Neil Williams = http://www.linux.codehelp.co.uk/ pgpwz2vJnP6PI.pgp Description: OpenPGP digital signature
Processed: Not currently a problem
Processing commands for cont...@bugs.debian.org: notfound 771226 0.4 Bug #771226 [gcc-arm-linux-gnueabihf] gcc-arm-linux-gnueabihf: Currently uninstallable There is no source info for the package 'gcc-arm-linux-gnueabihf' at version '0.4' with architecture '' Unable to make a source version for version '0.4' No longer marked as found in versions cross-gcc-defaults/0.4. tag 771226 + moreinfo Bug #771226 [gcc-arm-linux-gnueabihf] gcc-arm-linux-gnueabihf: Currently uninstallable Added tag(s) moreinfo. severity 771226 important Bug #771226 [gcc-arm-linux-gnueabihf] gcc-arm-linux-gnueabihf: Currently uninstallable Severity set to 'important' from 'serious' tag 771729 + moreinfo Bug #771729 [gcc-arm-linux-gnueabihf] Depends: gcc-4.9-arm-linux-gnueabihf (= 4.9.2-2) but it is not installable Added tag(s) moreinfo. severity 771729 important Bug #771729 [gcc-arm-linux-gnueabihf] Depends: gcc-4.9-arm-linux-gnueabihf (= 4.9.2-2) but it is not installable Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 771226: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771226 771729: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771729 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#773818: Crashes on start
On Tue, Dec 30, 2014 at 10:49:34AM +0100, Andreas Henriksson wrote:
Hello Adam Majer!
Hello!
Stumbled across your bug report while browsing over release-critical ones...
I haven't even looked at the lpe source, but just from looking at the
hunk included as context in your patch it looks like the source
could really use some wider review then just targeted fixes.
That's quite correct. lpe hasn't really been updated in a decade. But
it's still a very simple editor I prefer over vim or emacs for simple
tasks.
- Ctrl-C close without saving
- Ctrl-X close and save
- Ctrl-V Ctrl-V/A/S - pass buffer through shell command, awk, or sed
Can't get faster than that.
On Tue, Dec 23, 2014 at 09:34:20AM -0600, Adam Majer wrote:
[...]
diff -u lpe-1.2.7/src/buffer.c lpe-1.2.7/src/buffer.c
--- lpe-1.2.7/src/buffer.c 2014-06-23 22:53:33.582593198 -0500
+++ lpe-1.2.7/src/buffer.c 2014-12-23 09:08:54.888625050 -0600
@@ -158,8 +158,8 @@
int (*accept) (buffer *);
Consider the case where strlen(ent-d_name) == basename_len.
if (strlen(ent-d_name) basename_len) {
This should probably use = .
No. This already includes null when accounting for basename_len. If
strlen == basename_len then there is enough room in the buffer. Output
is just before the \0 that is already allocated.
That is also why that +1 to account for \0 in the calculation was in
the wrong spot and caused issues on next loop when filename could be
+1 character longer. And those happen,
cppmode.so
htmlmode.so
As mentioned, I haven't looked at the full source so I might very well
be missing something. As I understood it this is the second attempt at
fixing an issue here. Possibly a wider review of how to avoid
off-by-one in the entire source could be useful.
In this case this is the problem. I think it was caused by trying to
be fancy and retaining old code that used fixed length array and
then apply it to dynamic array. Better approach would have been to
simplify all those concatenations in one spot instead of all over the
loop.
You are 100% correct. lpe would benefit from overall update.
Thanks for looking at this.
- Adam
--
Adam Majer
ad...@zombino.com
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771126: libav/tests/lena.pnm: also not mentioned in debian/copyright
On 2014-12-02 15:31:39, Jonas Smedegaard wrote: Jonas, would you mind taking over from here and upload https://libav.org/releases/libav-11.1.tar.xz to unstable? I don't mind doing the technical work of packaging, but prefer if someone else takes to dialogue with release team about freeze exception, as I don't have the stomach for that (no blame on the release team for that!). I also don't mind doing the additional technical work of cherry-picking only the fix for this bug and apply to 6:11-2 currently targeted Jessie. Which of those to do would probably need input from the person willing to do the negotiation with release team, however. So I await someone volunteering for that (and while waiting will prepare that new upstream release, and if noone have appeared before done release it targeted experimental). I'm currently preparing the upload to unstable and will follow up with the release team. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#773041: marked as done (libmspack: hangs on a crafted CAB file)
Your message dated Tue, 30 Dec 2014 17:03:39 + with message-id e1y60cp-yl...@franck.debian.org and subject line Bug#773041: fixed in libmspack 0.4-2 has caused the Debian Bug report #773041, regarding libmspack: hangs on a crafted CAB file 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.) -- 773041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: cabextract Version: 1.4-4+b1 Severity: minor Usertags: afl The attached file makes cabextract hang forever (or at least for two minutes, after which I lost my patience :-P). This bug was found using American fuzzy lop: http://lcamtuf.coredump.cx/afl/ -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages cabextract depends on: ii libc6 2.19-13 -- Jakub Wilk hang.cab Description: application/cab ---End Message--- ---BeginMessage--- Source: libmspack Source-Version: 0.4-2 We believe that the bug you reported is fixed in the latest version of libmspack, 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 773...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marc Dequènes (Duck) d...@duckcorp.org (supplier of updated libmspack package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 30 Dec 2014 17:40:47 +0100 Source: libmspack Binary: libmspack0 libmspack-dev libmspack-dbg libmspack-doc Architecture: source amd64 all Version: 0.4-2 Distribution: unstable Urgency: medium Maintainer: Marc Dequènes (Duck) d...@duckcorp.org Changed-By: Marc Dequènes (Duck) d...@duckcorp.org Description: libmspack-dbg - library for Microsoft compression formats (debugging symbols) libmspack-dev - library for Microsoft compression formats (development files) libmspack-doc - library for Microsoft compression formats (documentation) libmspack0 - library for Microsoft compression formats (shared library) Closes: 773041 Changes: libmspack (0.4-2) unstable; urgency=medium . * Added patch 'qtmd-fix-frame_end-overflow.patch' to fix an overflow causing an infinite loop in some situation (Closes: #773041). Checksums-Sha1: f84986daa0318462b156e739abfa10a83e3c3f35 2064 libmspack_0.4-2.dsc fb6cbf08a9fc2fbfd713ba2d048f06d7aeeccceb 3516 libmspack_0.4-2.debian.tar.xz a9ea854769dcd26dad3a965daee1cc8d5f42fc20 45570 libmspack0_0.4-2_amd64.deb bebc11d8e2e89c1e87998a913d6ece23d768a946 63944 libmspack-dev_0.4-2_amd64.deb 583b9ab31401e42fb336e2d5e085e83fff638192 82966 libmspack-dbg_0.4-2_amd64.deb 6a6ed210f9125f7a11b2f1a835197a38b2189609 87766 libmspack-doc_0.4-2_all.deb Checksums-Sha256: 45c8f9a2280a0857b1dc2a3b1ed2a1c593eefc25b003dcb1e8ccdd9d5201c008 2064 libmspack_0.4-2.dsc cc59f38c4661112139817ddbb177ec966b7ffbb8fa215ccf9fa6531e9b1c6e54 3516 libmspack_0.4-2.debian.tar.xz d5bfe0ddfd7eae30bf5dff7b68053f28f8844f1fa204fc6419992e3e6d623091 45570 libmspack0_0.4-2_amd64.deb 60bd8c1fcbce7a165fc62313b048b02d1d4c0cda19ec86e713f1f2c429019e6b 63944 libmspack-dev_0.4-2_amd64.deb e5a5a5da15bcedcaf6439732e08941ba9619f72718bd630978d20bee0c901aad 82966 libmspack-dbg_0.4-2_amd64.deb 578913a0c8bc6bba3abf7b045f10a73f55449f0219a97a653b5c2f1bc7c298e5 87766 libmspack-doc_0.4-2_all.deb Files: 2f4d81be6b8025ba24d3318678200fd7 2064 libs optional libmspack_0.4-2.dsc 40301461d418e010cd6fbbf3d3fd6a55 3516 libs optional libmspack_0.4-2.debian.tar.xz a1f869d6e77d53784d9cdcd089c64366 45570 libs optional libmspack0_0.4-2_amd64.deb d4258fb2c2747ec3c0edfafe8ff7db11 63944 libdevel optional libmspack-dev_0.4-2_amd64.deb 6bb0e11c8893f0fc0b1a0f701f9d5b32 82966 debug extra libmspack-dbg_0.4-2_amd64.deb fb93a34a6279963a791dcc6e09448ba0 87766 doc optional libmspack-doc_0.4-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUotguAAoJEFXp+fesHEQ/WVgQAKZMKwZpeaGokq9RqOp4rsbr
Bug#774185: marked as done (libsys-virt-perl: Wrong runtime dependency on libvirt-bin)
Your message dated Tue, 30 Dec 2014 17:33:52 + with message-id e1y60g4-0006oa...@franck.debian.org and subject line Bug#774185: fixed in libsys-virt-perl 1.2.9-2 has caused the Debian Bug report #774185, regarding libsys-virt-perl: Wrong runtime dependency on libvirt-bin 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.) -- 774185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libsys-virt-perl Severity: normal Dear Maintainer, right now libsys-virt-perl declares a hard dependency on libvirt-bin which is rather silly since libvirt supports accessing remote daemons via the network so why should this library depend on the deamon anyways? This is not only an inconvinience but could also result in security issues for users unknowingly installing an autostarting daemon even though they just tried to install libguestfs-tools for example (which is the problem I ran into). So I propose at least downgrading the dependency on libvirt-bin to a Recomends so users can choose not to install the daemon. Thanks -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ---End Message--- ---BeginMessage--- Source: libsys-virt-perl Source-Version: 1.2.9-2 We believe that the bug you reported is fixed in the latest version of libsys-virt-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 774...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso car...@debian.org (supplier of updated libsys-virt-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 30 Dec 2014 08:11:19 +0100 Source: libsys-virt-perl Binary: libsys-virt-perl Architecture: source amd64 Version: 1.2.9-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: Salvatore Bonaccorso car...@debian.org Description: libsys-virt-perl - Perl module providing an extension for the libvirt library Closes: 774185 Changes: libsys-virt-perl (1.2.9-2) unstable; urgency=medium . * Change Build-Depends from libvirt-bin to libvirt-daemon libvirt-bin is now a transitional package and only libvirt-daemon is used during build. * Drop Depends on libvirt-bin. The runtime dependency to neither libvirt-daemon-system or libvirt-clients is required to have the Perl module working. It only requires the dependency on the library, since libvirt supports also accessing remote daemons via the network. Thanks to Daniel Gröber d...@darkboxed.org (Closes: #774185) Checksums-Sha1: f2bd56eb47922e193966e7515c53b90dbc54ca90 2194 libsys-virt-perl_1.2.9-2.dsc 25bf98d79f5ae48968f2f2f7a636d09843d6f694 3800 libsys-virt-perl_1.2.9-2.debian.tar.xz Checksums-Sha256: 29f745727edade4a417852a25931724250237b2c3815f8814bf1a5ddf0451303 2194 libsys-virt-perl_1.2.9-2.dsc 6d75981e6d6f9946377cf148ea1dac8aa8d98edd42bffb065d9040e8555bd256 3800 libsys-virt-perl_1.2.9-2.debian.tar.xz Files: 605a5aed5e239b1a86b00cc2d6f237fd 2194 perl optional libsys-virt-perl_1.2.9-2.dsc 790d6ab191262f7d5993352fb24195b3 3800 perl optional libsys-virt-perl_1.2.9-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUouBuAAoJEAVMuPMTQ89ETA8P/RMHYrF67NbBdWgMoSTFbyoO U8x8e9t+2zsfD+OeBANecq+aieAqVZ+MP2bHJrCjDWjSb/Q+xQYvBCyZWP/JdZGj zzzWJwZZCAKxPuTc1kbTDKE4yoaCgGkxPRk42A4VRSFaeprVHw1/J+IWQQRd/BDC UPO1EsreiwFrzRTFHO69PtQlywseOkC0wpsp3u1tpXpUjJV6fPoKxfsqYlMWRRe0 jb367HA0sRwkawCVGFBRgLSU0vsNESJv0DI+2Ga+LbATDMJeECLFIiud7gxHXHLU RTHP1cHaiWb9EfheyWItdLgoZR6+zPaM1NL2E0shoNjw9LSN5QbhBdvpnSn1QKfc GLbpd8hI7nr7MZDV5DPN2MvOTz+vmMQ3mrx0auYn4CMYMCXdKseR0MsZ1JUG3hZW cc0dM83O/QkqmPu7K4yewy9y73rKdw8xSD0Vtr80GqzdEjw/iyWY4YKBDk6waB78 SYw5OLsfmTOEveYHkKhkMNJ5+LpEhtp9R+bQq/IucZwamxwbIFu+0KC4KqHOczh3
Processed: severity of 773806 is grave
Processing commands for cont...@bugs.debian.org: severity 773806 grave Bug #773806 [libdb5.3-java] libdb5.3-java: Pre-installation script fails Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 773806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773806 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#773806: [pkg-db-devel] Bug#773806: Bug#773806: libdb5.3-java: Pre-installation script fails
JFTR This is caused by older dpkg ( 1.17.22) that didn't set
${misc:Pre-Depends} to = 1.17.14.
This is not a bug in src:db5.3 per se, but it needs to be fixed by
sourceful upload of db5.3 anyway since libdb5.3-java is arch:all and
cannot be fixed by binNMU.
As a temporary fix upgrade your dpkg to = 1.17.14 first and then
upgrade rest of the system.
Cheers,
Ondrej
On Tue, Dec 30, 2014, at 15:50, Ondřej Surý wrote:
Control: severity -1 important
Control: tags -1 + moreinfo
Hi Ulrich,
I can't reproduce the bug and by reading dpkg-maintscript-helper I think
you are mistaken in your diagnosis.
It's the $SYMLINK and not the $SYMLINK_TARGET that has to be absolute
target, see the code.
But it looks like the support for relative symlinks were added in
1.17.14:
dpkg (1.17.14) unstable; urgency=low
[...]
* Add support for relative symlinks to dpkg-maintscript-helper
symlink_to_dir
command. Suggested by Don Armstrong d...@debian.org.
and the ${misc:Pre-Depends} was fixed in 1.17.22:
dpkg (1.17.22) unstable; urgency=low
[...]
* Bump minimal version for dir_to_symlink and symlink_to_dir commands
to 1.17.14 in dpkg-maintscript-helper(1) man page. Closes: #769843
So libdb5.3-java just needs binNMU with dpkg 1.17.22.
Cheers,
Ondrej
On Tue, Dec 23, 2014, at 14:45, Ulrich Klauer wrote:
Package: libdb5.3-java
Version: 5.3.28-7~deb8u1
Severity: grave
Justification: prevents package from being installed/upgraded
Unfortunately, there is another[1] bug in libdb5.3-java.maintscript which
means that the package still can't be installed or, if an earlier version
is present, can't be upgraded. The error message is:
dpkg-maintscript-helper: error: original symlink target is not an
absolute path
So, the target argument to symlink_to_dir must be an absolute path, i.e.
/usr/share/doc/libdb5.3 instead of just libdb5.3. See [2] for an
explanation of why this was changed in dpkg 1.17.13.
Ulrich
[1] http://bugs.debian.org/771877
[2] http://bugs.debian.org/758778
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (990, 'testing'), (800, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-2-amd64 (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 libdb5.3-java depends on:
ii dpkg 1.17.13
ii libdb5.3-java-jni 5.3.28-7~deb8u1
libdb5.3-java recommends no packages.
Versions of packages libdb5.3-java suggests:
pn libdb5.3-java-gcj none
-- no debconf information
___
pkg-db-devel mailing list
pkg-db-de...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-db-devel
--
Ondřej Surý ond...@sury.org
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
___
pkg-db-devel mailing list
pkg-db-de...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-db-devel
--
Ondřej Surý ond...@sury.org
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#774217: yum: Missing dependency on python-lzma
Processing control commands: severity -1 normal Bug #774217 [yum] yum: Missing dependency on python-lzma Severity set to 'normal' from 'serious' -- 774217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774217 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#774217: yum: Missing dependency on python-lzma
Control: severity -1 normal Hi, thanks for catching and reporting this oversight. On Tue, Dec 30, 2014 at 13:42:46 +0100, John Paul Adrian Glaubitz wrote: yum is missing the dependency on the python-lzma package which is needed to decompress the repository files used in newer Fedora repositories. Agreed, so a simple workaround is apt-get install yum python-lzma. I agree a dependency should be added on python-lzma, probably no higher than Recommends, since yum works perfectly well without it, assuming you are pulling from a repository that uses either gzip or bzip2 compression. But I honestly don't think this bug, which isn't a policy violation and has such a simple workaround, is RC. -- mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771126: libav/tests/lena.pnm: also not mentioned in debian/copyright
Hi Sebastian, Quoting Sebastian Ramacher (2014-12-30 18:01:24) On 2014-12-02 15:31:39, Jonas Smedegaard wrote: Jonas, would you mind taking over from here and upload https://libav.org/releases/libav-11.1.tar.xz to unstable? I don't mind doing the technical work of packaging, but prefer if someone else takes to dialogue with release team about freeze exception, as I don't have the stomach for that (no blame on the release team for that!). I also don't mind doing the additional technical work of cherry-picking only the fix for this bug and apply to 6:11-2 currently targeted Jessie. Which of those to do would probably need input from the person willing to do the negotiation with release team, however. So I await someone volunteering for that (and while waiting will prepare that new upstream release, and if noone have appeared before done release it targeted experimental). I'm currently preparing the upload to unstable and will follow up with the release team. Great! - Jonas -- * 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#774242: libical1 1.0-1.2 breaks kalarm
Package: libical1 Version: 1.0-1.1 Severity: critical Justification: breaks unrelated software Dear Maintainer, after updating libical1 to 1.0-1.2 kalarm does not work anymore. Manual downgrading libical1 back to 1.0-1.1 fixes this. Setting high bug priority to prevent migration to jessie at this point of release. If you need any more input let me know. Bye Thilo -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (400, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libical1 depends on: ii libc6 2.19-13 ii tzdata 2014j-1 libical1 recommends no packages. libical1 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#764630: marked as done (missing JNI multi-arch PATHs in jarwrapper)
Your message dated Tue, 30 Dec 2014 18:18:36 + with message-id e1y61nm-0004gr...@franck.debian.org and subject line Bug#764630: fixed in javatools 0.48 has caused the Debian Bug report #764630, regarding missing JNI multi-arch PATHs in jarwrapper 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.) -- 764630: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: dicomscope Version: 3.6.0-11 Severity: important Some dependency seems to be missing. $ dicomscope starting DICOMscope please wait... Exception in thread main java.lang.UnsatisfiedLinkError: no jInterface in java.library.path at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1886) at java.lang.Runtime.loadLibrary0(Runtime.java:849) at java.lang.System.loadLibrary(System.java:1088) at main.MainContext.clinit(MainContext.java:58) at dicomscope.DICOMscope.main(DICOMscope.java:91) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (700, 'testing'), (650, 'stable'), (600, 'unstable'), (550, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-rc7-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dicomscope depends on: ii default-jre 2:1.7-52 ii jarwrapper 0.47 ii libc62.19-11 ii libdcmtk23.6.0-15+b1 ii libgcc1 1:4.9.1-15 ii libstdc++6 4.9.1-15 ii tk [wish]8.6.0+8 ii tk8.68.6.2-1 dicomscope recommends no packages. dicomscope suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: javatools Source-Version: 0.48 We believe that the bug you reported is fixed in the latest version of javatools, 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 764...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany a...@gambaru.de (supplier of updated javatools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 05 Dec 2014 10:38:23 +0100 Source: javatools Binary: jarwrapper javahelper java-propose-classpath Architecture: source all Version: 0.48 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Markus Koschany a...@gambaru.de Description: jarwrapper - Run executable Java .jar files java-propose-classpath - Helper script to suggest a classpath for jar files javahelper - Helper scripts for packaging Java programs Closes: 764630 Changes: javatools (0.48) unstable; urgency=medium . * Team upload. * jarwrapper: Add MULTIARCH_LIBRARY_PATH variables for 32bit and 64bit arches which contain all known multiarch jni library paths and use this as value for -Djava.library.path depending on the JVM that is used to launch the application. Add an additional check for the GIJ bytecode interpreter and let it handle the library path by itself. This ensures that all JVM will find the corresponding libraries correctly. (Closes: #764630) Checksums-Sha1: 0759ab0e7c1cacb5adbebaf35bcbe81757c8272c 1968 javatools_0.48.dsc 9cb1662da725b533e126e2e949731fb97afda5af 49948 javatools_0.48.tar.xz 042c61bfe1792bd7d5637590bce7b039f054ddb0 17116 jarwrapper_0.48_all.deb 094161b9fd023294b3f08e46bc4ba89c4c0bf148 84148 javahelper_0.48_all.deb 03cb6102ad6a1cefa026f6b78c4096750dbbefe5 13796 java-propose-classpath_0.48_all.deb Checksums-Sha256: 352cf4837d00483dc068ab6b0cb59470b7e04e93566838765eced4b85fedccfb 1968 javatools_0.48.dsc e2e6eff0a563ded62a937265fe88a8308040e824586482272c703d010cce7626 49948 javatools_0.48.tar.xz a5d177213261b366c44ad0d0ea998bdd79644819173aec40663bedbaed8bd8e0 17116 jarwrapper_0.48_all.deb 1d57d84fa33873c7c144d6a663f37825f00618e26c873fb897aa126f56d4b07b 84148 javahelper_0.48_all.deb ff66f067d09f01a2812be25e5b90ac9f712197182254c88bb8d98447131bf86e 13796 java-propose-classpath_0.48_all.deb Files: ca2a05c00fd5148554eec0a36ff983dd 1968 java optional javatools_0.48.dsc
Bug#764630: RFS: javatools 0.48 [RC]
On 12/29/2014 02:15 PM, Markus Koschany wrote:
On Sun, 21. Dec 09:57 tony mancill tmanc...@debian.org wrote:
On 12/15/2014 12:06 AM, Mathieu Malaterre wrote:
On Sun, Dec 14, 2014 at 6:50 PM, Markus Koschany a...@gambaru.de wrote:
[...]
Actually what was the reasoning behind the choice to use a custom shell
script like jarwrapper instead of jexec to register executable jars with
binfmt-misc? This question also came up in the bug report.
Here is my guess:
`jexec` only works with openjdk installed. At one point debian had
multiple java implementation (sun, kaffe...). These days only two
really remains, so maybe an easier solution would be to have a
`gcj-exec` provided by `gcj-jdk` to mimic openjdk package. Which means
it would be much easier to handle the LD_LIBRARY_PATH issue within the
`gcj-exec` executable.
jarwrapper is only really needed with a custom jre installation...
That sounds reasonable to me, although it can be hard in practice to
keep things functional for users running non-Debian JRE packages. Which
is not to say that we shouldn't generally discourage jarwrapper...
I think before we create another solution like gcj-exec, it is easier to
maintain the current implementation of jarwrapper. I agree that gcj's
handling of LD_LIBRARY_PATH and Multiarch could be improved but in my
opinion there are other aspects about gcj which deserve even more
attention. Most modern Java applications just don't work with it.
I suggest to upload the fix for #764630 now. I just saw tony's email
from the 21th. The current state on master is final. I haven't planned
any further changes to jarwrapper. Please go ahead.
Uploaded to unstable. Markus, would you be willing to file the unblock
request for this bug? Attached are the debdiffs for the upload I
performed. As the author of this change, you're in the best position to
discuss specifics with the Release Team if there are any questions.
If you'd rather not, please let me know and I'll do it. I think we want
this change for jessie, if that's still possible.
Thank you,
tony
diff -Nru javatools-0.47/debian/changelog javatools-0.48/debian/changelog
--- javatools-0.47/debian/changelog 2014-09-10 13:42:21.0 -0700
+++ javatools-0.48/debian/changelog 2014-12-11 22:44:41.0 -0800
@@ -1,3 +1,16 @@
+javatools (0.48) unstable; urgency=medium
+
+ * Team upload.
+ * jarwrapper: Add MULTIARCH_LIBRARY_PATH variables for 32bit and 64bit arches
+which contain all known multiarch jni library paths and use this as
+value for -Djava.library.path depending on the JVM that is used to
+launch the application. Add an additional check for the GIJ bytecode
+interpreter and let it handle the library path by itself.
+This ensures that all JVM will find the corresponding libraries correctly.
+(Closes: #764630)
+
+ -- Markus Koschany a...@gambaru.de Fri, 05 Dec 2014 10:38:23 +0100
+
javatools (0.47) unstable; urgency=medium
* Team upload.
diff -Nru javatools-0.47/jarwrapper javatools-0.48/jarwrapper
--- javatools-0.47/jarwrapper 2014-09-10 12:33:53.0 -0700
+++ javatools-0.48/jarwrapper 2014-12-11 22:44:41.0 -0800
@@ -19,7 +19,7 @@
JAVAOPTS=$(perl -0nE 's{\r?\n\s}{}gsm; print $1 if m{^Debian-Java-Parameters:\s*([^\r\n]+)}m;' $TEMP/META-INF/MANIFEST.MF)
rm -rf $TEMP
-for i in $NEW_JAVA_HOMES; do
+for i in $NEW_JAVA_HOMES; do
if [ -x $i/bin/java ]; then
JAVA=$i/bin/java
JAVA_HOME=$i
@@ -33,9 +33,25 @@
JAVA=java
fi
+MULTIARCH_LIBRARY_PATH_32BIT=/usr/lib/jni:/usr/lib/arm-linux-gnueabi/jni:/usr/lib/arm-linux-gnueabihf/jni:/usr/lib/i386-gnu/jni:/usr/lib/i386-linux-gnu/jni:/usr/lib/i386-kfreebsd-gnu/jni:/usr/lib/mips-linux-gnu/jni:/usr/lib/mipsel-linux-gnu/jni:/usr/lib/powerpc-linux-gnu/jni:/usr/lib/powerpc-linux-gnuspe/jni:/usr/lib/sparc-linux-gnu/jni:/usr/lib/x86_64-linux-gnux32/jni:/usr/lib/hppa-linux-gnu/jni:/usr/lib/sh4-linux-gnu/jni:/usr/lib/m68k-linux-gnu/jni
+
+MULTIARCH_LIBRARY_PATH_64BIT=/usr/lib/jni:/usr/lib/alpha-linux-gnu/jni:/usr/lib/x86_64-linux-gnu/jni:/usr/lib/aarch64-linux-gnu/jni:/usr/lib/x86_64-kfreebsd-gnu/jni:/usr/lib/powerpc64-linux-gnu/jni:/usr/lib/powerpc64le-linux-gnu/jni:/usr/lib/s390x-linux-gnu/jni:/usr/lib/sparc64-linux-gnu/jni
+
if which $JAVA /dev/null 21; then
- export LD_LIBRARY_PATH=/usr/lib/jni
- exec $JAVA $JAVAOPTS -Djava.library.path=/usr/lib/jni -jar $JAR $@
+if java --version 21 | grep GNU libgcj /dev/null; then
+# Let GNU gij handle the library path by itself
+export LD_LIBRARY_PATH=/usr/lib/jni
+exec $JAVA $JAVAOPTS -jar $JAR $@
+fi
+if java -d32 21 | grep does not support /dev/null; then
+# 64bit
+export LD_LIBRARY_PATH=$MULTIARCH_LIBRARY_PATH_64BIT
+exec $JAVA $JAVAOPTS -Djava.library.path=$MULTIARCH_LIBRARY_PATH_64BIT -jar $JAR $@
+else
+# 32bit
+export LD_LIBRARY_PATH=$MULTIARCH_LIBRARY_PATH_32BIT
+exec $JAVA $JAVAOPTS
Bug#766700: marked as done (pidgin-encryption: Please default to stronger keys)
Your message dated Tue, 30 Dec 2014 18:49:49 + with message-id e1y61rz-yy...@franck.debian.org and subject line Bug#766700: fixed in pidgin-encryption 3.1-1.1 has caused the Debian Bug report #766700, regarding pidgin-encryption: Please default to stronger keys 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.) -- 766700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766700 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pidgin-encryption Version: 3.1-1:amd64 Severity: important Dear Maintainer, Pidgin-encryption generates 1024 bit keys by default, while they are now considered to be weak. Please switch to defaulting to 4096 bit keys. I'm setting severity to important since the aim of this package is providing strong security with little work, thus IMO the defaults should provide strong encryption. Cheers, Balint ---End Message--- ---BeginMessage--- Source: pidgin-encryption Source-Version: 3.1-1.1 We believe that the bug you reported is fixed in the latest version of pidgin-encryption, 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. Balint Reczey bal...@balintreczey.hu (supplier of updated pidgin-encryption 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, 25 Dec 2014 13:43:08 +0100 Source: pidgin-encryption Binary: pidgin-encryption Architecture: source Version: 3.1-1.1 Distribution: unstable Urgency: medium Maintainer: Leo Costela cost...@debian.org Changed-By: Balint Reczey bal...@balintreczey.hu Description: pidgin-encryption - pidgin plugin that provides transparent encryption Closes: 766700 Changes: pidgin-encryption (3.1-1.1) unstable; urgency=medium . * Non-maintainer upload. * Default to 4096 bits when creating new keys (Closes: #766700) * Pass hardening flags to configure Checksums-Sha1: 685a02ef257b9883616f4cd23a813eeb43ec 1851 pidgin-encryption_3.1-1.1.dsc e0bc6acec89b1ecc3ee6cbfff474e9cdaf253862 5240 pidgin-encryption_3.1-1.1.debian.tar.xz Checksums-Sha256: 0142c5653a223c5812885caf0a9480b3b390632002f68a9c5facd48ce2879bbe 1851 pidgin-encryption_3.1-1.1.dsc b1bfe8f3f4aca2d0f7b1a1ebb5305ed100cba0cf9895a431c0530f327af7b70a 5240 pidgin-encryption_3.1-1.1.debian.tar.xz Files: b9a1e16cb6dafb62386614ecaafa9b96 1851 net optional pidgin-encryption_3.1-1.1.dsc 54d6ac7be9193172321e7755592e21fb 5240 net optional pidgin-encryption_3.1-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJUnEq6AAoJEPZk0la0aRp9jMcP/jBviJZf7P45euoBnu4fXOUO mYEsJaxnNrXQPmIXFmcpTFRVjQYGnkk+KmnDxrf1ALASKHhKNzNOQROZa7Gw0eVd dvHRsQH9TtvSYpZGt1pRVAA3rjhLTSVPSc2iFYnX9CNToCUNgKpCtnAZs+6IaaTa FFlQTugj2xv9TKf2dmmUkoiLF63J329vdSRe4UePoB77nLBDh+v/q/A/ssmOHjF9 Z1bPD8ZPSSO6APvwSsQGd+i3VaPtqo9TjDfgj/Hy00e6Zt5cspECOjKxPtm5HZa6 tGbKMDZVi/ljtLdTXSBf1ZVvzVCSvXYTOAKn7XeBGMMwIrM+qnHSJo9OxyCh3U6W LmneVSh0eT0B71jzxSnXzpfldNZuGOI/l5XLhrpXynN5i0s6JjFyDpozHJfv1obk R1arEIstXF1L5mmQYQs1CHyzdtdbPKnJZGk34TMmK5Wz5bPrmBQTrgWpMHIiVO/y W/GK1IJ7DNwCG8+rU2d7O4sr87qDhPWUZfL25grk+L82NczjuSUu6a3bOA8tG4fz Oh1b6HNMXXtG8gBcioPW/ltK6OVXC9IaEZXL9juGIVvk+oTjbMedjikctGT8uaUH HogxBi0XiSl2HaJpe5BFj7JftqCkvNaJcgrdPO4mqzX5R6PqCtSb1+BbPOhTDnVE y5ivdzQM6EeD5nUh1w79 =UZS8 -END PGP SIGNATUREEnd Message---
Bug#773806: marked as done (libdb5.3-java: Pre-installation script fails)
Your message dated Tue, 30 Dec 2014 18:49:18 + with message-id e1y61r4-tn...@franck.debian.org and subject line Bug#773806: fixed in db5.3 5.3.28-8 has caused the Debian Bug report #773806, regarding libdb5.3-java: Pre-installation script fails 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.) -- 773806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libdb5.3-java Version: 5.3.28-7~deb8u1 Severity: grave Justification: prevents package from being installed/upgraded Unfortunately, there is another[1] bug in libdb5.3-java.maintscript which means that the package still can't be installed or, if an earlier version is present, can't be upgraded. The error message is: dpkg-maintscript-helper: error: original symlink target is not an absolute path So, the target argument to symlink_to_dir must be an absolute path, i.e. /usr/share/doc/libdb5.3 instead of just libdb5.3. See [2] for an explanation of why this was changed in dpkg 1.17.13. Ulrich [1] http://bugs.debian.org/771877 [2] http://bugs.debian.org/758778 -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (800, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (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 libdb5.3-java depends on: ii dpkg 1.17.13 ii libdb5.3-java-jni 5.3.28-7~deb8u1 libdb5.3-java recommends no packages. Versions of packages libdb5.3-java suggests: pn libdb5.3-java-gcj none -- no debconf information ---End Message--- ---BeginMessage--- Source: db5.3 Source-Version: 5.3.28-8 We believe that the bug you reported is fixed in the latest version of db5.3, 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 773...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý ond...@debian.org (supplier of updated db5.3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 30 Dec 2014 18:20:12 +0100 Source: db5.3 Binary: db5.3-doc libdb5.3-dev libdb5.3 db5.3-util db5.3-sql-util libdb5.3++ libdb5.3++-dev libdb5.3-tcl libdb5.3-dbg libdb5.3-java-jni libdb5.3-java libdb5.3-java-gcj libdb5.3-java-dev libdb5.3-sql-dev libdb5.3-sql libdb5.3-stl-dev libdb5.3-stl Architecture: source all Version: 5.3.28-8 Distribution: unstable Urgency: medium Maintainer: Debian Berkeley DB Group pkg-db-de...@lists.alioth.debian.org Changed-By: Ondřej Surý ond...@debian.org Description: db5.3-doc - Berkeley v5.3 Database Documentation [html] db5.3-sql-util - Berkeley v5.3 SQL Database Utilities db5.3-util - Berkeley v5.3 Database Utilities libdb5.3 - Berkeley v5.3 Database Libraries [runtime] libdb5.3++ - Berkeley v5.3 Database Libraries for C++ [runtime] libdb5.3++-dev - Berkeley v5.3 Database Libraries for C++ [development] libdb5.3-dbg - Berkeley v5.3 Database Libraries [debug] libdb5.3-dev - Berkeley v5.3 Database Libraries [development] libdb5.3-java - Berkeley v5.3 Database Libraries for Java libdb5.3-java-dev - Berkeley v5.3 Database Libraries for Java [development] libdb5.3-java-gcj - Berkeley v5.3 Database Libraries for Java (native code) libdb5.3-java-jni - Berkeley v5.3 Database Libraries for Java libdb5.3-sql - Berkeley v5.3 Database Libraries [SQL runtime] libdb5.3-sql-dev - Berkeley v5.3 Database Libraries [SQL development] libdb5.3-stl - Berkeley v5.3 Database Libraries [STL runtime] libdb5.3-stl-dev - Berkeley v5.3 Database Libraries [STL development] libdb5.3-tcl - Berkeley v5.3 Database Libraries for Tcl [module] Closes: 773806 Changes: db5.3 (5.3.28-8) unstable; urgency=medium . * Force dpkg-dev to 1.17.22 to have correct Pre-Depends (Closes: #773806) Checksums-Sha1: 9acfa9e09e2270ea33b72da1bbe4a0fa2a528205 3179 db5.3_5.3.28-8.dsc fe1fa912372031f68ba19fbd0c53455118eb97da 27608 db5.3_5.3.28-8.debian.tar.xz f8119c6724268a450dedf1281beb6f3019955f6b 19053500 db5.3-doc_5.3.28-8_all.deb
Processed: Re: Bug#768076: abcde: latest upstream version breaks eyeD3 usage
Processing control commands: merge 768076 772778 Bug #768076 [abcde] abcde: latest upstream version breaks eyeD3 usage Bug #772778 [abcde] abcde: Tagging mp3 fails with eyeD3 - version conflict Added tag(s) upstream. Merged 768076 772778 severity 768076 grave Bug #768076 [abcde] abcde: latest upstream version breaks eyeD3 usage Bug #772778 [abcde] abcde: Tagging mp3 fails with eyeD3 - version conflict Severity set to 'grave' from 'normal' Severity set to 'grave' from 'normal' tags 768076 + patch Bug #768076 [abcde] abcde: latest upstream version breaks eyeD3 usage Bug #772778 [abcde] abcde: Tagging mp3 fails with eyeD3 - version conflict Added tag(s) patch. Added tag(s) patch. -- 768076: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768076 772778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#768076: abcde: latest upstream version breaks eyeD3 usage
Processing control commands: merge 768076 772778 Bug #768076 [abcde] abcde: latest upstream version breaks eyeD3 usage Bug #772778 [abcde] abcde: Tagging mp3 fails with eyeD3 - version conflict Bug #772778 [abcde] abcde: Tagging mp3 fails with eyeD3 - version conflict Merged 768076 772778 severity 768076 grave Bug #768076 [abcde] abcde: latest upstream version breaks eyeD3 usage Bug #772778 [abcde] abcde: Tagging mp3 fails with eyeD3 - version conflict Ignoring request to change severity of Bug 768076 to the same value. Ignoring request to change severity of Bug 772778 to the same value. tags 768076 + patch Bug #768076 [abcde] abcde: latest upstream version breaks eyeD3 usage Bug #772778 [abcde] abcde: Tagging mp3 fails with eyeD3 - version conflict Ignoring request to alter tags of bug #768076 to the same tags previously set Ignoring request to alter tags of bug #772778 to the same tags previously set -- 768076: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768076 772778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772778 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#772778: Bug#768076: abcde: latest upstream version breaks eyeD3 usage
Control: merge 768076 772778
Control: severity 768076 grave
Control: tags 768076 + patch
Hello,
I can confirm the issue: abcde just can't work ATM because when using
eyeD3, it passes --encoding and --text-frame, instead of what the
current debian version of eyeD3 expects: --set-encoding and
--set-text-frame.
Also, I don't see abcde being able to use id3v2 any more for ID3
tags. This gravely reduces the usefulness of the package.
The attached patch fixed the behavior for me, with eyed3 0.7. Of
course, when eyed3 = 0.7 gets uploaded to Debian, this will have to be
reverted, thus putting a versioned suggestion.
Samuel
--- a/abcde
+++ b/abcde
@@ -835,8 +835,8 @@ do_tag ()
-a $TRACKARTIST -t
$TRACKNAME ${CDYEAR:+-Y $CDYEAR} \
-G $GENREID -n
${TRACKNUM:-$1} \
${TRACKNUM:+-N $TRACKS} \
-
${ENCODING:+--encoding=$ENCODING} \
-
${TPE2:+--text-frame=TPE2:$TPE2} \
+
${ENCODING:+--set-encoding=$ENCODING} \
+
${TPE2:+--set-text-frame=TPE2:$TPE2} \
$ABCDETEMPDIR/track$1.$OUTPUT
;;
# FIXME # Still not activated...
@@ -3324,7 +3324,7 @@ ID3OPTS=
# FIXME # Older versions of eyeD3 ( 0.7.0) expect --set-encoding=utf16-LE
# so perhaps some version sniffing would be useful. Or perhaps it might be
# better to simply cut ties with the older eyeD3... Andrew.
-EYED3OPTS=--encoding utf16
+EYED3OPTS=--set-encoding utf16
CDPARANOIAOPTS=
CDDA2WAVOPTS=
DAGRABOPTS=
--- debian/control.original 2014-12-30 19:49:39.514180740 +0100
+++ debian/control 2014-12-30 19:49:58.117642148 +0100
@@ -12,7 +12,7 @@
Architecture: all
Depends: ${misc:Depends}, cd-discid, wget, cdparanoia | icedax, vorbis-tools
(= 1.0beta4-1) | lame | flac | bladeenc | speex | musepack-tools | opus-tools
Recommends: vorbis-tools, libmusicbrainz-discid-perl,
libwebservice-musicbrainz-perl, libdigest-sha-perl, bsd-mailx
-Suggests: eject, distmp3, id3 (= 0.12), id3v2, eyed3, normalize-audio,
vorbisgain, mkcue, mp3gain, atomicparsley
+Suggests: eject, distmp3, id3 (= 0.12), id3v2, eyed3 ( 0.7~),
normalize-audio, vorbisgain, mkcue, mp3gain, atomicparsley
Description: A Better CD Encoder
frontend program to cdparanoia, wget, cd-discid, id3, and your favorite
Ogg/Vorbis, MP3, FLAC, Ogg/Speex and/or MPP/MP+(Musepack) encoder (defaults
Bug#764630: RFS: javatools 0.48 [RC]
On 30.12.2014 19:19, tony mancill wrote: [...] Uploaded to unstable. Markus, would you be willing to file the unblock request for this bug? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774255 Done. Thanks for the upload tony! signature.asc Description: OpenPGP digital signature
Bug#772815: marked as done (pyyaml: CVE-2014-9130)
Your message dated Tue, 30 Dec 2014 21:17:20 +
with message-id e1y64ak-0003aw...@franck.debian.org
and subject line Bug#772815: fixed in pyyaml 3.10-4+deb7u1
has caused the Debian Bug report #772815,
regarding pyyaml: CVE-2014-9130
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.)
--
772815: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: pyyaml
Severity: grave
Tags: security
Hi,
CVE-2014-9130 from libyaml also affects pyyaml. I'm attaching a short
reproducer.
Cheers,
Moritz
import yaml
import codecs
with codecs.open('CVE-2014-9130.yaml', 'r') as stream:
foo = yaml.load(stream)
for key, value in foo.items():
setattr(self, key, value)
abc:
def: 'xxx
' ghi: 'yyy'---End Message---
---BeginMessage---
Source: pyyaml
Source-Version: 3.10-4+deb7u1
We believe that the bug you reported is fixed in the latest version of
pyyaml, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 772...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Moritz Muehlenhoff j...@debian.org (supplier of updated pyyaml 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: Sun, 28 Dec 2014 23:35:53 +0100
Source: pyyaml
Binary: python-yaml python-yaml-dbg python3-yaml python3-yaml-dbg
Architecture: source amd64
Version: 3.10-4+deb7u1
Distribution: wheezy-security
Urgency: medium
Maintainer: Debian Python Modules Team
python-modules-t...@lists.alioth.debian.org
Changed-By: Moritz Muehlenhoff j...@debian.org
Description:
python-yaml - YAML parser and emitter for Python
python-yaml-dbg - YAML parser and emitter for Python (debug build)
python3-yaml - YAML parser and emitter for Python3
python3-yaml-dbg - YAML parser and emitter for Python3 (debug build)
Closes: 772815
Changes:
pyyaml (3.10-4+deb7u1) wheezy-security; urgency=medium
.
* CVE-2014-9130, patch by Thorsten Alteholz (Closes: #772815)
Checksums-Sha1:
d66b30c9e327438aacfa4785a28a3ff65a991f07 2193 pyyaml_3.10-4+deb7u1.dsc
476dcfbcc6f4ebf3c06186229e8e2bd7d7b20e73 241524 pyyaml_3.10.orig.tar.gz
60b7c5e6920684c273bd1c489469c67176cd08ee 6535 pyyaml_3.10-4+deb7u1.diff.gz
aa88f35bb1c5e09814f56265cd73a006d97605d8 176034
python-yaml_3.10-4+deb7u1_amd64.deb
12ff228a192c1687fd8afcd4c4f2605e21cd57ae 168636
python-yaml-dbg_3.10-4+deb7u1_amd64.deb
e5975a56983da44d57409d490f6858e153cd40f5 105238
python3-yaml_3.10-4+deb7u1_amd64.deb
5d5fcc15ea2f9a8a9982c004286691009520bfa7 84276
python3-yaml-dbg_3.10-4+deb7u1_amd64.deb
Checksums-Sha256:
9190dc62f7a85a9d6761795ddc2efbc35b5a28413966468dc00899e5af5938da 2193
pyyaml_3.10-4+deb7u1.dsc
e713da45c96ca53a3a8b48140d4120374db622df16ab71759c9ceb5b8d46fe7c 241524
pyyaml_3.10.orig.tar.gz
62bf97dc495ca6a9c251a12271f9dc472f39b5739fcb1c4bb73caf1687fb0ecc 6535
pyyaml_3.10-4+deb7u1.diff.gz
c47bd55ee5a7ba19b403fc090075ca079b37db43f5128ca5a396d8b3f06a30f5 176034
python-yaml_3.10-4+deb7u1_amd64.deb
34fd8e9952193c8fca48924316e0d90937db0efa98b03bbe14bd2ab9fc7b3001 168636
python-yaml-dbg_3.10-4+deb7u1_amd64.deb
7a7969149dad1a77a8973965d0586590101da6ed00ea1d991779459f021b0e24 105238
python3-yaml_3.10-4+deb7u1_amd64.deb
ba022dd06d2c687e3fcefb2b494c4c499d748dc499243d035ffeb469ae2e7d44 84276
python3-yaml-dbg_3.10-4+deb7u1_amd64.deb
Files:
4180e6eb4c4c1f011e9580057d82ad15 2193 python optional pyyaml_3.10-4+deb7u1.dsc
74c94a383886519e9e7b3dd1ee540247 241524 python optional pyyaml_3.10.orig.tar.gz
e1f3b69f2d3b7167f2bfac403ce99f40 6535 python optional
pyyaml_3.10-4+deb7u1.diff.gz
ca2eb20c56eaf7779fb10171f4cee9b6 176034 python optional
python-yaml_3.10-4+deb7u1_amd64.deb
99210f59b004904651a1ace9d1593c98 168636 debug extra
python-yaml-dbg_3.10-4+deb7u1_amd64.deb
ab74da300825221025233d102407b605 105238 python optional
python3-yaml_3.10-4+deb7u1_amd64.deb
3193abd088987ee27fed04a71bfd9928 84276 debug extra
python3-yaml-dbg_3.10-4+deb7u1_amd64.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBAgAGBQJUoIwXAAoJEBDCk7bDfE427z0P/2oP6tBxtKdvFj2x+p1j+xVp
kgmSzT/W1jexhIogVzoQ0SDjjo7uFH8B/Z0JoRxS/85wyIvN4kXXLF3/KL9ciT50
Bug#773785: marked as done (unzip: FTBFS on armhf)
Your message dated Tue, 30 Dec 2014 21:51:59 + with message-id e1y64hr-0007om...@franck.debian.org and subject line Bug#773785: fixed in unzip 6.0-14 has caused the Debian Bug report #773785, regarding unzip: FTBFS on armhf 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.) -- 773785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773785 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: unzip version: 6.0-13 severity: serious Hi, The latest upload of unzip fails on armhf. This blocks migration to testing. https://buildd.debian.org/status/package.php?p=unzip Cheers, Ivo ---End Message--- ---BeginMessage--- Source: unzip Source-Version: 6.0-14 We believe that the bug you reported is fixed in the latest version of unzip, 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 773...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Santiago Vila sanv...@debian.org (supplier of updated unzip package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 30 Dec 2014 22:17:12 +0100 Source: unzip Binary: unzip Architecture: source amd64 Version: 6.0-14 Distribution: unstable Urgency: medium Maintainer: Santiago Vila sanv...@debian.org Changed-By: Santiago Vila sanv...@debian.org Description: unzip - De-archiver for .zip files Closes: 773785 Changes: unzip (6.0-14) unstable; urgency=medium . * Drop -O2 optimization on armhf as a workaround for gcc Bug #764732. Closes: #773785. Checksums-Sha1: 45d734aea62a601dfea4288b8474684beeb38190 1311 unzip_6.0-14.dsc d0eb2e1723dd03276fb8aa02f726747da67e675c 13608 unzip_6.0-14.debian.tar.xz 854a35442f0836f713fac66c91fb5e47ce9dfba3 160796 unzip_6.0-14_amd64.deb Checksums-Sha256: d68b75cd0db65507a2f6f4ab427bb272bb8774aa51ee20153c74fafca73c7db0 1311 unzip_6.0-14.dsc 75810cc21a6f1e4ccbe69042be567c658abe45def9f9e8358ceca17149adcd9f 13608 unzip_6.0-14.debian.tar.xz 6a12033b9cd6b508da6eab87a8ae11ea9aa0f143d4797610b7ea22bf3f9ef695 160796 unzip_6.0-14_amd64.deb Files: e0395bcb0ffee66f9fcb6a032214f32c 1311 utils optional unzip_6.0-14.dsc 106ec6e7b3cfd9c05765af09cc0d4312 13608 utils optional unzip_6.0-14.debian.tar.xz b7050d27077be2480ca64eecb546d389 160796 utils optional unzip_6.0-14_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJUoxaeAAoJEEHOfwufG4syePMH/2MObU/eChM2/aldSkH2YwYW agyivPgB3EsdsZgxHcFMBBMWFxa94s0bleFgubJqZkaMWmPJQkEe5CEgL1T+yk9R SFXzYu6AST78gs4lwJqSnhUE2Gf+TkPKoxdJBNNnZyrOKFFm5x8cvLbMkL3FsUu6 StN88utcImyMcCnkj/m6AK7t4tZWgFFq5yvj6q0BG6VX10ptw+r5/aHb+hiViDN0 2zuUXtksD2Aoxsoz4lvkJPqeTsmjfJ3ltl2q7c9oDU0vZjIp59RUt04fu+uAl4V6 2GxSI39/pe+vQxgyKXKCKCVrlkZX4HQ8g+oyqYlG0aoYcFxXvhAdzbI+M9FsthQ= =PQt4 -END PGP SIGNATUREEnd Message---
Bug#774264: dvb-apps: Source not available
Package: dvb-apps Version: 1.1.1+rev1500-1 Severity: serious Justification: Policy 4.13 Dear Maintainer, For some reason the source package appears not to be available for dvb-apps -- I tried wheezy and testing: # apt-get source dvb-apps/testing Reading package lists... Done Building dependency tree Reading state information... Done Picking 'linuxtv-dvb-apps' as source package instead of 'dvb-apps' E: Ignore unavailable version '1.1.1+rev1500-1' of package 'dvb-apps' E: Unable to find a source package for linuxtv-dvb-apps I may be missing something, but this looks like a violation of Debian policy (and GPL). Cheers, David -- System Information: Debian Release: jessie/sid APT prefers stable APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.12.24 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US) Shell: /bin/sh linked to /bin/dash Versions of packages dvb-apps depends on: ii dtv-scan-tables 0+git20141218.b46a22c-1 ii libc62.18-5 ii libpng12-0 1.2.49-1 ii libx11-6 2:1.5.0-1+deb7u1 ii libzvbi0 0.2.33-6 ii udev 175-7.2 ii zlib1g 1:1.2.8.dfsg-1 dvb-apps recommends no packages. dvb-apps 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#774264: marked as done (dvb-apps: Source not available)
Your message dated Wed, 31 Dec 2014 00:10:27 +0100 with message-id 20141230231027.gg7...@ramacher.at and subject line Re: Bug#774264: dvb-apps: Source not available has caused the Debian Bug report #774264, regarding dvb-apps: Source not available 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.) -- 774264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: dvb-apps Version: 1.1.1+rev1500-1 Severity: serious Justification: Policy 4.13 Dear Maintainer, For some reason the source package appears not to be available for dvb-apps -- I tried wheezy and testing: # apt-get source dvb-apps/testing Reading package lists... Done Building dependency tree Reading state information... Done Picking 'linuxtv-dvb-apps' as source package instead of 'dvb-apps' E: Ignore unavailable version '1.1.1+rev1500-1' of package 'dvb-apps' E: Unable to find a source package for linuxtv-dvb-apps I may be missing something, but this looks like a violation of Debian policy (and GPL). Cheers, David -- System Information: Debian Release: jessie/sid APT prefers stable APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.12.24 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US) Shell: /bin/sh linked to /bin/dash Versions of packages dvb-apps depends on: ii dtv-scan-tables 0+git20141218.b46a22c-1 ii libc62.18-5 ii libpng12-0 1.2.49-1 ii libx11-6 2:1.5.0-1+deb7u1 ii libzvbi0 0.2.33-6 ii udev 175-7.2 ii zlib1g 1:1.2.8.dfsg-1 dvb-apps recommends no packages. dvb-apps suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- On 2014-12-30 14:07:38, David Liontooth wrote: Package: dvb-apps Version: 1.1.1+rev1500-1 Severity: serious Justification: Policy 4.13 Dear Maintainer, For some reason the source package appears not to be available for dvb-apps -- I tried wheezy and testing: # apt-get source dvb-apps/testing Reading package lists... Done Building dependency tree Reading state information... Done Picking 'linuxtv-dvb-apps' as source package instead of 'dvb-apps' E: Ignore unavailable version '1.1.1+rev1500-1' of package 'dvb-apps' E: Unable to find a source package for linuxtv-dvb-apps I may be missing something, but this looks like a violation of Debian policy (and GPL). Looks like you do not have the appropriate deb-src lines in your sources.list. apt-get(8) has the following bit about apt-get source: Source packages are tracked separately from binary packages via deb-src lines in the sources.list(5) file. This means that you will need to add such a line for each repository you want to get sources from; otherwise you will probably get either the wrong (too old/too new) source versions or none at all. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature ---End Message---
Bug#773504: NMU patch on top of current GIT
Hi Please find attached the patch on top of the current git tree on Alioth for the NMU of version 2014.1.3-7.1. If you add me to the Alioth project I can also push these changes myself. Gaudenz From 6f8528cc0cd4d7c2bd0a8f2519971acec310cdf9 Mon Sep 17 00:00:00 2001 From: Gaudenz Steinlin gaud...@soziologie.ch Date: Tue, 30 Dec 2014 23:41:16 +0100 Subject: [PATCH] Fix changelog and add NMU version The two last changelog entries don't belong to the -7 release which is already uploaded. Also add bug number to changelog entry. --- debian/changelog | 14 ++ 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/debian/changelog b/debian/changelog index b0c0add..3f354cc 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,13 @@ +nova (2014.1.3-7.1) unstable; urgency=medium + + * Non-maintainer upload. + * Added avoid_changing_UUID_when_redefining_nwfilters.patch so that nova +continues to work with libvirt = 1.2.7 (Closes: #773504). + * Updated the es.po debconf translation, thanks to jathan +jathanblack...@openmailbox.org (Closes: #773483). + + -- Gaudenz Steinlin gaud...@debian.org Tue, 30 Dec 2014 23:41:04 +0100 + nova (2014.1.3-7) unstable; urgency=medium * Now init scripts depends on libvirtd and not libvirt-bin, as this has been @@ -11,10 +21,6 @@ nova (2014.1.3-7) unstable; urgency=medium openstack-pkg-tools (= 20~). * Only calls pkgos_dbc_postinst if the user asked for dbconf-common management. - * Added avoid_changing_UUID_when_redefining_nwfilters.patch so that nova -continues to work with libvirt = 1.2.7. - * Updated the es.po debconf translation, thanks to jathan -jathanblack...@openmailbox.org (Closes: #773483). -- Thomas Goirand z...@debian.org Wed, 10 Dec 2014 19:21:37 +0800 -- 2.1.4 signature.asc Description: PGP signature
Bug#773504: marked as done (python-nova: nwfilter-problem with libvirt = 1.2.7)
Your message dated Tue, 30 Dec 2014 23:21:27 +
with message-id e1y666r-0004yw...@franck.debian.org
and subject line Bug#773504: fixed in nova 2014.1.3-7.1
has caused the Debian Bug report #773504,
regarding python-nova: nwfilter-problem with libvirt = 1.2.7
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.)
--
773504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-nova
Version: 2014.1.3-6
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Running openstack on jessie. Starting or migrating VMs leads to errors like
libvirtError: operation failed: filter
'nova-instance-instance-0012-fa163e8eb435' already exists with uuid
6b2b71c1-486c-4ef2-b0e3-1c0918bd317f
* What exactly did you do (or not do) that was effective (or
ineffective)?
Including patch from https://review.openstack.org/#/c/122721/
*** firewall.py.origThu Dec 18 14:20:43 2014
--- firewall.py Thu Dec 18 14:19:55 2014
***
*** 15,20
--- 15,23
#License for the specific language governing permissions and limitations
#under the License.
+ import uuid
+
+ from lxml import etree
from oslo.config import cfg
from nova.cloudpipe import pipelib
***
*** 59,89
return self._libvirt_get_connection()
_conn = property(_get_connection)
! @staticmethod
! def nova_no_nd_reflection_filter():
This filter protects false positives on IPv6 Duplicate Address
Detection(DAD).
return '''filter name='nova-no-nd-reflection' chain='ipv6'
!-- no nd reflection --
!-- drop if destination mac is v6 mcast mac addr and
we sent it. --
!
rule action='drop' direction='in'
mac dstmacaddr='33:33:00:00:00:00'
dstmacmask='ff:ff:00:00:00:00' srcmacaddr='$MAC'/
/rule
! /filter'''
! @staticmethod
! def nova_dhcp_filter():
The standard allow-dhcp-server filter is an ip one, so it uses
ebtables to allow traffic through. Without a corresponding rule in
iptables, it'll get blocked anyway.
!
return '''filter name='nova-allow-dhcp-server' chain='ipv4'
! uuid891e4787-e5c0-d59b-cbd6-41bc3c6b36fc/uuid
rule action='accept' direction='out'
priority='100'
udp srcipaddr='0.0.0.0'
--- 62,91
return self._libvirt_get_connection()
_conn = property(_get_connection)
! def nova_no_nd_reflection_filter(self):
This filter protects false positives on IPv6 Duplicate Address
Detection(DAD).
+ uuid = self._get_filter_uuid('nova-no-nd-reflection')
return '''filter name='nova-no-nd-reflection' chain='ipv6'
!-- no nd reflection --
!-- drop if destination mac is v6 mcast mac addr and
we sent it. --
! uuid%s/uuid
rule action='drop' direction='in'
mac dstmacaddr='33:33:00:00:00:00'
dstmacmask='ff:ff:00:00:00:00' srcmacaddr='$MAC'/
/rule
! /filter''' % uuid
! def nova_dhcp_filter(self):
The standard allow-dhcp-server filter is an ip one, so it uses
ebtables to allow traffic through. Without a corresponding rule in
iptables, it'll get blocked anyway.
! uuid = self._get_filter_uuid('nova-allow-dhcp-server')
return '''filter name='nova-allow-dhcp-server' chain='ipv4'
! uuid%s/uuid
rule action='accept' direction='out'
priority='100'
udp srcipaddr='0.0.0.0'
***
*** 97,103
srcportstart='67'
dstportstart='68'/
/rule
! /filter'''
def setup_basic_filtering(self, instance, network_info):
Set up basic filtering (MAC, IP, and ARP spoofing protection).
--- 99,105
srcportstart='67'
dstportstart='68'/
Bug#773768: pandoc upload
[responding to bug rather than (directly) our list] Quoting Joachim Breitner (2014-12-31 00:35:49) Am Dienstag, den 30.12.2014, 20:42 +0100 schrieb Jonas Smedegaard: Did you find out anything new about your ghc/linker problems? Nope :-( I guess the suggestion these days would be: Can you reproduce it with a Dockerfile that you can share with us? I don't mind you pointing me to some guide on how to mimick with docker the routines pbuilder and cowbuilder have done flawlessly for years - just for some mysterious reason no longer with Haskell. I won't promise when I will take time to explore such alternative setup, nor that I will like it and change - but I am not against it, just have absolute zero experience with that fancy new approach. - Jonas -- * 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
Processed: severity of 774257 is serious
Processing commands for cont...@bugs.debian.org: severity 774257 serious Bug #774257 [gnome-control-center] Configuring a printer does not work without system-config-printer Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 774257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774257 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#773806: libdb5.3-java: Pre-installation script fails
Hi!
On Tue, 2014-12-30 at 18:42:42 +0100, Ondřej Surý wrote:
JFTR This is caused by older dpkg ( 1.17.22) that didn't set
${misc:Pre-Depends} to = 1.17.14.
dpkg never sets misc:Pre-Depends, that's debhelper, so this fix
is not correct.
On Tue, Dec 30, 2014, at 15:50, Ondřej Surý wrote:
and the ${misc:Pre-Depends} was fixed in 1.17.22:
dpkg (1.17.22) unstable; urgency=low
[...]
* Bump minimal version for dir_to_symlink and symlink_to_dir commands
to 1.17.14 in dpkg-maintscript-helper(1) man page. Closes: #769843
So libdb5.3-java just needs binNMU with dpkg 1.17.22.
Nope, as the changelog says, that was just a man page update. The fix
you are looking for is:
,---
debhelper (9.20141221) unstable; urgency=medium
[ Niels Thykier ]
* dh_installdeb: Raise required dpkg version for dir_to_symlink to
1.17.13 (see #769843, msg #10). Thanks to Guillem Jover.
…
[ Axel Beckert ]
* dh_installdeb: Raise required dpkg version for symlink_to_dir to
1.17.14. It is needed in case of relative symlinks. (Closes: #770245)
-- Niels Thykier ni...@thykier.net Sun, 21 Dec 2014 21:21:18 +0100
`---
Thanks,
Guillem
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
