Bug#724807: RFS: yt/2013.09.28-1 [ITP]

[Javier P.L.]

Package: sponsorship-requests
Severity: normal whislist

I am looking for a sponsor for my package "yt"

 * Package name: yt
   Version : 2013.09.28-1
   Upstream Author : Rich Wareham 
 * URL : https://github.com/rjw57/yt
 * License : MIT
   Section : web

  It builds those binary packages:

yt- command-line YouTube client

  To access further information about this package, please visit the following 
URL:

  http://mentors.debian.net/package/yt

  Alternatively, one can download the package with dget using this command:

dget -x http://mentors.debian.net/debian/pool/main/y/yt/yt_2013.09.28-1.dsc

  Changes since the last upload:

  Initial release, closes: #724801.

  Regards,
   Javier Lopez


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

Bug#724808: ocl-icd-libopencl1: Handle invalid object references

[Simon Richter]

Package: ocl-icd-libopencl1
Version: 1.3-3+debug
Severity: minor

Running the Piglit test suite reports several errors where NULL pointers
are dereferenced in libOpenCL.so. Apparently, OpenCL implementations are
expected to recognize NULL pointers as invalid object references.

I could not find scripture to support this, but it might be a good idea
nonetheless (i.e. clGetKernelInfo returns CL_INVALID_KERNEL if given a NULL
pointer, etc.).

Higher than wishlist as it makes running the compliance test suite show
false negatives.

   Simon

-- System Information:
Debian Release: 7.1
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-3-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 ocl-icd-libopencl1 depends on:
ii  libc6  2.17-93
ii  multiarch-support  2.13-38

ocl-icd-libopencl1 recommends no packages.

Versions of packages ocl-icd-libopencl1 suggests:
ii  amd-opencl-icd [opencl-icd] 1:12-6+point-3
ii  beignet [opencl-icd]0.2+git20130928+187c17e-1
ii  nvidia-opencl-icd [opencl-icd]  304.88-1+deb7u1

-- 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#722971: chewing doesn't remember our names etc. anymore

[jidanni]

>
> Every time I type in 積丹尼 I have to enter it again just like it was the 
> first time I ever entered it.
>

Bug#724805: qemu-kvm: internal error with guest kernel bug

[Brian Silverman]

Package: qemu-kvm
Version: 1.1.2+dfsg-6
Severity: normal

While working on bug
724802 (ie
reproducing it repeatedly on a guest kernel), I got an error message from
KVM (copied in a bit later on in this message). That bug is some kind of
serious error in the kernel, so it's not very surprising that it triggered
a bug in KVM. After it happened, the kvm window went all black, but that
kernel bug that sometimes results in that on it's own.

Unfortunately, this error message only happened once, and I closed the
whole VM (by clicking the "close" window decoration button, which did close
everything) before remembering to gather any more information about the
state... If it happens again, is there anything I should grab besides a
core dump of the KVM process?

I started the VM with `kvm -drive
file=wheezy-futex-kernel-panic-test.qcow,cache=writeback,if=virtio \
  -cpu host \
  -m 1G \
  -vga vmware \
  -smp 4 \
  -virtfs
local,id=src,path=/path/to/a/local/folder,security_model=none,mount_tag=src`.
That image .qcow is a fairly standard Debian image, but it has had lots and
lots of kernel crashes etc, so it might be corrupted in some way. However,
it was working fine before I saw this message and it still seems to work
fine afterwards, so I don't think so. The "src" 9p share gets mounted in
the guest from /etc/fstab.

Here's the error message (which was printed out in the terminal I ran `kvm`
from):
KVM internal error. Suberror: 1
emulation failure
EAX= EBX=f77a7004 ECX=ff8613cc EDX=f77aa430
ESI= EDI=f77a7000 EBP=f779eff4 ESP=ff8613cc
EIP=f77aa430 EFL=00010296 [--S-AP-] CPL=3 II=0 A20=1 SMM=0 HLT=0
ES =002b   00c0f300 DPL=3 DS   [-WA]
CS =0023   00c0fb00 DPL=3 CS32 [-RA]
SS =002b   00c0f300 DPL=3 DS   [-WA]
DS =002b   00c0f300 DPL=3 DS   [-WA]
FS =   
GS =0063 f763f8d0  00d0f300 DPL=3 DS   [-WA]
LDT=   
TR =0040 3fbdfc40 2087 8b00 DPL=0 TSS64-busy
GDT= 88003fb84000 007f
IDT= 81786000 0fff
CR0=8005003b CR2=08049be0 CR3=38d68000 CR4=000406e0
DR0= DR1= DR2=
DR3=
DR6=0ff0 DR7=0400
EFER=0d01
Code=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00
KVM internal error. Suberror: 1
emulation failure
RAX=817e3847 RBX=817e3846 RCX=0001
RDX=0016
RSI=ffe8 RDI=88003f955fc1 RBP=817e3c30
RSP=88003f955f78
R8 =fffe R9 = R10=0078
R11=88003fbe2000
R12=88003f955fc2 R13=817e3c00 R14=817e3846
R15=0400
RIP=811bd231 RFL=00010087 [--S--PC] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =002b   00c0f300 DPL=3 DS   [-WA]
CS =0010   00a09b00 DPL=0 CS64 [-RA]
SS =   
DS =002b   00c0f300 DPL=3 DS   [-WA]
FS =   
GS =0063 88003fb8  00d0f300 DPL=3 DS   [-WA]
LDT=   
TR =0040 88003fbdfc40 2087 8b00 DPL=0 TSS64-busy
GDT= 88003fb84000 007f
IDT= 81786000 0fff
CR0=8005003b CR2=57c5b047 CR3=38d68000 CR4=000406e0
DR0= DR1= DR2=
DR3=
DR6=0ff0 DR7=0400
EFER=0d01
Code=0f bf c0 41 ff c8 39 c2 7c ea 48 89 d8 eb 11 48 39 e8 73 06 <41> 8a 0c
24 88 08 48 ff c0 49 ff c4 89 c1 29 d9 39 d1 7c e7 eb 0b 48 39 e8 73 03 c6
00 20


-- Package-specific info:


/proc/cpuinfo:

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz
stepping : 7
microcode : 0x14
cpu MHz : 800.000
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm
constant_tsc arch_perfmon pebs bts nopl xtopology nonstop_tsc aperfmperf
pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid
sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx lahf_lm ida arat
epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid
bogomips : 4585.19
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz
stepping : 7
microcode : 0x14
cpu MHz : 800.000
cache size : 3072 KB
physical id 

Bug#724804: Arduino 1:1.0.5+dfsg2-1

[JohnK]

Package: Arduino
Version:   1:1.0.5+dfsg2-1
Running under: Raspian GNU/Linux jessie/sid raspberri pi
Last apt-get update/upgrade Sept 26 2013

I'm running 1.0.5/Testing/Jessie because 1.0.1/Stable/Wheezy doesn't have 
header files for the Micro board.

Application: IDE.
Development board: Arduino Micro.
IDE reports in top/main banner: Arduino 1:1.0.5+dfsg2-1
IDE reports in bottom banner, in right corner: Arduino Micro on /dev/ttyACM0.  
And this was selected from the Tools/Serial Port dropdown, intially, but 
currently this dropdown is grayed/non-selectable. 
Tools/Board dropdown reports "Micro" correctly as selected by me. 
Tools/Programmer shows "Arduino as ISP", as selected by me. 

Problems:
-When running the IDE, selecting the "Serial Monitor" control from the third 
banner or from Tools/ Serial Monitor dropdown crashes the IDE.  This happens 
with no code loaded, or a working sketch loaded.

-in "void setup() {"   the code
Serial.begin(9600);
while (!Serial) {
 ;   // Wait for serial port to connect.
}
causes the Sketch to not run.   Removing this code allows problem-free 
uploading of Sketches.  "while (!Serial)"  is supposed to apply to both the 
Leonardo and Micro boards since they both use the same processor to handle 
communications.  This is listed in the Arduino Reference material that comes 
with this IDE.  The purpose of this code is to establish communication with the 
board during uploading (all of the other boards have a separate processor for 
this communication and the setup for the upload is different for them.)  I 
initially had trouble, or a beginner's confusion, with my first attempts at 
uploading, and tried using the Reset button on the Micro board as suggested in 
the documentation as well as the "while (!Serial) code, but finally it started 
working - perhaps I just managed to get all the bits in order after several 
trials.  But there still remains the issue with the while (!Serial) behaviour


I can develop Sketches in the IDE, Upload them to the Micro board, and they do 
work.  Since I'm just starting out, I am not trying anything sophisticated or 
complex.

Note: While I've been developing information systems for large business clients 
in a variety of platforms, OSs and Languages, this is my first serious work 
with Unix (and I think it's WONDERFUL!).




John K
Cincinnati, Ohio USA

---
This mail was sent with the Java email client Columba. Read more at 
http://columbamail.org


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

Bug#724803: amd64-microcode: breaks amd box

[tester]

Package: amd64-microcode
Version: 2.20131007.1+really20130710.1
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these lines ***



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

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

-- 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#637346: The same problem while creating from XML.

[Alexey Knyazev]

I was obtaining the same error message even if I wrote XML.
It contains:














There's no crime here. DVDauthor of previous versions (0.6.0 and earlier) 
process this correctly, but 0.7.0 can't understand empty  tag et all.
So my case solution was to purge 0.7.0 and install version 0.6.0 back. :(


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

Bug#724801: ITP: yt -- yt is a command-line front-end to YouTube

[Javier P.L.]

Package: wnpp
Severity: wishlist
Owner: "Javier P.L." 

* Package name: yt
  Version : 2013.09.28
  Upstream Author : Rich Wareham 
* URL : https://github.com/rjw57/yt
* License : MIT
  Programming Lang: Python
  Description : yt is a command-line front-end to YouTube

yt is a command-line front-end to YouTube which allows you to browse
YouTube videos and play them directly from the command-line. It uses
youtube-dl and mplayer or omxplayer to actually play the videos


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

Bug#724800: Xlib: extension "RANDR" missing on display

[Trevor A]

Package: xvfb
Version: 2:1.14.3-3
Severity: grave
Justification: renders package unusable

I can no longer use Xvfb or xvfb-run after upgrading. Below is the output of a 
scenario that worked prior to the upgrade.

astrope@trevor:~$ Xvfb :1 &
[1] 25891
astrope@trevor:~$ Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension SELinux
Initializing built-in extension GLX
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing 
from list!
export DISPLAY=:1
astrope@trevor:~$ firefox

(process:25902): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size 
== 0' failed
Xlib:  extension "RANDR" missing on display ":1".


I also tried it with the +extension RANDR with the same result.


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

Bug#724306: Bug #724306: pu: package dpkg/1.16.11

[Guillem Jover]

On Thu, 2013-09-26 at 05:37:30 +0100, Adam D. Barratt wrote:
> On Thu, 2013-09-26 at 04:46 +0200, Guillem Jover wrote:
> > On Tue, 2013-09-24 at 19:47:16 +0100, Adam D. Barratt wrote:
> > > Control: tags -1 + confirmed
> [...]
> > > This looks okay overall; thanks. I'm assuming that the changes have been
> > > tested on a stable system, particularly the Replaces.
> > 
> > Yes. Let me know if and when you want this uploaded to the stable
> > queue.
> 
> Please feel free to go ahead.

Done, thanks!

Regards,
Guillem


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

Bug#585838: rubygems1.8: writes gems only readable by root

[Neil Stockbridge]

Package: rubygems
Version: 1.8.24-1
Followup-For: Bug #585838

Dear Maintainer,

This bug affects me too.  Here is a quick and dirty workaround:


--- /usr/bin/gem.orig 2013-09-28 14:52:12.255306658 +1200
+++ /usr/bin/gem  2013-09-28 14:41:23.919304084 +1200
@@ -9,6 +9,8 @@
 require 'rubygems/gem_runner'
 require 'rubygems/exceptions'
 
+File.umask 022
+
 required_version = Gem::Requirement.new ">= 1.8.7"
 
 unless required_version.satisfied_by? Gem.ruby_version then


-- System Information:
Debian Release: 7.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages rubygems depends on:
ii  ruby1.8  1.8.7.358-7

Versions of packages rubygems recommends:
ii  build-essential  11.5
pn  ruby1.8-dev  

rubygems 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#724320: gmp: x32: sizeof(mp_limb_t)!=sizeof(void*) is not supported by GAP and PARI

[Steve M. Robbins]

Hello,

For readers of gmp-discuss and Daniel Schepler: this concerns a bug reported 
to Debian regarding GMP on the x32 architecture.  In a nutshell: x32 selects a 
limb size of 8, which means it is larger than a pointer and some software 
(gap, pari) fail to build.  The question is whether it makes sense to change
the limb size to 4 on x32.  I'd appreciate your thoughts.

See full thread at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724320

Thanks,
-Steve


On September 24, 2013 10:54:11 PM Bill Allombert wrote:
> On Mon, Sep 23, 2013 at 04:44:15PM -0500, Steve M. Robbins wrote:
> > Bill,
> > 
> > Thanks for clarifying the issue.
> > 
> > On Mon, Sep 23, 2013 at 08:14:58PM +0200, Bill Allombert wrote:
> > > Admittedly, this is a bug in pari and gap for having such requirement.
> > > However, it seems unlikely to be ever fixed, hence this report.
> > > 
> > > Using 8 should result in a faster library, so this is a trade-off, even
> > > if I do not expect that people will use x32 for HPC.
> > 
> > OK, so this trade-off is the real issue.  What is the best choice?
> > 
> > On the one hand, 8 should be faster but how much faster?  Enough to
> > matter?  If not, the choice is clear: switch to 4.
> 
> I suppose it will depend of the hardware. I do not know who will choose
> to use x32 rather than x86_64.
> If the purpose is to save memory, they it could be argued that using 4 is
> better, since this saves 2 bytes on average for each GMP integers.
> (e.g. Numbers < 2^32 are stored on 4 bytes instead of 8).
> 
> > If the speed difference matters, then the question is whether pari and
> > gap are important enough to x32 that we should accept the lower speed.
> > I don't know, myself, but my gut instinct is to leave the size at 8
> > and exclude x32 from the architectures for pari and gap.
> 
> Well, there might be other packages affected, I did not do a full search.
> (It affects packages that uses the mpn class of functions)
> The problem of excluding pari and gap is that this also excludes their
> reverse dependencies.
> 
> Alternatively, both version of ligmp-dev could be provided on x32.
> 
> Cheers,
> Bill.

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

Bug#646377: Xonotic packaging for new games team members (was Nexuiz 2.5.2-7)

[David Bate]

On Friday 27 September 2013 23:17:06 Anton Balashov wrote:
> Hi, Simon.
> Thank you for detailed response! I agree, this reason is not enough
> for upload the new version.
> I wish know that earlier :) Anyway, I got some experience..
> About Xonotic packaging: I have week packaging skills yet and
> Xonotic is a big "project". Don't know, could I be useful?.. I'll
> think and maybe will ask David Bate.
> 
> 
> Thanks you.
> Anton.

Hi Anton,

In the whole Xonotic is big, but we can split it up and it becomes 
much easier :).  The problem is that it is too big for me alone...

Currently the engine that Xonotic uses (Darkplaces) is upto date in 
sid.  The next step is to package

1. gmqcc RFP: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712125
a new QuakeC compiler used in Xonotic, or
2. q3map2 RFP: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693637
the map compiler.

After a quick look, gmqcc looks like a good starting point to learn 
how to package.  I would be willing to help and even have a very quick 
start on the package that I can share if you take up the challenge.

q3map2 could be another start, though the upstream tarball has to be 
cleaned before it is suitable for Debian and so requires (a little) 
more work.
- Possibly we could use the UFO:AI map compiler that is not yet in 
Debian, but looks like it could be soon.  This has the potential of 
completely not working, or producing maps that are somehow not 
compatible with upstream Xonotic (?) but it would reduce clutter and 
maybe our work load.
- Another option would be to skip compiling the maps for a first 
packaging and use the ones provided upstream (along with source), like 
what is currently done for the other Quake derived games in Debian.

These are also options for any of the other new members of the games 
team!

David


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

Bug#724711: insighttoolkit4: Drops architecture support

[Steve M. Robbins]

On September 27, 2013 09:22:58 AM Kurt Roeckx wrote:

> As far as I can see, it builds, it just fails in the test suite.

Sometimes the build itself fails but often it is indeed the test cases.  
However, I make no distinction: software that "builds" but doesn't run 
correctly is no more valuable than software that doesn't build.

> Has anyone actually looked at why it failed?

Sure, people have looked.  The problem is nobody has fixed the failures.


> we need to file bugs against the
> reverse dependencies of this package.

Agreed.

-Steve


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

Bug#724798: qemu-kvm: kvm hangs using high CPU

[Ross Boylan]

Package: qemu-kvm
Version: 1.1.2+dfsg-6
Severity: important

Dear Maintainer,

