Bug#778668: suricata and libhtp-dev: error when trying to install together
Package: libhtp-dev,suricata Version: libhtp-dev/0.5.15-1 Version: suricata/2.0.6-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2015-02-18 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Extracting templates from packages: 88% Extracting templates from packages: 100% Selecting previously unselected package libdb5.3:amd64. (Reading database ... 10938 files and directories currently installed.) Preparing to unpack .../libdb5.3_5.3.28-9_amd64.deb ... Unpacking libdb5.3:amd64 (5.3.28-9) ... Selecting previously unselected package libgcrypt20:amd64. Preparing to unpack .../libgcrypt20_1.6.2-4+b1_amd64.deb ... Unpacking libgcrypt20:amd64 (1.6.2-4+b1) ... Selecting previously unselected package libgmp10:amd64. Preparing to unpack .../libgmp10_2%3a6.0.0+dfsg-6_amd64.deb ... Unpacking libgmp10:amd64 (2:6.0.0+dfsg-6) ... Selecting previously unselected package libnettle4:amd64. Preparing to unpack .../libnettle4_2.7.1-5_amd64.deb ... Unpacking libnettle4:amd64 (2.7.1-5) ... Selecting previously unselected package libhogweed2:amd64. Preparing to unpack .../libhogweed2_2.7.1-5_amd64.deb ... Unpacking libhogweed2:amd64 (2.7.1-5) ... Selecting previously unselected package libffi6:amd64. Preparing to unpack .../libffi6_3.1-2+b2_amd64.deb ... Unpacking libffi6:amd64 (3.1-2+b2) ... Preparing to unpack .../libp11-kit0_0.20.7-1_amd64.deb ... Unpacking libp11-kit0:amd64 (0.20.7-1) over (0.18.5-3) ... Selecting previously unselected package libtasn1-6:amd64. Preparing to unpack .../libtasn1-6_4.2-2_amd64.deb ... Unpacking libtasn1-6:amd64 (4.2-2) ... Selecting previously unselected package libgnutls-deb0-28:amd64. Preparing to unpack .../libgnutls-deb0-28_3.3.8-5_amd64.deb ... Unpacking libgnutls-deb0-28:amd64 (3.3.8-5) ... Selecting previously unselected package libmagic1:amd64. Preparing to unpack .../libmagic1_1%3a5.22+15-1_amd64.deb ... Unpacking libmagic1:amd64 (1:5.22+15-1) ... Selecting previously unselected package libpython2.7-minimal:amd64. Preparing to unpack .../libpython2.7-minimal_2.7.9-1_amd64.deb ... Unpacking libpython2.7-minimal:amd64 (2.7.9-1) ... Selecting previously unselected package python2.7-minimal. Preparing to unpack .../python2.7-minimal_2.7.9-1_amd64.deb ... Unpacking python2.7-minimal (2.7.9-1) ... Selecting previously unselected package python-minimal. Preparing to unpack .../python-minimal_2.7.8-3_amd64.deb ... Unpacking python-minimal (2.7.8-3) ... Selecting previously unselected package mime-support. Preparing to unpack .../mime-support_3.58_all.deb ... Unpacking mime-support (3.58) ... Selecting previously unselected package libexpat1:amd64. Preparing to unpack .../libexpat1_2.1.0-6+b3_amd64.deb ... Unpacking libexpat1:amd64 (2.1.0-6+b3) ... Selecting previously unselected package libpython2.7-stdlib:amd64. Preparing to unpack .../libpython2.7-stdlib_2.7.9-1_amd64.deb ... Unpacking libpython2.7-stdlib:amd64 (2.7.9-1) ... Selecting previously unselected package python2.7. Preparing to unpack .../python2.7_2.7.9-1_amd64.deb ... Unpacking python2.7 (2.7.9-1) ... Selecting previously unselected package libpython-stdlib:amd64. Preparing to unpack .../libpython-stdlib_2.7.8-3_amd64.deb ... Unpacking libpython-stdlib:amd64 (2.7.8-3) ... Processing triggers for man-db (2.7.0.2-5) ... Setting up libpython2.7-minimal:amd64 (2.7.9-1) ... Setting up python2.7-minimal (2.7.9-1) ... Setting up python-minimal (2.7.8-3) ... Selecting previously unselected package python. (Reading database ... 11812 files and directories currently installed.) Preparing to unpack .../python_2.7.8-3_amd64.deb ... Unpacking python (2.7.8-3) ... Selecting previously unselected package libcap-ng0:amd64. Preparing to unpack .../libcap-ng0_0.7.4-2_amd64.deb ... Unpacking libcap-ng0:amd64 (0.7.4-2) ... Selecting previously unselected package libjansson4:amd64. Preparing to unpack .../libjansson4_2.7-1_amd64.deb ... Unpacking libjansson4:amd64 (2.7-1) ... Selecting previously unselected package libltdl7:amd64. Preparing to unpack .../libltdl7_2.4.2-1.11_amd64.deb ... Unpacking libltdl7:amd64 (2.4.2-1.11) ... Selecting previously unselected package libluajit-5.1-common. Preparing to unpack .../libluajit-5.1-common_2.0.3+dfsg-3_all.deb ... Unpacking libluajit-5.1-common (2.0.3+dfsg-3) ... Selecting previously unselected package libluajit-5.1-2:amd64. Preparing to unpack .../libluajit-5.1-2_2.0.3+dfsg-3_amd64.deb ... Unpacking libluajit-5.1-2:amd64 (2.0.3+dfsg-3) ... Selecting previously unselected package libnet1:amd64. Preparing to unpack .../libnet1_1.1.6+dfsg-3_amd64.deb ... Unpacking libnet1:amd64 (1.1.6+dfsg-3) ... Selecting previously unselected package libnspr4:amd64. Preparing to unpack .../libnspr4_2%3a4.10.7-1_amd64.deb ... Unpacking libnspr4:amd64 (2:4.10.7-1) ... Selecting previously unselected package libnss3:amd64.
Bug#777347: RFS: pidgin-gnome-keyring/2.0-1 [ITP] [RFP #714018] -- integrates pidgin (and libpurple) with the system keyring
Hi Luca, On 2015-02-10 22:51, Luca Boccassi wrote: Done, upload on mentors now lists unstable as a distribution in the changelog. Thank you very much! :-) just two minor lintian nitpicks: P: pidgin-gnome-keyring source: debian-watch-may-check-gpg-signature You can add a lintian override for this in debian/source/lintian-overrides. P: pidgin-gnome-keyring: no-upstream-changelog You can override this in debian/pidgin-gnome-keyring.lintian-overrides. Cheers, -- Michael Fladischer Fladi.at signature.asc Description: OpenPGP digital signature
Bug#775892: unblock (pre-approval): python-django/1.7.3-1
Hi Mehdi, On Tue, 17 Feb 2015, Mehdi Dogguy wrote: Le 2015-02-04 09:01, Raphael Hertzog a écrit : it's been two weeks that I have opened this pre-approval request and I got almost no feedback from the release team (except Neil saying that he has no answer for me on IRC). Neil or Niels? Sorry, I meant Niels. I can understand why the former doesn't have any answer for you on this subject. The latter might not have make his mind yet on this because it is not an easy subject. Sure. If I don't hear back from you in the next two days, I will proceed with what I believe to be best, which is: Do you think such a statement helps you in any way? Well, it was not meant to help me, but to help Debian. If the arguments I have put forth were not enough to convince anyone of the release team in a reasonable timeframe, then I hoped that some real-life testing in unstable would be a supplementary proof that it was the safe thing to do. The non-trivial part is to try to draw a line to know what should be allowed to be updated using new upstream releases, and what doesn't. An effort has been made into this direction (See packages like linux, iceweasel, postgresql, etc...) but I think that there is still room for improvement there. Certainly, that's why I was arguing that we could/should handle python-django like the cases that you mention. And if you don't agree, then I would be interested to know what could bring you the required confidence so that we can gain that status (maybe adding autopkgtests to reverse dependencies and running those tests, or stuff like that). Anyway. Based on my blabla about security stuff, I've decided to unblock this package so that it migrates to Jessie. Note that this doesn't mean that we will accept (let's say) 1.7.5 next time. Thanks! -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777347: RFS: pidgin-gnome-keyring/2.0-1 [ITP] [RFP #714018] -- integrates pidgin (and libpurple) with the system keyring
On Wed, Feb 18, 2015 at 4:38 PM, Michael Fladischer wrote: just two minor lintian nitpicks: Generally there is no need to override info and pedantic level lintian complaints because they are not shown by default. P: pidgin-gnome-keyring source: debian-watch-may-check-gpg-signature You can add a lintian override for this in debian/source/lintian-overrides. It is only appropriate to override this if upstream refuses to sign their tarballs. In that case you should include a comment with a link to where they have stated that. P: pidgin-gnome-keyring: no-upstream-changelog You can override this in debian/pidgin-gnome-keyring.lintian-overrides. It is only appropriate to override this if upstream refuses to add an upstream NEWS file or ChangeLog and doesn't have a VCS that could be turned into a changelog. In that case you should include a comment with a link to where they have refused to add those things. -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759530: libc-bin: ldconfig breaks a system
Hi, Could this bug be caused by a corrupt aux-cache[1] (possibly, in addition to a corrupt ld.so.cache)? A bit of google searching suggests that a broken aux-cache can cause ldconfig to seg. fault. With the ld.so.cache itself being corrupt (or sufficiently outdated?), both ldconfig and most other binaries would simply just seg. fault fitting the symptoms pretty well so far. It partly also fits with the removal of libjasper1, as the removed library would force ldconfig to *not* use its cache for said library. Though I cannot explain why it seems like stat itself seg. faults. Assuming my hypothesis is correct, a broken system could be restored by running[2]: $ ldconfig.real --ignore-aux-cache Failling that: $ /var/cache/ldconfig/aux-cache $ ldconfig.real Maybe take a copy of the aux-cache before doing the restore command(s). This way we should be able to re-break the system by re-instating the old aux-cache (and possibly breaking the ld.so.cache). Thanks, ~Niels [1] /var/cache/ldconfig/aux-cache [2] Using ldconfig.real in case /bin/sh got borked by the ld.so.cache as well. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778239: Strange GRE packet forwarding slowness in 3.16.7-ckt2-1~bpo70+1
On 18.02.2015 02:25, Ben Hutchings wrote: On Wed, 2015-02-18 at 00:14 +0100, Sven Hartge wrote: On Thu, 12 Feb 2015 16:33:09 +0100 Sven Hartge s...@svenhartge.de wrote: I have encountered a strange slowness on a router/packetfilter system (Wheezy 7.8 with backported kernel 3.16.7-ckt2-1~bpo70+1) of mine while forwarding GRE packets. Could this be the fix for this bug: https://lists.ubuntu.com/archives/kernel-team/2014-December/052158.html gre: Set inner mac header in gro complete I don't know. I cannot confirm this myself right now, as the only systems affected are in production and I am not able to set up a lab installation right now. As that went into 3.16.7-ckt3, it is therefore included in the current packages in testing/unstable. Well, I've got a window for testing later today. I will report back, if this release fixes the problem I am seeing. Grüße, Sven. signature.asc Description: OpenPGP digital signature
Bug#778669: mediatomb allows anyone to browse and export the whole filesystem
Package: mediatomb-daemon Version: 0.12.1-4 Severity: grave Tag: security This is a regression of the bug that was fixed in #580120, but somehow the patch applied got revert. Anyone can list and download all the file accessible to the mediatomb user via the daemon web interface, which is binded to 0.0.0.0 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580120 -- Olivier Lê Thanh Duong oliv...@lethanh.be
Bug#778621: Unable to access system settings after applying updates
Hi Some additional information about this: Running Gnome 3 graphics. When i move the mouse in the upper left corner Nothing happens. Résolution is ok. When I try to access the system settings, system closes and ask me to login again with my password. Graphic card is GTX 970 - NVidia NVidia proprietary driver installed is : 346.35. I've compiled it with GCC 4.6 Kind regards Mauro
Bug#778620: systemd: Add less to suggests or recommends
Hi, On 02/18/2015 11:03 AM, Floris wrote: I have installed the Debian Base system and add gnome-session, gdm, xserver-xorg-video-nvidia and probably some other packages to get a working gnome environment. Maybe coincidental, but none of these packages recommends less. Only man-db and gzip suggests it. Git have a recommend, but I don't think an end-desktop-user will use it. What does Debian Base system mean to you? less in testing has Priority: important and should be included in all new installs. In Debian 7, it had only Priority: standard and would only be installed if you did not uncheck standard system (or similar) in the installer. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778651: reminiscence segfault and exit on cinematic
Control: tags -1 unreproducible -=| nicolas fargier, 17.02.2015 23:11:47 +0100 |=- Package: reminiscence Version: 0.2.1-2 Severity: important I was able to play the game, but on the first stage ther is a terminal in which you have to insert the battery to make a bridge. When you do this there's a cinematic, but this one is not rendered properly and the game crash. Here is the terminal output : nicolas@INSPIRON:~$ reminiscence Detected PC version rs: graphics.cpp:353: void Graphics::drawPolygon(uint8, bool, const Point*, uint8): Assertion `numPts * 4 0x100' failed. Abandon I was not able to reproduce this. Perhaps a data file is damaged? Running under 'strace -D -e trace=file' shows that when charging the battery GEN.CMD and GEN.POL files are opened. $ md5sum .reminiscence/data/GEN.* 334a59e20d79c24256f30179e62d1799 .reminiscence/data/GEN.CMD b70017fbd9a281071fa2b71cf7d4d3ae .reminiscence/data/GEN.POL $ LANG=C ls -ln .reminiscence/data/GEN.* -rw-r--r-- 1 1000 1000 6364 Aug 17 1993 .reminiscence/data/GEN.CMD -rw-r--r-- 1 1000 1000 7853 Aug 17 1993 .reminiscence/data/GEN.POL Just to be clear that we are trying the same thing, the charging happens at the far right of the first level. The item that is charged is then to be used to power a force-field bridge at left. -- dam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776847: gsasl 1.8.0-6 does not support GSSAPI
Morgan, could you please test 'gsasl' from experimental? It should fix
the GSSAPI issue you reported in #768352. If you can confirm, I can
upload to unstable -- I'm hoping it is possible to fix this before the
release.
On Mon, Feb 16, 2015 at 11:38:46PM +0100, Simon Josefsson wrote:
On 16/02/15 22:13, Simon Josefsson wrote:
It seems clear that the #745332 fix was incorrect. You can see
in the build logs GSSAPI is not enabled since krb5-config isn't
found:
https://buildd.debian.org/status/fetch.php?pkg=gsaslarch=amd64ver=1.8.0-6stamp=1412611018
On considering solutions, I don't like the unpredictability in
depending on libkrb5-dev|libheimdal-dev. The GSSAPI library
used by the binary libgsasl package in Debian will depend on
whether the buildds have Heimdal or MIT installed when you
built the package. Coping with different GSS libraries on
different architecture sounds like a recipe for disaster. For
Jessie, gsasl should be built against the same Kerberos library
on all architectures, unless there is a reason not to -- and I
don't know of a reason. MIT is picked arbitrarily here.
Cc'ing Jelmer (who reported 745332) and Andreas (who uploaded
it) -- any comments? Jelmer, what prompted your initial
report? The way I see it, it is important (for us) that you
buildds don't have multiple Kerberos development packages
installed when they build gsasl. So the old way was the
preferred way, causing heimdal-dev to be removed and
libkrb5-dev to be pulled in. People with other preferences who
build their own packages can surely modify the gsasl package to
their liking.
I've pushed a fix in git and attmpted to upload to
experimental, so you can test the new packages.
The main reason for proposing this change was just to make it
easier to have heimdal-dev installed while working on other parts
of the system. At the moment, building gsasl requires
uninstalling a number of packages for me, that indirectly depend
on heimdal-dev.
With the patch, the intent was to gsasl still build against MIT
kerberos
- e.g. no change in the binary packages. It merely changed the
dependency from libkrb5-dev to libkrb5-multidev, the latter of
which doesn't prevent heimdal-dev from being installed.
Right -- but the patch also had the consequence of completely
disabling GSSAPI in gsasl. Reverting the patch makes GSSAPI work
again.
FWIW the patch applied to the Debian package was different from the
one I provided with the original bug report.
(https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=0001-Depend-on-krb5-multidev-rather-than-libkrb5-dev.patch;att=1;bug=745332)
The upload that closed this bug just changes the dependency
from libkrb5-dev to libkrb5-multidev (rather than krb5-multidev)
and doesn't set KRB5_CONFIG.
(http://anonscm.debian.org/cgit/pkg-xmpp/gsasl.git/commit/?id=1bbeb7bc1e9404daaf1cdef64ec382794a77b217)
Yeah, I made a typo in the first upload, and I thought Andreas fixed
that but now that I look I see that the rest of your patch was not
merged. Oops.
Anyway, as you say, I can manually patch gsasl if I need to, and
at the moment I don't work on any packages that depend on
libgsasl-dev. I still think it would be nice to not have gsasl
conflict with heimdal-dev, but it's not the end of the world if
it doesn't.
Maybe libkrb5-dev|heimdal-dev is a better build-dep -- but I don't
know what holds for Debian buildds: are they allowed to have some
packages pre-installed? If they can never have heimdal-dev
installed (or for some other reason prefer heimdal-dev over
libkrb5-dev), I don't see a problem using libkrb5-dev|heimdal-dev
instead of libkrb5-dev. But if there are no guarantees, I prefer
hard-coding libkrb5-dev to avoid linking with different Kerberos
libraries depending on Debian architecture. Does anyone know?
heimdal and MIT kerberos have enough differences in behaviour that I
think allowing to build against build is likely to cause unexpected
behaviour for users. MIT and Heimdal support different settings in
krb5.conf, for example.
gsasl also currently doesn't build against heimdal-dev:
/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H
-I. -I.. -I../intl -D_FORTIFY_SOURCE=2 -fvisibility=hidden -g -O2
-fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o
gss-extra.lo gss-extra.c libtool: compile: gcc -DHAVE_CONFIG_H -I.
-I.. -I../intl -D_FORTIFY_SOURCE=2 -fvisibility=hidden -g -O2
-fstack-protector-strong -Wformat -Werror=format-security -Wall -c
gss-extra.c -fPIC -DPIC -o .libs/gss-extra.o In file included
from /usr/include/gssapi.h:39:0, from gss-extra.h:30, from
gss-extra.c:28: gss-extra.c:43:9: error: expected identifier or '('
before '' token gss_OID GSS_C_NT_HOSTBASED_SERVICE = tmp; ^
For exactly this reason, cyrus sasl builds modules
Bug#777753: [Reproducible-builds] Bug#777753: gcc: LTO produces unreproducible debug information
I have to correct my last statement. It is still necessary to add
-flto-partition=none when using -flto in a package. My earlier statement
came from the wrong understanding of buildid as explained in the gcc bug [3].
A new patch [4] was submitted by Richard Biener. Together these patches [1,2,3]
were enough to fix all my testcases and at least build some of the affected
packages reproducible (I haven't tested all of them).
-flto-partition=none wasn't necessary anymore in my tests
The gcc-4.9 patch used for this test is attached.
[1] https://gcc.gnu.org/viewcvs/gcc?view=revisionrevision=220678
[2] https://gcc.gnu.org/viewcvs/gcc?view=revisionrevision=220613
[3] https://gcc.gnu.org/viewcvs/gcc?view=revisionrevision=220735
[4] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65015#c22diff -u gcc-4.9-4.9.2/debian/rules.patch gcc-4.9-4.9.2/debian/rules.patch
--- gcc-4.9-4.9.2/debian/rules.patch
+++ gcc-4.9-4.9.2/debian/rules.patch
@@ -232,6 +232,7 @@
sys-auxv-header \
libcilkrts-targets \
go-use-gold \
+ drop_opt \
ifeq ($(with_softfloat),yes)
debian_patches += arm-multilib-soft-float
only in patch2:
unchanged:
--- gcc-4.9-4.9.2.orig/debian/patches/drop_opt.diff
+++ gcc-4.9-4.9.2/debian/patches/drop_opt.diff
@@ -0,0 +1,46 @@
+Bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65015
+
+--- a/src/gcc/dwarf2out.c
b/src/gcc/dwarf2out.c
+@@ -19196,6 +19196,9 @@ gen_producer_string (void)
+ case OPT__sysroot_:
+ case OPT_nostdinc:
+ case OPT_nostdinc__:
++ case OPT_fpreprocessed:
++ case OPT_fltrans_output_list_:
++ case OPT_fresolution_:
+ /* Ignore these. */
+ continue;
+ default:
+@@ -23984,8 +23987,13 @@ dwarf2out_finish (const char *filename)
+ gen_remaining_tmpl_value_param_die_attribute ();
+
+ /* Add the name for the main input file now. We delayed this from
+- dwarf2out_init to avoid complications with PCH. */
+- add_name_attribute (comp_unit_die (), remap_debug_filename (filename));
++ dwarf2out_init to avoid complications with PCH.
++ For LTO produced units use a fixed artificial name to avoid
++ leaking tempfile names into the dwarf. */
++ if (!in_lto_p)
++add_name_attribute (comp_unit_die (), remap_debug_filename (filename));
++ else
++add_name_attribute (comp_unit_die (), artificial);
+ if (!IS_ABSOLUTE_PATH (filename) || targetm.force_at_comp_dir)
+ add_comp_dir_attribute (comp_unit_die ());
+ else if (get_AT (comp_unit_die (), DW_AT_comp_dir) == NULL)
+--- a/src//gcc/varasm.c
b/src//gcc/varasm.c
+@@ -6964,7 +6964,12 @@ default_file_start (void)
+ fputs (ASM_APP_OFF, asm_out_file);
+
+ if (targetm.asm_file_start_file_directive)
+-output_file_directive (asm_out_file, main_input_filename);
++{
++ if (in_lto_p)
++output_file_directive (asm_out_file, artificial);
++ else
++output_file_directive (asm_out_file, main_input_filename);
++}
+ }
+
+ /* This is a generic routine suitable for use as TARGET_ASM_FILE_END
Bug#773541: [Pkg-gnupg-maint] Bug#773541: Bug#773541: uninitalized pointer read
Control: tags 773541 + moreinfo On Tue 2015-01-06 23:06:50 -0500, NIIBE Yutaka wrote: Hello, Thanks for your reviewing and reporting. On 12/20/2014 02:19 AM, Joshua Rogers wrote: Package: gnupg2 Version: 2.1.1 Severity: normal [...] On line 204 of crlfetch.c 'hd' is run through http_get_status_code, but it is possible for 'hd' not to be set, if opt.disable_http is true.(see lines 192-202) When opt.disable_http is true, err is set (at line 199). The expression in question is: err? 9 : http_get_status_code (hd) The function call http_get_status_code (hd) is not evaluated in that case (and its value is 9). gniibe's explanation suggests that this is not a bug, so i'm closing it. if you think it's still a bug, please reopen it and provide more details. --dkg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778302: MATE: Default file browser for Places submenu indeterministically set to applications that are not Caja
Am 13.02.2015 um 12:48 schrieb Mike Gabriel: Happy about opinions and feedback. Thanks! I have been installing two laptops with vanilla mate + jessie, and found more similar issues. I don't know if it's worth opening new threads for each. For example, I did install vim and now plain text files are being opened with vim (!) instead of pluma. jpgs are opened with iceweasel instead of eom ... Cheers, Philipp -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778239: Strange GRE packet forwarding slowness in 3.16.7-ckt2-1~bpo70+1
On 18.02.2015 09:17, Sven Hartge wrote: On 18.02.2015 02:25, Ben Hutchings wrote: On Wed, 2015-02-18 at 00:14 +0100, Sven Hartge wrote: On Thu, 12 Feb 2015 16:33:09 +0100 Sven Hartge s...@svenhartge.de wrote: I have encountered a strange slowness on a router/packetfilter system (Wheezy 7.8 with backported kernel 3.16.7-ckt2-1~bpo70+1) of mine while forwarding GRE packets. Could this be the fix for this bug: https://lists.ubuntu.com/archives/kernel-team/2014-December/052158.html gre: Set inner mac header in gro complete I don't know. I cannot confirm this myself right now, as the only systems affected are in production and I am not able to set up a lab installation right now. As that went into 3.16.7-ckt3, it is therefore included in the current packages in testing/unstable. Well, I've got a window for testing later today. I will report back, if this release fixes the problem I am seeing. Yes, this patch fixes this problem for me. Should I close the bug or do you want to do it? Grüße, Sven. signature.asc Description: OpenPGP digital signature
Bug#778529: lame: fill_buffer_resample segmentation fault
Control: tags -1 + patch Am Mittwoch, den 18.02.2015, 10:53 +0100 schrieb Fabian Greffrath: But this is still not the cause of the crash, sigh! Patching the sample to report 1 channel, it still crashes at the same location. Phew, got it. This time, it was a simple logical error in the lame sources: The fake sample rate of the fuzzed input file is 1631 kHz which lame tries to sample down to 48 kHz in the process of encoding. The ratio between input and output samplerates is thus 1631/48000=339.79 which is very close, but only close, to the integer value 340. In libmp3lame/util.c:fill_buffer_resample(), lame checks if the ratio between input and output sample rate is an integer by the following calculation (l. 547): intratio = (fabs(resample_ratio - floor(.5 + resample_ratio)) .0001); Please note that the value of .0001, which the fabs() of the difference is compared against here, is a rather arbitrary value and is *not* sufficient to tell the difference between an integer and a floating point ratio in the case at hand (where it is actually about 0.2)! The value of intratio is added to another variable filter_l a few lines later, which in turn is used in the calculation of the value of the offset variable, which triggers the assertion (l. 594f): offset = (time0 - esv-itime[ch] - (j + .5 * (filter_l % 2))); assert(fabs(offset) = .501); In the case at hand, filter_l has got an even value by addition of intratio, which in turn was set to 1 in good faith that the sample rate ratio is integer, whereas in reality it is not. Thus, the latter part of the equation above is not substracted from the offset variable, so its value is higher than it should. In the following line, offset is used to calculate the value of joff, which is used to dereference esv-blackfilt, where it causes an overflow and finally a segfault (l. 608): xvalue += y * esv-blackfilt[joff][i]; The trivial fix for this would be to decrease the arbitrary value of .0001 by another factor 10 and compare against 0.1, but this would only suffice until the next fuzzed sample with an even higher sample rate is provided. I thus suggest to compare against the smallest number of type double (resample_ratio is of type double) that can still be distinguished from 0: DBL_EPSILON. The attached patch does exact that. Cheers, Fabian -- Dr.-Ing. Fabian Greffrath, Dipl.-Phys. RWTH Aachen University Institute of Mineral Engineering (GHI) Mauerstr. 5, D-52064 Aachen Phone: +49-241-8094979, Fax: +49-241-8092226 Subject: Fix decision if sample rate ratio is an integer value or not If the sample rate of the input file is sufficiently close to an integer multiple of the output sample rate, the value of the intratio variable is calculated incorrectly. This leads to further values being miscalculated up to the joff variable which is used as an index to dereference the esv-blackfilt array. This leads top an overflow and causes a segmentation fault. Author: Fabian Greffrath fabian+deb...@greffrath.com Bug-Debian: https://bugs.debian.org/778529 --- a/libmp3lame/util.c +++ b/libmp3lame/util.c @@ -26,6 +26,7 @@ # include config.h #endif +#include float.h #include lame.h #include machine.h #include encoder.h @@ -544,7 +545,7 @@ fill_buffer_resample(lame_internal_flags if (bpc BPC) bpc = BPC; -intratio = (fabs(resample_ratio - floor(.5 + resample_ratio)) .0001); +intratio = (fabs(resample_ratio - floor(.5 + resample_ratio)) = DBL_EPSILON); fcn = 1.00 / resample_ratio; if (fcn 1.00) fcn = 1.00;
Bug#767597: [debian-mysql] Bug#767597: Bug#767597: mariadb-server-10.0: piuparts / Package purging left files on system
All issues mentioned in this bug report seems to have been fixed. Piuparts pass successfully e.g. here: https://piuparts.debian.org/sid/source/m/mariadb-10.0.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778671: mirrors: Mirror debian.mirror.evertje.net unreachable
Package: mirrors Severity: normal Dear Maintainer, * What led up to the situation? I tried mirror debian.mirror.evertje.net but it does not resolve in to an IP address anymore for at least a couple of days now. * What exactly did you do (or not do) that was effective (or ineffective)? Try to connect for several days * What was the outcome of this action? Connection fails * What outcome did you expect instead? Connection succeeds and apt-get update working like normal -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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#778374: [php-maint] Bug#778374: Bug#778374: [pkg-horde] Bug#778374: php5 5.6.5 fully breaks Horde packages in Debian jessie
On Tue, Feb 17, 2015, at 20:52, David Prévot wrote: P.-S.: getting in touch with the people running ci.d.n may be worth it to help track possible regressions in the future (by running a specific instance of tests with a new PHP version before uploading it to stable). Thanks for the tip, that is a terrific idea! Cheers, -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778529: lame: fill_buffer_resample segmentation fault
Am Dienstag, den 17.02.2015, 11:19 +0100 schrieb Fabian Greffrath: But, the sample at hand reports -251 channels. Adding ... || gfp-num_channels 0) to Maks' patch actually fixes the crash. But this is still not the cause of the crash, sigh! Patching the sample to report 1 channel, it still crashes at the same location. - Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778620: systemd: Add less to suggests or recommends
Op Wed, 18 Feb 2015 12:04:49 +0100 schreef Ansgar Burchardt ans...@debian.org: Hi, On 02/18/2015 11:03 AM, Floris wrote: I have installed the Debian Base system and add gnome-session, gdm, xserver-xorg-video-nvidia and probably some other packages to get a working gnome environment. Maybe coincidental, but none of these packages recommends less. Only man-db and gzip suggests it. Git have a recommend, but I don't think an end-desktop-user will use it. What does Debian Base system mean to you? standard system less in testing has Priority: important and should be included in all new installs. In Debian 7, it had only Priority: standard and would only be installed if you did not uncheck standard system (or similar) in the installer. Ansgar You are right. less have also the priority important in unstable. So one way or another I must have removed it from my system. You may close this bug. floris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778446: python-argh: Please provide Python 3 package
On 18 Feb 2015 19:56, Marco Nenciarini mnen...@debian.org wrote: I've tagged the 0.26.1-1 version on git and uploaded the package yesterday. However it is still in NEW queue, but judging from the queue size it could take some time to be approved.. Thanks for this. Some of my packages left NEW last weekend, so fingers crossed it won't be too long...
Bug#777237: Sagemath has special needs
Hi, Le 11/02/2015 21:44, Bill Allombert a écrit : On Fri, Feb 06, 2015 at 07:08:49PM +0100, Julien Puydt wrote: Package: pari-gp Version: 2.7.2-1 Severity: wishlist Hello Julien, While trying to use the debian package in sagemath, it turned out two things were lacking to make it work: - they use anal.h ; This is a private header file, there is no good purpose to include in the binary package. If SAGE really needs it, they should just copy the part they need. There is not interface garanty anyway. I don't know what they use it for. - they also have backported patches to add cb_pari_err_handle from upstream's repository (see end of this mail). Can we get those in debian too? This patch is breaking the ABI and API, thus this is not possible to apply it. Since it's backported from upstream, it will be in some version at some point : do you have an ETA? Beside SAGE could do the same thing without patching PARI, by using the standard PARI error trapping mechanism (iferr_env and global_err_data). This would be much better. That would be the sensible thing to do, but sage developers have a terrible tendency to patch upstream instead of using upstream. On some occasions, I have proposed them to replace an upstream patch with a one-line patch to their code, because the api to configure what they wanted was right there... It looks like they've been toying with pari error handling for months: http://trac.sagemath.org/ticket/14894 Is there a better way to do what they want ? Snark -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777664: [Pkg-salt-team] Bug#777664: Bug#777664: salt-minion: Make log file readable by adm group
Am Sonntag, den 15.02.2015, 00:03 +1100 schrieb Joe Healy: Hi Ben, On Wed, Feb 11, 2015 at 9:18 PM, Benjamin Drung benjamin.dr...@profitbricks.com wrote: I'll make these changes. You are partially right - I/we do need a sponsor, but I haven't asked for one yet as I want to make sure the latest addition to the packaging (salt-api) is ok before I do (hence the -3...). Working through the patch, setting the directory mode to 2750 causes the lintian issue non-standard-dir-perm. Is this needed? I'm not sure I follow the reason for it (the directory permission change). Yes, this change is needed. A root:adm owned directory with mode 2750 gives root the permission to read and write to that directory and the group adm to read. Thanks to setgid, files written to the directory by root:root processes are stored as root:adm. The samba package does the (nearly) same and overrides the lintian warning: # This is on purpose to hide sensitive information samba-common: non-standard-dir-perm var/log/samba/ 0750 != 0755 -- Benjamin Drung System Developer ProfitBricks GmbH - The IaaS-Company Greifswalder Str. 207 D - 10405 Berlin Mail: benjamin.dr...@profitbricks.com Fax: +49 30 577 008 598 URL: http://www.profitbricks.com Sitz der Gesellschaft: Berlin. Registergericht: Amtsgericht Charlottenburg, HRB 125506 B. Geschäftsführer: Andreas Gauger, Achim Weiss. signature.asc Description: This is a digitally signed message part
Bug#778546: RFS: miceamaze/4.2-1 -- video game with mice in a maze
2015-02-18 3:17 GMT+01:00 Paul Wise p...@debian.org: On Tue, Feb 17, 2015 at 10:09 PM, Raphaël Champeimont wrote: I have (I hope) addressed the blocking issue and some of your recommendations also. You have addressed the blocking issue, uploaded to Debian. OK thank you very much. I'm not sure I can fix this, because all I do is ask for SDL to setup a full-screen OpenGL display, but don't think it is possible to specify the behavior on multi-screen. It sounds like SDL2 might have better support for this. I'm adding a bug report to my github project, so I can remember to check this when switching to SDL 2. Yes. Actually I had checked this list and noticed nothing applied for miceamaze. I have added the changelog entry. BTW, since that entry isn't related to the new upstream release there was no need to indent it under that item in debian/changelog. yes, that's right Did I do that? The only thing I changed is experimental instead of unstable. Is it what you are talking about? I'm talking about the change from Priority optional to extra in debian/control, which you mentioned in the debian/changelog entry for 1.8-2. OK I see. Last time I checked, SDL2 was not shipped with most linux distributions (in stable releases) so I wanted to wait. Fair enough. I'm surprised because gcc never complained about missing includes. I will look into that later (this is not fixed in this release). The includes aren't completely missing so gcc would not complain, the include-what-you-use tool complains about indirectly including headers via other headers instead of directly including them, when you directly use their functions/macros/classes. The reason is that doing only direct includes reduces the amount of code the compiler has to parse, which speeds things up. It also helps with the other goal of include-what-you-use, which is to remove headers that are no longer used. At least this is how I interpret it. ok I understand I agress this might have been another option, but actually I did not make this change myself and the other developped preferred to do like this. I see. It is probably too late to change since the images are already combined and can't be un-combined unless the other developer has a copy of the original images? Perhaps you could discuss the idea with them? That's true but I cannot provide anything better because I just downloaded it like this and did not change anything. I see. It is a bit sad you can't change the music in the same ways as the original person did, but that is your choice I guess. So if I want to fix that, I should build two packages: miceamaze with the binary file and miceamaze-data with the rest? Indeed, some info about that on the wiki. https://wiki.debian.org/PkgSplit ok thanks -- bye, pabs https://wiki.debian.org/PaulWise Regards, Raphael
Bug#773223: [debian-mysql] Bug#773223: mariadb-server-10.0: Fails to upgrade to 10.0.15-2
I will close this issue unless the original reporter adds some more information that would enable us to reproduce the bug. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773223 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752134: ftp.debian.org: Please provide signed checksums for all files
Package: ftp.debian.org Followup-For: Bug #752134 Same here. Currently the /doc and /tools directories can only be downloaded using ftp or rsync, since there is no file that lists what files they contain. Enrico -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778670: suricata: --build-info reports wrong libhtp version
Package: suricata Version: 2.0.6-1 Severity: minor $ suricata --build-info This is Suricata version 2.0.6 (rev 12f14ae) [snip] compiled with LibHTP v0.5.10, linked against LibHTP v0.5.10 = wrong version $ suricata -V This is Suricata version 2.0.6 (rev 12f14ae) It seems the library version is harcoded, in this patch: https://sources.debian.net/src/suricata/2.0.6-1/debian/patches/10-fix-missing-script-autoreconf.patch -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.18.0-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages suricata depends on: ii libc62.19-15 ii libcap-ng0 0.7.4-2 ii libgcrypt20 1.6.2-4+b1 ii libgnutls-deb0-283.3.8-5 ii libjansson4 2.7-1 ii libluajit-5.1-2 2.0.3+dfsg-3 ii libmagic11:5.22+15-1 ii libnet1 1.1.6+dfsg-3 ii libnetfilter-queue1 1.0.2-2 ii libnfnetlink01.0.1-3 ii libnspr4 2:4.10.7-1 ii libnss3 2:3.17.2-1.1 ii libpcap0.8 1.6.2-2 ii libpcre3 2:8.35-3.3 ii libprelude2 1.0.0-11.4 ii libyaml-0-2 0.1.6-3 ii python 2.7.8-3 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages suricata recommends: ii oinkmaster 2.0-4 ii snort-rules-default 2.9.7.0-4 suricata suggests no packages. -- no debconf information -- Arturo Borrero González -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778620: systemd: Add less to suggests or recommends
Op Wed, 18 Feb 2015 07:31:57 +0100 schreef Martin Pitt mp...@debian.org: Hello Floris, floris [2015-02-17 15:47 +0100]: from man journalctl: The output is paged through less by default, and long lines are truncated to screen width. The hidden part can be viewed by using the left-arrow and right- arrow keys. In particular it's $PAGER, and it defaults to less. But I'm not sure whether we should add a suggests to it -- it rather seems like if you really have a minimal system without any pager, then you probably have a good reason for it. I have installed the Debian Base system and add gnome-session, gdm, xserver-xorg-video-nvidia and probably some other packages to get a working gnome environment. Maybe coincidental, but none of these packages recommends less. Only man-db and gzip suggests it. Git have a recommend, but I don't think an end-desktop-user will use it. Also, systemd is installed by default, so chances are high that a user would never actually see the suggestion. When a program behave strange, I always look at the suggested packages. (maybe I am the only one) I admit, the man pages had the same problem as the journal, so eventually that package had pointed me to less. So I'm inclined to wontfix and/or close this. But this isn't a strong opinion, adding a Suggests: less is fairly harmless after all. Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761730: tracker.d.o: please provide links to https://security-tracker.debian.org/tracker/source-package/$PKG
On Wed, 18 Feb 2015, Raphael Hertzog wrote:
One thing that comes to my mind is that we probably also want the
associated Debian bug number when there's an associated bug report.
So instead of a plain CVE identifier we probably want a hash:
{ 'id': 'CVE--', 'bug': '12345', 'severity': 'low' }
That way we could also export the severity and easily add more data
in case of future needs.
And I just thought that I would like to have the status... in particular
to differentiate no-dsa issues.
status: open|no-dsa|end-of-life|resolved ?
or just
status: open|resolved
no-dsa: True|False
This would suggest to have a single list of issues per suite and have
the status/severity in the data of each CVE:
'bind9': {
'squeeze': {
'CVE--': {
'status': 'open|resolved',
'severity': 'unimportant|low|normal|high|unknown',
'no-dsa': True|False,
'end-of-life': True|False,
},
...
],
'wheezy': [
...
]
},
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778674: apt-p2p: fails to start (throws exception)
Package: apt-p2p Version: 0.1.7 Severity: grave Justification: renders package unusable Hi, I wanted to test apt-p2p and noticed that it won't even start: [ ~ ] $ sudo apt-p2p [sudo] password for toma: 2015-02-18 11:47:31+0100 [-] Log opened. 2015-02-18 11:47:31+0100 [-] Loading config files: '/etc/apt-p2p/apt-p2p.conf', '/root/.apt-p2p/apt-p2p.conf', '' 2015-02-18 11:47:31+0100 [-] Successfully loaded config files: '/etc/apt-p2p/apt-p2p.conf' 2015-02-18 11:47:31+0100 [-] Starting application with uid/gid 141/65534 2015-02-18 11:47:31+0100 [-] Starting main application server 2015-02-18 11:47:31+0100 [-] Traceback (most recent call last): 2015-02-18 11:47:31+0100 [-] File /usr/sbin/apt-p2p, line 73, in module 2015-02-18 11:47:31+0100 [-] from apt_p2p.apt_p2p import AptP2P 2015-02-18 11:47:31+0100 [-] File /usr/lib/python2.7/dist-packages/apt_p2p/apt_p2p.py, line 19, in module 2015-02-18 11:47:31+0100 [-] from MirrorManager import MirrorManager 2015-02-18 11:47:31+0100 [-] File /usr/lib/python2.7/dist-packages/apt_p2p/MirrorManager.py, line 16, in module 2015-02-18 11:47:31+0100 [-] from AptPackages import AptPackages 2015-02-18 11:47:31+0100 [-] File /usr/lib/python2.7/dist-packages/apt_p2p/AptPackages.py, line 40, in module 2015-02-18 11:47:31+0100 [-] from apt.progress.old import OpProgress 2015-02-18 11:47:31+0100 [-] ImportError: No module named old Just letting you know and putting it under RC. Tomasz -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apt-p2p depends on: ii adduser 3.113+nmu3 ii python 2.7.8-3 ii python-apt 0.9.3.11 ii python-debian0.1.25 ii python-pysqlite2 2.6.3-3 ii python-twisted-web2 8.1.0-3 pn python:any none apt-p2p recommends no packages. apt-p2p 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#778673: unblock: suricata/2.0.6-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package suricata
We just uploaded to unstable a new suricata version (2.0.6-2) which
would require another unblock to enter jessie.
This is the debdiff, which was generated with (unfiltered):
% debdiff suricata_2.0.6-1.dsc suricata_2.0.6-2.dsc
diff -Nru suricata-2.0.6/debian/changelog suricata-2.0.6/debian/changelog
--- suricata-2.0.6/debian/changelog 2015-02-18 11:42:51.0 +0100
+++ suricata-2.0.6/debian/changelog 2015-02-18 11:33:51.0 +0100
@@ -1,3 +1,14 @@
+suricata (2.0.6-2) unstable; urgency=medium
+
+ [ Arturo Borrero Gonzalez ]
+ * d/patches: drop 10-fix-missing-script-autoreconf.patch (Closes: #778670)
+ * d/rules: prevent not .so libhtp files from entering binary suricata package
+
+ [ Pierre Chifflier ]
+ * Add conflicts/replaces fields for transition from libhtp (Closes: #778668)
+
+ -- Pierre Chifflier pol...@debian.org Wed, 18 Feb 2015 11:19:31 +0100
+
suricata (2.0.6-1) unstable; urgency=medium
[ Pierre Chifflier ]
diff -Nru suricata-2.0.6/debian/control suricata-2.0.6/debian/control
--- suricata-2.0.6/debian/control 2015-02-18 11:42:51.0 +0100
+++ suricata-2.0.6/debian/control 2015-02-18 11:33:51.0 +0100
@@ -30,6 +30,8 @@
Depends: ${shlibs:Depends},
${misc:Depends},
${python:Depends}
+Conflicts: libhtp1 ( 0.5.16), libhtp-dev ( 0.5.16)
+Replaces: libhtp1 ( 0.5.16), libhtp-dev ( 0.5.16)
Recommends: oinkmaster, snort-rules-default, python
Description: Next Generation Intrusion Detection and Prevention Tool
Suricata is a network Intrusion Detection System (IDS). It is based on
diff -Nru suricata-2.0.6/debian/patches/10-fix-missing-script-autoreconf.patch
suricata-2.0.6/debian/patches/10-fix-missing-script-autoreconf.patch
--- suricata-2.0.6/debian/patches/10-fix-missing-script-autoreconf.patch
2015-02-18 11:42:51.0 +0100
+++ suricata-2.0.6/debian/patches/10-fix-missing-script-autoreconf.patch
1970-01-01 01:00:00.0 +0100
@@ -1,13 +0,0 @@
-Index: suricata/libhtp/configure.ac
-===
suricata.orig/libhtp/configure.ac 2014-04-01 08:25:37.604832456 +0200
-+++ suricata/libhtp/configure.ac 2014-04-02 20:11:01.504628889 +0200
-@@ -3,7 +3,7 @@
- dnl Initialization macros
- dnl --
-
--AC_INIT([LibHTP], m4_esyscmd([./get-version.sh VERSION]))
-+AC_INIT([LibHTP], 0.5.10)
- AM_INIT_AUTOMAKE()
-
- AC_CONFIG_HEADERS([config.h])
diff -Nru suricata-2.0.6/debian/patches/series
suricata-2.0.6/debian/patches/series
--- suricata-2.0.6/debian/patches/series2015-02-18 11:42:51.0
+0100
+++ suricata-2.0.6/debian/patches/series1970-01-01 01:00:00.0
+0100
@@ -1 +0,0 @@
-10-fix-missing-script-autoreconf.patch
diff -Nru suricata-2.0.6/debian/rules suricata-2.0.6/debian/rules
--- suricata-2.0.6/debian/rules 2015-02-18 11:42:51.0 +0100
+++ suricata-2.0.6/debian/rules 2015-02-18 10:57:35.0 +0100
@@ -35,7 +35,11 @@
rm -rf $(DEB_DESTDIR)/usr/lib/python*;\
(cd scripts/suricatasc \
python -B setup.py install --install-layout=deb --prefix
$(DEB_DESTDIR)/usr)
+ # we don't want to deploy any of the libhtp files, only the .so
rm -rf $(CURDIR)/debian/suricata/usr/lib/*/*.la
+ rm -rf $(CURDIR)/debian/suricata/usr/lib/*/*.a
+ rm -rf $(CURDIR)/debian/suricata/usr/lib/*/pkgconfig
+ rm -rf $(CURDIR)/debian/suricata/usr/include
override_dh_auto_configure:
dh_auto_configure -- $(CONFIGURE_ARGS)
unblock suricata/2.0.6-2
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778675: openssh-server: conf.d directory for configuration snippets (similar to nginx or apache)
Package: openssh-server Version: 1:6.6p1-2ubuntu2 Severity: wishlist Tags: upstream Dear Maintainer, It would be nice if openssh-server had a config directory in the same vein as /etc/nginx/conf.d. This would allow third party packages to add config blobs without mangling /etc/ssh/sshd_config. As an example, I would like to add support for sftp-internal iff a specific package is installed (For sftp only access to a chrooted path). If there was a conf.d directory, the deb package could have dropped the relevant config block and SIGHUP'd sshd. With the current setup, I'll probably be forced to use debian overrides to replace the existing /etc/ssh/sshd_config. -- System Information: Debian Release: jessie/sid APT prefers trusty-updates APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty') Architecture: amd64 (x86_64) Kernel: Linux 3.13.0-30-generic (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openssh-server depends on: ii adduser3.113+nmu3ubuntu3 ii debconf [debconf-2.0] 1.5.51ubuntu2 ii dpkg 1.17.5ubuntu5.3 ii init-system-helpers1.14 ii libc6 2.19-0ubuntu6.3 ii libck-connector0 0.4.5-3.1ubuntu2 ii libcomerr2 1.42.9-3ubuntu1 ii libdbus-1-31.6.18-0ubuntu4.1 ii libgssapi-krb5-2 1.12+dfsg-2ubuntu4.2 ii libkrb5-3 1.12+dfsg-2ubuntu4.2 ii libpam-modules 1.1.8-1ubuntu2 ii libpam-runtime 1.1.8-1ubuntu2 ii libpam0g 1.1.8-1ubuntu2 ii libselinux12.2.2-1ubuntu0.1 ii libssl1.0.01.0.1f-1ubuntu2.5 ii libwrap0 7.6.q-25 ii lsb-base 4.1+Debian11ubuntu6 ii openssh-client 1:6.6p1-2ubuntu2 ii openssh-sftp-server1:6.6p1-2ubuntu2 ii procps 1:3.3.9-1ubuntu2 ii sysv-rc2.88dsf-41ubuntu6 ii zlib1g 1:1.2.8.dfsg-1ubuntu1 Versions of packages openssh-server recommends: ii ncurses-term 5.9+20140118-1ubuntu1 ii ssh-import-id 3.21-0ubuntu1 ii xauth 1:1.0.7-1ubuntu1 Versions of packages openssh-server suggests: pn molly-guard none pn monkeysphere none pn rssh none pn ssh-askpass none ii ufw 0.34~rc-0ubuntu2 -- debconf information: openssh-server/permit-root-login: false -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778656: Malformed access ACL
Control: tag -1 - unreproducible moreinfo Am 18.02.2015 um 07:27 schrieb Martin Pitt: Control: tag -1 unreproducible moreinfo Hey Michael, I tried to reproduce this in various ways. I created a persistant journal under 215-12, rebooted, upgraded to 219-1, dpkg-reconfigured, apt-get install --reinstall'ed, etc., but I can't get this to happen. Here are the steps to reproduce: Assume you have created /var/log/journal in the past, then systemd.postinst will have applied the ACL (or you followed the instructions in README.Debian): # remove existing /var/log/journal $ rm -rf /var/log/journal $ install -d -g systemd-journal /var/log/journal $ setfacl -R -nm g:adm:rx,d:g:adm:rx /var/log/journal # simulate a reboot $ systemctl restart systemd-journald.service $ getfacl /var/log/journal/567a68a5c2672114bcf5192d0008/system.journal getfacl: Entferne führende '/' von absoluten Pfadnamen # file: var/log/journal/567a68a5c2672114bcf5192d0008/system.journal # owner: root # group: root user::rw- group::r-x #effective:r-- group:adm:r-x #effective:r-- mask::r-- other::--- # Apply the ACLs shipped by systemd (which would happen on next reboot) $ systemd-tmpfiles --create /usr/lib/tmpfiles.d/systemd.conf $ getfacl /var/log/journal/567a68a5c2672114bcf5192d0008/system.journal getfacl: Entferne führende '/' von absoluten Pfadnamen # file: var/log/journal/567a68a5c2672114bcf5192d0008/system.journal # owner: root # group: root user::rw- group::r-x group:adm:r-x group:adm:r-x mask::r-x other::--- # Note the duplicate adm group # Upgrade systemd i.e. re-run systemd.postinst $ dpkg-reconfigure systemd setfacl: /var/log/journal/567a68a5c2672114bcf5192d0008: Malformed access ACL `user::rwx,group::r-x,group:adm:r-x,group:adm:r-x,mask::r-x,other::r-x': Duplicate entries at entry 4 setfacl: /var/log/journal/567a68a5c2672114bcf5192d0008/system.journal: Malformed access ACL `user::rw-,group::r-x,group:adm:r-x,group:adm:r-x,mask::r-x,other::---': Duplicate entries at entry 4 setfacl: /var/log/journal/567a68a5c2672114bcf5192d0008/user-1000.journal: Malformed access ACL `user::rw-,user:michael:r--,group::r-x,group:adm:r-x,group:adm:r-x,mask::r-x,other::---': Duplicate entries at entry 5 et voila! The problem apparently comes from systemd.conf and our existing postinst/README.Debian using different ACLs, leading to the duplicate group:adm entry when both are applied. -- 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#681691: Having same error after updating kernel
Version: 1.58 Hello, I never had this error before using the kernel from wheezy-backports, but now apt said that there are these updates available: linux-compiler-gcc-4.6-x86 linux-headers-3.16.0-0.bpo.4-amd64 linux-headers-3.16.0-0.bpo.4-common linux-image-3.16.0-0.bpo.4-amd64 I installed them and it called update-grub as expected. Before the updates update-grub correctly detected all 4 operating systems on my computer and I could start them all without problems. But now I experienced just the same error and it only detected the current running OS, Debian Wheezy, and Windows 8. After mounting the other two partitions manually everything works. The versions that the packages were updated to: # aptitude versions linux-compiler-gcc-4.6-x86 linux-headers-3.16.0-0.bpo.4-amd64 linux-headers-3.16.0-0.bpo.4-common linux-image-3.16.0-0.bpo.4-amd64 Paket linux-compiler-gcc-4.6-x86: i A 3.16.7-ckt4-3~bpo70+1 wheezy-backports 800 Paket linux-compiler-gcc-4.6-x86:i386: p 3.16.7-ckt4-3~bpo70+1 wheezy-backports 800 Paket linux-headers-3.16.0-0.bpo.4-amd64: i 3.16.7-ckt4-3~bpo70+1 wheezy-backports 800 Paket linux-headers-3.16.0-0.bpo.4-amd64:i386: p 3.16.7-ckt4-3~bpo70+1 wheezy-backports 800 Paket linux-headers-3.16.0-0.bpo.4-common: i A 3.16.7-ckt4-3~bpo70+1 wheezy-backports 800 Paket linux-headers-3.16.0-0.bpo.4-common:i386: p 3.16.7-ckt4-3~bpo70+1 wheezy-backports 800 Paket linux-image-3.16.0-0.bpo.4-amd64: i A 3.16.7-ckt4-3~bpo70+1 wheezy-backports 800 Paket linux-image-3.16.0-0.bpo.4-amd64-dbg: p 3.16.7-ckt4-3~bpo70+1 wheezy-backports 800 Paket linux-image-3.16.0-0.bpo.4-amd64:i386: p 3.16.7-ckt4-3~bpo70+1 wheezy-backports 800 The versions of the responsible packages: # aptitude versions grub2-common os-prober Paket grub2-common: i A 1.99-27+deb7u2stable 900 p A 2.02~beta2-21 unstable 10 Paket grub2-common:i386: p 1.99-27+deb7u2stable 900 p 2.02~beta2-21 unstable 10 Paket os-prober: i A 1.58 stable 900 p A 1.65 unstable 10 Paket os-prober:i386: p 1.58 stable 900 p 1.65 unstable 10
Bug#750586: Problem continues to exist
also sprach Cyril Brulebois k...@debian.org [2015-02-15 15:50 +0100]: I thought this issue was actually resolved? With the new d-i-n-a version, this now works for me. If you think we can infer “martin is using d-i-n-a” from “Unfortunately, ldlinux.c32 is still being sought and not found. Any news?” then I can assure you that we cannot… Yeah, sorry about that. I now took another look and I think that when I wrote in to the bug, I actually didn't have much of a clue about the issue at hand and the problem wasn't applicable to me in the first place. -- .''`. martin f. krafft madduck@d.o @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems whatever you do will be insignificant, but it is very important that you do it. -- mahatma gandhi digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#749799: php-horde-core: problem with horde's smartphone view because of outdated libjs-jquery-mobile
Package: php-horde-core Version: 2.15.0+debian0-1 Followup-For: Bug #749799 unfortunately i can confirm, that this bug still exists with current jquery-mobile. it makes the mobile-view of (e.g.) imp utterly useless, that is: - when i switch to imp, no folders are displayed - this can be worked around by selecting Show all folders manually - when i select a folder, e.g. Inbox, the folder appears to be empty - this can be worked around by clicking on Refresh (which btw gives an inconsistent view) - clicking on a message will open up a virtually empty view, with two collapsed views, which (when opened) are empty. here's a screenshot http://pbrd.co/1MwIzPY - i haven't found a workaround yet to actually display any email. replacing the jquery.mobile directory with the one that actually comes with horde (horde-5.2.3 ships with jquery-mobile 1.3.2), seems to fix the problem. fgmasdr IOhannes -- 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/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages php-horde-core depends on: ii libjs-jquery1.7.2+dfsg-3.2 ii libjs-jquery-mobile 1.2.0+dfsg-2 ii libjs-prototype 1.7.1-3 ii libjs-scriptaculous 1.9.0-2 ii php-horde-alarm 2.2.1-5 ii php-horde-auth 2.1.5-5 ii php-horde-autoloader2.1.0-5 ii php-horde-browser 2.0.7-2 ii php-horde-cache 2.5.0-2 ii php-horde-cli 2.0.5-2 ii php-horde-compress 2.0.8-5 ii php-horde-compress-fast 1.0.3-5 ii php-horde-controller2.0.1-7 ii php-horde-cssminify 1.0.2-1 ii php-horde-data 2.1.0-5 ii php-horde-date 2.0.12-5 ii php-horde-exception 2.0.4-4 ii php-horde-group 2.0.4-4 ii php-horde-hashtable 1.2.0-4 ii php-horde-history 2.3.1-4 ii php-horde-injector 2.0.3-4 ii php-horde-javascriptminify 1.1.0-2 ii php-horde-lock 2.1.1-4 ii php-horde-log 2.1.0-4 ii php-horde-logintasks2.0.3-4 ii php-horde-mime 2.4.5-3 ii php-horde-mime-viewer 2.0.7-2 ii php-horde-notification 2.0.1-6 ii php-horde-pack 1.0.4-2 ii php-horde-perms 2.1.2-4 ii php-horde-prefs 2.7.0-3 ii php-horde-secret2.0.3-4 ii php-horde-serialize 2.0.2-5 ii php-horde-sessionhandler2.2.4-4 ii php-horde-share 2.0.5-4 ii php-horde-support 2.1.1-4 ii php-horde-template 2.0.1-6 ii php-horde-text-filter 2.2.1-5 ii php-horde-token 2.0.5-4 ii php-horde-translation 2.1.0-4 ii php-horde-url 2.2.3-4 ii php-horde-util 2.5.1-5 ii php-horde-view 2.0.4-4 ii php-pear5.6.5+dfsg-1 ii php5-common 5.6.5+dfsg-1 Versions of packages php-horde-core recommends: ii php-horde-activesync 2.19.2-2 ii php-horde-crypt2.5.0-5 ii php-horde-dav 1.1.0-1 ii php-horde-db 2.1.4-3 ii php-horde-editor 2.0.4+debian0-3 ii php-horde-elasticsearch1.0.2-3 ii php-horde-form 2.0.8-2 ii php-horde-http 2.1.1-4 ii php-horde-icalendar2.0.9-4 ii php-horde-image2.1.0-4 ii php-horde-imap-client 2.25.2-1 ii php-horde-kolab-server 2.0.2-5 ii php-horde-kolab-session2.0.1-7 ii php-horde-kolab-storage2.1.1-3 ii php-horde-ldap 2.2.0-4 ii php-horde-mail 2.4.0-4 ii php-horde-mongo1.0.2-2 ii php-horde-nls 2.0.4-2 ii php-horde-oauth2.0.1-5 ii php-horde-queue1.1.1-2 ii php-horde-routes 2.0.2-5 ii php-horde-service-twitter 2.1.1-2 ii php-horde-spellchecker 2.1.1-4 ii php-horde-tree 2.0.2-3 ii php-horde-vfs 2.2.0-4 ii php-net-dns2 1.3.2-2 ii php-text-captcha 0.4.3-1 ii php-text-figlet1.0.2-3 pn php-text-languagedetectnone Versions of packages php-horde-core suggests: pn php-horde-javascriptminify-jsmin none ii php-horde-test2.4.4+debian0-2 -- 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#778446: python-argh: Please provide Python 3 package
I've tagged the 0.26.1-1 version on git and uploaded the package yesterday. However it is still in NEW queue, but judging from the queue size it could take some time to be approved.. Regards, Marco -- - |Marco Nenciarini| Debian/GNU Linux Developer - Plug Member | | mnen...@prato.linux.it | http://www.prato.linux.it/~mnencia | - Key fingerprint = 7C23 B804 3E65 D298 0A21 B6E2 589F 03F0 1BA5 5038 signature.asc Description: OpenPGP digital signature
Bug#778672: linphone: TLS , reading of Trusted CA file : '/etc/ssl/certs' failed because it is a directory
Package: linphone Version: 3.6.1-2.4+b1 Severity: normal Tags: newcomer Dear Maintainer, using of TLS not working in Linphone debug window: error: eXosip: Couldn't read CA list message: eXosip: Trusted CA folder : '/etc/ssl/certs' Linphone want to read etc/ssl/certs as pem file I tested it with mv /etc/ssl/cert /etc/ssl/cert2 cp my.pem /etc/ssl/cert and TLS works ! In source 'coreapi/linphonecore.c' this line has to changed to a defined pem file #ifdef __linux sal_set_root_ca(lc-sal, lp_config_get_string(lc-config,sip,root_ca, /etc/ssl/certs)); there is already a pem file in linephone /usr/share/linphone/rootca.pem so a patch would look like #ifdef __linux sal_set_root_ca(lc-sal, lp_config_get_string(lc-config,sip,root_ca, /usr/share/linphone/rootca.pem)); regards markus -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing-proposed-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.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 linphone depends on: ii libasound21.0.28-1 ii libatk1.0-0 2.14.0-1 ii libavcodec56 6:11.2-1 ii libavutil54 6:11.2-1 ii libc6 2.19-13 ii libcairo2 1.14.0-2.1 ii libexosip2-11 4.1.0-2 ii libfontconfig12.11.0-6.3 ii libfreetype6 2.5.2-2 ii libgdk-pixbuf2.0-02.31.1-2+b1 ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libglew1.10 1.10.0-3 ii libglib2.0-0 2.42.1-1 ii libglu1-mesa [libglu1]9.0.0-2 ii libgtk2.0-0 2.24.25-1 ii liblinphone5 3.6.1-2.4+b1 ii libmediastreamer-base33.6.1-2.4+b1 ii libnotify40.7.6-2 ii libogg0 1.3.2-1 ii libopus0 1.1-2 ii libortp9 3.6.1-2.4+b1 ii libosip2-11 4.1.0-2 ii libpango-1.0-01.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-0 1.36.8-3 ii libpulse0 5.0-13 ii libsoup2.4-1 2.48.0-1 ii libspandsp2 0.0.6-2+b2 ii libspeex1 1.2~rc1.2-1 ii libspeexdsp1 1.2~rc1.2-1 ii libsqlite3-0 3.8.7.1-1 ii libswscale3 6:11.2-1 ii libtheora01.1.1+dfsg.1-6 ii libudev1 215-11 ii libupnp6 1:1.6.19+git20141001-1 ii libv4l-0 1.6.0-2 ii libvpx1 1.3.0-3 ii libx11-6 2:1.6.2-3 ii libxv12:1.0.10-1+b1 ii linphone-nogtk3.6.1-2.4+b1 linphone recommends no packages. Versions of packages linphone suggests: ii yelp 3.14.1-1 -- 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#777264:
I agree that the stability of ftp.tw.debian.org has been less than ideal. I admin servers in multiple countries with sources.lists typically auto-generated using ftp.XX.debian.org for the primary mirror. By far I see the most problems with the Taiwan mirror. Most are transient (1hr) or non-critical such as packages being stale, so go unreported. I checked my records and found 5 bug reports related to the Taiwan mirror over 5 years: 646794 694042 719020 732545 777264 This isn't horrible, but it does demonstrate a pattern of problems with the availability of this mirror. Certainly this current outage of 11 days and counting is the extreme example (and because of the new year's holiday may not receive attention until next week). -- James Lick -- 黎建溥 -- james.l...@jameslick.com -- http://jameslick.com/
Bug#761730: tracker.d.o: please provide links to https://security-tracker.debian.org/tracker/source-package/$PKG
Hi,
On Tue, 16 Sep 2014, Raphael Hertzog wrote:
Let's not continue that bad tradition. If anything it should provide
either YAML or JSON with something structured:
bind9:
squeeze:
open:
- CVE-XXX
- CVE-YYY
open-unimportant:
- ...
resolved:
- ...
wheezy:
...
One thing that comes to my mind is that we probably also want the
associated Debian bug number when there's an associated bug report.
So instead of a plain CVE identifier we probably want a hash:
{ 'id': 'CVE--', 'bug': '12345', 'severity': 'low' }
That way we could also export the severity and easily add more data
in case of future needs.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778694: marco doesn't receive GSettings notifications with GLib = 2.43
Source: marco Version: 1.8.2+dfsg1-4 Severity: important With the latest GLib changes [1], if an app reads some data from GSettings before connecting there, it actually won't receive any notifications from GSettings afterwards. The upstream pull request [2] fixes the issue for Marco, making it connect to GSettings before reading the data. [1] https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619 [2] https://github.com/mate-desktop/marco/pull/175
Bug#776319: CVE-2015-0361
retitle 776319 xen: CVE-2015-0361 CVE-2015-1563 thanks On Mon, Jan 26, 2015 at 08:52:53PM +0100, Moritz Muehlenhoff wrote: Source: xen Severity: important Tags: security Hi, please see http://xenbits.xen.org/xsa/advisory-116.html for details and a patch. Also http://xenbits.xen.org/xsa/advisory-118.html needs to be fixed in jessie. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773223: [debian-mysql] Bug#773223: mariadb-server-10.0: Fails to upgrade to 10.0.15-2
Hello, I can't reproduce it anymore. I think you can close it. Le 18 février 2015 12:22:44 CET, Otto Kekäläinen o...@seravo.fi a écrit : I will close this issue unless the original reporter adds some more information that would enable us to reproduce the bug. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773223 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778683: Error creating partition table on RAID device
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 tags 778683 + moreinfo thanks I can't really follow your very well, but it sounds like you did simply select the wrong device in gparted. If you can reproduce this using just parted showing how would make things clear. If you can only reproduce it in gparted, then more detailed steps of how, as well as a copy of the gparted log file should help track down the problem there. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) iQEcBAEBAgAGBQJU5NaVAAoJENRVrw2cjl5RJT0H/3/mVrSSxGrWUyBrNKWY5ko6 o6YpqfSdLF/xHBRGAvKsCaw7g8Uv/GDrJXaIg3IUU4Ba8b3S+lKsmQ/UbZFARSQH FWWUBsrJmJARjs7T7azxjUDbipVFJZQxxoNKKPqzeNwGhXIGHM8WVmffP1YUOYzK 00Of92sZffPyw2DdTIJaHtJNFMJiVkdf7K7RRkURzHvSoA8uEw2ezQVjaHJmQ1OA 8Bdc759gi+OrjDGRALJrA86ztLNvqFOa9nb5PQ491jfkBSHyrYVziGZ8HIgkEmZ0 drDyEA9pMH8obz+EEDTOw6HbMFS9xghAtcbKKALaQRkbc+wDEJK3ovQh476mabQ= =uEDM -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#731683: network-manager: WWAN broadband connections crashes after some seconds
Package: network-manager Version: 0.9.10.0-6 Followup-For: Bug #731683 I asked in the modemmanager mailing list (see http://lists.freedesktop.org/archives/modemmanager-devel/2015-February/001758.html) and somebody finds the problem and posted a patch for 0.9.10, 1.0.0 and git branch. Now it should work. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages network-manager depends on: ii adduser3.113+nmu3 ii dbus 1.8.16-1 ii init-system-helpers1.22 ii isc-dhcp-client4.3.1-6 ii libc6 2.19-15 ii libdbus-1-31.8.16-1 ii libdbus-glib-1-2 0.102-1 ii libgcrypt201.6.2-4+b1 ii libglib2.0-0 2.42.1-1 ii libgnutls-deb0-28 3.3.8-5 ii libgudev-1.0-0 215-12 ii libmm-glib01.4.0-1 ii libndp01.4-2 ii libnewt0.520.52.17-1+b1 ii libnl-3-2003.2.24-2 ii libnl-genl-3-200 3.2.24-2 ii libnl-route-3-200 3.2.24-2 ii libnm-glib40.9.10.0-6 ii libnm-util20.9.10.0-6 ii libpam-systemd 215-12 ii libpolkit-gobject-1-0 0.105-8 ii libreadline6 6.3-8+b3 ii libsoup2.4-1 2.48.0-1 ii libsystemd0215-12 ii libteamdctl0 1.12-1 ii libuuid1 2.25.2-5 ii lsb-base 4.1+Debian13+nmu1 ii policykit-10.105-8 ii udev 215-12 ii wpasupplicant 2.3-1 Versions of packages network-manager recommends: ii crda 3.13-1 ii dnsmasq-base 2.72-3 ii iptables 1.4.21-2+b1 ii iputils-arping 3:20121221-5+b2 ii ppp2.4.6-3 ii wader-core [modemmanager] 0.5.12-2 Versions of packages network-manager suggests: ii avahi-autoipd 0.6.31-4+b2 pn libteam-utils 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#773250: linux-image-3.18.0-trunk-amd64: USB keyboard not recognized at the time cryptsetup prompt shows up
Update... It seems that the 'xhci-hcd' module was split into 'xhci-pci' and 'xhci-platform' since kernel version 3.18. Adding the 'xhci-pci' module to initramfs fixes the issue for me. It worked for me too... I should have read this thread till the last post... Sorry. -- Emmanuel Fleury A good compromise leaves everyone mad. -- Calvin Hobbes (Bill Waterson) signature.asc Description: OpenPGP digital signature
Bug#775527: live-images: upgrade splash to Jessie theme
No problem, and thanks for taking care of that :) On Tue, 2015-02-17 at 21:45 +0100, juliette Belin wrote: Hi, i'm very busy this month, sorry for the delay! I assume I am correct in thinking that you had no intention for any of the boot screen (grub/syslinux/isolinux) images you have supplied to be used in this way for install/live boot menus, but it might be helpful to the discussion if you could please confirm this correct, i wasn't aware of this usage. Your image looks good, i'll add it to the archive on the lines artwork. Thank you very much for taking the time to create it! Regards, Juliette -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778673: unblock: suricata/2.0.6-2
On Wed, Feb 18, 2015 at 11:54:04 +0100, Arturo Borrero Gonzalez wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package suricata We just uploaded to unstable a new suricata version (2.0.6-2) which would require another unblock to enter jessie. This is the debdiff, which was generated with (unfiltered): % debdiff suricata_2.0.6-1.dsc suricata_2.0.6-2.dsc The libhtp.so symlink should not be installed either, so you shouldn't need any conflicts with libhtp-dev. Cheers, Julien signature.asc Description: Digital signature
Bug#778695: wheezy - jessie: no gdm3 prompt, dependency loops and broken initrd
Package: upgrade-reports Severity: grave This is the third jessie upgrade I perform from jessie. The previous one was documented in #774314. It seems that the dependency loop problems are still there, and there were so many problems with the upgrade that I don't believe it would be right to release jessie as such (hence the grave severity). I know that I certainly can't spend the 6h i did on this workstation on all the workstations in the office. :) I followed the two-stage upgrade procedure from the install manual. My notes are here: https://wiki.koumbit.net/JessieUpgrade During the `dist-upgrade` step (after the `upgrade`), there was a failure i couldn't trace back (because i somehow got out of that ttyrec by mistake). After that, I got the following error trying to run `dist-upgrade` again: root@desktop008:/# apt-get dist-upgrade -y -o Dpkg::Options::='--force-confdef' -o Dpkg::Options::='--force-confold' Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: aptdaemon : Depends: python-aptdaemon (= 0.45-2) but 1.1.1-4 is installed auctex : Depends: emacs24 or emacs-snapshot but it is not installable cheese : Depends: libgnome-desktop-3-2 (= 3.2.0) but it is not installable cups : Depends: cups-core-drivers (= 1.7.5-10) but it is not installed Depends: cups-server-common (= 1.7.5-10) but it is not installed Depends: cups-client (= 1.7.5-10) but 1.5.3-5+deb7u4 is installed Depends: cups-filters (= 1.0.24-3~) but 1.0.18-2.1+deb7u1 is installed Recommends: cups-filters (= 1.0.42) but 1.0.18-2.1+deb7u1 is installed or foomatic-filters (= 4.0) Recommends: cups-filters (= 1.0.36) but 1.0.18-2.1+deb7u1 is installed or ghostscript-cups (= 9.02~) cups-bsd : Depends: cups-client (= 1.7.5-10) but 1.5.3-5+deb7u4 is installed cups-client : Depends: libcups2 (= 1.5.3-5+deb7u4) but 1.7.5-10 is installed dpkg : Breaks: fontconfig ( 2.11.0-6.2) but 2.9.0-7.1 is installed Breaks: man-db ( 2.6.3-6) but 2.6.2-1 is installed eog : Depends: libgnome-desktop-3-2 (= 3.2.0) but it is not installable evolution : Depends: libgnome-desktop-3-2 (= 3.2.0) but it is not installable evolution-plugins : Depends: libgnome-desktop-3-2 (= 3.2.0) but it is not installable foomatic-db-engine : Depends: cups-filters (= 1.0.42) but 1.0.18-2.1+deb7u1 is installed or foomatic-filters (= 4.0) gdm3 : Depends: libaudit0 (= 1.7.13) but it is not installable gir1.2-freedesktop : Depends: gir1.2-glib-2.0 (= 1.32.1-1) but 1.42.0-2.2 is installed gnome-color-manager : Depends: libgnome-desktop-3-2 (= 3.2.0) but it is not installable gnome-contacts : Depends: libgnome-desktop-3-2 (= 3.2.0) but it is not installable gnome-control-center : Depends: libgnome-desktop-3-2 (= 3.2.0) but it is not installable gnome-documents : Depends: libgnome-desktop-3-2 (= 3.2.0) but it is not installable gnome-panel : Depends: libgnome-desktop-3-2 (= 3.2.0) but it is not installable gnome-screensaver : Depends: libgnome-desktop-3-2 (= 3.2.0) but it is not installable gnome-settings-daemon : Depends: libgnome-desktop-3-2 (= 3.4.0) but it is not installable gnome-themes-standard : Depends: libpangocairo-1.0-0 (= 1.14.0) but it is not installed gtk2-engines-pixbuf : Depends: libgtk2.0-0 (= 2.24.10-2) but 2.24.25-1 is installed libc-dev-bin : Depends: libc6 ( 2.14) but 2.19-13 is installed libc6-dev : Depends: libc6 (= 2.13-38+deb7u7) but 2.19-13 is installed libcairo2-dev : Depends: libcairo2 (= 1.12.2-3) but 1.14.0-2.1 is installed libcupscgi1 : Depends: libcups2 (= 1.5.3-5+deb7u4) but 1.7.5-10 is installed libcupsdriver1 : Depends: libcups2 (= 1.5.3-5+deb7u4) but 1.7.5-10 is installed libcupsimage2 : Depends: libcups2 (= 1.5.3-5+deb7u4) but 1.7.5-10 is installed libcupsmime1 : Depends: libcups2 (= 1.5.3-5+deb7u4) but 1.7.5-10 is installed libcupsppdc1 : Depends: libcups2 (= 1.5.3-5+deb7u4) but 1.7.5-10 is installed libevolution : Depends: libgnome-desktop-3-2 (= 3.2.0) but it is not installable libgail-3-0 : Depends: libgtk-3-0 (= 3.4.2-7) but 3.14.5-1 is installed libgail18 : Depends: libgtk2.0-0 (= 2.24.10-2) but 2.24.25-1 is installed libgdk-pixbuf2.0-dev : Depends: libgdk-pixbuf2.0-0 (= 2.26.1-1) but 2.31.1-2+b1 is installed libglib2.0-bin : Depends: libglib2.0-0 (= 2.33.12+really2.32.4-5) but 2.42.1-1 is installed libglib2.0-dev : Depends: libglib2.0-0 (= 2.33.12+really2.32.4-5) but 2.42.1-1 is installed libgtk-3-0 : Depends: libpangocairo-1.0-0 (= 1.36.7) but it is not installed libgtk-3-bin : Depends: libgtk-3-common (= 3.4.2-7) but 3.14.5-1 is installed libgtk-3-dev : Depends: libgtk-3-0 (= 3.4.2-7) but 3.14.5-1 is installed libgtk2.0-0 : Depends: libpangocairo-1.0-0 (= 1.28.3) but it is not installed libgtk2.0-bin :
Bug#778697: libparted2: error on opening with regard to RAID member devices
Package: libparted2 Severity: grave With a 'fake RAID' RAID0 device constructed using motherboard firmware, which has a GPT partitioning table setup using fdisk (gparted failed me - see #778683), opening gparted now results in errors in relation to the RAID member disks. Specifically, I firstly get the following error regarding the first disk in the RAID array: Title: Libparted bug found! Message: Invalid argument during seek for read on /dev/sdb Clicking on 'ignore' then results in this followup message: Title: Libparted bug found! Message: The backup GPT table is corrupt, but the primary appears OK, so that will be used. fdisk seems perfectly happy with the setup. Presumably libparted is not processing the member disks as actually being part of an array. Marking as grave on the off chance of data loss with libparted not processing things properly here, and the possibility of users fiddling with things in gparted in relation to it (e.g. trying to correct the 'unrecognised partition table' status of member disks, wiping out their array. Should array members even be listed in gparted? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778683: Info received (Bug#778683: Error creating partition table on RAID device)
Investigating with fdisk I discovered that after this the second disk in the array was reported to have the following issue: 'MBR/GPT mismatches'. I managed to get things fixed and the partition table created successfully with fdisk instead. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778698: unable to build with kernel 3.19
Package: nvidia-kernel-source
Version: 343.36-1
Severity: important
Tags: upstream patch
Patch attached, tested, please apply.
-- Package-specific info:
uname -a:
Linux zombie 3.19.0+ #10 SMP PREEMPT Wed Feb 11 20:39:23 CET 2015 x86_64
GNU/Linux
/proc/version:
Linux version 3.19.0+ (root@zombie) (gcc version 4.9.2 (Debian 4.9.2-10) ) #10
SMP PREEMPT Wed Feb 11 20:39:23 CET 2015
/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 343.36 Mon Dec 1 16:18:58 PST
2014
GCC version: gcc version 4.9.2 (Debian 4.9.2-10)
--- nvidia-graphics-drivers-343.36/debian/module/debian/patches/f_path.dentry.patch 1970-01-01 01:00:00.0 +0100
+++ nvidia-graphics-drivers-343.36.patched/debian/module/debian/patches/f_path.dentry.patch 2015-02-18 18:45:32.435160595 +0100
@@ -0,0 +1,33 @@
+diff -urd kernel-source-tree.orig/nv-frontend.c kernel-source-tree/nv-frontend.c
+--- a/nv-frontend.c 2014-12-02 00:26:56.0 +0100
b/nv-frontend.c 2015-02-18 18:37:00.135142310 +0100
+@@ -327,7 +327,7 @@
+ unsigned long i_arg
+ )
+ {
+-return nvidia_frontend_ioctl(file-f_dentry-d_inode, file, cmd, i_arg);
++return nvidia_frontend_ioctl(file-f_path.dentry-d_inode, file, cmd, i_arg);
+ }
+
+ long nvidia_frontend_compat_ioctl(
+@@ -336,7 +336,7 @@
+ unsigned long i_arg
+ )
+ {
+-return nvidia_frontend_ioctl(file-f_dentry-d_inode, file, cmd, i_arg);
++return nvidia_frontend_ioctl(file-f_path.dentry-d_inode, file, cmd, i_arg);
+ }
+
+ int nvidia_frontend_mmap(
+diff -urd kernel-source-tree.orig/nv.c kernel-source-tree/nv.c
+--- a/nv.c 2014-12-02 00:26:56.0 +0100
b/nv.c 2015-02-18 18:36:32.471141323 +0100
+@@ -1824,7 +1824,7 @@
+ unsigned long i_arg
+ )
+ {
+-return nvidia_ioctl(file-f_dentry-d_inode, file, cmd, i_arg);
++return nvidia_ioctl(file-f_path.dentry-d_inode, file, cmd, i_arg);
+ }
+
+ /*
--- nvidia-graphics-drivers-343.36/debian/module/debian/patches/series 2014-10-14 11:31:09.0 +0200
+++ nvidia-graphics-drivers-343.36.patched/debian/module/debian/patches/series 2015-02-18 18:44:37.023158617 +0100
@@ -3,3 +3,4 @@
use-nv-kernel-ARCH.o_shipped.patch
conditionally-include-linux_version.h.patch
uvm-symvers.patch
+f_path.dentry.patch
Bug#612371: memtest86+: added two more variables for enabling/disabling serial and/or multiboot menuentries
Package: memtest86+
Version: 4.20-1.1
Followup-For: Bug #612371
Dear Maintainer,
I added two more variables in /etc/default/grub for being able to
enabling/disabling the serial and the multiboot menuentry.
Here is what I did:
1.) In /etc/default/grub I added these lines:
GRUB_MEMTEST_ENABLE_SERIAL=false
GRUB_MEMTEST_ENABLE_MULTIBOOT=false
2.) In /usr/sbin/grub-mkconfig I added these variables to the list of exportet
variables:
at line 280:
GRUB_MEMTEST_SERIAL_PARAMS \
GRUB_MEMTEST_ENABLE_SERIAL \
GRUB_MEMTEST_ENABLE_MULTIBOOT
3.) I modified /etc/grub.d/20_memtest86+:
Two times:
if [ ${GRUB_MEMTEST_ENABLE_SERIAL} = true ]; then
...
fi
One time:
if [ ${GRUB_MEMTEST_ENABLE_MULTIBOOT} = true ]; then
...
fi
I'm not sure if it's the best solution, but at least it works...
See my attached patch-files.
-- System Information:
Debian Release: 7.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages memtest86+ depends on:
ii debconf [debconf-2.0] 1.5.49
memtest86+ recommends no packages.
Versions of packages memtest86+ suggests:
ii grub-pc 1.99-27+deb7u2
pn hwtools none
pn kernel-patch-badram none
pn memtest86none
pn memtesternone
pn mtools none
-- Configuration Files:
/etc/grub.d/20_memtest86+ changed [not included]
-- debconf information excluded
--- /tmp/grub-mkconfig 2011-09-19 05:12:37.0 +0200
+++ /usr/sbin/grub-mkconfig 2015-02-18 16:56:41.151090002 +0100
@@ -276,7 +276,10 @@
GRUB_DISABLE_OS_PROBER \
GRUB_INIT_TUNE \
GRUB_SAVEDEFAULT \
- GRUB_BADRAM
+ GRUB_BADRAM \
+ GRUB_MEMTEST_SERIAL_PARAMS \
+ GRUB_MEMTEST_ENABLE_SERIAL \
+ GRUB_MEMTEST_ENABLE_MULTIBOOT
if test x${grub_cfg} != x; then
rm -f ${grub_cfg}.new
--- /tmp/20_memtest86+ 2010-10-19 18:32:29.0 +0200
+++ /etc/grub.d/20_memtest86+ 2015-02-18 17:47:52.385794462 +0100
@@ -30,16 +30,21 @@
cat EOF
$LX $MEMTESTPATH
}
-menuentry Memory test (memtest86+, serial console 115200) {
+EOF
+ if [ ${GRUB_MEMTEST_ENABLE_SERIAL} = true ]; then
+ cat EOF
+menuentry Memory test (memtest86+, serial console) {
EOF
printf '%s\n' ${prepare_boot_cache}
cat EOF
- $LX $MEMTESTPATH console=ttyS0,115200n8
+ $LX $MEMTESTPATH console=${GRUB_MEMTEST_SERIAL_PARAMS}
}
EOF
+ fi
fi
-if test -e /boot/memtest86+_multiboot.bin ; then
+if [ ${GRUB_MEMTEST_ENABLE_MULTIBOOT} = true ]; then
+ if test -e /boot/memtest86+_multiboot.bin ; then
MEMTESTPATH=$( make_system_path_relative_to_its_root /boot/memtest86+_multiboot.bin )
echo Found memtest86+ multiboot image: $MEMTESTPATH 2
cat EOF
@@ -49,11 +54,16 @@
cat EOF
multiboot $MEMTESTPATH
}
-menuentry Memory test (memtest86+, serial console 115200, experimental multiboot) {
+EOF
+ if [ ${GRUB_MEMTEST_ENABLE_SERIAL} = true ]; then
+ cat EOF
+menuentry Memory test (memtest86+, experimental multiboot, serial console) {
EOF
printf '%s\n' ${prepare_boot_cache}
cat EOF
- multiboot $MEMTESTPATH console=ttyS0,115200n8
+ multiboot $MEMTESTPATH console=${GRUB_MEMTEST_SERIAL_PARAMS}
}
EOF
+ fi
+ fi
fi
Bug#775892: unblock (pre-approval): python-django/1.7.3-1
Le 2015-02-18 09:38, Raphael Hertzog a écrit : And if you don't agree, then I would be interested to know what could bring you the required confidence so that we can gain that status (maybe adding autopkgtests to reverse dependencies and running those tests, or stuff like that). The list of packages that we started with are the ones that give more trouble to the security team. Maybe the list should be expanded, I don't know. Most probably. What we would like to have is a general discussion (not now please... but after jessie release) to put some criteria to help to distinguish packages that need a special treatement and others that don't. For now, the criteria has been security team has trouble with X but I don't find this criteria good enough. The autopkgtests might be part of the answer, but not the only one I hope. Regards, -- Mehdi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758110: base: suspend to ram key (Fn+F4) does not work anymore
Hi Debian, I don't have the problem anymore. Here is what I did to remove it: - apt-get install sysvinit-core sysvinit sysvinit-utils - reboot - apt-get remove --purge --auto-remove systemd - apt-get install acpid - apt-get install acpi-support I don't remember if I removed the acpi thing before or after systemd popped up (unwillingly). I guess it's after (why would I have done it before? why did I include that information in my previous email?). Anyway, now fn-f4 suspends the computer. Putting the screen down does not suspend it anymore (did I ask you to suspend? No I just asked you to turn the screen off, so just do that thank you). Everything is back in order. Systemd is at its place, with all due respect to people's hard work (but you know, it's also good to realize what you're doing just sucksTM and give up and do something saner). Regards, Cédric. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778673: unblock: suricata/2.0.6-2
On 18 February 2015 at 18:01, Julien Cristau jcris...@debian.org wrote: On Wed, Feb 18, 2015 at 11:54:04 +0100, Arturo Borrero Gonzalez wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package suricata We just uploaded to unstable a new suricata version (2.0.6-2) which would require another unblock to enter jessie. This is the debdiff, which was generated with (unfiltered): % debdiff suricata_2.0.6-1.dsc suricata_2.0.6-2.dsc The libhtp.so symlink should not be installed either, so you shouldn't need any conflicts with libhtp-dev. Is OK to upload a -3 with no symlink and request again for unblock? regards -- Arturo Borrero González -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778698: unable to build with kernel 3.19
On 2015-02-18 18:58, Eduard Bloch wrote: Patch attached, tested, please apply. Thanks, but NACK on the patch in this form - this needs to be properly #if'ed on the kernel version s.t. it builds on all kernel versions. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773250: linux-image-3.18.0-trunk-amd64: USB keyboard not recognized at the time cryptsetup prompt shows up
Same problem as previously mentioned. I have an Apple MacBook with luks, my keyboard is recognized (I can navigate in the GRUB option menu), but typing the passphrase to access the disk and boot on my system has no effect. Moreover, I am compiling my own kernels for my distribution and the problem occurred at 3.18.x and higher (I just tried with 3.19.0 right now, the problem is still here). So, the problem comes from a modification of the kernel settings and not because of some tweaks from specific to linux-image-3.18.0-trunk-amd64. The new kernel series may need to tick a new box in the menuconfig phase, but I can tell which one. I am still looking for some clues that could lead to a resolution of the problem (if a least I could see where it fails it would be a starting point). So, any hint is welcome ! Regards -- Emmanuel Fleury Experience is one thing you can't get for nothing. -- Oscar Wilde signature.asc Description: OpenPGP digital signature
Bug#778651: reminiscence segfault and exit on cinematic
Control: submitter -1 Fargier Nicolas bioprodu...@yahoo.fr -=| Fargier Nicolas, 18.02.2015 12:11:58 + |=- Hi,i am the submitter of the bug, i made a mistake with my mail it is bioprodu...@yahoo.fr , don't know if i could change this with reportbug ? I hope the above control line fixes that. I will try with other data files tonight just to be sure that my data files are ok. Can you compare the md5 checksums and the sizes with those in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778651#8 ? I used the french version of the pc dos game and amiga mod files for music. To confirm you : the crash did not happen during the charging but it happen when you use the battery to power up the bridge.i have try it 3 times and it always crash at the same moment. Alright, I'll see if I can go pass that point. -- dam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778699: Vidalia should not be part of Jessie
Package: vidalia Version: 0.2.21-5 Severity: serious Vidalia has been dead upstream for years, and has a crapload of bugs nobody will ever fix. The Tor Project is currently actively removing any reference to Vidalia from their website. We're not even sure if it's in good shape in Jessie, e.g. about what happens exactly on initial installation -- not sure it is configured properly to use the control socket as it should. Some people are happier with 0.3.x, but that one is itself alpha-quality software with another crapload of bugs that nobody will ever fix. Even Tails is going to ditch Vidalia soonish, and Tails is shipping its patched version anyway. So, it is the maintainers' opinion (agreed by Holger on the pkg-anonymity-tools@ mailing-list, and by Lunar on IRC) that Vidalia should not be part of the Jessie release. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777695: ITA: tiff -- TIFF manipulation and conversion documentation
On Wed, Feb 11, 2015 at 05:05:59PM +0100, Ondrej Sury wrote: Control: retitle -1 ITA: tiff -- TIFF manipulation and conversion documentation Control: owner -1 ! Hi Jay, as I happen to maintain now default libjpeg library, it seems only logical I will take over this as well. Do you need a help with the two RC bugs that are lingering in BTS right now? It would be great if you could upload fixed packages! Last time I checked not all of them were fixed upstream, please refer to the links specified in the Debian Security Tracker for details: https://security-tracker.debian.org/tracker/CVE-2015-1547 https://security-tracker.debian.org/tracker/CVE-2014-9655 https://security-tracker.debian.org/tracker/CVE-2014-8130 https://security-tracker.debian.org/tracker/CVE-2014-8129 https://security-tracker.debian.org/tracker/CVE-2014-8128 https://security-tracker.debian.org/tracker/CVE-2014-8127 Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778700: sysv-generator creates unnecessary/wrong symlinks
Package: systemd Version: 219-1 Severity: normal With current 219-1, I get the following log messages: Feb 18 19:22:27 pluto systemd-sysv-generator[13773]: Overwriting existing symlink /run/systemd/generator.late/radvd.service with real service Feb 18 19:22:27 pluto systemd-sysv-generator[13773]: Overwriting existing symlink /run/systemd/generator.late/saned.service with real service Feb 18 19:22:27 pluto systemd-sysv-generator[13773]: Overwriting existing symlink /run/systemd/generator.late/nfs-common.service with real service Feb 18 19:22:27 pluto systemd-sysv-generator[13773]: Overwriting existing symlink /run/systemd/generator.late/gogoc.service with real service Feb 18 19:22:27 pluto systemd-sysv-generator[13773]: Overwriting existing symlink /run/systemd/generator.late/ebtables.service with real service Feb 18 19:22:27 pluto systemd-sysv-generator[13773]: Overwriting existing symlink /run/systemd/generator.late/nfs-kernel-server.service with real service Feb 18 19:22:27 pluto systemd-sysv-generator[13773]: Overwriting existing symlink /run/systemd/generator.late/mysql.service with real service Feb 18 19:22:27 pluto systemd-sysv-generator[13773]: Overwriting existing symlink /run/systemd/generator.late/virtualbox.service with real service ... The generator seems to have created a symlink for every real sysv init script. This didn't happen with 215-12 and looks like a regression. -- Package-specific info: -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 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 systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-58 ii libacl1 2.2.52-2 ii libapparmor12.9.0-3+exp1 ii libaudit1 1:2.4-1+b1 ii libblkid1 2.25.2-5 ii libc6 2.19-15 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.2-4+b1 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b3 ii libmount1 2.25.2-5 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 219-1 ii mount 2.25.2-5 ii sysv-rc 2.88dsf-58 ii udev219-3~local0 ii util-linux 2.25.2-5 Versions of packages systemd recommends: ii dbus1.8.16-1 ii libpam-systemd 219-1 Versions of packages systemd suggests: ii systemd-ui 3-2 -- Configuration Files: /etc/systemd/journal-upload.conf fbc67bdd554f87d2f189c1a5fbdcfb27 [Errno 2] Datei oder Verzeichnis nicht gefunden: u'/etc/systemd/journal-upload.conf fbc67bdd554f87d2f189c1a5fbdcfb27' /etc/systemd/journald.conf changed [not included] -- 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#778532: apt-cacher-ng fails with Acquire::http to http.debian.net
* Eduard Bloch: Re: Bug#778532: apt-cacher-ng fails with Acquire::http to http.debian.net (Mon, 16 Feb 2015 19:02:50 +0100): tags 778532 +moreinfo thanks Hallo, * Mathias Behrle [Mon, Feb 16 2015, 12:45:40PM]: Package: apt-cacher-ng Version: 0.8.0-3 Severity: normal Ign http://http.debian.net jessie-updates Release Err http://http.debian.net jessie/main amd64 Packages 404 Not Found [IP: 192.168.99.13 ] Err http://http.debian.net jessie-updates/main amd64 Packages Please send me the apt-cacher-ng logs and configuration files from your server. Here we go, all other configuration/log files are untouched/empty. -- Mathias Behrle PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6 1424285255|I|468|192.168.99.14|debrep/dists/jessie/InRelease 1424285255|O|210|192.168.99.14|debrep/dists/jessie/InRelease 1424285255|I|475|192.168.99.14|debrep/dists/jessie-updates/InRelease 1424285255|O|218|192.168.99.14|debrep/dists/jessie-updates/InRelease 1424285255|I|399|192.168.99.14|security.debian.org/dists/jessie/updates/InRelease 1424285255|O|84369|192.168.99.14|security.debian.org/dists/jessie/updates/InRelease 1424285255|I|469|192.168.99.14|debrep/dists/jessie/Release.gpg 1424285255|O|212|192.168.99.14|debrep/dists/jessie/Release.gpg 1424285256|I|477|192.168.99.14|debrep/dists/jessie-updates/Release.gpg 1424285256|O|220|192.168.99.14|debrep/dists/jessie-updates/Release.gpg 1424285256|I|465|192.168.99.14|debrep/dists/jessie/Release 1424285256|O|208|192.168.99.14|debrep/dists/jessie/Release 1424285256|I|473|192.168.99.14|debrep/dists/jessie-updates/Release 1424285256|O|216|192.168.99.14|debrep/dists/jessie-updates/Release 1424285256|I|487|192.168.99.14|debrep/dists/jessie/main/binary-amd64/Packages.gz 1424285256|O|230|192.168.99.14|debrep/dists/jessie/main/binary-amd64/Packages.gz 1424285256|I|495|192.168.99.14|debrep/dists/jessie-updates/main/binary-amd64/Packages.gz 1424285256|O|238|192.168.99.14|debrep/dists/jessie-updates/main/binary-amd64/Packages.gz 1424285257|I|488|192.168.99.14|debrep/dists/jessie/main/binary-amd64/Packages.bz2 1424285257|O|231|192.168.99.14|debrep/dists/jessie/main/binary-amd64/Packages.bz2 1424285257|I|496|192.168.99.14|debrep/dists/jessie-updates/main/binary-amd64/Packages.bz2 1424285257|O|239|192.168.99.14|debrep/dists/jessie-updates/main/binary-amd64/Packages.bz2 1424285257|I|487|192.168.99.14|debrep/dists/jessie/main/binary-amd64/Packages.xz 1424285257|O|230|192.168.99.14|debrep/dists/jessie/main/binary-amd64/Packages.xz 1424285257|I|495|192.168.99.14|debrep/dists/jessie-updates/main/binary-amd64/Packages.xz 1424285257|O|238|192.168.99.14|debrep/dists/jessie-updates/main/binary-amd64/Packages.xz 1424285257|I|489|192.168.99.14|debrep/dists/jessie/main/binary-amd64/Packages.lzma 1424285257|O|232|192.168.99.14|debrep/dists/jessie/main/binary-amd64/Packages.lzma 1424285258|I|497|192.168.99.14|debrep/dists/jessie-updates/main/binary-amd64/Packages.lzma 1424285258|O|240|192.168.99.14|debrep/dists/jessie-updates/main/binary-amd64/Packages.lzma 1424285258|I|484|192.168.99.14|debrep/dists/jessie/main/binary-amd64/Packages 1424285258|O|227|192.168.99.14|debrep/dists/jessie/main/binary-amd64/Packages 1424285258|I|394|192.168.99.14|security.debian.org/dists/jessie/updates/main/binary-amd64/Packages.gz 1424285258|O|329|192.168.99.14|security.debian.org/dists/jessie/updates/main/binary-amd64/Packages.gz 1424285258|I|492|192.168.99.14|debrep/dists/jessie-updates/main/binary-amd64/Packages 1424285258|O|235|192.168.99.14|debrep/dists/jessie-updates/main/binary-amd64/Packages acng.conf Description: Binary data pgp3DW9bXoXKP.pgp Description: Digitale Signatur von OpenPGP
Bug#778647: closed by Benjamin Kaduk ka...@mit.edu (Bug#778647: fixed in krb5 1.12.1+dfsg-18)
Hi Benjamin, On Wed, Feb 18, 2015 at 06:24:10PM +, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the src:krb5 package: #778647: krb5: CVE-2014-5355 It has been closed by Benjamin Kaduk ka...@mit.edu. [...] krb5 (1.12.1+dfsg-18) unstable; urgency=high . * Import upstream patch for CVE-2014-5355, Closes: #778647 Thank you! Can you also ask for an unblock of it to the Release Team, so that this fix can go as well into jessie? Regards, Salvatore signature.asc Description: Digital signature
Bug#762723: pastebinit: [INTL:de] updated German po file translation
Hello Rolf, On Wed, Feb 18, 2015 at 10:22:33AM +0800, Rolf Leggewie wrote: On 18.02.2015 02:44, Helge Kreutzmann wrote: I do not intend to introduce a delta for this in Debian. In this case it would be great if you could pull the (latest) de.po from upstream / launchpad Helge, in principle I agree, but as you can see above I already said I will not introduce a delta to upstream only for this. Well, of course it's your choice, but given that we serve users I usually integrate l10n updates in my packages - they are low risk and typically high gain patches, especially before a freeze. But I suppose we agree to disagree, so let's keep this at that. (Just as a side note: since missing / incomplete translations are listed on Debian web pages, other languages might send in patches as well). Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
Bug#778671: Debian.mirror.evertje.net is unreachable
Domain is no longer valid. Email bounced: -- This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: n...@evertjenetworks.nl The mail server could not deliver mail to n...@evertjenetworks.nl. The account or domain may not exist, they may be blacklisted, or missing the proper dns entries. -- This is a copy of the message, including all the headers. -- On 02/18/2015 10:38 AM, Donald Norwood wrote: Hello, A bug has been opened regarding a non-responsive state for your mirror. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778671 Could you please take a look into this matter? Best regards, Donald Norwood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778705: description is a mess
Package: autoradio Severity: normal Hi, the package description is a big mess. Most of the sentences are missing words, or simply don't make sense. After reading through it several times, I still don't know what the package does. Please rewrite it from scratch. Christoph -- c...@df7cb.de | http://www.df7cb.de/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767320:
Spoke too soon. sshd did not start this morning. From syslog, the first mention of sshd Feb 19 08:32:56 ithilien kernel: [ 15.709442] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). Feb 19 08:32:56 ithilien kernel: [ 16.917767] vboxdrv: Found 8 processor cores. Feb 19 08:32:56 ithilien kernel: [ 16.918072] vboxdrv: fAsync=0 offMin=0x26a offMax=0x1cb4 Feb 19 08:32:56 ithilien kernel: [ 16.918161] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. Feb 19 08:32:56 ithilien kernel: [ 16.918163] vboxdrv: Successfully loaded version 4.3.18_Debian (interface 0x001a0008). Feb 19 08:32:56 ithilien kernel: [ 17.431707] vboxpci: IOMMU not found (not registered) Feb 19 08:32:56 ithilien systemd[1]: ssh.service: main process exited, code=exited, status=255/n/a Feb 19 08:32:56 ithilien systemd[1]: Unit ssh.service entered failed state. Feb 19 08:32:56 ithilien polkitd[890]: started daemon version 0.105 using authority implementation `local' version `0.105' V -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778644: qtdeclarative-opensource-src: port to m68k
Lisandro Damián Nicanor Pérez Meyer dixit: m68k is not a release arch so the severity should be at most normal. No: for non-release archs, “important” is the cap, and FTBFS are RC if the package built before (means important due to the cap) and important if it did not build before. The patch won't work because on the next upload we will be using the system's double-conversion lib. Just check that the lib builds on m68k and problem fixed. I’ll have a look. It was previously marked Not-For-Us due to, I assume, this exact problem, but it appears having been fixed upstream. By the way, don't waste your time with symbols patches. We get symbols from build logs, and m68k is already present in debian-ports, so they will be used on the next upload. This is wrong for several reasons, mostly that the symbols list is wrong, so the next (regular) upload would fail, and only the second-to-next upload would succeed. Plus, we actually need the lib *right now*, to be able to build things such as qt5webkit, so I need to prepare the symbols file patches *anyway* because I have to upload the package to dpo “unreleased”. bye, //mirabilos -- This space for rent. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778701: Wrong disk usage displayed
Package: gnome-system-monitor Version: 3.14.1-1 Gnome system monitor is reporting inaccurate disk usage information. Example (1TB HDD): total: 984.4GB available: 46.7 GB used: 887.7 GB 95% full 887.7 + 46.7 = 934.4, not 984.4 The used amount is correct, as is the total (I believe), but the amount available is significantly off and so thus is the percentage. gnome-disk-utility however reports the correct usage: Size: 1.0 TB - 97 GB free )90.3% full). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699849: Bug#778644: qtdeclarative-opensource-src: port to m68k
Lisandro Damián Nicanor Pérez Meyer dixit: The patch won't work because on the next upload we will be using the system's double-conversion lib. Just check that the lib builds on m68k and problem fixed. Turns out it does not, but it just needs either the patch or a newer upstream version *plus* manual notification of the m68k porters (just prod me) to unblock the newer pak‐ kage in wanna-build. This is #699849 already – Cc’ing that bug since its main‐ tainers should know we have a fix and upstream also fixed it. Note that this does not prevent you from applying the patch to any further uploads that d̲o̲ include the code un‐ der 3rdparty/. bye, //mirabilos -- diogenese Beware of ritual lest you forget the meaning behind it. igli yeah but it means if you really care about something, don't ritualise it, or you will lose it. don't fetishise it, don't obsess. or you'll forget why you love it in the first place. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775506: unblock: tbb/4.2~20140122-4
On Wed, Feb 18, 2015 at 10:35:38AM +0800, Steven Capper steven.cap...@gmail.com wrote: Hi, arm64 should be building in -5, so shouldn't the arm64 reverse dependancies be unaffected? Under mips, mipsel, and s390x tbb fails to build unit tests due to missing/incorrect gcc atomics. I have very little confidence in the functional correctness of the reverse dependencies, so I would be inclined to remove them to be safe. Ok. Thanks for the confirmation. I've followed-up on Bug#775263 and asked for the removal of old binaries and reverse dependencies. Once that done, we will be able to unblock tbb. Regards, -- Mehdi Dogguy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775263: RM: tbb [mips mipsel] -- ANAIS; 768040
Hi, On Fri, Jan 16, 2015 at 01:45:45PM +, James Cowgill james...@cowgill.org.uk wrote: On Tue, 13 Jan 2015 11:43:45 +0100 Mathieu Malaterre ma...@debian.org wrote: Package: ftp.debian.org Severity: normal This is a follow up to: 768040 libtbb2 should not be available on s390x, mips and mipsel, please remove them: https://packages.debian.org/jessie/libtbb2 The problem is, if tbb ever gets rebuilt in jessie (eg security issue), then it will get reintroduced into mips/s390x. Regardless you probably want to talk to the release team about this since it concerns testing rather than unstable. They talked to us now and we are ready to accept -5 in Jessie (-5 restricts the architectures list). Can you please process this request? We'd like to get tbb decrufted and get rid of reverse-dependencies on mips, mipsel and s390x. FWIW, dak reports the following binary packages: # Broken Depends: deal.ii: libdeal.ii-8.1.0 [mipsel] libdeal.ii-dev [mipsel] flexbar: flexbar [mips mipsel] mia: libmia-2.2-0 [mips mipsel] libmia-2.2-dev [mips mipsel] mia-tools [mips mipsel] Regards, -- Mehdi Dogguy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777553: pu: package libfcgi/2.4.0-8
Control: tags -1 + confirmed On Mon, 2015-02-09 at 19:53 -0800, Joe Damato wrote: On Mon, Feb 9, 2015 at 1:16 PM, Salvatore Bonaccorso car...@debian.org wrote: Joe, if you get an ack from the release team on your upload for libfcgi I can happily sponsor the upload itself. How do I go about doing that? Is there a separate email list I need to ping? No, just be patient until we replied. :-) Please feel free to go ahead with the upload. I don't have a GPG key that is connected to Debian in any way. I can create a key and upload it to the MIT pgp server. Is that useful at all for the upload of my changes file? Not sure if signing with my key will help or just complicate things further. From what I read, I was under the impression that changes without signatures from GPG keys in the web of trust are not processed in the upload queue. That's correct. You'd need someone with a known key to sponsor your upload. According to his earlier mail, Salvatore is happy to do that, so you shouldn't have to do anything further. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778704: unblock: libgtk2-perl/1.2492-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package libgtk2-perl The only change it contains is a security fix cherry-picked from upstream, and the corresponding test case. I'm in the process of convincing them to ask a CVE, and of preparing a security upload for Wheezy. unblock libgtk2-perl/1.2492-4 Thanks! diff -Nru libgtk2-perl-1.2492/debian/changelog libgtk2-perl-1.2492/debian/changelog --- libgtk2-perl-1.2492/debian/changelog 2014-08-29 23:46:41.0 +0200 +++ libgtk2-perl-1.2492/debian/changelog 2015-02-18 19:53:25.0 +0100 @@ -1,3 +1,10 @@ +libgtk2-perl (2:1.2492-4) unstable; urgency=high + + * Fix-incorrect-memory-management-in-Gtk2-Gdk-Display-list_devices.patch: +new patch, cherry-picked from upstream, that fixes a security issue. + + -- intrigeri intrig...@debian.org Wed, 18 Feb 2015 19:45:09 +0100 + libgtk2-perl (2:1.2492-3) unstable; urgency=medium [ Salvatore Bonaccorso ] diff -Nru libgtk2-perl-1.2492/debian/patches/Fix-incorrect-memory-management-in-Gtk2-Gdk-Display-list_devices.patch libgtk2-perl-1.2492/debian/patches/Fix-incorrect-memory-management-in-Gtk2-Gdk-Display-list_devices.patch --- libgtk2-perl-1.2492/debian/patches/Fix-incorrect-memory-management-in-Gtk2-Gdk-Display-list_devices.patch 1970-01-01 01:00:00.0 +0100 +++ libgtk2-perl-1.2492/debian/patches/Fix-incorrect-memory-management-in-Gtk2-Gdk-Display-list_devices.patch 2015-02-18 19:53:25.0 +0100 @@ -0,0 +1,47 @@ +From: Torsten Schönfeld kaffeeti...@gmx.de +Date: Sat, 17 Jan 2015 14:59:24 +0100 +Origin: https://git.gnome.org/browse/perl-Gtk2/commit/?id=4856da628ce37099b27b66a88141dc6daad693b0 +Applied-Upstream: 1.2495 +Subject: Fix incorrect memory management in Gtk2::Gdk::Display::list_devices + +We do not own the returned list. +--- + t/GdkDisplay.t | 4 +++- + xs/GdkDisplay.xs | 2 -- + 2 files changed, 3 insertions(+), 3 deletions(-) + +diff --git a/t/GdkDisplay.t b/t/GdkDisplay.t +index d290446..f4aef59 100644 +--- a/t/GdkDisplay.t b/t/GdkDisplay.t +@@ -1,7 +1,7 @@ + #!/usr/bin/perl -w + use strict; + use Gtk2::TestHelper +- tests = 26, ++ tests = 27, + at_least_version = [2, 2, 0, GdkDisplay is new in 2.2]; + + # $Id$ +@@ -32,6 +32,8 @@ ok(!$display - pointer_is_grabbed()); + # $display - beep(); + $display - sync(); + ++# Do this twice to ensure we did not damage the list. ++isa_ok(($display - list_devices())[0], Gtk2::Gdk::Device); + isa_ok(($display - list_devices())[0], Gtk2::Gdk::Device); + + $display - put_event(Gtk2::Gdk::Event - new(button-press)); +diff --git a/xs/GdkDisplay.xs b/xs/GdkDisplay.xs +index f558f1d..a019eee 100644 +--- a/xs/GdkDisplay.xs b/xs/GdkDisplay.xs +@@ -69,8 +69,6 @@ gdk_display_list_devices (display) + devices = gdk_display_list_devices (display); + for (i = devices ; i != NULL ; i = i-next) + XPUSHs (sv_2mortal (newSVGdkDevice (i-data))); +- g_list_free (devices); +- + + GdkEvent* gdk_display_get_event (GdkDisplay *display) + diff -Nru libgtk2-perl-1.2492/debian/patches/series libgtk2-perl-1.2492/debian/patches/series --- libgtk2-perl-1.2492/debian/patches/series 2014-08-29 23:46:41.0 +0200 +++ libgtk2-perl-1.2492/debian/patches/series 2015-02-18 19:53:25.0 +0100 @@ -1,3 +1,4 @@ Make_t_GtkCellRenderer.t_more_robust.patch 30-disable_libgtk_version_check.patch fix-typo.patch +Fix-incorrect-memory-management-in-Gtk2-Gdk-Display-list_devices.patch
Bug#778707: differing dependencies between builds
Source: pyliblo Version: 0.9.2-1 User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness Hi! While working on Debian's “reproducible builds” effort [1], we have noticed that pyliblo-utils had different dependencies in two different builds [2]. In the first build it had: Depends: python-liblo, python, python:any (= 2.5~) While on the second build: Depends: python-liblo, python3, python:any (= 2.5~) (python3 instead of python) The included scripts also had different shebangs, #!/usr/bin/python vs. #!/usr/bin/python3. Regards, Reiner [1]: https://wiki.debian.org/ReproducibleBuilds [2]: https://reproducible.debian.net/pyliblo signature.asc Description: OpenPGP digital signature
Bug#778706: flooding log with Not implemented reached in virtual void extensions::DisplayInfoProviderAura::UpdateDisplayUnitInfoForPlatform
Package: chromium Version: 40.0.2214.111-1 Severity: important Tags: upstream I have initially used jessie's version and observed the flood of such messages (cited below). Upstream is aware of it and I believe had it fixed recentish: https://code.google.com/p/chromium/issues/detail?id=442326 by making warning appear once. Since the logs flood is not a healthy sign for any stable system, I have marked it as important and hope patch could be taken for jessie's version of chromium Feb 18 14:22:42 hopa chromium.desktop[6301]: [6301:6301:0218/142242:ERROR:display_info_provider_aura.cc(28)] Not implemented reached in virtual void extensions::DisplayInfoProviderAura::UpdateDisplayUnitInfoForPlatform(const gfx::Display , extensions::core_api::system_display::DisplayUnitInfo *) Feb 18 14:22:43 hopa kernel: AIF:PRIV UDP packet: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:b0:d0:3d:90:99:08:00 SRC=129.170.30.28 DST=129.170.31.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=31450 PROTO=UDP SPT=137 DPT=137 LEN=58 Feb 18 14:22:47 hopa chromium.desktop[6301]: [6301:6301:0218/142247:ERROR:display_info_provider_aura.cc(28)] Not implemented reached in virtual void extensions::DisplayInfoProviderAura::UpdateDisplayUnitInfoForPlatform(const gfx::Display , extensions::core_api::system_display::DisplayUnitInfo *) Feb 18 14:22:51 hopa kernel: AIF:UNPRIV UDP packet: IN=eth0 OUT= MAC= SRC=129.170.31.1 DST=129.170.31.255 LEN=175 TOS=0x00 PREC=0x00 TTL=64 ID=16655 DF PROTO=UDP SPT=17500 DPT=17500 LEN=155 Feb 18 14:22:52 hopa chromium.desktop[6301]: [6301:6301:0218/142252:ERROR:display_info_provider_aura.cc(28)] Not implemented reached in virtual void extensions::DisplayInfoProviderAura::UpdateDisplayUnitInfoForPlatform(const gfx::Display , extensions::core_api::system_display::DisplayUnitInfo *) Feb 18 14:22:55 hopa kernel: AIF:PRIV UDP packet: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:16:cb:93:6d:ec:08:00 SRC=129.170.31.191 DST=129.170.31.255 LEN=200 TOS=0x00 PREC=0x00 TTL=64 ID=55726 PROTO=UDP SPT=631 DPT=631 LEN=180 Feb 18 14:22:57 hopa chromium.desktop[6301]: [6301:6301:0218/142257:ERROR:display_info_provider_aura.cc(28)] Not implemented reached in virtual void extensions::DisplayInfoProviderAura::UpdateDisplayUnitInfoForPlatform(const gfx::Display , extensions::core_api::system_display::DisplayUnitInfo *) Feb 18 14:23:01 hopa kernel: AIF:UNPRIV UDP packet: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:32:9d:35:f6:08:00 SRC=129.170.31.159 DST=129.170.31.255 LEN=162 TOS=0x00 PREC=0x00 TTL=64 ID=20929 PROTO=UDP SPT=17500 DPT=17500 LEN=142 Feb 18 14:23:02 hopa chromium.desktop[6301]: [6301:6301:0218/142302:ERROR:display_info_provider_aura.cc(28)] Not implemented reached in virtual void extensions::DisplayInfoProviderAura::UpdateDisplayUnitInfoForPlatform(const gfx::Display , extensions::core_api::system_display::DisplayUnitInfo *) Feb 18 14:23:02 hopa kernel: AIF:PRIV UDP packet: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:17:a4:99:80:11:08:00 SRC=129.170.31.166 DST=129.170.31.255 LEN=202 TOS=0x00 PREC=0x00 TTL=128 ID=2587 PROTO=UDP SPT=138 DPT=138 LEN=182 Feb 18 14:23:07 hopa chromium.desktop[6301]: [6301:6301:0218/142307:ERROR:display_info_provider_aura.cc(28)] Not implemented reached in virtual void extensions::DisplayInfoProviderAura::UpdateDisplayUnitInfoForPlatform(const gfx::Display , extensions::core_api::system_display::DisplayUnitInfo *) Feb 18 14:23:11 hopa kernel: AIF:UNPRIV UDP packet: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:c4:2c:03:16:24:f1:08:00 SRC=129.170.31.29 DST=129.170.31.255 LEN=44 TOS=0x00 PREC=0x00 TTL=64 ID=52216 PROTO=UDP SPT=59445 DPT=8612 LEN=24 Feb 18 14:23:12 hopa chromium.desktop[6301]: [6301:6301:0218/142312:ERROR:display_info_provider_aura.cc(28)] Not implemented reached in virtual void extensions::DisplayInfoProviderAura::UpdateDisplayUnitInfoForPlatform(const gfx::Display , extensions::core_api::system_display::DisplayUnitInfo *) -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17-1-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 chromium depends on: ii libasound2 1.0.28-1 ii libc62.19-13 ii libcairo21.14.0-2.1 ii libcap2 1:2.24-6 ii libcups2 1.7.5-10 ii libdbus-1-3 1.8.12-3 ii libexpat12.1.0-6+b3 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgnome-keyring03.12.0-1+b1 ii libgtk2.0-0 2.24.25-1 ii libharfbuzz0b0.9.35-2 ii libjpeg62-turbo 1:1.3.1-11 ii libnspr4 2:4.10.7-1 ii libnss3 2:3.17.2-1.1 ii libpango-1.0-0 1.36.8-3 ii
Bug#778697: libparted2: error on opening with regard to RAID member devices
These errors actually disappeared after a reboot :/ ... I guess that means I should have refreshed something, or fdisk should have refreshed something, and thus this can be closed? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778702: sunflow: please make the build reproducible
Source: sunflow Version: 0.07.2.svn396+dfsg-13 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps Hi! While working on Debian's “reproducible builds” effort [1], we have noticed that sunflow doesn't build reproducibly. A PNG icon contains an embedded timestamp. The attached patch fixes this. Once applied, sunflow can be built reproducibly in our current experimental framework. Regards, Reiner [1]: https://wiki.debian.org/ReproducibleBuilds diff --git a/debian/rules b/debian/rules index a9ebb20..f67c0ac 100755 --- a/debian/rules +++ b/debian/rules @@ -74,7 +74,7 @@ build/sunflow:: debian/sunflow.pod -o debian/sunflow.1 # Render icons - convert -background rgba(255,255,255,0) -geometry 48x48 debian/sunflow.svg debian/sunflow.png + convert -background rgba(255,255,255,0) -geometry 48x48 debian/sunflow.svg +set date:create +set date:modify -define png:exclude-chunk=time debian/sunflow.png convert -background rgba(255,255,255,0) -geometry 32x32 debian/sunflow.svg debian/sunflow.xpm clean:: signature.asc Description: OpenPGP digital signature
Bug#778647: closed by Benjamin Kaduk ka...@mit.edu (Bug#778647: fixed in krb5 1.12.1+dfsg-18)
On Wed, 18 Feb 2015, Salvatore Bonaccorso wrote: Hi Benjamin, On Wed, Feb 18, 2015 at 06:24:10PM +, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the src:krb5 package: #778647: krb5: CVE-2014-5355 It has been closed by Benjamin Kaduk ka...@mit.edu. [...] krb5 (1.12.1+dfsg-18) unstable; urgency=high . * Import upstream patch for CVE-2014-5355, Closes: #778647 Thank you! Can you also ask for an unblock of it to the Release Team, so that this fix can go as well into jessie? Hi Salvatore, I plan to do so; I was just going to wait a couple hours to make sure that the buildds are happy with it, first. (I had problems with 1.12.1+dfsg-13 of that nature, IIRC.) -Ben -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778683: Error creating partition table on RAID device
Control: close -1 thanks (resending, forgot to cc bug) On Wed, 2015-02-18 at 13:14 -0500, Phillip Susi wrote: tags 778683 + moreinfo thanks I can't really follow your very well, but it sounds like you did simply select the wrong device in gparted. If you can reproduce this using just parted showing how would make things clear. If you can only reproduce it in gparted, then more detailed steps of how, as well as a copy of the gparted log file should help track down the problem there. You caught me just in time, as I'm intending to actually use this and so it won't be practical to test afterwards. I recreated the RAID array and tried again, and while I have found a serious issue, I can't reproduce the original issue reported in this particular bug, so I'll close this and write up a new report for the other issue. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778644: qtdeclarative-opensource-src: port to m68k
On Wednesday 18 February 2015 09:59:44 Lisandro Damián Nicanor Pérez Meyer wrote: [snip] The patch won't work because on the next upload we will be using the system's double-conversion lib. Just check that the lib builds on m68k and problem fixed. I'm right now building with the above mentioned patch so you can just fix double-conversion. Symbols will be updated with the next upload as soon as there is a build log available at debian ports. Kinds regards, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#776137: sudo: fails to switch between sudo and sudo-ldap: chown: cannot access '/etc/sudoers': No such file or directory
Hi, On 2015-02-07 01:02, Christian Kastner wrote: I've looked into this now, and I believe that the --compare-versions issue and the chown/chmod issue is all there is to this bug. I have attached a new debdiff (v2) with fixes for both. I have tested this patch in a number of combinations, including (but not limited to): sudo (squeeze) - sudo (jessie) upgrade sudo-ldap (squeeze) - sudo-ldap (jessie) upgrade Works as intended. An unchanged /etc/sudoers gets replaced with the new version, a changed sudoers will cause the user to be asked what to do. sudo (jessie)- sudo (jessie+deb8u2) upgrade sudo-ldap (jessie)- sudo-ldap (jessie+deb8u2) upgrade Same result as in the previous case. sudo (jessie+deb8u2) - sudo-ldap (jessie+deb8u2) switch sudo-ldap (jessie+deb8u2) - sudo (jessie+deb8u2) switch /etc/sudoers always gets carried over. There is no scenario where the user might have to be asked, as the package versions (and the sudoers they supply) are identical, and the user's changed version therefore trumps the default version. did anyone get the chance to confirm my results yet? Bdale, once such a confirmation (or another fix) is in, how would you like to proceed? I could help with the RT communication again Regards, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778622: wheezy-pu: package vigor/0.016-19+deb7u1
Control: tags -1 + confirmed On Tue, 2015-02-17 at 15:33 +, Colin Watson wrote: I'd like to upload the following patch to stable-proposed-updates to fix #778409, which the security team doesn't think warrants a DSA (and honestly I'd have to agree). Would this be OK? It matches 0.016-24 in unstable. Please go ahead; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778655: doxygen: Doxygen should not enable markdown by default
Control: tags -1 + moreinfo Hi Ron, Duplicating a bit of our discussion here for keeping track of it. On Wed, Feb 18, 2015 at 09:58:25AM +1030, Ron wrote: So doxygen 1.8 added support for interpreting markdown, and it does this in all normal comment blocks before applying the normal doxygen formatting. Unfortunately, they also chose to enable this by default, so any package that is building docs against this version, which didn't update the doxyconf configuration using this version, to see that this option exists and to turn it off if it breaks the generated documentation, is going to run a fairly high chance of generating fairly horribly broken docs. A quick canary for the extent of this problem is to search for: 'warning: unexpected command endcode' Which went by uncommented on (or I assume inspected) in logs such as was posted to https://bugs.debian.org/680896 and many other places. This is just one fairly common way this fails horribly, resulting in all the comments *above* a @code section being treated as code, and the code section itself being dumped literally to the output - but there are quite a few other ways this will generate awful unreadable documentation when markdown syntax is inadvertently applied to an existing codebase. Thanks for reporting this. I was not aware! Unless we want to ship with a lot of fairly useless -doc packages, it seems like this should probably be disabled by default, until people have become more aware of the problem and have taken steps to avoid it in their own source. I found a lot of build logs that show people having this problem, but no discussion of the cause, the impact, or the fix. I suspect a lot of people who build -doc packages rarely or never actually read them themselves ... Flipping the default of MARKDOWN_SUPPORT in Debian won't happen for the following reasons: * Deviating from upstream is bad. Of course, this means that convincing upstream to change the default necessitates revisiting this decision. * Changing this in the doxygen package won't fix any documentation: I don't expect many packages to be uploaded after a doxygen upload and binNMUs cannot be used as most documentation resides in arch:all packages. Thus it should be easier to just fix build-rdeps of doxygen. Fixing the ones that are already broken is probably going to be something of a major operation in its own right, but the mood in #d-d seemed to be that we should start by limiting the damage here and then tackle that part separately. And this is where the moreinfo tag comes into place: The information of which packages actually are broken is missing entirely. Before this bug becomes actionable in any way, the purported damage needs to be understood. Please remove the moreinfo tag when adding an affected jessie package and explaining how it is affected. Let me add a few hints on which packages to look for. The following packages set MARKDOWN_SUPPORT=NO: hdf5 hwloc libsbml mpich openms ppl simbody witty The following packages set MARKDOWN_SUPPORT=YES: ace apophenia apt aubio bladerf boost1.54 boost1.55 casablanca clipper cmocka colobot cpl csound cupt eigen3 elektra exiv2 feel++ fflas-ffpack freecontact gazebo gdcm geographiclib givaro glfw3 gnuradio gr-fcdproplus grass gtkspellmm imagemagick libam7xxx libburn libcaca libclaw libdatrie libdebian-installer libevdev libhmsbeagle liblo libltc libopendbx libreoffice libsdl2-gfx libsidplayfp libssh libstxxl libthai linbox litl lvtk lxc mysql-workbench ns3 ogre-1.9 openmprtl orthanc pcl psocksxx python-odf qof rapidjson rivet schroot sdformat serd simgrid sord speech-tools sratom ui-gxmlcpp ui-utilcpp v4l-utils visp vlfeat websocketpp The vast majority of build-rdeps of doxygen or doxygen-latex appear to not set MARKDOWN_SUPPORT at all. Helmut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778698: unable to build with kernel 3.19
Hallo, * Andreas Beckmann [Wed, Feb 18 2015, 07:06:40PM]: On 2015-02-18 18:58, Eduard Bloch wrote: Patch attached, tested, please apply. Thanks, but NACK on the patch in this form - this needs to be properly #if'ed on the kernel version s.t. it builds on all kernel versions. Wrong. The thing I exchanged was just the use of a convenience shortcut, and it should work just fine without it with almost any kernel released in the last 8 years. $ git blame v3.18 include/linux/fs.h | grep f_dentry 0f7fc9e4d (Josef Jeff Sipek2006-12-08 02:36:35 -0800 792) #define f_dentry f_path.dentry Regards, Eduard. -- Every great idea is worthless without someone to do the work. --Neil Williams -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699849: Bug#778644: qtdeclarative-opensource-src: port to m68k
On Wednesday 18 February 2015 18:44:16 Thorsten Glaser wrote: [snip] This is #699849 already – Cc’ing that bug since its main‐ tainers should know we have a fix and upstream also fixed it. Note that this does not prevent you from applying the patch to any further uploads that d̲o̲ include the code un‐ der 3rdparty/. There will be no uploads to Qt 5.3.2 unless an RC bug is found, in which case only the RC bug will be fixed as required by the RT. The newer versions (currently 5.4.0) are already available in experimental. -- One World, One web, One program - Microsoft Promo ad. Ein Volk, Ein Reich, Ein Führer - Adolf Hitler 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#777932: FTBFS with gcc 5 : lcalc
Hi, in fact this bug is a duplicate of #748898, where it's stated that sagemath has the same issue : http://trac.sagemath.org/ticket/12437 they have patches, which they might have sent upstream. On the one hand they modify the API/ABI, on the other they fix the compilation... is it a case where it's ok to patch upstream? Snark on #debian-science -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778477: vim-common: vim.svg has non-square bounding box, appears distorted in GNOME Shell
On Sun, 15 Feb 2015 12:00:56 -0500 James McCoy james...@debian.org wrote: On Sun, Feb 15, 2015 at 03:47:31PM +, Simon McVittie wrote: It would probably be possible to postprocess the SVG with xmlstarlet to assign a suitable bounding box. Alternatively, using vimlogo.eps instead of vimlogo.pdf as your source format would probably work, since vimlogo.eps seems to have the correct bounding box already. My poor search skills didn't turn up an eps â svg converter. I would prefer to do that as well, since the eps is the original source file. Do you happen to know of a converter? It looks like inkscape can do this: inkscape --export-plain-svg=vimlogo.svg vimlogo.eps I also tried pstoedit, but it produces an incorrect bounding box. Regards, -- Matijs signature.asc Description: OpenPGP digital signature
Bug#776748: (pre-approval) unblock: libxml2/2.9.1+dfsg1-5 (via t-p-u)
On Thu, Feb 12, 2015 at 23:37:48 +0800, Aron Xu wrote: On Wed, Feb 11, 2015 at 5:59 AM, Julien Cristau jcris...@debian.org wrote: On Tue, Feb 3, 2015 at 04:02:51 +0800, Aron Xu wrote: Updated version of debdiff, removing the -O3 change. The changelog still says build with -O3. Updated as attached. Go ahead, thanks. Cheers, Julien signature.asc Description: Digital signature
Bug#778715: Edge scrolling is quite annoying
Package: evince-gtk Version: 3.14.1-1 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi! Since some versions, evince scrolls its content when the mouse is on the top edge or the bottom edge. This also happens when evince doesn't have the focus or when the mouse is on another screen. The behavior is also quite unexpected. If there is some compile-time option to disable this, it would be welcome. I have an hard time to understand why such a feature has been implemented. - -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages evince-gtk depends on: ii evince-common 3.14.1-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii libatk1.0-02.14.0-1 ii libc6 2.19-15 ii libcairo-gobject2 1.14.0-2.1 ii libcairo2 1.14.0-2.1 ii libevdocument3-4 3.14.1-1 ii libevview3-3 3.14.1-1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-01.36.8-3 ii libxml22.9.2+dfsg1-3 ii shared-mime-info 1.3-1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages evince-gtk recommends: ii dbus-x11 1.8.16-1 Versions of packages evince-gtk suggests: pn gvfs none pn nautilus none ii poppler-data 0.4.7-1 ii unrar 1:5.2.5-1 - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJU5QTiAAoJEJWkL+g1NSX5KhMQAJlpi3oCJr8lddM1f7yjewKz 8VDz9IMo30dVonek9fWHKzauBfw9kRMc8+4LId2InCsXmc3DXbMcD5D+vDC9+j/W MjqLM1/JlMX/5F9n+GVh+otQjd7RqJji45+G8jPO4glC7ODQsqaI8/VMf8NWz3tn N87oN2dim8FQoo5vL7ltlFGdTPLaI1D83RFBHbjv68mCSEWd7yJ14bouk2hir5zw xe4k/DL2tBjMMWfZQ3hL/8VipEAirHCwXh1c87z+TWiUGlAcKsDDD+7TY7BSGifk ihUZjTeSPRfhSV6ueQ0y59Wajvo6PoQ6H2vg+RFbpIhyMqjzSC9ECuXChuKPYFI/ 2yNsSObaGRS5O7TEyWRhAqnRcqtJxAleAy/aj0qZGZuRa4Wf8XoNf8R2fFL8ffAA 7I/4Q7cfB8qOGvezopmGwByloMNO+HiuxyJARwGhbhVKKXVFP86mAvDxVXqojowO hIFY2XVTidhayg7Ez+Gf0xAxKf0Up6hvbx2pfo+crMfBVQRQgKZWEpZ6un0YADq9 lqmjh2Vft0Oe6yednksHVcboD+hLqvJKlGTSxghhpVNzaF7IkMptsmfXIro9dUpL vleeVJvktd9dqvqkM41qsJWQQW19T4MxtqTswISU92jwFgolxi8/QMS4jSAHjVrM n6WOaHo6/WU3bWtGMxUY =qu3a -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#771208: unblock: busybox/1:1.22.0-14
Mehdi Dogguy me...@dogguy.org (2015-02-18): On Thu, Dec 11, 2014 at 08:52:05AM +0100, Ivo De Decker iv...@debian.org wrote: Could you do a new upload with only the security fix? I just did so and uploaded 1:1.22.0-9+deb8u1 to t-p-u. Please push both your jessie branch and tag to git. Mraw, KiBi. signature.asc Description: Digital signature
Bug#768188: Jessie Installer hangs after processing DHCPv6 stateful addressing
Philipp Kern pk...@debian.org (2015-02-18): On Tue, Feb 10, 2015 at 09:22:25AM +0100, Philipp Kern wrote: On Sun, Feb 08, 2015 at 04:21:25PM +0100, Philipp Kern wrote: On the other hand it also seems wrong for di_exec_shell_log to continue after the invoked binary exited. I suspect that'd mean ppoll() and proper signal handling, but I'm at a loss right now how to do that properly in C. Maybe that's the right place to fix it in the meantime. I guess signalfd would make this rather neat, but it's not available on FreeBSD. :( The alternative would be to overwrite the SIGCHLD signal handler regardless of what has been set before and handle the signal in the library. So now I guess the question is if we revert the change that broke it: Don't kill_dhcp_client without reason (Closes: #757711, #757988) Do not kill_dhcp_client after setting the hostname and domain, otherwise Linux udhcpc will stop renewing its lease, and on other platforms dhclient will de-configure the network interface (Closes: #757711, #757988) At this point kFreeBSD is no longer a release architecture and the other platform using dhclient is Ubuntu. GNU/kFreeBSD people are (AFAICT) going to try and get an unofficial release out, so pushing a regression in their way doesn't look too good to me. Maybe using an #ifdef here to avoid killing the DHCP client on kfreebsd, and reinstating the previous codepath on linux would be an acceptable compromise until some evolved signal/process handling pops up (during the stretch release cycle)? (No idea about hurd; anyway, adding both porter lists to Cc.) Mraw, KiBi. signature.asc Description: Digital signature
Bug#778712: libparted2: Breakage of RAID GPT header
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2/18/2015 4:05 PM, jnqnfe wrote: Background = I have a 'fake-raid' RAID0 array, created from two HDDs using my motherboard firmware. This is not used for root, just data. FYI, unless you have to dual boot with windows, you should avoid using fakeraid and stick with conventional linux software raid, which is much better supported. sdb and sdc are the RAID members here and the RAID device is md126. Then you need to only manipulate md126 and ignore sdb and sdc. Most of what you seem to be reporting involves looking directly at the individual disks, which you must not do as that will present a partial/corrupt view of the raid array. In other words, if the first few sectors of the raid array map to sdb, then sdb will appear to have a partition table in its sector 0 that describes a disk that is twice the size, since this partition table is actually describing the raid array and not the individual disk. The one thing you mention that I can't write off as user error is but parted is not and seems to be forcibly applying what it believes to be correct (ignoring the fact that it was only asked to display info, not modify anything). Can you provide more details here? Exactly what command did you run and what changed before vs. after? Parted should not be modifying anything on the disk unless you tell it to. Normally it will throw a warning telling you something is wrong with the disk and ask if you want it to fix it and you have to answer fix for it to modify the disk. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) iQEcBAEBAgAGBQJU5QWEAAoJENRVrw2cjl5RwnkH/0jvimRzKxUZjFait+KVZQgW gq2m6MVJYiDZLX3ajGZj2mxQNVu2RFqDn+YwqAWeDtrQEj/B0TXJC3RbBJpoN3Ao 5kH+lU2Z+YihRDpQMst8VGt1MVA6izcapN1uVeJOcLB2wICSGd0WcjAn8ROSnZNS o/7hXLh7dhxQZT+2HsTpmWa6pLEVvyBeQ8u2giNB0w8he75qv4/AxCFYAdVqhr4Y nNfC9zzCtcOGExu12GyigEpWUPlxUcyGsYzaQRR2hG1Vv7LKBsDBsok3qAag033E DyhyCWDj8NJk1WQIW2ZyVjhcskSyl59Oatd7X3TGSqr2L7yaHV+QAA5Cng+A9fw= =WuvR -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#768878: RFS: sfarklib/0.20131219gitee08d0c-1 [ITP]
Hi Felipe, Do you have some time for sponsoring of these two packages? (sfarklib and sfarkxtc) Or should we ask someone else? Best regards, Ruben Thanks for that. The changes look fine to me, and thanks a heap for the get-orig-source target, it worked like a dream. From my point of view the package is ready for Felipe to take a look when he is available. Best regards, Ruben Cheers, Ross -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776137: sudo: fails to switch between sudo and sudo-ldap: chown: cannot access '/etc/sudoers': No such file or directory
Christian Kastner deb...@kvr.at writes: Bdale, once such a confirmation (or another fix) is in, how would you like to proceed? I could help with the RT communication again Sure. I'm willing to merge a patch and do uploads, but need to know which path they want me to use since the sudo in unstable has diverged From the one in jessie, and there's another new upstream release I plan to upload to unstable soon'ish. Bdale signature.asc Description: PGP signature
Bug#778318: gnuplot5: when using the pdfcairo terminal, lines are much thicker than with gnuplot4
tags 778318 +wontfix thanks Hi Vincent, thanks for bugreport. Gnuplot5 is not quite Gnuplot4, so some incompatibilities are possible. There is an answer from Gnuplot author: === I agree that the default line thickness for pdfcairo is thicker in version 5 than it was in version 4, but do not consider this a bug. Pretty much all the linetype/dash/color properties of default linetypes were reworked in version 5, and this change was a primary reason for bumping the gnuplot major version from 4.x to 5.x In the case of pdfcairo I think the change was made so that the visual appearance would be the same if the same gnuplot commands are run through set term pngcairo and set term pdfcairo. In version 4 the lines appeared much thinner in the png output than in the pdf output. So the change was an intentional part of a larger set of changes. === Regards Anton 2015-02-13 15:43 GMT+01:00 Vincent Lefevre vinc...@vinc17.net: Package: gnuplot5 Version: 5.0.0~rc+dfsg2-1 Severity: important When using the pdfcairo terminal, lines are much thicker than with gnuplot4, so that old plot code is not compatible with gnuplot5, though this incompatibility is not listed on http://www.gnuplot.info/ReleaseNotes_5_0.html This can be seen with: for i in 4 5 do gnuplot$i EOF set terminal pdfcairo lw 10 set output 'out$i.pdf' plot '-' using 1:2 t '' with line 0 0 10 10 e EOF done when both gnuplot4 and gnuplot5 are installed. I've attached the produced out4.pdf and out5.pdf files. Getting too thick lines is annoying in some cases as details can be lost (or become less visible). -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages gnuplot5 depends on: ii gnuplot5-qt [gnuplot5-nox] 5.0.0~rc+dfsg2-1 gnuplot5 recommends no packages. Versions of packages gnuplot5 suggests: ii gnuplot5-doc 5.0.0~rc+dfsg2-1 -- no debconf information -- debian-science-maintainers mailing list debian-science-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778717: Check if we really need to ship libQt5Bootstrap
Source: qtbase-opensource-src Version: 5.3.2+dfsg-4+b1 Severity: normal Check if we really need to ship libQt5Bootstrap*. The name suggests it's only used for bootstrapping... -- 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#768188: Jessie Installer hangs after processing DHCPv6 stateful addressing
On Tue, Feb 10, 2015 at 09:22:25AM +0100, Philipp Kern wrote: On Sun, Feb 08, 2015 at 04:21:25PM +0100, Philipp Kern wrote: On the other hand it also seems wrong for di_exec_shell_log to continue after the invoked binary exited. I suspect that'd mean ppoll() and proper signal handling, but I'm at a loss right now how to do that properly in C. Maybe that's the right place to fix it in the meantime. I guess signalfd would make this rather neat, but it's not available on FreeBSD. :( The alternative would be to overwrite the SIGCHLD signal handler regardless of what has been set before and handle the signal in the library. So now I guess the question is if we revert the change that broke it: Don't kill_dhcp_client without reason (Closes: #757711, #757988) Do not kill_dhcp_client after setting the hostname and domain, otherwise Linux udhcpc will stop renewing its lease, and on other platforms dhclient will de-configure the network interface (Closes: #757711, #757988) At this point kFreeBSD is no longer a release architecture and the other platform using dhclient is Ubuntu. Kind regards Philipp Kern signature.asc Description: Digital signature
