date:20140704

John Paul Adrian Glaubitz gave a good answer which I totally agree with.

PulseAudio is everywhere now, and it's mature enough already to be used
as the default backend.

Bug#753588: Should depend on mate-settings-daemon-pulse | mate-settings-daemon-gstreamer

See our answers in the discussion at [1] - they'd be the same here.

[1] https://bugs.debian.org/753584

Bug#753670: sensible-utils: Error spew when $SELECTED_EDITOR is unavailable

2014-07-04 Thread Matthias Urlichs

Package: sensible-utils
Version: 0.0.9
Severity: normal

$ /usr/bin/sensible-editor /tmp/fubar
/usr/bin/sensible-editor: 25: /usr/bin/sensible-editor: /usr/bin/vim.basic: not 
found
/usr/bin/sensible-editor: 28: /usr/bin/sensible-editor: nano: not found
/usr/bin/sensible-editor: 31: /usr/bin/sensible-editor: nano-tiny: not found
[ proceeds to edit /tmp/fubar as normal ]

Two problems here:
* Please respect my decision not to have nano installed and don't complain
  about that

* Please tell the user that $SELECTED_EDITOR is responsible for the
  vim.basic problem and that they can fix it by re-running `select-editor`.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'stable'), (600, 'unstable'), (550, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.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#692274:

2014-07-04 Thread Mathieu Malaterre

On Thu, Jul 3, 2014 at 9:07 AM, Alexander Wirt formo...@debian.org wrote:
 On Thu, 03 Jul 2014, Mathieu Malaterre wrote:

 Neat suggestion: https://bugs.debian.org/692274#41 !
 indeed. do you want to provide some suggestions for names and dependencys?

Technically all backends would be defined (docbook45, xhtml11, html4,
html5, slidy, wordpress or latex). With this defnition
asciidoc-docbook45 would also pull in fop just in case target document
type is PDF (fop is not required when doc type is article or
manpage...but we are getting picky).

The only one I would be interested (selfish) is asciidoc-docbook45
(offline docbook + pdf).

Thanks


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

Bug#753671: caff: please support gpg2

2014-07-04 Thread Ryan Kavanagh

Package: signing-party
Version: 1.1.7-1
Severity: wishlist

caff fails when the $CONFIG{'gpg'} configuration option points to
'/usr/bin/gpg2' with the following error:

ryan@nu:~$ ls .caff/gnupghome/
gpg.conf  pubring.gpg  pubring.kbx  random_seed  secring.gpg  trustdb.gpg
ryan@nu:~$ caff -u7BD15207E95EDDC9,8F7BF8FC4A11C97A 
7A33ECAA188B96F27C917288B3464F896AA15948
[trace] Exporting key(s) 7BD15207E95EDDC9,8F7BF8FC4A11C97A from your normal 
GnuPGHOME to /home/ryan/.caff/gnupghome.
[INFO] Fetching keys from hkp://keyring.debian.org, this may take a while...
[DEBUG] Imported 7A33ECAA188B96F27C917288B3464F896AA15948 for 
7A33ECAA188B96F27C917288B3464F896AA15948
[INFO] Sign the following keys according to your policy, then exit gpg with 
'save' after signing each key
/usr/bin/gpg2 --local-user 7BD15207E95EDDC9 
--homedir=/home/ryan/.caff/gnupghome --secret-keyring 
/home/ryan/.gnupg/secring.gpg --no-auto-check-trustdb --trust-model=always 
--edit 7A33ECAA188B96F27C917288B3464F896AA15948 sign
gpg (GnuPG) 2.0.24; Copyright (C) 2013 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.


pub  4096R/6AA15948  created: 2009-05-10  expires: never   usage: SC
sub  4096R/2497B8B2  created: 2009-05-10  expires: never   usage: E
[SNIP]
gpg save
[trace] Exporting key(s) 7BD15207E95EDDC9,8F7BF8FC4A11C97A from 
/home/ryan/.caff/gnupghome to 
/tmp/caff-7A33ECAA188B96F27C917288B3464F896AA15948-i6wSZ.
gpg: Fatal: can't open 
`/tmp/caff-7A33ECAA188B96F27C917288B3464F896AA15948-i6wSZ/trustdb.gpg': No such 
file or directory
Not all keys in '$CONFIG{'keyid'}' could be imported from caff's GnuPGHOME 
(with 'export-minimal').

Please consider supporting gpg2.

Best wishes,
Ryan

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

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

Versions of packages signing-party depends on:
ii  gnupg  1.4.16-1.2
ii  libc6  2.19-4
ii  libclass-methodmaker-perl  2.21-1
ii  libgnupg-interface-perl0.50-2
ii  libmailtools-perl  2.12-1
ii  libmime-tools-perl 5.505-1
ii  libnet-idn-encode-perl 2.200-1
ii  libterm-readkey-perl   2.32-1
ii  libtext-template-perl  1.46-1
ii  perl   5.18.2-4
pn  python:any none
ii  qprint 1.0.dfsg.2-2

Versions of packages signing-party recommends:
ii  dialog1.2-20140219-1
ii  libgd-gd2-noxpm-perl  1:2.46-2.1+b1
ii  libintl-perl  1.23-1
ii  libpaper-utils1.1.24+nmu3
ii  libtext-iconv-perl1.7-5+b1
ii  opensmtpd [mail-transport-agent]  5.4.2p1-2
ii  recode3.6-21
ii  whiptail  0.52.17-1

Versions of packages signing-party suggests:
ii  fonts-droid1:4.3-3
ii  imagemagick8:6.7.7.10+dfsg-3
ii  mutt   1.5.23-1
ii  texlive-latex-recommended  2014.20140528-3
ii  texlive-xetex  2014.20140528-3
pn  wipe   none

-- no debconf information


signature.asc
Description: Digital signature

Bug#753584: Should depend on mate-media-pulse | mate-media-gstreamer

Thanks for your answer. See also [1].

[1] https://bugs.debian.org/753588

Bug#739402: awesome-extra: 2012061101 version is out of date, please upgrade

2014-07-04 Thread Adam Lee

On Thu, Feb 20, 2014 at 10:27:29AM +0900, Arnaud Fontaine wrote:
 Jonathan McCrohan jmccro...@gmail.com writes:
  Its on my to-do list. I hope to get some time this weekend.
 
 Great, thanks!
 
  Arnaud, what is the current status of awesome 3.5? Can it be uploaded to
  unstable yet?
 
 As #736314 has still not been fixed, it's still in experimental. But
 that should not affect awesome-extra which should work with 3.4 anyway,
 right?

Hi, Jonathan and Arnaud, any updates of this?

-- 
Adam Lee
http://adam8157.info


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

Bug#753671: caff: please support gpg2

2014-07-04 Thread Peter Palfrader

On Fri, 04 Jul 2014, Ryan Kavanagh wrote:

 Package: signing-party
 Version: 1.1.7-1
 Severity: wishlist
 
 [trace] Exporting key(s) 7BD15207E95EDDC9,8F7BF8FC4A11C97A from 
 /home/ryan/.caff/gnupghome to 
 /tmp/caff-7A33ECAA188B96F27C917288B3464F896AA15948-i6wSZ.
 gpg: Fatal: can't open 
 `/tmp/caff-7A33ECAA188B96F27C917288B3464F896AA15948-i6wSZ/trustdb.gpg': No 
 such file or directory
 Not all keys in '$CONFIG{'keyid'}' could be imported from caff's 
 GnuPGHOME (with 'export-minimal').

This seems like a gpg2 bug in the spirit of #737128.

-- 
   |  .''`.   ** Debian **
  Peter Palfrader  | : :' :  The  universal
 http://www.palfrader.org/ | `. `'  Operating System
   |   `-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#753672: ITP: node-mime-types -- ultimate JavaScript content-type utility - Node.js module

2014-07-04 Thread Leo Iannacone

Package: wnpp
Severity: wishlist
Owner: Leo Iannacone l...@ubuntu.com
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-mime-types
  Version : 1.0.1
  Upstream Author : Jonathan Ong m...@jongleberry.com (http://jongleberry.com)
* URL : https://github.com/expressjs/mime-types
* License : Expat
  Programming Lang: JavaScript
  Description : ultimate JavaScript content-type utility - Node.js module
 This package provides a library for mime-type mapping similar to mime
 module with some differences, such as it always returns a value, even
 false if mime type is not found, and supports additional mime types.
 .
 Node.js is an event-based server-side JavaScript engine.


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

Bug#753370: pu: package intel-microcode/1.20140624.1

2014-07-04 Thread Adam D. Barratt


Control: tags -1 + pending

On 2014-07-01 11:25, Henrique de Moraes Holschuh wrote:

On Tue, 01 Jul 2014, Adam D. Barratt wrote:

On Mon, 2014-06-30 at 21:15 -0300, Henrique de Moraes Holschuh wrote:
 Please approve a fast-track upload of intel-microcode to non-free stable
 (Wheezy).

[...]

Please go ahead; thanks.


Uploaded.   Thank you very much!


(slightly belatedly) 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#751978: pu: package xmms2/0.8+dfsg-4+deb7u1

2014-07-04 Thread Adam D. Barratt


Control: tags -1 + pending

On 2014-06-19 13:11, Adam D. Barratt wrote:

Control: tags -1 + confirmed

On 2014-06-18 13:47, Moritz Mühlenhoff wrote:

attached debdiff fixes a FTBFS in xmms (#724487).


Please go ahead.


For the record, this was uploaded and I've just flagged it for 
acceptance.


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#753673: dnssec-trigger: conffile contains version number

2014-07-04 Thread Jonas Smedegaard

Package: dnssec-trigger
Version: 0.13~svn683-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

/etc/dnssec-trigger/dnssec-trigger.conf contains a header which includes
a version number.  That is bad for a conffile, as that means it triggers
a dialogue at each and every upstream version bump, not only when actual
changes to the config file occurs, when edited locally.

Please strip the version number from the conffile.

 - Jonas

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQF8BAEBCgBmBQJTtl1YXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0
RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWN8oIALOgYkYuXfw59gVgXAVzj1BG
sqfg/kb+tgC5XdQuffIwFxa9ZVVAAOGUJfaYeeYFYdFda20c871NZODbLMvuFyTl
hQ9uYARDdEIX7sKnHcGD8dCCQoQG5tirnV5MRa8wlQYG3SkIf6pmH6X5soseixps
TQrXxZI0H3qfw9RVOPMlNbUm2VvQWUj3Jdn6qSj6c1oQk5LS8YueQkah/yJyAiBt
8uKBvN0VjSRLMaQ0gE4Oi2wd0mTxOtsWqHbVihg9t8YSjYF6MFsgdaVyq+jpeWW2
Qj8VPkcHU/tVuUxY2Ocg4vTSbe5+2Uvu8ankkUKHMWCpfJOvnD6JuOwwvW59OA4=
=p4oS
-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#752674: Upstream bug

2014-07-04 Thread Pietro Battiston

Il giorno ven, 04/07/2014 alle 07.20 +0900, Mike Hommey ha scritto:
 On Thu, Jul 03, 2014 at 03:03:40PM +0200, Pietro Battiston wrote:
  This seems quite similar to
  https://bugzilla.mozilla.org/show_bug.cgi?id=1015175
  ... but my browser does not crash with mapy.cz .
  [...]
  
  (all but the first do crash mine)
 
 Your crash is bug 751569.
 

Oops... thanks.

Pietro


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

Bug#753674: [dash] dash aborts a script, when 'shift' tested by 'while' fails

2014-07-04 Thread Andre Naujoks

Package: dash
Version: 0.5.7-4
Severity: normal

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

Hi.

dash seems to abort the following script, when reaching the expected
error when the shift command has nothing more to shift and fails.


#!/bin/sh

# just output all parameters
echo $1
while shift; do
echo $1
done

echo done


It never reaches the echo done part, which it should in my eyes. bash
behaves differently (and IMHO correctly) in this case and reaches the
end of the script.

Additionally an error string is output from dash, which is probably not
needed but documented that way in the manpage.

This is a run with dash (echo done is not reached):
$ ./shifttest.sh 1 2 3 4
1
2
3
4

./shifttest.sh: 4: shift: can't shift that many
$

This is a run with bash:
$ ./shifttest.sh 1 2 3 4
1
2
3
4

done
$

The problem seems only to happen when shift is tested. Other things,
like checking for the existence of a file, do not trigger an immediate exit.

Regards
  Andre

--- System information. ---
Architecture: amd64
Kernel:   Linux 3.14-1-amd64

Debian Release: jessie/sid
  500 unstableftp.de.debian.org
  500 unstableftp-stud.hs-esslingen.de

--- Package information. ---
Depends   (Version) | Installed
===-+-
debianutils   (= 2.15) | 4.4
dpkg(= 1.15.0) | 1.17.10


Package's Recommends field is empty.

Package's Suggests field is empty.


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

Bug#753675: libvirtError: argument unsupported: parameter '' not supported on virDomainSetBlkioParameters

2014-07-04 Thread Jackie

Package: python-libvirt
Version: 1.2.1-2~bpo70+1
Severity: normal

Dear Maintainer,

Python-libvirt package in wheezy-backports have a serious bug
that set-APIs just like virDomainSetBlkioParameters can not take
function. I believe this is caused by a bug which is fixed in
soucecode from libvirt community of version 1.2.4.

The fix patch seems to be setPyVirTypedParameter: Copy full
field name(commitid: 412c93a7b9111ad15c543e286f23bb5891749c42)
in libvirt git repository(git://libvirt.org/libvirt-python.git)

The steps to reporduce this bug are as following:
1) start a kvm vm
2) use ipython to call setBlkioParameters function as following:

root@libvirt-test-gq:~# ipython
Python 2.7.3 (default, Mar 13 2014, 11:03:55)
Type copyright, credits or license for more information.

IPython 0.13.1 -- An enhanced Interactive Python.
? - Introduction and overview of IPython's features.
%quickref - Quick reference.
help - Python's own help system.
object? - Details about 'object', use 'object??' for extra details.

In [1]: import libvirt

In [2]: conn = libvirt.open()

In [3]: doms = conn.listAllDomains()

In [4]: doms
Out[4]: [libvirt.virDomain at 0x26cb6d0]

In [5]: dom = doms[0]

In [6]: dom.blkioParameters()
Out[6]:
{'device_read_bytes_sec': '',
'device_read_iops_sec': '',
'device_weight': '',
'device_write_bytes_sec': '',
'device_write_iops_sec': '',
'weight': 500}

In [7]: params = {'weight': 250}

In [8]: dom.setBlkioParameters(params, 0)
libvirt: error : argument unsupported: parameter '' not supported
---
libvirtError Traceback (most recent call last)
ipython-input-8-d746a68b6973 in module()
 1 dom.setBlkioParameters(params, 0)

/usr/lib/python2.7/dist-packages/libvirt.pyc in setBlkioParameters(self,
params, flags)
1961 Change the blkio tunables 
1962 ret = libvirtmod.virDomainSetBlkioParameters(self._o, params, flags)
- 1963 if ret == -1: raise libvirtError ('virDomainSetBlkioParameters()
failed', dom=self)
1964 return ret
1965

libvirtError: argument unsupported: parameter '' not supported


Then I compiled and installed the python-libvirt from sourcecode
of 1.2.4 version and do the same operations as above,
it returned the right answer now:
root@libvirt-test-gq:~/github/libvirt-python# ipython
Python 2.7.3 (default, Mar 13 2014, 11:03:55)
Type copyright, credits or license for more information.

IPython 0.13.1 -- An enhanced Interactive Python.
? - Introduction and overview of IPython's features.
%quickref - Quick reference.
help - Python's own help system.
object? - Details about 'object', use 'object??' for extra details.

In [1]: import libvirt

In [2]: conn = libvirt.open()

In [3]: dom = conn.listAllDomains()[0]

In [4]: params = {'weight': 250}

In [5]: dom.setBlkioParameters(params, 0)
Out[5]: 0

In [6]: dom.blkioParameters(0)
Out[6]:
{'device_read_bytes_sec': '',
'device_read_iops_sec': '',
'device_weight': '',
'device_write_bytes_sec': '',
'device_write_iops_sec': '',
'weight': 250}

Besides the virDomainSetBlkioParameters function, I believe many set-APIs
have the same problem in version 1.2.1. Can maintainer think about
to package a new version of python-libvirt, or backport the fix patch?

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

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

Versions of packages python-libvirt depends on:
ii libc6 2.17-97
ii libvirt0 1.2.4-1~bpo70+1
ii python 2.7.3-4+deb7u1

Versions of packages python-libvirt recommends:
ii libvirt-bin 1.2.4-1~bpo70+1

python-libvirt 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#753641: ITP: liblinux-pid-perl -- wrapper around the getpid() and getppid() C functions

2014-07-04 Thread Guillem Jover

Hi!

On Thu, 2014-07-03 at 20:37:47 +0200, gregor herrmann wrote:
 Package: wnpp
 Owner: gregor herrmann gre...@debian.org
 Severity: wishlist
 X-Debbugs-CC: debian-de...@lists.debian.org,debian-p...@lists.debian.org
 
 * Package name: liblinux-pid-perl
   Version : 0.04
   Upstream Author : Rafael Garcia-Suarez r...@consttype.org
 * URL : https://metacpan.org/release/Linux-Pid
 * License : Artistic or GPL-1+
   Programming Lang: Perl
   Description : wrapper around the getpid() and getppid() C functions
 
 Perl already returns the PID and PPID in variables and builtins. Linux::Pid
 forces perl to call the underlying C functions getpid() and getppid().
 
 This is useful with multithreaded programs. Linux' C library, using the Linux
 thread model, returns different values of the PID and the PPID from different
 threads.

With glibc and NPTL this module does not seem to make much sense, as
each different thread will have the same PID. If it was exposing the
Linux gettid() syscall then it would be the modern equivalent, but
that depends on the assumptions from the call sites and the expected
threading model, I suppose.

I guess this is just a dependency from something else? Why not patch
it to use the native perl functions instead?

Thanks,
Guillem


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

Bug#753171: FTBFS: /usr/bin/ld: cannot find -lee

2014-07-04 Thread Emilio Pozuelo Monfort

On 29/06/14 20:16, Michael Biebl wrote:
 Source: sagan
 Version: 0.2.1.r1-1
 Severity: serious
 
 Due to the latest updates in liblognorm, sagan now FTBFS
 
 configure:2701: checking whether the C compiler works
 configure:2723: gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4
 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wl,-z,relro
 conftest.c -lm -lestr -lee 5
 /usr/bin/ld: cannot find -lee
 collect2: error: ld returned 1 exit status
 
 Full build log is attached.
 
 Due to the changes in liblognorm, the liblognorm-dev package no longer
 depends on libee-dev.
 
 Simply adding libee-dev to Build-Depends was not sufficient, due to a
 bug in libestmp [1]

libestmp got fixed. Is adding libee-dev enough now?

Emilio


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

Bug#753656: linux-image-3.14-1-rt-amd64: Kernel panic caused by ohci_hcd

2014-07-04 Thread Andrei POPESCU

Control: reassign -1 src:linux

On Jo, 03 iul 14, 18:35:01, The GZeus wrote:
 Source: linux-image-3.14-1-rt-amd64
 Severity: important
 
 Dear Maintainer,
 
 
 Twice I have had a kernel panic with nearly identical messages while playing 
 a game (Dust: An Elysian Tail, obtained via native Linux Steam, which I 
 installed from non-free) with an official MS XBox 360 wired controller with 
 the standard xpad driver.
 
 I took a photo of the most recent one, and I'm willing to type out whatever 
 lines contain the necessary information.
 Would you like the output of lspci/lsusb?
 
 Odd that I've never had this happen in any other situation, but that's what 
 happened.
 
 My system uses an AMD A10 APU.
 
 *** Reporter, please consider answering these questions, where appropriate ***
 
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
  ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
 
 *** End of the template - remove these template lines ***
 
 
 -- System Information:
 Debian Release: jessie/sid
   APT prefers testing
   APT policy: (900, 'testing')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386
 
 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
 Locale: LANG=en_GB.UTF-8, LC_CTYPE=ja_JP.utf8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Bug#753584: Should depend on mate-media-pulse | mate-media-gstreamer

2014-07-04 Thread Mike Gabriel


Hi Vlad,

On  Fr 04 Jul 2014 08:57:12 CEST, Vlad Orlov wrote:


John Paul Adrian Glaubitz gave a good answer which I totally agree with.

PulseAudio is everywhere now, and it's mature enough already to be used
as the default backend.


doing something because everyone is doing it has not been a good  
reason for acting in the past with several awful examples in human  
history.


Can you provide a more technical reason? Why should we skip using the  
gstreamer layer and directly communicate with pulseaudio? If I  
understand the gstreamer design correctly, it ends up using pulse  
underneath, anyway.


Mike
--

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

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

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


pgp47q1HXMs4N.pgp
Description: Digitale PGP-Signatur

Bug#752674: iceweasel - segmentation fault (mapy.cz)

2014-07-04 Thread Jan Korbel

It is not reproducible anymore. Possibly changes in some library or
mapy.cz website. I'm still on 30.0-2.

So this could be closed. Thanks.

J.


On Fri, 4 Jul 2014 07:20:09 +0900
Mike Hommey m...@glandium.org wrote:
 Please provide a crash backtrace (see instructions in
 /usr/share/bug/iceweasel/presubj)


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

Bug#750715: ipython: FTBFS against uglify 2.x series - uglifyjs -nc is not a supported option

2014-07-04 Thread Leo Iannacone

Hi Julian,

please consider to test this patch.

Thanks!
Index: debian/patches/packaged-js.patch
===
--- debian/patches/packaged-js.patch(revision 29613)
+++ debian/patches/packaged-js.patch(working copy)
@@ -6,7 +6,7 @@
  mkdir -p bootstrap/js
  cat js/bootstrap-transition.js js/bootstrap-alert.js js/bootstrap-button.js js/bootstrap-carousel.js js/bootstrap-collapse.js js/bootstrap-dropdown.js js/bootstrap-modal.js js/bootstrap-tooltip.js js/bootstrap-popover.js js/bootstrap-scrollspy.js js/bootstrap-tab.js js/bootstrap-typeahead.js js/bootstrap-affix.js  bootstrap/js/bootstrap.js
 -./node_modules/.bin/uglifyjs -nc bootstrap/js/bootstrap.js  bootstrap/js/bootstrap.min.tmp.js
-+uglifyjs -nc bootstrap/js/bootstrap.js  bootstrap/js/bootstrap.min.tmp.js
++uglifyjs bootstrap/js/bootstrap.js  bootstrap/js/bootstrap.min.tmp.js
  echo /*!\n* Bootstrap.js by @fat  @mdo\n* Copyright 2012 Twitter, Inc.\n* http://www.apache.org/licenses/LICENSE-2.0.txt\n*/;  bootstrap/js/copyright.js
  cat bootstrap/js/copyright.js bootstrap/js/bootstrap.min.tmp.js  bootstrap/js/bootstrap.min.js
  rm bootstrap/js/copyright.js bootstrap/js/bootstrap.min.tmp.js

Bug#753581: qt4-designer: Fails to start, symbol lookup error in qscintilla

2014-07-04 Thread Gudjon I. Gudjonsson

Hi Lisandro and Scott

Thanks for the answers
 
 _ZN13QsciScintillaC1EP7QWidget demangles to
 QsciScintilla::QsciScintilla(QWidget*) and
 qscintilla2-2.8.2+dfsg/Qt4Qt5/qsciscintilla.cpp has
 QsciScintilla::QsciScintilla(QWidget *parent) which is unchanged for a long
 time.  So I believe that things are as they should be for Qt4 in
 qscintilla2, but the designer plugin for Qt5 is not yet packaged.
 
 If you are using the qtcreator from Unstable, you probably got the Qt5 one
 and this may be a poor error message that turns out to mean the Qt5
 designer plugin isn't packaged yet.
 
I do run designer from the shell.
Today I could install python3-pyqt5 (it was uninstallable yesterday) and I 
rebuilt qscintilla2 and designer works without problems.
This is against my intuition, I thought designer needed to be rebuilt not the 
library.

Scott, can you please rebuild qscintilla2?

Regards
Gudjon


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

Bug#715821: plasma-widget-networkmanagement: Should not ask for wallet access when no password is used

2014-07-04 Thread Petter Reinholdtsen


Control: found -1 0.9.3.3-3

I just tested in Jessie, and the problem exist here too.  I've poked the
upstream bug too, where it was said that this should be fixed in
network-manager, not the plasma widget, but I have not quite understood
why.  If so, perhaps it should be reassigned?

Btw: Why is this bug tagged 'fixed-upstream'?

-- 
Happy hacking
Petter Reinholdtsen


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

Bug#753676: tracker.debian.org: Review the trello board and file relevant entries in the BTS

2014-07-04 Thread Raphaël Hertzog

Package: tracker.debian.org
Severity: normal

Up to now, we have been using the following Trello board:
https://trello.com/b/faDgzjwO/pts-rewrite

We should scan all the cards there and file corresponding bugs in the BTS
when there's still something actionable and/or interesting to consider.

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

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (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#730017: debugging link

2014-07-04 Thread Dominique Dumont


the debug page is now:

https://wiki.gnome.org/Projects/NetworkManager/Debugging

-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.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#753677: audacious: FTBFS on s390x: Requested 'libguess = 1.2' but version of libguess is 1.1

2014-07-04 Thread Emilio Pozuelo Monfort

Source: audacious
Version: 3.5-1
Severity: serious

Your package fail to build on s390x because libguess is too old there. You
should bump your minimum build-dependency, or possibly lower the requirement
as suggested in #753402.

This is blocking your own (uncoordinated) audacious transition.

Emilio


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

Bug#753584: Should depend on mate-media-pulse | mate-media-gstreamer

2014-07-04 Thread John Paul Adrian Glaubitz

On 07/04/2014 10:19 AM, Mike Gabriel wrote:
 PulseAudio is everywhere now, and it's mature enough already to be used
 as the default backend.
 
 doing something because everyone is doing it has not been a good reason
 for acting in the past with several awful examples in human history.

Eh, please keep that in philosophy class.

 Can you provide a more technical reason? Why should we skip using the
 gstreamer layer and directly communicate with pulseaudio? If I
 understand the gstreamer design correctly, it ends up using pulse
 underneath, anyway.

I already explained that. Pulse Audio has become the de-facto standard
audio server on Linux and MATE should therefore install it's PA
backend by default.

You also only get a fully working Pulse Audio volume control [1] in MATE
when mate-media-pulse is installed.

Adrian

 [1] http://fedoraproject.org/wiki/Features/VolumeControl#User_Experience

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



signature.asc
Description: OpenPGP digital signature

Bug#753483: libgnustep-dl2-0d: Programs using EOControl die with NSInvalidArgumentException, reason: Can not determine type information for +[GDL2CDNSObject (null)]

2014-07-04 Thread Yavor Doganov

Federico Giménez Nieto wrote:
 DBModeler should be also readded to the menu, right?

For wheezy, that is up to the SRMs I believe.

For jessie, yes, but gnutsep-dl2 will be broken again after the
transition so you probably would want to package a SVN snapshot or a
(forthcoming?) new release.


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

Bug#753674: [dash] dash aborts a script, when 'shift' tested by 'while' fails

2014-07-04 Thread Andre Naujoks

I just noticed Bug #627856, which deals with a very similar issue.

Is a shift without an argument also considered a syntax error if it is
called too often? If yes, then this bug can be closed and I am sorry for
the noise.

IMHO this should not be considered a syntax error, because it is (again
IMHO) a valid way of getting all arguments of a script or shell function.

Regards
  Andre


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

Bug#753584: Should depend on mate-media-pulse | mate-media-gstreamer

That's right, you can only get the normally looking and working volume control
dialog with PulseAudio backend. With GStreamer one the volume control dialog
is practically useless - especially if GStreamer ends up using pulse 
underneath.

If PulseAudio is installed in the system (and it is), you need a 
PulseAudio-compatible
volume control dialog - for example, to manage input/output devices effectively.

Bug#752075: daemontools-run: Add systemd support

2014-07-04 Thread Gerrit Pape

Hi,

I looked into latest policy, but did not find anything about systemd
support.  I'm surprised that this is now a release critical bug, and the
package marked for removal.  What's the justification?

This package hooks into /etc/inittab, does systemd not automatically
manage services from inittab?  Isn't it systemd having release critical
bug then?

Regards, Gerrit


On Thu, Jun 19, 2014 at 12:54:06PM +0200, Joern Heissler wrote:
 Package: daemontools-run
 Version: 1:0.76-3
 Severity: grave
 Justification: renders package unusable
 
 Hi,
 Debian decided to use systemd.
 
 I'm using a local dnscache (djbdns) for recursive dns lookups, but this
 service isn't started automatically. I assume that it's because
 daemontools-run only supports sysvinit's inittab.
 
 Please add systemd support,
 Cheers!
 
 
 -- System Information:
 Debian Release: jessie/sid
   APT prefers unstable
   APT policy: (600, 'unstable')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386
 
 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash
 
 Versions of packages daemontools-run depends on:
 ii  daemontools  1:0.76-3
 
 daemontools-run recommends no packages.
 
 daemontools-run 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#753678: vim-nox: matchadd() highlightning lost on split window

2014-07-04 Thread Ph. Marek

Package: vim-nox
Version: 2:7.4.335-1
Severity: normal

Steps to reproduce:

start vim
   # vim -u NONE -U NONE -N
enter some text
   i this is a testESC
define a match
   :call matchadd(MoreMsg, is)
and note that two occurrences are found.

Now press
   Ctrl-W s
*or*
   Ctrl-W v
to get a split window.

Bug: in the old window the match is no longer highlighted.



-- Package-specific info:

--- real paths of main Vim binaries ---
/usr/bin/vi is /usr/bin/vim.gnome
/usr/bin/vim is /usr/bin/vim.gnome
/usr/bin/gvim is /usr/bin/vim.gnome

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

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

Versions of packages vim-nox depends on:
ii  libacl1   2.2.52-1
ii  libc6 2.19-4
ii  libgpm2   1.20.4-6.1
ii  liblua5.2-0   5.2.3-1
ii  libperl5.18   5.18.2-4
ii  libpython2.7  2.7.7-2
ii  libruby2.12.1.2-2
ii  libselinux1   2.3-1
ii  libtcl8.6 8.6.1-6
ii  libtinfo5 5.9+20140118-1
ii  vim-common2:7.4.335-1
ii  vim-runtime   2:7.4.335-1

vim-nox recommends no packages.

Versions of packages vim-nox suggests:
ii  cscope   15.8a-2
pn  vim-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#753620: wishlist: idl/gdl-written software

2014-07-04 Thread Sylwester Arabas


Hi Axel, hi All,

Thanks for quick reply.

On 04/07/14 00:32, Axel Beckert wrote:

While the gnudatalanguage package is their main dependency, this is
actually nothing we can fix in the gnudatalanguage Debian package
itself.

Bascially for each software you listed, there should be an RFP (need
to be filed against the pseudo-package wnpp, neither without package
attribution nor attributed to the gnudatalanguage package).

I've already reassigned the GSHHS stuff to the wnpp pseudo-package.

I can reassign and clone this bug report for each of these programs,
but you will likely need to add some more details (licenses, etc.)
afterwards to make the proper RFPs.

Alternatively you can write new RFP bug reports (against the wnpp
pseudo package) on your own and I'll close this one afterwards. If you
are on Debian you can use the command reportbug wnpp to get assisted
filing of the RFP bug reports. (Not sure if that works on Ubuntu, too.)


I'll of course do the resubmission myself. Although I did not recall the 
wnpp tag yesterday, I had intentionally linked this discussion with 
gdl package - perhaps before starting submitting multiple RFPs we can 
discuss some issues here?


- where to place the IDL/GDL-written software in the system
- how to inform GDL package about their location?
- how to make these packages usable for IDL / PV-WAVE users?
- how to name these packages?
- should idlastro be splitted into multiple subpackages?
- should idlastro become a dependency of gdl?
- can you guys from the debian-astro team maintain these packages?
- what other IDL/GDL-written software is of interest?

Looking forward to hearing your comments,
Thanks,
Sylwester

--
http://www.igf.fuw.edu.pl/~slayoo/


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

Bug#747989: Help required

2014-07-04 Thread Yavor Doganov

[ Apologies for replying to myself again. ]

Yavor Doganov wrote:
   - The autorelease pool should be created in the constructor, before
 the first object is allocated.  That's openvpn_plugin_open_v1,

Actually, after looking more into this and reading openvpn-plugin.h, I
see that the upstream patch is correct here.  ctx-config is manually
released in openvpn_plugin_close_v1, so that's perfectly fine.

There are a few other potential issues with initialization -- not
assigning self to the result of super or [self init] and using [self
init] when [super init] should be used.  These are easily fixable.


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

Bug#750361: [Pkg-chromium-maint] Bug#750361: Experimental

2014-07-04 Thread Mark Hindley

On Thu, Jul 03, 2014 at 06:10:19PM -0400, Michael Gilbert wrote:
 On Sun, Jun 22, 2014 at 3:28 AM, Mark Hindley wrote:
  i have just tried the experimental package in an unstable/experimental 
  chroot on non SSE2 hardware (Via Ezra). The good news is that chromium 
  36.0.1985.67-1 runs without SIGILL but then it fails with
 
   [0622/072436:FATAL:content_main_runner.cc(689)] Check failed: 
  base::i18n::InitializeICU().
  Aborted
 
 That error is expected when /proc is not mounted within the chroot.
 Outside the chroot, you can do
 
 # mount -o bind /proc chroot/proc

Thanks. With that and also

# chmod 1777 /dev/shm

chromium version 36.0.1985.84-1 runs fine from the chroot on my Via Ezra.

Mark


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

Bug#753612: libsofthsm: switch to multiarch should have happened

2014-07-04 Thread Ondřej Surý

Hi,

that change was introduced by upstream (and I have missed that),
so thanks for noticing, I will explicitly set the path back to correct
location and upload in a moment.

O.

On Thu, Jul 3, 2014, at 17:27, Marc Dequènes (Duck) wrote:
 Package: libsofthsm
 Version: 1.3.7-1
 Severity: important
 Control: affects -1 opendnssec
 
 
 Coin,
 
 Since you changed the default configuration in opendnssec to use:
Module/usr/lib/x86_64-linux-gnu/softhsm/libsofthsm.so/Module
 instead of:
Module/usr/lib/softhsm/libsofthsm.so/Module
 you need to make the multiarch switch.
 
 I raised the severity as current opendnssec's configuration is  
 unusable with this package. You should have done this in the right  
 order in the first place.
 
 Regards.
 
 -- 
 Marc Dequènes (Duck)
 
 Email had 1 attachment:
 + Attachment2
   1k (application/pgp-signature)


-- 
Ondřej Surý ond...@sury.org
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server


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

Bug#753679: schroedinger: : use dh-autoreconf to fix ppc64el FTBFS

2014-07-04 Thread Brahadambal Srinivasan


Package: schroedinger
Version: 1.0.11-2
Severity: normal
User: debian-powe...@lists.debian.org
Usertags: ppc64elTags: patch
User: debian-de...@lists.debian.org
Usertags: autoreconf


Dear Maintainer,

The schroedinger pkg fails to build from source, because the libtool
configuration files need to be updated. This patch includes
dh-autoreconf to the build so it builds accordingly.

Thanks and regards,
Brahadambal

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

Kernel: Linux 3.13-1-powerpc64le (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

--===4138465864465701622==
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/x-diff; charset=utf-8
Content-Disposition: attachment; filename=add_ppc64le_support.patch

--- schroedinger-1.0.11.orig/debian/control2012-04-26 
06:12:04.0 +
+++ schroedinger-1.0.11/debian/control2014-07-04 09:34:30.0 
+

@@ -5,6 +5,7 @@
 Uploaders: Sebastian Dröge sl...@debian.org
 Build-Depends: cdbs (= 0.4.93~),
debhelper (= 8.1.3~),
+  dh-autoreconf,
liborc-0.4-dev (= 1:0.4.16),
pkg-config
 Build-Depends-Indep: gtk-doc-tools (= 1.0)
--- schroedinger-1.0.11.orig/debian/rules2012-04-26 
06:03:26.0 +

+++ schroedinger-1.0.11/debian/rules2014-07-04 09:35:20.0 +
@@ -1,6 +1,7 @@
 #!/usr/bin/make -f

 include /usr/share/cdbs/1/rules/debhelper.mk
+include /usr/share/cdbs/1/rules/autoreconf.mk
 include /usr/share/cdbs/1/class/gnome.mk
 include /usr/share/cdbs/1/rules/utils.mk


--===4138465864465701622==--


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

Bug#753680: [paraview] fail to build application on top of paraview

2014-07-04 Thread trophime

Package: paraview
Version: 4.1.0+dfsg-3
Severity: normal

Trying to build application on top of paraview-dev (for instance Salome 7.4.0)
because of some missing files:

usr/lib/cmake/paraview/VTKTargets.cmake
usr/lib/cmake/paraview/Modules/*.cmake
usr/lib/cmake/paraview/Modules/*.txt

usr/bin/vtkHashSource
usr/bin/vtkWrapPython
usr/bin/vtkWrapTcl
usr/bin/vtkWrapPythonInit
usr/bin/vtkParseJava
usr/bin/vtkWrapJava
usr/bin/vtkWrapTclInit
usr/bin/vtkParseOGLExt
usr/bin/vtkWrapHierarchy
usr/bin/smTestDriver
usr/bin/vtkkwProcessXML
usr/bin/vtkEncodeString

It's fairly easy to add these files to the paraview-dev package.
eg for VTKTargets.cmake:
override_dh_install:
# install missing file
mkdir -p $(DESTDIR)/usr/lib/cmake/paraview
find . -name VTKTargets.cmake | xargs -i -t install -m 644 {} 
$(DESTDIR)/usr/lib/cmake/paraview/
sed -i 
s%\(IMPORTED_LOCATION_NONE.*\\).*/lib/\([^/]\+\\)%\1/usr/lib/paraview/\2%g 
$(DESTDIR)/usr/lib/cmake/paraview/
VTKTargets.cmake
sed -i 
s%\(IMPORTED_LOCATION_NONE.*\\).*/bin/\([^/]\+\\)%\1/usr/bin/\2%g 
$(DESTDIR)/usr/lib/cmake/paraview/VTKTarget
s.cmake
#cat $(DESTDIR)/usr/lib/cmake/paraview/VTKTargets.cmake
#find . -name VTKTargets.cmake

dh_install --list-missing



However there are some name clashes with tcl-tk, libvtk5-dev, libvtk-java and 
python-vtk
5.8.0 versions.

The solution is either :
* to add conflicts with these vtk5 packages
* or to use an extension for any executables generated by paraview 
by removing the -DVTK_CUSTOM_LIBRARY_SUFFIX= option in cmake  

I would personally by in favor of the second solution as it will
enable to install and use both paraview, vtk6 and vtk5 packages 
on a given machine

Best
C

 
--- System information. ---
Architecture: amd64
Kernel:   Linux 3.14-1-amd64

Debian Release: jessie/sid
  500 testing-proposed-updates ftp.fr.debian.org 
  500 testing security.debian.org 
  500 testing http.us.debian.org 
  500 testing ftp.fr.debian.org 
  500 testing euler.lcmi.local 
  500 stable  dl.google.com 
  500 sid linux.dropbox.com 
  500 jessie  neuro.debian.net 
  500 dataneuro.debian.net 

--- Package information. ---
Depends (Version) | Installed
=-+-==
tcl8.5| 8.5.15-4
 OR tclsh | 
libavcodec55(= 6:10~beta1~)  | 6:10.1-1
 OR libavcodec-extra-55   (= 6:10.1) | 
libavformat55(= 6:10~beta1~) | 6:10.1-1
libavutil53  (= 6:10~beta1~) | 6:10.1-1
libc6   (= 2.15) | 
libexpat1  (= 2.0.1) | 
libfreetype6   (= 2.2.1) | 
libgcc1  (= 1:4.1.1) | 
libgl1-mesa-glx   | 
 OR libgl1| 
libhdf5-7 | 
libjpeg8  (= 8c) | 
libjsoncpp0   | 
libogg0   (= 1.0rc3) | 
libopenmpi1.6 | 
libpng12-0  (= 1.2.13-4) | 
libpython2.7 (= 2.7) | 
libqt4-help  (= 4:4.5.3) | 
libqt4-network   (= 4:4.5.3) | 
libqtcore4   (= 4:4.8.0) | 
libqtgui4(= 4:4.8.0) | 
libqtwebkit4   (= 2.2.1) | 
libstdc++6   (= 4.6) | 
libswscale2  (= 6:10~beta1~) | 
libtheora0   (= 1.0) | 
libtiff5   (= 4.0.3) | 
libx11-6  | 
libxml2(= 2.7.4) | 
libxt6| 
zlib1g (= 1:1.2.3.4) | 


Recommends   (Version) | Installed
==-+-===
mpi-default-bin| 1.0.2+nmu1
paraview-python| 
paraview-doc   | 4.1.0+dfsg-3


Suggests(Version) | Installed
=-+-===
hdf5-tools| 
h5utils   | 

-- 


Christophe TROPHIME
Research Engineer

LNCMI
CNRS - LNCMI
25, rue des Martyrs
BP 166
38042 GRENOBLE Cedex 9
FRANCE
CNRS

Tel : +33 (0)4 76 88 90 02 
Fax : +33 (0) 4 76 88 10 01
Office U 19 
M@il : christophe.troph...@lncmi.cnrs.fr 



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

Bug#752075: daemontools-run: Add systemd support

2014-07-04 Thread Ansgar Burchardt

Hi,

On 07/04/2014 11:08, Gerrit Pape wrote:
 I looked into latest policy, but did not find anything about systemd
 support.  I'm surprised that this is now a release critical bug, and the
 package marked for removal.  What's the justification?

Ask the submitter?

 This package hooks into /etc/inittab, does systemd not automatically
 manage services from inittab?  Isn't it systemd having release critical
 bug then?

Could we please not have another systemd thread on -devel@? The last one
is not even cold yet... Thanks!

Unrelated to that, I would think that any package that modifies
/etc/inittab is buggy: maintainer scripts should not modify
configuration files belonging to other packages (Policy 10.7.4).

Even worse, daemontools-run adds a new entry uncoditionally on upgrade
even when the existing one was removed/commented out by the local admin.
That's a RC bug (Policy 10.7.3: local changes must be preserved during
a package upgrade)...

Ansgar


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

Bug#752075: daemontools-run: Add systemd support

2014-07-04 Thread Ondřej Surý

Gerrit,

it's up to you to lower the severity of the bug to important (I guess
since it will break with default init system).

You should have done that instead of ccing debian-devel in the
current situation.

Please do not abuse debian-devel to questions that could be politely
and calmly discussed outside the list.

Thanks,
O.

On Fri, Jul 4, 2014, at 11:08, Gerrit Pape wrote:
 Hi,
 
 I looked into latest policy, but did not find anything about systemd
 support.  I'm surprised that this is now a release critical bug, and the
 package marked for removal.  What's the justification?
 
 This package hooks into /etc/inittab, does systemd not automatically
 manage services from inittab?  Isn't it systemd having release critical
 bug then?
 
 Regards, Gerrit
 
 
 On Thu, Jun 19, 2014 at 12:54:06PM +0200, Joern Heissler wrote:
  Package: daemontools-run
  Version: 1:0.76-3
  Severity: grave
  Justification: renders package unusable
  
  Hi,
  Debian decided to use systemd.
  
  I'm using a local dnscache (djbdns) for recursive dns lookups, but this
  service isn't started automatically. I assume that it's because
  daemontools-run only supports sysvinit's inittab.
  
  Please add systemd support,
  Cheers!
  
  
  -- System Information:
  Debian Release: jessie/sid
APT prefers unstable
APT policy: (600, 'unstable')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386
  
  Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
  Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
  Shell: /bin/sh linked to /bin/dash
  
  Versions of packages daemontools-run depends on:
  ii  daemontools  1:0.76-3
  
  daemontools-run recommends no packages.
  
  daemontools-run suggests no packages.
  
  -- no debconf information
 
 
 -- 
 To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive:
 https://lists.debian.org/20140704090821.13265.qm...@79b6c771442573.315fe32.mid.smarden.org
 


-- 
Ondřej Surý ond...@sury.org
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server


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

Bug#753681: unbound: Race condition in verbose log system

2014-07-04 Thread Stephane Lapie

Package: unbound
Version: 1.4.17-3
Severity: important

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

   * What led up to the situation?
I have a need for verbose logging on a server with intensive traffic (2000q/s),
and of course need log rotation (on a hourly basis).
We actually have 1G of logs building up every 2 hours.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I am using a custom logfile (logfile: /var/log/unbound/query.log),
with verbose logging (verbosity: 2), and no syslog (use-syslog: no),
and I set up logrotate to run unbound-control log_reopen as postrotate script.
   * What was the outcome of this action?
Randomly, upon rotating, or just after, a segfault occurs, or the process just 
dies.

I filed a bug report with the upstream developper, who fixed it in the latest 
SVN trunk.
https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=593

The fixed file is as follows :
http://unbound.nlnetlabs.nl/svn/trunk/util/log.c

Given this is valid for the latest SVN trunk, but not relevant for version 
1.4.17,
I backported the relevant bits into my own patch.

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


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

Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages unbound depends on:
ii  adduser 3.113+nmu3
ii  libc6   2.13-38+deb7u1
ii  libevent-2.0-5  2.0.19-stable-3
ii  libgcc1 1:4.7.2-5
ii  libldns11.6.13-1
ii  libpython2.72.7.3-6+deb7u2
ii  libssl1.0.0 1.0.1e-2+deb7u11
ii  openssl 1.0.1e-2+deb7u11
ii  unbound-anchor  1.4.17-3

unbound recommends no packages.

unbound suggests no packages.

-- Configuration Files:
/etc/unbound/unbound.conf changed [not included]

-- no debconf information
--- util/log.c.orig	2014-07-04 18:16:38.20649 +0900
+++ util/log.c	2014-07-04 18:18:22.403506000 +0900
@@ -66,6 +66,10 @@
 static int key_created = 0;
 /** pthread key for thread ids in logfile */
 static ub_thread_key_t logkey;
+#ifndef THREADS_DISABLED
+/** pthread mutex to protect FILE* */
+static lock_quick_t log_lock;
+#endif
 /** the identity of this executable/process */
 static const char* ident=unbound;
 #if defined(HAVE_SYSLOG_H) || defined(UB_ON_WINDOWS)
@@ -84,14 +88,19 @@
 	if(!key_created) {
 		key_created = 1;
 		ub_thread_key_create(logkey, NULL);
+		lock_quick_init(log_lock);
 	}
+	lock_quick_lock(log_lock);
 	if(logfile 
 #if defined(HAVE_SYSLOG_H) || defined(UB_ON_WINDOWS)
 	|| logging_to_syslog
 #endif
-	)
-	verbose(VERB_QUERY, switching log to %s, 
-		use_syslog?syslog:(filenamefilename[0]?filename:stderr));
+	) {
+		lock_quick_unlock(log_lock); /* verbose() needs the lock */
+		verbose(VERB_QUERY, switching log to %s, 
+			use_syslog?syslog:(filenamefilename[0]?filename:stderr));
+		lock_quick_lock(log_lock);
+	}
 	if(logfile  logfile != stderr)
 		fclose(logfile);
 #ifdef HAVE_SYSLOG_H
@@ -104,6 +113,7 @@
 		 * chroot and no longer be able to access dev/log and so on */
 		openlog(ident, LOG_NDELAY, LOG_DAEMON);
 		logging_to_syslog = 1;
+		lock_quick_unlock(log_lock);
 		return;
 	}
 #elif defined(UB_ON_WINDOWS)
@@ -112,11 +122,13 @@
 	}
 	if(use_syslog) {
 		logging_to_syslog = 1;
+		lock_quick_unlock(log_lock);
 		return;
 	}
 #endif /* HAVE_SYSLOG_H */
 	if(!filename || !filename[0]) {
 		logfile = stderr;
+		lock_quick_unlock(log_lock);
 		return;
 	}
 	/* open the file for logging */