I have just started using kvm on this system, and twice in the last couple of
days the VM (though not the qemu console) became unresponsive and use of the
host CPU maxed out.  The first time useage was consistent with 2 cores at 100%;
the second time 1 core.

   * What led up to the situation?
invoking kvm with
sudo kvm -cpu pentium3 -smp 2 -hda /dev/sunflower/corn_vdisk -m 2G -soundhw hda
-display sdl -vga std -boot order=c -net nic,macaddr=12:34:56:00:00:01 -net tap
Host hardware is 64 bit, 4-core (each with 2 hyperthreads) Intel(R) Xeon(R) CPU
E3-1245 V2 @ 3.40GHz running Wheezy amd64.  16G ram.

The first time I booted of a virtual CD with the Lenny installer.  I walked the
installation and rebooted.  I did some tweaks to the system and installed
additional packages.  While in aptitude I started typing a package name to
search when the VM became unresponsive.  This used 2 CPU's until I stopped it.

It might be relevant that the virtual disk has a partition managed by LVM, and
provides some encrypted volumes.

The second time I started the system, did more work, and left it overnight.
Late afternoon on the following day it hung up, using one cpu.  I was doing
nothing in the VM at the time (there was an ssh session, as well as the
console).  The failure seemed to coincide with the start of CPU intensive
activities on the host system.


   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I restarted the VM and let the virtual file systems recover from a dirty
shutdown.

For the second failure there was error information in the console; I have
attached a screen capture.  There didn't seem to be any trace of it in the logs
of the VM when I restarted.

   * What was the outcome of this action?
VM back up, though apparently not reliably.

   * What outcome did you expect instead?
The VM just worked.

Comment: I'm not sure I need to emulate a 32 bit PC; I'm doing it to match the
dead system I'm trying to recover as closely as possible.

I found this in the host logs, though I believe these are associated with
bringing the VM back up rather than its failure:
Sep 26 17:45:40 tempserver kernel: [27824.056938] ADDRCONF(NETDEV_UP): tap0:
link is not ready
Sep 26 17:45:40 tempserver kernel: [27824.108960] Bridge firewalling registered
Sep 26 17:45:40 tempserver kernel: [27824.112560] device eth2 entered
promiscuous mode
Sep 26 17:45:40 tempserver kernel: [27824.116976] device eth1 entered
promiscuous mode
Sep 26 17:45:40 tempserver kernel: [27824.197127] ADDRCONF(NETDEV_UP): eth1:
link is not ready
Sep 26 17:45:40 tempserver kernel: [27824.197851] device tap0 entered
promiscuous mode
Sep 26 17:45:40 tempserver kernel: [27824.199665] br0: port 1(eth2) entering
forwarding state
Sep 26 17:45:40 tempserver kernel: [27824.199673] br0: port 1(eth2) entering
forwarding state
Sep 26 17:45:50 tempserver kernel: [27834.544004] br0: no IPv6 routers present
Sep 26 17:46:46 tempserver kernel: [27890.232688] device tap1 entered
promiscuous mode
Sep 26 17:46:46 tempserver kernel: [27890.232709] br0: port 4(tap1) entering
forwarding state
Sep 26 17:46:46 tempserver kernel: [27890.232727] br0: port 4(tap1) entering
forwarding state
Sep 26 17:46:51 tempserver kernel: [27894.948716] kvm: emulating exchange as
write
Sep 26 17:46:56 tempserver kernel: [27900.437117] tap1: no IPv6 routers present



-- Package-specific info:


/proc/cpuinfo:

processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 58
model name  : Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz
stepping: 9
microcode   : 0x16
cpu MHz : 3401.000
cache size  : 8192 KB
physical id : 0
siblings: 8
core id : 0
cpu cores   : 4
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr 
pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c 
rdrand lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi 
flexpriority ept vpid fsgsbase smep erms
bogomips: 6785.31
clflush size: 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model   : 58
model name  : Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz
stepping: 9
microcode   : 0x16
cpu MHz : 3401.000
cache size  : 8192 KB
physical id : 0
siblings: 8
core id : 1
cpu cores   : 4
apicid  : 2
initial apicid  : 2
fpu : yes
fpu_exception   : yes
cpuid leve

Bug#693637: retitle

[David Bate]

Control: retitle -1 RFP: netradiant-q3map2 -- a quake 3 map compiler

I have not really got to work on this yet, and may not happen soon.  
Changing to RFP.


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

Bug#724532: Pending fixes for bugs in the libterm-ui-perl package

[pkg-perl-maintainers]

tag 724532 + pending
thanks

Some bugs in the libterm-ui-perl package are closed in revision
e918931b243cbb88a42dfe6ba900c134b9b7c5aa in branch 'master' by Axel
Beckert

The full diff can be seen at
http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libterm-ui-perl.git;a=commitdiff;h=e918931

Commit message:

Add B-D-I and D on "liblog-message-simple-perl | perl (<< 5.17)"

Closes: #724532


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

Bug#724797: systemd-tmpfiles fails to run during boot with split-usr

[Michael Biebl]

Package: systemd
Version: 204-5
Severity: important

On a (LVM based) test installation with a split /usr configuration,
the systemd-tmpfiles-setup.service service fails to run during boot:
systemd-tmpfiles-setup.service
Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service)
Active: inactive (dead)
start condition failed

Problem is, that the tmpfiles reside on /usr which is not available when
this service is started.
Upstream has changed the fstab generator [1] and assumes that /usr has
been mounted in the initramfs, thus no longer adds usr.mount to
local-fs.target.wants.
We should consider reverting this patch as long as initramfs-tools
doesn't support usr-mount.



[1] 
http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=blob;f=src/fstab-generator/fstab-generator.c;h=c17299f267aefe4ea5247081fbebfff01891f253;hb=HEAD#l199


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

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

Versions of packages systemd depends on:
ii  initscripts  2.88dsf-43
ii  libacl1  2.2.52-1
ii  libaudit11:2.3.2-2
ii  libc62.17-93
ii  libcap2  1:2.22-1.2
ii  libcryptsetup4   2:1.6.1-1
ii  libdbus-1-3  1.6.14-1
ii  libgcrypt11  1.5.3-2
ii  libkmod2 15-0.1
ii  liblzma5 5.1.1alpha+20120614-2
ii  libpam0g 1.1.3-9
ii  libselinux1  2.1.13-2
ii  libsystemd-daemon0   204-5
ii  libsystemd-journal0  204-5
ii  libsystemd-login0204-5
ii  libudev1 204-5
ii  libwrap0 7.6.q-24
ii  udev 207-1
ii  util-linux   2.20.1-5.5

Versions of packages systemd recommends:
ii  libpam-systemd  204-5

Versions of packages systemd suggests:
ii  systemd-ui  2-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#724796: [Pkg-systemd-maintainers] Bug#724796: systemd loses track of rsyslog state when syslog.service is replaced during upgrade

[Michael Biebl]

Am 28.09.2013 02:17, schrieb Michael Biebl:
> Atm, the only workaround I see is to *manually* kill the old rsyslogd
> process in postinst via kill $(cat /run/rsyslogd.pid) before the daemon
> is restarted via invoke-rc.d rsyslog restart.
> This is of course an ugly hack and I assume syslog-ng will be effected
> by this in a similar way.
> not a great solution.

Another option which seems to work, is to "systemctl stop syslog.socket
syslog.service" in rsyslog.preinst of the new version. Then let dpkg
remove the symlink and d-s-h (re)create it in postinst.
The only downside of this approach is, that rsyslog will be down for
quite a while and not log any messages during the dist-upgrade.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#724796: systemd loses track of rsyslog state when syslog.service is replaced during upgrade

[Michael Biebl]

Am 28.09.2013 02:17, schrieb Michael Biebl:

> To reproduce the issue, one can follow those steps:
> - Make sure rsyslog is installed and running.
>   status: step1.txt

The command I used was:
systemctl status rsyslog.service syslog.service syslog.socket

> - rm -f /etc/systemd/system/syslog.service
> - systemctl daemon-reload
>   status: step2.txt
> - re-create symlink: systemctl enable rsyslog.service
> - systemctl daemon-reload
>   status: step3.txt
>   (at this point systemd thinks, rsyslog.service is active (dead), while

correction: if you look at step3.txt, systemd thinks rsyslog.service is
in state *in*active (dead).




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#724796: systemd loses track of rsyslog state when syslog.service is replaced during upgrade

[Michael Biebl]

Package: systemd
Version: 204-5
Severity: important

I've been investigating a dist-upgrade failure, where rsyslog fails to
upgrade properly from its wheezy to jessie version.
The problem is, that the wheezy version shipped the
/etc/systemd/system/syslog.service symlink (pointing to rsyslog.service)
in the package and in jessie we use i-s-h to create the symlink upon
installation. During the upgrade, there is a time frame where the
syslog.service symlink has been removed by dpkg, but postinst has not
been run yet to (re)create the symlink. If at this point a daemon-reload
is issued (e.g. from another package via invoke-rc.d), systemd loses
track of the rsyslog process, which is still running.
So in rsyslog.posinst, when invoke-rc.d rsyslog restart is called,
systemd thinks rsyslog.service is dead and instead of restarting, starts
the service. As the old rsyslog process is still running, this fails.

To reproduce the issue, one can follow those steps:
- Make sure rsyslog is installed and running.
  status: step1.txt
- rm -f /etc/systemd/system/syslog.service
- systemctl daemon-reload
  status: step2.txt
- re-create symlink: systemctl enable rsyslog.service
- systemctl daemon-reload
  status: step3.txt
  (at this point systemd thinks, rsyslog.service is active (dead), while
  the rsyslog process is still happily running
- "systemctl restart rsyslog.service" produces
Job for rsyslog.service failed. See 'systemctl status rsyslog.service'
and 'journalctl -xn' for details.

Atm, the only workaround I see is to *manually* kill the old rsyslogd
process in postinst via kill $(cat /run/rsyslogd.pid) before the daemon
is restarted via invoke-rc.d rsyslog restart.
This is of course an ugly hack and I assume syslog-ng will be effected
by this in a similar way.
not a great solution.

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

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

Versions of packages systemd depends on:
ii  initscripts  2.88dsf-43
ii  libacl1  2.2.52-1
ii  libaudit11:2.3.2-2
ii  libc62.17-93
ii  libcap2  1:2.22-1.2
ii  libcryptsetup4   2:1.6.1-1
ii  libdbus-1-3  1.6.14-1
ii  libgcrypt11  1.5.3-2
ii  libkmod2 15-0.1
ii  liblzma5 5.1.1alpha+20120614-2
ii  libpam0g 1.1.3-9
ii  libselinux1  2.1.13-2
ii  libsystemd-daemon0   204-5
ii  libsystemd-journal0  204-5
ii  libsystemd-login0204-5
ii  libudev1 204-5
ii  libwrap0 7.6.q-24
ii  udev 207-1
ii  util-linux   2.20.1-5.5

Versions of packages systemd recommends:
ii  libpam-systemd  204-5

Versions of packages systemd suggests:
ii  systemd-ui  2-2

-- no debconf information
rsyslog.service - System Logging Service
   Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled)
   Active: active (running) since Sa 2013-09-28 00:52:29 CEST; 1h 16min ago
 Main PID: 6285 (rsyslogd)
   CGroup: name=systemd:/system/rsyslog.service
   └─6285 /usr/sbin/rsyslogd -n

Sep 28 00:52:29 pluto systemd[1]: Started System Logging Service.

rsyslog.service - System Logging Service
   Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled)
   Active: active (running) since Sa 2013-09-28 00:52:29 CEST; 1h 16min ago
 Main PID: 6285 (rsyslogd)
   CGroup: name=systemd:/system/rsyslog.service
   └─6285 /usr/sbin/rsyslogd -n

Sep 28 00:52:29 pluto systemd[1]: Started System Logging Service.

syslog.socket - Syslog Socket
 Loaded: loaded (/lib/systemd/system/syslog.socket; static)
 Active: active (running) since Sa 2013-09-28 00:49:27 CEST; 1h 19min 
ago
   Docs: man:systemd.special(7)
 http://www.freedesktop.org/wiki/Software/systemd/syslog
 Listen: /run/systemd/journal/syslog (Datagram)

Warning: Journal has been rotated since unit was started. Log output is 
incomplete or unavailable.
rsyslog.service - System Logging Service
   Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled)
   Active: active (running) since Sa 2013-09-28 00:52:29 CEST; 1h 18min ago
 Main PID: 6285 (rsyslogd)
   CGroup: name=systemd:/system/rsyslog.service
   └─6285 /usr/sbin/rsyslogd -n

Sep 28 00:52:29 pluto systemd[1]: Started System Logging Service.

syslog.service
   Loaded: error (Reason: No such file or directory)
   Active: inactive (dead)


syslog.socket - Syslog Socket
 Loaded: loaded (/lib/systemd/system/syslog.socket; static)
 Active: active (running) since Sa 2013-09-28 00:49:27 CEST; 1h 21min 
ago
   Docs: man:systemd.special(7)
 http://www.freedesktop.org/wiki/Software/systemd/syslog
 Listen: /run/systemd/journal/syslog (Datagram)

Warning: Journal has been rotated since unit was start

Bug#154693: wmaker requires WMGLOBAL

[Rodolfo García Peñas]

Hi,

please, can you give me more info about the probleam and check if it is 
reproducible in the curren wmaker package?

Thanks a lot.

