Bug#672487: reportbug tells UnicodeDecodeError: codec can't decode byte 0xd0 'ascii'

[Sebastian Podjasek]

Package: reportbug
Version: 6.4.4
Followup-For: Bug #672487

I was trying to report bug about libvirt-bin and ended with following python 
error:
---
[...]
Maintainer for libvirt-bin is 'Debian Libvirt Maintainers 
'.
Looking up dependencies of libvirt-bin...
Getting changed configuration files...
Traceback (most recent call last):
  File "/usr/bin/reportbug", line 2206, in 
main()
  File "/usr/bin/reportbug", line 1080, in main
return iface.user_interface()
  File "/usr/bin/reportbug", line 1819, in user_interface
conftext = conftext + u'%s %s\n' % (f, confinfo[f])
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 20: 
ordinal not in range(128)
---


Regards,
Sebastian


-- Package-specific info:
** Environment settings:
INTERFACE="text"

** /home/seba/.reportbugrc:
reportbug_version "6.3"
mode novice
ui text
realname "Sebastian Podjasek"
email "sebast...@podjasek.pl"
smtphost "*"
smtpuser "*"
smtptls

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

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

Versions of packages reportbug depends on:
ii  apt   0.8.15.9
ii  python2.7.2-9
ii  python-reportbug  6.4.4

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
pn  debconf-utils  
pn  debsums
pn  dlocate
pn  emacs22-bin-common | emacs23-bin-common
ii  exim4  4.77-1
ii  exim4-daemon-light [mail-transport-agent]  4.77-1
ii  file   5.09-2
ii  gnupg  1.4.11-3
pn  python-gtk2
pn  python-gtkspell
pn  python-urwid   
pn  python-vte 
pn  xdg-utils  

Versions of packages python-reportbug depends on:
ii  apt   0.8.15.9
ii  python2.7.2-9
ii  python-debian 0.1.21
ii  python-debianbts  1.10
ii  python-support1.0.14

python-reportbug 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#101072: latest xalan doesn't like xbel DTD

[Mathieu Malaterre]

On Tue, Jul 30, 2013 at 1:09 AM, Brian May
 wrote:
> On 30 July 2013 06:39, Mathieu Malaterre  wrote:
>>
>> where I can I get this 'unix.xml' file ? Where can I get this
>> 'xbel.dtd' ? I cannot reproduce it here.
>
>
> I would assume that they use to come with the xbel package, version 0.6.5-2,
> as per the bug report, which was opened Sat, 16 Jun 2001 17:19:19 +1000.

The actual issue is that xbel is neither available from debian.org nor
from snapshot.d.o...


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

Bug#718218: coquelicot: fails to start due to "invalid byte sequence" error in fast_gettext

[Jérémy Bobbio]

Johannes Schauer:
> Though when doing so in above statement, the problem persists. What does
> work though is to insert the following lines right into
> /usr/bin/coquelicot:
> 
> 
>   Encoding.default_external = Encoding::UTF_8
>   Encoding.default_internal = Encoding::UTF_8
> 
> Since I have no clue about ruby I do not know how what the proper fix
> would be. In case this is a ruby-fast-gettext problem, please re-assign
> and excuse my ignorance. :)

I am glad you have found a work around for the time being. I'll
investigate further — probably not before a week or two, though.

-- 
Jérémy Bobbio.''`. 
lu...@debian.org: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature

Bug#672487: reportbug tells UnicodeDecodeError: codec can't decode byte 0xd0 'ascii'

[Sebastian Podjasek]

> Package: reportbug
> Version: 6.4.4
> Followup-For: Bug #672487
>
> Kernel: Linux 3.1.0-1-amd64 (SMP w/24 CPU cores)
> Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>

I've upgraded python to version 2.7.5 - no change, but running reportbug
with LANG=C helps, no exception was thrown and I was able to complete my
bug report on libvirt-bin


-- 
Sebastian Podjasek


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

Bug#718021: [Resolvconf-devel] Bug#718021: dns-nameservers vs dns-nameserver

[Thomas Hood]

On Tue, Jul 30, 2013 at 12:16 AM, Christoph Anton Mitterer <
cales...@scientia.net> wrote:

> it's just that we're probably better off with
> suggesting people only one variant... so we can phase out the other on
> the long term scale...
>


I'll make "dns-nameserver" the canonical one and "dns-nameservers" an
explicitly supported alternative. The former is more consistent with the
semantics of resolv.conf; the latter is too established to eliminate now.

The other reason for recommending "dns-nameserver" is that it takes exactly
one argument. This leaves room to extend the semantics of this option in
the future. E.g., it might be useful to be able to say

dns-nameserver 192.168.1.254 some.domain
dns-nameserver 12.34.56.78 another.one
dns-nameserver 8.8.8.8

meaning that *.some.domain queries should be routed to 192.168.1.254;
*.another.one to 12.34.56.78 and the rest to 8.8.8.8. Dnsmasq supports this
sort of query routing.


Perhaps you should also ask the ifupdown people what they're going to
> plan with their stanzas at the long term.
> Especially for the "address" keyword a version that supports more
> addresses per line would be reasonable... and I guess the concepts
> should be kept more or less sync on all the /e/n/interfaces keywords.
>


Accepting multiple instances of an option in a stanza is a feature that was
recently added to ifupdown. I presume that it will continue to be a
supported feature in the future. :)
-- 
Thomas

Bug#718319: [Pkg-fonts-devel] Bug#718319: fonts-linuxlibertine: Vcs-Svn link broken

[Christian PERRIER]

Quoting Timo Juhani Lindfors (timo.lindf...@iki.fi):
> Package: fonts-linuxlibertine
> Version: 5.3.0-1
> Severity: normal
> 
> The package has
> 
> Vcs-Browser: 
> http://anonscm.debian.org/viewvc/pkg-fonts/packages/linux-libertine/trunk/
> 
> but that gives me 404. Right link should be
> 
> Vcs-Browser: 
> http://anonscm.debian.org/viewvc/pkg-fonts/packages/fonts-linuxlibertine/trunk/

Indeed, the package moved to git but I forgot updating the VCS-*
fields. I'll do so in the next upload. Thanks for pointing this.




signature.asc
Description: Digital signature

Bug#707201: Unable to initialize /machine cgroup: Invalid argument

[Sebastian Podjasek]

Package: libvirt-bin
Version: 1.1.0-4
Followup-For: Bug #707201

I'm also affected with this bug. Temporarily umount /sys/fs/cgroup helps to 
start libvirt/quemu containers, but I need to mount it back to start LXC 
later...
LXC container are not handled by libvirt-bin.


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

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

Versions of packages libvirt-bin depends on:
ii  adduser  3.113
ii  gettext-base 0.18.1.1-5
ii  init-system-helpers  1.7
ii  libaudit01:1.7.18-1.1
ii  libavahi-client3 0.6.30-6
ii  libavahi-common3 0.6.30-6
ii  libblkid12.19.1-5
ii  libc62.17-5
ii  libcap-ng0   0.6.6-1
ii  libdbus-1-3  1.4.16-1
ii  libdevmapper1.02.1   2:1.02.67-1
ii  libgcrypt11  1.5.3-1
ii  libgnutls26  2.12.23-5
ii  libnetcf11:0.2.3-3
ii  libnl-3-200  3.2.21-1
ii  libnl-route-3-2003.2.21-1
ii  libnuma1 2.0.8~rc2-1
ii  libparted0debian12.3-8
ii  libpcap0.8   1.1.1-10
ii  libpciaccess00.12.902-1
ii  libreadline6 6.2-7
ii  libsasl2-2   2.1.25.dfsg1-2
ii  libudev0 172-1
ii  libvirt0 1.1.0-4
ii  libxenstore3.0   4.1.2-2
ii  libxml2  2.7.8.dfsg-5
ii  libyajl2 2.0.4-4
ii  logrotate3.7.8-6

Versions of packages libvirt-bin recommends:
ii  bridge-utils1.5-6
ii  dmidecode   2.11-4
ii  dnsmasq-base2.59-4
ii  ebtables2.0.9.2-2
ii  gawk1:3.1.8+dfsg-0.1
ii  iproute 20110629-1
ii  iptables1.4.12-1
ii  libxml2-utils   2.7.8.dfsg-5
ii  netcat-openbsd  1.89-4
ii  parted  2.3-8
ii  pm-utils1.4.1-11
ii  qemu-kvm1.5.0+dfsg-5
ii  qemu-system-x86 [qemu-kvm]  1.5.0+dfsg-5

Versions of packages libvirt-bin suggests:
pn  auditd   
pn  policykit-1  
pn  radvd
pn  systemtap

-- Configuration Files:
/etc/libvirt/qemu.conf [Errno 13] Permission denied: u'/etc/libvirt/qemu.conf'

-- 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]

Hi,

On Mon, Jul 29, 2013 at 11:39:37AM +0200, Rene Engelhard wrote:
> > 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.)

And a s/rm/rm -f/. Done in -3 which is just uploading.

Regards,
 
Rene


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

Bug#718295: /usr/bin/dpkg-deb: dpkg-deb -Zgzip -z0 produces invalid debian packages

[Guillem Jover]

On Tue, 2013-07-30 at 08:43:45 +0200, Raphael Hertzog wrote:
> On Mon, 29 Jul 2013, Guillem Jover wrote:
> > > The linux maintainers chose to pass -Zgzip -z0 to dpkg-deb to retain
> > > backwards compatibility.
> > 
> > To retain compatibility they should either not have specified -z at all
> > or used -z9. dpkg-deb(1) is pretty clear that -z0 for gzip is equivalent
> > to no compression.
> 
> They want no compression but they want to work with old dpkg too:

I noticed yesterday when checking the changelog. There's no way to
get that with gzip anyway...

> # We don't want to recompress, but -Znone is not compatible with older
> # tools and is currently rejected by dak.  -Zgzip -z0 has almost the
> # same effect.
> 
> > At this point I'm tempted to just deprecate -Zgzip -z0. I'll fix this
> > in any way for 1.17.2.
> 
> Suggested patch (untested):
> 
> $ git diff
> diff --git a/lib/dpkg/compress.c b/lib/dpkg/compress.c
> index 12c694c..63df7af 100644
> --- a/lib/dpkg/compress.c
> +++ b/lib/dpkg/compress.c
> @@ -771,6 +771,8 @@ compressor_get_strategy(const char *name)
>  bool
>  compressor_check_params(struct compress_params *params, struct dpkg_error 
> *err)
>  {
> +   compressor_fixup_params(params);
> +
> if (params->strategy == compressor_strategy_none)
> return true;
>  
> The fixup function for gzip already switches the compression_type to none, but
> it's only called in compress_filter() which happens in a sub-process. Calling
> it when we validate the parameters seems a good way to have it happen in the
> main process as well and avoid this problem.

I got a tested and working patch yesterday, fixing this, as I said I
was going to do. Didn't push because I was pondering about the
implications and how to best fix this if at all, for example by just
deprecating the option or simply fixing the docs. And this would not
help the Linux kernel maintainers anyway.

Guillem


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

Bug#549431: pidgin-otr: Logging should be disabled by default

[intrigeri]

Hi Thibaut,

I've seen you've tagged this bug `upstream' a while ago,
but I see no mention of this bug being forwarded to them.

Was it?

(FWIW, I agree this is a wishlist.)

Cheers,
--
  intrigeri
  | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc


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

Bug#718287: wolf4sdl: Potentially non-free resource

[Fabian Greffrath]

Am Montag, den 29.07.2013, 13:43 -0400 schrieb GhostlyDeath: 
> Hello, the following file ./debian/pixmaps/wolf4sdl.xpm contains a
> face shot of the
> main character of this game. Which is extracted from the game itself
> on the status
> bar.

You are probably right. Do you have any other idea for an icon? I
already digged through the FreeDoom resources but could not find
anything that would fit IMHO.

- Fabian


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

Bug#711071: bitlbee: please port to libotr5-dev

[intrigeri]

Hi,

Wilmer van der Gaast wrote (06 Jul 2013 16:05:27 GMT) :
> Just had a response from him on Twitter now, might get a fix over the
> next weeks.

Any news on this front?

