Bug#776483: python-imaging: no smooth upgrade path from wheezy due to python-imaging-tk becoming a virtual package
I have prepared an NMU with the transitional package that Andreas recommended. diff -Nru pillow-2.6.1/debian/changelog pillow-2.6.1/debian/changelog --- pillow-2.6.1/debian/changelog 2014-10-13 11:31:22.0 -0700 +++ pillow-2.6.1/debian/changelog 2015-03-06 18:39:18.0 -0800 @@ -1,3 +1,10 @@ +pillow (2.6.1-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add python-imaging-tk transitional package. Closes: #776483. + + -- Cameron Norman camerontnor...@gmail.com Fri, 06 Mar 2015 18:37:54 -0800 + pillow (2.6.1-1) unstable; urgency=medium * Pillow 2.6.1 release. diff -Nru pillow-2.6.1/debian/control pillow-2.6.1/debian/control --- pillow-2.6.1/debian/control 2014-10-13 11:31:43.0 -0700 +++ pillow-2.6.1/debian/control 2015-03-06 18:49:47.0 -0800 @@ -94,6 +94,12 @@ . This package contains the extension built for the Python debug interpreter. +Package: python-imaging-tk +Architecture: all +Depends: python-pil.imagetk +Description: transitional dummy package for smooth upgrades to python-pil.imagetk + This package can be safely removed. + Package: python-sane Architecture: any Multi-Arch: same
Bug#774886: [Pkg-gauche-devel] Bug#774886: Bug #774886: gauche: update libatomic-ops for mips64el
James Cowgill james...@cowgill.org.uk writes: On Thu, 08 Jan 2015 16:57:17 + James Cowgill james...@cowgill.org.uk wrote: I've forwarded the patch upstream. I've also cloned this bug to the with upstream you mean libatomic-ops here, right? other packages shipping libatomic-ops so that they don't forget to update - although they probably shouldn't until upstream / this package has. And here's a patch specifically for gauche. may i forward this as is to gauche ml? greetings, jens -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765478: Probably caused by previous systemd failures
The error you’re seeing is likely because systemd has already had failures which the netfilter-persistent service depends on. I also had the same problem when I had modules listed in /etc/modules which had since been compiled into the kernel. Since the module loading was a dependency for almost everything else in systemd, it cause the install of netfilter-persistent to fail as well. As soon as I’d sorted out the other systemd errors, the package installed without any problems. Perhaps this bug should be moved to the systemd package, since in my opinion a package install should still work even when there are bugs in /etc/modules. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774886: [Pkg-gauche-devel] Bug#774886: gauche: update libatomic-ops for mips64el
On Fri, 2015-03-06 at 23:29 +0100, Jens Thiele wrote: James Cowgill james...@cowgill.org.uk writes: On Thu, 08 Jan 2015 16:57:17 + James Cowgill james...@cowgill.org.uk wrote: I've forwarded the patch upstream. I've also cloned this bug to the with upstream you mean libatomic-ops here, right? Yes. The bug was originally filed against libatomic-ops, but I cloned it to libgc and gauche since they have embedded copies of the library. https://github.com/ivmai/libatomic_ops/pull/12 other packages shipping libatomic-ops so that they don't forget to update - although they probably shouldn't until upstream / this package has. And here's a patch specifically for gauche. may i forward this as is to gauche ml? Yes you can :) Thanks, James -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779968: icecast2: Please package Icecast 2.4.1
Package: icecast2 Version: 2.4.0-1.1 Severity: wishlist Tags: security Dear maintainer, Icecast 2.4.0 seems to be quite buggy: http://icecast.org/news/icecast-release-2_4_1/ I think version 2.4.1 might be a better choice for Jessie: it's basically a bug fixing release with no new features. Thank you! Carlo -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779969: ITP: coreclr -- .NET Core Runtime
Package: wnpp Severity: wishlist Owner: Mirco Bauer mee...@debian.org * Package name: coreclr Version : git Upstream Author : Microsoft and contributors * URL : http://www.dotnetfoundation.org/netcore5 * License : MIT/X11 Programming Lang: C++, C# Description : .NET Core Runtime The .NET Core Runtime also named CoreCLR is an open source, cross-platform runtime for the Common Language Infrastructure. The runtime currently only supports on Linux the AMD64/x86_64 CPU architecture. This runtime provides an smaller alternative to the Mono runtime. The CoreCLR is not feature on par with Mono. This package will be maintained under the Debian CLI/Mono umbrella. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777731: chromium-dbg: Incomplete debug symbols
On Fri, Mar 6, 2015 at 4:57 PM, Paul Menzel wrote: No, I did not. So to create meaningful stack/back traces for non-reproducible issues, I need to pass the switch `--debug` at every start? Is that correct? Well, --debug helps by automatically making sure you have the right paths set (you could also do that on your own). It could just as well not be helpful at all for this problem. If it's not, then this more of an upstream or debhelper problem since the package uses straight debhelper for creating the dbg package without doing anything special. Anyway, if anyone really wants this fixed, it's going to require some dedicated time and effort to track it down. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777237: Sagemath has special needs
On Thu, Mar 05, 2015 at 05:46:13PM +0100, Julien Puydt wrote: cdef GEN E cdef long errnum cdef jmp_buf env iferr_env = env if setjmp (iferr_env[0]) != 0: E = pari_err_last() errnum = E[1] _pari_err_handle(E) cb_pari_err_recover(errnum) Did I miss something about pari (in which case you can probably help), or something about sage (in which case sage-devel's mailing-list might help) ? Where are you including this code ? This is the crucial point. I do not think it is possible to use setjmp in a subfunction like _pari_init_error_handling(). How does cb_pari_err_recover() work ? How does the old code worked ? Cheers, -- Bill. ballo...@debian.org Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779967: liferea: poor error reporting for command sourced feeds
Package: liferea Version: 1.10.12-1 Severity: wishlist Dear Maintainer, When feeds generated by a command fail to produce a working feed, the error messages are both misleading and useless. Pretty much no matter what the problem is, it outputs: The last update of this subscription failed! There were errors while parsing this feed! Details Could not detect the type of this feed! Please check if the source really points to a resource provided in one of the supported syndication formats! XML Parser Output: The URL you want Liferea to subscribe to points to a webpage and the auto discovery found no feeds on this page. Maybe this webpage just does not support feed auto discovery.Source points to HTML document. You may want to contact the author/webmaster of the feed about this! (Strangely, that error even sometimes included saying that it got an HTTP 404 which makes no sense for a local resource.) My understanding is that once Liferea fails to parse an input as a feed, it tries to parse it as a webpage that has a link to a feed and it only reports the error for the second failure, despite the first failure almost always being the relevant one. As a workaround, using the same command as a conversion filter (not caring what the input being filtered is) gives more useful errors. In case that led to this bug report, telling me that the command was returning an exit code of 1 (although actually seeing the error message in output would have been more helpful). This is a very minor issue because in addition to the workaround just mentioned, I suspect this is a rarely used feature and except in edge cases like the one I ran into (it turned out the script worked with my bash environment variables but not with my X session's), simply running the command from a terminal would give the desired debugging information. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-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 Init: systemd (via /run/systemd/system) Versions of packages liferea depends on: ii dbus-x11 1.8.16-1 ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii gir1.2-gtk-3.0 3.14.5-1 ii gir1.2-peas-1.0 1.12.1-2 ii libatk1.0-0 2.14.0-1 ii libc62.19-15 ii libcairo21.14.0-2.1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libgirepository-1.0-11.42.0-2.2 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1 ii libindicate5 0.6.92-2 ii libjson-glib-1.0-0 1.0.2-1 ii libnotify4 0.7.6-2 ii libpango-1.0-0 1.36.8-3 ii libpeas-1.0-01.12.1-2 ii libsoup2.4-1 2.48.0-1 ii libsqlite3-0 3.8.7.4-1 ii libwebkitgtk-3.0-0 2.4.8-1 ii libxml2 2.9.1+dfsg1-4 ii libxslt1.1 1.1.28-2+b2 ii liferea-data 1.10.12-1 ii python-gi3.14.0-1 pn python:any none Versions of packages liferea recommends: pn gir1.2-gnomekeyring-1.0 none ii gnome-icon-theme 3.12.0-1 ii gnome-keyring3.14.0-1+b1 ii steadyflow 0.2.0-1.1 Versions of packages liferea suggests: pn network-manager none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770644: systemd: can't start dbus if dbus is not running
control: tags -1 moreinfo Am 22.11.2014 um 23:33 schrieb brian m. carlson: retitle 770644 systemd: systemd is completely unusable after a fatal signal # Justification: breaks the whole system, not suitable for release severity 770644 serious kthxbye On Sat, Nov 22, 2014 at 09:34:03PM +, brian m. carlson wrote: Package: systemd Version: 215-6 Severity: important I'm trying to start strongswan: castro ok % sudo service strongswan start Failed to get D-Bus connection: No such file or directory Okay: castro ok # systemctl start dbus Failed to get D-Bus connection: No such file or directory So I start dbus by hand (à la /etc/init.d/dbus), and: castro ok # service dbus restart Failed to restart dbus.service: Launch helper exited with unknown return code 1 castro ok # service freeradius restart Failed to restart freeradius.service: Launch helper exited with unknown return code 1 castro ok # sudo telinit u Failed to execute operation: Launch helper exited with unknown return code 1 Perhaps systemctl needs to learn a non-dbus way to talk to systemd. telinit should be using signals, not dbus, to signal init. systemd also does not fix itself even after receiving a SIGHUP, SIGUSR1, or SIGTERM. Even better is this: castro ok % sudo shutdown -r now Failed to open initctl FIFO: No such device or address Failed to talk to init daemon. I just noticed that the issue is that systemd called assert. I've attached an image of the console when this happened. I don't think I need to explain why using assert in /sbin/init is a bad idea. Can you provide steps how this issue can be reproduced? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#732452: Still valid?
Hi Roy, is this bug report still valid with Icecast 2.4.0? Thank you! Carlo
Bug#779970: ITP: corefx -- .NET Core Libraries
Package: wnpp Severity: wishlist Owner: Mirco Bauer mee...@debian.org * Package name: corefx Version : git Upstream Author : Microsoft and contributors * URL : http://www.dotnetfoundation.org/netcore5 * License : MIT Programming Lang: C# Description : .NET Core Libraries The .NET Core Runtime also named CoreCLR is an open source, cross-platform runtime for the Common Language Infrastructure. The runtime currently only supports on Linux the AMD64/x86_64 CPU architecture. This package contains the libraries of the runtime. This package will be maintained under the Debian CLI/Mono umbrella. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779676: dep5-copyright-license-name-not-unique check is too strict or too severe.
On Tue, Mar 3, 2015 at 11:13 PM, Charles Plessy ple...@debian.org wrote: I think that the dep5-copyright-license-name-not-unique tag should either: - reduce its severity, as just an advice for readability, or - only be issued when the same short name is used with a different description. Le Fri, Mar 06, 2015 at 11:19:38PM +0100, Bastien ROUCARIES a écrit : Could you pin point the exact verse of the specification ? Hi Bastien: Stand-alone License paragraphs can be used to provide the full license text for a given license once, instead of repeating it in each Files paragraph that refers to it. https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#stand-alone-license-paragraph Since it is can and not must, Lintian is too severe. Have a nice week-end, Charles -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#475889: Still open?
Hi Vincent, this is a very old bug report. Is this issue still reproducible with recent versions of Icecast (2.3.2 or 2.4.0)? Thank you! Carlo
Bug#779178: pdftopdf does not handle the landscape option correctly
On Thu 05 Mar 2015 at 12:14:00 +0100, Jonas Smedegaard wrote: Quoting Brian Potkin (2015-03-04 17:09:17) I am having doubts that a solution with orientation-requested will meet with success as landscape printing in testing for PDFs appears to be broken. Could it perhaps be that the rotation was expressed as non-integer? Ghostscript project just made a change to cover rotation expressed as 90.0: http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=12ddbaa (Yes, I am aware that ghostscript might be totally irrelevant here since a libpoppler tool is used instead: passing this only for inspiration) pdftopdf stopped being poppler based at version 1.0.22-1 in Aug 2012: * New upstream release - pdftopdf filter replaced by new QPDF-based filter from Tobias Hoffmann's Google Summer of Code project. The former Poppler-based pdftopdf duplicated a lot of Poppler's code. The old filter is still in the package as pdftopdf.old with source code in filter/pdftopdf.old. It will be removed in a later release. The filter no longer uses libpoppler but libqpdf. I was wary about approaching this bug because most of my printing is done from the command line. After looking at the outputs of printing from evince, iceweasel, okular and libreoffice on Jessie with the landscape option set (they do not produce the same output for me) I am even less inclined to print from a DE application and expect consistency. On the other hand a simple command like 'lp -d test -o landscape' with a PDF file doesn't do what it did on Wheezy. My final test (which I did had done before): Set up a print queue: lpadmin -p test -v file:/tmp/test.ps -E -m drv:///sample.drv/generic.ppd Print to the queue. The image is shown rotated by 180 degrees with gv test.ps It is upside down. This is also how it prints on paper. May I point to https://github.com/smilingthax/pdfautorotate and suggest there may be some connection between the present state of affairs and the change introduced in cups-filters (1.0.25-1)? Anyway: lp -d test -o landscape -o pdfAutoRotate=off file.pdf gets me a printout rotated by 270 degrees. Regards, Brian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779866: lintian: debian/copyright parser emits non-understandable warnings
On 2015-03-05 19:40, Helge Kreutzmann wrote: Package: lintian Version: 2.5.30-150-g79ba4df Severity: normal The parser for debian/copyright seems to be under heavy development. Hi, The DEP-5 copyright check only got two new tag (the ones you list below) since the last release to unstable and the actual changes to the check are rather modest. Unfortunately I only learn about the (possible) problems after upload, i.e. it is not possible to work on them in unstable and fix the issues before upload. Furthermore (and the core of this bug) is the problem that the emitted errors are hard to understand, so uploads become something like trial and error. Indeed, you would be unable to test these with the packaged version of lintian. However, it is fairly uncomplicated to run lintian from a git checkout. $ git clone https://anonscm.debian.org/git/lintian/lintian.git $ lintian/frontend/lintian [options] path/to/your/package.changes I fully understand if you do not want to do that. I am just mentioning the option, in case you might find it useful. The two most recent occasions for me are a) dep5-copyright-license-name-not-unique cf. to https://lists.debian.org/debian-mentors/2015/03/msg00029.html for a discussion and subsequent bug from Charles Plessy (#779676) Indeed, there is a separate bug for that tag, so lets keep the discussion about that there. b) dep5-file-paragraph-reference-header which I now receive after fixing the previous error. Do your Header-paragraph contain a license field and does a Files-paragraph reference the license of that field? That seems to be what this is checking for. I tried to understand the first sentence of the long description, but failed: One of the file paragraph reference in the license field a standalone license defined in the header paragraph. Also the second sentence is very long and quite difficult to understand (at least for non native speakers). Yes, the description is some what difficult to read. The source of your woes are caused by several issues combined. In my opinion two actions should resolve this issue: a) Provide lintian to unstable *before* using it to check uploaded packages. This enables maintainers to upload lintian clean packages. Generally, we do that. Though in some cases, we do rapid deploys to lintian.d.o for updating the reporting framework. This time, we had a nasty issue where the reporting framework suffered from out of memory issues causing parts of it to fail. This is the reason why these checks are now live without being released. b) Spend a little more time for the description of the tag. c) Reword dep5-file-paragraph-reference-header, possibly using simpler english and several sentences. The tag descriptions were drafted by a person with dyslexia. Under normal circumstances, the new tag descriptions are sent to review on debian-l18n(-english?) prior to a release and they would assist with maturing the tag description. Though as explained above, in this particular case, the tags are live on the website prior to a release (and therefore, also a review). If you are unhappy with the tag descriptions, I am happy to revised descriptions. ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748781: Ok, here is a decent patch to build pcre16
I think I included everthing, I named the package libpcre16-3, per debian policy (I don't recall the section/paragraph right now). This is actually a complex library, also quite patched by us, so sorry if I missed something. While I was at it I also prepared a patch to enable pcre32, maybe there is (will be) some packages requiring/enjoying it. I'd not mind an upload to experimental, if you are ok. Thanks for maintaning (and adopting, for the new (coming) maintainer, CCed to get his input) pcre! -- regards, Mattia Rizzolo GPG Key: 4096R/B9444540 http://goo.gl/I8TMB more about me: http://mapreri.org Launchpad User: https://launchpad.net/~mapreri Ubuntu Wiki page: https://wiki.ubuntu.com/MattiaRizzolo From a20738d14889cdd67404fc01940792f660798130 Mon Sep 17 00:00:00 2001 From: Mattia Rizzolo mat...@mapreri.org Date: Sat, 7 Mar 2015 01:36:30 +0100 Subject: [PATCH 1/2] Add a libpcre16-3 package with the 16 bit pcre16 library (Closes: 748781). --- debian/changelog | 7 +++ debian/control | 14 +- debian/libpcre16-3.install | 1 + debian/rules | 2 ++ 4 files changed, 23 insertions(+), 1 deletion(-) create mode 100644 debian/libpcre16-3.install diff --git a/debian/changelog b/debian/changelog index 758a88c..e777147 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +pcre3 (2:8.35-3.4) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Add a libpcre16-3 package with the 16 bit pcre16 library (Closes: 748781). + + -- Mattia Rizzolo mat...@mapreri.org Sat, 07 Mar 2015 01:29:03 +0100 + pcre3 (2:8.35-3.3) unstable; urgency=medium * Non-maintainer upload. diff --git a/debian/control b/debian/control index d9f8c7d..2ed1936 100644 --- a/debian/control +++ b/debian/control @@ -59,7 +59,7 @@ Package: libpcre3-dev Section: libdevel Architecture: any Multi-Arch: same -Depends: libc6-dev, libpcre3 (= ${binary:Version}), libpcrecpp0 (= ${binary:Version}), ${misc:Depends} +Depends: libc6-dev, libpcre3 (= ${binary:Version}), libpcre16-3 (= ${binary:Version}), libpcrecpp0 (= ${binary:Version}), ${misc:Depends} Conflicts: libpcre1-dev, libpcre2-dev Description: Perl 5 Compatible Regular Expression Library - development files This is a library of functions to support regular expressions whose syntax @@ -92,3 +92,15 @@ Description: grep utility that uses perl 5 compatible regexes. . The other reason for the existence of pcregrep is that its source code is an example of programming with libpcre. + +Package: libpcre16-3 +Section: libs +Architecture: any +Depends: ${shlibs:Depends}, ${misc:Depends} +Multi-Arch: same +Pre-Depends: ${misc:Pre-Depends} +Description: Perl 5 Compatible Regular Expression Library - 16 bit runtime files + This is a library of functions to support regular expressions whose syntax + and semantics are as close as possible to those of the Perl 5 language. + . + This package contains the 16 bit runtime library. diff --git a/debian/libpcre16-3.install b/debian/libpcre16-3.install new file mode 100644 index 000..df85ecf --- /dev/null +++ b/debian/libpcre16-3.install @@ -0,0 +1 @@ +debian/tmp/usr/lib/*/libpcre16.so.* diff --git a/debian/rules b/debian/rules index 12d98bc..e953cdf 100755 --- a/debian/rules +++ b/debian/rules @@ -32,6 +32,7 @@ configure-stamp: --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) \ --enable-utf8 --enable-unicode-properties \ --disable-silent-rules \ + --enable-pcre16 \ $(shell . debian/jit-test) \ $(shell DEB_CFLAGS_MAINT_APPEND=-Wall DEB_BUILD_MAINT_OPTIONS=hardening=+all dpkg-buildflags --export=configure) touch configure-stamp @@ -112,6 +113,7 @@ binary-arch: build install dh_fixperms -a dh_makeshlibs -plibpcre3 --add-udeb=libpcre3-udeb -V 'libpcre3 (= 1:8.35)' dh_makeshlibs -plibpcrecpp0 -V 'libpcrecpp0 (= 7.7)' + dh_makeshlibs -plibpcre16-3 dh_installdeb -a # dh_perl -a dh_shlibdeps -a -ldebian/libpcre3/usr/lib/$(DEB_HOST_MULTIARCH) -- 2.1.4 From aece74f3497d25d298b9c0b069d9b280ca089af0 Mon Sep 17 00:00:00 2001 From: Mattia Rizzolo mat...@mapreri.org Date: Sat, 7 Mar 2015 02:01:21 +0100 Subject: [PATCH 2/2] Add a libpcre32-3 package with the 32 bit pcre32 library. --- debian/changelog | 1 + debian/control | 14 +- debian/libpcre32-3.install | 1 + debian/rules | 3 ++- 4 files changed, 17 insertions(+), 2 deletions(-) create mode 100644 debian/libpcre32-3.install diff --git a/debian/changelog b/debian/changelog index e777147..d256414 100644 --- a/debian/changelog +++ b/debian/changelog @@ -2,6 +2,7 @@ pcre3 (2:8.35-3.4) UNRELEASED; urgency=medium * Non-maintainer upload. * Add a libpcre16-3 package with the 16 bit pcre16 library (Closes: 748781). + * Add a libpcre32-3 package with the 32 bit pcre32 library. -- Mattia Rizzolo mat...@mapreri.org Sat, 07 Mar 2015 01:29:03 +0100 diff --git a/debian/control b/debian/control index
Bug#745901: fglrx-driver: fglrx update crashes totem, gdm, gnome-session and anything that uses clutter
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there I'm hoping you know whats up and can point me in the right direction... The Problem: The problem i am having is when it says swell-foop: symbol lookup error: /usr/lib/fglrx/fglrx-libglx.so: undefined symbol: xf86Screens Below is the output from my shell before and after .. I'm hoping you'll just know what it is, i think it's the same bug i saw somewhere something about a sim link ... but was unsure where or what was being pointed at... in any-case i hope this makes sense to you ... So First before the commands whatsis@debian8:~$ swell-foop (swell-foop:14382): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' failed (swell-foop:14382): Clutter-CRITICAL **: Unable to initialize Clutter: The OpenGL version could not be determined ** (swell-foop:14382): WARNING **: swell-foop.vala:452: Failed to initialise Clutter whatsis@debian8:~$ Then whatsis@debian8:~$ export COGL_DRIVER=gl whatsis@debian8:~$ export COGL_OVERRIDE_GL_VERSION=4.4 whatsis@debian8:~$ export COGL_RENDERER=GLX whatsis@debian8:~$ export LD_PRELOAD=/usr/lib/fglrx/fglrx-libglx.so whatsis@debian8:~$ swell-foop swell-foop: symbol lookup error: /usr/lib/fglrx/fglrx-libglx.so: undefined symbol: xf86Screens whatsis@debian8:~$ I guess i should mention that i run enlightenment sparky linux which is testing. Thank you for your time, Jesse B. R. On Sat, 03 May 2014 18:26:51 +0200 Tobias Hansen than...@debian.org wrote: Comment 4 from [1] has a workaround that lets you use GNOME and fglrx together. I had to switch to lightdm since gdm3 doesn't work and use this ~/.xsession: export COGL_DRIVER=gl export COGL_OVERRIDE_GL_VERSION=1.4 export COGL_RENDERER=GLX export LD_PRELOAD=/usr/lib/x86_64-linux-gnu/fglrx/fglrx-libGL.so.1.2 gnome-session Note that this will link everything run under the session with the GL library. See [1] for further explanation. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1054435#c4 Cheers, Tobias -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJU+nqTAAoJEPhJCDCVodHZrpQP/izGTGfc0lQd+OGzl98Qpr8x 6DejO9JxbE2aj/P/2HDh+vnA5R0EpqtK65JJGoTYHmifff+N6qXDN+BYaRSra502 2pa45BKeliNv9kihqwoCbsvsGOkYW6n1hLGsPxRnj0jYWYWpQQGLUIxVa+JvLkqj xUzLpKqMpRiJP8gabVoeFduWmWc9gywuyVazzmJ6XiYDe2tUb20d+XSJfT6Y3Irt uoCQIZDp3uOLtmJ7cSaXRJhTQQEV/X8t2VxgHvyRTfKv4xtEhTOtNpzcfR2TWLiP sHhy/DPt0Vx8Xa3W0EHdtGkji5W7ZYArhxgci/gA2bMMjwRFcFuEVzsO8Zp7dq+d FdcgPkV6jUbhn2BawfuTsSC160z1dXwjlbtxfl3GskJVSv5J5d+1Gy6oLf9sox7Q Thacwtr81Mpcgei41ZUV1r/jGiGfc05ZMhvlUwlNlpK0E4qEHkY1e3MaZsQRlm93 OKO59iPwboQSwfhM83/LaczSpFcho77YvpT4y8oVlZVh2lKC9q8/QNFUYVux/0eL pAxQ/MZceaIPkt0GAR2YT5784kV5KAcR64AOTbSL9gSEx3ckOOtYt9wLBrxhXKjt tlhZ1MoV37PbQrvI9ZMlQ6BGhzrhpQ9J4FvyneX4aGhvarlQ//n6BkV3bJ4rp2CJ PDg7WO8hoT6u5mI1bHZ7 =6wN/ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779904: ITP: c -- Compile and execute C scripts in one go!
Package: wnpp Severity: wishlist Compile and execute C scripts in one go! https://github.com/ryanmjacobs/c
Bug#779906: evince: segfault viewing result of Print to File from #768133 reproducer
Package: evince Version: 3.14.1-2 Severity: normal I encountered this while testing the proposed patch for #768133, but this bug seems less bad than #768133 (printing to an actual printer is unaffected) so I'm going to upload anyway... If I open the reproducer attached to #768133 and Print to File in PS format, I get the attached Postscript file (I have compressed it, the original was uncompressed). Viewing that Postscript works in gv but crashes evince. Printing the same PDF from #768133 to a real printer (HP Color LaserJet 2605dtn) instead of printing to file is fine now that the commit causing #768133 has been reverted. This might well be a Cairo or Pixman bug, the actual crash is in libpixman and there's a lot of Cairo in the stack trace. Stack, with as many debug symbols as I could conveniently install (I didn't recompile anything with nostrip): #0 bits_image_fetch_separable_convolution_affine (repeat_mode=PIXMAN_REPEAT_NONE, format=PIXMAN_x8r8g8b8, convert_pixel=optimized out, mask=0x0, buffer=0x7fff91cfba80, width=optimized out, line=optimized out, offset=optimized out, image=0x19eb380) at ../../pixman/pixman-fast-path.c:2813 #1 bits_image_fetch_separable_convolution_affine_none_x8r8g8b8 (iter=0x7fff91cfb960, mask=0x0) at ../../pixman/pixman-fast-path.c:3153 #2 0x7ffa94c6dd43 in general_composite_rect (imp=0x1377d50, info=optimized out) at ../../pixman/pixman-general.c:211 #3 0x7ffa94c21711 in pixman_image_composite32 (op=op@entry=PIXMAN_OP_SRC, src=src@entry=0x19eb380, mask=mask@entry=0x0, dest=dest@entry=0x1997660, src_x=0, src_y=0, mask_x=0, mask_y=0, dest_x=0, dest_y=0, width=1149, height=686) at ../../pixman/pixman.c:707 #4 0x7ffa9b6698f5 in composite_boxes (_dst=optimized out, op=optimized out, abstract_src=optimized out, abstract_mask=optimized out, src_x=0, src_y=0, mask_x=0, mask_y=0, dst_x=0, dst_y=0, boxes=0x7fff91d021b0, extents=0x7fff91d0247c) at ../../../../src/cairo-image-compositor.c:538 #5 0x7ffa9b6a33dd in composite_aligned_boxes (boxes=optimized out, extents=optimized out, compositor=optimized out) at ../../../../src/cairo-spans-compositor.c:683 #6 clip_and_composite_boxes (compositor=0x7ffa9b94b140 spans, extents=0x7fff91d02440, boxes=0x7fff91d021b0) at ../../../../src/cairo-spans-compositor.c:882 #7 0x7ffa9b6a393e in clip_and_composite_boxes (compositor=0x7ffa9b94b140 spans, extents=0x7fff91d02440, boxes=0x7fff91d021b0) at ../../../../src/cairo-spans-compositor.c:901 #8 0x7ffa9b6a3a59 in _cairo_spans_compositor_paint (_compositor=0x7ffa9b94b140 spans, extents=0x7fff91d02440) at ../../../../src/cairo-spans-compositor.c:983 #9 0x7ffa9b65eb69 in _cairo_compositor_paint (compositor=0x7ffa9b94b140 spans, surface=0x19eb090, op=optimized out, source=optimized out, clip=optimized out) at ../../../../src/cairo-compositor.c:65 #10 0x7ffa9b6a6b31 in _cairo_surface_paint (surface=0x19eb090, op=CAIRO_OPERATOR_SOURCE, source=0x7fff91d027b0, clip=0x0) at ../../../../src/cairo-surface.c:2091 #11 0x7ffa9b6ab882 in _cairo_surface_offset_paint (target=target@entry=0x19eb090, x=optimized out, y=49, op=op@entry=CAIRO_OPERATOR_SOURCE, source=0x7fff91d027b0, source@entry=0x7fff91d032b0, clip=clip@entry=0x0) at ../../../../src/cairo-surface-offset.c:85 #12 0x7ffa9b6d31a8 in render_pattern (dst=optimized out, pattern=0x7fff91d032b0, is_mask=optimized out, extents=0x7fff91d0326c, src_x=0x7fff91d02b0c, src_y=0x7fff91d02b10) at ../../../../src/cairo-xlib-source.c:305 #13 0x7ffa9b6d4003 in _cairo_xlib_source_create_for_pattern (_dst=0x19de570, pattern=0x7fff91d032b0, is_mask=1854795792, extents=0x1fc719, sample=0x7fff91d03290, src_x=0x7fff91d02b0c, src_y=0x7fff91d02b10) at ../../../../src/cairo-xlib-source.c:1159 #14 0x7ffa9b6b9a21 in composite_aligned_boxes (boxes=optimized out, extents=optimized out, compositor=optimized out) at ../../../../src/cairo-traps-compositor.c:1292 #15 clip_and_composite_boxes (compositor=0x7ffa9b94c480 compositor, extents=0x7fff91d03230, boxes=0x7fff91d02fa0) at ../../../../src/cairo-traps-compositor.c:1792 #16 0x7ffa9b6b9ed9 in clip_and_composite_boxes (compositor=0x7ffa9b94c480 compositor, extents=0x7fff91d03230, boxes=0x7fff91d02fa0) at ../../../../src/cairo-traps-compositor.c:1742 #17 0x7ffa9b6ba575 in _cairo_traps_compositor_paint (_compositor=0x7ffa9b94c480 compositor, extents=0x7fff91d03230) at ../../../../src/cairo-traps-compositor.c:2063 #18 0x7ffa9b65eb69 in _cairo_compositor_paint (compositor=0x7ffa9b94c480 compositor, surface=0x19de570, op=optimized out, source=optimized out, clip=optimized out) at ../../../../src/cairo-compositor.c:65 #19 0x7ffa9b6a6b31 in _cairo_surface_paint (surface=0x19de570, op=CAIRO_OPERATOR_OVER, source=0x7fff91d03570, clip=0x19c51a0) at ../../../../src/cairo-surface.c:2091 #20 0x7ffa9be7 in _cairo_gstate_paint (gstate=0x192f200) at ../../../../src/cairo-gstate.c:1067 #21 0x7ffa9b6595c5 in INT_cairo_paint
Bug#779902: /tmp can be mounted as tmpfs against user's will
Control: found -1 215-12 Control: tag -1 confirmed Ça va Didier, Didier Roche [2015-03-06 9:36 +0100]: In debian, tmp.mount is disabled through a distro-patch by default. It means we don't want user's system to get /tmp on tmpfs without explicit enablement (either by enabling tmp.mount unit or via fstab). We noticed that starting an unit using PrivateTmp=yes will pull tmp.mount (which mounts /tmp on tmpfs) in its requirements chain (even if this unit is condition fail). Confirmed. systemctl start colord or systemd-timesyncd will start tmp.mount and thus overmount the existing /tmp in the running system. I reproduced that in a clean sid VM (with LXDE, but I suppose that doesn't matter much). We need to find a way to ensure that tmp.mount is never accidentally trigger, while still enabling the user using fstab to enable /tmp as tmpfs. Enabling the unit to get the same effect would be a nice addition. I dislike masking it, as that will most probalby lead to problems with units which have a Requires=tmp.mount (directly or indirectly), these would block on a masked unit. I think the best way forward is to either not ship the unit at all and document in README.Debian to add /tmp as tmpfs in fstab [1], or ship it in /usr/share/doc/systemd/ as an example, and document how to enable it from there. Michael, WDYT? Thanks, Martin [1] I have none /tmp tmpfs defaults 0 0 in fstab -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779717: FATAL:isolate_holder.cc(70)] Couldn't mmap v8 natives data file
Jason, could you please put the unofficial package somewhere to test it? -- Sergio Fernández http://www.wikier.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779907: evince: enable libgnome-desktop post-jessie
On Fri, Mar 06, 2015 at 09:20:45AM +, Simon McVittie wrote: Package: evince Version: 3.14.1-2 Severity: wishlist Tags: patch Iain Lane enabled libgnome-desktop support in evince/unstable svn after 3.14.1-1 was uploaded. I reverted that change to be able to commit 3.14.1-2 with #768133 fixed, without introducing unapproved changes during the freeze. I assume there was some reason to want libgnome-desktop support, although I don't know what concrete feature(s) this enables. After jessie, someone (Iain?) should probably reinstate that change; I'm filing it as a bug to keep it on the radar. Sure. I'll try to remember, but if I forget someone else should feel free to do the same. FWIW, the feature is that it enables evince to use the GNOME thumbnail cache in its 'recent' view instead of computing them each time. https://developer.gnome.org/gnome-desktop3/stable/GnomeDesktopThumbnailFactory.html Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] signature.asc Description: Digital signature
Bug#779929: evolution: does not mark the selected mail as read
Package: evolution Version: 3.12.9~git20141130.241663-1+b1 Severity: normal If Inbox or any other folder contains only one message, Evolution does not mark the selected mail as read. I need to hit CTRL+K or double click to mark the selected mail as read. Thanks Edy -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages evolution depends on: ii dbus 1.8.16-1 ii debconf [debconf-2.0] 1.5.55 ii evolution-common 3.12.9~git20141130.241663-1 ii evolution-data-server 3.12.9~git20141128.5242b0-2+deb8u1 ii gnome-icon-theme 3.12.0-1 ii libatk1.0-02.14.0-1 ii libc6 2.19-15 ii libcamel-1.2-493.12.9~git20141128.5242b0-2+deb8u1 ii libclutter-gtk-1.0-0 1.6.0-1 ii libecal-1.2-16 3.12.9~git20141128.5242b0-2+deb8u1 ii libedataserver-1.2-18 3.12.9~git20141128.5242b0-2+deb8u1 ii libevolution 3.12.9~git20141130.241663-1+b1 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1 ii libical1a 1.0-1.3 ii libnotify4 0.7.6-2 ii libsoup2.4-1 2.48.0-1 ii libwebkitgtk-3.0-0 2.4.8-1 ii libxml22.9.1+dfsg1-5 ii psmisc 22.21-2 Versions of packages evolution recommends: ii bogofilter 1.2.4+dfsg1-3 ii evolution-plugins 3.12.9~git20141130.241663-1+b1 ii yelp 3.14.1-1 Versions of packages evolution suggests: pn evolution-ews none pn evolution-plugins-experimental none ii gnupg 1.4.18-6 ii network-manager 0.9.10.0-6 -- debconf information: evolution/needs_shutdown: evolution/kill_processes: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779928: expect: unbuffer fails on long lines
Package: expect Version: 5.45-6 $ perl -e 'print ((x x 5000 . \n) x 3);' | cat | wc 3 3 15003 $ perl -e 'print ((x x 5000 . \n) x 3);' | unbuffer -p cat | wc 1 1 906 It doesn't just truncate the long line; it loses the rest of the output. If this is a hard-to-avoid limitation please document it in the man page. It might have saved me some time if I'd known. Thanks. (What I was trying to do was attach a timestamp to each line in the output from sbuild. Any suggestions?) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779930: git-buildpackage: git-pbuilder does not honor --help
Package: git-buildpackage Version: 0.6.22 Severity: normal Dear Maintainer, git-pbuilder does not recognize --help and proceed anyway: $ git-pbuilder --verbose --help; echo $? Base directory /var/cache/pbuilder/base.cow does not exist 1 $ I would expect a command line usage or the man page output. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 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) Versions of packages git-buildpackage depends on: ii devscripts2.15.1 ii git 1:2.1.4-2.1 ii man-db2.7.0.2-5 ii python2.7.8-3 ii python-dateutil 2.2-2 ii python-pkg-resources 5.5.1-1 Versions of packages git-buildpackage recommends: ii cowbuilder0.73 ii pristine-tar 1.33 Versions of packages git-buildpackage suggests: ii python-notify 0.1.1-4 ii unzip 6.0-16 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656303: business proposal!
I have a business offer for you. Contact for more details.josephwong...@hotmail.com Regard.HK -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778045: add patch
Control: tags -1 + patch patch at http://launchpadlibrarian.net/199525513/openldap_2.4.31-1%2Bnmu2ubuntu11_2.4.31-1%2Bnmu2ubuntu12.diff.gz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779789: mpv: free(): invalid pointer: 0xedf28020 ***
On mer, mar 04, 2015 at 08:12:49 +0100, Jakub Wilk wrote: Package: mpv Version: 0.8.2-1 mpv crashes on the attached file: $ mpv crash.mp4 Playing: crash.mp4 [libav/video] h264: AVC: nal size 889 [libav/video] h264: no frame! [libav/demuxer] mov,mp4,m4a,3gp,3g2,mj2: stream 0, offset 0x8c69: partial file (+) Video --vid=1 (*) (h264) File tags: Title: 860240514032667 Opening video filter: [expand aspect=1440/900] [expand] Expand: -1 x -1, -1 ; -1, aspect: 1.60, round: 1 [libav/video] h264: AVC: nal size 889 [libav/video] h264: AVC: nal size 889 [libav/video] h264: no frame! VO: [xv] 3642x720 = 3642x2276 yuv420p V: 00:00:00 / 00:00:15 (0%) Exiting... (End of file) *** Error in `mpv': free(): invalid pointer: 0xedf28020 *** Aborted I can't reproduce. Could you please also provide a backtrace (with both mpv and libav debug symbols)? It would also be nice if you could test the package in experimental that uses ffmpeg instead of libav. Cheers signature.asc Description: Digital signature
Bug#775079: Python/YAML needs support for installing files distributed in g-d-p
Can we close this metabug ? I guess work has been done for a while. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777461: add patch
Control: tags -1 + patch thanks for the upstream pointer http://launchpadlibrarian.net/199525564/ncurses_5.9%2B20140712-2ubuntu1_5.9%2B20140712-2ubuntu2.diff.gz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779851: cryptmount: Cannot mount as non-root user
Hello. On Thu, Mar 05, 2015 at 08:08:40PM +, R.Penney wrote: Hello Gilles, Thanks for your bug report about cryptmount, and the helpful reference to bug #759263. I've just re-run the cryptmount test-suite on my Jessie test system, and all the tests seem to pass. I suspect this means that the problem you're having is not related to bug #759263, which was caught by the test-suite. From your description, I'm guessing that your encrypted filesystem may live on a network share (mounted under /home/gilles/mnt ?). The device is a actually a remote file that is accessed through sshfs. And I've just found out what was the cause of the problem: only the user who mounted the sshfs directory can access its content. Thus, when cryptmount was trying to perform part of its duty as root, the contents was indeed unreadable! When using the -o allow_root option of sshfs, no problem anymore. So, this was my mistake; sorry for the noise. This isn't a use-case that I've tried, especially with LUKS encrypted filesystems, and I'm not sure whether it's an intended use-case for libcryptsetup. I'm attaching the steps I followed, in case you might be interested to add it as documentation for another possible use-case (I intended to use it for simple backup purpose). Best regards, Gilles Encrypted filesystem on a remote host using cryptmount (A) Assumptions * Remote machine is called rmach * User login on the local machine is luser * User login on the remote machine is ruser * No firewall (otherwise an error read: connection reset by peer can occur). * SSH public key of user luser is present in ~ruser/.ssh/authorized_keys on rmach * User luser is a member of the fuse group, to allow reading of /etc/fuse.conf * Option user_allow_other is enabled in /etc/fuse.conf (B) Preparing a virtual device (operations to be performed once) The following must be performed as the ordinary user on the local machine. 1. Mount the remote home on the local machine: $ mkdir -p mnt/remote $ sshfs ruser@rmach: mnt/remote 2. Create a 100 GB (sparse) file that will contain the filesystem: $ cd mnt/remote $ truncate -s 100G virtual_disk.img 3. Release the mount point: $ cd $ fusermount -u mnt/remote 4. Define a mount point whose contents will be stored encrypted, e.g. $ mkdir enc_remote The following must be performed as root on the local machine. 5. Create an entry in /etc/cryptmount/cmtab luser_data { dev=/home/luser/mnt/remote/virtual_disk.img dir=/home/luser/enc_remote loop=auto fstype=ext4 mountoptions=defaults cipher=aes-cbc-plain keyformat=luks } 6. Mount the remote filesystem: # cd ~luser # sshfs -o IdentityFile=~luser/.ssh/id_rsa ruser@rmach: mnt/remote 7. Prepare the encrypted device (setting the password to access the encrypted filesystem data): # cryptmount --prepare luser_data 8. Create the filesystem (must be same as defined in the cmtab entry) # mkfs.ext4 /dev/mapper/luser_data # chown luser.luser 9. Finalize: # cryptmount --release luser_data 10. Mount encrypted filesystem in order to set appropriate ownership: # cryptmount luser_data # chown luser.luser /home/luser/enc_remote 11. Release all resources: # cryptmount -u luser_data # fusermount -u mnt/remote (C) Saving data to the remote encrypted filesystem 1. Mounting the remote home (as an ordinary user): $ sshfs -o allow_root ruser@rmach: mnt/remote 2. Mounting the encrypted filesystem (password will be requested): $ cryptmount luser_data 3. Checking the available space on the encrypted filsystem: $ df -k enc_remote
Bug#779936: empathy: Jabber did not connect to several servers.
Package: empathy Version: 3.12.7-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** I use Debian 8 and Gnome. If i konfigure empathy with jabber (my own server and jabber.org) both doesn't connect. Empathy say that the password is wrong, but it isn't. It depends both accounts. *** End of the template - remove these template lines *** -- 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.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages empathy depends on: ii dbus-x11 1.8.16-1 ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii empathy-common 3.12.7-1 ii geoclue-2.0 2.1.10-2 ii gnome-icon-theme 3.12.0-1 ii gsettings-desktop-schemas3.14.1-1 ii gstreamer1.0-pulseaudio 1.4.4-2 ii libc62.19-15 ii libcairo21.14.0-2.1 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libchamplain-0.12-0 0.12.9-1 ii libchamplain-gtk-0.12-0 0.12.9-1 ii libcheese-gtk23 3.14.1-2 ii libclutter-1.0-0 1.20.0-1 ii libclutter-gst-2.0-0 2.0.12-1 ii libclutter-gtk-1.0-0 1.6.0-1 ii libcogl-path20 1.18.2-3 ii libcogl201.18.2-3 ii libdbus-glib-1-2 0.102-1 ii libenchant1c2a 1.6.0-10.1 ii libfarstream-0.2-2 0.2.4-1 ii libfolks-telepathy25 0.10.0-1 ii libfolks25 0.10.0-1 ii libgcr-base-3-1 3.14.0-2 ii libgcr-ui-3-13.14.0-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libgee-0.8-2 0.16.1-1 ii libgeocode-glib0 3.14.0-1 ii libglib2.0-0 2.42.1-1 ii libgnutls-deb0-283.3.8-5 ii libgoa-1.0-0b3.14.2-1 ii libgstreamer-plugins-base1.0-0 1.4.4-2 ii libgstreamer1.0-01.4.4-2 ii libgtk-3-0 3.14.5-1 ii libgudev-1.0-0 215-12 ii libmission-control-plugins0 1:5.16.3-1 ii libnotify4 0.7.6-2 ii libpango-1.0-0 1.36.8-3 ii libpulse-mainloop-glib0 5.0-13 ii libpulse05.0-13 ii libsecret-1-00.18-1+b1 ii libsoup2.4-1 2.48.0-1 ii libtelepathy-farstream3 0.6.2-1 ii libtelepathy-glib0 0.24.1-1 ii libtelepathy-logger3 0.8.1-1 ii libwayland-server0 1.6.0-2 ii libwebkitgtk-3.0-0 2.4.8-1 ii libx11-6 2:1.6.2-3 ii libxml2 2.9.1+dfsg1-5 ii telepathy-logger 0.8.1-1 ii telepathy-mission-control-5 1:5.16.3-1 Versions of packages empathy recommends: ii gvfs-backends1.22.2-1 ii sound-theme-freedesktop 0.8-1 ii telepathy-gabble 0.18.3-1+b1 ii telepathy-haze 0.8.0-2 ii telepathy-salut 0.8.1-4 Versions of packages empathy suggests: ii telepathy-idle 0.2.0-2 ii vino3.14.0-2+b1 Versions of packages empathy is related to: ii telepathy-gabble [telepathy-connection-manager] 0.18.3-1+b1 ii telepathy-haze [telepathy-connection-manager]0.8.0-2 ii telepathy-idle [telepathy-connection-manager]0.2.0-2 ii telepathy-rakia [telepathy-connection-manager] 0.8.0-3 ii telepathy-salut [telepathy-connection-manager] 0.8.1-4 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779873: mariadb-server-core-10.0: missing breaks+replaces mysql-client-5.[56] for /usr/bin/innochecksum takeover
On 2015-03-06 15:47, Otto Kekäläinen wrote: Cool, I didn't know that piuparts also test mysql-mariadb migration scenarios. Issue fixed in git now. I don't test migration (but maybe that could be done as well somehow), but co-installability of packages sharing some files. (But for the issues that occur on carefully crafted upgrade paths, I usually just use the piuparts templates.) Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779935: linux: Patch missing from armhf simplefb backport
Source: linux Version: 3.16.7-ckt7-1 Severity: normal Hi, Simplefb support was recently backported to Debian's 3.16 kernel, including a patch series based on those shown at the top of this log: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?qt=rangeq=8284731e but unfortunately one of those patches is missing: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ba168a3c This would be useful to include because it initialises simplefb earlier in the boot sequence, so that earlier kernel messages can be printed to that console. This can be invaluable on devices with HDMI/LCD displays but without a serial console. Hans de Goede agreed it would be a good idea: http://www.mail-archive.com/linux-sunxi@googlegroups.com/msg10362.html Please could this patch be included? Thanks very much, B.R. Oake. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 3.16.0-4-armmp (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777919: add patch
Control: tags -1 + patch note that some other build issues are fixed as well: * Use dpkg-buildflags. * Really build findchip and smcinit on i386. patch at http://launchpadlibrarian.net/199528674/irda-utils_0.9.18-12ubuntu1_0.9.18-12ubuntu2.diff.gz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779937: GDP shouldn't process all yaml files all the time
Package: game-data-packager Version: 39 Severity: minor Dear Maintainer, When a user ask GDP to package some game, GDP will read _all_ yaml files. As the number of supported games rises, it gets worse. Running GDP without any argument also takes a very long time; users may think it has hanged. -- pi@raspberrypi ~/game-data-packager $ time ./run /dev/null real0m25.045s user0m24.950s sys 0m0.080s pi@raspberrypi ~/game-data-packager $ time ./run spear INFO:game-data-packager:downloading http://localhost/sodemo.zip generated /home/pi/game-data-packager/spear-of-destiny-demo-data_40_all.deb it is recommended to also install this game engine: wolf4sdl real0m29.888s user0m29.360s sys 0m0.300s pi@raspberrypi ~/game-data-packager $ rm out/*.yaml pi@raspberrypi ~/game-data-packager $ cp data/spear-of-destiny.yaml out/ pi@raspberrypi ~/game-data-packager $ time ./run spear INFO:game-data-packager:downloading http://localhost/destiny.zip generated /home/pi/game-data-packager/spear-of-destiny-demo-data_40_all.deb it is recommended to also install this game engine: wolf4sdl real0m6.091s user0m5.560s sys 0m0.310s -- System Information: Distributor ID: Raspbian Description:Raspbian GNU/Linux 8.0 (jessie) Release:8.0 Codename: jessie Architecture: armv7l Kernel: Linux 3.18.7-v7+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779902: /tmp can be mounted as tmpfs against user's will
Am 06.03.2015 um 10:10 schrieb Martin Pitt: Control: found -1 215-12 Control: tag -1 confirmed Ça va Didier, Didier Roche [2015-03-06 9:36 +0100]: In debian, tmp.mount is disabled through a distro-patch by default. It means we don't want user's system to get /tmp on tmpfs without explicit enablement (either by enabling tmp.mount unit or via fstab). We noticed that starting an unit using PrivateTmp=yes will pull tmp.mount (which mounts /tmp on tmpfs) in its requirements chain (even if this unit is condition fail). Confirmed. systemctl start colord or systemd-timesyncd will start tmp.mount and thus overmount the existing /tmp in the running system. I reproduced that in a clean sid VM (with LXDE, but I suppose that doesn't matter much). The odd thing though is, that PrivateTmp=yes does not trigger the start of tmp.mount during boot at least on all the test systems I have. Do we know, why that is? A Required=tmp.mount should always start the referenced unit, but it seemingly doesn't. We need to find a way to ensure that tmp.mount is never accidentally trigger, while still enabling the user using fstab to enable /tmp as tmpfs. Enabling the unit to get the same effect would be a nice addition. I dislike masking it, as that will most probalby lead to problems with units which have a Requires=tmp.mount (directly or indirectly), these would block on a masked unit. I think the best way forward is to either not ship the unit at all and document in README.Debian to add /tmp as tmpfs in fstab [1], or ship it in /usr/share/doc/systemd/ as an example, and document how to enable it from there. Michael, WDYT? This would also mean, to revert the existing work to migrate the RAMTMP=yes setting and clean up existing symlinks. Not really a fan of that, tbh. I think, PrivateTmp=yes pulling in tmp.mount is a bug and I would simply revert b46a529c [1] or replace unit_require_mounts_for with a After dependency [2] only. Michael [1] http://cgit.freedesktop.org/systemd/systemd/commit/?id=b46a529c [2] http://cgit.freedesktop.org/systemd/systemd/tree/src/core/mount.c#n265 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#779919: usb-modeswitch: IOMMU in BIOS not handled properly
Am 06.03.2015 um 13:35 schrieb William Melgaard: Although the USB-2 mouse and keyboard are dealt with effectively with IOMMU enabled, there are ~550 lines of page fault reported by dmesg at bootup. Further investigaiton finds that failure to access the northbridge (AMD 970 chip) USB-3 support is the cause of the page faults. usb_modeswitch is not involved in the standard boot process unless a USB device with multiple modes is attached, mainly 3G/4G modem or Wifi sticks. If this is not the case with your system, then I think your problem is rather related to the Linux kernel. Regards, Josua Dietze -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779931: sk_disk_check_sleep_mode: Operation not supported for USB3 HDD docking based on JMicron 152d:0551
Package: libatasmart4 Version: 0.19-3 Severity: grave Justification: causes non-serious data loss Dear Maintainer, I bought a new HDD docking station (for 2 HDDs) based on JMicron JMB551 chipset but I discover an issue that could cause data loss. If I mount some partitions of 2 HDDs connected to my laptop via USB 3.0 using this docking station all works fine until the JMBB551 go in sleep mode. This kind of docking station, in fact, have an intelligent sleep function that put the HDDs in sleep mode when there aren't R/W data operations for at least 5 minutes. Every 10 minutes udisksd control the state of SMART attributes of the attached HDDs but when the docking is in sleep mode we notice the error sk_disk_check_sleep_mode: Operation not supported and the USB connection to the docking is resetted as you can see in the next udisksd log: 14:37:52.873:[3496]:[NOTICE]: udisks daemon version 2.1.3 starting [main.c:146, main()] 14:37:52.874:[3496]:[DEBUG]: Entering main event loop [main.c:171, main()] 14:37:52.885:[3496]:[INFO]: Initialization (device probing) [udiskslinuxprovider.c:445, udisks_linux_provider_start()] 14:37:52.900:[3496]:[INFO]: Initialization (coldplug 1/2) [udiskslinuxprovider.c:457, udisks_linux_provider_start()] 14:37:52.900:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop0 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.902:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop1 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.902:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop2 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.903:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop3 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.903:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop4 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.904:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop5 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.904:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop6 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.905:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop7 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.905:[3496]:[DEBUG]: uevent add /sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.907:[3496]:[DEBUG]: uevent add /sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.908:[3496]:[DEBUG]: uevent add /sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda2 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.909:[3496]:[DEBUG]: uevent add /sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda3 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.910:[3496]:[DEBUG]: uevent add /sys/devices/pci:00/:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sr0 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.911:[3496]:[INFO]: Initialization (coldplug 2/2) [udiskslinuxprovider.c:457, udisks_linux_provider_start()] 14:37:52.911:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop0 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.911:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop1 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.912:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop2 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.912:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop3 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.912:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop4 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.913:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop5 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.913:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop6 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.913:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop7 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.914:[3496]:[DEBUG]: uevent add /sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.914:[3496]:[DEBUG]: uevent add /sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()] 14:37:52.915:[3496]:[DEBUG]: uevent add
Bug#779789: mpv: free(): invalid pointer: 0xedf28020 ***
* Alessandro Ghedini gh...@debian.org, 2015-03-06, 15:05: $ mpv crash.mp4 Playing: crash.mp4 [libav/video] h264: AVC: nal size 889 [libav/video] h264: no frame! [libav/demuxer] mov,mp4,m4a,3gp,3g2,mj2: stream 0, offset 0x8c69: partial file (+) Video --vid=1 (*) (h264) File tags: Title: 860240514032667 Opening video filter: [expand aspect=1440/900] [expand] Expand: -1 x -1, -1 ; -1, aspect: 1.60, round: 1 [libav/video] h264: AVC: nal size 889 [libav/video] h264: AVC: nal size 889 [libav/video] h264: no frame! VO: [xv] 3642x720 = 3642x2276 yuv420p V: 00:00:00 / 00:00:15 (0%) Exiting... (End of file) *** Error in `mpv': free(): invalid pointer: 0xedf28020 *** Aborted I can't reproduce. Could you try with these options? -vo=xv -vf=expand=1440/900 Apparently they are needed to trigger the crash. I forgot I had them in my mpv.conf. Could you please also provide a backtrace (with both mpv and libav debug symbols)? Here it is: #0 0xf763d425 in __kernel_vsyscall () #1 0xf5b9d307 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #2 0xf5b9e9c3 in __GI_abort () at abort.c:89 #3 0xf5bdb6f8 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0xf5cd165c *** Error in `%s': %s: 0x%s ***\n) at ../sysdeps/posix/libc_fatal.c:175 #4 0xf5be176a in malloc_printerr (action=optimized out, str=0xf5ccd172 free(): invalid pointer, ptr=0xedf28020) at malloc.c:4996 #5 0xf5be23bd in _int_free (av=0x80808080, p=optimized out, have_lock=0) at malloc.c:3840 #6 0xf7720de2 in m_refcount_unref (ref=0xf87cc910) at ../video/mp_image.c:102 #7 0xf7758736 in ta_free (ptr=0xf87c4970) at ../ta/ta.c:259 #8 0xf77228f2 in unref_image (ptr=0xf87c4970) at ../video/mp_image_pool.c:109 #9 0xf7720de2 in m_refcount_unref (ref=0xf87cc7f0) at ../video/mp_image.c:102 #10 0xf7758736 in ta_free (ptr=0xf88f4178) at ../ta/ta.c:259 #11 0xf774e451 in uninit (vo=0xf87ba090) at ../video/out/vo_xv.c:694 #12 0xf7741e72 in vo_thread (ptr=0xf87ba090) at ../video/out/vo.c:754 #13 0xf63daefb in start_thread (arg=0xefcfcb40) at pthread_create.c:309 #14 0xf5c5862e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129 Although Valgrind output might be more helpful, according to which an out-of-bounds write happens early on: ==2574== Invalid write of size 4 ==2574==at 0x482F85D: memset (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==2574==by 0x1CA7A0: memset (string3.h:84) ==2574==by 0x1CA7A0: memset_pic (memcpy_pic.h:57) ==2574==by 0x1CA7A0: mp_image_clear (mp_image.c:440) ==2574==by 0x1F86F6: allocate_xvimage (vo_xv.c:542) ==2574==by 0x1F86F6: reconfig (vo_xv.c:471) ==2574==by 0x1EA222: run_reconfig (vo.c:345) ==2574==by 0x16AD5F: mp_dispatch_queue_process (dispatch.c:197) ==2574==by 0x1EA535: vo_thread (vo.c:720) ==2574==by 0x5A87EFA: start_thread (pthread_create.c:309) ==2574==by 0x624162D: clone (clone.S:129) ==2574== Address 0xefbb000 is not stack'd, malloc'd or (recently) free'd It would also be nice if you could test the package in experimental that uses ffmpeg instead of libav. I'll try it later today. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779934: git-buildpackage: --git-pbuilder does not pass env variables such as DIST
Package: git-buildpackage Version: 0.6.22 Severity: important Dear Maintainer, I have several cow images and set the DIST env variable to easily switch between them. I found that `git-buildpackage --git-pbuilder` does not receive the DIST variable I have set: $ DIST=mydist git-buildpackage --git-pbuilder Building with cowbuilder for distribution sid ^^^--- wrong! The workaround is to use either: a) --git-builder=git-pbuilder`: $ git-buildpackage --git-builder=git-pbuilder building with cowbuilder for distribution mydist ^^--- good! b) --git-pbuilder --git-dist=mydist $ git-buildpackage --git-pbuilder --git-dist=mydist building with cowbuilder for distribution mydist ^^--- good! The function handling the --git-pbuilder command does not seem to pass the whole OS environement when invoking `git-pbuilder`. Unlike --git-builder which does pass the OS env. --git-dist should probably be set to default to whatever is provided in the DIST env variable. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 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) Versions of packages git-buildpackage depends on: ii devscripts2.15.1 ii git 1:2.1.4-2.1 ii man-db2.7.0.2-5 ii python2.7.8-3 ii python-dateutil 2.2-2 ii python-pkg-resources 5.5.1-1 Versions of packages git-buildpackage recommends: ii cowbuilder0.73 ii pristine-tar 1.33 Versions of packages git-buildpackage suggests: ii python-notify 0.1.1-4 ii unzip 6.0-16 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779933: python-qgis: fails to install, trying to overwrite other packages files: /usr/lib/python2.7/dist-packages/pyspatialite/dump.py
Package: python-qgis Version: 2.8.1+dfsg1-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package python-qgis. (Reading database ... 16341 files and directories currently installed.) Preparing to unpack .../python-qgis_2.8.1+dfsg1-1~exp1_amd64.deb ... Unpacking python-qgis (2.8.1+dfsg1-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/python-qgis_2.8.1+dfsg1-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/lib/python2.7/dist-packages/pyspatialite/dump.py', which is also in package python-pyspatialite 3.0.1-6 Errors were encountered while processing: /var/cache/apt/archives/python-qgis_2.8.1+dfsg1-1~exp1_amd64.deb cheers, Andreas python-qgis_2.8.1+dfsg1-1~exp1.log.gz Description: application/gzip
Bug#779873: [debian-mysql] Bug#779873: mariadb-server-core-10.0: missing breaks+replaces mysql-client-5.[56] for /usr/bin/innochecksum takeover
Cool, I didn't know that piuparts also test mysql-mariadb migration scenarios. Issue fixed in git now. Thanks for reporting! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779816: libmotif-dev should depend on libxt-dev
On 06/03/2015 08:29, Stephen Kitt wrote: Looking through all the headers in libmotif-dev, only headers from libx11-dev, libxft-dev and libxt-dev are included in header files provided by libmotif-dev, so you could provide a one-stop-shop with only these three extra dependencies. Thanks for doing this. I note that libxft-dev and libxt-dev both depend on libx11-dev. Do you think it would be safe to depend on libxft-dev and libxt-dev and rely on them pulling in libx11-dev, or is it better to explicitly depend on libx11-dev as well? Just out of interest, I tried to find the minimum extra dependencies (besides the current libmotif-dev) required to build all of the included demos. I managed to build most of them by only adding libxt-dev. The earth demo required libxext-dev as well. This method missed out libxft-dev though, but it is needed by Xm/TextFP.h. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779926: pu: package intel-microcode/1.20150121.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu I'd like to update the intel-microcode package in Wheezy to the latest available public Intel microcode. This intel-microcode release (20150121) has been tested in unstable and also Debian jessie for one month, without any error reports. It updates only the microcode for Intel Desktop/mobile Broadwell E0/F0 processors, such as the Core i7-5500U and a few others. It also updates the initramfs scripts, to decouple the intel-microcode and amd64-microcode packages. I will need this for a future stable update of amd64-microcode. These changes have been tested for oven one year in Debian unstable and Debian jessie, without issues. I've attached the abridged debdiff, without the upstream microcode changes. diffstat: changelog | 11 debian/changelog | 47 debian/initramfs.hook |2 debian/initramfs.init-premount | 19 microcode-20140913.dat |40694 microcode-20150121.dat |41591 + 6 files changed, 41663 insertions(+), 40701 deletions(-) Thank you. diff -Nru intel-microcode-1.20140913.1/changelog intel-microcode-1.20150121.1/changelog --- intel-microcode-1.20140913.1/changelog 2014-10-30 16:14:19.0 -0200 +++ intel-microcode-1.20150121.1/changelog 2015-02-11 20:32:44.0 -0200 @@ -1,3 +1,14 @@ +2015-01-21: + * Downgraded microcodes (to a previously shipped revision): +sig 0x000306f2, pf mask 0x6f, 2014-09-03, rev 0x0029, size 28672 + +2015-01-07: + * New Microcodes: +sig 0x000306d4, pf mask 0xc0, 2014-12-05, rev 0x0018, size 14336 + + * Updated Microcodes (this update is known to cause issues): +sig 0x000306f2, pf mask 0x6f, 2014-11-21, rev 0x002d, size 28672 + 2014-09-13: * New Microcodes: sig 0x000306f2, pf mask 0x6f, 2014-09-03, rev 0x0029, size 28672 diff -Nru intel-microcode-1.20140913.1/debian/changelog intel-microcode-1.20150121.1/debian/changelog --- intel-microcode-1.20140913.1/debian/changelog 2014-12-18 16:31:28.0 -0200 +++ intel-microcode-1.20150121.1/debian/changelog 2015-03-01 23:33:19.0 -0300 @@ -1,3 +1,50 @@ +intel-microcode (1.20150121.1) stable; urgency=high + + * New upstream microcode data file 20150121 ++ Downgraded microcodes (to a previously shipped revision): + sig 0x000306f2, pf mask 0x6f, 2014-09-03, rev 0x0029, size 28672 +* The microcode downgrade fixes a very nasty regression on Xeon E5v3 + processors (closes: #776431) + * critical urgency: the broken sig 0x306f2, rev 0x2b microcode shipped +in release 20150107 caused CPU core hangs and Linux boot failures. +The upstream fix was to downgrade it to the same microcode revision +that was shipped in release 20140913 + * source: remove superseded upstream data file: 20150107. + + -- Henrique de Moraes Holschuh h...@debian.org Fri, 30 Jan 2015 08:41:20 -0200 + +intel-microcode (1.20150107.1) stable; urgency=high + + * New upstream microcode data file 20150107 ++ New Microcodes: + sig 0x000306d4, pf mask 0xc0, 2014-12-05, rev 0x0018, size 14336 ++ Updated Microcodes: + sig 0x000306f2, pf mask 0x6f, 2014-11-21, rev 0x002d, size 28672 ++ High urgency: there are fast-tracked microcode updates in this + release which imply that critical errata are being fixed + (Broadwell Core i3/i5/i7 5th gen, Core M-5Y, Pentium 3805U, + Celeron 3755U, maybe others) + * source: remove superseded upstream data file: 20140913 + * initramfs: decouple from amd64-microcode: +Update the initramfs init-premount boot script to the script used in +intel-microcode 1.20130222.6 to 1.20130808.2, as well as all +intel-microcode 2.x packages. It has been throughoutly tested for +more than one year in unstable, testing (jessie), and +wheezy-backports. This new version of the boot script decouples +intel-microcode from amd64-microcode's boot script, and will trigger +a microcode update only when an Intel processor is installed. +amd64-microcode's boot script runs earlier, so this change will at +most cause a microcode update to be triggered twice (the kernel will +ignore the second attempt). Therefore, it is compatible with any +version of the amd64-microcode package. This change allows +amd64-microcode's boot script to also be updated to decouple itself +from intel-microcode. + * initramfs.hook: do not mix arrays and lists. +Avoid echo foo $@, use echo foo $* instead. This is unlikely +to be expĺoitable, but it makes ShellCheck happier. + + -- Henrique de Moraes Holschuh h...@debian.org Sun, 18 Jan 2015 19:17:01 -0200 + intel-microcode (1.20140913.1) stable; urgency=low * New upstream microcode data file 20140913 diff -Nru intel-microcode-1.20140913.1/debian/initramfs.hook
Bug#779927: ITP: node-osmium -- Osmium library Node.js bindings
Package: wnpp Severity: wishlist Owner: Bas Couwenberg sebas...@debian.org * Package name: node-osmium Version : 0.0~20150303-f074d94 Upstream Author : Osmium Developers d...@openstreetmap.org * URL : http://osmcode.org/node-osmium/ * License : BSL-1.0 Programming Lang: JavaScript Description : Osmium library Node.js bindings The osmium module for Node.js allows you to access some of the features of the Osmium Library from Javascript code. The Osmium library has extensive support for all types of OSM entities: nodes, ways, relations, and changesets. It allows reading from and writing to OSM files in XML and PBF formats, including change files and full history files. Osmium can store OSM data in memory and on disk in various formats and using various indexes. Its easy to use handler interface allows you to quickly write data filtering and conversion functions. Osmium can create WKT, WKB, OGR, GEOS and GeoJSON geometries for easy conversion into many GIS formats and it can assemble multipolygons from ways and relations. This package is part of the new Osmium family superseding the existing osmium source package. The new Osmium family consists of libosmium, node-osmium, pyosmium, osmium-tool, osmium-contrib osmcoastline. The packages for the Osmium family will be maintained in the Debian GIS team. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779919: usb-modeswitch: IOMMU in BIOS not handled properly
reassign -1 linux 3.16.7-ckt4-3 Le vendredi, 6 mars 2015, 07.35:44 William Melgaard a écrit : Dear Maintainer, * What led up to the situation? The default IOMMU setting in the BIOS for a GIGABYTE motherboard is off. Attempting to install a Debian system (Wheezy or Jessie AMD-64) with this setting results in not recognizing USB mouse or keyboard. However, booting with Squeeze or Wheezy 386 does work with this setting. * What exactly did you do (or not do) that was effective (or ineffective)? Turned on the IOMMU support * What was the outcome of this action? Although the USB-2 mouse and keyboard are dealt with effectively with IOMMU enabled, there are ~550 lines of page fault reported by dmesg at bootup. Further investigaiton finds that failure to access the northbridge (AMD 970 chip) USB-3 support is the cause of the page faults. * What outcome did you expect instead? Everything to work This has most likely nothing to do with usb-modeswitch, which doesn't handle the USB devices itself, but only ever through the Linux kernel. Hereby reassigning. Cheers, OdyX -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779932: ITP: pyosmium -- Osmium library bindings for Python
Package: wnpp Severity: wishlist Owner: Bas Couwenberg sebas...@debian.org * Package name: pyosmium Version : 0.0~20150204-298c708 Upstream Author : Osmium Developers d...@openstreetmap.org * URL : http://osmcode.org/pyosmium/ * License : BSD-2-Clause Programming Lang: Python Description : Osmium library bindings for Python The PyOsmium module allows you to access some of the features of the Osmium library from Python code. The Osmium library has extensive support for all types of OSM entities: nodes, ways, relations, and changesets. It allows reading from and writing to OSM files in XML and PBF formats, including change files and full history files. Osmium can store OSM data in memory and on disk in various formats and using various indexes. Its easy to use handler interface allows you to quickly write data filtering and conversion functions. Osmium can create WKT, WKB, OGR, GEOS and GeoJSON geometries for easy conversion into many GIS formats and it can assemble multipolygons from ways and relations. This package is part of the new Osmium family superseding the existing osmium source package. The new Osmium family consists of libosmium, node-osmium, pyosmium, osmium-tool, osmium-contrib osmcoastline. The packages for the Osmium family will be maintained in the Debian GIS team. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779938: ITP: osmium-tool -- Command line tool for working with OpenStreetMap data
Package: wnpp Severity: wishlist Owner: Bas Couwenberg sebas...@debian.org * Package name: osmium-tool Version : 0.0~20150306-4ef5dd5 Upstream Author : Osmium Developers d...@openstreetmap.org * URL : http://osmcode.org/osmium-tool/ * License : GPL-3+ Programming Lang: C++ Description : Command line tool for working with OpenStreetMap data Osmium Tool is a multipurpose command line tool based on the Osmium library. With the Osmium Tool you currently can: * Get information about an OSM file * Convert OSM files from one format into another (supports all XML and PBF formats) * Merge and apply change files to an OSM file (with or without history) * Extract data from OSM history files for a given point in time or a time range The Osmium library has extensive support for all types of OSM entities: nodes, ways, relations, and changesets. It allows reading from and writing to OSM files in XML and PBF formats, including change files and full history files. Osmium can store OSM data in memory and on disk in various formats and using various indexes. Its easy to use handler interface allows you to quickly write data filtering and conversion functions. Osmium can create WKT, WKB, OGR, GEOS and GeoJSON geometries for easy conversion into many GIS formats and it can assemble multipolygons from ways and relations. This package is part of the new Osmium family superseding the existing osmium source package. The new Osmium family consists of libosmium, node-osmium, pyosmium, osmium-tool, osmium-contrib osmcoastline. The packages for the Osmium family will be maintained in the Debian GIS team. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779902: /tmp can be mounted as tmpfs against user's will
Le 06/03/2015 16:04, Michael Biebl a écrit : Am 06.03.2015 um 10:10 schrieb Martin Pitt: Control: found -1 215-12 Control: tag -1 confirmed Ça va Didier, Didier Roche [2015-03-06 9:36 +0100]: In debian, tmp.mount is disabled through a distro-patch by default. It means we don't want user's system to get /tmp on tmpfs without explicit enablement (either by enabling tmp.mount unit or via fstab). We noticed that starting an unit using PrivateTmp=yes will pull tmp.mount (which mounts /tmp on tmpfs) in its requirements chain (even if this unit is condition fail). Confirmed. systemctl start colord or systemd-timesyncd will start tmp.mount and thus overmount the existing /tmp in the running system. I reproduced that in a clean sid VM (with LXDE, but I suppose that doesn't matter much). The odd thing though is, that PrivateTmp=yes does not trigger the start of tmp.mount during boot at least on all the test systems I have. Do we know, why that is? A Required=tmp.mount should always start the referenced unit, but it seemingly doesn't. For reference, I dig a little bit into it and asked on the upstream ML: http://lists.freedesktop.org/archives/systemd-devel/2015-March/029072.html Let's see if the bug we are seeing is really due to tmp.mount not being explicitly referenced anywhere. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779931: [Pkg-utopia-maintainers] Bug#779931: sk_disk_check_sleep_mode: Operation not supported for USB3 HDD docking based on JMicron 152d:0551
Am 06.03.2015 um 15:30 schrieb Gianluca Oglietti: Package: libatasmart4 Version: 0.19-3 Severity: grave Justification: causes non-serious data loss Dear Maintainer, I bought a new HDD docking station (for 2 HDDs) based on JMicron JMB551 chipset but I discover an issue that could cause data loss. If I mount some partitions of 2 HDDs connected to my laptop via USB 3.0 using this docking station all works fine until the JMBB551 go in sleep mode. This kind of docking station, in fact, have an intelligent sleep function that put the HDDs in sleep mode when there aren't R/W data operations for at least 5 minutes. Every 10 minutes udisksd control the state of SMART attributes of the attached HDDs but when the docking is in sleep mode we notice the error sk_disk_check_sleep_mode: Operation not supported and the USB connection to the docking is resetted as you can see in the next udisksd log: If checking the SMART state of the sleeping disk resets the USB connection, then this sounds like a kernel bug. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#779912: unblock: cdbs/0.4.128
On 2015-03-06 14:08, Niko Tyni wrote: On Fri, Mar 06, 2015 at 12:10:47PM +0100, Niels Thykier wrote: [...] FWIW, the only arch:any packages build-depending on both cdbs and libmodule-build-perl would be libdevel-callchecker-perl libdevel-callparser-perl liblucy-perl libmarpa-r2-perl Ack with it just being ~4 packages, I have no problem with scheduling them. Accordingly, they are now waiting for a buildd to process them. As Module::Build is also in perl-modules (but is being phased out), it's possible that there are other affected packages. I'd be surprised if there were many more, though. Hope this helps, Noted, I suspect we can live with that risk given the 4 packages above shows no regressions. Thanks, ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779912: unblock: cdbs/0.4.128
On 2015-03-06 14:17, Jonas Smedegaard wrote: Quoting Niels Thykier (2015-03-06 12:10:47) On 2015-03-06 11:58, Jonas Smedegaard wrote: Additionally, the fix for #770767 is believed to also fix applying all default security-strengthening compiler flags for arch-any packages that uses a CDBS perl snippet. Since that is a release goal, and since missing default flags may also lead to other breakage on i386 due to how that platform links perl code (see bug#770767), unblocking of cdbs should probably be followed by BinNMUs + unblock of e.g. all arch-any packages matching regext '^include\s+.*perl.*\.mk' for its rules file. We might not want that actually. Why? Please note that your search below include far too many packages: most perl libraries are arch-all which need not - and cannot - be BinNMUed. Indeed it did. I don't know (and am not skilled so now is probably the wrong time to start if others can help) how to reliably locate such package list, but can do it among the packages I maintain myself which might be adequate (I am not alone in using CDBS but might be for perl libs specifically). Probably http://codesearch.debian.net/results/include%5Cs+.*perl.*%5C.mk%20path:debian/rules/page_0 I knew of that search, but it locates _all_ packages using perl snippet - not only arch-any packages. I can only think of needing to both grep rules file for snippet inclusion and control file to exclude arch-all - but I don't think such cross-file combo is possible with codesearch.d.n. Indeed, my bad. And then the To see all packages which contain results: cmd. Where is that command? - Jonas When I tried the search, codesearch showed me a command for figuring out the affecting packages. Something like: curl -s http://codesearch.debian.net/results/.../packages.json | \ jq -r '.Packages[]' Didn't work for me as I did not have jq though. ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779940: fail2ban: Incorrect regextp in apache-common.conf
Package: fail2ban Version: 0.8.6-3wheezy3 Severity: important Tags: patch Dear Maintainer, With the original /etc/fail2ban/filter.d/apache-common.conf regexp doesn't match. I have hundred of thousands of connections of an IP that makes this log entries on my /var/log/apache/error.log: [Fri Mar 06 16:01:25.519865 2015] [:error] [pid 824] [client XXX.YYY.ZZZ.AAA:P] script '/var/www/pruebas/wp-login.php' not found or unable to stat Original regexp in the file is simlar to this (don't know now): _apache_error_client = \[[^]]+\] \[:error\] \[client HOST\] I solved the problem editing /etc/fail2ban/filter.d/apache-common.conf and modifying that line to: _apache_error_client = \[[^]]+\] \[:error\].*\[client HOST(:\d*)] -- System Information: Debian Release: 7.8 APT prefers stable APT policy: (990, 'stable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to es_ES.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fail2ban depends on: ii lsb-base4.1+Debian8+deb7u1 ii python 2.7.8-2 ii python-central 0.6.17 Versions of packages fail2ban recommends: ii iptables 1.4.21-2+b1 ii python-gamin 0.1.10-4.1 ii whois 5.1.1~deb7u1 Versions of packages fail2ban suggests: ii heirloom-mailx [mailx] 12.5-2+deb7u1 -- no debconf information Agur: Javier Ortega Conde _ MetaUniversidad: formación y aprendizaje onlinehttp://metauniversidad.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779902: /tmp can be mounted as tmpfs against user's will
Am 06.03.2015 um 16:04 schrieb Michael Biebl: I think, PrivateTmp=yes pulling in tmp.mount is a bug and I would simply revert b46a529c [1] or replace unit_require_mounts_for with a After dependency [2] only. The check to add a hard Requires Dependency, is to test for a fragment path [3]. If we extend that and check also if the unit is actually enabled, this would solve our problem afaics. Michael [3] http://cgit.freedesktop.org/systemd/systemd/tree/src/core/mount.c#n280 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#779939: libmagickwand-6.q16-2: MagickSetImageBias() has no effect for MagickConvolveImage()
Package: libmagickwand-6.q16-2 Version: 8:6.8.9.9-5 Severity: normal Dear Maintainer, the version of ImageMagick packages with Debian Wheezy suffers from a known and fixed upstream bug, regarding the application of convolution filters when using the MagickWand API. In order to reproduce this issue, try to use the MagickConvolveImage() API function after using MagickSetImageBias(). No matter to which value the Bias is set, the outcome will always lack any bias. This issue only shows itself when using the API. It is not present when using the ImageMagick command line tools. The upstream bug report can be found here: http://www.imagemagick.org/discourse-server/viewtopic.php?t=25732 According to it, this issue should be fixed meanwhile, in ImageMagick versions starting from 6.9.0-1 Beta. Just in case someone stumbles across this and is looking for a workaround: I'm not sure, but It seems to me, that the MagickMorphologyImage() function does take the bias into account. best Regards, Andreas -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_AT.utf8, LC_CTYPE=de_AT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libmagickwand-6.q16-2 depends on: ii dpkg 1.17.24 ii imagemagick-common 8:6.8.9.9-5 ii libc6 2.19-15 ii libgcc11:4.9.2-10 ii libgomp1 4.9.2-10 ii libmagickcore-6.q16-2 8:6.8.9.9-5 ii libx11-6 2:1.6.2-3 ii multiarch-support 2.19-15 libmagickwand-6.q16-2 recommends no packages. libmagickwand-6.q16-2 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779941: python-matplotlib-data: Some links point to /usr/share/fonts/truetype/ttf-lyx, it should be lyx instead of ttf-lyx
Package: python-matplotlib-data Version: 1.1.1~rc2-1 Severity: normal Dear Maintainer, In /usr/share/matplotlib/mpl-data/fonts/ttf, some soft links were defined as: cmex10.ttf - ../../../../fonts/truetype/ttf-lyx/cmex10.ttf cmmi10.ttf - ../../../../fonts/truetype/ttf-lyx/cmmi10.ttf cmr10.ttf - ../../../../fonts/truetype/ttf-lyx/cmr10.ttf cmsy10.ttf - ../../../../fonts/truetype/ttf-lyx/cmsy10.ttf However, package fonts-lyx now install these at /usr/share/fonts/truetype/lyx.Thus the following soft links definition should change to: cmex10.ttf - ../../../../fonts/truetype/lyx/cmex10.ttf cmmi10.ttf - ../../../../fonts/truetype/lyx/cmmi10.ttf cmr10.ttf - ../../../../fonts/truetype/lyx/cmr10.ttf cmsy10.ttf - ../../../../fonts/truetype/lyx/cmsy10.ttf Regards, CVR -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 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 python-matplotlib-data depends on: ii fonts-lyx 2.0.3-3 python-matplotlib-data recommends no packages. python-matplotlib-data suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713967: apache2-bin: daemon doesn't close all fds on fork - which causes postinst with debconf to hang
Package: apache2 Version: 2.2.22-13+deb7u4 Followup-For: Bug #713967 I filed https://bz.apache.org/bugzilla/show_bug.cgi?id=57671 with Apache-APR for this issue. -- System Information: Debian Release: 7.8 APT prefers stable APT policy: (900, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-0.bpo.4-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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777939: add patch
Control: tags -1 + patch patch at http://launchpadlibrarian.net/199479544/libbonoboui_2.24.5-0ubuntu3_2.24.5-0ubuntu4.diff.gz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779334: libminiupnpc10: library should at most suggest its daemon
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 02/27/2015 11:45 AM, Jonas Smedegaard wrote: Package: libminiupnpc10 Version: 1.9.20140610-2 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 libminiupnpc10 recommends minissdpd. As a consequence, any package which links against the library pulls in the daemon. Please lower to only suggest, so that Bitcoin, Transmission and other tools linking against this library can each decide on their own how strongly they consider their relation to be. - Jonas Hi Jonas, I do not agree with you. The minissdpd really is a useful tool, which speeds up discovery in the LAN, and I think it's a good idea to have it as a recommends. Tools like Bitcoin, Transmission and others will work better regarding to UPnP if minissdpd is running. You can read the description of minissdpd if you don't know why yet. So, I believe having minissdpd as a recommends is exactly what should be done here, and I don't really think it's a good idea to revert this. If you do, please explicitly say why, as here you haven't explained why running minissdpd is not what we recommend. Cheers, Thomas Goirand (zigo) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJU+Yn9AAoJENQWrRWsa0P+AqAQAJOjUtGMPw0+0Lfw/ax63VVo BXrkxMUe74D3XWLRlNVTsC8n3OzHhWiXSBBvH02G1bbq+PUME4GcqLevq8CYsovR BNc4lU9tbnK40Ep4jUnmb9I87jA0LNLNPhlJWaidonm4Nqj4NjDiu/3NcwAQU7Mg KhbjUxO2WZQ9dVkITysJjjRc0AcTXIzlae9MNKkaWGBTTD53K7acfW/92bcEtZZZ sXa12aUy5Ujd0G9r8ChKRZBDZgBH8TbtJn3EVmxDYW1sqZtC/cvMrZJM5fDYjDv9 RC90WWD3Ij2GpbV2Ckn4G8iHdba9Y8jQ8oEQiWEITCwSbCmQfnWf8cXurz9fCLIT 1pli/p//NfYJnMru/JNTc9cVG/0HGFCXvaJUtEDMWnDvnNRlAjowCYutUXYRnOTY iwCwVv49QvbEphjqpjdtjC9lGum+aFoZv57qG+YrETKvqAMM8Jf3tTvHEjuYot1D AWy2YFZdVGSQH/k/jaorzDzLGfbtPSy3l5MqeUo3Nvnh26AcRzKRkbt0sN7l0PKH 9pcTdfseoWVv3b4idUk+WK5wrRVA8D4b+INhp7r3Fq1MPZwlt8TL6PusQqgJ00QK lhhXUqz0A/9ZNPbHpWXKxUi/6p7oSrEtp9LnjwI0npExYodoqABZbPw3ZgZiGtK2 pcOnceVCN1b9RaBkWkcX =uuw8 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779820: unblock (pre-approval): mate-netbook/1.8.1-4
Hi Emilio, On Fr 06 Mär 2015 12:12:36 CET, Emilio Pozuelo Monfort wrote: Control: tags -1 moreinfo On 05/03/15 08:52, Mike Gabriel wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please consider unblocking of planned upload of package mate-netbook. + [ Martin Wimpress ] + * debian/patches: ++ Add 0001_respect_undecorate_setting.patch. Ensure mate-maximus + undecorates maximized windows only when the undecorate dconf + option is set. (Closes: #778816). Once mate-netbook is installed most applications loose their window decorations when maximized (expected behabiour of mate-maximus inside the mate-netbook package). In dconf there is a setting that allows one to disable this undecorate behaviour (i.e. make windows behave normally (desktop-like) again when maximized. However, this undecorate option in dconf has no effect for users attempting to disable the undecorate feature, window decorations stay lost until mate-netbook gets uninstalled. Impossible to configure mate-maximus on a per-user basis or with a system-wide override file. With the provided patch in the attached .debdiff, this issue is fixed. While the patch is minimal, the bug is only of normal severity, and we are at the point where only (or mostly) RC bug fixes go through. So I'm unsure about letting this through. Can you argue why this is actually more important, or why we should make an exception for it? Emilio Basically, I submitted this issue out of two reasons: o in a private communication with Niels about open MATE issues he encouraged me to file the unblock request for the above mentioned issue (I hope I got him right concerning that). o once mate-netbook is installed, it is not possible to disable mate-maximus's functionality, although there are switches for it (namely: the undecorate switch in dconf). mate-netbook also ships another applet (mate-window-picker-applet), if people want to have that, but not mate-maximus they face a problem... The behaviour of mate-maximus should be controllable via gsettings and not via dpkg (installation / removal of the package). light+love Mike -- mike gabriel aka sunweaver (Debian Developer) fon: +49 (1520) 1976 148 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net pgpv9BFGMltab.pgp Description: Digitale PGP-Signatur
Bug#726430: apt-listbugs: Does not uses proxy from Acquire::http::ProxyAutoDetect
On Thursday 05 March 2015 23:57:47 Francesco Poli wrote: On Thu, 05 Mar 2015 15:19:51 -0300 Lisandro Damián Nicanor Pérez Meyer wrote: On Tuesday 03 March 2015 23:29:25 Francesco Poli wrote: [snip] $ grep -i detect /etc/apt/apt.conf /etc/apt/apt.conf.d/* /etc/apt/apt.conf.d/30autoproxy:Acquire::http::ProxyAutoDetect /usr/share/squid-deb-proxy-client/apt-avahi-discover; ProxyAutoDetect is the legacy option name (see apt.conf(5) man page for more details) and it's not supported by apt-listbugs. Interesting, this comes from apt-squid-proxy-client, maybe we need a bug there :) Yes, I think it's the appropriate thing to do. Allow me to do it :) [snip working stuff] = Response ! CONNECTION CLOSED Exception `HTTPClient::KeepAliveDisconnected' at /usr/lib/ruby/vendor_ruby/httpclient/session.rb:882 - HTTPClient::KeepAliveDisconnected Exception `HTTPClient::KeepAliveDisconnected' at /usr/lib/ruby/vendor_ruby/httpclient/session.rb:670 - HTTPClient::KeepAliveDisconnected Exception `HTTPClient::KeepAliveDisconnected' at /usr/lib/ruby/vendor_ruby/soap/streamHandler.rb:251 - HTTPClient::KeepAliveDisconnected Fallo Exception: HTTPClient::KeepAliveDisconnected Error al obtener informes de fallo del servidor con el siguiente mensaje de error: E: HTTPClient::KeepAliveDisconnected But something goes wrong while waiting for a response from the SOAP server... I'm guessing here that the problem is now in acng, right? I am not sure. Do you happen to know the meaning of the HTTPClient::KeepAliveDisconnected error? If not, I'll have to investigate and figure out what may be the cause of this error... I don't know, but allow me to look for this myself (but feel free to check if you have will and time). -- Hiroshima '45, Chernobyl '86, Windows '95. Grafitti en Niceto Vega 5940, Buenos Aires. De una foto de Mario Gallo. Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#779920: debconf: questions sourced from a template owned by another package block purge/install of other package
Package: debconf Version: 1.5.24 Severity: normal Control: blocks 578960 by -1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 dbconfig-common can not be purged and reinstalled correctly without purging all reverse dependent packages. This has been reported against dbconfig-common a long time ago (578960 and merged bugs), but I don't believe that the bug is actually in dbconfig-common. To prevent the the bug list of debconf to be poluted by the duplicates I file a new bug against debconf which can just be closed if you really think this is something that dbconfig-common should work around itself. (Analysis from bug 578960 by Sean Finney) This is what happens: dbconfig-common installs a collection of templates. Example from debconf config.dat cache file: Name: dbconfig-common/database-type Template: dbconfig-common/database-type Owners: dbconfig-common Later, someone installs a webapp (say, phpbb3), which registers a subset of these packages from dbconfig-common. Relevant entries in debconf cache file: Name: dbconfig-common/database-type Template: dbconfig-common/database-type Owners: dbconfig-common Name: phpbb3/database-type Template: dbconfig-common/database-type Value: Owners: phpbb3 Variables: database_types = mysql, pgsql, sqlite pkg = phpbb3 Later, both packages are removed, and even later dbconfig-common is purged (but not phpbb3). config.dat cache now contains: Name: phpbb3/database-type Template: dbconfig-common/database-type Value: Owners: phpbb3 Variables: database_types = mysql, pgsql, sqlite pkg = phpbb3 And the template still exists in templates.dat And even later, dbconfig-common is reinstalled. However, config.dat cache is the same as before (i.e. no dbconfig-common/database-type ). I'm guessing that the un-purged package with the registered copy of the template is preventing dbconfig-common from properly setting up its own debconf-stuff, and as pointed out it requires purging not just dbconfig-common but all dbconfig-common using packages in order to get a working behavior again. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJU+Z+fAAoJEJxcmesFvXUK1kgH/Re8IcYt1oZviNFydLJ4zM0K VlRAmH0vuW0uryCR/KOX8SrLc2yr7QkT8HmtmSuPYlwzr1Nb/1foQed7dgX3iZmP iU7tD8kOP6d+KTcVFtzI/HwgJejxW3gkb6ZjZmo057tHfXQWkB0F20CU+IirXW0e pI88BxyCcu+a8NqnpuXG3nJS94dPvEoOPHwMgYJN+QjuidX8HZYZQX7uI0o4aX4y J+wwB64AZl1Z5ilq5O8rm7IoI81quMdAqdyynW6mK9NL39vlKbXy13ad/4g9z8ae Qxntum8SliV8BW+1tm2nQvI97N0GIk5Q5FGM6QLEC7dnt6Z7+bXDDd3JzHmMA3I= =d5lQ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779921: afl: Wrong path in help output
Package: afl Version: 1.56b-1 Severity: minor $ afl-gcc afl-cc 1.56b (Mar 5 2015 12:25:51) by lcam...@google.com ... CC=/usr/local/bin/afl-gcc ./configure CXX=/usr/local/bin/afl-g++ ./configure but $ which afl-gcc /usr/bin/afl-gcc so a simple copy-paste doesn't work. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.18.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages afl depends on: ii libc6 2.19-15 Versions of packages afl recommends: ii g++ 4:4.9.2-2 ii gcc 4:5-0 Versions of packages afl suggests: pn clang none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779910: ITP: docker-compose -- Tool to define and run complex applications with Docker
❦ 6 mars 2015 18:34 +0800, ChangZhuo Chen (陳昌倬) czc...@gmail.com : Package: wnpp Severity: wishlist Owner: ChangZhuo Chen (陳昌倬) czc...@gmail.com * Package name: docker-compose Version : 1.1.0 Upstream Author : Docker, Inc. * URL : https://github.com/docker/compose * License : Apache 2.0 Programming Lang: Python Description : Tool to define and run complex applications with Docker Compose is a tool for defining and running complex applications with Docker. With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running. fig is already packaged in Debian: https://tracker.debian.org/pkg/fig -- Avoid multiple exits from loops. - The Elements of Programming Style (Kernighan Plauger) signature.asc Description: PGP signature
Bug#704989: dkms: Add POST_BUILD to the dkms_conf_variables list
Control: tags -1 + fixed-upstream This was applied ustream on 22/Sep/2014: git://linux.dell.com/dkms.git 8653e9f44145bbf77d7145bc0c4f9f0c336a7fb9 signature.asc Description: OpenPGP digital signature
Bug#779918: kdenlive: Effects are not localized
The bug is actually against kdenlive 0.9.10-2 and not the neptune version (reportbug somehow grabbed that. Sry for the confusion) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779912: unblock: cdbs/0.4.128
Quoting Niels Thykier (2015-03-06 12:10:47) On 2015-03-06 11:58, Jonas Smedegaard wrote: Additionally, the fix for #770767 is believed to also fix applying all default security-strengthening compiler flags for arch-any packages that uses a CDBS perl snippet. Since that is a release goal, and since missing default flags may also lead to other breakage on i386 due to how that platform links perl code (see bug#770767), unblocking of cdbs should probably be followed by BinNMUs + unblock of e.g. all arch-any packages matching regext '^include\s+.*perl.*\.mk' for its rules file. We might not want that actually. Why? Please note that your search below include far too many packages: most perl libraries are arch-all which need not - and cannot - be BinNMUed. I don't know (and am not skilled so now is probably the wrong time to start if others can help) how to reliably locate such package list, but can do it among the packages I maintain myself which might be adequate (I am not alone in using CDBS but might be for perl libs specifically). Probably http://codesearch.debian.net/results/include%5Cs+.*perl.*%5C.mk%20path:debian/rules/page_0 I knew of that search, but it locates _all_ packages using perl snippet - not only arch-any packages. I can only think of needing to both grep rules file for snippet inclusion and control file to exclude arch-all - but I don't think such cross-file combo is possible with codesearch.d.n. And then the To see all packages which contain results: cmd. Where is that command? - 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#779924: stellarium: Needs GLSL1.30 or later
Package: stellarium Version: 0.13.2-1 Severity: normal Tags: upstream The programm seems to work normally. But the startup log says: Detected: OpenGL 2.1 Driver version string: 2.1 Mesa 10.3.2 GL vendor is Intel Open Source Technology Center GL renderer is Mesa DRI Intel(R) Ironlake Mobile GL Shading Language version is 1.20 MESA Version Number after parsing: 10.3 Mesa version is fine, we should not see a graphics problem. GLSL Version Number after parsing: 1.2 This is not enough: we need GLSL1.30 or later. You should update graphics drivers, graphics hardware, or use the MESA v= ersion. Else, please try to use an older version like 0.12.4, and try there with= --safe-mode Config option main/ignore_opengl_warning found, continuing. Expect probl= ems. This is 4-5 year old thinkpad T510 with graphic card: *-display description: VGA compatible controller product: Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 02 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=3Di915 latency=3D0 resources: irq:24 memory:f200-f23f memory:d000-dfff ioport:1800(size=3D8) -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.0-4-gd5d51a7 (SMP w/4 CPU cores) Locale: LANG=3Dde_DE, LC_CTYPE=3Dde_DE (charmap=3DISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages stellarium depends on: ii libc62.19-15 ii libgcc1 1:4.9.2-10 ii libgl1-mesa-glx [libgl1] 10.4.2-2 ii libqt5concurrent55.3.2+dfsg-4+b1 ii libqt5core5a [qtbase-abi-5-3-2] 5.3.2+dfsg-4+b1 ii libqt5declarative5 5.3.2-3 ii libqt5gui5 5.3.2+dfsg-4+b1 ii libqt5network5 5.3.2+dfsg-4+b1 ii libqt5opengl55.3.2+dfsg-4+b1 ii libqt5script55.3.2+dfsg-2 ii libqt5widgets5 5.3.2+dfsg-4+b1 ii libstdc++6 4.9.2-10 ii qtquick1-qml-plugins 5.3.2-3 ii stellarium-data 0.13.2-1 ii zlib1g 1:1.2.8.dfsg-2+b1 stellarium recommends no packages. stellarium suggests no packages. -- no debconf information --=20 To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmaster@lists.debian= .org
Bug#759544: nslcd: fails 'sometimes' to start at boot (systemd?)
On Wed, 2015-03-04 at 16:59 +0100, Rike-Benjamin Schuppner wrote: On Sun, 04 Jan 2015 00:42:42 +0100 Bernhard Schmidt be...@birkenwald.de wrote: This sounds like http://arthurdejong.org/git/nss-pam-ldapd/commit/?id=1d3b19b1ecd3b10f36e8925e8a752a28e3e74b56 could help here. Unfortunately I wasn't able to reproduce the problem so testing the patch won't help. No luck with this patch for me. Still getting the ‘unable to daemonize’ messages in the log. Of course it would be more helpful, if the nslcd daemon would be able to give a better error code to systemd. Thanks for providing your test feedback. Could you also test http://arthurdejong.org/git/nss-pam-ldapd/commit/?id=a726d291b0f6794abec0a0192cf2b2a742648e4a to see if that helps. It should give a little more information on why start-up failed. Thanks, -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong -- signature.asc Description: This is a digitally signed message part
Bug#779597: proofgeneral: Buffer is read-only when there is an error compiling dependant Coq files
Ralf Jung p...@ralfj.de writes: Weird enough, it shows that error even when there is nothing to do: A This might be because the buffer is always initialized, see coq-init-compile-response-buffer. Looking quickly over the code, all usages of this buffer seem to be guarded with (inhibit-read-only t), which should disable the read-only check. I don't know what is going on, I have to look more carefully. Bye, Hendrik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776280: g-d-p: please add support for No Rest For The Living
Hi Fabian, After having extensively debugged this game; I've settled for doom2-nerve-wad before a new GDP is released; so we don't have to add Replaces:/Conflicts doom2-norest-wad . This makes most sense. http://anonscm.debian.org/cgit/pkg-games/game-data-packager.git/commit/?id=886484ed97dae145c2724b6cb966d5444c52b15a Alexandre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#458226: 's contact info
Title: Join Brewster Current City 458...@bugs.debian.org Mobile Number Confirm/Update for For your safety, this link expires in 48 hours Featured on: Your Contacts, Synced Anywhere Why did you receive this email? 11 East 4th St. #2F New York, NY 10003 Unsubscribe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680272: 's contact info
Title: Join Brewster Current City 680...@bugs.debian.org Mobile Number Confirm/Update for For your safety, this link expires in 48 hours Featured on: Your Contacts, Synced Anywhere Why did you receive this email? 11 East 4th St. #2F New York, NY 10003 Unsubscribe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#771857: 's contact info
Title: Join Brewster Current City 771...@bugs.debian.org Mobile Number Confirm/Update for For your safety, this link expires in 48 hours Featured on: Your Contacts, Synced Anywhere Why did you receive this email? 11 East 4th St. #2F New York, NY 10003 Unsubscribe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#777889: add patch
Control: tags -1 + patch patch at http://launchpadlibrarian.net/199522141/grantlee_0.5.1-0ubuntu1_0.5.1-0ubuntu2.diff.gz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778085: add patch
Control: tags -1 + patch patch at http://launchpadlibrarian.net/199520528/qt4-x11_4%3A4.8.6%2Bgit64-g5dc8b2b%2Bdfsg-3~ubuntu5_4%3A4.8.6%2Bgit64-g5dc8b2b%2Bdfsg-3~ubuntu6.diff.gz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779922: debian-installer: Installation freezes with The attempt to mount a files system with type ext4 in SCSI1 (0, 0, 0), partition #1 (sda) at / failed.
Control: severity -1 important Control: tag -1 - d-i Hi Igor, and thanks for your report. Igor Liferenko igor.lifere...@gmail.com (2015-03-06): Package: debian-installer Severity: critical Tags: d-i Justification: breaks the whole system Ajusting severity since there's no system to break at this point. Also, released images don't suffer from this issue. I take debian testing weekly build from http://cdimage.debian.org/cdimage/weekly-builds/i386/jigdo-dvd/debian-testing-i386-DVD-1.jigdo, add preseed to it and install in qemu. Preseed contains this: d-i partman-auto/method string regular d-i partman-auto/choose_recipe select atomic d-i partman-partitioning/confirm_write_new_label boolean true d-i partman/confirm_nooverwrite boolean true d-i partman/choose_partition select finish d-i partman/confirm boolean true Qemu image is created as: qemu-img create -f qcow2 newcd-qemu.qcow2 10G Previous debian testing builds caused no problem with the same setup (I test each week). Problem arised with latest debian testing build (from 02.03.2015). Installation freezes with the following error (Partition disks stage): The attempt to mount a files system with type ext4 in SCSI1 (0,0,0), partition #1 (sda) at / failed. You may resume partitioning from the partitioning menu. Do you want to resume partitioning? - No - Yes Relevant parts of installer log from qemu follow: partman: mke2fs 1.42.12 (29-Aug-2014) kernel: ext4: Unknown symbol pagecache_get_page_fixed (err 0) This was reported as #779651 against installation-reports and as #779616 against debian-cd. We're trying to figure out what to do in the latter. Mraw, KiBi. signature.asc Description: Digital signature
Bug#779922: debian-installer: Installation freezes with The attempt to mount a files system with type ext4 in SCSI1 (0, 0, 0), partition #1 (sda) at / failed.
Package: debian-installer Severity: critical Tags: d-i Justification: breaks the whole system Dear Maintainer, I take debian testing weekly build from http://cdimage.debian.org/cdimage/weekly-builds/i386/jigdo-dvd/debian-testing-i386-DVD-1.jigdo, add preseed to it and install in qemu. Preseed contains this: d-i partman-auto/method string regular d-i partman-auto/choose_recipe select atomic d-i partman-partitioning/confirm_write_new_label boolean true d-i partman/confirm_nooverwrite boolean true d-i partman/choose_partition select finish d-i partman/confirm boolean true Qemu image is created as: qemu-img create -f qcow2 newcd-qemu.qcow2 10G Previous debian testing builds caused no problem with the same setup (I test each week). Problem arised with latest debian testing build (from 02.03.2015). Installation freezes with the following error (Partition disks stage): The attempt to mount a files system with type ext4 in SCSI1 (0,0,0), partition #1 (sda) at / failed. You may resume partitioning from the partitioning menu. Do you want to resume partitioning? - No - Yes Relevant parts of installer log from qemu follow: main-menu INFO: Menu item 'disk-detect' selected kernel: sda: unknown partition table main-menu: INFO: Menu item 'partman-base' selected anna-install: Installing partman-auto-lvm anna: DEBUG: retrieving crc-modules-3.16.0-4-586-di 3.16.7-ckt7-1 anna: DEBUG: retrieving lvm2-udeb 2.02.111-2 anna: DEBUG: retrieving partman-auto-lvm 56 anna: DEBUG: retrieving partman-lvm 105 anna-install: Installing partman-auto-crypto anna: DEBUG: retrieving partman-auto-crypto 22 anna: DEBUG: retrieving partman-crypto 78 kernel: ext4: Unknown symbol pagecache_get_page_fixed (err 0) kernel: raid6: mmxx158 MB/s kernel: raid6: mmxx276 MB/s kernel: raid6: sse1x1 70 MB/s kernel: raid6: sse1x2 78 MB/s kernel: raid6: sse2x1 157 MB/s kernel: raid6: sse2x2 123 MB/s kernel: raid6: using algorithm sse2x1 (157 MB/s) kernel: raid6: using intx1 recovery algorithm kernel: xor: measuring software checksum speed kernel: pIII_sse : 430.000 MB/sec kernel: prefetch64-sse: 429.000 MB/sec kernel: xor: using function: pIII_sse (430.000 MB/sec) kernel: btrfs: Unknown symbol pagecache_get_page_fixed (err 0) kernel: ext4: Unknown symbol pagecache_get_page_fixed (err 0) kernel: ext4: Unknown symbol pagecache_get_page_fixed (err 0) kernel: jfs: Unknown symbol pagecache_get_page_fixed (err 0) kernel: SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled md-devices: mdadm: No arrays found in config file or automatically kernel: device-mapper: uevent: version 1.0.3 kernel: device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-de...@redhat.com partman: No matching physical volumes found partman: Reading all physical volumes. This may take a while... partman: No volume groups found partman-lvm: No volume groups found kernel: sda: unknown partition table kernel: sda: unknown partition table kernel: sda: unknown partition table kernel: sda: sda1 sda2 sda5 kernel: Adding 477189k swap on /dev/sda5. Priority:-1 extents:1 across:477189k FS partman: mke2fs 1.42.12 (29-Aug-2014) kernel: ext4: Unknown symbol pagecache_get_page_fixed (err 0) -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779911: mailman: Upstream 2.1.19 available
On 06.03.2015 11:55, Joost van Baal-Ilić wrote: Thanks for your bugreport. Thank *you* for the quick reply! - could you paste upstream NEWS and/or changelog here? It's too long. Please see: https://mail.python.org/pipermail/mailman-announce/2015-February/000202.html Any other urgent improvements apart from DEFAULT_SUBSCRIBE_OR_INVITE? Many new features which might be interesting for one or another user, e.g. this one: | - Added real name display to the web roster. (LP: #266754) Many resolved bugs. Any security-related improvements? At least one important privacy topic: | - Organization: headers are now unconditionally removed from posts to |anonymous lists. - upcoming debian jessie will very likely ship with mailman 1:2.1.18-1+b1; even if we package and upload 2.1.19 today. 2.1.19 will likely be available via unstable and testing and jessie+1. You could try to use the privacy topic mentioned above to get 2.1.19 into Jessie. If this doesn't work, 2.1.19 will hopefully appear in Jessie-Backports. Greetings, Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779923: ITP: libosmium -- Fast and flexible C++ library for working with OpenStreetMap data
Package: wnpp Severity: wishlist Owner: Bas Couwenberg sebas...@debian.org * Package name: libosmium Version : 0.0~20150303-f074d94 Upstream Author : Osmium Developers d...@openstreetmap.org * URL : http://osmcode.org/libosmium/ * License : BSL-1.0 Programming Lang: FIXME Description : Fast and flexible C++ library for working with OpenStreetMap data The Osmium Library has extensive support for all types of OSM entities: nodes, ways, relations, and changesets. It allows reading from and writing to OSM files in XML and PBF formats, including change files and full history files. Osmium can store OSM data in memory and on disk in various formats and using various indexes. Its easy to use handler interface allows you to quickly write data filtering and conversion functions. Osmium can create WKT, WKB, OGR, GEOS and GeoJSON geometries for easy conversion into many GIS formats and it can assemble multipolygons from ways and relations. Osmium is a header-only library, so there is nothing to compile to build it. Just include the header files you need. This package is part of the new Osmium family superseding the existing osmium source package. The new Osmium family consists of libosmium, node-osmium, pyosmium, osmium, osmium-contrib osmcoastline. The packages for the Osmium family will be maintained in the Debian GIS team. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779597: proofgeneral: Buffer is read-only when there is an error compiling dependant Coq files
Hi, Weird enough, it shows that error even when there is nothing to do: A This might be because the buffer is always initialized, see coq-init-compile-response-buffer. I should have been more clear: It doesn't always show that error when there is nothing to do. Often, things just work as long as there is no error from Coq. As far as I'm concerned, the issue is not really pressing - since everything is all right with concurrent compilation. Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779917: Uses legacy option for setting proxy
Package: squid-deb-proxy-client Version: 0.8.10 Severity: normal Tags: patch Hi Michael! Francesco Poli and I have been struggling to get #726430 solved and during testing Francesco found that /etc/apt/apt.conf.d/30autoproxy uses the legacy option for proxies Acquire::http::ProxyAutoDetect instead of Acquire::http::Proxy-Auto-Detect. This causes that the fix for the above mentioned bug still needs this change. You can find Francesco's mail in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726430#102 I'm tagging this as patch-available just because the fix is mentioned here. Thanks a lot!!! -- System Information: Debian Release: 8.0 Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779334: libminiupnpc10: library should at most suggest its daemon
Hi Thomas, Quoting Thomas Goirand (2015-03-06 12:05:38) On 02/27/2015 11:45 AM, Jonas Smedegaard wrote: libminiupnpc10 recommends minissdpd. As a consequence, any package which links against the library pulls in the daemon. Please lower to only suggest, so that Bitcoin, Transmission and other tools linking against this library can each decide on their own how strongly they consider their relation to be. I do not agree with you. The minissdpd really is a useful tool, which speeds up discovery in the LAN, and I think it's a good idea to have it as a recommends. Tools like Bitcoin, Transmission and others will work better regarding to UPnP if minissdpd is running. You can read the description of minissdpd if you don't know why yet. So, I believe having minissdpd as a recommends is exactly what should be done here, and I don't really think it's a good idea to revert this. If you do, please explicitly say why, as here you haven't explained why running minissdpd is not what we recommend. Currently the library dictates for all of its consumers how important the daemon shall be for them. I argue that each consumer shall be allowed to declare on their own how important the daemon is for them. You now look at concrete consumers, and argue that all of the ones you look at make sense to recommend the daemon - but that does not change my underlying point that each consumer should be allowed to decide that rather than have that dictated by the library. It is wrong of a library to dictate how important itself and its surrunding tools are for its consumers. Example: Imagine if Bitcoin package maintainers decide that uPNP is nice but may be considered a security risk for some users, and therefore should be treated as an *optional* feature for that package. Currently you impose a recommendation that they can only avoid by not linking at all or by rewriting code to be a plugin which can then not be installed at all. You make flexibility harder, which is bad for Debian. Does that make sense? - 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#779820: unblock (pre-approval): mate-netbook/1.8.1-4
Control: tags -1 + confirmed On 06/03/15 13:18, Mike Gabriel wrote: Hi Emilio, On Fr 06 Mär 2015 12:12:36 CET, Emilio Pozuelo Monfort wrote: Control: tags -1 moreinfo On 05/03/15 08:52, Mike Gabriel wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please consider unblocking of planned upload of package mate-netbook. + [ Martin Wimpress ] + * debian/patches: ++ Add 0001_respect_undecorate_setting.patch. Ensure mate-maximus + undecorates maximized windows only when the undecorate dconf + option is set. (Closes: #778816). Once mate-netbook is installed most applications loose their window decorations when maximized (expected behabiour of mate-maximus inside the mate-netbook package). In dconf there is a setting that allows one to disable this undecorate behaviour (i.e. make windows behave normally (desktop-like) again when maximized. However, this undecorate option in dconf has no effect for users attempting to disable the undecorate feature, window decorations stay lost until mate-netbook gets uninstalled. Impossible to configure mate-maximus on a per-user basis or with a system-wide override file. With the provided patch in the attached .debdiff, this issue is fixed. While the patch is minimal, the bug is only of normal severity, and we are at the point where only (or mostly) RC bug fixes go through. So I'm unsure about letting this through. Can you argue why this is actually more important, or why we should make an exception for it? Emilio Basically, I submitted this issue out of two reasons: o in a private communication with Niels about open MATE issues he encouraged me to file the unblock request for the above mentioned issue (I hope I got him right concerning that). o once mate-netbook is installed, it is not possible to disable mate-maximus's functionality, although there are switches for it (namely: the undecorate switch in dconf). mate-netbook also ships another applet (mate-window-picker-applet), if people want to have that, but not mate-maximus they face a problem... The behaviour of mate-maximus should be controllable via gsettings and not via dpkg (installation / removal of the package). OK. Based on that and the fact that the patch is trivial, and the issue seems important enough that I'd approve it for a pu in stable, I'm going to ack it now. Please upload it and remove the moreinfo tag when the package is accepted. Regards, Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779918: kdenlive: Effects are not localized
Package: kdenlive Version: 0.9.10-neptune3 Severity: important Tags: upstream The kdenlive in upstream is shipping broken localizations that do not localize effects anymore. We fixed it for Neptune and want to provide our upstream (Debian) with the patch that can be found here: https://github.com/NeptuneOS/kde-patches/tree/master/kdenlive -- System Information: Debian Release: 7.8 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.3 (SMP w/4 CPU cores; PREEMPT) 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 kdenlive depends on: ii kde-runtime 4:4.13.0-neptune6 ii kdenlive-data 0.9.10-neptune3 ii libav-tools 6:10.1-1~bpo70+1neptune1 ii libc6 2.13-38+deb7u8 ii libgcc1 1:4.7.2-5 ii libgl1-mesa-glx [libgl1] 9.2.2-1neptune1 ii libglu1-mesa [libglu1]8.0.5-4+deb7u2 ii libice6 2:1.0.8-2 ii libkdecore5 4:4.14.3-neptune2 ii libkdeui5 4:4.14.3-neptune2 ii libkio5 4:4.14.3-neptune2 ii libknewstuff3-4 4:4.14.3-neptune2 ii libknotifyconfig4 4:4.14.3-neptune2 ii libkrossui4 4:4.14.3-neptune2 ii libmlt++3 0.9.2+git20141027-1neptune1 ii libmlt6 0.9.2+git20141027-1neptune1 ii libnepomukcore4abi1 4:4.13.0-neptune1 ii libqjson0 0.8.1-1 ii libqt4-dbus 4:4.8.2+dfsg-11 ii libqt4-network4:4.8.2+dfsg-11 ii libqt4-opengl 4:4.8.2+dfsg-11 ii libqt4-script 4:4.8.2+dfsg-11 ii libqt4-svg4:4.8.2+dfsg-11 ii libqt4-xml4:4.8.2+dfsg-11 ii libqtcore44:4.8.2+dfsg-11 ii libqtgui4 4:4.8.2+dfsg-11 ii libsm62:1.2.1-2 ii libsolid4 4:4.14.3-neptune2 ii libsoprano4 2.9.3+dfsg1-0neptune1 ii libstdc++64.7.2-5 ii libv4l-0 0.8.8-3 ii libx11-6 2:1.5.0-1+deb7u1 ii libxau6 1:1.0.7-1 ii libxdmcp6 1:1.1.1-1 ii libxext6 2:1.3.1-2+deb7u1 ii libxft2 2.3.1-1 ii libxpm4 1:3.5.10-1 ii melt 0.9.2+git20141027-1neptune1 Versions of packages kdenlive recommends: ii dvdauthor0.7.0-1.1+b2 ii dvgrab 3.5-2 ii frei0r-plugins 1.1.22git20091109-1.2 ii genisoimage 9:1.1.11-2 ii recordmydesktop 0.3.8.1+svn602-1+b1 ii swh-plugins 0.4.15+1-6 Versions of packages kdenlive suggests: ii khelpcenter4 4:4.13.0-neptune6 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779919: usb-modeswitch: IOMMU in BIOS not handled properly
Package: usb-modeswitch Version: 2.2.0+repack0-2 Severity: normal Tags: d-i Dear Maintainer, * What led up to the situation? The default IOMMU setting in the BIOS for a GIGABYTE motherboard is off. Attempting to install a Debian system (Wheezy or Jessie AMD-64) with this setting results in not recognizing USB mouse or keyboard. However, booting with Squeeze or Wheezy 386 does work with this setting. * What exactly did you do (or not do) that was effective (or ineffective)? Turned on the IOMMU support * What was the outcome of this action? Although the USB-2 mouse and keyboard are dealt with effectively with IOMMU enabled, there are ~550 lines of page fault reported by dmesg at bootup. Further investigaiton finds that failure to access the northbridge (AMD 970 chip) USB-3 support is the cause of the page faults. * What outcome did you expect instead? Everything to work -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages usb-modeswitch depends on: ii libc62.19-15 ii libjim0.75 0.75-1 ii libusb-1.0-0 2:1.0.19-1 ii usb-modeswitch-data 20140529-1 usb-modeswitch recommends no packages. Versions of packages usb-modeswitch suggests: pn comgt none pn wvdial none -- Configuration Files: /etc/usb_modeswitch.conf changed: DisableSwitching=0 EnableLogging=1 SetStorageDelay=4 TargetVendor= 0x1199 TargetProduct= 0x9051 TargetCclass= 0xff MessageContent=55534243785634120100860100 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#464794: idea
have you tried asking for an sponsor at the games team? https://wiki.debian.org/Games/Team -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779912: unblock: cdbs/0.4.128
On Fri, Mar 06, 2015 at 12:10:47PM +0100, Niels Thykier wrote: On 2015-03-06 11:58, Jonas Smedegaard wrote: Additionally, the fix for #770767 is believed to also fix applying all default security-strengthening compiler flags for arch-any packages that uses a CDBS perl snippet. Since that is a release goal, and since missing default flags may also lead to other breakage on i386 due to how that platform links perl code (see bug#770767), unblocking of cdbs should probably be followed by BinNMUs + unblock of e.g. all arch-any packages matching regext '^include\s+.*perl.*\.mk' for its rules file. We might not want that actually. If the fixed cdbs enters jessie, not rebuilding those now might risk regressions later during jessie's lifetime, for instance with security updates AFAICS? I don't know (and am not skilled so now is probably the wrong time to start if others can help) how to reliably locate such package list, but can do it among the packages I maintain myself which might be adequate (I am not alone in using CDBS but might be for perl libs specifically). FWIW, the only arch:any packages build-depending on both cdbs and libmodule-build-perl would be libdevel-callchecker-perl libdevel-callparser-perl liblucy-perl libmarpa-r2-perl As Module::Build is also in perl-modules (but is being phased out), it's possible that there are other affected packages. I'd be surprised if there were many more, though. Hope this helps, -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779925: grml-debootstrap: Lacks escaping of user input
Package: grml-debootstrap Version: 0.68 Severity: important grml-debootstrap lacks escaping of user input. To give an example, execution with --password '$(echo OOPS 2)non-empty' makes grml-debootstrap execute code. Trouble characters are $ ! ` \ . For more details please see https://github.com/grml/grml-debootstrap/issues/58 .. To my understanding, the fact that grml-debootstrap needs root permissions to be operated is the reeason why oss-security decided to not assign a CVE number, see http://thread.gmane.org/gmane.comp.security.oss.general/15483 . The bug affects all versions of grml-debootstrap (wheezy, jessie, sid). A pull request with a proposed fix hit upstream earlier today: https://github.com/grml/grml-debootstrap/pull/68 I'm filing a bug downstream, since this bug may be critical to the release of jessie. Best, Sebastian -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-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 grml-debootstrap depends on: ii cdebootstrap0.5.9 ii debian-archive-keyring 2014.3~deb7u1 ii debootstrap 1.0.48+deb7u2 ii gawk1:4.0.1+dfsg-2.1 Versions of packages grml-debootstrap recommends: ii dialog 1.1-20120215-2 ii kpartx 0.4.9+git0.4dfdaf2b-7~deb7u2 ii mksh40.9.20120630-7 ii parted 2.3-12 ii qemu-utils 1.1.2+dfsg-6a+deb7u6 grml-debootstrap suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776984: closed by Guillem Jover guil...@debian.org (Bug#776984: fixed in dpkg 1.17.24)
On 2015-03-05 21:52, Andreas Beckmann wrote: (I'm now rerunning tests for all packages where dpkg has Breaks/Conflicts) No further problems found :-) Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706352: New upstream version available: 2.2.0
On 2015-03-02 16:23, Salvador Fandino wrote: Python bindings for 2.2 are available from GitHub. http://leenissen.dk/fann/wp/language-bindings/ The CPP bindings are available on the main package. Anyway, the library is completely backward compatible, so bindings for 2.1 can be compiled against 2.2. Nice! I'll try to update the package soon. Thanks, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778000: add test
Control: tags -1 + patch patch at http://launchpadlibrarian.net/199536689/memtest86%2B_4.20-1.1ubuntu8_4.20-1.1ubuntu9.diff.gz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777991: add patch
Control: tags -1 + patch patch at http://launchpadlibrarian.net/199536450/ltrace_0.7.3-4ubuntu6_0.7.3-4ubuntu7.diff.gz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767888: firewall-applet: Cannot change zone of a connection
The problem still exists. Workaround: start the applet as root user from the command line: firewall-config Regards, Martin On Mon, 03 Nov 2014 11:07:44 +0100 Ralf Jung p...@ralfj.de wrote: Package: firewall-applet Version: 0.3.12-1 Severity: normal Dear Maintainer, I'd like to change the zone of an active connection temporarily, i.e., without changing the zone that will be associated to the connection per default. I select Options - Change zones of connections..., and then DHCP which is the currently active connection. I select public (currently, the zone for that connection is home) and click Ok. Nothing happens, i.e., the small window to change the zone remains opened and the zone does not change. On the console, I get Traceback (most recent call last): File /usr/bin/firewall-config, line 1007, in change_zone_connection_editor editor.run() File /usr/bin/firewall-config, line 5298, in run settings = connection_obj.GetSettings() File /usr/lib/python2.7/dist-packages/dbus/proxies.py, line 70, in __call__ return self._proxy_method(*args, **keywords) File /usr/lib/python2.7/dist-packages/slip/dbus/proxies.py, line 51, in __call__ return dbus.proxies._ProxyMethod.__call__(self, *args, **kwargs) File /usr/lib/python2.7/dist-packages/dbus/proxies.py, line 145, in __call__ **keywords) File /usr/lib/python2.7/dist-packages/dbus/connection.py, line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 7 matched rules; type=method_call, sender=:1.63 (uid=1000 pid=28011 comm=/usr/bin/python -Es /usr/bin/firewall-config ) interface=(unset) member=GetSettings error name=(unset) requested_reply=0 destination=:1.14 (uid=0 pid=1039 comm=/usr/sbin/NetworkManager --no-daemon ) Kind regards Ralf -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17.0+ (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages firewall-applet depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii firewalld0.3.12-1 ii gir1.2-glib-2.0 1.42.0-2.2 ii gir1.2-gtk-3.0 3.14.4-1 ii gir1.2-networkmanager-1.00.9.10.0-3 ii gir1.2-notify-0.70.7.6-2 ii policykit-1 0.105-7 ii python-dbus 1.2.0-2+b3 ii python-gi3.14.0-1 ii python-slip-dbus 0.6.0-2 pn python:any none firewall-applet recommends no packages. firewall-applet suggests no packages.
Bug#779942: ITP: osmium-contrib -- Various programs showing what you can do with the Osmium library
Package: wnpp Severity: wishlist Owner: Bas Couwenberg sebas...@xs4all.nl * Package name: osmium-contrib Version : 0.0~20150306-0c4f263 Upstream Author : Osmium Developers d...@openstreetmap.org * URL : http://osmcode.org/osmium-contrib/ * License : public-domain Programming Lang: C++ Description : Various programs showing what you can do with the Osmium library Osmium Contrib contains various programs showing what you can do with the Osmium library. The osmium-contrib repository collects little programs that use the Osmium library in various ways. These programs can be useful in their own right, but they also provide nice examples for developers who want to learn about the features of the Osmium library. Currently the following programs are available: * amenity_list - Print list of amenities in OSM file * export_to_wkt - Write out node, way, and area geometries as WKT * mapolution- Show evolution of OSM map * node_density - Create image showing OSM node density * pub_names - Extract names of pubs from OSM file * road_length - Calculate length of highways from an OSM file The Osmium library has extensive support for all types of OSM entities: nodes, ways, relations, and changesets. It allows reading from and writing to OSM files in XML and PBF formats, including change files and full history files. Osmium can store OSM data in memory and on disk in various formats and using various indexes. Its easy to use handler interface allows you to quickly write data filtering and conversion functions. Osmium can create WKT, WKB, OGR, GEOS and GeoJSON geometries for easy conversion into many GIS formats and it can assemble multipolygons from ways and relations. This package is part of the new Osmium family superseding the existing osmium source package. The new Osmium family consists of libosmium, node-osmium, pyosmium, osmium-tool, osmium-contrib osmcoastline. The packages for the Osmium family will be maintained in the Debian GIS team. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779943: octave: Enable large arrays: Build octave such that it can use arrays larger than 2 GB
Package: octave Version: 3.8.2-4 Severity: wishlist Dear Maintainer, the size of a single Octave array cannot exceed 2 GB of memory because octave is not built with --enable-64 flag Additional info: http://wiki.octave.org/Enable_large_arrays:_Build_octave_such_that_it_can_use_arrays_larger_than_2Gb www.gnu.org/software/octave/doc/interpreter/Compiling-Octave-with-64_002dbit-Indexing.html http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2013-May/010083.html It appears this will require 64-bit versions of at least ATLAS, qrupdate and suitesparse as well. There is a recent blog post about an Octave with 64-bit indexing built on Ubuntu 14.04: http://calaba.tumblr.com/post/107087607479/octave-64 The guy explains well why the need of 64-bit indexing, especially for stuff around big data analysis. He is even providing a github repository about this octave recompilation: https://github.com/calaba/octave-3.8.2-enable-64-ubuntu-14.04 Maybe it can help progressing on Debian side ? -- 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.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages octave depends on: ii default-jre-headless 2:1.7-52 ii libamd2.3.1 1:4.2.1-3 ii libarpack2 3.1.5-3 ii libatlas3-base [liblapack.so.3] 3.10.2-7 ii libblas3 [libblas.so.3] 1.2.20110419-10 ii libc62.19-13 ii libcamd2.3.1 1:4.2.1-3 ii libccolamd2.8.0 1:4.2.1-3 ii libcholmod2.1.2 1:4.2.1-3 ii libcolamd2.8.0 1:4.2.1-3 ii libcxsparse3.1.2 1:4.2.1-3 ii libfftw3-double3 3.3.4-2 ii libfftw3-single3 3.3.4-2 ii libfltk-gl1.31.3.2-6+b1 ii libfltk1.3 1.3.2-6+b1 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-2 ii libgcc1 1:4.9.1-19 ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libglpk364.55-1 ii libglu1-mesa [libglu1] 9.0.0-2 ii libgomp1 4.9.1-19 ii libgraphicsmagick++3 1.3.20-3+deb8u1 ii libgraphicsmagick3 1.3.20-3+deb8u1 ii liblapack3 [liblapack.so.3] 3.5.0-4 ii liboctave2 3.8.2-4 ii libqhull62012.1-5 ii libqrupdate1 1.1.2-1 ii libqscintilla2-112.8.4+dfsg-1 ii libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libstdc++6 4.9.1-19 ii libumfpack5.6.2 1:4.2.1-3 ii libx11-6 2:1.6.2-3 ii octave-common3.8.2-4 ii texinfo 5.2.0.dfsg.1-6 Versions of packages octave recommends: ii gnuplot-x11 4.6.6-2 ii libatlas3-base 3.10.2-7 pn pstoeditnone Versions of packages octave suggests: pn octave-doc none pn octave-htmldoc none pn octave-info none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779945: unblock: linux/3.16.7-ckt7-1
Control: tags -1 d-i On 2015-03-06 17:25, Ben Hutchings wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package linux - Stable updates 3.16.7-ckt{5,6,7} with many important fixes, including fix for CVE-2015-1465 - Additional security fixes: CVE-2015-1420, CVE-2015-1593 - Hardware enablement - Olimex A20 OLinuXino LIME2 system - GPIO-controlled backlights - Dumb framebuffer on Allwinner SoCs - Clock fix for Atom E6xx systems - Sound on some Haswell and Bay Trail based systems - Areca Raid ARC12x4 SCSI adapter - Bochs and QXL paravirtual framebuffers - BananaPro board - Fix regression in i915 driver in 3.16.y making some systems unbootable - Fix regression in nfsv4 uid/gid translation cache in 3.13 - Fix regressions in backlight control on some x86 systems in 3.16 - Configuration changes for alpha and hppa, which you can ignore The attached debdiff excludes the generated files under debian/abi/, debian/config.defines.dump, debian/control, debian/control.md5sum, debian/rules.gen and under debian/po/. This will also require an unblock-udeb. Ben. unblock linux/3.16.7-ckt7-1 [...] Ok from my PoV, CC'ing KiBi for a d-i ack. Thanks, ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775913: vala-0.26: diff for NMU version 0.26.1-1.1
Hi Gregor, On Fri, Mar 06, 2015 at 05:02:52PM +0100, gregor herrmann wrote: Control: tags 775913 + pending Dear maintainer, I've prepared an NMU for vala-0.26 (versioned as 0.26.1-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Thanks a lot for preparing that update! Note (but cannot check right now again), that it looks that any binary build with the buggy bindings package that use Gst.MapInfo() function are affected as well. See https://bugzilla.redhat.com/show_bug.cgi?id=1177840, so possibly shotwell. sources.debian.net might reveal others[*] :( [*] possibly rygel as well Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org