Best regards,
kix
-- 
 .''`.  Rodolfo García Peñas (kix) 
: :'  : Proud Debian Developer
`. `'`  4096R / 3F48 0B8C C385 AD41 9E28  006A 7B1F 5490 72B7 4923
 `- Debian - when you have better things to do than fixing systems


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

Bug#724023: The problem had been resolved.

[Hans Liao]

Hi,

The problem had been resolved after I got the ibus updates. I needed to
reconfigure everything in ibus, my original settings were not preserved. At
least the Cangjie3 input method is back along with my other input methods.

-- 
Regards

Hans Liao

Bug#723812: Pending fixes for bugs in the libdbd-sqlite3-perl package

[pkg-perl-maintainers]

tag 723812 + pending
thanks

Some bugs in the libdbd-sqlite3-perl package are closed in revision
95028df6cbb2e433cfc6dc159c05f0bd0bb4034f in branch 'master' by
Florian Schlichting

The full diff can be seen at
http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libdbd-sqlite3-perl.git;a=commitdiff;h=95028df

Commit message:

Add fix-test-sort.patch, fix test failure by forcing sqlite to actually 
sort something (closes: #723812)


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

Bug#724789: pu: package glusterfs/3.2.7-3+deb7u1

[Cyril Brulebois]

Control: tag -1 confirmed

Patrick Matthäi  (2013-09-27):
> --- tags/3.2.7-3/debian/changelog 2012-11-12 20:37:46.218864002 +0100
> +++ branches/wheezy/debian/changelog  2013-09-27 21:19:25.155488829 +0200
> @@ -1,3 +1,11 @@
> +glusterfs (3.2.7-3+deb7u1) stable; urgency=low
> +
> +  * Add patch 04-ext4-safe to fix broken glusterfs with Linux
> +>= 3.2.46-1+deb7u1 if you use ext4 as storage backend.
> +Closes: #722694
> +
> + -- Patrick Matthäi   Fri, 27 Sep 2013 21:13:42 +0200

Looks good to me, please upload.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#724795: [request-tracker-maintainers] Bug#724795: request-tracker4: not compatible with libencode-perl >= 2.53

[Dominic Hargreaves]

On Sat, Sep 28, 2013 at 12:15:15AM +0100, Dominic Hargreaves wrote:
> This may warrant a Conflicts (since this is dual-lived, and the
> bundled perl 5.18.1 has Encode 2.49).

Or just apply




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

Bug#724325: xserver-xorg-video-nv: FTBFS against xserver 1.14

[Robert Millan]

Julien Cristau:
> On Wed, Sep 25, 2013 at 10:57:10 +, Robert Millan wrote:
> 
>> Petr Salinger:
 your package needs to be rebuilt against xorg-server 1.14.
 That most likely means pulling in a couple changes from
 upstream git HEAD.
>>> 
>>> It suffices to put attached file into debian/patches/ and
>>> enlist it in debian/patches/series.
>>> 
>>> Please, could some DD (Robert, please) do the upload. Ideally
>>> for both kfreebsd-*, as non-free is usually not auto-build.
>> 
>> I'm on it.
>> 
> AFAICT only kbsd-amd64 was uploaded, not -i386?

kfreebsd-i386 uploaded now.

-- 
Robert Millan


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

Bug#724795: request-tracker4: not compatible with libencode-perl >= 2.53

[Dominic Hargreaves]

Package: request-tracker4
Version: 4.0.17-1
Tags: upstream

This may warrant a Conflicts (since this is dual-lived, and the
bundled perl 5.18.1 has Encode 2.49).

- Forwarded message from Alex Vandiver  -

Date: Fri, 27 Sep 2013 15:24:33 -0400
From: Alex Vandiver 
To: rt-us...@lists.bestpractical.com
Subject: Re: [rt-users] Big problem with encoding subject
Organization: Best Practical Solutions, LLC
X-Mailer: Evolution 3.2.3-0ubuntu6

On Mon, 2013-09-23 at 23:29 +0200, Albert Shih wrote:
> YESSSI find the problem.
> 
> The problem come with the new version of
> 
> p5-Encode-2.55

We've confirmed the bug; it is caused by Encode >= 2.53, and will be
fixed in RT 4.0.18 and 4.2.0.  Until 4.0.18 is released, we suggest
downgrading Encode to version 2.52.
 - Alex


-- 
RT Training in New York, October 8th and 9th: http://bestpractical.com/training

- End forwarded message -


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

Bug#723909: FTBFS: test failures

[Florian Schlichting]

Control: tags 723909 + confirmed

Damyans log snipped doesn't show it, but it't lots of subtests that fail
without any specific output:

t/00-load.t 
Failed 1/2 subtests 
t/01-dependencies.t  ok
t/01-test-mechanize.t .. 
Failed 6/6 subtests 
t/01-test-web.t  
Failed 5/5 subtests 
t/01-version_checks.t .. ok
t/02-connect.t . 
Failed 6/6 subtests 
t/03-form-protocol.t ... ok
t/03-is_passing-no_plan.t .. 
No subtests run 
t/03-is_passing.t .. 
Failed 7/7 subtests 
t/03-test-mailbox.t  
Failed 2/2 subtests 
t/04-test_file.t ... 
No subtests run 
t/05-dispatcher.t .. skipped: Not written 
yet
t/06-forms.t ... 
Failed 24/24 subtests 
t/07-limit-actions.t ... 
Failed 21/21 subtests 
t/08-client.t .. ok
t/09-url.t . 
Failed 6/6 subtests
...

Not all of these are reproducible for me outside the chroot. Those that
are turn out to be segfaults, and as far as I've investigated, they all
look very similar and occur in libsqlite3:

#0  0x7fbe1c61330e in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#1  0x7fbe1c613369 in sqlite3_db_filename () from 
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#2  0x7fbe1c8c968d in sqlite_db_filename () from 
/usr/lib/perl5/auto/DBD/SQLite/SQLite.so
#3  0x7fbe1c8bc45f in ?? () from /usr/lib/perl5/auto/DBD/SQLite/SQLite.so
#4  0x7fbe1cf2df5f in XS_DBI_dispatch () from /usr/lib/perl5/auto/DBI/DBI.so
#5  0x7fbe225cac86 in Perl_pp_entersub () from /usr/lib/libperl.so.5.18
#6  0x7fbe225c32d6 in Perl_runops_standard () from /usr/lib/libperl.so.5.18
#7  0x7fbe2255461c in Perl_call_sv () from /usr/lib/libperl.so.5.18
#8  0x7fbe1cf2e8c1 in XS_DBI_dispatch () from /usr/lib/perl5/auto/DBI/DBI.so
#9  0x7fbe225cac86 in Perl_pp_entersub () from /usr/lib/libperl.so.5.18
#10 0x7fbe225c32d6 in Perl_runops_standard () from /usr/lib/libperl.so.5.18
#11 0x7fbe22554890 in Perl_call_sv () from /usr/lib/libperl.so.5.18
#12 0x7fbe22556967 in Perl_call_list () from /usr/lib/libperl.so.5.18
#13 0x7fbe2253ca5f in ?? () from /usr/lib/libperl.so.5.18
#14 0x7fbe2254df2c in Perl_newATTRSUB_flags () from /usr/lib/libperl.so.5.18
#15 0x7fbe2254ea80 in Perl_newATTRSUB () from /usr/lib/libperl.so.5.18
#16 0x7fbe22551099 in Perl_utilize () from /usr/lib/libperl.so.5.18
#17 0x7fbe22580665 in Perl_yyparse () from /usr/lib/libperl.so.5.18
#18 0x7fbe2255a69c in perl_parse () from /usr/lib/libperl.so.5.18
#19 0x00400d7b in main ()

So maybe this (and the other jifty FTBFS) is related to #723812
(libdbd-sqlite3-perl FTBFS in test suite)?

Florian


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

Bug#724067: quodlibet: Error on initial load

[ondra]

On Sun, Sep 22, 2013 at 01:14:57PM -0400, Philipp Weis wrote:
> Package: quodlibet
> Version: 3.0.2-2
> Severity: normal
> 
> This started happening after upgrading from 2.4.1 to 3.0.2-2. Note
> that I manually installed gir1.2-gtk-3.0 to get past a previous error.
> 
> Attached is a Dump from the error. I can click Cancel in the error
> dialog, and then the UI comes up fine, but as soon as I start playing
> anything, the same error pops up again.

Hi,
I tried reproducing this error in an environment matching your report,
but with no success. Does quodlibet suffer the same when you temporarily
move your ~/.quodlibet directory out of the way?

Also note that quodlibet-plugins 3.x has not yet landed in unstable,
which might be the next probable cause. If moving ~/.quodlibet helps to
let quodlibet start OK, what about disabling all plugins/custom
pipelines if you have set up any?

Cheers,
Ondra


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

Bug#724794: Subject: subversion: sqlite version incompatibility

[James McCoy]

Control: reassign -1 libsvn1 1.7.9-1+nmu4
Control: forcemerge 721878 -1

On Fri, Sep 27, 2013 at 05:34:55PM -0400, Crowley, Stephen wrote:
> svn checkout svn://svn.code.sf.net/p/retroshare/code/trunk retroshare-code
> svn: E200029: Couldn't perform atomic initialization
> svn: E200030: SQLite compiled for 3.8.0.1, but running with 3.7.13

Merging with the other bugs.  Just upgrade your libsqlite3-0 package,
like the message suggests.

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy 


signature.asc
Description: Digital signature

Bug#392943: wmaker: Broken keyboard shortcuts with new default theme

[Rodolfo García Peñas]

Hi,

The current version of wmaker uses a new upstream since version 0.95.0. I am 
closing old bugs, because wmaker has been changed a lot.

this bug is very old. Can I close it?

Regards,
kix
-- 
 .''`.  Rodolfo García Peñas (kix) 
: :'  : Proud Debian Developer
`. `'`  4096R / 3F48 0B8C C385 AD41 9E28  006A 7B1F 5490 72B7 4923
 `- Debian - when you have better things to do than fixing systems


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

Bug#724678: RM: flightgear [kfreebsd-*] -- RoM; ANAIS due to missing systemd

[Rebecca N. Palmer]

I was unaware of the libusbhid-dev alternative at the time I suggested 
removal (everything else that depends on libudev is Linux-only: 
http://release.debian.org/transitions/html/libudev.html), and agree that 
it would now make more sense to try Pino's patch.



Does the package also actually work on non-Linux ?

What I'm concerned about is, that we are building software which isn't
actually runnable.


Upstream supports FreeBSD 
(http://www.flightgear.org/download/main-program/), but I don't know if 
that automatically translates to Debian-kFreeBSD.



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

Bug#721839: RFS: musl/0.9.13-2 [ITP]

[Kevin Bortis]

I have packed the newest upstream version 0.9.14

It builds those binary packages:

  musl  - standard C library
  musl-dev   - standard C library development files
  musl-tools - standard C library tools

To access further information about this package, please visit the
following URL:

  http://mentors.debian.net/package/musl

 Alternatively, one can download the package with dget using this command:

dget -x http://mentors.debian.net/debian/pool/main/m/musl/musl_0.9.14-1.dsc

Changes since the last upload:

  * Import upstream version 0.9.14
  * Only build on fully supported architectures
  * Point to new homepage in control file (Closes: #724277)
  * Revorked debian/rules
  * Solved possible problem with postrm script (Closes: #724247)

I would appreciate if someone could upload the package.

  Regards,
   Kevin Bortis

On Sat, Sep 21, 2013 at 2:15 PM, Anton Gladky  wrote:
> Ok, I uploaded it.  Have done only minor change:
>
> diff --git a/debian/changelog b/debian/changelog
> index 346bdf2..9e328e6 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,6 +1,6 @@
>  musl (0.9.13-3) unstable; urgency=low
>
> -  * Ready for Debian upload  (Closes: #721839)
> +  * Ready for Debian upload  (Closes: #713072)
>* Respect user set CC
>* Reworked package according to feedback gven
>  by Anton Gladky. See #721839 for reference.
>
>
> So you should close only ITP-bug. RFS-bug will be closed
> manually.
>
> Please, for future upload create only one additional
> changelog-paragraph.
>
> Cheers,
>
> Anton
>
>
> 2013/9/21 Kevin Bortis :
>> Hi
>>
>> I have revorked the debian/copyright file according to the additional
>> comments given by Paul Richards Tagliamonte (FTP Master).
>>
>> Work done:
>>   * Incorporated all copyright info given from upstream in their copyright 
>> file
>>   * grep over complete source tree for the term "Copyright" and
>> controlled it against debian/copyright
>>
>> I hope to statisfy all copyright holders and of course the Debian policy.
>>
>> The updated copyright file can be found for review under:
>> https://github.com/wermut/musl/blob/master/debian/copyright
>> https://github.com/wermut/musl
>>
>> The updated package is not yet uploaded to debian mentors.
>>
>> Sorry for the inconvenience and additional work.
>>
>> @ Boris Pek: Thank you for the tip.
>>
>> Regards
>>   Kevin
>>
>> On Fri, Sep 20, 2013 at 11:39 PM, Boris Pek  wrote:
>>> Hi Kevin,
>>>
>>  The package was not yet uploaded into Debian.
>>  - The package number should be 0.9.13-1
>
>  Could I still keep the incrementation, because the earlier versions
>  are already tagged & signed in the public git repository and also
>  already uploaded to a Ubuntu PPA? (ppa:bortis/musl) So the first
>  version for uploading would be 0.9.13-3 if you accept. Or we can wait
>  for musl 0.9.14 wich, according to upstreams roadmap, will be released
>  in the next two weeks to get a clean 0.9.14-1.

 My feeling is that you'll need to keep the Ubuntu PPA and the Debian
 package seperated and have them NOT in the same git branch. This will
 save you trouble down the road as Debian != Ubuntu in many aspects and
 you will face situations where you need only to upload Debian or
 Ubuntu...
>>>
>>> Just small additional tips: use specific versioning scheme in your PPA.
>>> For example: 0.9.14-0ppa1~raring1. As you can see, this version is lower 
>>> that
>>> version in official Debian and Ubuntu archives. So once updated package 
>>> will hit
>>> into main archive, it will be updated in users systems.
>>>
>>> I use this approach for a long period of time. You may find one of examples 
>>> here:
>>> https://launchpad.net/~tehnick/+archive/q4wine/+packages
>>> Just look at "Newer version available" string.
>>>
>>> Related Git-repo:
>>> https://github.com/tehnick/q4wine-debian
>>> Just look at git tags.
>>>
>>> Best wishes,
>>> Boris


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

Bug#722521: [Pkg-systemd-maintainers] Bug#722521: Fails to properly re-enable service on install-remove-install sequence

[Michael Biebl]

Am 12.09.2013 00:41, schrieb Michael Biebl:
> Package: init-system-helpers
> Version: 1.8
> Severity: important
> 
> Hi Michael,
> 
> to reproduce the problem, do the following steps:
> 1/ apt-get install rsyslog
>→ symlinks are properly created
> # find systemd/ -name "*syslog*"
> systemd/system/multi-user.target.wants/rsyslog.service
> systemd/system/syslog.service
> 
> 2/ apt-get remove rsyslog
>→ symlinks are removed
> # apt-get remove rsyslog
> [..]
> rm '/etc/systemd/system/multi-user.target.wants/rsyslog.service'
> rm '/etc/systemd/system/syslog.service'
> 
> 3/ apt-get install rsyslog
>→ symlinks are not re-created
> 


So, I've tested this sequence today again, and this issue is not yet fully 
sorted. 
The latest i-s-h/dh-systemd release no longer runs disable on postrm/remove:

root@pluto:/etc# dpkg -r rsyslog
(Lese Datenbank ... 276158 Dateien und Verzeichnisse sind derzeit installiert.)
Entfernen von rsyslog ...
ln -s '/dev/null' '/etc/systemd/system/rsyslog.service'
root@pluto:/etc# ls -al /etc/systemd/system
system/  system.conf  
root@pluto:/etc# ls -al /etc/systemd/system/syslog.service 
/etc/systemd/system/multi-user.target.wants/rsyslog.service 
lrwxrwxrwx 1 root root 35 Sep 27 23:55 
/etc/systemd/system/multi-user.target.wants/rsyslog.service -> 
/lib/systemd/system/rsyslog.service
lrwxrwxrwx 1 root root 35 Sep 27 23:55 /etc/systemd/system/syslog.service -> 
/lib/systemd/system/rsyslog.service


Those dangling symlinks are problematic, e.g. you can *not* install syslog-ng 
cleanly
and take over that symlink.

We currently only run "deb-systemd-helper disable" on purge, and no longer on
remove, I think this is how #722521 was "fixed".

Running "deb-systemd-helper disable" is problematic though, i.e. it
makes "deb-systemd-helper --quiet was-enabled" return "disabled".

# was-enabled defaults to true, so new installations run enable.
if deb-systemd-helper --quiet was-enabled rsyslog.service; then
# Enables the unit on first installation, creates new
# symlinks on upgrades if the unit file has changed.
deb-systemd-helper enable rsyslog.service >/dev/null || true
else

As a consequence, we don't re-enable the service on 
dpkg -r && dpkg -i


I think we need to distinguish here between admin disabled (via systemctl 
disable) 
and disabled by d-s-h.

This needs further discussion, how we address this.

Should I re-open this bug report or file a new one?

Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#721733: ***SPAM Hits=5.4*** Upstream removed __version_info__ from paramiko/__init__.py

[Mike Gabriel]

retitle 721733 Upstream removed __version_info__ from paramiko/__init__.py
reassign 721733 python-paramiko
severity 721733 minor
tag 721733 patch
thanks

Dear maintainer (of python-paramiko),

as you can read in the history of this re-assigned bug, there is a  
problem with more recent versions of paramiko and the mysql-workbench  
package in wheezy.


I have suggested to upstream reintroducing the __verion_info__  
variable in paramiko/__init__.py and also filed that as a pull request  
on Github [1].


I suggest adding the attached patch to the recent python-paramiko  
Debian packages.


Regards,
Mike

[1] https://github.com/paramiko/paramiko/pull/215



--

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
Description: Reintroduce __version_info__ as it breaks mysql-workbench 
Author: Mike Gabriel 
--- a/paramiko/__init__.py
+++ b/paramiko/__init__.py
@@ -87,6 +87,8 @@
 from config import SSHConfig
 from proxy import ProxyCommand
 
+__version_info__ = tuple([ int(d) for d in __version__.split(".") ])
+
 # fix module names for epydoc
 for c in locals().values():
 if issubclass(type(c), type) or type(c).__name__ == 'classobj':


binddXyYdS0Xt.bin
Description: Öffentlicher PGP-Schlüssel


pgpZIcMNJRdw4.pgp
Description: Digitale PGP-Signatur

Bug#724794: Subject: subversion: sqlite version incompatibility

[Crowley, Stephen]

Subject: subversion: sqlite version incompatibility
Package: subversion
Version: 1.7.9-1+nmu4
Severity: important


svn checkout svn://svn.code.sf.net/p/retroshare/code/trunk retroshare-code
svn: E200029: Couldn't perform atomic initialization
svn: E200030: SQLite compiled for 3.8.0.1, but running with 3.7.13


-- System Information:
Debian Release: 7.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386


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


Versions of packages subversion depends on:
ii libapr1 1.4.8-1
ii libc6 2.17-92+b1
ii libsasl2-2 2.1.25.dfsg1-6+deb7u1
ii libsvn1 1.7.9-1+nmu4


subversion recommends no packages.


Versions of packages subversion suggests:
pn db5.1-util 
ii patch 2.6.1-3
pn subversion-tools 


-- no debconf information

-- 
*Stephen* *Crowley*
*Principal* *|**International Equities Group*
*Canaccord Genuity Inc. *
350 Madison Avenue
New York*, *NY10017
T: 212-389-8193 C: 917-376-7830 IM:scrowleycg
E: scrow...@canaccordgenuity.com  | 
www.canaccordgenuity.com

--
The information contained in this communication may be confidential and/or 
legally privileged. If you are not the intended recipient, please contact the 
sender and destroy all copies of this message and any attachments. Any 
disclosure, copying, distribution or taking any action in reliance on this 
information other than by the intended recipient is strictly prohibited and may 
be unlawful. Canaccord Genuity Inc. is required by regulation to review and 
store both outgoing and incoming electronic correspondence. E-mail 
transmissions cannot be guaranteed to be secure, timely or error-free. This 
communication is not an offer or solicitation to buy or sell any security or 
other investment product. Additional information, including disclosures 
regarding securities under research coverage, is available at 
http://www.canaccordgenuity.com/en/Our-Company/Research/ . Any information 
regarding specific investment products is subject to change without notice. 
Canaccord Genuity Inc. - Member FINRA/SIPC.


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

Bug#722062: linux-image-3.10-2-amd64: Please enable CONFIG_SENSORS_JC42=m and CONFIG_SENSORS_NCT6775=m

[Dmitry Eremin-Solenikov]

Package: src:linux
Version: 3.10.11-1
Followup-For: Bug #722062

Please enable JC42. It is a sensor module frequently used to monitor
temerature of DIMM modules.

-- Package-specific info:
** Version:
Linux version 3.10-3-amd64 (debian-ker...@lists.debian.org) (gcc version 4.7.3 
(Debian 4.7.3-7) ) #1 SMP Debian 3.10.11-1 (2013-09-10)

** Command line:
BOOT_IMAGE=/vmlinuz-3.10-3-amd64 root=/dev/mapper/rohan-root ro 
8250.nr_uarts=12 quiet

** Tainted: PIO (6145)
 * Proprietary module has been loaded.
 * Working around severe firmware bug.
 * Out-of-tree module has been loaded.

** Kernel log:
[   22.786087] nvidia :03:00.0: irq 71 for MSI/MSI-X
[   25.150853] tg3 :06:00.0 eth0: Link is up at 1000 Mbps, full duplex
[   25.150922] tg3 :06:00.0 eth0: Flow control is off for TX and off for RX
[   25.150938] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   65.302182] <6>[fglrx] Maximum main memory to use for locked dma buffers: 
17691 MBytes.
[   65.302862] <3>[fglrx:firegl_init_device_list] *ERROR* No supported display 
adapters were found
[   65.302865] <3>[fglrx:firegl_init_module] *ERROR* firegl_init_devices failed
[  151.811694] vboxdrv: Found 8 processor cores.
[  151.811962] vboxdrv: fAsync=0 offMin=0x23e offMax=0x21ef
[  151.812049] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 
'normal'.
[  151.812052] vboxdrv: Successfully loaded version 4.2.18 (interface 
0x001a0005).
[  152.024896] vboxpci: IOMMU not found (not registered)
[  158.795628] <6>[fglrx] Maximum main memory to use for locked dma buffers: 
17691 MBytes.
[  158.795856] <6>[fglrx]   vendor: 1002 device: 954f count: 1
[  158.796369] <6>[fglrx] ioport: bar 4, base 0xcc00, size: 0x100
[  158.796376] pci :04:00.0: enabling device (0002 -> 0003)
[  158.796951] <6>[fglrx] Kernel PAT support is enabled
[  158.796968] <6>[fglrx] module loaded - fglrx 8.97.2 [Nov 16 2012] with 1 
minors
[  285.359227] traps: ld-linux-x32.so[11760] general protection ip:f76fee8d 
sp:ffdbab08 error:0 in ld-2.17.so[f76e8000+21000]
[  285.409419] traps: ld-linux-x32.so[11782] general protection ip:f7706e8d 
sp:ffe47ce8 error:0 in ld-2.17.so[f76f+21000]
[  285.425257] traps: ld-linux-x32.so[11796] general protection ip:f77b2e8d 
sp:ffeceac8 error:0 in ld-2.17.so[f779c000+21000]
[  285.441043] traps: ld-linux-x32.so[11810] general protection ip:f7743e8d 
sp:ff9ed5c8 error:0 in ld-2.17.so[f772d000+21000]
[  285.456702] traps: ld-linux-x32.so[11824] general protection ip:f771fe8d 
sp:ffe48238 error:0 in ld-2.17.so[f7709000+21000]
[  285.472329] traps: ld-linux-x32.so[11838] general protection ip:f7771e8d 
sp:ffe734b8 error:0 in ld-2.17.so[f775b000+21000]
[  285.488026] traps: ld-linux-x32.so[11852] general protection ip:f7708e8d 
sp:ff9aa298 error:0 in ld-2.17.so[f76f2000+21000]
[  285.544036] traps: ld-linux-x32.so[11880] general protection ip:f77aee8d 
sp:ffc478e8 error:0 in ld-2.17.so[f7798000+21000]
[  285.640493] traps: ld-linux-x32.so[11926] general protection ip:f77c6e8d 
sp:ffe47268 error:0 in ld-2.17.so[f77b+21000]
[  285.826934] traps: ld-linux-x32.so[12022] general protection ip:f778ee8d 
sp:ffc907e8 error:0 in ld-2.17.so[f7778000+21000]
[  291.873373] do_general_protection: 29 callbacks suppressed
[  291.873379] traps: ld-linux-x32.so[14984] general protection ip:f77bde8d 
sp:ffe7c4e8 error:0 in ld-2.17.so[f77a7000+21000]
[  298.877646] traps: ld-linux-x32.so[15429] general protection ip:f7712e8d 
sp:ffd57488 error:0 in ld-2.17.so[f76fc000+21000]
[  298.907607] traps: ld-linux-x32.so[15451] general protection ip:f77dee8d 
sp:ffc2e328 error:0 in ld-2.17.so[f77c8000+21000]
[  298.922999] traps: ld-linux-x32.so[15465] general protection ip:f7799e8d 
sp:fff9de08 error:0 in ld-2.17.so[f7783000+21000]
[  298.938213] traps: ld-linux-x32.so[15479] general protection ip:f773fe8d 
sp:ffce1038 error:0 in ld-2.17.so[f7729000+21000]
[  298.953687] traps: ld-linux-x32.so[15493] general protection ip:f7713e8d 
sp:ffb876f8 error:0 in ld-2.17.so[f76fd000+21000]
[  298.969143] traps: ld-linux-x32.so[15507] general protection ip:f7788e8d 
sp:ffb4e548 error:0 in ld-2.17.so[f7772000+21000]
[  298.984725] traps: ld-linux-x32.so[15521] general protection ip:f77c9e8d 
sp:ffd97b28 error:0 in ld-2.17.so[f77b3000+21000]
[  299.024429] traps: ld-linux-x32.so[15549] general protection ip:f774fe8d 
sp:ff9f8688 error:0 in ld-2.17.so[f7739000+21000]
[  299.096335] traps: ld-linux-x32.so[15595] general protection ip:f7776e8d 
sp:ffd87518 error:0 in ld-2.17.so[f776+21000]
[  304.367111] do_general_protection: 30 callbacks suppressed
[  304.367117] traps: ld-linux-x32.so[18612] general protection ip:f77c6e8d 
sp:ffab7a48 error:0 in ld-2.17.so[f77b+21000]
[  319.418115] traps: ld-linux-x32.so[19803] general protection ip:f77f3e8d 
sp:ff8a6598 error:0 in ld-2.17.so[f77dd000+21000]
[  319.448194] traps: ld-linux-x32.so[19825] general protection ip:f77b4e8d 
sp:ffd6b338 error:0 in ld-2.17.so[f779e000+21000]
[  319.463808] traps: ld-linux-x32.so[198

Bug#724580: nmap: ncat segfaults when scanned with nmap --script 'ssl*,tls*'

[Fyodor]

On Wed, Sep 25, 2013 at 3:10 AM, Timo Juhani Lindfors
wrote:

> Package: nmap
> Version: 6.40-0.1
> Severity: normal
>
> Steps to reproduce:
> 1) ncat -k --ssl -l localhost 443
> 2) nmap -sC --script-trace --script 'ssl*,tls*' -6 localhost -p 443
>
> Expected results:
> 2) ncat does not segfault
>
> Actual results:
> 2) ncat segfaults, dmesg shows
>

Thanks for the report.  I was able to reproduce this with our latest Nmap
svn version on Fedora, so it doesn't seem specific to the Debian package.
 I am adding an entry to our todo list for fixing this.

-Fyodor

Bug#724678: RM: flightgear [kfreebsd-*] -- RoM; ANAIS due to missing systemd

[Michael Biebl]

Hi,

Am 27.09.2013 22:05, schrieb Steven Chamberlain:
> Control: block 724678 by 724686
> 
> On 26/09/13 15:34, Markus Wanner wrote:
>> as correctly reported by Rebecca N. Palmer, flightgear no longer builds
>> on kfreebsd-* (due to systemd dependency). Please remove the kfreebsd
>> variants of the flightgear binary package from testing.
> 
> I'm a little concerned by this:
> 
> * that a package can 'Build-Depend' on systemd seems rather odd,

It build-depends on libudev-dev, which is not quite the same.

> * as a sign of things to come, that systemd's non-portability is
> spreading to other software,

libudev has always been Linux-specific, nothing new here.

> * that the package's removal is requested, AFAIK without mentioning this
> to debian-bsd@, or Cc'ing us on a FTBFS bug for example so that someone
> might take a look at this.
> 
> But thankfully Pino Toscano contributed a patch that can fix this, by
> simply changing the Build-Depends, therefore I hope the removal is not
> needed now:  http://bugs.debian.org/724686

Does the package also actually work on non-Linux ?

What I'm concerned about is, that we are building software which isn't
actually runnable.
A good example is gnome-shell, which takes a lot of effort to keep
building on non-Linux but ttbomk is totally non-functional on e.g.
kfreebsd. Removing software for those architectures is imho more honest.

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#724275: uswsusp: Stops at boot with "resume: libgcrypt version 1.5.3"

[Philipp Huebner]

Hi

On 27/09/13 19:32, Rodolfo García Peñas wrote:
> can you try it?

I just did. Unfortunately without success, the behaviour is the same as
before.

In the meantime I had uswsusp purged to be able to boot normally. It's a
workaround, but not a solution.

Regards,
-- 
 .''`.   Philipp Huebner 