@@ -125,6 +137,7 @@
 		filename += strlen(chrootdir);
 	f = fopen(filename, a);
 	if(!f) {
+		lock_quick_unlock(log_lock);
 		log_err(Could not open logfile %s: %s, filename, 
 			strerror(errno));
 		return;
@@ -134,11 +147,14 @@
 	setvbuf(f, NULL, (int)_IOLBF, 0);
 #endif
 	logfile = f;
+	lock_quick_unlock(log_lock);
 }
 
 void log_file(FILE *f)
 {
+	lock_quick_lock(log_lock);
 	logfile = f;
+	lock_quick_unlock(log_lock);
 }
 
 void log_thread_set(int* num)
@@ -207,7 +223,11 @@
 		return;
 	}
 #endif /* HAVE_SYSLOG_H */
-	if(!logfile) return;
+	lock_quick_lock(log_lock);
+	if(!logfile) {
+		lock_quick_unlock(log_lock);
+		return;
+	}
 	if(log_now)
 		now = (time_t)*log_now;
 	else	now = (time_t)time(NULL);
@@ -225,6 +245,7 @@
 	/* line buffering does not work on windows */
 	fflush(logfile);
 #endif
+	lock_quick_unlock(log_lock);
 }
 
 /**

Bug#753455: apt-cacher: doesn't allow x32 and arm64 packages

2014-07-04 Thread Mark Hindley

On Wed, Jul 02, 2014 at 05:59:08AM +0200, Adam Borowski wrote:
 Package: apt-cacher
 Version: 1.7.9.1
 Severity: normal
 
 With its default configuration, apt-cacher refuses to download packages for
 a bunch of new architectures, including x32, arm64 and others.

Thanks. I took the default list from https://www.debian.org/ports/. 

I can add arm64, powerpcspe, ppc64, sparc64 and x32 to the default 
list. Are you aware of any others?

Best 

Mark


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

Bug#753682: gummiboot: FTBFS with GCC 4.9 due to undefined va_copy in EFI binary

2014-07-04 Thread Julian Andres Klode

Package: gummiboot
Version: 44-1
Severity: serious

gummiboot's EFI binary fails to build from source with GCC 4.9

gcc  -I. -include config.h -I/usr/include/efi -I/usr/include/efi/x86_64 
-DMACHINE_TYPE_NAME=\x64\  -Wall -Wextra -nostdinc -ggdb -O0 -fpic 
-fshort-wchar -nostdinc -ffreestanding -fno-strict-aliasing 
-fno-stack-protector -Wsign-compare -mno-sse -mno-mmx -mno-red-zone 
-DEFI_FUNCTION_WRAPPER -DGNU_EFI_USE_MS_ABI -c src/efi/util.c -o src/efi/util.o
gcc  -I. -include config.h -I/usr/include/efi -I/usr/include/efi/x86_64 
-DMACHINE_TYPE_NAME=\x64\  -Wall -Wextra -nostdinc -ggdb -O0 -fpic 
-fshort-wchar -nostdinc -ffreestanding -fno-strict-aliasing 
-fno-stack-protector -Wsign-compare -mno-sse -mno-mmx -mno-red-zone 
-DEFI_FUNCTION_WRAPPER -DGNU_EFI_USE_MS_ABI -c src/efi/console.c -o 
src/efi/console.o
gcc  -I. -include config.h -I/usr/include/efi -I/usr/include/efi/x86_64 
-DMACHINE_TYPE_NAME=\x64\  -Wall -Wextra -nostdinc -ggdb -O0 -fpic 
-fshort-wchar -nostdinc -ffreestanding -fno-strict-aliasing 
-fno-stack-protector -Wsign-compare -mno-sse -mno-mmx -mno-red-zone 
-DEFI_FUNCTION_WRAPPER -DGNU_EFI_USE_MS_ABI -c src/efi/graphics.c -o 
src/efi/graphics.o
gcc  -I. -include config.h -I/usr/include/efi -I/usr/include/efi/x86_64 
-DMACHINE_TYPE_NAME=\x64\  -Wall -Wextra -nostdinc -ggdb -O0 -fpic 
-fshort-wchar -nostdinc -ffreestanding -fno-strict-aliasing 
-fno-stack-protector -Wsign-compare -mno-sse -mno-mmx -mno-red-zone 
-DEFI_FUNCTION_WRAPPER -DGNU_EFI_USE_MS_ABI -c src/efi/gummiboot.c -o 
src/efi/gummiboot.o
ld  -T /usr/lib/elf_x86_64_efi.lds -shared -Bsymbolic -nostdlib -znocombreloc 
-L /usr/lib /usr/lib/crt0-efi-x86_64.o ./src/efi/util.o ./src/efi/console.o 
./src/efi/graphics.o ./src/efi/gummiboot.o \
-o src/efi/gummiboot.so -lefi -lgnuefi 
/usr/lib/gcc/x86_64-linux-gnu/4.9/libgcc.a; \
nm -D -u src/efi/gummiboot.so | grep ' U '  exit 1 || :
 U va_copy
make[2]: *** [src/efi/gummiboot.so] Error 1
Makefile:1037: recipe for target 'src/efi/gummiboot.so' failed


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

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

Versions of packages gummiboot depends on:
ii  libblkid1  2.20.1-5.8
ii  libc6  2.19-3

Versions of packages gummiboot recommends:
ii  systemd  204-10

gummiboot suggests no packages.

-- Configuration Files:
/etc/default/gummiboot changed [not included]

-- no debconf information

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

Be friendly, do not top-post, and follow RFC 1855 Netiquette.
- If you don't I might ignore you.


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

Bug#753641: ITP: liblinux-pid-perl -- wrapper around the getpid() and getppid() C functions

On Fri, 04 Jul 2014 10:09:12 +0200, Guillem Jover wrote:

  * Package name: liblinux-pid-perl
Version : 0.04
Upstream Author : Rafael Garcia-Suarez r...@consttype.org
  * URL : https://metacpan.org/release/Linux-Pid
  * License : Artistic or GPL-1+
Programming Lang: Perl
Description : wrapper around the getpid() and getppid() C functions
  
  Perl already returns the PID and PPID in variables and builtins. Linux::Pid
  forces perl to call the underlying C functions getpid() and getppid().
  
  This is useful with multithreaded programs. Linux' C library, using the 
  Linux
  thread model, returns different values of the PID and the PPID from 
  different
  threads.
 
 With glibc and NPTL this module does not seem to make much sense, as
 each different thread will have the same PID. If it was exposing the
 Linux gettid() syscall then it would be the modern equivalent, but
 that depends on the assumptions from the call sites and the expected
 threading model, I suppose.
 
 I guess this is just a dependency from something else? Why not patch
 it to use the native perl functions instead?

Right, as noted in the third paragraph of the description, mod_perl
wants it:
https://bugs.debian.org/684290
https://lists.debian.org/debian-perl/2014/07/msg2.html ff.


Cheers,
gregor, not opposed to a mod_perl patch as an alternative

-- 
 .''`.  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: Peter Ratzenbeck: Flowers from Ayako


signature.asc
Description: Digital Signature

Bug#753171: FTBFS: /usr/bin/ld: cannot find -lee

2014-07-04 Thread Michael Biebl

Am 04.07.2014 10:10, schrieb Emilio Pozuelo Monfort:
 On 29/06/14 20:16, Michael Biebl wrote:
 Source: sagan
 Version: 0.2.1.r1-1
 Severity: serious

 Due to the latest updates in liblognorm, sagan now FTBFS

 configure:2701: checking whether the C compiler works
 configure:2723: gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4
 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wl,-z,relro
 conftest.c -lm -lestr -lee 5
 /usr/bin/ld: cannot find -lee
 collect2: error: ld returned 1 exit status

 Full build log is attached.

 Due to the changes in liblognorm, the liblognorm-dev package no longer
 depends on libee-dev.

 Simply adding libee-dev to Build-Depends was not sufficient, due to a
 bug in libestmp [1]
 
 libestmp got fixed. Is adding libee-dev enough now?

No, unfortunately not.
As I wrote in the bug report, sagan's configure needs to use pkg-config
proper to get all necessary compiler and linker flags.
Without them it will fail to find the json header files.

Even when this is fixed, I don't know if sagan already works with
liblognorm.

My suggestion would be to RM it from testing.


-- 
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#753683: tracker.debian.org: '1 bug tagged help in the BTS', but no bug is open

2014-07-04 Thread Andreas Cadhalpun


Package: tracker.debian.org
Severity: normal

Dear maintainer,

thanks for the new package tracker. ;)

Looking at [1] I find it strange, that it says:
'1 bug tagged help in the BTS'
While at the same time there is no open bug and indeed clicking on the 
'1 bug' link leads to [2] without a bug.


Probably the tracker finds #591881 and doesn't realize that this is 
already closed.


Best regards,
Andreas


1: https://tracker.debian.org/pkg/ffmpeg
2: 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ffmpegtag=helppend-exc=done



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

Bug#753682: gummiboot: FTBFS with GCC 4.9 due to undefined va_copy in EFI binary

2014-07-04 Thread Julian Andres Klode

Control: reassign -1 gnu-efi 3.0v-2

On Fri, Jul 04, 2014 at 12:11:30PM +0200, Julian Andres Klode wrote:
 Package: gummiboot
 Version: 44-1
 Severity: serious
 
 gummiboot's EFI binary fails to build from source with GCC 4.9
 
 gcc  -I. -include config.h -I/usr/include/efi -I/usr/include/efi/x86_64 
 -DMACHINE_TYPE_NAME=\x64\  -Wall -Wextra -nostdinc -ggdb -O0 -fpic 
 -fshort-wchar -nostdinc -ffreestanding -fno-strict-aliasing 
 -fno-stack-protector -Wsign-compare -mno-sse -mno-mmx -mno-red-zone 
 -DEFI_FUNCTION_WRAPPER -DGNU_EFI_USE_MS_ABI -c src/efi/util.c -o 
 src/efi/util.o
 gcc  -I. -include config.h -I/usr/include/efi -I/usr/include/efi/x86_64 
 -DMACHINE_TYPE_NAME=\x64\  -Wall -Wextra -nostdinc -ggdb -O0 -fpic 
 -fshort-wchar -nostdinc -ffreestanding -fno-strict-aliasing 
 -fno-stack-protector -Wsign-compare -mno-sse -mno-mmx -mno-red-zone 
 -DEFI_FUNCTION_WRAPPER -DGNU_EFI_USE_MS_ABI -c src/efi/console.c -o 
 src/efi/console.o
 gcc  -I. -include config.h -I/usr/include/efi -I/usr/include/efi/x86_64 
 -DMACHINE_TYPE_NAME=\x64\  -Wall -Wextra -nostdinc -ggdb -O0 -fpic 
 -fshort-wchar -nostdinc -ffreestanding -fno-strict-aliasing 
 -fno-stack-protector -Wsign-compare -mno-sse -mno-mmx -mno-red-zone 
 -DEFI_FUNCTION_WRAPPER -DGNU_EFI_USE_MS_ABI -c src/efi/graphics.c -o 
 src/efi/graphics.o
 gcc  -I. -include config.h -I/usr/include/efi -I/usr/include/efi/x86_64 
 -DMACHINE_TYPE_NAME=\x64\  -Wall -Wextra -nostdinc -ggdb -O0 -fpic 
 -fshort-wchar -nostdinc -ffreestanding -fno-strict-aliasing 
 -fno-stack-protector -Wsign-compare -mno-sse -mno-mmx -mno-red-zone 
 -DEFI_FUNCTION_WRAPPER -DGNU_EFI_USE_MS_ABI -c src/efi/gummiboot.c -o 
 src/efi/gummiboot.o
 ld  -T /usr/lib/elf_x86_64_efi.lds -shared -Bsymbolic -nostdlib -znocombreloc 
 -L /usr/lib /usr/lib/crt0-efi-x86_64.o ./src/efi/util.o ./src/efi/console.o 
 ./src/efi/graphics.o ./src/efi/gummiboot.o \
   -o src/efi/gummiboot.so -lefi -lgnuefi 
 /usr/lib/gcc/x86_64-linux-gnu/4.9/libgcc.a; \
 nm -D -u src/efi/gummiboot.so | grep ' U '  exit 1 || :
  U va_copy
 make[2]: *** [src/efi/gummiboot.so] Error 1
 Makefile:1037: recipe for target 'src/efi/gummiboot.so' failed
 

This is a regression from the fix for #747158 in gnu-efi

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

Be friendly, do not top-post, and follow RFC 1855 Netiquette.
- If you don't I might ignore you.


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

Bug#752075: daemontools-run: Add systemd support

2014-07-04 Thread Russ Allbery

Gerrit Pape p...@dbnbgs.smarden.org writes:

 I looked into latest policy, but did not find anything about systemd
 support.  I'm surprised that this is now a release critical bug, and the
 package marked for removal.  What's the justification?

I'm very dubious about this being release-critical.

 This package hooks into /etc/inittab, does systemd not automatically
 manage services from inittab?

Correct, systemd doesn't use inittab.

 Isn't it systemd having release critical bug then?

I don't think it's likely that systemd will support inittab.  The
semantics of inittab are quite a bit inferior to what's available with
very little additional work using the native configuration format, and the
regular inittab jobs are provided by regularly-configured services.  Yes,
that is a disruptive change for people who were using inittab to run other
things.

-- 
Russ Allbery (r...@debian.org)   http://www.eyrie.org/~eagle/


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

Bug#753684: ifupdown: Dead symlinks in /etc/network/if-pre-up.d block networking

2014-07-04 Thread Matthias Urlichs

Package: ifupdown
Version: 0.7.48.1
Severity: serious
Justification: Policy 10.7 (?)

# ln -s /not/an/existing/file /etc/network/if-pre-up.d/buggy
# ifup eth0
[ one error message and no networking ]

… which is fun if you remote-admin something.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'stable'), (600, 'unstable'), (550, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-rc7-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 ifupdown depends on:
ii  adduser  3.113+nmu3
ii  initscripts  2.88dsf-53.2
ii  iproute  1:3.15.0-2
ii  iproute2 3.15.0-2
ii  libc62.19-4
ii  lsb-base 4.1+Debian13

Versions of packages ifupdown recommends:
ii  isc-dhcp-client [dhcp-client]  4.2.4-7

Versions of packages ifupdown suggests:
ii  net-tools  1.60-26
ii  ppp2.4.6-2
pn  rdnssd 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#753685: dist-packages/paraview/ColorMaps.xml missing

2014-07-04 Thread Sylwester Arabas


Package: paraview-python

Hello,

After installing current sid paraview-python, each call to 
LoadLookupTable(), regardless if the argument is valid or not, gives a 
warning about missing ColorMaps.xml file:


$ pvpython --version
paraview version 4.1.0


$ cat bug.py
from paraview.simple import *
LoadLookupTable('')


$ pvpython bug.py
WARNING: default LUTs not found at 
/usr/lib/python2.7/dist-packages/paraview/ColorMaps.xml



HTH, best regards,
Sylwester


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

Bug#753686: squeeze-pu: package mobile-broadband-provider-info/20140317-1~deb6u1

2014-07-04 Thread Raphael Geissert

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

Hi,

Similar to #750757, but for squeeze. The idea would be to give some
fresh air to the package that hasn't been updated in four years,
before no more updates are made to squeeze.

Will be sending the debdiff later today. Actual packaging difference
to make the backport is a downgrade of debhelper compat level (and the
b-d) from 9 to 8.

TIA and apologies for sending the mail until now.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net


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

Bug#753370: pu: package intel-microcode/1.20140624.1

2014-07-04 Thread Henrique de Moraes Holschuh

On Fri, 04 Jul 2014, Adam D. Barratt wrote:
 Control: tags -1 + pending
 On 2014-07-01 11:25, Henrique de Moraes Holschuh wrote:
 On Tue, 01 Jul 2014, Adam D. Barratt wrote:
 On Mon, 2014-06-30 at 21:15 -0300, Henrique de Moraes Holschuh wrote:
  Please approve a fast-track upload of intel-microcode to non-free stable
  (Wheezy).
 [...]
 Please go ahead; thanks.
 
 Uploaded.   Thank you very much!
 
 (slightly belatedly) flagged for acceptance; thanks.

Thank you!

-- 
  One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie. -- The Silicon Valley Tarot
  Henrique Holschuh


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

Bug#753687: nautilus: Nautilus-window in fullscreen-mode is diffcult to un-maximise, titlebar-contextmenu is missing

2014-07-04 Thread Andreas Glaeser

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: nautilus
Version: 3.8.2-3
Severity: normal

Dear Maintainer,

I have not been using Gnome here on my testing-box for quite some time now 
because of the
nautilus file-manager. It used to start up with a maximised window and took the 
whole
screen and was very difficult to un-maximise. When trying Gnome-classic today, 
this worked
suddenly, there showed to be a very small margin at the top of the 
window-titlebar, where
one can doubleclick in order to unmaximise the nautilus-window. Once it is 
un-maximised,
then the context-menu of the titlebar is also visible again, containing items 
like
'Minimise','Maximise','Move' and so on. Gnome-classic seems to perform worse 
than a
normal Gnome-session, it seems to have lots of latencies when opening, moving 
and
resizing windows. Please have the nautilus-window behave like one would expect 
and
re-enable the titlebar-context-menu also in maximised mode.

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

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

Versions of packages nautilus depends on:
ii  desktop-file-utils 0.22-1
ii  gsettings-desktop-schemas  3.8.2-2
ii  gvfs   1.20.2-1
ii  libatk1.0-02.12.0-1
ii  libc6  2.19-4
ii  libcairo-gobject2  1.12.16-2
ii  libcairo2  1.12.16-2
ii  libexempi3 2.2.1-2
ii  libexif12  0.6.21-1
ii  libgail-3-03.12.2-1+b1
ii  libgdk-pixbuf2.0-0 2.30.7-1
ii  libglib2.0-0   2.40.0-3
ii  libglib2.0-data2.40.0-3
ii  libgnome-desktop-3-7   3.8.4-2
ii  libgtk-3-0 3.12.2-1+b1
ii  libnautilus-extension1a3.8.2-3
ii  libnotify4 0.7.6-2
ii  libpango-1.0-0 1.36.3-1
ii  libpangocairo-1.0-01.36.3-1
ii  libselinux12.3-1
ii  libtracker-sparql-1.0-01.0.1-2
ii  libx11-6   2:1.6.2-2
ii  libxml22.9.1+dfsg1-3
ii  nautilus-data  3.8.2-3
ii  shared-mime-info   1.3-1

Versions of packages nautilus recommends:
ii  eject  2.1.5+deb1+cvs20081104-13.1
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  gnome-sushi3.10.0-1+b1
ii  gvfs-backends  1.20.2-1
ii  librsvg2-common2.40.2-1

Versions of packages nautilus suggests:
ii  brasero3.10.0-1
ii  eog3.12.0-1
ii  evince [pdf-viewer]3.12.1-1
ii  totem  3.12.1-1
ii  tracker1.0.1-2
ii  vlc [mp3-decoder]  2.1.4-1+b2
ii  vlc-nox [mp3-decoder]  2.1.4-1+b2
ii  xdg-user-dirs  0.15-1

- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlO2hy8ACgkQ5+rBHyUt5wvZqwCfbfg53nORpzroI07wT3ujZMK5
5wYAn3JrwP5QxOnJwzVgx5/XcDRDSCkv
=+u+C
-END PGP SIGNATURE-

Bug#751047: nss-pam-ldapd: [INTL:pt] Portuguese translation for debconf messages

On Tue, 2014-06-10 at 22:06 +0200, Arthur de Jong wrote:
 Control: tags -1 + pending
 
 On Mon, 2014-06-09 at 20:32 +0100, Américo Monteiro wrote:
  Updated Portuguese translation for nss-pam-ldapd's debconf messages.
  Translator: Américo Monteiro a_monte...@gmx.com
  Feel free to use it.
  
  For translation updates please contact 'Last Translator' or the
  Portuguese Translation Team traduz at debianpt.org.
 
 Thanks for the updated translation, it will be in the next upload.
 
 I expect to ask the English language list for a review of the templates
 and I also expect the addition of one more template so there may be
 another update coming in the near future (that's why I didn't call for
 translations yet).

I haven't gotten around to asking the English language list but another
template was added. Please see the attached .po file.

I would be grateful if you could take the time to update it.

Thanks,

-- 
-- arthur - adej...@debian.org - http://people.debian.org/~adejong --
# Translation of nss-pam-ldapd debconf to Portuguese.
# Copyright (C) 2007 the nss-pam-ldapd's copyright holder
# This file is distributed under the same license as the nss-pam-ldapd package.
#
# Translators:
#
# Américo Monteiro a_monte...@gmx.com, 2007 - 2014.
msgid 
msgstr 
Project-Id-Version: nss-pam-ldapd 0.9.4-1\n
Report-Msgid-Bugs-To: nss-pam-ld...@packages.debian.org\n
POT-Creation-Date: 2014-06-08 11:45+0200\n
PO-Revision-Date: 2014-06-09 20:28+0100\n
Last-Translator: Américo Monteiro a_monte...@gmx.com\n
Language-Team: Portuguese tra...@debianpt.org\n
Language: pt\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
X-Generator: Lokalize 1.4\n
Plural-Forms: nplurals=2; plural=(n != 1);\n

#. Type: string
#. Description
#: ../nslcd.templates:1001
msgid LDAP server URI:
msgstr URI do servidor LDAP:

#. Type: string
#. Description
#: ../nslcd.templates:1001
msgid 
Please enter the Uniform Resource Identifier of the LDAP server. The format 
is \ldap://hostname_or_IP_address:port/\. Alternatively, \ldaps://\ 
or \ldapi://\ can be used. The port number is optional.
msgstr 
Por favor insira o Uniform Resource Identifier do servidor LDAP. O formato é 
'ldap://nome_da_máquina_ou_endereço_IP:porto/'. Alternativamente, pode 
ser usado 'ldaps://' ou 'ldapi://'. O número do porto é opcional.

#. Type: string
#. Description
#: ../nslcd.templates:1001
msgid 
When using an ldap or ldaps scheme it is recommended to use an IP address to 
avoid failures when domain name services are unavailable.
msgstr 
Quando se usa um esquema ldap ou ldaps é recomendado usar endereços IP para 
evitar falhas quando os serviços de nomes de domínio não estão disponíveis.

#. Type: string
#. Description
#: ../nslcd.templates:1001
msgid Multiple URIs can be separated by spaces.
msgstr Múltiplos URIs podem ser separados por espaços.

#. Type: string
#. Description
#: ../nslcd.templates:2001
msgid LDAP server search base:
msgstr Base de busca do servidor LDAP:

#. Type: string
#. Description
#: ../nslcd.templates:2001
msgid 
Please enter the distinguished name of the LDAP search base. Many sites use 
the components of their domain names for this purpose. For example, the 
domain \example.net\ would use \dc=example,dc=net\ as the distinguished 
name of the search base.
msgstr 
Por favor insira o nome distinto da base de busca LDAP. Muitos sítios usam 
componentes dos seus nomes de domínio para este propósito. Por exemplo, o 
domínio \exemplo.net\ deverá usar \dc=exemplo,dc=net\ como nome distinto 
da base de busca.

#. Type: select
#. Choices
#: ../nslcd.templates:3001
msgid none
msgstr nenhum

#. Type: select
#. Choices
#: ../nslcd.templates:3001
msgid simple
msgstr simples

#. Type: select
#. Choices
#: ../nslcd.templates:3001
msgid SASL
msgstr SASL

#. Type: select
#. Description
#: ../nslcd.templates:3002
msgid LDAP authentication to use:
msgstr Autenticação LDAP a usar:

#. Type: select
#. Description
#: ../nslcd.templates:3002
msgid 
Please choose what type of authentication the LDAP database should require 
(if any):
msgstr 
Por favor escolha que tipo de autenticação a base de dados LDAP deverá pedir 
(se algum):

#. Type: select
#. Description
#: ../nslcd.templates:3002
msgid 
 * none: no authentication;\n
 * simple: simple bind DN and password authentication;\n
 * SASL: any Simple Authentication and Security Layer mechanism.
msgstr 
 * nenhum: nenhuma autenticação;\n
 * simples: ligação DN simples e autenticação por palavra-passe;\n
 * SASL: qualquer mecanismo Simple Authentication e Security Layer.

#. Type: string
#. Description
#: ../nslcd.templates:4001
msgid LDAP database user:
msgstr Utilizador da base de dados LDAP:

#. Type: string
#. Description
#: ../nslcd.templates:4001
msgid 
Please enter the name of the account that will be used to log in to the LDAP 
database. This value should be specified as a DN (distinguished name).
msgstr 
Por favor indique o nome da conta que irá ser usada para login na

Bug#751100: nss-pam-ldapd: [INTL:fr] French debconf templates translation update

On Tue, 2014-06-10 at 22:38 +0200, Arthur de Jong wrote:
I expect the addition of one more template soon and I may ask the
l10n-english list for a review of some of the new templates. Because I
expect some more changes in the near future I haven't sent out a call
for translations yet.

I haven't gotten around to asking the English language list but another
template was added. Please see the attached .po file.

I would be grateful if you could take the time to update it.

Thanks,

--
-- arthur - adej...@debian.org - http://people.debian.org/~adejong --
# Translation of nss-pam-ldapd debconf templates to French.
# Copyright (C) 2007, 2009, 2010 Debian French l10n team debian-l10n-fre...@lists.debian.org
# This file is distributed under the same license as the nss-pam-ldapd package.
#
# Translators:
#
# Cyril Brulebois cyril.bruleb...@enst-bretagne.fr, 2007.
# Philippe Batailler philippe.batail...@free.fr, 2007.
# Guillaume Delacour g...@iroqwa.org, 2009.
# Christian Perrier bubu...@debian.org, 2009, 2010, 2011, 2013, 2014.
msgid
msgstr
Project-Id-Version: nss-pam-ldapd 0.9.1-2\n
Report-Msgid-Bugs-To: nss-pam-ld...@packages.debian.org\n
POT-Creation-Date: 2014-06-08 11:45+0200\n
PO-Revision-Date: 2014-06-10 07:19+0200\n
Last-Translator: Christian Perrier bubu...@debian.org\n
Language-Team: French debian-l10n-fre...@lists.debian.org\n
Language: fr\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
X-Generator: Lokalize 1.5\n
Plural-Forms: nplurals=2; plural=(n 1);\n

#. Type: string
#. Description
#: ../nslcd.templates:1001
msgid LDAP server URI:
msgstr URI du serveur LDAP :

#. Type: string
#. Description
#: ../nslcd.templates:1001
msgid
Please enter the Uniform Resource Identifier of the LDAP server. The format
is \ldap://hostname_or_IP_address:port/\. Alternatively, \ldaps://\
or \ldapi://\ can be used. The port number is optional.
msgstr
Veuillez indiquer l'URI (« Uniform Resource Identifier ») du serveur LDAP à
utiliser. Il s'agit d'une adresse de la forme « ldap://nom de machine ou
IP:port/ ». Des adresses sous la forme « ldaps:// » et « ldapi:// »
peuvent aussi être utilisées. Le numéro de port est facultatif.

#. Type: string
#. Description
#: ../nslcd.templates:1001
msgid
When using an ldap or ldaps scheme it is recommended to use an IP address to
avoid failures when domain name services are unavailable.
msgstr
Lorsque le protocole utilisé est « ldap » ou « ldaps », il est recommandé
d'utiliser une adresse IP plutôt qu'un nom d'hôte afin de réduire les
risques d'échec en cas d'indisponibilité du service de noms.

#. Type: string
#. Description
#: ../nslcd.templates:1001
msgid Multiple URIs can be separated by spaces.
msgstr
Des adresses multiples peuvent être indiquées, séparées par des espaces.

#. Type: string
#. Description
#: ../nslcd.templates:2001
msgid LDAP server search base:
msgstr Base de recherche du serveur LDAP :

#. Type: string
#. Description
#: ../nslcd.templates:2001
msgid
Please enter the distinguished name of the LDAP search base. Many sites use
the components of their domain names for this purpose. For example, the
domain \example.net\ would use \dc=example,dc=net\ as the distinguished
name of the search base.
msgstr
Veuillez indiquer le nom distinctif (« DN ») de la base de recherche du
serveur LDAP. Beaucoup de sites utilisent les éléments composant leur nom de
domaine à cette fin. Par exemple, le domaine « example.net » utiliserait
« dc=example,dc=net ».

#. Type: select
#. Choices
#: ../nslcd.templates:3001
msgid none
msgstr aucune

#. Type: select
#. Choices
#: ../nslcd.templates:3001
msgid simple
msgstr simple

#. Type: select
#. Choices
#: ../nslcd.templates:3001
msgid SASL
msgstr SASL

#. Type: select
#. Description
#: ../nslcd.templates:3002
msgid LDAP authentication to use:
msgstr Authentification LDAP :

#. Type: select
#. Description
#: ../nslcd.templates:3002
msgid
Please choose what type of authentication the LDAP database should require
(if any):
msgstr
Veuillez choisir le type d'authentification que la base LDAP utilise (si
nécessaire).

#. Type: select
#. Description
#: ../nslcd.templates:3002
msgid
* none: no authentication;\n
* simple: simple bind DN and password authentication;\n
* SASL: any Simple Authentication and Security Layer mechanism.
msgstr
- aucune : pas d'authentification;\n
- simple : authentification simple avec un identifiant (DN) et un\n
mot de passe;\n
- SASL : mécanisme basé sur SASL (« Simple Authentication and\n
Security Layer ») : méthode simplifiée d'authentification\n
et de sécurité;

#. Type: string
#. Description
#: ../nslcd.templates:4001
msgid LDAP database user:
msgstr Utilisateur de la base LDAP :

Bug#748752: Reopened

2014-07-04 Thread Andreas Glaeser

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sat, 28 Jun 2014 10:09:56 -0500
David Smith sidic...@gmail.com wrote:

 On 06/24/2014 08:41 AM, Andreas Glaeser wrote:
  
  The problem seemed to be solved, but in fact is is not, the
  situation with liferea is
  
  unchanged, so the report was reopened.
  
 
 Can you make sure you have dbus-x11 installed and if not, install it
 and see if the problem persists? I'm adding a depend on dbus-x11 to
 close out #748087 and it might fix this issue as well. That's just a
 guess since I saw in your bug report that you were getting warnings
 about not being able to register with the accessibility bus.
 
 -David
 

Yes dbus-x11 package is installed, I recently re-installed the whole system, so
everything should be pretty much in factory-default state.

andrew@s5:~$ aptitude show dbus-x11
Package: dbus-x11
State: installed
Automatically installed: yes
Multi-Arch: foreign
Version: 1.8.4-1
Priority: optional
Section: x11
Maintainer: Utopia Maintenance Team 
pkg-utopia-maintain...@lists.alioth.debian.org
Architecture: amd64
Uncompressed Size: 98.3 k
Depends: libc6 (= 2.15), libx11-6, dbus
Breaks: x11-common ( 1:7.5+4)
Description: simple interprocess messaging system (X11 deps)
 D-Bus is a message bus, used for sending messages between applications. 
Conceptually, it
fits somewhere in between raw sockets and CORBA in terms of complexity. 
 
 This package contains the dbus-launch utility which is necessary for packages 
using a
D-Bus session bus. 
 See the dbus description for more information about D-Bus in general.
Homepage: http://dbus.freedesktop.org/

Tags: devel::rpc, implemented-in::c, interface::daemon, protocol::TODO, 
role::program,
scope::utility

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlO2iGcACgkQ5+rBHyUt5wsz/gCfRw8NjjGrMAty3jxobV6C1ay+
fX4AniGzgK6EFrUQgNLqftiQgz5kCL0W
=fvZ9
-END PGP SIGNATURE-

Bug#752515: nss-pam-ldapd: [INTL:ja] New Japanese debconf translation

On Wed, 2014-07-02 at 23:22 +0200, Arthur de Jong wrote:
There is however another template that has recently been added and I am
considering asking the English language list for a review of the
templates that were added a while back (that's why I didn't call for
translations yet).

I haven't gotten around to asking the English language list but another
template was added. Please see the attached .po file.

I would be grateful if you could take the time to update it.

Thanks,

--
-- arthur - adej...@debian.org - http://people.debian.org/~adejong --
# Translation of nss-pam-ldapd debconf templates to Japanese.
#
msgid
msgstr
Project-Id-Version: nss-pam-ldapd 0.9.4-1\n
Report-Msgid-Bugs-To: nss-pam-ld...@packages.debian.org\n
POT-Creation-Date: 2014-06-08 11:45+0200\n
PO-Revision-Date: 2013-10-18 21:41+0900\n
Last-Translator: Kenshi Muto km...@debian.org\n
Language-Team: Japanese debian-japan...@lists.debian.org\n
Language: ja\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n

#. Type: string
#. Description
#: ../nslcd.templates:1001
msgid LDAP server URI:
msgstr LDAP サーバの URI:

#. Type: string
#. Description
#: ../nslcd.templates:1001
msgid
Please enter the Uniform Resource Identifier of the LDAP server. The format
is \ldap://hostname_or_IP_address:port/\. Alternatively, \ldaps://\
or \ldapi://\ can be used. The port number is optional.
msgstr
LDAP サーバの Uniform Resource Identifier を入力してください。形式は 'ldap://;
ホスト名または IP:ポート/' です。このほかに 'ldaps://' または 'ldapi://'
も利用できます。ポート番号は省略できます。

#. Type: string
#. Description
#: ../nslcd.templates:1001
msgid
When using an ldap or ldaps scheme it is recommended to use an IP address to
avoid failures when domain name services are unavailable.
msgstr
ldap または ldaps スキーマを使う際には、ネームサービスが利用できないときの障
害回避のために IP アドレスを使うことを推奨します。

#. Type: string
#. Description
#: ../nslcd.templates:1001
msgid Multiple URIs can be separated by spaces.
msgstr スペースで区切って、複数の URI を指定できます。

#. Type: string
#. Description
#: ../nslcd.templates:2001
msgid LDAP server search base:
msgstr LDAP サーバの検索ベース:

#. Type: string
#. Description
#: ../nslcd.templates:2001
msgid
Please enter the distinguished name of the LDAP search base. Many sites use
the components of their domain names for this purpose. For example, the
domain \example.net\ would use \dc=example,dc=net\ as the distinguished
name of the search base.
msgstr
LDAP 検索ベースの識別名を入力してください。多くのサイトではそのドメイン名の要
素をこの目的に使っています。たとえば、ドメイン \example.net\ では検索ベース
の識別名として \dc=example,dc=net\ を使っているでしょう。

#. Type: select
#. Choices
#: ../nslcd.templates:3001
msgid none
msgstr なし

#. Type: select
#. Choices
#: ../nslcd.templates:3001
msgid simple
msgstr simple

#. Type: select
#. Choices
#: ../nslcd.templates:3001
msgid SASL
msgstr SASL

#. Type: select
#. Description
#: ../nslcd.templates:3002
msgid LDAP authentication to use:
msgstr 使用する LDAP 認証:

#. Type: select
#. Description
#: ../nslcd.templates:3002
msgid
Please choose what type of authentication the LDAP database should require
(if any):
msgstr
LDAP データベースが (もし何か) 必要とすべき認証の形式を選択してください:

#. Type: select
#. Description
#: ../nslcd.templates:3002
msgid
* none: no authentication;\n
* simple: simple bind DN and password authentication;\n
* SASL: any Simple Authentication and Security Layer mechanism.
msgstr
* なし: 認証なし;\n
* simple: シンプルバインド DN とパスワード認証;\n
* SASL: 何らかの Simple Authentication and Security Layer 機構。

#. Type: string
#. Description
#: ../nslcd.templates:4001
msgid LDAP database user:
msgstr LDAP データベースユーザ:

#. Type: string
#. Description
#: ../nslcd.templates:4001
msgid
Please enter the name of the account that will be used to log in to the LDAP
database. This value should be specified as a DN (distinguished name).
msgstr
LDAP データベースへのログインに使われるアカウントの名前を入力してください。こ
の値は DN (識別名) として指定すべきです。

#. Type: password
#. Description
#: ../nslcd.templates:5001
msgid LDAP user password:
msgstr LDAP ユーザパスワード:

#. Type: password
#. Description
#: ../nslcd.templates:5001
msgid
Please enter the password that will be used to log in to the LDAP database.
msgstr LDAP データベースにログインするのに使うパスワードを入力してください。

#. Type: select
#. Description
#: ../nslcd.templates:6001
msgid SASL mechanism to use:
msgstr 使用する SASL 機構:

#. Type: select
#. Description
#: ../nslcd.templates:6001
msgid
Please choose the SASL mechanism that will be used to authenticate to the
LDAP database:
msgstr LDAP データベースを認証するのに使われる SASL 機構を選んでください:

#. Type: select
#. Description
#: ../nslcd.templates:6001
msgid
* auto: auto-negotiation;\n
* LOGIN: deprecated in favor of PLAIN;\n
* PLAIN: simple cleartext password mechanism;\n
* NTLM: NT LAN Manager authentication mechanism;\n
* CRAM-MD5: challenge-response scheme based on HMAC-MD5;\n
* DIGEST-MD5: HTTP Digest compatible challenge-response scheme;\n
* SCRAM: salted challenge-response mechanism;\n
* GSSAPI: used for Kerberos;\n
* SKEY: S/KEY mechanism (obsoleted by OTP);\n
* OTP: One Time Password mechanism;\n
* EXTERNAL:

Bug#752550: nss-pam-ldapd: [INTL:ru] Russian debconf templates translation update

On Wed, 2014-07-02 at 23:27 +0200, Arthur de Jong wrote:
There is however another template that has recently been added and I am
considering asking the English language list for a review of the
templates that were added a while back (that's why I didn't call for
translations yet).

I haven't gotten around to asking the English language list but another
template was added. Please see the attached .po file.

I would be grateful if you could take the time to update it.

Thanks,

--
-- arthur - adej...@debian.org - http://people.debian.org/~adejong --
# Translation of nss-pam-ldapd debconf templates to Russian.
#
# Translators:
#
# Debian Description Translation Project debc...@ddtp.debian.org, 2003.
# Ilgiz Kalmetev transla...@ilgiz.pp.ru, 2003.
# Yuri Kozlov yu...@komyakino.ru, 2009, 2010, 2011, 2013, 2014.
msgid
msgstr
Project-Id-Version: nss-pam-ldapd 0.9.4-1\n
Report-Msgid-Bugs-To: nss-pam-ld...@packages.debian.org\n
POT-Creation-Date: 2014-06-08 11:45+0200\n
PO-Revision-Date: 2014-06-24 19:16+0400\n
Last-Translator: Yuri Kozlov yu...@komyakino.ru\n
Language-Team: Russian debian-l10n-russ...@lists.debian.org\n
Language: ru\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
X-Generator: Lokalize 1.5\n
Plural-Forms: nplurals=3; plural=(n%10==1 n%100!=11 ? 0 : n%10=2 n
%10=4 (n%10010 || n%100=20) ? 1 : 2);\n

#. Type: string
#. Description
#: ../nslcd.templates:1001
msgid LDAP server URI:
msgstr URI сервера LDAP:

#. Type: string
#. Description
#: ../nslcd.templates:1001
msgid
Please enter the Uniform Resource Identifier of the LDAP server. The format
is \ldap://hostname_or_IP_address:port/\. Alternatively, \ldaps://\
or \ldapi://\ can be used. The port number is optional.
msgstr
Укажите универсальный индикатор ресурса (URI) сервера LDAP. Формат: «ldap://;
имя_узла или IP:порт/». Также можно использовать «ldaps://» или
«ldapi://». Номер порта необязателен.

#. Type: string
#. Description
#: ../nslcd.templates:1001
msgid
When using an ldap or ldaps scheme it is recommended to use an IP address to
avoid failures when domain name services are unavailable.
msgstr
При использовании схемы ldap или ldaps, обычно, лучше указывать IP-адрес;
это снижает риск появления проблем в случае отказа службы имён.

#. Type: string
#. Description
#: ../nslcd.templates:1001
msgid Multiple URIs can be separated by spaces.
msgstr Можно указывать несколько URI через пробел.

#. Type: string
#. Description
#: ../nslcd.templates:2001
msgid LDAP server search base:
msgstr База поиска сервера LDAP:

#
#. Type: string
#. Description
#: ../nslcd.templates:2001
msgid
Please enter the distinguished name of the LDAP search base. Many sites use
the components of their domain names for this purpose. For example, the
domain \example.net\ would use \dc=example,dc=net\ as the distinguished
name of the search base.
msgstr
Введите уникальное имя базы поиска LDAP. Для этой цели на многих серверах
используют части своих доменных имён. Например, для домена «example.net» в
качестве уникального имени базы поиска использовалось бы «dc=example,dc=net».

#. Type: select
#. Choices
#: ../nslcd.templates:3001
msgid none
msgstr отсутствует

#. Type: select
#. Choices
#: ../nslcd.templates:3001
msgid simple
msgstr простой

#. Type: select
#. Choices
#: ../nslcd.templates:3001
msgid SASL
msgstr SASL

#. Type: select
#. Description
#: ../nslcd.templates:3002
msgid LDAP authentication to use:
msgstr Используемый метод аутентификации LDAP:

#. Type: select
#. Description
#: ../nslcd.templates:3002
msgid
Please choose what type of authentication the LDAP database should require
(if any):
msgstr
Укажите, какой тип аутентификации нужно использовать для получения доступа к
базе данных LDAP (если нужно):

#. Type: select
#. Description
#: ../nslcd.templates:3002
msgid
* none: no authentication;\n
* simple: simple bind DN and password authentication;\n
* SASL: any Simple Authentication and Security Layer mechanism.
msgstr
* отсутствует: без аутентификации;\n
* простой: привязка DN и пароль;\n
* SASL:любой механизм простой аутентификацию и слоя безопасности.

#. Type: string
#. Description
#: ../nslcd.templates:4001
msgid LDAP database user:
msgstr Пользователь базы данных LDAP:

#. Type: string
#. Description
#: ../nslcd.templates:4001
msgid
Please enter the name of the account that will be used to log in to the LDAP
database. This value should be specified as a DN (distinguished name).
msgstr
Введите имя учетной записи, которая будет использована для подключения к
базе данных LDAP. Значение должно быть указано в форме DN (отличительного
имени).

#. Type: password
#. Description
#: ../nslcd.templates:5001
msgid LDAP user password:
msgstr Пароль пользователя LDAP:

#. Type: password
#. Description
#: ../nslcd.templates:5001
msgid
Please enter the password that will be used to log in to the LDAP database.
msgstr
Введите пароль, который будет использован для

Bug#753552: elfutils: FTBFS on arm64 (test failed)

2014-07-04 Thread Petr Machata

Mark Wielaard m...@redhat.com writes:

 diff --git a/backends/aarch64_retval.c b/backends/aarch64_retval.c
 index 0ed7d56..68de307 100644
 --- a/backends/aarch64_retval.c
 +++ b/backends/aarch64_retval.c
 @@ -357,6 +357,7 @@ aarch64_return_value_location (Dwarf_Die
 *functypedie, const Dwarf_Op **locp)
  size of the argument is less than or equal to 8 bytes
  [...] the argument is copied to the least significant
  bits in x[NGRN].  */
 +   case DW_ATE_boolean:
 case DW_ATE_signed:
 case DW_ATE_unsigned:
 case DW_ATE_unsigned_char:

