Bug#699212: initscripts: checkfs.sh halts on un-configured luks filesystem (fstab set to noauto)

2013-01-28 Thread T. Doubrava
Package: initscripts
Version: 2.88dsf-13.1+squeeze1
Severity: important

---
Note: This bug report is against Testing, not Squeeze. It is being written from
a separate Squeeze installation due to other difficulties not yet resolved.
Please disregard the additional system information provided by reportbug.
---

Short version: Upgraded from squeeze to testing.  Machine stopped booting
properly.  Preliminary conclusion: checkfs.sh from initscripts package should
never halt a boot due to failure to check a filesystem configured with the
noauto option in /etc/fstab.

The particulars of this case get a bit more complicated.  Bear with me...

Goal (Fullfilled with Squeeze, broken with testing): LUKS encryption on top of
mdraid, with unattended boot into full network-enabled mode.

This server is semi-headless.  Grub is configured with its console on a serial
port (but I also occasionally use the monitor/kbd).  The disks are divided into
two md-raid sets.  The first is /.  The second is encrypted with LUKS.
initramfs and cryptdisks have been configured to not prompt for a LUKS password
at boot so that the machine can come up onto the network when booted remotely
(and without operator assistance at the keyboard or serial terminal).  The LUKS
partition is configured in /etc/fstab to mount at /var/lib/libvirt with the
noauto option.  Once booted (and typically from within an SSH session), I run
cryptdisks_start, supply a LUKS passphrase, and finally run the mount command
(mount /var/lib/libvirt).

With Debian testing, the behavior is this:

   Boot
   Grub
   A couple unimportant kernel boot messages appear
   Physical console has no new output, no capability to receive input (Locked
up?  Confusion sets in... Then, finally, realization!)
   Serial port has a Ctrl+D or login prompt to correct the failed fsck on the
LUKS partition which was never opened.




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

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages initscripts depends on:
ii  coreutils  8.5-1 GNU core utilities
ii  debianutils3.4   Miscellaneous utilities specific t
ii  libc6  2.11.3-3  Embedded GNU C Library: Shared lib
ii  lsb-base   3.2-23.2squeeze1  Linux Standard Base 3.2 init scrip
ii  mount  2.17.2-9  Tools for mounting and manipulatin
ii  sysv-rc2.88dsf-13.1+squeeze1 System-V-like runlevel change mech
ii  sysvinit-utils 2.88dsf-13.1+squeeze1 System-V-like utilities

Versions of packages initscripts recommends:
ii  e2fsprogs   1.41.12-4stable1 ext2/ext3/ext4 file system utiliti
ii  psmisc  22.11-1  utilities that use the proc file s

initscripts 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#699213: unblock: network-manager/0.9.4.0-9

2013-01-28 Thread Michael Biebl
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package network-manager

It fixes a bunch of RC bugs and long standing issues.
Dropping the /e/n/i mangling bits is now possible due to the fine work
the d-i people did for d-i 7.0 RC1.

It's important to get those fixes in to wheezy along with the
corresponding changes in network-manager-applet: #699115,
gnome-control-center: #697894 and gnome-shell: #699119

The changelog:

network-manager (0.9.4.0-9) unstable; urgency=low

  * Change the ifupdown dispatcher script and set ADDRFAM to inet or inet6