: :'  :  pgp fp: 6719 25C5 B8CD E74A 5225  3DF9 E5CA 8C49 25E4 205F
`. `'`
  `-



signature.asc
Description: OpenPGP digital signature

Bug#721844: transition: ibus

[Julien Cristau]

On Fri, Sep 27, 2013 at 23:11:15 +0900, Osamu Aoki wrote:

> 
> Why BTS believes #712575 affects 1.5.3-3?  Was this some automatic logic
> or was this due to my bad communication in my original transition bug
> report text.
> 
Because none of the versions in the sid package's changelog were marked
as having this bug fixed.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#724793: RM: kfreebsd-headers-9-686 [i386] -- ANAIS; obsolete package

[Steven Chamberlain]

Package: ftp.debian.org
X-Debbugs-Cc: debian-...@lists.debian.org

Hi,

Following on from #720320, please could you also remove this
meta-package for the same reason (ANAIS; obsolete package) :

kfreebsd-headers-9-686 | 9.2~svn255465-1 | i386

Thank you!
Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


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

Bug#702241: gnome-packagekit: gpk-update-viewer does not update package index so falsely says is up to date.

[nodiscc]

Package: gnome-packagekit
Version: 3.8.2-4
Followup-For: Bug #702241

Hi,
I have this exact problem on Jessie, gnome-packagekit 3.8.2-4.
So this is not a wheezy-related bug. I have made sure packagekitd and
gnome-settings-daemon were running, and that the "updates" g-s-d plugin
was enabled. gpk-prefs has the "check for updates" value set to "daily".

The cron job workaround works for me, but this is definitely a hack.

Any idea about what's happening?

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

Kernel: Linux 3.10-2-686-pae (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

Versions of packages gnome-packagekit depends on:
ii  gnome-packagekit-session  3.8.2-4
ii  libatk1.0-0   2.8.0-2
ii  libc6 2.17-92+b1
ii  libcairo-gobject2 1.12.14-4
ii  libcairo2 1.12.14-4
ii  libcanberra-gtk3-00.30-2
ii  libcanberra0  0.30-2
ii  libdbus-1-3   1.6.14-1
ii  libdbus-glib-1-2  0.100.2-1
ii  libfontconfig12.10.2-2
ii  libgdk-pixbuf2.0-02.28.2-1
ii  libglib2.0-0  2.36.4-1
ii  libgtk-3-03.8.4-1
ii  libnotify40.7.6-1
ii  libpackagekit-glib2-160.8.10-2
ii  libpango-1.0-01.32.5-5+b1
ii  libpangocairo-1.0-0   1.32.5-5+b1
ii  libpolkit-gobject-1-0 0.105-3
ii  libsqlite3-0  3.8.0.2-1
ii  libsystemd-login0 204-4
ii  libupower-glib1   0.9.21-3
ii  libx11-6  2:1.6.1-1

gnome-packagekit recommends no packages.

Versions of packages gnome-packagekit suggests:
pn  gnome-packagekit-tools  

-- 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#724721: zsh: Tab completion error with vi

[Ludovic Lebègue]

Hi Frank

It indeed happened after an update to a new version of zsh.

Head of dump :

ludo@leonardo ~ % head .zcompdump 
#files: 693 version: 5.0.2

_comps=(
'-' '_precommand'
'.' '_source'
'5g' '_go'
'5l' '_go'
'6g' '_go'
'6l' '_go'
'8g' '_go'


Deleting the .zcompdump file fixed this bug.

Thank you.

On Fri, 2013-09-27 at 09:55 +0200, Frank Terbeck wrote:
> Hi Ludovic,
> 
> Ludovic Lebègue wrote:
> [...]
> > While using zsh shell trying to autocomplete with tab key display the 
> > following
> > message instead of showing the files in the current directory :
> >
> > ludo@leonardo ~ % vi
> > _arguments:450: _vim_files: function definition file not found
> 
> Did this happen after updating zsh? What's the old zsh version?
> 
> In any case, what's the output of following?
> 
>   % head ~/.zcompdump
> 
> 
> Problems like this are usually cause by that cache file being out of
> date and something is keeping an automatic rebuild from happening.
> 
> If you remove the file and restart the shell, the problem should be
> gone.
> 
> Regards, Frank



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

Bug#724721: [Pkg-zsh-devel] Bug#724721: zsh: Tab completion error with vi

[Ludovic Lebègue]

Hi

Checksum are OK.

Here is my try :

ludo@leonardo ~ % md5sum /usr/share/zsh/functions/Completion/Unix/_vim
d90eb09ccc0a48b9337ada7f71d8e803  /usr/share/zsh/functions/Completion/Unix/_vim
ludo@leonardo ~ % md5sum /usr/share/zsh/functions/Completion/Unix.zwc
4be49e59d09c72925b42dc4605511265  /usr/share/zsh/functions/Completion/Unix.zwc
ludo@leonardo ~ % zsh -f
leonardo% autoload -Uz compinit
leonardo% compinit
leonardo% vi
leonardo% exit
ludo@leonardo ~ % vi 
_arguments:450: _vim_files: function definition file not found
ludo@leonardo ~ % vi


Autocompletion  is ok when I launch your sequence of commands. Going
back to my current zsh shell shows the same error as before.


On Fri, 2013-09-27 at 09:11 +0200, Axel Beckert wrote:
> Control: tag -1 + unreproducible moreinfo
> 
> Hi Ludovic,
> 
> Ludovic Lebègue wrote:
> > While using zsh shell trying to autocomplete with tab key display the 
> > following
> > message instead of showing the files in the current directory :
> > 
> > ludo@leonardo ~ % vi
> > _arguments:450: _vim_files: function definition file not found
> 
> I just tried to reproduce this, but it seems to work for me (also on
> Sid amd64):
> 
> % zsh -f
> kiva6% autoload -Uz compinit
> kiva6% compinit
> kiva6% vi 
> zsh: do you wish to see all 109 possibilities (55 lines)? 
> 
> _vim_files is a function defined in
> /usr/share/zsh/functions/Completion/Unix/_vim
> 
> Can you check that this file exists and has the following md5sum:
> 
> % md5sum /usr/share/zsh/functions/Completion/Unix/_vim
> d90eb09ccc0a48b9337ada7f71d8e803 /usr/share/zsh/functions/Completion/Unix/_vim
> 
> There's also a precompiled version of it in Unix.zwc, so please also
> check the existence and MD5 hashsum of that file:
> 
> %  md5sum /usr/share/zsh/functions/Completion/Unix.zwc
> 4be49e59d09c72925b42dc4605511265  /usr/share/zsh/functions/Completion/Unix.zwc
> 
> If that looks fine, can you please check it from a zsh without config
> as I did above:
> 
> Your zsh config: % zsh -f
> Without config:  % autoload -Uz compinit
> Without config:  % compinit
> Without config:  % vi 
> 
> > Versions of packages zsh depends on:
> [...]
> > ii  zsh-common  5.0.2-4
> 
> This looks fine.
> 
>   Regards, Axel



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

Bug#724791: RFS: gogglesmm/0.12.7-2

[Hendrik Rittich]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "gogglesmm"

 * Package name: gogglesmm
   Version : 0.12.7-2
   Upstream Author : Sander Jansen 
 * URL : http://code.google.com/p/gogglesmm/
 * License : GPLv3
   Section : sound

It builds those binary packages:

  gogglesmm  - Goggles Music Manager

To access further information about this package, please visit the following 
URL:

  http://mentors.debian.net/package/gogglesmm


Alternatively, one can download the package with dget using this command:

  dget -x 
http://mentors.debian.net/debian/pool/main/g/gogglesmm/gogglesmm_0.12.7-2.dsc

More information about hello can be obtained from http://www.example.com.

Changes since the last upload:

 * Changed dependencies from libxine-dev to libxine2-dev, closes: #724762


Regards,
 Hendrik Rittich


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

Bug#719396: libcitygml: FTBFS: debian/gencontrol: 6: debian/gencontrol: Illegal number: 0~rc1

[peter green]

The code that fails is

LIBOSG_SHARE=`dpkg --get-selections|awk '{print $1}'|grep 
libopenscenegraph[0-9]`
LIBOSG_VERSION=`dpkg -l $LIBOSG_SHARE |grep $LIBOSG_SHARE |sed 's/-/ /' 
|awk '{print $3}'`

TMP1=`echo $LIBOSG_VERSION|awk -F '.' '{print $1}'`
TMP2=`echo $LIBOSG_VERSION|awk -F '.' '{print $2}'`
TMP3=`echo $LIBOSG_VERSION|awk -F '.' '{print $3}'`
TMP3=$((TMP3+1))
LIBOSG_VERSIONPLUS=$TMP1.$TMP2.$TMP3
echo $LIBOSG_VERSION
dh_gencontrol -- -Vlibosg-share="$LIBOSG_SHARE" 
-Vlibosg-static="libopenscenegraph-dev (>=$LIBOSG_VERSION), 
libopenscenegraph-dev (<< $LIBOSG_VERSIONPLUS)"


This seems to be trying to create a >= relation on the current 
libopenscenegraph "upstream version" and a << relation on the "next" 
libopenscenegraph "upstream version" assuming that libosg "upstream 
versions" follow the pattern x.y.z where x y and z are integers.


However the current libosg "upstream version" is 3.2.0~rc1 . This means 
that the code ends up trying to add 1 to "0~rc1" and fails.


I made two changes to this code in my patch.
1: I added code to strip stuff after the ~ before adding 1
2: I added a ~ to the generated "next version". This ensures that if the 
next upstream version has release candidates that they are properly 
caught by the << dependency relationship.


Note that this assumes that release candidates are sufficiently 
compatible with the corresponding final versions. If they are not then a 
stricter dependency check may be needed.


Debdiff attatched, no intent to NMU.
diff -Nru libcitygml-0.14+svn128/debian/changelog 
libcitygml-0.14+svn128/debian/changelog
--- libcitygml-0.14+svn128/debian/changelog 2013-02-01 16:23:03.0 
+
+++ libcitygml-0.14+svn128/debian/changelog 2013-09-27 17:13:01.0 
+
@@ -1,3 +1,10 @@
+libcitygml (0.14+svn128-1+3p0p1+4+rpi1) jessie-staging; urgency=low
+
+  * Make code in debian/gencontrol handle releasecandidate version of
+openscenegraph correctly. (Closes: #719396)
+
+ -- Peter Michael Green   Fri, 27 Sep 2013 17:11:40 
+
+
 libcitygml (0.14+svn128-1+3p0p1+4) unstable; urgency=low
 
   [Sebastian Ramacher]
diff -Nru libcitygml-0.14+svn128/debian/gencontrol 
libcitygml-0.14+svn128/debian/gencontrol
--- libcitygml-0.14+svn128/debian/gencontrol2012-06-12 17:21:06.0 
+
+++ libcitygml-0.14+svn128/debian/gencontrol2013-09-27 17:11:17.0 
+
@@ -3,7 +3,8 @@
 TMP1=`echo $LIBOSG_VERSION|awk -F '.' '{print $1}'`
 TMP2=`echo $LIBOSG_VERSION|awk -F '.' '{print $2}'`
 TMP3=`echo $LIBOSG_VERSION|awk -F '.' '{print $3}'`
+TMP3=`echo $TMP3|awk -F '~' '{print $1}'`
 TMP3=$((TMP3+1))
-LIBOSG_VERSIONPLUS=$TMP1.$TMP2.$TMP3
+LIBOSG_VERSIONPLUS=$TMP1.$TMP2.$TMP3~
 echo $LIBOSG_VERSION
 dh_gencontrol -- -Vlibosg-share="$LIBOSG_SHARE" 
-Vlibosg-static="libopenscenegraph-dev (>=$LIBOSG_VERSION), 
libopenscenegraph-dev (<< $LIBOSG_VERSIONPLUS)"

Bug#724792: electrum does not have python-qt4 as dependency

[Ati Sharma]

Package: electrum
Version: 1.8-1
Severity: normal

Dear Maintainer,

# aptitude install electrum
installs electrum but does not install python-qt4 which should be a
dependency.

electrum thus fails to start. Installing python-qt4 fixes the problem.

thanks


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

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

Versions of packages electrum depends on:
ii  python   2.7.5-5
ii  python-electrum  1.8-1

electrum recommends no packages.

electrum 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#724678: RM: flightgear [kfreebsd-*] -- RoM; ANAIS due to missing systemd

[Guillem Jover]

Hi!

On Thu, 2013-09-26 at 16:34:06 +0200, Markus Wanner wrote:
> Package: release.debian.org
> Tags: jessie
> User: release.debian@packages.debian.org
> Usertags: rm
> X-Debbugs-Cc: pkg-fgfs-c...@lists.alioth.debian.org
> X-Debbugs-Cc: r.pal...@bham.ac.uk

> as correctly reported by Rebecca N. Palmer, flightgear no longer builds
> on kfreebsd-* (due to systemd dependency). Please remove the kfreebsd
> variants of the flightgear binary package from testing.

There should be no need for this any longer, as Pino Toscano has
provided a patch while reporting the bug report 724686.

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#724678: RM: flightgear [kfreebsd-*] -- RoM; ANAIS due to missing systemd

[Steven Chamberlain]

Control: block 724678 by 724686

On 26/09/13 15:34, Markus Wanner wrote:
> as correctly reported by Rebecca N. Palmer, flightgear no longer builds
> on kfreebsd-* (due to systemd dependency). Please remove the kfreebsd
> variants of the flightgear binary package from testing.

I'm a little concerned by this:

* that a package can 'Build-Depend' on systemd seems rather odd,

* as a sign of things to come, that systemd's non-portability is
spreading to other software,

* that the package's removal is requested, AFAIK without mentioning this
to debian-bsd@, or Cc'ing us on a FTBFS bug for example so that someone
might take a look at this.

But thankfully Pino Toscano contributed a patch that can fix this, by
simply changing the Build-Depends, therefore I hope the removal is not
needed now:  http://bugs.debian.org/724686

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


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

Bug#721805: hdf5 misbehaves when compiled with gcc 4.8.0

[Antonio Valentino]

Hi Francesco, hi Sylvestre,
this bug has been fixed upstream.
Please find attached a patch tho backport the fix to HDF5 1.8.11.

I should have commit access to the repo of the debian package [2] so
please let me know if you want me to update the package to include the
patch.


[1]
http://mail.lists.hdfgroup.org/pipermail/hdf-forum_lists.hdfgroup.org/2013-September/007137.html
[2] git://git.debian.org/git/pkg-grass/hdf5.git


best regards

-- 
Antonio Valentino
>From 4707d38bd9994de69dded7e3599b4efd20b13aec Mon Sep 17 00:00:00 2001
From: Antonio Valentino 
Date: Fri, 27 Sep 2013 19:23:52 +
Subject: [PATCH] Fix long double detection

---
 src/H5detect.c | 67 --
 1 file changed, 47 insertions(+), 20 deletions(-)

diff --git a/src/H5detect.c b/src/H5detect.c
index d6f6a3b..eedf175 100644
--- a/src/H5detect.c
+++ b/src/H5detect.c
@@ -118,10 +118,12 @@ static volatile int	nd_g = 0, na_g = 0;
 
 static void print_results(int nd, detected_t *d, int na, malign_t *m);
 static void iprint(detected_t *);
-static int byte_cmp(int, const void *, const void *);
-static int bit_cmp(int, int *, volatile void *, volatile void *);
+static int byte_cmp(int, const void *, const void *, const unsigned char *);
+static int bit_cmp(int, int *, volatile void *, volatile void *,
+const unsigned char *);
 static void fix_order(int, int, int *, const char **);
-static int imp_bit(int, int *, volatile void *, volatile void *);
+static int imp_bit(int, int *, volatile void *, volatile void *,
+const unsigned char *);
 static unsigned long find_bias(int, int, int *, void *);
 static void precision (detected_t*);
 static void print_header(void);
@@ -293,6 +295,8 @@ precision (detected_t *d)
 #define DETECT_F(TYPE,VAR,INFO) {	  \
volatile TYPE _v1, _v2, _v3;		  \
unsigned char _buf1[sizeof(TYPE)], _buf3[sizeof(TYPE)];		  \
+unsigned char _pad_mask[sizeof(TYPE)];\
+unsigned char _byte_mask; \
int _i, _j, _last = (-1);		  \
char *_mesg;  \
 	  \
@@ -300,11 +304,26 @@ precision (detected_t *d)
INFO.varname = #VAR;			  \
INFO.size = sizeof(TYPE);		  \
 	  \
-   /* Completely initialize temporary variables, in case the bits used in */  \
-   /* the type take less space than the number of bits used to store the type */  \
-   memset(&_v3, 0, sizeof(TYPE)); \
-   memset(&_v2, 0, sizeof(TYPE)); \
-   memset(&_v1, 0, sizeof(TYPE)); \
+/* Initialize padding mask */ \
+HDmemset(_pad_mask, 0, sizeof(_pad_mask));\
+  \
+/* Padding bits.  Set a variable to 4.0, then flip each bit and see if\
+ * the modified variable is equal ("==") to the original.  Build a\
+ * padding bitmask to indicate which bits in the type are padding (i.e.   \
+ * have no effect on the value and should be ignored by subsequent\
+ * steps).  This is necessary because padding bits can change arbitrarily \
+ * and interfere with detection of the various properties below unless we \
+ * know to ignore them. */\
+_v1 = 4.0;\
+HDmemcpy(_buf1, (const void *)&_v1, sizeof(TYPE));\
+for(_i = 0; _i < (int)sizeof(TYPE); _i++) \
+for(_byte_mask = (unsigned char)1; _byte_mask; _byte_mask <<= 1) {\
+_buf1[_i] ^= _byte_mask;  \
+HDmemcpy((void *)&_v2, (const void *)_buf1, sizeof(TYPE));\
+if(_v1 != _v2)\
+_pad_mask[_i] |= _byte_mask;  \
+_buf1[_i] ^= _byte_mask;  \
+} /* enf for */   \
 	  \
/* Byte Order */			  \
for(_i = 0, _v1 = 0.0, _v2 = 1.0; _i < (int)sizeof(TYPE); _i++) {	  \
@@ -313,7 +332,7 @@ precision (detected_t *d)
   _v2 /= 256.0;			  \
   memcpy(_buf1, (const void *)&_v1, sizeof(TYPE));			  \
   memcpy(_buf3, (const void *)&_v3, sizeof(TYPE));			  \
-  _j = byte_cmp(sizeof(TYPE), &_buf3, &_buf1);			  \
+  _j = byte_cmp(sizeof(TYPE), _buf3, _buf1, _pad_mask);			  \
   if(_j >= 0) {			  \
   INFO.perm[_i] = _j;		  \
   _last = _i;			  \
@@ -327,19 +346,19 @@ precision (detected_t *d)
/* I

Bug#724656: Yet another followup. It appears to have something to do with hyperthreading.

[Robert Frazier]

Just for a lark, I turned off hyperthreading, turned on intel_pstate, 
then subjected the system to the high load encoding.  No burn and 
crash.  My (absolutely wild) guess is that the intel_pstate stuff isn't 
adequately accommodating the fact, when using hyperthreading, two of the 
"cores" are tightly connected, so the slaved "cores" end up running 
wild.  However, I'm not familiar enough with the code to check for myself.


Best wishes,
Bob



--
Robert L. Frazieremail: robert.fraz...@chch.ox.ac.uk
Christ Church
Oxford OX1 1DP www: http://kant1.chch.ox.ac.uk
UK


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

Bug#724790: linux-image-3.10-3-amd64: mei_me reset storm after resuming from RAM

[Vincent Blut]

Package: src:linux
Version: 3.10.11-1
Severity: important

Hi,

As you can see in my kernel log, my mei controller goes crazy after resuming 
from RAM. I know that that piece of code isn't really mature but as the 'mei'
module is automatically loaded by udev, and didn't cause any issue in prior 
kernel 
I didn't really care about it. But since I upgraded to 3.10-3, it seemed clear 
enough that I had to blacklist it. Note that I don't remember this kind of 
behavior 
in 3.10-2, but I'll test.
Also I'll give a try to Linux ⩾ 3.11.1 when it'll be available in experimental 
because there is an interesting commit in it:

mei: me: fix hardware reset flow

commit ff96066e3171acdea356b331163495957cb833d0 upstream.

Both H_IS and H_IE needs to be set to receive H_RDY
interrupt

1. Assert H_IS to clear the interrupts during hw reset
and use mei_me_reg_write instead of mei_hcsr_set as the later
strips down the H_IS

2. fix interrupt disablement embarrassing typo
  hcsr |= ~H_IE -> hcsr &= ~H_IE;
  this will remove the unwanted interrupt on power down

  3. remove useless debug print outs

  Signed-off-by: Tomas Winkler 
  Cc: Shuah Khan 
  Cc: Konstantin Khlebnikov 
  Signed-off-by: Greg Kroah-Hartman 

If it fixes my issue, I'll ping Greg to apply it to 3.10.  

Good week-end,
Vincent


-- Package-specific info:
** Version:
Linux version 3.10-3-amd64 (debian-ker...@lists.debian.org) (gcc version 4.7.3 
(Debian 4.7.3-7) ) #1 SMP Debian 3.10.11-1 (2013-09-10)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.10-3-amd64 
root=UUID=05885802-d6d1-4a25-b7ef-8c3e00c144b0 ro quiet pcie_aspm=force 
elevator=noop i915.i915_enable_rc6=3 i915.semaphores=1

** Tainted: C (1024)
 * Module from drivers/staging has been loaded.

** Kernel log:
[ 6586.705622] mei_me :00:16.0: reset: unexpected enumeration response hbm.
[ 6586.705626] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.705640] mei_me :00:16.0: reset: wrong host start response
[ 6586.705643] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.705674] mei_me :00:16.0: reset: unexpected enumeration response hbm.
[ 6586.705677] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.705691] mei_me :00:16.0: reset: wrong host start response
[ 6586.705695] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.705725] mei_me :00:16.0: reset: unexpected enumeration response hbm.
[ 6586.705728] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.705742] mei_me :00:16.0: reset: wrong host start response
[ 6586.705746] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.705775] mei_me :00:16.0: reset: unexpected enumeration response hbm.
[ 6586.705779] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.705793] mei_me :00:16.0: reset: wrong host start response
[ 6586.705797] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.705827] mei_me :00:16.0: reset: unexpected enumeration response hbm.
[ 6586.705830] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.705844] mei_me :00:16.0: reset: wrong host start response
[ 6586.705847] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.705878] mei_me :00:16.0: reset: unexpected enumeration response hbm.
[ 6586.705882] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.705896] mei_me :00:16.0: reset: wrong host start response
[ 6586.705899] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.705929] mei_me :00:16.0: reset: unexpected enumeration response hbm.
[ 6586.705932] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.705946] mei_me :00:16.0: reset: wrong host start response
[ 6586.705950] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.705979] mei_me :00:16.0: reset: unexpected enumeration response hbm.
[ 6586.705983] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.705996] mei_me :00:16.0: reset: wrong host start response
[ 6586.706000] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.706012] mei_me :00:16.0: we can't read the message slots =0001.
[ 6586.706027] mei_me :00:16.0: reset: unexpected enumeration response hbm.
[ 6586.706031] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.706045] mei_me :00:16.0: reset: wrong host start response
[ 6586.706048] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.706083] mei_me :00:16.0: reset: unexpected enumeration response hbm.
[ 6586.706087] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.706101] mei_me :00:16.0: reset: wrong host start response
[ 6586.706104] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.706134] mei_me :00:16.0: reset: unexpected enumeration response hbm.
[ 6586.706138] mei_me :00:16.0: unexpected reset: dev_state = RESETTING
[ 6586.7061

Bug#724789: pu: package glusterfs/3.2.7-3+deb7u1

[Patrick Matthäi]

Sorry I forget to attach the diff :)

Am 27.09.2013 21:32, schrieb Patrick Matthäi:

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

Hello,

glusterfs does not work with the current Wheezy Linux (>= 3.2.46-1+deb7u1)
anymore, if you use ext4 as storage backend. Salvatore backported the upstream
patch. I would be happy if I could upload this version to stable to make
glusterfs useable again. :)

Details and upstream ACK:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722694


--
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/
diff -Naur '--exclude=.svn' tags/3.2.7-3/debian/changelog 
branches/wheezy/debian/changelog
--- tags/3.2.7-3/debian/changelog   2012-11-12 20:37:46.218864002 +0100
+++ branches/wheezy/debian/changelog2013-09-27 21:19:25.155488829 +0200
@@ -1,3 +1,11 @@
+glusterfs (3.2.7-3+deb7u1) stable; urgency=low
+
+  * Add patch 04-ext4-safe to fix broken glusterfs with Linux
+>= 3.2.46-1+deb7u1 if you use ext4 as storage backend.
+Closes: #722694
+
+ -- Patrick Matthäi   Fri, 27 Sep 2013 21:13:42 +0200
+
 glusterfs (3.2.7-3) unstable; urgency=low
 
   * Remove duplicated and faulty call of the glusterd daemon from the init
diff -Naur '--exclude=.svn' tags/3.2.7-3/debian/patches/04-ext4-safe.diff 
branches/wheezy/debian/patches/04-ext4-safe.diff
--- tags/3.2.7-3/debian/patches/04-ext4-safe.diff   1970-01-01 
01:00:00.0 +0100
+++ branches/wheezy/debian/patches/04-ext4-safe.diff2013-09-27 
21:17:40.119491904 +0200
@@ -0,0 +1,137 @@
+# Upstream patch to fix broken glusterfs if you use ext4 as storage backend.
+# This was introduced with the Linux 3.2.46-1+deb7u1 version.
+# This patch has been backported by Salvatore Bonaccorso, thanks!
+# Closes: #722694
+
+diff -Naur glusterfs-3.2.7.orig/xlators/cluster/dht/src/dht-helper.c 
glusterfs-3.2.7/xlators/cluster/dht/src/dht-helper.c
+--- glusterfs-3.2.7.orig/xlators/cluster/dht/src/dht-helper.c  2012-06-10 
19:44:16.0 +0200
 glusterfs-3.2.7/xlators/cluster/dht/src/dht-helper.c   2013-09-27 
21:05:25.895511703 +0200
+@@ -49,6 +49,43 @@
+ }
+ 
+ 
++static uint64_t
++dht_bits_for (uint64_t num)
++{
++  uint64_t bits = 0, ctrl = 1;
++
++  while (ctrl < num) {
++  ctrl *= 2;
++  bits ++;
++  }
++
++  return bits;
++}
++
++/*
++ * A slightly "updated" version of the algorithm described in the commit log
++ * is used here.
++ *
++ * The only enhancement is that:
++ *
++ * - The number of bits used by the backend filesystem for HUGE d_off which
++ *   is described as 63, and
++ * - The number of bits used by the d_off presented by the transformation
++ *   upwards which is described as 64, are both made "configurable."
++ */
++
++
++#define BACKEND_D_OFF_BITS 63
++#define PRESENT_D_OFF_BITS 63
++
++#define ONE 1ULL
++#define MASK (~0ULL)
++#define PRESENT_MASK (MASK >> (64 - PRESENT_D_OFF_BITS))
++#define BACKEND_MASK (MASK >> (64 - BACKEND_D_OFF_BITS))
++
++#define TOP_BIT (ONE << (PRESENT_D_OFF_BITS - 1))
++#define SHIFT_BITS (max (0, (BACKEND_D_OFF_BITS - PRESENT_D_OFF_BITS + 1)))
++
+ int
+ dht_itransform (xlator_t *this, xlator_t *subvol, uint64_t x, uint64_t *y_p)
+ {
+@@ -56,6 +93,9 @@
+ int cnt = 0;
+ int max = 0;
+ uint64_ty = 0;
++uint64_thi_mask = 0;
++uint64_toff_mask = 0;
++int max_bits = 0;
+ 
+ if (x == ((uint64_t) -1)) {
+ y = (uint64_t) -1;
+@@ -69,7 +109,23 @@
+ max = conf->subvolume_cnt;
+ cnt = dht_subvol_cnt (this, subvol);
+ 
+-y = ((x * max) + cnt);
++  if (max == 1) {
++  y = x;
++  goto out;
++  }
++
++max_bits = dht_bits_for (max);
++
++hi_mask = ~(PRESENT_MASK >> (max_bits + 1));
++
++if (x & hi_mask) {
++/* HUGE d_off */
++off_mask = MASK << max_bits;
++y = TOP_BIT | ((x >> SHIFT_BITS) & off_mask) | cnt;
++} else {
++/* small d_off */
++y = ((x * max) + cnt);
++}
+ 
+ out:
+ if (y_p)
+@@ -147,16 +203,38 @@
+ int max = 0;
+ uint64_tx = 0;
+ xlator_t   *subvol = 0;
++int max_bits = 0;
++uint64_toff_mask = 0;
++uint64_thost_mask = 0;
+ 
+ if (!this->private)
+-goto out;
++return -1;
+ 
+ conf = this->private;
+ max = conf->subvolume_cnt;
+ 
+-cnt = y % max;
+-x   = y / max;
++  if (max == 1) {
++  x = y;
++  cnt = 0;
++  goto out;
++  }
++
++if (y & TOP_BIT) {
++/* HUGE d_off */
++max_bits = dht_bits_for (max);
++off_mask = (MASK << max_bits);
++   

Bug#724789: pu: package glusterfs/3.2.7-3+deb7u1

[Patrick Matthäi]

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

Hello,

glusterfs does not work with the current Wheezy Linux (>= 3.2.46-1+deb7u1)
anymore, if you use ext4 as storage backend. Salvatore backported the upstream
patch. I would be happy if I could upload this version to stable to make
glusterfs useable again. :)

Details and upstream ACK:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722694

-- System Information:
Debian Release: 7.1
  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


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

Bug#720796: gstreamer0.10-ffmpeg: FTBFS with libav9: gstffmpeg.h:63:1: error: unknown type name 'URLProtocol'

[Sebastian Dröge]

On So, 2013-09-22 at 14:52 +0200, Sebastian Ramacher wrote:
> On 2013-09-13 09:16:35, Sebastian Dröge wrote:
> > On Fr, 2013-09-13 at 02:56 +0200, Sebastian Ramacher wrote:
> > > On 2013-09-12 14:00:43, Sebastian Dröge wrote:
> > > > On Do, 2013-09-12 at 12:57 +0200, Sebastian Ramacher wrote:
> > > > > On 2013-09-09 20:53:03, Luk Claes wrote:
> > > > > > >> Can/should this be removed in favour of gst-libav1.0?
> > > > > > >
> > > > > > > Yes it should probably be just removed. I plan to get rid of all 
> > > > > > > of
> > > > > > > gstreamer 0.10 in the next months, so let's just let this one go 
> > > > > > > now
> > > > > > > already :)
> > > > > > 
> > > > > > testing removal hint added.
> > > > > 
> > > > > That didn't work - there are reverse dependencies. Seems like
> > > > > gstreamer0.10-ffmpeg needs to be fixed.
> > > > 
> > > > The rdepends should be ported to GStreamer 1.0 instead probably. Also
> > > > most of these rdepends should at most Recommend the package.
> > > 
> > > Sure, ideally they would be ported to use GStreamer 1.0 instead. But I'd
> > > rather not add yet another transition on top of the libav transition.
> > > 
> > > I've started to backport the necessary changes for libav 9 from
> > > gst-libav1.0. I'm at a state where it compiles and appreciate another
> > > pair of eyes looking over it as the patch got really large.
> > 
> > From skipping over it this patch looks good, you only remove support for
> > paletted video formats and also some more changes are necessary to
> > convert from the planar audio formats that are output by some decoders
> > now to an interleaved audio format.
> 
> Here is a new version of the patch. Support for paletted video formats
> should be back (as far as I can tell from gst-libav1.0's code
> *_set_palette was removed altogether and is no longer needed). Support
> for planar audio formats gives me headaches as too much has been
> changed. I've started to backport it for the encoder but failed to do
> so for the decoder.

Yeah, there's a reason why we did a new version with improved API after
many years of experience with annoyances and unneeded complications like
that ;)

Generally looks good the patch

> In gst-libav1.0 gst_ffmpegauddec_get_buffer gets a GstAudioInfo pointer
> from a GstAudioDecoder* instance. Where do I get that from in
> gstreamer-ffmpeg0.10? Or is there some other way to get the same
> information? The same questions also bugs me for the encoder.

In 0.10 you could create (with later versions of 0.10) a GstAudioInfo
from the GstCaps. See gst/audio/audio.h for the relevant functions.

> Since GstFFmpegDec is not a GstAudioDecoder, what's the proper
> replacement for gst_audio_decoder_allocate_output_buffer? (as used in
> gst-libav1.0's gst_ffmpegauddec_get_buffer)

Just gst_buffer_new_and_alloc()


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

Bug#724788: Please delete this bug #724788, is duplicate of #724787

[Ingo]

Delete me


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

Bug#724788: linux: CPU scaling: higher frequencies and sometimes even "performance" after s2ram

[Ingo]

Package: src:linux
Version: 3.10.11-1
Severity: important
File: linux

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these lines ***


-- Package-specific info:
** Version:
Linux version 3.10-3-amd64 (debian-ker...@lists.debian.org) (gcc version
4.7.3 (Debian 4.7.3-7) ) #1 SMP Debian 3.10.11-1 (2013-09-10)

** Command line:
BOOT_IMAGE=/vmlinuz root=/dev/sda3 ro quiet

** Not tainted

** Kernel log:
[ 1155.524559] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE
CONFIGURATION OVERLAY) filtered out
[ 1155.527013] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES)
succeeded
[ 1155.527016] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE
LOCK) filtered out
[ 1155.527019] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE
CONFIGURATION OVERLAY) filtered out
[ 1155.528204] ata2.00: configured for UDMA/133
[ 1155.543358] sd 1:0:0:0: [sdb] Starting disk
[ 1155.565351] PM: resume of devices complete after 9641.930 msecs
[ 1155.565488] PM: Finishing wakeup.
[ 1155.565489] Restarting tasks ... done.
[ 1155.566134] video LNXVIDEO:00: Restoring backlight state
[ 1416.437695] PM: Syncing filesystems ... done.
[ 1416.438090] PM: Preparing system for mem sleep
[ 1416.438187] Freezing user space processes ... (elapsed 0.01 seconds)
done.
[ 1416.452452] Freezing remaining freezable tasks ... (elapsed 0.01
seconds) done.
[ 1416.468442] PM: Entering mem sleep
[ 1416.468496] Suspending console(s) (use no_console_suspend to debug)
[ 1416.469921] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[ 1416.469977] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 1416.470044] sd 0:0:0:0: [sda] Stopping disk
[ 1416.470070] sd 1:0:0:0: [sdb] Stopping disk
[ 1416.470080] serial 00:08: disabled
[ 1416.470083] serial 00:08: System wakeup disabled by ACPI
[ 1416.470201] mei_me :00:16.0: suspend
[ 1417.148132] PM: suspend of devices complete after 679.950 msecs
[ 1417.148223] PM: late suspend of devices complete after 0.089 msecs
[ 1417.148393] ehci-pci :00:1d.0: System wakeup enabled by ACPI
[ 1417.164064] ehci-pci :00:1a.0: System wakeup enabled by ACPI
[ 1417.180030] e1000e :00:19.0: System wakeup enabled by ACPI
[ 1417.212011] xhci_hcd :00:14.0: System wakeup enabled by ACPI
[ 1417.228007] PM: noirq suspend of devices complete after 79.829 msecs
[ 1417.228245] ACPI: Preparing to enter system sleep state S3
[ 1417.228468] PM: Saving platform NVS memory
[ 1417.229022] Disabling non-boot CPUs ...
[ 1417.331890] smpboot: CPU 1 is now offline
[ 1417.435829] smpboot: CPU 2 is now offline
[ 1417.437219] smpboot: CPU 3 is now offline
[ 1417.438332] ACPI: Low-level resume complete
[ 1417.438372] PM: Restoring platform NVS memory
[ 1417.438831] Enabling non-boot CPUs ...
[ 1417.438902] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 1417.452417] Intel pstate controlling: cpu 1
[ 1417.452470] CPU1 is up
[ 1417.452519] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ 1417.466046] Intel pstate controlling: cpu 2
[ 1417.466082] CPU2 is up
[ 1417.466138] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ 1417.479665] Intel pstate controlling: cpu 3
[ 1417.479701] CPU3 is up
[ 1417.483308] ACPI: Waking up from system sleep state S3
[ 1417.513152] xhci_hcd :00:14.0: System wakeup disabled by ACPI
[ 1417.561123] ehci-pci :00:1a.0: System wakeup disabled by ACPI
[ 1417.593098] ehci-pci :00:1d.0: System wakeup disabled by ACPI
[ 1417.609135] PM: noirq resume of devices complete after 125.501 msecs
[ 1417.609221] PM: early resume of devices complete after 0.068 msecs
[ 1417.609250] i915 :00:02.0: setting latency timer to 64
[ 1417.609252] xhci_hcd :00:14.0: setting latency timer to 64
[ 1417.609280] mei_me :00:16.0: irq 41 for MSI/MSI-X
[ 1417.609300] e1000e :00:19.0: System wakeup disabled by ACPI
[ 1417.609307] e1000e :00:19.0: setting latency timer to 64
[ 1417.609321] e1000e :00:19.0: irq 43 for MSI/MSI-X
[ 1417.609389] ehci-pci :00:1a.0: setting latency timer to 64
[ 1417.609390] ahci :00:1f.2: setting latency timer to 64
[ 1417.609462] snd_hda_intel :00:1b.0: irq 45 for MSI/MSI-X
[ 1417.609560] ehci-pci :00:1d.0: setting latency timer to 64
[ 1417.610430] serial 00:08: activated
[ 1417.936837] ata6: SATA link down (SStatus 0 SControl 300)
[ 1417.936855] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1417.938286] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES)
succeeded
[ 1417.938287] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE
LOCK) filtered out
[ 1417.938289] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE
CONFIGURATION OVERLAY) filtered out
[ 1417.952828] ata5: SATA link down (SStatus 0 SControl 300)
[ 1417.958278] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES)
succeeded
[ 1417.958279] a

Bug#724787: linux: CPU scaling: higher frequencies and sometimes even "performance" after s2ram

[Ingo]

Package: src:linux
Version: 3.10.11-1
Severity: important
File: linux

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these lines ***


-- Package-specific info:
** Version:
Linux version 3.10-3-amd64 (debian-ker...@lists.debian.org) (gcc version 4.7.3 
(Debian 4.7.3-7) ) #1 SMP Debian 3.10.11-1 (2013-09-10)

** Command line:
BOOT_IMAGE=/vmlinuz root=/dev/sda3 ro quiet

** Not tainted

** Kernel log:
[ 1155.524559] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
[ 1155.527013] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 1155.527016] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
[ 1155.527019] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
[ 1155.528204] ata2.00: configured for UDMA/133
[ 1155.543358] sd 1:0:0:0: [sdb] Starting disk
[ 1155.565351] PM: resume of devices complete after 9641.930 msecs
[ 1155.565488] PM: Finishing wakeup.
[ 1155.565489] Restarting tasks ... done.
[ 1155.566134] video LNXVIDEO:00: Restoring backlight state
[ 1416.437695] PM: Syncing filesystems ... done.
[ 1416.438090] PM: Preparing system for mem sleep
[ 1416.438187] Freezing user space processes ... (elapsed 0.01 seconds) done.
[ 1416.452452] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) 
done.
[ 1416.468442] PM: Entering mem sleep
[ 1416.468496] Suspending console(s) (use no_console_suspend to debug)
[ 1416.469921] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[ 1416.469977] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 1416.470044] sd 0:0:0:0: [sda] Stopping disk
[ 1416.470070] sd 1:0:0:0: [sdb] Stopping disk
[ 1416.470080] serial 00:08: disabled
[ 1416.470083] serial 00:08: System wakeup disabled by ACPI
[ 1416.470201] mei_me :00:16.0: suspend
[ 1417.148132] PM: suspend of devices complete after 679.950 msecs
[ 1417.148223] PM: late suspend of devices complete after 0.089 msecs
[ 1417.148393] ehci-pci :00:1d.0: System wakeup enabled by ACPI
[ 1417.164064] ehci-pci :00:1a.0: System wakeup enabled by ACPI
[ 1417.180030] e1000e :00:19.0: System wakeup enabled by ACPI
[ 1417.212011] xhci_hcd :00:14.0: System wakeup enabled by ACPI
[ 1417.228007] PM: noirq suspend of devices complete after 79.829 msecs
[ 1417.228245] ACPI: Preparing to enter system sleep state S3
[ 1417.228468] PM: Saving platform NVS memory
[ 1417.229022] Disabling non-boot CPUs ...
[ 1417.331890] smpboot: CPU 1 is now offline
[ 1417.435829] smpboot: CPU 2 is now offline
[ 1417.437219] smpboot: CPU 3 is now offline
[ 1417.438332] ACPI: Low-level resume complete
[ 1417.438372] PM: Restoring platform NVS memory
[ 1417.438831] Enabling non-boot CPUs ...
[ 1417.438902] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 1417.452417] Intel pstate controlling: cpu 1
[ 1417.452470] CPU1 is up
[ 1417.452519] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ 1417.466046] Intel pstate controlling: cpu 2
[ 1417.466082] CPU2 is up
[ 1417.466138] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ 1417.479665] Intel pstate controlling: cpu 3
[ 1417.479701] CPU3 is up
[ 1417.483308] ACPI: Waking up from system sleep state S3
[ 1417.513152] xhci_hcd :00:14.0: System wakeup disabled by ACPI
[ 1417.561123] ehci-pci :00:1a.0: System wakeup disabled by ACPI
[ 1417.593098] ehci-pci :00:1d.0: System wakeup disabled by ACPI
[ 1417.609135] PM: noirq resume of devices complete after 125.501 msecs
[ 1417.609221] PM: early resume of devices complete after 0.068 msecs
[ 1417.609250] i915 :00:02.0: setting latency timer to 64
[ 1417.609252] xhci_hcd :00:14.0: setting latency timer to 64
[ 1417.609280] mei_me :00:16.0: irq 41 for MSI/MSI-X
[ 1417.609300] e1000e :00:19.0: System wakeup disabled by ACPI
[ 1417.609307] e1000e :00:19.0: setting latency timer to 64
[ 1417.609321] e1000e :00:19.0: irq 43 for MSI/MSI-X
[ 1417.609389] ehci-pci :00:1a.0: setting latency timer to 64
[ 1417.609390] ahci :00:1f.2: setting latency timer to 64
[ 1417.609462] snd_hda_intel :00:1b.0: irq 45 for MSI/MSI-X
[ 1417.609560] ehci-pci :00:1d.0: setting latency timer to 64
[ 1417.610430] serial 00:08: activated
[ 1417.936837] ata6: SATA link down (SStatus 0 SControl 300)
[ 1417.936855] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1417.938286] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 1417.938287] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
[ 1417.938289] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
[ 1417.952828] ata5: SATA link down (SStatus 0 SControl 300)
[ 1417.958278] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 1417.95

Bug#724786: RM: autoconf-gl-macros -- ROM; obsoleted by autoconf-archive

[Paul Wise]

Package: ftp.debian.org
Severity: normal

Please remove the autoconf-gl-macros source package from unstable. It
has been replaced by a transitional package to autoconf-archive which is
built from the autoconf-archive source package.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


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

Bug#724785: heimdall-flash-frontend: Package doesn't depend on heimdall-flash

[Riccardo Boninsegna]

Package: heimdall-flash-frontend
Version: 1.4~rc1+dfsg-1
Severity: important

I initially installed heimdall-flash-frontend only and ran the executable from
a terminal. The software refused to do anything unless an executable found in
heimdall-flash was found.
Therefore, according to the definition of package relationships, a

Depends: heimdall-flash

line should be added to the control file.



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

Kernel: Linux 3.10-3-rt-amd64 (SMP w/4 CPU cores; PREEMPT)
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 heimdall-flash-frontend depends on:
ii  libc6   2.17-93
ii  libgcc1 1:4.8.1-10
ii  libqt4-xml  4:4.8.5+git121-g2a9ea11+dfsg-1
ii  libqtcore4  4:4.8.5+git121-g2a9ea11+dfsg-1
ii  libqtgui4   4:4.8.5+git121-g2a9ea11+dfsg-1
ii  libstdc++6  4.8.1-10
ii  zlib1g  1:1.2.8.dfsg-1

heimdall-flash-frontend recommends no packages.

heimdall-flash-frontend 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#724784: description typo

[Joey Hess]

Package: empire
Severity: minor

 they keyboard.
^

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#724782: packaging-tutorial: [INTL:pt] Updated Portuguese translation

[Américo Monteiro]

Package: packaging-tutorial
Version: 0.10
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for packaging-tutorial.
Translator: Américo Monteiro 
Feel free to use it.

For translation updates please contact 'Last Translator' or the
Portuguese Translation Team .

-- 
Melhores cumprimentos/Best regards,

Traduz! - Portuguese Translation Team


packaging-tutorial_0.10_pt.po.gz
Description: GNU Zip compressed data

Bug#724783: iproute: ip rule delete local table if table number doesn't exist

[Nicolas HICHER]

Package: iproute
Version: 1:3.11.0-1
Severity: important
Tags: upstream

Dear Maintainer,

On debian wheezy, jessie, sid, if you try to delete an inexistant
table with ip rule, the local table will be deleted. The table number must
be greater than 256: 

root@wheezy:~# ip rule
0:  from all lookup local 
32766:  from all lookup main 
32767:  from all lookup default 
root@wheezy:~# ip rule delete table 10
RTNETLINK answers: No such file or directory
root@wheezy:~# ip rule delete table 256
root@wheezy:~# ip rule 
32766:  from all lookup main 
32767:  from all lookup default 

On debian squeeze, the problem does not exist:

root@squeeze:~# ip rule delete table 256
RTNETLINK answers: Operation not permitted

There is the same problem with iproute on Arch linux (iproute-3.10).

Thanks.

Nico

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages iproute depends on:
ii  iproute2  3.11.0-1

iproute recommends no packages.

iproute 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#724781: dhelp: [INTL:pt] Updated Portuguese translation

[Américo Monteiro]

Package: dhelp
Version: 0.6.22
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for dhelp.
Translator: Américo Monteiro 
Feel free to use it.

For translation updates please contact 'Last Translator' or the
Portuguese Translation Team .

-- 
Melhores cumprimentos/Best regards,

Traduz! - Portuguese Translation Team


dhelp_0.6.22_pt.po.gz
Description: GNU Zip compressed data

Bug#724763: sudo: Doesn't support sssd auth backend. Described already in bug 719574

[Bdale Garbee]

Dominik  writes:

> But sudo is compiled without the "--with-sssd" configure option see
  ...
> The result is that sssd support still doesn't work.

Right.  If you actually read to the end of #719987, you'd see that Jakub
already pointed this out to me.  The fix is included in the 1.8.8~rc1-1
build that's in experimental if you want to try that version
immediately.  

I thought I'd uploaded 1.8.7-4 to unstable, too, but apparently I
didn't.  Since I'm not sure when 1.8.8 will actually release, I'll go do
that now. 

Bdale


pgp6dGFJ2YRH4.pgp
Description: PGP signature

Bug#544641: problem nailed, but how to fix?

[Rodolfo García Peñas]

On Thu, 26 Sep 2013, Giacomo Mulas escribió:

> I think I found why uswsusp is unable to resume when the swap partition is
> on a lvm device, but I suspect that the problem lies with lvm2
> and will have to be fixed either there or in initramfs-tools.
> 
> Essentially, when in the boot sequence scripts/local-top/lvm2 gets executed
> in the ramdisk, it does not activate all available lvm devices, but rather
> tries to individually activate the root device and the resume device,
> calling the function activate_vg which is defined in the same script.
> Now, what happens is that when activate_vg is called with a
> /dev/mapper/something device as argument it works correctly; instead, when
> it is given an argument "UUID=whateversensibleuuid" it fails to activate the
> matching lvm partition, even if it exists in the system.
> 
> Now, since ROOT is defined by the argument provided in the kernel boot
> command line, and since the grub scripts set it up to
> /dev/mapper/rootvg-rootlvm, this works ok to activate the root partition.
> 
> Instead, the RESUME variable is set up in the conf/conf.d/resume
> configuration file, which is magically set up by mkinitramfs to always be in
> the form UUID=someuuid EVEN IF this was explicitly set in
> /etc/initramfs-tools/conf/conf.d/resume as
> RESUME=/dev/mapper/somecorrectlvmdevice
> This happens in /usr/share/initramfs-tools/hooks/resume, which calls blkid
> to translate _any_ candidate resume device found to UUID form. This is then
> passed to activate_vg which fails to activate it.
> 
> 
> Possible solutions I see:
> 
> 1) The Right Thing: fix the function activate_vg in
> /usr/share/initramfs-tools/scripts/local-top/lvm2 so that it activates an
> lvm partition which is given in the form UUID=somecorrectlvmuuid
> 
> 2) not too bad kludge: add a special case in
> /usr/share/initramfs-tools/hooks/resume so that if a resume device is given
> as /dev/mapper/something it is left alone and not forcibly translated to
> UUID=correspondinguuid; this would make previously working configurations
> (e.g. in which one had specified a correct RESUME line in
> /etc/initramfs-tools/conf/conf.d/resume) happy again
> 
> 3) atomic bomb approach: instead of going to great lengths to determine and
> activate in the initramdisk only the root and resume lvm devices, just put
> an unconditional lvm vgchange -aly --ignorelockingfailure
> line in /usr/share/initramfs-tools/scripts/local-top/lvm2, which will always
> activate all lvm devices and be done with it.
> 
> I suggest that the uswsusp maintainer should relay this email (and/or his
> own better analysis) to the maintainers of the lvm2 and initramfs-tools
> packages, so that a common agreement can be found for a solution accepted by
> all, which can hopefully be expected to work for some time and not be broken
> time and again by some apparently unrelated change.
> 
> 
> Bye
> Giacomo

Hi Giacomo,

thanks a lot for your report. I will forward it to the maintainers, but can you 
try first this new uswsusp version? 

http://www.kix.es/Philipp/

This version only change the variable name in the uswsusp scripts from RES_DEV 
to RESUME and adds the offset argument to the resume file. This change could 
help in other bug and Ben (initramfs-tools maintainer) suggest me the change.

Thanks!
kix


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

Bug#724780: xulrunner-dev uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: xulrunner-dev
Version: 24.0-2
User: ametz...@debian.org
Usertags: find_perm_plus

Hello,

the xulrunner-dev package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/BUGS$ grep -lr -- '-perm +'
iceweasel-24.0/debian/dh/dh_xulrunner.in
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


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

Bug#724779: uucp uses install-info but does not depend on it.

[cloos]

Package: uucp
Version: 1.07-20
Severity: normal

apt-get install uucp failed in the postinst phase because install-info
was not found.

Manually installing install-info enabled uucp's postinst script to succeed.

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

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

Versions of packages uucp depends on:
ii  cron   3.0pl1-124
ii  cu 1.07-20
ii  heirloom-mailx [mailx] 12.5-2
ii  libc6  2.17-93
ii  libpam-runtime 1.1.3-9
ii  libpam0g   1.1.3-9
ii  logrotate  3.8.6-1
ii  netbase5.1
ii  xinetd [inet-superserver]  1:2.3.15-1

Versions of packages uucp recommends:
ii  postfix  2.11-20130825-1

uucp suggests no packages.

-- Configuration Files:
/etc/uucp/call [Errno 13] Permission denied: u'/etc/uucp/call'
/etc/uucp/passwd [Errno 13] Permission denied: u'/etc/uucp/passwd'

-- 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#724275: uswsusp: Stops at boot with "resume: libgcrypt version 1.5.3"

[Rodolfo García Peñas]

On Thu, 26 Sep 2013, Philipp Huebner escribió:

> Hi,
> 
> neither option made any difference.
> 
> I even tried it with /dev/dm-1 in both places, still no luck.

Hi Philipp,

I have an issue with the image restore, and perhaps it can affect this problem 
too. I left a new package version (for your testing only, not for upload, is 
not signed) at http://www.kix.es/Philipp/

can you try it?

Thanks a lot,

Best Regards,
kix


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

Bug#724776: lazarus uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: lazarus
Version: 1.0.10+dfsg-1
User: ametz...@debian.org
Usertags: find_perm_plus

Hello,

the lazarus package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/BUGS$ grep -lr -- '-perm +'
lazarus-1.0.10+dfsg/tools/install/create_clean_fpcsrc_directory.sh
lazarus-1.0.10+dfsg/tools/install/create_clean_lazarus_directory.sh
lazarus-1.0.10+dfsg/tools/install/macosx/create_lazarus_dmg.sh
-

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


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

Bug#683042: Blender: debian/copyright: No information of embedded external libraries

[Ross Gammon]

Hi,

I am looking to join the Multimedia team soon. This bug looked like a
nice one to start with for a new chum.

Give me a few days, and then hopefully I can attach a patch with a fresh
copyright file to the bug for review.

Regards,

Ross


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

Bug#724778: nova uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: nova
Version: 2013.1.3-2
User: ametz...@debian.org
Usertags: find_perm_plus

Hello,

the nova package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/BUGS$ grep -lr -- '-perm +'
nova-2013.1.3/tools/run_pep8.sh
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


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

Bug#724777: ncbi-tools6 uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: ncbi-tools6
Version: 6.1.20120620-6
User: ametz...@debian.org
Usertags: find_perm_plus

Hello,

the ncbi-tools6 package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/BUGS$ grep -lr -- '-perm +'
ncbi-tools6-6.1.20120620/debian/rules
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


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

Bug#724775: kernel-package uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: kernel-package
Version: 12.036+nmu3
User: ametz...@debian.org
Usertags: find_perm_plus

Hello,

the kernel-package package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/BUGS$ grep -lr -- '-perm +'
kernel-package-12.036+nmu3/kernel/ruleset/targets/doc.mk
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


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

Bug#724774: ace uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: ace
Version: 6.0.3+dfsg-0.1
User: ametz...@debian.org
Usertags: find_perm_plus

Hello,

the ace package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/BUGS$ grep -lr -- '-perm +'
ace-6.0.3+dfsg/bin/ace-install
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


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

Bug#724773: zeroc-ice uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: zeroc-ice
Version: 3.5.0-3
User: ametz...@debian.org
Usertags: find_perm_plus

Hello,

the zeroc-ice package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/BUGS$ grep -lr -- '-perm +'
zeroc-ice-3.5.0/perf/makedist.py
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


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

Bug#724772: sendmail uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: sendmail
Version: 8.14.4-4.1
User: ametz...@debian.org
Usertags: find_perm_plus

Hello,

the sendmail package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/BUGS$ grep -lr -- '-perm +'
sendmail-8.14.4/debian/local/update_sys.in
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


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

Bug#724727: gnubg: fails to detect SSE at runtime

[Russ Allbery]

Now that I've had another look at this, I realized a couple other things.
First, your architecture is i386, not amd64 (I'd gotten confused by the
fact that you have an AMD processor, but of course that's not related).
That means that this problem actually should be fixed in 1.02.000-2, where
I disabled all the SIMD types for i386 builds.

Second...

> However, this machine does have SSE:

>   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

...yes, but what gnubg means by SSE in this particular case is actually
SSE2, which you don't have.

I think 1.02.000-2 will fix gnubg on this system.

This would have indeed been broken since 1.01.003, since I had gotten
confused by how the runtime testing was working.  I had thought that gnubg
was testing at runtime and falling back on non-SIMD code, but it was just
testing at runtime and then refusing to run.  Somewhat less useful for
generic Debian builds than I was hoping.  :)

-- 
Russ Allbery (r...@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#724770: Uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: csound
Version: 1:6.00.1~dfsg-2
User: ametz...@debian.org
Usertags: find_perm_plus

Hello,

the csound package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/BUGS$ grep -lr -- '-perm +'
csound-6.00.1~dfsg/installer/misc/mksrcpkg.sh
csound-6.00.1~dfsg/installer/misc/makedeb.sh
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


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

Bug#724771: freealut uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: freealut
Version: 1.1.0-3
User: ametz...@debian.org
Usertags: find_perm_plus

Hello,

the freealut package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/BUGS$ grep -lr -- '-perm +'
freealut-1.1.0/Makefile.in
freealut-1.1.0/Makefile.am
freealut-1.1.0/.pc/100_rebootstrap.diff/Makefile.in
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


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

Bug#724769: Uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: timidity
Version: 2.13.2-40.1
User: ametz...@debian.org
Usertags: find_perm_plus

Hello,

the timidity source package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/BUGS$ grep -lr -- '-perm +' timidity-2.13.2
timidity-2.13.2/debian/rules
timidity-2.13.2/debian/patches/debian-changes-2.13.2-36
timidity-2.13.2/autogen.sh
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


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

Bug#724768: glark: Does not work with ruby 1.9, but doesn't have according dependencies

[Axel Beckert]

Package: glark
Version: 1.8.0-1
Severity: grave
Justification: Wrong/missing dependency, does only work after changing a 
system's ruby default version
Tags: wheezy jessie sid patch

Dear Maintainer,

while glark 1.8.0-1 seems to work fine on Debian Squeeze, it no more
does so on Wheezy:

$ glark
/usr/share/glark/glark.rb:135: warning: assigned but unused variable - srclines
/usr/share/glark/glark.rb:262: warning: assigned but unused variable - e
/usr/share/glark/glark.rb:351: warning: assigned but unused variable - e
/usr/share/glark/glark.rb:460: warning: assigned but unused variable - fname
/usr/share/glark/glark.rb:640: warning: assigned but unused variable - e
/usr/share/glark/glark.rb:816: warning: assigned but unused variable - str
/usr/share/glark/options.rb:501: warning: assigned but unused variable - e
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': 
/usr/share/glark/options.rb:81: formal argument cannot be an instance variable 
(SyntaxError)
:set  => Proc.new { |@after| },
   ^
/usr/share/glark/options.rb:87: formal argument cannot be an instance variable
:set  => Proc.new { |@before| },
^
/usr/share/glark/options.rb:191: formal argument cannot be an instance variable
:set  => Proc.new { |@directory| }
   ^
/usr/share/glark/options.rb:216: formal argument cannot be an instance variable
:set  => Proc.new { |@split_as_path| }
   ^
/usr/share/glark/options.rb:221: formal argument cannot be an instance variable
:set  => Proc.new { |@directory| }
   ^
/usr/share/glark/options.rb:234: formal argument cannot be an instance variable
:set  => Proc.new { |@label| }
   ^
/usr/share/glark/options.rb:239: formal argument cannot be an instance variable
:set  => Proc.new { |@match_limit| }
 ^
/usr/share/glark/options.rb:296: formal argument cannot be an instance variable
:set  => Proc.new { |@size_limit| }
^
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/share/glark/glark.rb:20:in `'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/bin/glark:17:in `'
$

