date:20120122

Hello David,
hello list,
any news on this listing? All my packages contain (additional, not
upstreamable) content which is set up for po4a-translation and I really
would like them to gather more translations. For this, it has to be
visible on those statistic pages. (And I can name a few more packages
where I just discovered by chance that they are available for
translation).

So it would be great if you could either document the requirements for
inclusion (so that I can fix at least my packages) or -- which would
be better -- improve the inclusion heuristic to get more packages
listed, including but not limited to mine.

Thanks for working on those pages and making i18n/l10n a reality!

Greetings

  Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software libre: http://www.ffii.de/


signature.asc
Description: Digital signature

Bug#656848: libav-dev package?

2012-01-22 Thread Harald Dunkel

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: libav
Version: 4:0.8~beta2-3
Severity: wishlist

Would you mind to provide a meta package libav-dev requesting
all the other libav development packages in the same version?
This could make writing package build dependencies much easier.


Many thanx in advance

Harri
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk8b3lEACgkQUTlbRTxpHjf9JACfWUTV5KKV7Is8VKh/BH9rT0dF
lEEAnjnobbkAgP1mdMCFbE7zOMZBaGMc
=SbJr
-END PGP SIGNATURE-



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

Bug#656849: zd1211-firmware: Connection drops frequently

2012-01-22 Thread R33D3M33R

Package: zd1211-firmware
Version: 2.21.0.0-1
Severity: important

I have a USB wireless adapter:

Bus 003 Device 032: ID 0ace:1215 ZyDAS ZD1211B 802.11g

I installed zd1211-firmware like the wiki says: http://wiki.debian.org/zd1211rw

The connection drops frequently. It seems to be related to the amount of load.
When downloading with fast speeds, watching videos online and so on it's stable
only for few seconds, but normal browsing seems to work ok.



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

Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=sl_SI.UTF-8, LC_CTYPE=sl_SI.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#552747: aptitude: Internal error: unexpected null solution.

2012-01-22 Thread Hristo Hristov

Hi Daniel,

I found the root cause of this bug:
http://anonscm.debian.org/gitweb/?p=aptitude/aptitude.git;a=commitdiff;h=36164657896b16a079f2e52d57ebdfcef3c61178#patch15

The correct change should have been:
-if(sol.get_actions().empty())
+if(sol.get_choices().size() == 0)

Cheers,
Hristo Hristov



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

Bug#656113: wims: fails to install - bin/mkindex: cannot create mkindex.log: Permission denied

2012-01-22 Thread Georges Khaznadar

Hello Andreas,

thank you for the notification.

I tried to reproduce the failure you described. I could reproduce it
*once*:

- pbuilder login == creates a directory /var/cache/pbuilder/build/foo
- cp wims*_4.02-1_amd64.deb /var/cache/pbuilder/build/foo/tmp == copies
  of relevant packages
