Bug#732828: mona: use dh-autoreconf to fix FTBFS on ppc64el

[Logan Rosen]

Package: mona
Version: 1.4-13-3
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch

Dear Maintainer,

For the ppc64el architecture in Ubuntu, since this package uses libtool, a full
autoreconf is necessary instead of just config.{sub,guess} updates. This is
because we need new libtool macros for ppc64el.

In Ubuntu, the attached patch was applied to achieve the following:

  * Use dh-autoreconf instead of autotools-dev to fix FTBFS on ppc64el.

Thanks for considering the patch.

Logan Rosen



-- System Information:
Debian Release: wheezy/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 
'trusty'), (100, 'trusty-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12.0-7-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru mona-1.4-13/debian/control mona-1.4-13/debian/control
--- mona-1.4-13/debian/control	2011-05-11 16:19:03.0 -0400
+++ mona-1.4-13/debian/control	2013-12-22 02:21:13.0 -0500
@@ -3,7 +3,7 @@
 Priority: extra
 Maintainer: Debian Science Maintainers 
 Uploaders: Ralf Treinen 
-Build-Depends: debhelper (>= 7.0), bison, flex, autotools-dev, chrpath
+Build-Depends: debhelper (>= 7.0), bison, flex, autotools-dev, chrpath, dh-autoreconf
 Standards-Version: 3.9.2
 Homepage: http://www.brics.dk/~amoeller/mona/index.html
 Vcs-Git: git://git.debian.org/git/debian-science/packages/mona.git
diff -Nru mona-1.4-13/debian/rules mona-1.4-13/debian/rules
--- mona-1.4-13/debian/rules	2011-05-11 16:19:03.0 -0400
+++ mona-1.4-13/debian/rules	2013-12-22 01:54:42.0 -0500
@@ -23,6 +23,7 @@
 ln -s /usr/share/misc/config.guess; };\
  [ -h config.sub ] || { mv config.sub config.sub.upstream; \
 ln -s /usr/share/misc/config.sub; })
+	dh_autoreconf
 	./configure --prefix=/usr CFLAGS=$(OPTFLAGS) CXXFLAGS=$(OPTFLAGS)
 	$(MAKE) CFLAGS=$(OPTFLAGS) CXXFLAGS=$(OPTFLAGS)
 	touch build-stamp
@@ -37,6 +38,7 @@
  [ ! -h  config.sub ] || mv config.sub.upstream config.sub)
 	if [ -e makefile ]; then $(MAKE) distclean; fi
 	-rm build-stamp
+	dh_autoreconf_clean
 	dh_clean
 
 install: build

Bug#732826: Please provide peak.util.proxies

[martin f krafft]

Package: python-peak.util
Version: 20110909-1
Severity: wishlist

It would be great if you could provide peak.util.proxies¹. I am
sorry for filing this against python-peak.util, but it seems like
the best place.

¹) https://pypi.python.org/pypi/ProxyTypes

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

