Bug#563748: installation-reports: Provide script to update resume and uswsusp.conf files?

[Boris Barbour]

Thanks for looking at this old bug. Yes, fine by me to close the bug. Perhaps 
my main problem as an inexperienced user was just discovering which package 
should generate the files (i.e. it was less obvious for /etc/initramfs-
tools/conf.d/resume). Maybe this discussion will help others in the same 
situation.

> >Quoting Boris Barbour (boris.barb...@ens.fr):
> >> On migrating my long-running system to a new disk (by cp), I discovered
> >> that /etc/uswsusp.conf and /etc/initramfs-tools/conf.d/resume then
> >> contained stale information regarding the partition to resume from.
> >> apt-file reports no package as responsible for these files; they appear
> >> to have been written out by the installer. It might be useful to
> >> provide a small script to update these files ("update-resume-info"?).
> >> Changes in the way devices are represented or the configuration of
> >> other disks in the computer may also be a scenarios where such an
> >> updater would prove useful.
> >
> >I doubt this should be in the scope of the installer. As you
> >mentioned, the job was done properly during the initial install. I
> >doubt, by the way, that this initial setting of the resume partition
> >was done by D-I itself. It happened during the installation of the
> >uswsusp package.
> >
> >What you want is probably something that belongs to that one
> >package. It's indeed probably enough to just "dpkg-reconfigure
> >uswsusp".
> 
> Hi Boris, Christian,
> 
> The files /etc/uswsusp.conf and /etc/initramfs-tools/conf.d/resume are
> conffiles, but these files are different in every host, so we shouldn't
> include them as "conffiles". See [1] and [2]. For this reason you cannot
> find them using 'apt-file' or 'dpkg -S'. IMO, the current configuration
> (no automatic conffile) is right.
> 
> When you move your filesystems, some things could change. For example, the
> /etc/fstab could be different. If you change the machine, the hardware
> could be different and some drivers (pe. video) should be changed. In
> those cases, you edit the fstab file and update your X11 package. Why
> should be different with uswsusp? uswsusp doesn't have any bug, simply
> your filesystems are different and you should reconfigure it.
> 'dpkg-reconfigure uswsusp' do it.
> 
> IMO, nothing is wrong, your script "update-resume-info" is
> "dpkg-reconfigure uswsusp" and probably this bug should be closed.
> 
> Please, tell us if you agree with closing this bug.
> 
> Best regards,
> kix.
> 
> [1] http://www.debian.org/doc/debian-policy/ap-pkg-conffiles.html
> [2] http://www.debian.org/doc/manuals/maint-guide/dother.en.html#conffiles


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

Bug#718244: biblatex 1.7 are not compatible with TeXlive 2013

[Vasiliy Shlykov]

Package: biblatex
Version: 1.7-1
Severity: normal

Dear Maintainer,

there is a single version of biblatex package now - 1.7. However this version
is not compatible with TeXlive 2013 which places in unstable repo because of
incompatibility with polyglossia package.

This xetex source:

\usepackage{polyglossia}
\usepackage[backend=biber,language=auto]{biblatex}
\usepackage{csquotes}

Produces following error output:

! Package biblatex Error: Patching 'babel' package failed.

See the biblatex package documentation for explanation.
Type  H   for immediate help.
 ...

l.93 \begin{document}

(/usr/share/texmf/tex/latex/biblatex/lbx/english.lbx)

Package csquotes Warning: Using preliminary 'polyglossia' interface.
(csquotes)Some of the multilingual features may not
(csquotes)work as expected.


I found some explanation on stackexchange:
http://tex.stackexchange.com/questions/119682/how-to-use-polyglossia-with-
biblatex

Please consider an update biblatex package in unstable repo.



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

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

Versions of packages biblatex depends on:
ii  dpkg   1.16.10
ii  etoolbox   2.1-1
ii  logreq 1.0-1
ii  tex-common 4.03
ii  texlive-latex-base 2013.20130722-1
ii  texlive-latex-extra2013.20130722-1
ii  texlive-latex-recommended  2013.20130722-1

Versions of packages biblatex recommends:
ii  biber  0.9.9+release-1

biblatex suggests no packages.

-- no debconf information


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

Bug#718245: adequate: please do not display using dialog as option

[Thorsten Glaser]

Package: adequate
Version: 0.7.1
Severity: wishlist

Hi,

I find myself confused by adequate displaying things with dialog
instead of simply printing them line-by-line which also has the
potential of being either better legible (by indenting wrapped
lines) or copy-past-able.

Please add an option to do plaintext output. The dialog window
gets irritating once things like Libreoffice are in, and I fear
to miss one-entry packages in that mess.


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

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

Versions of packages adequate depends on:
ii  debconf  1.5.50
ii  perl 5.14.2-21

adequate recommends no packages.

adequate suggests no packages.

-- Configuration Files:
/etc/apt/apt.conf.d/20adequate changed [not included]

-- no debconf information

-- debsums errors found:
sh: /usr/sbin/dpkg-divert: not found


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

Bug#717989: python-ase,silversearcher-ag: error when trying to install together

[Jens Jørgen Mortensen]

Den 28-07-2013 23:12, Ask Hjorth Larsen skrev:

Hello