That looks reasonable to me.

Thanks,
P.


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

Bug#753688: homepage field 404

2014-07-04 Thread Gürkan Sengün


Package: qfits-tools
Version: 6.2.0-5
Severity: wishlist

Please update the Homepage field (currently 404), probably should be:
https://www.eso.org/sci/software/eclipse/qfits/

Thank you
Gürkan


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

Bug#752075: daemontools-run: Add systemd support

2014-07-04 Thread Joern Heissler

Hi,

On Fri, Jul 04, 2014 at 09:08:21AM +, Gerrit Pape wrote:
 This package hooks into /etc/inittab, does systemd not automatically
 manage services from inittab?  Isn't it systemd having release critical

For clarity: daemontools-run does *not* include a file in /etc/init.d/
which systemd might use, instead it adds this line to /etc/inittab:
SV:123456:respawn:/usr/bin/svscanboot

systemd's source doesn't even include the word inittab and I wouldn't
expect it to. I don't think that it's systemd's fault.

 I looked into latest policy, but did not find anything about systemd
 support.  I'm surprised that this is now a release critical bug, and the
 package marked for removal.  What's the justification?

With the current stable (wheezy) this package works for most users.

I assume that the next stable release, Jessie, will use systemd by
default: https://lists.debian.org/debian-ctte/2014/02/msg00405.html