(Adding parameters or command-line options make no difference at all.)

The default ruby version since Wheezy is 1.9.3. But even with installing
the ruby1.8 package and calling "ruby1.8 /usr/bin/glark" does not help.

The only thing which helps so far is installing ruby1.8 (but glark's
dependency unconditionally pulls in ruby 1.9.x) and then letting
/usr/bin/ruby point to ruby1.8 by running "update-alternatives --config
ruby".

But that's just a short-term solution since ruby1.8 seems scheduled for
removal: http://release.debian.org/transitions/html/ruby1.8-removal.html

IMHO this bug should also be fixed in Wheezy as glark does not work on
Wheezy without changing the default ruby version and that's completely
up to the local administrator and no package must depend on that
decision.

Intermediately, this fix should also work for Jessie and Sid, but only
until Ruby 1.8 is removed.

The following patch fixes the issue:

diff -u glark-1.8.0/debian/control glark-1.8.0/debian/control
--- glark-1.8.0/debian/control
+++ glark-1.8.0/debian/control
@@ -8,7 +8,7 @@
 
 Package: glark
 Architecture: all 
-Depends: ruby (>= 1.6.7-3) 
+Depends: ruby1.8
 Description: pattern matching tool similar to grep
  glark is a program like 'grep' to search for text in files. It can
  be used from the command line or in scripts.