I believe the 'ag' script in python-ase will change its name to
ase-gui in future upstream versions.  Jens Jørgen (CC'd), isn't that
correct?


That's correct.  The renaming is in the "cli" branch which I hope to 
merge soon.


Should we simply drop "ag" for version 3.8 or keep it for one more 
release with a deprecation warning?


Jens Jørgen



Either way, two-letter script names are probably a very bad idea
unless they are OS commands or something like that.

Best regards
Ask

2013/7/27 Andreas Beckmann :

Package: python-ase,silversearcher-ag
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Architecture: amd64
Distribution: jessie

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

   Selecting previously unselected package python-ase.
   Unpacking python-ase (from .../python-ase_3.6.0.2515-1.1_all.deb) ...
   dpkg: error processing 
/var/cache/apt/archives/python-ase_3.6.0.2515-1.1_all.deb (--unpack):
trying to overwrite '/usr/bin/ag', which is also in package 
silversearcher-ag 0.15~pre+20130512-1
   dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
   Errors were encountered while processing:
/var/cache/apt/archives/python-ase_3.6.0.2515-1.1_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

   usr/bin/ag
   usr/share/man/man1/ag.1.gz

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see http://edos.debian.net/file-overwrites/.



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

Bug#718246: zabbix-proxy-sqlite3: Unable to stop zabbix_proxy process

[makeijan]

Package: zabbix-proxy-sqlite3
Version: 1:2.0.6+dfsg-1~bpo70+1
Severity: normal

Dear Maintainer,
zabbix-proxy.conf misses PidFile option, and default behavior is to use 
/tmp/zabbix-proxy.pid
So you always get an:
[FAIL] zabbix_proxy is not running ... failed!
when trying to stop it using init script.
In order to actually stop the daemon you have to kill the process.

Adding this line to installed zabbix-proxy.conf fixes the issue.
PidFile=/var/run/zabbix/zabbix_proxy.pid

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

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

Versions of packages zabbix-proxy-sqlite3 depends on:
ii  adduser  3.113+nmu3
ii  fping3.2-1
ii  libc62.13-38
ii  libcurl3-gnutls  7.26.0-1+wheezy3
ii  libldap-2.4-22.4.31-1+nmu2
ii  libopenipmi0 2.0.16-1.3
ii  libsnmp155.4.3~dfsg-2.7
ii  libsqlite3-0 3.7.13-1+deb7u1
ii  libssh2-11.4.2-1.1
ii  lsb-base 4.1+Debian8+deb7u1
ii  sqlite3  3.7.13-1+deb7u1
ii  ucf  3.0025+nmu3

zabbix-proxy-sqlite3 recommends no packages.

Versions of packages zabbix-proxy-sqlite3 suggests:
ii  logrotate  3.8.1-4

-- Configuration Files:
/etc/default/zabbix-proxy 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#717988: Speculation about cause for the deadlock

[Pauli Nieminen]

It seems the hotplug mutex is taken when I shutdown my qemu VM having USB
passthrough configured for a device. There is libusb_init called followed
quickly after by libusb_exit.

Deadlock happens most likely because libusb_exit holds linux_hotplug_lock
during whole exit phase. With bad timeing event thread can try to take same
lock simultanously leading to the deadlock shown by backtrace in original
report.

Bug#718247: cloud-utils: man page for cloud-localds

[Thomas Bechtold]

Package: cloud-utils
Version: 0.26-2
Severity: minor
Tags: patch

Dear Maintainer,
attached is a manpage for cloud-localds.
..\" cloud-localds (1) manual page
..\" Copyright (C) 2013 Thomas Bechtold 
..\" License: GPL-3
..\"

..TH cloud-localds 1 "July 2013" cloud\-utils "cloud\-utils"
..SH NAME
cloud-localds \- create a disk for cloud-init to utilize nocloud
..SH SYNOPSIS
..B cloud-localds
[options] output user-data [meta-data]

..SH DESCRIPTION
..B cloud-localds
creates a disk-image with user-data and/or meta-data for
..BR cloud-init (1).
user-data can contain everything which is supported by
..BR cloud-init (1)
..
..SH OPTIONS
..TP
..BR \-d ", " \-\-disk_format =\fIDISKFORMAT\fR
Disk format to output. See
..BR qemu-img (1)
for allowed disk formats.
Default is raw.

..TP
..BR \-f ", " \-\-filesystem =\fIFORMAT\fR
Filesystem format. Allowed formats are vfat and iso.
Default is iso9660.

..TP
..BR \-h ", " \-\-help
Show usage.

..TP
..BR \-i ", " \-\-interfaces
Write network interfaces file into metadata.

..TP
..BR \-m ", " \-\-dsmode =\fIMODE\fR
Add dsmode to the metadata. Allowed are local or net.
Default in
..BR cloud-init (1)
is net.

..SH EXAMPLES
This example creates a disk image with user-data which can be used to start a cloud image which supports
..BR cloud-init (1).

..IP "Create some user-data:"
..IP
..PP
..nf
..RS
cat > my-user-data < for Debian systems (but may be used by others). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 3 published by the Free Software Foundation.

Bug#717981: libimage-magick-q16-perl: fails to upgrade from 'sid' - trying to overwrite /usr/lib/perl5/auto/Image/Magick/Magick.so

[roucaries . bastien]

Control: tag -1 + patch
Control: tag -1 + confirmés

Thanks i have done a patch


Andreas Beckmann  a écrit :
>Package: libimage-magick-q16-perl
>Version: 8:6.8.5.6-3
>Severity: serious
>User: debian...@lists.debian.org
>Usertags: piuparts
>
>Hi,
>
>during a test with piuparts I noticed your package fails to upgrade
>from
>'sid' to 'experimental'.
>It installed fine in 'sid', then the upgrade to 'experimental' fails
>because it tries to overwrite other packages files without declaring a
>Breaks+Replaces relation.
>
>See policy 7.6 at
>http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
>
>>From the attached log (scroll to the bottom...):
>
>  Selecting previously unselected package libimage-magick-q16-perl.
>Unpacking libimage-magick-q16-perl (from
>.../libimage-magick-q16-perl_8%3a6.8.5.6-3_amd64.deb) ...
>dpkg: error processing
>/var/cache/apt/archives/libimage-magick-q16-perl_8%3a6.8.5.6-3_amd64.deb
>(--unpack):
>trying to overwrite '/usr/lib/perl5/auto/Image/Magick/Magick.so', which
>is also in package perlmagick 8:6.7.7.10-5
>  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
>  Errors were encountered while processing:
>/var/cache/apt/archives/libimage-magick-q16-perl_8%3a6.8.5.6-3_amd64.deb
>
>
>cheers,
>
>Andreas

-- 
Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté.

Bug#718244: biblatex 1.7 are not compatible with TeXlive 2013

[Norbert Preining]

On Mo, 29 Jul 2013, Vasiliy Shlykov wrote:
> Please consider an update biblatex package in unstable repo.

Agreed, the problem is well known, but due to dependency we are in
a serious problem. 

The maintainers are well aware of these problems.

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094



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

Bug#718248: nsca-client: Random segmentation faults of send_nsca

[Cyril Bouthors]

Package: nsca-client
Version: 2.9.1-2
Severity: important

Hi,

Our NSCA installation has random segmentation faults:

Jul 29 00:33:20 backup8 kernel: [5668958.752572] send_nsca[10854]: segfault
at 7fff2d847000 ip 004014b0 sp 7fff2d842fd0 error 6 in
send_nsca[40+5000]
Jul 29 00:33:21 backup8 kernel: [5668959.786642] send_nsca[10856]: segfault
at 7fffb1512000 ip 004014b0 sp 7fffb150ddc0 error 6 in
send_nsca[40+5000]
Jul 29 00:33:20 backup8 kernel: [5668958.752572] send_nsca[10854]: segfault
at 7fff2d847000 ip 004014b0 sp 7fff2d842fd0 error 6 in
send_nsca[40+5000]
Jul 29 00:33:21 backup8 kernel: [5668959.786642] send_nsca[10856]: segfault
at 7fffb1512000 ip 004014b0 sp 7fffb150ddc0 error 6 in
send_nsca[40+5000]
Jul 29 00:33:20 backup8 kernel: [5668958.752572] send_nsca[10854]: segfault
at 7fff2d847000 ip 004014b0 sp 7fff2d842fd0 error 6 in
send_nsca[40+5000]
Jul 29 00:33:21 backup8 kernel: [5668959.786642] send_nsca[10856]: segfault
at 7fffb1512000 ip 004014b0 sp 7fffb150ddc0 error 6 in
send_nsca[40+5000]
Jul 29 00:33:20 backup8 kernel: [5668958.752572] send_nsca[10854]: segfault
at 7fff2d847000 ip 004014b0 sp 7fff2d842fd0 error 6 in
send_nsca[40+5000]
Jul 29 00:33:21 backup8 kernel: [5668959.786642] send_nsca[10856]: segfault
at 7fffb1512000 ip 004014b0 sp 7fffb150ddc0 error 6 in
send_nsca[40+5000]

This seems to appear when the system is under extremely heavy I/O, CPU,
memory usage and when send_nsca is called frequently, about 1 time per
second with bursts to probably 20/s.

I can reproduce this issue on at least 3 machines under the same condition
(heavy I/O/CPU/memory usage) under squeeze and wheezy.

On machines with less I/Os, send_nsca is running just fine.

What information would you need from me in order to reproduce and fix this
issue?

Please do not hesitate to ask me for more debug information.

Regards,

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

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

Versions of packages nsca-client depends on:
ii  libc6   2.17-7
ii  libmcrypt4  2.5.8-3.1

nsca-client recommends no packages.

nsca-client suggests no packages.

-- no debconf information
-- 
 ,''`.
: :' :  Cyril Bouthors
`. `' Debian.org
  `-

Bug#718000: llvm-dev: LLVM gold plugin has failed to create LTO module: Invalid bitcode signature

[Léo Cavaillé]

Hello,

I believe the bug you reported has been fixed by a patch in
llvm-toolchain-3.3 (not yet in testing).
The bug is likely to be the same as bug #712437.

The 3.3 release is the latest stable release of clang available upstream.

Let me know if the problem is still there (I have not tested it on
i386), if not I will patch my patch according to your output.

Regards,

-- 
Léo Cavaillé


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

Bug#618863: /usr/bin/ssh: insecurely verifies host key with VerifyHostKeyDNS option

[Richard Salts]

Package: openssh-client
Version: 1:6.0p1-4
Followup-For: Bug #618863

openssh now includes a configure option to link to ldns for verification of
the dnssec service rather than relying on the +ad bit in a response for a
resolver. Maybe it would be worth adding that to the configuration options on
the deb ( although probably not necessary on the udeb).

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

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

Versions of packages openssh-client depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.49
ii  dpkg   1.16.10
ii  libc6  2.13-38
ii  libedit2   2.11-20080614-5
ii  libgssapi-krb5-2   1.10.1+dfsg-5+deb7u1
ii  libselinux12.1.9-5
ii  libssl1.0.01.0.1e-2
ii  passwd 1:4.1.5.1-1
ii  zlib1g 1:1.2.7.dfsg-13

Versions of packages openssh-client recommends:
ii  openssh-blacklist0.4.1+nmu1
ii  openssh-blacklist-extra  0.4.1+nmu1
ii  xauth1:1.0.7-1

Versions of packages openssh-client suggests:
pn  keychain  
pn  libpam-ssh
pn  monkeysphere  
ii  ssh-askpass   1:1.2.4.1-9

-- Configuration Files:
/etc/ssh/ssh_config 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#718247: cloud-utils: man page for cloud-localds

[Charles Plessy]

Le Mon, Jul 29, 2013 at 10:11:50AM +0200, Thomas Bechtold a écrit :
> Package: cloud-utils
> Version: 0.26-2
> Severity: minor
> Tags: patch
> 
> Dear Maintainer,
> attached is a manpage for cloud-localds.

Thanks Thomas,

could you submit it Upstream as well ?

https://launchpad.net/cloud-init

Have a nice day,

-- 
Charles Plessy
Tsurumi, Kanagawa, Japan


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

Bug#718249: javascript-common: postinst fails trying to remove non-existent apache conf.d

[Theppitak Karoonboonyanan]

Package: javascript-common
Version: 10
Severity: normal

Dear Maintainer,

While upgrading javascript-common from 8 to 10 in my box:

---8<---
Setting up javascript-common (10) ...
apache2_invoke javascript-common: already enabled
[ ok ] Reloading web server: apache2.
rmdir: failed to remove '/etc/apache2/conf.d': No such file or directory
dpkg: error processing javascript-common (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 javascript-common
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up javascript-common (10) ...
apache2_invoke javascript-common: already enabled
[ ok ] Reloading web server: apache2.
rmdir: failed to remove '/etc/apache2/conf.d': No such file or directory
dpkg: error processing javascript-common (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 javascript-common
---8<---


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

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

javascript-common depends on no packages.

javascript-common recommends no packages.

Versions of packages javascript-common suggests:
ii  apache2  2.4.6-2
ii  apache2-bin [httpd]  2.4.6-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#718250: kfreebsd-image-9.1-1-amd64: attaching USB keyboard makes system reboot

[Lars Lansink]

Package: kfreebsd-image-9.1-1-amd64
Version: 9.1-3
Severity: important

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

   * What led up to the situation?
 After upgrading a headless wheezy to jessie and after the reboot attaching 
a USB keyboard.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Powered down the system, attached keyboard and screen, powered on.
   * What was the outcome of this action?
 Endless reboot loop due to KBD: stack traceback.
   * What outcome did you expect instead?
 Usable keyboard.

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


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

Kernel: kFreeBSD 9.1-1-amd64
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 kfreebsd-image-9.1-1-amd64 depends on:
ii  devd   9.1-2
ii  freebsd-utils  9.1-2
ii  kbdcontrol 9.1-2
ii  kldutils   9.1-2

kfreebsd-image-9.1-1-amd64 recommends no packages.

kfreebsd-image-9.1-1-amd64 suggests no packages.

-- no debconf information


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

Bug#712803: Bad settings?

[Matthew Spraggs]

Does anyone have any idea what might be causing this? Have I not
configured gnome properly or something? It's still happening and it's
starting to get quite annoying.

Matt

Bug#717988: libusb-1.0-0: upowerd deadlocks in libusb (maybe related to suspend/resume)

[Aurelien Jarno]

On Sat, Jul 27, 2013 at 06:21:56PM +0300, Pauli wrote:
> Package: libusb-1.0-0
> Version: 2:1.0.16-1
> Severity: important
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> 
> Exact steps are unknown but during last two days I have noticed upowerd
> daemon beeing stuck for unknown reason after suspend/resume.
> 
>* What exactly did you do (or not do) that was effective (or ineffective)?
> 
> I suspend my laptop frequently using keyboard hotkey. That used to work
> without problems until upowerd now started deadlocking.
> 
>* What was the outcome of this action?
> 
> upowerd daemon deadlocks forcing me to manually restart it before any
> power related functionality works in gnome.

Is it a new issue following a dist-upgrade? Have you tried to rollback
to libusb-1.0-0 version 1.0.15-1 to see if the problem is related to the
new version.

-- 
Aurelien Jarno  GPG: 1024D/F1BCDB73
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#697703: p247 update

[Tristan Hill]

Hi,

I've done some updates for p247 here -
https://github.com/stan3/debian-ruby2.0

Tristan

Bug#707933: closed by Rene Engelhard (Bug#707933: fixed in libreoffice 1:4.1.0-2)

[Andreas Beckmann]

Control: found -1 1:4.1.0-2

On 2013-07-28 05:21, Debian Bug Tracking System wrote:
>* debian/libreoffice-common.postrm.in:
>  - don't create /var/lib/libreoffice/share/config/ anymore and
>remove it (and javaunopkginstall.xml if exists) on purge

The "if exists" does not work:

  Removing libreoffice-common ...
  Purging configuration files for libreoffice-common ...
  rm: cannot remove 
'/var/lib/libreoffice/share/config/javasettingsunopkginstall.xml': No such file 
or directory
  dpkg: error processing libreoffice-common (--purge):
   subprocess installed post-removal script returned error exit status 1
  Errors were encountered while processing:
   libreoffice-common

Andreas


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

Bug#718251: texlive-bin: FTBFS: makeinfo: not found

[Thorsten Glaser]

Source: texlive-bin
Version: 2013.20130722.31261-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

your package fails to build, even on release architectures,
apparently due to missing Build-Depends(-Arch), possibly
due to either them appearing in Build-Depends-Indep (which
probably should be empty) or by you using an unclean and
not minimal chroot (or none at all) for building the pak-
kage you uploaded.

-- System Information:
Debian Release: 7.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: m68k

Kernel: Linux 3.2.0-4-atari
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/mksh-static


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

Bug#632627: Re[4]: resume file

[Askar Safin]

> But I wonder whether this configuration file is really needed for most
> system.  Couldn't we use blkid to find the swap partition automagically?
> (The configuration file would still be necessary if there are multiple
> swap partitions.)
Imagine the following: there is Debian on /dev/sda1, Debian on /dev/sda2 and 
swap on /dev/sda3.
Debian on sda2 configured to use sda3. Debian on sda1 doesn't use swap. Debian 
on sda2 suspends to sda3. Then user runs Debian on sda1.
Initramfs from sda1 looks at the sda3 and says: "Oh! There is swap. Let's wake 
up from it". And initramfs performs waking up from wrong partition.
So, don't search swap at the resume time.

> initramfs-tools has its own resume configuration file, but so far as I
> can see the uswsusp package does not use it. So there would be no
> reason for you to modify it - would there?
No, "resume" file is really used. It used by early userspace. I just created 
virtual machine with fresh jessie and without swap and performed the following 
test:
1. Installed uswsusp. uswsusp said to me that I have no swap and I should add 
it and run "dpkg-reconfigure uswsusp".
2. I added swap
3. Rebooted
4. I ran "dpkg-reconfigure uswsusp". uswsusp found my swap and it was happy. It 
asked me a lot of questions. Then uswsusp triggered initramfs rebuilding
5. Rebooted
6. I ran "s2disk" and I could not wake up. So, this is a bug.
7. I created "resume" file (there was no such file before) and I put 
"RESUME=UUID=..." to it.
8. I ran "s2disk" and it failed again (of course, because 
/etc/initramfs-tools/conf.d/resume alone is not enough, there should be 
/conf/conf.d/resume in initramfs).
9. I ran "dpkg-reconfigure uswsusp", it triggered initramfs (so, 
/conf/conf.d/resume was created)
10. I successfully performed "s2disk"

In fact, s2disk works (without manual editing configs) only if you created swap 
at installing of Debian.

> The uswsusp package can edit its own configuration file though I do not
> recommend it. I think it would be better to leave the resume device
> unspecified in /etc/uswsusp.conf by default, and then to select it
> automatically (both at suspend and resume time) if possible.
As I said, selecting automatically at resume time is bad idea.
At suspend time is probably, too, because two systems can have one swap.

Ideally, there should be some guarantee that if user didn't edit configs 
himself and it performed suspend then he guaranteed wakes up successfully.
Of course, such guarantee is very important because user can have a lot of 
opened programs, unsaved documents etc. Ideally, s2disk should perform some 
checks (for example, it can check configs) that all is OK, before doing real 
suspending.
If uswsusp detects swap automatically, then there was no such guarantee. For 
example, let's assume, uswsusp detects swap automatically, and let's assume 
this bug #632627 is fixed (i. e. "dpkg-reconfigure uswsusp" writes "resume"). 
User just added new swap and didn't run any "dpkg-reconfigure" yet. Then he ran 
"s2disk". "s2disk" detected his swap, suspended. And then this user cannot wake 
up, because "dpkg-reconfigure" is not done and "resume" is not written.

Askar Safin

Bug#718252: rename "Paraview viewer" to "Paraview client"?

[Sylwester Arabas]

Package: paraview
Version: 4.0.1-1

After installing Paraview, its menu item in xfce (likely other managers 
too?) is placed under "Education" and named "Paraview viewer".


In my understanding, the "viewer" name is misleading - perhaps it could 
be named "client" (as in the Paraview docs). "Education" category is 
also not too intuitive...


Finally, thanks for packaging it!

HTH, best regards,
Sylwester


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

Bug#712803: xsession-errors

[Matthew Spraggs]

Attached is the last part of my .xsession-errors file, from the
moment I hit shutdown. Once I've clicked the shutdown button,
I then kill the xserver with Ctrl-Alt-Backspace.

Matt


xsession-error
Description: Binary data

Bug#710039: packaging osmosis for use on the Live

[Andreas Tille]

Hi Brian,

On Sun, Jul 28, 2013 at 12:55:13PM -0700, mapl...@light42.com wrote:
> Hi All -
> 
>   I noticed this
> 
> Maintainer: Debian OpenStreetMap Team 

... so I decided to CC this team (isn't this obvious??) and also the
relevant bug report (#710039) ... which is admittedly a bit redundant
but anyway.  The fact that there is no response to the bug report since
two monthes would tell me, that the two uploaders are busy with other
things / on vac whatever and are happy to receive patches (otherwise
they could have answered: "No, we intentionally keep this version.")

So you can decide:  Well, that's the Debian maintainers problem - I'll
just keep on working for osgeo or you consider it a good idea to
checkout the existing packaging.  If you

  debcheckout osmosis

you actually see that Giovanni Mascellani has decided to leave the team
last year and the missing manpower issue becomes obvious.

Trying to verify the hypothesis that there is a problem with manpower
in pkg-osm team which leads to not up to date packages we check the
team statistics for this group:

  What people are discussing
   http://blends.debian.net/liststats/authorstat_pkg-osm-maint.png

  Who fixes bugs
   http://blends.debian.net/liststats/authorstat_pkg-osm-maint.png

  Who commits code
   http://blends.debian.net/liststats/commitstat_pkg-osm.png

  And finally who uploads packages
   http://blends.debian.net/liststats/uploaders_pkg-osm.png

you come to the conclusion that the main driver of this team is David
whom I have the pleasure to (virtually) know from Debian Med as very
active and resonsive.  So if even David does not find the time to
respond in a reasonable time frame I'm afraid that several packages of
pkg-osm are in danger to be improperly maintained.

The statistics for pkg-grass / debian-gis are a bit better and finally
if you compare the amount of packages via an UDD query

udd=# SELECT maintainer_email, count(*) FROM (SELECT DISTINCT source, 
maintainer_email FROM sources WHERE maintainer_email like '%pkg-grass%' or 
maintainer_email like '%pkg-osm%') tmp GROUP BY maintainer_email; 
maintainer_email | count 
-+---
 pkg-osm-ma...@lists.alioth.debian.org   |16
 pkg-grass-de...@lists.alioth.debian.org |72


the number of packages in pkg-grass repository is four times higher than
in pkg-osm.  So in case people would consider a merge moving from
pkg-osm to pkg-grass would mean less work.

As a consequence out of this analysis I would propose the following:
Create a patch against the latest status of osmosis Git repository.  I'd
take over the responsibility to care for a move into pkg-grass team and
will sponsor the updated package as offered in SoB[1].  We keep on
discussing about this plan on pkg-osm list which leaves enough time to
insist if the plan is not accepted.

>   while looking around.. The reason I mentioned osmosis recently is,
> the version we have on the Live is
> 
>   Osmosis Version 0.40.1
> 
> which is very stale.. many new features and filters have been added
> 
> "The stable releases below should be used whenever possible."
> 
>    http://wiki.openstreetmap.org/wiki/Osmosis
> 
> I verified current stable runs correctly on the Live beta1 with:
> 
>   PLANET_FILE=california-130721.osm.pbf
>   ./bin/osmosis --read-pbf-fast file="$PLANET_FILE" workers=8 --b 
> bufferCapacity=1 --tf accept-ways "building=*" --tf accept-nodes 
> "building=*" --tf accept-relations "building=*" --write-pbf 
> file="buildings.osm.pbf"
> 
>   I dont know about java packaging, but osmosis seems like a decent candidate 
> for learning how ..
> I think it would be useful to have a more current version.

Yes, for sure are current versions useful.  I just want to lay out a
plan how we could have better chances for a sustainable way to get
recent versions also in future.

>   best regards from Berkeley, California

Best regards from way to hot Germany

  Andreas.

PS: I'll be at DebConf13 and would be happy to talk about Debian GIS[2]


[1] https://wiki.debian.org/DebianPureBlends/SoB
[2] https://penta.debconf.org/dc13_schedule/events/990.en.html

-- 
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#718253: openafs-dbserver: buserver segmentation fault with -servers option specified

[Gunnar Krull]

Package: openafs-dbserver
Version: 1.6.5-1~bpo70+1
Severity: important

Hi!

I've upgraded our fileservers from OpenAFS version 1.6.4 to 1.6.5.
After restarting the server processes the bos log shows that the
buserver process could not be started. This is the corresponding
BosConfig entry:

bnode simple buserver 1
parm /usr/lib/openafs/buserver -servers 134.76.81.219

Starting the buserver manually with the "-servers" option like above
gives an segmentation fault. 

But staring the buserver without the "-servers" option works without an
error. 

Also version 1.6.4 works to which I've reverted now. 

The segfault also only appears on this i386 system, the other amd64 systems
are not effected.

You can find my bug report with a strace log here:
http://rt.central.org/rt/Ticket/Display.html?id=131706

Regards,
Gunnar


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

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

Versions of packages openafs-dbserver depends on:
ii  libc6   2.13-38
ii  libcomerr2  1.42.5-1.1
ii  libk5crypto31.10.1+dfsg-5+deb7u1
ii  libkrb5-3   1.10.1+dfsg-5+deb7u1
ii  openafs-fileserver  1.6.5-1~bpo70+1
ii  perl5.14.2-21

Versions of packages openafs-dbserver recommends:
ii  openafs-client  1.6.5-1~bpo70+1

Versions of packages openafs-dbserver suggests:
pn  openafs-doc  

-- 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#707933: closed by Rene Engelhard (Bug#707933: fixed in libreoffice 1:4.1.0-2)

[Rene Engelhard]

notfound 707933 1:4.1.0-2
thanks

On Mon, Jul 29, 2013 at 11:08:19AM +0200, Andreas Beckmann wrote:
> Control: found -1 1:4.1.0-2

Eh, no? This bug is something else than...
 
> On 2013-07-28 05:21, Debian Bug Tracking System wrote:
> >* debian/libreoffice-common.postrm.in:
> >  - don't create /var/lib/libreoffice/share/config/ anymore and
> >remove it (and javaunopkginstall.xml if exists) on purge
> 
> The "if exists" does not work:
> 
>   Removing libreoffice-common ...
>   Purging configuration files for libreoffice-common ...
>   rm: cannot remove 
> '/var/lib/libreoffice/share/config/javasettingsunopkginstall.xml': No such 
> file or directory
>   dpkg: error processing libreoffice-common (--purge):
>subprocess installed post-removal script returned error exit status 1
>   Errors were encountered while processing:
>libreoffice-common

.. postrm purge fails on systems never upgraded from OOo times.

If you really want, file a new bug, but this bug is about "doesn't remove
share/config"

(but yeah, I forgot || true there.)

Please keep bugs clean, thanks.

Regards,

Rene
> 
> Andreas
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-openoffice-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/51f63103.8030...@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#717717: lxc: live-debconfig failes to execute chpasswd and useradd

[Daniel Baumann]

close 717717 0.9.0-14
thanks

On 07/24/2013 10:19 AM, Johannes Schauer wrote:
> I'm using lxc 0.9.0-12 from experimental on Debian sid. After having
> created a container I cannot log in to it.

i cannot reproduce this, it must be a local inconsistency/error in your
preseeding file or usage of live-debconfig.

also, it's impossible to know what excatly went wrong on your end,
please do always provide the full run of lxc-debconfig (with set -x) and
the full preseed file that you've used, together with the full command
on how you invoked the container creation.


> I think that lxc should abort the container
> creation process

this is done in 0.9.0-14.

-- 
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:  daniel.baum...@progress-technologies.net
Internet:   http://people.progress-technologies.net/~daniel.baumann/


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

Bug#717717: lxc: live-debconfig failes to execute chpasswd and useradd

[Johannes Schauer]

Hi,

Quoting Daniel Baumann (2013-07-29 11:55:03)
> i cannot reproduce this, it must be a local inconsistency/error in your
> preseeding file or usage of live-debconfig.

Indeed it was an error in my preseed file. It actually did occur in the part
which I posted in the initial bugreport. Strangely enough, the part which
created the error must not have survived the copy-paste from my preseed file.

The error was simply that I had a space at the end of the
live-debconfig/passwd/user-name line which in turn made chpasswd and useradd
fail in the ways written in my original report.

I did not know that preseed files are sensitive to whitespace in such a way but
indeed this was a bug in my preseed and not lxc.

> > I think that lxc should abort the container creation process
> 
> this is done in 0.9.0-14.

Thanks!

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#717983: dpkg: Failed upgrade due to file conflicts with manpages-it

[Andreas Beckmann]

Control: found -1 1.17.1
Control: affects -1 + deselect dpkg-dev

Hi Guillem,

dpkg-dev and dselect also need to replace manpages-it.

Can you make that a versioned Breaks+Replaces?
(To avoid having files "disappear" from manpages-it in the sequence
install manpages-it, install dpkg-dev, remove dpkg-dev.)

  Breaks: manpages-it (<= 2.80-3)
  Replaces: manpages-it (<= 2.80-3)

Thanks


Andreas


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

Bug#718151: libburn: FTBFS: Failed to install docs

[Thomas Schmitt]

Hi,

i am the upstream programmer of libburn.
If i can do anything to help fixing the problem, please tell me.



About the doxygen complaints (of which i am unsure whether they are
the reason for the stalled build process):

libburn release does not build doxygen stuff any more since several
years. The doxygen.conf.in file is part of the makefile, target "doc"
is still defined in the makefile, but it is not required by target "all".
So Debian seems to call "make doc" explicitly, or do something else
that triggers doxygen.

doxygen is a recurring source of problems. I would advise to
remove it from the Debian build process for libburn.
I'd remove it from the release if that was not a potential
way to break the distro builds.

I corrected most of the complained items in libburn.h now
(release 1.3.2 will come soon).

But this one riddles me:
> /«PKGBUILDDIR»/libburn/libburn.h:3515: Warning: explicit link request to 'if' 
> could not be resolved
There is a word "If" in the comment text. But there are lots
of similar occasion where doxygen raises no protest.


Have anice day :)

Thomas


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

Bug#713879: [lintian] Multiarch ?

[bastien ROUCARIES]

Package: lintian
Version: 2.5.13

According to multiarch specs:
- usr/i686-w64-mingw32/include/ => usr/include/i686-w64-mingw32/
- usr/x86_64-w64-mingw32/lib/ => usr/lib/x86_64-w64-mingw32/

May be a new check is worth it, checking gnu triplet and suggesting something 
more appropriate.

Bastien


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

Bug#718249: javascript-common: postinst fails trying to remove non-existent apache conf.d

[Jean-Michel Vourgère]

Control: tags -1 + patch

I missed the case where obsolete /etc/apache2/conf.d/ was already removed.

Attached is a patch with an extra test.

Thank you for the repport!
diff -Nru javascript-common-10/debian/changelog javascript-common-11/debian/changelog
--- javascript-common-10/debian/changelog	2013-07-28 22:57:03.0 +
+++ javascript-common-11/debian/changelog	2013-07-29 10:20:39.0 +
@@ -1,3 +1,10 @@
+javascript-common (11) UNRELEASED; urgency=low
+
+  * Test if obsolete /etc/apache2/conf.d/ was removed by user before
+touching it. (Closes: #718249)
+
+ --  Jean-Michel Vourgère   Mon, 29 Jul 2013 10:16:39 +
+
 javascript-common (10) unstable; urgency=low
 
   * Downgrading webservers relation from 'recommends' to 'suggests'
diff -Nru javascript-common-10/debian/javascript-common.postinst javascript-common-11/debian/javascript-common.postinst
--- javascript-common-10/debian/javascript-common.postinst	2013-07-28 21:48:58.0 +
+++ javascript-common-11/debian/javascript-common.postinst	2013-07-29 10:18:40.0 +
@@ -61,7 +61,11 @@
 # Will make piupart more happy on upgrades
 if [ "$1" = "configure" ] && dpkg --compare-versions "$2" lt "9"
 then
-	rmdir --ignore-fail-on-non-empty /etc/apache2/conf.d
+	# Remove old /etc/apache2/conf.d if empty and not already removed by user:
+	if [ -d /etc/apache2/conf.d ]
+	then
+		rmdir --ignore-fail-on-non-empty /etc/apache2/conf.d
+	fi
 	 # This is a work around bug #584185:
 	if [ -d /etc/javascript-common ]
 	then

Bug#718251: texlive-bin: FTBFS: makeinfo: not found

[Hilmar Preusse]

On 29.07.13 Thorsten Glaser (t...@mirbsd.de) wrote:

Hi,

> your package fails to build, even on release architectures,
> apparently due to missing Build-Depends(-Arch), possibly
> due to either them appearing in Build-Depends-Indep (which
> probably should be empty) or by you using an unclean and
> not minimal chroot (or none at all) for building the pak-
> kage you uploaded.
> 
The relevant error message is:

/«PKGBUILDDIR»/build-aux/missing: 81:
/«PKGBUILDDIR»/build-aux/missing: makeinfo: not found
WARNING: 'makeinfo' is missing on your system.
 You should only need it if you modified a '.texi' file, or
 any other file indirectly affecting the aspect of the manual.
 You might want to install the Texinfo package:
 
 The spurious makeinfo call might also be the consequence of
 using a buggy 'make' (AIX, DU, IRIX), in which case you
 might
 want to install GNU make:
 

..needs to be added to Build-Depends.

Hilmar
-- 
sigmentation fault


signature.asc
Description: Digital signature

Bug#716827: linux-image-3.9-1-amd64: Not detected laptop webcam with Jessie (ver: 3.9.8-1) although Wheezy (ver: 3.2.35-2) did it

[robert]

Package: src:linux
Version: 3.9.8-1
Followup-For: Bug #716827

Dear Maintainer,

The bug can be closed.

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

The reported camera had been deactivated by hardware by mean of a
rather bizarre key combination.
 After realizing that, I activated it. Now the camera is working
without any problem.

Sorry for the annoyance.  I really didn't know that it is possible to
change the camera state in this way.

robert



-- Package-specific info:
** Version:
Linux version 3.9-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.7.3 
(Debian 4.7.3-5) ) #1 SMP Debian 3.9.8-1

** Command line:
BOOT_IMAGE=/vmlinuz-3.9-1-amd64 root=/dev/mapper/nyxVG-root ro quiet

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[   17.132399] ACPI Warning: 0x0500-0x052f SystemIO 
conflicts with Region \GPIO 1 (20130117/utaddress-251)
[   17.132409] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   17.132413] lpc_ich: Resource conflict(s) found affecting gpio_ich
[   17.132670] ACPI Warning: 0xf040-0xf05f SystemIO 
conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20130117/utaddress-251)
[   17.132698] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   17.133041] snd_hda_intel :00:1b.0: irq 46 for MSI/MSI-X
[   17.140257] iTCO_vendor_support: vendor-support=0
[   17.140857] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
[   17.140901] iTCO_wdt: Found a Panther Point TCO device (Version=2, 
TCOBASE=0x0460)
[   17.140993] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   17.153707] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1b.0/sound/card0/input7
[   17.153863] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input8
[   17.154003] input: HDA Intel PCH Front Headphone as 
/devices/pci:00/:00:1b.0/sound/card0/input9
[   17.173250] psmouse serio2: synaptics: Touchpad model: 1, fw: 7.2, id: 
0x1c0b1, caps: 0xd04733/0xa4/0xa, board id: 3655, fw id: 582762
[   17.208092] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio2/input/input10
[   17.460063] ACPI: AC Adapter [AC] (off-line)
[   17.461015] ACPI Error: [_T_0] Namespace lookup failure, AE_ALREADY_EXISTS 
(20130117/dswload2-330)
[   17.461027] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog 
(20130117/psobject-222)
[   17.461033] ACPI Error: Method parse/execution failed [\_SB_.AC__.ADJP] 
(Node 88021549dce0), AE_ALREADY_EXISTS (20130117/psparse-537)
[   17.461043] ACPI Error: Method parse/execution failed [\_SB_.AC__._PSR] 
(Node 88021549dd30), AE_ALREADY_EXISTS (20130117/psparse-537)
[   17.461056] ACPI Exception: AE_ALREADY_EXISTS, Error reading AC Adapter 
state (20130117/ac-122)
[   17.461287] ACPI Error: [_T_0] Namespace lookup failure, AE_ALREADY_EXISTS 
(20130117/dswload2-330)
[   17.461299] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog 
(20130117/psobject-222)
[   17.461304] ACPI Error: Method parse/execution failed [\_SB_.AC__.ADJP] 
(Node 88021549dce0), AE_ALREADY_EXISTS (20130117/psparse-537)
[   17.461314] ACPI Error: Method parse/execution failed [\_SB_.AC__._PSR] 
(Node 88021549dd30), AE_ALREADY_EXISTS (20130117/psparse-537)
[   17.461325] ACPI Exception: AE_ALREADY_EXISTS, Error reading AC Adapter 
state (20130117/ac-122)
[   17.461878] ACPI Error: [_T_0] Namespace lookup failure, AE_ALREADY_EXISTS 
(20130117/dswload2-330)
[   17.461906] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog 
(20130117/psobject-222)
[   17.461911] ACPI Error: Method parse/execution failed [\_SB_.AC__.ADJP] 
(Node 88021549dce0), AE_ALREADY_EXISTS (20130117/psparse-537)
[   17.461919] ACPI Error: Method parse/execution failed [\_SB_.AC__._PSR] 
(Node 88021549dd30), AE_ALREADY_EXISTS (20130117/psparse-537)
[   17.461933] ACPI Exception: AE_ALREADY_EXISTS, Error reading AC Adapter 
state (20130117/ac-122)
[   17.467192] ACPI: Marking method ADJP as Serialized because of 
AE_ALREADY_EXISTS error
[   17.468112] ACPI: Marking method _PSR as Serialized because of 
AE_ALREADY_EXISTS error
[   17.775074] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
[   17.975784] ACPI: Battery Slot [BAT0] (battery present)
[   17.976227] wmi: Mapper loaded
[   18.315303] Adding 8785916k swap on /dev/mapper/nyxVG-swap.  Priority:-1 
extents:1 across:8785916k SS
[   18.340752] EXT4-fs (dm-1): re-mounted. Opts: (null)
[   18.442669] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro
[   18.712810] fuse init (API version 7.21)
[   18.725937] loop: module loaded
[   19.039358] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: 
(null)
[   19.472002] RPC: Registered named UNIX socket transport module.
[   19.472008] RPC: Registered udp transport modul