So upon release, when this bug is not fixed yet, the package becomes
useless for most users.
makes the package in question unusable hence I choose grave as severity.

I was actually tempted to mark it critical. makes … the whole system … 
break.
Because that's what happens for me. Upon reboot, there's no working DNS
resolution (nameserver 127.0.0.1, using djbdns).
But I assume that this setup is not very common.

Now I'm wondering about a few things:
* Can I only choose a release-critical severity for bugs affecting the
  current stable but not the next stable?
* Is there documentation clearly describing this?
* If I want to use djb's dnscache, is it the correct way to
  install daemontools and daemontools-run, or is there any better way?

My knowledge of Debian's policies is limited, so if you believe that my
reasoning above is flawed, please point me to the relevant sections of
the docs.

Cheers
Joern


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

Bug#753689: New Upstream Release

2014-07-04 Thread Mark Purcell

Source: libopencv-dev
Severity: wishlist

Hi,

Upstream releved opencv 2.4.9 on 25 Apr 14:
http://opencv.org/opencv-2-4-9-is-out.html

digikam/4.1.0 now depends on that version to build libkface:

-- Starting CMake configuration for: libkface
-- Found Qt-Version 4.8.6 (using /usr/bin/qmake)
-- Found X11: /usr/lib/i386-linux-gnu/libX11.so
-- First try at finding OpenCV...
-- Great, found OpenCV on the first try.
-- OpenCV Root directory is: /usr/share/OpenCV
-- OpenCV: Found version 2.4.8 (required: 2.4.9)
CMake Warning at extra/libkface/CMakeLists.txt:78 (MESSAGE):
  OpenCV: Version is too old.