depending on whether the connection has a valid IPv4 or IPv6 address.
Using NetworkManager as ADDRFAM type did confuse most ifupdown hook
scripts and e.g. broke async NFS mounts. (Closes: #475188, #656584)
  * debian/patches/05-force-online-with-unmanaged-devices.patch: If network
interfaces are configured in /etc/network/interfaces, NM will mark those
devices as unmanaged by default. If such a network interface has been
brought up by ifup, set the global online state to CONNECTED.
(Closes: #512286)
  * No longer run the ifblacklist_migrate.sh script upon installation. This
script was used to comment out DHCP type network interface configurations
in /etc/network/interfaces as otherwise NM would mark such devices as
unmanaged. This script was buggy though and sometimes created a broken
network configuration.
Since debian-installer in wheezy (7.0) will create proper configuration
for NM if the network-manager package is part of the installation, this is
no longer necessary.
If users make a minimal system installation and install the
network-manager package afterwards, show a warning in postinst if we
find any interface configurations in /etc/network/interfaces.
(Closes: #688355, #690987, #606268)
  * Update README.Debian for the latest changes.

 -- Michael Biebl bi...@debian.org  Tue, 29 Jan 2013 04:10:11 +0100

Full debdiff is attached.

Cheers,
Michael



unblock network-manager/0.9.4.0-9

-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff --git a/debian/changelog b/debian/changelog
index cc2ead9..46d0ab2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,30 @@
+network-manager (0.9.4.0-9) unstable; urgency=low
+
+  * Change the ifupdown dispatcher script and set ADDRFAM to inet or inet6
+depending on whether the connection has a valid IPv4 or IPv6 address.
+Using NetworkManager as ADDRFAM type did confuse most ifupdown hook
+scripts and e.g. broke async NFS mounts. (Closes: #475188, #656584)
+  * debian/patches/05-force-online-with-unmanaged-devices.patch: If network
+interfaces are configured in /etc/network/interfaces, NM will mark those
+devices as unmanaged by default. If such a network interface has been
+brought up by ifup, set the global online state to CONNECTED.
+(Closes: #512286)
+  * No longer run the ifblacklist_migrate.sh script upon installation. This
+script was used to comment out DHCP type network interface configurations
+in /etc/network/interfaces as otherwise NM would mark such devices as
+unmanaged. This script was buggy though and sometimes created a broken
+network configuration.
+Since debian-installer in wheezy (7.0) will create proper configuration
+for NM if the network-manager package is part of the installation, this is
+no longer necessary.
+If users make a minimal system installation and install the
+network-manager package afterwards, show a warning in postinst if we
+find any interface configurations in /etc/network/interfaces.
+(Closes: #688355, #690987, #606268)
+  * Update README.Debian for the latest changes.
+
+ -- Michael Biebl bi...@debian.org  Tue, 29 Jan 2013 04:10:11 +0100
+
 network-manager (0.9.4.0-8) unstable; urgency=low
 
   * Move the pkla file to /etc/polkit-1 as requested by the release team.
diff --git a/debian/network-manager-dispatcher.script b/debian/network-manager-dispatcher.script
index 5869bda..ebadfd1 100644
--- a/debian/network-manager-dispatcher.script
+++ b/debian/network-manager-dispatcher.script
@@ -9,42 +9,68 @@ if [ -z $1 ]; then
 exit 1;
 fi
 
+if [ -n $IP4_NUM_ADDRESSES ]  [ $IP4_NUM_ADDRESSES -gt 0 ]; then
+   ADDRESS_FAMILIES=$ADDRESS_FAMILIES inet
+fi
+if [ -n $IP6_NUM_ADDRESSES ]  [ $IP6_NUM_ADDRESSES -gt 0 ]; then
+   ADDRESS_FAMILIES=$ADDRESS_FAMILIES inet6
+fi
+
+# If we have a VPN connection ignore the underlying IP address(es)
+if [ $2 = vpn-up ] || [ $2 = vpn-down ]; then
+   ADDRESS_FAMILIES=
+fi
+
+if [ -n $VPN_IP4_NUM_ADDRESSES ]  [ $VPN_IP4_NUM_ADDRESSES -gt 0 ]; then
+   

Bug#593988: network-manager-kde: Unable to connect to WIFI AP with a very long WPA key

2013-01-28 Thread Michael Biebl
Hi,

is this problem still reproducible on an up-to-date unstable / wheezy
system?


-- 
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#576582: network-manager: Unaligned trap error messages in syslog on alpha port

2013-01-28 Thread Michael Biebl
Hi,

is that issue still reproducible?
With alpha no longer being an official port, I'm wondering what to do
with this bug report. Unless someone is willing to debug and send me a
patch for this issue, I'm planning to close this bug, as it wouldn't
make sense to keep it open indefinitely.

Cheers,
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#598662: network-manager: should add IPv6 environment for dispatcher

2013-01-28 Thread Michael Biebl
severity 598662 normal
forwarded 598662 https://bugzilla.gnome.org/show_bug.cgi?id=689741
thanks

Hi,

I've filed an upstream bug report some time ago which basically
describes the same problem, so marking accordingly.

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#699214: xserver-xorg-video-nouveau: Fonts are not displayed

2013-01-28 Thread Julio Merino
Package: xserver-xorg-video-nouveau
Version: 1:1.0.1-4
Severity: important

Dear Maintainer,

* What led up to the situation?

I installed Debian testing powerpc64 on a PowerMac G5 with a NVIDIA
Corporation NV34 [GeForce FX 5200 Ultra] (rev a1) graphics card (as
reported by lspci).

Running the X server results in no fonts being displayed at all, with
the exception of the default fixed font in xterm.  Something as simple
as xterm -fa Monospace also shows the problem (a blank window with
a cursor but no visible text), which denotes that the issue is quite
down the dependency chain.

* What exactly did you do (or not do) that was effective (or
  ineffective)?

I uninstalled the xserver-xorg-video-nouveau package, to force the X
server to fallback to fbdev, and the issue went away.  The fonts are
now properly displayed.  But, of course, this is just a workaround and
not a solution; I'd like to use the real driver.

I also attempted to downgrade libxft and libfreetype6 to older versions
(libfreetype6_2.4.2-2.1+squeeze4_powerpc.deb and
libxft2_2.1.14-2_powerpc.deb) but this did not help.

The graphics driver seems to be at fault here.

* Logs and screenshot depicting the problem:

http://www.NetBSD.org/~jmmv/g5-no-fonts/Xorg.log-with-nouveau
http://www.NetBSD.org/~jmmv/g5-no-fonts/Xorg.log-without-nouveau
http://www.NetBSD.org/~jmmv/g5-no-fonts/dmesg
http://www.NetBSD.org/~jmmv/g5-no-fonts/screenshot.jpg

-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: powerpc (ppc64)

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

Versions of packages xserver-xorg-video-nouveau depends on:
ii  libc6  2.13-37
ii  libdrm22.4.40-1~deb7u2
ii  libudev0   175-7
ii  xserver-xorg-core [xorg-video-abi-12]  2:1.12.4-4

Versions of packages xserver-xorg-video-nouveau recommends:
ii  libgl1-mesa-dri  8.0.5-3

xserver-xorg-video-nouveau suggests no packages.


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



Bug#696650: [PATCH v3] md: protect against crash upon fsync on ro array

2013-01-28 Thread Ben Hutchings
On Mon, 2013-01-28 at 13:39 +0100, Sebastian Riemer wrote:
 
 On 28.01.2013 11:32, Sebastian Riemer wrote:
  O.K., then I hope Neil applies the attached patch. I've changed the
  return value to success.
  
  This is also something for linux-stable and should apply to many kernel
  versions without an issue.
  
 
 I've tried to race with continuous fsyncs against continuous mdadm -o
 /dev/md0; mdadm -w /dev/md0; in parallel but couldn't break it.
 Therefore, no additional locking is required and this part can be put
 directly before the RCU locking stuff and the suspended handling.
 
 I've attached version 3 of the patch.

 From fe0357344877c9b9cc623fd582a4e0670e448317 Mon Sep 17 00:00:00 2001
 From: Sebastian Riemer sebastian.rie...@profitbricks.com
 Date: Fri, 25 Jan 2013 12:46:59 +0100
 Subject: [PATCH v3] md: protect against crash upon fsync on ro array
 
 If an fsync occurrs on a read-only array, we need to send a
 completion for the IO and may not increment the active IO count.
 Otherwise, we hit a bug trace and can't stop the MD array anymore.
 
 By advice of Christoph Hellwig we silently return success.
 
 Cc: Christoph Hellwig h...@infradead.org
 Cc: Ben Hutchings b...@decadent.org.uk
 Cc: NeilBrown ne...@suse.de
 Signed-off-by: Sebastian Riemer sebastian.rie...@profitbricks.com
 Reported-by: Ben Hutchings b...@decadent.org.uk
 
 ---
  drivers/md/md.c |5 +
  1 files changed, 5 insertions(+), 0 deletions(-)
 
 diff --git a/drivers/md/md.c b/drivers/md/md.c
 index 3db3d1b..6ba20f7 100644
 --- a/drivers/md/md.c
 +++ b/drivers/md/md.c
 @@ -307,6 +307,10 @@ static void md_make_request(struct request_queue
 *q, struct bio *bio)
 bio_io_error(bio);
 return;
 }
 +   if (mddev-ro == 1  unlikely(rw == WRITE)) {
 +   bio_endio(bio, 0);
 +   return;
 +   }
 smp_rmb(); /* Ensure implications of  'active' are visible */
 rcu_read_lock();
 if (mddev-suspended) {

I'm slightly uneasy about returning 0 for all writes to a read-only
deivce, because if someone ever fails to check the read-only flag
elsewhere this could turn into silent data loss.  Does this work:

BUG_ON(bio_segments(bio));

Or should it be:

bio_endio(bio, bio_segments(bio) == 0 ? 0 : -EROFS);

to make the error survivable?

Ben.

-- 
Ben Hutchings
If more than one person is responsible for a bug, no one is at fault.


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


Bug#699215: vlc: segfaults while opening certain videos.

2013-01-28 Thread David M Smith
Package: vlc
Version: 2.0.3-4
Severity: important

vlc segfaults while opening some H.264 videos.

gdb output below.


david@Aya:~$ gdb vlc
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/bin/vlc...Reading symbols from
/usr/lib/debug/usr/bin/vlc...done.
done.
(gdb) start
Temporary breakpoint 1 at 0x401180: file vlc.c, line 97.
Starting program: /usr/bin/vlc
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.

Temporary breakpoint 1, main (i_argc=1, ppsz_argv=0x7fffe7c8) at vlc.c:97
97  vlc.c: No such file or directory.
(gdb) continue
Continuing.
VLC media player 2.0.3 Twoflower (revision 2.0.2-93-g77aa89e)
[New Thread 0x7fffecfb8700 (LWP 8604)]
[0x605108] main libvlc: Running vlc with the default interface. Use 'cvlc' to
use vlc without interface.
[New Thread 0x7fffedd17700 (LWP 8605)]
[New Thread 0x7fffda763700 (LWP 8611)]
[New Thread 0x7fffd9d83700 (LWP 8615)]
[New Thread 0x7fffd9f62700 (LWP 8619)]
[New Thread 0x7fffd81bb700 (LWP 8620)]
[New Thread 0x7fffd39c0700 (LWP 8621)]
[Thread 0x7fffd9f62700 (LWP 8619) exited]
[Thread 0x7fffd39c0700 (LWP 8621) exited]
[New Thread 0x7fffc8c88700 (LWP 8622)]
[New Thread 0x7fffc8487700 (LWP 8623)]
[New Thread 0x7fffc7c86700 (LWP 8624)]
[New Thread 0x7fffc7485700 (LWP 8625)]
[New Thread 0x7fffd39c0700 (LWP 8626)]
[New Thread 0x7fffd9f62700 (LWP 8627)]
libva: VA-API version 0.32.0
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva: va_openDriver() returns 0
[0x1542158] avcodec decoder: Using VA API version 0.32 for hardware decoding.
[New Thread 0x7fffd0150700 (LWP 8628)]
[New Thread 0x7fffc31a8700 (LWP 8629)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffd39c0700 (LWP 8626)]
0x7fffcbbf0f37 in CopyFromUswc (dst=0x131ab10
\020\020\020\020\020\020\020\020\020\020,
dst@entry=0x131a960 '\020' repeats 50 times,
\021\021\022\024\027\033\035\036\036\037\037\037\036\036\035\034, '\033'
repeats 16 times,
\032\032\031\031\030\030\030\030\027\027\026\026\026\026\026\027\027\027\027\027\030\031\032\033\027\027\032\032\027\027\027\027\027,
'\030' repeats 16 times,
\027\030\031\035\035\035\034\033\033\033\033\034\034\035\035\035\036\036\036\036\036\036\036\035\035\034\034\033\033\034
\034 \033\033
\037\037\036\036\035\035\035\036\036\036\036\037\036\036\036\036\035\035\035\035\036\036\035\035\034\034\034\034\035\035\036\037...,
dst_pitch=dst_pitch@entry=432,
src=0x7fffd9dba1aa '\020' repeats 52 times,
\021\023\026\027\026\026\026\026\026\026\026\025\025\025, '\024' repeats 16
times,
\025\025\026\026\026\027\027\027\026\026\026\026\026\026\026\027\027\027\027\027\027\027\026\027\033\034\033\032\027\025\023\023,
'\022' repeats 16 times,
\023\024\026\030\033\034\033\033\034\035\036\037\037\037\037\037\036\036\036\036\036\036\036\036\037\037
!!\036((\036 \033\033 \037\037\037\037\036\036\037\037
\#%%%$$$%'''...,
src@entry=0x7fffd9dba000 '\020' repeats 50 times,
\021\021\022\024\027\033\035\036\036\037\037\037\036\036\035\034, '\033'
repeats 16 times,
\032\032\031\031\030\030\030\030\027\027\026\026\026\026\026\027\027\027\027\027\030\031\032\033\027\027\032\032\027\027\027\027\027,
'\030' repeats 16 times,
\027\030\031\035\035\035\034\033\033\033\033\034\034\035\035\035\036\036\036\036\036\036\036\035\035\034\034\033\033\034
\034 \033\033
\037\037\036\036\035\035\035\036\036\036\036\037\036\036\036\036\035\035\035\035\036\036\035\035\034\034\034\034\035\035\036\037...,
src_pitch=src_pitch@entry=426, width=width@entry=426,
height=height@entry=9, cpu=cpu@entry=4072) at copy.c:86
86  copy.c: No such file or directory.
(gdb) bt
#0  0x7fffcbbf0f37 in CopyFromUswc (dst=0x131ab10
\020\020\020\020\020\020\020\020\020\020,
dst@entry=0x131a960 '\020' repeats 50 times,
\021\021\022\024\027\033\035\036\036\037\037\037\036\036\035\034, '\033'
repeats 16 times,
\032\032\031\031\030\030\030\030\027\027\026\026\026\026\026\027\027\027\027\027\030\031\032\033\027\027\032\032\027\027\027\027\027,
'\030' repeats 16 times,
\027\030\031\035\035\035\034\033\033\033\033\034\034\035\035\035\036\036\036\036\036\036\036\035\035\034\034\033\033\034
\034 \033\033
\037\037\036\036\035\035\035\036\036\036\036\037\036\036\036\036\035\035\035\035\036\036\035\035\034\034\034\034\035\035\036\037...,
dst_pitch=dst_pitch@entry=432,
src=0x7fffd9dba1aa '\020' repeats 52 times,
\021\023\026\027\026\026\026\026\026\026\026\025\025\025, '\024' repeats 16
times,

Bug#699191: Bug#699191: aptitude don't depend on apt, but don't work correctly without apt

2013-01-28 Thread Daniel Hartwig
On 29 January 2013 06:02, Robert Paciorek rob...@opcode.eu.org wrote:
 On 2013-01-28 22:09:27 Axel Beckert wrote:
  aptitude don't depend on apt package but without apt can't download
  packages - display error:
 
  The method driver /usr/lib/apt/methods/http could not be found.

 This has been discussed just recently on the Aptitude mailing list:

 http://lists.alioth.debian.org/pipermail/aptitude-devel/2012-December/003251.html

Right.  The issue of libapt-pkg being unable to acquire files with apt
should be followed up at that bug: http://bugs.debian.org/696411.

Otherwise, you may have bumped in to another problem in aptitude.

 But when i have apt (0.8.15.10) with auto flag

For now you should not do that.

 and apt config
 (etc/apt/apt.conf):
 APT::AutoRemove::RecommendsImportant false;
 APT::AutoRemove::SuggestsImportant false;
 APT::Install-Recommends false;
 APT::Install-Suggests false;
 aptitude::UI::Incremental-Search false;

 aptitude remove apt without special confirmation, writing to log
 not used:
 [log appears to be a large upgrade]

 When i try manualy remove apt i see message:
 apt is an essential package!
 Are you sure you want to remove it?
 Type 'Yes, I am aware this is a very bad idea' if you are.

 The same when i run from command line aptitude full-upgrade or
 aptitude install aptitude:

 But NOT when update aptitude (or update all upgradable packages) from
 ncurses interface.

So you only encounter this problem (no remove-essential warning) when
upgrading packages in the curses interface?  If so, I will retitle
this report to include just that problem.


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



Bug#699216: ITP: dtc -- Tools for Flattened Device Trees (FDT)

2013-01-28 Thread Shawn
Package: wnpp
Owner: shawnland...@gmail.com
Severity: wishlist

* Package name: dtc
  Version : 1.3.0
  Upstream Author : David Gibson d...@au1.ibm.com
* URL : http://www.denx.de/wiki/U-Boot/UBootFdtInfo
* License : GPL-2+ and BSD (parts)
  Programming Lang: C
  Description : Tools for Flattened Device Trees (FDT)

A number of devices now boot with use of Flattened Device Trees (FDT). In
addition
to the general purpose libfdt library, this package includes the tools
convert-dtsv0, dtc
dtdiff, fdtdump, fdtget, fdtput.

This package will be useful, for example, in packaging kernels that can
boot on the
Samsung ARM chromebook.

I have the package in a largely working state, but it needs a little more
polishing.


Bug#699215: vlc: segfaults while opening certain videos.

2013-01-28 Thread David Smith

notfound 699215 2.0.5-1
thanks

On 01/29/2013 01:50 PM, David M Smith wrote:

Package: vlc
Version: 2.0.3-4
Severity: important

vlc segfaults while opening some H.264 videos.

gdb output below.



This crash does not happen while using the version of VLC in Debian 
unstable 2.0.5-1. The video files open just fine.



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



Bug#698952: RM: llvm-3.2 -- ROM; A new source package will be uploaded (including clang)

2013-01-28 Thread Sylvestre Ledru
On 28/01/2013 22:22, Ansgar Burchardt wrote:
 Sylvestre Ledru sylves...@debian.org writes:
 On 28/01/2013 21:02, Matthias Klose wrote:
  and what does hinder you to first get the new package accepted,
 and then removing the old ones?

 It is what I tried but it failed with:
 Version check failed (binary=llvm-3.2-runtime, version=3.2-1~exp1,
 other-version=3.2-2, suite=unstable)
 
 Don't upload packages to experimental that have a lower version than
 packages already existing in unstable. (Yes, the error message could be
 improved.)
Oh I understood the message.  :)
It is just that I have new two source tarballs for my package. I guess
that just going 3.2-3 would not work.

Sylvestre


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



Bug#699123: about packaging python-sh

2013-01-28 Thread Ben Carrillo
On Tue, Jan 29, 2013 at 12:52:54AM +, Laszlo Boszormenyi (GCS) wrote:
 Hi Ben,
 
 How the packaging goes? I've a package, ready to be uploaded. But the

Hi Laszlo,
I got a sponsor and it is already in the NEW queue.
http://ftp-master.debian.org/new/python-sh_1.07-1.html

Any feedback is more than welcome :)

 -- 
 To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: http://lists.debian.org/1359420774.21674.141.camel@julia
 


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



Bug#699122: package uploaded to mentors

2013-01-28 Thread Ben Carrillo
I uploaded a first version of the package:
https://mentors.debian.net/package/python-srp

I got a sponsor who will be reviewing it soon, any other feedback is more
than welcome.


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



Bug#659440: bumblebee packaging

2013-01-28 Thread Vincent Cheng
On Wed, Jan 23, 2013 at 2:24 AM, Vincent Cheng vincentc1...@gmail.com wrote:
[...]
 Anyways, right now I'm hitting a strange bug with the packages I
 built; dpkg just seems to hang while installing bumblebee and
 bumblebee-nvidia, i.e.:
 $ sudo dpkg -i bumblebee_3.0.1-1_amd64.deb bumblebee-nvidia_3.0.1-1_amd64.deb
 (Reading database ... 398188 files and directories currently installed.)
 Preparing to replace bumblebee 3.0.1-1 (using bumblebee_3.0.1-1_amd64.deb) ...
 [ ok ] Stopping Bumblebee daemon: bumblebeed.
 Unpacking replacement bumblebee ...
 Preparing to replace bumblebee-nvidia 3.0.1-1 (using
 bumblebee-nvidia_3.0.1-1_amd64.deb) ...
 Unpacking replacement bumblebee-nvidia ...
 Setting up bumblebee (3.0.1-1) ...
 Installing new version of config file /etc/init.d/bumblebeed ...
 update-initramfs: deferring update (trigger activated)
 ...seems to get stuck here

It turns out that the problem isn't caused by the postinst script. I
tried stripping out portions of it piece by piece (starting with the
conffile handling/dpkg-maintscript-helper snippets), but nothing
helped. Then I took a look at what should've appeared right afterwards
if dpkg didn't get stuck somehow:

snip
Setting up bumblebee (3.0.1-1) ...
Adding members from group(s) 'adm sudo admin' to 'bumblebee':
update-initramfs: deferring update (trigger activated)
[ ok ] Starting Bumblebee daemon: bumblebeed.

Ah, bumblebee's init script...

A 3-way comparison later between the distro-agnostic init script
provided upstream, the one provided by suwako.nomanga.net, and the one
currently in the pkg-nvidia git repo (presumably taken from a dh-make
template?), and it turns out that this is what was missing:

-DAEMON_ARGS=--use-syslog
+DAEMON_ARGS=--daemon --use-syslog

And the package installs fine now. :)

Aron, have you contacted upstream and asked to merge our work with
their PPA packaging? I want to try to push as much of our work
upstream to avoid duplicate work and potential oversights on our
part...also, I suppose maybe some of their Ubuntu PPA packagers might
be able to help with upstart. I'll go about preparing a merge request
on Github if you aren't planning on doing so yourself.

Now that bumblebee is taken care of, I've (finally) uploaded my primus
packaging, to collab-maint for now (but am open to moving it into
pkg-nvidia) [1].

Regards,
Vincent

[1] http://anonscm.debian.org/gitweb/?p=collab-maint/primus.git


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



Bug#691477: (no subject)

2013-01-28 Thread Marek Buras
You are right. It wasn't the best idea to use Iceweasel ;)
I updated the patch, so now xchat will use Epiphany instead.
Sorry for the confusion.

-- 
Marek Buras
cyfr0n (at) go2.pl
Description: Changes default browser from Opera (which is non-free) to Epiphany.
Author: Marek Buras cyf...@go2.pl
Origin: vendor
Forwarded: no
Last-Update: 2013-01-29
--- a/src/common/xchat.c
+++ b/src/common/xchat.c
@@ -604,7 +604,7 @@
 	NAME WII\n			CMD quote WHOIS %2 %2\n\n;
 
 static char defaultconf_urlhandlers[] =
-		NAME Open Link in Opera\n		CMD !opera -remote 'openURL(%s)'\n\n;
+		NAME Open Link in Epiphany\n		CMD !epiphany '%s'\n\n;
 
 #ifdef USE_SIGACTION
 /* Close and open log files on SIGUSR1. Usefull for log rotating */


Bug#699217: nss: FTBFS on x32: Using -m32

2013-01-28 Thread Daniel Schepler
Source: nss
Version: 2:3.14.1.with.ckbi.1.93-1
Severity: wishlist
Tags: patch
User: debian-...@lists.debian.org
Usertags: port-x32 ftbfs-x32

The nss source package is getting a build failure on x32:

URL:http://buildd.debian-ports.org/status/fetch.php?pkg=nssarch=x32ver=2%3A3.14.1.with.ckbi.1.93-1stamp=1359406833
...
cd nsinstall; /usr/bin/make libs
make[4]: Entering directory
`/build/buildd-nss_3.14.1.with.ckbi.1.93-1-x32-quS2VQ/nss-3.14.1.with.ckbi.1.93/mozilla/security/coreconf/nsinstall'
gcc -o Linux3.6_x86_glibc_PTH_OPT.OBJ/nsinstall.o -c -g -O2
-fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security -Wall -pipe -D_FORTIFY_SOURCE=2 -ansi
-D_POSIX_SOURCE -D_BSD_SOURCE -D_XOPEN_SOURCE -fPIC -Di386 -DLINUX2_1
-m32 -Wall -Werror-implicit-function-declaration -Wno-switch -pipe
-DHAVE_STRERROR -DLINUX -Dlinux -DXP_UNIX -UDEBUG -DNDEBUG
-D_REENTRANT -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -I/usr/include/nspr
-I/build/buildd-nss_3.14.1.with.ckbi.1.93-1-x32-quS2VQ/nss-3.14.1.with.ckbi.1.93/mozilla/dist/include
-I../../../dist/public/coreconf -I../../../dist/private/coreconf
nsinstall.c
In file included from /usr/include/features.h:341:0,
 from /usr/include/stdio.h:27,
 from nsinstall.c:8:
/usr/include/stdc-predef.h:30:26: fatal error: bits/predefs.h: No such
file or directory
compilation terminated.
make[4]: *** [Linux3.6_x86_glibc_PTH_OPT.OBJ/nsinstall.o] Error 1
make[4]: Leaving directory
`/build/buildd-nss_3.14.1.with.ckbi.1.93-1-x32-quS2VQ/nss-3.14.1.with.ckbi.1.93/mozilla/security/coreconf/nsinstall'
...

It should be using -mx32 instead of -m32.  I'm attaching a debdiff for
changes I applied to get the package to build on x32, for an upload to
debian-ports/unreleased.  (It's very loosely based on the patch from
Gentoo, except I made it based on an amd64 build where they made it
based on an i386 build.)
-- 
Daniel Schepler


nss.debdiff
Description: Binary data


Bug#685640: severity?

2013-01-28 Thread Thomas Lange
I'm not sure about the severity of this bug. It affects all
distributions which uses yum. These are all versions of CentOS and
SLC, but I bet all others are also affected.

The bug makes it impossible to create an RPM installation and therefore
is at least important. But it makes rinse unsusable for the affected
distributions. 
-- 
regards Thomas


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



Bug#694286: fstrcmp: missing Breaks+Replaces: libfstrcmp-dev ( 0.4)

2013-01-28 Thread Andreas Beckmann
Followup-For: Bug #694286

Hi,

I'm attaching a proposed patch for a t-p-u upload.


Andreas
diff -Nru fstrcmp-0.4.D001/debian/changelog fstrcmp-0.4.D001/debian/changelog
--- fstrcmp-0.4.D001/debian/changelog	2011-10-06 01:38:39.0 +0200
+++ fstrcmp-0.4.D001/debian/changelog	2013-01-29 08:26:41.0 +0100
@@ -1,3 +1,10 @@
+fstrcmp (0.4.D001-1.1) UNRELEASED; urgency=low
+
+  * Non-maintainer upload.
+  * fstrcmp: Add Breaks/Replaces: libfstrcmp-dev ( 0.4).  (Closes: #694286)
+
+ -- Andreas Beckmann a...@debian.org  Tue, 29 Jan 2013 08:22:38 +0100
+
 fstrcmp (0.4.D001-1) unstable; urgency=low
 
   * This change set prepares the fstrcmp project for the next public release.
diff -Nru fstrcmp-0.4.D001/debian/control fstrcmp-0.4.D001/debian/control
--- fstrcmp-0.4.D001/debian/control	2011-10-06 01:38:39.0 +0200
+++ fstrcmp-0.4.D001/debian/control	2013-01-29 08:26:39.0 +0100
@@ -12,6 +12,8 @@
 Description: fuzzy comparison of strings
  This package provides a command to make fuzzy string comparisons.
 Depends: ${misc:Depends}, ${shlibs:Depends}, libfstrcmp0
+Breaks: libfstrcmp-dev ( 0.4)
+Replaces: libfstrcmp-dev ( 0.4)
 
 Package: libfstrcmp0
 Section: libs


Bug#699192: installation-reports: French translation for message displayed in case of invalid hostname is wrong

2013-01-28 Thread Christian PERRIER
reassign 699192 netcfg
thanks

Quoting Thierry Rascle (thier...@free.fr):
 Package: installation-reports
 Severity: minor
 Tags: l10n d-i
 
 Dear Maintainer,
 
 When the user types in an invalid hostname, a message is displayed to explain
 which characters are allowed in a hostname, and what is the maximum length of 
 a
 hostname. The french translation of this message states that the length of an
 hostname should be greater than 63 characters, which is wrong.

Doh. It took me 10 minutes to figure out that you're right..:-). I was
about to close your bug report stating that my translation is damn correct.


#. Type: error
#. Description
#. :sl2:
#: ../netcfg-common.templates:20001
msgid 
A valid hostname may contain only the numbers 0-9, upper and lowercase 
letters (A-Z and a-z), and the minus sign. It must be at most 
${maxhostnamelen} characters long, and may not begin or end with a minus 
sign.
msgstr 
Un nom valable ne peut contenir que les chiffres 0-9, des lettres minuscules 
ou majuscules (A-Z et a-z) et le signe moins ; sa longueur doit être 
supérieure à ${maxhostnamelen} caractères et il ne peut ni commencer ni 
finir par un signe moins.

sa longueur NE doit PAS être..:-)

Fun to see that this message hasn't been changed for over two years
probably and nobody ever noticed..:-)

Mercije vais essayer de convaincre le D-I release manager qui se
trouve comprendre un peu le français...:-)




signature.asc
Description: Digital signature


<    1   2   3