- cd /var/cache/pbuilder/build/foo/; dpkg -i tmp/*deb == fails to
  install due to missing dependencies. By the way, i noticed a strange
  quirk: the package adduser was missing.
- apt-get -f install == downloads dependencies, and installs them, then
  tries to install wims : then I could reproduce the failure you
  noticed!

However my pbuilder archive (for ARCH=amd64, DIST=sid) was not
refreshed. So I made another try:

- pbuilder update
- pbuilder login
- cd /var/cache/pbuilder/build/foo; apt-get install wims

And then the package wims was properly installed.
Running this sequence again gave the same result, of course.



So my opinion is that at some time the environment provided by Sid
missed some feature, which is missing no longer, now.

In my opinion, this bug report should closed, as the bug is not
reproducible. What is your idea about it?

Best regards,   Georges.

Andreas Beckmann a écrit :
 Package: wims
 Version: 4.02-5
 Severity: serious
 User: debian...@lists.debian.org
 Usertags: piuparts
 
 Hi,
 
 during a test with piuparts I noticed your package failed to install. As
 per definition of the release team this makes the package too buggy for
 a release, thus the severity.
 
 From the attached log (scroll to the bottom...):
 
   Selecting previously unselected package wims.
   (Reading database ... 26747 files and directories currently installed.)
   Unpacking wims (from .../archives/wims_4.02-5_amd64.deb) ...
   Adding system user `wims' (UID 102) ...
   Adding new group `wims' (GID 105) ...
   Adding new user `wims' (UID 102) with group `wims' ...
   Not creating home directory `/var/lib/wims'.
   Adding system user `nowims' (UID 103) ...
   Adding new group `nowims' (GID 106) ...
   Adding new user `nowims' (UID 103) with group `nowims' ...
   Not creating home directory `/'.
   Processing triggers for wims-modules ...
   Indexed 21 modules.
   Indexed 0 cn sheets.
   Indexed 27 en sheets.
   Indexed 0 es sheets.
   Indexed 321 fr sheets.
   Indexed 19 it sheets.
   Indexed 48 nl sheets.
   bin/mkindex: 194: bin/mkindex: cannot create mkindex.log: Permission denied
   bin/mkindex: 199: bin/mkindex: cannot create index.log: Permission denied
   oefdoc.pl en
   peut pas créer public_html/scripts/js/editor/scripts_1/bd_js/en/iff_bd.js 
 at bin/oefdoc.pl line 430.
   dpkg: error processing wims-modules (--unpack):
subprocess installed post-installation script returned error exit status 13
   configured to not write apport reports
   Errors were encountered while processing:
wims-modules
 
 The installation performed by piuparts is done with
 DEBIAN_FRONTEND=noninteractive and stdin redirected from /dev/null.
 
 cheers,
 
 Andreas



-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: Digital signature

Bug#656204: this is in fact not an RC bug

2012-01-22 Thread Cyril Brulebois

Rolf Leggewie debian-b...@rolf.leggewie.biz (22/01/2012):
 The current package is installable just fine.  While no doubt
 resulting in a bit of an ugly state, the update from one particular
 unstable package to another breaks but also works at least to the
 point of not leaving the package unusable and according to Paul there
 is also an easy workaround to resolve the situation.  Nothing
 qualifying for grave severity that I can see.

Erm. Breaking the dpkg configuration phase means you can break alot of
other packages. On mine that was “just” glib*, gtk*, so the whole X
session was totally broken.

 I find it highly irritating that nobody wanted to properly maintain
 this package for years and now that I've taken on this difficult task
 of cleaning up this year-long neglect everybody and their uncle thinks
 they know better how to do that. [ more whining ]

Heh, welcome to maintaining libraries. The policy has details, lintian
helps one not to trivial errors, and fixing the package (be it about
where to ship this or that part of the -dev/lib packages, or about
fixing upgradability issues) is AFAICT trivial. Why don't you just fix
the package and move to other things? Mistakes happen every day, it's
not the end of the world to have a grave bug in ones package if one
learns about it and tries to avoid doing the same mistakes again.

 This bug never affected testing, it's in fact not an RC bug even for
 unstable itself.  Anybody who blocks the current package from going to
 testing is not doing Debian a favour.

Wrong. Policy 7.6 says it's an RC bug.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#653630: /sbin/mount.nfs: Re: nfs-common: Only root can unmount, nautilus badly confused

Package: nfs-common
Version: 1:1.2.5-3
Followup-For: Bug #653630

Dear Maintainer,


Seems that I have the same issue with nfs.

There is an entry in my fstab:
liveserv:/mnt/library//mnt/library   nfs 
noauto,user   0 0
I mount the nfs share as user without any problem:
$mount /mnt/library
Then I try to umount:
$umount /mnt/library
 umount: only root can unmount liveserv:/mnt/library/ from 
/mnt/library

Everything was working properly before the last dist-upgrade Jan 21 
2012 (I did the previos one on Jan 9 2012).
Just after the upgrade I've got the error: umount: /mnt/library mount 
disagrees with the fstab.
Then I managed to get rid of this error by putting a trailing slash to 
the fstab entry, but the error I mentioned above is still there.


Thanks,
Pavel Yakunin


-- Package-specific info:
-- rpcinfo --
   program vers proto   port
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
1000241   udp  50933  status
1000241   tcp  48722  status
1000211   udp  57840  nlockmgr
1000213   udp  57840  nlockmgr
1000214   udp  57840  nlockmgr
1000211   tcp  37262  nlockmgr
1000213   tcp  37262  nlockmgr
1000214   tcp  37262  nlockmgr
-- /etc/default/nfs-common --
NEED_STATD=
STATDOPTS=
NEED_IDMAPD=
NEED_GSSD=
-- /etc/idmapd.conf --
[General]
Verbosity = 0
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
-- /etc/fstab --
liveserv:/mnt/library/mnt/library   nfs noauto,user   0 
0 
liveserv:/mnt/photo/  /mnt/photo  nfs noauto,user   0 0
liveserv:/mnt/backup/  /mnt/backup  nfs noauto,user   0 0
lserv:/mnt/music/ /mnt/lserv-music   nfs noauto,user
   0 0
lserv:/mnt/archive/ /mnt/archive   nfs noauto,user  
 0 0
lserv:/home//mnt/lserv-home  nfs noauto,user
   0 0
liveserv:/mnt/mirror/   /mnt/mirror nfs noauto,user 0 0
-- /proc/mounts --
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0
liveserv:/mnt/library/ /mnt/library nfs 
rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.104,mountvers=3,mountport=46570,mountproto=udp,local_lock=none,addr=192.168.1.104
 0 0

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

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

Versions of packages nfs-common depends on:
ii  adduser 3.113
ii  initscripts 2.88dsf-18
ii  libc6   2.13-24
ii  libcap2 1:2.22-1
ii  libcomerr2  1.42-1
ii  libdevmapper1.02.1  2:1.02.67-2
ii  libevent-2.0-5  2.0.16-stable-1
ii  libgssapi-krb5-21.10+dfsg~alpha2-1
ii  libgssglue1 0.3-4
ii  libk5crypto31.10+dfsg~alpha2-1
ii  libkeyutils11.5.2-2
ii  libkrb5-3   1.10+dfsg~alpha2-1
ii  libnfsidmap20.25-1
ii  libtirpc1   0.2.2-5
ii  libwrap07.6.q-22
ii  lsb-base3.2-28
ii  rpcbind 0.2.0-7
ii  ucf 3.0025+nmu2

Versions of packages nfs-common recommends:
ii  python  2.7.2-9

nfs-common 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#656850: MPlayer recommends libbluray1 which in turn recommends libbluray-bdj which requires JRE so the default mplayer install brings java bloat to the system

2012-01-22 Thread Paul Fertser

Package: mplayer
Version: 2:1.0~rc4.dfsg1+svn34540-1
Severity: minor

Trying to install mplayer on a system with default apt configuration
results in installing all the recommended packages as well which
necessarily brings in some headless Java variant as libbluray-bdj
dependency which is recommended by libbluray1 to the system which
might be highly undesired and confusing.

Imho it would be nice if mplayer only suggested libbluray1.

Package: libbluray1
Version: 1:0.2.1+git20111208.63e308d-1

Debian wheezy/sid armhf



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

Bug#656851: nmu: libmediainfo_0.7.52-1 (FTBFS fix)

2012-01-22 Thread Chow Loong Jin

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


nmu libmediainfo_0.7.52-1 . s390 . -m Rebuild against fixed libzen

-- System Information:
Debian Release: wheezy/sid
  APT prefers oneiric-updates
  APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500, 
'oneiric'), (400, 'oneiric-proposed'), (100, 'oneiric-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-hyper2 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_SG.utf8, LC_CTYPE=en_GB.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#652146: hwinfo: diff for NMU version 16.0-2.2

2012-01-22 Thread Christoph Biedl

Steffen Winterfeldt wrote...

 On Wed, 18 Jan 2012, Christoph Biedl wrote:
 
 Steffen Winterfeldt wrote...
 
 Thanks! But shouldn't it be 'mov %%rbx,%%rdi' etc, then?
 
 Hm, why? cpuid affects only the lower 32 Bits. Using %rbx instead
 shouldn't do harm, though.
 
 No, the result is zero-extended to 64 bits in 64bit-mode.

I stand corrected.

(Call me Thomas, I wanted to see that with my own eye, this took a
while, sorry about that.)


By the way, I am quite confused by the fact

  cpuid with %eax set to 0 returns the ID in %ebx,%edx,%ecx

while

  cpuid with %eax set to 0x4000 appearently returns, if running
  under xen, the ID in %ebx,%ecx,%edx, read: With %ecx and %edx in
  swapped order.

Mind of you double-check your code does the right thing unless you've
already done so? I don't have a Xen installation at hand to do this,
they crashed or did other nasty things every time I've tried in the
past six years.

Christoph



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

Bug#650596: gnujump: game does not start

2012-01-22 Thread Bas Wijnen

Thanks for the reminder, I had planned to fixed this, but forgot about
it. It's a trivial fix, though, so I'll get to it soon(tm).

Thanks,
Bas

On 22-01-12 09:44, Dean Evans wrote:
 
 This bug is caused by upgrading to version 1.0.6-3 of gnujump.
 
 It looks like during the updating of the packaging for gnujump the
 --datadir configure flag was incorrectly changed to point to
 '--datadir=/usr/share/games/gnujump' instead of
 '--datadir=/usr/share/games' as in the previous package.
 
 The ~/.gnujump/gnujump.cfg file (correctly) does not get updated during
 upgrade and default_skin variable will still point to
 '/usr/share/games/gnujump/skins/default' while the data is now in 
 '/usr/share/games/gnujump/gnujump/skins/default'.
 
 Thanks,
 Dean
 
 
 
 ___
 Pkg-games-devel mailing list
 pkg-games-de...@lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-games-devel




signature.asc
Description: OpenPGP digital signature

Bug#656197: plasma-widget-networkmanagement conflicts with KDE=4.7

2012-01-22 Thread Allan Sandfeld Jensen

I got new information upstream: https://bugs.kde.org/show_bug.cgi?id=291677

Since this is an old and necessary change, they can not revert it, and since 
this is in kdebase, and not kdelibs, ABI changes are allowed I guess.



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

Bug#230990: Changing libncurses SONAME

2012-01-22 Thread Sven Joachim

tags 230990 + help
thanks

On 2005-06-12 17:20 +0200, Daniel Jacobowitz wrote:

On Tue, Feb 03, 2004 at 03:06:45PM -0500, Daniel Burrows wrote:
It would be nice if the ncurses mouse API could be used to track wheel
events. (reported in X11 as buttons 4/5) At the moment, ncurses seems
to report all wheel events as button 4.

FYI, the latest version of ncurses (uploading soon) does support this -
but it's disabled, because the change is binary incompatible. The next
time we need a new SONAME for libncurses, I intend to enable this.

Unfortunately, switching SONAME seems to be out of the question since
even after the introduction of libtinfo5 we still have dozens of
libraries linking against libncurses. My feeble attempt¹ to fix a few
of them has not changed anything yet.

The only safe way to do this seems to be to introduce versioned symbols
in ncurses, and I don't know at all how to do that in a way which

a) is acceptable for upstream;

b) works correctly for all the bazillion configuration options that
change the ABI, for instance --enable-widec, --enable-ext-colors,
--enable-ext-mouse, --with-termlib=..., --with-ticlib=... etc.

In short, we're stuck with the current insane mishmash of
libncurses5/libncursesw5, and I have no idea how to ever get out of this
mess.

See also the thread starting at
http://lists.debian.org/debian-devel/2008/09/msg00435.html.

Sven

¹
http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=ncur...@packages.debian.org;usertag=libncurses5-dependency

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

Bug#611653: Pending fixes for bugs in the w3c-linkchecker package

2012-01-22 Thread pkg-perl-maintainers

tag 611653 + pending
tag 656764 + pending
thanks

Some bugs in the w3c-linkchecker package are closed in revision
bd3518a8214d016d349edf8f68b0d14b920aecb2 in branch 'master' by
Nicholas Bamber

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

Commit message:

* Added Czech translation (note out of date) (Closes: #611653)
* Added Danish translation (Closes: #656764)
* Added Dutch translation (Closes: 656770)




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

Bug#656815: pu: package mediawiki/1:1.15.5-2squeeze3

2012-01-22 Thread Adam D. Barratt

tag 656815 + pending
thanks

On Sat, 2012-01-21 at 23:19 +, Jonathan Wiltshire wrote:
 On Sat, Jan 21, 2012 at 10:39:05PM +, Adam D. Barratt wrote:
  Please go ahead; thanks.
 
 Uploading, thanks for the quick turnaround.

Flagged for acceptance; thanks.

Regards,

Adam




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

Bug#656852: [INTL:he] grub2 translation update

2012-01-22 Thread Lior Kaplan

Package: grub2
Version: 1.99-14
Severity: wishlist
Tags: l10n patch
 X-Debbugs-CC: w...@zak.co.il

Please include the attached translation update in the next upload.

Thanks,
Kaplan

-- Forwarded message --
From: Omer Zak w...@zak.co.il
Date: 2012/1/21
Subject: Re: Missing files for D-I level 2
To: Lior Kaplan kap...@debian.org


Hi Kaplan,
Attached please find the file with updated fuzzy translations and added
missing translations (about 20/40 have been added+modified).

Shabbat Shalom,
--- Omer


On Sat, 2012-01-21 at 00:05 +0200, Lior Kaplan wrote:
 Hi Christian,

 Two updated files attached.

 Omer - could you take a look on the grub file?

 Kaplan

 On Fri, Jan 20, 2012 at 11:55 PM, Christian PERRIER
 bubu...@debian.org wrote:
         You can make full 100%...:-)

         To complete:
         
 http://d-i.debian.org/l10n-stats/level2/files/he/iso-codes_iso_3166_he.po
         http://d-i.debian.org/l10n-stats/level2/files/he/grub_debian_po_he.po

         To translate (ONE string):
         http://d-i.debian.org/l10n-stats/level2/POT/espeakup_debian_po.pot

         --




# translation of grub_debian_po_he.po to Hebrew
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
#
#
# Omer Zak w...@zak.co.il, 2010, 2012.
# Lior Kaplan kap...@debian.org, 2010.
msgid 
msgstr 
Project-Id-Version: grub_debian_po_he\n
Report-Msgid-Bugs-To: gr...@packages.debian.org\n
POT-Creation-Date: 2011-05-27 13:33+0100\n
PO-Revision-Date: 2012-01-21 00:52+0200\n
Last-Translator: Omer Zak w...@zak.co.il\n
Language-Team: Hebrew debian-hebrew-com...@lists.alioth.debian.org\n
Language: he\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
X-Generator: KBabel 1.11.4\n
Plural-Forms:  nplurals=2; plural=(n != 1);\n

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:2001
msgid Chainload from menu.lst?
msgstr הטענה בשרשור מ-menu.lst?

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:2001
msgid GRUB upgrade scripts have detected a GRUB Legacy setup in /boot/grub.
msgstr תסריטי העדכון של GRUB גילו הגדרות GRUB ישנות ב-‎‎/boot/grub.

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:2001
msgid 
In order to replace the Legacy version of GRUB in your system, it is 
recommended that /boot/grub/menu.lst is adjusted to load a GRUB 2 boot image 
from your existing GRUB Legacy setup. This step can be automatically 
performed now.
msgstr כדי להחליף את גירסת GRUB הישנה במערכת שלך, מומלץ לשנות את ‎/boot/grub/menu.lst כך שיבצע הטענה משורשרת של קוד האיתחול של GRUB 2 מהגדרות GRUB הישנות שלך. ניתן לבצע פעולה זו באופן אוטומטי עכשיו.

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:2001
msgid 
It's recommended that you accept chainloading GRUB 2 from menu.lst, and 
verify that the new GRUB 2 setup works before it is written to the MBR 
(Master Boot Record).
msgstr מומלץ שתסכים להטענה משורשרת של GRUB 2 מ-menu.lst ותוודא שהגדרות GRUB 2 החדשות עובדות עבורך, לפני שקוד האתחול נכתב ל-MBR (Master Boot Record)‎ שלך.

#. Type: boolean
#. Description
#: ../grub-pc.templates.in:2001
msgid 
Whatever your decision, you can replace the old MBR image with GRUB 2 later 
by issuing the following command as root:
msgstr לא משנה מהי החלטתך, ביכולתך להחליף יותר מאוחר את קוד האתחול הישן ב-MBR בקוד האתחול של  GRUB 2 ע\י מתן הפקודה הבאה כמשתמש-על:

#. Type: multiselect
#. Description
#. Type: multiselect
#. Description
#: ../grub-pc.templates.in:3001 ../grub-pc.templates.in:4001
msgid GRUB install devices:
msgstr התקנים להתקנת GRUB:

#. Type: multiselect
#. Description
#: ../grub-pc.templates.in:3001
msgid 
The grub-pc package is being upgraded. This menu allows you to select which 
devices you'd like grub-install to be automatically run for, if any.
msgstr חבילת grub-pc משתדרגת כעת. תפריט זה מאפשר לך לבחור בהתקנים שברצונך ש-grub-install ירוץ עליהם אוטומטית, באם יש כאלה.

#. Type: multiselect
#. Description
#: ../grub-pc.templates.in:3001
msgid 
Running grub-install automatically is recommended in most situations, to 
prevent the installed GRUB core image from getting out of sync with GRUB 
modules or grub.cfg.
msgstr בדרך כלל מומלץ להריץ אוטומטית את grub-install כדי למנוע מליבת קוד האתחול המותקנת של GRUB מלהפסיק להיות מתואמת עם מודולי GRUB או עם grub.cfg.

#. Type: multiselect
#. Description
#. Type: multiselect
#. Description
#: ../grub-pc.templates.in:3001 ../grub-pc.templates.in:4001
msgid 
If you're unsure which drive is designated as boot drive by your BIOS, it is 
often a good idea to install GRUB to all of them.
msgstr אם אינך בטוח איזה התקן הוגדר כהתקן האתחול ע\י ה-BIOS שלך, לעתים קרובות יהא זה רעיון טוב להתקין GRUB בכולם.

#. Type: multiselect
#. Description
#. Type: multiselect
#. Description
#: ../grub-pc.templates.in:3001 ../grub-pc.templates.in:4001
msgid 
Note: it is possible to install GRUB to partition boot records as well, and 
some appropriate partitions are offered here. However,

Bug#608647: Typo in package description: down loading

2012-01-22 Thread Benjamin Kerensa

I have attached a fix for the typo in this package description which is 
attached.


--
Benjamin Kerensa  I am what I am because
Team Lead, Ubuntu Oregon  of who we all are. - Ubuntu
bkere...@ubuntu.com
http://ubuntu-oregon.org

diff -u a2ps-4.14/debian/changelog a2ps-4.14/debian/changelog
--- a2ps-4.14/debian/changelog
+++ a2ps-4.14/debian/changelog
@@ -1,3 +1,10 @@
+a2ps (1:4.14-1.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fixed typo in package description. (Closes: #608647)
+
+ -- Benjamin Kerensa bkere...@ubuntu.com  Sun, 22 Jan 2012 03:02:42 -0800
+
 a2ps (1:4.14-1.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -u a2ps-4.14/debian/control a2ps-4.14/debian/control
--- a2ps-4.14/debian/control
+++ a2ps-4.14/debian/control
@@ -26,7 +26,7 @@
  .
  Among the other most noticeable features of a2ps are:
   - various encodings (all the Latins and others),
-  - various fonts (automatic font down loading),
+  - various fonts (automatic font downloading),
   - various medias,
   - various printer interfaces,
   - various output styles,

Bug#653630: /sbin/mount.nfs: Re: nfs-common: Only root can unmount, nautilus badly confused

2012-01-22 Thread Luk Claes

On 01/22/2012 11:34 AM, Pavel Yakunin wrote:

 Seems that I have the same issue with nfs.
 
 There is an entry in my fstab:
 liveserv:/mnt/library//mnt/library   nfs 
 noauto,user   0 0
 I mount the nfs share as user without any problem:
 $mount /mnt/library
 Then I try to umount:
 $umount /mnt/library
  umount: only root can unmount liveserv:/mnt/library/ from 
 /mnt/library
 
 Everything was working properly before the last dist-upgrade Jan 21 
 2012 (I did the previos one on Jan 9 2012).
 Just after the upgrade I've got the error: umount: /mnt/library 
 mount disagrees with the fstab.
 Then I managed to get rid of this error by putting a trailing slash 
 to the fstab entry, but the error I mentioned above is still there.

According to below snippet that automatically was attached to your bug
report, the trailing slash is not in /etc/fstab?

Anyway this bug was introduced by the conversion of /etc/mtab (putting
Michael in Cc, maybe he has an idea how we should prevent this and
similar issues from happening).

 -- /etc/fstab --
 liveserv:/mnt/library/mnt/library   nfs noauto,user   
 0 0 
 liveserv:/mnt/photo/  /mnt/photo  nfs noauto,user   0  0
 liveserv:/mnt/backup/  /mnt/backup  nfs noauto,user   
 0 0
 lserv:/mnt/music/ /mnt/lserv-music   nfs noauto,user  
  0 0
 lserv:/mnt/archive/ /mnt/archive   nfs noauto,user
0 0
 lserv:/home//mnt/lserv-home  nfs noauto,user  
  0 0
 liveserv:/mnt/mirror/ /mnt/mirror nfs noauto,user 0 0
 -- /proc/mounts --
 rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0
 liveserv:/mnt/library/ /mnt/library nfs 
 rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.104,mountvers=3,mountport=46570,mountproto=udp,local_lock=none,addr=192.168.1.104
  0 0

Cheers

Luk



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

Bug#655151: python-newt: ImportError: No module named _snack

2012-01-22 Thread Ulrich P. Klein

Package: python-newt
Version: 0.52.14-7
Followup-For: Bug #655151

The bug is still present in 0.52.14-7 on amd64:

|% python -c 'import snack'
|Traceback (most recent call last):
|  File string, line 1, in module
|  File /usr/lib/python2.7/dist-packages/snack.py, line 42, in module
|import _snack
|ImportError: No module named _snack

From the build log:
|install: cannot stat `python2.6/_snackmodule.so': No such file or directory
|install: cannot stat `python2.7/_snackmodule.so': No such file or directory


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'testing'), (150, 
'unstable'), (99, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-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 python-newt depends on:
ii  libnewt0.52  0.52.14-7
ii  python   2.7.2-9
ii  python2.62.6.7-4
ii  python2.72.7.2-8

python-newt recommends no packages.

python-newt 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#656063: usb_modeswitch_dispatcher: free(): invalid next size

2012-01-22 Thread Josua Dietze


Am 15.01.2012 17:48, schrieb Frederic MASSOT:

I have several crash of usb_modeswitch_dispatcher ...
...
Jan 15 17:12:23 lobon usb_modeswitch_dispatcher: *** glibc detected
*** /usr/sbin/usb_modeswitch_ dispatcher: free(): invalid next size
(normal): 0x099c3340 ***


After several tests I have pinpointed a problem with seems to revolve 
around setting the PATH environment variable from within the dispatcher 
script. Any subsequent exec command resulted in a crash.


This happens only with the binary dispatcher and *only* in the 
udev-triggered context. Running the binary dispatcher manually from the 
command line will succeed as expected.


I have attached a patch for an immediate work-around.

Further research is neccessary though.

Josua Dietze
diff -urN usb-modeswitch-1.2.2/usb_modeswitch.tcl 
usb-modeswitch-1.2.2-1/usb_modeswitch.tcl
--- usb-modeswitch-1.2.2/usb_modeswitch.tcl 2012-01-19 01:02:58.0 
+0100
+++ usb-modeswitch-1.2.2-1/usb_modeswitch.tcl   2012-01-22 11:43:21.0 
+0100
@@ -27,7 +27,7 @@
 set flags(logging) 0
 set flags(noswitching) 0
 
-set env(PATH) /bin:/sbin:/usr/bin:/usr/sbin
+#set env(PATH) /bin:/sbin:/usr/bin:/usr/sbin
 
 # Execution starts at file bottom
 
@@ -230,7 +230,7 @@
# Now we are actually switching
if $flags(logging) {
Log Command to be run:\nusb_modeswitch -I -W -D -s 20 
$configParam $busParam $devParam -v $usb(idVendor) -p $usb(idProduct) -f 
\$configBuffer
-   set report [exec usb_modeswitch -I -W -D -s 20 
$configParam $busParam $devParam -v $usb(idVendor) -p $usb(idProduct) -f 
$configBuffer 2@ stdout]
+   set report [exec /usr/sbin/usb_modeswitch -I -W -D -s 
20 $configParam $busParam $devParam -v $usb(idVendor) -p $usb(idProduct) -f 
$configBuffer 2@ stdout]
Log \nVerbose debug output of usb_modeswitch and 
libusb follows
Log (Note that some USB errors are to be expected in 
the process)
Log 
@@ -238,7 +238,7 @@
Log 
Log (end of usb_modeswitch output)\n
} else {
-   set report [exec usb_modeswitch -I -Q -D -s 20 
$configParam $busParam $devParam -v $usb(idVendor) -p $usb(idProduct) -f 
$configBuffer 2@ stdout]
+   set report [exec /usr/sbin/usb_modeswitch -I -Q -D -s 
20 $configParam $busParam $devParam -v $usb(idVendor) -p $usb(idProduct) -f 
$configBuffer 2@ stdout]
}
break
} else {

Bug#656770: Pending fixes for bugs in the w3c-linkchecker package

2012-01-22 Thread pkg-perl-maintainers

tag 656770 + pending
thanks

Some bugs in the w3c-linkchecker package are closed in revision
91a8434b32649136f96b1c6ea2454d09bb321618 in branch 'master' by
Nicholas Bamber

The full diff can be seen at
http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/w3c-linkchecker.git;a=commitdiff;h=91a8434

Commit message:

Added Dutch translation (Closes: #656770)




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

Bug#656693: Tried again using upstream git

2012-01-22 Thread Chris Boot

Today I tried again, this time just running debuild over the package source. 
The resulting package did not crash.

-- 
Chris Boot
bo...@bootc.net




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

Bug#656204: this is in fact not an RC bug

2012-01-22 Thread Rolf Leggewie

Thank you for your comment, Cyril.  I'm not convinced but willing to
listen.  I hope you are, too.

On 22.01.2012 18:30, Cyril Brulebois wrote:
 Erm. Breaking the dpkg configuration phase means you can break alot of
 other packages. On mine that was “just” glib*, gtk*, so the whole X
 session was totally broken.

Then grave is the wrong severity, it should be critical.  Are you now
saying this bug is critical?

 Heh, welcome to maintaining libraries. 

Yes, I know.  Much of the pain cannot be avoided.

My frustration is about people who don't really know what's going on
with the package making my life even more difficult than it already is
or needs to be - and insisting on it for the wrong reasons, as it seems
to me.

 fixing the package [...] is AFAICT trivial. Why don't you just fix
 the package and move to other things? Mistakes happen every day, it's
 not the end of the world to have a grave bug in ones package if one
 learns about it and tries to avoid doing the same mistakes again.

See, this is one of the things I'm talking about.  People only
understand half the story (at best) and refuse to read explanations even
after they were given several times.  You for example are apparently
still ignoring the fact that the fix for my mistake had been up well
before this bug even went to grave status.  I've stressed this fact in
almost every comment I made here and you still missed it.

Just one example of how my life gets more complicated than it should be.
 Again, I guess a certain level of this cannot be avoided in a
collaborative effort, but the amount of it I'm seeing is frustrating.

 This bug never affected testing, it's in fact not an RC bug even for
 unstable itself.  Anybody who blocks the current package from going to
 testing is not doing Debian a favour.
 
 Wrong. Policy 7.6 says it's an RC bug.

Even if this was indeed the case, why should the package be kept from
migrating to testing if the problem never affected testing?  That's my
idea of course and only covered by common sense not by Policy.

In any case, 7.6 tells me how to get out of the hole (D'uh!) I had dug
for myself. Nowhere does it say that the hole I dug is RC. Furthermore,
grave severity implies either of the following three

* data loss - obviously not
* security hole - obviously not
* makes package unusable - that's why normally this would be RC but it
  does not apply to this particular ticket, 656204 is a bit special

I've also looked into whether this ticket is critical or serious and
came to the conclusion it isn't.  You and Adam were the ones to set it
to grave, so you must have had one of the three reasons above.

If you really look at it (as I have done) you will find it hard to
justify the initial reflex of RC bug and most definitely of grave
status.  This came a bit as a surprise to me as well.

Apparently, the package already migrated to testing, so this is merely
an opportunity for me to learn more about policy now.




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

Bug#653630: /sbin/mount.nfs: Re: nfs-common: Only root can unmount, nautilus badly confused


Thanks, Luk.


According to below snippet that automatically was attached to your bug
report, the trailing slash is not in /etc/fstab?



Sorry, I've tried different variants of fstab to fix the issue, so that 
there is no trailing slash in the first line of the attached fstab. But 
the mount behavior is the same for all of the nfs entries in my fstab.


Best regards,
Pavel



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

Bug#656215: kicad: New upstream stable version 2011-12-28

2012-01-22 Thread Georges Khaznadar

Hello Andres, I wish you a happy new year!

Andres Cimmarusti a écrit :
Package: kicad
Version: 0.0.20100314-1
Severity: wishlist

I just wanted to bring the maintainers' attention to the fact that there
is a new upstream stable release since december (2011-12-28):

http://iut-tice.ujf-grenoble.fr/cao/

The release dated 29/12/2011 is currently located in the subdirectory
sources/old_versions/

the directory http://iut-tice.ujf-grenoble.fr/cao/ provides some files
which were uploaded more recently (20/01/2012).

My guess is that I should use either
http://iut-tice.ujf-grenoble.fr/cao/kicad-2012-01-19-BZR3256-stable-UBUNTU_10.10_full_with_components_doc.tgz
or
http://iut-tice.ujf-grenoble.fr/cao/kicad_sources-2012-01-19-BZR3256-stable.zip

Those archives are very different in size (201 MB, 13.4 MB) and their
size is different from the size of the archive wich was packaged for
wheezy last time (97 MB).

Which archive should I consider? Have you some documentation summarizing
the changes, and specially the changes in the components set, and the
embedded documents? I rememeber that there have been a few license issues
in the past about sourceless documents.

... hmmm.

I browsed both archives in a viewer.

- The biggest one comes with sourceless executable binaries, many
documents and resources. Only a few documents come with a clearly
declared license (for example French documents are correctly
licensed), and tracking the ownership and the licenses in components
appears as quite impossible.

- the smaller archive unfolds into a directory KiCad-sources. This one
has a valid documentation about ownership and licensing.

I think that I should split the packaging effort in two: make the
package for KiCad's programs now, and begin an ITP (Intention To
Package) for a second package, probably named kicad-common or
kicad-share, based on
kicad-2012-01-19-BZR3256-stable-UBUNTU_10.10_full_with_components_doc.tgz

For the second package, I shall remove many stuff due to license
incertitude, and repack its source into a file
kicad-common_2012.01.19+dfsg1.orig.tar.gz, the suffix dfsg1 standing
for in application of the Debian Free Software Guidelines, which
preclude the distribution of sourceless or ill licensed materials.

Do you agree with such a proposition?

Best regards, Georges.

signature.asc
Description: Digital signature

Bug#656824: Reinstalling GRUB did not help

2012-01-22 Thread Ben Hutchings

On Sun, 2012-01-22 at 15:42 +1100, James Robertson wrote:
 I re-installed grub-pc and grub2 using the following commands:
 
 apt-get install --reinstall grub2
 apt-get install --reinstall grub-pc.
 
 This did not help.

 I then purged the following packages and answered yes to the debconf
 prompt about removing /boot/grub and reinstalled them:
 
 apt-get autoremove --purge grub-common grub-pc-bin grub-pc grub2 grub2-common
 
 This did not help either.
 
 Booting linux-image-3.1.0-1-amd64 works fine.
 
 Is there something specific I am missing or should this bug be re-opened?

Sorry, I've reopened it and will take another look.

Ben.

-- 
Ben Hutchings
Knowledge is power.  France is bacon.


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

Bug#656853: python2.7: Local directories vs. pats are inconsistent

2012-01-22 Thread Matthias Urlichs

Package: python2.7
Version: 2.7.2-8
Severity: normal

Looking at a typical Python installation, I find:

# ls /usr/local/lib/python2.7
dist-packages  site-packages
# python
Python 2.7.2+ (default, Dec  1 2011, 01:55:02) 
[GCC 4.6.2] on linux2
Type help, copyright, credits or license for more information.
 import sys
 sys.path
['', '/usr/lib/python2.7', '/usr/lib/python2.7/plat-linux2', 
'/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', 
'/usr/lib/python2.7/lib-dynload', '/usr/local/lib/python2.7/dist-packages', 
'/usr/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist-packages/PIL', 
'/usr/lib/python2.7/dist-packages/gtk-2.0', '/usr/lib/pymodules/python2.7']
 

The Python path contains /usr/local/dist-packages but not 
/usr/local/site-packages. 
That doesn't make sense.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'unstable'), (600, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.1.0-1-686-pae (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 python2.7 depends on:
ii  libbz2-1.0 1.0.6-1
ii  libc6  2.13-24
ii  libdb4.8   4.8.30-11
ii  libexpat1  2.0.1-7.2
ii  libncursesw5   5.9-4
ii  libreadline6   6.2-8
ii  libsqlite3-0   3.7.9-2
ii  libtinfo5  5.9-4
ii  mime-support   3.51-1
ii  python2.7-minimal  2.7.2-8

python2.7 recommends no packages.

Versions of packages python2.7 suggests:
pn  binutils   2.22-2
pn  python2.7-doc  none

-- no debconf information



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

Bug#548513: Any problem with removing this space?

Hello,
is there anything unclear about this superflous space? If so, do not
hesitate to ask, otherwise it would be great if you could fix this for
Wheezy. If you need help unfuzzying I can help as well.

Thanks!

Greetings

   Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software libre: http://www.ffii.de/


signature.asc
Description: Digital signature

Bug#653630: /sbin/mount.nfs: Re: nfs-common: Only root can unmount, nautilus badly confused

2012-01-22 Thread Michael Biebl

On 22.01.2012 12:30, Luk Claes wrote:
 -- /etc/fstab --
 liveserv:/mnt/library/mnt/library   nfs noauto,user  
  0 0 
 -- /proc/mounts --
 liveserv:/mnt/library/ /mnt/library nfs 
 rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.104,mountvers=3,mountport=46570,mountproto=udp,local_lock=none,addr=192.168.1.104
  0 0

I am missing a bit of context here. Is the problem related to the user
option or regarding a trailing /?

wrt /etc/mtab being a symlink to /proc/mounts: I assume mount.nfs is
built against libmount, seeing [1] as fixed? Do you get a file
/run/mount/utab when the nfs share is mounted? What does it contain?



[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626478
-- 
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#656204: this is in fact not an RC bug

2012-01-22 Thread Cyril Brulebois

Rolf Leggewie debian-b...@rolf.leggewie.biz (22/01/2012):
 Then grave is the wrong severity, it should be critical.  Are you now
 saying this bug is critical?

There might have been no other packages co-upgraded, so grave as “the
package is unusable” is enough.

 My frustration is about people who don't really know what's going on
 with the package making my life even more difficult than it already is
 or needs to be - and insisting on it for the wrong reasons, as it
 seems to me.

I'm not sure if I qualify for this description, AFAICT I only set the
appropriate severity based on what I saw on my system and policy.

  fixing the package [...] is AFAICT trivial. Why don't you just fix
  the package and move to other things? Mistakes happen every day, it's
  not the end of the world to have a grave bug in ones package if one
  learns about it and tries to avoid doing the same mistakes again.
 
 See, this is one of the things I'm talking about.  People only
 understand half the story (at best) and refuse to read explanations
 even after they were given several times.  You for example are
 apparently still ignoring the fact that the fix for my mistake had
 been up well before this bug even went to grave status.  I've stressed
 this fact in almost every comment I made here and you still missed it.

You said there's a fix in git, but there's no fix in the archive. So
setting the appropriate severity, affected versions, etc. is what is
expected. I'm sorry you don't seem to like that.

 Just one example of how my life gets more complicated than it should
 be.  Again, I guess a certain level of this cannot be avoided in a
 collaborative effort, but the amount of it I'm seeing is frustrating.

I could say the same about people whining.

  Wrong. Policy 7.6 says it's an RC bug.
 
 Even if this was indeed the case, why should the package be kept from
 migrating to testing if the problem never affected testing?  That's my
 idea of course and only covered by common sense not by Policy.

We have suite-specific tags, which might have been used to reflect that,
but of course challenging the severity repeatedly was much more
interesting. I'm not throwing Adam's hat at you, but he's been handling
RC bugs for a long while now, you might have just trusted his judgement.

 In any case, 7.6 tells me how to get out of the hole (D'uh!) I had dug
 for myself. Nowhere does it say that the hole I dug is RC. Furthermore,
 grave severity implies either of the following three
 
 * data loss - obviously not
 * security hole - obviously not
 * makes package unusable - that's why normally this would be RC but it
   does not apply to this particular ticket, 656204 is a bit special

No it is not special. You claim it is.

 I've also looked into whether this ticket is critical or serious and
 came to the conclusion it isn't.  You and Adam were the ones to set it
 to grave, so you must have had one of the three reasons above.
 
 If you really look at it (as I have done) you will find it hard to
 justify the initial reflex of RC bug and most definitely of grave
 status.  This came a bit as a surprise to me as well.

Please look again.

(Oh and if you want Adam to look at it again, maybe you should be Ccing
him.)

 Apparently, the package already migrated to testing, so this is merely
 an opportunity for me to learn more about policy now.

Thank you so much for playing bug severity ping pong.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#653630: /sbin/mount.nfs: Re: nfs-common: Only root can unmount, nautilus badly confused

2012-01-22 Thread கா . சேது | කා . සේතු | K . Sethu



There was two problems after update, but the first one (umount: 
/mnt/library mount disagrees with the fstab) can be easily solved by 
the trailing slash. The reason why I mentioned it here is that it may be 
useful to know that it came along with the main unsolved problem with 
the user option (umount: only root can unmount liveserv:/mnt/library/ 
from /mnt/library). So the problem is related to user option.


On 2012-01-22 15:55, Michael Biebl wrote:

On 22.01.2012 12:30, Luk Claes wrote:

-- /etc/fstab --
liveserv:/mnt/library/mnt/library   nfs noauto,user   0 0
-- /proc/mounts --
liveserv:/mnt/library/ /mnt/library nfs 
rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.104,mountvers=3,mountport=46570,mountproto=udp,local_lock=none,addr=192.168.1.104
 0 0


I am missing a bit of context here. Is the problem related to the user
option or regarding a trailing /?

wrt /etc/mtab being a symlink to /proc/mounts: I assume mount.nfs is
built against libmount, seeing [1] as fixed? Do you get a file
/run/mount/utab when the nfs share is mounted? What does it contain?



[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626478




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

Bug#656212: xrdp: unowned files after purge (policy 6.8, 10.8)

2012-01-22 Thread Vincent Bernat

OoO  En ce début  d'après-midi nuageux  du mardi  17 janvier  2012, vers
14:48, Andreas Beckmann deb...@abeckmann.de disait :

 during a test with piuparts I noticed your package left unowned files on
 the system after purge, which is a violation of policy 6.8 (or 10.8):

 http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

 Filing this as important as having a piuparts clean archive is a release
 goal since lenny.

 From the attached log (scroll to the bottom...):

 0m19.6s ERROR: FAIL: Package purging left files on system:
   /var/log/sesman.log not owned

OK for this one.

 During a test with piuparts I noticed your package failed to purge due to a
 command not found. According to policy 7.2 you cannot rely on the depends
 being available during purge, only the essential packages are available for
 sure.

 Filing this as important because a.) it's a clear policy violation (to not
 clean up at purge) b.) having a piuparts clean archive is a release goal
 since lenny and c.) this package being piuparts buggy blocks packages
 depending on it from being tested by piuparts (and thus possibly the
 detection of more severe problems).

 From the attached log (scroll to the bottom...):

 The fix should be easy: your package is using adduser or deluser from the
 adduser package, which is only priority important. Using useradd or userdel
 from the passwd package should fix this problem.

   Removing xrdp ...
   Purging configuration files for xrdp ...
   /var/lib/dpkg/info/xrdp.postrm: 18: /var/lib/dpkg/info/xrdp.postrm: 
 deluser: not found
   /var/lib/dpkg/info/xrdp.postrm: 19: /var/lib/dpkg/info/xrdp.postrm: 
 delgroup: not found

Not OK  for this  one. deluser and  delgroup provides the  --system flag
that ensure that the group or user  is deleted only if it was created as
a system group or user.

For example,  a user install xrdp  with a user  xrdp already existing.
It then purges  the package.  The user xrdp should  not be removed. This
is not something easily achieved with userdel and groupdel.

I am fixing the first part. If you want to keep the second issue, I will
clone this bug.
-- 
Vincent Bernat ☯ http://vincent.bernat.im

Identify bad input; recover if possible.
- The Elements of Programming Style (Kernighan  Plauger)


pgpKQmpq5E8KD.pgp
Description: PGP signature

Bug#656210: xrdp: Create files with predictable name in /tmp/?

2012-01-22 Thread Vincent Bernat

OoO  En ce début  d'après-midi nuageux  du mardi  17 janvier  2012, vers
14:43, Petter Reinholdtsen p...@hungry.com disait :

 Package: xrdp
 Version: 0.5.0~20100303cvs-6
 Tags: security
 Severity: important
 User: debian-...@lists.debian.org
 Usertags: debian-edu

 I discovered this on Debian Edu/Squeeze, and it made me wonder if there
 is some security risk involved here.

 When starting xrdp, the following files are created in /tmp/:

   srwxr-xr-x 1 xrdp xrdp 0 16 jan.  09:49 
 /tmp/xrdp_07ba_listen_pro_done_event
   srwxr-xr-x 1 xrdp xrdp 0 16 jan.  09:49 /tmp/xrdp_07ba_main_sync
   srwxr-xr-x 1 xrdp xrdp 0 16 jan.  09:49 /tmp/xrdp_07ba_main_term
   srwxr-xr-x 1 root root 0 16 jan.  09:49 /tmp/xrdp_sesman_07cc_main_sync
   srwxr-xr-x 1 root root 0 16 jan.  09:49 /tmp/xrdp_sesman_07cc_main_term

 The file names seem to be predictable, and unless much care is taken
 when the files are created, this could be a security risk.  Is this a
 security issue, or is it harmless?

The issue  is harmless.  It is not  possible to exploit  symlink attacks
with  Unix sockets. You'll  get a  Address already  in use  error when
trying to do so.  Also, I am unsure if the names  matter. For example, a
predictable name could be used to allow unrelated processes to find each
other. Looking at the source code, this does not seem the case.

 In any case, it would be nice if these sockets could be moved elsewhere,
 either into a subdirectory like /tmp/xrdp/ or into /var/run/.  I assume
 they should not be automatically cleaned out by the jobs that might
 remove old files from /tmp/ from time to time.

Yes, in  /run/xrdp. I am making a  patch for this. This  will also solve
the security issue (since it could be possible to a DoS attack).
-- 
Vincent Bernat ☯ http://vincent.bernat.im

Make sure special cases are truly special.
- The Elements of Programming Style (Kernighan  Plauger)


pgp5krBcIful2.pgp
Description: PGP signature

Bug#653630: /sbin/mount.nfs: Re: nfs-common: Only root can unmount, nautilus badly confused

2012-01-22 Thread Roger Leigh

On Sun, Jan 22, 2012 at 12:55:45PM +0100, Michael Biebl wrote:
 On 22.01.2012 12:30, Luk Claes wrote:
  -- /etc/fstab --
  liveserv:/mnt/library/mnt/library   nfs noauto,user
 0 0 
  -- /proc/mounts --
  liveserv:/mnt/library/ /mnt/library nfs 
  rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.104,mountvers=3,mountport=46570,mountproto=udp,local_lock=none,addr=192.168.1.104
   0 0
 
 I am missing a bit of context here. Is the problem related to the user
 option or regarding a trailing /?
 
 wrt /etc/mtab being a symlink to /proc/mounts: I assume mount.nfs is
 built against libmount, seeing [1] as fixed? Do you get a file
 /run/mount/utab when the nfs share is mounted? What does it contain?

I'm afraid I can't help with the specifics immediately (I'll need
to set up some NFS mounts), but some general comments about the
recent changes:

- if you mount a filesystem with the user option, the user who
  mounted it will be written to /run/mount/utab.  While I've not
  tested this for NFS, it's certainly the case for all other mounts.

- when umounting a filesystem, the content of /etc/fstab should be
  irrelevant.  The information needed is in /etc/mtab (/proc/mounts)
  and /run/mount/utab.  If the NFS mount helpers are using fstab
  during umount, I think that's a separate bug in its own right.

- the trailing / may be an issue.  Does the entry (if any) in
  /run/mount/utab match this?  Does adding a trailing / to the
  umount command affect things?

Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?   http://gutenprint.sourceforge.net/
   `-GPG Public Key: 0x25BFB848   Please GPG sign your mail.



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

Bug#650258: 2nd status ping on ,,dhcpHost not removed if system is removed''

2012-01-22 Thread Cajus Pollmeier

Am Sonntag, 22. Januar 2012, 00:36:27 schrieben Sie:
 Hi Cajus,
 
 this is a second status ping on the ,,dhcpHost not removed if system
 is removed'' issue with GOsa² in Debian sid and squeeze.
 
 To be able to upload a fix for this to Debian squeeze this bug has to
 be fixed in Debian sid.
 
 The Debian Edu team is really desperate for this fix to be introduced
 into Debian squeeze.
 
 If you need any help with this, please let me/us know.
 
 Thanks!!!
 Mike

Sorry for the delay, Mike. We've already prepared a new release with a couple 
of fixes including this one. Will be uploaded on monday. Promised! ;-)

Cheers,
Cajus


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

Bug#652934: please rebase your patches

2012-01-22 Thread Holger Levsen

tags 652934 - patch
thanks

Hi Dave,

please rebase feature/package-master-slave on 0.43, or rather the current 
piuparts.git.

piuparts.git has branch piatti.git, which contains just that.

so:

git checkout develop
git branch new_branch
git checkout new_branch
git merge piatti.git

and then add your patches.

I just added this to debian/changelog:

piuparts (0.44) UNRELEASED; urgency=low

  * continue development.
  * One of the first steps should be the merge of the branch piatti.git into
the develop branch of piuparts.git, followed by the removal of the git
repository piatti.git.
I'merely not doing this right now, because I don't want to fix the
breakage now, or IOW, because I want to continue to be able to fixup
piatti.debian.org quickly.


cheers,
Holger




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

Bug#589863: rrdtool resize: ERROR: attempting to write beyond end of file

2012-01-22 Thread Christoph Biedl

tag 589863 fixed-upstream
thanks

 When I try to resize my rrd databases I get the following error message:
 
   ERROR: attempting to write beyond end of file

As far as I can see this has been fixed in upstream release 1.4.6,
commit is http://oss.oetiker.ch/rrdtool-trac/changeset/2192.

By the way, thanks for the reproducer.

Christoph


signature.asc
Description: Digital signature

Bug#656854: usb-modeswitch throws general protection error and umts modem is unusable

2012-01-22 Thread Joaquim Boura

Package: usb-modeswitch
Version: 1.2.2+repack0-1
Severity: important

Dear Maintainer,

after plug.in the usb device ( tried with different ones) no tty is found. An 
error message is thrown to /var/log/messages  and the umts modem is unusable

[  104.068068] usb 1-6: new high-speed USB device number 6 using ehci_hcd
[  104.184440] usb 1-6: New USB device found, idVendor=12d1, idProduct=1446
[  104.184448] usb 1-6: New USB device strings: Mfr=3, Product=2, SerialNumber=0
[  104.184454] usb 1-6: Product: HUAWEI Mobile
[  104.184458] usb 1-6: Manufacturer: HUAWEI Technology
[  104.186577] scsi7 : usb-storage 1-6:1.0
[  104.187020] scsi8 : usb-storage 1-6:1.1
[  104.289129] usb_modeswitch_[2176] general protection ip:7f9f2f2dd038 
sp:7fffd014ec40 error:0 in libc-2.13.so[7f9f2f299000+17a000]
[  105.188240] scsi 7:0:0:0: CD-ROMHUAWEI   Mass Storage 2.31 
PQ: 0 ANSI: 2
[  105.188863] scsi 8:0:0:0: Direct-Access HUAWEI   SD Storage   2.31 
PQ: 0 ANSI: 2
[  105.192201] sr1: scsi-1 drive
[  105.192457] sr 7:0:0:0: Attached scsi CD-ROM sr1
[  105.196202] sd 8:0:0:0: [sdc] Attached SCSI removable disk


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

Kernel: Linux 3.2-1.slh.3-aptosid-amd64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages usb-modeswitch depends on:
ii  dpkg 1.16.1.2
ii  libc62.13-24
ii  libjim0debian2   0.73-1
ii  libusb-0.1-4 2:0.1.12-20
ii  usb-modeswitch-data  20111023-1

usb-modeswitch recommends no packages.

Versions of packages usb-modeswitch suggests:
ii  comgt   none
ii  wvdial  1.61-4

-- 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#651768: Further Comments : bug for sans-serif not solved yet?

I have now tested with ttf-indic-fonts_0.5.13 installed to my Debian
Testing (Wheezy) desktop.

Of the two types of bugs I raised as issues, I have found the following:

1) the type two - i.e. selection for Serif for some languages dominating
all languages, is fully solved.

i2) But the first type of bug, i.e. selection for sans-serif is not solved
and is continuing based on my testing with the following 3 cases:

i. Tamil - if TSCu_Paranar (regular and/or bold) is installed then that is
matched to Sans-Serif still and not to Lohit Tamil as 90-ttf-tamil.conf
ii. Punjabi - 90-ttf-punjabi.conf prescribes Saab for Sans-Serif but the
match taking place is to Lohit Punjabi though Saab is installed
iii. Oriya - 90-ttf-punjabi.conf prescribes utkal for Sans-Serif but the
match taking place is to Lohit Oriya though utkal is installed

I haven't tested for other languages yet.

But from the above three samples, we can see that the 90-*.conf files
including the fixes for this bug, are still not effective for what they are
supposed to do for the matching for Sans-Serif!

K. Sethu

Bug#653630: /sbin/mount.nfs: Re: nfs-common: Only root can unmount, nautilus badly confused

2012-01-22 Thread Roger Leigh

On Sun, Jan 22, 2012 at 12:34:39PM +, Roger Leigh wrote:
 On Sun, Jan 22, 2012 at 12:55:45PM +0100, Michael Biebl wrote:
  On 22.01.2012 12:30, Luk Claes wrote:
   -- /etc/fstab --
   liveserv:/mnt/library/mnt/library   nfs noauto,user  
0 0 
   -- /proc/mounts --
   liveserv:/mnt/library/ /mnt/library nfs 
   rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.104,mountvers=3,mountport=46570,mountproto=udp,local_lock=none,addr=192.168.1.104
0 0
  
  I am missing a bit of context here. Is the problem related to the user
  option or regarding a trailing /?
  
  wrt /etc/mtab being a symlink to /proc/mounts: I assume mount.nfs is
  built against libmount, seeing [1] as fixed? Do you get a file
  /run/mount/utab when the nfs share is mounted? What does it contain?
 
 I'm afraid I can't help with the specifics immediately (I'll need
 to set up some NFS mounts), but some general comments about the
 recent changes:
 
 - if you mount a filesystem with the user option, the user who
   mounted it will be written to /run/mount/utab.  While I've not
   tested this for NFS, it's certainly the case for all other mounts.

A quick test with NFS4 showed that /run/mount/utab does not contain
anything, and additionally it looks like mount.nfs4 is /not/ linked
against libmount, which I thought (perhaps mistakenly, unless it's
a regression) was now using libmount.

NFS certainly does support libmount, it's right there in the
configure script.  Looks like it just needs adding to the Build-Deps
and enabling in debian/rules by configuring with
--enable-libmount-mount.  I would highly recommend that the nfs-common
enable this as soon as possible!


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?   http://gutenprint.sourceforge.net/
   `-GPG Public Key: 0x25BFB848   Please GPG sign your mail.



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

Bug#653630: /sbin/mount.nfs: Re: nfs-common: Only root can unmount, nautilus badly confused

2012-01-22 Thread கா . சேது | කා . සේතු | K . Sethu



I've tried:

- /run/mount/utab is empty even when my NFS share is mounted by user.
- corresponding entry in /etc/mtab is liveserv:/mnt/library/ 
/mnt/library nfs 
rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.104,mountvers=3,mountport=46570,mountproto=udp,local_lock=none,addr=192.168.1.104 
0 0 and it's indifferent to the trailing slash in /etc/fstab. But if 
there is no trailing slash in the fstab, another error message accurs 
umount: /mnt/library mount disagrees with the fstab (in this  case 
fstab and mtab entries are different).




- if you mount a filesystem with the user option, the user who
   mounted it will be written to /run/mount/utab.  While I've not
   tested this for NFS, it's certainly the case for all other mounts.

- when umounting a filesystem, the content of /etc/fstab should be
   irrelevant.  The information needed is in /etc/mtab (/proc/mounts)
   and /run/mount/utab.  If the NFS mount helpers are using fstab
   during umount, I think that's a separate bug in its own right.

- the trailing / may be an issue.  Does the entry (if any) in
   /run/mount/utab match this?  Does adding a trailing / to the
   umount command affect things?

Regards,
Roger





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

Bug#656605: (Fwd) [rt.cpan.org #74192] libnetaddr-ip-perl: ip-addr() should follow RFC5952 Section 2.2 (Zero Compression)

2012-01-22 Thread gregor herrmann

tag 656605 + upstream wontfix
thanks

- Forwarded message from Michael Robinton via RT 
bug-netaddr...@rt.cpan.org -

From: Michael Robinton via RT bug-netaddr...@rt.cpan.org
To: gre...@debian.org
Subject: [rt.cpan.org #74192] libnetaddr-ip-perl: ip-addr() should follow 
RFC5952 Section 2.2 (Zero Compression)
Date: Fri, 20 Jan 2012 18:16:05 -0500
Reply-To: bug-netaddr...@rt.cpan.org

URL: https://rt.cpan.org/Ticket/Display.html?id=74192 

The upper/lower case issue predates the RFC you refer to and its
immediate predecessors. When NetAddr::IP added support for IPV6, all the
rfc documentation showed addresses in UPPER case and did not specify a
preference for case. We opted to not change the standard way in which
NetAddr::IP does this so that we would not break anyone's existing code
that might be case sensitive. Instead, the pre-load directives :upper
and :lower were added so new code could use the newer rfc standard
notation if desired by simply including :lower in the 

use NetAdder::IP qw
  :lower
   whatever...
}

statement when invoking the NetAddr::IP module.

With respect to the section 2.2 compression. We consider this to be a
pretty text issue. In the sub module NetAddr::IP::InetBase, the
function packzeros will pretty up the text representation to conform
to 2.2 at the cost of many cpu cycles -- which is substantial beyond the
conversion of the binary IPV6 representation to text. For ordinary
processing of data, even in text form this is highly in-efficent so we
have not adopted compressed pretty text as a standard, opting instead
for quickly converted standard length strings. Programers wishing pretty
IPV6 strings at the expense of slower code can add the packzeros
function call to their programs that output text for human readers.

Best regards,
Michael

On Fri Jan 20 16:27:20 2012, GREGOA wrote:
 This bug has been forwarded from http://bugs.debian.org/656605

[..]

- End forwarded message -

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT  SPI, fellow of the Free Software Foundation Europe
   `-   NP: Eagles

signature.asc
Description: Digital signature

Bug#656855: backintime-common: Version number is 1.0.7 though the package claimes to be 1.0.8-1

2012-01-22 Thread 399man

Package: backintime-common
Version: 1.0.8-1
Severity: normal

Dear maintainer,

The version number of backintime is wrong.

Apt tells me this :

$ apt-cache showpkg backintime-common
Package: backintime-common
Versions:
1.0.8-1 (/var/lib/apt/lists/ftp.ch.debian.org_debian_dists_testing_main_binary-
amd64_Packages) (/var/lib/apt/lists/ftp.ch.debian
..org_debian_dists_unstable_main_binary-amd64_Packages)
(/var/lib/apt/lists/ftp.ch.debian.org_debian_dists_sid_main_binary-
amd64_Packages) (/var/lib/dpkg/status)
 Description Language: uk
 File: /var/lib/apt/lists/ftp.ch.debian
..org_debian_dists_testing_main_i18n_Translation-uk
  MD5: 54cf40bb197abf1b066486813bd7d134
 Description Language: it
 File: /var/lib/apt/lists/ftp.ch.debian
..org_debian_dists_testing_main_i18n_Translation-it
  MD5: 54cf40bb197abf1b066486813bd7d134
 Description Language: fr
 File: /var/lib/apt/lists/ftp.ch.debian
..org_debian_dists_testing_main_i18n_Translation-fr
  MD5: 54cf40bb197abf1b066486813bd7d134
 Description Language:
 File: /var/lib/apt/lists/ftp.ch.debian
..org_debian_dists_testing_main_binary-amd64_Packages
  MD5: 54cf40bb197abf1b066486813bd7d134

0.9.26-4 (/var/lib/apt/lists/ftp.ch.debian.org_debian_dists_stable_main_binary-
amd64_Packages)
 Description Language: uk
 File: /var/lib/apt/lists/ftp.ch.debian
..org_debian_dists_stable_main_i18n_Translation-uk
  MD5: 54cf40bb197abf1b066486813bd7d134
 Description Language: it
 File: /var/lib/apt/lists/ftp.ch.debian
..org_debian_dists_stable_main_i18n_Translation-it
  MD5: 54cf40bb197abf1b066486813bd7d134
 Description Language: fr
 File: /var/lib/apt/lists/ftp.ch.debian
..org_debian_dists_stable_main_i18n_Translation-fr
  MD5: 54cf40bb197abf1b066486813bd7d134
 Description Language:
 File: /var/lib/apt/lists/ftp.ch.debian
..org_debian_dists_stable_main_binary-amd64_Packages
  MD5: 54cf40bb197abf1b066486813bd7d134


Reverse Depends:
  backintime-kde,backintime-common 1.0.8-1
  backintime-gnome,backintime-common 1.0.8-1
  backintime-kde,backintime-common 0.9.26-4
  backintime-gnome,backintime-common 0.9.26-4
Dependencies:
1.0.8-1 - rsync (0 (null)) cron (0 (null)) python (2 2.6.6-7~)
0.9.26-4 - rsync (0 (null)) python (2 2.5) cron (0 (null)) python-support (2
0.90.0)
Provides:
1.0.8-1 -
0.9.26-4 -
Reverse Provides:

backintime binary tells me this :

$ backintime -v

Back In Time
Version: 1.0.7

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime --license' for details.




-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (900, 'testing-proposed-updates'), (850, 
'stable'), (700, 'unstable'), (500, 'proposed-updates'), (500, 'oldstable'), 
(400, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages backintime-common depends on:
ii  cron3.0pl1-120
ii  python  2.7.2-9
ii  rsync   3.0.9-1

backintime-common recommends no packages.

backintime-common 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#656856: base: Power button(hardware) deosnt shut the system after update

2012-01-22 Thread korek

Package: base
Severity: normal
Tags: upstream

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: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.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#651768: Further Comments : bug for sans-serif not solved yet?

A correction to my previous mail please:

2012/1/22 கா. சேது | කා. සේතු | K. Sethu skh...@gmail.com

 iii. Oriya - 90-ttf-punjabi.conf prescribes utkal for Sans-Serif but the
 match taking place is to Lohit Oriya though utkal is installed


90-ttf-punjabi.conf in above is wrong. Instead it should be Oriya -
90-ttf-oriya.conf 

K. Sethu

Bug#653630: /sbin/mount.nfs: Re: nfs-common: Only root can unmount, nautilus badly confused

2012-01-22 Thread Michael Biebl

 On Sun, Jan 22, 2012 at 12:55:45PM +0100, Michael Biebl wrote:

 I am missing a bit of context here. Is the problem related to the user
 option or regarding a trailing /?


The trailing / might be a red herring. I've tried the following:

as root
1/ mkdir /foo /bar
2/ echo /foo /bar none bind,user 0 0  /etc/fstab
as user
1/ mount /bar (successful)
2/ umount /bar
umount: /bar mount disagrees with the fstab
(umount as root works without problems)

When /bar is mounted, I get:

# cat /run/mount/utab
SRC=/dev/disk/by-uuid/5c503ec2-6528-44bb-9ff5-aa2687aa9706 TARGET=/bar 
ROOT=/foo BINDSRC=/foo OPTS=user=michael
(looks ok)

# findmnt /bar/
TARGET SOURCE   FSTYPE 
OPTIONS
/bar   /dev/disk/by-uuid/5c503ec2-6528-44bb-9ff5-aa2687aa9706[/foo] ext4   
rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered
(I'd expect the user option to be set)

# cat /proc/mounts | grep /bar
/dev/disk/by-uuid/5c503ec2-6528-44bb-9ff5-aa2687aa9706 /bar ext4 
rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered 0 0

When I do
as root
1/ rm /etc/mtab
2/ touch /etc/mtab
as user
1/ mount /bar
2/ mount
/foo on /bar type none (rw,noexec,nosuid,nodev,bind,user=michael)
3/ umount /bar

everything works as expected.

So it looks like something's fishy going on here

-- 
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#654523: Please implement source-contains-waf-binary tag

2012-01-22 Thread Luca Falavigna

It seems I omitted footnotes, here they are:

[0] http://code.google.com/p/waf/
[1] Yes, that phrase originates from the GPL, nevertheless Debian uses
it as definiton of source.
[2] http://wiki.debian.org/UnpackWaf



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

Bug#655629: smuxi-frontend-gnome: [INTL:pt] Updated Portuguese translation for debconf messages

2012-01-22 Thread Mirco Bauer


tags 655629 + pending
thanks

On 01/12/2012 10:25 PM, Traduz - Portuguese Translation Team wrote:

Package: smuxi-frontend-gnome
Version: n/a
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for smuxi-frontend-gnome's debconf 
messages.

Translator: Pedro Ribeiro p.m42.ribe...@gmail.com
Feel free to use it.

For translation updates please contact 'Last Translator' or the
Portuguese Translation Team traduz _at_ debianpt.org.




Applied to git:
http://git.qnetp.net/?p=smuxi.git;a=commitdiff;h=11ce23cbe19da1addd5647490088a294f4737cf9

Thank you very much for your contribution to Smuxi!

--
Regards,

Mirco 'meebey' Bauer

PGP-Key ID: 0xEEF946C8

FOSS Developermee...@meebey.net  http://www.meebey.net/
PEAR Developermee...@php.net http://pear.php.net/
Debian Developer  mee...@debian.org  http://www.debian.org/




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

Bug#655708: mudita24: meters don't work

2012-01-22 Thread Alessio Treglia

tags 655708 moreinfo
thanks

Hello Raffaele,

On Fri, Jan 13, 2012 at 2:54 PM, Raffaele Morelli
raffaele.more...@gmail.com wrote:
 you're welcome, feel free to ask if needed.

Few days ago I uploaded a new SVN snapshot, would you check if this
bug is still reproducible with the latest mudita24 1.0.3+svn13-2
available in sid?

Thanks in advance for any reply.

-- 
Alessio Treglia          | www.alessiotreglia.com
Debian Developer         | ales...@debian.org
Ubuntu Core Developer    | quadris...@ubuntu.com
0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A



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

Bug#656801: License short name should not be empty in DEP5 copyright file

2012-01-22 Thread Jakub Wilk


* Aron Xu happyaron...@gmail.com, 2012-01-22, 04:15:
License short name should not be empty in DEP5 copyright file, either 
in a single license paragraph or in a paragraph with other keys and 
values, for example the following situation should not exist:


License:
SOMETHING TRULY BRAIN DAMAGED

Instead, it should be like this:

License: whatever-shortname
SOMETHING TRULY BRAIN DAMAGED



Right. This is something that was allowed in early DEP-5 versions 
(around r135) and probably many people didn't notice that it's not 
permitted anymore when bumping format version. Definitely it's worth 
checking.


--
Jakub Wilk



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

Bug#656380: mangling fixes for ppc64

2012-01-22 Thread Hiroyuki Yamamoto


Hi,

(2012-01-22 22:20 +0100), Pino Toscano wrote:

Alle mercoledì 18 gennaio 2012, Pino Toscano ha scritto:

However, we need also to fix the information about symbols mangling
on ppc64 in our symbols helpers (part of pkg-kde-tools), so I've
cloned this bug for pkg-kde-tools; will followup on that bug further
(simple) instructions on how to provide them.


So, attached there is a small source, which you should compile (making
sure to have libqt4-dev installed):
$ g++ -Wno-long-long-g3 -O0 -DWITH_QT -I/usr/include/qt4 \
   -o manglingtest manglingtest.cpp
and then
$ readelf -a manglingtest | grep _type
please attach the output of this last readelf command.


Thanks.
Here is test result.
--
57: 100112e848 FUNCGLOBAL DEFAULT   24 _Z14f_int64_t_typel
58: 1001134848 FUNCGLOBAL DEFAULT   24 _Z12f_qreal_typed
63: 100112b848 FUNCGLOBAL DEFAULT   24 _Z13f_size_t_typem
66: 1001133048 FUNCGLOBAL DEFAULT   24 _Z15f_quintptr_typey
73: 1001131848 FUNCGLOBAL DEFAULT   24 _Z15f_qptrdiff_typex
74: 100112d048 FUNCGLOBAL DEFAULT   24 _Z14f_ssize_t_typel
77: 1001130048 FUNCGLOBAL DEFAULT   24 _Z15f_uint64_t_typem
--

Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA  91AC 3A10 59C6 5203 04DC
57: 100112e848 FUNCGLOBAL DEFAULT   24 _Z14f_int64_t_typel
58: 1001134848 FUNCGLOBAL DEFAULT   24 _Z12f_qreal_typed
63: 100112b848 FUNCGLOBAL DEFAULT   24 _Z13f_size_t_typem
66: 1001133048 FUNCGLOBAL DEFAULT   24 _Z15f_quintptr_typey
73: 1001131848 FUNCGLOBAL DEFAULT   24 _Z15f_qptrdiff_typex
74: 100112d048 FUNCGLOBAL DEFAULT   24 _Z14f_ssize_t_typel
77: 1001130048 FUNCGLOBAL DEFAULT   24 _Z15f_uint64_t_typem

Bug#656854: usb-modeswitch throws general protection error and umts modem is unusable

2012-01-22 Thread Josua Dietze


Am 22.01.2012 13:49, schrieb Joaquim Boura:

after plug.in the usb device ( tried with different ones) no tty is
found. An error message is thrown to /var/log/messages  and the umts
modem is unusable.


This is the same issue as bug #656688.

See
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656688

Josua Dietze



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

Bug#656755: Help with architecture not supporting SSE (Was: Bug#656755: libhmsbeagle FTBFS on everything except amd64)

2012-01-22 Thread Andreas Tille

Hi,

I have to admit that I do not have any experience with SSE issues.  Any
advise what to do in cases like this (see build logs linked below)?

The error message starts with

libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../libhmsbeagle 
-I/build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0 
-I/build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0 -O3 -c 
BeagleCPUSSEPlugin.cpp  -fPIC -DPIC -o 
.libs/libhmsbeagle_cpu_sse_la-BeagleCPUSSEPlugin.o
In file included from 
/build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/SSEDefinitions.h:37:0,
 from 
/build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/BeagleCPU4StateSSEImpl.hpp:44,
 from 
/build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/BeagleCPU4StateSSEImpl.h:240,
 from BeagleCPUSSEPlugin.cpp:9:
/usr/lib/gcc/i486-gnu/4.6/include/emmintrin.h:32:3: error: #error SSE2 
instruction set not enabled
In file included from 
/build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/SSEDefinitions.h:39:0,
 from 
/build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/BeagleCPU4StateSSEImpl.hpp:44,
 from 
/build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/BeagleCPU4StateSSEImpl.h:240,
 from BeagleCPUSSEPlugin.cpp:9:
/usr/lib/gcc/i486-gnu/4.6/include/xmmintrin.h:32:3: error: #error SSE 
instruction set not enabled
In file included from 
/build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/BeagleCPU4StateSSEImpl.hpp:44:0,
 from 
/build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/BeagleCPU4StateSSEImpl.h:240,
 from BeagleCPUSSEPlugin.cpp:9:
/build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/SSEDefinitions.h:52:10:
 error: '__m128d' does not name a type
/build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/SSEDefinitions.h:80:2:
 error: 'V_Real' does not name a type
In file included from 
/build/buildd-libhmsbeagle_1.0-3-hurd-i386-sfmc4g/libhmsbeagle-1.0/libhmsbeagle/CPU/BeagleCPU4StateSSEImpl.h:240:0,
 from BeagleCPUSSEPlugin.cpp:9:

Any help is welcome

 Andreas.

On Sat, Jan 21, 2012 at 09:50:16PM +, Adam D. Barratt wrote:
 On Sat, 2012-01-21 at 17:16 +0100, Andreas Tille wrote:
  On Sat, Jan 21, 2012 at 03:00:25PM +, peter green wrote:
   It seems things are a little more complex than they first  appeared.
   In particular it seems libhmsbeagle has a specific sse2 plugin
   which can only be built with sse2 enabled and that is built even if
   --enable-sse=no is passed (which seems like a bug in the upstream
   build system to me). Therefore disabling -msse2 has caused the
   package to FTBFS everywhere except amd64.
   
   For non pc architectures I would think the sse2 plugin should simply
   be disabled.
  
  Do you have any hint how I could find this plugin which should be
  disabled.
 [...]
  A failed build log would probably be helpful.  I also have included
  upstream whether they might be able to give any hint about this issue:
 
 Predictably, https://buildd.debian.org/status/package.php?p=libhmsbeagle
 has several - the hurd-i386, powerpc and s390x logs all look like they
 fail whilst building libhmsbeagle_cpu_sse_la-BeagleCPUSSEPlugin.lo.
 
 Regards,
 
 Adam
 
 

-- 
http://fam-tille.de



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

Bug#655708: mudita24: meters don't work

2012-01-22 Thread Raffaele Morelli

2012/1/22 Alessio Treglia ales...@debian.org

 tags 655708 moreinfo
 thanks

 Hello Raffaele,

 On Fri, Jan 13, 2012 at 2:54 PM, Raffaele Morelli
 raffaele.more...@gmail.com wrote:
  you're welcome, feel free to ask if needed.

 Few days ago I uploaded a new SVN snapshot, would you check if this
 bug is still reproducible with the latest mudita24 1.0.3+svn13-2
 available in sid?


Hello Alessio,

yes, the bug is still reproducible with svn13-2.

Ciao
-r

Bug#656857: Hardened build flags not fully enabled

Package: nas
Version: 1.9.3-2
Severity: important

Hi Steve,
thanks for enabling support for dpkg-buildflags in 1.9.3-2.
One bit of the default hardening flags for Wheezy is still
missing, though: read-only relocations:

root@pisco:~# hardening-check /usr/lib/x86_64-linux-gnu/libaudio.so.2
/usr/lib/x86_64-linux-gnu/libaudio.so.2:
(..)
 Read-only relocations: no, not found!

root@pisco:~# hardening-check /usr/bin/nasd
(..)
 Read-only relocations: no, not found!

The reason is apparently that the upstream Makefile has no support
for LDFLAGS. Instead you could probably use EXTRA_LDOPTIONS 
(untested)

Cheers,
Moritz



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

Bug#617543: dcraw: new upstream version

2012-01-22 Thread Christoph Anton Mitterer


9.12 is out :)

C.



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

Bug#656380: mangling fixes for ppc64

2012-01-22 Thread Pino Toscano

tag 656380 + pending
thanks

Alle domenica 22 gennaio 2012, Hiroyuki Yamamoto ha scritto:
 (2012-01-22 22:20 +0100), Pino Toscano wrote:
  Alle mercoledì 18 gennaio 2012, Pino Toscano ha scritto:
  However, we need also to fix the information about symbols
  mangling on ppc64 in our symbols helpers (part of pkg-kde-tools),
  so I've cloned this bug for pkg-kde-tools; will followup on that
  bug further (simple) instructions on how to provide them.
  
  So, attached there is a small source, which you should compile
  (making sure to have libqt4-dev installed):
  $ g++ -Wno-long-long-g3 -O0 -DWITH_QT -I/usr/include/qt4 \
  
 -o manglingtest manglingtest.cpp
  
  and then
  $ readelf -a manglingtest | grep _type
  please attach the output of this last readelf command.
 
 Thanks.
 Here is test result.

Thanks!

I've applied them to the pkg-kde-tools repo, so they will be part of the 
next (still unscheduled though) upload of pkg-kde-tools.

-- 
Pino Toscano


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

Bug#656858: libimage-exiftool-perl: new upstream version available

2012-01-22 Thread Christoph Anton Mitterer

Package: libimage-exiftool-perl
Version: 8.60-2
Severity: wishlist


Hi.

A far newer upstream version (8.76) would be available.


Cheers,
Chris.



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

Bug#656859: Please enabled hardened build flags

Package: pdns-recursor
Version: 3.3-2
Severity: important
Tags: patch

Please enabled hardened build flags

Please enable hardened build flags for your package. Since your
package has already been converted to dh, setting debian/compat
to 9 is all you need to do.

I've tested in a local build that this is sufficient to enable
hardened build flags.

Cheers,
Moritz
diff -aur pdns-recursor-3.3.harden/debian/compat pdns-recursor-3.3/debian/compat
--- pdns-recursor-3.3.harden/debian/compat	2010-11-06 11:29:26.0 +0100
+++ pdns-recursor-3.3/debian/compat	2012-01-21 19:07:15.0 +0100
@@ -1 +1 @@
-5
+9
Nur in pdns-recursor-3.3/debian: compat~.

Bug#651359: python-sphinx makes virtualenvwrapper FTBFS: unknown JavaScript code: debian/virtualenvwrapper/usr/share/doc/virtualenvwrapper/ja/html/_static/translations.js

2012-01-22 Thread Jakub Wilk


* Sandro Tosi mo...@debian.org, 2012-01-22, 01:34:

Right, it's only a warning about translations.js.

In theory we _could_ move translations to the libjs-* package and then 
symlink them too, but this is probably too much hassle for very little 
benefit.


if translates.js is the same for all the projects using sphinx then it 
probably makes sense to symlink it,


I believe that this is the case, yes. 

but it's also true that there's only one occurrence of translate.js in 
all debian packages, so probably we can also wait and see how the 
situation evolves.


Right, that's why I was reluctant to do this. Also, translations take a 
good amount of space:


$ du -sh /usr/share/javascript/{jquery,underscore,sphinxdoc} 
/usr/share/sphinx/locale
356K/usr/share/javascript/jquery
52K /usr/share/javascript/underscore
76K /usr/share/javascript/sphinxdoc
220K/usr/share/sphinx/locale

Well, maybe the way to go is to declare that dh_sphinxdoc doesn't 
support translated documentation (neither translations.js nor 
searchtools.js), possibly improve error messages, and then 
clonereassign the bug to virtualenvwrapper?


That'd mean that if we ever had to update Sphinx's javascript code e.g. 
because new version of jQuery broke it, we'd have to rebuild 
virtualenvwrapper, but that's not a big deal, since it's team-maintained 
(especially when you compare it to number of package that doesn't use 
dh_sphinxdoc at all...).


But it we decide that not symlinking translations.js is by design, 
then we should also silence the warning.


that too, or differentiate the warning and error messages (that are now 
the same, which could be a bit misleading).


Right. I fixed this in svn. Now it's:

$ dh_sphinxdoc
dh_sphinxdoc: ignoring unknown JavaScript code: 
debian/virtualenvwrapper/usr/share/doc/virtualenvwrapper/ja/html/_static/translations.js
dh_sphinxdoc: error: unknown JavaScript code: 
debian/virtualenvwrapper/usr/share/doc/virtualenvwrapper/ja/html/_static/searchtools.js

--
Jakub Wilk



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

Bug#656860: libcv2.3: /usr/include/opencv2/opencv.hpp missing

2012-01-22 Thread Markus Raab

Package: libcv2.3
Version: 2.3.1-4
Severity: normal

Dear Maintainer,

I was trying to compile a opencv program which needs opencv2/opencv.hpp

But neither installing libcv-dev nor recompiling (or backporting) the source 
package installs /usr/include/opencv2/opencv.hpp

During dpkg-buildpackage I saw the warning that
/home/markus/Downloads/src/opencv/opencv-2.3.1/debian/tmp/usr/include/opencv2/opencv.hpp
will not be included - so I assume that this is a packaging bug.

best regards
Markus


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.1.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=locale: Cannot set 
LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages libcv2.3 depends on:
ii  libopencv-calib3d2.3 2.3.1-4
ii  libopencv-core2.32.3.1-4
ii  libopencv-features2d2.3  2.3.1-4
ii  libopencv-flann2.3   2.3.1-4
ii  libopencv-imgproc2.3 2.3.1-4
ii  libopencv-legacy2.3  2.3.1-4
ii  libopencv-ml2.3  2.3.1-4
ii  libopencv-objdetect2.3   2.3.1-4
ii  libopencv-video2.3   2.3.1-4

libcv2.3 recommends no packages.

libcv2.3 suggests no packages.

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = de_AT.UTF-8
are supported and installed on your system.
perl: warning: Falling back to the standard locale (C).
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory



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

Bug#197254: messing around with stuff in /etc is grounds for RC status

2012-01-22 Thread Rolf Leggewie

severity 197254 serious
severity 331116 serious
tags 197254 help
tags 331116 help
thank you

the legacy maintainer scripts are unconditionally messing around in /etc
and they absolutely should not.  this is RC-level severity.  I plan to
replace the problematic code and manage the files in question with ucf,
but this is new to me and may take a bit of time.  Help as always welcome.



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

Bug#656857: Hardened build flags not fully enabled

2012-01-22 Thread Steve McIntyre

On Sun, Jan 22, 2012 at 02:41:31PM +0100, Moritz Muehlenhoff wrote:
Package: nas
Version: 1.9.3-2
Severity: important

Hi Steve,
thanks for enabling support for dpkg-buildflags in 1.9.3-2.
One bit of the default hardening flags for Wheezy is still
missing, though: read-only relocations:

root@pisco:~# hardening-check /usr/lib/x86_64-linux-gnu/libaudio.so.2
/usr/lib/x86_64-linux-gnu/libaudio.so.2:
(..)
 Read-only relocations: no, not found!

root@pisco:~# hardening-check /usr/bin/nasd
(..)
 Read-only relocations: no, not found!

Ah, OK. Didn't know about the hardening-check test program... :-)

The reason is apparently that the upstream Makefile has no support
for LDFLAGS. Instead you could probably use EXTRA_LDOPTIONS 
(untested)

Looking now.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
There's no sensation to compare with this
Suspended animation, A state of bliss




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

Bug#656861: Please enabled hardened build flags

Source: pdns
Severity: important
Tags: patch

Please enabled hardened build flags through dpkg-buildflags.

Patch attached.

Cheers,
Moritz
diff -aur pdns-3.0.harden/debian/rules pdns-3.0/debian/rules
--- pdns-3.0.harden/debian/rules	2011-11-06 23:04:05.0 +0100
+++ pdns-3.0/debian/rules	2012-01-21 19:08:16.0 +0100
@@ -14,7 +14,7 @@
 	./bootstrap
 	
 	# Add here commands to configure the package.
-	CFLAGS=$(CFLAGS) CXXFLAGS=$(CXXFLAGS) ./configure \
+	./configure $(shell dpkg-buildflags --export=configure) \
 		--host=$(DEB_HOST_GNU_TYPE) \
 		--build=$(DEB_BUILD_GNU_TYPE) \
 		--prefix=/usr \
Nur in pdns-3.0/debian: rules~.

Bug#656862: Please enabled hardened build flags

Source: vnc4
Severity: important
Tags: patch

Please enabled hardened build flags through dpkg-buildflags.

Patch attached. (dpkg-buildflags abides noopt from DEB_BUILD_OPTIONS)

Cheers,
Moritz
diff -aur vnc4-4.1.1+X4.3.0.harden/debian/rules vnc4-4.1.1+X4.3.0/debian/rules
--- vnc4-4.1.1+X4.3.0.harden/debian/rules	2012-01-21 18:54:33.0 +0100
+++ vnc4-4.1.1+X4.3.0/debian/rules	2012-01-21 18:56:29.0 +0100
@@ -16,24 +16,19 @@
 # This has to be exported to make some magic below work.
 export DH_OPTIONS
 
-
-
-CFLAGS = -Wall -g
-CXXFLAGS = -Wall -g
-
-ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
-	CFLAGS += -O0
-	CXXFLAGS += -O0
-else
-	CFLAGS += -O2
-endif
+CFLAGS = `dpkg-buildflags --get CFLAGS`
+CFLAGS += -Wall
+CXXFLAGS = `dpkg-buildflags --get CXXFLAGS`
+CXXFLAGS += -Wall
+LDFLAGS = `dpkg-buildflags --get LDFLAGS`
+CPPFLAGS = `dpkg-buildflags --get CPPFLAGS`
 
 configure: configure-unix-stamp configure-common-stamp
 
 configure-common-stamp:
 	dh_testdir
 	# Add here commands to configure the package.
-	(cd common; CFLAGS=$(CFLAGS) CXXFLAGS=$(CXXFLAGS) ./configure \
+	(cd common; CFLAGS=$(CFLAGS) CXXFLAGS=$(CXXFLAGS) CPPFLAGS=$(CPPFLAGS) LDFLAGS=$(LDFLAGS) ./configure \
 		--host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) \
 		--prefix=/usr --mandir=\$${prefix}/share/man \
 		--infodir=\$${prefix}/share/info \
@@ -43,7 +38,7 @@
 configure-unix-stamp:
 	dh_testdir
 	# Add here commands to configure the package.
-	(cd unix; CFLAGS=$(CFLAGS) CXXFLAGS=$(CXXFLAGS) ./configure \
+	(cd unix; CFLAGS=$(CFLAGS) CXXFLAGS=$(CXXFLAGS) CPPFLAGS=$(CPPFLAGS) LDFLAGS=$(LDFLAGS) ./configure \
 		--host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) \
 		--prefix=/usr --mandir=\$${prefix}/share/man \
 		--infodir=\$${prefix}/share/info \
Nur in vnc4-4.1.1+X4.3.0/debian: rules~.

Bug#656863: liblightdm: lightdm.conf's xsessions-directory is ignored

2012-01-22 Thread Yair Yarom

Package: lightdm
Version: 1.0.6-3
Severity: normal

Dear Maintainer,

liblightdm is opening a hardcoded XSESSIONS_DIR as the xsessions
directory instead of reading lightdm.conf first (both qt and
gobject). As such the xsessions-directory configuration option is
ignored by the greeters.

Yair.

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

Kernel: Linux 3.2.1-aufs-2 (SMP w/6 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages lightdm depends on:
ii  adduser3.113
ii  consolekit 0.4.5-1
ii  dbus   1.4.16-1
ii  debconf [debconf-2.0]  1.5.41
ii  libc6  2.13-21
ii  libglib2.0-0   2.30.2-4
ii  libpam0g   1.1.3-6
ii  libxcb11.7-4
ii  libxdmcp6  1:1.1.0-4
ii  lightdm-gtk-greeter1.0.6-3
ii  lightdm-qt-greeter 1.0.6-3

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.6+8

Versions of packages lightdm suggests:
ii  accountsservice  0.6.15-2

-- Configuration Files:
/etc/lightdm/lightdm.conf changed [not included]
/etc/pam.d/lightdm changed [not included]

-- debconf information:
  lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm



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

Bug#656864: bzr-svn: Bazaar cannot pull from Subversion repository

2012-01-22 Thread Russel Winder

Package: bzr-svn
Version: 1.1.2-1
Severity: important

Dear Maintainer,

I have some pre-existing Bazaar branches branched from a Subversion repository. 
  Recently (not sure how
recently) pull has stopped working giving error messages such as:

  Using saved parent location: 
svn+https://webdav.seas.upenn.edu/svn/unison/trunk
  bzr: ERROR: Not a branch: 
svn+https://webdav.seas.upenn.edu/svn/unison/trunk/branches;.  

This means that Bazaar is now not usable for this purpose

I checked ont he Bazaar mailing list and am told that:

  This is a compatibility issue between bzr-svn and prereleases of bzr. 
  This list is not the appropriate place for Debian bug reports, please 
  file a bug against the bzr-svn package in Debian.

So there must be an inconsistent collection of packages in Debian Unstable as I 
only use packages from the
repository for Bazaar.


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

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

Versions of packages bzr-svn depends on:
ii  python2.7.2-9
ii  python-bzrlib 2.5.0~beta5-2
ii  python-subvertpy  0.8.9-1
ii  python2.6 2.6.7-4
ii  python2.7 2.7.2-13

Versions of packages bzr-svn recommends:
ii  bzr 2.5.0~beta5-2
ii  python-tdb  1.2.9-4+b1
ii  python-xdg  0.19-3

Versions of packages bzr-svn suggests:
ii  bzr-rewrite  0.6.2+bzr238-1

-- no debconf information



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

Bug#532227: rsync seems unable to transfer 4Gb of data

2012-01-22 Thread Maximiliano Curia

Hi,

Regarding the bug report made to the rsync package in the Jun 7th of 2009
http://bugs.debian.org/532227
 Running rsync -avHX /foo /bar, where /foo contains several hundred Gb of
 data, (and a lot of hard links) I eventually get:

 rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32)
 rsync: connection unexpectedly closed (429796854 bytes received so far)
 [sender]
 rsync error: error in rsync protocol data stream (code 12) at io.c(635)
 [sender=3.0.3]

 This is on a 32-bit system, where the source file system is reiserfs and
 the destination file system ext3. I'm surprised that I don't seem to
 find anything about this problem by searching (I only see mentions of
 limits on individual file size).

The error message claims that 429796854 bytes were transmited, which is about
410M. This issue doesn't seem to be related a 4G limit. I think the problem is
related to a filesystem error that ends up in a read error.

Anyway, can you still reproduce this issue?

How many files are you trying to rsync?

What's the filesize of the larger file?

If you copy the data to another filesystem (preferably an ext3 one), would the
rsync succeed? (say, something like cp -ax /foo /tmp; rsync -avHX /tmp/foo /bar)

Thanks,
-- 
We must be very careful when we give advice to younger people: sometimes they
follow it!
-- Edsger W. Dijkstra
Saludos /\/\ /\  `/


signature.asc
Description: Digital signature

Bug#631117: Ping - apply simple patch for Wheezy?

Hello Muttprint-maintainer,
I just wanted to inquire about the status of this bug. Do you think it
is possible to apply this simple patch for Wheezy?

Thanks for maintaining Muttprint.

Greetings

Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software libre: http://www.ffii.de/


signature.asc
Description: Digital signature

Bug#656865: apt-get update crashes

2012-01-22 Thread Philipp Klaus Krause

Package: apt
Version: 0.8.15.9
Severity: important

For me apt-get update fails most of time:

 apt-get update
Hit http://ftp.de.debian.org unstable InRelease
Hit http://ftp.de.debian.org experimental InRelease
Hit http://ftp.de.debian.org unstable/main Sources/DiffIndex
Hit http://ftp.de.debian.org unstable/main amd64 Packages/DiffIndex
Hit http://ftp.de.debian.org unstable/contrib amd64 Packages/DiffIndex
Hit http://ftp.de.debian.org unstable/non-free amd64 Packages/DiffIndex
Ign http://ftp.de.debian.org unstable/contrib TranslationIndex
Hit http://ftp.de.debian.org unstable/main TranslationIndex
Ign http://ftp.de.debian.org unstable/non-free TranslationIndex
Hit http://ftp.de.debian.org experimental/main Sources/DiffIndex
Hit http://ftp.de.debian.org experimental/main amd64 Packages/DiffIndex
Ign http://ftp.de.debian.org experimental/main TranslationIndex
Get:1 http://ftp.de.debian.org unstable/main 2012-01-21-0227.10.pdiff
[22.4 kB]
Get:2 http://ftp.de.debian.org unstable/main amd64
2012-01-21-0227.10.pdiff [30.3 kB]
Get:3 http://ftp.de.debian.org unstable/main 2012-01-21-0227.10.pdiff
[22.4 kB]
E: Method rred has died unexpectedly!
E: Sub-process rred received a segmentation fault.

The problem seems to depend on the downloaded data: I get this problem
most of the time, but not always; but when the problem is there, just
doing another apt-get update immediately will certainly fail, and if it
isn't there, doing another apt-get update immediately will certainly
work. Doing an apt-get clean doesn't help:

 apt-get clean
 apt-get update
Hit http://ftp.de.debian.org unstable InRelease
Hit http://ftp.de.debian.org experimental InRelease
Hit http://ftp.de.debian.org unstable/main Sources/DiffIndex
Hit http://ftp.de.debian.org unstable/main amd64 Packages/DiffIndex
Hit http://ftp.de.debian.org unstable/contrib amd64 Packages/DiffIndex
Hit http://ftp.de.debian.org unstable/non-free amd64 Packages/DiffIndex
Ign http://ftp.de.debian.org unstable/contrib TranslationIndex
Hit http://ftp.de.debian.org unstable/main TranslationIndex
Ign http://ftp.de.debian.org unstable/non-free TranslationIndex
Hit http://ftp.de.debian.org experimental/main Sources/DiffIndex
Hit http://ftp.de.debian.org experimental/main amd64 Packages/DiffIndex
Ign http://ftp.de.debian.org experimental/main TranslationIndex
Get:1 http://ftp.de.debian.org unstable/main 2012-01-21-0227.10.pdiff
[22.4 kB]
Get:2 http://ftp.de.debian.org unstable/main amd64
2012-01-21-0227.10.pdiff [30.3 kB]
Get:3 http://ftp.de.debian.org unstable/main 2012-01-21-0227.10.pdiff
[22.4 kB]
E: Method rred has died unexpectedly!
E: Sub-process rred received a segmentation fault.

I mostly use unstable with a few packages from experimental.

Philipp

P.S.: Some versions of other packages on my system:
dpkg: 1.16.1.2
debian-archive-keyring: 2010.08.28
libc6: 2.13-24
gnupg: 1.4.11-3
libgcc1: 1:4.6.2-12
libstdc++6: 4.6.2-12



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

Bug#610882: Ping - severity of these messages?

Hello, 
a year ago I reported about unclear syslog messages from gpm. Could
you clarify if they are harmless (and provide a logcheck snippet to
hide them) or if they are serious and hence should be dealt with by an
administrator?

Thanks!

Greetings

   Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software libre: http://www.ffii.de/


signature.asc
Description: Digital signature

Bug#634882: Now iptables-xml.8 is missing completely

Hello,
in 1.4.12.2-1 the man page iptables-xml.8 has gone completly. Is this
intended?

Technically this would close the bug, though.

Greetings

 Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software libre: http://www.ffii.de/


signature.asc
Description: Digital signature

Bug#624273: /usr/share/mdadm/checkarray should check creation date

2012-01-22 Thread Sergey B Kirpichev

tag 624273 +patch
thanks

A simple patch attached.
From 25f0fd586192ec2567344a5beceb16d2f8ef7959 Mon Sep 17 00:00:00 2001
From: Sergey B Kirpichev skirpic...@gmail.com
Date: Sun, 22 Jan 2012 18:38:30 +0400
Subject: [PATCH] Cancel check for recently created arrays

---
 debian/checkarray |7 +++
 1 files changed, 7 insertions(+), 0 deletions(-)

diff --git a/debian/checkarray b/debian/checkarray
index 2043d8c..929109c 100644
--- a/debian/checkarray
+++ b/debian/checkarray
@@ -175,6 +175,13 @@ for array in $arrays; do
 continue
   fi
 
+  creation_date=$(mdadm --detail /dev/$array|sed -n 's/.*Creation Time : \(.*\)/\1/p')
+  if [ $(date +%s -d $creation_date + 2 weeks) -gt $(date +%s) ]
+  then
+[ $quiet -lt 1 ]  echo $PROGNAME: I: check for array $array canceled due to recent creation date 2
+continue
+  fi
+
   # queue request for the array. The kernel will make sure that these requests
   # are properly queued so as to not kill one of the array.
   echo $action  $MDBASE/sync_action
-- 
1.7.2.5

Bug#656564: libglib2.0-0: since upgrade to 2.30.2-5 programs start segfaulting at random

2012-01-22 Thread Norbert Preining

Hi Michael,

On Fr, 20 Jan 2012, Michael Biebl wrote:
 - Revert this commit and recompile glib2.0 to see if it fixes the crashes

THis is what I did, I disabled 
  94-closure-fix-handling-of-ENUMs-and-integral-return-ty.patch
recompiled and installed, but g-s-d still has the tendency to
die on me.

Anything else?

 - Install libglib2.0-0-dbg and libffi5-dbg and get a backtrace or a core
 dump. For the latter you'll probably need to adjust ulimit.

Where should I do that in the gnome-session path? /etc/profile?

Best wishes

Norbert

Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live  Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094

Far out in the uncharted backwaters of the unfashionable
end of the western spiral arm of the Galaxy lies a small
unregarded yellow sun.
 --- Douglas Adams, The Hitchhikers Guide to the Galaxy



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

Bug#656866: Please enabled hardened build flags

Package: icinga
Version: 1.6.1-2
Severity: important
Tags: patch

Please enabled hardened build flags through dpkg-buildflags.

Patch attached. (dpkg-buildflags abides noopt from DEB_BUILD_OPTIONS)

Cheers,
Moritz
--- icinga-1.6.1.harden/debian/rules	2012-01-22 15:35:01.0 +0100
+++ icinga-1.6.1/debian/rules	2012-01-22 15:43:29.0 +0100
@@ -8,17 +8,12 @@
 export DEB_HOST_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
 export DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
 
-# -Wall disabled until source is fixed to not print tons of warnings with it. :)
-#CFLAGS = -Wall -g
-CFLAGS = -g
-ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
-CFLAGS += -O0
-else
-CFLAGS += -O2
-endif
+CFLAGS = `dpkg-buildflags --get CFLAGS`
+CFLAGS += `dpkg-buildflags --get CPPFLAGS`
+LDFLAGS = `dpkg-buildflags --get LDFLAGS`
 
 SHELL		= /bin/sh -e
-CONFIGURE	= CFLAGS='$(CFLAGS)' ./configure --prefix=/usr \
+CONFIGURE	= CFLAGS=$(CFLAGS) LDFLAGS=$(LDFLAGS) ./configure --prefix=/usr \
 --mandir=/usr/share/man \
 --bindir=/usr/sbin \
 --sbindir=/usr/lib/cgi-bin/icinga \

Bug#656868: emacs-goodies-el: markdown-mode should be loaded automatically for suffix .md

2012-01-22 Thread Axel Beckert

Package: emacs-goodies-el
Version: 35.2
Severity: wishlist

Hi,

Emacs should automatically start markdown-mode if it opens a file with
suffix .md (as common and recommended for e.g. GitHub README files).

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (900, 'testing'), (600, 'stable'), (400, 
'oldstable'), (110, 'experimental')
Architecture: i386 (i686)

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

Versions of packages emacs-goodies-el depends on:
ii  bash   4.2-1
ii  dpkg   1.16.1.2
ii  emacs [emacsen]23.3+1-4
ii  emacs23 [emacsen]  23.3+1-4
ii  install-info   4.13a.dfsg.1-8

Versions of packages emacs-goodies-el recommends:
ii  dict  1.12.0+dfsg-4
ii  perl-doc  5.14.2-6
ii  wget  1.13.4-2

emacs-goodies-el 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#656867: Please enabled hardened build flags