CMake Error at extra/libkface/CMakeLists.txt:162 (MESSAGE):
  LibKface cannot be compiled.

I would be greatful if you could progress the new upstream release into
Debian.

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

Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.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#752075: daemontools-run: Add systemd support

2014-07-04 Thread Gerrit Pape

Hi Joern, you did nothing wrong.  Severity and justification looks quite
right to me.

On Fri, Jul 04, 2014 at 12:42:43PM +0200, Joern Heissler wrote:
 On Fri, Jul 04, 2014 at 09:08:21AM +, Gerrit Pape wrote:
  I looked into latest policy, but did not find anything about systemd
  support.  I'm surprised that this is now a release critical bug, and the
  package marked for removal.  What's the justification?
 
 With the current stable (wheezy) this package works for most users.
 
 I assume that the next stable release, Jessie, will use systemd by
 default: https://lists.debian.org/debian-ctte/2014/02/msg00405.html
 
 So upon release, when this bug is not fixed yet, the package becomes
 useless for most users.
 makes the package in question unusable hence I choose grave as severity.

Yep, fully understandable from you POV, thanks for filing the bug.

 * Can I only choose a release-critical severity for bugs affecting the
   current stable but not the next stable?

Bug reporters are free to choose any severity they think applies.  It's
the maintainer setting it straight if she doesn't agree.

