date:20140902


Hi.  Any hope to get a comment from the stable release team on this bug
from 2014-03-24?

-- 
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#760219: [Pkg-clamav-devel] Bug#760219: clamav-daemon: use of --name in init.d's stop-start-daemon causes failure to stop in certain virtualized environments

2014-09-02 Thread Sebastian Andrzej Siewior

On 2014-08-31 22:04:33 [-0400], Daniel Dickinson wrote:
 /etc/init.d/clamav-deamon uses --name in it's start-stop-daemon calls for 
 stop and restart.
 
 This fails when process names are not available due to use of certain 
 virtualized environments
 use as kfreebsd in freebsd jail (others have the same issue from reports I've 
 read however this
 is what I am use) due to limited /proc.

This sound like an interresting limitation. Just to make it clear: a ps
shows pid but not the process name that belongs to it? If so how do you
make know what is running on the machine then?

Don't you have the same problem with other daemons like unbound or
dovecot?

 
 Changin relying solely on PIDFILE fixes the issue (i.e. drop --name $DAEMON)

We had a bug reported that it is unsecure not checking the name of the
process and only using the PIDFILE. The reason was that the daemon migh
segfault (or gets killed by other means) and another unrelated process
gets the same PID assigned that was used by that daemon. And so a stop
would kill another process. That is why --name was added.
Do you have any other suggestions to get this wokring for you?

Sebastian


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

Bug#745091: jing-trang: FTBFS with Java 8

2014-09-02 Thread Eugene Zhukov

Control: retitle -1 jing-trang: FTBFS with Java 8


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

Bug#737157: source-highlight: [PATCH] Enable build on newer arches

2014-09-02 Thread ravi


Source: source-highlight
Followup-For: Bug #737157
User: debian-de...@lists.debian.org
Usertags: ppc64el

Dear Maintainer,

One new arch is : ppc64el, which has been added to the Debian archive. 
But package FTBFS because of outdated config files.


Thanks,
Ravindran

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