Bug#717989: python-ase,silversearcher-ag: error when trying to install together

[Ask Hjorth Larsen]

Hello

If we rename all the scripts to "ase-", then the change is
obvious enough that we probably won't need that - in my opinion.  It
would be slightly annoying to have many scripts installed under two
names, with half of them deprecated.

Regards
Ask

2013/7/29 Jens Jørgen Mortensen :
> Den 28-07-2013 23:12, Ask Hjorth Larsen skrev:
>
>> Hello
>>
>> I believe the 'ag' script in python-ase will change its name to
>> ase-gui in future upstream versions.  Jens Jørgen (CC'd), isn't that
>> correct?
>
>
> That's correct.  The renaming is in the "cli" branch which I hope to merge
> soon.
>
> Should we simply drop "ag" for version 3.8 or keep it for one more release
> with a deprecation warning?
>
> Jens Jørgen
>
>
>>
>> Either way, two-letter script names are probably a very bad idea
>> unless they are OS commands or something like that.
>>
>> Best regards
>> Ask
>>
>> 2013/7/27 Andreas Beckmann :
>>>
>>> Package: python-ase,silversearcher-ag
>>> Severity: serious
>>> User: trei...@debian.org
>>> Usertags: edos-file-overwrite
>>>
>>> Architecture: amd64
>>> Distribution: jessie
>>>
>>> Hi,
>>>
>>> automatic installation tests of packages that share a file and at the
>>> same time do not conflict by their package dependency relationships has
>>> detected the following problem:
>>>
>>>Selecting previously unselected package python-ase.
>>>Unpacking python-ase (from .../python-ase_3.6.0.2515-1.1_all.deb) ...
>>>dpkg: error processing
>>> /var/cache/apt/archives/python-ase_3.6.0.2515-1.1_all.deb (--unpack):
>>> trying to overwrite '/usr/bin/ag', which is also in package
>>> silversearcher-ag 0.15~pre+20130512-1
>>>dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
>>>Errors were encountered while processing:
>>> /var/cache/apt/archives/python-ase_3.6.0.2515-1.1_all.deb
>>>
>>> This is a serious bug as it makes installation fail, and violates
>>> sections 7.6.1 and 10.1 of the policy. An optimal solution would
>>> consist in only one of the packages installing that file, and renaming
>>> or removing the file in the other package. Depending on the
>>> circumstances you might also consider Replace relations or file
>>> diversions. If the conflicting situation cannot be resolved then, as a
>>> last resort, the two packages have to declare a mutual
>>> Conflict. Please take into account that Replaces, Conflicts and
>>> diversions should only be used when packages provide different
>>> implementations for the same functionality.
>>>
>>> Here is a list of files that are known to be shared by both packages
>>> (according to the Contents file for sid/amd64, which may be
>>> slightly out of sync):
>>>
>>>usr/bin/ag
>>>usr/share/man/man1/ag.1.gz
>>>
>>> This bug is assigned to both packages. If you, the maintainers of
>>> the two packages in question, have agreed on which of the packages will
>>> resolve the problem please reassign the bug to that package. You may
>>> also register in the BTS that the other package is affected by the bug.
>>>
>>> Cheers,
>>>
>>> Andreas
>>>
>>> PS: for more information about the detection of file overwrite errors
>>> of this kind see http://edos.debian.net/file-overwrites/.
>
>


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

Bug#718254: typo on debconf template

[Holger Levsen]

package: slbackup
severity: minor
x-debbugs-cc: victory 

On Samstag, 27. Juli 2013, victory wrote:
> --- slbackup.templates.orig   2013-07-27 17:32:35 +0900
> +++ slbackup.templates2013-07-27 17:32:55 +0900
> @@ -29,7 +29,7 @@
>  Type: string
>  Default: localhost
>  _Description: Name of your client:
> - In slbackup each client has a uniqe name which identifies it. This name
> + In slbackup each client has a unique name which identifies it. This name
>   does not necessarily have anything to do with the hostname. Please enter
>   the unique name of the client you want to configure.





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

Bug#709369: libimobiledevice: Please package 1.1.5

[Noël Köthe]

retitle 709369 libimobiledevice: Please package 1.1.5
found 709369 1.1.1-4
thanks

Hello,

the 1.1.1-4 version does not work with iOS 6.1.4 as far as I tested.
Please update to version 1.1.5 which got positive results for the
current iOS 6 and coming iOS 7 version.

Thank you.

-- 
Noël Köthe 
Debian GNU/Linux, www.debian.org


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

Bug#718232: update-rc.d: warning: start and stop actions are no longer supported

[Thomas Hood]

Thanks for the report.  I wasn't aware of this issue.

It seems the "start" and "stop" arguments are now deprecated. Roger Leigh
announced this debian-devel.

http://lists.debian.org/debian-devel/2013/05/msg01109.html

We should go with the flow and stop using "start" and "stop". Here's the
postinst code that needs to be changed.

# Automatically added by dh_installinit
if [ -x "/etc/init.d/resolvconf" ]; then
update-rc.d resolvconf start 38 S . stop 89 0 6 . >/dev/null ||
exit $?
fi
# End automatically added section

This arises from the following line in debian/rules.

dh_installinit --no-start -- start 38 S . stop 89 0 6 .

I see that Roger Leigh has opened a report (#717592) against debhelper
asking that dh_installinit not pass through "start" and "stop".  But we
shouldn't rely on this.

I guess the debian/rules line should be simply the following.

dh_installinit --no-start

-- 
Thomas

Bug#718255: ifuse: please update the package to version 1.1.2

[Noël Köthe]

Package: ifuse
Version: 1.0.0-1.1
Severity: wishlist

Dear Maintainer,

09.04.2012: ifuse-1.1.2.tar.bz2 has been officially released.
http://www.libimobiledevice.org/

Version 1.1.2
~

* Changes:
  - Add direct linking with libplist to fix build issues
  - Add basic manpage
  - Use UDID instead of UUID as it is the correct term for it
  - Remove obsolete glib and gthread dependencies


Please update the package to this latest version.

Thanks you.:)

Regards

Noël

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

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

Versions of packages ifuse depends on:
ii  fuse   2.9.2-4
ii  libc6  2.17-7
ii  libfuse2   2.9.2-4
ii  libglib2.0-0   2.36.3-3
ii  libimobiledevice2  1.1.1-4

ifuse recommends no packages.

ifuse suggests no packages.

-- no debconf information


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

Bug#718193: Gtk-WARNING: Theme parsing error

[Dmitry Smirnov]

Dear Alex,

It looks like "gtk3-engines-oxygen" is no longer compatible with
GTK-3.4.

Could you please install "libgtk-3-0" from testing to check if it fix
this problem for you? Thanks.

Regards,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B


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

Bug#717376: moreinfo / unreproducible

[Holger Levsen]

control: tags -1 + moreinfo unreproducible

Hi Salvatore,

piupartsm@pejacevic:/srv/piuparts.debian.org/master$ find * -name 
"yardradius_*log"
jessie/pass/yardradius_1.1.2-4.log
lenny2squeeze/pass/yardradius_1.1.2-4.log
sid/pass/yardradius_1.1.2-4.log
sid-nodoc/pass/yardradius_1.1.2-4.log
squeeze/pass/yardradius_1.1.2-4.log
squeeze2wheezy/pass/yardradius_1.1.2-4.log
squeeze2wheezy-proposed/pass/yardradius_1.1.2-4.log
testing2sid/pass/yardradius_1.1.2-4.log
wheezy/pass/yardradius_1.1.2-4.log
wheezy2jessie/pass/yardradius_1.1.2-4.log
wheezy2proposed/pass/yardradius_1.1.2-4.log

not sure what you are doing differently?! :)