I'm just asking debian-devel how to resolve this.  I heard systemd is
backward-compatible to sysvinit, but looks like this doesn't apply to
the inittab interface.

Regards, Gerrit


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

Bug#753690: pbuilder: ccache handling broken after SUTOUSER / CCACHE_ENV changes in 0.215+nmu1

Package: pbuilder
Version: 0.215+nmu1
Severity: normal
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

After upgrading to 0.215+nmu1, pbuilder tells me various times during
a build:

ccache: failed to create /var/cache/pbuilder/ccacheLD_PRELOAD= (Permission 
denied)
dpkg-architecture: warning: Couldn't determine gcc system type, falling back to 
default (native compilation)

Adding a 'set -x' into /usr/lib/pbuilder/pbuilder-buildpackage shows:

I: Setting up ccache
+ SUTOUSER='/usr/bin/unshare -n --  env 
CCACHE_DIR=/var/cache/pbuilder/ccacheLD_PRELOAD= LOGNAME=pbuilder 
/sbin/start-stop-daemon --start --pidfile /dev/null --chuid pbuilder --startas 
/bin/sh'

Looks like a missing space ...

And indeed, either of the two following options work:

Change
SUTOUSER=${SUTOUSER/ env / env $CCACHE_ENV}
to
SUTOUSER=${SUTOUSER/ env / env $CCACHE_ENV }
in /usr/lib/pbuilder/pbuilder-buildpackage, line 118