diff -u glark-1.8.0/debian/rules glark-1.8.0/debian/rules
--- glark-1.8.0/debian/rules
+++ glark-1.8.0/debian/rules
@@ -4,0 +5,5 @@
+
+install/glark::
+   sed -e 's/^exec ruby /exec ruby1.8 /;s/^#!ruby 
/#!ruby1.8/;s:^#!/usr/bin/ruby :#!/usr/bin/ruby1.8 :' -i \
+   $(CURDIR)/debian/glark/usr/bin/glark \
+   $(CURDIR)/debian/glark/usr/share/glark/*.rb


-- System Information:
Debian Release: 7.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages glark depends on:
ii  ruby1:1.9.3
ii  ruby1.8 [ruby]  1.8.7.358-7

glark recommends no packages.

glark 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#724767: Uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: clisp
Version: 1:2.49-8.2
User: ametz...@debian.org
Usertags: find_perm_plus

Hello,

the clisp source package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/BUGS$ grep -lr -- '-perm +' clisp-2.49
clisp-2.49/utils/fix-perms.sh
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


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

Bug#724766: Uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: mc
Version: 3:4.8.10-4
User: ametz...@debian.org
Usertags: find_perm_plus

Hello,

the mc package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/BUGS$ grep -lr -- '-perm +'
mc-4.8.10/src/filemanager/panelize.c
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


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

Bug#724765: Uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: systemd
Version: 204-5
User: ametz...@debian.org
Usertags: find_perm_plus

Hello,

the systemd source package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/BUGS$ grep -lr -- '-perm +' systemd-204/
systemd-204/debian/patches/debian-changes
systemd-204/test/TEST-03-JOBS/test.sh
systemd-204/test/TEST-01-BASIC/test.sh
systemd-204/test/TEST-02-CRYPTSETUP/test.sh
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


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

Bug#376140: find2perl doesn't support +PERM

[Andreas Metzler]

On 2006-06-30 Simon Waters  wrote:
> Package: perl
> Version: 5.8.4-8sarge4
> Severity: wishlist


> find2perl doesn't support the "-perm +PERM" option of find.

> I may try my hand at a patch.

Please note that -perm +PERM has been superceded by -perm /PERM and is
therefore not supported in latest GNU findutils.

cu Andreas


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

Bug#677475: Sun Fire X4140 with NVIDIA Corporation MCP55 Ethernetcards and bridge interface resets on boot

[Paweł Tomulik]

I have same issue. I ue xcp-xapi with openvswitch.
Had to disconnect all connected interfaces to start my machine.

I've the following lines at the top of my /etc/init.d/openvswitch as a 
workaround (seems to help):



/sbin/ifconfig eth0 up # (Debian BUG#677475)
/sbin/ifconfig eth1 up # (Debian BUG#677475)

sleep 1 # (Debian BUG#677475)


Regards!

--
Paweł Tomulik, tel. +48 22 234 7374
Instytut Techniki Lotniczej i Mechaniki Stosowanej
Politechnika Warszawska


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

Bug#724727: gnubg: fails to detect SSE at runtime

[Russ Allbery]

Matteo Cortese  writes:

> when I run gnubg, I get this error:

>   This version of GNU Backgammon is compiled with SSE support
>   but this machine does not support SSE

If you have a chance, could you try with the version in unstable just
uploaded yesterday (1.02.000-2)?  That disables AVX support and goes back
to explicitly configuring SSE.

I don't think it will fix it, though, so don't worry about it if it's a
hassle.  I think this is a bug in the runtime probe.  I can disable that
(there's a configure switch) and report it upstream.

-- 
Russ Allbery (r...@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#724764: ifupdown: interfaces(5) doesn't describe constraints on device names

[Tom Jones]

Package: ifupdown
Version: 0.7.8
Severity: normal

Dear Maintainer,

interfaces(5) should say what constraints exist on ethernet device
names.  For example, the 15 char limit.  Also, what chars are valid
in the name?


-- System Information:
Debian Release: 7.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages ifupdown depends on:
ii  dpkg 1.16.10
ii  initscripts  2.88dsf-41
ii  iproute  20120521-3+b3
ii  libc62.13-38
ii  lsb-base 4.1+Debian8+deb7u1

ifupdown recommends no packages.

Versions of packages ifupdown suggests:
ii  isc-dhcp-client [dhcp-client]  4.2.2.dfsg.1-5+deb70u6
ii  net-tools  1.60-24.2
pn  ppp
pn  rdnssd 

-- 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#724600: ibus-table-latex: Can't switch to latex input method

[frydo]

Package: ibus-table-latex
Followup-For: Bug #724600

Hi,

I updated today to 1.5.3-7.

The system changes a lot from previously.
Now Ibus is in constant use (I think that before I could switch between Ibus
and X input method) with gnome.
But before I needed to add my inputs methods (Hangul, and latex), and another
one (some kind of default one for me : my language table), and be sure to set
Ibus to default input method.

Now I can use them : α→∞ and 항욱.
(For latex you just need to type '\' before writing the latex code of the
symbol)

Thanks.



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-proposed-updates'), (500, 
'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.10-3-686-pae (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

Versions of packages ibus-table-latex depends on:
ii  ibus-table  1.5.0.is.1.5.0.20130419-2

ibus-table-latex recommends no packages.

ibus-table-latex 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#724763: sudo: Doesn't support sssd auth backend. Described already in bug 719574

[Dominik]

Package: sudo
Version: 1.8.7-3
Severity: normal

Hi,

in bugreport http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719574 the
sssd functionality for sudo is claimed to be enabled in testing version 1.8.7-3

But sudo is compiled without the "--with-sssd" configure option see

>> sudo -V | grep --color sssd

The result is that sssd support still doesn't work.


kind Regards & thanks in advance
Dominik



-- System Information:
Debian Release: 7.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages sudo depends on:
ii  libc6   2.17-92
ii  libpam-modules  1.1.3-7.1
ii  libpam0g1.1.3-7.1
ii  libselinux1 2.1.9-5

sudo recommends no packages.

sudo 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#724762: gogglesmm: rebuild against libxine2

[Darren Salt]

Package: gogglesmm
Version: 0.12.7-1
Severity: important

As I would like to drop xine-lib 1.1.x at some point (!), this package needs
be ported to xine-lib 1.2 (Build-Depend on libxine2-dev). This may require
code changes.

-- 
|  _  | Darren Salt, using Debian GNU/Linux (and Android)
| ( ) |
|  X  | ASCII Ribbon campaign against HTML e-mail
| / \ | http://www.asciiribbon.org/

If it isn't broken, break it then charge for repair.


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

Bug#724761: qtkeychain: FTBFS on kfreebsd-any and hurd-i386

[Svante Signell]

Source: qtkeychain
Version: 0.1.0-1
Severity: important
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd

Hi,

qtkeychain fails to build on GNU/kFreeBSD and GNU/Hurd due to that the file
cmake/Modules/GNUInstallDirs.cmake shipped with the package is too old.
Please remove the whole directory. Then the default version from
cmake-data will be used. The difference between the shipped file and
the one from cmake-data-2.8.11.2-1 is:

--- cmake/Modules/GNUInstallDirs.cmake  2013-01-31 02:33:08.0 +0100
+++ /usr/share/cmake-2.8/Modules/GNUInstallDirs.cmake   2013-07-04 
22:31:57.0 +0200
@@ -78,7 +78,7 @@ if(NOT DEFINED CMAKE_INSTALL_LIBDIR)
   # For Debian with multiarch, use 'lib/${CMAKE_LIBRARY_ARCHITECTURE}' if
   # CMAKE_LIBRARY_ARCHITECTURE is set (which contains e.g. "i386-linux-gnu"
   # See http://wiki.debian.org/Multiarch
-  if(CMAKE_SYSTEM_NAME MATCHES "Linux"
+  if((CMAKE_SYSTEM_NAME MATCHES "Linux|kFreeBSD" OR CMAKE_SYSTEM_NAME STREQUAL 
"GNU")
   AND NOT CMAKE_CROSSCOMPILING)
 if (EXISTS "/etc/debian_version") # is this a debian system ?
if(CMAKE_LIBRARY_ARCHITECTURE)


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

Bug#724760: lm-sensors: Hardware breakage reported Over the past few months reported at lm-sensors.org

[Claudio]

Package: lm-sensors
Version: 1:3.3.2-2
Severity: important

Dear Maintainer,

As reported on lm-sensors.org I quote:

"September 5th, 2013: Hardware breakage reported Over the past few months, we
had several reports of sensors-detect causing serious trouble on recent
hardware (most notably laptops.) We still don't know what exactly is happening,
and while it might be reversible, we don't know how, so in practice this is
equivalent to the hardware itself being broken. The symptoms are that the
display starts misbehaving ( wrong resolution or wrong gamma factor.) We have
mitigated the risk by changing the default behavior of sensors-detect to no
longer touch EDID EEPROMs and then to no longer probe graphics adapters at all
unless the user asks for it. We urge maintainers to backport changesets r6040
and r6084 to all Linux distributions which are still shipping lm-sensors 3.3.2
or older. Versions 3.3.3 and newer are not affected."

Debian stable (wheezy) is using 3.3.2, I haven't personally experienced any
issues but I think it's important enough and should be looked into.

Claudio



-- System Information:
Debian Release: 7.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages lm-sensors depends on:
ii  libc62.13-38
ii  libsensors4  1:3.3.2-2
ii  lsb-base 4.1+Debian8+deb7u1
ii  perl 5.14.2-21
ii  sed  4.2.1-10

lm-sensors recommends no packages.

Versions of packages lm-sensors suggests:
pn  fancontrol  
pn  i2c-tools   
pn  read-edid   
pn  sensord 

-- 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#724759: libplayer2: incorrect dependencies: libxine1-x | libxine2-x (hard), libxine2-vdr (suggested)

[Darren Salt]

Package: libplayer2
Version: 2.0.1-2.1
Severity: serious
Tags: patch

libplayer2 depends on libxine1-x | libxine2-x. This is incorrect.

* It will be satisfied if libxine2-x is present, despite the package using
  libxine1 and therefore needing libxine1-x.

* It will pull in libxine2 (well, libxine2-bin) anyway...

This is fixable by running dh_xine at build time (“dh --with xine $@” –
default behaviour is sufficient here) and having the package depend on
${xine-x:Depends}. (Advantage: works without change when adapting to
libxine2, covers possible future package name changes.)

Similarly, it suggests libxine2-vdr while depending on libxine1. This is
pointless unless it instead depends on libxine2 and should, therefore, be
removed for now.

-- 
|  _  | Darren Salt, using Debian GNU/Linux (and Android)
| ( ) |
|  X  | ASCII Ribbon campaign against HTML e-mail
| / \ | http://www.asciiribbon.org/

Aleph sub alpha is the alpha'th aleph.



fix-xine-deps.patch
Description: Binary data

Bug#647621: Nexuiz 2.5.2-7

[Simon McVittie]

(cc'ing the bug)

On 27/09/13 15:05, Anton Balashov wrote:
> What about versions? If there will be nexuiz-data_2.5.2-7, must
> there be rest of nexuiz packages 2.5.2-7 or 2.5.2-6 for rest of
> packages is OK?

All binary packages built from the same source package (e.g.
nexuiz-data, nexuiz-music and nexuiz-textures built from
src:nexuiz-data) must[1] have the same version. When a Debian
maintainer uploads a release, what they upload is an entire source
package.

Binary packages built from different source packages (e.g.
nexuiz-music built from src:nexuiz-data and nexuiz built from
src:nexuiz) do not need to share a version number. nexuiz and
nexuiz-data don't.

> What step should I do next for release?

If you consider src:nexuiz-data to be ready for upload, a Debian
Developer with upload rights needs to check it over, and if they
approve, do the actual upload. This means uploading > 750M of data,
which is probably why nobody is particularly enthusiastic about doing
it :-)

In principle, recompressing large binary packages is great, but in
practice, it isn't necessarily worth doing the upload just for that,
unless/until there is some other reason to do it. nexuiz-data 2.5.2-6
(> 850M) is in stable, so it will stay in the archive regardless; so
when someone uploads a recompressed version, it will take > 750M
*more* archive space. Similarly, existing Nexuiz users (if they don't
put the package on hold) will download 750M of new data, in order for
new Nexuiz users to be able to download 75M less.

I'm not convinced that's worth it, for data for a game that is no
longer developed upstream (some of its upstream developers started a
new proprietary game under the Nexuiz name, and the rest forked it and
called the actively-developed fork Xonotic). If you're interested in
the Nexuiz codebase, IMO a better thing to do would be to help David
Bate package Xonotic ().

If there is some other bug in nexuiz-data that justifies an upload
*anyway*, then my reasons not to do it no longer apply, and your
changes should be included in that upload.

Regards,
S

[1] well, that's not 100% true: the real situation is that each of
their version numbers must increase with each upload, but they can be
different. But don't do that.


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

Bug#724757: RFS: dxsamples/4.2.0-2 [ITA] -- Sample programs for the OpenDX Data Explorer

[Graham Inggs]

Package: sponsorship-requests
Severity: normal

Dear mentors

I am looking for a sponsor for my package "dxsamples":

 * Package name: dxsamples
   Version : 4.2.0-2
   Upstream Authors : IBM Research 
 * URL : http://www.opendx.org/
 * License : IBM PUBLIC LICENSE
   Section : science

It builds the following binary packages:

dxsamples - Sample programs for the OpenDX Data Explorer

My packaging attempt is available here:

http://anonscm.debian.org/gitweb/?p=collab-maint/dxsamples.git

Changes since the last upload:

* New maintainer. (Closes: #654647)
* Convert to source format 3.0 (quilt).
* Create d/watch.
* Convert d/rules to dh.
* New patch d/patches/convert-csh-scripts-to-sh:
  - convert csh scripts to sh syntax.
* Update d/control:
  - update homepage and vcs
  - bumped dephelper compatibility level to 9
  - drop recommends on tcsh, c-shell
  - bumped Standards-Version to 3.9.4 (no further changes)

Regards
Graham


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

Bug#724758: Live Migration Causes Performance Issues

[Harald Staub]

Package: qemu-kvm
Version: 1.1.2+dfsg-6

We have seen some performance degradation after live migration.

Corresponding Ubuntu bug:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1100843

It probably really is this bug because the mentioned "workaround" with 
the option ept=N for kvm-intel works.


They fixed it with a one-line patch. It looks easy to backport it to 
Debian stable.



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