cheers,
Holger


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

Bug#716827: linux-image-3.9-1-amd64: Not detected laptop webcam with Jessie (ver: 3.9.8-1) although Wheezy (ver: 3.2.35-2) did it

[Caio Begotti]

And what exactly was/is the key combination in case others (like me)
need it and have no clue about it? :-)

On 7/29/13, robert  wrote:
> Package: src:linux
> Version: 3.9.8-1
> Followup-For: Bug #716827
>
> Dear Maintainer,
>
> The bug can be closed.
>
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>
> The reported camera had been deactivated by hardware by mean of a
> rather bizarre key combination.
>  After realizing that, I activated it. Now the camera is working
> without any problem.
>
> Sorry for the annoyance.  I really didn't know that it is possible
> to
> change the camera state in this way.
>
> robert
>
>
>
> -- Package-specific info:
> ** Version:
> Linux version 3.9-1-amd64 (debian-ker...@lists.debian.org) (gcc version
> 4.7.3 (Debian 4.7.3-5) ) #1 SMP Debian 3.9.8-1
>
> ** Command line:
> BOOT_IMAGE=/vmlinuz-3.9-1-amd64 root=/dev/mapper/nyxVG-root ro quiet
>
> ** Tainted: O (4096)
>  * Out-of-tree module has been loaded.
>
> ** Kernel log:
> [   17.132399] ACPI Warning: 0x0500-0x052f SystemIO
> conflicts with Region \GPIO 1 (20130117/utaddress-251)
> [   17.132409] ACPI: If an ACPI driver is available for this device, you
> should use it instead of the native driver
> [   17.132413] lpc_ich: Resource conflict(s) found affecting gpio_ich
> [   17.132670] ACPI Warning: 0xf040-0xf05f SystemIO
> conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20130117/utaddress-251)
> [   17.132698] ACPI: If an ACPI driver is available for this device, you
> should use it instead of the native driver
> [   17.133041] snd_hda_intel :00:1b.0: irq 46 for MSI/MSI-X
> [   17.140257] iTCO_vendor_support: vendor-support=0
> [   17.140857] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
> [   17.140901] iTCO_wdt: Found a Panther Point TCO device (Version=2,
> TCOBASE=0x0460)
> [   17.140993] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
> [   17.153707] input: HDA Intel PCH HDMI/DP,pcm=3 as
> /devices/pci:00/:00:1b.0/sound/card0/input7
> [   17.153863] input: HDA Intel PCH Mic as
> /devices/pci:00/:00:1b.0/sound/card0/input8
> [   17.154003] input: HDA Intel PCH Front Headphone as
> /devices/pci:00/:00:1b.0/sound/card0/input9
> [   17.173250] psmouse serio2: synaptics: Touchpad model: 1, fw: 7.2, id:
> 0x1c0b1, caps: 0xd04733/0xa4/0xa, board id: 3655, fw id: 582762
> [   17.208092] input: SynPS/2 Synaptics TouchPad as
> /devices/platform/i8042/serio2/input/input10
> [   17.460063] ACPI: AC Adapter [AC] (off-line)
> [   17.461015] ACPI Error: [_T_0] Namespace lookup failure,
> AE_ALREADY_EXISTS (20130117/dswload2-330)
> [   17.461027] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog
> (20130117/psobject-222)
> [   17.461033] ACPI Error: Method parse/execution failed [\_SB_.AC__.ADJP]
> (Node 88021549dce0), AE_ALREADY_EXISTS (20130117/psparse-537)
> [   17.461043] ACPI Error: Method parse/execution failed [\_SB_.AC__._PSR]
> (Node 88021549dd30), AE_ALREADY_EXISTS (20130117/psparse-537)
> [   17.461056] ACPI Exception: AE_ALREADY_EXISTS, Error reading AC Adapter
> state (20130117/ac-122)
> [   17.461287] ACPI Error: [_T_0] Namespace lookup failure,
> AE_ALREADY_EXISTS (20130117/dswload2-330)
> [   17.461299] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog
> (20130117/psobject-222)
> [   17.461304] ACPI Error: Method parse/execution failed [\_SB_.AC__.ADJP]
> (Node 88021549dce0), AE_ALREADY_EXISTS (20130117/psparse-537)
> [   17.461314] ACPI Error: Method parse/execution failed [\_SB_.AC__._PSR]
> (Node 88021549dd30), AE_ALREADY_EXISTS (20130117/psparse-537)
> [   17.461325] ACPI Exception: AE_ALREADY_EXISTS, Error reading AC Adapter
> state (20130117/ac-122)
> [   17.461878] ACPI Error: [_T_0] Namespace lookup failure,
> AE_ALREADY_EXISTS (20130117/dswload2-330)
> [   17.461906] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog
> (20130117/psobject-222)
> [   17.461911] ACPI Error: Method parse/execution failed [\_SB_.AC__.ADJP]
> (Node 88021549dce0), AE_ALREADY_EXISTS (20130117/psparse-537)
> [   17.461919] ACPI Error: Method parse/execution failed [\_SB_.AC__._PSR]
> (Node 88021549dd30), AE_ALREADY_EXISTS (20130117/psparse-537)
> [   17.461933] ACPI Exception: AE_ALREADY_EXISTS, Error reading AC Adapter
> state (20130117/ac-122)
> [   17.467192] ACPI: Marking method ADJP as Serialized because of
> AE_ALREADY_EXISTS error
> [   17.468112] ACPI: Marking method _PSR as Serialized because of
> AE_ALREADY_EXISTS error
> [   17.775074] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
> [   17.975784] ACPI: Battery Slot [BAT0] (battery present)
> [   17.976227] wmi: Mapper loaded
> [   18.315303] Adding 8785916k swap on /dev/mapper/nyxVG-swap.  Priority:-1
> extents:1 across:8785916k SS
> [   18.340752] EXT4-fs (dm-1): re-mounted. Opts: (null)
> [   18.442669] EXT4-fs (dm-1): re-mounted. Opts: e

Bug#717988: libusb-1.0-0: upowerd deadlocks in libusb (maybe related to suspend/resume)

[Aurelien Jarno]

forwarded 717988 https://bugzilla.redhat.com/show_bug.cgi?id=985484
thanks

On Sat, Jul 27, 2013 at 06:21:56PM +0300, Pauli wrote:
> Package: libusb-1.0-0
> Version: 2:1.0.16-1
> Severity: important
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> 
> Exact steps are unknown but during last two days I have noticed upowerd
> daemon beeing stuck for unknown reason after suspend/resume.
> 
>* What exactly did you do (or not do) that was effective (or ineffective)?
> 
> I suspend my laptop frequently using keyboard hotkey. That used to work
> without problems until upowerd now started deadlocking.
> 
>* What was the outcome of this action?
> 
> upowerd daemon deadlocks forcing me to manually restart it before any
> power related functionality works in gnome.
> 

The bug has been reported upstream and patches are being written.
Actually a first patch already exists, but has side effects.

I will do a new upload as soon as the final patch is committed (upstream
might do a new release for that).


-- 
Aurelien Jarno  GPG: 1024D/F1BCDB73
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#718256: edbrowse: Wrong URL in control file for Subversion-Repository.

[Simon Kainz]

Package: edbrowse
Version: 3.4.9-1
Severity: minor
Tags: patch

Dear Maintainer,

Typo in Vcs-Svn-URL. Please see my attached patch. 

Regards, Simon


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

Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--- control.orig	2013-07-29 12:56:57.947908330 +0200
+++ control	2013-07-29 12:57:04.708120642 +0200
@@ -7,7 +7,7 @@
 Maintainer: Jean-Philippe MENGUAL 
 Build-Depends: debhelper (>= 9), libreadline-dev, libpcre3-dev, libssl-dev,
  libcurl4-openssl-dev, libmozjs185-dev
-Vcs-Svn: svn://anoncsm.debian.org/collab-maint/deb-maint/edbrowse
+Vcs-Svn: svn://anonscm.debian.org/collab-maint/deb-maint/edbrowse
 Homepage: http://the-brannons.com/edbrowse
 Standards-Version: 3.9.4
 

Bug#708122: Status / need help for pjproject packaging?

[Jeremy Lainé]

Tzafrir,

What is the current status of your Debian packaging for pjproject (still the 
one on github?)?

Can I help you out in any way, as I am eager to see asterisk 11.x in Debian?

Cheers,
Jeremy


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

Bug#696306: freeciv: CVE-2012-5645

[Jonathan Wiltshire]

Package: freeciv

Dear maintainer,

Recently you fixed one or more security problems and as a result you closed
this bug. These problems were not serious enough for a Debian Security
Advisory, so they are now on my radar for fixing in the following suites
through point releases:

squeeze (6.0.8) - use target "oldstable"

Please prepare a minimal-changes upload targetting each of these suites,
and submit a debdiff to the Release Team [0] for consideration. They will
offer additional guidance or instruct you to upload your package.

I will happily assist you at any stage if the patch is straightforward and
you need help. Please keep me in CC at all times so I can
track [1] the progress of this request.

For details of this process and the rationale, please see the original
announcement [2] and my blog post [3].

0: debian-rele...@lists.debian.org
1: http://prsc.debian.net/tracker/696306/
2: <201101232332.11736.th...@debian.org>
3: http://deb.li/prsc

Thanks,

with his security hat on:
--
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51


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

Bug#576998: The Debian Edu packaging team is interested in packaging etherpad-lite

[Johannes Schauer]

Hi,

Quoting Mike Gabriel (2013-03-09 11:43:26)
> In the context of the Debian Edu packaging team> I am interest in  bringing
> this package into Debian.
> 
> Everyone, feel free to join in (debian-edu-pkg-team on Alioth).

Has some packaging of etherpad-lite already been done?

I'm also interested in etherpad-lite and wondered if I have to start from
scratch. I'm successfully running etherpad-lite from its git source for a while
now and packaging shouldn't be too hard?

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#718035: get-orig-source is not policy compliant

[Mathias Ertl]

Hi,

I've removed the get-orig-source target in the git-repo. But since its
an optional line anyway, I haven't tagged a new version. Or do you think
I should tag a new version?

greetings, Mati

On 07/28/2013 05:13 AM, Thomas Goirand wrote:
> Package: python-mimeparse
> Version: 0.1.4-1
> Severity: important
> 
> Here's the FTP masters remark after validating mimeparse 0.1.4. Please fix
> this problem on the next upload.
> 
>  Original Message 
> Subject: Comments regarding python-mimeparse_0.1.4-1_amd64.changes
> Date: Sat, 27 Jul 2013 23:33:33 +
> From: Paul Richards Tagliamonte 
> To: Mathias Ertl ,  
> CC: Debian FTP Masters 
> 
> Howdy, maintainer,
> 
> Please either fix or remove the get-orig-source line; from
> the policy - section 4.9:
> 
>   This target may be invoked in any directory, and should take care to clean
>   up any temporary files it may have left.
> 
> Clearly, uscan can't be invoked in any directory :)
> 
> It's optional, so I'm letting it through, (and since this target is also
> broken
> in the archive.) It'd be nice to get that fixed quickly, though! :)
> 
> Cheers,
>   Paul
> 


-- 
twitter: @mathiasertl | xing: Mathias Ertl | email: m...@er.tl
I only read plain-text mail!  I prefer signed/encrypted mail!



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#718193: Gtk-WARNING: Theme parsing error

[Alex Wilk]

Package: gtk3-engines-oxygen
Followup-For: Bug #718193

Dear Dmitry,

# LANG=en ac policy libgtk-3-0
libgtk-3-0: Installed: 3.8.2-3

Works, thanks!


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

Bug#717780: RFS: ruby-serverspec/0.7.1-1 [ITP] -- RSpec tests for your servers

[dai]

On Thu, Jul 25, 2013 at 11:51:58AM +0900, KURASHIKI Satoru wrote:
> dget -x 
> http://mentors.debian.net/debian/pool/main/r/ruby-serverspec/ruby-serverspec_0.7.1-1.dsc

ruby-serverspec: Newer version (0.7.2) available.
debian/control: don't you use anonscm.debian.org repository?
debian/patches/fix-sample: remains template strings.
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: Digital signature

Bug#576998: The Debian Edu packaging team is interested in packaging etherpad-lite

[Mike Gabriel]

Hi Josch,

- Original message -
> Hi,
> 
> Quoting Mike Gabriel (2013-03-09 11:43:26)
> > In the context of the Debian Edu packaging team> I am interest in 
> > bringing this package into Debian.
> > 
> > Everyone, feel free to join in (debian-edu-pkg-team on Alioth).
> 
> Has some packaging of etherpad-lite already been done?
> 
> I'm also interested in etherpad-lite and wondered if I have to start from
> scratch. I'm successfully running etherpad-lite from its git source for
> a while now and packaging shouldn't be too hard?

I have started packaging the enormous list of dependencies for etherpad-lite. 
You cannot use npm in Debian, so every npm package must be built as .deb 
package.

All node-* and *.js found on my QA page [1] are related to the packaging of 
etherpad-lite. And there are many a more

[1] http://qa.debian.org/developer.php?login=mike.gabriel%40das-netzwerkteam.de

So what you can do is: join pkg-javascript-devel on lists.alioth.debian.org and 
peer into #debian-js IRC, so that we can coordinate the dependency packaging. 
(/me is sunweaver on IRC).

Greets,
Mike

-- 

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

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


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

Bug#718224: UDP_ENCAP kernel definition doesn't match userland

[Robert Millan]

2013/7/29 Steven Chamberlain :
> Some code appears to have
> possibly hardcoded a value of 100.  And even NetBSD seems to have
> chosen that value.  So I think we should simply change GNU/kFreeBSD to
> use 100 in the kernel.
>
> I don't foresee any breakage from such a change.  This is only relevant
> to IPSEC-enabled kernels anyway, which Debian doesn't currently build.
>
> Alternatively we could even accept *both* values to mean UDP_ENCAP.

For proposals to change kernel-user ABI, would it be possible to
discuss them in freebsd-arch instead? It seems to me that you have a
strong case in favour of accepting both values.

Upstream is receptive to changes that improve their compatibility.
Running Debian in a chroot on FreeBSD is a valid use case that they
would be happy to discuss improvements about as long as they're not
detrimental to FreeBSD userland.

I still think the right solution would be to move UDP_ENCAP into a
kernel-specific header, though. But I don't see why we can't have both
(FreeBSD can benefit from supporting Wheezy chroots regardless of what
Glibc does in the future).


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

Bug#718250: kfreebsd-image-9.1-1-amd64: attaching USB keyboard makes system reboot

[Robert Millan]

2013/7/29 Lars Lansink :
>* What led up to the situation?
>  After upgrading a headless wheezy to jessie and after the reboot 
> attaching a USB keyboard.
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>  Powered down the system, attached keyboard and screen, powered on.
>* What was the outcome of this action?
>  Endless reboot loop due to KBD: stack traceback.
>* What outcome did you expect instead?
>  Usable keyboard.

Can you reproduce this using kfreebsd-downloader-9.1?


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

Bug#718257: Use the current timezone by default