or change
CCACHE_ENV=CCACHE_DIR=$CCACHEDIR
to
CCACHE_ENV=CCACHE_DIR=$CCACHEDIR 
in /usr/lib/pbuilder/pbuilder-buildpackage-funcs, line 110.


Cheers,
gregor


-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJrBAEBCgBVBQJTtov4ThSAAB0AKGlzc3Vlci1mcHJAZ3BnLmNvbW9kby5w
cml2LmF0RDFFMTMxNkU5M0E3NjBBODEwNEQ4NUZBQkIzQTY4MDE4NjQ5QUEwNgAK
CRC7OmgBhkmqBjJ+EAClN9YeYLzV00QCJmfeMIuufQcm0+nNAaRMoZpdRs8Ugix4
cIQbcdaPRVz1K1ivVUwcnoMAlIQh/40HGhKHLIGuTm3wEqOZ4XY/8fuGHybspvSf
fkYCK+chna/GV17aeTjUNBhjZ29aA3FIzgrTGFh8aAMFfX++vI+ngyIKduWuixxL
lEaP5tWTM0uDqyRW/M+SpG3Dg6FLxMqJdyHFYgpytwWGeRC3AkMVRE38KBOoXP4l
sCmi6gY1XxeKJXFBMudLqYOUHyQxxwIZfMsmsVQ3uygEujMsQLgRpMKu6KUtFv+5
FLrAVuyLSQHGyphl2P7g2KWbOo8G020N8U7lKRFPdXE+5H+wJZaGHyRKvymG51Fe
GHWVnLfvWGP8xphwd1GA8vogRucPk/8u0VnJqx47/9Jmk3VOs/HnOJEd2ex06k6l
6l+Sw1shVwYWN7syeR1pv4Jd9u5UeEeT/ZWXEUgf6K/tcfQxttZfPDX+oetv2S5G
DvUZJKtyX5ukrX9xRV//kWYU2tzfYIF1fK/DnrjukKfdrRoChxsjJs4UNkRpyr4T
29ru44bNL4UCUyBhJFE538Kg8vJJT/1/PQ1GP55gLRfCkCjW2xAHKwHTwv6CpNDH
Et5TLxdNPpWKKT1wsmXHIjyRaej/iBXUMeh8TJO8opvsliSDNVmzVCAkK9kiVA==
=e0Nq
-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#743635: openvswitch: OVS should probably start before networking

2014-07-04 Thread Fabio Fantoni

I have same or similar problem, configuring ovs bridge in dhcp 
newtworking is working but with static ip not.
I have already tried the LSB header change above (and insserv 
-r/insserv) but not solves the problem.


In my /etc/network/interfaces there is the follow ovs confguration:


allow-ovs xenbr0
iface xenbr0 inet static
 address 192.168.1.90
 netmask 255.255.255.0
 network 192.168.1.0
 broadcast 192.168.1.255
 gateway 192.168.1.200
 ovs_type OVSBridge
 ovs_ports bond0

allow-xenbr0 bond0
iface bond0 inet manual
 ovs_bridge xenbr0
 ovs_type OVSBond
 ovs_bonds eth0 eth1
 ovs_options bond_mode=balance-tcp lacp=active

auto eth0
allow-hotplug eth0
iface eth0 inet manual
up ip link set up dev eth0
down ip link set down dev eth0

auto eth1
allow-hotplug eth1
iface eth1 inet manual
up ip link set up dev eth1
down ip link set down dev eth1


If you need more details tell me and I'll post them.

Thanks for any reply and sorry for my bad english.


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

Bug#747989: Help required

2014-07-04 Thread Alberto Gonzalez Iniesta

On Fri, Jul 04, 2014 at 12:32:06PM +0300, Yavor Doganov wrote:
 [ Apologies for replying to myself again. ]
 
 Yavor Doganov wrote:
- The autorelease pool should be created in the constructor, before
  the first object is allocated.  That's openvpn_plugin_open_v1,
 
 Actually, after looking more into this and reading openvpn-plugin.h, I
 see that the upstream patch is correct here.  ctx-config is manually
 released in openvpn_plugin_close_v1, so that's perfectly fine.
 
 There are a few other potential issues with initialization -- not
 assigning self to the result of super or [self init] and using [self
 init] when [super init] should be used.  These are easily fixable.

Hi Yagor,

Thanks for your help!! I'll apply the patch and do some testing next
week, hopefully closing this.

Cheers,

Alberto

-- 
Alberto Gonzalez Iniesta| Formación, consultoría y soporte técnico
mailto/sip: a...@inittab.org | en GNU/Linux y software libre
Encrypted mail preferred| http://inittab.com

Key fingerprint = 5347 CBD8 3E30 A9EB 4D7D  4BF2 009B 3375 6B9A AA55


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

Bug#753690: pbuilder: ccache handling broken after SUTOUSER / CCACHE_ENV changes in 0.215+nmu1

2014-07-04 Thread Thorsten Glaser

gregor herrmann dixit:

ccache: failed to create /var/cache/pbuilder/ccacheLD_PRELOAD= (Permission 
denied)

Oops, my apologies. Yes, there was clearly a space missing
in the substitution. I’ve uploaded the attached patch as followup
(to fix what I broke).

bye,
//mirabilos
-- 
21:27⎜[Natureshadow] BÄH! Wer hatn das Bier neben den Notebooklüfter
 ⎜gestellt ... Das ist ja warm!
