Bug#767356: xserver-xorg-core: segfaults when starting on an AMD APU at glamor_set_screen_pixmap from within radeon_drv (Failed to create fbo, incomplete attachment)
On 12.12.2014 17:48, Wim Lewis wrote: Package: xserver-xorg-core Version: 2:1.16.2.901-1 Followup-For: Bug #767356 Dear Maintainer, Xorg segfaults with a backtrace at startup on my AMD desktop with integrated (Radeon KAVERI) graphics. This looks like the same problem as Yaroslav Halchenko's report in bug #767356. I've attached a more detailed backtrace. I had this problem in 1.16.1.901 in testing, upgraded to 1.16.2.901 from unstable, no apparent change. There is discussion of what looks like the same bug at: https://www.libreoffice.org/bugzilla/show_bug.cgi?id=84186 As you found out there, upgrading libgbm1 to 10.3.y helped. Do you have libegl1-mesa-drivers installed? If yes, can you try if the problem also occurs without it? -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773416: [DEBIAN-LTS] ettercap package
Hello, On Tue, 23 Dec 2014, Thorsten Alteholz wrote: On Tue, 23 Dec 2014, Nguyen Cong wrote: I have created .deb file for ettercap package. great, thanks alot. Since I'm not DD or DM so I attached debdiff file for review as mentioned in LTS/Development wiki page. Could anyone please check it and tell me if any comments? After a first glimpse it seems to be that this package uses quilt, but you directly changed the source files. Please don't change the way of the original maintainer to handle patches. It looks like the upstream author made the same mistake when preparing an upload of his own in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773416#50 I propose to let Nguyen Cong take care of fixing this so that he can learn about quilt and have some easy entry into contributing to the LTS team. Nguyen, feel free to get some inspiration from Gianfranco's more verbose changelog message though. :) 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#773765: pbuilder issue which is related to systemd
Hey Daniel,
Daniel Schepler [2014-12-23 13:54 -0800]:
I was wondering if you could take a look at #773765 and provide your input
on it. Basically, if you create a new pbuilder chroot and then try to use
it to build libxshmfence, it's failing because it doesn't have a working
shm filesystem in the chroot. The cause is that the chroot gets systemd
installed instead of sysvinit, and the systemd package doesn't include any
/run/shm directory (or symlink). So, when pbuilder tries to mount a tmpfs
on chroot/run/shm that fails.
The init system (systemd-sysv vs. sysvinit) is largely irrelevant
here. The binary package which sets up /dev/shm vs. /run/shm for
chroots is initscripts (sysvinit source), and more recent versions
removed a lot of the old postinst magic to handle the gazillion
possible combinations of {dev,run}/shm being a symlink or a directory.
In Ubuntu we already had funny bugs like
https://launchpad.net/bugs/1399772 or https://launchpad.net/bugs/1389891
which Ubuntu now handles in the initscript postinst. I didn't forward
these to Debian as there is still no real consensus how the layout
should be :/
The pbuilder maintainers are saying this is a bug in systemd, as the /run
release goal says the system should have /run/shm with /dev/shm being a
compatibility/ABI symlink to it.
IMHO /run/shm was a really bad idea, but that's a different topic.
/run must never be an actual directory, it must be a tmpfs mount.
Usually the init system sets this up, but as init doesn't run in
schroot, pbuilder, and friends, it's the job of those *chroot
construction packages to set it up. schroot does, maybe pbuilder
doesn't always set this up?
Anyway, I think this is between pbuilder and initscripts to negotiate
what package sets up which directory. I think initscripts should
either create a /dev/shm directory and all init systems and
schroot/pbuilder etc. mount tmpfs there, or we stick to the weird
debianism of /run/shm and then initscripts sets up /dev/shm → /run/shm
and schroot/pbuilder etc. mout a tmpfs there.
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773857: ITP: mitk -- The Medical Imaging Interaction Toolkit
Package: wnpp Severity: wishlist Owner: Mathieu Malaterre ma...@debian.org * Package name: mitk Version : 2014.10.0 Upstream Author : mitk-us...@users.sf.net * URL : http://www.mitk.org * License : BSD Programming Lang: C++ Description : The Medical Imaging Interaction Toolkit The Medical Imaging Interaction Toolkit (MITK) is a free open-source software system for development of interactive medical image processing software. MITK combines the Insight Toolkit (ITK) and the Visualization Toolkit (VTK) with an application framework. As a toolkit, MITK offers those features that are relevant for the development of interactive medical imaging software covered neither by ITK nor VTK, see the Toolkit_Features for details. MITK can be used or integrated with existing solutions in several ways, see Research Platform for examples. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773856: CVE-2014-8136 deadlock on failed migration
Source: libvirt Version: 1.2.9-6 Severity: important Tags: security Current stable is not affected. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-rc6 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773855: CVE-2014-8135 crash when using virStorageVolUpload
Source: libvirt Version: 1.2.9-6 Severity: grave Tags: security Current stable is not affected. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-rc6 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773858: CVE-2014-8131 deadlock or segfault in virConnectGetAllDomainStats
Source: libvirt Version: 1.2.9-6 Severity: grave Tags: security Current stable is not affected. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-rc6 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773859: unblock: edk2/0~20131112.2590861a-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package edk2
Current package in testing has 2 FTBFS bugs due to testing switched to
gcc4.9 and edk2 in testing not supporting it. Version in unstable contains
two fixes for these 2 FTBFS bugs, plus a clarification of why it is not
part of debian main archive (it is in non-free). The package in unstable
builds and works fine.
Overall, edk2, being a UEFI firmware, is a leaf package -- it builds only
ovmf binary package which is optional, to be used with qemu-system to emulate
an UEFI system. Nothing else depends on it, so unblock should not affect
anything. On the other hand, if it is to be removed, qemu will need to be
modified to remove ovmf from the list of recommends.
unblock edk2/0~20131112.2590861a-3
Thanks,
/mjt
Debdiff (please note: some files are with MS-DOS (CR/LF) line endings):
diff -Nru edk2-0~20131112.2590861a/debian/changelog
edk2-0~20131112.2590861a/debian/changelog
--- edk2-0~20131112.2590861a/debian/changelog 2014-02-25 22:49:07.0
+0400
+++ edk2-0~20131112.2590861a/debian/changelog 2014-12-19 10:23:06.0
+0300
@@ -1,3 +1,17 @@
+edk2 (0~20131112.2590861a-3) unstable; urgency=medium
+
+ [ Steve Langasek ]
+ * debian/copyright: include a Disclaimer field to document clearly why
+this package is not in main. Closes: #742589.
+
+ [ Michael Tokarev ]
+ * apply gcc-4.9-align.patch kindly provided by dann frazier to fix ftbfs
+with gcc-4.9 (Closes: #771114)
+ * apply upstream fix-undefined-behavior-in-vfrcompiler.patch, kindly provided
+by dann frazier, to fix another ftbfs (Closes: #773492)
+
+ -- Michael Tokarev m...@tls.msk.ru Fri, 19 Dec 2014 10:16:14 +0300
+
edk2 (0~20131112.2590861a-2) unstable; urgency=medium
* debian/ovmf.links: create a OVMF.fd link for qemu
diff -Nru edk2-0~20131112.2590861a/debian/copyright
edk2-0~20131112.2590861a/debian/copyright
--- edk2-0~20131112.2590861a/debian/copyright 2014-02-25 22:49:07.0
+0400
+++ edk2-0~20131112.2590861a/debian/copyright 2014-12-19 09:52:21.0
+0300
@@ -4,6 +4,10 @@
and https://efi-shell.svn.sourceforge.net/svnroot/efi-shell/trunk/Shell,
with .efi binary files removed from the source at package generation time.
See get-orig-source in debian/rules for details.
+Disclaimer: This package is not part of Debian because it does not meet
+ Debian's license standards due to the licensing on the Intel FAT driver
+ (see License: Intel-Fat-Driver below). With this exception, all other
+ code in this package meets the Debian Free Software Guidelines.
Files: *
Copyright: 1999-2013, Intel Corporation
diff -Nru
edk2-0~20131112.2590861a/debian/patches/fix-undefined-behavior-in-vfrcompiler.patch
edk2-0~20131112.2590861a/debian/patches/fix-undefined-behavior-in-vfrcompiler.patch
---
edk2-0~20131112.2590861a/debian/patches/fix-undefined-behavior-in-vfrcompiler.patch
1970-01-01 03:00:00.0 +0300
+++
edk2-0~20131112.2590861a/debian/patches/fix-undefined-behavior-in-vfrcompiler.patch
2014-12-19 10:22:48.0 +0300
@@ -0,0 +1,35 @@
+Description: Fix undefined behavior in VfrCompiler.
+Origin: http://sourceforge.net/p/edk2-buildtools/code/2667/
+Bug-Debian: http://bugs.debian.org/773492
+Author: Reza Jelveh reza.jel...@tuhh.de
+Reviewed-by: Eric Dong eric.d...@intel.com
+Last-Update: 2014-12-18
+Applied-Upstream: commit:r2667
+
+Index: edk2-0~20131112.2590861a/BaseTools/Source/C/VfrCompile/VfrCompiler.cpp
+===
+--- edk2-0~20131112.2590861a.orig/BaseTools/Source/C/VfrCompile/VfrCompiler.cpp
edk2-0~20131112.2590861a/BaseTools/Source/C/VfrCompile/VfrCompiler.cpp
+@@ -372,6 +372,8 @@ CVfrCompiler::CVfrCompiler (
+ mPreProcessCmd = (CHAR8 *) PREPROCESSOR_COMMAND;
+ mPreProcessOpt = (CHAR8 *) PREPROCESSOR_OPTIONS;
+
++ SET_RUN_STATUS (STATUS_STARTED);
++
+ OptionInitialization(Argc, Argv);
+
+ if ((IS_RUN_STATUS(STATUS_FAILED)) || (IS_RUN_STATUS(STATUS_DEAD))) {
+Index: edk2-0~20131112.2590861a/BaseTools/Source/C/VfrCompile/VfrCompiler.h
+===
+--- edk2-0~20131112.2590861a.orig/BaseTools/Source/C/VfrCompile/VfrCompiler.h
edk2-0~20131112.2590861a/BaseTools/Source/C/VfrCompile/VfrCompiler.h
+@@ -61,7 +61,8 @@ typedef struct {
+ } OPTIONS;
+
+ typedef enum {
+- STATUS_INITIALIZED = 1,
++ STATUS_STARTED = 0,
++ STATUS_INITIALIZED,
+ STATUS_PREPROCESSED,
+ STATUS_COMPILEED,
+ STATUS_GENBINARY,
diff -Nru edk2-0~20131112.2590861a/debian/patches/gcc-4.9-align.patch
edk2-0~20131112.2590861a/debian/patches/gcc-4.9-align.patch
--- edk2-0~20131112.2590861a/debian/patches/gcc-4.9-align.patch 1970-01-01
03:00:00.0 +0300
+++ edk2-0~20131112.2590861a/debian/patches/gcc-4.9-align.patch 2014-12-19
10:21:22.0 +0300
@@ -0,0 +1,30 @@
+Description: Update linker script for gcc-4.9 which
Bug#773860: Update CTK package for integration with MITK
Package: ctk Version: 0.1.0+git20131105~b8307961b6-2 Severity: wishlist Tags: patch Control: block -1 773857 On 12/18/2014 01:17 PM, Mathieu Malaterre wrote: Hi Could someone please let me know what is the status of MITK package in debian ? All I can find is at: http://bugs.mitk.org/show_bug.cgi?id=2637 Ok, this is terribly outdated. I will try to build a current MITK against debian packages and update this. Did anyone started a skeleton package ? I am interested in having mitk directly in debian. We did some work on getting the ctk package to work since ctk is the only big toolkit MITK needs that's not in debian either. The status can be found here [1]. I think most issues are resolved but we did not follow this with high priority. In general I'm not sure if a separate ctk package would be strictly necessary as long as MITK is the only project in debian using it. Some patches for the ctk packages are on my github [2], let me know if they are any questions about them. For MITK it would be great to have at least the workbench application as a general DICOM viewer / annotation tool in debian. We would be very happy to help on packaging this. Do you think we would need lib and dev packages right from the beginning? We currently do not have a working make install that includes header files, but we are currently moving to newest CMake's module system which should greatly simplify things. Thanks for any info, -M Best, and happy holidays Marco [1]: http://www.commontk.org/index.php/Debian_Packaging [2]: https://github.com/nolden/ctk-debian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759457: kbuild: please add support for aarch64
Package: kbuild Version: 1:0.1.9998svn2734+dfsg-1 Followup-For: Bug #759457 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu vivid ubuntu-patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * debian/patches/12_arm64.diff: Add arm64 support to fix FTBFS. Thanks for considering the patch. Logan Rosen -- System Information: Debian Release: jessie/sid APT prefers vivid-updates APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), (100, 'vivid-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-28-generic (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: upstart (via init_is_upstart()) diff -Nru kbuild-0.1.9998svn2734+dfsg/debian/patches/12_arm64.diff kbuild-0.1.9998svn2734+dfsg/debian/patches/12_arm64.diff --- kbuild-0.1.9998svn2734+dfsg/debian/patches/12_arm64.diff 1969-12-31 19:00:00.0 -0500 +++ kbuild-0.1.9998svn2734+dfsg/debian/patches/12_arm64.diff 2014-12-24 03:45:55.0 -0500 @@ -0,0 +1,36 @@ +--- a/kBuild/env.sh b/kBuild/env.sh +@@ -372,6 +372,9 @@ + arm|armv4l|armv5tel|armv5tejl|armv7l) + KBUILD_HOST_ARCH='arm' + ;; ++aarch64) ++KBUILD_HOST_ARCH='arm64' ++;; + alpha) + KBUILD_HOST_ARCH='alpha' + ;; +--- a/kBuild/header.kmk b/kBuild/header.kmk +@@ -189,8 +189,8 @@ + # build types. (PORTME) + # + KBUILD_OSES := darwin dos dragonfly freebsd gnukfreebsd haiku l4 linux netbsd nt openbsd os2 solaris win os-agnostic +-KBUILD_ARCHES:= x86 amd64 sparc32 sparc64 s390 s390x ppc32 ppc64 ppc64el mips32 mips64 ia64 hppa32 hppa64 arm alpha sh +-KBUILD_ARCHES_64 := amd64 sparc64 s390x ppc64 ppc64el mips64 ia64 hppa64 alpha ++KBUILD_ARCHES:= x86 amd64 sparc32 sparc64 s390 s390x ppc32 ppc64 ppc64el mips32 mips64 ia64 hppa32 hppa64 arm arm64 alpha sh ++KBUILD_ARCHES_64 := amd64 sparc64 s390x ppc64 ppc64el mips64 ia64 hppa64 arm64 alpha + KBUILD_ARCHES_32 := x86 sparc32 s390 ppc32 mips32 hppa32 arm sh + + +--- a/src/lib/k/kDefs.h b/src/lib/k/kDefs.h +@@ -192,6 +192,8 @@ + # define K_ARCHK_ARCH_ALPHA + # elif defined(__arm__) || defined(__arm32__) + # define K_ARCHK_ARCH_ARM_32 ++# elif defined(__aarch64__) ++# define K_ARCHK_ARCH_ARM_64 + # elif defined(__hppa__) defined(__LP64__) + # define K_ARCHK_ARCH_PARISC_64 + # elif defined(__hppa__) diff -Nru kbuild-0.1.9998svn2734+dfsg/debian/patches/series kbuild-0.1.9998svn2734+dfsg/debian/patches/series --- kbuild-0.1.9998svn2734+dfsg/debian/patches/series 2014-12-05 05:18:44.0 -0500 +++ kbuild-0.1.9998svn2734+dfsg/debian/patches/series 2014-12-24 03:20:18.0 -0500 @@ -8,3 +8,4 @@ 09_read.c_record_files_SV_33034_Changes_fatal_to_error.patch 10_ppc64el.diff 11_find-glob.patch +12_arm64.diff
Bug#773861: RFS: signify-openbsd/7-1 [ITP] -- Lightweight cryptographic signing and verifying tool
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package signify-openbsd * Package name: signify-openbsd Version : 7-1 Upstream Author : Adrian Perez ape...@igalia.com * URL : https://github.com/aperezdc/signify * License : BSD Section : utils Similar to GNU Privacy Guard (GPG), signify is the tool which OpenBSD uses to cryptographically sign its releases, so that you can be sure that you are actually getting a release made by OpenBSD, as opposed to a malicious forgery designed to look the same. Signify's usage is not limited to OpenBSD's releases, however - it can be used to sign any software. So that it will work on Linux, the version of signify provided in this package is not exactly the same as the version provided in OpenBSD's CVS tree; however the upstream changes are frequently merged. It builds those binary packages: signify-openbsd - Lightweight cryptographic signing and verifying tool To access further information about this package, please visit the following URL: http://mentors.debian.net/package/signify-openbsd Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/s/signify-openbsd /signify-openbsd_7-1.dsc More information about signify-openbsd can be obtained from http://www.tedunangst.com/flak/post/signify Changes since the last upload: * Initial release (Closes: #773850) Regards, Riley Baird -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.13-1-686-pae (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773862: scikit-learn: FTBFS on armhf
Package: scikit-learn
Version: 0.15.2-3
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu vivid ubuntu-patch
Dear Maintainer,
scikit-learn currently FTBFS on armhf due to the patch for skipping tests.
In Ubuntu, the attached patch was applied to achieve the following:
* debian/patches/deb_skip_some_tests:
- Call SkipTest instead of nose.SkipTest to fix NameError.
- Import SkipTest from nose for test_metrics.py.
Thanks for considering the patch.
Logan Rosen
-- System Information:
Debian Release: jessie/sid
APT prefers vivid-updates
APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'),
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-28-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: upstart (via init_is_upstart())
diff -Nru scikit-learn-0.15.2/debian/patches/deb_skip_some_tests_on_arm scikit-learn-0.15.2/debian/patches/deb_skip_some_tests_on_arm
--- scikit-learn-0.15.2/debian/patches/deb_skip_some_tests_on_arm 2014-10-07 22:14:36.0 -0400
+++ scikit-learn-0.15.2/debian/patches/deb_skip_some_tests_on_arm 2014-12-24 03:41:27.0 -0500
@@ -1,25 +1,33 @@
--- a/sklearn/feature_extraction/tests/test_text.py
+++ b/sklearn/feature_extraction/tests/test_text.py
-@@ -357,6 +357,10 @@ def test_tfidf_no_smoothing():
+@@ -357,6 +357,10 @@
numpy_provides_div0_warning = len(w) == 1
in_warning_message = 'divide by zero'
+import platform
+if platform.uname()[4].startswith('armv'):
-+raise nose.SkipTest(no warning gets issued on armel)
++raise SkipTest(no warning gets issued on armel)
+
tfidf = assert_warns_message(RuntimeWarning, in_warning_message,
tr.fit_transform, X).toarray()
if not numpy_provides_div0_warning:
--- a/sklearn/metrics/tests/test_metrics.py
+++ b/sklearn/metrics/tests/test_metrics.py
-@@ -1221,6 +1221,9 @@ def test_precision_recall_curve_toydata(
+@@ -1,6 +1,7 @@
+ from __future__ import division, print_function
+
+ import numpy as np
++from nose import SkipTest
+ from functools import partial
+ from itertools import product
+ import warnings
+@@ -1221,6 +1222,9 @@
y_true = [0, 0]
y_score = [0.25, 0.75]
+import platform
+if platform.uname()[4].startswith('armv'):
-+raise nose.SkipTest(no precision-related exceptions get issued on armel)
++raise SkipTest(no precision-related exceptions get issued on armel)
assert_raises(Exception, precision_recall_curve, y_true, y_score)
assert_raises(Exception, average_precision_score, y_true, y_score)
Bug#768407: cryptsetup: dm-crypt disk unlocks on older Debian, does not on current testing
As the original reporter, I can confirm that it is indeed fixed now for me. Thanks guys! Clayton -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767356: xserver-xorg-core: segfaults when starting on an AMD APU at glamor_set_screen_pixmap from within radeon_drv (Failed to create fbo, incomplete attachment)
On Wed, 24 Dec 2014 16:56:05 +0900 Michel Dänzer mic...@daenzer.net wrote: Do you have libegl1-mesa-drivers installed? If yes, can you try if the problem also occurs without it? It doesn't seem to make a difference. After downgrading libgbm1 back to 10.2.8-1, the problem occurs with or without libegl1-mesa-drivers_10.3.2 (and its dependency libopenvg1-mesa_10.3.2). After upgrading libgbm1 back to 10.3.2-1, X11 works with or without libegl1-mesa-drivers. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773335: www.debian.org: Adding a new entry CD vendors list
Le dimanche 21 décembre 2014, vers 21:37, Alexandre Delanoë écrivait: Le samedi 20 décembre 2014, vers 22:50, Holger Wansing écrivait: Hi, Hello, Alexandre Delanoe deb...@delanoe.org wrote: Package: www.debian.org Severity: normal Dear Maintainer, According to email (and related): * Message-ID: CANarOZoAJhFnKi8uGVN-b2_J+NXGrTYZfNX2K1by=mykzsp...@mail.gmail.com Adding a new entry. Hmm, the following patch is the same as in bug #773261. Not exactly. Maybe you meant another request, probably the one from Sebastian Steins IT-Consulting ? Yes, indeed. I made the cvs diff -u without having added the patch of previous bug report (then this patch add to previous patch the request of Sebastian). I presume I should have commited the previous change in order to create a new patch. If yes, I will do this next time. Should I report a new bug for that ? -- Alexandre Delanoë -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773777: [Pkg-securepass-devel] Bug#773777: libapache2-mod-authz-securepass: incompatible with Apache 2.4 due to use of ap_requires
Dear Logan, a fix for apache 2.4 is currently under development and testing. Due to season's holidays, we expect to commit the fix upstream in January. We would really appreciate if we can hold on for the holidays. Thanks for understanding and Merry Christmas, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766151: [PKG-OpenRC-Debian] Bug#766151: Bug#766151: openrc: tor service fails to start
hero...@gentoo.org writes: Ritesh Raj Sarraf r...@researchut.com writes: On Tuesday 21 October 2014 01:35 PM, Ritesh Raj Sarraf wrote: tor |/lib/rc/sh/runscript.sh: 274: exec: /bin/bash: not found tor | * ERROR: tor failed to start The tor service works if the init script interpreter is changed from /bin/bash to /bin/sh, with /bin/sh symlinking to /bin/dash This seems to be a bug of tor. I don't agree. After talking some with the folks on #openrc, I think this problem is caused by the shebang line at the top of the tor initscript: #! /bin/bash and inparticular that it has a space. (Looking at line 274 gives the location of the exec; tracing through the file says that SHELLBANG is set to /bin/bash, and `exec /bin/bash` fails). It was suggested that this might be fixed in a newer version of openrc (specifically, at or before 0.13.6, since in that version the references to shebang have disappeared), but I do not have the ability to test that right now. signature.asc Description: PGP signature
Bug#773863: fail2ban: jail name is too long
Package: fail2ban
Version: 0.8.6-3wheezy3
Severity: minor
Hello,
If you enable the apache-overflows jail, fail2ban reports the following:
fail2ban.actions.action: ERROR iptables -N fail2ban-apache-overflows
iptables -A fail2ban-apache-overflows -j RETURN
iptables -I INPUT 1 -p tcp -m multiport --dports http,https -j
fail2ban-apache-overflows
iptables -N fail2ban-apache-overflows-log
iptables -I fail2ban-apache-overflows-log -j LOG --log-prefix $(expr
fail2ban-apache-overflows : '\(.\{1,23\}\)'):DROP --log-level warning -m
limit --limit 6/m --limit-burst 2
iptables -A fail2ban-apache-overflows-log -j DROP returned 200
this is because chain name must be shorter than 29 characters:
# iptables -N fail2ban-apache-overflows-log
iptables v1.4.14: chain name `fail2ban-apache-overflows-log' too long (must be
under 29 chars)
Try `iptables -h' or 'iptables --help' for more information.
The solution here is to rename the jail to something shorter.
Best regards,
Ghostdog
-- System Information:
Debian Release: 7.7
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=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages fail2ban depends on:
ii lsb-base4.1+Debian8+deb7u1
ii python 2.7.3-4+deb7u1
ii python-central 0.6.17
Versions of packages fail2ban recommends:
ii iptables 1.4.14-3.1
ii python-gamin 0.1.10-4.1
ii whois 5.1.1~deb7u1
Versions of packages fail2ban suggests:
ii bsd-mailx [mailx] 8.1.2-0.2006cvs-1+deb7u1
-- Configuration Files:
/etc/fail2ban/action.d/iptables-multiport-log.conf changed [not included]
/etc/fail2ban/action.d/iptables-multiport.conf changed [not included]
/etc/fail2ban/action.d/iptables-new.conf changed [not included]
/etc/fail2ban/action.d/iptables.conf changed [not included]
/etc/fail2ban/filter.d/postfix.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#717287: [Packaging] Bug#717287: munin-plugins-core: cpuspeed plugin doesn't work with kernel 3.10
Hi, thanks for your further investigations! On Dienstag, 23. Dezember 2014, gregor herrmann wrote: (Maybe we should retitle the bug report?) please do! thanks already! :) cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#773844: wheezy-pu: package apache2/2.2.22-13+deb7u4
Control: tags -1 + confirmed Hi, please review the update for apache2 for inclusion into s-p-u. It fixes a low-impact security issue and also includes two one-line bug fixes. The changelog is below, debdiff is attached. As I couldn't find any mail about it, I guess that 7.8 Not yet planned; likely mid-December is not yet closed? Indeed. There's probably around 10 days before it closes, assuming I can get all the cats herded in time. * CVE-2013-5704: Fix handling of chunk trailers. A remote attacker could use this flaw to bypass intended mod_headers restrictions, allowing them to send requests to applications that include headers that should have been removed by mod_headers. The new behavior is to not merge trailers into the headers autmatically. A new directive MergeTrailers is introduced to restore the old behavior. * Fix hostname comparison with SNI to be case insensitive. Closes: #771199 * Fix valule of SSL_CLIENT_S_DN_UID in mod_ssl (broken in 2.2.15). Closes: #773841 * Add paragraph about session ticket key life-time and forward secrecy to README.Debian. Closes: #762619 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#754459: ERROR: CCurlFile::FillBuffer - Failed: HTTP response code said error(22)
Hi, I have a similar problem trying to play youtube files. I'm not behind a proxy or anything and a browser can play the same youtube file just fine. It also doesn't appear for every youtube file. Here is an example: I'm having the same problem with the current version in jessie (2:13.2+dfsg1-4): The Youtube plugin does not work, and I get HTTP errors. Same on my Raspberry Pi. It looks like to be a problem with encryption, not with XBMC itself. The videos I could play used TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, while the one I could not used TLS_RSA_WITH_AES_128_GCM_SHA256 and the client signaled decryption error: Interestingly, running curl on the URL that XBMC spits out works (well, the result is a 403, but the HTTPS works). Also, I was able to fix the issue on my Raspberry Pi by downgrading the libcurl-gnutls to the version from Wheezy. Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773864: pre-approval: unblock: python-greenlet/0.4.2-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hi Release Team,
Package python-greenlet FTBFS on ARM architectures, but it's part of
Jessie. Then upstream fixed the build failure[1][2] and released it in
version 0.4.5 that didn't make it to testing. Then Ubuntu backported
those fixes for Utopic[3]. I did the same, used the fixes for 0.4.2 and
asked an other DD, Bálint Réczey to confirm it. Indeed, he says[4] the
fixes are working correctly.
Please let me upload 0.4.2-2 to t-p-u, debdiff is attached.
Thanks,
Laszlo/GCS
unblock python-greenlet/0.4.2-2
[1]
https://github.com/python-greenlet/greenlet/commit/c1437e3677b8f2489e9dab3215eedb58590443c8
[2]
https://github.com/python-greenlet/greenlet/commit/f90dbe4c24a9aed261a5fa9f66fb95ebdb8f21cc
[3]
http://patches.ubuntu.com/p/python-greenlet/python-greenlet_0.4.2-1ubuntu1.patch
[4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751498#63
diff -Nru python-greenlet-0.4.2/debian/changelog python-greenlet-0.4.2/debian/changelog
--- python-greenlet-0.4.2/debian/changelog 2014-02-01 12:34:37.0 +0100
+++ python-greenlet-0.4.2/debian/changelog 2014-12-22 08:48:28.0 +0100
@@ -1,3 +1,12 @@
+python-greenlet (0.4.2-2) testing-proposed-updates; urgency=medium
+
+ [ Robie Basak robie.ba...@ubuntu.com ]
+ * d/p/arm32-{always-use-frame-pointer,unoptimize-return-value}: adjust
+armhf-specific platform code to fix armhf FTBFS (closes: #751498);
+cherry-picked from upstream (LP: #1379297).
+
+ -- Laszlo Boszormenyi (GCS) g...@debian.org Mon, 22 Dec 2014 07:42:41 +
+
python-greenlet (0.4.2-1) unstable; urgency=low
* New upstream release.
diff -Nru python-greenlet-0.4.2/debian/patches/arm32-always-use-frame-pointer python-greenlet-0.4.2/debian/patches/arm32-always-use-frame-pointer
--- python-greenlet-0.4.2/debian/patches/arm32-always-use-frame-pointer 1970-01-01 01:00:00.0 +0100
+++ python-greenlet-0.4.2/debian/patches/arm32-always-use-frame-pointer 2014-12-22 08:46:22.0 +0100
@@ -0,0 +1,34 @@
+From: Robie Basak robie.ba...@canonical.com
+Date: Tue, 14 Oct 2014 13:07:59 +0100
+Subject: [PATCH] arm32: make sure gcc uses a frame pointer
+
+This code assumes that there is a frame pointer. When gcc doesn't use a
+frame pointer here and __thumb__ is defined, then the code clobbers r7
+without declaring it to the compiler. If the compiler uses r7 for
+something else, then this causes arbitrary failures, depending on what
+the optimizer did.
+
+To work around this, tell gcc to always use a frame pointer.
+
+Bug: https://github.com/python-greenlet/greenlet/pull/64
+Origin: upstream, https://github.com/python-greenlet/greenlet/commit/c1437e3677b8f2489e9dab3215eedb58590443c8
+Last-Update: 2014-10-15
+
+---
+ platform/switch_arm32_gcc.h | 3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/platform/switch_arm32_gcc.h b/platform/switch_arm32_gcc.h
+index c6e160d..f74b2bb 100644
+--- a/platform/switch_arm32_gcc.h
b/platform/switch_arm32_gcc.h
+@@ -50,6 +50,9 @@
+ #endif
+
+ static int
++#ifdef __GNUC__
++__attribute__((optimize(no-omit-frame-pointer)))
++#endif
+ slp_switch(void)
+ {
+ void *fp;
diff -Nru python-greenlet-0.4.2/debian/patches/arm32-unoptimize-return-value python-greenlet-0.4.2/debian/patches/arm32-unoptimize-return-value
--- python-greenlet-0.4.2/debian/patches/arm32-unoptimize-return-value 1970-01-01 01:00:00.0 +0100
+++ python-greenlet-0.4.2/debian/patches/arm32-unoptimize-return-value 2014-12-22 08:46:22.0 +0100
@@ -0,0 +1,68 @@
+From 505c91a68aaf5ab56325affd4d8581b32b649cf4 Mon Sep 17 00:00:00 2001
+From: Robie Basak robie.ba...@canonical.com
+Date: Tue, 14 Oct 2014 13:16:22 +0100
+Subject: [PATCH] arm32: force return value from asm
+
+In my case, instead of a simple mov r0, #0, the optimizer had done
+this:
+
+Between calls to slp_save_state and slp_restore_state, it saved the
+value now guaranteed to be 0 using str r0, [r7].
+
+Now, at the end, it restores that value into r0 using ldr r3, [r7]
+and then mov r0, r3.
+
+It isn't clear to me that intermediate values managed by the compiler,
+like this one at [r7], would be preserved in the stack this way,
+especially as at this point we're in a different stack (unknown to the
+optimizer).
+
+Instead, prevent the optimizer from re-using a previous result like this
+by forcing it to rely on the inline assembly to produce the result.
+
+This fixes test failures on Ubuntu Utopic using gcc 4.9.1 (-5ubuntu1).
+
+I think even this is still a hack though, and not guaranteed to work.
+Ultimately, gcc can even re-order the __asm__ volatile functions at
+will around the entire function, or just wrap each REGS_TO_SAVE
+clobbering call with a simple push/pop, thus not preserving the
+registers between stack switches.
+
+The only way I can see of doing this without relying on undefined
+compiler behaviour is to write the entire slp_switch function in
+assembly for
Bug#773852: unblock: zodb/1:3.9.7-5 (pre-approval)
Control: tags -1 + confirmed moreinfo On 2014-12-24 3:25, Arnaud Fontaine wrote: Some time ago I uploaded python-zodb to fix RC bug #767554 but I forgot to remove some headers files, sorry about that. Would it be possible to upload python-zodb with the (really straightforward) diff attached? Please go ahead, and remove the moreinfo tag once the package has been accepted. 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#773865: unblock: imagemagick/8:6.8.9.9-4 [security]
Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: normal Please unblock package imagemagick This fix a few security bug. Bugs are well isolated. Debdiff joined unblock imagemagick/8:6.8.9.9-4 -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) debdiff.xz Description: application/xz
Bug#773866: unblock: mediawiki/1:1.19.20+dfsg-2.2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Dear Release Team,
on behalf of the Security Team, could you please unblock the package
mediawiki ? It fixes yet another security vulnerability (CVE
assignment pending), which prompted the issuing of DSA-3110-1 for
wheezy-security. The corresponding Debian bug is 773654.
You can find the debdiff at the end of this email.
unblock mediawiki/1:1.19.20+dfsg-2.2
-- System Information:
Debian Release: 7.7
APT prefers stable
APT policy: (501, 'stable'), (500, 'oldstable-proposed-updates'), (500,
'oldstable'), (1, 'unstable'), (1, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
diff -Nru mediawiki-1.19.20+dfsg/debian/changelog
mediawiki-1.19.20+dfsg/debian/changelog
--- mediawiki-1.19.20+dfsg/debian/changelog 2014-12-14 18:27:31.0
+0100
+++ mediawiki-1.19.20+dfsg/debian/changelog 2014-12-21 13:11:10.0
+0100
@@ -1,3 +1,12 @@
+mediawiki (1:1.19.20+dfsg-2.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch fixing T76686: thumb.php outputs wikitext message as raw
+HTML, which could lead to xss. Permission to edit MediaWiki namespace
+is required to exploit this.
+
+ -- Sebastien Delafond s...@debian.org Sun, 21 Dec 2014 13:11:10 +0100
+
mediawiki (1:1.19.20+dfsg-2.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru mediawiki-1.19.20+dfsg/debian/patches/series
mediawiki-1.19.20+dfsg/debian/patches/series
--- mediawiki-1.19.20+dfsg/debian/patches/series2014-12-14
18:22:55.0 +0100
+++ mediawiki-1.19.20+dfsg/debian/patches/series2014-12-21
13:10:23.0 +0100
@@ -11,3 +11,4 @@
suppress_warnings.patch
CVE-2014-9277_1.patch
CVE-2014-9277_2.patch
+T76686.patch
diff -Nru mediawiki-1.19.20+dfsg/debian/patches/T76686.patch
mediawiki-1.19.20+dfsg/debian/patches/T76686.patch
--- mediawiki-1.19.20+dfsg/debian/patches/T76686.patch 1970-01-01
01:00:00.0 +0100
+++ mediawiki-1.19.20+dfsg/debian/patches/T76686.patch 2014-12-21
13:10:21.0 +0100
@@ -0,0 +1,55 @@
+From fdd3f464ef9aa7f3276a2a8dddc85e3769cfda83 Mon Sep 17 00:00:00 2001
+From: Kunal Mehta lego...@gmail.com
+Date: Thu, 4 Dec 2014 14:06:55 -0800
+Subject: [PATCH] thumb.php: Set proper output formats for messages going into
+ HTML
+
+* Use -parse() instead of -text() for wikitext messages that were
+ being treated as HTML
+* Explicitly specify -parse() if no output format was set
+* Document that wfThumbError() takes HTML
+
+Bug: T76686
+Change-Id: Id6e7548b2e081cfda7803772ed0395a15feb1f84
+---
+ thumb.php | 8
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+diff --git a/thumb.php b/thumb.php
+index 60a7ffb..a7a09fc 100644
+--- a/thumb.php
b/thumb.php
+@@ -107,13 +107,13 @@ function wfStreamThumb( array $params ) {
+ // Format is timestamp!name
+ $bits = explode( '!', $fileName, 2 );
+ if ( count( $bits ) != 2 ) {
+- wfThumbError( 404, wfMsg( 'badtitletext' ) );
++ wfThumbError( 404, wfMessage( 'badtitletext' )-parse()
);
+ wfProfileOut( __METHOD__ );
+ return;
+ }
+ $title = Title::makeTitleSafe( NS_FILE, $bits[1] );
+ if ( !$title ) {
+- wfThumbError( 404, wfMsg( 'badtitletext' ) );
++ wfThumbError( 404, wfMessage( 'badtitletext' )-parse()
);
+ wfProfileOut( __METHOD__ );
+ return;
+ }
+@@ -136,7 +136,7 @@ function wfStreamThumb( array $params ) {
+
+ // Check the source file storage path
+ if ( !$img ) {
+- wfThumbError( 404, wfMsg( 'badtitletext' ) );
++ wfThumbError( 404, wfMessage( 'badtitletext' )-parse() );
+ wfProfileOut( __METHOD__ );
+ return;
+ }
+@@ -291,7 +291,7 @@ function wfExtractThumbParams( $uri ) {
+ * Output a thumbnail generation error message
+ *
+ * @param $status integer
+- * @param $msg string
++ * @param string $msg HTML
+ * @return void
+ */
+ function wfThumbError( $status, $msg ) {
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773864: pre-approval: unblock: python-greenlet/0.4.2-2
Control: tags -1 + confirmed moreinfo On 2014-12-24 10:54, Laszlo Boszormenyi (GCS) wrote: Package python-greenlet FTBFS on ARM architectures, but it's part of Jessie. Then upstream fixed the build failure[1][2] and released it in version 0.4.5 that didn't make it to testing. Then Ubuntu backported those fixes for Utopic[3]. I did the same, used the fixes for 0.4.2 and asked an other DD, Bálint Réczey to confirm it. Indeed, he says[4] the fixes are working correctly. Please let me upload 0.4.2-2 to t-p-u, debdiff is attached. Please go ahead, and remove the moreinfo tag once the package has been accepted. 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#717287: [Packaging] Bug#717287: munin-plugins-core: cpuspeed plugin doesn't work with kernel 3.10
Control: retitle -1 munin-plugins-core: cpuspeed plugin doesn't work with scaling_driver intel_pstate On Wed, 24 Dec 2014 11:31:27 +0100, Holger Levsen wrote: On Dienstag, 23. Dezember 2014, gregor herrmann wrote: (Maybe we should retitle the bug report?) please do! thanks already! :) Done :) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: B.B. King and Eric Clapton signature.asc Description: Digital Signature
Bug#773864: pre-approval: unblock: python-greenlet/0.4.2-2
Control: tags -1 - moreinfo On Wed, Dec 24, 2014 at 12:11 PM, Adam D. Barratt a...@adam-barratt.org.uk wrote: On 2014-12-24 10:54, Laszlo Boszormenyi (GCS) wrote: Please let me upload 0.4.2-2 to t-p-u, debdiff is attached. Please go ahead, and remove the moreinfo tag once the package has been accepted. Done, uploaded. Thanks, Laszlo/GCS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773867: no sources.lists in bootstraped foreign chroots
package: debootstrap version: 1.0.64~bpo70 Hi, first of all, two phase bootstrapping rocks. debootstrap²++! :-) problem description / steps to reproduce (on amd64 on wheezy, with debooststrap from bpo): # apt-get install qemu-user-static binfmt-support # debootstrap --arch=armel --foreign jessie ./jessie http://ftp.de.debian.org/debian # cp /usr/bin/qemu-arm-static jessie/usr/bin/ # chroot ./jessie/ /debootstrap/debootstrap --second-stage - a nice armel chroot, but /etc/apt/sources.list is empty (and so is sources.list.d/) cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#773834: Prparing a release for stable and lts
Hi, I am now doing my home work for stable and lts Bastien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773868: live-boot: Does not include overlayfs support in initramfs, due to wrong kernel module naming
Package: live-boot Version: 4.0.2-1 Severity: normal Tags: patch Hi, backend/initramfs-tools/live.hook tries to include the overlayfs kernel module in the initramfs. However, that module is called overlay, so it's never included, and then booting with the union=overlayfs parameter can't work out-of-the-box. I've fixed this in the bugfix/overlay-module branch at https://git-tails.immerda.ch/live-boot = please review and merge :) Once Linux 3.18+ reaches sid, with only overlayfs support and no more aufs, Debian Live systems who want/need to ship a kernel newer than the one from Jessie will need to use overlayfs, so it would be good if live-boot in Jessie supported it. I'll let the maintainer judge. 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#773869: freehep-vectorgraphics: Newer version of software exists at http://freehep.github.io/freehep-vectorgraphics/
Source: freehep-graphicsio-pdf Version: 2.1.1+dfsg-1 Severity: normal The software at java.freehep.org was declared obsolete in 2007, but has been taken up at http://freehep.github.io/freehep-vectorgraphics/ where it is undergoing - AFAICT - minor development and bug-fixing work. The current release is version 2.4 - it may well make sense to package this in place of the current version. This obviously applies to all of the freehep-vectorgraphics packages, but I'm only writing this single bug report. Best wishes, Julian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773416: [DEBIAN-LTS] ettercap package
On Wed, 24 Dec 2014, Nguyen Cong wrote: I have done rebuild the ettercap package using quilt patch. Could you please give me some comments. Here they are. diff -u ettercap-0.7.3/debian/changelog ettercap-0.7.3/debian/changelog --- ettercap-0.7.3/debian/changelog +++ ettercap-0.7.3/debian/changelog @@ -1,3 +1,11 @@ +ettercap (1:0.7.3-2.1+squeeze2) squeeze-lts; urgency=medium + + * Non-maintainer upload. + * Fix CVE-2014-9380 and CVE-2014-9381 using patch file from +Gianfranco Costamagna in Bug#773416 Mes#20 + + -- Nguyen Cong cong.nguyen...@toshiba-tsdv.com Tue, 23 Dec 2014 09:44:32 +0700 Please have a look at the changelog of Gianfranco and acknowledge the origin of the patch as coming from their true author. --- ettercap-0.7.3/debian/patches/series +++ ettercap-0.7.3/debian/patches/series @@ -3,0 +4 @@ +04_CVE-2014-9380-9381.patch Why is there no context shown here? --- ettercap-0.7.3/debian/patches/03_CVE-2013-0722.patch +++ ettercap-0.7.3/debian/patches/03_CVE-2013-0722.patch Why are there changes to this patch file? You should strive to modify the strict minimum. And AFAIK this patch doesn't have to be updated. It is applying cleanly. --- ettercap-0.7.3.orig/debian/patches/04_CVE-2014-9380-9381.patch +++ ettercap-0.7.3/debian/patches/04_CVE-2014-9380-9381.patch @@ -0,0 +1,30 @@ +From: Gianfranco Costamagna costamagnagianfra...@yahoo.it +Subject: Re: Bug#773416: fixed in ettercap 1:0.8.1-3 +Date: Mon, 22 Dec 2014 10:22:56 + (UTC) + +The dissector_cvs function in dissectors/ec_cvs.c in Ettercap 8.1 +allows remote attackers to cause a denial of service (out-of-bounds +read) via a packet containing only a CVS_LOGIN signature. + +See Debian Bug #773416 Message #20 FYI, we like to document new patches with meta-information that respect this format: http://dep.debian.net/deps/dep3/ Besides those details, it looks ok. 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#773871: unblock: ivy/2.3.0-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package ivy. The jar distributed is missing a template file
(#762108) and this is breaking one of the functionalities.
Thank you
unblock ivy/2.3.0-4
diff -Nru ivy-2.3.0/debian/build.xml ivy-2.3.0/debian/build.xml
--- ivy-2.3.0/debian/build.xml 2013-07-15 18:25:53.0 +0200
+++ ivy-2.3.0/debian/build.xml 2014-12-24 12:24:06.0 +0100
@@ -17,6 +17,7 @@
include name=**/?*.ent /
include name=**/?*.css /
include name=**/?*.ico /
+include name=**/pom.template /
/patternset
target name=clean
delete dir=${class.dir} quiet=true /
diff -Nru ivy-2.3.0/debian/changelog ivy-2.3.0/debian/changelog
--- ivy-2.3.0/debian/changelog 2013-09-09 21:19:23.0 +0200
+++ ivy-2.3.0/debian/changelog 2014-12-24 12:48:03.0 +0100
@@ -1,3 +1,11 @@
+ivy (2.3.0-4) unstable; urgency=medium
+
+ * Team upload.
+ * Added the missing pom.template file in ivy.jar (Closes: #762108)
+ * Standards-Version updated to 3.9.6 (no changes)
+
+ -- Emmanuel Bourg ebo...@apache.org Wed, 24 Dec 2014 12:47:57 +0100
+
ivy (2.3.0-3) unstable; urgency=low
* Team upload.
diff -Nru ivy-2.3.0/debian/control ivy-2.3.0/debian/control
--- ivy-2.3.0/debian/control2013-08-07 09:08:14.0 +0200
+++ ivy-2.3.0/debian/control2014-12-24 12:33:23.0 +0100
@@ -8,7 +8,7 @@
libcommons-lang-java, libcommons-cli-java, liboro-java,
libcommons-collections3-java, libcommons-vfs-java (= 2.0), junit,
libjsch-java, libbcprov-java, libbcpg-java, default-jdk-doc
-Standards-Version: 3.9.4
+Standards-Version: 3.9.6
Vcs-Svn: svn://anonscm.debian.org/pkg-java/trunk/ivy
Vcs-Browser: http://anonscm.debian.org/viewvc/pkg-java/trunk/ivy/
Homepage: http://ant.apache.org/ivy/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773872: biber: hyphenation hints fail
Package: biber Version: 1.9-2 When I add hyphenation hints (hy\-phe\-na\-tion) to bibliography entries, running biber and then latex again causes the following error: ! Package inputenc Error: Unicode char \u8:‑ not set up for use with LaTeX. Reportedly, this bug is fixed in the 2.0 version of biber. But maybe the corresponding patch (commit 732ebc5962850416178d4802a44583e3cd1b3740 upstream) could be backported to jessie? More information on this bug may be found upstream at https://github.com/plk/biber/issues/46 . Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772560: debsources: please add a CA-signed SSL setup
On Tue, 2014-12-23 at 23:45 -0500, James McCoy wrote: Debsources itself isn't something that specifically warrants https-only access, so we should enable the amin deploying the code to make that choice for herself. Using scheme-relative URLs enables that choice. Using schema-relative URLs makes sense for debsources itself since we can't know which protocol the sysadmin will make it available over. Hence why the patch I posted didn't change debsources URLs. Debian has chosen to use https, so our instance of the service can be configured at the httpd level to only allow https access. Ack, Stefano, could you redirect http URLs to https? -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#773873: libidna-punycode-perl: dead code - replaced by liburi-perl
Package: libidna-punycode-perl Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 IDNA::Punycode has disappeared from CPAN. URI mentions its URI::_punycode being based on IDNA::Punycode. No packages depend on libidna-punycode-perl - candidate for removal? - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQF8BAEBCgBmBQJUmsLYXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0 RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWFIMH/1V5U54QvZbOBhQiXCJPbPzW /inE5tgBUPOigjtPyo8O7Zrjp+qbmlEAZD2us3c1p0UR3aDrND+IeL03NLkszfr6 tWyA8TRU6A2LYXC8VuG8Xyp43lrO+d7QgSY44kT4RveXmkK9eMmdGoaZEi8nm0Ta 4HwxYjUBqzi2AnjZmHMMAHKTT8w1gQChZZI2nWAHbYwSa3woZTMKKIxeelJzfLRO /ZbCX/N+gnkLMdQY2IA7b3YiuUFIjQ26iwHr9bZNAW9MkzvDKXu++r9dJ3TicfQH g8QSWH/yIT/qR0asx8JyyHVVms8DTy5HGlnWdYeiP7uIhuvek6KLI7CAJk613Js= =qzK6 -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#773874: piuparts: schroot option fails with valid name without :
Package: piuparts
Version: 0.61
Severity: important
Tags: patch
If I try to use piuparts with schroot parameter:
Command line arguments: /usr/sbin/piuparts --allow-database -D ubuntu -d trusty
--schroot trusty-amd64 [...] --apt baloo=4.14.3.0.git20141125.e4ddeb6
0m0.0s INFO: Running on: Linux tabin.local 3.17-1.towo.4-siduction-amd64 #1 SMP
PREEMPT siduction 3.17-9 (2014-10-28) x86_64
Traceback (most recent call last):
File /usr/sbin/piuparts, line 3068, in module
main()
File /usr/sbin/piuparts, line 3060, in main
process_packages(regular_packages_list)
File /usr/sbin/piuparts, line 2973, in process_packages
chroot.create()
File /usr/sbin/piuparts, line 703, in create
self.setup_from_schroot(settings.schroot)
File /usr/sbin/piuparts, line 808, in setup_from_schroot
self.schroot_session = schroot.split(:)[1] + - + str(uuid.uuid1()) +
-piuparts
IndexError: list index out of range
The schroot environment must not have an : as delimiter, than schroot starts
a new session. mk-sbuild is there very clear:
To CHANGE the golden image: sudo schroot -c source:${SCHROOT_NAME} -u root
To ENTER an image snapshot: schroot -c $SCHROOT_NAME
and normally you don't want to change the base image if you access schroot or
at least you should have the possibility :)
--- a/piuparts 2014-12-24 14:51:34.902723380 +0100
+++ b/piuparts 2014-12-24 14:52:21.306523398 +0100
@@ -805,7 +805,11 @@
run(prefix + [tar, -C, self.name, -zxf, tarball])
def setup_from_schroot(self, schroot):
- self.schroot_session = schroot.split(:)[1] + - + str(uuid.uuid1())
+ -piuparts
+ try:
+ name = schroot.split(:)[1]
+ except:
+ name = schroot
+ self.schroot_session = name + - + str(uuid.uuid1()) + -piuparts
run(['schroot', '--begin-session', '--chroot', schroot ,
'--session-name', self.schroot_session])
ret_code, output = run(['schroot', '--chroot', session: +
self.schroot_session, '--location'])
self.name = output.strip()
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (600, 'unstable'), (500, 'testing'), (500, 'stable'), (110,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.17-1.towo.4-siduction-amd64 (SMP w/2 CPU cores; PREEMPT)
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 piuparts depends on:
ii debootstrap 1.0.66
ii debsums 2.0.52+nmu2
ii dpkg 1.17.22
ii lsb-release 4.1+Debian13+nmu1
ii lsof 4.86+dfsg-1
ii piuparts-common 0.61
ii python-debian0.1.25
pn python:any none
Versions of packages piuparts recommends:
ii adequate 0.12.1
Versions of packages piuparts suggests:
ii schroot 1.6.10-1+b1
-- debconf-show failed
-- debsums errors found:
debsums: changed file /usr/sbin/piuparts (from piuparts package)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773876: Desktop file uses outdated Icedove-bin for StartupWMClass
Package: icedove Version: 31.3.0-1 Severity: normal Tags: patch Hi, The .desktop file shipped with the Icedove package has an entry StartupWMClass with value Icedove-bin. I believe this was necessary some time ago when Icedove was launched differently but it seems that it's now outdated since the value set for WM_CLASS by the application doesn't contain -bin anymore : raph@arche:~$ xprop | grep CLASS WM_CLASS(STRING) = Mail, Icedove This disturbs application launchers, for example I tried plank from experimental and it had some trouble matching the window to the correct launcher/icon. Unless there is some valid reason to keep the Icedove-bin value for StartupWMClass, I suggest to change it to simply Icedove (a patch for the current sid version is included), hopefully before jessie is released. Regards, -- Raphaël Halimi -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages icedove depends on: ii debianutils 4.4+b1 ii fontconfig2.11.0-6.3 ii libasound21.0.28-1 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-13 ii libcairo2 1.14.0-2.1 ii libdbus-1-3 1.8.12-2 ii libdbus-glib-1-2 0.102-1 ii libevent-2.0-52.0.21-stable-1.1 ii libffi6 3.1-2+b2 ii libfontconfig12.11.0-6.3 ii libfreetype6 2.5.2-2 ii libgcc1 1:4.9.2-9 ii libgdk-pixbuf2.0-02.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk2.0-0 2.24.25-1 ii libhunspell-1.3-0 1.3.3-3 ii libnspr4 2:4.10.7-1 ii libnss3 2:3.17.2-1 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 libpixman-1-0 0.32.6-3 ii libsqlite3-0 3.8.7.2-1 ii libstartup-notification0 0.12-4 ii libstdc++64.9.2-9 ii libvpx1 1.3.0-3 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii libxrender1 1:0.9.8-1+b1 ii libxt61:1.1.4-1+b1 ii psmisc22.21-2 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages icedove recommends: ii hunspell-en-us [hunspell-dictionary] 20070829-6 ii hunspell-fr-comprehensive [hunspell-dictionary] 1:5.2-1 Versions of packages icedove suggests: ii fonts-lyx 2.1.2-3 ii libgssapi-krb5-2 1.12.1+dfsg-16 -- no debconf information diff -rupN icedove-31.3.0.orig/debian/icedove.desktop icedove-31.3.0/debian/icedove.desktop --- icedove-31.3.0.orig/debian/icedove.desktop 2014-12-04 18:58:41.0 +0100 +++ icedove-31.3.0/debian/icedove.desktop 2014-12-24 14:36:51.953252223 +0100 @@ -9,7 +9,7 @@ Type=Application Icon=icedove Categories=Network;Email;News;GTK; MimeType=message/rfc822;x-scheme-handler/mailto; -StartupWMClass=Icedove-bin +StartupWMClass=Icedove StartupNotify=true Name[ca]=Client de correu Icedove Name[cs]=Poštovní klient Icedove
Bug#773875: totem: video stutter and high CPU load for 5-10 seconds opening every video file
Package: totem Version: 3.14.0-2 Severity: normal Dear Maintainer, * What led up to the situation? Opening any video file. * What exactly did you do (or not do) that was effective (or ineffective)? Tried opening different files (containers) and launching totem via the command line (no errors or messages at all). * What was the outcome of this action? File plays but video stutters and CPU load is very high for 5-10 seconds; after that video plays normally and CPU load is fine. * What outcome did you expect instead? File plays normally with no stuttering nor high CPU load right from the start (as with VLC). This bug is annoying because I often happen to launch files for a few seconds and discard them almost immediately so I happen to see this bad behaviour most of the time. Don't know if it's relevant but I'm running intel video drivers from experimental and SNA (new default). Thanks! -- 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/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 totem depends on: ii gnome-icon-theme3.12.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii grilo-plugins-0.2 0.2.13-3 ii gsettings-desktop-schemas 3.14.1-1 ii gstreamer1.0-clutter2.0.12-1 ii gstreamer1.0-plugins-bad1.4.4-2 ii gstreamer1.0-plugins-base 1.4.4-2 ii gstreamer1.0-plugins-good 1.4.4-2 ii gstreamer1.0-x 1.4.4-2 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-13 ii libcairo-gobject2 1.14.0-2.1 ii libcairo2 1.14.0-2.1 ii libclutter-1.0-01.20.0-1 ii libclutter-gst-2.0-02.0.12-1 ii libclutter-gtk-1.0-01.6.0-1 ii libcogl-pango20 1.18.2-3 ii libcogl-path20 1.18.2-3 ii libcogl20 1.18.2-3 ii libdrm2 2.4.58-2 ii libegl1-mesa [libegl1-x11] 10.3.2-1 ii libgbm1 10.3.2-1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libgirepository-1.0-1 1.42.0-2.2 ii libglib2.0-02.42.1-1 ii libgnome-desktop-3-10 3.14.1-1 ii libgrilo-0.2-1 0.2.11-2 ii libgstreamer-plugins-base1.0-0 1.4.4-2 ii libgstreamer1.0-0 1.4.4-2 ii libgtk-3-0 3.14.5-1 ii libjson-glib-1.0-0 1.0.2-1 ii libnautilus-extension1a 3.14.1-2 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpeas-1.0-0 1.12.1-2 ii libtotem-plparser18 3.10.3-1 ii libtotem0 3.14.0-2 ii libwayland-client0 1.6.0-2 ii libwayland-cursor0 1.6.0-2 ii libwayland-egl1-mesa [libwayland-egl1] 10.3.2-1 ii libwayland-server0 1.6.0-2 ii libx11-62:1.6.2-3 ii libxcomposite1 1:0.4.4-1 ii libxdamage1 1:1.1.4-2+b1 ii libxext62:1.3.3-1 ii libxfixes3 1:5.0.1-2+b2 ii libxi6 2:1.7.4-1+b2 ii libxkbcommon0 0.4.3-2 ii libxml2 2.9.2+dfsg1-1+b1 ii libxrandr2 2:1.4.2-1+b1 pn python:any none ii totem-common3.14.0-2 Versions of packages totem recommends: ii gstreamer1.0-libav 1.4.4-2 ii gstreamer1.0-plugins-ugly 1.4.4-2 ii gstreamer1.0-pulseaudio1.4.4-2 ii totem-plugins 3.14.0-2 Versions of packages totem suggests: pn gnome-codec-install 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#741451: Bugfix
On 23/12/14 16:00, Jay Berkenbilt wrote: Thanks, Tomasz, for preparing the NMU and Balint for uploading! I've tweaked the DEP-3 stuff in the patch a little and changed its name, and am preparing a regular, non-NMU upload which I will upload momentarily. I've given Tomasz credit for the fix. Sorry for not being more on top of it. Your good efforts made my job trivial. Thanks! I have also submitted an unblock request to the release team. -- Jay Berkenbilt q...@debian.org Great! :D Merry Christmas! Tomasz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773863: fail2ban: jail name is too long
On Wed, 24 Dec 2014, Ghostdog wrote:
Package: fail2ban
Version: 0.8.6-3wheezy3
Severity: minor
Hello,
If you enable the apache-overflows jail, fail2ban reports the following:
fail2ban.actions.action: ERROR iptables -N fail2ban-apache-overflows
iptables -A fail2ban-apache-overflows -j RETURN
iptables -I INPUT 1 -p tcp -m multiport --dports http,https -j
fail2ban-apache-overflows
iptables -N fail2ban-apache-overflows-log
iptables -I fail2ban-apache-overflows-log -j LOG --log-prefix $(expr
fail2ban-apache-overflows : '\(.\{1,23\}\)'):DROP --log-level warning -m
limit --limit 6/m --limit-burst 2
iptables -A fail2ban-apache-overflows-log -j DROP returned 200
this is because chain name must be shorter than 29 characters:
# iptables -N fail2ban-apache-overflows-log
iptables v1.4.14: chain name `fail2ban-apache-overflows-log' too long (must
be under 29 chars)
Try `iptables -h' or 'iptables --help' for more information.
The solution here is to rename the jail to something shorter.
Thanks. It is unlikely I would be uploading proper fix for this to
wheezy but let's keep it open others find a fix for them happen they run
into it. But upstream in 0.9.0 we reduced prefix to f2b- to mitigate
this problem. Not sure what course of action to choose for jessie's
version. since bug is not severe, actually it would unlikely be
accepted at this point either
Cheers!
--
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Research Scientist,Psychological and Brain Sciences Dept.
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773877: mirror submission for pubmirrors.dal.corespace.com
Package: mirrors Severity: wishlist Submission-Type: new Site: pubmirrors.dal.corespace.com Type: leaf Archive-architecture: amd64 i386 Archive-ftp: /debian/ Archive-http: /debian/ IPv6: no Archive-upstream: lug.mtu.edu Updates: four Maintainer: Ryan Coplen mirr...@corespace.com Country: US United States Location: Dallas, TX Sponsor: Corespace http://corespace.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773878: wide-dhcpv6-server: not debootstrap installable
Package: wide-dhcpv6-server Version: 20080615-11.1 Severity: normal Dear Maintainer, When trying to use wide-dhcpv6-server with debootstrap it fails; attached is the console output and debootstrap.log. Looking at the postinst script I think I see the problematic section, which is also present in sid's 20080615-13 release too: # Automatically added by dh_installinit if [ -x /etc/init.d/wide-dhcpv6-server ]; then update-rc.d wide-dhcpv6-server defaults /dev/null invoke-rc.d wide-dhcpv6-server start || exit $? HERE fi # End automatically added section If we compare it to something like unbound which works fine with debootstrap: # Automatically added by dh_installinit if [ -x /etc/init.d/unbound ]; then update-rc.d unbound defaults /dev/null if [ -n $2 ]; then _dh_action=restart else _dh_action=start fi invoke-rc.d unbound $_dh_action || true HERE fi # End automatically added section I suspect all that needs to be done is replace 'exit $?' with 'true' to solve this. However, I see in the source it is just a macro (#DEBHELPER#) and I have no idea how to persuade dh_installinit at your end to emit this kind of output instead. Let me know if you need any more information. Kind Regards -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-0.bpo.4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash aclouter@stevemcqueen:/usr/src/bratwurst$ sudo debootstrap --arch=i386 --variant=minbase --include=wide-dhcpv6-server wheezy fakeisp/.rootfs http://http.debian.net/debian [snipped] I: Configuring libstdc++6:i386... I: Configuring readline-common... I: Configuring libapt-pkg4.12:i386... I: Configuring libreadline6:i386... I: Configuring gnupg... I: Configuring apt... W: Failure while configuring base packages. This will be re-attempted up to five times. W: See /usr/src/bratwurst/fakeisp/.rootfs/debootstrap/debootstrap.log for details (possibly the package wide-dhcpv6-server is at fault) I: Configuring wide-dhcpv6-server... W: Failure while configuring base packages. This will be re-attempted up to five times. W: See /usr/src/bratwurst/fakeisp/.rootfs/debootstrap/debootstrap.log for details (possibly the package wide-dhcpv6-server is at fault) W: Failure while configuring base packages. This will be re-attempted up to five times. W: See /usr/src/bratwurst/fakeisp/.rootfs/debootstrap/debootstrap.log for details (possibly the package wide-dhcpv6-server is at fault) W: Failure while configuring base packages. This will be re-attempted up to five times. W: See /usr/src/bratwurst/fakeisp/.rootfs/debootstrap/debootstrap.log for details (possibly the package wide-dhcpv6-server is at fault) W: Failure while configuring base packages. This will be re-attempted up to five times. W: See /usr/src/bratwurst/fakeisp/.rootfs/debootstrap/debootstrap.log for details (possibly the package wide-dhcpv6-server is at fault) gpgv: Signature made Sat Oct 18 11:33:02 2014 BST using RSA key ID 46925553 gpgv: Good signature from Debian Archive Automatic Signing Key (7.0/wheezy) ftpmas...@debian.org gpgv: Signature made Sat Oct 18 11:37:18 2014 BST using RSA key ID 65FFB764 gpgv: Good signature from Wheezy Stable Release Key debian-rele...@lists.debian.org dpkg: warning: parsing file '/var/lib/dpkg/status' near line 5 package 'dpkg': missing description dpkg: warning: parsing file '/var/lib/dpkg/status' near line 5 package 'dpkg': missing architecture Selecting previously unselected package base-files. dpkg: regarding .../base-files_7.1wheezy7_i386.deb containing base-files, pre-dependency problem: base-files pre-depends on awk awk is not installed. dpkg: warning: ignoring pre-dependency problem! (Reading database ... 0 files and directories currently installed.) Unpacking base-files (from .../base-files_7.1wheezy7_i386.deb) ... Selecting previously unselected package base-passwd. Unpacking base-passwd (from .../base-passwd_3.5.26_i386.deb) ... dpkg: base-passwd: dependency problems, but configuring anyway as you requested: base-passwd depends on libc6 (= 2.8); however: Package libc6 is not installed. Setting up base-passwd (3.5.26) ... dpkg: base-files: dependency problems, but configuring anyway as you requested: base-files depends on awk; however: Package awk is not installed. Setting up base-files (7.1wheezy7) ... dpkg: warning: parsing file '/var/lib/dpkg/status' near line 50 package 'dpkg': missing description dpkg: warning: parsing file '/var/lib/dpkg/status' near line 50 package 'dpkg': missing architecture dpkg: regarding .../archives/dpkg_1.16.15_i386.deb containing dpkg, pre-dependency problem: dpkg pre-depends on libbz2-1.0 libbz2-1.0 is not
Bug#768345: devscripts: upstream signature verification fails with gpg 2.1
Hi, Daniel Kahn Gillmor wrote: On 12/16/2014 03:51 PM, James McCoy wrote: On Dec 16, 2014 2:57 PM, Daniel Kahn Gillmor d...@fifthhorseman.net wrote: On Thu 2014-11-06 12:20:14 -0500, Daniel Kahn Gillmor wrote (in #768345): when gpg2 2.1 is installed (currently available in debian experimental), uscan --verbose fails to check the upstream signature when the upstream signing key is ascii-armored. I ran into this, too. 2.1 is unlikely to be released with jessie, but i am hoping to backport relatively early in the jessie cycle so that people can have access to OpenPGP ECC. I suppose if devscripts gets backported as well, we can just rely on jessie-backports users to upgrade both together. Adding a Breaks: devscripts (= 2.14.11) or similar to the gnupg2 package in Experimental should fix that issue. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773879: pulseaudio: FTBFS on non-linux archs
Package: pulseaudio Version: 5.99.2-1 Severity: serious Enabling systemd socket activation was unconditional, causing failures in non-linux archs. Filing this bug so I don't forget to fix this. -- Saludos, Felipe Sateler
Bug#773880: installation-reports: EFI partition cannot be logical
Package: installation-reports Severity: normal Tags: d-i Dear Maintainer, When I tried to install Debian Jessie on a UEFI PC for the first time, I tried to create the EFI partition as a logical one. This resulted in GRUB entering rescue mode and the system unable to boot. Everything worked fine when I tried again with the EFI partition as a primary one. In case the EFI partition must be primary, the solution is to simply modify the installer so that it does not allow the EFI partition to be logical. -- Package-specific info: Boot method: Image version: Date: Date and time of the install Machine: Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=8 (jessie) - installer build 20141002 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux wil-pc 3.16-2-amd64 #1 SMP Debian 3.16.3-2 (2014-09-20) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06) lspci -knn: Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000] lspci -knn: Kernel driver in use: hsw_uncore lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) lspci -knn: Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06) lspci -knn: Subsystem: Intel Corporation Device [8086:2010] lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 05) lspci -knn: Subsystem: Gigabyte Technology Co., Ltd Device [1458:5007] lspci -knn: Kernel driver in use: xhci_hcd lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04) lspci -knn: Subsystem: Gigabyte Technology Co., Ltd Device [1458:1c3a] lspci -knn: 00:16.3 Serial controller [0700]: Intel Corporation 8 Series/C220 Series Chipset Family KT Controller [8086:8c3d] (rev 04) lspci -knn: Subsystem: Gigabyte Technology Co., Ltd Device [1458:1c3a] lspci -knn: Kernel driver in use: serial lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I217-V [8086:153b] (rev 05) lspci -knn: Subsystem: Gigabyte Technology Co., Ltd Device [1458:e000] lspci -knn: Kernel driver in use: e1000e lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d] (rev 05) lspci -knn: Subsystem: Gigabyte Technology Co., Ltd Device [1458:5006] lspci -knn: Kernel driver in use: ehci-pci lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller [8086:8c20] (rev 05) lspci -knn: Subsystem: Gigabyte Technology Co., Ltd Device [1458:a002] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 [8086:8c10] (rev d5) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 [8086:8c16] (rev d5) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 [8086:8c18] (rev d5) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset
Bug#773817: Some analysis regarding the socks4 related segfault
TLDR: Workaround: Bypass the name resolution attempt and provide the IPv4 address directly. I cannot upload a fixed package to Debian at the moment -- I'd be very grateful if somebody prepared an NMU. The crash happens in sock_proxychain_new() [sock_proxy.c:nsock_proxy.c:106] when a proxy entry has not been properly initialized. In the reported scenario, there seem to be two connected causes: (1) proxy_socks4_node_new() exits with an error if the resulting address as returned by proxy_resolve() is not an AF_INET address. Running nmap -v --proxies socks4://ipv6.google.com:8909 reproducably leads to a segfault at the same place. (2) As the *_node_new() function has failed, proxy_noew_new() [nsock_proxy.c:371] returns a NULL pointer which is dereferenced in nsock_proxychain_new(). It does not matter why proxy_socks4_node_new() fails, either: Running nmap -v --proxies socks4://foo:8909 also segfaults if foo cannot be resolved to an IPv4 address. Cheers, -Hilko -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773881: live-boot: Fails to boot with union=overlayfs
Package: live-boot
Version: 4.0.2-1
Severity: normal
Hi,
I've tried booting a Wheezy system (live-boot 3.x) with Linux 3.18
from experimental, udev from wheezy-backports (Wheezy's udev isn't
supported by this new kernel), and union=overlayfs.
I'm manually had the overlay module included into the initramfs, to
workaround the other bug I've just reported.
Boots fails and I get dropped into the initramfs emergency shell, for
various reasons:
* first, mount -t overlayfs is called, while it should be
mount -t overlay
* second, we try to mount the ${UNIONTYPE} (aka. overlayfs)
device, which fails: it should be overlay
* third, the call to mount lacks the workdir= option.
I've verified that the source code in the debian-next branch is
affected as well (but not tested in practice, which seemed futile
given the code hasn't changed). I may work on a fix soonish, but don't
hold your breathe.
It seems that the code would be simpler if we accepted union=overlay
instead of union=overlayfs. Can we do that? Non-experimental Debian
kernels have never supported overlayfs yet, so that should be
fine, no?
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#773765: pbuilder issue which is related to systemd
Martin Pitt dixit: Usually the init system sets this up, but as init doesn't run in schroot, pbuilder, and friends, it's the job of those *chroot construction packages to set it up. schroot does, maybe pbuilder doesn't always set this up? More or less. With cowbuilder (which is how people normally use pbuilder), CHROOT/run is a regular directory and a copy of what was in the base.cow/tgz, but that doesn’t matter as it’s ⓐ fresh and ⓑ deconstructed after the build. CHROOT/run/shm gets bindmounted from the outside (used to be CHROOT/dev/shm until it broke). It’s not strictly necessary for throwaway chroots to actually have CHROOT/run a tmpfs, plus there are setup costs involved that are tricky to get right in a generic way (after mounting the tmpfs, you have permissions, files, subdirectories, etc. to take care of; normally, init scripts would do that), which is why I’d not object to this setup. what package sets up which directory. I think initscripts should either create a /dev/shm directory and all init systems and schroot/pbuilder etc. mount tmpfs there, or we stick to the weird debianism of /run/shm and then initscripts sets up /dev/shm b /run/shm ^ eh what? and schroot/pbuilder etc. mout a tmpfs there. I agree that we definitely fucked up bad (two releases after the fact, still!) and should decide on one thing and stick with that “period”. The release goal page mentions that /dev/shm is going to eventually go away so AIUI a tmpfs on the /run/shm directory (bindmounted by pbuilder) it is. If so, no changes to pbuilder are required currently. I think the other option is to agree that Debian fucked up, revert /run/shm, and do stable uploads to the same effect, so that chroot tools can continue to work the same independent of the distribution in the chroot. That would not so be welcome. Thanks for digging in deeper. I did not know that initscripts broke this setup (my apologies towards the systemd camp), and I wonder *why* there is a different setup for chroots vs. the main system in the first place? A system could just have the chroot setup, with early userspace mounting a tmpfs “over” it, so we have the same thing everywhere. Less code paths. bye, //mirabilos -- hecker cool ein Ada Lovelace Google-Doodle. aber zum 197. Geburtstag? Hätten die nicht noch 3 Jahre warten können? mirabilos bis dahin gibts google nicht mehr hecker ja, könnte man meinen. wahrscheinlich ist der angekündigte welt- untergang aus dem maya-kalender die globale abschaltung von google ☺ und darum müssen die die doodles vorher noch raushauen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773730: base: Broadcom card-reader BCM57765/BCM57785 not working
Hi T, I did try the ideas in [1] with similar results - i.e. the card is not automatically detected or mounted. Can you tell me how to check for tg3 module? Lastly, here is the dmesg output from boot with the SDHC card inserted. I ejected and reinserted the card at 466 but it did not create any messages. Cokes [0.00] CPU0 microcode updated early to revision 0x1b, date = 2014-05-29 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-16) ) #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=e62a123d-2aeb-45d4-a8e5-26db09151af1 ro acpi_backlight=vendor quiet [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009d7ff] usable [0.00] BIOS-e820: [mem 0x0009d800-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x1fff] usable [0.00] BIOS-e820: [mem 0x2000-0x201f] reserved [0.00] BIOS-e820: [mem 0x2020-0x40003fff] usable [0.00] BIOS-e820: [mem 0x40004000-0x40004fff] reserved [0.00] BIOS-e820: [mem 0x40005000-0xa6abefff] usable [0.00] BIOS-e820: [mem 0xa6abf000-0xa6ebefff] reserved [0.00] BIOS-e820: [mem 0xa6ebf000-0xa6fbefff] ACPI NVS [0.00] BIOS-e820: [mem 0xa6fbf000-0xa6ffefff] ACPI data [0.00] BIOS-e820: [mem 0xa6fff000-0xa6ff] usable [0.00] BIOS-e820: [mem 0xa700-0xaf9f] reserved [0.00] BIOS-e820: [mem 0xe000-0xefff] reserved [0.00] BIOS-e820: [mem 0xfeb0-0xfeb03fff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfed1-0xfed19fff] reserved [0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xffc8-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00014f5f] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.7 present. [0.00] DMI: Acer V5-131/Mimic , BIOS V1.09 10/30/2012 [0.00] e820: update [mem 0x-0x0fff] usable == reserved [0.00] e820: remove [mem 0x000a-0x000f] usable [0.00] AGP: No AGP bridge found [0.00] e820: last_pfn = 0x14f600 max_arch_pfn = 0x4 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-E7FFF write-protect [0.00] E8000-E write-combining [0.00] F-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 0 mask F8000 write-back [0.00] 1 base 08000 mask FC000 write-back [0.00] 2 base 0A700 mask FFF00 uncachable [0.00] 3 base 0A800 mask FF800 uncachable [0.00] 4 base 0B000 mask FF000 uncachable [0.00] 5 base 0FFC0 mask FFFC0 write-protect [0.00] 6 base 1 mask FC000 write-back [0.00] 7 base 14000 mask FF000 write-back [0.00] 8 base 14F60 mask FFFE0 uncachable [0.00] 9 base 14F80 mask FFF80 uncachable [0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [0.00] e820: last_pfn = 0xa7000 max_arch_pfn = 0x4 [0.00] found SMP MP-table at [mem 0x000fe1b0-0x000fe1bf] mapped at [880fe1b0] [0.00] Base memory trampoline at [88097000] 97000 size 24576 [0.00] init_memory_mapping: [mem 0x-0x000f] [0.00] [mem 0x-0x000f] page 4k [0.00] BRK [0x01af2000, 0x01af2fff] PGTABLE [0.00] BRK [0x01af3000, 0x01af3fff] PGTABLE [0.00] BRK [0x01af4000, 0x01af4fff] PGTABLE [0.00] init_memory_mapping: [mem 0x14f40-0x14f5f] [0.00] [mem 0x14f40-0x14f5f] page 2M [0.00] BRK [0x01af5000, 0x01af5fff] PGTABLE [0.00] init_memory_mapping: [mem 0x14c00-0x14f3f] [0.00] [mem 0x14c00-0x14f3f] page 2M [0.00] init_memory_mapping: [mem 0x1-0x14bff] [0.00] [mem 0x1-0x14bff] page 2M [0.00] BRK [0x01af6000, 0x01af6fff] PGTABLE [0.00] init_memory_mapping: [mem
Bug#773778: libverto-libev1: set_flags implementation broken
This looks simple and I'll put together a request. My understanding is that unless we call this RC because it totally breaks libkrad, that I need to file for a pre-approved change, and that such a change must be approved by Jan 5. I should be able to put together the unblock by Monday or so. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660298: Progress
Hello, Any progress with this? Maybe there is walk-around/alternative to get/convert Debian Reference as pdf/epub? Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773873: libidna-punycode-perl: dead code - replaced by liburi-perl
Hi Jonas, Jonas Smedegaard wrote: Package: libidna-punycode-perl Severity: normal IDNA::Punycode has disappeared from CPAN. URI mentions its URI::_punycode being based on IDNA::Punycode. Indeed, I recently used URI::_punycode when I needed some punycode stuff -- and was happy that it's in such a common module/package. I though wondered and still wonder about that strange module name. The underscore often means internal. Anyone knows more? The POD doesn't help with that question. No packages depend on libidna-punycode-perl - candidate for removal? Popcon shows about 35-45 installations with around 5 activity votes. IMHO that are too many installations for a removal without RC bug, but likely a removal candidate if it catches a non-trivial RC bug in the future. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773778: libverto-libev1: set_flags implementation broken
]] Sam Hartman This looks simple and I'll put together a request. My understanding is that unless we call this RC because it totally breaks libkrad, that I need to file for a pre-approved change, and that such a change must be approved by Jan 5. I've not been able to make my KDC do RADIUS at all without it, so I'd argue for it being RC, but that's up to you/the release team. I should be able to put together the unblock by Monday or so. Thanks, much appreciated. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760926: libapache-poi-java: ftbfs with OpenJDK 8
It seems the Icedtea folks have found the same issue. Maybe their fix is helpful to solve the issue in the Debian build. http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=1393 Cheers Tobias Wich signature.asc Description: This is a digitally signed message part.
Bug#771667: libapparmor1: Please move to /lib
Control: tag -1 + pending Hi, Martin Pitt wrote (02 Dec 2014 06:30:37 GMT) : Martin Pitt [2014-12-02 7:26 +0100]: Debdiff attached. Thanks a lot for the patch! I've applied it locally, and plan to upload to experimental shortly. 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#773763: task-mate-desktop: Should install libreoffice-gnome
Hello, Jean-Philippe MENGUAL, le Tue 23 Dec 2014 01:06:20 +0100, a écrit : * What was the outcome of this action? LibreOffice was announced inaccessible by Orca. The solution: add libreoffice-gnome to the automatically installed packages with task-mate-desktop. A quick measurement from a fresh MATE installation gives only 4MiB additional installed size. This would probably need to be added to other desktop tasks too: task-lxde-desktop, task-xfce-desktop, task-cinnamon-desktop, task-mate-desktop (but not task-kde-desktop, since the KDE desktop is not accessible with Orca yet). Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764493: python-eventlet 0.15.2-1 to Sid/Jessie
Hi, On Fri, Nov 14, 2014 at 11:12:22PM -0500, Scott Kitterman wrote: On Wed, 15 Oct 2014 18:24:06 +0200 =?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?= g...@debian.org wrote: Hi, Thomas packaged v0.15.2 and uploaded to experimental. In my opinion it should be uploaded to Sid and let migrate to Jessie. ... Now that we are in Freeze, this is pretty unlikely. Any objection to just uploading the Ubuntu patch so we can close the RC bug? This looks like the obvious way to go. Laszlo, what do you think? Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773882: ssh_exchange_identification: read: Connection reset by peer
Package: xinetd
Version: 1:2.3.15-3
Severity: normal
Dear Maintainer,
I have been running sshd from xinetd with
service ssh
{
disable = no
socket_type = stream
wait= no
user= root
server = /usr/sbin/sshd
protocol= tcp
log_on_failure += USERID
only_from = 192.168.0.0/29 192.168.10.0/29
}
without problems for some years. This has recently stopped working: if a
(only_from) client tries to connect, something like this happens:
$ ssh -vX ael@conquest2
OpenSSH_6.7p1 Debian-3, OpenSSL 1.0.1j 15 Oct 2014
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to conquest2 [192.168.0.2] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /home/ael/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ael/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ael/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ael/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ael/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ael/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ael/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ael/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.7p1 Debian-3
ssh_exchange_identification: read: Connection reset by peer
Removing sshd from xinetd and running it standalone on this same machine
with no other changes solves the problem.
-- System Information:
Debian Release: 8.0
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages xinetd depends on:
ii libc6 2.19-13
ii libwrap0 7.6.q-25
ii netbase 5.3
ii update-inetd 4.43
Versions of packages xinetd recommends:
ii logrotate3.8.7-1+b1
ii rsyslog [system-log-daemon] 8.4.2-1
xinetd suggests no packages.
-- Configuration Files:
/etc/default/xinetd changed:
INETD_COMPAT=No
XINETD_OPTS=-stayalive
-- 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#773883: unblock: fontypython/0.4.4-1.3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package fontypython 0.4.4-1.3 solves the grave bug #773579 (formally, but in fact bugs #757886 and #757886, which had never really been fixed). Moreover, the one-liner 0001-Do-not-crash-on-empty-pogs-list.patch solves another grave bug (fontypython would crash if it had never been ran successfully in the past - and yes, this is unfortunately a recursive definition). Attached is the debdiff since 0.4.4-1.1 (notice that 0.4.4-1.2 only introduced a patch, which was deleted in 0.4.4-1.3). Thanks, Pietro unblock fontypython/0.4.4-1.3 -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) diff -Nru fontypython-0.4.4/debian/changelog fontypython-0.4.4/debian/changelog --- fontypython-0.4.4/debian/changelog 2014-09-04 02:18:51.0 +0200 +++ fontypython-0.4.4/debian/changelog 2014-12-24 17:27:13.0 +0100 @@ -1,3 +1,19 @@ +fontypython (0.4.4-1.3) unstable; urgency=medium + + * Non-maintainer upload. + * Removed flawed patch (wx 2.8 is not in jessie) + * Patch: do not crash on empty pogs list + * Patches for compatibility with wxpython 3.0 (Closes: #773579) + + -- Pietro Battiston m...@pietrobattiston.it Sun, 21 Dec 2014 22:54:02 +0100 + +fontypython (0.4.4-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Patch: select wx 2.8 (rather than 3.0) (Closes: #765487) + + -- Pietro Battiston m...@pietrobattiston.it Sun, 14 Dec 2014 09:39:51 +0100 + fontypython (0.4.4-1.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru fontypython-0.4.4/debian/patches/0001-Do-not-crash-on-empty-pogs-list.patch fontypython-0.4.4/debian/patches/0001-Do-not-crash-on-empty-pogs-list.patch --- fontypython-0.4.4/debian/patches/0001-Do-not-crash-on-empty-pogs-list.patch 1970-01-01 01:00:00.0 +0100 +++ fontypython-0.4.4/debian/patches/0001-Do-not-crash-on-empty-pogs-list.patch 2014-12-24 17:29:21.0 +0100 @@ -0,0 +1,21 @@ +From: Pietro Battiston m...@pietrobattiston.it +Date: Sun, 21 Dec 2014 11:50:28 +0100 +Subject: Do not crash on empty pogs list + +--- + fontypythonmodules/gui_PogChooser.py | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/fontypythonmodules/gui_PogChooser.py b/fontypythonmodules/gui_PogChooser.py +index 94b7f2e..f233529 100644 +--- a/fontypythonmodules/gui_PogChooser.py b/fontypythonmodules/gui_PogChooser.py +@@ -80,7 +80,7 @@ class PogChooser(wx.ListCtrl) : + i = self.FindItem(-1, select) + self.indexselected = i # Set this to help initial icon settings. + self.Select(i, True) +- else: ++ elif self.__poglistCopy: + self.Select(0, False) + self.indexselected = -1 + diff -Nru fontypython-0.4.4/debian/patches/0002-Removed-unused-code-which-causes-crash-with-wx-3.0.patch fontypython-0.4.4/debian/patches/0002-Removed-unused-code-which-causes-crash-with-wx-3.0.patch --- fontypython-0.4.4/debian/patches/0002-Removed-unused-code-which-causes-crash-with-wx-3.0.patch 1970-01-01 01:00:00.0 +0100 +++ fontypython-0.4.4/debian/patches/0002-Removed-unused-code-which-causes-crash-with-wx-3.0.patch 2014-12-24 17:29:21.0 +0100 @@ -0,0 +1,134 @@ +From: Pietro Battiston m...@pietrobattiston.it +Date: Sun, 21 Dec 2014 09:14:19 +0100 +Subject: Removed unused code which causes crash with wx 3.0 + +--- + fontypython| 2 -- + fontypythonmodules/dialogues.py| 4 + fontypythonmodules/gui_Left.py | 4 + fontypythonmodules/gui_Middle.py | 5 - + fontypythonmodules/gui_PogChooser.py | 4 + fontypythonmodules/gui_Right.py| 4 + fontypythonmodules/gui_ScrolledFontView.py | 4 + fontypythonmodules/wxgui.py| 4 + 8 files changed, 31 deletions(-) + +diff --git a/fontypython b/fontypython +index a05290f..e46e34e 100755 +--- a/fontypython b/fontypython +@@ -72,8 +72,6 @@ else: # err code -11 + + ## Setup wxPython to access translations : enables the stock buttons. + localedir = fontypythonmodules/locales +- langid = wx.LANGUAGE_DEFAULT +- mylocale = wx.Locale( langid ) + + iPC = PC.PathControl() + +diff --git a/fontypythonmodules/dialogues.py b/fontypythonmodules/dialogues.py +index 1fbff5f..eba7ab3 100644 +--- a/fontypythonmodules/dialogues.py b/fontypythonmodules/dialogues.py +@@ -23,10 +23,6 @@ import wx + import wx.html as html + + +-## Setup wxPython to access translations : enables the stock buttons. +-langid = wx.LANGUAGE_DEFAULT # Picks this up from $LANG +-mylocale = wx.Locale( langid ) +- + ## langcode = locale.getlocale()[0] # I must not use getlocale... + ## This is suggested by Martin: + loc = locale.setlocale(locale.LC_CTYPE) # use *one* of the categories (not LC_ALL) +diff --git
Bug#689146: gcstar: Import Scanner plugin fails due to unblessed reference
Package: gcstar Version: 1.7.0-1 Followup-For: Bug #689146 Apologies for the delay in replying. The unblessed reference is still present. The steps that I used, with results, are as follows. Run gcstar from the command line. The following warning message appears, along with the gcstar window: Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. at /usr/lib/x86_64-linux- gnu/perl5/5.20/Gtk2.pm line 126. (I do not think this is relevant to the bug in question, though). Next, as there is currently no collection saved, I created a new collection of type Music collection, and pressed Okay. I went to the File menu, and selected Import and Barcode scanner. The relevant dialog box appeared. The Site to be used setting is disabled, and greyed out. I set the Scanner type to Network, and selected Add to current collection. Everything else was left as default. Finally, I pressed Import, at which point, the following was printed out on the terminal that I had started it from: *** unhandled exception in callback: *** Can't call method getEanField on unblessed reference at /usr/bin/../share/gcstar/lib/GCImport/GCImportScanner.pm line 292. *** ignoring at /usr/bin/gcstar line 328. Nothing appears to change within the gcstar UI. Pressing either Import or Cancel does nothing obvious. Pressing the Escape key does dismiss the dialog box. However, the cursor icon is changed to a spinning icon (which to me says that it is still trying to do something). At this point, I can now use the menus again etc. - creating a new album entry works, for example. If I then try to get back into the Import dialog again, no dialog appears, although a small rectangular object appears (about big enough for one character), and the folllowing GTK error is displayed: Gtk-CRITICAL **: IA__gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed at /usr/bin/../share/gcstar/lib/GCExportImport.pm line 116. This can only be cleared by pressing Escape, leaving the system in the same situation as before. If I start again, and use the Books collection type, things behave slightly differently. This time the import dialog does not have the Site to be used setting disabled. Setting this to something useful for me (such as ISBNdb), and pressing Import, brings up another Waiting dialog. This then allows an item to be scanned successfully (assuming that there is something set up correctly to scan in from). However, if while at the Waiting dialog, the Done button is pressed with nothing scanned, then the following different unhandled exception is called: *** unhandled exception in callback: *** Can't call method close on an undefined value at /usr/bin/../share/gcstar/lib/GCImport/GCImportScanner.pm line 169. *** ignoring at /usr/bin/gcstar line 328. (I hadn't previously noticed this, but spotted it while I was checking the existing bug out.) At this point, as before, the Import and Cancel buttons do nothing, and the only way to get past this is to hit Escape. If there is any more information required, please let me know, and I will attempt to obtain it. Regards, Alan -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gcstar depends on: ii fonts-liberation1.07.4-1 ii libarchive-zip-perl 1.39-1 ii libgtk2-perl2:1.2492-3 ii libmp3-tag-perl 1.13-1 ii libogg-vorbis-header-pureperl-perl 1.0-3 ii libwww-perl 6.08-1 ii libxml-parser-perl 2.41-3 ii libxml-simple-perl 2.20-1 ii perl5.20.1-3 ii perl-modules [libarchive-tar-perl] 5.20.1-3 Versions of packages gcstar recommends: ii libdatetime-format-strptime-perl 1.5600-1 ii libgtk2-spell-perl1.04-2+b1 ii libmp3-info-perl 1.24-1 ii libnet-freedb-perl0.08-4+b1 gcstar 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#773873: libidna-punycode-perl: dead code - replaced by liburi-perl
Hi Axel, Quoting Axel Beckert (2014-12-24 16:58:38) Jonas Smedegaard wrote: Package: libidna-punycode-perl Severity: normal IDNA::Punycode has disappeared from CPAN. URI mentions its URI::_punycode being based on IDNA::Punycode. Indeed, I recently used URI::_punycode when I needed some punycode stuff -- and was happy that it's in such a common module/package. I though wondered and still wonder about that strange module name. The underscore often means internal. Anyone knows more? The POD doesn't help with that question. I wondered the same, and digged deeper: _punycode is used by _idna which in turn is used by ihost and as_iri: perl -MURI -E 'say URI-new(http://xn--99zt52a.example.org/%E2%80%AE;)-as_iri' I now updated https://github.com/miyagawa/URI-Find-UTF8/issues/2 reflecting that new discovery :-) No packages depend on libidna-punycode-perl - candidate for removal? Popcon shows about 35-45 installations with around 5 activity votes. IMHO that are too many installations for a removal without RC bug, but likely a removal candidate if it catches a non-trivial RC bug in the future. Fair enough - but I do believe it effectively means we take over as upstream, and should then adapt packaging to reflect that - not repackage as dpkg source format 3.0 (native), but have Homepage, watch file and debian/copyright source URLs point to our resources at Alioth. It must've happened before among our thousands of packages - do we have formalized some procedures for which actions we should remember to take, and how we then monitor its health? Do we e.g. push to CPAN and monitor tkwalitee and cpantesters.org, also against Windows and Mac? As a minimum, I guess it makes sense to keep this bug open, and 45 hits on popcon is not enough for me to volunteer as new upstream for code I see no need for, even if bugfree... - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#773833:
The submitted build.log says:
dd: failed to open ‘chroot/usr/lib/syslinux/mbr.bin’: No such file or directory
This is because the syslinux version in jessie expects mbr.bin to be found in:
/usr/lib/SYSLINUX/mbr.bin
(see https://packages.debian.org/jessie/i386/syslinux/filelist)
As you can see the difference is in the syslinux/SYSLINUX capital letters.
I have run a test with live-build 4.0.4-1 in sid using your same
config ($ lb config --binary-images hdd). I have edited
/usr/lib/live/build/binary_hdd and substituted:
dd if=chroot/usr/lib/${_BOOTLOADER}/mbr.bin of=${FREELO} bs=440 count=1
with:
dd if=chroot/usr/lib/SYSLINUX/mbr.bin of=${FREELO} bs=440 count=1
(since the case ${LB_BUILD_WITH_CHROOT} is true by default)
and it produced a working hdd image. Be warned that the resulting
image does not have any extension such as .img because it is renamed
as follows:
mv chroot/binary.img ${LIVE_IMAGE_NAME}-${LB_ARCHITECTURES}
In my case it was called: live-image-i386
I know this is not a fix in any way, just a test. But I hope this
information is useful.
Have a Merry Christmas!
--
chals
www.chalsattack.com
ch...@chalsattack.com
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773457: ministat: man page: '-w' description is incomplete
Kristof Provost reported (see below) that ministat(1) doesn't correctly document the default width. I suggest the following patch to correct this. --- a/ministat.1 +++ b/ministat.1 @@ -65,7 +65,9 @@ See .Xr strtok 3 for details. .It Fl w Ar width -Width of ASCII-art plot in characters, default is 74. +Width of ASCII-art plot in characters. +The default is the terminal width, or 74 if standard output is not a +terminal. .El .Pp A sample output could look like this: --- END --- Ben. On Thu, 2014-12-18 at 16:57 +0100, Kristof Provost wrote: Package: ministat Version: 20100628-1 Severity: minor The man page states that: '-w widthWidth of ASCII-art plot in characters, default is 74.' This is not entirely correct. The mini-help is more accurate: '-w : width of graph/test output (default 74 or terminal width)' In other words: the man page fails to explain that ministat will default to the terminal width, not 74. It will only fall back to 74 if 'COLUMNS' is not set and ioctl(TIOCGWINSZ) fails. -- Ben Hutchings If more than one person is responsible for a bug, no one is at fault. signature.asc Description: This is a digitally signed message part
Bug#773873: libidna-punycode-perl: dead code - replaced by liburi-perl
Hi, Jonas Smedegaard wrote: No packages depend on libidna-punycode-perl - candidate for removal? Popcon shows about 35-45 installations with around 5 activity votes. IMHO that are too many installations for a removal without RC bug, but likely a removal candidate if it catches a non-trivial RC bug in the future. Fair enough - but I do believe it effectively means we take over as upstream, and should then adapt packaging to reflect that - not repackage as dpkg source format 3.0 (native), but have Homepage, watch file and debian/copyright source URLs point to our resources at Alioth. I disagree. As long as there's no major issue for the package in Sid... It must've happened before among our thousands of packages - do we have formalized some procedures for which actions we should remember to take, and how we then monitor its health? Do we e.g. push to CPAN and monitor tkwalitee and cpantesters.org, also against Windows and Mac? I think that's all totally overkill. As a minimum, I guess it makes sense to keep this bug open, Yes. I though would lower the severity to minor. and 45 hits on popcon is not enough for me to volunteer as new upstream for code I see no need for, And I see no need for that effort. even if bugfree... For me, that makes quite some difference. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773873: libidna-punycode-perl: dead code - replaced by liburi-perl
Quoting Axel Beckert (2014-12-24 18:25:12) Jonas Smedegaard wrote: No packages depend on libidna-punycode-perl - candidate for removal? Popcon shows about 35-45 installations with around 5 activity votes. IMHO that are too many installations for a removal without RC bug, but likely a removal candidate if it catches a non-trivial RC bug in the future. Fair enough - but I do believe it effectively means we take over as upstream, and should then adapt packaging to reflect that - not repackage as dpkg source format 3.0 (native), but have Homepage, watch file and debian/copyright source URLs point to our resources at Alioth. I disagree. As long as there's no major issue for the package in Sid... Which parts do you disagree with? Do you disagree that code is dead upstream, and perhaps believe it is simply some temporary hickup causing the code to not appear at CPAN? If you agree that code is dead upstream, but disagree that we have taken over? Or only *how* we should take over? As a minimum, I guess it makes sense to keep this bug open, Yes. I though would lower the severity to minor. Bug title needs adjusting too - to reflect whatever it is this bug really means. I think we can agree at least to strip last part: Interface of URI is not identical, even if it covers all of its functionality. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#705647: mailavenger: Missing SASL support and macutil
Package: mailavenger Version: 0.8.3rc1-1 Followup-For: Bug #705647 Hi Dererk, I installed this package a couple of days before the freeze. Ata ny other time I'd have just done a delayed NMU with this bug fixed, since you seem to be OK with fixing it, but have obviously overlooked it. I think it's a bit of a shame that you didn't bother to mention in the README that you'd stripped out the macutil stuff, especially since you've left the man pages untouched, so that avenger(1) has a SEE ALSO that refers to macutil(1) which then (after searching around for some time) turns out to not exist in Debian -- which strike one as a bit odd. I must say that when I eventually found the: don't really need MAC stuff in our free world =) comment, I wasn't greatly pleased. BTW is there something non-free about the macutil? I fail to see what. Anyway, since then I set things up without using macutil to protect my bounces, and find that my fake bounce problem has almost completely disapeared due to SPF, so I'm much less vexed about the lack of macutil now, and the time wasted on looking for it has almost certianly been more than compensated for with the time not spent setting it up :-) Perhaps you could at least ddocument it in the next upload? I think you should just remove your patch though (as you seemed to intend originally). Cheers, Phil. -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/3 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mailavenger depends on: ii adduser 3.113+nmu3 ii libc6 2.13-38+deb7u6 ii libdb5.15.1.29-5 ii libgcc1 1:4.7.2-5 ii libpcap0.8 1.3.0-1 ii libssl1.0.0 1.0.1e-2+deb7u13 ii libstdc++6 4.7.2-5 ii lsb-base4.1+Debian8+deb7u1 ii postfix [mail-transport-agent] 2.9.6-2 mailavenger recommends no packages. mailavenger suggests no packages. -- Configuration Files: /etc/avenger/asmtpd.conf changed [not included] /etc/avenger/unknown changed [not included] /etc/default/mailavenger 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#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC
Sorry for e-mailing on this old bug, but it seemed like the right thing to do, to attach the information about where to go next. Do you know where I could follow the development work (or lack thereof) on the upstream Mesa r300 big endian problem, to check the status, or to contribute to a solution? Is there a specific defect number? Sorry I just don't know where this work is being done. Any information you can provide to point me in the right direction would be helpful. Thanks very much. On Tue, 9/23/14, Michel Dänzer mic...@daenzer.net wrote: Subject: Re: Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC To: Bill Chatfield bill_chatfi...@yahoo.com Cc: 762...@bugs.debian.org Date: Tuesday, September 23, 2014, 9:17 PM On 23.09.2014 00:25, Bill Chatfield wrote: If I understand this correctly, then one of the defects in this situation is that the old radeonfb, nouveaufb, etc fb device drivers are still being compiled into the kernel. This shouldn't happen if they're not really supported by the rest of the system. I could file a bug in that regard, if that is the right thing to do. There is a file that attempts to blacklist all the old cardnamefb drivers, but since they are not loadable modules, this fails. You'd have to discuss that with the kernel package maintainers. I have determined that the reason why gdm and gnome will not run is because they require an accelerated driver, which radeonfb does not support. So I either have to use radeonfb with xfce or get the radeon/drm to work so I can run gnome. Unfortunately, the upsream Mesa r300 driver currently doesn't work correctly on big endian hosts. That would need to be fixed before you can run gnome-shell. So I'm afraid there's no obvious 'right thing to do', it's more a 'pick your poison' kind of situation. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773884: qtxmlpatterns-opensource-src: FTBFS on arm64
Package: qtxmlpatterns-opensource-src
Version: 5.4.0-1
Severity: important
Tags: patch
User: debian-...@lists.debian.org
Usertag: arm64
This package seems to have a problem building on arm64.
It has failed twice on the autobuilders, although not with exactly the same
issue:
It built OK on a porterbox, according to
https://lists.debian.org/debian-wb-team/2014/12/msg00010.html
The previous version built OK.
Do the failures below give any clues as to might be wrong? They seem
similar but not identical. Is there parallelism in this build making
it less obvious which test is actually at fault?
Clues about what this is testing and how to re-run just the tests
manually would be helpful to see if this can be reproduced at all.
Build:https://buildd.debian.org/status/fetch.php?pkg=qtxmlpatterns-opensource-srcarchhttps://buildd.debian.org/status/fetch.php?pkg=qtxmlpatterns-opensource-srcarch=arm64ver=5.4.0-1stamp=1418732066
make[4]: Leaving directory '/«PKGBUILDDIR»/tests/auto'
PASS :
tst_CheckXMLFiles::checkXMLFiles(/«PKGBUILDDIR»/tests/auto/xmlpatternsschemats/Baseline.xml)
PASS :
tst_CheckXMLFiles::checkXMLFiles(/«PKGBUILDDIR»/tests/auto/xmlpatternssdk/docs/XMLIndenterExampleResult.xml)
PASS :
tst_CheckXMLFiles::checkXMLFiles(/«PKGBUILDDIR»/tests/auto/xmlpatternssdk/docs/XMLWriterExampleResult.xml)
Error XSDError in Unknown location, at line 1, column 0: Premature end of
document.
PASS : tst_QXmlSchema::loadSchemaUrlFail()
PASS : tst_QXmlSchemaValidator::loadInstanceUrlFail()
PASS : tst_QXmlSchema::loadSchemaDeviceSuccess()
QWARN : tst_QXmlSchema::loadSchemaDeviceFail() The device must be readable.
PASS : tst_QXmlSchema::loadSchemaDeviceFail()
PASS : tst_QXmlSchemaValidator::loadInstanceDeviceSuccess()
PASS : tst_QXmlSchema::loadSchemaDataSuccess()
QWARN : tst_QXmlSchemaValidator::loadInstanceDeviceFail() The device must be
readable.
PASS : tst_QXmlSchemaValidator::loadInstanceDeviceFail()
terminate called after throwing an instance of 'bool'
PASS : tst_QXmlSchemaValidator::loadInstanceDataSuccess()
Aborted
make[4]: *** [check] Error 134
Makefile:268: recipe for target 'check' failed
make[4]: Leaving directory '/«PKGBUILDDIR»/tests/auto/qxmlschema
=arm64ver=5.4.0-1stamp=1419353311
make[4]: Entering directory '/«PKGBUILDDIR»/tests/auto/qxmlschema'
QT_PLUGIN_PATH=/usr/lib/aarch64-linux-gnu/qt5/plugins
LD_LIBRARY_PATH=/«PKGBUILDDIR»/lib:/usr/lib/aarch64-linux-gnu${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}
./tst_qxmlschema
* Start testing of tst_QXmlSchema *
Config: Using QtTest library 5.4.0, Qt 5.4.0 (arm64-little_endian-lp64 shared
(dynamic) release build; by GCC 4.9.1)
PASS : tst_QXmlSchema::initTestCase()
PASS : tst_QXmlSchema::defaultConstructor()
PASS : tst_QXmlSchema::copyConstructor()
PASS : tst_QXmlSchema::constructorQXmlNamePool()
PASS : tst_QXmlSchema::copyMutationTest()
PASS : tst_QXmlSchema::isValid()
PASS : tst_QXmlSchema::documentUri()
PASS : tst_QXmlSchema::loadSchemaUrlSuccess()
PASS : tst_QXmlSchema::loadSchemaUrlFail()
PASS : tst_QXmlSchema::loadSchemaDeviceSuccess()
QWARN : tst_QXmlSchema::loadSchemaDeviceFail() The device must be readable.
PASS : tst_QXmlSchema::loadSchemaDeviceFail()
PASS : tst_QXmlSchema::loadSchemaDataSuccess()
Error XSDError in Unknown location, at line 1, column 0: Premature end of
document.
terminate called after throwing an instance of 'bool'
Aborted
Makefile:268: recipe for target 'check' failed
make[4]: *** [check] Error 134
make[4]: Leaving directory '/«PKGBUILDDIR»/tests/auto/qxmlschema'
-- System Information:
Debian Release: 7.7
APT prefers stable
APT policy: (990, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.60-kvm-i386-20140609 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765406: ping?
Any chance this can get fixed before the release? -- Eric Dorland e...@kuroneko.ca 43CF 1228 F726 FD5B 474C E962 C256 FBD5 0022 1E93 signature.asc Description: Digital signature
Bug#773885: dosfsck: segmentation fault
Package: dosfstools Version: 3.0.27-1 Usertags: afl dosfsck crashes when checking the attached filesystem: $ /sbin/dosfsck -n crash.vfat [SNIP - lots of errors] Directory has non-zero size. Fixing it. Segmentation fault This bug was found using American fuzzy lop: https://packages.debian.org/experimental/afl -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages dosfstools depends on: ii libc6 2.19-13 -- Jakub Wilk crash.vfat.gz Description: application/gzip
Bug#773886: initramfs-growroot grows wrong partition
Package: cloud-initramfs-growroot Version: 0.18.debian5~bpo70+1 When installed debian with LVM, using whole disk (default option), the LVM was created on /dev/vda5, which was on vda2 extended partition: Device BootStart End #sectors Id System /dev/vda1 * 2048499711 497664 83 Linux /dev/vda2501758 41943039 41441282 5 Extended /dev/vda3 0 - 0 0 Empty /dev/vda4 0 - 0 0 Empty /dev/vda5501760 41943039 41441280 8e Linux LVM when booted on bigger virtual disk, the primary partition 2 was changed to type linux, containing the rest of the disk, which unfortunately made the LVM unreadable. the growpart should aparently support extended partitions... -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Saving Private Ryan... Private Ryan exists. Overwrite? (Y/N) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773887: unblock: sox/14.4.1-5
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package sox
Version 14.4.1-5 addresses DSA-3112-1. A specially crafted wav file
could cause an application using SoX to crash or, possibly, execute ar
bitrary code.
Please see attached file for the debdiff against the package in testing.
Please,
unblock sox/14.4.1-5
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_CA.utf8, LC_CTYPE=fr_CA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
--
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
COMunité/LACIME: École de technologie supérieure (http://www.comunite.ca)
ISIP Laboratory: McGill (http://www.isip.ece.mcgill.ca)
diff -Nru sox-14.4.1/debian/changelog sox-14.4.1/debian/changelog
--- sox-14.4.1/debian/changelog 2014-05-21 22:09:53.0 -0400
+++ sox-14.4.1/debian/changelog 2014-12-24 14:40:04.0 -0500
@@ -1,3 +1,12 @@
+sox (14.4.1-5) unstable; urgency=medium
+
+ * Patches to fix memory corruptions on the heap, CVE-2014-8145
+(closes: #773720):
++ 0001-Check-for-minimum-size-sphere-headers.patch
++ 0002-More-checks-for-invalid-MS-ADPCM-blocks.patch
+
+ -- Pascal Giard pas...@debian.org Wed, 24 Dec 2014 14:33:55 -0500
+
sox (14.4.1-4) unstable; urgency=low
* [debian/rules,debian/control]:
diff -Nru
sox-14.4.1/debian/patches/0001-Check-for-minimum-size-sphere-headers.patch
sox-14.4.1/debian/patches/0001-Check-for-minimum-size-sphere-headers.patch
--- sox-14.4.1/debian/patches/0001-Check-for-minimum-size-sphere-headers.patch
1969-12-31 19:00:00.0 -0500
+++ sox-14.4.1/debian/patches/0001-Check-for-minimum-size-sphere-headers.patch
2014-12-24 14:32:59.0 -0500
@@ -0,0 +1,14 @@
+--- src/sphere.c.old
src/sphere.c
+@@ -47,6 +47,11 @@ static int start_read(sox_format_t * ft)
+
+ /* Determine header size, and allocate a buffer large enough to hold it. */
+ sscanf(fldsval, %lu, header_size_ul);
++ if (header_size_ul 16) {
++lsx_fail_errno(ft, SOX_EHDR, Error reading Sphere header);
++return (SOX_EOF);
++ }
++
+ buf = lsx_malloc(header_size = header_size_ul);
+
+ /* Skip what we have read so far */
diff -Nru
sox-14.4.1/debian/patches/0002-More-checks-for-invalid-MS-ADPCM-blocks.patch
sox-14.4.1/debian/patches/0002-More-checks-for-invalid-MS-ADPCM-blocks.patch
---
sox-14.4.1/debian/patches/0002-More-checks-for-invalid-MS-ADPCM-blocks.patch
1969-12-31 19:00:00.0 -0500
+++
sox-14.4.1/debian/patches/0002-More-checks-for-invalid-MS-ADPCM-blocks.patch
2014-12-24 14:32:59.0 -0500
@@ -0,0 +1,11 @@
+--- src/wav.c.old
src/wav.c
+@@ -166,7 +166,7 @@ static unsigned short AdpcmReadBlock(sox_format_t * ft)
+ /* work with partial blocks. Specs say it should be null */
+ /* padded but I guess this is better than trailing quiet. */
+ samplesThisBlock = lsx_ms_adpcm_samples_in((size_t)0,
(size_t)ft-signal.channels, bytesRead, (size_t)0);
+-if (samplesThisBlock == 0)
++if (samplesThisBlock == 0 || samplesThisBlock wav-samplesPerBlock)
+ {
+ lsx_warn(Premature EOF on .wav input file);
+ return 0;
Bug#773888: faenza-icon-theme: use debian icons instead of ubuntu ones for start-here icons
Package: faenza-icon-theme
Version: 1.3.1-1
Severity: wishlist
Hi,
the package contains start-here-distribution icons with symbols of
various distributions, including Debian. However start-here icons are
symlinks to icons with ubuntu symbols.
E.g.:
$ realpath /usr/share/icons/Faenza/places/22/start-here.png
/usr/share/icons/Faenza/places/22/start-here-ubuntu.png
My suggestion is to change these symlinks to point to icons with Debian
symbols.
The start-here icons are used e.g. on panels (Mate, Gnome, ...)
for applications menus.
FYI I did the following to fix this for myself:
dpkg -L faenza-icon-theme |grep 'start-here\.' |while read path; do
p=${path#/usr/share/icons/}; p=${p%/start-here*}; mkdir -p ~/.icons/${p};
cd ~/.icons/${p}; icpath=$(realpath $path); ext=${icpath##*.};
icpath=${icpath%-ubuntu*}-debian.${ext}; ln -s $icpath start-here.${ext}; done
dpkg -L faenza-icon-theme |grep 'start-here-symbolic\.' |while read path; do
p=${path#/usr/share/icons/}; p=${p%/start-here*}; mkdir -p ~/.icons/${p};
cd ~/.icons/${p}; icpath=$(realpath $path); ext=${icpath##*.};
icpath=${icpath%-ubuntu*}-debian.${ext}; ln -s $icpath
start-here-symbolic.${ext}; done
Thanks,
Martin
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (900, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-- 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#773889: jekyll: fails to start
Package: jekyll Version: 2.2.0+dfsg-2 Severity: important Dear Maintainer, shawn@www:~/blog$ jekyll serve -w Notice: for 10x faster LSI support, please install http://rb-gsl.rubyforge.org/ Configuration file: /home/shawn/blog/_config.yml Source: /home/shawn/blog Destination: /home/shawn/blog/_site Generating... done. /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- listen (LoadError) from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/vendor_ruby/jekyll/commands/watch.rb:24:in `watch' from /usr/lib/ruby/vendor_ruby/jekyll/commands/build.rb:62:in `watch' from /usr/lib/ruby/vendor_ruby/jekyll/commands/build.rb:35:in `process' from /usr/lib/ruby/vendor_ruby/jekyll/commands/serve.rb:24:in `block (2 levels) in init_with_program' from /usr/lib/ruby/vendor_ruby/mercenary/command.rb:220:in `call' from /usr/lib/ruby/vendor_ruby/mercenary/command.rb:220:in `block in execute' from /usr/lib/ruby/vendor_ruby/mercenary/command.rb:220:in `each' from /usr/lib/ruby/vendor_ruby/mercenary/command.rb:220:in `execute' from /usr/lib/ruby/vendor_ruby/mercenary/program.rb:35:in `go' from /usr/lib/ruby/vendor_ruby/mercenary.rb:22:in `program' from /usr/bin/jekyll:18:in `main' -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages jekyll depends on: ii ruby1:2.1.0.4 ii ruby-classifier 1.3.4-2 ii ruby-colorator 0.1-3 ii ruby-jekyll-coffeescript1.0.0-1 ii ruby-jekyll-gist1.1.0-1 ii ruby-jekyll-paginate1.0.0-1 ii ruby-jekyll-sass-converter 1.0.0-2 ii ruby-jekyll-watch 1.0.0-1 ii ruby-kramdown 1.4.2-1 ii ruby-liquid 2.6.1-2 ii ruby-mercenary 0.3.4-1 ii ruby-pygments.rb0.5.4~ds1-1.1 ii ruby-redcarpet 3.1.2-1 ii ruby-safe-yaml 1.0.3-1 ii ruby-toml 0.1.1-1 ii ruby2.1 [ruby-interpreter] 2.1.5-1 Versions of packages jekyll recommends: pn ruby-mysql none pn ruby-rouge none pn ruby-sequel none pn ruby-sequel-pg none jekyll 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#773890: flash-kernel: No entry for BeagleBone Black when running 3.18 kernel
Package: flash-kernel Version: 3.28 Severity: normal Tags: patch When running the 3.18 kernel from experimental on a BeagleBone Black, /proc/device-tree/model contains TI AM335x BeagleBone Black. With the 3.16 kernel from Jessie, it contains TI AM335x BeagleBone. The following patch adds an additional Machine entry for the more specific name. Not sure if there's a more elegant way to add an entry that's simply a duplicate of another entry with a different Machine id. commit 327811b97bf3c78d0411d64a5fd86975ec53aace Author: Vagrant Cascadian vagr...@debian.org Date: Wed Dec 24 12:32:47 2014 -0800 Add entry for BeagleBone Black, which has a distinct /proc/device-tree/model entry from BeagleBone (white) when running a newer kernel (3.18+). diff --git a/db/all.db b/db/all.db index a09d1fb..72ea33a 100644 --- a/db/all.db +++ b/db/all.db @@ -580,6 +580,13 @@ Boot-Script-Path: /boot/boot.scr U-Boot-Script-Name: bootscr.beaglebone Required-Packages: u-boot-tools +Machine: TI AM335x BeagleBone Black +Kernel-Flavors: armmp +DTB-Id: am335x-boneblack.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.beaglebone +Required-Packages: u-boot-tools + Machine: TI OMAP5 uEVM board Kernel-Flavors: armmp armmp-lpae DTB-Id: omap5-uevm.dtb Thanks! live well, vagrant signature.asc Description: PGP signature
Bug#773891: libreadline6: inputrc with some comments causes libreadline6 linked program(s) to segfault
Package: libreadline6 Version: 6.3-8+b2 Severity: normal Dear Maintainer, attached is an inputrc that causes bc to segfault when INPUTRC is set to its path. However, bc does not segfault when the comment on line 29 is removed (as in vi's dd command, for example). -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libreadline6 depends on: ii libc6 2.19-13 ii libtinfo5 5.9+20140913-1+b1 ii multiarch-support 2.19-13 ii readline-common6.3-8 libreadline6 recommends no packages. libreadline6 suggests no packages. -- no debconf information set bell-style none set completion-ignore-case off set convert-meta off set disable-completion off set expand-tilde on set horizontal-scroll-mode off set input-meta on set isearch-terminators \C-v set keymap emacs set mark-directories on set mark-symlinked-directories on set match-hidden-files off set output-meta on set print-completions-horizontally off # XXX ## set revert-all-at-newline off # Show choices immediately instead of ringing the bell (first) (cf. csh). set show-all-if-ambiguous on # XXX ## set show-all-if-unmodified off ## set skip-completed-text off ## set visible-stats off # … # [https://www.gnu.org/software/bash/manual/html_node/Readline-Init-File-Syntax.html] TAB: complete # → isearch-terminators # [https://www.gnu.org/software/bash/manual/html_node/Readline-Init-File-Syntax.html] # [https://www.gnu.org/software/bash/manual/html_node/Commands-For-History.html] Control-^: reverse-search-history ### XXX ## Control-o: aaa bbb ccc! ## M-o: xxx yyy
Bug#773892: fsck.minix: segmentation fault
Package: util-linux Version: 2.25.2-4 Usertags: afl fsck.minix crashes on the attached (corrupted) filesystem: $ /sbin/fsck.minix -a -f crash.minix Forcing filesystem check on crash.minix. /: bad directory: '..' isn't second /®.: bad directory: '..' isn't second /®./®.: bad directory: '..' isn't second /®./®./®.: bad directory: '..' isn't second [SNIP - more bad directory errors] Segmentation fault This bug was found using American fuzzy lop: https://packages.debian.org/experimental/afl -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages util-linux depends on: ii initscripts2.88dsf-58 ii libblkid1 2.25.2-4 ii libc6 2.19-13 ii libmount1 2.25.2-4 ii libncurses55.9+20140913-1+b1 ii libpam0g 1.1.8-3.1 ii libselinux12.3-2 ii libslang2 2.3.0-2 ii libsmartcols1 2.25.2-4 ii libtinfo5 5.9+20140913-1+b1 ii libuuid1 2.25.2-4 ii lsb-base 4.1+Debian13+nmu1 ii tzdata 2014j-1 ii zlib1g 1:1.2.8.dfsg-2+b1 -- Jakub Wilk crash.minix.gz Description: application/gzip
Bug#773795: fsck.ext2: memory corruption
On Tue, Dec 23, 2014 at 12:51:14PM +0100, Jakub Wilk wrote: Package: e2fsprogs Version: 1.42.12-1 Usertags: afl fsck.ext2 crashes when checking the attached filesystem: $ /sbin/fsck.ext2 -n crash.ext2 e2fsck 1.42.12 (29-Aug-2014) One or more block group descriptor checksums are invalid. Fix? no Group descriptor 0 checksum is 0xa634, should be 0x6639. IGNORED. Group descriptor 0 has invalid unused inodes count 21. Fix? no crash.ext2 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Signal (11) SIGSEGV si_code=SEGV_MAPERR fault addr=0x8663000 *** Error in `/sbin/fsck.ext2': malloc(): memory corruption: 0x086529e8 *** Aborted Thanks for the bug report! It should be noted the crash only happens when e2fsck is run with -n. If you run with the -fy options, the crash does *not* happen. This indicates that e2fsck made an assumption that a particular filesystem inconsistency *would* be fixed, but in the case where it was not fixed, it wasn't being sufficiently paranoid --- or, if the inconsistency is so fundamental that we can not proceed if the user refuses to fix it, we should abort the e2fsck run. This is still a bug, of course, and I tend to look into getting it fixed, but in my opinion a bug fix for this issue doesn't meet the freeze criteria[1]. This is especially true since e2fsprogs is part of the installer, and the release team is generally much more conservative about package uploads which require respinning (and retesting) the installer. [1] https://release.debian.org/jessie/freeze_policy.html Many thanks, - Ted Script started on Wed 24 Dec 2014 04:29:21 PM EST Top-level shell (parent script) Using ssh-agent pid 3105 % dpkg -l e2fsprogs Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-=-=-=== ii e2fsprogs 1.42.12-1 amd64 ext2/ext3/ext4 file system utilities % /bin/cp /tmp/crash.ext2 /tmp/foo.img % valgrind /sbin/e2fsck -fy /tmp/foo.img ==4870== Memcheck, a memory error detector ==4870== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==4870== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==4870== Command: /sbin/e2fsck -fy /tmp/foo.img ==4870== e2fsck 1.42.12 (29-Aug-2014) ==4870== Warning: noted but unhandled ioctl 0x4c05 with no size/direction hints. ==4870==This could cause spurious value errors to appear. ==4870==See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper. ==4870== Conditional jump or move depends on uninitialised value(s) ==4870==at 0x4E58801: check_loop_mounted (ismounted.c:67) ==4870==by 0x4E58801: check_mntent_file (ismounted.c:122) ==4870==by 0x4E58A57: check_mntent (ismounted.c:227) ==4870==by 0x4E58A57: ext2fs_check_mount_point (ismounted.c:360) ==4870==by 0x409812: check_mount (unix.c:228) ==4870==by 0x409812: main (unix.c:1242) ==4870== ==4870== Conditional jump or move depends on uninitialised value(s) ==4870==at 0x4E58801: check_loop_mounted (ismounted.c:67) ==4870==by 0x4E58801: check_mntent_file (ismounted.c:122) ==4870==by 0x4E58A7C: check_mntent (ismounted.c:236) ==4870==by 0x4E58A7C: ext2fs_check_mount_point (ismounted.c:360) ==4870==by 0x409812: check_mount (unix.c:228) ==4870==by 0x409812: main (unix.c:1242) ==4870== One or more block group descriptor checksums are invalid. Fix? yes Group descriptor 0 checksum is 0xa634, should be 0x6639. FIXED. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /tmp/foo.img: 11/16 files (0.0% non-contiguous), 21/64 blocks ==4870== ==4870== HEAP SUMMARY: ==4870== in use at exit: 0 bytes in 0 blocks ==4870== total heap usage: 442 allocs, 442 frees, 117,158 bytes allocated ==4870== ==4870== All heap blocks were freed -- no leaks are possible ==4870== ==4870== For counts of detected and suppressed errors, rerun with: -v ==4870== Use --track-origins=yes to see where uninitialised values come from ==4870== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) % cp /tmp/crash.ext2 /tmp/foo.img /bin/cp: overwrite ‘/tmp/foo.img’? y % valgrind /sbin/e2fsck -n /tmp/foo.img ==4884== Memcheck, a memory error detector ==4884== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==4884== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==4884== Command: /sbin/e2fsck -n /tmp/foo.img ==4884== e2fsck
Bug#660298: Progress
On Wed, Dec 24, 2014 at 05:54:33PM +0200, Vincas Dargis wrote: Any progress with this? Maybe there is walk-around/alternative to get/convert Debian Reference as pdf/epub? We are under freeze. No structual change at this moment. PDF: Not possible as far as I know. If you know how to get some table etc., maybe. EPUB: You can call me lazy. Patch welcome. Osamu PS: I am not too keen on working the PDF by myself at this moment. It requires significant efforts. Please do not underestimate it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773893: bacula-director-sqlite3: Bacula update to 5.2 - update script of sqlite did not update DB table RestoreObject properly
Package: bacula-director-sqlite3
Version: 5.2.6+dfsg-9
Severity: normal
Dear Maintainer,
When upgrading to bacula 5.2.6 the sqlite database version changes from 12 to
14. Bacula director does not start, when starting with debug option manually:
/usr/sbin/bacula-dir -d 99 -c /etc/bacula/bacula-dir.conf
It gives the error
bacula-dir JobId 0: Fatal error: Version error for database bacula. Wanted
14, got 12
bacula-dir ERROR TERMINATION
Acording to some vague documentation the script provided here is supposed to
resolve this issue
/usr/share/bacula-director/update_sqlite3_tables
The package update and dpkg configure should include this script automatically.
However event if called manually there is still another issue. After completed
backup from a windows client we get:
24-дек 23:34 ratix-dir JobId 7405: Fatal error: sql_create.c:1219 Create db
Object record INSERT INTO RestoreObject
(ObjectName,PluginName,RestoreObject,ObjectLength,ObjectFullLength,ObjectIndex,ObjectType,ObjectCompression,FileIndex,JobId)
VALUES ('job_metadata.xml','job', .. OMITED.. ) failed. ERR=table
RestoreObject has no column named ObjectCompression
Looking closer at the script show that there is a typo in the create table
statement.
/usr/share/bacula-director/update_sqlite3_tables
CREATE TABLE RestoreObject (
RestoreObjectId INTEGER,
ObjectName TEXT DEFAULT '',
RestoreObject TEXT DEFAULT '',
PluginName TEXT DEFAULT '',
ObjectLength INTEGER DEFAULT 0,
ObjectFullLength INTEGER DEFAULT 0,
ObjectIndex INTEGER DEFAULT 0,
ObjectType INTEGER DEFAULT 0,
FileIndex INTEGER UNSIGNED DEFAULT 0,
ObejctCompression INTEGER DEFAULT 0,
JobId INTEGER UNSIGNED REFERENCES Job NOT NULL,
PRIMARY KEY(RestoreObjectId)
);
##
ObejctCompression should be ObjectCompression
-- System Information:
Debian Release: 7.6
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-486
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages bacula-director-sqlite3 depends on:
ii bacula-common 5.2.6+dfsg-9
ii bacula-common-sqlite3 5.2.6+dfsg-9
ii bacula-director-common 5.2.6+dfsg-9
ii dbconfig-common 1.8.47+nmu1
ii debconf [debconf-2.0] 1.5.49
ii file5.11-2+deb7u5
ii libc6 2.13-38+deb7u4
ii libcap2 1:2.22-1.2
ii libgcc1 1:4.7.2-5
ii libpython2.72.7.3-6+deb7u2
ii libssl1.0.0 1.0.1e-2+deb7u12
ii libstdc++6 4.7.2-5
ii libwrap07.6.q-24
ii sqlite3 3.7.13-1+deb7u1
ii ucf 3.0025+nmu3
ii zlib1g 1:1.2.7.dfsg-13
bacula-director-sqlite3 recommends no packages.
Versions of packages bacula-director-sqlite3 suggests:
pn gawk none
-- Configuration Files:
/etc/bacula/scripts/delete_catalog_backup changed [not included]
-- debconf information excluded
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#628454:
I am having this same problem on Debian jessie with kernel 3.16.0-4-686-pae. About 50% of the time when I turn on my computer, I get the message and my Bluetooth doesn't work. However, it doesn't happen every time. Sometimes my Bluetooth works perfectly for no reason at all.
Bug#770930: libav memory leak
Dear Multimedia Maintainers, This issue is a very nasty one and I would be grateful if you may consider applying the fix into jessie version. Do you have any plans regarding it? Regards, Mert On Tue, 25 Nov 2014 11:12:17 +0100 Moritz Fiedler deb...@znn.info wrote: Package: mpv Version: 0.6.2-2 Severity: important Hello, when you use mpv with bigger files it happens that mpv consumes all RAM and swap and the system gets unusable. The mpv team investigated the issue: https://github.com/mpv-player/mpv/issues/1204 It looks like there is a problem with libav. But there is a patch. I think there are two solutions: * compile with ffmpeg * patch libav I filed the bug here, because i only experience the problem with mpv. Thanks for maintaining mpv. Greetings Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773872: biber: hyphenation hints fail
On Wed, 24 Dec 2014, Dominik Brodowski wrote: corresponding patch (commit 732ebc5962850416178d4802a44583e3cd1b3740 upstream) could be backported to jessie? More information on this bug may be That is easy, already done in the git repo, but getting it into jessie at this time ... code changes ... I don't know. But I will try. Norbert PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773894: fuse: .
Package: fuse Version: 2.9.3-15+b1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages fuse depends on: ii adduser 3.113+nmu3 ii libc6 2.19-13 ii libfuse2 2.9.3-15+b1 ii mount 2.25.2-4 ii sed 4.2.2-4+b1 ii udev 215-8 fuse recommends no packages. fuse suggests no packages. -- Configuration Files: /etc/fuse.conf [Errno 13] Permission denied: u'/etc/fuse.conf' -- 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#773894: some info about 773894
I apologize for the fact that the following information that I entered at
reportbug was not included.
Michael Biebl suggests to me that the fact that the latest fuse package
creates /lib/modules-load.d/fuse.conf is a bug. I have
fuse_2.9.3-15+b1_amd64.deb and am running the Testing rolling release. He
suggests that this file was formerly needed in orderly to manually load the
fuse module but that it should now be loaded automatically.
Thanks for doing the hard work to maintain the package,
Alison Chaiken
--
Alison Chaiken ali...@she-devel.com
650-279-5600http://{she-devel.com,
exerciseforthereader.org}
Never underestimate the cleverness of advertisers, or mischief makers, or
criminals. -- Don Norman
Bug#773727: [debian-mysql] Bug#773727: mariadb-server-10.0: Mroonga TokuDB plugins missing
Hello,
AFAIK, mroonga also requires some CREATE FUNCTION (and of course to be
loaded either in MariaDB configuration or through INSTALL PLUGIN). I'm
not sure how other plugins do, but what is the general stance about such
things? Shall we do it automatically or leave it to the user?
I'm asking because I recently had to automatically install mroonga for a
customer. I have attached to this email a (very rough) patch to
automatically load the plugin and issue CREATE FUNCTION (if necessary of
course) on startup.
Cheers,
--
Arnaud Fontaine
--- a/debian/additions/debian-start
+++ b/debian/additions/debian-start
@@ -30,6 +30,7 @@ trap SIGHUP
upgrade_system_tables_if_necessary;
check_root_accounts;
check_for_crashed_tables;
+ upgrade_mroonga_if_necessary;
) 2
exit 0
--- a/debian/additions/debian-start.inc.sh
+++ b/debian/additions/debian-start.inc.sh
@@ -70,3 +70,30 @@ function check_root_accounts() {
logger -p daemon.warn -i -t$0 WARNING: mysql.user contains $ret root accounts without password!
fi
}
+
+function upgrade_mroonga_if_necessary() {
+ set -e
+ set -u
+
+ if [ -e /var/lib/mysql/upgraded-debian.flag ]; then
+logger -p daemon.info -i -t$0 Upgrading mroonga.
+
+# From storage/mroonga/data/install.sql.in
+echo -e \
+ DROP FUNCTION IF EXISTS last_insert_grn_id;\n \
+ CREATE FUNCTION last_insert_grn_id RETURNS INTEGER SONAME 'ha_mroonga.so';\n \
+ DROP FUNCTION IF EXISTS mroonga_snippet;\n \
+ CREATE FUNCTION mroonga_snippet RETURNS STRING SONAME 'ha_mroonga.so';\n \
+ DROP FUNCTION IF EXISTS mroonga_command;\n \
+ CREATE FUNCTION mroonga_command RETURNS STRING SONAME 'ha_mroonga.so';\n \
+ DROP FUNCTION IF EXISTS mroonga_escape;\n \
+ CREATE FUNCTION mroonga_escape RETURNS STRING SONAME 'ha_mroonga.so';\n | \
+ $MYSQL --skip-column-names
+
+if [ $? -ne 0 ]; then
+ logger -p daemon.warn -i -t$0 WARNING: Could not upgrade mroonga!
+else
+ rm -f /var/lib/mysql/upgraded-debian.flag
+fi
+ fi
+}
--- a/debian/additions/mariadb.cnf
+++ b/debian/additions/mariadb.cnf
@@ -15,3 +15,4 @@
#collation-server = utf8_general_ci
#character_set_server = utf8
#collation_server = utf8_general_ci
+plugin-load=Mroonga=ha_mroonga.so
--- a/debian/mariadb-server-10.0.postinst
+++ b/debian/mariadb-server-10.0.postinst
@@ -229,6 +229,8 @@ EOF
echo $replace_query| $MYSQL_BOOTSTRAP 21 | $ERR_LOGGER
echo $install_plugins | $MYSQL_BOOTSTRAP 21 | $ERR_LOGGER
set -e
+
+touch /var/lib/mysql/upgraded-debian.flag
;;
abort-upgrade|abort-remove|abort-configure)
Bug#773895: sysvinit: package to pin sysvinit during upgrades
package: src:sysvinit severity: important tags: patch Hi, In order to provide an option for users to control the init system outcome during an upgrade, I propose the attached update to src:sysvinit. This adds a new package, which the user can elect to install prior to their upgrade. It will prevent systemd installation and retain sysvinit. Please let me know if you have any feedback. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773895: sysvinit: package to pin sysvinit during upgrades
Proposed patch included this time.
diff -Nru sysvinit-2.88dsf/debian/block-systemd sysvinit-2.88dsf/debian/block-systemd
--- sysvinit-2.88dsf/debian/block-systemd 1970-01-01 00:00:00.0 +
+++ sysvinit-2.88dsf/debian/block-systemd 2014-12-25 03:47:23.0 +
@@ -0,0 +1,3 @@
+Package: systemd systemd-sysv libsystemd-daemon0 libsystemd-login0 libsystemd-journal0
+Pin: release o=Debian
+Pin-Priority: -1
diff -Nru sysvinit-2.88dsf/debian/changelog sysvinit-2.88dsf/debian/changelog
--- sysvinit-2.88dsf/debian/changelog 2014-11-11 19:34:28.0 +
+++ sysvinit-2.88dsf/debian/changelog 2014-12-25 04:10:49.0 +
@@ -1,3 +1,11 @@
+sysvinit (2.88dsf-58.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Provide a sysvinit-pin package, which can be used to retain sysvinit as
+the init system during an upgrade.
+
+ -- Michael Gilbert mgilb...@debian.org Thu, 25 Dec 2014 03:17:27 +
+
sysvinit (2.88dsf-58) unstable; urgency=low
* Fix typo in invoke-rc.d breaking upstart installations (Closes:
diff -Nru sysvinit-2.88dsf/debian/control sysvinit-2.88dsf/debian/control
--- sysvinit-2.88dsf/debian/control 2014-10-25 21:24:19.0 +
+++ sysvinit-2.88dsf/debian/control 2014-12-25 04:04:01.0 +
@@ -73,6 +73,16 @@
Specifically, this package includes:
killall5, last, lastb, mesg, pidof, service, sulogin
+Package: sysvinit-pin
+Priority: extra
+Architecture: all
+Depends: ${misc:Depends}, sysvinit-core
+Conflicts: systemd-sysv
+Description: Prevent systemd from becoming the init system, retain sysvinit
+ This package uses apt-pinning to prevent systemd from becoming the init
+ system during an upgrade. To work as expected, it should be the first new
+ package installed prior to upgrading the rest of the system.
+
Package: sysv-rc
Architecture: all
Multi-Arch: foreign
diff -Nru sysvinit-2.88dsf/debian/sysvinit-pin.install sysvinit-2.88dsf/debian/sysvinit-pin.install
--- sysvinit-2.88dsf/debian/sysvinit-pin.install 1970-01-01 00:00:00.0 +
+++ sysvinit-2.88dsf/debian/sysvinit-pin.install 2014-12-25 03:43:52.0 +
@@ -0,0 +1 @@
+debian/block-systemd etc/apt/preferences.d
Bug#773775: Fix and improve progress-linux archive key installation
Small mistake: Somehow in mulling over the possibility of also adding gpg gpg2 to the list of possible tools to use (which I ditched), I mistakenly came under the impression that the --no-default-keyring parameter was available on gpgv/gpgv2, but it's not, so it needs removing from the patch I submitted, if adopted, otherwise it results in an error. I also noticed that in fact there's already a patch on the debian-next branch addressing the progress-linux file/folder/release renaming aspects, and covers more of them than me. Though mine does fix a possible important apt-key add failure issue (as described in previous message), and some other improvements. Perhaps both could be merged together, or whatever... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773896: monkeyscan: identity menu has no indicator for expired keys
Package: monkeysign Version: 2.0.2 Severity: normal File: /usr/bin/monkeyscan I have an expired key in my local keyring but monkeyscan doesn't indicate that it is expired in the menu. I would expect the menu item to be either greyed or crossed out or not be visible in the Identity menu at all. I don't have any revoked keys but I would expect those to have an indicator too, probably a different one to expired keys. Probably greyed out for expired keys and crossed out for revoked keys. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages monkeysign depends on: ii gnupg 1.4.18-6 ii gnupg-agent 2.0.26-3 ii python2.7.8-2 ii python-pkg-resources 5.5.1-1 Versions of packages monkeysign recommends: ii python-gtk2 2.24.0-4 ii python-qrencode 1.01-4 ii python-zbar 0.10+doc-10 ii python-zbarpygtk 0.10+doc-10 monkeysign suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#764732: gcc-4.9: broken -O2 optimizations on armhf
the escalation is wrong. there exist several workarounds for it (lowering the optimization, using gcc-4.8, ...). I asked the ARM porters to address this properly (Hector on IRC agreed to forward this), however I don't see any progress here. Now CCing debian-arm explicitly. On 12/23/2014 11:48 AM, Santiago Vila wrote: severity 764732 serious thanks On Fri, 10 Oct 2014, Hector Oron wrote: Package: gcc-4.9 Version: 4.9.1-16 Severity: important Hello, Found a FTBFS while trying to build unzip package in Debian/sid on armhf host. [...] Yesterday, I uploaded unzip 6.0-13 fixing several security bugs, but it will not migrate to testing because of this, which has just been reported against unzip as Bug #773785. Since this is really a gcc bug, I'm raising the severity accordingly. Please tell me about the likelihood that this is indeed fixed in gcc, because if it's low I will have to look for a workaround in unzip (such as lowering the optimization level). Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773343: [request-tracker-maintainers] Bug#773343: request-tracker4: fails to upgrade from 'wheezy' if rt4-extension-assettracker is installed
hi, On Mon, Dec 22, 2014 at 8:08 AM, gregor herrmann gre...@debian.org wrote: during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'jessie' fails. rt4-extension-assettracker is not in jessie due to #748737: doesn't support RT 4.2 Good news: I can reproduce the bug. Bad news: Neither a Breaks: rt4-extension-assettracker nor a Conflicts: rt4-extension-assettracker helps ... RC Autoremovals is set as of 2015/1/30. What is the plan to get rid of this? The RT instance which altered by assettracker will seem to be fail to upgrade, so it would be as follows: a. implement some migration from assettracker to RTx::Assets (but refered as too late in #748737) b. patch RT's db migration script to allow assettracker's modification c. purge assettracker with its data dump and recover RTDB before upgrading RT d. skip RT upgrade if assettracker is installed e. etc, etc. assettracker is already removed from testing, so I think that something like c. and d. would be candidates... regards, -- KURASHIKI Satoru -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762097: nat-rtsp-dkms: not work
El 06/10/14 a las #4, Julien Muchembled escribió: Thank you for the detail. And just an email to write what I've done so far. If I'm going to contribute upstream, I prefer to first have a way to easily test things, I agree so I started to write a unit test which sets up 3 nodes (server, router client) using network namespaces. I'm sorry, I don't know network namespace. I can't contritute anything to that. However, I'm stuck because it works without nf_nat_rtsp loaded. I tried VLC GStreamer as server. I discovered that UDP streams are initiated by the client and that both servers reply to correct source port so simple NAT is of course enough. Just wondering why there are rtsp servers in the wild that don't simply work like that. I guess you don't know any server I could use to finish this unit test. I agree again I have written a tiny rtsp server and client. I created, with kvm, three virtual machines, a firewall (router), a server and a client, ___ ___ ___ | || || | | C |[1]--[2]| F |[3]--[4]| S | |___||___||___| [1] 192.168.200.33 client ip [2] 192.168.200.2 firewall ip client side [3] 192.168.100.2 firewall ip server side [4] 192.168.100.33 server ip You must configure firewall with nat-rtsp and ip_forwarding. Then run rtsp_server.pl, as root, in the server and rtsp_client.pl in the client machine. I advise you to compile nat-rtsp with debug and monitor syslog. You can see that without the patch does not work, and it does patched. Sorry for the delay -- Eduardo rtsp_client.pl Description: Perl program rtsp_server.pl Description: Perl program
Bug#773895: [Pkg-sysvinit-devel] Bug#773895: sysvinit: package to pin sysvinit during upgrades
[Michael Gilbert] Proposed patch included this time. Thank you. It is a bit unclear to me why such package should be part of the sysvinit source package. Why not make it a separate package? Also, What is the idea behind the list of pinned packages? Should it only affect the boot system, or also user space programs trying to use systemd outside the boot? -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773897: please remove the upper dependency on a specific gcc package version
Package: libstarpu-contrib-dev Version: 1.1.3+dfsg-3 please remove the upper dependency on a specific gcc package version. I can't see a reason why the package shouldn't work with GCC 4.8.3, but not with GCC 4.8.4. The dependency on the major gcc version is already there. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773898: please binNMU starpu-contrib
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu please binNMU starpu-contrib, using gcc-4.8 (= 4.8.4-1) for the build, to bump the upper version dependency in libstarpu-contrib-dev. A separate issue is filed to remove this dependency altogether (#773897). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