[Yuri D'Elia]

Package: gpscorrelate
Version: 1.6.1-4
Severity: wishlist

It would be nice if gpscorrelate would actually make use of the current
timezone for correlating photos instead of defaulting to '0'. All cameras that
I used write the time in the local timezone, and even the manpage seems to
suggest that -z should basically always be used.

I'm currently using the following alias:

  gpscorrelate -z $(date +%::z)

but it feels like unnecessary burden.

Thanks.


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

Bug#713012: [lintian] patch

[bastien ROUCARIES]

Package: lintian
Version: 2.5.13

patch here

Notice that I have created a common-license data in case of new license in data 
for checking .gz
From ab3489353b6504d098bd03efc8f051ff086d83d6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bastien=20ROUCARI=C3=88S?= 
Date: Mon, 29 Jul 2013 13:06:05 +0200
Subject: [PATCH 1/2] Add generic infrastructure for checking common-licenses

Add data/copyright-file/common-licenses in order to robustly check
reference to /usr/share/common-licenses.
---
 checks/copyright-file.pm|7 +--
 data/copyright-file/common-licenses |   16 
 2 files changed, 21 insertions(+), 2 deletions(-)
 create mode 100644 data/copyright-file/common-licenses

diff --git a/checks/copyright-file.pm b/checks/copyright-file.pm
index e126df6..7fd5251 100644
--- a/checks/copyright-file.pm
+++ b/checks/copyright-file.pm
@@ -32,6 +32,7 @@ use Lintian::Tags qw(tag);
 use Lintian::Util qw(slurp_entire_file file_is_encoded_in_non_utf8);
 
 our $KNOWN_ESSENTIAL = Lintian::Data->new('fields/essential');
+our $KNOWN_COMMON_LICENSES =  Lintian::Data->new('copyright-file/common-licenses');
 
 sub run {
 
@@ -115,8 +116,10 @@ if (m,\r,) {
 
 my $wrong_directory_detected = 0;
 
-if (m,(usr/share/common-licenses/(?:GPL|LGPL|BSD|Artistic)\.gz),) {
-tag 'copyright-refers-to-compressed-license', $1;
+if (m,(usr/share/common-licenses/(?'licensename'.*?)\.gz),) {
+if($KNOWN_COMMON_LICENSES->known($+{licensename})) {
+tag 'copyright-refers-to-compressed-license', $1;
+}
 }
 
 # Avoid complaining about referring to a versionless license file if the word
diff --git a/data/copyright-file/common-licenses b/data/copyright-file/common-licenses
new file mode 100644
index 000..d627204
--- /dev/null
+++ b/data/copyright-file/common-licenses
@@ -0,0 +1,16 @@
+# /usr/share/common-licenses list
+# generated by ls -1 /usr/share/common-licenses/
+Apache-2.0
+Artistic
+BSD
+GFDL
+GFDL-1.2
+GFDL-1.3
+GPL
+GPL-1
+GPL-2
+GPL-3
+LGPL
+LGPL-2
+LGPL-2.1
+LGPL-3
-- 
1.7.10.4

From 17490607edf651969e6762ab6679c4dc9ad63e38 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bastien=20ROUCARI=C3=88S?= 
Date: Mon, 29 Jul 2013 14:29:37 +0200
Subject: [PATCH 2/2] Warm about apache-2 license and no link to common
 license

Warm if license is apache-2 and we do not link to /usr/share/license-common
---
 checks/copyright-file.desc |   14 +++
 checks/copyright-file.pm   |3 +++
 .../debian/debian/control.in   |   14 +++
 ...right-missing-apache2-license-pointer.copyright |   26 
 t/tests/copyright-file-general/desc|1 +
 t/tests/copyright-file-general/tags|2 ++
 6 files changed, 60 insertions(+)
 create mode 100644 t/tests/copyright-file-general/debian/debian/copyright-missing-apache2-license-pointer.copyright

diff --git a/checks/copyright-file.desc b/checks/copyright-file.desc
index 3f45227..0da7605 100644
--- a/checks/copyright-file.desc
+++ b/checks/copyright-file.desc
@@ -169,6 +169,20 @@ Info: If your package is released under the same terms as Perl itself,
  it should refer to the Artistic and GPL license files in the
  /usr/share/common-licenses directory.
 
+Tag: copyright-should-refer-to-common-license-file-for-apache-2
+Severity: important
+Certainty: possible
+Ref: policy 12.5
+Info: The strings Apache License, Version or Apache-2 appear in the
+ copyright file for this package, but the copyright file does not
+ reference /usr/share/common-licenses as the location of the
+ Apache-2 on Debian systems.
+ .
+ If the package uses some other license that just mentions the Apache-2 and
+ that Lintian should detect as an exception, please file a Lintian bug.
+ If the copyright file must mention the Apache-2 for reasons other than 
+ stating the license of the package, please add a Lintian override.
+
 Tag: copyright-should-refer-to-common-license-file-for-gpl
 Severity: important
 Certainty: possible
diff --git a/checks/copyright-file.pm b/checks/copyright-file.pm
index 7fd5251..5f5c492 100644
--- a/checks/copyright-file.pm
+++ b/checks/copyright-file.pm
@@ -223,7 +223,10 @@ if (m,/usr/share/common-licenses,
 } elsif (m/GNU General Public License/i or m/\bGPL\b/) {
 tag 'copyright-should-refer-to-common-license-file-for-gpl';
 $gpl = 1;
+} elsif (m/Apache License\s+,? Version 2\.0/i or m/\bApache-2(?:\.0)?\b/) {
+tag 'copyright-should-refer-to-common-license-file-for-apache-2';
 }
+
 if (m,(?:under )?(?:the )?(?:same )?(?:terms )?as Perl itself,i &&
 !m,usr/share/common-licenses/,) {
 tag 'copyright-file-lacks-pointer-to-perl-license';
diff --git a/t/tests/copyright-file-general/debian/debian/control.in b/t/tests/copyright-file-general/debian/debian/control.in
index 3277846..e98b351 100644
--- a/t/tests/copyright-file-general/debian/debian/control.in
+++ b/t/tests/copyright-file-general/debian/debian/control.in
@@ -182,6 +182,20 @@ Descriptio

Bug#687022: [lintian] close ?

[bastien ROUCARIES]

Package: lintian
Version: 2.5.13

it seems that the second point you raised was correct.
So time to close this bug ?

Bastien


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

Bug#717473: [PATCH] adm64_edac: Fix single-channel setups

[Borislav Petkov]

It can happen that configurations are running in a single-channel mode
even with a dual-channel memory controller, by, say, putting the DIMMs
only on the one channel and leaving the other empty. This causes a
problem in init_csrows which implicitly assumes that when the second
channel is enabled, i.e. channel 1, the struct dimm hierarchy will be
present. Which is not.

So always allocate two channels unconditionally.

This provides for the nice side effect that the data structures are
initialized so some day, when memory hotplug is supported, it should
just work out of the box when all of a sudden a second channel appears.

Reported-and-tested-by: Roger Leigh 
Signed-off-by: Borislav Petkov 
---
 drivers/edac/amd64_edac.c | 9 -
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/drivers/edac/amd64_edac.c b/drivers/edac/amd64_edac.c
index 8b6a0343c220..8b3d90143514 100644
--- a/drivers/edac/amd64_edac.c
+++ b/drivers/edac/amd64_edac.c
@@ -2470,8 +2470,15 @@ static int amd64_init_one_instance(struct pci_dev *F2)
layers[0].size = pvt->csels[0].b_cnt;
layers[0].is_virt_csrow = true;
layers[1].type = EDAC_MC_LAYER_CHANNEL;
-   layers[1].size = pvt->channel_count;
+
+   /*
+* Always allocate two channels since we can have setups with DIMMs on
+* only one channel. Also, this simplifies handling later for the price
+* of a couple of KBs tops.
+*/
+   layers[1].size = 2;
layers[1].is_virt_csrow = false;
+
mci = edac_mc_alloc(nid, ARRAY_SIZE(layers), layers, 0);
if (!mci)
goto err_siblings;
-- 
1.8.3

-- 
Regards/Gruss,
Boris.

Sent from a fat crate under my desk. Formatting is fine.
--


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

Bug#718258: libgphoto2-2: turns on libusbx debugging by default

[Martin Pitt]

Package: libgphoto2-2
Version: 2.4.14-2.3

Hello,

The change from libusb to libusbx in libgphoto2 now somehow turned on libusbx
debugging by default:

$ gphoto2 --auto-detect
libusbx: debug [libusb_get_device_list]
libusbx: debug [discovered_devs_append] need to increase capacity
libusbx: debug [libusb_get_device_descriptor]

The same can be seen when starting shotwell, so it's not a problem in the
gphoto2 binary. It does not happen with "lsusb", so it seems it's also not a
problem with libusbx itself.

Thanks for considering,

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


signature.asc
Description: Digital signature

Bug#711069: [lintian] patch

[bastien ROUCARIES]

Package: lintian
Version: 2.5.13

patch here
From 798a031f470e459cc546653ea9023ac86199a251 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bastien=20ROUCARI=C3=88S?= 
Date: Mon, 29 Jul 2013 14:58:49 +0200
Subject: [PATCH] Check for typo like description: description : in field

Check for duplicated fieldname in field
---
 checks/control-file.desc  |8 
 checks/control-file.pm|4 
 t/tests/control-file-general/debian/debian/control.in |   10 ++
 t/tests/control-file-general/desc |1 +
 t/tests/control-file-general/tags |3 ++-
 5 files changed, 25 insertions(+), 1 deletion(-)

diff --git a/checks/control-file.desc b/checks/control-file.desc
index 6fb786d..9903063 100644
--- a/checks/control-file.desc
+++ b/checks/control-file.desc
@@ -36,6 +36,14 @@ Info: The field on this line of debian/control has whitespace
  in the syntax of Debian control files, but as Policy says, it is
  conventional to put a single space after the colon.
 
+Tag: debian-control-has-repeated-field-name-as-field
+Severity: normal
+Certainty: possible
+Ref: policy 5.1
+Info: The field on this line of debian/control has been 
+ repeated in the field description, like for instance
+ Maintainer: Maintainer: maintai...@mail.example.com. 
+
 Tag: binary-control-field-duplicates-source
 Severity: wishlist
 Certainty: certain
diff --git a/checks/control-file.pm b/checks/control-file.pm
index cf56840..ee985db 100644
--- a/checks/control-file.pm
+++ b/checks/control-file.pm
@@ -84,6 +84,10 @@ while (<$fd>) {
 unless (/^\S+: \S/ || /^\S+:$/) {
 tag 'debian-control-has-unusual-field-spacing', "line $.";
 }
+# something like "Maintainer: Maintainer: bad field"
+if (/^(\S+):\s*\1\s*:/) {
+tag 'debian-control-has-repeated-field-name-as-field', "line $.";
+}
 }
 }
 close($fd);
diff --git a/t/tests/control-file-general/debian/debian/control.in b/t/tests/control-file-general/debian/debian/control.in
index d99a5b2..dc5d694 100644
--- a/t/tests/control-file-general/debian/debian/control.in
+++ b/t/tests/control-file-general/debian/debian/control.in
@@ -72,6 +72,16 @@ Description: {$description} (four)
  Lintian.  It is part of the Lintian test suite and may do very odd
  things.  It should not be installed like a regular package.  It may
  be an empty package.
+ 
+Package: {$srcpkg}-5
+Section: {$section}
+Architecture: {$architecture}
+Depends: $\{shlibs:Depends\}, $\{misc:Depends\}
+Description: Description: {$description}
+ This is a test package designed to exercise some feature or tag of
+ Lintian.  It is part of the Lintian test suite and may do very odd
+ things.  It should not be installed like a regular package.  It may
+ be an empty package.
 
 Package: {$srcpkg}-udeb
 Section: debian-installer
diff --git a/t/tests/control-file-general/desc b/t/tests/control-file-general/desc
index 100880e..edde9fe 100644
--- a/t/tests/control-file-general/desc
+++ b/t/tests/control-file-general/desc
@@ -6,6 +6,7 @@ Test-For:
  binary-control-field-duplicates-source
  build-info-in-binary-control-file-section
  control-file-contains-dh_make-vcs-comment
+ debian-control-has-repeated-field-name-as-field
  duplicate-long-description
  duplicate-short-description
  missing-separator-between-items
diff --git a/t/tests/control-file-general/tags b/t/tests/control-file-general/tags
index 506cc2e..b9ca609 100644
--- a/t/tests/control-file-general/tags
+++ b/t/tests/control-file-general/tags
@@ -3,10 +3,11 @@ E: control-file-general source: missing-separator-between-items in control-file-
 E: control-file-general source: obsolete-relation-form-in-source in control-file-general-1 breaks: libsqlite3-0 (< 3.6.12)
 E: control-file-general source: obsolete-relation-form-in-source in source build-depends-indep: perl (> 5.8)
 I: control-file-general source: binary-control-field-duplicates-source field "maintainer" in package control-file-general
-I: control-file-general source: duplicate-long-description control-file-general control-file-general-1 control-file-general-2 control-file-general-3 control-file-general-4
+I: control-file-general source: duplicate-long-description control-file-general control-file-general-1 control-file-general-2 control-file-general-3 control-file-general-4 control-file-general-5
 I: control-file-general source: duplicate-short-description control-file-general control-file-general-1
 I: control-file-general source: xs-vcs-header-in-debian-control xs-vcs-svn
 W: control-file-general source: control-file-contains-dh_make-vcs-comment
+W: control-file-general source: debian-control-has-repeated-field-name-as-field line 80
 W: control-file-general source: no-section-field-for-source
 W: control-file-general source: package-depends-on-itself control-file-general depends
 W: control-file-general source: stronger-dependency-implies-weaker control-file-general depends ->

Bug#718259: libgtkada: Fix missing dependency and autopkgtest

[Martin Pitt]

Package: libgtkada
Version: 2.24.1-11 
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch saucy

Hello,

libgtkada's autopkgtest is currently broken [1]:

  gnatlink: error when calling /usr/bin/gcc-4.6
  /usr/bin/ld: cannot find -lgtkgl-2.0
  collect2: ld returned 1 exit status
  gnatmake: *** link failed.

This proves that libgtkglada2.24.1-dev ought to depend on
libgtkgl2.0-dev, or be fixed to not require the dependency (thus is
this not a problem with the test, but an actual packaging bug).

When adding this, the build succeeds, but running the test program
fails due to missing $DISPLAY. Thus the test ought to run under xvfb.

The attached debdiff fixes both, see the recent runs on [2].

Thanks for considering,

Martin

[1] 
https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy-adt-libgtkada/5/ARCH=i386,label=adt/
[2] 
https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy-adt-libgtkada/
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
diff -Nru libgtkada-2.24.1/debian/changelog libgtkada-2.24.1/debian/changelog
--- libgtkada-2.24.1/debian/changelog   2013-07-22 20:34:37.0 +0200
+++ libgtkada-2.24.1/debian/changelog   2013-07-26 08:58:39.0 +0200
@@ -1,3 +1,13 @@
+libgtkada (2.24.1-11ubuntu1) saucy; urgency=low
+
+  * Add missing libgtkgl2.0-dev dependency to libgtkglada2.24.1-dev (spotted
+by autopkgtest).
+  * debian/tests/control: Add xvfb test dependency.
+  * debian/tests/link-with-shared: Run test program through xvfb as it needs a
+$DISPLAY.
+
+ -- Martin Pitt   Fri, 26 Jul 2013 08:57:39 +0200
+
 libgtkada (2.24.1-11) unstable; urgency=low
 
   * copyright: now machine-readable.
diff -Nru libgtkada-2.24.1/debian/control libgtkada-2.24.1/debian/control
--- libgtkada-2.24.1/debian/control 2013-07-22 18:19:35.0 +0200
+++ libgtkada-2.24.1/debian/control 2013-07-26 08:58:41.0 +0200
@@ -65,6 +66,7 @@
 Section: libdevel
 Architecture: any
 Depends: ${misc:Depends}, ${ada:Depends},
+ libgtkgl2.0-dev,
  libgl1-mesa-dev
 Suggests: libgtkada-doc (= ${binary:Version})
 Description: Ada binding for GTK+ OpenGL extensions (development files)
diff -Nru libgtkada-2.24.1/debian/tests/control 
libgtkada-2.24.1/debian/tests/control
--- libgtkada-2.24.1/debian/tests/control   2013-07-22 18:19:35.0 
+0200
+++ libgtkada-2.24.1/debian/tests/control   2013-07-26 08:58:09.0 
+0200
@@ -1 +1,2 @@
 Tests: link-with-shared
+Depends: @, xvfb
diff -Nru libgtkada-2.24.1/debian/tests/link-with-shared 
libgtkada-2.24.1/debian/tests/link-with-shared
--- libgtkada-2.24.1/debian/tests/link-with-shared  2013-07-22 
18:19:35.0 +0200
+++ libgtkada-2.24.1/debian/tests/link-with-shared  2013-07-26 
08:58:26.0 +0200
@@ -24,4 +24,4 @@
 end P;
 EOF
 gnatmake -q -P p.gpr
-./main
+xvfb-run ./main


signature.asc
Description: Digital signature

Bug#718260: 1:2.0.3-3 doesn't support grub-legacy

[Michal Hocko]

Package: kexec-tools
Version: 1:2.0.3-2
Severity: normal

Hi,
I am not sure what is the current policy regarding grub-legacy but the
current update from 1:2.0.3-2 -> 1:2.0.3-3 requires grub2-common (>=
2.00) which basically puts grub-legacy into the old trash.

I assume this came up from:
  * Fixed kexec-load init script to parse newer grub.cfg files correctly
(closes: Bug#714016)

Is it possible that both old and the new grub configurations would be
supported?

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

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

Versions of packages kexec-tools depends on:
ii  debconf [debconf-2.0]  1.5.50
ii  libc6  2.17-5

kexec-tools recommends no packages.

kexec-tools suggests no packages.

-- debconf information:
  kexec-tools/use_grub_config: false
* kexec-tools/load_kexec: true

-- 
Michal Hocko


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

Bug#718261: Home page is not correct

[Sergey Alyoshin]

Package: gerbv

gerbv homepage is gerbv.geda-project.org
gerbv.gpleda.org only list links.


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

Bug#632627: Re[4]: resume file

[Rodolfo García Peñas (kix)]

Askar Safin  escribió:


But I wonder whether this configuration file is really needed for most
system.  Couldn't we use blkid to find the swap partition automagically?
(The configuration file would still be necessary if there are multiple
swap partitions.)

Imagine the following: there is Debian on /dev/sda1, Debian on
/dev/sda2 and swap on /dev/sda3.
Debian on sda2 configured to use sda3. Debian on sda1 doesn't use
swap. Debian on sda2 suspends to sda3. Then user runs Debian on sda1.
Initramfs from sda1 looks at the sda3 and says: "Oh! There is swap.
Let's wake up from it". And initramfs performs waking up from wrong
partition.
So, don't search swap at the resume time.


initramfs-tools has its own resume configuration file, but so far as I
can see the uswsusp package does not use it. So there would be no
reason for you to modify it - would there?

No, "resume" file is really used. It used by early userspace. I just
created virtual machine with fresh jessie and without swap and
performed the following test:
1. Installed uswsusp. uswsusp said to me that I have no swap and I
should add it and run "dpkg-reconfigure uswsusp".
2. I added swap
3. Rebooted
4. I ran "dpkg-reconfigure uswsusp". uswsusp found my swap and it
was happy. It asked me a lot of questions. Then uswsusp triggered
initramfs rebuilding
5. Rebooted
6. I ran "s2disk" and I could not wake up. So, this is a bug.
7. I created "resume" file (there was no such file before) and I put
"RESUME=UUID=..." to it.
8. I ran "s2disk" and it failed again (of course, because
/etc/initramfs-tools/conf.d/resume alone is not enough, there should
be /conf/conf.d/resume in initramfs).
9. I ran "dpkg-reconfigure uswsusp", it triggered initramfs (so,
/conf/conf.d/resume was created)
10. I successfully performed "s2disk"

In fact, s2disk works (without manual editing configs) only if you
created swap at installing of Debian.


The uswsusp package can edit its own configuration file though I do not
recommend it. I think it would be better to leave the resume device
unspecified in /etc/uswsusp.conf by default, and then to select it
automatically (both at suspend and resume time) if possible.

As I said, selecting automatically at resume time is bad idea.
At suspend time is probably, too, because two systems can have one swap.

Ideally, there should be some guarantee that if user didn't edit
configs himself and it performed suspend then he guaranteed wakes up
successfully.
Of course, such guarantee is very important because user can have a
lot of opened programs, unsaved documents etc. Ideally, s2disk
should perform some checks (for example, it can check configs) that
all is OK, before doing real suspending.
If uswsusp detects swap automatically, then there was no such
guarantee. For example, let's assume, uswsusp detects swap
automatically, and let's assume this bug #632627 is fixed (i. e.
"dpkg-reconfigure uswsusp" writes "resume"). User just added new
swap and didn't run any "dpkg-reconfigure" yet. Then he ran
"s2disk". "s2disk" detected his swap, suspended. And then this user
cannot wake up, because "dpkg-reconfigure" is not done and "resume"
is not written.

Askar Safin


So, initramfs-tools should read /etc/uswsusp.conf and add the resume
device to the resume file?

Then, when the user run dpkg-reconfigure uswsusp,
update-initramfs-tools will update the initrd resume file and then the
system know where find the resume file.

kix

--
 .''`.
: :'  : Rodolfo García Peñas (kix) 
`. `'`  Proud Debian Developer
 `-


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

Bug#718262: wget: NTLM not supported

[Vladislav Kurz]

Package: wget
Version: 1.13.4-3
Severity: normal


Hello,

after upgrading from squeeze to wheezy, wget cannot connect to NTLM 
authenticated web sites any more.
It says "unknown authentication scheme". After some googling I decided to 
recompile with options:

--enable-ntlm

However it did not help, and I got error message that I need openssl instead of 
gnutls.
So I have installed libssl-dev and added another option:

--with-ssl=openssl

And now NTLM auth is working.

Is ther any particular reason why gnuTLS is used by default, and why gnuTLS 
does not support NTLM?

Regards
Vladislav Kurz


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

Bug#718258: libgphoto2-2: turns on libusbx debugging by default

[Martin Pitt]

tag 718258 patch
user ubuntu-de...@lists.ubuntu.com
usertags 718258 origin-ubuntu saucy ubuntu-patch
thanks

Hello again,

Martin Pitt [2013-07-29 14:47 +0200]:
> The change from libusb to libusbx in libgphoto2 now somehow turned on libusbx
> debugging by default:

Tested debdiff (uploaded to Ubuntu).

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
diff -Nru libgphoto2-2.4.14/debian/changelog libgphoto2-2.4.14/debian/changelog
--- libgphoto2-2.4.14/debian/changelog  2013-07-25 23:28:36.0 +0200
+++ libgphoto2-2.4.14/debian/changelog  2013-07-29 14:54:42.0 +0200
@@ -1,3 +1,11 @@
+libgphoto2 (2.4.14-2.3ubuntu1) saucy; urgency=low
+
+  * Add 02-libusbx_no_debug.patch: Disable libusbx debugging messages by
+default. They can be turned back on with $LIBUSB_DEBUG if necessary.
+(LP: #1206104, Closes: #718258)
+
+ -- Martin Pitt   Mon, 29 Jul 2013 14:54:17 +0200
+
 libgphoto2 (2.4.14-2.3) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru libgphoto2-2.4.14/debian/patches/02-libusbx_no_debug.patch 
libgphoto2-2.4.14/debian/patches/02-libusbx_no_debug.patch
--- libgphoto2-2.4.14/debian/patches/02-libusbx_no_debug.patch  1970-01-01 
01:00:00.0 +0100
+++ libgphoto2-2.4.14/debian/patches/02-libusbx_no_debug.patch  2013-07-29 
14:54:14.0 +0200
@@ -0,0 +1,17 @@
+Description: Disable libusbx debugging messages by default. They can be turned 
back on with $LIBUSB_DEBUG if necessary.
+Author: Martin Pitt 
+Bug-Ubuntu: https://launchpad.net/bugs/1206104
+Bug-Debian: http://bugs.debian.org/718258
+
+Index: libgphoto2-2.4.14/libgphoto2_port/libusb1/libusb1.c
+===
+--- libgphoto2-2.4.14.orig/libgphoto2_port/libusb1/libusb1.c   2013-07-29 
14:48:49.0 +0200
 libgphoto2-2.4.14/libgphoto2_port/libusb1/libusb1.c2013-07-29 
14:52:26.250620640 +0200
+@@ -260,7 +260,6 @@
+   port->pl->config = port->pl->interface = port->pl->altsetting = -1;
+ 
+   libusb_init (&port->pl->ctx);
+-  libusb_set_debug (port->pl->ctx, 255);
+ 
+ #if 0
+   usb_init ();
diff -Nru libgphoto2-2.4.14/debian/patches/series 
libgphoto2-2.4.14/debian/patches/series
--- libgphoto2-2.4.14/debian/patches/series 2013-07-25 23:25:22.0 
+0200
+++ libgphoto2-2.4.14/debian/patches/series 2013-07-29 14:52:11.0 
+0200
@@ -2,3 +2,4 @@
 #11_hurd_no_path_max_bsdsource
 01-increase_max_entries.patch
 kFreeBSD-ENODATA.patch
+02-libusbx_no_debug.patch


signature.asc
Description: Digital signature

Bug#718263: Backtrace when adding printer with French locales

[Laurent Bigonville]

Package: system-config-printer
Version: 1.4.1-3
Severity: important

Hi,

When trying to add a new printer I get the following backtrace:

Traceback (most recent call last):
  File "/usr/share/system-config-printer/newprinter.py", line 3587, in 
on_tvNPModels_cursor_changed
self.fillDriverList(self.NPMake, pmodel)
  File "/usr/share/system-config-printer/newprinter.py", line 3539, in 
fillDriverList
iter = model.append ((driver + _(" (recommended)"),))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 11: 
ordinal not in range(128)

This seems to be related to the French translation of "recommended" (using 
fr_BE.utf8 locales).

Changing the locales to "C" is preventing this backtrace

Cheers

Laurent Bigonville

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

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

Versions of packages system-config-printer depends on:
ii  gir1.2-gdkpixbuf-2.0   2.28.2-1
ii  gir1.2-glib-2.01.36.0-2+b1
ii  gir1.2-gtk-3.0 3.8.2-3
ii  gir1.2-notify-0.7  0.7.5-2
ii  gir1.2-packagekitglib-1.0  0.8.10-1
ii  gir1.2-pango-1.0   1.32.5-5+b1
ii  gnome-icon-theme   3.8.2-2
ii  python 2.7.5-2
ii  python-cups1.9.62-2
ii  python-cupshelpers 1.4.1-3
ii  python-dbus1.2.0-2
ii  python-libxml2 2.9.1+dfsg1-2
ii  python-support 1.0.15

Versions of packages system-config-printer recommends:
ii  cups-pk-helper  0.2.5-1
ii  gir1.2-gnomekeyring-1.0 3.8.0-2
ii  python-smbc 1.0.6-1+b1
ii  system-config-printer-udev  1.4.1-3

Versions of packages system-config-printer suggests:
pn  python-gnomekeyring  
pn  sessioninstaller 

-- no debconf information

-- debsums errors found:
sh: 1: /usr/sbin/dpkg-divert: not found


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

Bug#718264: luatex builds with internal copies of poppler and libzzip (and pixman?)

[Matthias Klose]

Package: luatex
Version: 0.76.0-1
Severity: important

luatex builds with internal copies of poppler and libzzip. build dependencies
for poppler and pixman exist, but apparently are not used.  libzzip doesn't
appear in the build dependencies at all.


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

Bug#97045: [Popcon-developers] Bug#97045: +1

[Bill Allombert]

On Sun, Jul 28, 2013 at 04:22:37PM +0200, Thomas Hood wrote:
> It would be very useful to maintainers to know what versions of packages
> are in use and with what relative frequency.

Hello Thomas,
I have no plan for popcon to report package versions. This would reduce privacy
and reduce the anonimity of the system too much.

On the other hand, popcon now provide separate statistics for stable, so you
can estimate the packages version frequency.

Also I think you are overstating the usefulness of packages version, unless 
people
use package outside of stable/testing/unstable, which then would increase the
privacy/security issue.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


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

Bug#717376: sorry for the noise

[Holger Levsen]

control: tags -1 - moreinfo unreproducible

Hi,

sigh, I guess I look somewhat stupid now, for repeating what I did nine days 
ago. The explaination is simple though: we working on RC bugs potentially 
affecting wheezy I use a custom script in combination with UDD. And my custom 
script uses /usr/bin/bts _and caching_ so when I looked at this bug today 
(among 30 other new RC bugs potentially affecting wheezy) this bug looked 
familar but I didnt recognized it, thus I did what I did.

So, sorry for the noise!


cheers,
Holger




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

Bug#718265: gvfs-backends: fails to mount secure WebDAV: SSL Handshake failed. server supports ECDH only.

[Sebastian Birkl]

Package: gvfs-backends
Version: 1.16.3-1
Severity: important

Dear Maintainer,
i tried to mount a secure WebDAV share with GVFS (gvfs-mount and Xfce) and it 
fails with Error mounting location: HTTP Error: SSL handshake failed.
The server supports ECDH ciphers only and the CA is imported into the system 
located at /usr/local/share/ca-certificates.
Server CA is located at http://reb00t.wtf.im/reb00t.crt
WebDAV at https://reb00t.wtf.im/remote.php/webdav/

Wget is also telling me that something is wrong. (dont worry about the ip 
address, just a LAN workaround for a not working nat reflection)
~ $ wget https://reb00t.wtf.im
--2013-07-29 15:26:43--  https://reb00t.wtf.im/
Resolving reb00t.wtf.im (reb00t.wtf.im)... 192.168.2.254
Connecting to reb00t.wtf.im (reb00t.wtf.im)|192.168.2.254|:443... connected.
GnuTLS: A TLS fatal alert has been received.
Unable to establish SSL connection.

nginx config:
ssl_ciphers 
ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES256-SHA:!MEDIUM:!LOW:!RC4:!aNULL:!MD5:!kEDH;

Iceweasel / Icedove and Android can connect without a problem.
And i am not planning to enable other ciphers.

If i am doing something wrong, please tell me.

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

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

Versions of packages gvfs-backends depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.16.1-1
ii  gvfs 1.16.3-1
ii  gvfs-common  1.16.3-1
ii  gvfs-daemons 1.16.3-1
ii  gvfs-libs1.16.3-1
ii  libarchive13 3.1.2-7
ii  libavahi-client3 0.6.31-2
ii  libavahi-common3 0.6.31-2
ii  libavahi-glib1   0.6.31-2
ii  libbluetooth34.101-2
ii  libc62.17-7
ii  libcdio-cdda10.83-4
ii  libcdio-paranoia10.83-4
ii  libcdio130.83-4
ii  libdbus-1-3  1.6.12-1
ii  libdbus-glib-1-2 0.100.2-1
ii  libexpat12.1.0-4
ii  libgcrypt11  1.5.2-3
ii  libglib2.0-0 2.36.3-3
ii  libgoa-1.0-0 3.8.2-1
ii  libgphoto2-2 2.4.14-2.1
ii  libgphoto2-port0 2.4.14-2.1
ii  libgtk-3-0   3.8.2-3
ii  libgudev-1.0-0   175-7.2
ii  libimobiledevice21.1.1-4
ii  libmtp9  1.1.6-2
ii  libplist11.8-1
ii  libsmbclient 2:3.6.16-2
ii  libsoup-gnome2.4-1   2.42.2-6
ii  libsoup2.4-1 2.42.2-6
ii  libxml2  2.9.1+dfsg1-2
ii  psmisc   22.20-1

Versions of packages gvfs-backends recommends:
ii  gnome-keyring  3.8.2-2

Versions of packages gvfs-backends suggests:
pn  obex-data-server  
ii  samba-common  2:3.6.16-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#702075: Abandoning Hexchat ITP

[Andreas Rönnquist]

noowner 702075
retitle 702075 RFP: hexchat -- an IRC client based on XChat
thanks

I am abandoning this ITP - First, it has a GPL license, but links
OpenSSL, but doesn't have an OpenSSL exception, which makes it a bit
problematic.
- 
Other than that, Hexchat is in active development upstream, but there
was talk from someone that said that he planned to continue XChat
development (as a fork of Hexchat if I understand correctly) and had got
the necessary rights from the previous XChat developer. Since XChat is
already present in Debian, I am guessing that they would continue
packaging this work. 

-- Andreas Rönnquist
gus...@gusnan.se


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

Bug#718258: libgphoto2-2: turns on libusbx debugging by default

[Markus Koschany]

On 29.07.2013 15:13, Martin Pitt wrote:
> tag 718258 patch
> user ubuntu-de...@lists.ubuntu.com
> usertags 718258 origin-ubuntu saucy ubuntu-patch
> thanks
> 
> Hello again,
> 
> Martin Pitt [2013-07-29 14:47 +0200]:
>> The change from libusb to libusbx in libgphoto2 now somehow turned on libusbx
>> debugging by default:
> 
> Tested debdiff (uploaded to Ubuntu).

Hello,

this change has been already incorporated in the latest upstream release
of libgphoto2. I suggest upgrading to version 2.5.2 which fixes the bug
automatically.

Regards,

Markus




signature.asc
Description: OpenPGP digital signature

Bug#718265: Acknowledgement (gvfs-backends: fails to mount secure WebDAV: SSL Handshake failed. server supports ECDH only.)

[Sebastian Birkl]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

and:
enabled protos:
ssl_protocols SSLv3 TLSv1.2;

On 07/29/2013 03:33 PM, Debian Bug Tracking System wrote:
> Thank you for filing a new Bug report with Debian.
> 
> This is an automatically generated reply to let you know your
> message has been received.
> 
> Your message is being forwarded to the package maintainers and
> other interested parties for their attention; they will reply in
> due course.
> 
> As you requested using X-Debbugs-CC, your message was also
> forwarded to siriu...@gmail.com (after having been given a Bug
> report number, if it did not have one).
> 
> Your message has been sent to the package maintainer(s): Debian
> GNOME Maintainers 
> 
> If you wish to submit further information on this problem, please 
> send it to 718...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish to
> report a problem with the Bug-tracking system.
> 

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

iQIcBAEBAgAGBQJR9nBeAAoJEAZCjU96LkierCUQAK2wxIzu3oZ0MLLfJnb6G2UP
GJe8n6ZNcQiHDRrQKXKlRxdvaYiLRbm8iKpIhLD4lEBiL4lQxhgSK5fjOEQJfsxM
5IPDh/bOOThOAwgGD8YUySY5jWNNrXDckYPertEanodNIMzJZNrnxeCcVLEBPMKi
PMsdXlzAPWNjnfB5R/2bdtVTOv+8Fo2JGEq3vvCEuCHalpXpsf8bYfk4RAoYYKjU
z3RdThKztR9n815oy5K++n8CcGS6Tbrai3+QDsWB7ooWmjs744Mfc/qNuVuUxSZg
JKGsK5W0IGweO4yk3sEK5cVae7sMu3+stX+rzUymh3rBjopRu6LZIXsqafB/Puxo
2L13LgeYfvVPv8xU7b+XOyPVBlCELQafIKf/jLiYsXdHZVucjKSnZxmKt6/ysG5A
i+3dzm21ofY/ct2fO+6zxR4tEjlvAgt3lvIFOjMDvXbkQ2Cb6w6hM+drHpEVKa0H
KE4cFyCgG2u7kYhKCDLbSbxP9jM50QZLGFzzHHjvqPjfiPEnoYqfo+R3sRM1x/73
Ya3uS1pM3IYhXdTeMzHxUH/oU+ntfXP6rzFOMRiomb+fj/OahIIr4QHrdxMQY3vT
7D4pg5Hlh8Apk9z9fHO2pMaxcJo1EXwZb714aajvirQ6ImVc3jeEdrna3XsyjnLd
4KIm8CBJrsH5FJZ04i9w
=h4Tc
-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#718266: libmodule-cpanfile-perl: invalid libcpan-meta-perl versioned dependency

[Niko Tyni]

Package: libmodule-cpanfile-perl
Version: 0.9036-1

This package build-depends and depends on

 libcpan-meta-perl (>= 2.12091) | perl (>= 5.17.1)

but libcpan-meta-perl Debian versions have had six digits the whole time:
even oldstable has 2.101670-1, which erroneously satisfies the above
constraint (due to differences in CPAN and Debian version ordering.)

 # dpkg --compare-versions 2.101670-1 gt 2.12091 && echo broken
 broken

I expect the related lintian overrides in debian/*.lintian-overrides
can and should be removed after this is fixed.  However, this part of
lintian has had recent changes so let me know if something went wrong
(see #708178 and #710919).
-- 
Niko Tyni   nt...@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#718258: libgphoto2-2: turns on libusbx debugging by default

[Martin Pitt]

Hey Markus,

Markus Koschany [2013-07-29 15:36 +0200]:
> this change has been already incorporated in the latest upstream release
> of libgphoto2. I suggest upgrading to version 2.5.2 which fixes the bug
> automatically.

Right, I know, but we don't yet have that in Debian (I guess since
there is no current maintainer). Hence I thought I'd send a patch
here, as this was introduced by the recent NMU.

Thanks,

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


signature.asc
Description: Digital signature

Bug#718267: ITP: xidle -- run a program on X inactivity

[Thorsten Glaser]

Package: wnpp
Severity: wishlist
Owner: Thorsten Glaser 

* Package name: xidle
  Version : CVS HEAD
  Upstream Author : Federico G. Schwindt 
* URL : https://www.mirbsd.org/man1/xidle
* License : 2-clause UCB
  Programming Lang: C
  Description : run a program on X inactivity

xidle uses the XScreenSaver(3) extension to receive inactivity events
when a timeout is specified, running a specific program after the
elapsed time. xidle also monitors the very corner of the given position
for pointer activity and runs a program if the pointer sits there for
more than the specified number of seconds. This behavior is always
present, whether -timeout is specified or not.

For example, I’ve got this in my ~/.xinitrc for use with evilwm:

# run xlock on moving to the upper-right corner
xidle -ne -program '/usr/bin/xlock -mode life' &


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

Bug#718268: svn-mailer silently failes

[Joseph Showalter]

Package: svn-mailer
Version: 1.0.8-12

Running on wheezy with a clean install, svn-mailer will not send emails.

No logs even with --debug included...




reportbug data:

Subject: svnmailer: none
Package: svnmailer
Version: 1.0.8-12
Severity: normal

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



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


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

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

Versions of packages svnmailer depends on: 
ii  python 2.7.3-4
ii  python-subversion  1.6.17dfsg-4+deb7u3
ii  python-support 1.0.15

svnmailer recommends no packages.

svnmailer suggests no packages.

-- no debconf information


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

Bug#718251: texlive-bin: FTBFS: makeinfo: not found

[Norbert Preining]

On Mo, 29 Jul 2013, Thorsten Glaser wrote:
> your package fails to build, even on release architectures,
> apparently due to missing Build-Depends(-Arch), possibly

Would be nice if you would have included a build error.

On Mo, 29 Jul 2013, Hilmar Preusse wrote:
> /«PKGBUILDDIR»/build-aux/missing: makeinfo: not found

Thanks. This is strange.
In former times makeinfo was not necessary. It seems that something
has changed. All the info files are built before, so why the build
process try to rebuild the info file is strange.

I will investigate.

> ..needs to be added to Build-Depends.

In emergency cases, but I want to know *why*, we *never* had to
use makeinfo till now.

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094



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

Bug#718260: 1:2.0.3-3 doesn't support grub-legacy

[Michal Hocko]

On Mon, Jul 29, 2013 at 03:01:39PM +0200, Michal Hocko wrote:
[...]
>   * Fixed kexec-load init script to parse newer grub.cfg files correctly
> (closes: Bug#714016)
> 
> Is it possible that both old and the new grub configurations would be
> supported?

Hmm, I was't able to find a patch which fixed the named bug but diff
between the two versions points to:
diff -uprN old/kexec-tools-2.0.3/debian/kexec-load.init.d 
new/kexec-tools-2.0.3/debian/kexec-load.init.d
--- old/kexec-tools-2.0.3/debian/kexec-load.init.d  2013-01-12 
23:04:53.0 +0100
+++ new/kexec-tools-2.0.3/debian/kexec-load.init.d  2013-07-25 
21:56:22.0 +0200
@@ -47,7 +47,7 @@ get_grub_kernel() {
 
# grub entries start with "menuentry" commands.  Get the line 
# numbers that surround the first entry
-   offsets=$(echo "$data" | grep -n ^menuentry | cut -d: -f1)
+   offsets=$(echo "$data" | grep -n '^[[:space:]]*menuentry[[:space:]]' | 
cut -d: -f1)
begin=$(echo "$offsets" | tail -n+$start_offset | head -n1)
end=$(echo "$offsets" | tail -n+$end_offset | head -n1)
 
And it doesn't seem to break grub-legacy support. So is the hard
dependency on the newer version really needed? Or was the dependency
change motivated by something else which wasn't mentioned in the
changelog?

Thanks!
-- 
Michal Hocko


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

Bug#718264: luatex builds with internal copies of poppler and libzzip (and pixman?)

[Norbert Preining]

On Mo, 29 Jul 2013, Matthias Klose wrote:
> luatex builds with internal copies of poppler and libzzip. build dependencies
> for poppler and pixman exist, but apparently are not used.  libzzip doesn't
> appear in the build dependencies at all.

Due to changes to the included libraries, or outdatedness of the 
Debian included libraries.

Poppler is a classical case where the versions in Debian usually
lack behind a lot, and in additional there are changes made to the
internal copies.

I will investigate and see if this has changed recently.

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094



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

Bug#710412: mod_access_compat apparently not working

[Jean-Michel Vourgère]

Control: tags -1 + patch

As of 2.4.6-1, authn_core is enabled by default, so your problem should now be
fixed in most cases. See bugs.debian.org/cgi-bin/bugreport.cgi?bug=717496

Nevertheless, the dependency should be properly registered:


--- a/debian/config-dir/mods-available/access_compat.load
+++ b/debian/config-dir/mods-available/access_compat.load
@@ -1 +1,2 @@
+# Depends: authn_core
 LoadModule access_compat_module /usr/lib/apache2/modules/mod_access_compat.so


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

Bug#718269: segfaults upon changing displays/resolution in XGrabServer

[Yaroslav Halchenko]

Package: xfce4-power-manager
Version: 1.2.0-2
Severity: important

It has been going on for a while but I do not remember exactly after which 
upgrade.

I am running awesome as a window manager for XFCE4.  Whenever I connect to 
external monitors, or disconnect from them I issue xrandr commands e.g.

xrandr --output $LVDS --off
xrandr --fbmm 520x326 \
   --output DP1 --same-as LVDS1 --mode 1920x1200 \
   --output VGA1 --mode 1920x1200 --rotate left --right-of DP1 \
   --output LVDS1 --off \
|| xrandr --output $LVDS --mode 1440x900

where LVDS is set to output of xrandr | awk '/LVDS/{print $1;}'

then some times (not always but often) xfce4-power-manager crashes with
the following traceback:

(gdb) bt
#0  XGrabServer (dpy=dpy@entry=0x0) at ../../src/GrServer.c:36
#1  0x7783ec08 in gtk_tray_icon_update_manager_window 
(icon=0x557f1020) at /tmp/buildd/gtk+2.0-2.24.20/gtk/gtktrayicon-x11.c:488
#2  0x7783ef0b in gtk_tray_icon_manager_filter (xevent=, 
event=, user_data=)
at /tmp/buildd/gtk+2.0-2.24.20/gtk/gtktrayicon-x11.c:398
#3  0x7712524d in gdk_event_apply_filters (filters=0x55813340, 
event=, xevent=)
at /tmp/buildd/gtk+2.0-2.24.20/gdk/x11/gdkevents-x11.c:356
#4  gdk_event_translate (display=display@entry=0x557ab020, 
event=event@entry=0x557d9c80, xevent=xevent@entry=0x7fffd890, 
return_exposes=return_exposes@entry=0) at 
/tmp/buildd/gtk+2.0-2.24.20/gdk/x11/gdkevents-x11.c:946
#5  0x77126a68 in _gdk_events_queue 
(display=display@entry=0x557ab020) at 
/tmp/buildd/gtk+2.0-2.24.20/gdk/x11/gdkevents-x11.c:2336
#6  0x77126aee in gdk_event_dispatch (source=, 
callback=, user_data=)
at /tmp/buildd/gtk+2.0-2.24.20/gdk/x11/gdkevents-x11.c:2397
#7  0x7633fea6 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x763401f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x763405fa in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x776b9257 in IA__gtk_main () at 
/tmp/buildd/gtk+2.0-2.24.20/gtk/gtkmain.c:1257
#11 0xbf7a in ?? ()
#12 0xc58b in main ()

here is a full one:

(gdb) bt full
#0  XGrabServer (dpy=dpy@entry=0x0) at ../../src/GrServer.c:36
No locals.
#1  0x7783ec08 in gtk_tray_icon_update_manager_window 
(icon=0x557f1020) at /tmp/buildd/gtk+2.0-2.24.20/gtk/gtktrayicon-x11.c:488
widget = 0x557f1020
screen = 0x0
display = 0x0
xdisplay = 0x0
#2  0x7783ef0b in gtk_tray_icon_manager_filter (xevent=, 
event=, user_data=)
at /tmp/buildd/gtk+2.0-2.24.20/gtk/gtktrayicon-x11.c:398
icon = 
xev = 
#3  0x7712524d in gdk_event_apply_filters (filters=0x55813340, 
event=, xevent=)
at /tmp/buildd/gtk+2.0-2.24.20/gdk/x11/gdkevents-x11.c:356
filter = 
tmp_list = 0x55813340
result = 
#4  gdk_event_translate (display=display@entry=0x557ab020, 
event=event@entry=0x557d9c80, xevent=xevent@entry=0x7fffd890, 
return_exposes=return_exposes@entry=0) at 
/tmp/buildd/gtk+2.0-2.24.20/gdk/x11/gdkevents-x11.c:946
result = 
window = 0x0
window_private = 0x0
filter_window = 
window_impl = 0x0
return_val = 0
screen = 0x0
screen_x11 = 0x0
toplevel = 0x0
display_x11 = 0x557ab020
xwindow = 
filter_xwindow = 
#5  0x77126a68 in _gdk_events_queue 
(display=display@entry=0x557ab020) at 
/tmp/buildd/gtk+2.0-2.24.20/gdk/x11/gdkevents-x11.c:2336
node = 0x557d4e40
event = 0x557d9c80
xevent = {type = 33, xany = {type = 33, serial = 117553, send_event = 
1, display = 0x5579c400, window = 134}, xkey = {type = 33, 
serial = 117553, send_event = 1, display = 0x5579c400, window = 
134, root = 451, subwindow = 32, time = 0, x = 455, y = 0, 
x_root = 12582916, y_root = 0, state = 0, keycode = 0, same_screen 
= 0}, xbutton = {type = 33, serial = 117553, send_event = 1, 
display = 0x5579c400, window = 134, root = 451, subwindow = 32, 
time = 0, x = 455, y = 0, x_root = 12582916, y_root = 0, state = 0, 
button = 0, same_screen = 0}, xmotion = {type = 33, serial = 
117553, send_event = 1, display = 0x5579c400, window = 134, 
root = 451, subwindow = 32, time = 0, x = 455, y = 0, x_root = 
12582916, y_root = 0, state = 0, is_hint = 0 '\000', same_screen = 0}, 
  xcrossing = {type = 33, serial = 117553, send_event = 1, display = 
0x5579c400, window = 134, root = 451, subwindow = 32, time = 0, 
x = 455, y = 0, x_root = 12582916, y_root = 0, mode = 0, detail = 
0, same_screen = 0, focus = 0, state = 0}, xfocus = {type = 33, 
serial = 117553, send_event = 1, display = 0x5579c400, window = 
134, mode = 451, detail = 0}, xexpose = {type = 33, 
seria

Bug#718270: linux: FTBFS on hppa: module mbcache.ko is in more than one package

[John David Anglin]

Source: linux
Version: 3.10.3-1
Severity: normal

Build ends here with error:

install -m 644 
debian/linux-image-3.10-1-parisc/lib/modules/3.10-1-parisc/modules.builtin 
debian/linux-image-3.10-1-parisc/lib/modules/3.10-1-parisc/modules.order 
debian/kernel-image-3.10-1-parisc-di/lib/modules/3.10-1-parisc/
install -D -m 644 
debian/linux-image-3.10-1-parisc/boot/System.map-3.10-1-parisc 
debian/kernel-image-3.10-1-parisc-di/boot/System.map-3.10-1-parisc
kernel-wedge copy-modules 3.10-1 parisc 3.10-1-parisc
kernel-wedge find-dups 3.10-1-parisc
some modules are in more than one package
debian/ext4-modules-3.10-1-parisc-di 
lib/modules/3.10-1-parisc/kernel/fs/mbcache.ko
debian/ext3-modules-3.10-1-parisc-di 
lib/modules/3.10-1-parisc/kernel/fs/mbcache.ko
command exited with status 1
make[2]: *** [install-udeb_hppa] Error 2
make[2]: Leaving directory `/mnt/debian/linux/linux-3.10.3'
make[1]: *** [binary-arch_hppa] Error 2
make[1]: Leaving directory `/mnt/debian/linux/linux-3.10.3'
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
Build command 'cd linux-3.10.3 && dpkg-buildpackage -b -uc' failed.
Fetched 76.5 MB in 41s (1,838 kB/s)


-- System Information:
Debian Release: 7.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: hppa (parisc64)

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


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

Bug#717900: libsqlite3-0: Please increase SQLITE_MAX_VARIABLE_NUMBER to something bigger like 500000

[GCS]

Hi Raphaël,

On Fri, Jul 26, 2013 at 11:13 AM, Raphaël Hertzog  wrote:
> http://www.sqlite.org/limits.html#max_variable_number
>
> Upstream document this compile-time limit. But 999 is ridiculously low
> by today's standard of memory size. This limit can be increased to
> something bigger.
[...]
> In my use case, I have queries that embed all the Debian package names so
> I need several dozens of thousands of variables. This is for a query that
> Django generates and it's similar to something like this:
> SELECT * FROM packageinfos WHERE name in (?,?,?,…).
 What would be an acceptable value for your use case? I don't want to
just shot a number, but choose one that sounds reasonable.

Regards,
Laszlo/GCS


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

Bug#717900: libsqlite3-0: Please increase SQLITE_MAX_VARIABLE_NUMBER to something bigger like 500000

[Raphael Hertzog]

Hi,

On Mon, 29 Jul 2013, László Böszörményi (GCS) wrote:
> On Fri, Jul 26, 2013 at 11:13 AM, Raphaël Hertzog  wrote:
> > http://www.sqlite.org/limits.html#max_variable_number
> >
> > Upstream document this compile-time limit. But 999 is ridiculously low
> > by today's standard of memory size. This limit can be increased to
> > something bigger.
> [...]
> > In my use case, I have queries that embed all the Debian package names so
> > I need several dozens of thousands of variables. This is for a query that
> > Django generates and it's similar to something like this:
> > SELECT * FROM packageinfos WHERE name in (?,?,?,…).
>  What would be an acceptable value for your use case? I don't want to
> just shot a number, but choose one that sounds reasonable.

Given that we are at 4 unique binary package names and that we want to
accomodate for some future growth, 10 would be enough for a while for
me.

But you might want to estimate "reasonable" based on the memory that those
arguments consumes and the average amount of memory that you get on modern
machines.

I bet that you will get a bigger number and that Apple's choice of 50
is not unreasonable.

Cheers,
-- 
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#718266: libmodule-cpanfile-perl: invalid libcpan-meta-perl versioned dependency

[gregor herrmann]

On Mon, 29 Jul 2013 16:46:47 +0300, Niko Tyni wrote:

> This package build-depends and depends on
> 
>  libcpan-meta-perl (>= 2.12091) | perl (>= 5.17.1)
> 
> but libcpan-meta-perl Debian versions have had six digits the whole time:

D'oh, what a silly mistake.
Sorry, and thanks for pointing it out!

> I expect the related lintian overrides in debian/*.lintian-overrides
> can and should be removed after this is fixed.  However, this part of
> lintian has had recent changes so let me know if something went wrong
> (see #708178 and #710919).

Works fine without them now.


Cheers,
gregor

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


signature.asc
Description: Digital signature

Bug#718266: Pending fixes for bugs in the libmodule-cpanfile-perl package

[pkg-perl-maintainers]

tag 718266 + pending
thanks

Some bugs in the libmodule-cpanfile-perl package are closed in
revision 9bba154d86eb8061cd5aa6878ae5e731189ea6a9 in branch 'master'
by gregor herrmann

The full diff can be seen at
http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libmodule-cpanfile-perl.git;a=commitdiff;h=9bba154

Commit message:

Fix version of libcpan-meta-perl (build) dependency

and drop bogus lintian overrides.

Thanks: Niko Tyni for catching this mistake.
Closes: #718266


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

Bug#668596: Fwd: Re: iRODS in Debian

[Alastair McKinstry]

To track:


 Original Message 
Subject:Re: iRODS in Debian
Date:   Wed, 27 Jun 2012 08:02:20 -0400
From:   Terrell Russell 
To: Alastair McKinstry 



Ah, we don't yet have a source package as we are still in the process of
developing licensing decisions.  The plan is to be fully open source,
but for now, we have only beta released the binary DEB files for E-iRODS.

Terrell



On 6/27/12 5:27 AM, Alastair McKinstry wrote:
> On 2012-06-27 03:45, Terrell Russell wrote:
>> Alastair,
>>
>> Regarding the wnpp ITP bug for iRODS here:
>>   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668596
>>
>> We at RENCI have been working on packaging iRODS/E-iRODS for the last
>> few months.  We released our second beta this week.
>>
>>   http://e-irods.org/release/e-irods-beta-2-is-released/
>>
>>   http://e-irods.org/about/
>>
>> We are not yet lintian clean, but we are close and hope to start the
>> eventual process of getting our software into the Debian upstream.
> Is it possible to get the source package? I can only see the .deb files
> in the ftp site.
> 
> best regards
> Alastair
> 
>> Since you are named as the owner of this intent to package bug, I wanted
>> to let you know of our progress.  We are working closely with the DICE
>> group, original authors and maintainers of the iRODS community code base.
>>
>> Thank you,
>>
>> Terrell
> 
> 

Bug#718271: FTBFS: could not find kernel image at …/kernel-wedge/…/install-files line 101, line 2.

[Thorsten Glaser]

Source: linux
Version: 3.10.3-1
Severity: important
Justification: fails to build from source (but built successfully in the past)

Hi,

the latest Linux kernel source package fails to build:

[…]
make[2]: Entering directory `/tmp/buildd/linux-3.10.3'
dh_testdir
dh_prep
kernel-wedge install-files 3.10-1
could not find kernel image at /usr/share/kernel-wedge/commands/install-files 
line 101,  line 2.
make[2]: *** [install-udeb_m68k] Error 2
make[2]: Leaving directory `/tmp/buildd/linux-3.10.3'
make[1]: *** [binary-arch_m68k] Error 2
[…]

Full log attached.

-- System Information:
Debian Release: 7.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: m68k

Kernel: Linux 3.2.0-4-atari
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/mksh-static


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

Bug#716935: What i have done

[Holger Levsen]

Hi Bernhard,

On Freitag, 26. Juli 2013, Bernhard wrote:
> What i have done:
> 1.
> 2.
> 3.
[...]
> With the images from wheezy, installation from USB stick is successfully.
> With the current daily images, installation fails.
[...]
> Possibly, we only have to wait for the new kernel.
> I'll test the installation, after new kernel is available in sid.

thanks for the update and please do keep us posted! 


cheers,
Holger


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

Bug#718272: upstream does not support stable releases (block migration to testing)

[Scott Howard]

Source: bitcoin
Severity: serious

The bitcoin network requires on strict adherence to consensus between nodes.
Small changes to underlying libraries, even justified security changes,
threaten to break consensus and could possible cause accidental forks.

For example, it is possible for bug fix in libleveldb to cause a fork in the
network if existing nodes expect buggy behaviour.

Therefore, bitcoin upstream developers have strongly encouraged downstream
packagers to use the exact version of libleveldb included with their source
code.  However, upstream does not backport or support previously released
versions of bitcoind/bitcoin-qt.

For example: if we release Debian Jessie with version 0.8 of bitcoin, and a
security bug is found in that version and fixed upstream, the fix may be based
on top of version 0.10 and unable to be ported to 0.8. Upstream will, in that
case, release version 0.10 and not backport the fix to 0.8. This is especially
tricky now that Debian is using the bitcoin packaged version of leveldb.

Because of the sensitivity of this situation (lots of money can be lost), I
believe we should block migration to testing until either upstream supports
stable releases or we have a volunteer that works closely enough with upstream
code (an upstream developer) that is will to backport security and network-
related fixes.


There has been some work on multibit and electrum packages in Debian, these may
be better choices for wallets. If we keep bitcoin in unstable, we'll be able to
update as needed and users will understand that these packages are not stable
and will need to be updated often.



-- System Information:
Debian Release: wheezy/sid
  APT prefers raring-updates
  APT policy: (500, 'raring-updates'), (500, 'raring-security'), (500, 
'raring-proposed'), (500, 'raring'), (100, 'raring-backports')
Architecture: i386 (i686)

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


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

Bug#718273: ITP: go-fuse -- Native Go bindings for the FUSE kernel module

[Philipp Kern]

Package: wnpp
Severity: wishlist
Owner: Philipp Kern 

* Package name : xidle
  Version  : git master
  Upstream Authors : Han-Wen Nienhuys 
 Ivan Krasin 
* URL  : https://github.com/hanwen/go-fuse
* License  : New BSD License
  Programming Lang : Go
  Description  : Native Go bindings for the FUSE kernel module

go-fuse provides FUSE bindings written in native Go. It does not rely
on libfuse. Other Go programs can use this library to implement custom
userspace 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#718271: linux: FTBFS: could not find kernel image at …/kernel-wedge/…/install-files line 101, line 2.

[Thorsten Glaser]

Sorry, of course I forgot the attachment…

bye,
//mirabilos
-- 
«MyISAM tables -will- get corrupted eventually. This is a fact of life. »
“mysql is about as much database as ms access” – “MSSQL at least descends
from a database” “it's a rebranded SyBase” “MySQL however was born from a
flatfile and went downhill from there” – “at least jetDB doesn’t claim to
be a database”  (#nosec)‣‣‣ Please let MySQL and MariaDB finally die!

linux_3.10.3-1_m68k.build.gz
Description: Binary data

Bug#716748: gnome-shell: black background in overview (and desktop)

[Eugenio M. Vigo]

Dear Mantainer,
it appears that the problem has been solved.

Thanks!

Bug#718274: fife: FTBFS: virtual memory exhausted: Cannot allocate memory

[Thorsten Glaser]

Source: fife
Version: 0.3.4-3
Severity: important
Justification: FTBFS on non-release arch

Hi,

your package fails to build with:

[…]
g++ -o build/engine/release/swigwrappers/python/py_fife_wrap.os -c 
-DPNG_SKIP_SETJMP_CHECK -O2 -Wall -Wno-unused -fPIC -DTIXML_USE_STL 
-D_GNU_SOURCE=1 -D_REENTRANT -DUSE_SYSTEM_TINY_XML -DNDEBUG -DHAVE_OPENGL 
-DHAVE_ZIP -DLOG_ENABLED -I/opt/include -I/usr/include/vorbis 
-I/usr/include/SDL -I/usr/include/python2.7 -Iext/install/include -Iengine/core 
build/engine/release/swigwrappers/python/fife_wrap.cc
build/engine/release/swigwrappers/python/fife_wrap.cc: In function 'void 
handleDirectorException()':
build/engine/release/swigwrappers/python/fife_wrap.cc:6606:41: warning: 
deprecated conversion from string co
nstant to 'char*' [-Wwrite-strings]
   PySys_SetObject("last_type", exception);
 ^
build/engine/release/swigwrappers/python/fife_wrap.cc:6607:38: warning: 
deprecated conversion from string co
nstant to 'char*' [-Wwrite-strings]
   PySys_SetObject("last_value", value);
  ^
build/engine/release/swigwrappers/python/fife_wrap.cc:6608:46: warning: 
deprecated conversion from string co
nstant to 'char*' [-Wwrite-strings]
   PySys_SetObject("last_traceback", traceback);
  ^
virtual memory exhausted: Cannot allocate memory
scons: *** [build/engine/release/swigwrappers/python/py_fife_wrap.os] Error 1
[…]

Sadly, we’re somewhat at the memory maximum (782 MiB RAM plus
several GiB of swap) there.

http://buildd.debian-ports.org/status/fetch.php?pkg=fife&arch=m68k&ver=0.3.4-3&stamp=1375109074

bye,
//mirabilos
-- 
15:41⎜ Somebody write a testsuite for helloworld :-)


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

Bug#717473: [PATCH] adm64_edac: Fix single-channel setups

[Ben Hutchings]

There's a typo in the subject line. :-)

Ben.

-- 
Ben Hutchings
The two most common things in the universe are hydrogen and stupidity.


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

Bug#709422: Depending on binary that is not available on boot (liblzo2.so.2)

[Dmitrijs Ledkovs]

Both btrfs and fsck.btrfs are now unconditionally included in the
initramfs, and thus should be available on your system to boot & mount
'/' and '/usr'. Together with the ongoing work to mount and fsck '/'
and '/usr' from initramfs, you should have less problems booting going
into the future. It is unfortunate that lzo2 is not installed into
/lib/, I will request the maintainer of that package to do so, by
reassigning the bug there.

Regards,

Dmitrijs.


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

Bug#708381: [lintian] Patch

[bastien ROUCARIES]

Package: lintian
Version: 2.5.13
control: tags -1 + patch
From 933ff11c5766d08e3d1a1eb65f87a37929d06c4b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bastien=20ROUCARI=C3=88S?= 
Date: Mon, 29 Jul 2013 16:58:56 +0200
Subject: [PATCH] Fix false-negative brace-expansion-in-debhelper-config-file
 for "{, foo}"

Lintian does not trigger for:
for
patterns like this:

{,foo}

or this:

{foo,}
---
 checks/debhelper.pm|2 +-
 .../debian/debian/control.in   |   84 
 .../debian/debhelper-brace-problem-1.install   |1 +
 .../debian/debhelper-brace-problem-2.install   |1 +
 .../debian/debhelper-brace-problem-3.install   |1 +
 .../debian/debhelper-brace-problem-4.install   |1 +
 .../debian/debhelper-brace-problem-5.install   |1 +
 .../debian/debhelper-brace-problem-6.install   |1 +
 .../debian/debhelper-brace-problem-good.install|2 +
 .../debian/debian/install  |1 -
 10 files changed, 93 insertions(+), 2 deletions(-)
 create mode 100644 t/tests/debhelper-brace-expansion/debian/debian/control.in
 create mode 100644 t/tests/debhelper-brace-expansion/debian/debian/debhelper-brace-problem-1.install
 create mode 100644 t/tests/debhelper-brace-expansion/debian/debian/debhelper-brace-problem-2.install
 create mode 100644 t/tests/debhelper-brace-expansion/debian/debian/debhelper-brace-problem-3.install
 create mode 100644 t/tests/debhelper-brace-expansion/debian/debian/debhelper-brace-problem-4.install
 create mode 100644 t/tests/debhelper-brace-expansion/debian/debian/debhelper-brace-problem-5.install
 create mode 100644 t/tests/debhelper-brace-expansion/debian/debian/debhelper-brace-problem-6.install
 create mode 100644 t/tests/debhelper-brace-expansion/debian/debian/debhelper-brace-problem-good.install
 delete mode 100644 t/tests/debhelper-brace-expansion/debian/debian/install

diff --git a/checks/debhelper.pm b/checks/debhelper.pm
index 7232497..8592a56 100644
--- a/checks/debhelper.pm
+++ b/checks/debhelper.pm
@@ -363,7 +363,7 @@ for my $file (sort(readdir($dirfd))) {
 while (<$fd>) {
 next if /^\s*$/;
 next if (/^\#/ and $level >= 5);
-if (m/(?= 9)
+
+Package: {$srcpkg}
+Architecture: {$architecture}
+Depends: $\{misc:Depends\}
+Description: {$description}
+ This is a test package designed to exercise some feature or tag of
+ Lintian.  It is part of the Lintian test suite and may do very odd
+ things.  It should not be installed like a regular package.  It may
+ be an empty package.
+
+Package: debhelper-brace-problem-1
+Architecture: {$architecture}
+Depends: $\{misc:Depends\}
+Description: {$description} another extra string
+ This is a test package designed to exercise some feature or tag of
+ Lintian.  It is part of the Lintian test suite and may do very odd
+ things.  It should not be installed like a regular package. Extra
+ string.  It may be an empty package.
+ 
+Package: debhelper-brace-problem-2
+Architecture: {$architecture}
+Depends: $\{misc:Depends\}
+Description: {$description} another extra string three
+ This is a test package designed to exercise some feature or tag of
+ Lintian.  It is part of the Lintian test suite and may do very odd
+ things.  It should not be installed like a regular package. Extra
+ string three.  It may be an empty package.
+ 
+Package: debhelper-brace-problem-3
+Architecture: {$architecture}
+Depends: $\{misc:Depends\}
+Description: {$description} three test case
+ This is a test package designed to exercise some feature or tag of
+ Lintian.  It is part of the Lintian test suite and may do very odd
+ things.  It should not be installed like a regular package. Extra
+ string three test case. It may be an empty package. 
+ 
+Package: debhelper-brace-problem-4
+Architecture: {$architecture}
+Depends: $\{misc:Depends\}
+Description: {$description} fourth test case
+ This is a test package designed to exercise some feature or tag of
+ Lintian.  It is part of the Lintian test suite and may do very odd
+ things.  It should not be installed like a regular package. Extra
+ string fourth test case. It may be an empty package.
+ 
+Package: debhelper-brace-problem-5
+Architecture: {$architecture}
+Depends: $\{misc:Depends\}
+Description: {$description} fifth test case
+ This is a test package designed to exercise some feature or tag of
+ Lintian.  It is part of the Lintian test suite and may do very odd
+ things.  It should not be installed like a regular package. Extra
+ string fifth test case. It may be an empty package.
+
+Package: debhelper-brace-problem-6
+Architecture: {$architecture}
+Depends: $\{misc:Depends\}
+Description: {$description} sixth test case
+ This is a test package designed to exercise some feature or tag of
+ Lintian.  It is part of the Lintian test suite and may do very odd
+ things.  It should not be installed like a regular package. Extra
+ string sixth test

Bug#718260: 1:2.0.3-3 doesn't support grub-legacy

[Khalid Aziz]

On Mon, 2013-07-29 at 15:57 +0200, Michal Hocko wrote:
> On Mon, Jul 29, 2013 at 03:01:39PM +0200, Michal Hocko wrote:
> [...]
> And it doesn't seem to break grub-legacy support. So is the hard
> dependency on the newer version really needed? Or was the dependency
> change motivated by something else which wasn't mentioned in the
> changelog?
> 
> Thanks!

I agree, that dependency is incorrect. I have uploaded a newer version
of the package to UploadQueue and am waiting for it to be processed.

--
Khalid


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

Bug#718270: linux: FTBFS on hppa: module mbcache.ko is in more than one package

[Ben Hutchings]

Control: tag -1 patch

On Mon, 2013-07-29 at 10:03 -0400, John David Anglin wrote:
> Source: linux
> Version: 3.10.3-1
> Severity: normal
> 
> Build ends here with error:
> 
> install -m 644 
> debian/linux-image-3.10-1-parisc/lib/modules/3.10-1-parisc/modules.builtin 
> debian/linux-image-3.10-1-parisc/lib/modules/3.10-1-parisc/modules.order 
> debian/kernel-image-3.10-1-parisc-di/lib/modules/3.10-1-parisc/
> install -D -m 644 
> debian/linux-image-3.10-1-parisc/boot/System.map-3.10-1-parisc 
> debian/kernel-image-3.10-1-parisc-di/boot/System.map-3.10-1-parisc
> kernel-wedge copy-modules 3.10-1 parisc 3.10-1-parisc
> kernel-wedge find-dups 3.10-1-parisc
> some modules are in more than one package
> debian/ext4-modules-3.10-1-parisc-di 
> lib/modules/3.10-1-parisc/kernel/fs/mbcache.ko
> debian/ext3-modules-3.10-1-parisc-di 
> lib/modules/3.10-1-parisc/kernel/fs/mbcache.ko
> command exited with status 1
> make[2]: *** [install-udeb_hppa] Error 2
> make[2]: Leaving directory `/mnt/debian/linux/linux-3.10.3'
> make[1]: *** [binary-arch_hppa] Error 2
> make[1]: Leaving directory `/mnt/debian/linux/linux-3.10.3'
> make: *** [binary-arch] Error 2
> dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
> 2
> Build command 'cd linux-3.10.3 && dpkg-buildpackage -b -uc' failed.
> Fetched 76.5 MB in 41s (1,838 kB/s)

Does this patch (applied with -p0) fix it?

--- debian/installer/hppa/modules/hppa/core-modules (revision 0)
+++ debian/installer/hppa/modules/hppa/core-modules (working copy)
@@ -0,0 +1 @@
+#include 
--- END ---

Ben.

-- 
Ben Hutchings
The two most common things in the universe are hydrogen and stupidity.


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