21:27⎜Natureshadow lol 21:27⎜Natureshadow du?
21:27⎜[Natureshadow] vermutlich ...   -- Kev^WNatureshadow allein zu Hausdiff -Nru pbuilder-0.215+nmu1/debian/changelog 
pbuilder-0.215+nmu2/debian/changelog
--- pbuilder-0.215+nmu1/debian/changelog2014-06-23 15:38:36.0 
+0200
+++ pbuilder-0.215+nmu2/debian/changelog2014-07-04 13:21:10.0 
+0200
@@ -1,3 +1,9 @@
+pbuilder (0.215+nmu2) unstable; urgency=low
+
+  * Fix missing space, thanks gregoa for spotting (Closes: #753690)
+
+ -- Thorsten Glaser t...@mirbsd.de  Fri, 04 Jul 2014 13:20:42 +0200
+
 pbuilder (0.215+nmu1) unstable; urgency=low
 
   [ Ivo De Decker ]
diff -Nru pbuilder-0.215+nmu1/pbuilder-buildpackage 
pbuilder-0.215+nmu2/pbuilder-buildpackage
--- pbuilder-0.215+nmu1/pbuilder-buildpackage   2014-06-23 15:37:33.0 
+0200
+++ pbuilder-0.215+nmu2/pbuilder-buildpackage   2014-07-04 13:20:38.0 
+0200
@@ -115,7 +115,7 @@
 createbuilduser
 CCACHE_ENV=
 setup_ccache
-SUTOUSER=${SUTOUSER/ env / env $CCACHE_ENV}
+SUTOUSER=${SUTOUSER/ env / env $CCACHE_ENV }
 log I: Installing the build-deps
 executehooks D
 trap saveaptcache_umountproc_cleanbuildplace_trap exit sighup sigpipe

Bug#753691: [INTL:sv] Swedish strings for nss-pam-ldapd debconf

2014-07-04 Thread Martin Bagge

package: nss-pam-ldapd
severity: wishlist
tags: patch l10n

Please consider to add this file to translation of debconf.

-- 
brother
http://sis.bthstuden.se


sv.po
Description: Binary data

Bug#753690: pbuilder: ccache handling broken after SUTOUSER / CCACHE_ENV changes in 0.215+nmu1

On Fri, 04 Jul 2014 11:26:03 +, Thorsten Glaser wrote:

 ccache: failed to create /var/cache/pbuilder/ccacheLD_PRELOAD= (Permission 
 denied)
 
 Oops, my apologies. Yes, there was clearly a space missing
 in the substitution. I’ve uploaded the attached patch as followup
 (to fix what I broke).

Great, thanks for the super-quick fix!

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


signature.asc
Description: Digital Signature

Bug#717691: need more info

2014-07-04 Thread Thomas Lange

What do you mean by preserving a partition? Do you mean a LVM
partition or a physical disk partition?

Please provide your disk_config file, so we can understand your
problem.

-- 
regards Thomas


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

Bug#753171: FTBFS: /usr/bin/ld: cannot find -lee

2014-07-04 Thread Emilio Pozuelo Monfort

On 04/07/14 12:24, Michael Biebl wrote:
 Am 04.07.2014 10:10, schrieb Emilio Pozuelo Monfort:
 On 29/06/14 20:16, Michael Biebl wrote:
 Source: sagan
 Version: 0.2.1.r1-1
 Severity: serious

 Due to the latest updates in liblognorm, sagan now FTBFS

 configure:2701: checking whether the C compiler works
 configure:2723: gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4
 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wl,-z,relro
 conftest.c -lm -lestr -lee 5
 /usr/bin/ld: cannot find -lee
 collect2: error: ld returned 1 exit status

 Full build log is attached.

 Due to the changes in liblognorm, the liblognorm-dev package no longer
 depends on libee-dev.

 Simply adding libee-dev to Build-Depends was not sufficient, due to a
 bug in libestmp [1]

 libestmp got fixed. Is adding libee-dev enough now?
 
 No, unfortunately not.
 As I wrote in the bug report, sagan's configure needs to use pkg-config
 proper to get all necessary compiler and linker flags.
 Without them it will fail to find the json header files.
 
 Even when this is fixed, I don't know if sagan already works with
 liblognorm.
 
 My suggestion would be to RM it from testing.

There are a few fixes upstream to fix these issues:
https://github.com/beave/sagan/commits/master

But yes, we can remove this package from testing is this bug doesn't get fixed.

Emilio


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

Bug#753692: DDNS vs FQDN generated by dhcp server

2014-07-04 Thread Harald Dunkel

Package: isc-dhcp-server
Version: 4.3.0+dfsg-1

Problem with DDNS support: If the dhcp server has
set
ddns-updates on;
ddns-update-style standard; # or interim
allow client-updates;
do-forward-updates on;
:
zone example.com {
primary localhost;
}
zone 0.0.10.in-addr.arpa {
primary localhost;
}
subnet 10.0.0.0 netmask 255.255.255.0 {
ddns-domainname example.com.;
:
pool {
range 10.0.0.100 10.0.0.254;
}
}

and if the client foo.example.com has

send host-name = gethostname();

in dhclient.conf, then the server tries to register
A and PTR records for

foo.example.com.example.com.

Doesn't sound reasonable to me.

If the client's host name is set to foo.example.com.
(please note the dot), then the generated host name is

foo.example.com..example.com.

Thats weird.

bind9 is version 1:9.9.5.dfsg-4


Regards
Harri


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

Bug#753693: googleearth-package: mention 'make-googleearth-package' in package description

2014-07-04 Thread Paul

Package: googleearth-package
Version: 1.1.0
Severity: wishlist

It would be nice if the description for this package (as reported by
'aptitude show' and friends) mentioned the 'make-googleearth-package'
script and /usr/share/doc/googleearth-package/README.Debian.

At the moment it is unclear what to do with the package and a simple
hint would be helpful.


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

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

Versions of packages googleearth-package depends on:
ii  bzip2   1.0.6-5
ii  dpkg-dev1.17.10
ii  fakeroot1.20-3
ii  file1:5.19-1
ii  wget1.15-1+b1
ii  x11-common  1:7.7+7
ii  x11-utils   7.7+1

googleearth-package recommends no packages.

googleearth-package suggests no packages.

-- no debconf information

--
Paul.


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

Bug#753694: wheezy-pu: package libflickr-api-perl/1.01-3+deb7u1

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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I've prepared an update for libflickr-api-perl for the upcoming point
release, as a fix for RC bug #753522:

Changelog:

#v+
  * Update Flickr API URLs in lib/Flickr/API.pm.

Flickr changed their API URLs from http://www.flickr.com to
https://api.flickr.com.

Backport this change in lib/Flickr/API.pm and test.pl from upstream
releases 1.05 (www - api) and 1.09 (http - https).

Thanks to Lars Hansen and Paul L for the respective bug reports.
(Closes: #753522) (LP: #1317464)
#v-

The changes are in a quilt patch which only changes the URLs in the
module and the test.

Full debdiff (well, git diff) attached.


Cheers,
gregor

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJrBAEBCgBVBQJTtpIjThSAAB0AKGlzc3Vlci1mcHJAZ3BnLmNvbW9kby5w
cml2LmF0RDFFMTMxNkU5M0E3NjBBODEwNEQ4NUZBQkIzQTY4MDE4NjQ5QUEwNgAK
CRC7OmgBhkmqBg6ID/4kXlwrZSIdqOy0IrBRw3uTnjUBaccRF23eyOiyqC9x/5ss
QS6JHHEZu9dBWa+zTyPc15hT/0SzwLQldxHUsgbu6I5cOQi8L8k1RuQQPWw+yf9F
YEj5IVEaZo0TTxlc36HEDBFcE7h2eKth0Hcqnznyc25pOzmuQArH3pBH/5xrn6wV
FtMqrrvka0q3kok3qMOad5YYVyoI1tHRxJOj1mXQZMuYR+JnJ5HGl8zkMapmcIBR
vwjO+amAYRd+8Gz7pZgoWNTawurk4yjD8T39ap6vEUWpdUwzQibqpTyuTK+Dx1mn
k/bwIpjysxvfznCgcUZsWWxzhGk++O3p2+wzqccsoBis6P9R7YWX6lIT2HgWltQQ
+54iTO2WhUZUpEatpyHH+0qSopSP9TtDvsDZUANxqKIUnz7EZ3OtQkj0sR54mkNj
nWKbazx/3iBhv4i4lV5rF61jmvAn6FZZdyoXgj/orZtQy6NcXK6CR/znEpeopte9
Yd3E5OgFGh62Sxxq39dlW8H5E6bU+MVugBfkLlwCLUbNxzTFi956kKkGhf5Kk6xV
ybtNvG19sWflr4m9wNpGGlkhUpDNU1JY6WEJw58VZwYhcGnWOQHv6i1ZyYiEwGQl
9ihye/WuS7gj79KqkbQsBinZlrSXMSocVSuA1J1KiAAKurq6QvWQnaM9O6GZNA==
=aJZs
-END PGP SIGNATURE-
diff --git a/debian/changelog b/debian/changelog
index 61a..ad31e2f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,18 @@
+libflickr-api-perl (1.01-3+deb7u1) UNRELEASED; urgency=medium
+
+  * Update Flickr API URLs in lib/Flickr/API.pm.
+
+Flickr changed their API URLs from http://www.flickr.com to
+https://api.flickr.com.
+
+Backport this change in lib/Flickr/API.pm and test.pl from upstream
+releases 1.05 (www - api) and 1.09 (http - https).
+
+Thanks to Lars Hansen and Paul L for the respective bug reports.
+(Closes: #753522) (LP: #1317464)
+
+ -- gregor herrmann gre...@debian.org  Fri, 04 Jul 2014 13:28:55 +0200
+
 libflickr-api-perl (1.01-3) unstable; urgency=low
 
   * Drop patch should_query_for_tags_not_elements, breaks with newer
diff --git a/debian/patches/flickr-api-urls.patch b/debian/patches/flickr-api-urls.patch
new file mode 100644
index 000..a519a0d
--- /dev/null
+++ b/debian/patches/flickr-api-urls.patch
@@ -0,0 +1,34 @@
+Description: Update Flickr API URLs.
+Origin: vendor
+Bug-Debian: https://bugs.debian.org/753522
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+bug/1317464
+Author: gregor herrmann gre...@debian.org
+Last-Update: 2014-07-04
+Applied-Upstream: fixed in 1.09
+
+--- a/lib/Flickr/API.pm
 b/lib/Flickr/API.pm
+@@ -18,8 +18,8 @@
+ 	my $self = new LWP::UserAgent;
+ 	$self-{api_key}	= $options-{key};
+ 	$self-{api_secret}	= $options-{secret};
+-	$self-{rest_uri}	= $options-{rest_uri} || 'http://www.flickr.com/services/rest/';
+-	$self-{auth_uri}	= $options-{auth_uri} || 'http://www.flickr.com/services/auth/';
++	$self-{rest_uri}	= $options-{rest_uri} || 'https://api.flickr.com/services/rest/';
++	$self-{auth_uri}	= $options-{auth_uri} || 'https://api.flickr.com/services/auth/';
+ 
+ 	eval {
+ 		require Compress::Zlib;
+--- a/test.pl
 b/test.pl
+@@ -81,8 +81,8 @@
+ }
+ 
+ ok($uri-path eq '/services/auth/', Checking correct return path);
+-ok($uri-host eq 'www.flickr.com', Checking return domain);
+-ok($uri-scheme eq 'http', Checking return protocol);
++ok($uri-host eq 'api.flickr.com', Checking return domain);
++ok($uri-scheme eq 'https', Checking return protocol);
+ 
+ 
+ ##
diff --git a/debian/patches/series b/debian/patches/series
index d49b4f5..05c4b35 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
 test-no-internet
+flickr-api-urls.patch

Bug#753522: Pending fixes for bugs in the libflickr-api-perl package

2014-07-04 Thread pkg-perl-maintainers

tag 753522 + pending
thanks

Some bugs in the libflickr-api-perl package are closed in revision
bb4a0185b2e8682c53653834cbe75ca93632df70 in branch '  wheezy' by
gregor herrmann

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

Commit message:

Update Flickr API URLs in lib/Flickr/API.pm.

Flickr changed their API URLs from http://www.flickr.com to
https://api.flickr.com. Backport this change in lib/Flickr/API.pm and
test.pl from upstream releases 1.05 (www - api) and 1.09 (http - https).

Closes: #753522
LP: #1317464
Thanks: Lars Hansen and Paul L for the respective bug reports.


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

Bug#753695: cloud-init: please drop iproute build-dependency

2014-07-04 Thread Andreas Henriksson

Package: cloud-init
Version: 0.7.6~bzr976-1
Severity: normal
Usertags: iproute-removal

Dear Maintainer,

Please consider dropping the iproute build-dependency from
your package as it doesn't seem to be needed at all.

The iproute package is now a transitional package and all
dependencies on it should be replaced with iproute2.

Your package on the other hand doesn't seem to actually
need it (it was once in a time long before the package
entered debian used, but cloud-init seems to since
then switch to using the netlink interface directly
instead of invoking the iproute2 utilities).

Please investigate if you can confirm that it is no longer
needed and drop the build-dependency, or switch it to
iproute2.


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

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=sv_SE.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#753696: cluster-glue: please consider dropping iproute build-dependency

2014-07-04 Thread Andreas Henriksson

Source: cluster-glue
Version: 1.0.12~rc1+hg2777-1
Severity: normal
Usertags: iproute-removal

Dear Maintainer,

The iproute package is being removed from Debian and all
users needs to update their dependencies to use the new iproute2
package.

Your package build-depends on iproute, but it doesn't seem
to actually need it. I've done a simple rebuild-test
of cluster-glue with the iproute package removed from
build-dependencies and that finished successfully.

Please consider investigating if you can confirm that
the iproute is not needed as a build-dependency and drop
it if so, otherwise please switch to iproute2.


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

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=sv_SE.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#752075: RFH: Re: Bug#752075: daemontools-run: Add systemd support

2014-07-04 Thread Gerrit Pape

On Fri, Jul 04, 2014 at 03:37:20AM -0700, Russ Allbery wrote:
 Gerrit Pape p...@dbnbgs.smarden.org writes:
  I looked into latest policy, but did not find anything about systemd
  support.  I'm surprised that this is now a release critical bug, and the
  package marked for removal.  What's the justification?
 
 I'm very dubious about this being release-critical.

I think it is.  The package will not work as expected without the
inittab interface.

  This package hooks into /etc/inittab, does systemd not automatically
  manage services from inittab?
 
 Correct, systemd doesn't use inittab.
 
  Isn't it systemd having release critical bug then?
 
 I don't think it's likely that systemd will support inittab.  The
 semantics of inittab are quite a bit inferior to what's available with
 very little additional work using the native configuration format, and the
 regular inittab jobs are provided by regularly-configured services.  Yes,
 that is a disruptive change for people who were using inittab to run other
 things.

Thanks Russ.  This also applies to the runit package actually.

Having my own init system since more than 10 years, I'm not that much in
systemd.  I looked at policy, but didn't find any instructions.

I hereby ask for help to add systemd support to these packages.

Important thing to know is: init scripts don't work out for this.  The
service management concept of daemontools and runit is, amongst other
things, a process tree with guaranteed process state, including
envrionment.  init scripts don't provide that.

Regards, Gerrit.


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

Bug#753697: openafs-filserver: OPENAFS-fileserver does not answer

2014-07-04 Thread f...@fkoop.de


Package: openafs-filserver
Version: openafs-fileserver
Severity: important

Dear Maintainer,

I have an OPENAFS-cell that used to work for several months. After having
a crash on the machine, it started not to work anymore. The fileserver does
not answer to requests any more. In the logs I see the following errors:

FileLog

Fri Jul  4 12:52:15 2014 File server starting (/usr/lib/openafs/fileserver)
Fri Jul  4 12:52:15 2014 VL_RegisterAddrs rpc failed; will retry periodically
(code=5376, err=0)
Fri Jul  4 12:52:15 2014 Couldn't get CPS for AnyUser, will try again in 30
seconds; code=5376.
Fri Jul  4 12:52:45 2014 Couldn't get CPS for AnyUser, will try again in 30
seconds; code=5376.

VolserLog

Fri Jul  4 12:53:01 2014 SYNC_connect: temporary failure on circuit 'FSSYNC'
(will retry)
Fri Jul  4 12:53:17 2014 SYNC_connect: temporary failure on circuit 'FSSYNC'
(will retry)
Fri Jul  4 12:53:41 2014 SYNC_connect: temporary failure on circuit 'FSSYNC'
(will retry)
Fri Jul  4 12:54:13 2014 SYNC_connect: temporary failure on circuit 'FSSYNC'
(will retry)
Fri Jul  4 12:54:53 2014 SYNC_connect: temporary failure on circuit 'FSSYNC'
(will retry)
Fri Jul  4 12:55:41 2014 Unable to connect to file server; will retry at need
Fri Jul  4 12:55:41 2014 Starting AFS Volserver 2.0 (/usr/lib/openafs/volserver)


This Cell has only 1 server, so all processes run on the same machine.
bos status tells me that all processes (fs, vlserver, ptserver) are running
fine. What else can I do to debug and/or fix the situation?

Thanks for your help.


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

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

Bug#738631: Severity upgraded because of unchanged situation

2014-07-04 Thread Andreas Glaeser

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


When I leave the workplace, I usually want to lock the screen or log out, but 
the
situation here is still unchanged.
I had another look at bug severity levels and now I think it's a normal problem 
even,
not minor.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlO2lVkACgkQ5+rBHyUt5wt7JwCcD9j6Q0xvPF+sL0GF/SdeUaVh
HDQAnAw6wemMSHuuRmmpiftwM+U3Itxx
=4v3A
-END PGP SIGNATURE-

Bug#753698: alpine: FTBFS on hurd-i386

2014-07-04 Thread Gabriele Giacone

Source: alpine
Severity: important
User: debian-h...@lists.debian.org
Usertags: hurd

Dear Maintainer,

please re-enable and refresh 10_hurd_build.patch patch. It fixes FTBFS.

Thanks


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

Bug#753699: lynx: Alert!: This client does not contain support for HTTPS URLs.

2014-07-04 Thread Thorsten Glaser

Package: lynx-cur
Version: 2.8.9dev1-1
Severity: grave
Justification: renders package unusable

Just updated:

Unpacking lynx-cur (2.8.9dev1-1) over (2.8.8pre5-1) ...

After updating:

Alert!: This client does not contain support for HTTPS URLs.

lynx: Can't access startfile 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601683


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

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

Versions of packages lynx-cur depends on:
ii  libbsd0   0.6.0-2
ii  libbz2-1.01.0.6-5
ii  libc6 2.19-4
ii  libidn11  1.28-2
ii  libncursesw5  5.9+20140118-1
ii  libtinfo5 5.9+20140118-1
ii  zlib1g1:1.2.8.dfsg-1

Versions of packages lynx-cur recommends:
ii  mime-support  3.56

lynx-cur suggests no packages.

-- Configuration Files:
/etc/lynx-cur/lynx.cfg changed [not included]
/etc/lynx-cur/lynx.lss changed [not included]

-- debconf information excluded


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

Bug#753691: [INTL:sv] Swedish strings for nss-pam-ldapd debconf