Bug#769802: closed by Colin Watson (Re: Bug#769802: man-db: cron.daily fails: "fopen: Permission denied")

[Hartmut Brüning]

 

Thanks a lot. I did not suspect duplicity because it seemed to me quite
stable. But in fact it is not. Duplicity really changed the permissions.
The user proxy in the rescue system has the same uid than the user man
in Debian. It is reproducible now. Better I start a complete new
installation now. Fortunately I was still testing the backup procedures.


I will ask someone of the duplicity guys or use something different.
Thank you very much. 

Hartmut 

root@sysresccd /root % duplicity -t 4D --file-to-restore
var/cache/man/id/ ftp://XX@XX
/mnt/backup/tmp/4D_var_cache_man_id
root@sysresccd /root % ls /mnt/backup/tmp/4D_var_cache_man_id -l
total 32
-rw-r--r-- 1 man root 190 Nov 9 09:36 CACHEDIR.TAG
drwxr-sr-x 2 man root 4096 Nov 9 09:35 cat1
drwxr-sr-x 2 man root 4096 Nov 9 09:35 cat5
drwxr-sr-x 2 man root 4096 Nov 9 09:35 cat8
-rw-r--r-- 1 man root 13559 Nov 12 18:44 index.db
root@sysresccd /root % chroot /mnt/backup /bin/bash
root@sysresccd:/# ls /tmp/4D_var_cache_man_id/ -l
total 32
-rw-r--r-- 1 proxy root 190 Nov 9 10:36 CACHEDIR.TAG
drwxr-sr-x 2 proxy root 4096 Nov 9 10:35 cat1
drwxr-sr-x 2 proxy root 4096 Nov 9 10:35 cat5
drwxr-sr-x 2 proxy root 4096 Nov 9 10:35 cat8
-rw-r--r-- 1 proxy root 13559 Nov 12 19:44 index.db

Am 2014-11-16 22:45, schrieb ow...@bugs.debian.org: 

> This is an automatic notification regarding your Bug report
> which was filed against the man-db package:
> 
> #769802: man-db: cron.daily fails: "fopen: Permission denied"
> 
> It has been closed by Colin Watson .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Colin Watson 
>  by
> replying to this email.
> 
> Received: (at 769802-close) by bugs.debian.org; 16 Nov 2014 21:43:56 +
> X-Spam-Checker-Version: SpamAssassin 3.3.2-bugs.debian.org_2005_01_02
> (2011-06-06) on buxtehude.debian.org
> X-Spam-Level: 
> X-Spam-Status: No, score=-8.3 required=4.0 
> tests=BAYES_00,FROMDEVELOPER,GENDER,
> HAS_BUG_NUMBER,RCVD_IN_DNSWL_LOW autolearn=ham
> version=3.3.2-bugs.debian.org_2005_01_02
> X-Spam-Bayes: score:0. Tokens: new, 14; hammy, 151; neutral, 108; spammy,
> 0. spammytokens: hammytokens:0.000-+--rw-r, 0.000-+--UD:cron.daily,
> 0.000-+--cron.daily, 0.000-+--crondaily, 0.000-+--H*u:1.5.21
> Return-path: 
> Received: from b.a.painless.aa.net.uk ([81.187.30.65])
> by buxtehude.debian.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256)
> (Exim 4.80)
> (envelope-from )
> id 1Xq7bv-0008Qt-Vm
> for 769802-cl...@bugs.debian.org; Sun, 16 Nov 2014 21:43:56 +
> Received: from 
> 3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.4.1.b.e.2.f.f.b.0.b.8.0.1.0.0.2.ip6.arpa 
> ([2001:8b0:bff2:eb14::3] helo=riva.pelham.vpn.ucam.org)
> by a.painless.aa.net.uk with esmtps (TLSv1:AES128-SHA:128)
> (Exim 4.77)
> (envelope-from )
> id 1Xq7br-0006P9-8n
> for 769802-cl...@bugs.debian.org; Sun, 16 Nov 2014 21:43:51 +
> Received: from ns1.pelham.vpn.ucam.org ([172.20.153.2] helo=riva.ucam.org)
> by riva.pelham.vpn.ucam.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128)
> (Exim 4.80)
> (envelope-from )
> id 1Xq7bq-fV-Av
> for 769802-cl...@bugs.debian.org; Sun, 16 Nov 2014 21:43:50 +
> Date: Sun, 16 Nov 2014 21:43:49 +
> From: Colin Watson 
> To: 769802-cl...@bugs.debian.org
> Subject: Re: Bug#769802: man-db: cron.daily fails: "fopen: Permission denied"
> Message-ID: <20141116214349.gg5...@riva.ucam.org>
> References: <20141116152558.4573.39446.report...@desktop.brueningserver.de>
> <20141116175643.gf5...@riva.ucam.org>
> 
> MIME-Version: 1.0
> Content-Type: text/plain; charset=utf-8
> Content-Disposition: inline
> Content-Transfer-Encoding: 8bit
> In-Reply-To: 
> User-Agent: Mutt/1.5.21 (2010-09-15)
> 
> On Sun, Nov 16, 2014 at 07:29:45PM +0100, Hartmut Brüning wrote:
> 
>> Wow! It is this: -rwxr-xr-x 1 root root 133728 Nov 3 22:39 /usr/bin/mandb 
>> /var/cache/man/id/: total 40 drwxr-sr-x 5 proxy root 4096 Nov 16 15:23 . 
>> drwxr-sr-x 33 man root 4096 Nov 16 16:16 .. -rw-r--r-- 1 proxy root 190 Nov 
>> 9 10:36 CACHEDIR.TAG drwxr-sr-x 2 proxy root 4096 Nov 9 10:35 cat1 
>> drwxr-sr-x 2 proxy root 4096 Nov 9 10:35 cat5 drwxr-sr-x 2 proxy root 4096 
>> Nov 9 10:35 cat8 -rw-r--r-- 1 root root 13513 Nov 12 19:44 index.db I am 
>> trying to find out how this could have happen.
> 
> Ah, you said you'd used duplicity. At least some versions of duplicity
> have a terrible flaw whereby it stores ownership information about files
> by user/group name rather than number. This means that you cannot
> safely use it, for example, to restore a full-system backup when running
> from a live CD, because user and group names and numbers are not going
> to match up. I had a very similar experience with duplicity some years
> ago, and as a result of this and other flaws concluded that it was
> unsuitable for use as a full-system backup program, and could only
> reasonably be used on a smaller scale, perhaps fo

Bug#769813: pre-approval: unblock: hdapsd/1:20141024-2

[Jonathan Wiltshire]

Control: tag -1 confirmed

On Mon, Nov 17, 2014 at 08:06:59AM +0100, Evgeni Golov wrote:
> On 11/16/2014 10:15 PM, Jonathan Wiltshire wrote:
> > Control: tag -1 moreinfo
> > 
> > On Sun, Nov 16, 2014 at 06:24:01PM +0100, Evgeni Golov wrote:
> >> +To disable hdapsd under systemd, use “systemctl disable hdapsd.service”.
> >> +For inits using the init.d scripts, adjust /etc/default/hdapsd to have
> >> +  START=no
> >> +in it.
> > 
> > We have update-rc.d, no?
> 
> Yes we do. So how about:
> 
> To disable hdapsd under systemd, use “systemctl disable hdapsd.service”.
> For inits using the init.d scripts, use “update-rc.d hdapsd disable” or
> adjust /etc/default/hdapsd to have “START=no” in it.

Hm, well, my point was to get rid of the setting a flag in a defaults file
bit, but ok. Having a standard (and programmable) interface is way better
than having to manipulate defaults.

> (I still prefer to use systemctl, which is native to systemd, instead of
> update-rc.d which somehow can handle systemd links).

Sure - I wasn't proposing to remove the systemd advice.


-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



signature.asc
Description: Digital signature

Bug#769863: d-i ask for installing non-free software

[root]

Package: debian-installer
Severity: wishlist

Hi,
during install of a Debian Installer Jessie Beta 2 ( 
http://cdimage.debian.org/cdimage/jessie_di_beta_2/multi-arch/iso-cd/debian-jessie-DI-b2-amd64-i386-netinst.iso
 ) d-i ask using non-free packages, but at the end of the install process, 