Kernel: Linux 3.11-2-amd64 (SMP w/4 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 python-peak.util depends on:
ii  python   2.7.5-5
ii  python-peak.util.decorators  1.8-2
ii  python-support   1.0.15

python-peak.util recommends no packages.

python-peak.util 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#732205: Also happening on powerpc in Ubuntu

[Logan Rosen]

Just wanted to note that this same FTBFS is happening on powerpc in Ubuntu:
https://launchpad.net/ubuntu/+source/lives/2.2.0~ds0-1/+build/5312356

Bug#732827: RM: partman-ext2r0 -- ROM; No longer used in the installer

[Christian Perrier]

Package: ftp.debian.org
Severity: normal


As stated by Martin Michlmayr in debian-boot:

==
I just removed support for Cobalt devices from the installer as these
devices are extremely old now and there are problems with the boot
loader.

We still have partman-ext2r0.  This package was created to generate a
revision 0 ext2 filesystem, which is required to boot on 2 systems:
Netwinder (ARM) and Cobalt (MIPS).

Neither Netwinder nor Cobalt devices are supported by the installer
anymore, so I suggest we remove partman-ext2r0.  Any objections?
==


As a consequence, the partman-ext2r0 package that only produces udeb
packages for D-I can be safely removed from unstable and testing.


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

Bug#732825: provides "grass643" , however qgis-plugin-grass depends from "grass642"

[Joseba Goitia]

Package: grass-core
Version: 6.4.3-3
Severity: important
Tags: upstream

Dear maintainer:

Grass-core provides  "grass643" virtual package. On the other
side, qgis-plugin-grass depends from "grass642" witch is provided by grass-core
package, in the previous version, actually in testing. Broken dependencies i
suppose.

other packages i found with the same "grass642" dependency
libgdal1-1.9.0-grass.

Many thanks for your time.



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

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

Versions of packages grass-core depends on:
ii  libc6 2.17-97
ii  libcairo2 1.12.16-2
ii  libfftw3-double3  3.3.3-7
ii  libfontconfig12.11.0-2
ii  libfreetype6  2.5.1-2
ii  libgcc1   1:4.8.2-10
ii  libgdal1h 1.10.1+dfsg-2
ii  libgeos-3.4.2 3.4.2-1
ii  libgeos-c13.4.2-1
ii  libgl1-mesa-glx [libgl1]  9.2.2-1
ii  libglu1-mesa [libglu1]9.0.0-2
ii  libice6   2:1.0.8-2
ii  libmysqlclient18  5.5.33+dfsg-1
ii  libncurses5   5.9+20130608-1
ii  libodbc1  2.3.1-1
ii  libpng12-01.2.49-5
ii  libpq59.3.2-1
ii  libproj0  4.8.0-2
ii  libreadline6  6.2+dfsg-0.1
ii  libsm62:1.2.1-2
ii  libsqlite3-0  3.8.2-1
ii  libstdc++64.8.2-10
ii  libtiff5  4.0.3-6
ii  libtinfo5 5.9+20130608-1
ii  libx11-6  2:1.6.2-1
ii  libxext6  2:1.3.2-1
ii  libxrender1   1:0.9.8-1
ii  python-numpy  1:1.7.1-3
pn  python:any
ii  zlib1g1:1.2.8.dfsg-1

Versions of packages grass-core recommends:
pn  gdal-bin  
pn  proj-bin  

Versions of packages grass-core suggests:
pn  avce00   
ii  curl 7.34.0-1
pn  e00compr 
pn  gnuplot  
pn  gpsbabel 
pn  gpstrans 
pn  grass-dev
ii  grass-doc6.4.3-3
ii  grass-gui6.4.3-3
pn  netpbm   
pn  python-rpy2  
ii  wget 1.14-5
pn  xml2 

-- 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#732824: judy: use autotools-dev to update config.{sub,guess} for new arches

[Logan Rosen]

Package: judy
Version: 1.0.5-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch

Dear Maintainer,

Please use autotools-dev to update config.{sub,guess} for new architectures.
For example, we needed these updates in Ubuntu for the new arm64 and ppc64el
architectures.

In Ubuntu, the attached patch was applied to achieve the following:
  * Use autotools-dev to update config.{sub,guess} for new arches.

Thanks for considering the patch.
Logan Rosen



-- System Information:
Debian Release: wheezy/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 
'trusty'), (100, 'trusty-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12.0-7-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -u judy-1.0.5/debian/control judy-1.0.5/debian/control
--- judy-1.0.5/debian/control
+++ judy-1.0.5/debian/control
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Troy Heber 
 Uploaders:
-Build-Depends: debhelper (>> 4.0.0)
+Build-Depends: debhelper (>> 4.0.0), autotools-dev
 Standards-Version: 3.7.2.2
 
 Package: libjudy-dev
diff -u judy-1.0.5/debian/rules judy-1.0.5/debian/rules
--- judy-1.0.5/debian/rules
+++ judy-1.0.5/debian/rules
@@ -21,6 +21,7 @@
 configure-stamp:
 	dh_testdir
 	# Add here commands to configure the package.
+	dh_autotools-dev_updateconfig
 	./configure --prefix=/usr --mandir=/usr/share/man
 
 	touch configure-stamp
@@ -43,7 +44,7 @@
 
 	# Add here commands to clean up after the build process.
 	-$(MAKE) distclean
-
+	dh_autotools-dev_restoreconfig
 	dh_clean
 
 install: build

Bug#732823: xmms2-client-cli: segfault when dealing with long pathnames

[Tim Connors]

Package: xmms2-client-cli
Version: 0.8+dfsg-4
Severity: normal

I originally thought this was a UTF-8 bug, but now it looks like a
pathname length issue to me:

> xmms2 add "/home/tconnors/mp3/Classical/Benjamin Godard, Chloë Hanslip 
> (violin), Slovak Radio Symphony Orchestra, Kirk Trevor - Godard - Concerto 
> Romantique, op46 - Violin Concerto No2, op131 - Scènes Poétiques, op46 - 
> Hanslip-Trevor/01 - Violin Concerto No2, op131 - I Allegro moderato.flac"
Segmentation fault

And I suspect 'xmms2 add' includes the full pathname when talking to
the server (duh, of course it does), because I can be in that
directory, and add just the file, and it still crashes.

Note that the directory is less than 256 chars, and the total length
is more than 256.

If I shorten the parent directory name by a number of characters, then
some files (the shorter ones) work, and some fail - but the total
pathname length is still greater than 256 chars.  The boundary seems
to be at 272 characters working, 273 failing.  If I shorten the
pathname so they're all under 272 chars, then all the files work.

> pwd | wc
  1   2 215
> for i in * ; do xmms2 add "$i" && echo -n +"$(pwd)/$i" || echo -n 
> -"$(pwd)/$i" ; realpath "$i" | wc ; echo ; done
Segmentation fault
-/home/tconnors/mp3/Classical/Benjamin 
GodardBenaaa/01
 - Violin Concerto No2, op131 - I Allegro moderato.flac  1  11 273

Segmentation fault
-/home/tconnors/mp3/Classical/Benjamin 
GodardBenaaa/02
 - Violin Concerto No2, op131 - II Adagio quasi andante.flac  1  12 
278

Segmentation fault
-/home/tconnors/mp3/Classical/Benjamin 
GodardBenaaa/03
 - Violin Concerto No2, op131 - III Allegro non troppo.flac  1  12 
277

+/home/tconnors/mp3/Classical/Benjamin 
GodardBenaaa/04
 - Concerto Romantique, op35 - I Allegro moderato.flac  1  10 272

Segmentation fault
-/home/tconnors/mp3/Classical/Benjamin 
GodardBenaaa/05
 - Concerto Romantique, op35 - II Adagio non troppo.flac  1  11 274

Segmentation fault
-/home/tconnors/mp3/Classical/Benjamin 
GodardBenaaa/06
 - Concerto Romantique, op35 - III Canzonetta-Allegretto moderato.flac  1   
   10 288

+/home/tconnors/mp3/Classical/Benjamin 
GodardBenaaa/07
 - Concerto Romantique, op35 - IV Allegro molto.flac  1  10 270

+/home/tconnors/mp3/Classical/Benjamin 
GodardBenaaa/08
 - Scènes Poétiques, op46 - I Dans les bois.flac  1  11 268

+/home/tconnors/mp3/Classical/Benjamin 
GodardBenaaa/09
 - Scènes Poétiques, op46 - II Dans les champs.flac  1  11 271

+/home/tconnors/mp3/Classical/Benjamin 
GodardBenaaa/10
 - Scènes Poétiques, op46 - III Sur la montagne.flac  1  11 272

+/home/tconnors/mp3/Classical/Benjamin 
GodardBenaaa/11
 - Scènes Poétiques, op46 - IV Au village.flac  1  10 266



-- System Information:
Debian Release: 7.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (5, 'testing'), (2, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)

Bug#732822: jansson: use dh-autoreconf instead of autotools-dev to fix FTBFS on ppc64el

[Logan Rosen]

Package: jansson
Version: 2.5-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch

Dear Maintainer,

For the ppc64el architecture in Ubuntu, since this package uses libtool, a full
autoreconf is necessary instead of just config.{sub,guess} updates with
autotools-dev.

In Ubuntu, the attached patch was applied to achieve the following:

  * Use dh-autoreconf instead of autotools-dev to fix FTBFS on ppc64el.

Thanks for considering the patch.

Logan Rosen



-- System Information:
Debian Release: wheezy/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 
'trusty'), (100, 'trusty-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12.0-7-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru jansson-2.5/debian/control jansson-2.5/debian/control
--- jansson-2.5/debian/control	2013-09-20 04:45:06.0 -0400
+++ jansson-2.5/debian/control	2013-12-22 00:52:12.0 -0500
@@ -2,7 +2,7 @@
 Priority: optional
 Maintainer: Alessandro Ghedini 
 Build-Depends: debhelper (>= 9),
- autotools-dev
+ dh-autoreconf
 Build-Depends-Indep:
  python-sphinx (>= 1.0)
 Standards-Version: 3.9.4
diff -Nru jansson-2.5/debian/rules jansson-2.5/debian/rules
--- jansson-2.5/debian/rules	2013-09-20 04:45:06.0 -0400
+++ jansson-2.5/debian/rules	2013-12-22 00:28:44.0 -0500
@@ -2,7 +2,7 @@
 #export DH_VERBOSE=1
 
 %:
-	dh $@ --with=autotools-dev
+	dh $@ --with=autoreconf
 
 override_dh_auto_build:
 	dh_auto_build

Bug#730493: new release of QIV (v2.3.1)

[Andy Spiegl]

Hi,

fyi, version 2.3.1 of qiv was just released.

You can find the new version here:
 http://qiv.spiegl.de/download


Thanks to all contributors, especially Thomas Wiegner!
 Andy.


PS: Changes from 2.3 to 2.3.1:

  25.11.2013[tw] Add libXext to libraries for linking in Makefile.
 Fixes build problems on some distributions.


-- 
 "Barack me Obamadeus"   (http://xkcd.com/)


signature.asc
Description: Digital signature

Bug#618273: gambc has been orphaned

[Geoffrey Thomas]

tags 618273 - pending
thanks

The 2011 comment about a pending upload was from the previous maintainer, 
but this package was orphaned in 2012 ( http://bugs.debian.org/677709 ) 
due to lack of activity from that maintainer. So I'm untagging it as 
pending upload, for now, so that this bug's status is clearer.


Jackson Doak is working on taking over maintenance and has a 
slightly-newer version on mentors:

http://mentors.debian.net/package/gambc

It looks like it hasn't gotten any (nontrivial) reviews. I have a bunch of 
other pending Debian work that I'd like to get to over Christmas break, 
but if I get all of that done, I'm happy to take a look -- for whatever my 
review is worth, since I'm not a DD either. I talked to Jackson on IRC 
yesterday and he said that he's having trouble getting the current 
upstream release to build. I recall having trouble with this too last time 
I saw him mention it on IRC.


--
Geoffrey Thomas
http://ldpreload.com
geo...@ldpreload.com


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

Bug#707214: refpolicy: Please handle new dpkg_script_t execution context

[Guillem Jover]

Hi!

On Sun, 2013-12-22 at 02:26:44 +0100, Laurent Bigonville wrote:
> I quickly tried, and when the package is installed (dpkg -i) the
> maintainer script is properly transitioned to "dpkg_script_t".

Ah, good.

> dpkg-reconfigure is OTOH not transitioning the maintainer script to its
> own context, I guess it also should be the case here?

Right, a bug would need to be filed for debconf. You are probably in a
better position to file it, and test possible implementations, would
you mind?

> Otherwise I think that the policy already has support for the
> dpkg_script_t execution context, or did you had something specific in
> mind?

Yeah, but it seemed incomplete/partial or just with some workarounds
to handle the missing dpkg_script_t support in dpkg. See for example
the TODO item or the “Use named file transition to fix this” commend
in «policy/modules/contrib/dpkg.te». Maybe there's other things that
could be improved or refined now in the policy? I don't know. :)

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#732821: ocl-icd: Use autoreconf instead of autotools-dev to allow rebuildability

[Wookey]

Source: ocl-icd
Version: 2.1.0
Severity: normal
Tags: patch

I spent a while trying to build the unstable version on unstable, discovering 
the AM_PROG_AR bug 71 and then the
test bug 700398, before realising that there was a newer version that already 
fixed all this in experimental.

During that process I discovered that this package will only ever build once 
after unpacking. Because it does an autoreconf, 
and thus a load of autotools files get overwritten with new verions, and it is 
a dpkg quilt-format package: dpkg 
fails on the second build, pointing out the huge patch of changed source files.

This is very simply fixed by the attached patch which uses dh-autoreconf, 
instead of the dh_autotools-dev that 
was already in use, to track all the changed autotools files, and not just 
config.sub/guess, so that the source 
can be restored to its pristine state in the clean rule.

This works nicely.

Rebuildability is important, especially for porters, and in this case is very 
easy to preserve. Please include 
this in the next upload. (Can the experimental version be uploaded to unstable 
now BTW - that would be very helpful?)

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

Kernel: Linux 3.2.0-kvm-i386-20110111 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
diff -Nru ocl-icd-2.1.0/debian/changelog ocl-icd-2.1.0/debian/changelog
--- ocl-icd-2.1.0/debian/changelog	2013-10-02 14:25:10.0 +
+++ ocl-icd-2.1.0/debian/changelog	2013-12-22 03:24:45.0 +
@@ -1,3 +1,9 @@
+ocl-icd (2.1.0-1arm64) unstable; urgency=low
+
+  * Use dh-autoreconf so package is rebuildable
+
+ --Sun, 22 Dec 2013 03:23:36 +
+
 ocl-icd (2.1.0-1) experimental; urgency=low
 
   * New upstream release
diff -Nru ocl-icd-2.1.0/debian/control ocl-icd-2.1.0/debian/control
--- ocl-icd-2.1.0/debian/control	2013-10-02 14:25:10.0 +
+++ ocl-icd-2.1.0/debian/control	2013-12-22 03:22:18.0 +
@@ -2,7 +2,7 @@
 Priority: extra
 Maintainer: Vincent Danjean 
 Build-Depends: debhelper (>= 9.0.0), opencl-headers (>= 1.2), ruby,
- autotools-dev (>=20100122.1~),
+ dh-autoreconf,
  autoconf (>=2.68), automake (>=1:1.10), libtool,
  asciidoc, xmlto
 Standards-Version: 3.9.4
diff -Nru ocl-icd-2.1.0/debian/rules ocl-icd-2.1.0/debian/rules
--- ocl-icd-2.1.0/debian/rules	2013-10-02 14:25:10.0 +
+++ ocl-icd-2.1.0/debian/rules	2013-12-22 03:22:09.0 +
@@ -10,7 +10,7 @@
 #export DH_VERBOSE=1
 
 %:
-	dh $@ --parallel --with autotools_dev
+	dh $@ --parallel --with autoreconf
 
 .PHONY: override_dh_auto_configure
 override_dh_auto_configure:

Bug#732820: O: libpdf-fdf-simple-perl -- Perl module to read and write (Acrobat) FDF files

[Axel Beckert]

Package: wnpp
Severity: normal

Hi,

the maintainer of libpdf-fdf-simple-perl isn't active anymore, so I
hereby orphan this package.

Current package description:

Perl module to read and write (Acrobat) FDF files

Helps creating and extracting the content of FDF files. It is meant to
be a simple replacement for the Adobe FdfToolkit. Therefore some of it's
behavior, especially handling of diverse whitespace/newline artefacts is
orientated on FdfToolkit's handling.

After the extraction process the content is available within a hash
reference.

For creating FDF files it currently only supports setting text
values. Anyway, this should be enough to create FDF files for text
fields, text areas, checkboxes and radio buttons.

PDF::FDF::Simple uses Parse::RecDescent and understands both, the "Kids"
notation and the "dotted" notation for field names. Saving will always
use the "dotted"- notation.

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#732753: xserver-xorg-video-intel: Backlight changes very slow in gnome, server picks "wrong" interface

[Matthew Gabeler-Lee]

On 2013-12-21 09:38, Julien Cristau wrote:

Please report this upstream at bugs.freedesktop.org following the
instructions at
https://01.org/linuxgraphics/documentation/how-report-bugs and let us
know the bug number for tracking.


I've submitted https://bugs.freedesktop.org/show_bug.cgi?id=72959


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

Bug#732819: fontconfig-config: Upgrading from 2.9.0-7 doesn't change /etc/fonts/fonts.conf which leads to misconfiguration

[Ilia Lilov]

Package: fontconfig-config
Version: 2.10.2-2
Severity: serious
Justification: 3

Upgrading from 2.9.0-7 to 2.10 or 2.11 doesn't prompts to change 
/etc/fonts/fonts.conf and doesn't point to possible problem with keeping old 
fonts.conf version, although comment in the file says "IT WILL BE REPLACED WHEN 
FONTCONFIG IS UPDATED".
Not updating fonts.conf leads to the following: "sans", "serif", "monospace" 
and possibly other match queries to fontconfig return unpredictable font faces, 
which can be even serif face for "sans" query etc. They are unpredictable but 
the same for every query, so no "font-blinking" effect, just ugly, 
inappropriate faces everywhere (in Mate DE in my case). Some of them is taken 
from my ~/.fonts directory, although there are only "art" faces there, and they 
aren't included in any fontconfig config file by me.

I've got this bug twice on two different Debian installations: at home and at 
the office, and both times i spent almost full-day to find a way to fix it. 
Interestingly, downgrading to previously installed fontconfig version didn't 
fix the bug both times.
Finnaly, I found a way to fix the problem, just needed to remove the following 
sections from /etc/fonts/fonts.conf :






mono


monospace






sans serif


sans-serif






sans


sans-serif





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

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

Versions of packages fontconfig-config depends on:
ii  debconf [debconf-2.0]  1.5.46
ii  fonts-freefont-ttf [ttf-freefont]  20120503-1
ii  ttf-dejavu-core2.33+svn2514-3
ii  ucf3.0025+nmu3

fontconfig-config recommends no packages.

fontconfig-config suggests no packages.

-- Configuration Files:
/etc/fonts/fonts.conf changed:





/usr/share/fonts
/usr/X11R6/lib/X11/fonts /usr/local/share/fonts
fonts

~/.fonts

/etc/fonts/conf.d

/var/cache/fontconfig
fontconfig

~/.fontconfig



0x0020   
0x00A0   
0x00AD   
0x034F   
0x0600   
0x0601   
0x0602   
0x0603   
0x06DD   
0x070F   
0x115F   
0x1160   
0x1680   
0x17B4   
0x17B5   
0x180E   
0x2000   
0x2001   
0x2002   
0x2003   
0x2004   
0x2005   
0x2006   
0x2007   
0x2008   
0x2009   
0x200A   
0x200B   
0x200C   
0x200D   
0x200E   
0x200F   
0x2028   
0x2029   
0x202A   
0x202B   
0x202C   
0x202D   
0x202E   
0x202F   
0x205F   
0x2060   
0x2061   
0x2062   
0x2063   
0x206A   
0x206B   
0x206C   
0x206D   
0x206E   
0x206F   
0x2800   
0x3000   
0x3164   
0xFEFF   
0xFFA0   
0xFFF9   
0xFFFA   
0xFFFB   



30





-- debconf information excluded


-- 
To U

Bug#732818: apt: Doesn't autoremove kernels

[Mattthew Gabeler-Lee]

Package: apt
Version: 0.9.12.1
Severity: normal

The kernel postinst script creates an autoremove override conf file to
protect recent kernels.  But kernels that were automatically installed and
not protected by those rules are still not autoremoved.

This appears to be caused by linux-firmware-* packages suggesting
linux-image:amd64, and that metapackage being resolved to *all* the kernels
I have installed, instead of just the latest one, and thus no kernel is ever
autoremoved.

$ apt-show-versions -r -p linux-image | grep -v 'not installed'
linux-image-3.10-2-amd64:amd64 3.10.7-1 installed: No available version in 
archive
linux-image-3.10-3-amd64:amd64 3.10.11-1 installed: No available version in 
archive
linux-image-3.11-2-amd64:amd64/testing 3.11.10-1 uptodate
linux-image-amd64:amd64/testing 3.11+54 uptodate

$ sudo apt-get -oDebug::pkgAutoRemove=Yes autoremove | fgrep linux-image-3.10-2
Auto-Installed : linux-image-3.10-2-amd64:amd64
AutoDep: linux-image-3.10-2-amd64:amd64
Following dep: firmware-linux-free:amd64 3.2 Suggests linux-image:amd64 , 
provided by linux-image-3.10-2-amd64:amd64 3.10.7-1
Marking: linux-image-3.10-2-amd64:amd64 3.10.7-1, Curr=3.10.7-1, Inst=3.10.7-1
...
(This repeats for some other firmware-linux-* packages)

I'm not sure, but this sounds like it might be related to #557328

-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "0";
APT::Install-Suggests "0";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^kfreebsd-image.*";
APT::NeverAutoRemove:: "^gnumach$";
APT::NeverAutoRemove:: "^gnumach-image.*";
APT::NeverAutoRemove:: "^linux-image-3.10-3-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-3.10-3-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-3.10-3-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-3.10-3-amd64$";
APT::NeverAutoRemove:: "^linux-headers-3.10-3-amd64$";
APT::NeverAutoRemove:: "^linux-image-3.11-2-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-3.11-2-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-3.11-2-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-3.11-2-amd64$";
APT::NeverAutoRemove:: "^linux-headers-3.11-2-amd64$";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Never-MarkAuto-Sections:: "oldlibs";
APT::Never-MarkAuto-Sections:: "restricted/oldlibs";
APT::Never-MarkAuto-Sections:: "universe/oldlibs";
APT::Never-MarkAuto-Sections:: "multiverse/oldlibs";
APT::Periodic "";
APT::Periodic::Enable "1";
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Download-Upgradeable-Packages "1";
APT::Periodic::AutocleanInterval "7";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "test -x /usr/bin/apt-show-versions || exit 
0 ; apt-show-versions -i";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e 
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && 
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call 
--system --dest org.freedesktop.PackageKit --object-path 
/org/freedesktop/PackageKit --timeout 1 --method 
org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo 
> /dev/null";
APT::Default-Release "testing";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Architectures:: "i386";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "1";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension ".gz";
APT::Compressor::gzip::Binary "gzip";
APT::Compressor::gzip::Cost "2";
APT::Compressor::gzip::CompressArg "";
APT::Compressor::gzip::CompressArg:: "-9n";
APT::Compressor::gzip::UncompressArg "";
APT::Compressor::gzip::UncompressArg:: "-d";
APT::Compressor::bzip2 "";
APT::Compressor::bzip2::Name "bzip2";
APT::Compressor::bzip2::Extension ".bz2";
APT::Compressor::bzip2::Binary "bzip2";
APT::Compressor::bzip2::Cost "3";
APT::Compressor::bzip2::CompressArg "";
APT::Compressor::bzip2::CompressArg:: "-9";
APT::Compressor::bzip2::UncompressArg "";
APT::Compressor::bzip2::UncompressArg:: "-d";
APT::Compressor::xz "";
APT::Compressor::xz::Name "xz";
APT::Compressor::xz::Extension ".xz";
APT::Compressor::xz::Binary "xz";
APT::Compressor::xz::Cost "4";
APT::Compressor::xz::CompressArg "";
APT::Compressor::xz::CompressArg:: "-6";
APT::Compressor::xz::UncompressArg "";
APT::Compressor::xz::UncompressArg:: "-d";
APT::Compressor::lzma "";
APT::Compressor::lzma::Name "lzma";
APT::Compressor::lzma::Extens

Bug#732623: [Pkg-systemd-maintainers] Bug#732623: [Pkg-xfce-devel] Bug#732623: lightdm-gtk-greeter: Hibernate and Restart buttons disappear after first login/logout

[Vincent Lefevre]

On 2013-12-22 02:20:15 +0100, Michael Biebl wrote:
> Am 22.12.2013 00:12, schrieb Vincent Lefevre:
> > When I upgraded my second machine yesterday, I noticed that both
> > libpam-systemd and systemd had been installed, so that I thought
> > the bug was related to one of them. So, I did some tests to see
> > what minimal change triggered the problem, and it was not due to
> > libpam-systemd (which depends on systemd), but to systemd itself.
> > That's why I've reassigned the bug to systemd.
> 
> I'm not convinced the bug is in systemd and the package is clearly not
> unrelated (as lightdm  has systemd specific code) so the severity is
> incorrect.

OK, though this is more complex than that. I didn't install systemd
to use systemd, but just because systemd was installed as an indirect
dependency of some GNOME tool (actually for this reason, the only
solution would be that lightdm had code to optionally disable systemd
support on its side).

> It's very well possible that it's lightdm which has broken logind
> specific. Hard to tell with this little information.

I suppose that the calls related to systemd are:

r = login1_call_function ("CanSuspend", NULL, NULL);
r = login1_call_function ("CanHibernate", NULL, NULL);
r = login1_call_function ("CanReboot", NULL, NULL);
r = login1_call_function ("CanPowerOff", NULL, NULL);

and their handling is the same. Two of them work (CanSuspend and
CanPowerOff), but not the other two (CanHibernate and CanReboot).
Unless some names are incorrect, there seems to be at least an
inconsistency on systemd's side.

Otherwise is there a way to do a test of logind from the shell
such as querying the status of these features?

-- 
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#732006: uscan: broken handling of filenames with whitespace

[James McCoy]

Control: tag -1 pending

On Sun, Dec 22, 2013 at 01:17:01AM +0100, Stig Sandbeck Mathisen wrote:
> I've pushed a proposed fix for this security issue to the packaging
> repo git://anonscm.debian.org/collab-maint/devscripts.git as the
> branch CVE-2013-7085-ruin-someones-yuletide

Thanks for the patch.  We've addressed this by other means and are just
pending some final review before uploading.

> The change also fixes a second bug, where one could not exclude a
> non-empty top level directory, but had to use "somedirectory/*".

Thanks for noticing that.  I've made a change for this as well.

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy 


signature.asc
Description: Digital signature

Bug#732689: Please advise, bug #732689: ipset: kernel panic when adding ip to bitmap:ip

[Neutron Soutmun]

On Sun, Dec 22, 2013 at 9:29 AM, Ben Hutchings  wrote:

> I'll look at whether this fix can be backported.

Thanks a lot


signature.asc
Description: PGP signature

Bug#732689: Please advise, bug #732689: ipset: kernel panic when adding ip to bitmap:ip

[Ben Hutchings]

Control: reassign -1 src:linux 3.2.51-1
Control: fixed -1 3.7.1-1~experimental.1
Control: tag -1 upstream fixed-upstream patch

On Sun, 2013-12-22 at 08:59 +0700, Neutron Soutmun wrote:
> Hello,
> 
>   I'm the ipset package maintainer. As per the Bug [1], I found that is
> has been fixed upstream later of the linux 3.2 release, see [2].
> 
>   Please advise, how to properly fix this issue.
> 
> Best regards,
> Neutron Soutmun
> 
> [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732689 - ipset: kernel 
> panic when adding ip to bitmap:ip
> [2] 
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b9fed748185a96b7cfe74afac4bd228e8af16f01
>  

I'll look at whether this fix can be backported.

Ben.

-- 
Ben Hutchings
If at first you don't succeed, you're doing about average.


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

Bug#724869: base: Deadkeys do not work in Xorg French canadian keyboard

[James Brookes]

On 18/12/13 08:17 AM, Anton Zinoviev wrote:
> On Tue, Dec 17, 2013 at 09:31:14PM -0500, James Brookes wrote:
>> I solved the problem by selecting xim with im-config.
>> The default wheezy installation was giving 2 valid choices, here is an
>> extractfrom im-config:
>>
>> Current configuration for the input method:
>>  * Active configuration: xim (normally missing)
>>  * Automatic configuration: uim (normally ibus or fcitx or uim)
>>  * Number of valid choices: 2 (normally 1)
>> The configuration set by im-config is activated by re-starting X.
>> Explicit selection is not required to enable the automatic configuration
>> if the active one is default/auto/cjkv/missing.
>>   Available input methods: uim xim
>> Unless you really need them all, please make sure to install only one
>> input method tool.
> In order to see if this bug belongs to console-setup one has to check 
> the contents of /etc/config/keyboard.  Is it correct?  If it isn't then 
> the bug belongs to console-setup.  Otherwise it doesn't.  Please send us 
> the content of this file.
>
> Anton Zinoviev

There is no existing file named /etc/config/keyboard,

But there is a file named  /etc/default/keyboard, here is the content:
# KEYBOARD CONFIGURATION FILE

# Consult the keyboard(5) manual page.

XKBMODEL="pc105"
XKBLAYOUT="ca"
XKBVARIANT=""
XKBOPTIONS=""

BACKSPACE="guess"

>  
>
>


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

Bug#732815: mtpfs

[Volker Wysk]

When I unplug the smartphone's USB cable, and plug it again, before I call 
mtpfs, then the messages are slightly different:

~ $ mtpfs /mnt/android/
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
   Found 1 device(s):
   Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 8
Attempting to connect device
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, 
trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0


The line "ignoring..." replaces the line "PTP_ERROR_IO...".

Bye,
V


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

Bug#732689: ipset: kernel panic when adding ip to bitmap:ip

[Neutron Soutmun]

It has been fixed in mainline kernel also.

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b9fed748185a96b7cfe74afac4bd228e8af16f01


Regards,
Neutron Soutmun

On Sun, Dec 22, 2013 at 8:38 AM, Neutron Soutmun  wrote:
> Hello,
>
> This issue has been fixed upstream (ipset kernel part), see [1], which
> is not included in the 3.2 kernel of Wheezy.
>
> I'll ask the Debian Kernel Team how to properly fix this issue.
>
> [1] Check and reject crazy /0 input parameters -
> http://git.netfilter.org/ipset/commit/kernel/net/netfilter/ipse/ip_set_bitmap_ip.c?id=a1cbbc8f86a8ef955708d48f20f8ca021a0a7641
>
> On Fri, Dec 20, 2013 at 6:45 PM, Mi  wrote:
>> Package: ipset
>> Version: 6.12.1-1
>> Severity: important
>>
>>
>> # ipset create ipv4_ch bitmap:ip range 0.0.0.0/0
>> # ipset list
>> [ another previously defined hash:net set. No problem with that. ]
>>
>> Name: ipv4_ch
>> Type: bitmap:ip
>> Header: range 0.0.0.0-255.255.255.255
>> Size in memory: 120
>> References: 0
>> Members:
>>
>> # ipset add ipv4_ch 5.1.96.0/21
>>
>> Message from syslogd@pe1 at Dec 20 12:14:53 ...
>>  kernel:[3088568.395819] Oops: 0002 [#1] SMP
>>
>> Message from syslogd@pe1 at Dec 20 12:14:53 ...
>>  kernel:[3088568.398495] Stack:
>>
>> Message from syslogd@pe1 at Dec 20 12:14:53 ...
>>  kernel:[3088568.398495] Call Trace:
>>
>> Message from syslogd@pe1 at Dec 20 12:14:53 ...
>>  kernel:[3088568.398495] Code: 31 c0 48 85 ff 74 19 48 81 ff ff ff ff 7f b0 
>> 01 74 0e 48 8b 05 e7 af 1e e1 48 29 f8 48 c1 e8 3f c3 48 8b 47 40 0f b7 16 
>> 48 8b 00  0f ab 10 19 d2 83 fa 01 19 c0 f7 d0 25 f9 ef ff ff c3 48 8b
>>
>> Message from syslogd@pe1 at Dec 20 12:14:53 ...
>>  kernel:[3088568.398495] CR2: 0c10
>>
>> Message from syslogd@pe1 at Dec 20 12:14:53 ...
>>  kernel:[3088568.428341] Kernel panic - not syncing: Fatal exception in 
>> interrupt
>>
>>
>> That's all. The machine hung completely and needed a hard reset.
>>
>>
>>
>> -- System Information:
>> Debian Release: 7.3
>>   APT prefers stable-updates
>>   APT policy: (500, 'stable-updates'), (500, 'stable')
>> Architecture: amd64 (x86_64)
>> Foreign Architectures: i386
>>
>> 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 ipset depends on:
>> ii  iptables   1.4.14-3.1
>> ii  libc6  2.13-38
>> ii  libipset2  6.12.1-1
>>
>> ipset recommends no packages.
>>
>> ipset 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#732817: wine64: different alternatives not provided (32 vs 64 bit)

[Drew Parsons]

Package: wine64
Version: 1.6.1-6
Severity: normal

wine32 and wine64 are now distinct packages with different filepaths
allowing them to be installed concurrently.  They provide distinct
binaries, /usr/lib/i386-linux-gnu/wine/bin/wine32 and
/usr/lib/x86_64-linux-gnu/wine/bin/wine64

The packages have some kind of alternatives support to provide
/usr/bin/wine.

But at any one time, only one of wine32 or wine64 can be configured to
provide /usr/bin/wine.  update-alternatives fails to select the
preferred wine:
  $ sudo update-alternatives --config wine
  There is only one alternative in link group wine (providing /usr/bin/wine): 
/usr/lib/x86_64-linux-gnu/wine/bin/wine
  Nothing to configure.

The only way to reconfigure the alternative wine is with dpkg-reconfigure
wine64 or dpkg-reconfigure wine32.

I think this must be an incorrect handling of the alternatives
infrastructure.  wine32 and wine64 should both operate as alternatives
for /usr/bin/wine at the same time, not so?

Another thing odd in the wine alternatives is the handling of
/usr/bin/wine32 and /usr/bin/wine64.  After dpkg-reconfigure is run
(fixing /usr/bin/wine to wine32 or wine64), then only one of
/usr/bin/wine32 or /usr/bin/wine64 appears (the one for the package, wine32 or
wine64, that you just reconfigured).

The expected behaviour (with both wine32 and wine64 installed at the
same time) is :
1) "update-alternatives --config wine" allows selection between wine32
and wine64 for /usr/bin/wine
2) Both /usr/bin/wine32 and /usr/bin/wine64 exist at the same time
(We'd expect only one alternative for each of them, unless specific
wine*-unstable packages are also installed)



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

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

Versions of packages wine64 depends on:
ii  libc6  2.17-97
ii  libwine1.6.1-6
ii  libwine-gecko-1.4  1.4+dfsg1-3
ii  x11-utils  7.7+1

wine64 recommends no packages.

wine64 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#732803: firmware-iwlwifi: Unstable Wi-fi Signal in Samsung Chronos 7

[Ben Hutchings]

Control: tag -1 moreinfo

On Sat, 2013-12-21 at 19:31 -0200, Gustavo Dias do Nascimento wrote:
> Package: firmware-iwlwifi
> Version: 0.40~bpo70+1
> Severity: normal
> Tags: patch

Where?

> Dear Maintainer,
> 
> The package with this instability when departing more than a meter. The signal
> quality drops a lot in notebooks Samsung Chronos 7. The applications like
> browser can not browse the Internet

I doubt this is a firmware bug.  Try upgrading the kernel.

Ben.

-- 
Ben Hutchings
If at first you don't succeed, you're doing about average.


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

Bug#732815: mtpfs fails to connect to android smartphone

[Volker Wysk]

Package: mtpfs
Version: 1.1-4.1
Severity: normal
Tags: upstream

Hello!

I'm trying to access my smartphone by means of the Media Transfer Protocol
(MTP). I start mtpfs, which should mount it over a USB cable, but it fails to
connect to the device:

~ $ mkdir /mnt/android
~ $ mtpfs /mnt/android
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
   Found 1 device(s):
   Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 6
Attempting to connect device
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0

In /var/log/kern.log:

Dec 22 02:30:53 debian kernel: [23654.259601] usb 1-1.1: reset high-speed USB 
device number 6 using xhci_hcd
Dec 22 02:30:53 debian kernel: [23654.276610] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fd6f9240
Dec 22 02:30:53 debian kernel: [23654.276618] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fd6f9200
Dec 22 02:30:53 debian kernel: [23654.276623] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fd6f9280
Dec 22 02:30:53 debian kernel: [23654.276627] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fedc3600
Dec 22 02:30:53 debian kernel: [23654.276631] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fedc35c0
Dec 22 02:30:53 debian kernel: [23654.276635] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fdfcebc0
Dec 22 02:30:53 debian kernel: [23654.276639] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fedc3280
Dec 22 02:30:53 debian kernel: [23654.276643] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fedc3240
Dec 22 02:30:53 debian kernel: [23654.279055] cdc_acm 1-1.1:1.1: This device 
cannot do calls on its own. It is not a modem.
Dec 22 02:30:53 debian kernel: [23654.279171] cdc_acm 1-1.1:1.1: ttyACM0: USB 
ACM device

In /var/log/messages:

Dec 22 02:30:53 debian kernel: [23654.259601] usb 1-1.1: reset high-speed USB 
device number 6 using xhci_hcd
Dec 22 02:30:53 debian kernel: [23654.276610] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fd6f9240
Dec 22 02:30:53 debian kernel: [23654.276618] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fd6f9200
Dec 22 02:30:53 debian kernel: [23654.276623] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fd6f9280
Dec 22 02:30:53 debian kernel: [23654.276627] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fedc3600
Dec 22 02:30:53 debian kernel: [23654.276631] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fedc35c0
Dec 22 02:30:53 debian kernel: [23654.276635] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fdfcebc0
Dec 22 02:30:53 debian kernel: [23654.276639] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fedc3280
Dec 22 02:30:53 debian kernel: [23654.276643] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fedc3240
Dec 22 02:30:53 debian kernel: [23654.279171] cdc_acm 1-1.1:1.1: ttyACM0: USB 
ACM device

In /var/log/syslog:

Dec 22 02:30:53 debian kernel: [23654.259601] usb 1-1.1: reset high-speed USB 
device number 6 using xhci_hcd
Dec 22 02:30:53 debian kernel: [23654.276610] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fd6f9240
Dec 22 02:30:53 debian kernel: [23654.276618] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fd6f9200
Dec 22 02:30:53 debian kernel: [23654.276623] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fd6f9280
Dec 22 02:30:53 debian kernel: [23654.276627] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fedc3600
Dec 22 02:30:53 debian kernel: [23654.276631] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fedc35c0
Dec 22 02:30:53 debian kernel: [23654.276635] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fdfcebc0
Dec 22 02:30:53 debian kernel: [23654.276639] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fedc3280
Dec 22 02:30:53 debian kernel: [23654.276643] xhci_hcd :03:00.0: xHCI 
xhci_drop_endpoint called with disabled ep 8801fedc3240
Dec 22 02:30:53 debian kernel: [23654.279055] cdc_acm 1-1.1:1.1: This device 
cannot do calls on its own. It is not a modem.
Dec 22 02:30:53 debian kernel: [23654.279171] cdc_acm 1-1.1:1.1: ttyACM0: USB 
ACM device


Bye,
V.W.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing

Bug#732689: ipset: kernel panic when adding ip to bitmap:ip

[Neutron Soutmun]

Hello,

This issue has been fixed upstream (ipset kernel part), see [1], which
is not included in the 3.2 kernel of Wheezy.

I'll ask the Debian Kernel Team how to properly fix this issue.

[1] Check and reject crazy /0 input parameters -
http://git.netfilter.org/ipset/commit/kernel/net/netfilter/ipse/ip_set_bitmap_ip.c?id=a1cbbc8f86a8ef955708d48f20f8ca021a0a7641

On Fri, Dec 20, 2013 at 6:45 PM, Mi  wrote:
> Package: ipset
> Version: 6.12.1-1
> Severity: important
>
>
> # ipset create ipv4_ch bitmap:ip range 0.0.0.0/0
> # ipset list
> [ another previously defined hash:net set. No problem with that. ]
>
> Name: ipv4_ch
> Type: bitmap:ip
> Header: range 0.0.0.0-255.255.255.255
> Size in memory: 120
> References: 0
> Members:
>
> # ipset add ipv4_ch 5.1.96.0/21
>
> Message from syslogd@pe1 at Dec 20 12:14:53 ...
>  kernel:[3088568.395819] Oops: 0002 [#1] SMP
>
> Message from syslogd@pe1 at Dec 20 12:14:53 ...
>  kernel:[3088568.398495] Stack:
>
> Message from syslogd@pe1 at Dec 20 12:14:53 ...
>  kernel:[3088568.398495] Call Trace:
>
> Message from syslogd@pe1 at Dec 20 12:14:53 ...
>  kernel:[3088568.398495] Code: 31 c0 48 85 ff 74 19 48 81 ff ff ff ff 7f b0 
> 01 74 0e 48 8b 05 e7 af 1e e1 48 29 f8 48 c1 e8 3f c3 48 8b 47 40 0f b7 16 48 
> 8b 00  0f ab 10 19 d2 83 fa 01 19 c0 f7 d0 25 f9 ef ff ff c3 48 8b
>
> Message from syslogd@pe1 at Dec 20 12:14:53 ...
>  kernel:[3088568.398495] CR2: 0c10
>
> Message from syslogd@pe1 at Dec 20 12:14:53 ...
>  kernel:[3088568.428341] Kernel panic - not syncing: Fatal exception in 
> interrupt
>
>
> That's all. The machine hung completely and needed a hard reset.
>
>
>
> -- System Information:
> Debian Release: 7.3
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> 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 ipset depends on:
> ii  iptables   1.4.14-3.1
> ii  libc6  2.13-38
> ii  libipset2  6.12.1-1
>
> ipset recommends no packages.
>
> ipset 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#730829: systemd fails to activate logical volumes after a power failure

[Michael Biebl]

Am 29.11.2013 23:08, schrieb Praveen A:
> package: systemd
> version: 204-5
> severity: critical
> 
> Even when a simple fsck is enough to fix the issue. Currently it drops
> you into a shell where you have to manually run vgchange -a y. systemd
> should give up only when a simple fsck fails to fix the file system.

If you are dropped into such a rescue shell, can you run journalctl -b
(will output the journal log from the current boot) and dump that into a
file and attach it to the bug report.
A "systemctl dump" from such a boot would be helpful as well.


-- 
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#707214: refpolicy: Please handle new dpkg_script_t execution context

[Laurent Bigonville]

Hello Guillem,

I quickly tried, and when the package is installed (dpkg -i) the
maintainer script is properly transitioned to "dpkg_script_t".

dpkg-reconfigure is OTOH not transitioning the maintainer script to its
own context, I guess it also should be the case here?

Otherwise I think that the policy already has support for the
dpkg_script_t execution context, or did you had something specific in
mind?

Cheers,

Laurent Bigonville

For the record the discussion with selinux upstream is here:
https://lists.debian.org/debian-dpkg/2012/11/msg4.html


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

Bug#732623: [Pkg-systemd-maintainers] Bug#732623: [Pkg-xfce-devel] Bug#732623: lightdm-gtk-greeter: Hibernate and Restart buttons disappear after first login/logout

[Michael Biebl]

severity 732623 normal
tags 732623 + moreinfo
thanks

Am 22.12.2013 00:12, schrieb Vincent Lefevre:
> On 2013-12-21 22:53:15 +0100, Pascal Dormeau wrote:
>> Contrary to what I though (and wrote), I can reproduce the same with
>> xfce4-session or twm.
>> On my side, it seems to have to do with libpam-systemd, removing it
>> allows all 4 buttons. The problem is triggered as soon as
>> libpam-systemd is installed (installing upower does not change anything
>> to it).
> 
> When I upgraded my second machine yesterday, I noticed that both
> libpam-systemd and systemd had been installed, so that I thought
> the bug was related to one of them. So, I did some tests to see
> what minimal change triggered the problem, and it was not due to
> libpam-systemd (which depends on systemd), but to systemd itself.
> That's why I've reassigned the bug to systemd.

I'm not convinced the bug is in systemd and the package is clearly not
unrelated (as lightdm  has systemd specific code) so the severity is
incorrect.
It's very well possible that it's lightdm which has broken logind
specific. Hard to tell with this little information.




-- 
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#732814: libtiff5 transition

[Jackson Doak]

Package: dx
Version: 1:4.4.4-7

Please build depend on libtiff-dev rather than libtiff4-dev. The transition
is now ongoing and i will be uploading a fixed version to ubuntu soon.

Bug#732813: pitivi: incorrect dependency information causes pitivi to segfault on startup

[Benjamin Mako Hill]

Package: pitivi
Version: 0.92-1
Severity: important

Thanks for maintaining pitivi!

If pitivi 0.92 (the version currently in experimental) is installed on a
current Debian testing system, it will segfault on startup. The problem
is due to an incompatibility with python-gi 3.8 which is currently in
testing. If python-gi 3.10 is installed from sid, pitivi will start
normally.

This bug can be fixed by updating the dependency information for pitivi
0.92 to require python-gi (>=3.10).

Regards,
Mako


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

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

Versions of packages pitivi depends on:
ii  gir1.2-clutter-1.0  1.14.4-3
ii  gir1.2-gdkpixbuf-2.02.28.2-1
ii  gir1.2-ges-1.0  1.1.90-2
ii  gir1.2-glib-2.0 1.36.0-2+b1
ii  gir1.2-gst-plugins-base-1.0 1.2.1-2
ii  gir1.2-gstreamer-1.01.2.1-1
ii  gir1.2-gtk-3.0  3.8.4-1
ii  gir1.2-gtkclutter-1.0   1.4.4-3
ii  gir1.2-pango-1.01.32.5-5+b1
ii  gnome-icon-theme3.8.3-1
ii  gstreamer1.0-alsa [gstreamer1.0-audiosink]  1.2.1-2
ii  gstreamer1.0-gnonlin1.1.90-1
ii  gstreamer1.0-plugins-bad [gstreamer1.0-videosink]   1.2.1-2
ii  gstreamer1.0-plugins-base   1.2.1-2
ii  gstreamer1.0-plugins-good [gstreamer1.0-videosink]  1.2.1-1
ii  gstreamer1.0-pulseaudio [gstreamer1.0-audiosink]1.2.1-1
ii  gstreamer1.0-x [gstreamer1.0-videosink] 1.2.1-2
ii  libc6   2.17-92+b1
ii  libcairo2   1.12.14-4
ii  python  2.7.5-4
ii  python-cairo1.8.8-1+b2
ii  python-dbus 1.2.0-2+b1
ii  python-gi   3.10.2-1
ii  python-gst-1.0  1.1.90-1
ii  python-matplotlib   1.3.1-1
ii  python-numpy1:1.7.1-3
ii  python-xdg  0.25-3

pitivi recommends no packages.

Versions of packages pitivi suggests:
ii  frei0r-plugins 1:1.4-dmo4
ii  gstreamer1.0-libav 1:1.0.10-dmo1
ii  gstreamer1.0-plugins-bad   1.2.1-2
ii  gstreamer1.0-plugins-ugly  1.0.9-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#732798: [Pkg-systemd-maintainers] Bug#732798: document --full as an option for status

[Russ Allbery]

Zbigniew Jędrzejewski-Szmek  writes:

> http://cgit.freedesktop.org/systemd/systemd/commit/?id=e213d1a3c3
> http://cgit.freedesktop.org/systemd/systemd/commit/?id=69d918b

Thank you!  That's great.

-- 
Russ Allbery (r...@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#732006: uscan: broken handling of filenames with whitespace

[Stig Sandbeck Mathisen]

Control: tags -1 + patch

I've pushed a proposed fix for this security issue to the packaging
repo git://anonscm.debian.org/collab-maint/devscripts.git as the
branch CVE-2013-7085-ruin-someones-yuletide

One commit, see
http://anonscm.debian.org/gitweb/?p=collab-maint/devscripts.git;a=commit;h=f3b48a97d10fce5bb368b3af195b3c1cdb09e4b2

It's kind of a large commit for a small issue. Mostly because the
"wrap shell commands in backticks, and hope for the best" approach is
open for multiple potential issues, and I would like to remove them
all.

The change also fixes a second bug, where one could not exclude a
non-empty top level directory, but had to use "somedirectory/*".

-- 
Stig Sandbeck Mathisen


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

Bug#732812: ITP: golang-rrd -- Go bindings for the rrdtool C library

[Tonnerre LOMBARD]

Package: wnpp
Severity: wishlist
Owner: Tonnerre LOMBARD 

* Package name: golang-rrd
  Version : 0.0~git20131112
  Upstream Author : Michał Derkacz 
* URL : http://github.com/ziutek/rrd/
* License : BSD-3-Clause
  Programming Lang: Go
  Description : Go bindings for the rrdtool C library

This is a Go wrapper for the rrdtool C library, which can be used to
gather and process historical data as well as to create graphs of said
data. This library enables Go programs to access rrdtool files like any
other language can.


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

Bug#732798: [Pkg-systemd-maintainers] Bug#732798: document --full as an option for status

[Zbigniew Jędrzejewski-Szmek]

On Sat, Dec 21, 2013 at 10:32:46PM +0100, Michael Stapelberg wrote:
> Russ Allbery  writes:
> > systemctl status  truncates log messages from the journal to
> > 80 columns by default.  Some experimentation revealed that --full will
> > prevent this and show the full log message, but this isn't documented
> > in the systemctl man page.  --full only mentions a couple of other
> > commands, and status doesn't reference --full.
> >
> > Could you add a cross-reference or two?
> I’ll let Zbigniew comment on that, given that he already pushed the last
> documentation request upstream directly. Thanks!
http://cgit.freedesktop.org/systemd/systemd/commit/?id=e213d1a3c3
http://cgit.freedesktop.org/systemd/systemd/commit/?id=69d918b

Zbyszek


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

Bug#713126: gcj-4.6: FTBFS: unsatisfiable build-dependency: automake (< 1:1.12) but 1:1.13.3-1 is to be installed

[peter green]

Tags 713126 +patch
Thanks

The attatched debdiff makes this package build in current sid. I have 
not tested it beyond that. No intent to NMU.



diff -u gcj-4.6-4.6.4/debian/control.m4 gcj-4.6-4.6.4/debian/control.m4
--- gcj-4.6-4.6.4/debian/control.m4
+++ gcj-4.6-4.6.4/debian/control.m4
@@ -66,7 +66,7 @@
   realpath (>= 1.9.12), chrpath, lsb-release, make (>= 3.81), quilt
 Build-Depends-Indep: LIBSTDCXX_BUILD_INDEP JAVA_BUILD_INDEP
 ')dnl
-Build-Conflicts: binutils-gold
+Build-Conflicts: binutils-gold (<= 2.23.52.20130620-1)
 ifelse(regexp(SRCNAME, `gnat'),0,`dnl
 Homepage: http://gcc.gnu.org/
 ', regexp(SRCNAME, `gdc'),0,`dnl
diff -u gcj-4.6-4.6.4/debian/rules.parameters 
gcj-4.6-4.6.4/debian/rules.parameters
--- gcj-4.6-4.6.4/debian/rules.parameters
+++ gcj-4.6-4.6.4/debian/rules.parameters
@@ -2,15 +2,15 @@
 GCC_VERSION:= 4.6.4
 NEXT_GCC_VERSION   := 4.6.5
 BASE_VERSION   := 4.6
-SOURCE_VERSION := 4.6.4-2
-DEB_VERSION:= 4.6.4-2
-DEB_EVERSION   := 1:4.6.4-2
+SOURCE_VERSION := 4.6.4-2+plugwash1
+DEB_VERSION:= 4.6.4-2+plugwash1
+DEB_EVERSION   := 1:4.6.4-2+plugwash1
 GDC_BASE_VERSION  := 
 DEB_GDC_VERSION:= 
 DEB_SOVERSION  := 4.6
 DEB_SOEVERSION := 1:4.6
 DEB_LIBGCC_SOVERSION   := 1:4.6
-DEB_LIBGCC_VERSION := 1:4.6.4-2
+DEB_LIBGCC_VERSION := 1:4.6.4-2+plugwash1
 DEB_STDCXX_SOVERSION   := 4.6
 DEB_GCJ_SOVERSION  := 4.6
 PKG_GCJ_EXT:= 12
diff -u gcj-4.6-4.6.4/debian/rules.conf gcj-4.6-4.6.4/debian/rules.conf
--- gcj-4.6-4.6.4/debian/rules.conf
+++ gcj-4.6-4.6.4/debian/rules.conf
@@ -309,7 +309,7 @@
 endif
 
 AUTO_BUILD_DEP := m4, libtool,
-AUTO_BUILD_DEP += autoconf2.64, automake (>= 1:1.11), automake (<< 1:1.12),
+AUTO_BUILD_DEP += autoconf2.64, automake1.11,
 
 ifneq ($(DEB_CROSS),yes)
 LIBC_BUILD_DEP := libc6.1-dev (>= $(libc_dev_ver)) [alpha ia64] | libc0.3-dev 
(>= $(libc_dev_ver)) [hurd-i386] | libc0.1-dev (>= $(libc_dev_ver)) 
[kfreebsd-i386 kfreebsd-amd64] | libc6-dev (>= $(libc_dev_ver))
diff -u gcj-4.6-4.6.4/debian/changelog gcj-4.6-4.6.4/debian/changelog
--- gcj-4.6-4.6.4/debian/changelog
+++ gcj-4.6-4.6.4/debian/changelog
@@ -1,3 +1,18 @@
+gcj-4.6 (4.6.4-2+plugwash1) UNRELEASED; urgency=medium
+
+  * Patch for proposing to Debian BTS and use in Raspbian, no intent to NMU in 
+Debian.
+  * Switch arround build depends/conflicts so they are satisfiable in current
+sid (Closes: 713126)
+  + Remove automake (>= 1:1.11), automake (<< 1:1.12) from build-depends
+  + add automake1.11 to build-depends
+  + Version the build-conflicts on binutils-gold as (<= 2.23.52.20130620-1)
+(the last real version of the package) so it doesn't hit the virtual
+package now provided by binutils.
+  * Remove freetype/ from freetype includes as the files have moved.
+
+ -- Peter Michael Green   Sat, 21 Dec 2013 01:02:36 +
+
 gcj-4.6 (4.6.4-2) unstable; urgency=low
 
   * Sync packaging and updates with gcc-4.6 4.6.4-2.
diff -u gcj-4.6-4.6.4/debian/rules.patch gcj-4.6-4.6.4/debian/rules.patch
--- gcj-4.6-4.6.4/debian/rules.patch
+++ gcj-4.6-4.6.4/debian/rules.patch
@@ -342,6 +342,8 @@
   debian_patches += armhf-triplet
 endif
 
+debian_patches += freetype-includes
+
 #debian_patches += address-clauses-timed-entry-calls
 
 series_stamp = $(stampdir)/02-series-stamp
diff -u gcj-4.6-4.6.4/debian/control gcj-4.6-4.6.4/debian/control
--- gcj-4.6-4.6.4/debian/control
+++ gcj-4.6-4.6.4/debian/control
@@ -6,7 +6,7 @@
 Standards-Version: 3.9.4
 Build-Depends: dpkg-dev (>= 1.16.0~ubuntu4), debhelper (>= 5.0.62), 
g++-multilib [amd64 i386 kfreebsd-amd64 mips mipsel powerpc ppc64 s390 s390x 
sparc], 
   libc6.1-dev (>= 2.13-5) [alpha ia64] | libc0.3-dev (>= 2.13-5) [hurd-i386] | 
libc0.1-dev (>= 2.13-5) [kfreebsd-i386 kfreebsd-amd64] | libc6-dev (>= 2.13-5), 
libc6-dev-amd64 [i386], libc6-dev-sparc64 [sparc], libc6-dev-s390 [s390x], 
libc6-dev-s390x [s390], libc6-dev-i386 [amd64], libc6-dev-powerpc [ppc64], 
libc6-dev-ppc64 [powerpc], libc0.1-dev-i386 [kfreebsd-amd64], lib32gcc1 [amd64 
ppc64 kfreebsd-amd64 s390x], lib64gcc1 [i386 powerpc sparc s390], 
libc6-dev-mips64 [mips mipsel], libc6-dev-mipsn32 [mips mipsel],
-  m4, libtool, autoconf2.64, automake (>= 1:1.11), automake (<< 1:1.12), 
+  m4, libtool, autoconf2.64, automake1.11, 
   libunwind7-dev (>= 0.98.5-6) [ia64], libatomic-ops-dev [ia64],
   zlib1g-dev, gawk, lzma, xz-utils, patchutils,
   binutils (>= 2.21.1) | binutils-multiarch (>= 2.21.1), binutils-hppa64 (>= 
2.21.1) [hppa],
@@ -15,7 +15,7 @@
   libcloog-ppl-dev (>= 0.16), libmpc-dev (>= 1.0), libmpfr-dev (>= 3.0.0-9~), 
libgmp-dev (>= 2:5.0.1~), libelfg0-dev (>= 0.8.12), dejagnu [!m68k !hurd-i386 
!hurd-alpha],
   realpath (>= 1.9.12), chrpath, lsb-release, make (>= 3.81), quilt
 Build-Depends-Indep:  
-Build-Conflicts: binutils-gold
+Build-Conflicts: binutils-gold (<= 2.23.52.20130620-1)
 Homepage: http://gcc.gnu.org/
 XS-Vcs-Browser: http://svn.debian.org/viewsvn/gcccvs/branches/sid/gcc-4.6/
 XS-Vcs-Svn: svn://svn.debian.org/svn/gcccv

Bug#692938: emacsen-common: emacsen-common can get confused, uninstallable during its install

[Dima Kogan]

Hi. Thanks for replying.

Sadly, this all happened long enough ago that I don't remember details
that aren't in the bug report. If the report itself isn't sufficient to
suggest what the issue could be, maybe this bug can just be closed.

Thanks again

dima


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

Bug#732613: RFS: xye/0.12.2+dfsg-1 [ITA]

[Andreas Rönnquist]

> On Sat, 21 Dec 2013 21:30:28 +0100, Andreas Rönnquist
>  wrote:
 > Ah, I hadn't - thanks! Well, I am kind of irritated on that bug I
> > mentioned in README.source (##635920) which makes it impossible to
> > use git-import-orig --uscan in combination with a debian/repack
> > script... I guess using the mentioned Files-Excluded would solve
> > this?
> 
> I haven't actually got round to using it myself yet, so I can't say
> for sure... But I get the impression that uscan repacks the original
> tarball itself with the same name when removing excluded files, so it
> should work transparently with git-import-orig --uscan.
> 
> I'll leave it to you to decide what you want to do for this version
> of the xye package, since it's too late for the 0.12.2 import anyway,
> and it would require rewriting debian/copyright in machine-readable
> format.

Alright, lets put this conversion on hold at least to until before the
next upstream import then.

>  
> > Would you like me to put together a new package on mentors, or do
> > you simply get the gbp packaging from alioth?
> 
> I'm pulling your packaging from alioth, so no need to update mentors.
> 
> BTW I noticed in your email to debian-devel-games that you mentioned
> the "newer-standards-version" lintian warning; this is fixed in the
> latest version of lintian, currently available in unstable only. 
---8<---

Ah, I know - I get the 'newer-standards-version' lintian warning on
the mentors site - seems like they havn't updated the lintian version
there yet. (I have the latest lintian here on my computer, and don't get
the warning here).

> 
> Let me know when you reckon you've finished preparing the package,
> whether or not you fix the second segfault you mention (I can't
> reproduce it, but I may not be testing the right thing).
> 
I get it if I simply run "xye /usr/" (or any folder other
than /usr/share/xye/ for that matter)...

I have tried to debug it, but it seems to be a harder nut to crack.

I guess it can wait until another release (another debian release, or
another upstream) - I will of course report it upstream.

I find the package pretty much ready to upload - Would you like me to
replace that UNRELEASED with unstable in the changelog, or do you take
care of that?

best regards, and many many thanks
-- Andreas Rönnquist
gus...@gusnan.se


signature.asc
Description: PGP signature

Bug#730933: ltrace: diff for NMU version 0.5.3-2.2

[David Prévot]

tags 730933 + patch
thanks

Dear maintainer,

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

Regards.

David
diff -u ltrace-0.5.3/debian/changelog ltrace-0.5.3/debian/changelog
--- ltrace-0.5.3/debian/changelog
+++ ltrace-0.5.3/debian/changelog
@@ -1,3 +1,10 @@
+ltrace (0.5.3-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Build-depend on libiberty-dev instead of binutils-dev (Closes: #730933)
+
+ -- David Prévot   Sat, 21 Dec 2013 19:21:35 -0400
+
 ltrace (0.5.3-2.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -u ltrace-0.5.3/debian/control ltrace-0.5.3/debian/control
--- ltrace-0.5.3/debian/control
+++ ltrace-0.5.3/debian/control
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Juan Cespedes 
 Standards-Version: 3.8.2
-Build-Depends: cdbs (>= 0.4.23-1.1), debhelper (>= 5), binutils-dev, libelfg0-dev
+Build-Depends: cdbs (>= 0.4.23-1.1), debhelper (>= 5), libiberty-dev, libelfg0-dev
 
 Package: ltrace
 Architecture: i386 arm armeb armel m68k s390 powerpc sparc alpha amd64 ia64 ppc64


signature.asc
Description: Digital signature

Bug#730271: gnupg: Future FTBFS: gnupg attempts to build mpi on Windows and fails

[Stephen Kitt]

Hi Werner,

On Mon, 16 Dec 2013 20:53:11 +0100, Werner Koch  wrote:
> On Sat, 23 Nov 2013 15:36, sk...@debian.org said:
> > I'm getting ready to upload a new version of gcc-mingw-w64 using gcc
> > 4.8 and enabling libgomp. This causes the gpgv-win32 build to attempt
> 
> How many regression must a hacker see
> before you call him a mingw developer?
> Yes, and how many API changes must my Emacs resist
> before it stops to apply the patches?
> The answer my friends, is lingering in your BTS.
> 
> [Is Windows really worth the trouble]

Indeed...

The problem is that we build gnupg for Windows in Debian so it can be used in
the Windows-based installer. So we need to fix anything which causes the
Windows build to fail! I try to make sure I always provide a patch for
Windows-specific bugs in Debian packages, given that it's reasonable for
maintainers (and upstreams) to not care about that platform. In this
particular case the fix is easy enough, so I was hoping you would merge it
upstream as well.

Regards,

Stephen


signature.asc
Description: PGP signature

Bug#732811: ITP: libtest-moose-more-perl -- collection of tools for testing Moose packages

[gregor herrmann]

Package: wnpp
Owner: gregor herrmann 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org,debian-p...@lists.debian.org

* Package name: libtest-moose-more-perl
  Version : 0.022
  Upstream Author : Chris Weyl 
* URL : https://metacpan.org/release/Test-Moose-More
* License : LGPL-2.1
  Programming Lang: Perl
  Description : collection of tools for testing Moose packages

Test::Moose::More contains a number of additional tests that can be employed
against Moose classes/roles. It is intended to replace Test::Moose in tests.


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

Bug#732754: [Pkg-openssl-devel] Bug#732754: openssl: CVE-2013-6449: crash when using TLS 1.2

[Kurt Roeckx]

On Sat, Dec 21, 2013 at 09:24:38PM +0100, Salvatore Bonaccorso wrote:
> Hi Kurt,
> 
> On Sat, Dec 21, 2013 at 09:35:38AM +0100, Kurt Roeckx wrote:
> > On Sat, Dec 21, 2013 at 08:16:42AM +0100, Salvatore Bonaccorso wrote:
> > > Package: openssl
> > > Version: 1.0.1e-2
> > > Severity: grave
> > > Tags: security upstream patch
> > > 
> > > Hi,
> > > 
> > > the following vulnerability was published for openssl.
> > > 
> > > CVE-2013-6449[0]:
> > > crash when using TLS 1.2
> > > 
> > > It was reported in Apache Traffic Server[1] and upstream at [2], see
> > > also [3]. I was not able to reproduce any crash myself, just checking
> > > against the openssl source package to verify upstrem patches apply.
> > > See [4] and [5] for the patches applied.
> > 
> > I was expecting this, and planning an upload for it already.  I'll
> > prepare an upload later today.
> 
> Thanks!
> 
> > I have a bunch of other patches that I'd like to see reach stable,
> > but I'm not sure how many of those you like in a DSA.
> 
> Okay. Could you sent what you are thinking off, to the security team
> alias, so that somebody the team can comment/have a look/...? Is this
> about #720426? (If so an 'ack' from the Release Team would be needed
> also to have them included).

I'd like to see those reach stable too, and I'm really tired on
waiting for them.

But I'm also thinking about at least #732710

There are also things like:
Author: Dr. Stephen Henson 
Date:   Mon Sep 16 05:23:44 2013 +0100

Disable Dual EC DRBG.

Return an error if an attempt is made to enable the Dual EC DRBG: it
is not used by default.

And there is a whole bunch of other things I want to get fixed but
which are less important.


Kurt


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

Bug#732810: ITP: libtap-simpleoutput-perl -- simple closure-driven TAP generator

[gregor herrmann]

Package: wnpp
Owner: gregor herrmann 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org,debian-p...@lists.debian.org

* Package name: libtap-simpleoutput-perl
  Version : 0.002
  Upstream Author : Chris Weyl 
* URL : https://metacpan.org/release/TAP-SimpleOutput
* License : LGPL-2.1
  Programming Lang: Perl
  Description : simple closure-driven TAP generator

TAP::SimpleOutput provides one function, counters(), that returns a number of
simple closures designed to help output TAP easily and correctly, with a
minimum of fuss.


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

Bug#732623: [Pkg-xfce-devel] Bug#732623: lightdm-gtk-greeter: Hibernate and Restart buttons disappear after first login/logout

[Vincent Lefevre]

On 2013-12-21 22:53:15 +0100, Pascal Dormeau wrote:
> Contrary to what I though (and wrote), I can reproduce the same with
> xfce4-session or twm.
> On my side, it seems to have to do with libpam-systemd, removing it
> allows all 4 buttons. The problem is triggered as soon as
> libpam-systemd is installed (installing upower does not change anything
> to it).

When I upgraded my second machine yesterday, I noticed that both
libpam-systemd and systemd had been installed, so that I thought
the bug was related to one of them. So, I did some tests to see
what minimal change triggered the problem, and it was not due to
libpam-systemd (which depends on systemd), but to systemd itself.
That's why I've reassigned the bug to systemd.

-- 
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#732791: [l10n] codeblocks: Please include the translations in Debian

[Andreas Cadhalpun]

Hi Vincent,

On 21.12.2013 23:14, Vincent Cheng wrote:

Shouldn't these translations be included directly upstream? Do you
know if upstream already knows about these translations, or are they
somehow Debian-specific?


I somehow assumed that these translations are part of upstream, are they 
not?
I don't think they are specific to Debian, I just thought that upstream 
released them separately from the program source code.


Best regards,
Andreas


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

Bug#727085: Now we don't depend on the weird libevent patch

[Paul Tarjan]

>Not really, in my opinion.
>I think it's a valid rejection reason for anything that is not the
>reference PHP implementation published and copyrighted by the PHP Group.
>
>Personally, I consider the PHP License non-free even for PHP itself,
>but that's another story:
>https://lists.debian.org/debian-legal/2005/11/msg00272.html

What would you like me to do?


>Please let me understand: do you mean that hhvm includes code derived
>from the reference PHP implementation published and copyrighted by the
>PHP Group?

Yes. You can see our source code at https://github.com/facebook/hhvm


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

Bug#732809: pavucontrol: one should be able to modify the volume when audio is mute

[Vincent Lefevre]

Package: pavucontrol
Version: 1.0-1
Severity: wishlist

When "Mute" is selected, the volume sliders (Front Left & Front Right)
are greyed out, and it is not possible to modify the volume.

One should be able to modify the volume (in particular lower it)
just before unmuting. Otherwise it can be too high, which could
be annoying for the neighbors, even during a short period. :)

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

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

Versions of packages pavucontrol depends on:
ii  libatk1.0-0  2.10.0-2
ii  libatkmm-1.6-1   2.22.7-2
ii  libc62.17-97
ii  libcairo-gobject21.12.16-2
ii  libcairo21.12.16-2
ii  libcairomm-1.0-1 1.10.0-1
ii  libcanberra-gtk3-0   0.30-2
ii  libcanberra0 0.30-2
ii  libgcc1  1:4.8.2-10
ii  libgdk-pixbuf2.0-0   2.28.2-1+b1
ii  libglib2.0-0 2.36.4-1
ii  libglibmm-2.4-1c2a   2.36.2-1
ii  libgtk-3-0   3.8.6-1
ii  libgtkmm-3.0-1   3.8.1-1
ii  libpango1.0-01.36.0-1+b1
ii  libpangomm-1.4-1 2.34.0-1
ii  libpulse-mainloop-glib0  4.0-6+b1
ii  libpulse04.0-6+b1
ii  libsigc++-2.0-0c2a   2.2.10-0.2
ii  libstdc++6   4.8.2-10

pavucontrol recommends no packages.

pavucontrol 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#727085: Now we don't depend on the weird libevent patch

[Francesco Poli]

On Sat, 21 Dec 2013 20:42:37 + Paul Tarjan wrote:

> That rejection reason is pretty squarely aimed at people writing
> applications in the PHP language and makes sense for them.

Not really, in my opinion.
I think it's a valid rejection reason for anything that is not the
reference PHP implementation published and copyrighted by the PHP Group.

Personally, I consider the PHP License non-free even for PHP itself,
but that's another story:
https://lists.debian.org/debian-legal/2005/11/msg00272.html

[...]
> 
> As for the direct question. Much of our extension code was directly
> imported from php-src so we will absolutely be unable to relicense
> that portion. Untangling our contributions from the php-src ones is a
> very arduous task since there are many bug fixes to their code (some
> upstreamed, some not) as well as API changes and data structure
> replacements. We are happy with the php license so releasing the
> whole package under the same umbrella makes development much easier.

Please let me understand: do you mean that hhvm includes code derived
from the reference PHP implementation published and copyrighted by the
PHP Group?


-- 
 http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt
 New GnuPG key, see the transition document!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


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

Bug#730658: codeblocks: has icon in gnome using radeon driver, but not using fglrx driver

[Andreas Cadhalpun]

Control: retitle -1 codeblocks: no icon in gnome using fglrx driver

Hi Ove,

On 21.12.2013 21:27, Ove Kåven wrote:
> Well, I've looked into things a bit, and I think it has something to
> do with me running fglrx. For some reason, I think Gnome is using
> smaller fonts and icons when running fglrx than when running the
> open-source radeon driver. (The codeblocks icon is visible if I run
> the latter.)
Actually, I can confirm your observation on another machine with Radeon 
graphics card:
When using the proprietary fglrx, Code::Blocks does not show an icon, 
but it is shown using the radeon driver.


This is a weird bug, and it might be difficult to solve, because a 
non-free package is involved.


> Not sure where I can adjust that. Regardless, I think codeblocks
> ought to have an icon that is visible regardless of what font/icon
> size Gnome prefers, don't you think?
That should certainly be the case, but I don't understand why Gnome uses 
different fonts, depending on the video driver, or how that could lead 
to the icon not being displayed.


Best regards,
Andreas


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

Bug#732613: RFS: xye/0.12.2+dfsg-1 [ITA]

[Stephen Kitt]

On Sat, 21 Dec 2013 21:30:28 +0100, Andreas Rönnquist 
wrote:
> > I've just got a couple of comments:
> > * debian/repack is nice but seems like an awful lot of effort to
> >   remove two files; have you noticed the new Files-Excluded header in
> >   debian/copyright which uscan now supports?
> 
> Ah, I hadn't - thanks! Well, I am kind of irritated on that bug I
> mentioned in README.source (##635920) which makes it impossible to use
> git-import-orig --uscan in combination with a debian/repack script... I
> guess using the mentioned Files-Excluded would solve this?

I haven't actually got round to using it myself yet, so I can't say for
sure... But I get the impression that uscan repacks the original tarball
itself with the same name when removing excluded files, so it should work
transparently with git-import-orig --uscan.

I'll leave it to you to decide what you want to do for this version of the xye
package, since it's too late for the 0.12.2 import anyway, and it would
require rewriting debian/copyright in machine-readable format.

> > * The manpage doesn't follow the typical Unix manpage style, although
> >   if there are no command-line options then the text you've written is
> >   good enough. You might get bug reports requesting the manpage to
> >   document how to play but until then...
> 
> I'll think I'll wait for those bug reports... ;)

That's fine by me!

> > Incidentally while trying to determine whether xye takes any
> > command-line parameters, I discovered that specifying any parameter
> > causes xye to crash! (I'll file a bug...)
> 
> Oh! I have managed to include a patch that fixes this problem, but when
> doing so I found more related problems - if running with a folder which
> doesn't contain any data files it still segfaults (but later). I
> will try to put together a patch for this problem too.
> 
> (I have pushed my current changes to alioth).
> 
> Would you like me to put together a new package on mentors, or do you
> simply get the gbp packaging from alioth?

I'm pulling your packaging from alioth, so no need to update mentors.

BTW I noticed in your email to debian-devel-games that you mentioned the
"newer-standards-version" lintian warning; this is fixed in the latest
version of lintian, currently available in unstable only. I recommend that
for Debian development work you always use the unstable version of lintian; I
use the following apt pinning (in /etc/apt/preferences):

Package: lintian
Pin: release a=unstable
Pin-Priority: 500

Package: debian-policy
Pin: release a=unstable
Pin-Priority: 500

Let me know when you reckon you've finished preparing the package, whether
or not you fix the second segfault you mention (I can't reproduce it, but I
may not be testing the right thing).

Regards,

Stephen


signature.asc
Description: PGP signature

Bug#719618: RFA: spring -- modern full-3D RTS game engine

[Markus Koschany]

retitle 719618 RFA: spring -- modern full-3D RTS game engine
noowner 719618
tags 731372 patch
thanks


Hello Jan and Martin,

I have overhauled the Debian spring package and committed everything to
the team's git repository. The new package closes almost every bug
except the ones which require exceptional efforts by upstream, namely
making spring work on other architectures than amd64 or i386.

I'm sure that I improved the package but I don't intend to become one of
the uploaders at the moment. There are far too many embedded third party
software libraries and I can't see that upstream will try to change that
in the near future. I'm also a little disappointed that there is no kind
of security mailing list and only little effort to work with upstream
developers of embedded libs like assimp to incorporate spring's changes. [1]

However I would really appreciate it if someone reviewed the current
packaging work and helped with fixing the current RC bug.

As far as I can see the springlobby package could also benefit from a
new upstream release and rapid-spring is no longer supported (see the
info at the bottom of the page) [2] I don't think it's worth to support
this package for Jessie.

In any case

Happy Christmas!



[1] http://springrts.com/phpbb/viewtopic.php?f=20&t=31300
[2] http://springrts.com/wiki/GamesDownloads



signature.asc
Description: OpenPGP digital signature

Bug#732808: override: libcsfml-dev:libdevel/optional, override: libcsfml-doc:doc/optional

[James Cowgill]

Package: ftp.debian.org
Severity: normal

Dear ftp-team,

Please change the priority of the above packages from extra to optional.

This is because: these packages don't need to be extra priority, to make
the priorities consistent with the library packages in libcsfml, and to
make the priorities consistent with the priorities of the related
libsfml package.

Thanks,
James


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

Bug#732807: uscan: Use of uninitialized value in pattern match (m//) at /usr/bin/uscan line 1505.

[Salvatore Bonaccorso]

Package: devscripts
Version: 2.13.8
Severity: minor
Tags: patch

Hi

If debian/copyright is not in copyright-format 1.0, say

, [ debian/copyright ]
| Format-Specification: 
http://svn.debian.org/wsvn/dep/web/deps/dep5.mdwn?op=file&rev=166
| Upstream-Name: Archive-Any
| Upstream-Contact: Clint Moore 
| Source: https://metacpan.org/release/Archive-Any/
`

uscan issues a unitialized value in pattern match warning for uscan on
line 1505: 

Use of uninitialized value in pattern match (m//) at /usr/bin/uscan line 1505.

Attached is a patch which checks also for if $data->{'format'} is
actually defined.

Regards,
Salvatore
>From 53cf2ce057faae7ab6a808e1fac8d6fdfdde7f71 Mon Sep 17 00:00:00 2001
From: Salvatore Bonaccorso 
Date: Sat, 21 Dec 2013 23:25:38 +0100
Subject: [PATCH] Fix unitialized value warning when copyright is not in
 copyright-format 1.0

If debian/copyright is not in copyright-format 1.0 but say in old
revision of dep5, uscan issues a uninitialized value in pattern match
(m//) at /usr/bin/uscan line 1505.
---
 scripts/uscan.pl | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/scripts/uscan.pl b/scripts/uscan.pl
index 0ffe9f2..19f29d6 100755
--- a/scripts/uscan.pl
+++ b/scripts/uscan.pl
@@ -1502,7 +1502,11 @@ EOF
 	} or do {
 	  undef $data;
 	};
-	if ($data && $data->{'format'} =~ m{^$okformat/?$} && $data->{'files-excluded'} ) {
+if (   $data
+&& defined $data->{'format'}
+&& $data->{'format'} =~ m{^$okformat/?$}
+&& $data->{'files-excluded'} )
+{
 	my $tempdir = tempdir ( "uscan", TMPDIR => 1, CLEANUP => 1 );
 	my $globpattern = "*";
 	my $hidden = ".[!.]*";
-- 
1.8.5.2

Bug#732623: [Pkg-xfce-devel] Bug#732623: lightdm-gtk-greeter: Hibernate and Restart buttons disappear after first login/logout

[Vincent Lefevre]

Control: reassign -1 systemd 204-5
Control: retitle -1 systemd breaks lightdm (lightdm_get_can_hibernate and 
lightdm_get_can_restart return FALSE)
Control: severity -1 grave

set to grave because it breaks an unrelated package (BTW, I don't
even use systemd, it is just installed as a dependency; see below).

On 2013-12-21 01:35:10 +0100, Vincent Lefevre wrote:
> FYI, on another machine, the bug didn't occur. But after upgrading
> some packages (which also installed new packages due to dependencies),
> the bug now occurs.

After some tests, the bug is due to systemd, which was installed
due to some new GNOME dependency (gnome-control-center specifically,
in order to setup the sound volume, via gnome-settings-daemon,
otherwise I don't use GNOME). In my test, if I remove everything
except systemd, the bug still occurs, and if I remove systemd as
well, then the bug no longer occurs.

-- 
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#732791: [l10n] codeblocks: Please include the translations in Debian

[Vincent Cheng]

Hi Andreas,

On Sat, Dec 21, 2013 at 10:06 AM, Andreas Cadhalpun
 wrote:
> Package: codeblocks
> Version: 12.11-3
> Severity: wishlist
> Tags: l10n
>
> Dear Maintainer,
>
> there are translations for Codeblocks available from:
> https://translations.launchpad.net/codeblocks/trunk/+pots/codeblocks
> They are licensed under the same license as Codeblocks itself.
>
> Please include them in Debian.

Shouldn't these translations be included directly upstream? Do you
know if upstream already knows about these translations, or are they
somehow Debian-specific?

Regards,
Vincent


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

Bug#727708: upstart proposed policy in Debian [and 1 more messages]

[Russ Allbery]

Uoti Urpala  writes:

> BTW it's worth noting that in the typical daemon case where "readiness"
> means the listening socket is ready to accept requests, the right way to
> convert the daemon to a new API is to use socket activation, which
> removes the need for separate start-up completion notification. Thus the
> need to use sd_notify() for this purpose should be the exception rather
> than the rule. This means that daemons which would use libsystemd-daemon
> for startup notification and nothing else (and would thus be potential
> candidates to abuse SIGSTOP) should be rare.

Good point.  Anything that's using socket activation probably doesn't
really need additional synchronization.

-- 
Russ Allbery (r...@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#732806: vlc-data: installation error caused by trying to remove non-existing /etc/lvc/lua files

[Fernando Cerezal]

Package: vlc-data
Version: 2.1.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

trying to install package


   * What was the outcome of this action?

It fails because it installation script tries to remove non-existing 
files in /etc/vlc/lua:

Seleccionando el paquete vlc-data previamente no seleccionado.
(Leyendo la base de datos ... 388590 ficheros o directorios instalados 
actualmente.)
Preparing to unpack .../vlc-data_2.1.1-1_all.deb ...
Unpacking vlc-data (2.1.1-1) ...
Processing triggers for hicolor-icon-theme (0.12-1) ...
Configurando vlc-data (2.1.1-1) ...
rmdir: fallo al borrar «/etc/vlc/lua/http/dialogs»: No existe el fichero o el 
directorio
rmdir: fallo al borrar «/etc/vlc/lua/http»: No existe el fichero o el directorio
rmdir: fallo al borrar «/etc/vlc/lua»: No existe el fichero o el directorio
dpkg: error processing package vlc-data (--configure):
 el subproceso instalado el script post-installation devolvió el código de 
salida de error 1
Se encontraron errores al procesar:
 vlc-data
E: Sub-process /usr/bin/dpkg returned an error code (1)
Un paquete no se pudo instalar. Tratando de recuperarlo:
Configurando vlc-data (2.1.1-1) ...
rmdir: fallo al borrar «/etc/vlc/lua/http/dialogs»: No existe el fichero o el 
directorio
rmdir: fallo al borrar «/etc/vlc/lua/http»: No existe el fichero o el directorio
rmdir: fallo al borrar «/etc/vlc/lua»: No existe el fichero o el directorio
dpkg: error processing package vlc-data (--configure):
 el subproceso instalado el script post-installation devolvió el código de 
salida de error 1
Se encontraron errores al procesar:
 vlc-data


   * What outcome did you expect instead?
Package installed.


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

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

Versions of packages vlc-data depends on:
ii  dpkg  1.17.5

vlc-data recommends no packages.

vlc-data 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#727708: upstart proposed policy in Debian [and 1 more messages]

[Uoti Urpala]

On Sat, 2013-12-21 at 08:49 -0800, Russ Allbery wrote:
> Tollef Fog Heen  writes:
> > sd-daemon.c is also intentionally designed to not have dependencies on
> > the rest of the systemd source and to be portable to non-linux
> > architectures too (but basically just stubs then) just so people can put
> > the file in their source and not have to fiddle with checking for
> > libraries and such if they find that tedious.
> 
> I agree with Ian's dislike of this approach.  We try to avoid embedded
> code copies, and I'm not sure why this would be an exception.  Yes, the
> code is fairly simple and hopefully doesn't contain (for example) security
> vulnerabilities, but it's possible to find bugs in just about anything.
> Updating numerous copies of that code is not appealing.

I don't see why that should be considered a particularly significant
downside though. Copies are usually worse than shared code, but not
really worse than everything having a custom implementation. At least
implementing sd_notify() support with a code copy should be considered a
significant improvement over a daemon that always runs custom
double-forking code.

BTW it's worth noting that in the typical daemon case where "readiness"
means the listening socket is ready to accept requests, the right way to
convert the daemon to a new API is to use socket activation, which
removes the need for separate start-up completion notification. Thus the
need to use sd_notify() for this purpose should be the exception rather
than the rule. This means that daemons which would use libsystemd-daemon
for startup notification and nothing else (and would thus be potential
candidates to abuse SIGSTOP) should be rare.


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

Bug#732805: ruby-actionpack-3.2: Invalid requirements in actionpack-3.2.16.gemspec

[Christian Hofstaedtler]

Package: ruby-actionpack-3.2
Version: 3.2.16-2

Dear Maintainer,

The shipped gemspec contains an invalid requirements on sprockets:

/usr/share/rubygems-integration/1.9.1/specifications/actionpack-3.2.16.gemspec:
  s.add_runtime_dependency(%q, [">= 
#"])
  s.add_dependency(%q, [">= #"])
s.add_dependency(%q, [">= #"])

This causes bundler, and likely gem to emit these warnings:
Invalid gemspec in 
[/usr/share/rubygems-integration/1.9.1/specifications/actionpack-3.2.16.gemspec]:
 Illformed requirement [">= #"]

I suspect that the version tracking is broken as well.

  Christian

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

Kernel: Linux 3.11-2-amd64 (SMP w/8 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 ruby-actionpack-3.2 depends on:
ii  ruby  1:1.9.3
ii  ruby-activemodel-3.2  3.2.16-1
ii  ruby-activerecord-3.2 3.2.16-1
ii  ruby-activesupport-3.23.2.16-1
ii  ruby-builder  3.2.0-1
ii  ruby-erubis   2.7.0-2
ii  ruby-journey  1.0.4-1
ii  ruby-rack-cache   1.2-3
ii  ruby-rack-test0.6.2-2
ii  ruby-rack1.4  1.4.5-1
ii  ruby-sprockets2.4.3-2
ii  ruby-tzinfo   1.1.0-1
ii  ruby1.8 [ruby-interpreter]1.8.7.358-9
ii  ruby1.9.1 [ruby-interpreter]  1.9.3.484-1
ii  ruby2.0 [ruby-interpreter]2.0.0.353-1

ruby-actionpack-3.2 recommends no packages.

ruby-actionpack-3.2 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#732623: [Pkg-xfce-devel] Bug#732623: lightdm-gtk-greeter: Hibernate and Restart buttons disappear after first login/logout

[Pascal Dormeau]

On Sat, 21 Dec 2013 20:57:08 +0100
Vincent Lefevre  wrote:

> I would like to know whether other users can reproduce the problem
> with twm, just by logging in then logging out. Since twm is a
> minimalist window manager, which doesn't start anything special,
> this could give an idea...
> 
Hi Vincent,
Contrary to what I though (and wrote), I can reproduce the same with
xfce4-session or twm.
On my side, it seems to have to do with libpam-systemd, removing it
allows all 4 buttons. The problem is triggered as soon as
libpam-systemd is installed (installing upower does not change anything
to it).
Best regards
Pascal Dormeau


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

Bug#732804: yabause-qt crashes when File > Settings accessed (if no optical drive in system)

[Jason Alavaliant]

Package: yabause-qt
Version: 0.9.13-1
Severity: normal

Dear Maintainer,

Yabause-qt mostly works for me but if from the main menu I select File > 
Settings...
to access the settings windows yabause instantly crashes printing in the shell

ASSERT: "f" in file /tmp/buildd/yabause-0.9.13/src/qt/ui/UISettings.cpp, line 
171
Aborted

I did an strace an yabause and found that prior to the ASSERT yabause was 
trying to access
/proc/sys/dev/cdrom/info
(open("/proc/sys/dev/cdrom/info", O_RDONLY) = -1 ENOENT (No such file or 
directory))

so I dug up a usb dvd drive and connected it to my machine (it normally doesn't 
have
an optical drive attached since I so rarely need optical media), as soon as the 
drive
was attached (which made /proc/sys/dev/cdrom/info come into existance) I was 
able
to access the settings window without crashing.

Thanks
Jason

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

Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages yabause-qt depends on:
ii  freeglut3 2.8.1-1
ii  libc6 2.17-97
ii  libgcc1   1:4.8.2-10
ii  libgl1-mesa-glx [libgl1]  10.0.1-1
ii  libmini18n1   0.2.1-1
ii  libopenal11:1.14-4
ii  libqt4-opengl 4:4.8.5+git192-g085f851+dfsg-2
ii  libqtcore44:4.8.5+git192-g085f851+dfsg-2
ii  libqtgui4 4:4.8.5+git192-g085f851+dfsg-2
ii  libsdl1.2debian   1.2.15-8
ii  libstdc++64.8.2-10
ii  libx11-6  2:1.6.2-1
ii  libxrandr22:1.4.1-1
ii  yabause-common0.9.13-1

yabause-qt recommends no packages.

yabause-qt 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#728467: Taking over packaging of mate-polkit

[Mike Gabriel]

Control: retitle -1 ITP: mate-polkit -- MATE authentication agent for  
Policykit-1

Control: owner -1 Mike Gabriel 

I am about to upload mate-polkit to Debian unstable...

Mike
--

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

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

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


pgptkjnxx73EU.pgp
Description: Digitale PGP-Signatur

Bug#732798: [Pkg-systemd-maintainers] Bug#732798: document --full as an option for status

[Michael Stapelberg]

Hi Russ,

Russ Allbery  writes:
> (Wow, the thousands of lines of systemd dump included in bug reports
> by default seems a little excessive.)
We’d like to fix this with http://bugs.debian.org/526110 because the
information is very valuable for debugging problems. Unfortunately,
there was no reply from the reportbug upstream side yet. If you know how
to fast-track the release of a new version of reportbug with that patch,
please let me know… :)

> systemctl status  truncates log messages from the journal to
> 80 columns by default.  Some experimentation revealed that --full will
> prevent this and show the full log message, but this isn't documented
> in the systemctl man page.  --full only mentions a couple of other
> commands, and status doesn't reference --full.
>
> Could you add a cross-reference or two?
I’ll let Zbigniew comment on that, given that he already pushed the last
documentation request upstream directly. Thanks!

-- 
Best regards,
Michael


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

Bug#728243: redmine: fails to install: Please install the mysql adapter

[Christian Hofstaedtler]

Jérémy,

ruby-mysql2 and ruby-mysql do not appear to provide the same
interfaces; as you have noticed Rails ships a seperate 'mysql2'
adapter for users wishing to use ruby-mysql2.

If you have redmine default to the 'mysql' adapter, please make sure
ruby-mysql is first in the Depends line of redmine-mysql.

I'd love to see this bug fixed with any resolution soon so
rails 3.2 can finally migrate to testing.

Thank you,
   Christian

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-



signature.asc
Description: Digital signature

Bug#731788: Correct version?

[Christian Hofstaedtler]

Hi,

In my local apt cache, redmine-sqlite depends on:

Depends: ruby-sqlite3, sqlite3

Are you sure that this bug applies to 2.3.3-3?

Thanks,
-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-



signature.asc
Description: Digital signature

Bug#732803: firmware-iwlwifi: Unstable Wi-fi Signal in Samsung Chronos 7

[Gustavo Dias do Nascimento]

Package: firmware-iwlwifi
Version: 0.40~bpo70+1
Severity: normal
Tags: patch

Dear Maintainer,

The package with this instability when departing more than a meter. The signal
quality drops a lot in notebooks Samsung Chronos 7. The applications like
browser can not browse the Internet



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

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

firmware-iwlwifi depends on no packages.

firmware-iwlwifi recommends no packages.

Versions of packages firmware-iwlwifi suggests:
ii  initramfs-tools  0.115~bpo70+1
ii  linux-image-3.2.0-4-amd64 [linux-image]  3.2.53-2

-- no debconf information


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

Bug#732802: evince: print pdf "unexpected brace token" error

[Jeremiah Mahler]

Package: evince
Version: 3.10.0-1+b1
Severity: normal

Dear Maintainer,

When printing some PDF's using Evince CUPS fails with
an "unexpected brace token" error.

  /var/log/cups/error_log
  ...
  E [21/Dec/2013:12:20:06 -0800] [Job 423] Exception: 
/var/spool/cups/d00423-001 (file position 2592): unexpected brace token
  ...

Printing from other programs produce no such error.
Both 'lpr' and the PDF viewer inside Google Chrome work.

  $ lpr plot1.pdf

To generate a PDF that will produce an error in Evince the
following steps were performed.  Octave is first to generate
a plot file.

  $ cat plot1.m
  x = [1 2 3 4];
  y = x;
  stairs(x, y);
  print('plot1.eps', '-deps');
  $ octave plot1.m
  (generates plot1.eps)
  
Then it is converted from .eps to .pdf

  $ epspdf plot1.eps
  (generates plot1.pdf)

Then if it is opened and printed the
"unexpected brace token" error will result.

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

Kernel: Linux 3.11-2-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 evince depends on:
ii  evince-common  3.10.0-1
ii  gnome-icon-theme-symbolic  3.10.1-1
ii  libatk1.0-02.10.0-2
ii  libc6  2.17-97
ii  libcairo-gobject2  1.12.16-2
ii  libcairo2  1.12.16-2
ii  libevdocument3-4   3.10.0-1+b1
ii  libevview3-3   3.10.0-1+b1
ii  libgail-3-03.8.6-1
ii  libgdk-pixbuf2.0-0 2.28.2-1+b1
ii  libglib2.0-0   2.36.4-1
ii  libgtk-3-0 3.8.6-1
ii  libice62:1.0.8-2
ii  libnautilus-extension1a3.8.2-2
ii  libpango-1.0-0 1.36.0-1+b1
ii  libpangocairo-1.0-01.36.0-1+b1
ii  libsecret-1-0  0.15-2
ii  libsm6 2:1.2.1-2
ii  libx11-6   2:1.6.2-1
ii  libxml22.9.1+dfsg1-3
ii  shared-mime-info   1.0-1+b1
ii  zlib1g 1:1.2.8.dfsg-1

Versions of packages evince recommends:
ii  dbus-x11  1.6.18-2
ii  gvfs  1.16.3-1+b2

Versions of packages evince suggests:
ii  nautilus  3.8.2-2
ii  poppler-data  0.4.6-4
pn  unrar 

-- no debconf information


plot1.pdf
Description: Adobe PDF document

Bug#477136: emacsen-common: Deep recursion on subroutine "main::generate_relevant_tsort_dependencies_internals"

[Rob Browning]

tags 477136 +wishlist
thanks

Laurent Bonnaud  writes:

> Setting up emacs22 (22.2+2-1) ...
> emacs-install emacs22
> Deep recursion on subroutine 
> "main::generate_relevant_tsort_dependencies_internals" at 
> /usr/lib/emacsen-common/generate-install-list line 93.

Since we haven't seen any other reports for a long time, I'm going to
assume this was a transient problem.

> Perhaps there is a loop in the dependencies graph this subroutine trying
> to sort topologically.  If so it would be useful to display this loop
> in order to submit a bug report to the appropriate package.

Agreed -- I'll leave the bug this open, but mark it wishlist for now.
Perhaps I or someone else will have some time to work on it later.

And we can certainly re-elevate the severity if the problem reappears.

Thanks for the help.
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4


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

Bug#645010: uswsusp: no attempt to resume when suspending to swapfile on dm-crypt device

[Marcus Osdoba]

Hi Rodolfo,

Thanks for asking. Surprisingly I launched another trial today. My (not 
that expensive) SSD was broken and I had to recover from a former backup 
(now on a new SLC ssd).


The problem is solved now. For documention purposes I write my config 
down here.


Bascially I followed to wiki under [0]
..which told me to use the device! (not /swap.file) where the swap file 
resides. Unfortunately, all my trials were unsuccessful, until I finally 
added GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/mapper/sda2_crypt quiet" 
to my grub cfg.


My ssd layout is as follows:
/dev/sda1 -> 512M /boot
/dev/sda2 -> base for a crypt device -> /dev/mapper/sda2_crypt -> rootfs
swap.file is a file on the fs on sda2_crypt

The installation of uswsusp automagically detected the device and the 
offset, where the swap file lives. I just never tried to add the above 
mentioned kernel option.


># cat /etc/uswsusp.conf
# /etc/uswsusp.conf(5) -- Configuration file for s2disk/s2both
resume device = /dev/mapper/sda2_crypt
#resume device = /swap.file # this does not work (verify [0])
compress = y
image size = 728022466
suspend loglevel = 1
max loglevel = 1
RSA key file = /etc/uswsusp.key
shutdown method = platform
resume offset = 1832960
# offset automagically detected, e.g. dpkg-reconfigure uswsusp

I didn't downgrade to initramfs-tools from wheezy(base), so I can't tell 
you if it also works with the wheezy version. Mine is:

initramfs-tools0.115~bpo70+1  all

The kernel option for GRUB_CMDLINE_LINUX_DEFAULT is documented in the 
wiki. Maybe it is possible to add a hint during the configuration 
questions. I believe the same applies to swapfiles on non-crypt devices, 
too.


Regards,
Marcus

[0] https://wiki.debian.org/Hibernation/Hibernate_Without_Swap_Partition


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

Bug#692938: emacsen-common: emacsen-common can get confused, uninstallable during its install

[Rob Browning]

Dima Kogan  writes:

> The issue, as I understand it is that during the emacsen-common
> postinst, emacsen-common decided that emacs22 is installed, and then
> tried to configure stuff for it. This failed because emacs22 wasn't
> actually installed anymore (the upgrade already removed it).
>
> The installed emacs flavor list:
>
> dkogan@t42:/var/lib/emacsen-common/state/flavor/installed$ ls
> emacs22 xemacs21
>
> So the postinst thinks emacs22 and xemacs21 are both still installed.
> This incorrect; aptitude already uninstalled both of these packages.

Is there a chance that the uninstall failed?  Though that should have
stopped things with an error earlier.

You can see in /usr/lib/emacsen-common/emacs-remove that the last thing
it does is remove that state file (assuming it's working).

I suppose one other option is that you were in the middle of
transitioning from pre-2.0.0 emacsen-common, and the code that handles
converting the old installed-flavors files to the new flavor/installed/*
files is broken (i.e. perhaps it's firing *after* the removal somehow in
the same aptitude run -- note I'm not familiar with aptitude, so I don't
know if that could be relevant either, though I assume not.

> Then I get a similar issue with the xemacs21 package:

I vaguely recall that there might be a problem with the xemacs package,
but I believe xemacs has been removed from Debian.  Though I'm not sure
I'm right, or that it's related.

> As a manual workaround, I'm simply going to remove both of the
> /var/lib/emacsen-common/state/flavor/installed/... files. At the very
> least, emacsen-common postinst can check, and do this itself.

I the general case, I'm not sure it can -- it has no way to know what
state things are in if/when the install/remove scripts don't complete
successfully.  We likely need to fix the underlying bug(s).

> In general, is there a strong reason for the state to be stored in
> that directory, separate from dpkg?

I believe so -- the idea of being "installed" and fully configured from
emacsen-common's perspective is not exactly the same as being installed
from dpkg's, though I think the latter should be a superset of the
latter.

I'm also not sure that it's acceptable (or at least "good form") to
query dpkg during the install process for this kind of information --
but I might be wrong.  In any case, specifically for "installed", I'm
not sure what we'd be asking dpkg, i.e. there's no comprehensive list of
"flavors" -- they come and go.

Thanks for the help.
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4


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

Bug#732801: Implicit declaration of strcasestr in virus_scan_vir.c

[Adam Conrad]

Package: c-icap-modules
Version: 1:0.3.1-2
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * 0002-Implicit-declaration.patch: Replace strcasestr() with ci_strcasestr()
  * debian/{control,rules}: Builddep on and use dh-autoreconf for new ports.

Due to a thinko in virus_scan_vir.c, it ends up implicitly declaring
strcasestr(), when it should have used the wrapped ci_strcasestr(). The
attached path fixes this.

While you're at it, you may as well take the other part of the patch,
which adds dh-autoreconf, and future-proofs your package for new ports,
such as ppc64el.

... Adam

-- System Information:
Debian Release: wheezy/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 
'trusty'), (500, 'saucy-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-0-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru c-icap-modules-0.3.1/debian/changelog c-icap-modules-0.3.1/debian/changelog
diff -Nru c-icap-modules-0.3.1/debian/control c-icap-modules-0.3.1/debian/control
--- c-icap-modules-0.3.1/debian/control	2013-12-21 02:37:38.0 -0700
+++ c-icap-modules-0.3.1/debian/control	2013-12-21 14:11:28.0 -0700
@@ -3,7 +3,7 @@
 Priority: extra
 Maintainer: Tim Weippert 
 Uploaders: Jochen Friedrich , Mathieu Parent 
-Build-Depends: debhelper (>= 9~), autotools-dev, libicapapi-dev (>=1:0.3.1~), libclamav-dev, libltdl-dev | libltdl3-dev, libdb-dev
+Build-Depends: debhelper (>= 9~), autotools-dev, libicapapi-dev (>=1:0.3.1~), libclamav-dev, libltdl-dev | libltdl3-dev, libdb-dev, dh-autoreconf
 Standards-Version: 3.9.4
 Homepage: http://c-icap.sourceforge.net/
 
diff -Nru c-icap-modules-0.3.1/debian/patches/0002-Implicit-declaration.patch c-icap-modules-0.3.1/debian/patches/0002-Implicit-declaration.patch
--- c-icap-modules-0.3.1/debian/patches/0002-Implicit-declaration.patch	1969-12-31 17:00:00.0 -0700
+++ c-icap-modules-0.3.1/debian/patches/0002-Implicit-declaration.patch	2013-12-21 13:51:56.0 -0700
@@ -0,0 +1,14 @@
+Description: Use ci_strcasestr() instead of strcasestr()
+Author: Adam Conrad 
+
+--- c-icap-modules-0.3.1.orig/services/virus_scan/virus_scan_vir.c
 c-icap-modules-0.3.1/services/virus_scan/virus_scan_vir.c
+@@ -197,7 +197,7 @@
+  int namelen;
+ 
+  content_disposition = ci_http_response_get_header(req, "Content-Disposition");
+- if (content_disposition && (filename = strcasestr(content_disposition, "filename="))) {
++ if (content_disposition && (filename = ci_strcasestr(content_disposition, "filename="))) {
+   filename = filename + 9;
+   if ((str = strrchr(filename, '/'))) {
+filename = str + 1;
diff -Nru c-icap-modules-0.3.1/debian/patches/series c-icap-modules-0.3.1/debian/patches/series
--- c-icap-modules-0.3.1/debian/patches/series	2013-12-21 02:37:38.0 -0700
+++ c-icap-modules-0.3.1/debian/patches/series	2013-12-21 12:30:36.0 -0700
@@ -1 +1,2 @@
 0001-Fix-manpage.patch
+0002-Implicit-declaration.patch
diff -Nru c-icap-modules-0.3.1/debian/rules c-icap-modules-0.3.1/debian/rules
--- c-icap-modules-0.3.1/debian/rules	2013-12-21 02:37:38.0 -0700
+++ c-icap-modules-0.3.1/debian/rules	2013-12-21 12:41:32.0 -0700
@@ -10,7 +10,7 @@
 export DEB_BUILD_MAINT_OPTIONS	:= hardening=+bindnow
 
 %:
-	dh $@
+	dh $@ --with autoreconf
 
 override_dh_auto_configure:
 	dh_auto_configure -- \

Bug#727085: Now we don't depend on the weird libevent patch

[Paul Tarjan]

>> What else should I be doing to get this packaged up for inclusion in
>> debian?
> 
> Do you mean apart from persuading the copyright holder (Facebook, Inc.)
> to re-license hhvm under more general DFSG-free terms, such as the
> 3-clause BSD license?
> Your help in getting this issue solved would be highly appreciated, I
> think.
> Please re-read  http://bugs.debian.org/727085#60
> for further details on the licensing issue.

That rejection reason is pretty squarely aimed at people writing applications 
in the PHP language and makes sense for them. We are an alternative to php-src 
mostly coded in C++ and x86 assembly. (and after we prove ourselves I'll 
petition to be marked as an alternative for the php package).

As for the direct question. Much of our extension code was directly imported 
from php-src so we will absolutely be unable to relicense that portion. 
Untangling our contributions from the php-src ones is a very arduous task since 
there are many bug fixes to their code (some upstreamed, some not) as well as 
API changes and data structure replacements. We are happy with the php license 
so releasing the whole package under the same umbrella makes development much 
easier.

We are willing to relicense our portions under BSD but the technical splitting 
of the files into us vs them is just too much to ask.

Again, we are the first viable runtime alternative to php-src so I would argue 
that the rejection paragraph does not apply to us and didn't even consider us.

> I think László (who reads us in Cc) is still interested in packaging
> hhvm for inclusion in Debian.
> At least the bug is still an ITP bug and still owned by László, hence,
> unless he has just changed his mind, he should be still willing to work
> on the packaging...
> 
> I suggest you to get in touch with László and ask him whether and how
> you can help.

Laszlo, if you are listening out there please build us a package. You can see 
what I was doing at http://github.com/hhvm/packaging

> Thanks for being a Debian-friendly upstream developer and for offering
> to help!
> 
> Bye.
> 
> 
> -- 
> http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt
> New GnuPG key, see the transition document!
> . Francesco Poli .
> GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


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

Bug#730658: codeblocks: has icon in gnome (at least for me)

[Ove Kåven]

Den 21. des. 2013 16:50, skrev Andreas Cadhalpun:

Hi Ove,

at least for me, Code::Blocks still has icons in the Gnome 3 dock and
the application list. I have pretty much the same setup as you (Debian
testing, codblocks 12.11-3), so I don't see, what could cause the problem.

Do you still experience the issue? And if so, could you specify, which
upgrade(s) let the icons vanish?


Well, I've looked into things a bit, and I think it has something to do 
with me running fglrx. For some reason, I think Gnome is using smaller 
fonts and icons when running fglrx than when running the open-source 
radeon driver. (The codeblocks icon is visible if I run the latter.) Not 
sure where I can adjust that. Regardless, I think codeblocks ought to 
have an icon that is visible regardless of what font/icon size Gnome 
prefers, don't you think?



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

Bug#705614: to not conflict with python2.3-* without reason

[Felix Krull]

Well, I'm managing a repository of various officially unsupported Python
interpreters for Ubuntu (https://launchpad.net/~fkrull/+archive/deadsnakes)
and that unnecessary python2.3-minimal Conflicts in python-twisted-web gets
in the way a bit (at the time of this message, I haven't yet uploaded a 2.3
package though). So I'll just bump this and hope it gets fixed at some
point.

Bug#732800: midori: segfaults on kfreebsd-amd64

[Michael Gilbert]

package: src:midori
severity: grave
version: 0.4.3+dfsg-0.1

midori always segfaults during startup on kfreebsd-amd64.  Here is
some debugging info

$ gdb /usr/bin/midori
(gdb) run
Starting program: /usr/bin/midori

Program received signal SIGSEGV, Segmentation fault.
0x00080534fe59 in WTFCrash ()
   from /usr/lib/x86_64-kfreebsd-gnu/libjavascriptcoregtk-1.0.so.0
(gdb) backtrace
#0  0x00080534fe59 in WTFCrash ()
   from /usr/lib/x86_64-kfreebsd-gnu/libjavascriptcoregtk-1.0.so.0
#1  0x000805153ef1 in
JSC::Interpreter::execute(JSC::ProgramExecutable*, JSC::ExecState*,
JSC::JSObject*) ()
   from /usr/lib/x86_64-kfreebsd-gnu/libjavascriptcoregtk-1.0.so.0
#2  0x000805249418 in JSC::evaluate(JSC::ExecState*,
JSC::SourceCode const&, JSC::JSValue, JSC::JSValue*) ()
   from /usr/lib/x86_64-kfreebsd-gnu/libjavascriptcoregtk-1.0.so.0
#3  0x0008050c8012 in JSEvaluateScript ()
   from /usr/lib/x86_64-kfreebsd-gnu/libjavascriptcoregtk-1.0.so.0
#4  0x00465474 in sokoke_js_script_eval ()
#5  0x00425864 in _start ()

Best wishes,
Mike


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

Bug#727708: upstart proposed policy in Debian [and 1 more messages]

[Tollef Fog Heen]

]] Russ Allbery 

> Tollef Fog Heen  writes:
> 
> > sd-daemon.c is also intentionally designed to not have dependencies on
> > the rest of the systemd source and to be portable to non-linux
> > architectures too (but basically just stubs then) just so people can put
> > the file in their source and not have to fiddle with checking for
> > libraries and such if they find that tedious.
> 
> I agree with Ian's dislike of this approach.  We try to avoid embedded
> code copies, and I'm not sure why this would be an exception.  Yes, the
> code is fairly simple and hopefully doesn't contain (for example) security
> vulnerabilities, but it's possible to find bugs in just about anything.

Sure.  There's a tradeoff as always.  I wanted to point out that
embedding it is intentionally easy.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are


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

Bug#732799: lintian: description debian-watch-may-check-gpg-signature tag

[gregor herrmann]

Package: lintian
Version: 2.5.20
Severity: minor
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

N:This watch file does not include a means to verify the the upstream tar
N:using crytpographic signature.

doesn't sound perfect; esp. the duplicate "the".

Proposed patch against git:

#v+
diff --git a/checks/watch-file.desc b/checks/watch-file.desc
index 480b085..f1e6cb4 100644
- --- a/checks/watch-file.desc
+++ b/checks/watch-file.desc
@@ -143,7 +143,7 @@ Severity: pedantic
 Certainty: certain
 Ref: uscan(1)
 Info: This watch file does not include a means to verify the
- - the upstream tar using crytpographic signature.
+ upstream tarball using crytpographic signature.
  .
  If upstream distributions provide such signatures please
  use the pgpsigurlmangle options in this watch file
#v-

Cheers,
gregor


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

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

Versions of packages lintian depends on:
ii  binutils   2.24-2
ii  bzip2  1.0.6-5
ii  diffstat   1.57-1
ii  file   1:5.14-2
ii  gettext0.18.3.1-2
ii  hardening-includes 2.5
ii  intltool-debian0.35.0+20060710.1
ii  libapt-pkg-perl0.1.29+b1
ii  libarchive-zip-perl1.30-7
ii  libclass-accessor-perl 0.34-1
ii  libclone-perl  0.35-1
ii  libdpkg-perl   1.17.5
ii  libemail-valid-perl1.192-1
ii  libfile-basedir-perl   0.03-1
ii  libipc-run-perl0.92-1
ii  liblist-moreutils-perl 0.33-1+b2
ii  libparse-debianchangelog-perl  1.2.0-1
ii  libtext-levenshtein-perl   0.06~01-2
ii  libtimedate-perl   2.3000-1
ii  liburi-perl1.60-1
ii  man-db 2.6.5-2
ii  patchutils 0.3.2-3
ii  perl [libdigest-sha-perl]  5.18.1-5
ii  t1utils1.37-2

Versions of packages lintian recommends:
ii  libautodie-perl 2.21-1
ii  libperlio-gzip-perl 0.18-1+b3
ii  perl-modules [libautodie-perl]  5.18.1-5

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.17.5
ii  libhtml-parser-perl3.71-1+b1
ii  libtext-template-perl  1.46-1
ii  xz-utils   5.1.1alpha+20120614-2

- -- no debconf information

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

iQIcBAEBCAAGBQJStf7WAAoJELs6aAGGSaoGJNcQAKH75f626kiJEH4jsQFudxkP
7L2BfQeV13dE8F3dK2sX1thF2c5D3Gs28wS9Nq2YDDMmJpBoL19P/fPPvWgOuwh3
/WSrjH375MN/CRRJ52onG2xDbwO9kPpyXMw15jKaMG5EPtjzQk/BjACYbP2YUwPM
KM0vxN3U7YdHoLEGpFU0frdEvQPVIDLZezbcCcQrdVTlgfRYVUrFkJAqnZYe6EuX
lNxs9St8k/VswQrnCm3gxXtX8PusvYZTJL/ShPYIFyxJmq2aCqSlON4ECwusbjOm
7HxTuyGR1dWgu/XTX2B48eD+VCqALTzL7BdPbkQ4sSBYwKpVpZpy0W2Q5QmO2Qpp
/pVyfKlxlnH1cBmP+8uVQ+1dMdxtkUHy9UwVGSWIAht9rEYPzCixsqmleQiRWWHt
aFWY6PVvNvHNemMVZk93GkJItXGe+aXM3TXg67+y6+JWUymlepssPy5hrgqgWM3n
cqdVpiHHDU9f7GlBIBkGs96VCYwQVmnsEWmgEo82E69WTEgJia/Gf27a9vaClm7E
mQPMmPSIpHzQfEcA7JHlLmIQiKFVbalu1gzWTIeXQyccrHl1ppIehAou8YfIvzMi
aii3E0CDKQIDUIj7UgS1wNsBEYL/NEAVqZa3izMZ2eH8eyy++gkKNxDd1Unl2QbA
qXdWy9kJr/jasbiW70rc
=vNpq
-END PGP SIGNATURE-


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

Bug#732798: document --full as an option for status

[Russ Allbery]

Package: systemd
Version: 204-5
Severity: minor

(Wow, the thousands of lines of systemd dump included in bug reports
by default seems a little excessive.)

systemctl status  truncates log messages from the journal to
80 columns by default.  Some experimentation revealed that --full will
prevent this and show the full log message, but this isn't documented
in the systemctl man page.  --full only mentions a couple of other
commands, and status doesn't reference --full.

Could you add a cross-reference or two?

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

Kernel: Linux 3.11-2-amd64 (SMP w/8 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 systemd depends on:
ii  initscripts  2.88dsf-43
ii  libacl1  2.2.52-1
ii  libaudit11:2.3.2-2
ii  libc62.17-97
ii  libcap2  1:2.22-1.2
ii  libcryptsetup4   2:1.6.1-1
ii  libdbus-1-3  1.6.18-2
ii  libgcrypt11  1.5.3-2
ii  libkmod2 9-3
ii  liblzma5 5.1.1alpha+20120614-2
ii  libpam0g 1.1.3-10
ii  libselinux1  2.2.1-1
ii  libsystemd-daemon0   204-5
ii  libsystemd-journal0  204-5
ii  libsystemd-login0204-5
ii  libudev1 204-5
ii  libwrap0 7.6.q-24
ii  udev 204-5
ii  util-linux   2.20.1-5.5

Versions of packages systemd recommends:
ii  libpam-systemd  204-5

Versions of packages systemd suggests:
pn  systemd-ui  

-- 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#732676: flashplugin-nonfree: Please leave the "nosse2" option

[Bart Martens]

tags 732676 moreinfo
stop

Hi Francesco,

Last time I checked the nosse2 option was broken due to changes at Adobe.  Have
more changes taken place so that the nosse2 option can work again ? Do you know
what the nosse2 did and how it worked ?

Regards,

Bart Martens


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

Bug#732613: RFS: xye/0.12.2+dfsg-1 [ITA]

[Andreas Rönnquist]

> Hi Andreas,
> 
> On Thu, Dec 19, 2013 at 12:00:25PM +0100, Andreas Rönnquist wrote:
> > I am looking for a sponsor for my package "xye"
> 
> I like Xye, so I thought I'd give your package a look, with the intent
> of sponsoring it eventually. 

Thank you, much appreciated!

> I've just got a couple of comments:
> * debian/repack is nice but seems like an awful lot of effort to
>   remove two files; have you noticed the new Files-Excluded header in
>   debian/copyright which uscan now supports?

Ah, I hadn't - thanks! Well, I am kind of irritated on that bug I
mentioned in README.source (##635920) which makes it impossible to use
git-import-orig --uscan in combination with a debian/repack script... I
guess using the mentioned Files-Excluded would solve this?

> * The manpage doesn't follow the typical Unix manpage style, although
>   if there are no command-line options then the text you've written is
>   good enough. You might get bug reports requesting the manpage to
>   document how to play but until then...

I'll think I'll wait for those bug reports... ;)

> * You should update debian/copyright to include yourself.

Done.

> 
> Incidentally while trying to determine whether xye takes any
> command-line parameters, I discovered that specifying any parameter
> causes xye to crash! (I'll file a bug...)
> 

Oh! I have managed to include a patch that fixes this problem, but when
doing so I found more related problems - if running with a folder which
doesn't contain any data files it still segfaults (but later). I
will try to put together a patch for this problem too.

(I have pushed my current changes to alioth).

Would you like me to put together a new package on mentors, or do you
simply get the gbp packaging from alioth?

best regards, and many thanks
-- Andreas Rönnquist
gus...@gusnan.se


signature.asc
Description: PGP signature

Bug#732754: [Pkg-openssl-devel] Bug#732754: openssl: CVE-2013-6449: crash when using TLS 1.2

[Salvatore Bonaccorso]

Hi Kurt,

On Sat, Dec 21, 2013 at 09:35:38AM +0100, Kurt Roeckx wrote:
> On Sat, Dec 21, 2013 at 08:16:42AM +0100, Salvatore Bonaccorso wrote:
> > Package: openssl
> > Version: 1.0.1e-2
> > Severity: grave
> > Tags: security upstream patch
> > 
> > Hi,
> > 
> > the following vulnerability was published for openssl.
> > 
> > CVE-2013-6449[0]:
> > crash when using TLS 1.2
> > 
> > It was reported in Apache Traffic Server[1] and upstream at [2], see
> > also [3]. I was not able to reproduce any crash myself, just checking
> > against the openssl source package to verify upstrem patches apply.
> > See [4] and [5] for the patches applied.
> 
> I was expecting this, and planning an upload for it already.  I'll
> prepare an upload later today.

Thanks!

> I have a bunch of other patches that I'd like to see reach stable,
> but I'm not sure how many of those you like in a DSA.

Okay. Could you sent what you are thinking off, to the security team
alias, so that somebody the team can comment/have a look/...? Is this
about #720426? (If so an 'ack' from the Release Team would be needed
also to have them included).

Regards,
Salvatore


signature.asc
Description: Digital signature

Bug#719219: upgrade to wheezy failed due to xemacs21 not available anymore

[Rob Browning]

tags 719219 +moreinfo
thanks

Harald Dunkel  writes:

> sorry, but I don't see who thinks that xemacs21 is still
> installed. AFAICS it was removed first, and the postremove
> script of another package depended on it.
>
> This is long gone, anyway. In the meantime I have upgraded
> all hosts to Wheezy or Jessie, working around the problem.

No problem; I know it's old.  I'll mark it "moreinfo" for now, and we'll
see if there are any further reports.  If not, after a while, I'll
assume we can close it.

Thanks for the help.
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4


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

Bug#732797: PKG_CHECK_MODULES should report the module name, not variable prefix

[Russ Allbery]

Package: pkg-config
Version: 0.26-1
Severity: minor

In Autoconf output from PKG_CHECK_MODULES in pkg.m4, the "checking for"
message refers to the first argument of PKG_CHECK_MODULES, the variable
prefix, instead of the second argument, the module being checked for.

I've seen this result in strange output (like ALL CAPS module names) in
various packages, and now have run into it in one of mine.  When
probing for the libsystemd-daemon module, one can't use a variable
prefix that matches the module name (since - isn't allowed in variable
names), so the Autoconf output is going to refer to something odd, like
SYSTEMD_DAEMON or libsystemd_daemon.

I think the status output should reference the module name being
probed for, both because it looks nicer and because, when debugging
problems, this references the actual thing being probed for on the
system, rather than an internal implementation detail.

This could be easily done by changing the line:

AC_MSG_CHECKING([for $1])

in pkg.m4 to:

AC_MSG_CHECKING([for $2])

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

Kernel: Linux 3.11-2-amd64 (SMP w/8 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 pkg-config depends on:
ii  libc6 2.17-97
ii  libglib2.0-0  2.36.4-1
ii  libpopt0  1.16-8

pkg-config recommends no packages.

pkg-config 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#725743: fixed in procps 1:3.3.9-1

[Ivo De Decker]

Control: reopen -1
Control: notfixed -1 1:3.3.9-1
Control: found -1 1:3.3.9-1

Hi Craig,

On Wed, Dec 18, 2013 at 12:00:06PM +, Craig Small wrote:
>  - Skip some tests if kill cannot be found Closes: #725743

It seems procps 1:3.3.9-1 still doesn't build on s390x and ia64.

Cheers,

Ivo


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

Bug#732717: growisofs - TRACKING SERVO FAILURE - Input/output error "

[Thomas Schmitt]

Hi,

> isoinfo gave me this.. 

Looks like quite a normal bootable ISO 9660 filesystem image.
Much like the Debian and Ubuntu ISOs which get burned to DVD
all over the world.

Still hard to believe that the problem should sit in this
image and not in burner drive and medium.

How much evidence do you have for your theory ?
(How often did it not work with that image, how often did it
 work with others ? How many media did you try ?)


Have a nice day :)

Thomas


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

Bug#732400: [Debichem-devel] Bug#732400: gromacs: Illegal instruction in all programs on Intel Core 2 CPU

[Nicholas Breen]

On Tue, Dec 17, 2013 at 05:57:10PM +0100, Andras Szilagyi wrote:
> Package: gromacs
> Version: 4.6.5-1
> Severity: important
> 
> All gromacs programs crash right at the start, reporting an illegal hardware 
> instruction while printing the program options. 
[snip]

This is my fault - although I did change the build setup to avoid this very
problem, I was also testing the build option that reenables all CPU extensions,
and it looks like I screwed up and uploaded the wrong set of binaries on amd64.
I apologize for the mistake, and will either get it binNMU'd or simply upload a
new (and more strictly verified!) version in the next day or two.


-- 
Nicholas Breen
nbr...@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#732623: [Pkg-xfce-devel] Bug#732623: lightdm-gtk-greeter: Hibernate and Restart buttons disappear after first login/logout

[Vincent Lefevre]

On 2013-12-21 10:25:50 +0100, Yves-Alexis Perez wrote:
> Honestly I have pretty much no idea how logind “works” so you're on your
> own here.

I would like to know whether other users can reproduce the problem
with twm, just by logging in then logging out. Since twm is a
minimalist window manager, which doesn't start anything special,
this could give an idea...

-- 
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#732796:

[Ma Xiaojun]

Package: kbd
Version: 1.15.5-1
Severity: wishlist

Dear Maintainer,

This package uses open(1).
This usage is neither standard (in terms of LSB and POSIX) nor popular.

The unpopularity can be seen as BusyBox implements openvt(1) only [1]
while toybox
has no plan for openvt(1) or open(1) [2].

Meanwhile, some other OS like OSX (and probably Haiku) use open(1) to provide
desktop integration [3]. Similar functionality is provided by xdg-open(1) now on
Linux. Some people, including I, believe that giving open(1) to xdg stuff is
probably a good idea [4][5].

The very first step would be discontinue open(1) that is symbol linked to
openvt(1). In other words, it is to remove open(1) from this package.

1. http://www.busybox.net/downloads/BusyBox.html
2. http://www.landley.net/toybox/status.html
3. 
https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/open.1.html
4. http://lists.freedesktop.org/archives/xdg/2013-December/012936.html
5. http://lists.freedesktop.org/archives/xdg/2013-December/012969.html


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

Bug#732780: Fwd: [libtomcrypt] Error: operand size mismatch for `movq' (#28)

[Mathieu Malaterre]

-- Forwarded message --
From: rofl0r 
Date: Sat, Dec 21, 2013 at 8:15 PM
Subject: Re: [libtomcrypt] Error: operand size mismatch for `movq' (#28)
To: libtom/libtomcrypt 


seems this #ifdef here is to blame
https://github.com/libtom/libtomcrypt/blob/master/src/headers/tomcrypt_macros.h#L101

can you paste output of your compiler when invoked as gcc -E -dM - <
/dev/null please ?

Bug#728789: dwb: crash with segmentation fault very often

[Sebastian Ramacher]

Control: tags -1 = confirmed
Control: reassign -1 libwebkitgtk-3.0-0 2.2.1-2
Control: affects -1 + dwb luakit

On 2013-12-21 16:27:00, Florian Birée wrote:
> Le Sat, 30 Nov 2013 18:04:06 +0100,
> Sebastian Ramacher  a écrit :
> > >A working browser ;-)
> > 
> > I tried to reproduce the crash but I wasn't able to. Does this work
> > with other webkit based browsers?
> 
> Exactly the same problem with luakit.
> 
> > > Versions of packages dwb depends on:
> > > ii  libc6   2.17-93
> > > ii  libgdk-pixbuf2.0-0  2.28.2-1
> > > ii  libglib2.0-02.36.4-1
> > > ii  libgnutls26 2.12.23-8
> > > ii  libgtk-3-0  3.8.6-1
> > > ii  libjavascriptcoregtk-3.0-0  2.2.1-2
> > > ii  libpango1.0-0   1.36.0-1
> > > ii  libsoup2.4-12.44.1-1
> > > ii  libwebkitgtk-3.0-0  2.2.1-2
> > 
> > There are newer versions of libwebkitgtk-3.0-0 and
> > libjavascriptcoregtk-3.0-0 available in unstable. Does the crash go
> > away after an upgrade of these two packages?
> 
> Same problem with libwebkitgtk-3.0-0 and libjavascriptcoregtk-3.0-0
> 2.2.3-1.
> 
> But the bug doesn't appear with stable versions of
> libwekitgtk-3.0-0 and libjavascriptcoregtk-3.0-0 (versions 1.8.1-3.4).
> It's my current workaround.

Thank you. Reassigning to libwebkitgtk-3.0-0 since the bug occurs with
multiple webkit based browsers.

I've now successfully reproduced the crash. It only happens on i386 for
me. amd64 works fine. gdb gives me the following backtrace when I try to
follow any link from http://fr.wikipedia.org in dwb:

#0  0xf67f25b5 in WebCore::EventListenerIterator::EventListenerIterator 
(this=0xc924, target=0x566ed940)
at ../Source/WebCore/dom/EventListenerMap.cpp:239
#1  0xf6629b09 in visitJSEventListeners (visitor=..., this=0x566ed940) at 
../Source/WebCore/dom/EventTarget.h:186
#2  WebCore::JSNode::visitChildren (cell=0xee83f8c8, visitor=...) at 
../Source/WebCore/bindings/js/JSNodeCustom.cpp:202
#3  0xf576e5a3 in visitChildren (cell=0xee83f8c8, visitor=...) at 
../Source/JavaScriptCore/heap/SlotVisitor.cpp:95
#4  JSC::SlotVisitor::drain (this=this@entry=0xf1b047c4) at 
../Source/JavaScriptCore/heap/SlotVisitor.cpp:148
#5  0xf5771650 in donateAndDrain (this=0xf1b047c4) at 
../Source/JavaScriptCore/heap/SlotVisitorInlines.h:208
#6  JSC::Heap::markRoots (this=this@entry=0xf1bc) at 
../Source/JavaScriptCore/heap/Heap.cpp:586
#7  0xf57730ff in JSC::Heap::collect (this=this@entry=0xf1bc, 
sweepToggle=sweepToggle@entry=JSC::Heap::DoSweep)
at ../Source/JavaScriptCore/heap/Heap.cpp:760
#8  0xf5773a4c in JSC::Heap::collectAllGarbage (this=0xf1bc) at 
../Source/JavaScriptCore/heap/Heap.cpp:713
#9  0xf65d7bcb in WebCore::collect () at 
../Source/WebCore/bindings/js/GCController.cpp:42
#10 0xf65d7ea5 in WebCore::Timer::fired 
(this=0xf1abe118) at ../Source/WebCore/platform/Timer.h:114
#11 0xf658ade2 in WebCore::ThreadTimers::sharedTimerFiredInternal 
(this=0xf1ab50a0) at ../Source/WebCore/platform/ThreadTimers.cpp:129
#12 0xf658ae65 in WebCore::ThreadTimers::sharedTimerFired () at 
../Source/WebCore/platform/ThreadTimers.cpp:105
#13 0xf65a10db in WebCore::timeout_cb () at 
../Source/WebCore/platform/gtk/SharedTimerGtk.cpp:49
#14 0xf53f00b1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#15 0xf53ef42e in g_main_context_dispatch () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
#16 0xf53ef7d8 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#17 0xf53ef898 in g_main_context_iteration () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
#18 0xf5ba6e44 in g_application_run () from 
/usr/lib/i386-linux-gnu/libgio-2.0.so.0
#19 0x5657561c in ?? ()
#20 0x565720c4 in main ()

For luakit the backtrace looks the same.

Regards
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#732794: migrate ftbfs in unstable

[Matthias Klose]

Package: migrate
Version: 0.8.2-2
Severity: serious
Tags: jessie, sid

dh build --with python2,sphinxdoc --buildsystem=python_distutils
   dh_testdir -O--buildsystem=python_distutils
   dh_auto_configure -O--buildsystem=python_distutils
   dh_auto_build -O--buildsystem=python_distutils
pyversions: missing X(S)-Python-Version in control file, fall back to
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
error in setup command: Error parsing
/scratch/packages/tmp/d/migrate-0.8.2/setup.cfg: Exception: Versioning for this
project requires either an sdist tarball, or access to an upstream git 
repository.
dh_auto_build: python setup.py build --force returned exit code 1
make: *** [build] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2


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

Bug#732795: don't build-depend on python-sqlite, included in the python standard library

[Matthias Klose]

Package: migrate
Version: 0.8.2-2
Severity: important
Tags: jessie, sid

don't build-depend on python-sqlite, included in the python standard library


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

Bug#732781: including old versions in changes

[Ian Jackson]

Joey Hess writes ("Bug#732781: including old versions in changes"):
> For some reason dgit has started including multiple past releases in the
> .changes files. This despite all recent releases having been made by
> dgit. Example .changes attached has releases back to 5.20131118.

Sorry about this.  It was a version comparison sense error.  I've sent
the fix to unstable but if you want you can apply this.

Ian.

diff --git a/dgit b/dgit
index 9b895b0..61af3b8 100755
--- a/dgit
+++ b/dgit
@@ -1803,7 +1803,7 @@ sub changesopts () {
my @vsns = archive_query('archive_query');
if (@vsns) {
@vsns = map { $_->[0] } @vsns;
-   @vsns = sort { version_compare_string($a, $b) } @vsns;
+   @vsns = sort { -version_compare_string($a, $b) } @vsns;
$changes_since_version = $vsns[0];
progress "changelog will contain changes since $vsns[0]";
} else {


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

Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1

[Josh Triplett]

On Mon, Dec 16, 2013 at 11:53:01AM +0100, BubuXP wrote:
> I found the cause (maybe).
> Probably the fuzzy fonts are all OpenType fonts. Starting from
> freetype 2.5.0.1, the Adobe CFF engine is the default rasterizer for
> those class of fonts.
> https://blogs.adobe.com/typblography/2013/05/adobe-contributes-cff-rasterizer-to-freetype.html
> 
> From: 
> http://lists.freedesktop.org/archives/fontconfig/2013-December/005026.html
> > If I remember correctly the new Adobe CFF hinter hinting levels are out of 
> > sync with the autohinter used with TTF fonts.
> 
> As reported in the above link, to mitigate the bug this fix should be
> enabled by default in the next fontconfig version (2.11.1, that will
> be released soon):
> 
> 
>   
> CFF
>   
>   
> hintslight
>   
> 

I can confirm that adding that to ~/.config/fontconfig/fonts.conf
(with the appropriate XML wrapping for a fontconfig config file) solves
the problem.  I took screenshots of the same dialog with 2.4.9-1.1 and
with 2.5.1-1 using the above config snippet, and got binary-identical
screenshot PNGs.

On Mon, Dec 16, 2013 at 09:50:33AM -0800, Steve Langasek wrote:
> Use of the Adobe hinter is optional and the default can be changed at
> compile time.  Does someone who's hitting this bug want to try rebuilding
> freetype locally with the option changed, to see if that fixes it?  (If not,
> I'll prepare a test build for people to try, but it'll take a few days
> before I can get to it.)

I'd actually recommend *against* disabling the new hinter.  I've seen
several examples of hinted fonts displaying better with the new hinter.
I'd simply recommend fixing the hintstyle mechanism such that it
respects the same configuration as the previous hinter, so that anyone
using slight hinting with the previous hinter will continue to get
slight hinting with the new hinter.

- Josh Triplett


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

Bug#732613: RFS: xye/0.12.2+dfsg-1 [ITA]

[Stephen Kitt]

Hi Andreas,

On Thu, Dec 19, 2013 at 12:00:25PM +0100, Andreas Rönnquist wrote:
> I am looking for a sponsor for my package "xye"

I like Xye, so I thought I'd give your package a look, with the intent
of sponsoring it eventually. I've just got a couple of comments:
* debian/repack is nice but seems like an awful lot of effort to
  remove two files; have you noticed the new Files-Excluded header in
  debian/copyright which uscan now supports?
* The manpage doesn't follow the typical Unix manpage style, although
  if there are no command-line options then the text you've written is
  good enough. You might get bug reports requesting the manpage to
  document how to play but until then...
* You should update debian/copyright to include yourself.

Incidentally while trying to determine whether xye takes any
command-line parameters, I discovered that specifying any parameter
causes xye to crash! (I'll file a bug...)

Regards,

Stephen


signature.asc
Description: Digital signature

Bug#726398: I have a similar problem with the USB mouse.

[Den V. Kaftaev]

UPD: This bug occurs only when running on battery. When the laptop is
powered by AC, the mouse works fine.


2013/12/19 Den V. Kaftaev 

> I have a similar problem with the mouse
> Mouse stops working after 2 seconds of inactivity. Scrolling and buttons
> at the same time continue to work. I clicked the button to "wake " the
> mouse.
> Dmesg:
> [3420.390279] input: A4Tech PS / 2 + USB Mouse as / devices/pci: 00
> / : 00:14.0 / usb1/1-6/1-6: 1.0/input/input17
> [3420.390658] a4tech 0003:09 DA: 0006.0002: input, hidraw0: USB HID v1.10
> Mouse [A4Tech PS / 2 + USB Mouse] on usb-  :00:14.0 -6 / input0
> [3421.285223] systemd-logind [ 3659 ]: Removed session c22.
> [3421.285614] systemd-logind [ 3659 ]: New session c23 of user gtt.
> [3429.592183] xhci_hcd :00:14.0: power state changed by ACPI to D3cold
> [3443.311561] systemd-logind [ 3659 ]: Removed session c23.
> [3443.311974] systemd-logind [ 3659 ]: New session c24 of user gtt.
> [3468.579112] xhci_hcd :00:14.0: power state changed by ACPI to D0
> [3468.681006] xhci_hcd :00:14.0: setting latency timer to 64
>
> gtt @ mercury: ~ $ uname-a
> Linux mercury 3.11- 2 -amd64 # 1 SMP Debian 3.11.10-1 (2013-12-04) x86_64
> GNU / Linux
>
> I think the problem started after I installed the packages for acpi:
> acpi-support laptop-mode-tools laptop-detect. And  I see that similar
> problems only in people with laptops.
> As s temporaly solution:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1116525/comments/9
>
> --
> Regards,
> Den V. Kaftaev
>



-- 
Regards,
Den V. Kaftaev

Bug#732412: chromium

[Serge]

I must  say, problem is resolved with today's update of linux image.
linux-image-3.2.0-4-rt-amd64 3.2.53-2 proposed updates

-- 
Claws Mail version 3.8.1
Linux debian 3.2.0-4-rt-amd64 #1 SMP PREEMPT RT Debian 3.2.53-2 x86_64
GNU/Linux


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

Bug#708297: SDL-mixer and SDL-sound: Problem with mp3 support

[Manuel A. Fernandez Montecelo]

Control: tag 708297 + upstream

2013/5/15 Vincent Prat :
>
>> I don't really know what's happening, just suggestions below.
>>
>> Were you using the same Debian architecture in the past, or did you
>> switch from i386->amd64 between working and failing?
>
> The only change between working and failing is the upgrade from squeeze to
> wheezy.
>
>
>>
>> And by the way, did you also try other format types (ogg, flac, wav)
>> and observe any anomaly?
>
> I have tried all these formats without any problem.

After compiling the binaries (had to use -fpermissive [1]), this is what I get:

--
$ ./playsound_simple ../scream.mp3
Now playing [../scream.mp3]...
Error decoding file: (null)

$ ./playsound ../scream.mp3
Now playing [../scream.mp3]...
Error in decoding sound file!
  reason: [MPGLIB: Free format not supported.].
--

So it seems that the .mp3 that you are playing is not supported by the
library.  From this reply of the author in the support mailing list
(from 2007, but the code does not seem to have changed much since
then, and indeed the code seems very fragile):

--
http://icculus.org/pipermail/sdlsound/2007-January/000655.html

mpglib is deeply unforgiving about file corruption...it gives up
immediately when it sees data it doesn't expect, which is a problem with
a lot of mp3s out there.

Also, unfortunately, one of the things it doesn't expect is ID3v2 tags,
so that excludes the vast majority of mp3s created in the past few
years. This is fairly easy to fix, just no one ever has (for ID3v1, we
just look for the struct in the last 128 bytes of the mp3, and don't
pass it to mpglib if we see it. ID3v2's layout is somewhat more
complicated, but something similar can still be done). In a more ideal
world, someone would take the time to understand the mpglib code and
make it recover from bad data. Or replace it with a different mp3
decoder, but I haven't found one that isn't GPL'd.

SDL_sound's SMPEG backend is more forgiving of strange data, but has its
own problems too. Use Ogg files if you control your content.  :)

As you can tell by my long apology here, we're sort of at the mercy of a
  disproportionate amount of third-party code here.
--


Cheers.
-- 
Manuel A. Fernandez Montecelo 


[1]

g++ -fpermissive -I/usr/include/SDL -lSDL -lSDL_sound
playsound_simple.c -o playsound_simple

g++ -fpermissive -I/usr/include/SDL -lSDL -lSDL_sound -DHAVE_SIGNAL_H
playsound.c -o playsound


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

Bug#730472: bug#15758: grep 2.15 calls abort() on larger searches with -P

[Jim Meyering]

On Sat, Dec 21, 2013 at 10:46 AM, Jim Meyering  wrote:
> I expect to push that patch as-is and defer to a separate commit
> (or maybe even skip altogether) any portability hack that might warn
> or disable PCRE support when detecting the broken library.

Pushed.  Let's take any discussion of grep's workaround for Debian's
PCRE problem to a new thread/issue.


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