(I'd like to stress out, since it may not be obvious to everyone
involved here, that libotr4 and later prevents protocol downgrade
attacks (while libotr2 doesn't). See this paper for details:
http://www.jbonneau.com/OTR_analysis.pdf)

Cheers,
--
  intrigeri
  | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc


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

Bug#711072: Building mcabber with libotr Version 4?

[intrigeri]

Hi Franziska,

Mikael Berthe wrote (13 Jul 2013 10:59:08 GMT) :
> There is a patch from Myhailo Danylenko in our issue tracker which has
> been reported to work, so I'll merge it.  If you can confirm it works
> with Debian packages (I haven't tried yet) it would be very helpful.

> https://bitbucket.org/McKael/mcabber-crew/issue/102/libotr-400-support

Ping?

Cheers,
--
  intrigeri
  | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc


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

Bug#718320: iceowl-extension: Problematic calendar file freezes icedove

[Antoon Pardon]

Package: iceowl-extension
Version: 10.0.12-1
Severity: important

Dear Maintainer,

I was taking a break while composing a message and when I returned
icedove was frozen. I terminated the session and from then on
icedove would freeze on startup.

I put aside the .icedove directory and started a new. Everything
worked until I included a specific calender file as netwerk
calendar, then icedove froze again.

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

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

Versions of packages iceowl-extension depends on:
ii  calendar-timezones  10.0.12-1
ii  icedove 10.0.12-1
ii  libc6   2.17-7
ii  libgcc1 1:4.8.1-2
ii  libnspr42:4.10-1
ii  libnspr4-0d 2:4.10-1
ii  libstdc++6  4.8.1-2

Versions of packages iceowl-extension recommends:
ii  calendar-google-provider  10.0.12-1

Versions of packages iceowl-extension suggests:
ii  fonts-lyx  2.0.6-1

-- no debconf information


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

Bug#718321: apache2-maintscript-helper doesn't support dpkg triggers

[vangelis muhtsis]

Package: apache2
Version: 2.4.6-2
Severity: important

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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



-- Package-specific info:

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

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

Versions of packages apache2 depends on:
ii  apache2-bin   2.4.6-2
ii  apache2-data  2.4.6-2
ii  lsb-base  4.1+Debian12
ii  mime-support  3.54
ii  perl  5.14.2-21
ii  procps1:3.3.8-2

Versions of packages apache2 recommends:
ii  ssl-cert  1.0.32

Versions of packages apache2 suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
pn  apache2-utils
ii  chromium [www-browser]   28.0.1500.71-2
ii  iceweasel [www-browser]  22.0-1
ii  konqueror [www-browser]  4:4.10.5-1
ii  links [www-browser]  2.7-2
ii  lynx-cur [www-browser]   2.8.8dev.15-2
ii  netsurf [www-browser]2.9-2
ii  netsurf-gtk [www-browser]2.9-2
ii  rekonq [www-browser] 0.9.2-1
ii  w3m [www-browser]0.5.3-9

Versions of packages apache2-bin depends on:
ii  libapr1  1.4.8-1
ii  libaprutil1  1.5.2-1
ii  libaprutil1-dbd-sqlite3  1.5.2-1
ii  libaprutil1-ldap 1.5.2-1
ii  libc62.17-7
ii  libcap2  1:2.22-1.2
ii  libldap-2.4-22.4.31-1+nmu2
ii  liblua5.1-0  5.1.5-4
ii  libpcre3 1:8.31-2
ii  libssl1.0.0  1.0.1e-3
ii  libxml2  2.9.1+dfsg1-2
ii  perl 5.14.2-21
ii  zlib1g   1:1.2.8.dfsg-1

Versions of packages apache2-bin suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  chromium [www-browser]   28.0.1500.71-2
ii  iceweasel [www-browser]  22.0-1
ii  konqueror [www-browser]  4:4.10.5-1
ii  links [www-browser]  2.7-2
ii  lynx-cur [www-browser]   2.8.8dev.15-2
ii  netsurf [www-browser]2.9-2
ii  netsurf-gtk [www-browser]2.9-2
ii  rekonq [www-browser] 0.9.2-1
ii  w3m [www-browser]0.5.3-9

Versions of packages apache2 is related to:
ii  apache2  2.4.6-2
ii  apache2-bin  2.4.6-2

-- 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#718322: libdoodle1: should not depend on libextractor-plugins

[Bertrand Marc]

Package: libdoodle1
Severity: normal

Dear Maintainer,

In the last revision of libextractor, the binary packages libextractor3 and 
libextractor-plugins are now merged. Therefore libextractor-plugins doesn't 
exist, and libdoodle1 should not depend on it.

Could you please upload a new version of doodle, without this hardcoded 
dependency ?

Cheers,
Bertrand


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

Bug#711072: Building mcabber with libotr Version 4?

[Franziska Lichtblau]

On Tue, Jul 30, 2013 at 09:50:35AM +0200, intrigeri wrote:
> Hi Franziska,
> 
> Mikael Berthe wrote (13 Jul 2013 10:59:08 GMT) :
> > There is a patch from Myhailo Danylenko in our issue tracker which has
> > been reported to work, so I'll merge it.  If you can confirm it works
> > with Debian packages (I haven't tried yet) it would be very helpful.
> 
> > https://bitbucket.org/McKael/mcabber-crew/issue/102/libotr-400-support
> 
> Ping?
>
Package is now with my sponsor and should be uploaded soon. 

Cheers,
Rhalina


signature.asc
Description: Digital signature

Bug#718324: Python traceback when trying to delete a lun/filio backstore *without* any mapping

[Raoul Bhatia [IPAX]]

Package: targetcli
Version: 2.0rc1-2
Severity: normal


my config (a little obfuscated because of privacy concerns):

# targetcli
Welcome to the targetcli shell:

 Copyright (c) 2011 by RisingTide Systems LLC.

Visit us at http://www.risingtidesystems.com.

Using ib_srpt fabric module.
Using qla2xxx fabric module.
Using iscsi fabric module.
Using loopback fabric module.
Using tcm_fc fabric module.
/iscsi/iqn.20...7c/tpgt1/luns> ls /
o- / 
.
 [...]
  o- backstores 
..
 [...]
  | o- fileio 
..
 [3 Storage Objects]
  | | o- kxxvsa  
[/data/customers/kxx/kxxvsa/backup.iscsi activated]
  | | o- kyyvsd  
[/data/customers/kyy/kyyvsd/backup.iscsi activated]
  | | o- test 
... 
[/data/customers/kxx/test.iscsi activated]
  | o- iblock 
...
 [0 Storage Object]
  | o- pscsi 

 [0 Storage Object]
  | o- rd_dr 

 [0 Storage Object]
  | o- rd_mcp 
...
 [0 Storage Object]
  o- ib_srpt 

 [0 Target]
  o- iscsi 
..
 [1 Target]
  | o- iqn.2003-01.org.linux-iscsi.server01.x8664:sn.083f7c9e8233 
.. [1 TPG]
  |   o- tpgt1 
...
 [enabled]
  | o- acls 
...
 [3 ACLs]
  | | o- iqn.1991-05.com.microsoft:kxxvsa.a.local 
... [1 Mapped LUN]
  | | | o- mapped_lun2 
.
 [lun2 (rw)]
  | | o- iqn.1991-05.com.microsoft:kyyvsd 
... [1 Mapped 
LUN]
  | | | o- mapped_lun1 
.
 [lun1 (rw)]
  | | o- iqn.1993-08.org.debian:01:6abdf44cfb2 
.. [0 Mapped 
LUN]
  | o- luns 
...
 [3 LUNs]
  | | o- lun0 
... [fileio/test 
(/data/customers/kxx/test.iscsi)]
  | | o- lun1  
[fileio/kyyvsd (/data/customers/kyy/kyyvsd/backup.iscsi)]
  | | o- lun2  
[fileio/kxxvsa (/data/customers/kxx/kxxvsa/backup.iscsi)]
  | o- portals 
.
 [2 Portals]
  |   o- 172.20.0.1:3260 
..
 [OK]
  |   o- 172.20.20.1:3260 
.
 [OK]
  o- loopback 
...
 [0 Target]
  o- qla2xxx 

 [0 Target]
  o- tcm_fc 
.
 [0 Target]


Now, i want to delete both iscs/.../luns/lun0 and
backstores/fileio/test:

/iscsi/iqn.20...7c/tpgt1/luns> delete 0
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/configshell/shell.py", line 983, in 
run_interactive
self._cli_loop()
  File "/usr/lib/python2.7/dist-packages/configshell/shell.py", line 806, in 
_cli_loop
self.run_cmdline(cmdline)
  File "/usr/lib/python2.7/dist-packages/configshell/shell.py", line 927, in 
run_cmdline
self._execute_command(path, command, p

Bug#718323: RFS: hyperrogue/3.7+dfsg-1 [ITP] -- non-euclidean graphical rogue-like game

[chrysn]

Package: sponsorship-requests
Severity: normal

hello mentors, and hello debian games team,

i've written a package for the hyperrogue game, and would like to ask
for sponsorship for this new package.

* Package name: hyperrogue
  Version : 3.7
  Upstream Author : Zeno Rogue 
* URL : http://www.roguetemple.com/z/hyper.php
* License : GPL-2+
  Programming Lang: C++
  Description : non-euclidean graphical rogue-like game
  Section : games

it builds a single binary package of the same name.

content-wise, it's a rogue-like game (walk around, collect treasures,
fight monsters) with the unique feature of being played on a hyperbolic
geometry (on regularly arranged hexagons and heptagons). its graphics
options range from ascii (still on sdl graphics output, for hyperbolic
geometry is hard to reflect in a terminal) to escher style interwoven
tiles.


the package's source git (git-buildpackage style, only the dfsg part
without the windows dlls checked in) already resides in the pkg-games
section on alioth. the master branch was *not* tagged debian/3.7+dfsg-1,
because i'm not sure whether this is supposed to be done by me or by
whoever sponsors it (wiki.d.o/Games/VCS/git seems to indicate the
former, from pkg-ruby-extras i know it's the latter way).

the relevant urls are:

Vcs-Web:
http://anonscm.debian.org/gitweb/?p=pkg-games/hyperrogue.git;a=summary
Vcs-Git:
git://anonscm.debian.org/pkg-games/hyperrogue.git
Mentors page:
https://mentors.debian.net/package/hyperrogue
dget line / dsc:
 dget -x 
http://mentors.debian.net/debian/pool/main/h/hyperrogue/hyperrogue_3.7+dfsg-1.dsc

this is the first version of hyperrogue to be uploaded to debian.

please consider sponsoring this package.

best regards
chrysn

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom


signature.asc
Description: Digital signature

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

[Jeremy Lainé]

I am assuming the current version of the packaging is on git.tzafrir.org, can 
we move this
to a repo on alioth, presumably under control of pkg-voip-maintainers?

I have spotted what looks like a mistake in debian/control for pjproject:

- it has a Build-Depends on libpulse-dev (which looks unnecessary)
- it is missing a Build-Depends on portaudio19-dev (without which it FTBFS for 
me)

The attached patch fixes this.

Jeremy
commit 559a90618b65cc809cc9db7b69bc4574faf4fd8a
Author: Jeremy Lainé 
Date:   Tue Jul 30 10:15:54 2013 +0200

Fix Build-Depends: replace pulse by portaudio

diff --git a/debian/control b/debian/control
index cd7561d..a50dda0 100644
--- a/debian/control
+++ b/debian/control
@@ -6,7 +6,7 @@ Build-Depends: debhelper (>= 8),
  libspeex-dev, libspeexdsp-dev,
  libgsm1-dev,
  libsrtp0-dev,
- libpulse-dev
+ portaudio19-dev
 Standards-Version: 3.9.3
 #Homepage: http://www.reviewboard.org/
 #Vcs-Git: git://anonscm.debian.org/collab-maint/rbtools.git

Bug#718325: 389-ds-base: CVE-2013-2219: ACLs inoperative in some search scenarios

[Salvatore Bonaccorso]

Source: 389-ds-base
Severity: important
Tags: security patch upstream

Hi

CVE-2013-2219 was assigned for
https://bugzilla.redhat.com/show_bug.cgi?id=979508 where affected code
seems present also in 389-ds-base. See Red Hat Bug for details and
a patch.

Regards,
Salvatore


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

Bug#706702: Report to upstream

[Shuxiong Ye]

Hi,
I've reported this bug to the upstream.
See it here:
http://bitronix-transaction-manager.10986.n7.nabble.com/libbtm-java-2-1-2-Fail-to-build-from-source-with-Java7-td1499.html

-- 
Sincerely

Shuxiong Ye

School of Electronics Engineering and Computer Science, Peking University

Bug#718324: Python traceback when trying to delete a lun/filio backstore *without* any mapping

[Raoul Bhatia [IPAX]]

I managed to use lio_node to successfully remove the lun:

# lio_node --dellun iqn.2003-01.org.linux-iscsi.server01.x8664:sn.083f7c9e8233 
1 0

> Successfully deleted iSCSI Target Logical Unit

I then was able to remove /backstores/fileio/test using targetcli:

/> cd /backstores/fileio/
/backstores/fileio> delete test
Deleted storage object test.
ls /
o- / 
.
 [...]
  o- backstores 
..
 [...]
  | o- fileio 
..
 [3 Storage Objects]
  | | o- kxxvsa  
[/data/customers/kxx/kxxvsa/backup.iscsi activated]
  | | o- kyyvsd  
[/data/customers/kyy/kyyvsd/backup.iscsi activated]
  | o- iblock 
...
 [0 Storage Object]
[...]


Cheers,
Raoul


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

Bug#708499: New dpkg no longer contains install-info, rising to serious

[Andreas Beckmann]

On Saturday, 27. July 2013 11:41:22 Guillem Jover wrote:
> dpkg 1.17.0 is now in unstable, and does not contain the install-info
> compatibility wrapper any longer. These bugs are severity serious now.

While a simple rebuild is sufficient to get rid of the install-info usage (a 
binNMU is not possible as this is an arch:all package), the rebuilt one comes 
with a new Lintian error:

E: t-code: package-contains-info-dir-file usr/share/info/dir.gz

Andreas


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

Bug#718326: gnome-power-manager: no sleep or hibernate button in the shutdown confirmation dialog

[intrigeri]

Package: gnome-power-manager
Version: 3.8.2-1
Severity: normal

Hi,

I'm running sid with systemd 204-2 from experimental, and GNOME in
fallback mode, on a ThinkPad X201.

Previously, I had working sleep and hibernate buttons in the shutdown
confirmation dialog. Yesterday, after reading this upower (0.9.21-1)
debian/changelog entry:

  * Add alternative systemd dependency instead of just hard-depending on
pm-utils. With logind, upower defers suspend to logind instead of calling
pm-*, this allows us to not install pm-utils with systemd.

I de-installed pm-utils and acpi-support. Since then, I can't see
these buttons anymore. Note that the keyboard shortcuts for sleep
(Fn-F4) and hibernate (Fn-F12) work fine, as does sleep-on-lid-close.

Feel free, obviously, to reassign to a better suitable package
(upower?) if needed.

Perhaps this combination of software isn't supported yet, and I should
get pm-utils back installed?

Thanks for your attention, and for maintaining GNOME in Debian!

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

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

Versions of packages gnome-power-manager depends on:
ii  dbus-x11 1.6.12-1
ii  dconf-gsettings-backend [gsettings-backend]  0.16.1-1
ii  gnome-settings-daemon3.4.2+git20121218.7c1322-6+b1
ii  libc62.17-7
ii  libcairo21.12.14-5
ii  libglib2.0-0 2.36.3-3
ii  libgtk-3-0   3.8.2-3
ii  libpango-1.0-0   1.32.5-5+b1
ii  libpangocairo-1.0-0  1.32.5-5+b1
ii  libupower-glib1  0.9.21-1
ii  notification-daemon  0.7.6-1
ii  upower   0.9.21-1

gnome-power-manager recommends no packages.

Versions of packages gnome-power-manager suggests:
ii  policykit-1  0.110-3

-- no debconf information

--
  intrigeri
  | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc


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

Bug#703010: debianutils: ischroot can no longer detect vservers

[Andrew Ruthven]

On Sun, 2013-07-28 at 00:47 +, Clint Adams wrote:
> On Fri, Mar 15, 2013 at 09:16:45PM +1300, Andrew Ruthven wrote:
> > The big downside to that approach that I can see is that according to
> > the changelog ischroot was implemented to *stop* people having checks
> > spread all over the place. And as we've just discovered those checks
> > break over time as things progress. Better to have them in one place,
> > than spread around.
> 
> I don't know; it seems pretty stupid to base script behavior on
> whether one is in a "chroot" or not.

Totally agree. The problem is with tools that don't run in a chroot, if
they are in a chroot, break horribly. Mostly they're stuff run from
init.d...

-- 
Andrew Ruthven
Wellington, New Zealand
At home: and...@etc.gen.nz |   linux.conf.au 2013
   | Come join the party...
   |  http://linux.conf.au


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

Bug#718327: [dpkg-dev] Fails apt-get upgrade

[Davide Governale]

Package: dpkg-dev
Version: 1.16.10
Severity: critical

--- Please enter the report below this line. ---
Dear Maintainer,
This is what apt-get tells me

# apt-get upgrade
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze   
Lettura informazioni sullo stato... Fatto
È utile eseguire "apt-get -f install" per correggere ciò.
I seguenti pacchetti hanno dipendenze non soddisfatte:
 dpkg-dev : Dipende: libdpkg-perl (= 1.16.10) ma la versione 1.17.1 è
installata E: Dipendenze non trovate. Riprovare usando -f.

root@atreides:/home/magellanino# apt-get -f install
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze   
Lettura informazioni sullo stato... Fatto
Correzione delle dipendenze... Fatto
I seguenti pacchetti saranno inoltre installati:
  dpkg-dev
Pacchetti suggeriti:
  debian-keyring
I seguenti pacchetti saranno aggiornati:
  dpkg-dev
1 aggiornati, 0 installati, 0 da rimuovere e 31 non aggiornati.
39 non completamente installati o rimossi.
È necessario scaricare 0 B/1341 kB di archivi.
Dopo quest'operazione, verranno occupati 72,7 kB di spazio su disco.
Continuare [S/n]? s
Preparativi per sostituire dpkg-dev v.1.16.10
(utilizzando .../dpkg-dev_1.17.1_all.deb)... Estrazione del sostituto
di dpkg-dev... dpkg: errore
nell'elaborare /var/cache/apt/archives/dpkg-dev_1.17.1_all.deb
(--unpack): tentata sovrascrittura di
"/usr/share/man/it/man5/deb-control.5.gz" presente anche nel pacchetto
manpages-it 2.80-3 dpkg-deb: errore: il sottoprocesso paste è stato
terminato dal segnale (Pipe interrotta) Elaborazione dei trigger per
man-db... Si sono verificati degli errori
nell'elaborazione: /var/cache/apt/archives/dpkg-dev_1.17.1_all.deb E:
Sub-process /usr/bin/dpkg returned an error code (1)

Kindly,
Davide Governale.



--- System information. ---
Architecture: i386
Kernel:   Linux 3.10-1-686-pae

Debian Release: jessie/sid
  500 unstablewww.deb-multimedia.org 
  500 unstableftp.de.debian.org 
  500 stable  dl.google.com 
1 experimentalftp.de.debian.org 

--- Package information. ---
Depends   (Version) | Installed
===-+-===
libdpkg-perl (= 1.17.1) | 1.17.1
bzip2   | 1.0.6-4
xz-utils| 5.1.1alpha+20120614-2
patch   | 2.7.1-3
make| 3.81-8.2
binutils| 2.23.52.20130727-1
base-files   (>= 5.0.0) | 7.2


Recommends   (Version) | Installed
==-+-===
gcc| 4:4.8.1-2
 OR c-compiler | 
build-essential| 11.6
fakeroot   | 1.19-2
gnupg  | 1.4.14-1
gpgv   | 1.4.14-1
libalgorithm-merge-perl| 0.08-2


Suggests(Version) | Installed
=-+-===
debian-keyring| 







signature.asc
Description: PGP signature

Bug#393876: libapache2-modxslt: xsl:sort doesn't work as expected

[Vincent Lefevre]

Control: found -1 1.1.26-14.1

On 2008-11-01 18:40:14 +0100, Nick Wellnhofer wrote:
> Support for the lang attribute of xsl:sort has been added to libxslt and
> should be available in the next release. If you set the lang attribute you
> should get the following sort order for most languages:
> 
> A a B b C c

Actually I get a A b B c C (case-order being unsupported).

Testcase (apply this stylesheet on itself):

http://www.w3.org/1999/XSL/Transform";>




  
c
A
B
b
a
C

  


  


  


  

  




I get:

$ xsltproc case-sort.xsl case-sort.xsl


  c
  A
  B
  b
  a
  C
  aAbBcC
  aAbBcC


-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


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

Bug#717280: Reported to upstream

[Shuxiong Ye]

Hi,
I've reported this bug to the upstream.
See it here: http://jira.codehaus.org/browse/WAGON-400

-- 
Sincerely

Shuxiong Ye

School of Electronics Engineering and Computer Science, Peking University

Bug#718328: gperf: Please mark Multi-Arch: foreign

[Colin Watson]

Package: gperf
Version: 3.0.3-2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch saucy

I was about to do a QA upload with this change, but I see that Hilko's
in the process of adopting this package, so perhaps you could apply it?

gperf is architecture-dependent but provides an architecture-independent
interface, so it doesn't matter which architecture you get of it
provided that you can execute its binaries.  The way to declare this in
multiarch-speak is to declare it Multi-Arch: foreign.  A number of
packages build-depend on gperf, including such important ones as
coreutils, so making gperf Multi-Arch: foreign eases the process of
cross-building the base system because you can use the version from your
build architecture rather than having to arrange to be able to emulate
the version for the host architecture at build time.

diff -u gperf-3.0.3/debian/control gperf-3.0.3/debian/control
--- gperf-3.0.3/debian/control
+++ gperf-3.0.3/debian/control
@@ -7,6 +7,7 @@
 
 Package: gperf
 Architecture: any
+Multi-Arch: foreign
 Depends: ${shlibs:Depends}
 Replaces: libg++272-dev, libg++27-dev
 Description: Perfect hash function generator

Thanks,

-- 
Colin Watson   [cjwat...@ubuntu.com]


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

Bug#718327: [dpkg-dev] Fails apt-get upgrade

[Guillem Jover]

Control: forcemerge 717983 -1

On Tue, 2013-07-30 at 11:10:26 +0200, Davide Governale wrote:
> Package: dpkg-dev
> Version: 1.16.10
> Severity: critical

This severity is quite excessive given the definition from the BTS.

> root@atreides:/home/magellanino# apt-get -f install
[…]
> Preparativi per sostituire dpkg-dev v.1.16.10
> (utilizzando .../dpkg-dev_1.17.1_all.deb)... Estrazione del sostituto
> di dpkg-dev... dpkg: errore
> nell'elaborare /var/cache/apt/archives/dpkg-dev_1.17.1_all.deb
> (--unpack): tentata sovrascrittura di
> "/usr/share/man/it/man5/deb-control.5.gz" presente anche nel pacchetto
> manpages-it 2.80-3 dpkg-deb: errore: il sottoprocesso paste è stato
> terminato dal segnale (Pipe interrotta) Elaborazione dei trigger per
> man-db... Si sono verificati degli errori
> nell'elaborazione: /var/cache/apt/archives/dpkg-dev_1.17.1_all.deb E:
> Sub-process /usr/bin/dpkg returned an error code (1)

This was reported in 717983 and fixed in git, will be included in
1.17.2 to be released in few days, for now you could follow the
workarounds in [0] (but applied to dpkg-dev instead of dpkg) or
upgrade manpages-it which has just been fixed.

[0] 

Thanks,
Guillem


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

Bug#697788: works in current svn

[tom fogal]

I just attempted your convert/for i data and saw working/expected 
behavior with ImageVis3D's latest svn.


Any chance you could try svn and see if that still has the issue?


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

Bug#695824: am experiencing the same issue

[Tshepang Lekhonkhobe]

The only -dkms package I have is virtualbox-dkms, version
4.2.16-dfsg-1, on Testing.

$ dkms status
Error! Could not locate dkms.conf file.
File:  does not exist.

$ find /etc/dkms /var/lib/dkms -ls
26259914 drwxr-xr-x   3 root root 4096 Jul 30 11:44 /etc/dkms
26259924 -rw-r--r--   1 root root  518 Jul  8  2008
/etc/dkms/framework.conf
26259934 drwxr-xr-x   3 root root 4096 Jul 30 11:44
/etc/dkms/template-dkms-mkdeb
26260174 drwxr-xr-x   2 root root 4096 Jul 30 11:44
/etc/dkms/template-dkms-mkdeb/debian
26260264 -rwxr-xr-x   1 root root  360 Jul  8  2008
/etc/dkms/template-dkms-mkdeb/debian/prerm
26260234 -rw-r--r--   1 root root  189 May 13  2009
/etc/dkms/template-dkms-mkdeb/debian/changelog
26260244 -rw-r--r--   1 root root  353 Jan 26  2010
/etc/dkms/template-dkms-mkdeb/debian/control
26260274 -rwxr-xr-x   1 root root 1233 Jul 14  2011
/etc/dkms/template-dkms-mkdeb/debian/postinst
26260224 -rw-r--r--   1 root root2 May 13  2009
/etc/dkms/template-dkms-mkdeb/debian/compat
26260214 -rw-r--r--   1 root root  150 Jul  8  2008
/etc/dkms/template-dkms-mkdeb/debian/README.Debian
26260194 -rwxr-xr-x   1 root root  881 May 13  2009
/etc/dkms/template-dkms-mkdeb/debian/rules
26260254 -rw-r--r--   1 root root8 Jul  8  2008
/etc/dkms/template-dkms-mkdeb/debian/dirs
26260204 -rw-r--r--   1 root root   70 Jul  8  2008
/etc/dkms/template-dkms-mkdeb/debian/copyright
26259944 -rw-r--r--   1 root root  699 Jun 17  2011
/etc/dkms/template-dkms-mkdeb/Makefile
26236900 lrwxrwxrwx   1 root root   19 Oct  6  2012
/etc/dkms/template-dkms-mkdsc -> template-dkms-mkdeb
14462504 drwxr-xr-x   3 root root 4096 Jul 30 11:43
/var/lib/dkms
14421694 -rw-r--r--   1 root root6 Jul  8  2008
/var/lib/dkms/dkms_dbversion
14557984 drwxr-xr-x   4 root root 4096 Jul 30 11:42
/var/lib/dkms/virtualbox
14425694 drwxr-xr-x   5 root root 4096 Jul 30 11:41
/var/lib/dkms/virtualbox/4.2.16
14433264 drwxr-xr-x   3 root root 4096 Jul 30 11:41
/var/lib/dkms/virtualbox/4.2.16/3.9-1-amd64
14439424 drwxr-xr-x   4 root root 4096 Jul 30 11:41
/var/lib/dkms/virtualbox/4.2.16/3.9-1-amd64/x86_64
14440434 drwxr-xr-x   2 root root 4096 Jul 30 11:41
/var/lib/dkms/virtualbox/4.2.16/3.9-1-amd64/x86_64/module
1469127  392 -rw-r--r--   1 root root   399976 Jul 30 11:41
/var/lib/dkms/virtualbox/4.2.16/3.9-1-amd64/x86_64/module/vboxdrv.ko
1469131   16 -rw-r--r--   1 root root12632 Jul 30 11:41
/var/lib/dkms/virtualbox/4.2.16/3.9-1-amd64/x86_64/module/vboxnetadp.ko
1469135   32 -rw-r--r--   1 root root30856 Jul 30 11:41
/var/lib/dkms/virtualbox/4.2.16/3.9-1-amd64/x86_64/module/vboxnetflt.ko
1443936   32 -rw-r--r--   1 root root30544 Jul 30 11:41
/var/lib/dkms/virtualbox/4.2.16/3.9-1-amd64/x86_64/module/vboxpci.ko
14440264 drwxr-xr-x   2 root root 4096 Jul 30 11:41
/var/lib/dkms/virtualbox/4.2.16/3.9-1-amd64/x86_64/log
1458401   12 -rw-r--r--   1 root root 9141 Jul 30 11:41
/var/lib/dkms/virtualbox/4.2.16/3.9-1-amd64/x86_64/log/make.log
14456840 lrwxrwxrwx   1 root root   26 Jul 30 11:40
/var/lib/dkms/virtualbox/4.2.16/source -> /usr/src/virtualbox-4.2.16
14424524 drwxr-xr-x  13 root root 4096 Jul 30 11:41
/var/lib/dkms/virtualbox/4.2.16/build
14439034 drwxr-xr-x   3 root root 4096 Jul 30 11:41
/var/lib/dkms/virtualbox/4.2.16/build/vboxpci
14683114 -rw-r--r--   1 root root  194 Jul 30 11:41
/var/lib/dkms/virtualbox/4.2.16/build/vboxpci/.built-in.o.cmd
1468846   16 -rw-r--r--   1 root root14568 Jul 30 11:41
/var/lib/dkms/virtualbox/4.2.16/build/vboxpci/SUPR0IdcClient.o
1469315   56 -rw-r--r--   1 root root55040 Jul 30 11:41
/var/lib/dkms/virtualbox/4.2.16/build/vboxpci/vboxpci.mod.o
14442054 drwxr-xr-x   2 root root 4096 Jul 30 11:41
/var/lib/dkms/virtualbox/4.2.16/build/vboxpci/linux
1468313  276 -rw-r--r--   1 root root   278944 Jul 30 11:41
/var/lib/dkms/virtualbox/4.2.16/build/vboxpci/linux/VBoxPci-linux.o
14457744 -rw-r--r--   1 root root 1975 Jul 30 11:41
/var/lib/dkms/virtualbox/4.2.16/build/vboxpci/linux/SUPR0IdcClient-linux.c
[snip lots of output]

$ bash -x dkms status
+ shopt -s extglob
+ readonly 'dkms_conf_variables=CLEAN REMAKE_INITRD remake_initrd PACKAGE_NAME
   PACKAGE_VERSION POST_ADD POST_INSTALL POST_REMOVE PRE_BUILD
   PRE_INSTALL BUILD_EXCLUSIVE_KERNEL BUILD_EXCLUSIVE_ARCH
   build_exclude OBSOLETE_BY MAKE MAKE_MATCH MODULES_CONF
   modules_conf_array PATCH PATCH_MATCH patch_array BUILT_MODULE_NAME
   built_module_name BUILT_MODULE_LOCATION built_module_location
   DEST_MODUL

Bug#549431: pidgin-otr: Logging should be disabled by default

[Thibaut Varène]

On 30 juil. 2013, at 09:38, intrigeri  wrote:

> Hi Thibaut,
> 
> I've seen you've tagged this bug `upstream' a while ago,
> but I see no mention of this bug being forwarded to them.
> 
> Was it?

Upstream is subscribed to the BTS.

HTH


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

Bug#718329: apt: Please add support for .deb with uncompressed data.tar member

[Guillem Jover]

Package: apt
Version: 0.9.9.4
Severity: wishlist

Hi!

The apt code does not support uncompressed data.tar .deb members, as
specified by deb(5), which have been supported by since dpkg 1.10.24.

At least the kernel team is currently using «dpkg-deb -Zgzip -z0» on
linux-source-3.10, which generates an uncompressed data.tar.gz member
(which TBH in a strict sense it's bogus for dpkg to create), because
otherwise dak rejects uncompressed .deb data.tar members by way of
python-apt, and finally libapt. dpkg-deb calls that “compressor” «none»,
in case you'd like to have some term consistency.

In any case uncompressed data.tar members are useful in general, when
the contents are all already compressed and there's no gain in
recompressing the member again. AFAIK debdelta is also using those
when reconstructing .debs to feed to dpkg, to avoid duped work.

Thanks,
Guillem


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

Bug#718262: wget: NTLM not supported

[Vladislav Kurz]

Hello,

thaks for the info about NTLM support and patches. Now I am satisfied with my 
solution - recompile against OpenSSL. I just wanted to make sure that NTLM 
support will be reintroduced to the packaged version of wget, so that other 
users will not need to patch and compile by themselves.

-- 
S pozdravem
Vladislav Kurz

=== WebStep, s.r.o. (Ltd.) = a step to the Web ===
address: Mezirka 1, 602 00 Brno, CZ, tel: +420 548 214 711
=== www.webstep.net === vladislav.k...@webstep.net ===


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

Bug#718330: python-apt: Please add support for .deb with uncompressed data.tar member

[Guillem Jover]

Package: python-apt
Version: 0.8.9.1
Severity: wishlist
Control: block -1 by 718329

Hi!

The python-apt code does not seem to support uncompressed data.tar .deb
members, as specified by deb(5), which have been supported by since
dpkg 1.10.24.

At least the kernel team is currently using «dpkg-deb -Zgzip -z0» on
linux-source-3.10, which generates an uncompressed data.tar.gz member
(which TBH in a strict sense it's bogus for dpkg to create), because
otherwise dak rejects uncompressed .deb data.tar members by way of
lintian, and might not be able to process them through python-apt, and
finally libapt, or other tools dealing with .deb files.

dpkg-deb calls that "compressor" «none», in case you'd like to have
some term consistency.

In any case uncompressed data.tar members are useful in general, when
the contents are all already compressed and there's no gain in
recompressing the member again. AFAIK debdelta is also using those
when reconstructing .debs to feed to dpkg, to avoid duped work.

Thanks,
Guillem


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

Bug#718329: apt: Please add support for .deb with uncompressed data.tar member

[Guillem Jover]

Hi!

On Tue, 2013-07-30 at 12:07:00 +0200, Guillem Jover wrote:
> At least the kernel team is currently using «dpkg-deb -Zgzip -z0» on
> linux-source-3.10, which generates an uncompressed data.tar.gz member
> (which TBH in a strict sense it's bogus for dpkg to create), because
> otherwise dak rejects uncompressed .deb data.tar members by way of
> python-apt, and finally libapt. dpkg-deb calls that “compressor” «none»,
> in case you'd like to have some term consistency.

Sorry, this seems to be somewhat outdated information, it appears as
if dak is rejecting these due to lintian, it *might* not be able to
process them afterwards due to python-apt and libapt anyway, but I've
not checked.

Although the Linux kernel team concerns are valid regardless as the
apt toolchain is unable to handle these, and there might be other
tools around too.

Thanks,
Guillem


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

Bug#718331: lintian: Please allow .deb with uncompressed data.tar member

[Guillem Jover]

Package: lintian
Version: 2.5.15
Severity: wishlist
Control: block -1 by 718329 718330

Hi!

The lintian checks seems to reject uncompressed data.tar .deb members,
as specified by deb(5), which have been supported since dpkg 1.10.24.

At least the kernel team is currently using «dpkg-deb -Zgzip -z0» on
linux-source-3.10, which generates an uncompressed data.tar.gz member
(which TBH in a strict sense it's bogus for dpkg to create), because
otherwise dak rejects uncompressed .deb data.tar members by way of
lintian.

Take into account that the Debian archive should probably continue
rejecting those for now until at least python-apt and apt are fixed to
support these members. I guess this could be fixed in lintian, and still
get dak to reject them, in such case please ignore the blocks.

dpkg-deb calls that "compressor" «none», in case you'd like to have
some term consistency.

In any case uncompressed data.tar members are useful in general, when
the contents are all already compressed and there's no gain in
recompressing the member again. AFAIK debdelta is also using those
when reconstructing .debs to feed to dpkg, to avoid duped work.

Thanks,
Guillem


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

Bug#718332: Incorrectly parsed dates from status file

[R�diger Schopper]

Package: logrotate
Version: 3.8.5-1
Severity: important
Tags: patch l10n upstream

Hi there,

we found a daylight saving time (DST) bug in logrotate. 
We want that our logfiles are rotated away once a year 
on January first, but only if they have grown larger than 1 MB.
Due to the bug in logrotate they get rotated twice a
year. First time on January first and a second time when they 
grow larger than 1 MB. This comes from a wrong conversion of 
the times stored in the status file. A example of the problem is:

   sh> export TZ="MEZ-1MSZ,M3.5.0,M10.5.0"
   sh> echo $TZ
   MEZ-1MSZ,M3.5.0,M10.5.0


   sh> date
   Tue Jul 30 10:46:03 MSZ 2013


   sh> cat /etc/logrotate.conf
   ...

   /tmp/logfile
   { yearly
 minsize 1M
   }

   ...


   sh> ls -lh /tmp/logfile
   -rw-rw-r-- 1 root root 39M Jul 30 10:40 /tmp/logfile


   sh> cat /var/lib/logrotate/status
   logrotate state -- version 2
   "/tmp/logfile" 2013-1-1-0:0:0


   sh> logrotate -d /etc/logrotate.conf
   rotating pattern: "/tmp/logfile"
yearly (100 rotations)
   olddir is /var/log/alt, empty log files are not rotated,
only log files >= 1048576 bytes are rotated, old logs are removed
   considering log /tmp/logfile
 log needs rotating
   rotating log /tmp/logfile, log->rotateCount is 100
   copying /tmp/logfile to /tmp/old/logfile-2013-07-29
   truncating /tmp/logfile


At

logrotate.c:945:   state->lastRotated = now;

the "lastRotated" is initialized with the value of "now", which makes
no sense, since whatever date is found in the status file, it has
never anything to do with the actual date. However, due to this 
initialisation, in our testcase the the field "state->lastRotated.tm_isdst"
is set to 1, because DST is active at the time "now".

At
logrotate.c:2107:  st->lastRotated.tm_year = year;
logrotate.c:2108:  st->lastRotated.tm_mon = month;
logrotate.c:2109:  st->lastRotated.tm_mday = day;
logrotate.c:2110:  st->lastRotated.tm_hour = hour;
logrotate.c:2111:  st->lastRotated.tm_min = minute;
logrotate.c:2112:  st->lastRotated.tm_sec = second;
logrotate.c:2113:
logrotate.c:2114:  /* fill in the rest of the st->lastRotated fields */
logrotate.c:2115:  lr_time = mktime(&st->lastRotated);
logrotate.c:2116:  st->lastRotated = *localtime(&lr_time);

only the fields "tm_year", "tm_month", "tm_mday", "tm_hour", "tm_min"
and "tm_sec" are changed but not tm_isdst, so it is still set when the time
conversions in line 2115 and 2116 are done. The documentation for mkdoc says,
that if tm_isdst is 1 then the time conversion is done with enabled DST which
is wrong in our case for the time 2013-01-01T00:00:00. For that reason we find
in "st->lastRotated" after the conversion the time 2012-12-31T23:00:00 which
lies in the year 2012 and therefore logrotate thinks the logfile needs rotation.

Our solution for the problem (pobably not the best) is to initialize the
structur correctly by setting the "tm_isdst" field to -1. The documentation
of mkdoc states, that this uses the DST which has been or will be in effect at
the date converted, which is precisely what we want.

Patch:
--- a/logrotate.c
+++ b/logrotate.c
@@ -2104,12 +2104,14 @@ static int readState(char *stateFilename)
return 1;
}

+   memset (&st->lastRotated, 0, sizeof st->lastRotated);
st->lastRotated.tm_year = year;
st->lastRotated.tm_mon = month;
st->lastRotated.tm_mday = day;
st->lastRotated.tm_hour = hour;
st->lastRotated.tm_min = minute;
st->lastRotated.tm_sec = second;
+   st->lastRotated.tm_isdst = -1;

/* fill in the rest of the st->lastRotated fields */
lr_time = mktime(&st->lastRotated);


Probably one would also have a look at all the other uses of mkdoc.
There might be similar problems.

Best regards

Rüdiger

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

Kernel: Linux 3.11.0-rc3-64+ (SMP w/16 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages logrotate depends on:
ii  base-passwd 3.5.26
ii  cron [cron-daemon]  3.0pl1-124
ii  libacl1 2.2.52-1
ii  libc6   2.17-7
ii  libpopt01.16-7
ii  libselinux1 2.1.13-2

Versions of packages logrotate recommends:
ii  heirloom-mailx [mailx]  12.5-2

logrotate suggests no packages.

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

-- no debconf information


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

Bug#718190: [Pkg-systemd-maintainers] Bug#718190: systemd: sometimes computer doesn't boot. It seems a problem with lvm.

[Antonio-M. Corbi Bellot]

El Mon, 29 Jul 2013 21:30:41 +0200
Michael Stapelberg  escribio:

> Hi Antonio-M.,
> 
> "Antonio-M. Corbi Bellot"  writes:
> > I think I've all the logs you asked for.
> Thanks for providing the logs. They reveal that you have /usr on a
> separate volume and don’t mount it in the initramfs, which is not
> supported:
> 
> [ 3.840308] systemd[1]: /usr appears to be on its own filesytem and is
> not already mounted. This is not a supported setup. Some things will
> probably break (sometimes even silently) in mysterious ways. Consult
> http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken
> for more information.

Hi Michael:

Yes...debian installer gave me the opportunity to partition the disk
like that and I decided to do so...

Systemd 44 from testing/unstable didn't gave problems with that
partition scheme neither did sysvinit.

I began having problems when I upgraded to systemd 204 from
experimental, and...

> I can see entries in your working log where the volume containing usr
> is recognized as plugged, whereas in the non-working log these
> entries are missing and instead a bunch of processes get killed.
> 
> This might well be a race condition that makes the boot work sometimes
> and sometimes not. Even if it later turns out that this was not the
> actual problem, it is definitely a good start to get this issue out of
> the way first.

...as you say here, not always...sometimes it worked, sometimes it
didn't; then the 'vgchange -a y' did the trick for me.

> So, you have two options:
> 
> 1) In case you definitely want to keep /usr separate, you need to
> mount it in the initramfs. See
>
> http://lists-archives.com/debian-devel/189709-mounting-usr-in-the-initramfs.html
> 
> 2) You could boot a live cd and move /usr to the root volume, then
>delete the separate /usr volume.
> 
> Please do that and report back. If you still encounter the issue,
> please re-gather the logs and attach the new logs. Thanks!

I have opted for a variant of option 2, resized the root partition,
cp'ed the '/usr' dir there with another name, commented the mounting
line of '/usr' in fstab, rebooted and renamed the '/new-usr' dir to
'usr', that worked for me.

Thanks for your help, hope this helps someone like me trying to use
newer systemd.

The computer boots faster and halts way faster than with sysvinit. I
still miss some software providing the '.service' files (like slim) but
they seem to work.

Best regards.
Antonio


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

Bug#675577: Bug#718094: mpfr4: FTBFS: configure: error: gmp.h can't be found, or is unusable.

[Vincent Lefevre]

On 2013-07-29 23:46:38 -0500, Steve M. Robbins wrote:
> OK, how about "with standard abi, the compiler will find it";i.e.
> without -m32. The lib32gmp package had to place its header in an
> unusual location which means, yes, the compiler won't find it
> without help.

But in the past, the header was placed in the usual location.

> Note, however, that the lib32gmp packages are going to be removed in 
> the near future.  I had sent a note to this effect to 
> mp...@packages.debian.org and received a positive response from 
> Laurent Fousse.  My suggestion is to simply remove the lib32mpfr 
> packages now.

That's bad because in the past, would could use the -m32 option
for programs using MPFR, and that's no longer possible (note that
libmpfr-dev:i386 is not installable).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


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

Bug#690986: Debian Bug#690986: CVE-2012-5363 CVE-2012-5365

[Steven Chamberlain]

Some further explanation of one of these issues:

> CVE-2012-5363 - flood of ICMPv6 Neighbor Solicitation messages
> 
> These packets announce an IPv6 host's presence on the local network.
> The source addresses of these packets are cached in a table
> of 'neighbour' hosts.  The table can be filled if a large number of
> source addresses are spoofed.  This incurs heavy CPU load and can break
> IPv6 networking on all interfaces.

It is important to note this is different from the others, and is not
related to having accept_rtadv enabled, but affects any FreeBSD IPv6 host.

A very elegant and complete fix for this is applied in OpenBSD and more
recently NetBSD, and this specific change is something we might want to
try ourselves and/or see merged upstream:

http://www.openbsd.org/cgi-bin/cvsweb/src/sys/netinet6/nd6.c.diff?r1=1.77;r2=1.78

This works by:

* triggering garbage collection of the neighbour cache when it fills
(this avoids a total DoS)

* using an LRU list, to try to preserve entries for hosts that are being
actively communicated with, in preference to spoofed entries which
eventually fall to the bottom of the list and are purged (this mitigates
the impact of cache purges on genuine IPv6 communication, and makes it
viable for the cache to be made smaller)

* limiting the size of the neighbour cache (ip6_neighborgcthresh) to
2048 entries by default (operations on a smaller cache incur less CPU
load) :

http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/netinet6/in6_proto.c.diff?r1=1.95&r2=1.95.8.1&f=h

There were other changes in this commit, to try to mitigate
CVE-2011-2393 and CVE-2012-5365, but less than ideal.

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


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

Bug#718243: [Aptitude-devel] Bug#718243: aptitude: complains about supposedly untrusted packages at _every_ install attempt

[Daniel Hartwig]

Control: severity -1 normal

On 29 July 2013 13:45, Axel Stammler  wrote:
> Package: aptitude
> Version: 0.6.8.2-1
> Severity: important
>
> Dear Maintainer,
>
> _Every_ time I call Aptitude with the "install" option, I get a message like
>
> WARNING: untrusted versions of the following packages will be installed!
>
> […]
>
> That happens even though all repositories I use have all keys installed (if 
> necessary at
> all).
>
> A simple "update" run suffices to make the message disappear so that the 
> installation can
> then proceed, but this only works for a day or so. Next time the warning 
> appears again.
>

Which sources are you using?  Provide /etc/apt/sources.list and all
files under /etc/apt/sources.list.d

Also, the output from these commands:
$ apt-cache policy
$ apt-cache policy libreoffice-lightproof-en


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

Bug#718333: perltidy: Please update package to new upstream version

[Per Carlson]

Package: perltidy
Version: 20120701-1
Severity: wishlist

Hi.

Could you please update perltidy to a newer upstream version? 20120714
and 20121207 do add a lot of useful flags and some bug fixes.


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

Bug#718281: Acknowledgement (race condition on execution of /etc/ifplugd/ifplug.action script and exit)

[Luke Kenneth Casson Leighton]

after some reflection overnight, i think a minor workaround would be
to have in /lib/udev/ifplugd.agent a check to see if '-M' is in the
$ARGS and if it is to *not* try to kill the ifplugd instance. for now
however i am just commenting out the kill:

remove|unregister)
debug_mesg Stopping $DAEMON_NAME for $INTERFACE

# kill a running ifplugd daemon
# NO!  DO NOT PERMIT THIS TO HAPPEN!
# let ifplugd exit on its own
#exec $DAEMON -k -i $INTERFACE

but this really is not the solution.  really, ifplugd should not be so
aggressive as to try to kill itself off without first letting it
complete the running of the "down" actions.

l.


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

Bug#718222: Dropping support for the smallest armel machines

[Ben Hutchings]

linux version 3.10.3-1 failed to build on armel, as the iop32x image
grew just over the limit.

As you volunteered to try maintaining the configuration changes for the
size-limited armel flavours, please can you try to find a configuration
change that will bring iop32x within the limit (also checking that
ixp4xx and orion5x fit).  I've been putting most such changes in
debian/config/armel/config-minimal which is applied to all those
flavours.

Ben.

-- 
Ben Hutchings
All extremists should be taken out and shot.




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

Bug#718253: debugging information

[Gunnar Krull]

Debugging buserver/budb_server with gdb shows this information:

(gdb) run -servers 134.76.81.219
Starting program: 
/usr/local/src/openafs/openafs_1.6.5-1-TEST/openafs-1.6.5/src/budb/budb_server 
-servers 134.76.81.219

[Thread debugging using libthread_db enabled]
Using host libthread_db library 
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".


Program received signal SIGSEGV, Segmentation fault.
verifyInterfaceAddress (ame=ame@entry=0xbfffef5c, 
info=info@entry=0xb050, aservers=aservers@entry=0x0) at beacon.c:628
628 tmpAddr = (afs_uint32) 
info->hostAddr[i].sin_addr.s_addr;



(gdb) list
623  ** application screwed up in dealing with multihomed concepts
624  */
625 for (j = 0, found = 0; j < count; j++) {
626 for (i = 0; i < totalServers; i++) {
627 if (info)
628 tmpAddr = (afs_uint32) 
info->hostAddr[i].sin_addr.s_addr;

629 else
630 tmpAddr = aservers[i];
631 if (myAddr[j] == tmpAddr) {
632 *ame = tmpAddr;

(lines 623-632 of beacon.c)


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

Bug#657666: w3m: -dump -o display_link_number=1 lists links in slightly random order

[Tatsuya Kinoshita]

tags 657666 + pending
thanks

On January 27, 2012 at 7:53PM +, debbugs (at xrad.org) wrote:
> I recently discovered w3m's "-dump -o display_link_number=1" options,
> and find them really useful.  One minor niggle is that the links are
> actually listed in an order quite close to, but not the same as, the
> number that's displayed.  So for example for one document I have, links
> 1-10 are presented in the order 1-7,9,10,8 in the References list at the
> end of the dump.  I attach a patch which sorts them according to number.

Merged in the development repository.

  
http://anonscm.debian.org/gitweb/?p=collab-maint/w3m.git;a=commitdiff;h=6be1df9b9f4e02ef59f74ebdde8aed3df624f8c3
  
http://anonscm.debian.org/gitweb/?p=collab-maint/w3m.git;a=shortlog;h=refs/heads/debian

On January 27, 2012 at 8:01PM +, debbugs (at xrad.org) wrote:
> By the way, I didn't look into W3M's memory management terribly
> carefully.  Since it appears to use a garbage collector, I assumed that
> there was no need to free in_order, but I do notice references to a
> GC_free function: perhaps I should call GC_free(in_order) after all?

Calling GC_free isn't needed.

Thanks,
--
Tatsuya Kinoshita


pgpsIi0sbQrS7.pgp
Description: PGP signature

Bug#718335: blosxom: Error on VCS-Browse Url

[Simon Kainz]

Package: blosxom
Version: 2.1.2-1
Severity: minor
Tags: patch

The Vcs-Browser-URL in the control in wrong. Please see my attahced patch.

Regards,



-- 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-30 13:54:43.731528743 +0200
+++ control	2013-07-30 13:54:48.499674594 +0200
@@ -6,7 +6,7 @@
 Standards-Version: 3.8.0
 Homepage: http://blosxom.sourceforge.net/
 Vcs-Git: git://repo.or.cz/blosxom.git
-Vcs-Browser: http://repo.or.cz/r/blosxom.git
+Vcs-Browser: http://repo.or.cz/w/blosxom.git
 
 Package: blosxom
 Architecture: all

Bug#718021: [Resolvconf-devel] Bug#718021: dns-nameservers vs dns-nameserver

[Christoph Anton Mitterer]

On Tue, 2013-07-30 at 09:15 +0200, Thomas Hood wrote: 

> meaning that *.some.domain queries should be routed to 192.168.1.254;
> *.another.one to 12.34.56.78 and the rest to 8.8.8.8. Dnsmasq supports
> this sort of query routing.
I see... yeah, that sounds like a good argument.


> Accepting multiple instances of an option in a stanza is a feature
> that was recently added to ifupdown. I presume that it will continue
> to be a supported feature in the future. :)
Sure... I just found it a bit ugly as it clutters up the file with
dozens of entries ;)



Cheers,
Chris. 


smime.p7s
Description: S/MIME cryptographic signature

Bug#718336: 2ping: Wrong URLs in control file.

[Simon Kainz]

Package: 2ping
Version: 2.0-1
Severity: minor
Tags: patch

According to the homepage, source code is now on github. Please see my attached 
patch.

-- 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-30 14:04:21.281199483 +0200
+++ control	2013-07-30 14:06:20.340843312 +0200
@@ -5,8 +5,8 @@
 Build-Depends: debhelper (>= 7.0.50~), dpkg-dev (>= 1.16.1~)
 Standards-Version: 3.9.3
 Homepage: http://www.finnie.org/software/2ping/
-Vcs-Browser: http://gitorious.org/2ping/2ping
-Vcs-Git: git://gitorious.org/2ping/2ping.git
+Vcs-Browser: https://github.com/rfinnie/2ping
+Vcs-Git: https://github.com/rfinnie/2ping
 XS-Dm-Upload-Allowed: yes
 
 Package: 2ping

Bug#718324: Python traceback when trying to delete a lun/filio backstore *without* any mapping

[Ritesh Raj Sarraf]

On Tuesday 30 July 2013 01:56 PM, Raoul Bhatia [IPAX] wrote:
> Package: targetcli
> Version: 2.0rc1-2
> Severity: normal
>
>
> my config (a little obfuscated because of privacy concerns):
>> # targetcli
>> Welcome to the targetcli shell:
>>
>>  Copyright (c) 2011 by RisingTide Systems LLC.
>>
>> Visit us at http://www.risingtidesystems.com.
>>
>> Using ib_srpt fabric module.
>> Using qla2xxx fabric module.
>> Using iscsi fabric module.
>> Using loopback fabric module.
>> Using tcm_fc fabric module.
>> /iscsi/iqn.20...7c/tpgt1/luns> ls /
>> o- /
>> .
>> [...]
>>   o- backstores
>> ..
>> [...]
>>   | o- fileio
>> ..
>> [3 Storage Objects]
>>   | | o- kxxvsa
>> 
>> [/data/customers/kxx/kxxvsa/backup.iscsi activated]
>>   | | o- kyyvsd
>> 
>> [/data/customers/kyy/kyyvsd/backup.iscsi activated]
>>   | | o- test
>> ...
>> [/data/customers/kxx/test.iscsi activated]
>>   | o- iblock
>> ...
>> [0 Storage Object]
>>   | o- pscsi
>> 
>> [0 Storage Object]
>>   | o- rd_dr
>> 
>> [0 Storage Object]
>>   | o- rd_mcp
>> ...
>> [0 Storage Object]
>>   o- ib_srpt
>> 
>> [0 Target]
>>   o- iscsi
>> ..
>> [1 Target]
>>   | o- iqn.2003-01.org.linux-iscsi.server01.x8664:sn.083f7c9e8233
>> .. [1 TPG]
>>   |   o- tpgt1
>> ...
>> [enabled]
>>   | o- acls
>> ...
>> [3 ACLs]
>>   | | o- iqn.1991-05.com.microsoft:kxxvsa.a.local
>> ... [1 Mapped LUN]
>>   | | | o- mapped_lun2
>> .
>> [lun2 (rw)]
>>   | | o- iqn.1991-05.com.microsoft:kyyvsd
>> ...
>> [1 Mapped LUN]
>>   | | | o- mapped_lun1
>> .
>> [lun1 (rw)]
>>   | | o- iqn.1993-08.org.debian:01:6abdf44cfb2
>> .. [0
>> Mapped LUN]
>>   | o- luns
>> ...
>> [3 LUNs]
>>   | | o- lun0
>> ...
>> [fileio/test (/data/customers/kxx/test.iscsi)]
>>   | | o- lun1 
>> [fileio/kyyvsd (/data/customers/kyy/kyyvsd/backup.iscsi)]
>>   | | o- lun2 
>> [fileio/kxxvsa (/data/customers/kxx/kxxvsa/backup.iscsi)]
>>   | o- portals
>> .
>> [2 Portals]
>>   |   o- 172.20.0.1:3260
>> ..
>> [OK]
>>   |   o- 172.20.20.1:3260
>> .
>> [OK]
>>   o- loopback
>> ...
>> [0 Target]
>>   o- qla2xxx
>> 
>> [0 Target]
>>   o- tcm_fc
>> .
>> [0 Target]
>
> Now, i want to delete both iscs/.../luns/lun0 and
> backstores/fileio/test:
>> /iscsi/iqn.20...7c/tpgt1/luns> delete 0
>> Traceback (most recent call last):
>>   File "/usr/lib/python2.7/dist-packages/con

Bug#718324: Python traceback when trying to delete a lun/filio backstore *without* any mapping

[Ritesh Raj Sarraf]

On Tuesday 30 July 2013 05:53 PM, Ritesh Raj Sarraf wrote:
> I'm glad you've been able to work around for the time being. I see
> upstream pushed some very recent fixes, which I suspect is the case of
> your bug too.
> http://www.risingtidesystems.com/git/?p=rtslib.git;a=commitdiff;h=9b9f3f6050acc4a700894d538d8d7475e33484f9

Actually, the fix is:
http://www.risingtidesystems.com/git/?p=rtslib.git;a=commitdiff;h=120e2c9a923ed300eba15c5c4de3f7a643f93712

It is my bad. This fix was pushed to me in May. But I never picked it
up. You'll run into this problem if you are on a kernel which is 3.9+

Like I said in the previous email, once the new upstream release is out,
I'll push it. That'll solve most of the problems.

-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."



signature.asc
Description: OpenPGP digital signature

Bug#718337: lintian: Wrong tag for lzma compressed udebs

[Guillem Jover]

Package: lintian
Version: 2.5.15
Severity: normal
Tags: patch

Hi!

The checks on deb incorrectly tag lzma compressed udebs with
lzma-deb-archive instead of
udeb-uses-unsupported-compression-for-data-tarball.

Here's a tentative (because the entire logic might need to be reworked
anyway, see my previous and next deb related bug reports) and untested
patch, although dpkg-deb emits a warning when building lzma compressed
.debs, and that option might either fail in the future or transparently
map the value to xz, not sure yet.

Thanks,
Guillem
From e3c4251a04d0985a86ee4c5c7189eddaacdb6dec Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Tue, 30 Jul 2013 14:13:55 +0200
Subject: [PATCH] c/deb-format.pm: Do not emit lzma-deb-archive on lzma
 compressed udebs

Emit the correct tag udeb-uses-unsupported-compression-for-data-tarball
instead.

Signed-off-by: Guillem Jover 
---
 checks/deb-format.pm| 5 ++---
 t/tests/deb-format-udeb-compression/debian/debian/rules | 2 +-
 2 files changed, 3 insertions(+), 4 deletions(-)

diff --git a/checks/deb-format.pm b/checks/deb-format.pm
index 276b22e..dc95b03 100644
--- a/checks/deb-format.pm
+++ b/checks/deb-format.pm
@@ -53,6 +53,8 @@ if ($success) {
 } elsif ($members[1] ne 'control.tar.gz') {
 tag 'malformed-deb-archive',
 "second member $members[1] not control.tar.gz";
+} elsif ($type eq 'udeb' && $members[2] !~ m/^data\.tar\.[gx]z$/) {
+tag 'udeb-uses-unsupported-compression-for-data-tarball';
 } elsif ($members[2] eq 'data.tar.lzma') {
 # Ubuntu's archive allows lzma packages.
 tag 'lzma-deb-archive';
@@ -60,9 +62,6 @@ if ($success) {
 tag 'malformed-deb-archive',
 "third member $members[2] not data.tar.(gz|bz2|xz)";
 } else {
-if ($type eq 'udeb' && $members[2] !~ m/^data\.tar\.[gx]z$/) {
-tag 'udeb-uses-unsupported-compression-for-data-tarball';
-}
 $okay = 1;
 }
 } else {
diff --git a/t/tests/deb-format-udeb-compression/debian/debian/rules b/t/tests/deb-format-udeb-compression/debian/debian/rules
index cba8c5d..5287abb 100644
--- a/t/tests/deb-format-udeb-compression/debian/debian/rules
+++ b/t/tests/deb-format-udeb-compression/debian/debian/rules
@@ -6,4 +6,4 @@
 override_dh_builddeb:
 	# manually call dpkg-deb because dh_builddeb uses -Zxz and does
 	# not allow us to override it.
-	dpkg-deb -Zbzip2 --build debian/some-udeb ../some-udeb_1.0_all.udeb
+	dpkg-deb -Zlzma --build debian/some-udeb ../some-udeb_1.0_all.udeb
-- 
1.8.3.2

Bug#718338: Abysmal performance with CalDAV

[martin f krafft]

Package: iceowl
Version: 1.9-3
Severity: normal

Adding a CalDAV calendar makes iceowl practically unusable.

During the initial communication with the server, the GUI stops
updating for minutes. The same applies to synchronisation runs. When
the GUI finally comes back, usage is sluggish, i.e. a mouse click is
followed by 10–20 seconds until the menu clicked finally opens.
Operations such as deleting an event take many seconds to complete,
although the server logs suggest almost instantaneous execution.

It seems that "offline support" (caching), makes it even worse.

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

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

Versions of packages iceowl depends on:
ii  libasound2  1.0.27.2-1
ii  libatk1.0-0 2.8.0-2
ii  libc6   2.17-7
ii  libcairo2   1.12.14-5
ii  libdbus-1-3 1.6.12-1
ii  libdbus-glib-1-20.100.2-1
ii  libevent-2.0-5  2.0.21-stable-1
ii  libffi5 3.0.10-3
ii  libfontconfig1  2.10.2-2
ii  libfreetype62.4.9-1.1
ii  libgcc1 1:4.8.1-8
ii  libgdk-pixbuf2.0-0  2.28.2-1
ii  libglib2.0-02.36.3-3
ii  libgtk2.0-0 2.24.20-1
ii  libhunspell-1.3-0   1.3.2-4
ii  libjpeg88d-1
ii  libnspr42:4.10-1
ii  libnss3 2:3.15-1
ii  libnss3-1d  2:3.15-1
ii  libpango1.0-0   1.32.5-5+b1
ii  libpixman-1-0   0.30.0-2
ii  libsqlite3-03.7.17-1
ii  libstdc++6  4.8.1-8
ii  libvpx1 1.2.0-2
ii  libx11-62:1.6.0-1
ii  libxext62:1.3.2-1
ii  libxrender1 1:0.9.8-1
ii  libxt6  1:1.1.3-1+deb7u1
ii  zlib1g  1:1.2.8.dfsg-1

Versions of packages iceowl recommends:
pn  calendar-google-provider  

iceowl suggests no packages.

-- no debconf information


-- 
 .''`.   martin f. krafft   Related projects:
: :'  :  proud Debian developer   http://debiansystem.info
`. `'`   http://people.debian.org/~madduckhttp://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#713668: lasso: diff for NMU version 2.3.6-2.2

[Sebastian Ramacher]

Control: tags -1 + patch pending

Dear maintainer,

I've prepared an NMU for lasso (versioned as 2.3.6-2.2) and uploaded it
to DELAYED/2. Please feel free to tell me if I should delay it longer.

(Sorry for the config.{sub,guess} noise. The clean target updates these
two files.)

Regards
-- 
Sebastian Ramacher
diff -u lasso-2.3.6/config.guess lasso-2.3.6/config.guess
--- lasso-2.3.6/config.guess
+++ lasso-2.3.6/config.guess
@@ -1,14 +1,12 @@
 #! /bin/sh
 # Attempt to guess a canonical system name.
-#   Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
-#   2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
-#   2011, 2012 Free Software Foundation, Inc.
+#   Copyright 1992-2013 Free Software Foundation, Inc.
 
-timestamp='2012-02-10'
+timestamp='2013-05-16'
 
 # This file is free software; you can redistribute it and/or modify it
 # under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2 of the License, or
+# the Free Software Foundation; either version 3 of the License, or
 # (at your option) any later version.
 #
 # This program is distributed in the hope that it will be useful, but
@@ -22,19 +20,17 @@
 # As a special exception to the GNU General Public License, if you
 # distribute this file as part of a program that contains a
 # configuration script generated by Autoconf, you may include it under
-# the same distribution terms that you use for the rest of that program.
-
-
-# Originally written by Per Bothner.  Please send patches (context
-# diff format) to  and include a ChangeLog
-# entry.
+# the same distribution terms that you use for the rest of that
+# program.  This Exception is an additional permission under section 7
+# of the GNU General Public License, version 3 ("GPLv3").
 #
-# This script attempts to guess a canonical system name similar to
-# config.sub.  If it succeeds, it prints the system name on stdout, and
-# exits with 0.  Otherwise, it exits with 1.
+# Originally written by Per Bothner.
 #
 # You can get the latest version of this script from:
 # http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD
+#
+# Please send patches with a ChangeLog entry to config-patc...@gnu.org.
+
 
 me=`echo "$0" | sed -e 's,.*/,,'`
 
@@ -54,9 +50,7 @@
 GNU config.guess ($timestamp)
 
 Originally written by Per Bothner.
-Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000,
-2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012
-Free Software Foundation, Inc.
+Copyright 1992-2013 Free Software Foundation, Inc.
 
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
@@ -138,6 +132,27 @@
 UNAME_SYSTEM=`(uname -s) 2>/dev/null`  || UNAME_SYSTEM=unknown
 UNAME_VERSION=`(uname -v) 2>/dev/null` || UNAME_VERSION=unknown
 
+case "${UNAME_SYSTEM}" in
+Linux|GNU|GNU/*)
+	# If the system lacks a compiler, then just pick glibc.
+	# We could probably try harder.
+	LIBC=gnu
+
+	eval $set_cc_for_build
+	cat <<-EOF > $dummy.c
+	#include 
+	#if defined(__UCLIBC__)
+	LIBC=uclibc
+	#elif defined(__dietlibc__)
+	LIBC=dietlibc
+	#else
+	LIBC=gnu
+	#endif
+	EOF
+	eval `$CC_FOR_BUILD -E $dummy.c 2>/dev/null | grep '^LIBC'`
+	;;
+esac
+
 # Note: order is significant - the case branches are not exclusive.
 
 case "${UNAME_MACHINE}:${UNAME_SYSTEM}:${UNAME_RELEASE}:${UNAME_VERSION}" in
@@ -200,6 +215,10 @@
 	# CPU_TYPE-MANUFACTURER-OPERATING_SYSTEM is used.
 	echo "${machine}-${os}${release}"
 	exit ;;
+*:Bitrig:*:*)
+	UNAME_MACHINE_ARCH=`arch | sed 's/Bitrig.//'`
+	echo ${UNAME_MACHINE_ARCH}-unknown-bitrig${UNAME_RELEASE}
+	exit ;;
 *:OpenBSD:*:*)
 	UNAME_MACHINE_ARCH=`arch | sed 's/OpenBSD.//'`
 	echo ${UNAME_MACHINE_ARCH}-unknown-openbsd${UNAME_RELEASE}
@@ -302,7 +321,7 @@
 arm:RISC*:1.[012]*:*|arm:riscix:1.[012]*:*)
 	echo arm-acorn-riscix${UNAME_RELEASE}
 	exit ;;
-arm:riscos:*:*|arm:RISCOS:*:*)
+arm*:riscos:*:*|arm*:RISCOS:*:*)
 	echo arm-unknown-riscos
 	exit ;;
 SR2?01:HI-UX/MPP:*:* | SR8000:HI-UX/MPP:*:*)
@@ -801,6 +820,9 @@
 i*:CYGWIN*:*)
 	echo ${UNAME_MACHINE}-pc-cygwin
 	exit ;;
+*:MINGW64*:*)
+	echo ${UNAME_MACHINE}-pc-mingw64
+	exit ;;
 *:MINGW*:*)
 	echo ${UNAME_MACHINE}-pc-mingw32
 	exit ;;
@@ -852,21 +874,21 @@
 	exit ;;
 *:GNU:*:*)
 	# the GNU system
-	echo `echo ${UNAME_MACHINE}|sed -e 's,[-/].*$,,'`-unknown-gnu`echo ${UNAME_RELEASE}|sed -e 's,/.*$,,'`
+	echo `echo ${UNAME_MACHINE}|sed -e 's,[-/].*$,,'`-unknown-${LIBC}`echo ${UNAME_RELEASE}|sed -e 's,/.*$,,'`
 	exit ;;
 *:GNU/*:*:*)
 	# other systems with GNU libc and userland
-	echo ${UNAME_MACHINE}-unknown-`echo ${UNAME_SYSTEM} | sed 's,^[^/]*/,,' | tr '[A-Z]' '[a-z]'``echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'`-gnu
+	echo ${UNAME_MACHINE}-unknown-`echo ${UNAME_SYSTEM} | sed 's,^[^/]*/,,' | tr '[A-Z]' '[a-z]'``echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'`-${LIBC}
 	exit ;;

Bug#718332: Acknowledgement (Incorrectly parsed dates from status file)

[Rüdiger Schopper]

Sorry,

any "mkdoc" should be a "mktime".

Best regards

On Tue, Jul 30, 2013 at 10:39:14AM +, 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.
> 
> Your message has been sent to the package maintainer(s):
>  Paul Martin 
> 
> 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.
> 
> -- 
> 718332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718332
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems


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

Bug#616689: Reproduced on a preseeded Jessie install

[Adam Baxter]

I just accidentally reproduced this while installing Jessie with a preseed
that did not include lvm2 - shouldn't it be part of the base install if LVM
is chosen in guided partitioning?

Debian GNU/Linux testing "Jessie" - Official Snapshot amd64 NETINST
Binary-1 20130729-21:37 (20130729) was used as a base.

Bug#681418: #681418 debugfs is a big security hole

[Steve Cotton]

On Sun, May 05, 2013 at 12:24:44PM +0300, Timo Juhani Lindfors wrote:
> the issue still exists in experimental
> 
> lindi3:~$ ls -ld /sys/kernel/debug
> drwxr-xr-x 2 root root 0 May  5 12:02 /sys/kernel/debug
> lindi3:~$ cat /proc/version 
> Linux version 3.8-trunk-amd64 (debian-ker...@lists.debian.org) (gcc version 
> 4.7.2 (Debian 4.7.2-5) ) #1 SMP Debian 3.8.5-1~experimental.1

Hi Timo,

For me the mount point changes permission when mounted, and from the hard link 
count I guess you have it unmounted.

tsunami:~# umount /sys/kernel/debug/
tsunami:~# ls -ld /sys/kernel/debug/
drwxr-xr-x 2 root root 0 Jul 30 13:08 /sys/kernel/debug/
tsunami:~# mount -t debugfs none /sys/kernel/debug
tsunami:~# ls -ld /sys/kernel/debug/
drwx-- 16 root root 0 Jul 29 08:52 /sys/kernel/debug/

I'm using a local build of 3.10.2.

Regards,
Steve


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

Bug#718339: please backport to wheezy

[Antoine Beaupré]

Package: git-annex
Version: 3.20120629
Severity: wishlist

Git annex is pretty amazing, particularly with the git-annex
assistant. Unfortunately, it is rather complicated to install (or even
build) under the most recent Debian release (wheezy). Here's what I
got last I tried:

The following NEW packages will be installed:
  bsdmainutils{a} debhelper{a} file{a} gettext{a} gettext-base{a} ghc{a}
  groff-base{a} html2text{a} intltool-debian{a} libasprintf0c2{a}
  libbsd-dev{a} libbsd0{a} libcroco3{a} libffi-dev{a} libffi5{a}
 Depends: libghc-dbus-dev (>= 0.10.3) but it is 
not going to be installed.
 Depends: libghc-yesod-dev but it is not going 
to be installed.
 Depends: libghc-yesod-static-dev but it is not 
going to be installed.
 Depends: libghc-yesod-default-dev but it is 
not going to be installed.
 Depends: libghc-hamlet-dev but it is not going 
to be installed.
 Depends: libghc-clientsession-dev but it is 
not going to be installed.
 Depends: libghc-warp-dev but it is not going 
to be installed.
 Depends: libghc-wai-dev but it is not going to 
be installed.
 Depends: libghc-wai-logger-dev but it is not 
going to be installed.
 Depends: libghc-case-insensitive-dev but it is 
not going to be installed.
 Depends: libghc-http-types-dev but it is not 
going to be installed.
 Depends: libghc-blaze-builder-dev but it is 
not going to be installed.
 Depends: libghc-crypto-api-dev but it is not 
going to be installed.
 Depends: libghc-network-multicast-dev which is 
a virtual package.
 Depends: libghc-network-info-dev which is a 
virtual package.
 Depends: libghc-safesemaphore-dev which is a 
virtual package.
 Depends: libghc-network-protocol-xmpp-dev (>= 
0.4.3-1+b1) but it is not going to be installed.
 Depends: libghc-gnutls-dev (>= 0.1.4) but it 
is not going to be installed.
 Depends: libghc-xml-types-dev but it is not 
going to be installed.
 Depends: libghc-async-dev which is a virtual 
package.
 Depends: ikiwiki but it is not going to be 
installed.
 Depends: perlmagick but it is not going to be 
installed.
 Depends: git but it is not going to be 
installed.
 Depends: rsync but it is not going to be 
installed.
 Depends: wget but it is not going to be 
installed.
 Depends: curl but it is not going to be 
installed.
 Depends: openssh-client but it is not going to 
be installed.
Unable to resolve dependencies!  Giving up...

I am not too familiar with the Haskell toolchain (but I wish i would!)
- how hard would a backport be?

A.

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

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

Versions of packages git-annex depends on:
ii  curl7.26.0-1+wheezy3
ii  git 1:1.7.10.4-1+wheezy1
ii  libc6   2.13-38
ii  libffi5 3.0.10-3
ii  libgmp102:5.0.5+dfsg-2
ii  libpcre31:8.30-5
ii  openssh-client  1:6.0p1-4
ii  rsync   3.0.9-4
ii  uuid1.6.2-1.3
ii  wget1.13.4-3

Versions of packages git-annex recommends:
ii  lsof  4.86+dfsg-1

Versions of packages git-annex suggests:
pn  bup   
ii  gnupg 1.4.12-7
ii  graphviz  2.26.3-14

-- 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#681418: #681418 debugfs is a big security hole

[Timo Juhani Lindfors]

Steve Cotton  writes:
> For me the mount point changes permission when mounted, and from the hard 
> link count I guess you have it unmounted.
>
> tsunami:~# umount /sys/kernel/debug/
> tsunami:~# ls -ld /sys/kernel/debug/
> drwxr-xr-x 2 root root 0 Jul 30 13:08 /sys/kernel/debug/
> tsunami:~# mount -t debugfs none /sys/kernel/debug
> tsunami:~# ls -ld /sys/kernel/debug/
> drwx-- 16 root root 0 Jul 29 08:52 /sys/kernel/debug/
>
> I'm using a local build of 3.10.2.

That might indeed be true. I can't reproduce the bug with

linux-image-3.10-1-amd64   3.10.3-1

today.


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

Bug#718340: conky: Fails to start from script

[sharon kimble]

Package: conky
Version: 1.9.0-3
Severity: normal

Dear Maintainer,
Programme 'conkygo' crashed with exit code 1.  Respawning..
Conky: can't open display:
* Imlib2 Developer Warning * :
This program is calling the Imlib call:

imlib_context_free();

With the parameter:

context

being NULL. Please fix your program.
Programme 'conkygo' crashed with exit code 1.  Respawning..
Terminated

conkygo is -
#!/bin/bash -e
#saved in /usr/local/bin

/usr/bin/conky -d ~c /home/boudiccas/.conky/.conkyrc-basic

Thanks
Sharon Kimble



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

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

Versions of packages conky depends on:
ii  conky-std  1.9.0-3

conky recommends no packages.

conky 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#676784: Policy §10.5 and .jar file noticeable exception

[Charles Plessy]

Le Tue, Jul 30, 2013 at 08:50:42AM +0300, Eugene Zhukov a écrit :
> On Tue, Jul 30, 2013 at 2:12 AM, Charles Plessy  wrote:
> > Le Fri, Jul 26, 2013 at 06:57:35AM +0900, Charles Plessy a écrit :
> >> Le Thu, Jul 25, 2013 at 12:13:12AM +0200, Bill Allombert a écrit :
> >> >
> >> > A .jar file is not a compressed file in the sense it is not meant to be 
> >> > uncompressed
> >> > with unzip or zless etc.
> >>
> >> I agree.  Shall we close that bug ?  Or add the above as a footnote if it 
> >> is
> >> felt necessary ?
> >
> > Hi all,
> >
> > if there is no futher input within a few days, I am going to close this 
> > bug, as
> > it is based on a clearly erroneous interpretation of the Policy.
> >
> > If a clearification is necessary, how about adding "in "sense it is meant 
> > to be
> > uncompressed with unzip or zless etc." either in parenthesis of as a 
> > footnote.
> 
> IMO a note in parenthesis or a footnote would help a lot. Then I guess
> it can be closed, since there is another #539315, which can be closed
> only after fixing lintian.

Thanks for the prompt feedback.

Unless there is objection, I will add the note in parenthesis as a
non-normative change, and then mark the bug pending.

Cheers,

-- 
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#711852: maven.pm: Don't install documentation jar into maven-repo by default

[Emmanuel Bourg]

An alternative is to specify the target used to generated the javadoc.
By default javadoc:jar is called. Switching to javadoc:javadoc solves
this issue:

DEB_MAVEN_DOC_TARGET := javadoc:javadoc

I would suggest changing the default target though.


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

Bug#675577: Bug#718094: mpfr4: FTBFS: configure: error: gmp.h can't be found, or is unusable.

[Steve M. Robbins]

On July 30, 2013 12:42:09 PM Vincent Lefevre wrote:
> On 2013-07-29 23:46:38 -0500, Steve M. Robbins wrote:
> > OK, how about "with standard abi, the compiler will find it";i.e.
> > without -m32. The lib32gmp package had to place its header in an
> > unusual location which means, yes, the compiler won't find it
> > without help.
> 
> But in the past, the header was placed in the usual location.

Yes.  Things were changed to accomodate multi-arch.


> > Note, however, that the lib32gmp packages are going to be removed in
> > the near future.  I had sent a note to this effect to
> > mp...@packages.debian.org and received a positive response from
> > Laurent Fousse.  My suggestion is to simply remove the lib32mpfr
> > packages now.
> 
> That's bad because in the past, would could use the -m32 option
> for programs using MPFR, and that's no longer possible

Yes.  The general idea is to take advantage of multi-arch to use the variant of 
your architecture.


> (note that libmpfr-dev:i386 is not installable).

I'm surprised you say that as it appears to have worked here.  To my surprise, 
it appears even to be co-installable with the amd64 version:

steve@riemann{2013}dpkg --list libmpfr-dev
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version   
Architecture  Description
+++-=-=-=-===
ii  libmpfr-dev:amd64 3.1.1-1   
amd64 multiple precision floating-point computation 
developers tools
ii  libmpfr-dev:i386  3.1.1-1   
i386  multiple precision floating-point computation 
developers tools
steve@riemann{2013}ls -l /usr/lib/*/*mpfr*
-rw-r--r-- 1 root root 692110 Feb 20 01:17 /usr/lib/i386-linux-gnu/libmpfr.a
lrwxrwxrwx 1 root root 16 Feb 20 01:17 /usr/lib/i386-linux-gnu/libmpfr.so 
-> libmpfr.so.4.1.1
lrwxrwxrwx 1 root root 16 Feb 20 01:17 /usr/lib/i386-linux-gnu/libmpfr.so.4 
-> libmpfr.so.4.1.1
-rw-r--r-- 1 root root 386044 Feb 20 01:17 
/usr/lib/i386-linux-gnu/libmpfr.so.4.1.1
-rw-r--r-- 1 root root 917162 Feb 19 22:13 /usr/lib/x86_64-linux-gnu/libmpfr.a
lrwxrwxrwx 1 root root 16 Feb 19 22:13 /usr/lib/x86_64-linux-gnu/libmpfr.so 
-> libmpfr.so.4.1.1
lrwxrwxrwx 1 root root 16 Feb 19 22:13 
/usr/lib/x86_64-linux-gnu/libmpfr.so.4 -> libmpfr.so.4.1.1
-rw-r--r-- 1 root root 382208 Feb 19 22:13 
/usr/lib/x86_64-linux-gnu/libmpfr.so.4.1.1

Regards,
-Steve


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

Bug#717174: corrupted kernel log file output

[Steve Cotton]

On Wed, Jul 17, 2013 at 03:47:24PM +0200, Harald Dunkel wrote:
> After some uptime kernel logging via rsyslog appears to be broken.
> Sample from /var/log/kern.log:
> 
> Jun  1 12:23:16 mydb01b kernel: [   45.332611] vethwUmR1j: no IPv6 routers 
> present
> Jun  1 12:23:17 mydb01b kernel: [   46.020652] br0: port 10(vethAEZSD9) 
> entering forwarding state
> Jun  1 12:23:18 mydb01b kernel: [   47.132635] eth0: no IPv6 routers present
> Jun  1 12:23:18 mydb01b kernel: [   47.612642] vethAEZSD9: no IPv6 routers 
> present
> Jun  1 12:23:30 mydb01b kernel: [   59.102427] sshd (7527): 
> /proc/7527/oom_adj is deprecated, please use /proc/7527/oom_score_adj instead.
> Jun  2 05:15:20 mydb01b kernel: tr58t6<>14]as:00tam.1ai:x9y:s.4] E(0ie,=14s 
> Oxer=i2-sN(0rliui 0) uAF4Bipu t:A 0rt2AI02ilib
> Jun  3 00:51:59 mydb01b kernel: F:0)rceu.ygstO:0:tyance
> Jun  4 08:09:26 mydb01b kernel: tru
> Jun  4 08:09:26 mydb01b kernel: 41RT)Dit
> Jun  4 08:10:10 mydb01b kernel: <>241227DCNEHG hdle <020 J na <09 
> (Anfdavdeone5otn6[4.3 1Denas6r Jege
> Jun  4 08:10:10 mydb01b kernel: s
 
> Every helpful hint would be highly appreciated.
> Harri

Hi Harri,

This looks similar to #702494, does that machine have any guest VMs?

Regards,
Steve


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

Bug#717026: libapreq2: diff for NMU version 2.13-2.1

[Julien Cristau]

tags 717026 + patch
tags 717026 + pending
thanks

Hi Steinar,

I've prepared an NMU for libapreq2 (versioned as 2.13-2.1) and
will upload it soon.  This is one of the last pieces needed before
apache 2.4 can be in jessie.

Cheers,
Julien
diff -Nru libapreq2-2.13/debian/changelog libapreq2-2.13/debian/changelog
--- libapreq2-2.13/debian/changelog	2013-07-15 19:37:40.0 +0200
+++ libapreq2-2.13/debian/changelog	2013-07-30 15:53:15.0 +0200
@@ -1,3 +1,11 @@
+libapreq2 (2.13-2.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Version libapreq2-3's Conflicts/Replaces on libapreq2 as << 2.13-2~
+(closes: #717026).
+
+ -- Julien Cristau   Tue, 30 Jul 2013 15:53:13 +0200
+
 libapreq2 (2.13-2) unstable; urgency=low
 
   * Build against Apache 2.4. (Closes: #666802)
diff -Nru libapreq2-2.13/debian/control libapreq2-2.13/debian/control
--- libapreq2-2.13/debian/control	2013-07-15 19:35:00.0 +0200
+++ libapreq2-2.13/debian/control	2013-07-30 15:51:36.0 +0200
@@ -26,8 +26,8 @@
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Recommends: libapache2-mod-apreq2
-Replaces: libapache2-request-perl (<< 2.05-dev-3), libapreq2 (<< 2.13-1)
-Conflicts: libapreq2 (<< 2.13-1)
+Replaces: libapache2-request-perl (<< 2.05-dev-3), libapreq2 (<< 2.13-2~)
+Conflicts: libapreq2 (<< 2.13-2~)
 Description: generic Apache request library
  The generic Apache request library (APR) contains modules for manipulating
  client request data with the Apache API from Perl and C. Functionality


signature.asc
Description: Digital signature

Bug#685617: Allow co-installation of nvidia-kernel-dkms and nvidia-kernel-legacy-173xx-dkms

[Gaudenz Steinlin]

Hi Andreas

Any update on this? If there is anything you don't like about the patch
or anything that needs fixing. Please tell me. Otherwise it would be
really nice to finally integrate this.

Thanks,
Gaudenz

Gaudenz Steinlin  writes:

> Hi Andreas
>
> Now that all the other issues with respect to co-installing the
> different nvidia generations are resolved I wanted to ask about your
> plans regarding the co-installation of the (dkms) kernel modules.
>
> Are you planning to apply my patches or implement an equivalent
> solution? Anything where you need help or would like to have updated
> patches?
>
> BTW, thanks for all the work you have done so far integrating my
> patches. Not really related to this bug, but what are your plans
> regarding the 319 and 304 branches? Will you soon upload 319 to unstable
> and are you planning to add legacy-304xx packages?
>
> I also built (unmodified) wheezy backports of the nvidia-settings-xxx
> and glx-alternatives packages for i386 today. If you want I can upload
> those to backports.
>  
> Thanks,
> Gaudenz
>
> Andreas Beckmann  writes:
>
>> On 2012-08-23 00:18, Gaudenz Steinlin wrote:
>>> Andreas Beckmann  writes:
 Switching between current and legacy is done by reconfiguring the nvidia
 alternative (/usr/lib/nvidia/nvidia) - can't that be used by the module
 load script to select the "right" module?
>>
>>> In theory yes. But there are several problems:
>>> - plain alternatives are not possible because the files (the compiled
>>>   kernel modules) don't necesserily exist even if the package is
>>
>> No, I didn't want to install alternatives for the kernel module, just
>> get the status of the alternative (update-alternatives --query nvidia)
>> to do the correct selection.
>>
>>> (why not just select the best module if
>>>   we can).
>>
>> because the module must match the xorg driver and libGL
>>
>>> To be honest I did not look at the -source packages too closely. I'm not
>>> sure if they are still relevant.
>> They are not going away :-)
>>
>>> Dkms is IMHO the far superior and easier alternative.
>> But not suitable for all applications ...
>>
>>> But anyway the -source packages are already
>>> co-installable AFAICS.
>> The -source packages are co-installable, but the generated module
>> packages are not.
>>
>>> I don't know if there is a good way to modify the
>>> build system so that the module is renamed. As I think the -source
>>> packages are mostly relevant for manual builds I'm not even sure if it's
>>> a good idea to do such a modification there.
>> Having the -dkms and -source package building different modules (or
>> naming them differently) is a bad idea.
>>
>>> Agreed. Backports to wheezy would be cool though.
>>
>> Planned.
>>
>>
>> Andreas
>
> -- 
> Ever tried. Ever failed. No matter.
> Try again. Fail again. Fail better.
> ~ Samuel Beckett ~

-- 
Ever tried. Ever failed. No matter.
Try again. Fail again. Fail better.
~ Samuel Beckett ~


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

Bug#675577: Bug#718094: mpfr4: FTBFS: configure: error: gmp.h can't be found, or is unusable.

[Vincent Lefevre]

On 2013-07-30 08:25:20 -0500, Steve M. Robbins wrote:
> On July 30, 2013 12:42:09 PM Vincent Lefevre wrote:
> > (note that libmpfr-dev:i386 is not installable).
> 
> I'm surprised you say that as it appears to have worked here. To my
> surprise, it appears even to be co-installable with the amd64
> version:

I thought there was a clash with "gcc" (or some other installed
package), but this was apparently due to a bug in apt. Adding
"gcc" to "apt-get install libmpfr-dev:i386" solves the problem.
I've reported the apt bug here:

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

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


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

Bug#718287: wolf4sdl: Potentially non-free resource

[GhostlyDeath]

I am not too sure on a logo myself. Perhaps a self drawn pistol,
german sheppard or perhaps a top down view of a teal plat with a
chicken leg, mashed potatoes, and peas on it.

On 7/30/13, Fabian Greffrath  wrote:
> Am Montag, den 29.07.2013, 13:43 -0400 schrieb GhostlyDeath:
>> Hello, the following file ./debian/pixmaps/wolf4sdl.xpm contains a
>> face shot of the
>> main character of this game. Which is extracted from the game itself
>> on the status
>> bar.
>
> You are probably right. Do you have any other idea for an icon? I
> already digged through the FreeDoom resources but could not find
> anything that would fit IMHO.
>
> - Fabian
>
>
>


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

Bug#717026: libapreq2: diff for NMU version 2.13-2.1

[Steinar H. Gunderson]

On Tue, Jul 30, 2013 at 03:57:44PM +0200, Julien Cristau wrote:
> tags 717026 + patch
> tags 717026 + pending
> thanks
> 
> Hi Steinar,
> 
> I've prepared an NMU for libapreq2 (versioned as 2.13-2.1) and
> will upload it soon.  This is one of the last pieces needed before
> apache 2.4 can be in jessie.

Hi,

Feel free to upload, although you seemingly did so already.

/* Steinar */
-- 
Homepage: http://www.sesse.net/


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

Bug#718341: 'aptitude install cups-daemon' doesn't create 'cupsd.conf' file

[Jeffrey Thomas]

Package: aptitude
Version: 0.6.8.2-1
Severity: normal

Dear Maintainer,

Due to the pain of CUPS, I needed to reinstall my printers and that started
with purging CUPS and reinstalling those related packages.  I backed up the
/etc/cups/ folder and ran 'aptitude purge cups-daemon', and then tired to
install with 'aptitude install cups cups-daemon cups-client
cups-server-common hplip-cups cups-common'.  DPKG wasn't able to configure
CUPS due to a missing cupsd.conf file (which is in the package that
aptitude was installing, so it should not be missing).

I used 'apt-get install cups cups-daemon cups-client cups-server-common
hplip-cups cups-common' instead and everything worked.

Aptitude should have unpacked the file contents as expected and as I've
experienced in the past.  The inability of a package manager to install
necessary files seems like the tool isn't doing its job correctly.

Thanks for Debian!



-- Package-specific info:
Terminal: xterm
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.6.8.2 compiled at Nov  7 2012 07:08:03
Compiler: g++ 4.7.2
Compiled against:
  apt version 4.12.0
  NCurses version 5.9
  libsigc++ version: 2.2.10
  Ept support enabled.
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 5.9.20110404
  cwidget version: 0.5.16
  Apt version: 4.12.0

aptitude linkage:
linux-vdso.so.1 (0x7fff1ddff000)
libapt-pkg.so.4.12 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
(0x7fdf2d9d8000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5
(0x7fdf2d7a8000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5
(0x7fdf2d57e000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0
(0x7fdf2d379000)
libcwidget.so.3 => /usr/lib/libcwidget.so.3 (0x7fdf2d079000)
libept.so.1.aptpkg4.12 => /usr/lib/libept.so.1.aptpkg4.12
(0x7fdf2cdd8000)
libxapian.so.22 => /usr/lib/libxapian.so.22 (0x7fdf2c9f3000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fdf2c7dc000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
(0x7fdf2c53)
libboost_iostreams.so.1.49.0 =>
/usr/lib/libboost_iostreams.so.1.49.0 (0x7fdf2c515000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x7fdf2c2f9000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x7fdf2bff1000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fdf2bcf3000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x7fdf2badd000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fdf2b73)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1
(0x7fdf2b52d000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fdf2b329000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0
(0x7fdf2b118000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1
(0x7fdf2af13000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fdf2ad0a000)
/lib64/ld-linux-x86-64.so.2 (0x7fdf2e373000)

-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (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 aptitude depends on:
ii  aptitude-common   0.6.8.2-1
ii  libapt-pkg4.120.9.7.7
ii  libboost-iostreams1.49.0  1.49.0-3.2
ii  libc6 2.17-7
ii  libcwidget3   0.5.16-3.4
ii  libept1.4.12  1.0.9
ii  libgcc1   1:4.7.0-8
ii  libncursesw5  5.9-10
ii  libsigc++-2.0-0c2a2.2.10-0.2
ii  libsqlite3-0  3.7.13-1
ii  libstdc++64.7.0-8
ii  libtinfo5 5.9-10
ii  libxapian22   1.2.12-2
ii  zlib1g1:1.2.7.dfsg-13

Versions of packages aptitude recommends:
pn  apt-xapian-index
pn  aptitude-doc-en | aptitude-doc  
pn  libparse-debianchangelog-perl   
ii  sensible-utils  0.0.7

Versions of packages aptitude suggests:
pn  debtags  
ii  tasksel  3.14+nmu1

-- no debconf information

Bug#718342: aptitude install cups-daemon doesn't create 'cupsd.conf' file

[JGThomas]

Package: aptitude
Version: 0.6.8.2-1
Severity: normal

Dear Maintainer,

Due to the pain of CUPS, I needed to reinstall my printers and that started 
with purging CUPS and reinstalling those related packages.  I backed up the 
/etc/cups/ folder and ran 'aptitude purge cups-daemon', and then tired to 
install with 'aptitude install cups cups-daemon cups-client cups-server-common 
hplip-cups cups-common'.  DPKG wasn't able to configure CUPS due to a missing 
cupsd.conf file (which is in the package that aptitude was installing, so it 
should not be missing).

I used 'apt-get install cups cups-daemon cups-client cups-server-common 
hplip-cups cups-common' instead and everything worked.

Aptitude should have unpacked the file contents as expected and as I've 
experienced in the past.  The inability of a package manager to install 
necessary files seems like the tool isn't doing its job correctly.

Thanks for Debian!



-- Package-specific info:
Terminal: xterm
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.6.8.2 compiled at Nov  7 2012 07:08:03
Compiler: g++ 4.7.2
Compiled against:
  apt version 4.12.0
  NCurses version 5.9
  libsigc++ version: 2.2.10
  Ept support enabled.
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 5.9.20110404
  cwidget version: 0.5.16
  Apt version: 4.12.0

aptitude linkage:
linux-vdso.so.1 (0x7fff1ddff000)
libapt-pkg.so.4.12 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 
(0x7fdf2d9d8000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7fdf2d7a8000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7fdf2d57e000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7fdf2d379000)
libcwidget.so.3 => /usr/lib/libcwidget.so.3 (0x7fdf2d079000)
libept.so.1.aptpkg4.12 => /usr/lib/libept.so.1.aptpkg4.12 
(0x7fdf2cdd8000)
libxapian.so.22 => /usr/lib/libxapian.so.22 (0x7fdf2c9f3000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fdf2c7dc000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7fdf2c53)
libboost_iostreams.so.1.49.0 => /usr/lib/libboost_iostreams.so.1.49.0 
(0x7fdf2c515000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fdf2c2f9000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fdf2bff1000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fdf2bcf3000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fdf2badd000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fdf2b73)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7fdf2b52d000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fdf2b329000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7fdf2b118000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fdf2af13000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fdf2ad0a000)
/lib64/ld-linux-x86-64.so.2 (0x7fdf2e373000)

-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (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 aptitude depends on:
ii  aptitude-common   0.6.8.2-1
ii  libapt-pkg4.120.9.7.7
ii  libboost-iostreams1.49.0  1.49.0-3.2
ii  libc6 2.17-7
ii  libcwidget3   0.5.16-3.4
ii  libept1.4.12  1.0.9
ii  libgcc1   1:4.7.0-8
ii  libncursesw5  5.9-10
ii  libsigc++-2.0-0c2a2.2.10-0.2
ii  libsqlite3-0  3.7.13-1
ii  libstdc++64.7.0-8
ii  libtinfo5 5.9-10
ii  libxapian22   1.2.12-2
ii  zlib1g1:1.2.7.dfsg-13

Versions of packages aptitude recommends:
pn  apt-xapian-index
pn  aptitude-doc-en | aptitude-doc  
pn  libparse-debianchangelog-perl   
ii  sensible-utils  0.0.7

Versions of packages aptitude suggests:
pn  debtags  
ii  tasksel  3.14+nmu1

-- 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#718287: wolf4sdl: Potentially non-free resource

[Fabian Greffrath]

Am Dienstag, den 30.07.2013, 10:10 -0400 schrieb GhostlyDeath: 
> I am not too sure on a logo myself. Perhaps a self drawn pistol,
> german sheppard or perhaps a top down view of a teal plat with a
> chicken leg, mashed potatoes, and peas on it.

Patches welcome! :D


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

Bug#711244: Acknowledgement (Please update for tracker 0.16)

[Michael Biebl]

severity 711244 serious
tags 711244 + patch
thanks

Hi,

I've just uploaded tracker 0.16 to unstable. This means, bognor-regis
will now FTBFS (thus raising the severity).
The patch is very simple (debdiff attached).
I can offer to NMU the package with this patch applied or sponsor the
upload, if you need sponsoring

Michael



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
diff -Nru bognor-regis-0.6.12+git20101007.02c25268/debian/changelog 
bognor-regis-0.6.12+git20101007.02c25268/debian/changelog
--- bognor-regis-0.6.12+git20101007.02c25268/debian/changelog   2012-03-17 
16:30:18.0 +0100
+++ bognor-regis-0.6.12+git20101007.02c25268/debian/changelog   2013-07-30 
16:37:19.0 +0200
@@ -1,3 +1,10 @@
+bognor-regis (0.6.12+git20101007.02c25268-7.1) UNRELEASED; urgency=low
+
+  * Non-maintainer upload.
+  * Update to tracker 0.16.
+
+ -- Michael Biebl   Tue, 30 Jul 2013 16:37:01 +0200
+
 bognor-regis (0.6.12+git20101007.02c25268-7) unstable; urgency=low
 
   [ Michael Biebl  ]
diff -Nru bognor-regis-0.6.12+git20101007.02c25268/debian/control 
bognor-regis-0.6.12+git20101007.02c25268/debian/control
--- bognor-regis-0.6.12+git20101007.02c25268/debian/control 2012-03-17 
16:29:48.0 +0100
+++ bognor-regis-0.6.12+git20101007.02c25268/debian/control 2013-07-30 
16:37:30.0 +0200
@@ -8,7 +8,7 @@
libgconf2-dev, libnotify-dev (>= 0.7.3),
intltool, autoconf, automake,
libgupnp-1.0-dev, libgupnp-av-1.0-dev,
-   libtracker-sparql-0.14-dev
+   libtracker-sparql-0.16-dev
 Standards-Version: 3.9.3
 
 Package: bognor-regis
diff -Nru 
bognor-regis-0.6.12+git20101007.02c25268/debian/patches/port_to_tracker-sparql-0.14.patch
 
bognor-regis-0.6.12+git20101007.02c25268/debian/patches/port_to_tracker-sparql-0.14.patch
--- 
bognor-regis-0.6.12+git20101007.02c25268/debian/patches/port_to_tracker-sparql-0.14.patch
   2012-03-17 16:15:17.0 +0100
+++ 
bognor-regis-0.6.12+git20101007.02c25268/debian/patches/port_to_tracker-sparql-0.14.patch
   2013-07-30 16:37:41.0 +0200
@@ -13,7 +13,7 @@
  AM_CONDITIONAL(HAVE_QUEUE_CONFIG, test "x$enable_queue_config" = "xyes")
  
 -PKG_CHECK_MODULES(BOGNOR, gtk+-2.0 glib-2.0 dbus-glib-1 gio-2.0 libnotify 
tracker-client-0.9 gupnp-1.0 >= 0.13.0 gupnp-av-1.0 >= 0.5)
-+PKG_CHECK_MODULES(BOGNOR, gtk+-2.0 glib-2.0 dbus-glib-1 gio-2.0 libnotify 
tracker-sparql-0.14 gupnp-1.0 >= 0.13.0 gupnp-av-1.0 >= 0.5)
++PKG_CHECK_MODULES(BOGNOR, gtk+-2.0 glib-2.0 dbus-glib-1 gio-2.0 libnotify 
tracker-sparql-0.16 gupnp-1.0 >= 0.13.0 gupnp-av-1.0 >= 0.5)
  PKG_CHECK_MODULES(BOGNOR_REGIS, glib-2.0 dbus-glib-1 $gconf_pkg)
  PKG_CHECK_MODULES(CLIENT, gio-2.0)
  


signature.asc
Description: OpenPGP digital signature

Bug#698674: Tcl/Tk multiarching

[Dmitrijs Ledkovs]

To address many of FTBFS bugs, I did in the end introduce a compat
tclConfig.sh tkConfig.sh in non-multiarch locations for Ubuntu, that
simply call dpkg-architecture and source the multi-arched variant.

This solved most of the bugs, but there are still some software that
either hardcoded locations of the default versioned tk/tcl or, in case
of ruby, instead of source the configuration file, it tries to read in
& parse the file by itself.

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#711275: transition: tracker

[Michael Biebl]

Hi Adam,

Am 29.07.2013 21:42, schrieb Adam D. Barratt:
> Control: tags -1 + pending
> 
> On Thu, 2013-06-06 at 00:59 +0200, Michael Biebl wrote:
>> in preparation for GNOME 3.8, I'd like start a small transition updating
>> tracker from 0.14 to 0.16.
> [...]
> 
> Apologies for the delay in getting back to you about this. Please go
> ahead with the upload to unstable, and let us know which of the r-deps
> will be getting source uploads and which we {can,should} binNMU.
> 
>> * rygel is tracker 0.16 ready and should be binNMUable.
> 
> There's #715132, which is marked pending. It's not a regression from
> testing, so not a blocker, but it would be nice to avoid binNMUing rygel
> just to have it re-uploaded right away.

I've uploaded tracker, brasero, gnome-boxes, gnome-documents, nautilus
and totem.
I've also poked the bognor-regis maintainer about #711244 (will NMU in a
couple of days, in case I don't hear anything back).

Please schedule the remaining binNMUs for rygel and grilo-plugins.

Cheers,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#718323: RFS: hyperrogue/3.7+dfsg-1 [ITP] -- non-euclidean graphical rogue-like game

[Paul Wise]

On Tue, Jul 30, 2013 at 10:23 AM, chrysn wrote:

> i've written a package for the hyperrogue game, and would like to ask
> for sponsorship for this new package.

Here is a first-pass review:

About the fonts stuff; The best would be if the program used SDL Pango
instead or as an alternative to SDL TTF. Other font rendering systems
that automatically discover system fonts and cope with multi-script
strings by falling back on other fonts are also OK. If upstream isn't
OK with switching to SDL Pango, please send them a patch to use
fontconfig to detect where the font files are located, falling back on
runtime or compile-time configured fonts. An example of how to do this
stuff is in chromium-bsu, which uses different rendering libs but the
principles are the same. The GLC backend is an example of the SDL
Pango style and the FTGL backend is an example of the SDL TTF style.

Why is -O3 in CXXFLAGS? I would suggest sticking to the Debian default
which is set by dpkg-buildflags (-O2) and not setting CXXFLAGS in the
Makefile.

Please forward the remaining patches, manual page and desktop file
upstream if you haven't already.

Please add --parallel to the dh arguments.

You may want to run wrap-and-sort -sa.

Please use imagemagick or similar at build time to create PNG and XPM
icons (for the Freedesktop and Debian menus) from the upstream MS
Windows icon. The XPM should be 32x32 and the PNG one should be the
maximum size available in the MS Windows icon.

The copyright years in debian/copyright are slightly wrong.

Could you ask upstream; What is the origin of the numbers in
polygons.cpp? Were they created by hand? Were they converted from some
other format and hard-coded into the file? Are they maintained in some
other format? Are they not maintained at all?

Automated checks:

https://wiki.debian.org/HowToPackageForDebian#Check_points_for_any_package

lintian:

P: hyperrogue: no-upstream-changelog

blhc:

CXXFLAGS missing (-fPIE): g++ hyper.cpp -o hyper -lSDL -lSDL_ttf -DFHS
-Wall -g -lSDL_gfx -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wl,-z,relro
LDFLAGS missing (-fPIE -pie -Wl,-z,now): g++ hyper.cpp -o hyper -lSDL
-lSDL_ttf -DFHS -Wall -g -lSDL_gfx -g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security
-D_FORTIFY_SOURCE=2 -Wl,-z,relro

bfbtester:

Lots and lots and lots of core dumps due to SIGABRT.

desktop-file-validate:

debian/hyperrogue.desktop: error: value
"hyperbolic;escher;noneuclidean" for locale string list key "Keywords"
in group "Desktop Entry" does not have a semicolon (';') as trailing
character

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


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

Bug#698674: [Pkg-tcltk-devel] Bug#698674: Tcl/Tk multiarching

[Sergei Golovan]

Hi Dmitrijs,

On Tue, Jul 30, 2013 at 6:38 PM, Dmitrijs Ledkovs  wrote:
> To address many of FTBFS bugs, I did in the end introduce a compat
> tclConfig.sh tkConfig.sh in non-multiarch locations for Ubuntu, that
> simply call dpkg-architecture and source the multi-arched variant.

I did copy your approach for packages in experimental. They've stuck
in the new queue for some time, but will go to the archive for testing
eventually.

>
> This solved most of the bugs, but there are still some software that
> either hardcoded locations of the default versioned tk/tcl or, in case
> of ruby, instead of source the configuration file, it tries to read in
> & parse the file by itself.

We'll report bugs for these packages (in fact, I hope that most of the
bugs will be spotted during periodic archive rebuild, after the new
Tcl/Tk will hit sid).

Cheers!
-- 
Sergei Golovan


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

Bug#718343: qtbase-opensource-src: New meta-package depending on all qt5 development packages

[WANA]

Package: qtbase-opensource-src
Version: 5.1.0+dfsg-1
Severity: wishlist

Dear Maintainer,

could you please provide some metapackage depending on or recommending all 
(main) qt5 development packages? This would ease development because you don't 
have to install all *-dev and *-dev-tools packages from ...
 - qtbase-opensource-src
 - qtdeclarative-opensource-src
 - qtgraphicaleffects-opensource-src
 - qtimageformats-opensource-src
 - qtjsbackend-opensource-src
 - qtmultimedia-opensource-src
 - qtquick1-opensource-src
 - qtscript-opensource-src
 - qtsvg-opensource-src
 - qttools-opensource-src
 - qttranslations-opensource-src
 - qtwebkit-opensource-src
 - qtxmlpatterns-opensource-src
 separately.

Some examples i have in mind here are libqt4-dev for qt4 or libboost-all-dev 
for the boost libraries.

Best regards,
Jakob M.

-- System Information:
Debian Release: 7.1
  APT prefers unstable
  APT policy: (650, 'unstable'), (650, 'stable'), (500, 
'testing-proposed-updates'), (500, 'stable-updates'), (500, 'proposed-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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


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

Bug#681512: lightdm: graphic glitches when shutting down (me too)

[Camaleón]

I'm also facing some glitches and oddities with LightDM in wheezy when
shutting down the system. 

Besides the login dialog is quickly displayed (this occurs randomly) the main 
problem I experience is that system restarts instead of powering off (when
pressing the "shutdown" button, of course), while shutting down from 
console (by means of "shutdown -h now" command) always works as expected.

I'm using nvidia VGA card and nouveau driver, on XFCE. 

Curiously enough, on another system (running Wheezy and XFCE) I've never
experienced such problems but this second systems uses the nvidia closed 
source driver.

Greetings,

-- 
Camaleón 


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

Bug#718341: [Aptitude-devel] Bug#71834{1,2}: aptitude install cups-daemon doesn't create 'cupsd.conf' file

[Axel Beckert]

Control: forcemerge 718341 718342
Control: reassign 718341 cups-daemon
Control: tag 718341 + moreinfo

Hi Jeffrey,

JGThomas wrote:
> Due to the pain of CUPS, I needed to reinstall my printers and that
> started with purging CUPS and reinstalling those related packages.

Did you only purge cups-daemon or also all of the also removed
dependencies like e.g. cups-common. By default (and as documented)
neither aptitude nor apt-get purge removed dependencies, too.

At least in Squeeze, cupsd.conf was part of cups-common. And if you
deleted cupsd.conf, then purged cups, but not cups-common, cupsd.conf
won't be recreated on purpose, because it obviously had been deleted
by the administrator on purpose.

See --purge-unused in aptitude's man page for how to configure to also
purge all removed dependencies in case of purging a package. But be
aware: This is a dangerous mode of operation as it can cause data loss
(some packages may also remove data generated by them on purge) and
not the default on purpose.

I suspect that the case in Wheezy and later is similar as there is
_no_ cupsd.conf in any package in neither Wheezy nor Sid nor Jessie.

cups (in Wheezy, cups-daemon in Jessie and Sid) only contains
/etc/cups/cupsd.conf.default which suggests that cupsd.conf is
generated at install time. I though haven't investigated that further.
I'm sure the cups package maintainer knows better and by mind how that
works with the cups-daemon package.

> I backed up the /etc/cups/ folder and ran 'aptitude purge
> cups-daemon', and then tired to install with 'aptitude install cups
> cups-daemon cups-client cups-server-common hplip-cups cups-common'.
> DPKG wasn't able to configure CUPS due to a missing cupsd.conf file
> (which is in the package that aptitude was installing, so it should
> not be missing).

It's not that simple. As explained above, purging just one package
likely does not suffice as it definitely didn't suffice in the past.

> Aptitude should have unpacked the file contents as expected and as
> I've experienced in the past.  The inability of a package manager to
> install necessary files seems like the tool isn't doing its job
> correctly.

No. This issue is very likely not a package manager issue (if it is
one at all). I'm therefore reassigning the issue to cups-daemon.

Nevertheless I'm not sure if it's really a bug as it seems as if not
all necessary packages have been purged before reinstallation.

It though may be a missing feature in the general package format (i.e.
dpkg) as there's currently no way for packages to declare that in case
of purging, a list of its dependencies need to be purged, too, or
similar. If such a feature would be really helpful is another
discussion.

> -- System Information:
> Debian Release: 7.0
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')

JFTR: This doesn't fit: 7.0 is Wheezy/Stable.

> Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)

This also looks more like Wheezy.

Since it's unclear which distribution your're running (or rather which
packages are uptodate as some doesn't seem to be uptodate), please
mention which versions of cups-daemon, cups-client,
cups-server-common, hplip-cups and cups-common you were trying to
reinstall, otherwise the cups maintainer can't really decide which
package versions may be affected (if at all).

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-|  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5


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

Bug#718348: qtbase5-dev: Unable to configure cmake project using qt5 without qtbase5-private-dev

[WANA]

Package: qtbase5-dev
Version: 5.1.0+dfsg-1
Severity: minor

Dear Maintainer,
please consider this minimal cmake project (CMakeLists.txt):

CMAKE_MINIMUM_REQUIRED(VERSION 2.8.9)
SET(QT_MIN_VERSION "5.0.1")
FIND_PACKAGE(Qt5Core ${QT_MIN_VERSION})



With Qt5 (at time of writing 5.1.0+dfsg-1 is in experimental) you will get this 
error, if the package "qtbase5-private-dev" is not installed:

CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Qt5Core/Qt5CoreConfig.cmake:15 
(message):
  The imported target "Qt5::Core" references the file

 "/usr/include/qt5/QtCore/5.1.0"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

 "/usr/lib/x86_64-linux-gnu/cmake/Qt5Core/Qt5CoreConfig.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/Qt5Core/Qt5CoreConfig.cmake:52 
(_qt5_Core_check_file_exists)
  CMakeLists.txt:6 (FIND_PACKAGE)


-- Configuring incomplete, errors occurred!



What i excepted was something like that:

-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/test



I don't know if this behavior was intended. But it might be more intuitive to 
just install qtbase5-dev and everything works out of the box. Perhaps a 
dependency or recommendation in qtbase5-dev on qtbase5-private-dev might help 
here.

Best regards,
Jakob M.


-- System Information:
Debian Release: 7.1
  APT prefers unstable
  APT policy: (650, 'unstable'), (650, 'stable'), (500, 
'testing-proposed-updates'), (500, 'stable-updates'), (500, 'proposed-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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


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

Bug#718346: alt string gets eaten when "too" long

[jidanni]

Package: midori
Version: 0.4.3+dfsg-0.1

Please browse this to see how the ALT string gets eaten when too long.
Title: Dramatic proof how ALT string gets totally eaten when longer
than a certian length




32
34
36
38
40
42
44



I am also reporting this for midori.
I don't think upstream ever fixes this... so I give up hope and write
to downstream...

Bug#718347: bootlogd keeps on running after boot

[jidanni]

Package: bootlogd
Version: 2.88dsf-43
Severity: wishlist

1. Why do these entries persist long after even rc.local has finished?

# pstree -aA|grep boot
  |   |-grep boot
  |-bootlogd -c -l /run/bootlog
  |-startpar -f -- bootlogd

One notes that an /etc/inid.d/bootlogd stop
fixes the problem and finally writes /var/log/boot ...
So there should be a stop action added when one reaches runlevels above 2 etc.

2. Also note the several [Errno 2]s etc. below:

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

Kernel: Linux 3.9-1-486
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages bootlogd depends on:
ii  libc6 2.17-90
ii  lsb-base  4.1+Debian12

bootlogd recommends no packages.

bootlogd suggests no packages.

-- Configuration Files:
/etc/init.d/stop-bootlogd [Errno 2] No such file or directory: 
u'/etc/init.d/stop-bootlogd'
/etc/init.d/stop-bootlogd-single [Errno 2] No such file or directory: 
u'/etc/init.d/stop-bootlogd-single'

-- no debconf information

-- debsums errors found:
sh: /usr/sbin/dpkg-divert: No such file or directory


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

Bug#718345: alt string gets eaten when "too" long

[jidanni]

Package: chromium
Version: 28.0.1500.71-2

Please browse this to see how the ALT string gets eaten when too long.
Title: Dramatic proof how ALT string gets totally eaten when longer
than a certian length




32
34
36
38
40
42
44


I am also reporting this for midori.
I don't think upstream ever fixes this... so I give up hope and write
to downstream...

Bug#718344: GRUB_DEFAULT vs. submenus

[jidanni]

Package: grub2-common
Version: 2.00-15
File: /usr/share/info/grub.info.gz

On # (info "(grub) Simple configuration") there is mentioned

`GRUB_DEFAULT'
 The default menu entry.  This may be a number, in which case
 it...

The problem is that it does not mention how it works in the case of
submenus,

(info "(grub) submenu")

or Debian's submenus, which by the way there is no simple way to turn off.


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

Bug#718349: lintian: Emits malformed-deb-archive on valid deb packages

[Guillem Jover]

Package: lintian
Version: 2.5.15
Severity: wishlist

Hi!

The malformed-deb-archive gets emitted on valid .deb archives as
specified in deb(5) and accepted by dpkg-deb, although those are not
accepted by the Debian archive. It would be nice to separate what's
a trully malformed .deb archive from what's not accepted by Debian,
probably through a profile?

For example the format explicitly supports extra members after the
known ones, and additional members inbetween the known ones as long
as they start with an underscore. Also uncompressed data.tar members
(as mentioned in another bug report).

Thanks,
Guillem


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

Bug#718350: python-mode fails to parse empty triple-quoted strings

[Matthew Vernon]

Package: emacs23-common
Version: 23.4+1-4
Severity: normal
Tags: upstream

Hi,

python-mode fails to parse empty triple-quoted strings properly. Consider the 
following brief example:

--begin example--
#!/usr/bin/env python

def bar():
  """ """
  print "bar"

def foo():
  ""
  print "foo"

if __name__=="__main__":
  foo()
--end example--

If you have syntax highlighting on, then "bar" is highlighted
correctly, but "foo" is not - 'print "foo"' et eq appears highlighted
as if it were part of a string. The parser is failing to handle ""
as an empty triple-quoted string.

Regards,

Matthew

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

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

Versions of packages emacs23-common depends on:
ii  dpkg1.16.10
ii  emacsen-common  2.0.5
ii  install-info4.13a.dfsg.1-10

emacs23-common recommends no packages.

Versions of packages emacs23-common suggests:
pn  emacs23-common-non-dfsg  
pn  emacs23-el   

-- 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#675502: S'il vous plait j'ai besoin de votre aide

[Akbar Sheikh]

Bonjour cher ami

Je vous saluts et aussi votre famille, mon nom est mr .Akbar Sheikh 
gestionnaire de projet et d'echange dans la banque, J’ai une affaire a vous 
proposee; j’ai eu l'occasion a la somme de (us$10,6 millions) pour virer sur 
votre compte pour l'investissement dans votre pays; si vous etes pres a 
m'aider, revenir a moi je vais vous donner plus de details sur la fa?on dont 
l'argent sera transferer a vous.

Vous devez me garantir que tout sera traitee de fa?on confidentielle parce que 
nous n'allons plus souffrir de nouveau dans la vie. Cela fait 10 ans maintenant 
que la plupart des politiciens avides utiliser notre banque pour blanchir de 
l'argent a l'etranger grace a l'aide de leurs conseillers politiques.

La plupart des fonds dont ils ont transferes sur les rivages de l'Afrique, de 
l'or et de l'argent du petrole qui etait cense avoir ete utilise pour 
developper le continent. Leurs conseillers politiques sont toujours gonfle; les 
montants avant de le transferer vers des comptes etrangers j'ai aussi profite 
de l'occasion pour detourner une partie des fonds par consequent, je suis 
conscient qu'il n'y a pas de trace de combien a ete transfere comme tous les 
comptes utilises pour ces transferts ont ete ferme apres le transfert.


J'ai agi a titre d'agent comme de la plupart des politiciens et quand j'ai 
decouvert qu'ils etaient de moi pour reussir dans leur acte gourmand, j'ai 
aussi nettoye une partie de leurs releves bancaires des dossiers de la Banque 
et ils ne se souciait de me demander parce que l'argent etait trop pour eux a 
controler.

Ils blanchirent plus de (US$90 millions) au cours du processus. Comme je vous 
envoie ce message pour vous, j'ai pu detourner dix millions six cent mille 
dollars (US$10,6 millions) sur un compte bloque qui n'appartient a personne a 
la banque.

La banque a hate maintenant de savoir qui est le beneficiaire des fonds parce 
qu'ils ont fait beaucoup de profits avec les fonds. Il y a plus de huit ans 
maintenant que la plupart des politiciens ne sont plus en mesure d’utiliser 
notre banque pour transferer des fonds a l'etranger. Les (US$10,6 millions) a 
ete couche dormant, mais je ne veux pas me retirer de la banque sans avoir  
transferer les fonds dans un compte a l'etranger pour me permettre de partager 
les recettes avec le recepteur.


L'argent sera partage a 60% pour moi et a 40% pour vous. Il n y a pas de 
probleme a ce que quelqu'un vient de vous poser des questions sur les fonds 
parce que j'ai obtenu toutes les informations. S’il vous plait me repondre 
rapidement.

Cordialement,
Mr.Akbar Sheikh
R?ponds moi sur mon email prive : barki_diy...@hotmail.fr


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

Bug#718351: lintian: Use of uninitialized values on bogus .dsc files

[Guillem Jover]

Package: lintian
Version: 2.5.15
Severity: normal

Hi!

lintian does not cope too well with bogus input .dsc files, I found
this out while testing the bogus PGP armored signatures, but forgot
to report it, sorry! Here's a test file and its output:

,--- test.dsc ---
Test: invalid
`---

$ lintian test.dsc
Use of uninitialized value in split at /usr/share/perl5/Lintian/Lab/Entry.pm 
line 297.
Use of uninitialized value $ver in substitution (s///) at 
/usr/share/lintian/collection/diffstat line 50.
Use of uninitialized value $ver in concatenation (.) or string at 
/usr/share/lintian/collection/diffstat line 52.
dpkg-source: error: missing critical source control field Source
internal error: dpkg-source -x failed with status  255 at 
/usr/share/lintian/collection/unpacked line 57
warning: collect info unpacked about package test failed
warning: skipping check of source package test

Thanks,
Guillem


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

Bug#718339: please backport to wheezy

[Joey Hess]

Antoine Beaupré wrote:
> Git annex is pretty amazing, particularly with the git-annex
> assistant. Unfortunately, it is rather complicated to install (or even
> build) under the most recent Debian release (wheezy). Here's what I
> got last I tried:

I've backported many of the haskell libraries git-annex depends on in
the past months. I am now stuck on multiple fronts.

Current status is:

haskell-lens
Test suite fails on multiple architectures, so is not reaching testing.
haskell-dav
Needs lens in testing. Or a rather simple change to not need
this lens stuff, which looks more appealing with every day that
goes on :P
haskell-gnutls
Version in wheezy will sometimes crash with a segfault.
I have made multiple attempts to upload this to backports and
they have all been REJECTED.. except for my last try on Jun
17th, which appears to have gone into limbo instead.
haskell-network-protocol-xmpp
Will need to be rebuilt to use new haskell-gnutls version,
but currently wheezy and testing have the same version;
a new version is tied up in a ghc transition.
It does not seem possible to upload a newer version to
backports until testing has something newer, and I have not
investigated what would be needed to get a binNMU done in
backports.

While it would be possible to build a git-annex backport without XMPP or
WebDAV, these are rather important features.

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#718348: qtbase5-dev: Unable to configure cmake project using qt5 without qtbase5-private-dev

[Sune Vuorela]

On Tuesday 30 July 2013 17:27:59 WANA wrote: 
> With Qt5 (at time of writing 5.1.0+dfsg-1 is in experimental) you will get
> this error, if the package "qtbase5-private-dev" is not installed:

Yep. It is a bug in the cmake files. They are fixed upstream for 5.1.1, iirc. I 
think we will include it in the next upload if we do any more 5.1.0 uploads.
 
> I don't know if this behavior was intended. But it might be more intuitive
> to just install qtbase5-dev and everything works out of the box. 

It is expected that everything works with using the public headers.

> Perhaps a
> dependency or recommendation in qtbase5-dev on qtbase5-private-dev might
> help here.

The private headers is not something you should install under normal 
conditions.

/Sune


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

Bug#718345: [Pkg-chromium-maint] Bug#718345: alt string gets eaten when "too" long

[Pierangelo Mancusi]

this bug happens when the alt string's lenght  is major then the img's
width


2013/7/30 

> Package: chromium
> Version: 28.0.1500.71-2
>
> Please browse this to see how the ALT string gets eaten when too long.
>
> I am also reporting this for midori.
> I don't think upstream ever fixes this... so I give up hope and write
> to downstream...
>
> ___
> Pkg-chromium-maint mailing list
> pkg-chromium-ma...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-chromium-maint
>

Bug#718352: Description word-wraps Python example

[Josh Triplett]

Package: python-bunch
Severity: normal

>From the description of python-bunch:

For instance, you can have the following: >>> b = bunch.bunchify({"foo":"bar"} 
>>> b.foo 'bar'


That example should really go on multiple lines.  See
http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Description
; you can put two spaces at the start of each of those lines to have
them show up verbatim.

Also, the call to bunchify needs a closing parenthesis.

- Josh Triplett

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

Kernel: Linux 3.10-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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#718339: please backport to wheezy

[Colin Watson]

On Tue, Jul 30, 2013 at 11:55:28AM -0400, Joey Hess wrote:
> Antoine Beaupré wrote:
> > Git annex is pretty amazing, particularly with the git-annex
> > assistant. Unfortunately, it is rather complicated to install (or even
> > build) under the most recent Debian release (wheezy). Here's what I
> > got last I tried:
> 
> I've backported many of the haskell libraries git-annex depends on in
> the past months. I am now stuck on multiple fronts.
> 
> Current status is:
> 
> haskell-lens
>   Test suite fails on multiple architectures, so is not reaching testing.

I don't see any test suite failures in haskell-lens that have anything
to do with testing.  It's BD-Uninstallable on architectures without
GHCi, but that's fine.  It should go in with the rest of the GHC
transition once the s390x business is sorted out one way or another.

-- 
Colin Watson   [cjwat...@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#718353: save/game.sav.gz:33309: function or expression too complex

[Sthu]

Package: boswars
Version: 2.7-1
Severity: normal

Dear Maintainer,


On loading saved game i get (in terminal):

/home/user1/.boswars/save/game.sav.gz:33309: function or expression too complex 
near ','
pure virtual method called
terminate called without an active exception


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

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 boswars depends on:
ii  boswars-data  2.7-1
ii  libc6 2.17-7
ii  libgcc1   1:4.8.1-2
ii  libgl1-mesa-glx [libgl1]  9.1.4-1
ii  liblua5.1-0   5.1.5-4
ii  libogg0   1.3.1-1
ii  libpng12-01.2.49-4
ii  libsdl1.2debian   1.2.15-5
ii  libstdc++64.8.1-2
ii  libtheora01.1.1+dfsg.1-3.1
ii  libvorbis0a   1.3.2-1.3
ii  libx11-6  2:1.6.0-1
ii  zlib1g1:1.2.8.dfsg-1

boswars recommends no packages.

boswars 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#718318: [Pkg-javascript-devel] Bug#718318: javascript-common does not install

[Jean-Michel Vourgère]

Apparently, your system is having a dangling symlink
/etc/apache2/conf-available/javascript-common.conf -> 
/etc/javascript-common/javascript-common.conf
that prevents the installation of package javascript-common.

javascript-common has been broken for a while in sid, since apache2.4 is out.
So maybe you created that link yourself by moving the content of conf.d/ into
conf-available/ ?

javascript-common does not create links and has never been creating links in
/etc/apache2/conf-available/
It did create links in /etc/apache2/conf.d/ up to version 8, however.

From which version were you upgrading?
You can probably find that information in logs such as var/log/aptitude,
/var/log/apt/history.log and /var/log/dpkg.


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

Bug#703010: debianutils: ischroot can no longer detect vservers

[Clint Adams]

On Tue, Jul 30, 2013 at 09:00:15PM +1200, Andrew Ruthven wrote:
> Totally agree. The problem is with tools that don't run in a chroot, if
> they are in a chroot, break horribly. Mostly they're stuff run from
> init.d...

I think that's what /usr/sbin/policy-rc.d is for.


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