packages like firmware-linux-nonfree and amd64-microcode/intel-microcode are 
not installed.
Please consider, if user choose to use non-free packages, to include them.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (1, 'testing-updates'), (1, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769206: unblock tnftp/20130505-3

[Aníbal Monsalve Salazar]

Control: retitle -1 unblock tnftp/20130505-3
Control: reopen -1

On Sat, 2014-11-15 11:00:16 +, Jonathan Wiltshire wrote:
> 
> Changing compat level just to add hardening is not a good solution.
> Other subtle changes are made in the packaging when that happens.
> Please find a way to apply the hardening flags without changing compat
> level.

Done.

Below is the debdiff between 20130505-1 in testing and 20130505-3 in
unstable.

Thank you!

debdiff tnftp_20130505-1.dsc tnftp_20130505-3.dsc
diff -Nru tnftp-20130505/debian/changelog tnftp-20130505/debian/changelog
--- tnftp-20130505/debian/changelog 2013-05-26 01:01:45.0 +0100
+++ tnftp-20130505/debian/changelog 2014-11-17 06:51:20.0 +
@@ -1,3 +1,26 @@
+tnftp (20130505-3) unstable; urgency=medium
+
+  * Revert DH compatibility level to 7.
+  * Set hardening options.
+
+ -- Anibal Monsalve Salazar   Mon, 17 Nov 2014 06:51:16 
+
+
+tnftp (20130505-2) unstable; urgency=medium
+
+  * Only trust filenames with special meaning if they came from
+the command line. CVE-2014-8517.
+Add upstream patch CVE-2014-8517.patch.
+Closes: #767171.
+  * Run dh-autoreconf to update for new architectures.
+Patch by Brahadambal Srinivasan .
+Closes: 759467.
+  * Standards Version is 3.9.6.
+  * Fix uses-deprecated-compression-for-data-tarball.
+  * Fix build-depends-on-obsolete-package.
+build-depends: hardening-wrapper => use dpkg-buildflags instead.
+
+ -- Anibal Monsalve Salazar   Thu, 06 Nov 2014 10:42:01 
+
+
 tnftp (20130505-1) unstable; urgency=low
 
   * New upstream version 20130505
diff -Nru tnftp-20130505/debian/control tnftp-20130505/debian/control
--- tnftp-20130505/debian/control   2013-05-26 00:04:41.0 +0100
+++ tnftp-20130505/debian/control   2014-11-17 06:31:39.0 +
@@ -2,8 +2,8 @@
 Section: net
 Priority: optional
 Maintainer: Anibal Monsalve Salazar 
-Build-Depends: debhelper (>= 7), hardening-wrapper, libncurses5-dev, libssl-dev
-Standards-Version: 3.9.4
+Build-Depends: debhelper (>= 7), libncurses5-dev, libssl-dev, autotools-dev
+Standards-Version: 3.9.6
 Homepage: http://en.wikipedia.org/wiki/Tnftp
 
 Package: tnftp
diff -Nru tnftp-20130505/debian/patches/CVE-2014-8517.patch 
tnftp-20130505/debian/patches/CVE-2014-8517.patch
--- tnftp-20130505/debian/patches/CVE-2014-8517.patch   1970-01-01 
01:00:00.0 +0100
+++ tnftp-20130505/debian/patches/CVE-2014-8517.patch   2014-11-06 
10:24:25.0 +
@@ -0,0 +1,92 @@
+Date: Sun, 26 Oct 2014 12:21:59 -0400
+From: Christos Zoulas 
+To: source-changes-f...@...bsd.org
+Subject: CVS commit: src/usr.bin/ftp
+X-Mailer: log_accum
+
+Module Name:src
+Committed By:   christos
+Date:   Sun Oct 26 16:21:59 UTC 2014
+
+Modified Files:
+src/usr.bin/ftp: fetch.c
+
+Log Message:
+don't pay attention to special characters if they don't come from the 
command
+line (from jmcneill)
+
+http://security-tracker.debian.org/tracker/CVE-2014-8517
+https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767171
+http://www.openwall.com/lists/oss-security/2014/10/28/4
+
+Index: tnftp-20130505/src/fetch.c
+===
+--- tnftp-20130505.orig/src/fetch.c
 tnftp-20130505/src/fetch.c
+@@ -571,7 +571,7 @@ fetch_url(const char *url, const char *p
+   url_decode(decodedpath);
+ 
+   if (outfile)
+-  savefile = ftp_strdup(outfile);
++  savefile = outfile;
+   else {
+   cp = strrchr(decodedpath, '/'); /* find savefile */
+   if (cp != NULL)
+@@ -595,8 +595,7 @@ fetch_url(const char *url, const char *p
+   rangestart = rangeend = entitylen = -1;
+   mtime = -1;
+   if (restartautofetch) {
+-  if (strcmp(savefile, "-") != 0 && *savefile != '|' &&
+-  stat(savefile, &sb) == 0)
++  if (stat(savefile, &sb) == 0)
+   restart_point = sb.st_size;
+   }
+   if (urltype == FILE_URL_T) {/* file:// URLs */
+@@ -1140,18 +1139,26 @@ fetch_url(const char *url, const char *p
+   }
+   }   /* end of ftp:// or http:// specific setup */
+ 
+-  /* Open the output file. */
+-  if (strcmp(savefile, "-") == 0) {
+-  fout = stdout;
+-  } else if (*savefile == '|') {
+-  oldintp = xsignal(SIGPIPE, SIG_IGN);
+-  fout = popen(savefile + 1, "w");
+-  if (fout == NULL) {
+-  warn("Can't execute `%s'", savefile + 1);
+-  goto cleanup_fetch_url;
++  /* Open the output file. */
++
++  /*
++   * Only trust filenames with special meaning if they came from
++   * the command line
++   */
++  if (outfile == savefile) {
++  if (strcmp(savefile, "-") == 0) {
++  fout = stdout;
++  } else if (*savefile == '|') {
++  oldintp

Bug#769844: linux: please make linux build reproducibly

[Bastian Blank]

On Mon, Nov 17, 2014 at 12:46:45AM +0100, Jérémy Bobbio wrote:
> The first patch adds call to `dh_strip_nondeterminism` and
> `dh_fixmtimes`, both being part of the custom toolchain currently used
> for reproducible builds. Hence not tagging the bug with “patch” until
> they are integrated in debhelper.

Why does this need new tool instead of being integrated into the
existing ones?

> The second patch changes the value of KBUILD_BUILD_TIMESTAMP to a
> timestamp parseable by `date`.

Well, no.  The string is this way for a reason.

> An unclear aspect is where to add a call to `dh_genbuildinfo` which
> generates the .buildinfo [2]. It should be called after all binary
> packages have been created.

Not possible, dh_* acts on single binary packages.

>  * linux-source: mtimes of many files differ. Would it be ok to just
>create the tarball with a single timestamp (`tar --mtime=`)?

Looks like a way.

Bastian


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#750361: Still happens on 38.0.2125.101-2

[Torsten Jerzembeck]

Hello,

I can confirm that this bug is present on an (old, but still working
fine) AMD Athlon XP 2500+ on current 38.0.2125.101-3.

/proc/cpuinfo:

processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 6
model   : 10
model name  : AMD Athlon(tm) XP 2500+
stepping: 0
cpu MHz : 1837.000
cache size  : 512 KB
physical id : 0
siblings: 1
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 1
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow
bogomips: 3704.32
clflush size: 32
cache_alignment : 32
address sizes   : 34 bits physical, 32 bits virtual
power management: ts

If you need more information I'll be happy to help out.

Best regards,

=ToJe=

-- 
Torsten Jerzembeck * Karlsruhe, Germany
Exil-Westfale * PGP: B74DB58D * MIME welcome * Generation Tux * >


signature.asc
Description: Digital signature

Bug#769864: vcmi: FTBFS on armhf, hurd-any, kfreebsd-any, mipsel and ppc64el

[Johannes Schauer]

Package: vcmi
Version: 0.97+dfsg-1
Severity: normal

Hi,

vcmi fails to build on several arches.

On armhf, this might just be an OOM error as vcmi eats tons of memory
because of C++ templating:

[ 43%] Building CXX object 
lib/CMakeFiles/vcmi.dir/registerTypes/TypesClientPacks2.cpp.o
cd /«BUILDDIR»/vcmi-0.97+dfsg/build/lib && /usr/bin/c++   
-DM_BIN_DIR=\"/usr/games\" -DM_DATA_DIR=\"/usr/share/vcmi\" 
-DM_LIB_DIR=\"/usr/lib/arm-linux-gnueabihf/vcmi\" -DUSE_SYSTEM_MINIZIP 
-DVCMI_DLL=1 -Dvcmi_EXPORTS -g -O2 -fPIE -fstack-protector-strong -Wformat 
-Werror=format-security -D_FORTIFY_SOURCE=2  -std=c++0x -Wall -Wextra 
-Wpointer-arith -Wno-strict-aliasing -Wno-switch -Wno-sign-compare 
-Wno-unused-local-typedefs  -Wno-unused-parameter -Wuninitialized 
-Wno-overloaded-virtual -Wno-type-limits  -fvisibility=hidden -O2 -g -DNDEBUG 
-fPIC -I/«BUILDDIR»/vcmi-0.97+dfsg -I/«BUILDDIR»/vcmi-0.97+dfsg/lib 
-I/usr/include/SDL2 -Winvalid-pch -include 
"/«BUILDDIR»/vcmi-0.97+dfsg/build/lib/cotire/vcmi_CXX_prefix.hxx"  -o 
CMakeFiles/vcmi.dir/registerTypes/TypesClientPacks2.cpp.o -c 
/«BUILDDIR»/vcmi-0.97+dfsg/lib/registerTypes/TypesClientPacks2.cpp
make[1]: *** [override_dh_auto_build] Terminated
debian/rules:36: recipe for target 'override_dh_auto_build' failed
make: *** [build-arch] Terminated
debian/rules:11: recipe for target 'build-arch' failed
E: Caught signal ‘Terminated’: terminating immediately
lib/CMakeFiles/vcmi.dir/build.make:1802: recipe for target 
'lib/CMakeFiles/vcmi.dir/IGameCallback.cpp.o' failed
make[4]: *** [lib/CMakeFiles/vcmi.dir/IGameCallback.cpp.o] Terminated
CMakeFiles/Makefile2:148: recipe for target 
'lib/CMakeFiles/vcmi.dir/all' failed
make[3]: *** [lib/CMakeFiles/vcmi.dir/all] Terminated
make[2]: *** [all] Terminated
Makefile:140: recipe for target 'all' failed
Build killed with signal TERM after 302 minutes of inactivity

On hurd-any and kfreebsd-any, there seems to be a check so that it errors out on
non-linux/windows/osx/android OSes, which affects hurd and kfreebsd:

[  1%] Building CXX precompiled header 
lib/cotire/vcmi_CXX_prefix.hxx.gch
cd /«BUILDDIR»/vcmi-0.97+dfsg/lib && /usr/bin/cmake 
-DCOTIRE_BUILD_TYPE:STRING=RelWithDebInfo -DCOTIRE_VERBOSE:BOOL=1 -P 
/«BUILDDIR»/vcmi-0.97+dfsg/cmake_modules/cotire.cmake precompile 
/«BUILDDIR»/vcmi-0.97+dfsg/build/lib/vcmi_CXX_cotire.cmake 
/«BUILDDIR»/vcmi-0.97+dfsg/build/lib/cotire/vcmi_CXX_prefix.hxx 
/«BUILDDIR»/vcmi-0.97+dfsg/build/lib/cotire/vcmi_CXX_prefix.hxx.gch StdInc.cpp
-- execute_process: 
/usr/bin/c++;-Dvcmi_EXPORTS;-DUSE_SYSTEM_MINIZIP;-DM_DATA_DIR="/usr/share/vcmi";-DM_BIN_DIR="/usr/games";-DM_LIB_DIR="/usr/lib/i386-gnu/vcmi";-DVCMI_DLL=1;-D_FORTIFY_SOURCE=2;-DNDEBUG;-g;-O2;-fPIE;-fstack-protector-strong;-Wformat;-Werror=format-security;-std=c++0x;-Wall;-Wextra;-Wpointer-arith;-Wno-strict-aliasing;-Wno-switch;-Wno-sign-compare;-Wno-unused-local-typedefs;-Wno-unused-parameter;-Wuninitialized;-Wno-overloaded-virtual;-Wno-type-limits;-fvisibility=hidden;-O2;-g;-fPIC;-I/«BUILDDIR»/vcmi-0.97+dfsg;-I/«BUILDDIR»/vcmi-0.97+dfsg/lib;-I/usr/include/SDL2;-x;c++-header;-c;/«BUILDDIR»/vcmi-0.97+dfsg/build/lib/cotire/vcmi_CXX_prefix.hxx;-o;/«BUILDDIR»/vcmi-0.97+dfsg/build/lib/cotire/vcmi_CXX_prefix.hxx.gch
In file included from /«BUILDDIR»/vcmi-0.97+dfsg/lib/StdInc.h:3:0,
 from 
/«BUILDDIR»/vcmi-0.97+dfsg/build/lib/cotire/vcmi_CXX_prefix.cxx:4,
 from 
/«BUILDDIR»/vcmi-0.97+dfsg/build/lib/cotire/vcmi_CXX_prefix.hxx:4:
/«BUILDDIR»/vcmi-0.97+dfsg/lib/../Global.h:75:4: error: #error "VCMI 
supports only Windows, OSX, Linux and Android targets"
 #  error "VCMI supports only Windows, OSX, Linux and Android targets"
^
CMake Error at 
/«BUILDDIR»/vcmi-0.97+dfsg/cmake_modules/cotire.cmake:1622 (message):
  cotire: error 1 precompiling
  /«BUILDDIR»/vcmi-0.97+dfsg/build/lib/cotire/vcmi_CXX_prefix.hxx.
Call Stack (most recent call first):
  /«BUILDDIR»/vcmi-0.97+dfsg/cmake_modules/cotire.cmake:3090 
(cotire_precompile_prefix_header)


make[4]: *** [lib/cotire/vcmi_CXX_prefix.hxx.gch] Error 1
make[3]: *** [lib/CMakeFiles/vcmi.dir/all] Error 2
make[2]: *** [all] Error 2

On mipsel, there is an ICE:

[ 41%] Building CXX object lib/CMakeFiles/vcmi.dir/CGameState.cpp.o
cd /«BUILDDIR»/vcmi-0.97+dfsg/build/lib && /usr/bin/c++   
-DM_BIN_DIR=\"/usr/games\" -DM_DATA_DIR=\"/usr/share/vcmi\" 
-DM_LIB_DIR=\"/usr/lib/mipsel-linux-gnu/vcmi\" -DUSE_SYSTEM_MINIZIP 
-DVCMI_DLL=1 -Dvcmi_EXPORTS -g -O2 -fPIE -fstack-protector-strong -Wformat 
-Werror=format-security -D_FORTIFY_SOURCE=2  -std=c++0x -Wall -Wextra 
-Wpointer-arith -Wno-strict-aliasing -Wno-switch -Wno-sign-compare 
-Wno-unused-local-typedefs  -Wno-unused-parameter -Wuninitialized 
-Wno-overload

Bug#769862: libav: target option broken - leads to wrong output files

[Vincent Pinon]

Source: libav
Version: 11
Severity: normal
Tags: upstream

This bug was reported upstream by someone else 1.5 year back,
with note on how to simply fix it, but the problem persists.

This breaks eg DVD production flow, as the encoding profiles produce
non-compliant output files.

Workaround is to re-enter all associated options, but this is an
annoying regression (not seen in FFmpeg).

Thanks for taking this into account!

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (100, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769861: libav: Blocky H264 decoding from Canon 5D Mark III

[Vincent Pinon]

Source: libav
Version: 11
Severity: important
Tags: upstream

Hello,

I reported the bug upstream first
(https://bugzilla.libav.org/show_bug.cgi?id=781), don't know if it is
useful to forward info here?

As this camera is being more and more used for pro videos, not
being able to edit them is a problem.
Workarounds are reverting to libav 10 or using ffmpeg daily builds, but
these are not comfortable options, nor accessible to everyone.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (100, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769813: pre-approval: unblock: hdapsd/1:20141024-2

[Evgeni Golov]

On 11/16/2014 10:15 PM, Jonathan Wiltshire wrote:
> Control: tag -1 moreinfo
> 
> On Sun, Nov 16, 2014 at 06:24:01PM +0100, Evgeni Golov wrote:
>> +To disable hdapsd under systemd, use “systemctl disable hdapsd.service”.
>> +For inits using the init.d scripts, adjust /etc/default/hdapsd to have
>> +  START=no
>> +in it.
> 
> We have update-rc.d, no?

Yes we do. So how about:

To disable hdapsd under systemd, use “systemctl disable hdapsd.service”.
For inits using the init.d scripts, use “update-rc.d hdapsd disable” or
adjust /etc/default/hdapsd to have “START=no” in it.

(I still prefer to use systemctl, which is native to systemd, instead of
update-rc.d which somehow can handle systemd links).

Greets


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#768450: Correct second version of the patch

[Martin Pitt]

Didier Roche [2014-11-07 16:38 +0100]:
> +  * invoke-rc.d: don't start disabled systemd services when invoke-rc.d
> +is directly invoked. The job is then started unconditionally on
> +invoke-rc.d [restart|start]. (Closes: #768450)
> +Use a similar logic than for upstart:
> +- invoke-rc.d start  don't do anything on systemd if the service is
> +  disabled.
> +- invoke-rc.d restart  only restart a disabled service if the 
> daemon
> +  was already running (forced by the admin).

Thanks for that! The patch looks logically correct to me.

> +systemctl --quiet is-enabled "${UNIT}"
> +ENABLED=$?
> +systemctl --quiet is-active "${UNIT}"
> +RUNNING=$?
> +
> +if [ $ENABLED != 0 ] && [ "$saction" = "start" ]; 
> then
> +exit 0
> +fi
> +# If the job is disabled and is not currently
> +# running, the job is not restarted. However, if
> +# the job is disabled but has been forced into
> +# the running state, we *do* stop and restart it
> +# since this is expected behaviour
> +# for the admin who forced the start.
> +if [ $ENABLED != 0 ] && [ $RUNNING != 0 ] && [ 
> "$saction" = "restart" ]; then
> +exit 0
> +fi

Maybe that's just my limited imagination, but I find this hard to read
("[ $ENABLED != 0 ]). I find this structure easier to read:

  # We never start disabled jobs; we only restart them if they are
  # already running (got started manually)
  if ! systemctl --quiet is-enabled "${UNIT}"; then
  if [ "$saction" = "start" ]; then
  exit 0
  elif [ "$saction" = "restart" ] && ! systemctl --quiet is-active 
"${UNIT}"; then
  exit 0
  fi
  fi

Anyway, I guess which one to take is for the sysvinit maintainers to
decide. :-)

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#376146: ***UNCHECKED*** Re: Bug#376146: perfect is the enemy of good :/

[Jaldhar H. Vyas]

On Sun, 16 Nov 2014, Mathieu Parent (Debian) wrote:

Hello,


Summary: please reconsider your wontfix.



1. It is much to late to make this kind of change for jessie.

2. I suggest you ask on debian-project or IRC for opinions on this, both 
for dovecot and SSL using servers in general, from people who understand 
this crypto thing much better than I do.


--
Jaldhar H. Vyas 


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769853: unblock: python-persistent/4.0.8-2

[Arnaud Fontaine]

Niels Thykier  writes:

> If files have been moved around, you need
>   Replaces: python-zodb (<< 3.11.0~)
>   Breaks: python-zodb (<< 3.11.0~)
>
> And not conflicts.  There is rarely a need for (lone) "Conflict" these
> days (notable exception being Policy §7.5.2[1]).
>
> Please confirm you really meant to use Conflicts (and why).  Otherwise
> please use Replaces+Breaks instead.

After discussing on  #767554 with other maintainers, there  is really no
other solution,  at least  for Jessie. Here  is the  relevant discussion
about this on #767554:

  From upstream point of view, ZODB3 (aka python-zodb in Debian) used to
  include  persistent, BTrees,  ZODB  and ZEO  modules.  However,  since
  ZODB3 3.11.0a1, upstream has split it up into 4 distinct packages (one
  for  each  module),  bump  the  version   to  4.0  and  made  ZODB3  a
  "metapackage" depending on all of them.

  As of fixing  this RC bug for Jessie: Among  the four, only persistent
  package is  currently available in Debian,  so there is no  way to get
  rid of ZODB3 (at least for Jessie). Barry: If persistent >= 4.0 Debian
  package is useful on its own to anyone (and thus should not be removed
  From testing), then  can I add a Conflict on  both packages and upload
  them to fix this bug?

And here is the reply from Barry Warsaw (maintainer of
python-persistent):

  I think  a Conflicts is  the right way to  handle this for  now, given
  where we are in the Jessie release cycle.

After releasing Jessie,  we plan to update python-zodb  and upload split
up modules  (namely python-zeo  and python-btrees which  are not  in the
archive yet).

Cheers,
-- 
Arnaud Fontaine


signature.asc
Description: PGP signature

Bug#751827: python-virtualenv: version of pip in virtualenvs fails to uninstall some packages

[Stefano Rivera]

Control: reassign -1 python-pip-whl
Control: found -1 python-pip-whl/1.5.6-2

> (I am unsure if this is because of interaction of pip with the virtualenv,
> so I am reporting against python-virtualenv, not python-pip. Feel free
> to reassign!)

Yeah, this is actually a pip bug.

So, it looks like the story is:
1. Debian patched setuptools/distribute to not include the Python
   version in egg-info dirs. There is no bug I can see that tracks this.
2. pip then implemented the same mangling, after un-installation trouble
   was reported in #562544.
3. pip upstream implemented a workaround, themselves
   https://github.com/pypa/pip/commit/0d60e37273c587237cd2f0678ecf19005d49cea7
   and filed #618367 about Debian's original patch.

This bug arises because the setuptools patch from 1 doesn't mangle the
name, inside a virtualenv, but the pip patch from 2 does. And the
solution in 3 was masked by the patch in 2.

So, my solution to this is to drop Debian's patch to pip.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  H: +27 21 461 1230 C: +27 72 419 8559


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#729856: Giving up ITP

[Vasudev Kamath]

Control: retitle -1 RFP: libtranslit -- Transliteration library with
multiple backends
Control: noowner -1

I mistakenly filed ITP for this bug its not really dependency for
ibus-typing-booster.

Cheers,
-- 

Vasudev Kamath
http://copyninja.info
copyninja@{frndk.de|vasudev.homelinux.net}


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769461: installing dovecot-core from scratch fails

[Jaldhar H. Vyas]

I think we should probably leave 10-ssl.conf commented out all together. 
While I prepare a new package that does this, you can do it youself by 
placing a # at the beginning of every line in 
/etc/dovecot/conf.d/10-ssl.conf which doesn't already have it and running 
the install again.  (If you are asked if you want to replace that file, 
say no.)


--
Jaldhar H. Vyas 


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769747: [PATCH] debian/control: switch order of systemd-sysv|systemd-shim dependencies for libpam-systemd. (Closes: #769747)

[Don Armstrong]

On November 16, 2014 10:29:21 PM PST, Martin Pitt  wrote:
>Hey Don,
>
>Don Armstrong [2014-11-16 14:14 -0800]:
>> Control: tag -1 patch
>
>whoops, I'm afraid I saw your patch too late, I alraedy committed
>http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=26a8a43
>when going through my Debian mailbox this morning. But it's
>essentially the same (obvious) thing with just a different changelog.


Cool! Thanks for taking care of that. No worries about the patch; I just wanted 
to make sure one was present.
-- 
This is not a signature.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769853: unblock: python-persistent/4.0.8-2

[Niels Thykier]

Control: tags -1 moreinfo

On 2014-11-17 05:58, Arnaud Fontaine wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package python-persistent
> 
> This fixes an error when trying to install it together with python-zodb,
> here is the changelog entry with further explanations:
> 
>   [...]
>   diff -Nru python-persistent-4.0.8/debian/control 
> python-persistent-4.0.8/debian/control
>   --- python-persistent-4.0.8/debian/control  2014-06-26 00:34:29.0 
> +0900
>   +++ python-persistent-4.0.8/debian/control  2014-11-14 18:31:01.0 
> +0900
>   @@ -22,6 +22,7 @@
>Package: python-persistent
>Architecture: any
>Depends: ${misc:Depends}, ${python:Depends}, ${shlibs:Depends}
>   +Conflicts: python-zodb (<< 3.11.0~)
>Description: Automatic persistence for Python objects
> This package contains a generic persistence implementation for Python. It
> forms the core protocol for making objects interact "transparently" with
> 
> Thanks in advance!
> 
> unblock python-persistent/4.0.8-2
> 
> Regards,
> 

Hi,

If files have been moved around, you need
  Replaces: python-zodb (<< 3.11.0~)
  Breaks: python-zodb (<< 3.11.0~)

And not conflicts.  There is rarely a need for (lone) "Conflict" these
days (notable exception being Policy §7.5.2[1]).

Please confirm you really meant to use Conflicts (and why).  Otherwise
please use Replaces+Breaks instead.

Thank you,
~Niels

[1] https://www.debian.org/doc/debian-policy/ch-relationships.html#s7.6.2


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769854: unblock: zodb/1:3.9.7-3

[Niels Thykier]

Control: tags -1 moreinfo

On 2014-11-17 06:00, Arnaud Fontaine wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package zodb
> 
> This fixes an error when trying to install it together with
> python-persistent and also add a Provides, here is the changelog entry
> with further explanations:
> 
>  [...]
> 
> Thanks in advance!
> 
> unblock zodb/1:3.9.7-3
> 
> Regards,
> 

Hi,

Same remark as in #769853: "Are you sure you want Conflicts and not
Replaces+Breaks?".

~Niels


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#768127: dhelp: Fails when building the index

[Yavor Doganov]

> Yavor Doganov wrote (05 Nov 2014 08:02:47 GMT) :
> > $ sudo dpkg-reconfigure dhelp
> > Building HTML tree...ArgumentError: invalid byte sequence in UTF-8 
> > (/usr/lib/ruby/vendor_ruby/debian.rb:914:in `block in initialize'
> 
> I cannot reproduce that in a sid GNOME VM, so I guess this is caused
> by some documentation file you have installed, but I haven't.
> Could you please try to get dhelp to tell you what file it's parsing
> when it fails?

Unfortunately I'm not familiar with Ruby and couldn't figure out how
to do that.  I tried to move away all UTF-8 files from
/var/lib/doc-base/documents and it fails again.  Then I moved all
files but "dc" and it fails, too.  FWIW, if I run dhelp_parse with
"LC_ALL=C" the error message is

ArgumentError: invalid byte sequence in US-ASCII
(/usr/lib/ruby/vendor_ruby/debian.rb:914:in `block in initialize'

(The backtrace is the same).

Could it be that debian.rb from ruby-debian is unable to parse the
Packages file(s)?

The log file in /var/lib/dhelp/tmp is empty, as well as
/var/lib/dhelp/documents.index.

I also tried with different doc-base files, the result is always the
same.  I'd be glad if I can assist in reproducing the issue, but I
I'd need some directions.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#728513: Giving up the ITP

[Vasudev Kamath]

Control: retitle -1 RFP: libdata-spreadpagination-perl -- page
numbering and spread pagination
Control: noowner -1

Since I don't have enough time to maintain this package, I'm giving
this ITP back. This is already packaged and source lies in pkg-perl
team repository [1], any one interested can take it up and upload the
same.

[1] 
http://anonscm.debian.org/cgit/pkg-perl/attic/libdata-spreadpagination-perl.git/tree/

Cheers,
-- 

Vasudev Kamath
http://copyninja.info
copyninja@{frndk.de|vasudev.homelinux.net}


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#728597: Giving up the ITP

[Vasudev Kamath]

Control: retitle -1 RFP: libcss-lessp-perl -- LESS for perl
Control: noowner -1

Since I don't have enough time to take care of this package and not
being a Perl programmer, I'm giving this ITP back but I've managed to
package this and source is in pkg-perl repository [1], any one
interested can take over this package and upload it.

[1] http://anonscm.debian.org/cgit/pkg-perl/packages/libcss-lessp-perl.git/

Cheers,
-- 

Vasudev Kamath
http://copyninja.info
copyninja@{frndk.de|vasudev.homelinux.net}


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769747: [PATCH] debian/control: switch order of systemd-sysv|systemd-shim dependencies for libpam-systemd. (Closes: #769747)

[Martin Pitt]

Hey Don,

Don Armstrong [2014-11-16 14:14 -0800]:
> Control: tag -1 patch

whoops, I'm afraid I saw your patch too late, I alraedy committed
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=26a8a43
when going through my Debian mailbox this morning. But it's
essentially the same (obvious) thing with just a different changelog.

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#769859: [workrave] Displays 2 icons in the system tray (KDE?)

[Francois Marier]

> Workrave has a system tray element with a sheep icon.
> 
> On this install, starting Workrave always causes the appearance of 2 such
> elements. They would seem to represent 2 different Workrave instances, but
> in fact, a single process is behind both, and trying to terminate any of
> these apparent instances causes the disappearance of both elements.

Are you sure you don't have both the "system tray icon" and the "applet"
turned on? They can be turned on/off from the UI section of the preferences.

> but this could also be a duplicate of #767739, which affects GNOME (I do
> not use GNOME, and the ticket is not clear enough to tell).

That bug is specifically about multiple processes (I think).

Francois

-- 
Francois Marier   identi.ca/fmarier
http://fmarier.org  twitter.com/fmarier


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769687: autopkgtest: FTBFS with no network access

[Martin Pitt]

Control: severity -1 minor
thanks

Hello Daniel,

Daniel Schepler [2014-11-15  7:52 -0800]:
> Severity: serious

I disagree. I don't think it is unreasonable for a package build to
expect to be able to download packages -- after all, you need to be
able to download the build dependencies. Thus lowering the severity.

Note that you can build with DEB_BUILD_OPTIONS=nocheck to skip the
test suite.

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#769589: debian-cd: Please improve .disk/cd_type for non-complete builds

[Petter Reinholdtsen]

[Steve McIntyre]
> Interesting change; I'd be tempted to refactor things slightly in
> the code, but that's a secondary thing. I'm more curious: what are
> the ramifications for d-i? Have you investigated/tested?

We use d-i in Debian Edu, and it is able to install from our ISO.  I
have not investigated more than that.  :) I suspect it might affect
apt-setup, but have not checked the code.

-- 
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#769815: ITP: cobbler -- network boot, install and update server

[Timo Aaltonen]

On 16.11.2014 19:34, Thomas Goirand wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Thomas Goirand 
> 
> * Package name: cobbler
>   Version : 2.6.6+dfsg1
>   Upstream Author : Michael DeHaan 
> * URL : http://www.cobblerd.org/
> * License : GPL-2
>   Programming Lang: Python
>   Description : network boot, install and update server
> 
>  Cobbler is a network install server. Cobbler supports PXE, virtualized
>  installs, and reinstalling existing Linux machines. The last two modes use a
>  helper tool, 'koan', that integrates with cobbler. Cobbler's advanced 
> features
>  include importing distributions from DVDs and rsync mirrors, kickstart
>  templating, integrated yum mirroring, and built-in DHCP/DNS Management.
>  Cobbler has a Python and XMLRPC API for integration with other applications.
>  There is also a web interface.
> 
> This is yet another dependency for OpenStack Fuel.

I've had packaging for this available in collab-maint git, based on the
Ubuntu package which still needs some cleanups:

http://anonscm.debian.org/cgit/collab-maint/cobbler.git

if useful to you in any way..

-- 
t


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769860: Gjiten could use kanjipad by default

[Bhavani Shankar R]

Package: gjiten
Severity: wishlist
Version: 2.6-2.3

Dear Maintainer,

Gjiten has a button labelled "KanjiPad", which launches kanjipad. But
even after installing gjiten and kanjipad, clicking on this button
pops up a warning about not knowing where the kanjipad executable is.

Given that kanjipad is also a official debian package, integration
between them can be improved.

Attached is a patch that does the same, which has been applied in ubuntu.

Regards,


-- 
Bhavani Shankar
Ubuntu Developer   |  www.ubuntu.com
https://launchpad.net/~bhavi
diff -pruN 2.6-2.2/src/conf.c 2.6-2.2ubuntu1/src/conf.c
--- 2.6-2.2/src/conf.c	2006-10-29 17:17:36.0 +
+++ 2.6-2.2ubuntu1/src/conf.c	2012-07-09 16:36:26.0 +
@@ -111,7 +111,7 @@ GjitenConfig *conf_load() {
 	
 
   conf->kanjipad = gconf_client_get_string(gconf_client, "/apps/gjiten/general/kanjipad", NULL);
-	if (conf->kanjipad == NULL) conf->kanjipad = "";
+	if (conf->kanjipad == NULL) conf->kanjipad = "/usr/bin/kanjipad";
 
   conf->numofdics = gconf_client_get_int(gconf_client, "/apps/gjiten/general/numofdics", NULL);
 
@@ -259,6 +259,7 @@ void conf_save_options(GjitenConfig *con
 gconf_client_set_bool(gconf_client, "/apps/gjiten/general/autoadjust_enabled", conf->autoadjust_enabled, NULL);
 gconf_client_set_bool(gconf_client, "/apps/gjiten/general/searchlimit_enabled", conf->searchlimit_enabled, NULL);
 gconf_client_set_int(gconf_client, "/apps/gjiten/general/maxwordmatches", conf->maxwordmatches, NULL);
+		gconf_client_set_string(gconf_client, "/apps/gjiten/general/kanjipad", conf->kanjipad, NULL);
 }
 
 gboolean conf_init_handler() {

Bug#769859: [workrave] Displays 2 icons in the system tray (KDE?)

[Filipus Klutiero]

Package: workrave
Version: 1.10.4-3
Severity: normal
X-Debbugs-Cc: 767...@bugs.debian.org

Workrave has a system tray element with a sheep icon.

On this install, starting Workrave always causes the appearance of 2 such 
elements. They would seem to represent 2 different Workrave instances, but in 
fact, a single process is behind both, and trying to terminate any of these 
apparent instances causes the disappearance of both elements.

As it seems that interacting with any of these works, this is apparently nothing more 
than a "cosmetic" bug.


This issue does not affect Windows. According to upstream ticket #786, Workrave 
has KDE-specific issues including a lack of sounds. This might be one, but this 
could also be a duplicate of #767739, which affects GNOME (I do not use GNOME, 
and the ticket is not clear enough to tell).

--- System information. ---
Architecture: i386
Kernel: Linux 3.16-2-amd64

Debian Release: jessie/sid
990 testing ftp3.nrc.ca
500 unstable ftp3.nrc.ca
1 experimental ftp3.nrc.ca

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.

--
Filipus Klutiero
http://www.philippecloutier.com


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#576503: 'man dash' typo: "the shell .... proceed onto"

[Herbert Xu]

Stéphane Aulery  wrote:
> [-- text/plain, encoding 8bit, charset: utf-8, 12 lines --]
> 
> Hello,
> 
> Here is a small patch reported by a user of Debian [1]. Could you please
> integrate? Thank you for your help.
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576503

Patch applied.  However, I had to manually apply it because you did
not generate the patch from the top of the source tree with -p1.

Please ensure future submissions are generated correctly.

Thanks,
-- 
Email: Herbert Xu 
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769858: wavesurfer: add a .desktop file

[Logan Rosen]

Package: wavesurfer
Version: 1.8.8p4-3
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu vivid ubuntu-patch

Dear Maintainer,

wavesurfer should have a .desktop file so that it can be launched easily by 
users in the GUI.

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/{wavesurfer.desktop,rules}: Add and install a .desktop file.

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-24-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
=== modified file 'debian/rules'
--- debian/rules	2011-05-08 00:35:42 +
+++ debian/rules	2014-11-17 04:50:34 +
@@ -22,6 +22,7 @@
 	dh_install 	-XREADME.txt -Xexample1.plug -Xexample2.plug	\
 			src/*			usr/share/tcltk/wavesurfer
 	dh_install 	debian/ws32.xpm		usr/share/pixmaps
+	dh_install	debian/wavesurfer.desktop 	usr/share/applications
 	dh_install 	wavesurfer		usr/bin
 	dh_installman 	debian/wavesurfer.1
 	dh_installdocs	doc

=== added file 'debian/wavesurfer.desktop'
--- debian/wavesurfer.desktop	1970-01-01 00:00:00 +
+++ debian/wavesurfer.desktop	2014-11-17 04:50:34 +
@@ -0,0 +1,9 @@
+[Desktop Entry]
+Type=Application
+Name=wavesurfer
+GenericName=
+Comment=Manipulate sound files
+Icon=ws32
+Exec=/usr/bin/wavesurfer
+Terminal=false
+Categories=AudioVideo;Audio;Player;

Bug#769792: eom: overwrites file permissions and group id

[Mike Gabriel]

Control: severity -1 important

Hi Stefan,

On  So 16 Nov 2014 14:31:53 CET, Stefan Frenzel wrote:


Package: eom
Version: 1.8.0+dfsg1-4+b2
Severity: normal

Dear Maintainer,

whenever updating an image, e.g. after rotating it, eom overwrites both file
permissions and group id. It seems to use an 7177 mask, that is only the
owner keeps access to the updated image. Because of this it is impossible to
share images between multiple users without having to manually reset file
permissions and/or group id.

This does not happen when using shotwell or gimp and imho it should not with
eom either.



This indeed can break collab workspace on shared file systems. Raising  
severity to important, as we should get this fixed in jessie.


Greets,
Mike

--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb


pgpbAy0HXWYxo.pgp
Description: Digitale PGP-Signatur

Bug#646847: Redirection: interval file descriptor (0-9)

[Herbert Xu]

Stéphane Aulery  wrote:
> [-- text/plain, encoding 8bit, charset: utf-8, 12 lines --]
> 
> Hello,
> 
> Here is a small patch reported by a user of Debian [1]. Could you please
> integrate? Thank you for your help.
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646847

Applied.
-- 
Email: Herbert Xu 
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769828: initramfs-tools: usb keyboard nonfunctional in initramfs (break=premount) (MODULES=most)

[Zack Weinberg]

On 11/16/2014 09:48 PM, Ben Hutchings wrote:
> [...]
> 
> I am very surprised that the keyboard is not functional.  Based on the
> lsmod output, your keyboard driver is hid-microsoft and that will be
> included in the initramfs.

$ lsinitramfs /boot/initrd.img-3.16.0-4-amd64 | grep drivers/usb
lib/modules/3.16.0-4-amd64/kernel/drivers/usb
lib/modules/3.16.0-4-amd64/kernel/drivers/usb/common
lib/modules/3.16.0-4-amd64/kernel/drivers/usb/common/usb-common.ko
lib/modules/3.16.0-4-amd64/kernel/drivers/usb/core
lib/modules/3.16.0-4-amd64/kernel/drivers/usb/core/usbcore.ko

zw


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769855: unblock: kdepimlibs/4:4.14.2-2

[Scott Kitterman]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package kdepimlibs

RC bug fix.  Note: This is a two part fix.  The other part is in
kdepim-runtime and will be requested in a separate unblock.  Both
have been tested and uploaded.

unblock kdepimlibs/4:4.14.2-2
diff -Nru kdepimlibs-4.14.2/debian/changelog kdepimlibs-4.14.2/debian/changelog
--- kdepimlibs-4.14.2/debian/changelog	2014-10-20 11:13:26.0 -0400
+++ kdepimlibs-4.14.2/debian/changelog	2014-11-16 22:38:20.0 -0500
@@ -1,3 +1,12 @@
+kdepimlibs (4:4.14.2-2) unstable; urgency=medium
+
+  * Team upload.
+  * Add new error code for ERR_SSL_FAILED to support fixing issue where
+connection via SSL using an unknown certificate could not be rejected
+(Closes: #769852)
+
+ -- Scott Kitterman   Sun, 16 Nov 2014 22:35:39 -0500
+
 kdepimlibs (4:4.14.2-1) unstable; urgency=medium
 
   * New upstream release (4.14.2).
diff -Nru kdepimlibs-4.14.2/debian/patches/series kdepimlibs-4.14.2/debian/patches/series
--- kdepimlibs-4.14.2/debian/patches/series	2014-10-20 11:13:26.0 -0400
+++ kdepimlibs-4.14.2/debian/patches/series	2014-11-16 22:40:13.0 -0500
@@ -1,2 +1,3 @@
 add_soname_to_xsd_file
 sslv2_disabled.patch
+tlscancelled.patch
diff -Nru kdepimlibs-4.14.2/debian/patches/tlscancelled.patch kdepimlibs-4.14.2/debian/patches/tlscancelled.patch
--- kdepimlibs-4.14.2/debian/patches/tlscancelled.patch	1969-12-31 19:00:00.0 -0500
+++ kdepimlibs-4.14.2/debian/patches/tlscancelled.patch	2014-11-16 22:41:40.0 -0500
@@ -0,0 +1,42 @@
+Description: Add SSL specific error type on SSL error
+ Add debian/patches/tlscancelled.patch to fix issue with inability to
+ cancel connections using unknown SSL certificates (Closes: #769852)
+Origin: vendor
+Author: Jim Scadden 
+Bug-Debian: http://bugs.debian.org/769852
+Bug: https://bugs.kde.org/show_bug.cgi?id=335994
+Forwarded: https://bugs.kde.org/show_bug.cgi?id=335994
+Reviewed-By: Scott Kitterman 
+Last-Update: 2014-11-16
+
+--- kdepimlibs-4.14.2.orig/kimap/loginjob.cpp
 kdepimlibs-4.14.2/kimap/loginjob.cpp
+@@ -535,7 +535,7 @@ void LoginJobPrivate::sslResponse(bool r
+ authState = LoginJobPrivate::Capability;
+ tags << sessionInternal()->sendCommand( "CAPABILITY" );
+   } else {
+-q->setError( LoginJob::UserDefinedError );
++q->setError( LoginJob::ERR_SSL_FAILED );
+ q->setErrorText( i18n( "Login failed, TLS negotiation failed." ) );
+ encryptionMode = LoginJob::Unencrypted;
+ q->emitResult();
+@@ -597,7 +597,6 @@ void LoginJob::connectionLost()
+   emitResult();
+ }
+   }
+-
+ }
+ 
+ void LoginJobPrivate::saveServerGreeting(const Message &response)
+--- kdepimlibs-4.14.2.orig/kimap/loginjob.h
 kdepimlibs-4.14.2/kimap/loginjob.h
+@@ -61,7 +61,8 @@ class KIMAP_EXPORT LoginJob : public Job
+ };
+ 
+ enum ErrorCode {
+-  ERR_COULD_NOT_CONNECT = KJob::UserDefinedError + 23 // same as in kio
++  ERR_COULD_NOT_CONNECT = KJob::UserDefinedError + 23, // same as in kio
++  ERR_SSL_FAILED = KJob::UserDefinedError + 128,  // outside of values used by kio
+ };
+ 
+ explicit LoginJob( Session *session );

Bug#769857: unblock: kdepim-runtime/4:4.14.2-2

[Scott Kitterman]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package kdepim-runtime

RC bug fix.  Note that this is part two of the fix.  Part one is in
kdepimlibs and subject of a different unblock request.

unblock kdepim-runtime/4:4.14.2-2
diff -Nru kdepim-runtime-4.14.2/debian/changelog kdepim-runtime-4.14.2/debian/changelog
--- kdepim-runtime-4.14.2/debian/changelog	2014-10-20 11:13:02.0 -0400
+++ kdepim-runtime-4.14.2/debian/changelog	2014-11-16 22:44:21.0 -0500
@@ -1,3 +1,13 @@
+kdepim-runtime (4:4.14.2-2) unstable; urgency=medium
+
+  * Team upload.
+  * Add debian/patches/tlscancelled.patch to fix issue with inability to
+cancel connections using unknown SSL certificates (Closes: #750995)
+  * Bump minimum kdepimlibs5-dev build-depends version to 4:4.14.2-2~
+in order to ensure the added enum is available
+
+ -- Scott Kitterman   Sun, 16 Nov 2014 22:14:26 -0500
+
 kdepim-runtime (4:4.14.2-1) unstable; urgency=medium
 
   * New upstream release (4.14.2).
diff -Nru kdepim-runtime-4.14.2/debian/control kdepim-runtime-4.14.2/debian/control
--- kdepim-runtime-4.14.2/debian/control	2014-10-20 11:13:02.0 -0400
+++ kdepim-runtime-4.14.2/debian/control	2014-11-16 22:43:51.0 -0500
@@ -11,7 +11,7 @@
debhelper (>= 9),
kde-sc-dev-latest (>= 4:4.12),
kdelibs5-dev (>= 4:4.12),
-   kdepimlibs5-dev (>= 4:4.14.0),
+   kdepimlibs5-dev (>= 4:4.14.2-2~),
libakonadi-dev (>= 1.12.90),
libboost-dev (>= 1.40.0-2),
libkgapi-dev (>= 2.2.0),
diff -Nru kdepim-runtime-4.14.2/debian/patches/series kdepim-runtime-4.14.2/debian/patches/series
--- kdepim-runtime-4.14.2/debian/patches/series	2014-10-20 11:13:02.0 -0400
+++ kdepim-runtime-4.14.2/debian/patches/series	2014-11-16 22:22:40.0 -0500
@@ -1,2 +1,3 @@
 hide_akonaditray.diff
 kolabproxy_unittest
+tlscancelled.patch
diff -Nru kdepim-runtime-4.14.2/debian/patches/tlscancelled.patch kdepim-runtime-4.14.2/debian/patches/tlscancelled.patch
--- kdepim-runtime-4.14.2/debian/patches/tlscancelled.patch	1969-12-31 19:00:00.0 -0500
+++ kdepim-runtime-4.14.2/debian/patches/tlscancelled.patch	2014-11-16 22:27:43.0 -0500
@@ -0,0 +1,25 @@
+Description: Use SSL specific error type on SSL error
+ Add debian/patches/tlscancelled.patch to fix issue with inability to
+ cancel connections using unknown SSL certificates (Closes: #750995)
+Origin: vendor
+Author: Jim Scadden 
+Bug-Debian: http://bugs.debian.org/750995
+Bug: https://bugs.kde.org/show_bug.cgi?id=335994
+Forwarded: https://bugs.kde.org/show_bug.cgi?id=335994
+Reviewed-By: Scott Kitterman 
+Last-Update: 2014-11-16
+
+--- kdepim-runtime-4.14.2.orig/resources/imap/sessionpool.cpp
 kdepim-runtime-4.14.2/resources/imap/sessionpool.cpp
+@@ -377,6 +377,11 @@ void SessionPool::onLoginDone( KJob *job
+i18n( "Could not connect to the IMAP-server.\n%1",
+  job->errorString() ) );
+   }
++} else if ( job->error() == KIMAP::LoginJob::ERR_SSL_FAILED ) {
++  cancelSessionCreation( login->session(),
++ EncryptionError,
++ i18n( "Could not connect to the IMAP-server %1.\n%2",
++   m_account->server(), job->errorString() ) );
+ } else {
+   // Connection worked, but login failed -> ask for a different password or ssl settings.
+   m_pendingInitialSession = login->session();

Bug#769856: unblock: mariadb-10.0/10.0.14-3

[Arnaud Fontaine]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package mariadb-10.0

This fixes 2 RC bugs. Here is the changelog entry and debdiff with
further explanations:

  diff -Nru mariadb-10.0-10.0.14/debian/changelog 
mariadb-10.0-10.0.14/debian/changelog
  --- mariadb-10.0-10.0.14/debian/changelog 2014-10-22 05:49:56.0 
+0900
  +++ mariadb-10.0-10.0.14/debian/changelog 2014-11-14 11:11:44.0 
+0900
  @@ -1,3 +1,11 @@
  +mariadb-10.0 (10.0.14-3) unstable; urgency=low
  +
  +  * Added patch d/username-in-tests-replace.patch to fix
  +test failure (Closes: #769212).
  +  * Added versioned dependency on libpcre3 (Closes: #767903).
  +
  + -- Otto Kekäläinen   Wed, 12 Nov 2014 15:00:11 +0300
  +
   mariadb-10.0 (10.0.14-2) unstable; urgency=low
   
 [ Tobias Frost ]
  diff -Nru mariadb-10.0-10.0.14/debian/control 
mariadb-10.0-10.0.14/debian/control
  --- mariadb-10.0-10.0.14/debian/control   2014-10-22 05:42:47.0 
+0900
  +++ mariadb-10.0-10.0.14/debian/control   2014-11-14 11:11:44.0 
+0900
  @@ -14,7 +14,7 @@
  libjudy-dev,
  libncurses5-dev (>= 5.0-6~),
  libpam0g-dev,
  -   libpcre3-dev,
  +   libpcre3-dev (>= 1:8.35),
  libreadline-gplv2-dev,
  libwrap0-dev (>= 7.6-8.3~),
  lsb-release,
  @@ -31,8 +31,7 @@
   Architecture: any
   Section: libdevel
   Pre-Depends: ${misc:Pre-Depends}
  -Depends: ${misc:Depends},
  - ${shlibs:Depends}
  +Depends: ${misc:Depends}, ${shlibs:Depends}
   Breaks: libmysqld-dev
   Replaces: libmysqld-dev
   Description: MariaDB embedded database development files
  @@ -58,9 +57,7 @@
   
   Package: mariadb-client-core-10.0
   Architecture: any
  -Depends: mariadb-common,
  - ${misc:Depends},
  - ${shlibs:Depends}
  +Depends: mariadb-common, ${misc:Depends}, ${shlibs:Depends}
   Conflicts: mysql-client-5.5, mysql-client-5.6
   Breaks: mariadb-client-core-5.5,
   mysql-client-core-5.5,
  diff -Nru mariadb-10.0-10.0.14/debian/patches/series 
mariadb-10.0-10.0.14/debian/patches/series
  --- mariadb-10.0-10.0.14/debian/patches/series2014-10-03 
06:46:10.0 +0900
  +++ mariadb-10.0-10.0.14/debian/patches/series2014-11-14 
11:11:44.0 +0900
  @@ -1,3 +1,4 @@
  +username-in-tests-replace.patch
   kfreebsd_tests.patch
   disable-buggy-tokudb-tests.patch
   scripts__mysql_create_system_tables__no_test.patch
  diff -Nru mariadb-10.0-10.0.14/debian/patches/username-in-tests-replace.patch 
mariadb-10.0-10.0.14/debian/patches/username-in-tests-replace.patch
  --- mariadb-10.0-10.0.14/debian/patches/username-in-tests-replace.patch   
1970-01-01 09:00:00.0 +0900
  +++ mariadb-10.0-10.0.14/debian/patches/username-in-tests-replace.patch   
2014-11-14 11:11:44.0 +0900
  @@ -0,0 +1,72 @@
  +Description: Closes #769212: mariadb-10.0: FTBFS in jessie: Tests failures
  + Reported a bug upstream and backported their fix that will also be included
  + in next upstream release (10.0.15). The root cause was the usage of username
  + 'user' on the Debian rebuilder, which wasn't a supported username until now.
  + .
  + MDEV-7089: Test failures in main.failed_auth_unixsocket and 
plugins.unix_socket
  + depending on environment
  + .
  + The test cases had some --replace_result $USER USER. The problem is that the
  + value of $USER can be anything, depending on the name of the unix account 
that
  + runs the test suite. So random parts of the result can be errorneously
  + replaced, causing test failures.
  + .
  + Fix by making the replacements more specific, so they will match only the
  + intended stuff regardless of the value of $USER.
  +Author: Kristian Nielsen 
  +Bug: https://mariadb.atlassian.net/browse/MDEV-7089
  +Last-Update: 2014-11-12
  +
  +=== modified file 'mysql-test/suite/plugins/t/unix_socket.test'
  +--- a/mysql-test/suite/plugins/t/unix_socket.test2014-03-16 18:21:37 
+
   b/mysql-test/suite/plugins/t/unix_socket.test2014-11-12 10:10:13 
+
  +@@ -12,11 +12,14 @@ eval install plugin unix_socket soname '
  + --echo # with named user
  + --echo #
  + 
  +---replace_result $USER USER
  ++--let $replace=create user $USER
  ++--replace_result $replace "create user USER"
  + eval create user $USER identified via unix_socket;
  + 
  + --write_file $MYSQLTEST_VARDIR/tmp/peercred_test.txt
  +---replace_result $USER USER
  ++--let $replace1=$USER at localhost
  ++--let $replace2=$USER@%
  ++--replace_result $replace1 "USER at localhost" $replace2 "USER@%"
  + select user(), current_user(), database();
  + EOF
  + 
  +@@ -31,7 +34,8 @@ EOF
  + --error 1
  + --exec $MYSQL_TEST -u foobar --plugin-dir=$plugindir < 
$MYSQLTEST_VARDIR/tmp/peercred_test.txt
  + 
  +---replace_result $USER USER
  ++--let $replace=drop user $USER
  ++--replace_result $replace "d

Bug#769854: unblock: zodb/1:3.9.7-3

[Arnaud Fontaine]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package zodb

This fixes an error when trying to install it together with
python-persistent and also add a Provides, here is the changelog entry
with further explanations:

  diff -Nru zodb-3.9.7/debian/changelog zodb-3.9.7/debian/changelog
  --- zodb-3.9.7/debian/changelog   2011-11-08 22:53:42.0 +0900
  +++ zodb-3.9.7/debian/changelog   2014-11-17 12:10:50.0 +0900
  @@ -1,3 +1,14 @@
  +zodb (1:3.9.7-3) unstable; urgency=medium
  +
  +  * Team upload.
  +  * d/control: ZODB3 >= 3.11a1 (python-zodb in Debian) has been split up
  +into distinct packages (persistent, BTrees, ZODB and ZEO), so until
  +python-zodb is updated to at least that version (eg after Jessie), add
  +a Conflicts and Provides of python-persistent. Thanks to Andreas
  +Beckmann. Closes: #767554.
  +
  + -- Arnaud Fontaine   Fri, 14 Nov 2014 18:34:36 +0900
  +
   zodb (1:3.9.7-2) unstable; urgency=low
   
 * Team upload.
  diff -Nru zodb-3.9.7/debian/control zodb-3.9.7/debian/control
  --- zodb-3.9.7/debian/control 2011-10-21 14:24:36.0 +0900
  +++ zodb-3.9.7/debian/control 2014-11-17 12:09:52.0 +0900
  @@ -20,9 +20,12 @@
${python:Depends},
${misc:Depends},
${shlibs:Depends}
  -Provides: ${pydeb:Provides}, ${python:Provides}
  +Provides: ${pydeb:Provides},
  +  ${python:Provides},
  +  python-persistent
   Suggests: ${pydeb:Suggests}
  -Conflicts: zope3
  +Conflicts: zope3,
  +   python-persistent
   Description: Zope Object Database (ZODB)
The Zope Object Database is an object-oriented database for Python that
provides a high-degree of transparency. Applications can take advantage of

Thanks in advance!

unblock zodb/1:3.9.7-3

Regards,
-- 
Arnaud Fontaine


signature.asc
Description: PGP signature

Bug#769853: unblock: python-persistent/4.0.8-2

[Arnaud Fontaine]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package python-persistent

This fixes an error when trying to install it together with python-zodb,
here is the changelog entry with further explanations:

  diff -Nru python-persistent-4.0.8/debian/changelog 
python-persistent-4.0.8/debian/changelog
  --- python-persistent-4.0.8/debian/changelog  2014-06-26 04:29:59.0 
+0900
  +++ python-persistent-4.0.8/debian/changelog  2014-11-14 18:30:25.0 
+0900
  @@ -1,3 +1,13 @@
  +python-persistent (4.0.8-2) unstable; urgency=medium
  +
  +  * Team upload.
  +  * d/control: ZODB3 >= 3.11a1 (python-zodb in Debian) has been split up
  +into distinct packages (persistent, BTrees, ZODB and ZEO), so until
  +python-zodb is updated to at least that version (eg after Jessie), add
  +a Conflicts. Thanks to Andreas Beckmann. Closes: #767554.
  +
  + -- Arnaud Fontaine   Fri, 14 Nov 2014 18:22:35 +0900
  +
   python-persistent (4.0.8-1) unstable; urgency=medium
   
 * Initial release. (Closes: #752679)
  diff -Nru python-persistent-4.0.8/debian/control 
python-persistent-4.0.8/debian/control
  --- python-persistent-4.0.8/debian/control2014-06-26 00:34:29.0 
+0900
  +++ python-persistent-4.0.8/debian/control2014-11-14 18:31:01.0 
+0900
  @@ -22,6 +22,7 @@
   Package: python-persistent
   Architecture: any
   Depends: ${misc:Depends}, ${python:Depends}, ${shlibs:Depends}
  +Conflicts: python-zodb (<< 3.11.0~)
   Description: Automatic persistence for Python objects
This package contains a generic persistence implementation for Python. It
forms the core protocol for making objects interact "transparently" with

Thanks in advance!

unblock python-persistent/4.0.8-2

Regards,
-- 
Arnaud Fontaine


signature.asc
Description: PGP signature

Bug#767554: python-persistent and python-zodb: error when trying to install together

[Arnaud Fontaine]

Hi,

Gediminas Paulauskas  writes:

>> If that's ok with you, I'm going to upload both packages to fix this bug:
>>
>> * python-persistent:
>>   Conflicts: python-zodb (<< 3.11.0~)
>>
>> * python-zodb:
>>   Conflicts: python-persistent
>>
>
> Since ZODB3 before the split included persistent, it should provide it:
>
> Provides: python-persistent
>
> One package that Build-Depends on python-persistent but should be
> installable with only python-zodb is zope.component.

Thank you very much for pointing this out. I will upload now with the
Provides then.

Cheers,
-- 
Arnaud Fontaine


signature.asc
Description: PGP signature

Bug#769828: initramfs-tools: usb keyboard nonfunctional in initramfs (break=premount) (MODULES=most)

[Zack Weinberg]

On 11/16/2014 09:48 PM, Ben Hutchings wrote:
> 
> I am very surprised that the keyboard is not functional.  Based on the
> lsmod output, your keyboard driver is hid-microsoft and that will be
> included in the initramfs.
> 
> If this system has some sockets that don't support USB 3, could you test
> whether the keyboard works when attached to them?  (The plastic inside a
> USB socket should be blue if it supports USB 3, and some other colour if
> it doesn't.)

It appears already to have been plugged into such a socket (the plastic
inside is black, anyway).  Is there some way I can confirm this from
software?

zw




signature.asc
Description: OpenPGP digital signature

Bug#767893: Info received (more info)

[John Holland]

I have tested more, I realized the problem I mentioned of ZFS
filesystems going away is due to my not building them from UUIDs
instead of device names like /dev/vdb - that is, the device names are
bad because they're not consistently mapped from boot to boot.


My bug is produced in the following way:

install jessie netinst in a kvm vm, all in one partition, two spare
virtio disks to use later for zfs - minimal packages

apt-get update, apt-get upgrade

Install desktop environment (KDE, I don't like gnome 3)

(apt-get install plasma-desktop, which takes a while)

shutdown and copy disk image to backup




apt-get install linux-headers-amd64

apt-get install linux-image (version to match headers)   and chromium

browse to zfsonlinux.org

download .deb for jessie , follow instructions to install

apt-get install cryptsetup plymouth plymouth-themes

edit /etc/plymouth/plymouthd.conf so that theme = details

make sure it runs update-initramfs   (or run update-initramfs -uk all)

cryptsetup luksFormat /dev/vdb  and again for /dev/vdc

edit /etc/crypttab to:
vdbb /dev/vdb none luks
vdcc /dev/vdc none luks


cryptsetup luksOpen /dev/vdb vdbb
cryptsetup luksOpen /dev/vdc vdcc

zpool create encpool /dev/mapper/vdbb /dev/mapper/vdcc 

mkdir /mnt/b

zfs create encpool/b

zfs set mountpoint=/mnt/b encpool/b

reboot, system prompts for passwords for encrypted volumes and /mnt/b
is mounted 

zfs create encpool/varr

mv /var /oldvar

mkdir /var

zfs set mountpoint=/var enchome/varr

cp -a /oldvar/* /var/


reboot - cryptsetup prompts are overwritten and it is difficult to
enter the passwords
/var is not mounted because it has been written to already.
Manual cryptsetup and mount commands etc needed to work at this point.


John Goerzen wrote something about this at
http://changelog.complete.org/
and he said that putting the zfs var volume on mountpoint=legacy and
mounting it in  /etc/fstab would work, but it has not for me. 
What I'm finding is that any zfs entry in fstab makes the password
entry at boot impossible and if it is a filesystem that is needed to
start up this creates a lot of problems.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769828: initramfs-tools: usb keyboard nonfunctional in initramfs (break=premount) (MODULES=most)

[Ben Hutchings]

Control: tag -1 moreinfo

On Sun, 2014-11-16 at 15:47 -0500, Zack Weinberg wrote:
> Package: initramfs-tools
> Version: 0.118
> Severity: normal
> 
> If I set break=premount to drop into the initramfs embedded shell
> (I have not tested other values of break=) I see a bunch of error messages
> about various USB-related modules not being in modules.dep, and then the
> (USB-based) keyboard is completely nonfunctional and the computer has
> to be reset using the hardware reset button.

Before starting a shell, the initramfs init script currently tries to
load many modules for different USB controller drivers, and not all of
them are actually built for any particular architecture.  So it is
expected that some of them will fail to load, but we ought to do
something to avoid those error messages.

> I played around with adding the missing modules to 
> /etc/initramfs-tools/modules
> but was not able to find a combination that worked.  The closest I got
> was with xhci_hcd + usbhid; then I see plausible-looking kernel probe
> messages for the USB hub and the keyboard, but after that the keyboard
> is still completely nonfunctional.
> 
> The keyboard does work just fine in single-user mode, so I presume this is
> indeed a problem with necessary modules not getting loaded.
> 
> I am using MODULES=most, so this is not the same as #701656.
[...]

I am very surprised that the keyboard is not functional.  Based on the
lsmod output, your keyboard driver is hid-microsoft and that will be
included in the initramfs.

If this system has some sockets that don't support USB 3, could you test
whether the keyboard works when attached to them?  (The plastic inside a
USB socket should be blue if it supports USB 3, and some other colour if
it doesn't.)

Ben.

-- 
Ben Hutchings
Any smoothly functioning technology is indistinguishable from a rigged demo.


signature.asc
Description: This is a digitally signed message part

Bug#769851: ITP: puppetlabs-spec-helper -- Ruby library for puppet module testing

[Jordan Metzmeier]

Package: wnpp
Severity: wishlist
Owner: Jordan Metzmeier 

* Package name: puppetlabs-spec-helper
  Version : 0.8.2
  Upstream Author : Puppet Labs Inc 
* URL : https://github.com/puppetlabs/puppetlabs_spec_helper
* License : Apache
  Programming Lang: Ruby
  Description : Ruby modules for puppet module testing

This project is meant to provide a single source of truth for how to initialize
different Puppet versions for spec testing. Differences in puppet versions are 
handled
for you. Convenience classes are provided for things such as creating 
tempfiles, common rspec
matchers, etc.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769804: jarjar-maven-plugin: FTBFS against rebuilt packages: Failed to resolve artifact ant

[Daniel Schepler]

On Sun, Nov 16, 2014 at 11:26 AM, tony mancill  wrote:
> I believe what Daniel is saying is that if you rebuild the entire
> dependency chain, ant isn't being pulled in (by velocity).

That's correct.

> Or put another way, there is a difference between the dependency graph
> that exists for the binary build-deps in the archive, and the dependency
> graph created by rebuilding all of the build-deps in the archive from
> source.
>
> Daniel, first, do I have that right, and secondly, is your rebuild on
> jessie or sid?

The rebuild is based on sid.

By the way, after I built maven-jarjar-plugin with ant added, I got a
similar failure building sisu-guice:

[ERROR] BUILD ERROR
[INFO] 
[INFO] Failed to resolve artifact.

Missing:
--
1) org.apache.ant:ant:jar:debian

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.apache.ant
-DartifactId=ant -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there:
  mvn deploy:deploy-file -DgroupId=org.apache.ant -DartifactId=ant
-Dversion=debian -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]

  Path to dependency:
1) org.sonatype.plugins:jarjar-maven-plugin:maven-plugin:1.9
2) org.apache.ant:ant:jar:debian

--
1 required artifact is missing.

for artifact:
  org.sonatype.plugins:jarjar-maven-plugin:maven-plugin:1.9

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)



NOTE: Maven is executing in offline mode. Any artifacts not already in
your local
repository will be inaccessible.


[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 4 seconds
[INFO] Finished at: Sun Nov 16 22:29:05 UTC 2014
[INFO] Final Memory: 17M/344M
[INFO] 
/usr/share/cdbs/1/class/maven.mk:87: recipe for target 'mvn-build' failed
make: *** [mvn-build] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2

I'm not sure why that's happening, given that as far as I can tell,
the dependency on ant is marked as optional in jarjar-maven-plugin's
pom.xml file.
-- 
Daniel Schepler


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769589: debian-cd: Please improve .disk/cd_type for non-complete builds

[Steve McIntyre]

Hi Petter,

On Fri, Nov 14, 2014 at 08:52:49PM +0100, Petter Reinholdtsen wrote:
>
>Package: debian-cd
>Version: 3.1.16
>Tags: patch
>
>In Debian Edu, we use the .disk/cd_type content to decide if Internet
>connectivity is required or not.  And this work fine when we build ISOs
>trying to include the complete archive, but not when we limit the ISO to
>only have the packages we want.
>
>But by default debian-cd do not put any useful value in the file if
>COMPLETE=0.  Please change it to document the cd type also in this case,
>with the same keywords used in the complete case, to allow our grep
>calls to work.
>
>This is the patch we use at the moment to build the Debian Edu ISOs:

Interesting change; I'd be tempted to refactor things slightly in the
code, but that's a secondary thing. I'm more curious: what are the
ramifications for d-i? Have you investigated/tested?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"This dress doesn't reverse." -- Alden Spiess


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#767442: xfonts-terminus: powerline symbols missing from 4.39

[Andre Klärner]

reassign 767442 trscripts
tag + patch
thanks

Hi Anton,

after some more digging and reverse engineering I found out what caused the
missing symbols in the packages. They were stripped by the unicode_conv AWK
script during the build, as the unicode to unicode conversion is not
lossless.

Hence the problem is created by trbdf I patched the unicode charset
definition to include the Unicode Private Use Area (U+E000..U+F8FF).
I think the assumption that the private use area should be excluded is
wrong, as it's use depends on the communicating partners, and it is not up
to a tool to strip characters defined in the source.

I attached the patch that includes the full Private Use Area. After
rebuilding xfonts-terminus with the patched trbdf in place the caracter
become usable.

Regards,
Andre

-- 
Andre Klärner


smime.p7s
Description: S/MIME cryptographic signature

Bug#769850: libc6: file not showing up

[westlake]

Package: libc6
Version: 2.19-12
Severity: important

There's a bug somewhere, and as seemingly obvious what the problem may 
be to one who is "new" to using commands, listing things with "ls" as an 
experienced user should list everything that is actually stored on the 
drive.


simply,
(1) "ls -la" was issued , and the file of interest
"barnyard2_v2-1.13.tar.gz" did not display

(2) mv ../barnyard2_v2-1.13.tar.gz .

There's now a "prompt" to overwrite barnyard2_v2-1.13.tar.gz

With everything still visual on terminal display and double checking 
there was no file of this name in the current path as there was indeed 
no more than 10 items to quicky glance from output.


Again, with "everything still visual" -- meaning no scroll-up buffers 
with the terminal (which can sometimes cut display output) or anything, 
it was very clear "ls" was not outputting everything which is very odd.


furthermore to check things,
- There were no bash ls aliases, nor other "ls" in $PATH or other shell 
functions which could explain this

- Filesystem consistency was also in good state

..coreutils 8.23-3 here on jessie/testing which contains the ls command

Should I file a report to the coreutils package? I know there's a bug 
but currently I can't pinpoint exactly what may have caused this,


fwiw, something a couple weeks ago I filed upstream concerning two 
filenames in the same path, another very rare bug. 
https://bugzilla.kernel.org/show_bug.cgi?id=86541


^ If this is not an "ls" or an "libc" bug, then there indeed be a 
kernel/ext4 issue. I know there is nothing else that could be causing 
this (eg, faulty drive hardware), since this latest bugreport happened 
in VM which nullifies any hardware problems...


Simply, "ls -la", file XYZ not there, "mv ../XYZ ." now it's 
prompting to overwrite. Can still see everything from "ls -la", 
double-checked the few items listed, yup "XYZ" is again not there.


odd indeed.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#768775: wrong spaces in package description between paragraphs

[Eriberto]

Hi Davide,

Thanks a lot for your suggestion. I will consider it in next revision.

Cheers,

Eriberto


2014-11-09 6:37 GMT-02:00 Davide Prina :
> Package: volatility
> Severity: minor
>
> Dear Maintainer,
>
> in DDTP I see:
>
> These are some of the data that can be extracted from a memory image:
>.
>- Image information (date, time, CPU count);
>
>
> note the extra spaces between the 1st line and the 3th. I think these would
> be two paragraphs, but with spaces before the dot they are seen as only one
> paragraphs.
> I think that the 2nd line dot must be at line start and the correct one is:
>
> These are some of the data that can be extracted from a memory image:
> .
>- Image information (date, time, CPU count);
>
>
> Ciao
> Davide
>
> -- System Information:
> Debian Release: jessie/sid
>   APT prefers testing
>   APT policy: (1001, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 3.16-3-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
>
> ___
> forensics-devel mailing list
> forensics-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769849: unblock: redmine-plugin-pretend/0.0.2+git20130821-2

[Dmitry Smirnov]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

redmine-plugin-pretend/0.0.2+git20130821-2

Please unblock the above package.

It contains an essential Redmine compatibility adaptation which is necessary
to avoid the following error on start or upgrade of Redmine:


An error occurred while loading the routes definition of redmine_pretend plugin 
(/usr/share/redmine/plugins/redmine_pretend/config/routes.rb):
You should not use the `match` method in your router without specifying an HTTP 
method.
If you want to expose your action to both GET and POST, add `via: [:get, 
:post]` option.
If you want to expose your action to GET, use `get` in the router:
Instead of: match "controller#action"
Do: get "controller#action".
Error when running rake db:migrate, check database configuration.


Patch is trivial and only changes "match" to "get" in "config/routes.rb":


--- a/config/routes.rb
+++ b/config/routes.rb
@@ -1,8 +1,8 @@
 if Rails::VERSION::MAJOR >= 3
 RedmineApp::Application.routes.draw do
- match 'admin/pretend_to/:id' => 'application#pretend_to', :as => 'pretend_to'
- match 'admin/unpretend' => 'application#unpretend', :as => 'unpretend'
+ get 'admin/pretend_to/:id' => 'application#pretend_to', :as => 'pretend_to'
+ get 'admin/unpretend' => 'application#unpretend', :as => 'unpretend'
 end
 else
 ActionController::Routing::Routes.draw do |map|
 map.pretend_to 'admin/pretend_to/:id', :controller => 'application', :action 
=> 'pretend_to'


See full list of changes in repository:

http://anonscm.debian.org/cgit/collab-maint/redmine-plugin-pretend.git/log/

Thank you.

-- 
All the best,
 Dmitry Smirnov.


signature.asc
Description: This is a digitally signed message part.

Bug#769848: [postgresql-contrib-9.4] uuid-ossp strange parms

[Bzzzz]

Package: postgresql-contrib-9.4
Version: 9.4~beta3-3
Severity: normal

--- Please enter the report below this line. ---

Hi folks,

There are 2 Fn that pose a problem in this extension:
   uuid_generate_v3(namespace uuid, name text)
   uuid_generate_v5(namespace uuid, name text)
because pg_get_function_identity_arguments(func_oid)
and pg_get_function_arguments(func_oid) always return:
"namespace uuid, name text" as parameters instead of
"uuid, text".

This prevents to reconstitute these Fn full names in
an external python program (in order to grant or revoke
user rights.)

Jean-Yves

--- System information. ---
Architecture: amd64
Kernel:   Linux 3.16.0-4-amd64

Debian Release: jessie/sid
  500 unstablewww.deb-multimedia.org 
  500 unstableftp.fr.debian.org 
  500 trusty  ppa.launchpad.net 

--- Package information. ---
Depends  (Version) | Installed
==-+-
postgresql-9.4 (= 9.4~beta2-1) | 9.4~beta3-3
libc6(>= 2.15) | 2.19-13
libpq5  (>= 9.2~beta3) | 9.4~beta3-3
libselinux1(>= 2.1.12) | 2.3-2
libssl1.0.0 (>= 1.0.0) | 1.0.1j-1
libuuid1 (>= 2.16) | 2.25.2-2
libxml2 (>= 2.7.4) | 2.9.2+dfsg1-1
libxslt1.1 (>= 1.1.25) | 1.1.28-2+b2
zlib1g(>= 1:1.1.4) | 1:1.2.8.dfsg-2


Package's Recommends field is empty.

Suggests(Version) | Installed
=-+-===
libdbd-pg-perl| 3.4.2-1


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769395: [Ceph-maintainers] Bug#769395: ceph-dkms: module FTBFS for kernel 3.16.0-4

[Dmitry Smirnov]

On Fri, 14 Nov 2014 14:18:07 Gaudenz Steinlin wrote:
> I just think there is not much point in keeping a package that's not updated
> and obsolete.

Who would argue with that? ;)


> It was not obvious to me that ceph-dkms is intended to always stay in
> experimental. If it's not intended to ever go into
> unstable/testing/stable I see no problem with the current state.

Depending on situation I think uploading to "unstable" may be potentially 
acceptable (in case of serious problem in kernel until fix is available in 
mainline). If I ever upload it to "unstable" I will file a bug to prevent 
migration to "testing".


> If things really fail miserably I would prefer to have the relevant
> patches in a stable kernel update though. AFAIK the Debian kernel
> maintainers are open to adding backported fixes that are included into
> the upstream kernel in later versions.

Well that's where I think DKMS package could be useful. For example before 
3.16 was released I experienced a range of problems from "read errors and 
corruption of data in RBD images" to "feature mismatch" with kernel 3.14.
DKMS package helped me to answer questions like

 * Is this problem fixed upstream?
 * Does the fix work?
 * Which fix to backport?
 * Is backport feasible or is upgrading to newer kernel is the only option?

Besides early versions of kernels 3.16 had regressions leading to corruption 
of data on Btrfs and NFS4 so upgrading was not wise. During this transitional 
period when 3.16 was stabilising I could only use RBD with DKMS modules on 
3.14.

Now 3.16 is better but I gave up kernel clients (RBD, CephFS) as they are 
still not up to my expectations and I have a feeling that kernel clients are 
not a priority for upstream and that upstream actively works on new kernels 
but not that active on backporting fixes...

-- 
Best wishes,
 Dmitry Smirnov.

---

The more false we destroy the more room there will be for the true.
 -- Robert G. Ingersoll, 1902


signature.asc
Description: This is a digitally signed message part.

Bug#769791: wine32 doesn't work after fresh install

[jre]

control: tags -1 patch


Hi,

[my answer/patch is based upon the mentioned #739863, otherwise we
really need more info from Andi:]


1.)
this happens in wine-wrapper (regedit, regsvr32, wineboot, winecfg,
winefile, winepath), but not in wine/wine32/wine64.

So "wineboot" fails with:
  cat: /home/jens/.wine/system.reg: No such file or directory
  /usr/bin/wineboot: 32: exec: wineboot.exe: not found

while "wine wineboot" or "wine32 wineboot" work. Instead of wineboot a
normal windows exe also works fine here.



2.)
... and only if "$WINEPREFIX/system.reg" is missing.

IF WINEARCH is not specified, then "$WINEPREFIX/system.reg" is used to
figure out which wine to use (wine32 or wine64). After a fresh install
obviously system.reg

With attached patch (taken from #739863) wine-wrapper falls back to
using /usr/bin/wine if system.reg is missing. This will then again
choose wine32, unless WINELOADER is specified.


Of course this is only a fix. In the long run (= wine(-development) post
Jessie) I'd suggest to move all 32/64-bit logic to wine(-development).
So add the system.reg test there, next to the existing WINEARCH and
WINELOADER tests and probably add a PE32+ check (for 64-bit binfmt
support, #769234.) Or should I post a patch for this now?


Mike, the git repository is out of date:
branch jessie is at "release 1.6.2-15" (while 1.6.2-16 is current)


Greets
jre
diff --git a/debian/scripts/wine-wrapper b/debian/scripts/wine-wrapper
index 95d2c8f..5c9a3f4 100644
--- a/debian/scripts/wine-wrapper
+++ b/debian/scripts/wine-wrapper
@@ -24,7 +24,11 @@ appname=`basename "$0" .exe`.exe
 
 if test -z $WINEARCH; then
 test ! -z "$WINEPREFIX" || WINEPREFIX="$HOME/.wine"
-wine=$(cat "$WINEPREFIX/system.reg" | grep ^\#arch= | cut -d= -f2 | sed s/win/wine/)
+if test -f "$WINEPREFIX/system.reg"; then
+wine=$(cat "$WINEPREFIX/system.reg" | grep ^\#arch= | cut -d= -f2 | sed s/win/wine/)
+else
+wine=/usr/bin/wine
+fi
 else
 wine=$(echo "$WINEARCH" | sed s/win/wine/)
 fi

Bug#769596: ceph: README.Debian suggests invalid command

[Dmitry Smirnov]

Control: tags -1 unreproducible

On Sun, 16 Nov 2014 16:17:27 Gaudenz Steinlin wrote:
> >  * Set 'hashpspool' flag on your pools (new default):
> > ceph osd pool set {pool} hashpspool true
> But on the other hand I could not find any information about why this
> should be run on upgrades. The documentation for this is very sparse.
> Dimitry do you know what sort of problems this command solves and why it
> should be run?

Running this command is not mandatory but since it affects distribution of 
data IMHO it make sense to set "hashpspool" just like you would adjust 
tunables after upgrade. New pools are created with "hashpspool" by default so 
I believe it just makes sense to update configuration of old pools.

-- 
All the best,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B

---

All that is necessary for the triumph of evil is that good men do nothing.


signature.asc
Description: This is a digitally signed message part.

Bug#769843: dpkg-maintscript-helper: Wrong pre-dependency information in man page

[Guillem Jover]

Hi!

On Mon, 2014-11-17 at 00:34:48 +0100, Stefan Fritsch wrote:
> Package: dpkg
> Version: 1.17.21
> Severity: normal

> The dpkg-maintscript-helper man page claims that symlink_to_dir needs
> Pre-Depends: dpkg (>= 1.17.5). But the relative symlink feature in
> symlink_to_dir was introduced in 1.17.14. This should be noted in the
> man page.

Yeah, I also noticed this the other day. Also the fixes for
dir_to_symlink to work with relative symlinks were added in 1.17.13.

> A package that follows the man page is RC buggy. Therefore filing this
> as severity normal, not minor.

I've fixed this now locally by bumping the version for both symlink
commands to just 1.17.14, which avoids translation work, and
targetting 1.17.22.

Thanks,
Guillem


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#757772: RFP: widevineplugin-nonfree: Widevine DRM Plugin - browser plugin

[Patrick Buick]

I noted when running google-chrome-stable 38.0.2125.122 on fully 
upgraded Wheezy that the widevine plugin doesn't load because of a 
dependency on glibc_2.15 and Wheezy is currently only at 2.13, so it 
still doesn't work.


On Mon, 11 Aug 2014 10:38:15 +0100 Franz Schrober 
 wrote:

> Package: wnpp
> Severity: wishlist
>
>
> Package name: widevineplugin-nonfree
> URL:  https://tools.google.com/dlpage/widevine
> License:  proprietary non-free
>
> The google chrome version 38 now provides libwidevinecdm.so and 
libwidevinecdmadapter.so which are (pepper?) plugins used to view things 
like Netflix through their HTML5 player [1]. It may need a package like 
pepperflashplugin-nonfree which has a script to automatically extract 
the plugins and installs it to the right place.

>
>
> [1] http://www.phoronix.com/scan.php?page=news_item&px=MTc1ODY
>
>
>


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769847: amule: Uses absolute obsolete path for dpkg-divert

[Guillem Jover]

Source: amule
Source-Version: 2.3.1+git1a369e47-2
Severity: important

Hi!

The amule and amule-utils packages are using obsolete absolute paths when
calling dpkg-divert. Those have been compatibility symblinks for a while
and got removed in dpkg 1.17.0, I'll reintroduce them in dpkg 1.17.22 but
will be removing them again in 1.18.x.

Please stop using absolute paths in maintainer scripts, as they will
suffer this kind of problem. For more info please see:



Thanks,
Guillem


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769846: unblock: radiotray/0.7.3-3

[Elías Alejandro]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Dear release team,

Please unblock package radiotray

Reason:
Added dependency gstreamer0.10-plugins-bad to works properly and fix 
bug #766059

Debdiff attached.

unblock radiotray/0.7.3-3

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.17.0-eudyptula+ (SMP w/2 CPU cores)
Locale: LANG=es_PE.UTF-8, LC_CTYPE=es_PE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


Best regards,

--
Elías Alejandro
diff -Nru radiotray-0.7.3/debian/changelog radiotray-0.7.3/debian/changelog
--- radiotray-0.7.3/debian/changelog	2014-09-28 13:30:38.0 -0500
+++ radiotray-0.7.3/debian/changelog	2014-11-04 09:32:45.0 -0500
@@ -1,3 +1,10 @@
+radiotray (0.7.3-3) unstable; urgency=low
+
+  * debian/control
++ Add gstreamer0.10-plugins-bad dependency (Closes: #766059)
+
+ -- Elías Alejandro Año Mendoza   Tue, 04 Nov 2014 09:28:31 -0500
+
 radiotray (0.7.3-2) unstable; urgency=low
 
   * debian/control
diff -Nru radiotray-0.7.3/debian/control radiotray-0.7.3/debian/control
--- radiotray-0.7.3/debian/control	2014-09-27 09:29:17.0 -0500
+++ radiotray-0.7.3/debian/control	2014-11-04 09:22:46.0 -0500
@@ -18,7 +18,8 @@
  python-xdg, python-gobject (>= 2.18.0), python-notify (>= 0.1.1),
  python-gst0.10 (>= 0.10), python-glade2, python-lxml (>= 2.1.5),
  python-dbus (>= 0.83.0), gstreamer0.10-plugins-base (>= 0.10),
- gstreamer0.10-plugins-good, gstreamer0.10-plugins-ugly
+ gstreamer0.10-plugins-good, gstreamer0.10-plugins-ugly,
+ gstreamer0.10-plugins-bad
 Description: online radio streaming player
  This is a simple music streaming player that lives on the system tray.
  By clicking on the RadioTray icon, you'll be presented with a list of

Bug#769845: lintian: False negatives on command-with-path-in-maintainer-script

[Guillem Jover]

Package: lintian
Version: 2.5.31
Severity: normal

Hi!

It seems the command-with-path-in-maintainer-script check is failing
to detect several such instances in maintainer scripts. I removed some
compat symlinks in dpkg some time ago, after the lintian site stopped
reporting any hit. But it seems there's still several missing, as
found by codesearch.debian.net.

See  for
more details.

Thanks,
Guillem


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769624: Major Security Flaw when viewing WebM videos.

[James Galizio]

On Sun, 16 Nov 2014 13:04:27 +0100 Yves-Alexis Perez 
wrote:
> On dim., 2014-11-16 at 10:48 +0100, Sebastian Dröge wrote:
> > On Sa, 2014-11-15 at 12:01 -0800, James Galizio wrote:
> > > Also; just ran iceweasel through the terminal and recreated the steps
to
> > > the crash. Terminal output below.
> > > [...]
> > > Segmentation fault
> > >
> > > That last line makes me believe that this isn't fixed yet; and in any
case,
> > > having the browser crash is still a bug, no?
> >
> > [Also CC'ing Yves-Alexis who reported the other bug]
> >
> > Definitely, yes. The patch from the other bug is applied, which is
> > supposed to be the fix for the CVE though. Unfortunately the only
> > reference to the fix that I can find is in the Debian bug report as the
> > Mozilla Bugzilla Bug is still non-public. Maybe there are more related
> > changes that were forgotten?
> >
> > Do you know anything about that? :)
> >
> > Also you you get a backtrace of the segfault to see where exactly it
> > comes from?
>
> And are you sure packages for that “crunchbang GNU/Linux” are really
> identical to the Debian ones?
> --
> Yves-Alexis

Crunchbang has a separate repo for Crunchbang specific packages; but shares
the vast majority of its packages (>99%, including all major system
libraries) with debian mainline. It uses the official debian repos. When I
said I was using the latest version of iceweasel from the experimental
branch, I meant it.

Also; apologies for not recording the error through gdb. Here's the log
that should have been posted; I have a longer version of it if need be, but
this seems to be the portion that is relevant to the current issue.

[New Thread 0x7fffbcdff700 (LWP 13614)]
[New Thread 0x7fffbc5fe700 (LWP 13615)]
[New Thread 0x7fffbbdfd700 (LWP 13616)]
[New Thread 0x7fffbb3ff700 (LWP 13617)]
[Thread 0x7fffbc5fe700 (LWP 13615) exited]
[Thread 0x7fffd03ff700 (LWP 13597) exited]
[New Thread 0x7fffba7ff700 (LWP 13618)]
[New Thread 0x7fffbc5fe700 (LWP 13619)]
[New Thread 0x7fffd03ff700 (LWP 13620)]
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve
property `GtkRange::activate-slider' of type `gboolean' from rc file value
"((GString*) 0x7fffda1f9660)" of type `GString'
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve
property `GtkRange::activate-slider' of type `gboolean' from rc file value
"((GString*) 0x7fffda1f9660)" of type `GString'
[New Thread 0x7fffb03ff700 (LWP 13621)]
[New Thread 0x7fffaeeff700 (LWP 13622)]
[New Thread 0x7fffab3ff700 (LWP 13623)]
[New Thread 0x7fffd198d700 (LWP 13624)]
[New Thread 0x7fffd196c700 (LWP 13625)]
[New Thread 0x7fffce93c700 (LWP 13626)]
[New Thread 0x7fffcde60700 (LWP 13627)]
[New Thread 0x7fffc88bb700 (LWP 13628)]
[New Thread 0x7fffc889a700 (LWP 13629)]
[New Thread 0x7fffaa4ff700 (LWP 13630)]
[New Thread 0x7fffa8d76700 (LWP 13631)]
out of memory: 0x bytes requested

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffce93c700 (LWP 13626)]
0x769ff3da in mozalloc_abort(char const*) ()
   from /usr/lib/iceweasel/
libmozalloc.so

(sorry for responding directly to your email address; this is my first time
reporting a bug on debian, so please bare with me - I'm trying to learn!)

Bug#766216: lxc: can't access console or stop a jessie container running systemd as PID 1

[Antonio Terceiro]

Control: tag -1 patch

Hello,

On Tue, Oct 21, 2014 at 01:06:08PM -0200, Antonio Terceiro wrote:
> Package: lxc
> Version: 1:1.0.6-3
> Severity: normal
> 
> I have created a fresh jessie container, which got systemd as its init.
> When I start it in the foreground, then its console shows up
> just fine in my current terminal.
> 
> When I start the container the background (lxc-start -d), however:
> 
> - I cannot attach to it using lxc-console; there is never any output there.
> - I cannot stop it with lxc-stop without -k (i.e. forced kill)

Indeed, adapting the systemd setup from the lxc-fedora template does the
trick. The attached patch solves both issues.

I have just posted a proper git patch version of this patch to the
upstream mailing list.

Daniel, it would be really nice if we got this in Jessie.

-- 
Antonio Terceiro 
Author: Antonio Terceiro 
Description: lxc-debian: support systemd as PID 1
 Containers with systemd need a somewhat special setup, which I borrowed
 from lxc-fedora.

--- a/templates/lxc-debian.in
+++ b/templates/lxc-debian.in
@@ -159,6 +159,34 @@ EOF
 return 0
 }
 
+configure_debian_systemd()
+{
+rootfs=$1
+init="$(chroot ${rootfs} dpkg-query --search /sbin/init | cut -d : -f 1)"
+if [ "$init" != "systemd-sysv" ]; then
+   # systemd is not PID 1
+   return
+fi
+
+# This function has been copied and adapted from lxc-fedora
+rm -f ${rootfs}/etc/systemd/system/default.target
+touch ${rootfs}/etc/fstab
+chroot ${rootfs} ln -s /dev/null /etc/systemd/system/udev.service
+chroot ${rootfs} ln -s /lib/systemd/system/multi-user.target /etc/systemd/system/default.target
+# Make systemd honor SIGPWR
+chroot ${rootfs} ln -s /lib/systemd/system/halt.target /etc/systemd/system/sigpwr.target
+sed -e 's/^ConditionPathExists=/# ConditionPathExists=/' \
+-e 's/After=dev-%i.device/After=/' \
+< ${rootfs}/lib/systemd/system/getty\@.service \
+> ${rootfs}/etc/systemd/system/getty\@.service
+# Setup getty service on the 4 ttys we are going to allow in the
+# default config.  Number should match lxc.tty
+( cd ${rootfs}/etc/systemd/system/getty.target.wants
+for i in 1 2 3 4 ; do ln -sf ../getty\@.service getty@tty${i}.service; done )
+
+return 0
+}
+
 cleanup()
 {
 rm -rf $cache/partial-$release-$arch
@@ -452,6 +480,8 @@ if [ $? -ne 0 ]; then
 exit 1
 fi
 
+configure_debian_systemd $rootfs
+
 copy_configuration $path $rootfs $name $arch
 if [ $? -ne 0 ]; then
 echo "failed write configuration file"


signature.asc
Description: Digital signature

Bug#769660: starting a single connection on an as-needed basis does not work with systemd

[Wouter Verhelst]

On Sat, Nov 15, 2014 at 01:40:14PM +0100, Alberto Gonzalez Iniesta wrote:
>Yep, systemd does not allow extra params on init.d scripts calls.
>How about the systemd way?
>systemctl start openvpn@$CUSTOMER
>:-)

Ah, yes, that would work :-)

I suppose it might be good if the init script were to produce a message
when called in such a manner under systemd; but I'm not sure how easy
that would be.

-- 
It is easy to love a country that is famous for chocolate and beer

  -- Barack Obama, speaking in Brussels, Belgium, 2014-03-26


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769670: ola-rdm-tests: FTBFS in a sid chroot with pbuilder (no network)

[Wouter Verhelst]

On Sat, Nov 15, 2014 at 02:46:10PM +0100, Pitamila wrote:
> Package: ola-rdm-tests
> Version: 0.9.1-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> Dear Maintainer,
> 
> see pbuilder log below:
> 
> InterfacePickerTest.cpp:67:Assertion
> Test name: InterfacePickerTest::testGetInterfaces
> assertion failed
> - Expression: interfaces.size() > 0
> 
> Failures !!!
> Run: 21   Failure total: 1   Failures: 1   Errors: 0
> FAIL: NetworkTester

Can you give some detail on what the network looked like for this build?

-- 
It is easy to love a country that is famous for chocolate and beer

  -- Barack Obama, speaking in Brussels, Belgium, 2014-03-26


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#557671: You have reach me if yoi lik called le me

[RobertBradford94]

Know ok

Bug#767676: ola-rdm-tests: fails to install: subprocess installed post-installation script returned error exit status 10

[Wouter Verhelst]

On Sun, Nov 16, 2014 at 06:12:56PM +0100, Jean Baptiste Favre wrote:
> Hello,
> I had a look on it during Debian BSP in Paris.
> 
> Problem is located into ola-rdm-test.postinst script:
> - It uses debconf, for variable ola-rdm-tests/daemon, without providing
> any template file
> - It uses db_get and never db_input, thus ola-rdm-tests/daemon is never set
> - debconf is not mentioned as dependency
> 
> Please find attached a patch which removes debconf usage from postinst
> script.

Thanks.

Feel free to NMU; I do need to talk to debian-release about some other things,
but this should be straightforward enough that it shouldn't interfere with
that.

-- 
It is easy to love a country that is famous for chocolate and beer

  -- Barack Obama, speaking in Brussels, Belgium, 2014-03-26


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#760168: dh-systemd: Patch for supporting -X option included.

[Andreas Henriksson]

Hello!

I'm attaching a lightly tested patch to implement support for
the -X option in both dh_systemd_enable and dh_systemd_start.
Please review carefully.

Regards,
Andreas Henriksson
>From 8ffc1b0c731a52bbbeb7411b08b77d5526403ff4 Mon Sep 17 00:00:00 2001
From: Andreas Henriksson 
Date: Mon, 17 Nov 2014 00:52:42 +0100
Subject: [PATCH] Add support for -X option. (Closes: #760168)

---
 debian/changelog | 6 ++
 script/dh_systemd_enable | 5 +
 script/dh_systemd_start  | 5 +
 3 files changed, 16 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 9698e4c..dbb3375 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+init-system-helpers (1.21+nmu1) UNRELEASED; urgency=medium
+
+  * Add support for -X option. (Closes: #760168)
+
+ -- Andreas Henriksson   Mon, 17 Nov 2014 00:26:13 +0100
+
 init-system-helpers (1.21) unstable; urgency=medium
 
   * Demote augeas-tools to Suggests and let the systemd2init tool error out
diff --git a/script/dh_systemd_enable b/script/dh_systemd_enable
index 41323dc..7fcd4bf 100755
--- a/script/dh_systemd_enable
+++ b/script/dh_systemd_enable
@@ -184,6 +184,11 @@ foreach my $package (@{$dh{DOPACKAGES}}) {
 	# all unit files that are installed in this package.
 	my @args = @ARGV > 0 ? @ARGV : @installed_units;
 
+	# support excluding units via -X
+	foreach my $x (@{$dh{EXCLUDE}}) {
+		@args = grep !/(^|\/)$x$/, @args;
+	}
+
 	for my $name (@args) {
 		my $base = basename($name);
 
diff --git a/script/dh_systemd_start b/script/dh_systemd_start
index 297f9c5..279ea4c 100755
--- a/script/dh_systemd_start
+++ b/script/dh_systemd_start
@@ -131,6 +131,11 @@ foreach my $package (@{$dh{DOPACKAGES}}) {
 	# all unit files that are installed in this package.
 	my @args = @ARGV > 0 ? @ARGV : @installed_units;
 
+	# support excluding units via -X
+	foreach my $x (@{$dh{EXCLUDE}}) {
+		@args = grep !/(^|\/)$x$/, @args;
+	}
+
 	# This hash prevents us from looping forever in the following while loop.
 	# An actual real-world example of such a loop is systemd’s
 	# systemd-readahead-drop.service, which contains
-- 
2.1.3

Bug#769844: linux: please make linux build reproducibly

[Jérémy Bobbio]

Source: linux
Version: 3.16.7-2
Severity: wishlist
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps randomness
Control: block -1 by 759886

Hi!

I have been doing some experimentation on making linux build
reproducibly [1]. With the attached patches, we are down to three binary
packages with differences on amd64. The kernel itself and its module can
be built reproducibly with our current framework.

The first patch adds call to `dh_strip_nondeterminism` and
`dh_fixmtimes`, both being part of the custom toolchain currently used
for reproducible builds. Hence not tagging the bug with “patch” until
they are integrated in debhelper.

The second patch changes the value of KBUILD_BUILD_TIMESTAMP to a
timestamp parseable by `date`. Otherwise, a timestamp of the current
time gets stored in usr/initramfs_data.cpio.gz because
`scripts/gen_initramfs_list.sh` will not pass the value of
KBUILD_BUILD_TIMESTAMP to `usr/gen_init_cpio`.
http://sources.debian.net/src/linux/3.16.7-2/scripts/gen_initramfs_list.sh/?hl302:308#L302

Another solution would be to patch `scripts/gen_initramfs_list.sh` to
parse the Debian format of KBUILD_BUILD_TIMESTAMP.

An unclear aspect is where to add a call to `dh_genbuildinfo` which
generates the .buildinfo [2]. It should be called after all binary
packages have been created.

For the remaining differences:

 * linux-doc: many variations due to ids generated in HTML documentation
   by XSLT processor. This needs to be addressed at that level.
 * linux-manual: see attached debbindiff output. I don't have good
   ideas.
 * linux-source: mtimes of many files differ. Would it be ok to just
   create the tarball with a single timestamp (`tar --mtime=`)?

 [1]: https://wiki.debian.org/ReproducibleBuilds
 [2]: https://wiki.debian.org/ReproducibleBuilds/BuildinfoSpecification

-- 
Lunar.''`. 
lu...@debian.org: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   
--- linux-3.16.7/debian/rules.real	2014-11-04 04:41:34.0 +
+++ b1/linux-3.16.7/debian/rules.real	2014-11-14 22:07:20.272662604 +
@@ -173,12 +173,14 @@
 	dh_installdocs $(INSTALLDOCS_ARGS)
 	dh_installchangelogs
 	dh_strip
+	dh_strip_nondeterminism
 	dh_compress
 	dh_fixperms
 	dh_installdeb
 	dh_gencontrol -- $(GENCONTROL_ARGS)
 	dh_md5sums
+	dh_fixmtimes
 	dh_builddeb -- -Zxz $(BUILDDEB_ARGS)
 
 install-dummy:
 	dh_testdir
@@ -427,8 +430,10 @@
 	dh_prep
 	kernel-wedge install-files $(ABINAME)
 	kernel-wedge check $(PACKAGE_NAMES)
+	dh_strip_nondeterminism
 	dh_fixperms
 	dh_gencontrol
+	dh_fixmtimes
 	dh_builddeb
 
 install-source: PACKAGE_NAME = linux-source-$(VERSION)
--- linux-3.16.7/debian/rules.real	2014-11-04 04:41:34.0 +
+++ b1/linux-3.16.7/debian/rules.real	2014-11-14 22:07:20.272662604 +
@@ -39,7 +39,7 @@
 stamp = [ -d $(dir $@) ] || mkdir $(dir $@); touch $@
 
 setup_env := env -u ABINAME -u ARCH -u FEATURESET -u FLAVOUR -u VERSION -u LOCALVERSION
-setup_env += DISTRIBUTION_OFFICIAL_BUILD=1 DISTRIBUTOR="$(DISTRIBUTOR)" DISTRIBUTION_VERSION="$(SOURCEVERSION)" KBUILD_BUILD_TIMESTAMP="$(DISTRIBUTOR) $(SOURCEVERSION) ($(SOURCE_DATE_UTC_ISO))" KBUILD_BUILD_USER="$(word 1,$(subst @, ,$(MAINTAINER)))" KBUILD_BUILD_HOST="$(word 2,$(subst @, ,$(MAINTAINER)))"
+setup_env += DISTRIBUTION_OFFICIAL_BUILD=1 DISTRIBUTOR="$(DISTRIBUTOR)" DISTRIBUTION_VERSION="$(SOURCEVERSION)" KBUILD_BUILD_TIMESTAMP="$(SOURCE_DATE_UTC_ISO)" KBUILD_BUILD_USER="$(word 1,$(subst @, ,$(MAINTAINER)))" KBUILD_BUILD_HOST="$(word 2,$(subst @, ,$(MAINTAINER)))"
 
 MAKE_CLEAN = $(setup_env) $(MAKE)
 MAKE_SELF := $(MAKE) -f debian/rules.real $(MAKEOVERRIDES)
Title: /usr/bin/debbindiff --debug --html debbindiff-manual.html b1/linux-manual-3.16_3.16.7-2.0~reproducible1_all.deb b2/linux-manual-3.16_3.16.7-2.0~reproducible1_all.deb







linux-manual-3.16_3.16.7-2.0~reproducible1_all.deb

control.tar.gz

control.tar

md5sums
Files in package differs




data.tar.xz

data.tar

kthread_create_on_node.9.gz

kthread_create_on_node.9






 1 +-- 63 lines: '\" t-
64 This helper function creates and names a kernel thread\&. The thread will be stopped: use
65 \fBwake_up_process\fR
66 to start it\&. See also
67 \fBkthread_run\fR\&.
68 .PP
69 If thread is going to be bound on a particular cpu, give its node in
70 \fInode\fR, to get NUMA affinity for kthread stack, or else give \-1\&. When woken, the thread will run
71 \fIthreadfn\fR() with
72 \fIdata\fR
73 as its argument\&.   
74 \fIthreadfn\fR() can either call 
75 \fBdo_exit\fR
76 directly if it is a standalone thread for which no one will call
77 \fBkthread_stop\fR, or return when \*(Aq\fBkthread_should_stop\fR\*(Aq is true (which means
78 \fBkthre

Bug#768543: libpython2.7-minimal vs. POODLE

[積丹尼 Dan Jacobson]

reassign 768543 libpython2.7-minimal
found 768543 2.7.8-11
thanks
I am guessing that libpython2.7-minimal needs to be fixed to match the
POODLE changes needed when upgrading libssl1.0.0:i386 from 1.0.2~beta2-1
to 1.0.2~beta3-1, or else it breaks many packages.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769843: dpkg-maintscript-helper: Wrong pre-dependency information in man page

[Stefan Fritsch]

Package: dpkg
Version: 1.17.21
Severity: normal

The dpkg-maintscript-helper man page claims that symlink_to_dir needs
Pre-Depends: dpkg (>= 1.17.5). But the relative symlink feature in
symlink_to_dir was introduced in 1.17.14. This should be noted in the
man page.

A package that follows the man page is RC buggy. Therefore filing this
as severity normal, not minor.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.6-7+b1
ii  libc62.19-13
ii  liblzma5 5.1.1alpha+20120614-2+b1
ii  libselinux1  2.3-2
ii  tar  1.27.1-2+b1
ii  zlib1g   1:1.2.8.dfsg-2

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt  1.0.9.3

-- 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#769842: foomatic-filters: Make paps the default for foomatic-filters/textfilter

[Stéphane Aulery]

Package: foomatic-filters
Version: 4.0.17-5
Severity: wishlist
Tags: patch

Hello,

I noticed that paps is not offered by debconf for package foomatic-rip. Yet it
is the only filter that is functional with utf-8 files.

Can we make paps the default, or at least add it to the proposals, please?

Two patchs are attached for this.

Thanks for your help.

Regards,

-- 
Stéphane Aulery


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages foomatic-filters depends on:
ii  bash   4.3-11+b1
ii  debconf [debconf-2.0]  1.5.53
ii  libc6  2.19-13
ii  libdbus-1-31.8.10-1
ii  ucf3.0030

Versions of packages foomatic-filters recommends:
ii  a2ps   1:4.14-1.3
ii  colord 1.2.1-1+b1
ii  enscript   1.6.5.90-2+b1
ii  ghostscript9.06~dfsg-1.1+b1
ii  lprng [lpr]3.8.B-2
ii  poppler-utils  0.26.5-2

foomatic-filters suggests no packages.

-- debconf information:
* foomatic-filters/textfilter: Custom
* foomatic-filters/custom_textfilter: paps
* foomatic-filters/spooler: lprng
  foomatic-filters/ps_accounting: true
* foomatic-filters/filter_debug: true
  foomatic-filters/title:
  foomatic-filters/config_parsed: true
--- control.old	2014-11-17 00:26:43.908988343 +0100
+++ control.new	2014-11-17 00:29:57.865936550 +0100
@@ -21,7 +21,7 @@
 Recommends:
  cups-client | lpr | lprng | rlpr,
  ghostscript,
- cups | enscript | a2ps | mpage,
+ cups | enscript | a2ps | mpage | paps,
  poppler-utils (>= 0.11.2),
  colord
 Breaks: foomatic-bin (<< 2.9), cupsomatic-ppd (<< 20030507)
--- parseconfig.pl.old	2014-11-17 00:22:44.875819769 +0100
+++ parseconfig.pl.new	2014-11-17 00:23:30.864044594 +0100
@@ -25,7 +25,7 @@
$conf{debug} > 0 ? 'true' : 'false', ";\n") if exists $conf{debug};
 if (exists $conf{textfilter})
 {
-if ($conf{textfilter} =~ m/^(a2ps|enscript|mpage)$/)
+if ($conf{textfilter} =~ m/^(paps|a2ps|enscript|mpage)$/)
 {
 print "db_set foomatic-filters/textfilter $1;\n";
 }

Bug#769840: debhelper: fails to build a python3 package

[Forest]

Package: debhelper
Version: 9.20131227ubuntu1
Severity: normal

Dear Maintainer,

When packaging a python 3 program, debhelper causes all build targets
(including clean) to fail. The underlying cause seems to be that it insists
on running the python2-only pyversions program to process setup.py, despite
setup.py using python3 syntax, and despite all the obvious signs that it is
a python3 build. For example:

- setup.py starts with #!/usr/bin/env python3
- control contains Build-Depends: python3 (and not python or python2)
- control contains X-Python3-Version: (and not X-Python-Version)
- rules contains %: dh $@ --with python3

The failure occurs regardless of whether the dh command line includes
--with python3.

After quite a bit of groveling through documentation and mailing list archives,
I discovered that adding --buildsystem=pybuild to the dh command line works
around the problem. However, this is not documented in the Debian Python Policy
or apparently anyplace else where it really should appear. For example:

https://www.debian.org/doc/packaging-manuals/python-policy/
https://wiki.debian.org/Python/FAQ
https://wiki.debian.org/Python/
https://www.debian.org/doc/manuals/maint-guide/dreq.en.html#customrules
the dh man page
the debhelper man page

This seems like a pretty big oversight. The Python Policy makes it very clear
that programs should use python 3, but the packaging tools fail when following
that policy:

https://www.debian.org/doc/packaging-manuals/python-policy/ch-python3.html
"Programs should use Python 3, and should not be packaged for Python 2 as well. 
Python 3 should be used for the packaging if the packaging scripts use Python."

If there is a good reason why the tools can't be made to follow the policy,
shouldn't the workaround be documented in an obvious place, at least?

Thanks for your attention.

-- System Information:
Debian Release: jessie/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 
'trusty'), (100, 'trusty-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-39-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages debhelper depends on:
ii  binutils 2.24-5ubuntu3
ii  dh-apparmor  2.8.95~2430-0ubuntu5
ii  dpkg 1.17.5ubuntu5.3
ii  dpkg-dev 1.17.5ubuntu5.3
ii  file 1:5.14-2ubuntu3.2
ii  man-db   2.6.7.1-1ubuntu1
ii  perl 5.18.2-2ubuntu1
ii  po-debconf   1.0.16+nmu2ubuntu1

debhelper recommends no packages.

Versions of packages debhelper suggests:
pn  dh-make  

-- 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#769841: rfcview.el: please add buffer-local rfcview-title variable

[Trent W. Buck]

Package: emacs-goodies-el
Version: 35.12
Severity: wishlist
File: /usr/share/emacs/site-lisp/emacs-goodies-el/rfcview.el

In 2009, I accidentally filed this bug upstream instead of here.
I don't care much about it, but I'm refiling it for completeness.

> https://debbugs.gnu.org/5242
>
> I would like to customize frame-title-format such that when I'm
> looking at an RFC with rfcview.el, I can set the frame title to the
> RFC's title.  For example, when looking at rfc3481.txt I want
>
> "TCP over Second (2.5G) and Third (3G) Generation Wireless Networks"
>
> AFAICT rfcview.el currently provides no such variable, but it DOES
> recognize the title line (lines?), so I think it would be relatively
> easy to set a buffer-local rfcview-title variable when rfcview-mode is
> activated by leveraging title-line-point in rfc-grok-buffer.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#768285: python-pyvorbis-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Jean-Michel Nirgal Vourgère]

Sandro Tosi:
> Hello,
> thanks for the patch, but...
> 
> On Sun, Nov 16, 2014 at 3:50 AM, Jean-Michel Nirgal Vourgère
>> I've prepared a patch for that RC bug. As part of a BSP in Paris, I may
>> get an delayed NMU sponsored tomorrow. Please fell free to tell me if
>> you'd like to handle the matter yourself.
>> Note that version in maintscript need to be changed in that case.
> 
> ...this patch basically replace the symlink with a directory (as you
> can verify installing the package in a system where no pyvorbis
> package was present) which is against what I wanted to achieve, so
> have the -dbg package have a doc dir symlinked to python-pyvorbis doc
> dir.
> 
> if you want to NMU then I guess you want to address the problem above.
> 
> Regards,

Hello

The patch does *not* replace the link by a directory.

Wheezy version of python-pyvorbis-dbg was having a link:
/usr/share/doc/python-pyvorbis-dbg -> python-pyvorbis

Version actually in jessie is having a full copy, the upgrade script
does not remove the link.
This results in python-pyvorbis-dbg overwriting (duplicate) files in
python-pyvorbis, hence the release critical severity.

That patch is only addressing that issue.

Try to install a fresh version of your package on testing, you'll see :)

Please check your "override_dh_installdocs" target in debian/rules. May
be removing the duplicates would be enough?


The NMU is delayed and will automatically be uploaded in unstable in 5
days. If you fell you need more time to resolve that bug in the way you
want, please send an email to Frederic Peters cc'ed of that email.

Jessie will not be reached after 5? more days (priority medium) + an
unblock bug filled against release.debian.org. Still, it's messy to move
links around, and it might be better if it never reach unstable, if you
to put the link back.

Regards.
-- 
Nirgal



signature.asc
Description: OpenPGP digital signature

Bug#768407: Passphrase management problem

[Quentin Lefebvre]

Hi,

I'm currently investigating such kind of trouble on my laptop.

During my tests, I created the following plain partition :

dd if=/dev/zero of=/test1.loop bs=10M count=1
cryptsetup open --type plain /test1.loop test1
(I enter a blank password by directly typing enter)
mkfs.ext2 /dev/mapper/test1

Of course, at this stage, mounting /dev/mapper/test1 succeeds.

BUT, then, I type :
cryptsetup close test1
cryptdisks_start test1
mount /dev/mapper/test1 /media/TMP
this last command fails !

By the way, the /etc/crypttab used for my test contains :
test1/test1.loopnonenoauto
which has the advantage to take the same default values as cryptsetup
(I'm not saying it's good practice not to specify the cipher, hash algo,
and so on... anyway...).

So I investigated cryptdisks_start script... and I found a solution :
dd if=/dev/zero of=/test1.loop bs=10M count=1
/lib/cryptsetup/askpass "Damn password bug" | cryptsetup --key-file=-
open --type plain /test1.loop test1
(I enter a blank password by directly typing enter)
mkfs.ext2 /dev/mapper/test1
cryptsetup close test1
cryptdisks_start test1
mount /dev/mapper/test1 /media/TMP

THIS works...

So, obviously, there is a problem in the passphrase management made by
the current cryptsetup version.

I encourage you to test the scenario I described.

If I can, I'll debug cryptsetup and askpass to find the bug.

I hope this can help to solve Clayton's bug, and maybe mine (which I'll
report soon as it doesn't involve a passphrase but a key file).

Best regards,
Quentin

PS : By the way, I also upgraded recently from Wheezy to Jessie. This
bug is definitely Jessie-related.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769839: xfce4: german name of file-system-icon "Dateisystem" with possibly missing s: "Dateiystem"

[aron]

Package: xfce4
Version: 4.8.0.3
Severity: minor

Dear Maintainer,

with great joy using xfce4. As novice to reportbug i find the missing s only on
the desktop of xfce4, not in menus not in other window-managers.

Thank you for your patience with my maybe wrong notice.



-- 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/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xfce4 depends on:
ii  gtk2-engines-xfce  2.8.1-3
ii  orage  4.8.3-2
ii  thunar 1.2.3-4+b1
ii  xfce4-appfinder4.8.0-3
ii  xfce4-mixer4.8.0-3+b1
ii  xfce4-panel4.8.6-4
ii  xfce4-session  4.8.3-3
ii  xfce4-settings 4.8.3-2
ii  xfce4-utils4.8.3-2
ii  xfconf 4.8.1-1
ii  xfdesktop4 4.8.3-2
ii  xfwm4  4.8.3-2

Versions of packages xfce4 recommends:
ii  desktop-base  7.0.3
ii  tango-icon-theme  0.8.90-5
ii  thunar-volman 0.6.1-1
ii  xfce4-notifyd 0.2.2-2
ii  xorg  1:7.7+3~deb7u1

Versions of packages xfce4 suggests:
ii  xfce4-goodies  4.8.2
ii  xfprint4   4.6.1-3

-- 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#769804: jarjar-maven-plugin: FTBFS against rebuilt packages: Failed to resolve artifact ant

[Emmanuel Bourg]

Daniel confirmed privately he rebuilt velocity locally. The pom.xml file
in velocity has a dependency on ant with the scope 'provided'. The
recent versions of maven-debian-helper no longer inject this kind of
dependencies in the package dependencies (because the provided
dependencies are usually satisfied at runtime by a container. This is
typical with the dependencies on the Servlet and the OSGi APIs). So here
the rebuilt velocity package lacks the dependency on ant and breaks
jarjar-maven-plugin.

Thank you for spotting this issue Daniel. I'm going to add the missing
build dependency on Ant.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769796: systemd: update-rc.d lightdm disable does not work

[Samuel Thibault]

Control: tag -1 - moreinfo

Hello,

> ... which leads me to think that as long as the default DM is lightdm,
> even if one disables the lightdm service, a display-manager service is
> set up and will start. If my guess is correct, then that's a bug in
> lightdm (or in the display-manager logic, perhaps other DMs have the
> same), not in systemd.
> 
> What's the output of these commands?
> 
>   # systemctl status display-manager.service 

● lightdm.service - Light Display Manager
   Loaded: loaded (/lib/systemd/system/lightdm.service; enabled)
   Active: active (running) since dim. 2014-11-16 23:51:12 CET; 55s ago
 Docs: man:lightdm(1)
  Process: 1238 ExecStartPre=/bin/sh -c [ "$(cat 
/etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/lightdm" ] 
(code=exited, status=0/SUCCESS)
 Main PID: 1245 (lightdm)
   CGroup: /system.slice/lightdm.service
   ├─1245 /usr/sbin/lightdm
   ├─1254 /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
   └─2032 lightdm --session-child 12 19

nov. 16 23:51:12 type systemd[1]: Started Light Display Manager.
nov. 16 23:51:14 type lightdm[1946]: pam_unix(lightdm-greeter:session): session 
opened for user lightdm by (uid=0)

>   # systemctl status lightdm.service 

● lightdm.service - Light Display Manager
   Loaded: loaded (/lib/systemd/system/lightdm.service; enabled)
   Active: active (running) since dim. 2014-11-16 23:51:12 CET; 1min 5s ago
 Docs: man:lightdm(1)
  Process: 1238 ExecStartPre=/bin/sh -c [ "$(cat 
/etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/lightdm" ] 
(code=exited, status=0/SUCCESS)
 Main PID: 1245 (lightdm)
   CGroup: /system.slice/lightdm.service
   ├─1245 /usr/sbin/lightdm
   ├─1254 /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
   └─2032 lightdm --session-child 12 19

nov. 16 23:51:12 type systemd[1]: Started Light Display Manager.
nov. 16 23:51:14 type lightdm[1946]: pam_unix(lightdm-greeter:session): session 
opened for user lightdm by (uid=0)

So it seems they are indeed aliases.  I have run

systemctl disable display-manager

and now lightdm doesn't start any more.

Samuel


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769838: e2fsprogs: "REBOOT LINUX" message on non-linux systems

[Gabriele Giacone]

Package: e2fsprogs
Version: 1.42.12-1
Severity: wishlist
Tags: patch

Dear Maintainer,

given it also builds on kfreebsd and hurd, please consider not to
mention kernel in reboot message (just "REBOOT"? "REBOOT SYSTEM"?), or
mentioning the correct one.

Thanks for considering.
-- 
G..e
--- a/e2fsck/unix.c
+++ b/e2fsck/unix.c
@@ -1742,7 +1742,7 @@ no_journal:
   "MODIFIED *\n"),
ctx->device_name);
if (ctx->mount_flags & EXT2_MF_ISROOT) {
-   log_out(ctx, _("%s: * REBOOT LINUX *\n"),
+   log_out(ctx, _("%s: * REBOOT SYSTEM *\n"),
ctx->device_name);
exit_value |= FSCK_REBOOT;
}

Bug#768376: libvirt-daemon-system: Please downgrade policykit-1 dependency to recommends

[Reco]

 Sorry to interrupt your discussion, but:

On Sun, 16 Nov 2014 10:17:55 +0100
Guido Günther  wrote:

> On Sat, Nov 15, 2014 at 11:23:58AM +0100, Axel Beckert wrote:
> [..snip..]
>  
> > Guido Günther wrote:
> > > And what about /lib/systemd/system/libvirtd.socket ?
> > 
> > There are people who use other init systems.
> 
> My point exactly. To _have_ a choice we need to properly document what
> to change for _all_ init systems.

As of current sid and experimental, libvirt-daemon-system provides a
generic init script and a systemd's unit. There's nothing
upstart-specific in the package, for example.

Therefore, there're only two cases to document - systemd one (being a
default init in jessie, this case deserves special treatment indeed),
and a generic one (i.e. anything other than systemd).

Both cases were addressed (I hope) in the patch I've sent to this bug
report earlier.

Reco


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#767961: unblock pre-approval: beignet/0.9.3~really.0.8+dfsg-1

[Ivo De Decker]

Hi,

On Sun, Nov 16, 2014 at 10:19:25PM +, Rebecca N. Palmer wrote:
> >I didn't look at the details of the patch for #768090, but the bug log
> >suggests that there are remaining failures. Is that still the case with this
> >patch?
> 
> Assuming you mean
> >The remaining test failures are:
> >-cospi/sinpi/tanpi, powr/pown/pow, tgamma are less accurate than the
> >OpenCL spec requires (at least the first group explicitly use the
> >fast-but-inaccurate path, 2e-5 instead of 1e-8 typical relative error
> >but 10-20x faster; one reason 0.9 is "faster" is that it has sin/cos/tan
> >do the same by default).
> >-sub_bufffer_check sometimes crashes.
> yes, it's the same patch so has the same failures: I don't claim
> this is perfect, just the best we can reasonably do within the
> freeze rules.
> 
> In current upstream (1.0), the crash is gone and a non-default
> "strict conformance" mode is added where cospi/sinpi/tanpi meet the
> accuracy standard, but powr/pown/pow and tgamma still fail.

OK.

> >you can use a version like 1:0.8+dfsg-1 in unstable if you don't like
> >0.9.3~really.0.8+dfsg-1
> Please don't do that: I'd rather have a temporary ~really than a
> (permanent) epoch.

An epoch isn't that bad, but some people don't like it. As I said, both
1:0.8+dfsg-1 and 0.9.3~really.0.8+dfsg-1 are fine for me. Just ping this bug
when the package is in unstable.

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#744753: anacron: Anacron not triggered when system resumes under systemd

[Laurent Bigonville]

Le Sun, 16 Nov 2014 20:42:57 +0100,
Laurent Bigonville  a écrit :

[...]
> Tell me what do you think about this.

A much smaller change would just to add the following file in the
cron.hourly directory (not tested):

8<

#!/bin/sh

/usr/sbin/invoke-rc.d anacron start >/dev/null

8<

Of course, my proposed patches would requires that the machine is
turned on at xx:00 at least once a day. And apparently some people wants
to use anacron without a cron implementation, this would not solve this
bug for them either.

We could also add a .service file in the sleep.target, this was
mentioned once on #d-systemd, but I'm not sure what was the issue with
that solution (if any?).

I'm personally not a fan of having the cronjobs calling a initscript,
but that's probably just me and outside of the scope of this bug.

So if somebody has a better solution...

Laurent Bigonville


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#768681: nodejs: FTBFS in jessie: tests failures

[William Bonnet]

Hi Kurt

> I think not returning which error occurred is actually intentional,
since you might
> leak that information and turn it into a padding oracle.

> But I'll check what the others thinks

Thanks for the feedback.

I have thought of the padding oracle attack, but since all others errors
have a distinct return code, having no return code would be close to
having the proper return code, since it can happen in only this case.

Well at least that's my understanding, and since i'm not a crypto guy
I'm really interested in the answer from the real experts :)

Kind regards,

-- 
William http://www.wbonnet.net

http://france.debian.netAssociation Debian France
http://www.opencsw.org  Community SoftWare for Solaris


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769837: RFA: creepy -- geolocation information aggregator

[Daniel Echeverry]

Package: wnpp
Severity: normal

Hi

I request an adopter for the creepy package. unfortunately I  don't
have much time to work on this :(

The package description is:

creepy is an application that allows you to gather geolocation related
information about users from social networking platforms and image
hosting services. The information is presented in a map embedded in
the application where all the retrieved data is shown accompanied with
relevant information (i.e. what was posted from that specific
location) to provide context to the presentation

Regards

-- 
Daniel Echeverry
http://wiki.debian.org/DanielEcheverry
Linux user: #477840
Debian user
Software libre


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#767961: unblock pre-approval: beignet/0.9.3~really.0.8+dfsg-1

[Rebecca N. Palmer]

I didn't look at the details of the patch for #768090, but the bug log
suggests that there are remaining failures. Is that still the case with this
patch?


Assuming you mean

The remaining test failures are:
-cospi/sinpi/tanpi, powr/pown/pow, tgamma are less accurate than the
OpenCL spec requires (at least the first group explicitly use the
fast-but-inaccurate path, 2e-5 instead of 1e-8 typical relative error
but 10-20x faster; one reason 0.9 is "faster" is that it has sin/cos/tan
do the same by default).
-sub_bufffer_check sometimes crashes.
yes, it's the same patch so has the same failures: I don't claim this is 
perfect, just the best we can reasonably do within the freeze rules.


In current upstream (1.0), the crash is gone and a non-default "strict 
conformance" mode is added where cospi/sinpi/tanpi meet the accuracy 
standard, but powr/pown/pow and tgamma still fail.



you can use a version like 1:0.8+dfsg-1 in unstable if you don't like
0.9.3~really.0.8+dfsg-1
Please don't do that: I'd rather have a temporary ~really than a 
(permanent) epoch.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769836: [chromium-browser] Please use -fexcess-precision=standard or -ffloat-store instead of enabling sse2

[bastien ROUCARIÈS]

Package: chromium-browser
Severity: serious
version: 38.0.2125.101-4
justification: i386 package must be compiled for i586

According to gcc documentation and my experience [1]:

>The following options control compiler behavior regarding floating-point 
>arithmetic. These options trade off between speed and >correctness. All must 
>be specifically enabled.
>
>-ffloat-store
>Do not store floating-point variables in registers, and inhibit other 
> options that might change whether a floating-point value is taken from a 
> register or memory.
>
>This option prevents undesirable excess precision on machines such as the 
> 68000 where the floating registers (of the 68881) keep more precision than a 
> double is supposed to have. Similarly for the x86 architecture. For most 
> programs, the excess precision does only good, but a few programs rely on the 
> precise definition of IEEE floating point. Use -ffloat-store for such 
> programs, after modifying them to store all pertinent intermediate 
> computations into variables.
>-fexcess-precision=style
>This option allows further control over excess precision on machines where 
> floating-point registers have more precision than the IEEE float and double 
> types and the processor does not support operations rounding to those types. 
> By default, -fexcess-precision=fast is in effect; this means that operations 
> are carried out in the precision of the registers and that it is 
> unpredictable when rounding to the types specified in the source code takes 
> place. When compiling C, if -fexcess-precision=standard is specified then 
> excess precision follows the rules specified in ISO C99; in particular, both 
> casts and assignments cause values to be rounded to their semantic types 
> (whereas -ffloat-store only affects assignments). This option is enabled by 
> default for C if a strict conformance option such as -std=c99 is used.

>-fexcess-precision=standard is not implemented for languages other than C, 
> and has no effect if -funsafe-math-optimizations or -ffast-math is specified. 
> On the x86, it also has no effect if -mfpmath=sse or -mfpmath=sse+387 is 
> specified; in the former case, IEEE semantics apply without excess precision, 
> and in the latter, rounding is unpredictable. 

 [1] 
https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Disappointments.html#Disappointments

signature.asc
Description: This is a digitally signed message part.

Bug#752629: bug#752629 (ming license issue)

[Gabriele Giacone]

On Sun, Nov 16, 2014 at 5:01 PM, intrigeri  wrote:
> Done in the attached debdiff. However, as reported separately, the
> package FTBFS on current sid (but builds fine on Jessie), so I'm not
> NMU'ing as-is.

Here both ming and pencil2d do build fine on an updated clean sid chroot.

BTW my only doubt is about licensing:
  https://github.com/libming/libming/issues/42#issuecomment-47538565

-- 
G..e


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769747: [PATCH] debian/control: switch order of systemd-sysv|systemd-shim dependencies for libpam-systemd. (Closes: #769747)

[Don Armstrong]

Control: tag -1 patch

---
 debian/changelog | 4 
 debian/control   | 2 +-
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index cf3c3af..6fc4716 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -27,6 +27,10 @@ systemd (215-6) UNRELEASED; urgency=medium
   * debian/ifup@.service: add a ConditionPath on /run/network, to avoid
 failing the unit if /etc/init.d/networking is disabled. (Closes: #769528)
 
+  [ Don Armstrong ]
+  * debian/control: switch order of systemd-sysv|systemd-shim dependencies
+for libpam-systemd. (Closes: #769747)
+
  -- Martin Pitt   Sun, 12 Oct 2014 17:29:00 +0200
 
 systemd (215-5) unstable; urgency=medium
diff --git a/debian/control b/debian/control
index 75986c1..cbd2d6a 100644
--- a/debian/control
+++ b/debian/control
@@ -112,7 +112,7 @@ Depends: ${shlibs:Depends},
  systemd (= ${binary:Version}),
  libpam-runtime (>= 1.0.1-6),
  dbus,
- systemd-sysv | systemd-shim (>= 8-2)
+ systemd-shim (>= 8-2) | systemd-sysv
 Description: system and service manager - PAM module
  systemd is a replacement for sysvinit.  It is dependency-based and
  able to read the LSB init script headers in addition to parsing rcN.d
-- 
2.1.0

-- 
Don Armstrong  http://www.donarmstrong.com

The attackers hadn't simply robbed the bank. They had carried off
everything portable, including the security cameras, the carpets, the
chairs, and the light and plumbing fixtures. The conspirators had
deliberately punished the bank, for reasons best known to themselves,
or to their unknown controllers. They had superglued doors and
shattered windows, severed power and communications cables, poured
stinking toxins into the wallspaces, and concreted all of the sinks
and drains. In eight minutes, sixty people had ruined the building so
thoroughly that it had to be condemned and later demolished.
 -- Bruce Sterling, _Distraction_ p4


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769835: googleearth-package: depenencies not installed before dpkg -i, causing unmet dependencies and other problems

[Matt Kukowski]

Package: googleearth-package
Version: 0.7.0
Severity: important

Dear Maintainer,

After running make-googleearth it builds the package just fine.

But, when it gets to Installing the pkg (dpkg -i ...) it reports unmet
dependancies.

bug spew...
-
dpkg: dependency problems prevent configuration of googleearth:
 googleearth depends on libfreeimage3; however:
  Package libfreeimage3 is not installed.
 googleearth depends on lsb-core; however:
  Package lsb-core is not installed.

dpkg: error processing googleearth (--install):
 dependency problems - leaving unconfigured
Processing triggers for desktop-file-utils ...
Processing triggers for gnome-menus ...
Processing triggers for shared-mime-info ...
Processing triggers for menu ...
Processing triggers for mime-support ...
Errors were encountered while processing:
 googleearth

You then have to run 'apt-get install -f'  to correct the dependancy problem as
it breaks apt-get.



-- System Information:
Debian Release: 7.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages googleearth-package depends on:
ii  bzip2   1.0.6-4
ii  dpkg-dev1.16.15
ii  fakeroot1.18.4-2
ii  file5.11-2+deb7u6
ii  wget1.13.4-3+deb7u2
ii  x11-common  1:7.7+3~deb7u1
ii  x11-utils   7.7~1

googleearth-package recommends no packages.

googleearth-package 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#759020: python-llvm: version string contains 'tag: '

[Reiner Herrmann]

Package: python-llvm
Version: 0.12.7-2
Tags: patch

The version string is contained in the file llvm/_version.py.
In the tarball downloaded from Github this already looks like 'tag: 0.12.7'.
I found out that the "official" tarball provided by upstream on PyPI [1]
contains the correct version string.

So either a different source archive can be used, or the version string can
be corrected before building the package.
I attached two patches for both ways. One modifies the watch file to look
for new versions on PyPI instead of Github. The other one adds a
override_dh_auto_configure section to debian/rules, which corrects the
version strings.

[1] https://pypi.python.org/pypi/llvmpy/
diff --git a/debian/rules b/debian/rules
index d7d9c68..9c73a24 100755
--- a/debian/rules
+++ b/debian/rules
@@ -2,6 +2,11 @@
 %:
 	LLVM_CONFIG_PATH=/usr/bin/llvm-config-3.4 dh $@ --with python2
 
+override_dh_auto_configure:
+	# _version.py contains "tag: " in the version string (#759020)
+	sed -i 's/^git_refnames.*tag: \([0-9]\+.[0-9]\+.[0-9]\+\).*/git_refnames = "\1"/g' llvm/_version.py
+	dh_auto_configure
+
 override_dh_strip:
 	dh_strip --dbg-package=python-llvm-dbg
 
diff --git a/debian/watch b/debian/watch
index ba14204..da201d8 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,3 +1,3 @@
 version=3
-opts=filenamemangle=s/.+\/v?(.*)\.tar\.gz/llvmpy-$1.tar.gz/ \
-  https://github.com/llvmpy/llvmpy/tags .*/v?(\d[\d\.]+)\.tar\.gz
+opts=uversionmangle=s/(rc|dev|a|b|c)/~$1/ \
+https://pypi.python.org/packages/source/l/llvmpy/llvmpy-(.*)\.(?:tar\.gz|zip|tar\.bz2)


signature.asc
Description: OpenPGP digital signature

Bug#728202: cmus: m4a and wma playback is broken

[doug]

On Sat, 16 Nov 2013 15:05:42 +0100 Thomas 
 wrote:

> Package: cmus
> Version: 2.5.0-4
> Followup-For: Bug #728202
>
> Hi!
>
> I noted today that cmus has exactly the same problem with wma-files.
>
> Thomas

Cmus should be upgraded to 2.6.0 & the ffmpeg plugin built off of FFmpeg 
using swresample, then it will work as expected

Doug


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#765567: Patch by Peter de Wachter

[Jelmer Vernooij]

tags 765567 +patch
thanks

Peter de Wachter wrote a patch for this bug, though it was attached to
the related bug against xsltproc.
Description: use EXSLT "replace" function when available
 A recursive implementation  of string.subst is problematic,
 long strings with many matches will cause stack overflows.
Author: Peter De Wachter 
Bug-Debian: https://bugs.debian.org/750593

--- docbook-xsl-1.78.1+dfsg.orig/docbook-xsl/lib/lib.xsl
+++ docbook-xsl-1.78.1+dfsg/docbook-xsl/lib/lib.xsl
@@ -10,7 +10,10 @@
  This module implements DTD-independent functions
 
   -->
-http://www.w3.org/1999/XSL/Transform"; version="1.0">
+http://www.w3.org/1999/XSL/Transform";
+xmlns:str="http://exslt.org/strings";
+exclude-result-prefixes="str"
+version="1.0">
 
 
   
@@ -56,6 +59,9 @@
   
 
   
+
+  
+
 
   
 

Bug#768324: unblock: appstream/0.7.4-1

[Jonathan Wiltshire]

Control: tag -1 moreinfo

On Thu, Nov 06, 2014 at 06:50:01PM +0100, Matthias Klumpp wrote:
> 2014-11-06 17:48 GMT+01:00 Jonathan Wiltshire :
> > On 2014-11-06 16:34, Matthias Klumpp wrote:
> >> [...]
> >
> > At least a debdiff is missing; the changelog and bugs would be handy.
> Okay, sorry for that.
> A debdiff is attached.

At ~800K it didn't make it to the list (and hence nobody has responded),
which should give you an idea of how much I'm looking forward to reading
it or the 67K one...

> Since the Debian changelog is rather boring (just says that a new
> upstream release was packaged), here's the upstream changelog instead:
> 
> #~#~#
> Version 0.7.4
> ~~
> Released: 2014-10-30
> 
> Notes:
> 
> Features:
>  * Add local icon directories to the icon search path
>  * Properly handle origin and icons in size-specific directories
>  * Allow client applications to fetch icons in multiple sizes
>  * qt: Implement multisize-icons
>  * qt: Add documentation to the deprecated methods
>  * validator: Ensure that stock and cached icons only contain the icon 
> basename

Features are out; sorry. It's too late for that sort of thing, especially
as the upstream release alone was only a few days ahead of the freeze.

An exception would be if they're causing real bugs in Debian.
 
> Bugfixes:
>  * dep11: refine quote test
>  * Don't count it as problem if no metadata is found [1]
>  * Check if AppInstall directory exists, before attempting to scan it [3]
>  * Don't query system categories while processing metadata [2]
> #~#~#
> Bugfix for [1] solves the issue that "appstream-index refresh" is
> failing, even if it shouldn't do that (since some tools may call it
> and check for the results, this is quite important - not for the
> post-install hook of packages, because the ignore the result, but at
> least the user won't see a "something is wrong" message then)
> [2] fixes some log-spam in case the user doesn't have extra category
> metadata installed (happens e.g. on GNOME) and [3] solves some
> annoying behaviour in case app-install-data or a similar package is
> not installed.
> The other remaining fix helps to ensure DEP-11
> (https://wiki.debian.org/DEP-11) compliance, but that one isn't
> relevant.
> The added features ensure compatibility with the more recent icon
> cache format of AppStream, as described in
> http://www.freedesktop.org/software/appstream/docs/sect-AppStream-IconCache.html
> and implement the necessary bits in the Qt and GLib libraries.
> The depending applications (Apper, Muon specifically) have been tested
> with these changes and work well.
> For convenience, I also included a clean upstream patch, which does
> not contain the changes in (generated) documentation, like the debdiff
> contains.

I'm interested in the bug fixes in isolation, but I'd need a debdiff for
first please.

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



signature.asc
Description: Digital signature

Bug#769834: [src:sqlkit] Some sources are not included in your package

[Bastien ROUCARIES]

Package: src:sqlkit
Version:0.9.6.1-1

user: lintian-ma...@debian.org
usertags: source-is-missing
severity: serious
X-Debbugs-CC: ftpmas...@debian.org

Hi,

Your package seems to include some files that lack sources
in prefered forms of modification:

doc/static/imgpreview.js
doc/html/_static/imgpreview.js


According to Debian Free Software Guidelines [1] (DFSG) #2:
 "The program must include source code, and must allow distribution
  in source code as well as compiled form.".

This could also constitute a license violation for some copyleft
licenses such as the GNU GPL.

In order to solve this problem, you could:
1. repack the origin tarball adding the missing source to it.
2  add the source files to "debian/missing-sources" directory

Both way satisfies the requirement that we ship the source. Second option
might be preferable due to the following reasons [2]:
 - Upstream can do it too and you could even supply a patch to them,
thus full filling our social contract [3], see particularly §2.

- If source and non-source are in different locations, ftpmasters may
   miss the source and (needlessly) reject the package.
 - The source isn't duplicated in every .diff.gz/.debian.tar.* (though
   this only really matters for larger sources).

You could also ask debian...@lists.debian.org or #debian-qa for more
guidance.

Note that your overriden file is bogus.
*The distribution of this js file complies with its MIT license, and it
# is not used by any binary package [4]

File-excluded really help here.

good (avoid copy and security problem) but does not solve this source
problem. [4]

[1] https://www.debian.org/social_contract.en.html#guidelines
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736873#8
[3] https://www.debian.org/social_contract
[4] For release team: I am checking lintian false positive. And I
submit only bug when they are bad override file.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#768619: proofgeneral: FTBFS in jessie: build-dependency not installable: emacs23-nox

[intrigeri]

Hi,

Hendrik Tews wrote (16 Nov 2014 21:17:08 GMT) :
> thanks, this is certainly one way to solve the bug. I would
> however have preferred to fix the problem in sbuild, as Felix
> Gruber pointed out.

The buildd network and some of our QA processes uses software (sbuild
or something else) that has had this limitation for years, and we've
get used to it somehow. I suspect it can't be easily fixed, otherwise
it would probably have been done a while ago. I'd be delighted to be
proven wrong, though.

So, as far as the Jessie release is concerned, I went with the
short-term fix. This being said, I certainly don't want to discourage
you from working on the root cause of the problem :)

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#769833: [trac] Some sources are not included in your package

[Bastien ROUCARIES]

Package: src:trac
Version:1.0.2-1
user: lintian-ma...@debian.org
usertags: source-is-missing
severity: serious
X-Debbugs-CC: ftpmas...@debian.org

Hi,

Your package seems to include some files that lack sources
in prefered forms of modification:

* trac/htdocs/js/jquery.js
* trac/htdocs/js/jquery-ui.js
* trac/htdocs/js/jquery-ui-addons.js
* trac/htdocs/js/excanvas.js

According to Debian Free Software Guidelines [1] (DFSG) #2:
 "The program must include source code, and must allow distribution
  in source code as well as compiled form.".

This could also constitute a license violation for some copyleft
licenses such as the GNU GPL.

In order to solve this problem, you could:
1. repack the origin tarball adding the missing source to it.
2  add the source files to "debian/missing-sources" directory

Both way satisfies the requirement that we ship the source. Second option
might be preferable due to the following reasons [2]:
 - Upstream can do it too and you could even supply a patch to them,
thus full filling our social contract [3], see particularly §2.
 - If source and non-source are in different locations, ftpmasters may
   miss the source and (needlessly) reject the package.
 - The source isn't duplicated in every .diff.gz/.debian.tar.* (though
   this only really matters for larger sources).

You could also ask debian...@lists.debian.org or #debian-qa for more
guidance.


Note that your overriden file is bogus. Linking to packaged file is
good (avoid copy and security problem) but does not solve this source
problem. [4]

[1] https://www.debian.org/social_contract.en.html#guidelines
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736873#8
[3] https://www.debian.org/social_contract
[4] For release team: I am checking lintian false positive. And I
submit only bug when they are bad override file.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769832: nxml-mode: XML validation is broken

[Vincent Lefevre]

Package: emacs24
Version: 24.4+1-4
Severity: important

After opening a valid XML file, Emacs said that the file was invalid.
I can't reproduce the problem (on exactly the same file). I suspect
that this is due to some race condition or memory corruption.

-- System Information:
Debian Release: jessie/sid
  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/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages emacs24 depends on:
ii  emacs24-bin-common 24.4+1-4
ii  gconf-service  3.2.6-3
ii  libacl12.2.52-2
ii  libasound2 1.0.28-1
ii  libatk1.0-02.14.0-1
ii  libc6  2.19-13
ii  libcairo-gobject2  1.14.0-2.1
ii  libcairo2  1.14.0-2.1
ii  libdbus-1-31.8.10-1
ii  libfontconfig1 2.11.0-6.1
ii  libfreetype6   2.5.2-2
ii  libgconf-2-4   3.2.6-3
ii  libgdk-pixbuf2.0-0 2.31.1-2+b1
ii  libgif44.1.6-11
ii  libglib2.0-0   2.42.1-1
ii  libgnutls-deb0-28  3.3.8-4
ii  libgomp1   4.9.2-1
ii  libgpm21.20.4-6.1
ii  libgtk-3-0 3.14.4-2
ii  libice62:1.0.9-1
ii  libjpeg62-turbo1:1.3.1-10
ii  libm17n-0  1.6.4-3
ii  libmagickcore-6.q16-2  8:6.8.9.9-3
ii  libmagickwand-6.q16-2  8:6.8.9.9-3
ii  libotf00.9.13-2
ii  libpango-1.0-0 1.36.8-2
ii  libpangocairo-1.0-01.36.8-2
ii  libpng12-0 1.2.50-2+b1
ii  librsvg2-2 2.40.5-1
ii  libselinux12.3-2
ii  libsm6 2:1.2.2-1
ii  libtiff5   4.0.3-10+b3
ii  libtinfo5  5.9+20140913-1
ii  libx11-6   2:1.6.2-3
ii  libxft22.3.2-1
ii  libxinerama1   2:1.1.3-1+b1
ii  libxml22.9.1+dfsg1-3
ii  libxpm41:3.5.11-1
ii  libxrandr2 2:1.4.2-1+b1
ii  libxrender11:0.9.8-1+b1
ii  zlib1g 1:1.2.8.dfsg-2

emacs24 recommends no packages.

Versions of packages emacs24 suggests:
ii  emacs24-common-non-dfsg  24.4+1-2

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769097: How is creating those files?

[Thomas Lange]

fai-quickstart is calling /etc/init.d/nfs-kernel-server reload which
calls exportfs -r

Stracing this command shows:

5284  open("/var/lib/nfs/export-lock", O_RDWR|O_CREAT, 0666) = 3
5284  open("/var/lib/nfs/.etab.lock", O_RDONLY|O_CREAT, 0600) = 4

Not sure if we can just remove those files.

-- 
regards Thomas


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#768619: proofgeneral: FTBFS in jessie: build-dependency not installable: emacs23-nox

[Hendrik Tews]

Hi,

thanks, this is certainly one way to solve the bug. I would
however have preferred to fix the problem in sbuild, as Felix
Gruber pointed out. The build-dependencies of the package are
IMHO not wrong, the package should also build with emacs23.

Bye,

Hendrik


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769705: unblock: pdns-recursor/3.6.2-2

[Christian Hofstaedtler]

* Jonathan Wiltshire  [141116 22:13]:
> On Sun, Nov 16, 2014 at 06:00:12PM +0100, Christian Hofstaedtler wrote:
> > * Julien Cristau  [141116 17:45]:
> > > On Sun, Nov 16, 2014 at 17:24:02 +0100, Christian Hofstaedtler wrote:
> > > > pdns-recursor does a check with upstream to see if they think the
> > > > version the user is running has a security issue. (This check is
> > > > done using DNS and a log message is printed if there are known
> > > > issues.)
> > > > 
> > > Calling home sounds like a misfeature...
> > 
> > In general I'd agree with you.
> > 
> > Users can turn this off by setting security-poll-suffix empty, as
> > pointed out by the upstream docs.
> > 
> > I think for PowerDNS the home call is warranted, given that...
> > 
> > 1) both pdns-server and -recursor are usually Internet exposed services
> > that regularly see abuse (DDoS reflection, regular DoS, ...)
> > 
> > 2) they usually end up being installed and then forgotten until they
> > stop working (then somebody may read a log file)
> > 
> > 3) upstream is not some evil enterprise corp, but a pure open source
> > company that really tries to tie in and work with downstreams.
> 
> We have a security team for this. Users who want to stay secure should
> subscribe to debian-security-announce, and react to DSAs.

I think the case here is that some users need more pushing, and
people come crying to upstream when they run versions from
oldstable. After all, Debian ends support for stable distributions
after some time, and "root servers" in some data center farms tend
to run way longer than that.

> I'd be pretty surprised if I installed pdns-* and found them checking up on
> security for me, even if it is mentioned in the upstream docs. After all,
> the point of installing from packages is that the maintainer has done the
> donkey work of making things work, so I might not even have cause to refer
> to them.
> 
> I realise this is done with the best of intentions by upstream, but it
> would be better if they worked with the security team and stable release
> managers to proactively push updates out to users, instead of relying on
> them finding a log snippet.

I agree, and I must say that I personally think the Debian packaging
(freshness) as well as upstream's (actual and commitment to) help
have improved dramatically.

> IMO this should be conservative and disabled by default in the package.

I disagree based on my view of what software runs (on) the Internet
today, and is sending me and others useless, dangerous, and expensive
traffic. (I do see the privacy issue here, but it's something
different for a server daemon and, say, an office package.)

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-



signature.asc
Description: Digital signature

Bug#769831: [testng] Some sources are not included in your package

[Bastien ROUCARIES]

Package: testng
Version: 6.8.8-2
user: lintian-ma...@debian.org
usertags: source-is-missing
severity: serious
X-Debbugs-CC: ftpmas...@debian.org

Hi,

Your package seems to include some files that lack sources
in prefered forms of modification:

src/main/resources/jquery-1.7.1.min.js

According to Debian Free Software Guidelines [1] (DFSG) #2:
 "The program must include source code, and must allow distribution
  in source code as well as compiled form.".

This could also constitute a license violation for some copyleft
licenses such as the GNU GPL.

In order to solve this problem, you could:
1. repack the origin tarball adding the missing source to it.
2  add the source files to "debian/missing-sources" directory

Both way satisfies the requirement that we ship the source. Second option
might be preferable due to the following reasons [2]:
 - Upstream can do it too and you could even supply a patch to them,
thus full filling our social contract [3], see particularly §2.
 - If source and non-source are in different locations, ftpmasters may
   miss the source and (needlessly) reject the package.
 - The source isn't duplicated in every .diff.gz/.debian.tar.* (though
   this only really matters for larger sources).

You could also ask debian...@lists.debian.org or #debian-qa for more
guidance.

Waiting for next upstream release is not sufficient.

[1] https://www.debian.org/social_contract.en.html#guidelines
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736873#8
[3] https://www.debian.org/social_contract


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org