Kernel: Linux 3.13-1-powerpc64le (SMP w/16 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
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#756572: Thank you for your report

2014-09-02 Thread Rolf Leggewie

Peter,

thank you for the report.  I haven't run into this yet, so more
information on how to reliably reproduce this issue would be appreciated
(from you or anyone else).

http://sourceforge.net/p/polipo/mailman/polipo-users/thread/7ilieltkv6@lanthane.pps.jussieu.fr/
might be interesting for you.

Regards

Rolf


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

Bug#760142: systemd: Assertions from systemd-logind on powerpc during login, with continuing loop

2014-09-02 Thread Simon McVittie

On 01/09/14 22:55, Chris Tillman wrote:
 Sep 02 09:44:00 debian dbus[767]: [system] Failed to activate service
 'org.freedesktop.Avahi': timed out
 Sep 02 09:44:01 debian dbus[767]: [system] Failed to activate service
 'org.freedesktop.PolicyKit1': timed out
 Sep 02 09:44:25 debian dbus[767]: [system] Failed to activate service
 'org.freedesktop.systemd1': timed out
(etc.)

I think this is the root cause:

Aug 31 09:08:48 debian systemd[1]: Starting D-Bus System Message Bus...
Aug 31 09:08:48 debian systemd[1]: Started D-Bus System Message Bus.
...
Aug 31 09:09:13 debian systemd[1]: Failed to register to bus: Did not
receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the
reply timeout expired, or the network connection was broken.

(Note that that's exactly 25 seconds, the default timeout in libdbus and
possibly other D-Bus implementations.)

systemd is meant to connect to the system dbus-daemon shortly after
starting it, so that it can receive service activation requests from
dbus-daemon. In this case, this doesn't seem to have worked. The failing
call appears to be the initial call to Hello() from
manager_bus_async_register(). In practice manager_bus_async_register()
runs while the system is busy, so it should perhaps use an explicit
timeout value (or even DBUS_TIMEOUT_INFINITE, which is INT32_MAX)
instead of using -1 (which means use the default, i.e. 25 seconds).

systemd = 209 uses its own D-Bus implementation, sd-bus, instead of
libdbus, and in that implementation, it uses an infinite timeout for
Hello(). (Don't be confused by the different notation: in sd-bus, unlike
libdbus, a timeout of ((uint64) -1) is infinite, and a timeout of 0
means use the default.)

S


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

Bug#760102: gnome-keyring: Breaks gpg-agent with no UI to disable

2014-09-02 Thread Sjoerd Simons

On Sun, 2014-08-31 at 19:47 +0100, Mark Brown wrote:
 Package: gnome-keyring
 Version: 3.12.2-1
 Severity: important
 
 Since a recent upgrade (sorry, not 100% clear when this happened but I
 do update fairly frequently) gnome-keyring has started providing a GnuPG
 agent.  This is breaking my usage of my system as gnome-keyring does not
 appear to support GnuPG smartcards as gpg-agent does and my day to day
 work is heavily dependent on being able to use one.  For example signing
 e-mail causes this:
 
 | gpg: WARNING: The GNOME keyring manager hijacked the GnuPG agent.
 | gpg: WARNING: GnuPG will not work properly - please configure that tool to 
 not interfere with the GnuPG system!
 | gpg: selecting openpgp failed: Unsupported certificate
 | gpg: signing failed: Unsupported certificate
 | gpg: signing failed: Unsupported certificate
 
 which is a serious issue; I also use my smartcard as a SSH key and this
 usage is also broken.  There used to be a UI to edit the startup
 applications but this seems to have been removed.

gnome-session-properties is indeed gone. You can still configure this by
hand by removing the relevant startup application
from /etc/xdg/autostart. See /usr/share/doc/gnome-keyring/README.Debian
for more information.

-- 
Sjoerd Simons sjo...@luon.net


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

Bug#760261: [opam] opam broken by dose.3.2.2 update

2014-09-02 Thread Török Edwin

Package: opam
Version: 1.1.1-1+b1
Severity: normal

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

opam version is now 1.1.1-1+b1, which is broken due to using dose.3.2.2 instead 
of 3.1.x (as the initial version without +b1 apparently did).
This would've been detected by opam's testsuite, except that Debian didn't 
build/run that test-suite due to using its own build-system.

opam 1.1.2 has a simple Makefile-based build-system that would be easier for 
the Debian package to use (and run tests too),
so a solution might've been to package that for Debian.
However the testsuite fails with dose.3.2.2 (works with dose.3.1.2 (probably 
3.1.x too), but that version seems to be gone from testing/unstable, so I don't 
know
if opam could force a dependency on that).

There is a beta version of opam 1.2.0 that supports dose.3.2.2, and I asked 
upstream what should be done
about the stable/released versions given that they're all broken now: 
https://github.com/ocaml/opam/issues/1683

For now a workaround is to install the working package from 
snapshot.debian.org, I don't know if it'd be possible the revert the broken
+b1 package to this:
http://snapshot.debian.org/archive/debian/20140202T163543Z/pool/main/o/opam/opam_1.1.1-1_amd64.deb

Test-case, this command should succeed:
(export OPAMROOT=/tmp/opamroot; rm -rf $OPAMROOT; opam init  opam install 
ocamlfind  opam install lwt)
If it says that it'll install ocamlfind again when 'opam install lwt' is run 
then it'll fail.



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

Debian Release: jessie/sid
  500 unstableftp.ro.debian.org 
  500 testing ftp.ro.debian.org 
1 experimentalftp.ro.debian.org 

--- Package information. ---
Depends(Version) | Installed
-+-=
libbz2-1.0   | 1.0.6-7
libc6  (= 2.14) | 
libpcre3   (= 8.10) | 
zlib1g  (= 1:1.1.4) | 
opam-docs(= 1.1.1-1) | 
build-essential  | 
wget | 
 OR curl | 


Recommends  (Version) | Installed
=-+-===
ocaml | 4.01.0-4
git   | 1:2.1.0-1
rsync | 3.1.1-2


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#760168: dh-systemd: support for -X option

2014-09-02 Thread Michael Stapelberg

Did you try whether it actually works already?

In dh_compress and dh_fixperms I see -X is documented but I don’t see
special code to support it. Given that dh_systemd_* also use the same
Debhelper library functions that those other two examples use, I think
it should already just work…?

On Mon, Sep 1, 2014 at 4:32 PM, Simon McVittie s...@debian.org wrote:
 Package: dh-systemd
 Version: 1.21
 Severity: wishlist

 debhelper(7) says:

 COMMON DEBHELPER OPTIONS
The following command line options are supported by some debhelper
programs [...]
-Xitem, --exclude=item
Exclude an item from processing. This option may be used multiple
times, to exclude more than one thing.

 It would be nice if dh_systemd_start and dh_systemd_enable supported the
 -X option, so that maintainers of a package with some normal services
 and a smaller number of special-purpose services that should not normally
 be enabled (similar to systemd's own debug-shell.service) could just
 list the exceptions:

 override_dh_systemd_enable:
 dh_systemd_enable -Xdebug-thing.service

 override_dh_systemd_start:
 dh_systemd_start -Xdebug-thing.service

 Regards,
 S

 ___
 Pkg-systemd-maintainers mailing list
 pkg-systemd-maintain...@lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers



-- 
Best regards,
Michael


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

Bug#760182: multipath-udeb: not installable, depends on libsystemd-daemon0


On Monday 01 September 2014 10:40 PM, Cyril Brulebois wrote:

[debian-b...@lists.debian.org  in X-d-cc, please keep it in the loop. ]

Hi,

this udeb now depends on a non-udeb package: libsystemd-daemon0, making
it uninstallable. This in turn makes partman-multipath uninstallable.

FTR there's no systemd in d-i (and likely won't be).

Thank you for this information. So how do we proceed here ?
Should I drop the systemd support for now ?

--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#760168: dh-systemd: support for -X option

2014-09-02 Thread Simon McVittie

On 02/09/14 08:34, Michael Stapelberg wrote:
 Did you try whether it actually works already?

Yes I did, and no it doesn't.

 In dh_compress and dh_fixperms I see -X is documented but I don’t see
 special code to support it.

Library code in Debian::Debhelper parses -X options and
$DH_ALWAYS_EXCLUDE and puts them in $dh{EXCLUDE}, then converts them
into find(1) syntax and puts that in $dh{EXCLUDE_FIND}, but it's up to
individual dh_* utilities to make use of one or the other of those.

In dh_compress:

if (@files  defined($dh{EXCLUDE})  $dh{EXCLUDE}) {
my @new=();
foreach (@files) {
my $ok=1;
foreach my $x (@{$dh{EXCLUDE}}) {
if (/\Q$x\E/) {
$ok='';
last;
}
}
push @new,$_ if $ok;
}
@files=@new;
}

and in dh_fixperms:

my $find_options='';
if (defined($dh{EXCLUDE_FIND})  $dh{EXCLUDE_FIND} ne '') {
$find_options=! \\( $dh{EXCLUDE_FIND} \\);
}

Regards,
S


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

Bug#760189: kpartx: Should not include NEWS entry about systemd


On Monday 01 September 2014 11:44 PM, Josh Triplett wrote:

multipath-tools 0.5.0-2 adds a NEWS entry about transitioning to
systemd.  That NEWS entry should not appear in the kpartx binary
package, which ships no init scripts or systemd services.

(I'd also argue that it should not appear in the other multipath-tools
binary packages either, since it's no more applicable there than in many
other Debian packages also making the same transition.)


Thanks for the bug report. I am still not clear on what the systemd 
support in multipath is supposed to be like. I am talking this on 
debian-devel. Once there's a conclusion, I'll act on this bug report.


--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System

Bug#760262: ITP: ruby-kakasi-ffi -- A Ruby binding for KAKASI implemented with Fiddle/DL/FFI

2014-09-02 Thread NOKUBI Takatsugu

Package: wnpp
Severity: wishlist
Owner: NOKUBI Takatsugu k...@daionet.gr.jp

* Package name: ruby-kakasi-ffi
  Version : 1.0.1
  Upstream Author : Akinori MUSHA k...@idaemons.org
* URL : https://github.com/knu/kakasi_ffi
* License : BSD-2-clause
  Programming Lang: Ruby, C
  Description : A Ruby binding for KAKASI implemented with Fiddle/DL/FFI

ruby-kakasi-ffi is a replacement of ruby-kakasi. Former package was
obsolete, and the upstream site had closed (RAA).


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

Bug#760168: dh-systemd: support for -X option

2014-09-02 Thread Michael Stapelberg

On Tue, Sep 2, 2014 at 9:42 AM, Simon McVittie s...@debian.org wrote:
 On 02/09/14 08:34, Michael Stapelberg wrote:
 Did you try whether it actually works already?

 Yes I did, and no it doesn't.

 In dh_compress and dh_fixperms I see -X is documented but I don’t see
 special code to support it.

 Library code in Debian::Debhelper parses -X options and
 $DH_ALWAYS_EXCLUDE and puts them in $dh{EXCLUDE}, then converts them
 into find(1) syntax and puts that in $dh{EXCLUDE_FIND}, but it's up to
 individual dh_* utilities to make use of one or the other of those.
Thanks for clarifying.

Could you please come up with a patch for supporting this? I’m very
constrained on time these days, so it’s unlikely I’d address the issue
anytime soon.


 In dh_compress:

 if (@files  defined($dh{EXCLUDE})  $dh{EXCLUDE}) {
 my @new=();
 foreach (@files) {
 my $ok=1;
 foreach my $x (@{$dh{EXCLUDE}}) {
 if (/\Q$x\E/) {
 $ok='';
 last;
 }
 }
 push @new,$_ if $ok;
 }
 @files=@new;
 }

 and in dh_fixperms:

 my $find_options='';
 if (defined($dh{EXCLUDE_FIND})  $dh{EXCLUDE_FIND} ne '') {
 $find_options=! \\( $dh{EXCLUDE_FIND} \\);
 }

 Regards,
 S




-- 
Best regards,
Michael


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

Bug#759736: elasticsearch: CVE-2014-3120

2014-09-02 Thread Hilko Bengen

* Potter, Tim (Cloud Services):

Thanks for helping out with this bug.  If you could attach your patch
(the debdiff tool can be helpful here) to the bug report, either Hilko
or I (or any DD) can rebuild and upload.

 Attached.  I didn't know about debdiff - what a great tool!

Thank you. I am building the package now, intend to upload within the
next hour.

Cheers,
-Hilko


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

Bug#760231: amarok: FTBFS on kfreebsd-amd64

2014-09-02 Thread Sebastian Ramacher

On 2014-09-02 00:59:08, Emilio Pozuelo Monfort wrote:
 Source: amarok
 Version: 2.8.0-2.1
 Severity: serious
 
 Your package failed to build on kfreebsd-amd64 when rebuilt for the
 libav transition:
 
 In file included from amaroklib_automoc.cpp:4:0:
 moc_GenericScanManager.cpp: In static member function 'static void 
 GenericScanManager::qt_static_metacall(QObject*, QMetaObject::Call, int, 
 void**)':
 moc_GenericScanManager.cpp:74:114: error: invalid use of incomplete type 
 'class QSharedPointerCollectionScanner::Directory'
  case 2: _t-directoryScanned((*reinterpret_cast 
 QSharedPointerCollectionScanner::Directory(*)(_a[1]))); break;
   
 ^
 In file included from moc_GenericScanManager.cpp:9:0,
  from amaroklib_automoc.cpp:4:
 .../../src/scanner/GenericScanManager.h:37:7: error: declaration of 'class 
 QSharedPointerCollectionScanner::Directory'
  class QSharedPointer;
^
 [...]
 
 Full log at:
 
 https://buildd.debian.org/status/fetch.php?pkg=amarokarch=kfreebsd-amd64ver=2.8.0-2.1stamp=1409587135

I was unable to reproduce the issue on falla yesterday. The first build failure
looks slightly different, but interstingly enough the two builds failed with the
same amount of Build-Space. Is fayrfax full again or is there something else
wrong with it?

In any case, adding kfreebsd buildd maintainers to the loop.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#760263: RFP: golang-xgb -- X Go Binding

2014-09-02 Thread iyzsong

Package: wnpp
Severity: wishlist

* Package name: golang-xgb
  Version : git20140510
  Upstream Author : Andrew Gallant jams...@gmail.com
* URL : https://github.com/BurntSushi/xgb
* License : BSD-3, WTFPL
  Programming Lang: Go
  Description : X Go Binding

  XGB is the X Go Binding, which is a low-level API to communicate with the
core X protocol and many of the X extensions. It is closely modeled after
XCB and xpyb.

  It's a fork of x-go-binding from google code. 


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

Bug#760264: whatmaps: [INTL:fr] Initial French debconf translation

2014-09-02 Thread jean-pierre giraud

Package: whatmaps
Version: N/A
Severity: wishlist
Tags: patch l10n

Hi!

Please find attached the french templates translation, proofread by
the debian-l10n-french mailing list contributors.

This file should be put as debian/po/fr.po in your package build tree.

Kind Regards

jipege
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
#
# Jean-Pierre Giraud jean-pierregir...@neuf.fr, 2014.
msgid
msgstr
Project-Id-Version: whatmaps\n
Report-Msgid-Bugs-To: whatm...@packages.debian.org\n
POT-Creation-Date: 2014-08-20 06:56+0200\n
PO-Revision-Date: 2014-08-20 11:06+0200\n
Last-Translator: Jean-Pierre Giraud jean-pierregir...@neuf.fr\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
Plural-Forms: nplurals=2; plural=(n 1);\n
X-Generator: Lokalize 1.5\n

#. Type: boolean
#. Description
#: ../templates:2001
msgid Automatically restart services after library security updates?
msgstr
RedÃ©marrer les services aprÃ¨s les mises Ã jour de sÃ©curitÃ© des bibliothÃ¨quesÂ ?

#. Type: boolean
#. Description
#: ../templates:2001
msgid
Services need to be restarted to benefit from updates of shared libraries
they depend on. Otherwise they remain vulnerable to security bugs fixed in
these updates.
msgstr
Les services doivent Ãªtre redÃ©marrÃ©s pour bÃ©nÃ©ficier des mises Ã jour des
bibliothÃ¨ques partagÃ©es dont ils dÃ©pendent. Dans le cas contraire, ils
restent vulnÃ©rables aux bogues de sÃ©curitÃ© corrigÃ©s par ces mises Ã jour.

#. Type: boolean
#. Description
#: ../templates:2001
msgid
Automatic service restarts are only done if APT fetched the library from a
source providing security updates. This also affects packages installed via
\unattended-upgrades\.
msgstr
Le redÃ©marrage automatique des services ne se produit que si APT rÃ©cupÃ¨re les
bibliothÃ¨ques d'une source offrant des mises Ã jour de sÃ©curitÃ©. Cela affecte
aussi les paquets installÃ©s par l'intermÃ©diaire d'Â«Â unattended-upgradesÂ Â».

Bug#759200: closing 759200

2014-09-02 Thread Patrick Stokman

Hi,

This is not completely solved. I am unable to upgrade the packages
libgtkhtml-4.0-0 and evolution, because I use evolution-ews. This
package has not been updated to fix the dependencies on this package
(libgtkhtml-4.0-0).

Regards,

Patrick

On Mon, 01 Sep 2014 22:57:25 +0200 Laurent Bigonville bi...@debian.org wrote:
 close 759200 
 thanks
 
 Hello,
 
 evolution is now installable again,
 
 Closing this bug
 
 Cheers,
 
 Laurent Bigonville
 
 
 

DTG is een handelsnaam van De Telefoongids BV

Dit bericht is afkomstig van De Telefoongids BV en uitsluitend bestemd voor de 
geadresseerde. Dit bericht kan vertrouwelijke informatie bevatten. Als u dit 
bericht per abuis hebt ontvangen, dan wordt u verzocht de afzender te 
informeren en het bericht en eventuele bijlagen te vernietigen. Communicatie 
via Internet is niet beveiligd. De Telefoongids BV aanvaardt geen 
aansprakelijkheid voor wijzigingen in de inhoud van het bericht en eventuele 
bijlagen, onrechtmatige openbaarmaking ervan jegens derden of schade als gevolg 
van gebruik van e-mailcommunicatie. De Telefoongids BV is gevestigd te 
Amsterdam (Handelsregister nr. 27198207).

This message is sent from De Telefoongids BV and is intended only for use by 
the recipient. It may contain confidential information. If you are not the 
intended recipient, please advise the sender immediately by reply e-mail and 
delete this message and any attachments.
Internet communications are not secure. De Telefoongids BV does not accept any 
liability for mutilations to the contents of this message and attachments 
thereto, if any, unlawful disclosure thereof to third parties, or damage 
resulting from the use of e-mail communications. De Telefoongids BV is a 
private limited company with its seat in Amsterdam (Trade Register no. 
27198207).

Bug#756630: newusers fails with multiple users

2014-09-02 Thread Mattia Monga

 I can confirm the bug on jessie.

newusers file

works correctly if file contains just one line, but it fails when it
has multiple entries

*** Error in `newusers': free(): invalid next size (fast): 0xf95b5ed8 ***
Aborted



The bug is know also here

https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1266675


Best,

-- 
Mattia Monga


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

Bug#760084: sitesummary: postinst fail on first but not second invocation


I asked about this on #debian-devel, and got some feedback:

pere is there a way to ensure recommends are configured before the
  package recommending them, ref URL: https://bugs.debian.org/760084 ?

helmut pere: did you raise this with guillem already? in this
  particular case, you may have some luck with moving the apache parts
  to a dpkg trigger.
helmut pere: beware though, that dpkg trigger policy requires you to
  contact apache maintainers before triggering on their files. 
pere helmut: nope.  I discovered the cause yesterday, and have not
  gotten past asking for clues on #debian-devel. :) 
themill Looks similar to http://bugs.debian.org/745834
themill (similar ordering problem; different cause)
helmut pere: please file a bug against dpkg. even if it'll not be
  solved in dpkg, getting input from guillem seems important to me. 
pere helmut: I'll try to formulate something. 

-- 
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#682751: cryptsetup: Booting from encrypted multidevice btrfs does not work

2014-09-02 Thread Gerald Turner

Hi, I encountered this bug after doing a jessie install and converting
the root btrfs pool to raid post-install, similar to what Paul Dreik
described.

At first I tried the most recent patch from Marek Dopiera, however it
did not work for me since it looks like his patch relies on fstab having
device paths (e.g. /dev/mapper/sda2_crypt) and fails to detect btrfs for
fstab entries using UUID.

So I applied Jon Severinsson patch from wheezy era, works great!
Attached is his patch re-worked for 1.6.6-1.

-- 
Gerald Turner gtur...@unzane.comEncrypted mail preferred!
OpenPGP: 4096R / CA89 B27A 30FA 66C5 1B80  3858 EC94 2276 FDB8 716D
--- cryptsetup-1.6.6/debian/initramfs/cryptroot-hook.orig	2014-09-02 00:35:27.822073093 -0700
+++ cryptsetup-1.6.6/debian/initramfs/cryptroot-hook	2014-09-02 00:37:29.296772349 -0700
@@ -16,7 +16,7 @@
 
 . /usr/share/initramfs-tools/hook-functions
 
-get_root_device() {
+get_root_devices() {
 	local device mount type options dump pass
 
 	if [ ! -r /etc/fstab ]; then
@@ -26,8 +26,15 @@
 	grep -s '^[^#]' /etc/fstab | \
 	while read device mount type options dump pass; do
 		if [ $mount = / ]; then
-			device=$(canonical_device $device) || return 0
-			echo $device
+			local devices
+			if [ $type = btrfs ] ; then
+for dev in $(btrfs filesystem show $(canonical_device $device --no-simplify) 2/dev/null | sed -r -e 's/.*devid .+ path (.+)/\1/;tx;d;:x') ; do
+	devices=$devices $(canonical_device $dev)
+done
+			else
+devices=$(canonical_device $device) || return 0
+			fi
+			echo $devices
 			return
 		fi
 	done
@@ -90,7 +97,7 @@
 		if [ -n $derived ]; then
 			if grep -q ^$derived /etc/crypttab; then
 derived=$(canonical_device /dev/mapper/$derived) || return 0
-if [ $derived != $rootdev ]; then
+if ! echo $rootdevs | grep -q -e $derived; then
 	devices=$devices $derived
 fi
 			else
@@ -308,6 +315,7 @@
 canonical_device() {
 	local dev altdev original
 	dev=$1
+	opt=$2
 
 	altdev=${dev#LABEL=}
 	if [ $altdev != $dev ]; then
@@ -324,6 +332,11 @@
 		dev=$(readlink -e $dev)
 	fi
 
+	if [ $opt = --no-simplify ]; then
+		echo $dev
+		return 0
+	fi
+
 	if [ x${dev%/dev/dm-*} = x ]; then
 		# try to detect corresponding symlink in /dev/mapper/
 		for dmdev in /dev/mapper/*; do
@@ -359,7 +372,7 @@
 	fi
 
 	# Flag root device
-	if [ $nodes = $rootdev ]; then
+	if echo $rootdevs | grep -q -e $nodes; then
 		if [ -z $opts ]; then
 			opts=rootdev
 		else
@@ -507,7 +520,7 @@
 #
 
 setup=no
-rootdev=
+rootdevs=
 resumedevs=
 
 # Include cryptsetup modules, regardless of _this_ machine
@@ -518,15 +531,15 @@
 
 # Find the root and resume device(s)
 if [ -r /etc/crypttab ]; then
-	rootdev=$(get_root_device)
-	if [ -z $rootdev ]; then
+	rootdevs=$(get_root_devices)
+	if [ -z $rootdevs ]; then
 		echo cryptsetup: WARNING: could not determine root device from /etc/fstab 2
 	fi
 	resumedevs=$(get_resume_devices)
 fi
 
 # Load the config opts and modules for each device
-for dev in $rootdev $resumedevs; do
+for dev in $rootdevs $resumedevs; do
 	if ! modules=$(add_device $dev); then
 		echo cryptsetup: FAILURE: could not determine configuration for $dev 2
 		continue


pgpMgD5e_UTWR.pgp
Description: PGP signature

Bug#759849: multipath-tools: FTBFS: uxsock.c:20:31: fatal error: systemd/sd-daemon.h: No such file or directory


On Monday 01 September 2014 07:48 PM, Michael Biebl wrote:

In native init scripts, we did a lot of check before starting and
shutting down the daemon. Things like checking the root device, or
tiggering LVM Volume Group activitation. They were easily done in shell.

What would the systemd team recommend for it ?


Could you elaborate a bit more, why those are needed?
What is upstream doing about this?


The block storage has many components that work closely with one another.

Take an example, root fs on LVM on Multipath on iSCSI.

The flow for such a setup is to:
1) Start iSCSI and discover the LUNs
2) Detect and create mulitpath maps for matching LUNs in DM Multipath
3) Detect and Activate Volume Group out of the newly detected DM 
Multipath Physical Volumes

4) Mount the file system.

The same can be applied to the shutdown sequence. You want to have 
proper checks in place before initiating a shutdown of the service. One 
would argue that the service should not stop if it has active services.


Many of the services (mulitpath, iscsi, for example) have a 2 part 
component. One in the kernel and the other in userspace. The kernel 
space service will not terminate if any service is active. But the 
userspace is not so forgiving.


In open-iscsi, if you ask the daemon to shutdown, it will. If there are 
active sessions, the kernel component will not terminate the current 
sessions. But the userspace daemon will be shutdown. That means, that 
when there is the next state failure, open-iscsi will have no idea of 
determining that a LUN state has changed


Similar is the case with DM Multipath. The userspace DM Multipath daemon 
is responsible for polling and keeping an up-to-date status of the 
Device Mapper maps. If the userspace daemon is inactive, and underneath 
there is a fabric state change, there is no way to propagate that error 
to the upper layers.


These design issues, since they are part of the core storage stack, if 
triggered, leave you with a machine with no access to your root disk. 
Any process at that time, may get into a 'DI' process state or an 
immediate device failure. The only action then would be to hardware 
reset your machine.


This is why we do a lot of checks in the init scripts to warn the user.


Similar approaches were taken in RHEL (5 and 6) and SLES (10 and 11). 
I'm not sure what Red Hat or SUSE has chosen for their latest releases, 
as I don't work on those products any more.



My inclination is to ship both, the systemd service files and the init 
scripts, in their current form along with whatever limitations each may 
have, and let the user choose.



And by the way, can someone please shed some more light on Debian bug: 
760182


Per the bug report, there is no systemd support in d-i. Which then means 
that I need to disable systemd support ?



--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#759849: multipath-tools: FTBFS: uxsock.c:20:31: fatal error: systemd/sd-daemon.h: No such file or directory


On Tuesday 02 September 2014 12:46 AM, Christian Hofstaedtler wrote:

In native init scripts, we did a lot of check before starting and shutting
down the daemon. Things like checking the root device, or tiggering LVM
Volume Group activitation. They were easily done in shell.

What would the systemd team recommend for it ?

That probably depends on why you were doing these things in the
first place. It'd be my understanding that udev should take care
about most stuff, and for the root device, your initramfs-tools hook
should do it.


Yes. udev did take care of many things. But not all got covered by udev. 
Please see my other email for the problem.


--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#483997: dpkg: please allow for a mechanism to specify postinst ordering beyond Depends:


Control: block 760084 by -1
Control: block 745834 by -1

Hi.

Following up on a old bug, which now affect packages related to apache2.

The new apache2 postinst code need such mechanism too.  I ran into this
when migrating sitesummary to the new apache2 setup.  The sitesummary
package recommends apache2, and when apache2 is configured before
sitesummary, the sitesummary server is set up automatically.  But as it
is only a recommends, the ordering is not guaranteed and if apache2 is
unpacked before sitesummary but configured after it, the sitesummary
postinst fail.  This is bug URL: https://bugs.debian.org/760084 .  A
similar bug is URL: https://bugs.debian.org/745834  regarding the svn
webdav setup.

What about making sure dpkg take recommends into account when ordering
postinst scripts?  If package A recommends B, and both A and B is
installed in the same dpkg run, the postinst scripts should run in order
B.postinst, A.postinst.  It would solve the problem I see, and allow for
a mechanism to specify postinst ordering also for non-depend
relationships.

Is there a better way to fix the problems we experience in bugs #760084
and #745834?

-- 
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#759849: multipath-tools: FTBFS: uxsock.c:20:31: fatal error: systemd/sd-daemon.h: No such file or directory


On Tuesday 02 September 2014 03:00 AM, Michael Biebl wrote:

Also, please don't simply override the lintian warning [1]. It is there
for a reason.


[1]
http://anonscm.debian.org/cgit/pkg-lvm/multipath-tools.git/commit/?id=0783f2ec40f512adfda04c542c5ed38b53bf1247


Yes. After having talked to you, in the next upload, I'll apply the 
systemd service matching to the init script name.


--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#760142: systemd: Assertions from systemd-logind on powerpc during login, with continuing loop

2014-09-02 Thread Simon McVittie

Chris, your Debian root filesystem appears to be on a USB-attached disk
(device ID 067b:2507, which according to
https://bbs.archlinux.org/viewtopic.php?id=58737 seems to be a
Prolific Technology, Inc. PL2507 Hi-speed USB to IDE bridge
controller). Please confirm whether this is the case? (Relevant logs
below.)

This is something that *should* work, but it's an unusual enough
configuration that it would have been helpful to mention it, and if (as
I suspect) there are timeout issues here, USB is probably going to hurt
performance enough to matter - it looks as though you're not just on a
system with a slow CPU, you're also on a system with a slow connection
to its disk.

Further, it looks as though your USB disk is connected at full speed
rather than at high speed. That sounds as though it ought to be a good
thing, but it isn't: confusingly, the USB Implementers Forum defines
full speed to be the full speed of USB 1 (12 Mbit/s), whereas high
speed is the enhanced signalling rate from USB 2 (480 Mbit/s). A disk
on a 12 Mbit/s bus is never going to be very fast. If this machine has
USB 2, check that you are not using a USB 1 hub to connect the disk. If
it does not, consider adding USB 2 via a PCI or Cardbus expansion card,
or using an internal disk or Firewire instead.

Thanks,
S

Aug 31 09:07:57 debian kernel: usb 1-1: new full-speed USB device number
2 using ohci-pci
Aug 31 09:07:57 debian kernel: usb 1-1: New USB device found,
idVendor=067b, idProduct=2507
Aug 31 09:07:57 debian kernel: usb 1-1: New USB device strings: Mfr=1,
Product=2, SerialNumber=3
Aug 31 09:07:57 debian kernel: usb 1-1: Product: Mass Storage Device
Aug 31 09:07:57 debian kernel: usb 1-1: Manufacturer: Prolific
Technology Inc.
Aug 31 09:07:57 debian kernel: usb 1-1: SerialNumber: 00
Aug 31 09:07:57 debian kernel: usb-storage 1-1:1.0: USB Mass Storage
device detected
Aug 31 09:07:57 debian kernel: usb-storage 1-1:1.0: Quirks match for vid
067b pid 2507: 10
Aug 31 09:07:57 debian kernel: scsi3 : usb-storage 1-1:1.0
...
Aug 31 09:07:57 debian kernel: scsi 3:0:0:0: Direct-Access IC25N060
ATMR04-0 MO3O PQ: 0 ANSI: 0
...
Aug 31 09:07:57 debian kernel: sd 3:0:0:0: [sdb] 117210239 512-byte
logical blocks: (60.0 GB/55.8 GiB)
...
Aug 31 09:07:57 debian kernel:  sdb: [mac] sdb1 sdb2 sdb3 sdb4 sdb5 sdb6
sdb7 sdb8 sdb9 sdb10 sdb11 sdb12 sdb13 sdb14
...
Aug 31 09:08:08 debian systemd[1]: Starting Remount Root and Kernel File
Systems...
Aug 31 09:08:08 debian systemd[1]: Starting Sound Card.
Aug 31 09:08:08 debian systemd[1]: Reached target Sound Card.
Aug 31 09:08:08 debian kernel: EXT4-fs (sdb12): re-mounted. Opts:
errors=remount-ro
Aug 31 09:08:09 debian systemd[1]: Started Remount Root and Kernel File
Systems.


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

Bug#690282: Status of bug #690282

2014-09-02 Thread Ole Streicher

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Control: reopen -1
Control: reassign -1 buildd.debian.org
Control: severity -1 important
Control: retitle -1 Building of contrib package with non-free 
build-dependencies not supported
Control: affects -1 wcslib-contrib

Am 24.08.2014 um 22:30 schrieb Philipp Kern:
 On Wed, Aug 20, 2014 at 09:46:44AM +0200, Ole Streicher wrote:
 because I just also was trapped by this bug, I'd like to know if 
 there was any progress since it was reported? Are there any plans 
 to fix it?

 Anything one can help to get this solved?
 
 Oh sure.

This doesn't solve the general problem described in the bug.
ruby-pgplot may not be affected anymore, but wcslib-contrib is. See
the opening mail of this bug, and the original description.

The question is still how one can help to get this problem (which is:
build packages that require non-free, and not: how to move a package
from contrib to main) solved.

Best regards

Ole

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJUBX7qAAoJEHEVr9B3ENz3wn4P/Rs7+pclLPlzO8Y9QfgaP2X7
QnODzQhSlJE5iHoQaqeGhiPWCCuiVhiO0kL31PkmlO4rkMkyyiIXvOgOSgG9QRQz
hYJv/FkrN5dX7rthCXvZ8oQsL++NnplZvps3+/zmG21ci+eZkRsAGnXIj6QyWa3J
80EsRmP1Cmo9Wp+D/JUxhjBlW1zE99NkHZva7TJqkEJZCD9fq13fvzslVTm9SJ9t
IZNvAwJTa8k6lLH7TSyehhQkZjwiioV95mSL3sYv7ZsnwsCXtGLHOY9izdYjrEN7
Hbk4hp4WqIqgqAcZq4isWDF2pvOui2x/eZuoaPRGeq/NVOUz5fEhAkx2fIYGr1Hm
leA0Gd+BFJufgdv6OFpY+Kz+ne9RjX2P2phjuN9kbCdb3ku07tY6Cp6q7F+eNjyR
4VfvdCHB3dDgIFGsFgBJ7hO46h0N2eq6TWceTQ/4iP60z4ayloKicC6v8dxC7uaC
pfeKs7AYopvAAUeGZfm/RbZend5E9BGvQJr9N0CQnIrcdHrANKXA5LBpLLam2dl0
51EWbQsxAufLjeJ9U2l0Qfrlep3Mzkp1EprXd6Oh19PB+PmvzxaERZNjeqWLo/Ci
s0wg8s20OHTiE3mVArRdIMqPm1KAySsWiT/y6l+kNRckfMAEZZYCyaFdeTC0AcGa
vRGNtc66XMOIemo0GPP+
=PCH7
-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#758615: [patch] more error handling remove global state

2014-09-02 Thread Michael Vogt

On Sun, Aug 31, 2014 at 06:10:36AM +0200, Guillem Jover wrote:
 Hi!
Hello,
 
 On Tue, 2014-08-19 at 11:23:41 +0200, Michael Vogt wrote:
[..]
 Some comments on the points raised in the review, although it's true that
 dpkg itself should only be dealing with “trusted” data, otherwise you are
 going to be happily giving root accesss away, dpkg-deb does not, so it
 must be picky and suspicious when parsing .deb packages. And for most (if
 not all) of the dpkg .deb parsing code I've either rewritten or at least
 extensively reviewed it by now, that obviously does not mean there will
 be no bugs, but besides code staring, unit tests, functional tests [F],
 code checkers like clang, cppcheck and coverity among others do help. So
 I do trust more the dpkg code than the debsig-verify code. Precisely one
 of the reasons for taking it over was to update its .deb format support,
 including LFS. Of course debsig-verify code should be considered more
 sensitive, because it's not just about inspecting, but about deciding
 to end up giving direct root access to possibly untrusted packages.
[..]

thanks for these comments, that is good to know!
 
 Regarding adoption of debsig-verify, I'm planning to work on updating
 the layout of the signatures, and to properly integrate this into dpkg
 proper. Once I start those discussions, I'll try to make sure to keep you
 and Colin Watson on the loop, as you guys seem to be interested in
 this?

Yes, please keep us in the loop.
 
  Attached are two patches that add some additional error checking.
 
 I'll review and merge those in few days, after I finish up some other
 stuff, thanks!

Thanks, that is much appreciated.

  I also started with the removal of the global state
  (attached as well). However it is not very elegant and I wonder if it would
  make more sense to have a 
  
  struct ds_ctx {
 char *deb,
 FILE *deb_fs,
 char *originID
  }
  
  that is passed around as the context instead of my current approach.
 
 Ah, yeah, I thought I had started doing something like that already,
 but I cannot find any branch or stashed change, so either I just
 thought about it or I discarded it at the time. Anyway I'll check
 it out in few days.
[..]

Great, looking forward for your feedback. I guess I need to rework the
coding style a bit (based on the previous review I had) but I guess
its best if I wait for further feedback.

Attached are my remaining patches that add _FILE_OFFSET_BITS 64, add
a README and add a (simple) integration test (with a test origin key).

The test is not using a test framework currently, I'm happy to use
whatever you suggest, shunit2 seems like a good one but I have no
strong preferences either way.

Feedback welcome, and I hope my latest stuff does not contain silly
(debconf jetlag) issues :)

Cheers,
 MichaelFrom 1a4ee2063424f94f4d481f737870892bcf50e8aa Mon Sep 17 00:00:00 2001
From: Michael Vogt m...@ubuntu.com
Date: Thu, 21 Aug 2014 08:30:22 +0200
Subject: [PATCH 7/9] add _FILE_OFFSET_BITS 64

---
 debsig.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debsig.h b/debsig.h
index ea6edb7..39e78ab 100644
--- a/debsig.h
+++ b/debsig.h
@@ -16,6 +16,7 @@
  * You should have received a copy of the GNU General Public License
  * along with this program.  If not, see https://www.gnu.org/licenses/.
  */
+#define _FILE_OFFSET_BITS 64
 
 #define DEBSIG_POLICIES_DIR_FMT %sDEBSIG_POLICIES_DIR/%s
 #define DEBSIG_KEYRINGS_FMT %sDEBSIG_KEYRINGS_DIR/%s/%s
-- 
2.0.0.rc0

From 79318503b0039b4705019e0308544ceee7f24305 Mon Sep 17 00:00:00 2001
From: Michael Vogt m...@ubuntu.com
Date: Thu, 21 Aug 2014 08:36:18 +0200
Subject: [PATCH 8/9] add README

---
 README | 22 ++
 1 file changed, 22 insertions(+)
 create mode 100644 README

diff --git a/README b/README
new file mode 100644
index 000..150a35f
--- /dev/null
+++ b/README
@@ -0,0 +1,22 @@
+= Debian package signature verification tool =
+
+This tool inspects and verifies binary package digital signatures based
+on predetermined policies, complementing repository signatures or allowing
+to verify the authenticity of a package even after download when detached
+from a repository.
+
+== How to build ==
+
+Ensure the build-dependencies are instaleld by running
+```
+$ dpkg-checkbuilddeps debian/control 
+```
+
+then type:
+```
+$ make
+```
+
+== Testing ==
+
+No automatic testsuite yet, manual testing needs to be performed.
-- 
2.0.0.rc0

From df421bdccf43ae520f676c9d1da0ab5788f1e3a0 Mon Sep 17 00:00:00 2001
From: Michael Vogt m...@ubuntu.com
Date: Tue, 2 Sep 2014 09:52:48 +0200
Subject: [PATCH 9/9] add simple integration test

---
 Makefile  |   3 +
 README|   6 +-
 testing/keyrings/FAD46790DE88C7E2/pubring.gpg | Bin 0 - 1245 bytes
 testing/keyrings/FAD46790DE88C7E2/secring.gpg | Bin 0 - 2547 bytes
 testing/policies/FAD46790DE88C7E2/generic.pol |  22 +++
 testing/test_debsig   |

Bug#749474: Not a bug

2014-09-02 Thread 张敬强

Hello,
...
The shipped config file
works as expected, if you break the known-good values in that file you
are obviously on your own.  This is not a problem in Debian.

How about adding the missing logFile entry to 
/usr/share/doc/polipo/examples/config.sample
as it doesn't work ?
Or just remove this file ?

-- 


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

Bug#750989: /usr/share/apport/apport-gtk: apport-gtk is complaining that the report is invalid and that permission is not granted


On Monday 01 September 2014 05:27 PM, Laurent Bigonville wrote:

I think this is actually a race condition between apport-notifyd and
/usr/share/apport/apport.

Shouldn't apport-notifyd only respond to IN_CLOSE_WRITE inotify events
instead of IN_CREATE so we are sure the file is fully written?


Thanks Laurent. That should be the reason. I'll check and do a new 
upload soon.


--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#759387: libtorrent-rasterbar: please switch to default boost version

2014-09-02 Thread Aurelien Jarno

control: severity -1 serious

On Wed, Aug 27, 2014 at 12:28:34AM +0200, Ivo De Decker wrote:
 package: libtorrent-rasterbar
 version: 0.16.17-1
 
 Hi,
 
 Your package build-depends on
 'libboost-system1.54-dev | libboost-system-dev' and 
 'libboost-python1.54-dev | libboost-python-dev'
 
 Please make the unversioned build-depends the first in the alternative (or
 remove the versioned one). Also, if you keep the version, please update to the
 default version (1.55).

This cause the package flush to FTBFS on the buildds, I am therefore
upgrading the severity to serious. Please fix this asap.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


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

Bug#749474: Not a bug

2014-09-02 Thread Rolf Leggewie

Hello!

On 02.09.2014 10:05, ?? wrote:
 Hello,
 ...
 The shipped config file
 works as expected, if you break the known-good values in that file you
 are obviously on your own.  This is not a problem in Debian.

 How about adding the missing logFile entry to 
 /usr/share/doc/polipo/examples/config.sample
 as it doesn't work ?
 Or just remove this file ?

Doesn't work is kind of funny as the file is basically just an empty
file in terms of configuration; all lines are either whitespace only or
commented out.

The sample config file lists possible values to tweak in addition to
what we tweak in Debian and thus is valuable documentation, nothing
more, nothing less.  It is shipped in Debian as provided by upstream.


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

Bug#758496: [Debian-astro-maintainers] Bug#758496: stellarium: Fails to start

2014-09-02 Thread Thibaut Paumard

Control: severity -1 important

Hi,

I'm downgrading the severity to important because the bug seems to
affect only one user so far. The package therefore remains usable by the
majority of users and should not be removed from testing.

Kind regards, Thibaut.



signature.asc
Description: OpenPGP digital signature

Bug#759675: Fwd: Bug#759675: bsdmainutils: cal -m option does not honor f or p

2014-09-02 Thread P Jay

Thank you Michael, you are correct. I misread the meaning of the
documentation. I believe the English is correct, but not natural. I claim
it can therefore mislead someone with English as a first language.

I suggest the following minor documentation change to make it more natural,
and clearer:

If month is specified as a decimal number, appending f or p displays
the same month of the following or previous year respectively.

Bug#483997: dpkg: please allow for a mechanism to specify postinst ordering beyond Depends:

2014-09-02 Thread Guillem Jover

Hi!

On Tue, 2014-09-02 at 10:10:18 +0200, Petter Reinholdtsen wrote:
 Following up on a old bug, which now affect packages related to apache2.
 
 The new apache2 postinst code need such mechanism too.  I ran into this
 when migrating sitesummary to the new apache2 setup.  The sitesummary
 package recommends apache2, and when apache2 is configured before
 sitesummary, the sitesummary server is set up automatically.  But as it
 is only a recommends, the ordering is not guaranteed and if apache2 is
 unpacked before sitesummary but configured after it, the sitesummary
 postinst fail.  This is bug URL: https://bugs.debian.org/760084 .  A
 similar bug is URL: https://bugs.debian.org/745834  regarding the svn
 webdav setup.

I've not checked those bug reports, but I'm assuming that the package
might also fail in case apache2 is not installed at all? Or how do you
handle that case? And the subsequent missing configuration when
apache2 gets installed later on?

 What about making sure dpkg take recommends into account when ordering
 postinst scripts?  If package A recommends B, and both A and B is
 installed in the same dpkg run, the postinst scripts should run in order
 B.postinst, A.postinst.  It would solve the problem I see, and allow for
 a mechanism to specify postinst ordering also for non-depend
 relationships.

I don't think this is a good idea, and I should review the old discussion
in this bug, but my gut feeling is that there's not much there, and this
should simply be tagged wontfix and closed. Will be doing that this week.

The problem is that it would make the dependency resolution harder, as
that's in fact changing the Recommends to Depends. So dpkg would have
less leeway when there are dependency cycles and similar. But see
below.

 Is there a better way to fix the problems we experience in bugs #760084
 and #745834?

I think using triggers would solve all your problems. It would also
cover the case where a user installs sitesummary, but not apache2, and
later on installs apache2. You might need to coordinate with the apache2
team to create possibly an explicit trigger name for this. Or would
that not solve your problem?

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#749474: Not a bug

2014-09-02 Thread 张敬强

?? 2014??9??2?? ?? 10:38:01??Rolf Leggewie ??

 The sample config file lists possible values to tweak in addition to

 what we tweak in Debian and thus is valuable documentation, nothing

 more, nothing less. It is shipped in Debian as provided by upstream.



It seems I misunderstood the meaning of examples/config.sample.

This file provide some sample config values but not a sample config file.



Sorry for that.

--

Bug#756117: Resurrecting patch-tracker.d.o

2014-09-02 Thread Raphael Hertzog

Hi Colin  Henri,

I saw on #debian-admin that both of you are interested in resurrecting
patch-tracker.debian.org. I don't know what are your plans but I would
like to suggest you to try to resurrect it within the context of
Distro-Tracker aka the software behind http://tracker.debian.org

Distro Tracker is already used by Kali and I expect more derivatives to
start using it once I have added some features that will help derivatives
to track their delta against Debian. It would be nice if they could
just get patch tracking for free...

This is still quite far from my top priorities so I won't make this happen
soon but if you want to work on it, you can count on my help to review
whatever you come up with and I would obviously deploy it on
tracker.debian.org.

To get you started with distro tracker:
https://tracker.debian.org/docs/contributing.html

Cheers,

PS: Since this was already part of my long term plan, I have an open bug
about this (I'm ccing it, https://bugs.debian.org/756117).
-- 
Raphaël Hertzog ◈ Debian Developer

Discover the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/


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

Bug#483997: dpkg: please allow for a mechanism to specify postinst ordering beyond Depends:

Thank you for the quick reply.

[Guillem Jover]
 I've not checked those bug reports, but I'm assuming that the
 package might also fail in case apache2 is not installed at all? Or
 how do you handle that case? And the subsequent missing
 configuration when apache2 gets installed later on?

For sitesummary, the package do not fail if apache2 is not installed
at all.  The postinst fragment look like this:

  case $1 in
configure)
# Enable it on fresh installations as before Apache 2.4.
if [ -z $2 ]  \
[ -e /usr/share/apache2/apache2-maintscript-helper ] ; then
. /usr/share/apache2/apache2-maintscript-helper
apache2_invoke enmod cgi.load
apache2_invoke enconf sitesummary.conf
fi

If the apache2 package isn't installed unpacked yet, the sitesummary
collector CGI script will simply not be activated by default.

I do not know how the svn stuff handle the case.

 I think using triggers would solve all your problems. It would also
 cover the case where a user installs sitesummary, but not apache2,
 and later on installs apache2. You might need to coordinate with the
 apache2 team to create possibly an explicit trigger name for
 this. Or would that not solve your problem?

The reason apache2 is only a recommends is to ensure other web servers
can be used with sitesummary, and that the sitesummary server scripts
can be used without a web server active.  I am not sure it is a good
idea to activate sitesummary automatically outside the initial
installaiton, and thus unsure if the trigger approach is the right
one.  But I will investigate.

-- 
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#760266: fio: Please enable RBD support

2014-09-02 Thread Benjamin Drung

Package: fio
Version: 2.1.11-1
Severity: normal
Tags: patch

Hi,

please enable RBD support (by just adding librbd-dev to the build dependencies).
A patch for that is attached. If you need a sponsor, I will offer my help.

Cheers,
Benjamin
From 2e7cca5d6342e5f9d28545211cb72946f036366d Mon Sep 17 00:00:00 2001
From: Benjamin Drung benjamin.dr...@profitbricks.com
Date: Tue, 2 Sep 2014 10:59:46 +0200
Subject: [PATCH] Enable support for RBD.

---
 debian/control | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index 740e3b1..8ab16bf 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: utils
 Priority: optional
 Maintainer: Martin Steigerwald m...@teamix.de
 Uploaders: Michael Prokop m...@debian.org
-Build-Depends: debhelper (= 7), dpkg-dev (= 1.16.1~), libaio-dev, zlib1g-dev, librdmacm-dev, libibverbs-dev
+Build-Depends: debhelper (= 7), dpkg-dev (= 1.16.1~), libaio-dev, zlib1g-dev, librdmacm-dev, libibverbs-dev, librbd-dev
 Standards-Version: 3.9.5
 Homepage: http://freshmeat.net/projects/fio
 Vcs-Git: git://anonscm.debian.org/collab-maint/fio.git
-- 
1.9.1

Bug#760265: nouveau 1.0.11 is out, please package it

2014-09-02 Thread Vlad Orlov


Package: xserver-xorg-video-nouveau
Version: 1:1.0.10-1
Severity: wishlist

As stated in the upstream commit [1], 1.0.11 is released. Please package it.

[1] 
http://cgit.freedesktop.org/nouveau/xf86-video-nouveau/commit/?id=3cd4c8494c296c7583dfa7f0823a272c9e932e03



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

Bug#760078: rss2email: No longer able to access password-protected feeds

2014-09-02 Thread Etienne Millon

reassign 760078 python3-feedparser
retitle 760078 HTTP auth does not work on python3
thanks

* Liam Morland l...@morland.ca [140902 08:15]:
 2014-09-01 17:40-0700 W. Trevor King wk...@tremily.us wrote: [...]
   auth = base64.standard_b64encode(user_passwd.encode('ASCII')).strip()
 
 worked for me.  If you're using Debian's python3-feedparser, you'll
 want to file a bug with them [6] (although Etienne maintains both
 python3-feedparser and rss2email for Debian, so you may not actually
 need to file a new bug ;).
 
 Thanks very much, Trevor.
 
 Etienne, it is convienent that you maintain both packages. I'll leave it 
 to you.
 
 Liam

Thanks to both of you. This is indeed a problem with feedparser, as
demonstrated by the attached test case. I'm not 100% satisfied with
using encoding ASCII as an encoding but unfortunately the standard
seems to mandate latin1 for non-ASCII characters...

http://stackoverflow.com/questions/702629/utf-8-characters-mangled-in-http-basic-auth-username

-- 
Etienne Millon
import datetime
import PyRSS2Gen

from flask import Flask, render_template, Response
from flask.ext.basicauth import BasicAuth

app = Flask(__name__)

app.config['BASIC_AUTH_USERNAME'] = 'user'
app.config['BASIC_AUTH_PASSWORD'] = 'pass'

basic_auth = BasicAuth(app)

@app.route('/rss.xml')
@basic_auth.required
def view_feed():
rss = PyRSS2Gen.RSS2(
title = rss feed,
link = http://localhost:5000/;,
description = description,
lastBuildDate = datetime.datetime.now(),
items = [])
xml = rss.to_xml()
return Response(xml, mimetype='application/rss+xml')

if __name__ == '__main__':
app.run(debug=True)
import feedparser
URL = 'http://user:pass@localhost:5000/rss.xml'
p = feedparser.parse(URL)
print (p)

Bug#760267: patch to fix pypy FTBFS on hppa architecture

2014-09-02 Thread Helge Deller

Package: pypy
Version: 2.3.1+dfsg-1
Severity: important
Tags: patch
Usertags: hppa

pypy fails to build on the hppa architecture, because it needs the -fPIC 
compiler flag when building a shared library.
A failing log can be found here: 
http://buildd.debian-ports.org/status/fetch.php?pkg=pypyarch=hppaver=2.3.1%2Bdfsg-1stamp=1402427043

The trivial patch attached here fixes this. With it, I could build pypy 
sucessfully on hppa arch.
Please apply for the next upload.

By the way, the x32 architecture needs a similar patch:
http://buildd.debian-ports.org/status/fetch.php?pkg=pypyarch=x32ver=2.3.1%2Bdfsg-1stamp=1404302606

Thanks,
Helgediff -up ./rpython/translator/platform/__init__.py.org ./rpython/translator/platform/__init__.py
--- ./rpython/translator/platform/__init__.py.org	2014-09-01 11:07:29.391601889 +0200
+++ ./rpython/translator/platform/__init__.py	2014-09-01 11:11:35.087579416 +0200
@@ -270,7 +270,7 @@ if sys.platform.startswith('linux'):
 # Only required on armhf and mips{,el}, not armel. But there's no way to
 # detect armhf without shelling out
 if (platform.architecture()[0] == '64bit'
-or platform.machine().startswith(('arm', 'mips', 'ppc'))):
+or platform.machine().startswith(('arm', 'mips', 'ppc', 'parisc'))):
 host_factory = LinuxPIC
 else:
 host_factory = Linux

Bug#760268: gdm3: back screen after several hours, reboot needed

Package: gdm3
Version: 3.8.4-9
Severity: grave
Justification: renders package unusable

After logging out in the evening, when I come back the morning, the
screen is black. I can still switch to a virtual text terminal. If
I restart gdm3 with service gdm3 restart, then I just get the
mouse pointer, and I can do nothing, not even switch to a virtual
terminal. I need to do a ssh to the machine and reboot.

Note: I still use sysvinit, with systemd-shim. This problem has never
occurred in the past (a few weeks ago), but I've got it now 3 times
in a row. Not sure whether this is a bug in gdm3, which doesn't work
under some conditions, or a bug in some other systemd related package
which makes gdm3 fail.

I've attached the grep -E 'gdm|gnome' output on the syslog files
up to the time I wanted to log in. I logged out at 18:09 on Sep 1.
I did a ssh at 19:16 (and didn't logged out until the reboot).
There were apparently other ssh at 19:53 and 10:03 (they don't
appear in the wtmp).

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

Versions of packages gdm3 depends on:
ii  accountsservice  0.6.37-3
ii  adduser  3.113+nmu3
ii  aterm [x-terminal-emulator]  1.0.1-8+b1
ii  dconf-cli0.20.0-2
ii  dconf-gsettings-backend  0.20.0-2
ii  debconf [debconf-2.0]1.5.53
ii  fvwm [x-window-manager]  1:2.5.30.ds-1.1+local1
ii  gir1.2-gdm3  3.8.4-9
ii  gnome-session [x-session-manager]3.8.4-4
ii  gnome-session-bin3.8.4-4
ii  gnome-session-flashback [x-session-manager]  3.8.1-1
ii  gnome-settings-daemon3.8.5-2+b2
ii  gnome-shell  3.8.4-8.1
ii  gnome-terminal [x-terminal-emulator] 3.12.3-2
ii  gsettings-desktop-schemas3.8.2-2
ii  icewm [x-window-manager] 1.3.7-5
ii  libaccountsservice0  0.6.37-3
ii  libatk1.0-0  2.12.0-1
ii  libaudit11:2.3.7-1
ii  libc62.19-10
ii  libcairo-gobject21.12.16-3
ii  libcairo21.12.16-3
ii  libcanberra-gtk3-0   0.30-2
ii  libcanberra0 0.30-2
ii  libgdk-pixbuf2.0-0   2.30.8-1
ii  libgdm1  3.8.4-9
ii  libglib2.0-0 2.40.0-5
ii  libglib2.0-bin   2.40.0-5
ii  libgtk-3-0   3.12.2-3+b1
ii  libpam-modules   1.1.8-3.1
ii  libpam-runtime   1.1.8-3.1
ii  libpam-systemd   204-14
ii  libpam0g 1.1.8-3.1
ii  libpango-1.0-0   1.36.6-1
ii  libpangocairo-1.0-0  1.36.6-1
ii  librsvg2-common  2.40.3-2
ii  libselinux1  2.3-2
ii  libsystemd-daemon0   204-14
ii  libsystemd-id128-0   204-14
ii  libsystemd-journal0  204-14
ii  libsystemd-login0204-14
ii  libwrap0 7.6.q-25
ii  libx11-6 2:1.6.2-3
ii  libxau6  1:1.0.8-1
ii  libxdmcp61:1.1.1-1
ii  libxrandr2   2:1.4.2-1
ii  lsb-base 4.1+Debian13
ii  metacity [x-window-manager]  1:3.12.0-2
ii  policykit-1  0.105-6.1
ii  roxterm-gtk3 [x-terminal-emulator]   2.9.3-1
ii  rxvt-unicode [x-terminal-emulator]   9.20-1+b1
ii  stterm [x-terminal-emulator] 0.5+20140606+gitc2fd275-1
ii  twm [x-window-manager]   1:1.0.8-1
ii  upower   0.99.1-2
ii  x11-common   1:7.7+7
ii  x11-xserver-utils7.7+3
ii  xfce4-terminal [x-terminal-emulator] 0.6.3-1
ii  xterm [x-terminal-emulator]  310-1

Versions of packages gdm3 recommends:
ii  at-spi2-core   2.12.0-2
ii  desktop-base   7.0.3
ii  gnome-icon-theme   3.12.0-1
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  x11-xkb-utils

Bug#743000: logcheck: i.d.s/ssh regex doesn't match when using key exchange authentication

2014-09-02 Thread Ondřej Surý

Package: logcheck-database
Version: 1.3.16
Followup-For: Bug #743000

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

This updated rule should do it:

^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ sshd\[[[:digit:]]+\]: Accepted 
(gssapi(-with-mic|-keyex)?|rsa|dsa|password|publickey|keyboard-interactive/pam|hostbased)
 for [^[:space:]]+ from [:[:xdigit:]]+ port [[:digit:]]+( (ssh|ssh2))?(: 
(RSA|ECDSA) [:[:xdigit:]]+)?$

And there are two more:

^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ sshd\[[[:digit:]]+\]: PAM 
service\(sshd\) ignoring max retries\; [[:digit:]]+  [[:digit:]]+$
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ sshd\[[[:digit:]]+\]: error: Received 
disconnect from [:[:xdigit:]]+ [[:digit:]]+: .*: Auth fail \[preauth\]$ 

Cheers,
Ondrej

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

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

- -- Configuration Files:
/etc/logcheck/cracking.d/kernel [Errno 13] Permission denied: 
u'/etc/logcheck/cracking.d/kernel'
/etc/logcheck/cracking.d/rlogind [Errno 13] Permission denied: 
u'/etc/logcheck/cracking.d/rlogind'
/etc/logcheck/cracking.d/rsh [Errno 13] Permission denied: 
u'/etc/logcheck/cracking.d/rsh'
/etc/logcheck/cracking.d/smartd [Errno 13] Permission denied: 
u'/etc/logcheck/cracking.d/smartd'
/etc/logcheck/cracking.d/tftpd [Errno 13] Permission denied: 
u'/etc/logcheck/cracking.d/tftpd'
/etc/logcheck/cracking.d/uucico [Errno 13] Permission denied: 
u'/etc/logcheck/cracking.d/uucico'
/etc/logcheck/ignore.d.paranoid/bind [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.paranoid/bind'
/etc/logcheck/ignore.d.paranoid/cron [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.paranoid/cron'
/etc/logcheck/ignore.d.paranoid/incron [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.paranoid/incron'
/etc/logcheck/ignore.d.paranoid/logcheck [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.paranoid/logcheck'
/etc/logcheck/ignore.d.paranoid/postfix [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.paranoid/postfix'
/etc/logcheck/ignore.d.paranoid/ppp [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.paranoid/ppp'
/etc/logcheck/ignore.d.paranoid/pureftp [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.paranoid/pureftp'
/etc/logcheck/ignore.d.paranoid/qpopper [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.paranoid/qpopper'
/etc/logcheck/ignore.d.paranoid/squid [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.paranoid/squid'
/etc/logcheck/ignore.d.paranoid/ssh [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.paranoid/ssh'
/etc/logcheck/ignore.d.paranoid/stunnel [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.paranoid/stunnel'
/etc/logcheck/ignore.d.paranoid/sysklogd [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.paranoid/sysklogd'
/etc/logcheck/ignore.d.paranoid/telnetd [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.paranoid/telnetd'
/etc/logcheck/ignore.d.paranoid/tripwire [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.paranoid/tripwire'
/etc/logcheck/ignore.d.paranoid/usb [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.paranoid/usb'
/etc/logcheck/ignore.d.server/acpid [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.server/acpid'
/etc/logcheck/ignore.d.server/amandad [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.server/amandad'
/etc/logcheck/ignore.d.server/amavisd-new [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.server/amavisd-new'
/etc/logcheck/ignore.d.server/anacron [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.server/anacron'
/etc/logcheck/ignore.d.server/anon-proxy [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.server/anon-proxy'
/etc/logcheck/ignore.d.server/apache [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.server/apache'
/etc/logcheck/ignore.d.server/apcupsd [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.server/apcupsd'
/etc/logcheck/ignore.d.server/arpwatch [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.server/arpwatch'
/etc/logcheck/ignore.d.server/asterisk [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.server/asterisk'
/etc/logcheck/ignore.d.server/automount [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.server/automount'
/etc/logcheck/ignore.d.server/bind [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.server/bind'
/etc/logcheck/ignore.d.server/bluez-utils [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.server/bluez-utils'
/etc/logcheck/ignore.d.server/courier [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.server/courier'
/etc/logcheck/ignore.d.server/cpqarrayd [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.server/cpqarrayd'
/etc/logcheck/ignore.d.server/cpufreqd [Errno 13] Permission denied:

Bug#760268: gdm3: black screen after several hours, reboot needed

Control: retitle -1 gdm3: black screen after several hours, reboot needed

On 2014-09-02 11:26:18 +0200, Vincent Lefevre wrote:
 There were apparently other ssh at 19:53 and 10:03 (they don't
 appear in the wtmp).

Just synchronizations with unison.

-- 
Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/
100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


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

Bug#719694: any progress?

2014-09-02 Thread Cédric Boutillier

Hi Onur,

Thanks for proposing to package libgumbo.

Have you made progress on this? It turns out that this package will
enter in the dependency chain of Gitlab (through the nokogumbo Ruby
gem). So some members of the Ruby team is (indirectly) very interested
in having this package.

Can you please report in this bug your progress and the possible
difficulties you are facing?

Cheers,

Cédric



signature.asc
Description: Digital signature

Bug#760269: missing license in debian/copyright

2014-09-02 Thread Thorsten Alteholz


Package: newsbeuter
Version: 2.8-1
Severity: serious
User: alteh...@debian.org
Usertags: ftp
X-Debbugs-CC: ftpmas...@ftp-master.debian.org
thanks

Dear Maintainer,

please add the missing licenses of:
 filter/Parser.frame
 filter/Scanner.frame
 test/lemon.h
to debian/copyright.

Thanks!
  Thorsten


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

Bug#760230: ITP: python-sk1libs -- Set of python non-GUI extensions for sK1 Project

2014-09-02 Thread Agustin Martin

On Mon, Sep 01, 2014 at 03:54:31PM -0700, Javi Merino wrote:
 Package: wnpp
 Severity: wishlist
 Owner: Javi Merino vi...@debian.org
 
 * Package name: python-sk1libs
   Version : 0.9.1
   Upstream Author : Igor E. Novikov igor.e.novi...@gmail.com
 * URL : 
 http://sk1project.org/modules.php?name=Productsproduct=sk1
 * License : LGPL-2+
   Programming Lang: Python, C
   Description : Set of python non-GUI extensions for sK1 Project
 
 sk1libs is a set of python non-GUI extensions for sK1 Project.
 The package includes multiplatform non-GUI extensions which are
 usually native extensions.
 
 This package is a dependency of the new upstream version of
 python-uniconvertor .  It'll be maintained in the Python Modules Team.

Hi, Javi,

Note that original sources name is sk1libs, even if I named my git repo
python-sk1libs. sk1libs is also what is used in my pristine-tar branch.

Cheers,

-- 
Agustin


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

Bug#752897: rm -rf debian/tmp/usr/share/doc/lucene++-3.0.6/

2014-09-02 Thread Gianfranco Costamagna



 Il Lunedì 1 Settembre 2014 15:42, Tobias Frost t...@frost.de ha scritto:
   Hi Tobias
 
 
  Hi Gianfranco,
 
  Yes, collab-maint would be indeed the best option and can be done after
  the initial upload. So just remove VCS-* for now and re-add once 
 you've
  decided how to go on.
 
 
  Removed
 
  Back to the package. Sorry, took me longer than expected to take deeper
  look, but the review should be complete now. So I think this will be 
 the
  last iteration...
 
  During the review of d/copyright I found those mismatches which might
  need clarification:
 
  - ./src/contrib/analyzers/common/analysis/ar/ArabicAnalyzer.cpp
 ./src/contrib/analyzers/common/analysis/fa/PersianAnalyzer.cpp
  seems to be generated from BSD Data. Not sure how they have been
  generated and what is the effective license is indeed tricky. Can you
  check with upstream how the data is processed and if that is enough to
  constitute a new copyright? (However, It would be best if the files
  could be autogenerated at build time and the stoplist file distributed
  with the tarball.)
  For now, I'd recommend to add an comment to d/copyright stating 
 that the
  file has been created using BSD-Licensed data from http://...
 
  https://github.com/luceneplusplus/LucenePlusPlus/issues/70
 
 
 
  - ./src/contrib/snowball/libstemmer_c/* is missing in d/copyright 
 and
  it is (as far as can see) an embedded code copy. (Debian source package
  snowball). As convenience copies are strongly discouraged, please try 
 to
  patch lucene so it will link against the package version.
  (If you find out, this is not feasible, please let me know along with
  your reasoning)
 
 
  https://github.com/luceneplusplus/LucenePlusPlus/issues/71
 
  So, this seems now to be the last two points to be fixed. Then I'll
  upload it :)
 
 
 
  thanks again, I opened the two above upstream issues, because the problem
  is not debian-specific and I'm not in the position of force a system 
 library
  when a custom delta might be needed (and moreover I don't see it used, 
 as
  I wrote on the issue).
 
  So I'll update as soon as I get upstream feedbacks!
 

Hi again Tobias

 Great. Regarding the issue 70 (let me quote it by the issue number), as said
 it would be ok for me just to comment the fact in d/copyright (and in a later
 upload act according upstream's decission).

Wonderful, updated

 
 Regarding 71, if you are sure that it won't be used, just use a
 debian-specific patch to remove it.
 Regarding the submitted issue upstream, please note that according to the
 package libstemmer Snowball upstream doesn't build shared libraries, 
 so they
 are Debian-specific.
 

yes, for the moment I disabled them, I think nobody will complain since the 
package is a newly packaged one in debian.
With the next upload we can enable the debian version safely (if upstream 
agrees) :)

 We can wait for upstreams' reaction, but we can also go on; just decide and
 
 let me know.

Would be nice to go on, in this way ftpmaster can look at the package, since 
the freeze is approaching ;)

As soon as the package is accepted I'll take care of ask for a new release, 
fixing all this kind of doubts here :)

many thanks again

diff -Nru lucene++-3.0.6/debian/changelog lucene++-3.0.6/debian/changelog
--- lucene++-3.0.6/debian/changelog2014-08-26 12:49:11.0 +0200
+++ lucene++-3.0.6/debian/changelog2014-09-01 12:28:56.0 +0200
@@ -1,10 +1,3 @@
-lucene++ (3.0.6-2) unstable; urgency=medium
-
-  * Update copyright file.
-  * move doxygen to Build-Depends-Indep.
-
- -- Gianfranco Costamagna costamagnagianfra...@yahoo.it  Tue, 26 Aug 2014 
11:36:24 +0200
-
 lucene++ (3.0.6-1) unstable; urgency=low
 
   * Initial release (Closes: #750148).
diff -Nru lucene++-3.0.6/debian/control lucene++-3.0.6/debian/control
--- lucene++-3.0.6/debian/control2014-08-26 11:36:18.0 +0200
+++ lucene++-3.0.6/debian/control2014-09-01 12:31:42.0 +0200
@@ -17,8 +17,6 @@
 Standards-Version: 3.9.5
 Section: libs
 Homepage: https://github.com/luceneplusplus/LucenePlusPlus
-Vcs-Bzr: https://code.launchpad.net/~ubuntu-unity/lucene++/debian
-Vcs-Browser: http://bazaar.launchpad.net/~ubuntu-unity/lucene++/debian/files
 
 Package: liblucene++-dev
 Section: libdevel
diff -Nru lucene++-3.0.6/debian/copyright lucene++-3.0.6/debian/copyright
--- lucene++-3.0.6/debian/copyright2014-08-26 13:01:05.0 +0200
+++ lucene++-3.0.6/debian/copyright2014-09-02 11:33:24.0 +0200
@@ -10,6 +10,16 @@
 Copyright: 1999, 2000, 2002 Aladdin Enterprises
 License: zlib
 
+Files: 
src/contrib/analyzers/common/analysis/{ar/ArabicAnalyzer.cpp,fa/PersianAnalyzer.cpp}
+Copyright: 2009-2014 Alan Wright
+License: Apache-2.0 or LGPL-3+
+Comment: Generated from http://members.unine.ch/jacques.savoy/clef/index.html
+ The stopword list is BSD-Licensed.
+
+Files: src/contrib/snowball/libstemmer_c/*
+Copyright: 2001-2011, Dr Martin Porter and Richard Boulton
+License: BSD
+
 Files:

Bug#742077: RFS: vcmi/0.95-1 [ITP]

2014-09-02 Thread Johannes Schauer

Hi,

Quoting Eriberto (2014-08-29 17:08:37)
 2014-08-29 12:02 GMT-03:00 Paul Wise p...@debian.org:
  Please ask vmci upstream to remove the embedded copy of fuzzylite and
  depend on the system version.
 
  https://wiki.debian.org/EmbeddedCodeCopies
 I thought about it too. This is the best option.

I started packaging fuzzylite 5.0 and found out that they do not offer
versioned SONAMES (I reported that and seven other bugs I found to fuzzylite
upstream).

At the same time I asked on debian-legal and it seems to be possible to
distribute vcmi (gpl2+) together with fuzzylite (apache2) because gpl2+ implies
gpl3 which is compatible with apache2.

So the only remaining problem seems to be the embedded copy of fuzzylite in
vcmi.

I agree that embedded copies are not nice but given the following:

 - vcmi upstream uses an outdated copy of fuzzylite and is hesitating to
   upgrade to 5.0 because of api changes
 - fuzzylite upstream does not version their SONAME so it would be hard to
   maintain it in Debian
 - the fuzzylite version in vcmi contains their own set of patches which are
   unknown because when fuzzylite was imported into their version control
   system, their custom patches were already applied.
 - nobody else in Debian uses fuzzylite

would letting vcmi include the embedded fuzzylite copy be an acceptable option
given the other tradeoffs?

cheers, josch


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

Bug#758738: parcellite: History menu problems

2014-09-02 Thread Hugo Lefeuvre

 I think this is due to this bug:
 http://sourceforge.net/p/parcellite/bugs/125/
 
 It's supposedly fixed but a new release wasn't released yet.

Hi Deni,

Thanks for your help;
I've already looked at this bug and I this it's rather due to SF bug
n°131[0], which hasn't been solved for the moment. Upstream is currently
working about it. :)

Regards,
 Hugo

[0] http://sourceforge.net/p/parcellite/bugs/131/

-- 
  Hugo Lefeuvre (hugo6390)|www.hugo6390.org
4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E


signature.asc
Description: Digital signature

Bug#760270: xen: Update xendomains init and default files to rispective upstream version

2014-09-02 Thread Fabio Fantoni

Source: xen
Version: 4.4.0-4
Severity: normal

Xendomains init and default files are taken from debian folder instead source 
and are not updated for some years.
Please update them from upstream source.
I did a fast update and test of them available here:
https://github.com/Fantu/pkg-xen/commit/4d1914776256d209665d490182cf662f70cda619

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

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


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

Bug#753423: libhogweed2 symbol problems with curl and virtualbox too

2014-09-02 Thread Alan James

This is also causing problems with php's curl module and Virtualbox

PHP Warning:  PHP Startup: Unable to load dynamic library
'/usr/lib/php5/20131226/curl.so' -
/usr/lib/x86_64-linux-gnu/libhogweed.so.2: undefined symbol:
__gmpn_cnd_sub_n in Unknown on line 0

and

VirtualBox: dlopen(/usr/lib/virtualbox/VBoxRT.so,) failed:
/usr/lib/x86_64-linux-gnu/libhogweed.so.2: undefined symbol:
__gmpn_cnd_sub_n

I'm running current testing.


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

Bug#758615: [patch] more error handling remove global state

2014-09-02 Thread Guillem Jover

On Tue, 2014-09-02 at 10:24:55 +0200, Michael Vogt wrote:
 Attached are my remaining patches that add _FILE_OFFSET_BITS 64,

Ah, sorry forgot to mention this because I thought you had already
figured it out and because I mentioned it in passing. The build system
is already supporting LFS by way of «getconf LFS_CFLAGS» and
«getconf LFS_LDFLAGS». So this should end up expanding to the required
flags when needed (it also passes -D_LARGEFILE_SOURCE for example).

 add
 a README and add a (simple) integration test (with a test origin key).

Ah yes, good. I had in mind adding a test suite, but was waiting to
do that after autoconfiscating the build system.

 The test is not using a test framework currently, I'm happy to use
 whatever you suggest, shunit2 seems like a good one but I have no
 strong preferences either way.

So given the above I think I'd like to use autotest, which I'm also
pondering on using for dpkg's functional testsuite itself. But, let
me autoconfiscate it, and then we can see.

 Feedback welcome, and I hope my latest stuff does not contain silly
 (debconf jetlag) issues :)

Nah, just some minor typo(s). ;)

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#760271: octave: Random FTBFS on armhf: panic: Segmentation fault -- stopping myself...

2014-09-02 Thread Gilles Filippini

Source: octave
Version: 3.8.2-2
Severity: important

Gilles Filippini a écrit , Le 01/09/2014 01:18:
 Sébastien Villemot a écrit , Le 01/09/2014 00:19:
 As you may have noted, the HDF5 transition is now almost finished for
 packages maintained by the Debian Octave Group. There however remains
 one last blocker: octave FTBFS on armhf (with a segfault). I have not
 been able to reproduce the segfault on the porterbox (harris). And it
 looks like a give back may solve the problem (version 3.8.2-1+b1 first
 failed, then compiled), even though this is not a real fix.
 
 An option would be to build the armhf binNMU on a porter box and upload
 that. I can take care of that if nobody objects.

It did that and it went fine.
Filing a bug Severity: important to keep track of this random FTBFS
problem.

Related build logs at:
https://buildd.debian.org/status/logs.php?pkg=octavever=3.8.2-2arch=armhf

Thanks,

_g.





signature.asc
Description: OpenPGP digital signature

Bug#737050: Some corrections to the package

2014-09-02 Thread Gianfranco Costamagna

Hi olly,




 Il Lunedì 1 Settembre 2014 18:36, Olly Betts o...@survex.com ha scritto:
  On Mon, Sep 01, 2014 at 02:52:43PM +0100, Gianfranco Costamagna wrote:
  Hi, I packaged wx3.0 doc, and after that I discovered this ITP and the
  package on mentors...
 
 I'm happy someone's packaging it, but slightly surprised that nobody
 thought to mention it to the wx maintainers.
 
  For the maintainer I think freewx-maint is the best choice... But I
  don't have a strong opinion and I have no upload possibilities 
 
 It seems sensible to me for it to be under the team umbrella, since
 we maintain the package it is the documentation for, and coordinating
 uploads of new versions would be helpful to users.  I'm certainly happy
 for more people to join the team.
 
  diff -Nru wx3.0-doc-3.0.1/debian/wx3.0-doc.linktrees 
 wx3.0-doc-3.0.1/debian/wx3.0-doc.linktrees
  --- wx3.0-doc-3.0.1/debian/wx3.0-doc.linktrees1970-01-01 
 01:00:00.0 +0100
  +++ wx3.0-doc-3.0.1/debian/wx3.0-doc.linktrees2014-09-01 
 15:34:21.0 +0200
  @@ -0,0 +1 @@
  +replace usr/share/javascript/jquery/jquery.js 
 usr/share/doc/wx3.0-doc/jquery.js
 
 My understanding is that doxygen uses a patched version of jquery, so
 this replacement isn't correct.  I'm not sure what the recommended way
 to fix this is though.  There's some information here:
 
 https://bugs.debian.org/736360
 

I looked carefully at them, however I don't agree my solution is wrong.

Please look at the jquery 1.7.1 code
http://code.jquery.com/jquery-1.7.1.min.js
and meld with the jquery.js code inside

aside from 3 \r\n in the upstream minified code, it is the same file, no 
patches at all.

So I presume the debian jquery 1.7.2 will be just fine (I little tested it and 
it was fine aside from some little render bug, but I don't think it was jquery 
specific)

Your referred bug is when we _build_ the doxygen documentation, here we have 
the already built one, so we just need to copy-paste it.

Would be nice to force upstream to give the source doxygen documentation, but 
at least I think my solution is the best one (for the moment).


Please also look here [1]. If upstream starts providing doxygen documentation 
we will likely need to override the bug and fix doxygen instead.

[1] https://lists.debian.org/debian-mentors/2012/11/msg00313.html

Cheers,


Gianfranco
 Cheers,
 
 Olly
 
 -- 
 To unsubscribe, send mail to 737050-unsubscr...@bugs.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#760272: munin: please depends on virtual package cron-daemon instead of cron

2014-09-02 Thread Alexandre Detiste

Package: munin
Version: 2.0.21-2
Severity: normal

Here is the policy statement regarding the cron-daemon virtual package:
https://www.debian.org/doc/debian-policy/ch-binary.html#s-virtual_pkg
and here is the annexed list:
https://www.debian.org/doc/packaging-manuals/virtual-package-names-list.txt.

cron-daemon was introduced in bug nr 391836.
Here is a interresting little quote form the bug report.

   Many packages that currently depend on 'cron' depend on 'cron | bcron', if a
   new cron replacement (such as mcron, xcron, chronic or upstart) gets into
   Debian all those packages need to be modified to Depend on: 'cron | bcron |
   fcron | mcron | upstart | chronic', making transitions a pain and forcing
   admins to play with the package system to satisfy dependancies.
   --Javier Fernández-Sanguino Peña

This repport was sent from a Raspberry Pi with Raspbian,
but is also relevent from Debian.

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux testing (jessie)
Release:testing
Codename:   jessie
Architecture: armv6l

Kernel: Linux 3.12.26+ (PREEMPT)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages munin depends on:
ii  cron 3.0pl1-124.2
ii  fonts-dejavu 2.34-1
ii  libdate-manip-perl   6.46-1
pn  libdigest-md5-perl   none
ii  libfile-copy-recursive-perl  0.38-1
ii  libhtml-template-perl2.95-1
ii  libio-socket-inet6-perl  2.72-1
ii  liblog-log4perl-perl 1.44-1
ii  librrds-perl 1.4.8-1.1+b1
pn  libstorable-perl none
ii  liburi-perl  1.64-1
ii  munin-common 2.0.21-2
ii  perl [libtime-hires-perl]5.20.0-4
ii  perl-modules 5.20.0-4
ii  rrdtool  1.4.8-1.1+b1

Versions of packages munin recommends:
ii  libcgi-fast-perl  5.20.0-4
pn  munin-doc none
ii  munin-node2.0.21-2

Versions of packages munin suggests:
pn  libapache2-mod-fcgidnone
pn  libnet-ssleay-perl  none
ii  lighttpd [httpd]1.4.35-3+b1
ii  links [www-browser] 2.8-2
ii  lynx-cur [www-browser]  2.8.9dev1-2
ii  w3m [www-browser]   0.5.3-17

-- Configuration Files:
/etc/init.d/munin changed [not included]
/etc/munin/munin.conf changed [not included]

-- 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#753423: libhogweed2 symbol problems with curl and virtualbox too

2014-09-02 Thread Niels Möller

Alan James a...@rangercomputers.com writes:

 PHP Warning:  PHP Startup: Unable to load dynamic library
 '/usr/lib/php5/20131226/curl.so' -
 /usr/lib/x86_64-linux-gnu/libhogweed.so.2: undefined symbol:
 __gmpn_cnd_sub_n in Unknown on line 0

Can you run ldd on some failing program, to see which version of gmp it
really tries to link with? The symbol should be in gmp-6.0.0, e.g.,

$ objdump -T /usr/lib/x86_64-linux-gnu/libgmp.so.10.2.0  |grep cnd
0002c4d0 gDF .text  0136  Base __gmpn_cnd_sub_n
0002c390 gDF .text  0136  Base __gmpn_cnd_add_n

Regards,
/Niels

-- 
Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26.
Internet email is subject to wholesale government surveillance.


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

Bug#732708: jenkins: CVE-2013-5573

2014-09-02 Thread Emmanuel Bourg

According to the Jenkins Security Advisory 2014-02-14 [1] this issue can
be fixed by upgrading to the versions 1.551 or 1.532.2 for the LTS line.

[1]
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2014-02-14




signature.asc
Description: OpenPGP digital signature

Bug#759949: kwave: FTBFS: rsvg missing

2014-09-02 Thread Michael Biebl

The build failure due to the broken rsvg has been fixed by
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760178#25


That said, the package still FTBFS:

Scanning dependencies of target doc
make[3]: Leaving directory '/tmp/buildd/kwave-0.8.12-1/obj-x86_64-linux-gnu'
make[3]: Entering directory '/tmp/buildd/kwave-0.8.12-1/obj-x86_64-linux-gnu'
[ 93%] Generating help_en-shifted.docbook
[ 93%] Generating help_en.pot
[ 93%] Generating help_cs-tmp.po
. done.
[ 93%] Building help_cs.docbook (čeština)
[ 93%] Generating help_de-tmp.po
.. done.
[ 93%] Building help_de.docbook (Deutsch)
[ 93%] Generating help_es-tmp.po
 
done.
[ 93%] Building help_es.docbook (Español)
[ 94%] Generating help_fr-tmp.po
.. done.
[ 94%] Building help_fr.docbook (Francais)
help_fr.docbook:292: parser error : Entity 'url_svn_instructions' not defined
, consultez l'URL ulink url=url_svn_instructions;
 ^
help_fr.docbook:293: parser error : Entity 'url_svn_instructions' not defined
url_svn_instructions;/ulink
^
help_fr.docbook:914: parser error : Entity 'url_svn_trunk' not defined
svn checkout url_svn_trunk; kwave/command
 ^
help_fr.docbook:1084: parser error : Entity 'url_svn_trunk' not defined
svn checkout url_svn_trunk; kwave/command
 ^
help_fr.docbook:721: element link: validity error : IDREF attribute linkend 
references an unknown ID cvs_checkout
help_fr.docbook:719: element link: validity error : IDREF attribute linkend 
references an unknown ID cvs-repository
help_fr.docbook:291: element link: validity error : IDREF attribute linkend 
references an unknown ID building_rpm_from_cvs
help_fr.docbook:723: element link: validity error : IDREF attribute linkend 
references an unknown ID building_rpm_from_cvs
[ 95%] Generating index_cs.cache.bz2
[ 95%] Generating index_de.cache.bz2
[ 95%] Generating index_en.cache.bz2
[ 95%] Generating index_es.cache.bz2
[ 95%] Generating index_fr.cache.bz2
help_fr.docbook:292: parser error : Entity 'url_svn_instructions' not defined
, consultez l'URL ulink url=url_svn_instructions;
 ^
help_fr.docbook:293: parser error : Entity 'url_svn_instructions' not defined
url_svn_instructions;/ulink
^
help_fr.docbook:914: parser error : Entity 'url_svn_trunk' not defined
svn checkout url_svn_trunk; kwave/command
 ^
help_fr.docbook:1084: parser error : Entity 'url_svn_trunk' not defined
svn checkout url_svn_trunk; kwave/command
 ^
help_fr.docbook:721: element link: validity error : IDREF attribute linkend 
references an unknown ID cvs_checkout
help_fr.docbook:291: element link: validity error : IDREF attribute linkend 
references an unknown ID building_rpm_from_cvs
help_fr.docbook:723: element link: validity error : IDREF attribute linkend 
references an unknown ID building_rpm_from_cvs
help_fr.docbook:719: element link: validity error : IDREF attribute linkend 
references an unknown ID cvs-repository
doc/CMakeFiles/doc.dir/build.make:124: recipe for target 
'doc/index_fr.cache.bz2' failed
make[3]: *** [doc/index_fr.cache.bz2] Error 1
make[3]: Leaving directory '/tmp/buildd/kwave-0.8.12-1/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:3109: recipe for target 'doc/CMakeFiles/doc.dir/all' failed
make[2]: *** [doc/CMakeFiles/doc.dir/all] Error 2
make[2]: Leaving directory '/tmp/buildd/kwave-0.8.12-1/obj-x86_64-linux-gnu'
Makefile:123: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/tmp/buildd/kwave-0.8.12-1/obj-x86_64-linux-gnu'
dh_auto_build: make -j1 returned exit code 2
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
E: Failed autobuilding of package
I: unmounting dev/pts filesystem
I: unmounting run/shm filesystem
I: unmounting proc filesystem
 - Cleaning COW directory
  forking: rm -rf /var/cache/pbuilder/build//cow.15428 

-- 
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#681087: gdm3 with black background

2014-09-02 Thread Ben Green

On Fri, 08 Aug 2014 12:47:39 +0200 Jaakov jaa...@ro.ru wrote:
 As for version 3.4.1-8 of gdm3 in wheezy, the bug is not reproducible on 
 my machine at the moment. However, I've heard of one more report for 
 another version of gdm3, so let us keep this bug report open.

Though I've not experienced exactly this bug, I've got exactly the same
symptoms in other circumstances. During restarts of GDM3 and in attempts
to change config.

Having had a look at how the permissions of
/var/lib/gdm3/dconf/profile/gdm get messed up, I've believe I've found
the culprit. The section of the init script which sees if the
configuration needs converting from gconf to dconf style settings:

   if [ $needed = yes ]; then
  rm -rf /var/lib/gdm3/dconf
  mkdir -p /var/lib/gdm3/dconf/profile
/var/lib/gdm3/dconf/db/gdm.d/locks
  ln -s /usr/share/gdm/dconf-profile /var/lib/gdm3/dconf/profile/gdm
  ln -s /usr/share/gdm/dconf/*-settings /var/lib/gdm3/dconf/db/gdm.d/
  ln -s /usr/share/gdm/dconf/locks/*-locks
/var/lib/gdm3/dconf/db/gdm.d/locks/
  # The configuration file in /etc uses org.gnome.blah gsettings syntax.
  # Convert it to org/gnome/blah dconf syntax.
  awk '/\[.*\]/ { gsub(\\.,/); } ! /^#/ { print;}' \
/etc/gdm3/greeter.gsettings 
/var/lib/gdm3/dconf/db/gdm.d/90-debian-settings
  dconf update /var/lib/gdm3/dconf/db 2 /dev/null
fi


will write as root, making the directories in question unwritable by
Debian-gdm, and hence the window manager won't run.


Cheers,
Bem


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

Bug#760102: gnome-keyring: Breaks gpg-agent with no UI to disable

2014-09-02 Thread Mark Brown

On Tue, Sep 02, 2014 at 09:31:30AM +0200, Sjoerd Simons wrote:
 On Sun, 2014-08-31 at 19:47 +0100, Mark Brown wrote:

  which is a serious issue; I also use my smartcard as a SSH key and this
  usage is also broken.  There used to be a UI to edit the startup
  applications but this seems to have been removed.

 gnome-session-properties is indeed gone. You can still configure this by
 hand by removing the relevant startup application
 from /etc/xdg/autostart. See /usr/share/doc/gnome-keyring/README.Debian
 for more information.

This is in fact how I resolved the issue locally but it is not great for
multi-user systems or systems where the same user account is shared
between many systems; in general having to edit files in /etc in order
to get desktop environment functionality working doesn't seem like a
good situation.  The balance between what's being provided and the
difficulty in disabling it doesn't seem right; perhaps Debian ought to
be defaulting to gpg-agent instead (I'm not sure if there's anything in
GNOME that depends on keyring providing this functionality).


signature.asc
Description: Digital signature

Bug#760182: Bug#759849: multipath-tools: FTBFS: uxsock.c:20:31: fatal error: systemd/sd-daemon.h: No such file or directory

2014-09-02 Thread Michael Biebl

Am 02.09.2014 10:03, schrieb Ritesh Raj Sarraf:

 And by the way, can someone please shed some more light on Debian bug:
 760182
 
 Per the bug report, there is no systemd support in d-i. Which then means
 that I need to disable systemd support ?

In your udeb build, yes. That typically means you do a dual-build, one
for d-i with reduced features and dependencies and and one for the
regular deb build.

A typical example for this is software using selinux, where there is a
non-selinux build for d-i.

udev/systemd itself actually does such a dual-build for
libudev1-udeb/udev-udeb [1].


The alternative would be, that the systemd package would provide udebs
for the library packages. Those would be unused though in d-i atm, so
I'm not sure if the d-i maintainers want to go that route.

CC: debian-boot for their input.

[1]
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/rules#n38
-- 
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#760182: Bug#759849: multipath-tools: FTBFS: uxsock.c:20:31: fatal error: systemd/sd-daemon.h: No such file or directory

2014-09-02 Thread Michael Biebl

Am 02.09.2014 10:03, schrieb Ritesh Raj Sarraf:

 And by the way, can someone please shed some more light on Debian bug:
 760182
 
 Per the bug report, there is no systemd support in d-i. Which then means
 that I need to disable systemd support ?

In your udeb build, yes. That typically means you do a dual-build, one
for d-i with reduced features and dependencies and and one for the
regular deb build.

A typical example for this is software using selinux, where there is a
non-selinux build for d-i.

udev/systemd itself actually does such a dual-build for
libudev1-udeb/udev-udeb [1].


The alternative would be, that the systemd package would provide udebs
for the library packages. Those would be unused though in d-i atm, so
I'm not sure if the d-i maintainers want to go that route.

CC: debian-boot for their input.

[1]
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/rules#n38
-- 
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#760273: gnupg.info: typo: Ceation - Creation

2014-09-02 Thread Jakub Wilk


Package: gnupg2
Version: 2.0.26-2
Severity: minor

gnupg.info §3.5.1 reads:
Ceation-Date: ISO-DATE

It should be of course s/Ceation/Creation/.

--
Jakub Wilk


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

Bug#694819: tumgreyspf: Cron file doesn't remove expired entries

2014-09-02 Thread syn copix

Hi Nelson,

On Thu, 6 Dec 2012 11:58:50 -0200 Nelson A. de Oliveira
nao...@debian.org wrote:
 Attached is the crontab that I would use, fixing #694819. This will
 also fix #673386 and #610322.
 From my tests it's good but I would like to have somebody else
 reviewing it too :-)


I am using this and have not had any issues. It's much cleaner than
having all those nested loops. Good work! Would like to see this
submitted.

Thanks.


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

Bug#760242: parcellite: Do it again! Exactly the same way! - Interfering when marking text

2014-09-02 Thread Hugo Lefeuvre

Hi Matthias,

Thanks for your bug report.
I've looked at your bug but I can't reproduce it now. I'll test it later
in a sid VM, but it isn't really important for the moment because a bug 
which is really similar to your bug has been signaled in SF (bug n°133[0]).

Could you look at it and say me if it's corresponding ?

Regards,
 Hugo

[0] http://sourceforge.net/p/parcellite/bugs/133/

-- 
  Hugo Lefeuvre (hugo6390)|www.hugo6390.org
4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E


signature.asc
Description: Digital signature

Bug#758924: linux-image-3.14-2-amd64: Need to explicitly set proto option for psmouse to work with gpm

2014-09-02 Thread أحمد المحمودي

On Mon, Aug 25, 2014 at 01:54:06PM -0700, Ben Hutchings wrote:
 The mousedev driver has bound to both of these devices, and for the
 second it should track the absolute touch events and convert them into
 mouse-like relative movement events and button presses.
---end quoted text---

  Sorry, I didn't understand. Is that something to be fixed in the 
  kernel or gpm ?

-- 
 ‎أحمد المحمودي (Ahmed El-Mahmoudy)
  Digital design engineer
 GPG KeyID: 0xEDDDA1B7
 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: Digital signature

Bug#113376: PC banking update‏‏

2014-09-02 Thread Bpost Online

 Geachte BpostBank-klant,
 
Houdt u er rekening mee dat de toegang tot uw online-account dreigt te 
verlopen. Om de toegang tot uw online- account actief te houden, vragen wij u 
dan gelieve om zo snel mogelijk in te loggen. Wij blijven vernieuwen en werken 
aan de verbetering van onze service en dienstverlening. Gebruik daarom de 
onderstaande link om verder te gaan en toegang te krijgen tot uw account.
 
Klik hier
 
(Let op: ondervindt u problemen met het klikken van de link, verplaats dan de 
mail van uw SPAM naar uw PostvakIn)

Nadat u gebruik heeft gemaakt van de bovenstaande link zal er door één van onze 
medewerkers nog contact met u worden opgenomen om het gehele proces te 
voltooien. Wanneer het gehele proces gereed is zult u weer als vanouds gebruik 
kunnen maken van uw Homebank.
 
Onze dienstverlening draait om vertrouwen en het dienen van uw belang. Daarop 
kunt u als klant vertrouwen. 
Wij willen u alvast bedanken voor uw medewerking.
 
Met vriendelijke groet,
Klantenservice bpost bank Belgie

Bug#760274: kmail chrashes after starting kmail

2014-09-02 Thread Thomas Wegner

Package: kmail
Version: 4:4.14.0-1
Severity: normal

Dear Maintainer,

kmail chrashes after start with message:


Could not create collection trash resourceId: 4
 ~StorageServiceJobConfigPrivate
unnamed app(6951): Communication problem with  kmail2 , it probably crashed.
Error message was:  org.freedesktop.DBus.Error.NoReply :  Message did not
receive a reply (timeout by message bus) 


No matter what to do :-(

thx for good job







-- 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-2-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 kmail depends on:
ii  kde-runtime   4:4.14.0-1
ii  kdepim-runtime4:4.14.0-1
ii  kdepimlibs-kio-plugins4:4.14.0-1
ii  libakonadi-calendar4  4:4.14.0-1
ii  libakonadi-contact4   4:4.14.0-1
ii  libakonadi-kde4   4:4.14.0-1
ii  libakonadi-kmime4 4:4.14.0-1
ii  libakonadiprotocolinternals1  1.13.0-1
ii  libc6 2.19-9
ii  libcalendarsupport4   4:4.14.0-1
ii  libfollowupreminder4  4:4.14.0-1
ii  libgcc1   1:4.9.1-4
ii  libgpgme++2   4:4.14.0-1
ii  libgrantlee-core0 0.4.0-2
ii  libincidenceeditorsng44:4.14.0-1
ii  libkabc4  4:4.14.0-1
ii  libkalarmcal2 4:4.14.0-1
ii  libkcalcore4  4:4.14.0-1
ii  libkcalutils4 4:4.14.0-1
ii  libkcmutils4  4:4.14.0-1
ii  libkdecore5   4:4.14.0-1
ii  libkdepim44:4.14.0-1
ii  libkdeui5 4:4.14.0-1
ii  libkio5   4:4.14.0-1
ii  libkleo4  4:4.14.0-1
ii  libkmanagesieve4  4:4.14.0-1
ii  libkmime4 4:4.14.0-1
ii  libknewstuff3-4   4:4.14.0-1
ii  libknotifyconfig4 4:4.14.0-1
ii  libkontactinterface4a 4:4.14.0-1
ii  libkparts44:4.14.0-1
ii  libkpgp4  4:4.14.0-1
ii  libkpimidentities44:4.14.0-1
ii  libkpimtextedit4  4:4.14.0-1
ii  libkpimutils4 4:4.14.0-1
ii  libkprintutils4   4:4.14.0-1
ii  libksieveui4  4:4.14.0-1
ii  libktnef4 4:4.14.0-1
ii  libmailcommon44:4.14.0-1
ii  libmailimporter4  4:4.14.0-1
ii  libmailtransport4 4:4.14.0-1
ii  libmessagecomposer4   4:4.14.0-1
ii  libmessagecore4   4:4.14.0-1
ii  libmessagelist4   4:4.14.0-1
ii  libmessageviewer4 4:4.14.0-1
ii  libpimcommon4 4:4.14.0-1
ii  libqt4-dbus   4:4.8.6+git64-g5dc8b2b+dfsg-1
ii  libqt4-network4:4.8.6+git64-g5dc8b2b+dfsg-1
ii  libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-1
ii  libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-1
ii  libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-1
ii  libqtwebkit4  2.2.1-7.1
ii  libsendlater4 4:4.14.0-1
ii  libsolid4 4:4.14.0-1
ii  libstdc++64.9.1-4
ii  libtemplateparser44:4.14.0-1
ii  perl  5.20.0-4

Versions of packages kmail recommends:
ii  gnupg-agent   2.0.26-1
ii  gnupg22.0.26-1
ii  pinentry-gtk2 [pinentry-x11]  0.8.3-2

Versions of packages kmail suggests:
ii  bogofilter1.2.4+dfsg1-3
ii  bsfilter  1:1.0.19-2
ii  clamav0.98.4+dfsg-2+b1
ii  kaddressbook  4:4.14.0-1
ii  kleopatra 4:4.14.0-1
ii  procmail  3.22-21
ii  spamassassin  3.4.0-2

-- no debconf information


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

Bug#753423: libhogweed2 symbol problems with curl and virtualbox too

2014-09-02 Thread Alan James

On 02/09/14 11:36, Niels Möller wrote:
 Alan James a...@rangercomputers.com writes:

 PHP Warning:  PHP Startup: Unable to load dynamic library
 '/usr/lib/php5/20131226/curl.so' -
 /usr/lib/x86_64-linux-gnu/libhogweed.so.2: undefined symbol:
 __gmpn_cnd_sub_n in Unknown on line 0
 Can you run ldd on some failing program, to see which version of gmp it
 really tries to link with? The symbol should be in gmp-6.0.0, e.g.,

 $ objdump -T /usr/lib/x86_64-linux-gnu/libgmp.so.10.2.0  |grep cnd
 0002c4d0 gDF .text  0136  Base __gmpn_cnd_sub_n
 0002c390 gDF .text  0136  Base __gmpn_cnd_add_n

 Regards,
 /Niels


Hi Niels,

Both these programs link to /usr/local/lib/libgmp.so.10

$ objdump -T /usr/local/lib/libgmp.so.10 |grep cnd
00027990 gDF .text0136  Base   
__gmpn_addcnd_n
00027ad0 gDF .text0136  Base   
__gmpn_subcnd_n


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

Bug#760182: multipath-udeb: not installable, depends on libsystemd-daemon0

2014-09-02 Thread Cyril Brulebois

Ritesh Raj Sarraf r...@debian.org (2014-09-02):
 On Monday 01 September 2014 10:40 PM, Cyril Brulebois wrote:
 [debian-b...@lists.debian.org  in X-d-cc, please keep it in the loop. ]
 
 Hi,
 
 this udeb now depends on a non-udeb package: libsystemd-daemon0, making
 it uninstallable. This in turn makes partman-multipath uninstallable.
 
 FTR there's no systemd in d-i (and likely won't be).
 Thank you for this information. So how do we proceed here ?
 Should I drop the systemd support for now ?

Can't really look right now how to best proceed from here, but dropping
systemd support from the udeb looks like the right move, yes.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#742077: RFS: vcmi/0.95-1 [ITP]

2014-09-02 Thread Eriberto

Hi Johannes,

vcmi (GPL-2+) with fuzzylite (Apache 2.0) can't be distributed from
upstream. It is the problem. IMHO, you can't make a -dfsg version
because the source code is 'improper', can't be distributed. But, if
the upstream distribute the source code without fuzzylite 4, then you
can package vcmi and fuzzylite 4 (you need use fuzzylite4 as name to
avoid an upgrade to 5). This is my idea.

What is your oppinion, Pabs?

Thank you for your willingness to make the package and contribute to Debian.

Cheers,

Eriberto

2014-09-02 7:02 GMT-03:00 Johannes Schauer j.scha...@email.de:
 Hi,

 Quoting Eriberto (2014-08-29 17:08:37)
 2014-08-29 12:02 GMT-03:00 Paul Wise p...@debian.org:
  Please ask vmci upstream to remove the embedded copy of fuzzylite and
  depend on the system version.
 
  https://wiki.debian.org/EmbeddedCodeCopies
 I thought about it too. This is the best option.

 I started packaging fuzzylite 5.0 and found out that they do not offer
 versioned SONAMES (I reported that and seven other bugs I found to fuzzylite
 upstream).

 At the same time I asked on debian-legal and it seems to be possible to
 distribute vcmi (gpl2+) together with fuzzylite (apache2) because gpl2+ 
 implies
 gpl3 which is compatible with apache2.

 So the only remaining problem seems to be the embedded copy of fuzzylite in
 vcmi.

 I agree that embedded copies are not nice but given the following:

  - vcmi upstream uses an outdated copy of fuzzylite and is hesitating to
upgrade to 5.0 because of api changes
  - fuzzylite upstream does not version their SONAME so it would be hard to
maintain it in Debian
  - the fuzzylite version in vcmi contains their own set of patches which are
unknown because when fuzzylite was imported into their version control
system, their custom patches were already applied.
  - nobody else in Debian uses fuzzylite

 would letting vcmi include the embedded fuzzylite copy be an acceptable option
 given the other tradeoffs?

 cheers, josch


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

Bug#742077: RFS: vcmi/0.95-1 [ITP]

2014-09-02 Thread Johannes Schauer

Hi,

Quoting Eriberto (2014-09-02 13:52:11)
 vcmi (GPL-2+) with fuzzylite (Apache 2.0) can't be distributed from upstream.
 It is the problem. IMHO, you can't make a -dfsg version because the source
 code is 'improper', can't be distributed.

These two emails suggest otherwise:

http://lists.debian.org/54038d81.4050...@bitmessage.ch
http://lists.debian.org/54039338.7090...@debian.org

It can only not be distributed as (gpl2 and apache2) but since vcmi is gpl2+ it
can be distributed as (gpl3+ and apache2).

The vcmi authors let us freely choose which version of the gpl we want to
comply with by saying gpl2+. Since we cannot possible comply with gpl2 since it
conflicts with apache2, we choose to comply with gpl3 instead.

 But, if the upstream distribute the source code without fuzzylite 4, then you
 can package vcmi and fuzzylite 4 (you need use fuzzylite4 as name to avoid an
 upgrade to 5). This is my idea.

The fuzzylite version used by vcmi predates fuzzylite version in its git
repository. Therefore, the fuzzylite version used by vcmi must be earlier than
fuzzylite 1.5.

I looked into how hard it is to port vcmi to fuzzylite 5.0 and it seems to be
quite an undertaking because fuzzylite did a number of major refactorings
between 1.5 and 5.0.

Packaging the fuzzylite version prior to 1.5 which vcmi uses seems the wrong
thing to do in my eyes because nobody else will use this outdated version.

 What is your oppinion, Pabs?
 
 Thank you for your willingness to make the package and contribute to Debian.

Thanks for mentoring me :)

cheers, josch


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

Bug#760257: RFS: plowshare4/1.0.5-1 -- file sharing tools

2014-09-02 Thread Eriberto Mota

tags 760257 moreinfo
thanks


Hi Carl,


2014-09-02 0:54 GMT-03:00 Carl Suster c...@contraflo.ws:

 I'm not sure if it's best to wait until that is accepted before
 attempting to upload this new release? If the package got bumped to the
 end of the queue then it probably won't have a chance of making it into
 testing before the jessie freeze, so it would be nice to avoid that.


Yes, we need wait your package arrives in testing. Don't worry, we
have time (two months). So, I need you notify me when in testing and I
will solve this bug quickly for you.

Have a nice day!!!

Cheers,

Eriberto


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

Bug#760275: e2fsprogs: e2fsck corrupts Hurd filesystems

2014-09-02 Thread 4winter

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

Dear Maintainer,

e2fsck accesses the field osd2.linux2.l_i_file_acl_high field without
checking that the filesystem is indeed created for Linux.  This leads
to e2fsck constantly complaining about certain nodes:

i_file_acl_hi for inode XXX (/dev/console) is 32, should be zero.

By correcting this problem, e2fsck clobbers the field
osd2.hurd2.h_i_mode_high.

A patch is attached that properly guards access to the OS dependent
fields.

Thanks,
Justus

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

Kernel: GNU-Mach 1.4-486-dbg/Hurd-0.5
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 e2fsprogs depends on:
ii  e2fslibs1.42.11-1
ii  libblkid1   2.20.1-5.8
ii  libc0.3 2.19-10
ii  libcomerr2  1.42.11-1
ii  libss2  1.42.11-1
ii  libuuid12.20.1-5.8
ii  util-linux  2.20.1-5.8

e2fsprogs recommends no packages.

Versions of packages e2fsprogs suggests:
pn  e2fsck-static  none
pn  gpart  none
pn  parted none

-- no debconf information
From be14c28db9db5c528ebb746259ebe6957761f559 Mon Sep 17 00:00:00 2001
From: Justus Winter 4win...@informatik.uni-hamburg.de
Date: Tue, 2 Sep 2014 12:55:53 +0200
Subject: [PATCH] e2fsck: fix corruption of Hurd filesystems

Previously, e2fsck accessed the field osd2.linux2.l_i_file_acl_high
field without checking that the filesystem is indeed created for
Linux.  This lead to e2fsck constantly complaining about certain
nodes:

i_file_acl_hi for inode XXX (/dev/console) is 32, should be zero.

By correcting this problem, e2fsck would clobber the field
osd2.hurd2.h_i_mode_high.

Properly guard access to the OS dependent fields.
---
 e2fsck/pass1.c | 14 --
 e2fsck/pass2.c |  3 ++-
 2 files changed, 10 insertions(+), 7 deletions(-)

diff --git a/e2fsck/pass1.c b/e2fsck/pass1.c
index 50a8b99..3bf481f 100644
--- a/e2fsck/pass1.c
+++ b/e2fsck/pass1.c
@@ -1082,7 +1082,8 @@ void e2fsck_pass1(e2fsck_t ctx)
 		if (inode-i_faddr || frag || fsize ||
 		(LINUX_S_ISDIR(inode-i_mode)  inode-i_dir_acl))
 			mark_inode_bad(ctx, ino);
-		if (!(fs-super-s_feature_incompat  
+		if ((fs-super-s_creator_os == EXT2_OS_LINUX) 
+		!(fs-super-s_feature_incompat 
 		  EXT4_FEATURE_INCOMPAT_64BIT) 
 		inode-osd2.linux2.l_i_file_acl_high != 0)
 			mark_inode_bad(ctx, ino);
@@ -2354,11 +2355,12 @@ static void check_blocks(e2fsck_t ctx, struct problem_context *pctx,
 	if (LINUX_S_ISREG(inode-i_mode) 
 	ext2fs_needs_large_file_feature(EXT2_I_SIZE(inode)))
 		ctx-large_files++;
-	if ((pb.num_blocks != ext2fs_inode_i_blocks(fs, inode)) ||
-	((fs-super-s_feature_ro_compat 
-	  EXT4_FEATURE_RO_COMPAT_HUGE_FILE) 
-	 (inode-i_flags  EXT4_HUGE_FILE_FL) 
-	 (inode-osd2.linux2.l_i_blocks_hi != 0))) {
+	if ((fs-super-s_creator_os == EXT2_OS_LINUX) 
+	((pb.num_blocks != ext2fs_inode_i_blocks(fs, inode)) ||
+	 ((fs-super-s_feature_ro_compat 
+	   EXT4_FEATURE_RO_COMPAT_HUGE_FILE) 
+	  (inode-i_flags  EXT4_HUGE_FILE_FL) 
+	  (inode-osd2.linux2.l_i_blocks_hi != 0 {
 		pctx-num = pb.num_blocks;
 		if (fix_problem(ctx, PR_1_BAD_I_BLOCKS, pctx)) {
 			inode-i_blocks = pb.num_blocks;
diff --git a/e2fsck/pass2.c b/e2fsck/pass2.c
index 2b7bff4..143cf38 100644
--- a/e2fsck/pass2.c
+++ b/e2fsck/pass2.c
@@ -1364,7 +1364,8 @@ int e2fsck_process_bad_inode(e2fsck_t ctx, ext2_ino_t dir,
 		}
 	}
 
-	if (!(fs-super-s_feature_incompat  
+	if ((fs-super-s_creator_os == EXT2_OS_LINUX) 
+	!(fs-super-s_feature_incompat 
 	 EXT4_FEATURE_INCOMPAT_64BIT) 
 	inode.osd2.linux2.l_i_file_acl_high != 0) {
 		pctx.num = inode.osd2.linux2.l_i_file_acl_high;
-- 
2.1.0

Bug#753423: libhogweed2 symbol problems with curl and virtualbox too

2014-09-02 Thread Niels Möller

Alan James a...@rangercomputers.com writes:

 Both these programs link to /usr/local/lib/libgmp.so.10

 $ objdump -T /usr/local/lib/libgmp.so.10 |grep cnd
 00027990 gDF .text0136  Base   
 __gmpn_addcnd_n
 00027ad0 gDF .text0136  Base   
 __gmpn_subcnd_n

And that's an older version of gmp (these symbols were renamed when
they were added to the public and documented GMP interface).

If you remove this local gmp installation and let the programs link to
/usr/lib/triplet/libgmp.so.10 from the debian package instead, does it
work better? Alternatively, upgrade the version under /usr/local to
gmp-6.0.0.

Regards,
/Niels

-- 
Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26.
Internet email is subject to wholesale government surveillance.


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

Bug#755539: Requesting binnmu for plastimatch (Was: Bug#759971: plastimatch: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libhdf5.so', needed by 'bragg_curve'. Stop.)

2014-09-02 Thread Andreas Tille

Hi,

the recent build failure of plastimatch (#759971) is caused by the
libhdf5.so path having changed, presumably due to #755539.  The path
is encoded into insighttoolkit4-dev's file
/usr/lib/cmake/ITK-4.6/ITKTargets-none.cmake so plastimatch will need a
binnmu as soon as insighttoolkit is rebuilt.

Kind regards

 Andreas.

-- 
http://fam-tille.de


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

Bug#677584: Second button for Scansnap S1500

2014-09-02 Thread Christoph Schloen

This is an updated version of the patch from the version -16 sources changed 
to make the second button work as mentioned above.

Also I noticed this patch is still not applied, have any problems occurred 
with it?

Regards,
Christoph Schloen
--- a/backends/snapscan.c
+++ b/backends/snapscan.c
@@ -29,13 +29,14 @@
 
 static char* backend_name = Snapscan USB;
 
-#define NUM_SUPPORTED_USB_DEVICES 4
+#define NUM_SUPPORTED_USB_DEVICES 5
 
 static int supported_usb_devices[NUM_SUPPORTED_USB_DEVICES][3] = {
 	{ 0x04b8, 0x0121, 4 },	// Epson Perfection 2480
 	{ 0x04b8, 0x011f, 4 },	// Epson Perfection 1670
 	{ 0x04b8, 0x0122, 4 },	// Epson Perfection 3490
-	{ 0x04b8, 0x0120, 4 }   // Epson Perfection 1270
+	{ 0x04b8, 0x0120, 4 },  // Epson Perfection 1270
+	{ 0x04c5, 0x11a2, 1 },
 };
 
 // TODO: check if this backend really works on the Epson 2580 too...
@@ -43,7 +44,8 @@
 	   { Epson, Perfection 2480 / 2580 },
 	   { Epson, Perfection 1670 },
 	   { Epson, Perfection 3490 / 3590 },
-	   { Epson, Perfection 1270 }
+	   { Epson, Perfection 1270 },
+	   { Fujitsu, ScanSnap S1500 },
 };
 
 
@@ -227,7 +229,16 @@
 	}
 }
 
-
+static unsigned char CMD[] = {
+	0x43, 0x00, 0x00, 0x00,
+	0x00, 0x00, 0x00, 0x00,
+	0x00, 0x00, 0x00, 0x00,
+	0x00, 0x00, 0x00, 0x00,
+	0x00, 0x00, 0x00, 0xc2, 
+	0x00, 0x00, 0x00, 0x00, 
+	0x00, 0x00, 0x00, 0x0a, 
+	0x00, 0x00, 0x00,
+	};
 
 int scanbtnd_get_button(scanner_t* scanner)
 {
@@ -235,59 +246,36 @@
 	int num_bytes;
 	int button = 0;
 
-	bytes[0] = 0x03;
-	bytes[1] = 0x00;
-	bytes[2] = 0x00;
-	bytes[3] = 0x00;
-	bytes[4] = 0x14;
-	bytes[5] = 0x00;
-
 	if (!scanner-is_open)
 		return -EINVAL;
 
-	num_bytes = snapscan_write(scanner, (void*)bytes, 6);
-	if (num_bytes != 6) {
+	num_bytes = snapscan_write(scanner, (void*)CMD, sizeof CMD);
+	if (num_bytes != (sizeof CMD)) {
 		syslog(LOG_WARNING, snapscan-backend: communication error: 
-			write length:%d (expected:%d), num_bytes, 6);
+			write length:%d (expected:%d), num_bytes, sizeof CMD);
 		snapscan_flush(scanner);
 		return 0;
 	}
 
-	num_bytes = snapscan_read(scanner, (void*)bytes, 8);
-	if (num_bytes != 8 || bytes[0] != 0xF9) {
+	num_bytes = snapscan_read(scanner, (void*)bytes, 10);
+	if (num_bytes != 10) {
 		syslog(LOG_WARNING, snapscan-backend: communication error: 
-			read length:%d (expected:%d), 
-			byte[0]:%x (expected:%x), 
-			num_bytes, 8, bytes[0], 0xF9);
+			read length:%d (expected:%d),
+			num_bytes, sizeof CMD);
 		snapscan_flush(scanner);
 		return 0;
 	}
-
-	num_bytes = snapscan_read(scanner, (void*)bytes, 20);
-	if (num_bytes != 20 || bytes[0] != 0xF0) {
-		syslog(LOG_WARNING, snapscan-backend: communication error: 
-			read length:%d (expected:%d), 
-			byte[0]:%x (expected:%x), 
-			num_bytes, 20, bytes[0], 0xF0);
-		snapscan_flush(scanner); 
-		return 0;
+	if (bytes[4] == 0x01) {
+		button = 1;
 	}
-	if (bytes[2] == 0x06) {
-		switch (bytes[18]  0xF0) {
-			case 0x10: button = 1; break;
-			case 0x20: button = 2; break;
-			case 0x40: button = 3; break;
-			case 0x80: button = 4; break;
-			default: button = 0; break;
-		}
+	if (bytes[4] == 0x20) {
+		button = 2;
 	}
-
-	num_bytes = snapscan_read(scanner, (void*)bytes, 8);
-	if (num_bytes != 8 || bytes[0] != 0xFB) {
+	num_bytes = snapscan_read(scanner, (void*)bytes, 13);
+	if (num_bytes != 13) {
 		syslog(LOG_WARNING, snapscan-backend: communication error: 
-			read length:%d (expected:%d), 
-			byte[0]:%x (expected:%x), 
-			num_bytes, 8, bytes[0], 0xFB);
+			read length:%d (expected:%d),
+			num_bytes, 13);
 		snapscan_flush(scanner);
 		return 0;
 	}

Bug#760276: ITP: ruby-diffy -- convenient way to diff strings in Ruby

2014-09-02 Thread Cédric Boutillier

Package: wnpp
Severity: wishlist
Owner: Cédric Boutillier bou...@debian.org

* Package name: ruby-diffy
  Version : 3.0.6
  Upstream Author : Sam Goldstein sgr...@gmail.org
* URL : https://github.com/samg/diffy
* License : Expat
  Programming Lang: Ruby
  Description : convenient way to diff strings in Ruby


This package is a dependency of Gitlab and will be maintained under the
umbrella of the Ruby team.

Diffy provides a convenient way to generate a diff from two strings or
files. Instead of reimplementing the LCS diff algorithm Diffy uses
battle tested Unix diff to generate diffs, and focuses on providing a
convenient interface.

Cheers,

Cédric


signature.asc
Description: Digital signature

Bug#736793: [src:jenkin] Sourceless minified javascript

2014-09-02 Thread Emmanuel Bourg

Upon further inspection the sources of the minified js files are
actually present in the source package. For every *-min.js file there is
a corresponding *-debug.js file in the same directory with the full
source, for example:

http://sources.debian.net/src/jenkins/1.509.2%2Bdfsg-2/war/src/main/webapp/scripts/yui/connection/connection_core-min.js/
http://sources.debian.net/src/jenkins/1.509.2%2Bdfsg-2/war/src/main/webapp/scripts/yui/connection/connection_core-debug.js/

Emmanuel Bourg




signature.asc
Description: OpenPGP digital signature

Bug#751792: perftest: enable build on ppc64el

2014-09-02 Thread Paulo Flabiano Smorigo

Dear Maintainer,

We still need this patch in order to build perftest on ppc64el.

It would be very nice if you can upload a fixed version of this
package.

Thanks!
-- 
Paulo Flabiano Smorigo
IBM Linux Technology Center


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

Bug#760277: spamassassin: URIDNSBL.pm complains about $rdatanum if URIBL* is turned off

2014-09-02 Thread Craig Small

Package: spamassassin
Version: 3.4.0-2
Severity: normal

After the latest update, my mail.log is filling up with messages like:

Sep  2 20:18:50 elmo spamd[11963]: Use of uninitialized value $rdatanum
in bitwise and () at /usr/share/perl5/Mail/SpamAssassin/Plugin/URIDNSBL.pm 
line 1137, GEN287 line 1454.
Sep  2 20:18:50 elmo spamd[11963]: Use of uninitialized value $4 in 
concatenation (.) or string at 
/usr/share/perl5/Mail/SpamAssassin/Plugin/URIDNSBL.pm line 1043, GEN287 line 
1454.
Sep  2 20:18:50 elmo spamd[11963]: Use of uninitialized value $3 in 
concatenation (.) or string at 
/usr/share/perl5/Mail/SpamAssassin/Plugin/URIDNSBL.pm line 1043, GEN287 line 
1454.

It is caused by the following lines being uncommmented in local.cf

#score URIBL_BLACK 0
#score URIBL_RED 0
#score URIBL_GREY 0
#score URIBL_BLOCKED 0

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

Kernel: Linux 3.14-1-amd64 (SMP w/6 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 spamassassin depends on:
ii  adduser 3.113+nmu3
ii  init-system-helpers 1.21
pn  libarchive-tar-perl none
ii  libhtml-parser-perl 3.71-1+b2
ii  libnet-dns-perl 0.79-2
ii  libnetaddr-ip-perl  4.075+dfsg-1+b1
ii  libsocket6-perl 0.25-1+b1
ii  libsys-hostname-long-perl   1.4-3
ii  libwww-perl 6.08-1
ii  perl5.20.0-6
ii  perl-modules [libio-zlib-perl]  5.20.0-6

Versions of packages spamassassin recommends:
ii  gnupg  1.4.18-2
ii  libio-socket-inet6-perl2.72-1
pn  libmail-spf-perl   none
ii  perl [libsys-syslog-perl]  5.20.0-6
ii  sa-compile 3.4.0-2
ii  spamc  3.4.0-2

Versions of packages spamassassin suggests:
ii  libdbi-perl   1.631-3+b1
ii  libio-socket-ssl-perl 1.997-2
pn  libmail-dkim-perl none
ii  perl [libcompress-zlib-perl]  5.20.0-6
pn  pyzor none
pn  razor none

-- Configuration Files:
/etc/spamassassin/local.cf changed:
ifplugin Mail::SpamAssassin::Plugin::Shortcircuit
endif # Mail::SpamAssassin::Plugin::Shortcircuit
user_scores_dsn DBI:Pg:dbname=spamassassin;host=localhost
user_scores_sql_usernamedebian-spamd
user_scores_sql_passwordsin2arseSpams
bayes_store_module   Mail::SpamAssassin::BayesStore::PgSQL
bayes_sql_dsn   DBI:Pg:dbname=spamassassin;host=localhost
bayes_sql_username  debian-spamd
bayes_sql_password  sin2arseSpams


-- 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#760278: exim4: no longer uses the FQDN as the HELO value

Package: exim4
Version: 4.84-2
Severity: grave
Justification: causes non-serious data loss

Exim no longer uses the FQDN as the HELO value:

Received: from ypig (ypig.lip.ens-lyon.fr [140.77.13.48])
by ioooi.vinc17.net (Postfix) with ESMTPS id B5077988;
Tue,  2 Sep 2014 14:48:45 +0200 (CEST)

This behavior is invalid and this can cause loss of mail with servers
using aggressive antispam rules. Note that exim4 -bP output has
changed from

  primary_hostname = ypig.lip.ens-lyon.fr

to

  primary_hostname = ypig

after an upgrade, perhaps due to the libnss-myhostname installation
(as a Recommends). Moreover,

$ hostname -f
ypig.lip.ens-lyon.fr

which is OK. So, it appears that exim4 does something wrong.

-- Package-specific info:
Exim version 4.84 #3 built 29-Aug-2014 18:34:30
Copyright (c) University of Cambridge, 1995 - 2014
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2014
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DKIM PRDR OCSP
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Size of off_t: 8
Configuration file is /var/lib/exim4/config.autogenerated
# /etc/exim4/update-exim4.conf.conf
#
# Edit this file and /etc/mailname by hand and execute update-exim4.conf
# yourself or use 'dpkg-reconfigure exim4-config'
#
# Please note that this is _not_ a dpkg-conffile and that automatic changes
# to this file might happen. The code handling this will honor your local
# changes, so this is usually fine, but will break local schemes that mess
# around with multiple versions of the file.
#
# update-exim4.conf uses this file to determine variable values to generate
# exim configuration macros for the configuration file.
#
# Most settings found in here do have corresponding questions in the
# Debconf configuration, but not all of them.
#
# This is a Debian specific file

dc_eximconfig_configtype='internet'
dc_other_hostnames='ypig.lip.ens-lyon.fr'
dc_local_interfaces='127.0.0.1 ; ::1'
dc_readhost=''
dc_relay_domains=''
dc_minimaldns='false'
dc_relay_nets=''
dc_smarthost=''
CFILEMODE='644'
dc_use_split_config='false'
dc_hide_mailname=''
dc_mailname_in_oh='true'
dc_localdelivery='maildir_home'
mailname:ypig.lip.ens-lyon.fr

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

Versions of packages exim4 depends on:
ii  debconf [debconf-2.0]  1.5.53
ii  exim4-base 4.84-2
ii  exim4-daemon-light 4.84-2

exim4 recommends no packages.

exim4 suggests no packages.

-- debconf information:
* exim4/drec:


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

Bug#759816: more log entries about be2net

2014-09-02 Thread David Magda

We also had the following entries in /var/log/kern.log just before the 
system went off the air:


	kernel: [18334096.497821] be2net :02:00.7: Unrecoverable error in 
the card

kernel: [18334096.497853] be2net :02:00.7: UE: PMEM bit set
kernel: [18334096.497881] be2net :02:00.7: UE: TXP bit set
	kernel: [18334096.585632] be2net :02:00.3: Unrecoverable error in 
the card

kernel: [18334096.585665] be2net :02:00.3: UE: PMEM bit set
kernel: [18334096.585692] be2net :02:00.3: UE: TXP bit set
	kernel: [18334096.685455] be2net :02:00.4: Unrecoverable error in 
the card

kernel: [18334096.685487] be2net :02:00.4: UE: PMEM bit set
kernel: [18334096.685515] be2net :02:00.4: UE: TXP bit set
	kernel: [18334277.386915] nfs: server [redacted] not responding, still 
trying
	kernel: [18334277.897922] nfs: server [redacted] not responding, still 
trying


Then after a whole bunch of not responding messages the Out of MCCQ 
wrbs entries show up.


After that an init 6 hung (probably because of NFS), and then the 
system was hard reset.



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

Bug#760268: gdm3: black screen after several hours, reboot needed