Bug#728179: Is anyone handling this?

[Mattias Ellert]

Is anyone receiving this bug report? It was filed a month ago and I have
not received any response so far.

Since my last mail nordugrid-arc was updated to a new version and was
built with the new gridsite, so it no longer needs a binnmu.

 nmu gridsite . amd64 i386 powerpc sparc . -m "Rebuild against libgsoap4"
 nmu voms . ALL . -m "Rebuild against libgsoap4"
 nmu cgsi-gsoap . ALL . -m "Rebuild against libgsoap4"
 nmu lcgdm . ALL . -m "Rebuild against libgsoap4"
 dw lcgdm . ALL . -m "libcgsi-gsoap-dev (>> 1.3.5-2+b1)"
 nmu srm-ifce . ALL . -m "Rebuild against libgsoap4"
 dw srm-ifce . ALL . -m "libcgsi-gsoap-dev (>> 1.3.5-2+b1)"
 nmu gfal2 . ALL . -m "Rebuild against libgsoap4 and libgridsite2"
 dw gfal2 . ALL . -m "srm-ifce-dev (>> 1.18.0-1+b1)"
 nmu condor . ALL . -m "Rebuild against libgsoap4"
 nmu virtualbox . amd64 i386 . -m "Rebuild against libgsoap4"




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

Bug#725596: Bug#728845: nmu fixing two issues

[Michael Gilbert]

On Sat, Nov 30, 2013 at 1:14 AM, Salvatore Bonaccorso wrote:
> Hey Mike,
>
> On Sat, Nov 16, 2013 at 07:15:49PM -0500, Michael Gilbert wrote:
>> control: tag -1 patch
>> control: tag -1 pending
>>
>> Hi, I've uploaded an nmu fixing these two issues to delayed/5.  Please
>> see attached patch.
>
> Looks like your NMU did not enter the archive. Could you check what
> was the rejection message (or waas it cancelled?).

It mysteriously disappeared from the deferred page one day, so I guess
somebody decided to cancel it.  Not sure if they thought something was
wrong with it, but that would be a nice thing to know in order to fix
whatever that was.

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#730830: ocaml: Please add powerpcspe to the list of native architectures

[Stéphane Glondu]

Le 29/11/2013 23:48, Roland Stigge a écrit :
> please add powerpcspe to the list of native architectures. I.e., add
> "powerpcspe" to:
> 
> * debian/native-archs
> * debian/natdynlink-archs
> * debian/control
> 
> similar as powerpc.
> 
> I'm attaching a patch that fixes an asm build problem on powerpcspe since some
> CPU registers don't exist on powerpcspe, so they can't be saved and restored.

Aren't those registers also used by generated code? Does ocamlopt
produce working executables with this patch? Does the whole test-suite pass?

> Further, please add libiberty-dev to the build-deps since this prevents a 
> build
> error.

Why?


Cheers,

-- 
Stéphane


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

Bug#730847: virtualbox-ose: cue not recognized only iso

[yellow]

Package: virtualbox-ose
Version: 3.2.10-dfsg-1+squeeze1
Severity: normal

Hi 

Most cdroms are either bin or iso, with a cue file alternatively, in
general when one backup. there is too the bin making from linux.
(clone)

Please add thesee formats as soon as possible. 

thanks


-- System Information:
Debian Release: 6.0.3
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages virtualbox-ose depends on:
ii  adduser3.112+nmu2add and remove users and groups
ii  libc6  2.11.3-4  Embedded GNU C Library: Shared lib
ii  libcurl3   7.21.0-2.1+squeeze4   Multi-protocol file transfer libra
ii  libgcc11:4.4.5-8 GCC support library
ii  libpng12-0 1.2.44-1+squeeze4 PNG library - runtime
ii  libpython2.6   2.6.6-8+b1Shared Python runtime library (ver
ii  libsdl1.2debian1.2.14-6.1Simple DirectMedia Layer
ii  libssl0.9.80.9.8o-4squeeze14 SSL shared libraries
ii  libstdc++6 4.4.5-8   The GNU Standard C++ Library v3
ii  libvncserver0  0.9.7-2+b1API to write one's own vnc server
ii  libx11-6   2:1.3.3-4+squeeze1X11 client-side library
ii  libxcursor11:1.1.10-2X cursor management library
ii  libxext6   2:1.1.2-1 X11 miscellaneous extension librar
ii  libxml22.7.8.dfsg-2+squeeze5 GNOME XML library
ii  libxmu62:1.0.5-2 X11 miscellaneous utility library
ii  libxt6 1:1.0.7-1 X11 toolkit intrinsics library
ii  python 2.6.6-3+squeeze6  interactive high-level object-orie
ii  python-central 0.6.16+nmu1   register and build utility for Pyt
ii  zlib1g 1:1.2.3.4.dfsg-3  compression library - runtime

Versions of packages virtualbox-ose recommends:
ii  libgl1-mesa-glx [ 7.7.1-6A free implementation of the OpenG
ii  libqt4-opengl 4:4.6.3-4+squeeze1 Qt 4 OpenGL module
ii  libqtcore44:4.6.3-4+squeeze1 Qt 4 core module
ii  libqtgui4 4:4.6.3-4+squeeze1 Qt 4 GUI module
ii  virtualbox-ose-dk 3.2.10-dfsg-1+squeeze1 x86 virtualization solution - kern
ii  virtualbox-ose-qt 3.2.10-dfsg-1+squeeze1 x86 virtualization solution - Qt b

Versions of packages virtualbox-ose suggests:
ii  libasound2 1.0.23-2.1shared library for ALSA applicatio
ii  libpulse0  0.9.21-3+squeeze1 PulseAudio client libraries
ii  vde2   2.2.3-3   Virtual Distributed Ethernet
pn  virtualbox-guest-addit (no description available)

-- 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#730848: postfix-ldap: Please allow SASL binds

[Guilhem Moulin]

Package: postfix-ldap
Version: 2.10.2-1
Severity: wishlist
Tags: patch

Dear Maintainer,

LDAP SASL binds have been added to Postfix back to v2.8, at the expense
of a flag in the CCARGS [1].

It would be great if postfix-ldap included SASL support. As far as I can
tell, the change boilds down to a mere modification in debian/rules:

-8<-

--- debian/rules.orig   2013-11-30 08:42:40.120610017 +0100
+++ debian/rules2013-11-30 08:44:52.449266206 +0100
@@ -45,7 +45,8 @@
 STRIP=y
 endif
 
-CCARGS=-DDEBIAN -DMAX_DYNAMIC_MAPS -DHAS_PCRE -DHAS_LDAP -DHAS_SQLITE \
+CCARGS=-DDEBIAN -DMAX_DYNAMIC_MAPS -DHAS_PCRE -DHAS_LDAP -DUSE_LDAP_SASL \
+   -DHAS_SQLITE \
-DMYORIGIN_FROM_FILE \
$(shell getconf LFS_CFLAGS) \
-DHAS_CDB \

-8<-

Many thanks!
Cheers,
-- 
Guilhem.

[1] http://www.postfix.org/LDAP_README.html#build , last paragraph.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (800, 'testing'), (700, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)

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

Versions of packages postfix-ldap depends on:
ii  libc6  2.17-97
ii  libldap-2.4-2  2.4.31-1+nmu2+b1
ii  postfix2.10.2-1

postfix-ldap recommends no packages.

postfix-ldap suggests no packages.

-- no debconf information


signature.asc
Description: Digital signature

Bug#729276: staden-io-lib-utils: bufferoverflow in index_tar

[Charles Plessy]

Le Sun, Nov 10, 2013 at 09:20:08PM -0500, Sang Kil Cha a écrit :
> Package: staden-io-lib-utils
> Version: 1.12.4-1
> Severity: grave
> Tags: security
> Justification: user security hole
> 
> index_tar has a buffer overflow vulnerability. A PoC file is attached.

Hello,

thanks for the report.  Have you also submitted it upstream ?  Do you
have a suggestion on how to solve the problem ?

Cheers,

-- 
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan


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

Bug#727708: systemd (security) bugs (was: init system question)

[Josselin Mouette]

Le vendredi 29 novembre 2013 à 17:55 +0100, Josselin Mouette a écrit : 
> Indeed, systemd has not been written with security in mind.

Obviously, such a subjective judgment of valor does not mean the same to
me as to other developers. It is easy to quote it out of context and say
“oh, look! some systemd advocate said that it is insecure! of course MY
init system of choice is more secure!”, but it is merely a fallacy since
we are not talking about the same thing.

Therefore, I have to retract this statement. 

-- 
 .''`.  Josselin Mouette
: :' :
`. `'
  `-


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

Bug#730849: network-manager-kde: KDE network manager, can't change from DHCP to static.

[Giorgos Kostopoulos]

Package: network-manager-kde
Version: 1:0.9.0.3-1
Severity: important

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?

KDE Network Manager can't change my wired connection from DHCP to static.


   * What was the outcome of this action?

On Wired window -> clicking the connection -> Edit -> Method -> Manual.
Here no matter what I'm entering, it can't save the changes.
After entering the values -> OK -> everything is lost.
Reopening the Edit window results to a blank window DHCP again.
Also testing with third-party tools, confirms that DHCP never changed to
static.

   * What outcome did you expect instead?

To save the changes (after OK).


Note 1: Wicd never worked for me, either.
Note 2: I opened a thread on fora, but a solution couldn't found.
Here: http://forums.debian.net/viewtopic.php?f=5&t=109403

My system is Wheezy (fresh installation) KDE x64.
Greets!!! :-)
Giorgos.



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

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

Versions of packages network-manager-kde depends on:
ii  plasma-widget-networkmanagement  0.9.0.3-1

network-manager-kde recommends no packages.

network-manager-kde 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#730846: gnupg2: FTBFS on mips, mipsel: gpg: Fatal: can't disable core dumps: Operation not permitted

[Salvatore Bonaccorso]

Hi Andreas,

On Sat, Nov 30, 2013 at 08:04:22AM +0100, Andreas Beckmann wrote:
> Package: gnupg2
> Version: 2.0.22-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> Hi,
> 
> gnupg FTBFS on mips*:
> 
> https://buildd.debian.org/status/fetch.php?pkg=gnupg2&arch=mips&ver=2.0.22-1&stamp=1381015396
> 
> [...]

I'm not the maintainer, but just additional reference for this issues.
See also [1] for followups with wb-team with this issue on mips*.
 
 [1] http://lists.debian.org/debian-wb-team/2013/11/msg0.html

Regards,
Salvatore


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

Bug#730850: libghc-xmonad-dev: is not installable

[Nicolas Évrard]

Package: libghc-xmonad-dev
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The libghc-xmonad-dev package is not installable because it depends on
a virtual package. Here is the log my attempt to install it:

balisto:~% apt-cache show libghc-xmonad-dev | grep Version
Version: 0.11-6
balisto:~% LANG=C sudo aptitude -R install libghc-xmonad-dev
The following NEW packages will be installed:
  ghc{a} libbsd-dev{a} libghc-extensible-exceptions-dev{a} libghc-mtl-dev{a} 
  libghc-transformers-dev{a} libghc-utf8-string-dev{a} libghc-x11-dev{ab} libghc-xmonad-dev 
  libgmp-dev{a} 
The following packages are RECOMMENDED but will NOT be installed:
  libghc-xmonad-contrib-dev 
0 packages upgraded, 9 newly installed, 0 to remove and 5 not upgraded.

Need to get 28.3 MB of archives. After unpacking 309 MB will be used.
The following packages have unmet dependencies:
 libghc-x11-dev : Depends: libghc-data-default-dev-0.4.0-cf4a6 which is a 
virtual package.
The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) libghc-x11-dev [Not Installed] 
2) libghc-xmonad-dev [Not Installed]  

Accept this solution? [Y/n/q/?]  


-- 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=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--
(°> Nicolas Évrard
( ) Liège
 `¯


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

Bug#724479: [Pkg-varnish-devel] Bug#724479: varnish-agent: FTBFS: automake errors

[Dererk]

On 29/11/13 19:06, Andreas Moog wrote:
> Hi there,
>
> I wanted to ask what the status of this bug is? The tags say it's
> "pending" but there hasn't been any further activity since October 11.
>
> Thanks for your time!
>
> Cheers,
>   Andreas
Hi Andreas!

The reason why this upload is being delayed is because I'm preparing an
upload that is going to provide more functionality than the current one
and is related to #721942.

Sorry for the confusion, It will soon be resolved.



Cheers,

Dererk

-- 
BOFH excuse #161:
monitor VLF leakage




signature.asc
Description: OpenPGP digital signature

Bug#729276: staden-io-lib-utils: bufferoverflow in index_tar

[Sang Kil Cha]

Hi,

Yes I think I did submitted it to upstream.

I don't have a particular patch, but I believe it is trivial to add a
check for the overflow.

Thanks,
Sang Kil

On Sat, Nov 30, 2013 at 3:40 AM, Charles Plessy  wrote:
> Le Sun, Nov 10, 2013 at 09:20:08PM -0500, Sang Kil Cha a écrit :
>> Package: staden-io-lib-utils
>> Version: 1.12.4-1
>> Severity: grave
>> Tags: security
>> Justification: user security hole
>>
>> index_tar has a buffer overflow vulnerability. A PoC file is attached.
>
> Hello,
>
> thanks for the report.  Have you also submitted it upstream ?  Do you
> have a suggestion on how to solve the problem ?
>
> Cheers,
>
> --
> Charles Plessy
> Debian Med packaging team,
> http://www.debian.org/devel/debian-med
> Tsurumi, Kanagawa, Japan


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

Bug#730835: bugs.debian.org: the BTS seems to no longer know who are the maintainers of the packages!

[Francesco Poli]

On Fri, 29 Nov 2013 16:48:04 -0800 Ryan Niebur wrote:

> Hello,
> 
> +1!

Hello Ryan, nice to read you!

Thanks for confirming what I noticed...

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


pgpv26gf0yAcf.pgp
Description: PGP signature

Bug#730835: closed by Don Armstrong (reply to ow...@bugs.debian.org) (Re: Bug#730835: bugs.debian.org: the BTS seems to no longer know who are the maintainers of the packages!)

[Francesco Poli]

On Fri, 29 Nov 2013 19:04:38 -0800 Don Armstrong wrote:

[...]
> Thanks for the report; this has been fixed now.

Hello Don,
thanks to you for fixing things up so promptly!
It's really appreciated.

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


pgpAZXencmQbk.pgp
Description: PGP signature

Bug#730851: ITP: ruby-rspec-puppet -- RSpec tests for your Puppet manifests

[Thomas Bechtold]

Package: wnpp
Severity: wishlist
Owner: Thomas Bechtold 

* Package name: ruby-rspec-puppet
  Version : 0.1.6
  Upstream Author : Tim Sharpe
* URL : https://rubygems.org/gems/rspec-puppet
* License : Expat
  Programming Lang: Ruby
  Description : RSpec tests for your Puppet manifests

Puppet lets you centrally manage every important aspect of your system
using a cross-platform specification language that manages all the
separate elements normally aggregated in different files, like users,
cron jobs, and hosts, along with obviously discrete elements like
packages, services, and files.
.
This ruby module contains RSpec tests for Puppet manifests.


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

Bug#725046: Bugs in packages meep-* (fwd)

[Adam D. Barratt]

On Fri, 2013-11-29 at 22:45 +0100, Thorsten Alteholz wrote:
> 
> On Fri, 29 Nov 2013, Adam D. Barratt wrote:
> 
> > On Fri, 2013-11-29 at 19:44 +0100, Thorsten Alteholz wrote:
> > Thanks. Unfortunately, you used the wrong version number for all of
> > them. :-(
> 
> Ooh, shame on me, I need new glasses. Can you remove these versions again?

I've marked them all for rejection, so it's just waiting for dak to
process that request.

Regards,

Adam


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

Bug#730852: evolution: use free Open Street Map instead of Google Maps

[Axel Stammler]

Package: evolution
Version: 3.4.4-3
Severity: wishlist

Dear Maintainer,

The “show map” feature is a great idea, but its associated action cannot be 
changed and
invariably points to Google. Please support Open Street Map.

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

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

Versions of packages evolution depends on:
ii  dbus 1.6.8-1+deb7u1
ii  debconf [debconf-2.0]1.5.49
ii  evolution-common 3.4.4-3
ii  evolution-data-server3.4.4-3
ii  gconf-service3.2.5-1+build1
ii  gconf2   3.2.5-1+build1
ii  gnome-icon-theme 3.4.0-2
ii  libatk1.0-0  2.4.0-2
ii  libc62.13-38
ii  libcairo-gobject21.12.2-3
ii  libcairo21.12.2-3
ii  libcamel-1.2-33  3.4.4-3
ii  libclutter-gtk-1.0-0 1.2.0-2
ii  libdbus-glib-1-2 0.100.2-1
ii  libebackend-1.2-23.4.4-3
ii  libebook-1.2-13  3.4.4-3
ii  libecal-1.2-11   3.4.4-3
ii  libedataserver-1.2-163.4.4-3
ii  libedataserverui-3.0-1   3.4.4-3
ii  libenchant1c2a   1.6.0-7
ii  libevolution 3.4.4-3
ii  libgail-3-0  3.4.2-6
ii  libgconf-2-4 3.2.5-1+build1
ii  libgdata13   0.12.0-1
ii  libgdk-pixbuf2.0-0   2.26.1-1
ii  libglib2.0-0 2.33.12+really2.32.4-5
ii  libgnome-desktop-3-2 3.4.2-1
ii  libgtk-3-0   3.4.2-6
ii  libgtkhtml-4.0-0 4.4.4-1
ii  libgtkhtml-editor-4.0-0  4.4.4-1
ii  libgweather-3-0  3.4.1-1+build1
ii  libical0 0.48-2
ii  libmx-1.0-2  1.4.6-1
ii  libnotify4   0.7.5-1
ii  libnspr4 2:4.9.2-1
ii  libnss3  2:3.14.5-1
ii  libnss3-1d   2:3.14.5-1
ii  libpango1.0-01.30.0-1
ii  libsoup2.4-1 2.38.1-2
ii  libsqlite3-0 3.7.13-1+deb7u1
ii  libxml2  2.8.0+dfsg1-7+nmu2
ii  psmisc   22.19-1+deb7u1

Versions of packages evolution recommends:
ii  bogofilter 1.2.2+dfsg1-2
ii  evolution-plugins  3.4.4-3
ii  evolution-webcal   2.32.0-2+b2
ii  yelp   3.4.2-1+b1

Versions of packages evolution suggests:
pn  evolution-dbg   
pn  evolution-exchange  
pn  evolution-plugins-experimental  
ii  gnupg   1.4.12-7+deb7u2
ii  network-manager 0.9.4.0-10

-- debconf information:
  evolution/kill_processes:
  evolution/needs_shutdown:


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

Bug#730853: ERROR: getaddrinfo: Name or service not known

[Adnan Hodzic]

Package: reportbug
Version: 6.4.4
Severity: serious
Justification: normal

When I run rdesktop I get following error:

absinthe@havoc:~$ rdesktop -d ebuddy -u ahodzic ts3.ebuddy-office.net -g
1280x1024
Autoselected keyboard map en-us
ERROR: getaddrinfo: Name or service not known
absinthe@havoc:~$

I also tried version from Sid (1.7.1-1+b1) but I'm encountering the same
problem.

Please inform me if you have additional questions or comments.


Adnan




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

** /home/absinthe/.reportbugrc:
reportbug_version "6.4.4"
mode standard
ui gtk2
email "ad...@foolcontrol.org"
smtphost "smtp.gmail.com:587"
smtpuser "absinthesyri...@gmail.com"
smtptls

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'stable-updates'), (300, 'unstable'), 
(200, 'stable'), (100, 'experimental')
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 reportbug depends on:
ii  apt   0.9.12.1
ii  python2.7.5-5
ii  python-reportbug  6.4.4

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
pn  debconf-utils  
pn  debsums
pn  dlocate
pn  emacs22-bin-common | emacs23-bin-common
ii  exim4  4.80-9
ii  exim4-daemon-light [mail-transport-agent]  4.80-9
ii  file   1:5.14-2
ii  gnupg  1.4.15-1.1
ii  python-gtk22.24.0-3+b1
pn  python-gtkspell
pn  python-urwid   
ii  python-vte 1:0.28.2-5
ii  xdg-utils  1.1.0~rc1+git20111210-7

Versions of packages python-reportbug depends on:
ii  apt   0.9.12.1
ii  python2.7.5-5
ii  python-debian 0.1.21+nmu2
ii  python-debianbts  1.11
ii  python-support1.0.15

python-reportbug suggests no packages.

-- no debconf information


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

Bug#729359: RFS: mtink/1.0.16-8 [QA] -- Status monitor tool for Epson inkjet printers

[Graham Inggs]

I've pushed some commits to the git on collab-maint.

I added a comment about the overridden Lintian spelling error
warnings, rewrote the package descriptions, merged the changes I had
made in d/control into d/control.in and regenerated d/control, and
updated d/watch.

I did find Ubuntu bug LP: #810871 was the same as Debian bug #716543
and marked it accordingly.


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

Bug#730853: ERROR: getaddrinfo: Name or service not known

[Sandro Tosi]

reassign 730853 rdesktop
thanks

rdesktop != reportbug

On Sat, Nov 30, 2013 at 11:04 AM, Adnan Hodzic  wrote:
> Package: reportbug
> Version: 6.4.4
> Severity: serious
> Justification: normal
>
> When I run rdesktop I get following error:
>
> absinthe@havoc:~$ rdesktop -d ebuddy -u ahodzic ts3.ebuddy-office.net -g
> 1280x1024
> Autoselected keyboard map en-us
> ERROR: getaddrinfo: Name or service not known
> absinthe@havoc:~$
>
> I also tried version from Sid (1.7.1-1+b1) but I'm encountering the same
> problem.
>
> Please inform me if you have additional questions or comments.
>
>
> Adnan
>
>
>
>
> -- Package-specific info:
> ** Environment settings:
> INTERFACE="gtk2"
>
> ** /home/absinthe/.reportbugrc:
> reportbug_version "6.4.4"
> mode standard
> ui gtk2
> email "ad...@foolcontrol.org"
> smtphost "smtp.gmail.com:587"
> smtpuser "absinthesyri...@gmail.com"
> smtptls
>
> -- System Information:
> Debian Release: jessie/sid
>   APT prefers testing
>   APT policy: (600, 'testing'), (500, 'stable-updates'), (300, 'unstable'), 
> (200, 'stable'), (100, 'experimental')
> 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 reportbug depends on:
> ii  apt   0.9.12.1
> ii  python2.7.5-5
> ii  python-reportbug  6.4.4
>
> reportbug recommends no packages.
>
> Versions of packages reportbug suggests:
> pn  claws-mail 
> pn  debconf-utils  
> pn  debsums
> pn  dlocate
> pn  emacs22-bin-common | emacs23-bin-common
> ii  exim4  4.80-9
> ii  exim4-daemon-light [mail-transport-agent]  4.80-9
> ii  file   1:5.14-2
> ii  gnupg  1.4.15-1.1
> ii  python-gtk22.24.0-3+b1
> pn  python-gtkspell
> pn  python-urwid   
> ii  python-vte 1:0.28.2-5
> ii  xdg-utils  1.1.0~rc1+git20111210-7
>
> Versions of packages python-reportbug depends on:
> ii  apt   0.9.12.1
> ii  python2.7.5-5
> ii  python-debian 0.1.21+nmu2
> ii  python-debianbts  1.11
> ii  python-support1.0.15
>
> python-reportbug suggests no packages.
>
> -- no debconf information
>



-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


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

Bug#730853: ERROR: getaddrinfo: Name or service not known

[Cyril Brulebois]

Control: severity -1 normal
Control: reassign -1 rdesktop

Adnan Hodzic  (2013-11-30):
> Package: reportbug
> Version: 6.4.4
> Severity: serious
> Justification: normal

You surely didn't mean to report this against reportbug?

> When I run rdesktop I get following error:
> 
> absinthe@havoc:~$ rdesktop -d ebuddy -u ahodzic ts3.ebuddy-office.net -g
> 1280x1024
> Autoselected keyboard map en-us
> ERROR: getaddrinfo: Name or service not known
> absinthe@havoc:~$
> 
> I also tried version from Sid (1.7.1-1+b1) but I'm encountering the same
> problem.
> 
> Please inform me if you have additional questions or comments.

Please check your DNS? If you can resolve outside rdesktop (host, dig,
ping), might be some nsswitch fun. What if you specify an IP instead of
a hostname?

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#730813: Acknowledgement (libsvnclientadapter-java: svnjavahl-1.so should be provided to better work with eclips-subclipse)

[Andrei POPESCU]

Control: reassign -1 eclipse-subclipse

On Vi, 29 nov 13, 14:56:21, crow wrote:
> nevermind, I see its in libsvn-java and my problem is actually with
> eclipse not launching java with -Djava.library.path set properly.
> Adding 
> 
> "-Djava.library.path=/usr/lib/x86_64-linux-gnu/jni" to /etc/eclise.ini
> fixed it
> 
> reassign eclipse-subclipse
> 
> On Fri, 2013-11-29 at 19:57 +, Debian Bug Tracking System wrote:
> > Thank you for filing a new Bug report with Debian.
> > 
> > This is an automatically generated reply to let you know your message
> > has been received.
> > 
> > Your message is being forwarded to the package maintainers and other
> > interested parties for their attention; they will reply in due course.
> > 
> > Your message has been sent to the package maintainer(s):
> >  unknown-pack...@qa.debian.org
> > 
> > If you wish to submit further information on this problem, please
> > send it to 730...@bugs.debian.org.
> > 
> > Please do not send mail to ow...@bugs.debian.org unless you wish
> > to report a problem with the Bug-tracking system.
> > 

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


signature.asc
Description: Digital signature

Bug#722914: qemu: leaves alternatives after purge: /usr/bin/qemu

[Michael Tokarev]

29.11.2013 23:38, Andreas Beckmann wrote:
> On 2013-11-29 19:52, Michael Tokarev wrote:
>> The lintian warning in question appears to make some sense.

> Perhaps ignore it. I'm not exactly sure what the right way is here.
> There is a long discussion in #7 (that 5-digit bug mentioned

71621

> earlier) and as I understood there might be cases where "prerm remove"
> is not being run and therefore we should try to clean up again in
> "postrm remove|disappear". Maybe lintian should not issue this warning
> is there is corresponding code in the prerm, too.
> 
> BTW, in case you ever remove something from @ARCH@, you should use
> something like @REMOVEDARCH@ and remove the obsolete alternatives in
> postinst (after adding the new ones) and pre/postrm.

Yes, I know.  It is even more complicated, because the list of arches
is per-target-binary-package and some arches may move between packages
(we've qemu-system-misc which may be split further in some point in
future).  But this is not something for you to worry about :)

> Out of curiosity: what was the difference in alternatives setup between
> wheezy and sid that caused this upgrade bug?

That's actually an interesting question.

The change was splitting single and large qemu-system package into several
arch-specific packages, each of which covering a few "similar" architectures.
For this, we had to change alternatives (in particular) handling from static
debian/qemu-system.{postinst,prerm} files into dynamic generation of
debhelper scripts.

Here's the partial diff from the large "split" commit, relevant to our case:


commit 82efafb79c97aa05d7a8f2611e261aa0633cf071
Author: Michael Tokarev 
Date:   Wed Sep 12 12:14:18 2012 +0400

split qemu-system into several arch-specific packages

Split arm, mips, ppc, sparc and x86 qemu-system binaries
into their own packages, create qemu-system-misc for the rest,
and qemu-system-common for the shared files.

diff --git a/debian/qemu-system.postinst b/debian/qemu-system.postinst
deleted file mode 100644
index 2e06d35..000
--- a/debian/qemu-system.postinst
+++ /dev/null
@@ -1,40 +0,0 @@
-#! /bin/sh
-
-set -e
-
-if [ "$1" = configure ] ; then
-# Add the kvm group unless it's already there
-if ! getent group kvm >/dev/null; then
-addgroup --quiet --system kvm || true
-fi
-
-if [ -x /usr/sbin/update-alternatives ]; then
-# Install alternatives for all qemu-system binaries.  Set i386 as 
highest
-# priority, as it has been the default qemu for quite some time.
-update-alternatives --install /usr/bin/qemu qemu \
-/usr/bin/qemu-system-i386 20
-arches="arm cris m68k microblaze mips mips64 mips64el mipsel ppc ppc64 
ppcemb s390x sh4 sh4eb sparc sparc64 x86_64"
-for arch in $arches ; do
-update-alternatives --install /usr/bin/qemu qemu \
-/usr/bin/qemu-system-"$arch" 10
-done
-fi
-fi

diff --git a/debian/qemu-system.postinst-in b/debian/qemu-system.postinst-in
new file mode 100644
index 000..6af9b7c
--- /dev/null
+++ b/debian/qemu-system.postinst-in
@@ -0,0 +1,10 @@
+# set up /usr/bin/qemu alternative to be one the qemu-system emulators
+if [ "$1" = configure -a -x /usr/sbin/update-alternatives ]; then
+  for arch in @ARCH@ ; do
+# Set i386 as highest priority,
+# as it has been the default qemu for quite some time.
+case $arch in i386) prio=20;; *) prio=10;; esac
+update-alternatives --install /usr/bin/qemu qemu \
+/usr/bin/qemu-system-$arch $prio
+  done
+fi

diff --git a/debian/qemu-system.prerm b/debian/qemu-system.prerm
deleted file mode 100644
index 0d32175..000
--- a/debian/qemu-system.prerm
+++ /dev/null
@@ -1,14 +0,0 @@
-#! /bin/sh
-set -e
-
-#DEBHELPER#
-
-if [ "$1" = remove ] || [ "$1" = deconfigure ] || [ "$1" = failed-upgrade ]; 
then
-if [ -x /usr/sbin/update-alternatives ]; then
-# remove alternatives for qemu-system binaries
-arches="arm cris m68k microblaze mips mips64 mips64el mipsel ppc ppc64 
ppcemb s390x sh4 sh4eb sparc sparc64 x86_64 i386"
-for arch in $arches ; do
-update-alternatives --remove qemu /usr/bin/qemu-system-"$arch"
-done
-fi
-fi
diff --git a/debian/qemu-system.prerm-in b/debian/qemu-system.prerm-in
new file mode 100644
index 000..bae7ae5
--- /dev/null
+++ b/debian/qemu-system.prerm-in
@@ -0,0 +1,11 @@
+# deregister /usr/bin/qemu alternatives
+case "$1" in
+  remove | deconfigure | failed-upgrade)
+if [ -x /usr/sbin/update-alternatives ]; then
+# remove alternatives for qemu-system binaries
+for arch in @ARCH@ ; do
+update-alternatives --remove qemu /usr/bin/qemu-system-$arch
+done
+fi
+;;
+esac


diff --git a/debian/rules b/debian/rules
index 8746eaa..67c87cf 100755
--- a/debian/rules
+++ b/debian/rules
 # list of system (softmmu) targets, from ./configure
 system_targets = \
  i386 x86_64 alpha arm cris lm32 m68k micro

Bug#714436: [Pkg-fonts-devel] Bug#714436: fonts-droid: No Hangul characters

[Anthony Fok]

Hello,

I came across the same peculiarity that Martin Tang discovered.  I was
comparing WQY MicroHei and Droid Sans Fallback using "ttx" from the
fonttools package, and noticed that, peculiarly,
DroidSansFallbackFull.ttf contains one and only one Hangul glyph,
U+AC00.

A quick Google search reveals this change in Android font selection:

https://android.googlesource.com/platform/frameworks/base.git/+/562c45cc841681ed80d4e94515b23c28eb60eae4

Latest versions of DroidSansFallback from Monotype.

The DroidSansFallback.ttf file has some additional glyphs and
glyph fixes (including a fix for bug 6723057 and will likely fix
bug 6629748).  It continues to cover Korean Hangul but does not
cover CJK Ext A (for space reasons on small system image devices).

The DroidSansFallbackFull.ttf file has the bug fixes listed and
also removes the Korean Hangul because we are now going to use
NanumGothic for Korean (NanumGothic.ttf is added in a separate
CL in the external/naver-fonts directory).

The falback_fonts.xml file has been modified to add NanumGothic.ttf
before DroidSansFallback.

Looks like we need to do the equivalent for the fonts-droid Debian package.

First of all, DroidSansFallback.ttf is not a strict subset of
DroidSansFallbackFull.ttf,
and DroidSansFallback.ttf should indeed be packaged.

Second, perhaps a fontconfig configuration snippet could be added so that
another font (e.g. that in fonts-nanum) come before Droid provided by
fonts-droid?

Cheers,
Anthony

On Sat, Jun 29, 2013 at 6:25 PM, Martin Tang  wrote:
> Package: fonts-droid
> Version: 1:4.2.r1-2
> Severity: normal
>
> Dear Maintainer,
>
> Korean characters do not display properly (they show up as boxes) after the 
> package is installed. After further investigation (downloading the .ttf files 
> from the Android git repository), I found that:
>
> 1. With only DroidSansFallbackFull.ttf (as is the case in fonts-droid), 
> Korean characters do not display properly.
>
> 2. With DroidSansFallback.ttf present, Korean characters display properly.
>
>
> -- Package-specific info:
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name Version Architecture 
>Description
> +++--===-===-=
> ii  fontconfig   2.10.2-2amd64
>generic font configuration library - support binaries
> ii  libfreetype6:amd64   2.4.9-1.1   amd64
>FreeType 2 font engine, shared library files
> ii  libxft2:amd642.3.1-1 amd64
>FreeType-based font drawing library for X
>
> -- 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.9-1-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages fonts-droid depends on:
> ii  dpkg  1.16.10
>
> fonts-droid recommends no packages.
>
> fonts-droid suggests no packages.
>
> -- no debconf information
>
> ___
> Pkg-fonts-devel mailing list
> pkg-fonts-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-fonts-devel


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

Bug#730822: apt-listbugs: Does not use proxy from Acquire::http::Proxy

[Martin Völlinger]

On Saturday 30 November 2013 01:11:27 CET, Francesco Poli wrote:
  
[...]
> Martin, please try and delete the line "require 'soap/soap'" at the
> beginning of /usr/share/apt-listbugs/apt-listbugs/logic.rb and let me
> know whether it fixes the issue for you too.

Hello Francesco,

yes this fixes the issue and everything seems to work fine.

Cheers,
Martin


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

Bug#730682: patch: removal of -q switch from emacspeak.sh

[Jarek Czekalski]

Please reopen this entry.

Although the title says about q switch removal, it should not be done in 
a plain way. Please see the original patch at [1].


If q switch is removed and INITSTR is left unchanged, it results in 
running the emacs user init file twice. Once normally, and once through 
INITSTR. And it's imposssible to turn it off using "emacspeak -q".


Actually now we have a new bug in Emacspeak 39, but it's originated 
here, so I don't submit a new entry.


Jarek

[1] http://www.cs.vassar.edu/~priestdo/emacspeak/2013/msg00564.html


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

Bug#730854: gem2deb -t lowercases paths

[Christian Hofstaedtler]

Package: gem2deb
Version: 0.5.1
Severity: minor

gem2deb -t apparently lowercases paths, causing it to not find the specified 
sourcefile:

% gem2deb -t ~/Downloads/bundler-1.3.5.gem 
-- Creating source tarball from /home/ch/Downloads/bundler-1.3.5.gem ...
tar xfm /home/ch/Downloads/bundler-1.3.5.gem
"tar xzfm data.tar.gz"
"zcat metadata.gz > metadata.yml"
tar czf /home/ch/downloads/bundler-1.3.5.tar.gz bundler-1.3.5
tar (child): /home/ch/downloads/bundler-1.3.5.tar.gz: Cannot open: No such file 
or directory
tar (child): Error is not recoverable: exiting now
/usr/lib/ruby/vendor_ruby/gem2deb.rb:54:in `run': tar czf 
/home/ch/downloads/bundler-1.3.5.tar.gz bundler-1.3.5 (Gem2
from /usr/lib/ruby/vendor_ruby/gem2deb/gem2tgz.rb:92:in `block in 
create_resulting_tarball'
from /usr/lib/ruby/vendor_ruby/gem2deb/gem2tgz.rb:91:in `chdir'
from /usr/lib/ruby/vendor_ruby/gem2deb/gem2tgz.rb:91:in 
`create_resulting_tarball'
from /usr/lib/ruby/vendor_ruby/gem2deb/gem2tgz.rb:61:in `convert!'
from /usr/lib/ruby/vendor_ruby/gem2deb/gem2tgz.rb:30:in `convert!'
from /usr/bin/gem2deb:82:in `'


Notice that it calls tar with lowercased 'Downloads'.

Thanks,
  Christian


-- 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_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gem2deb depends on:
ii  build-essential   11.6
ii  debhelper 9.20131110
ii  devscripts2.13.4
ii  perl  5.18.1-4
ii  ruby  1:1.9.3
ii  ruby1.8 [ruby-interpreter]1.8.7.358-8
ii  ruby1.9.1 [ruby-interpreter]  1.9.3.448-1
ii  ruby1.9.1-dev 1.9.3.448-1
ii  ruby2.0 [ruby-interpreter]2.0.0.343-1
ii  ruby2.0-dev   2.0.0.343-1

gem2deb recommends no packages.

gem2deb 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: systemd (security) bugs (was: init system question) [and 1 more messages]

[Michael Stapelberg]

Hi Ian,

Ian Jackson  writes:
> My point was that someone who is writing an init system for concurrent
> startup and dynamic service management needs to have a good
> understanding of concurrent system design, and in particular of race
> hazards.  I wouldn't expect a person or people who had such an
> understanding to make many mistakes of the kind seen here.
Neither do I, but there is no evidence for _many_ of these problems.

>> Personally, I don’t know about every little detail in fd passing
>> either. If I read you correctly, you seem to be saying one needs to be
>> an expert in a given area before being allowed to write code in it. I
>> think it works the other way around: by writing code in that area, you
>> become an expert in it.
>
> What a startling statement.  This is not some desktop toy we are
> talking about; this is critical core system infrastructure.
>
> I would prefer my pid 1 to have been written by experts.  It appears
> that you are saying that systemd wasn't and that this isn't important!
To clarify: I do think (most?) systemd authors are experts. I am also
saying that experts can make mistakes, and that having the expectation
that software has 0 bugs is unreasonable.

I also stand by my statement that one cannot be an expert in a subject
area before having experience in that subject area. Sure, one can
prepare, but there is the proverb “practice makes perfect”.

>> Instead of focusing on the actual security issues, what I’d much rather
>> look at is the process with which such bugs are fixed. I.e. are security
>> problems acknowledged as such, are they fixed clearly and in a timely
>> manner? Are there enough eyes looking at the project to uncover, report
>> and collaborate in fixing the issues?
>
> I don't think having a functioning security response process is a
> substitute for good system design, and a high initial code quality.
No argument there. I think having all three of them is better, and
that’s my opinion of systemd, at least of pid 1, which I have looked at
more closely than at the other parts of the larger system.

>> Also, and I think that should go without saying, if this branch of the
>> discussion is considered as reasoning against systemd in the decision
>> process, I’d like to see similar data on the other init systems :).
>
> You are of course welcome to go and find that information.
I may be misunderstanding how this works, but I strongly believe that if
the ctte looks at the security track record of systemd, it MUST also
look at the security track record of the other contenders. I.e., I
consider it unfair to say “we’re not using systemd because it had
security bugs, we’ll chose X instead, but we didn’t look at its security
at all”.

That said, I’d love to help, but I don’t have the time to look at the
security track record of other init systems in detail. Sorry.

-- 
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#730855: Please support mips(el), mipsn32(el) and mips64(el)

[Aron Xu]

Package: acpi-support
Severity: wishlist

Please add `mips mipsel mipsn32 mipsn32el mips64 mips64el' to
Architecture stanza of deian/control I can confirm that it build
successfully on mipsel/mips64el.

acpi has already adopt the support for MIPS architectures (Bug
#725918), so I think it's appropriate to add the support in
acpi-support.

Thanks,
Aron Xu


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

Bug#730856: transition: libtasn1-6

[Andreas Metzler]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hello,

I would like to finally (now that libimobiledevice builds again) get
rid of libtasn1-3.

This should a small painless transition, it will require sourceful uploads
of 3 source packages which are up to date in testing.
* gnutls26
* gcr
* libimobiledevice

All of these three can be built against libtasn1-6.

cu Andreas

Ben file:

title = "libtasn1-6";
is_affected = .depends ~ "libtasn1-3" | .depends ~ "libtasn1-6";
is_good = .depends ~ "libtasn1-6";
is_bad = .depends ~ "libtasn1-3";


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

Bug#730857: clang-3.4: Unable to build anything on i386 ('bits/c++config.h' file not found)

[Hans Joachim Desserud]

Package: clang-3.4
Version: 1:3.4~+rc1-1
Severity: important

Dear Maintainer,

I recently noticed clang-3.4 had been packaged and wanted to try it out,
but was unable to compile anything with it on my i386 system.

Prior to the install, clang-3.3 worked fine, and the same file builds without
problems with GCC. See below for detailed output.

I believe this might be http://bugs.debian.org/697127 which has reappeared.
Let me know if you need any additional information.

$ cat hello.cpp 
#include 

int main() {
std::cout << "hello";
}
$ g++ hello.cpp 
$ clang++ -v hello.cpp 
Debian clang version 3.4-1 (tags/RELEASE_34/rc1) (based on LLVM 3.4)
Target: i386-pc-linux-gnu
Thread model: posix
Found candidate GCC installation: /usr/bin/../lib/gcc/i486-linux-gnu/4.6
Found candidate GCC installation: /usr/bin/../lib/gcc/i486-linux-gnu/4.6.4
Found candidate GCC installation: /usr/bin/../lib/gcc/i486-linux-gnu/4.7
Found candidate GCC installation: /usr/bin/../lib/gcc/i486-linux-gnu/4.7.3
Found candidate GCC installation: /usr/bin/../lib/gcc/i486-linux-gnu/4.8
Found candidate GCC installation: /usr/bin/../lib/gcc/i486-linux-gnu/4.8.2
Found candidate GCC installation: /usr/lib/gcc/i486-linux-gnu/4.6
Found candidate GCC installation: /usr/lib/gcc/i486-linux-gnu/4.6.4
Found candidate GCC installation: /usr/lib/gcc/i486-linux-gnu/4.7
Found candidate GCC installation: /usr/lib/gcc/i486-linux-gnu/4.7.3
Found candidate GCC installation: /usr/lib/gcc/i486-linux-gnu/4.8
Found candidate GCC installation: /usr/lib/gcc/i486-linux-gnu/4.8.2
Selected GCC installation: /usr/bin/../lib/gcc/i486-linux-gnu/4.8
 "/usr/bin/clang" -cc1 -triple i386-pc-linux-gnu -emit-obj -mrelax-all 
-disable-free -disable-llvm-verifier -main-file-name hello.cpp 
-mrelocation-model static -mdisable-fp-elim -fmath-errno -masm-verbose 
-mconstructor-aliases -fuse-init-array -target-cpu pentium4 
-target-linker-version 2.23.90.20131116 -v -resource-dir 
/usr/bin/../lib/clang/3.4 -internal-isystem 
/usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++/4.8 
-internal-isystem 
/usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++/4.8/i486-linux-gnu
 -internal-isystem 
/usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++/4.8/backward 
-internal-isystem 
/usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/i486-linux-gnu/c++/4.8
 -internal-isystem /usr/local/include -internal-isystem 
/usr/bin/../lib/clang/3.4/include -internal-isystem 
/usr/include/clang/3.4/include/ -internal-externc-isystem 
/usr/include/i386-linux-gnu -internal-externc-isystem 
/usr/include/i486-linux-gnu -internal-extern
c-isystem /usr/include -fdeprecated-macro -fdebug-compilation-dir /home/debian 
-ferror-limit 19 -fmessage-length 112 -mstackrealign -fobjc-runtime=gcc 
-fcxx-exceptions -fexceptions -fdiagnostics-show-option -fcolor-diagnostics 
-vectorize-slp -o /tmp/hello-46e71e.o -x c++ hello.cpp
clang -cc1 version 3.4 based upon LLVM 3.4 default target i386-pc-linux-gnu
ignoring nonexistent directory 
"/usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++/4.8/i486-linux-gnu"
ignoring nonexistent directory 
"/usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/i486-linux-gnu/c++/4.8"
ignoring nonexistent directory "/usr/bin/../lib/clang/3.4/include"
ignoring nonexistent directory "/usr/include/i486-linux-gnu"
#include "..." search starts here:
#include <...> search starts here:
 /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++/4.8
 /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++/4.8/backward
 /usr/local/include
 /usr/include/clang/3.4/include
 /usr/include/i386-linux-gnu
 /usr/include
End of search list.
In file included from hello.cpp:1:
/usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++/4.8/iostream:38:10:
 fatal error: 
  'bits/c++config.h' file not found
#include 
 ^
1 error generated.



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

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

Versions of packages clang-3.4 depends on:
ii  libc62.17-96
ii  libclang-common-3.4-dev  1:3.4~+rc1-1
ii  libclang1-3.41:3.4~+rc1-1
ii  libffi6  3.0.13-8
ii  libgcc-4.8-dev   4.8.2-5
ii  libgcc1  1:4.8.2-5
ii  libllvm3.4   1:3.4~+rc1-1
ii  libobjc-4.8-dev  4.8.2-5
ii  libstdc++-4.8-dev4.8.2-5
ii  libstdc++6   4.8.2-5
ii  libtinfo55.9+20130608-1

Versions of packages clang-3.4 recommends:
ii  llvm-3.4-dev  1:3.4~+rc1-1
ii  python2.7.5-5

clang-3.4 suggests no packages.

-- no debconf information

-- 
mvh / best regards
Hans Joachim
http://desserud.org


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

Bug#730822: apt-listbugs: Does not use proxy from Acquire::http::Proxy

[Francesco Poli]

Control: tags -1 - moreinfo


On Sat, 30 Nov 2013 11:22:02 +0100 Martin Völlinger wrote:

> On Saturday 30 November 2013 01:11:27 CET, Francesco Poli wrote:
>   
> [...]
> > Martin, please try and delete the line "require 'soap/soap'" at the
> > beginning of /usr/share/apt-listbugs/apt-listbugs/logic.rb and let me
> > know whether it fixes the issue for you too.
> 
> Hello Francesco,
> 
> yes this fixes the issue and everything seems to work fine.

Good, thanks a lot for testing the proposed modification!

I'll try and prepare a new version to be uploaded to sid soon.
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


pgp49M2PzbGWD.pgp
Description: PGP signature

Bug#730859: qa.debian.org: PTS: Wrong news item linked when two versions went through NEW at the same time

[Axel Beckert]

Package: qa.debian.org
Severity: normal

Hi,

on http://packages.qa.debian.org/9/9mount.html both, "Accepted 1.3-8 in
unstable (low)" and "Accepted 1.3-9 in unstable (low)" link to
http://packages.qa.debian.org/9/9mount/news/20131130T10Z.html

The expected news item for "Accepted 1.3-9 in unstable (low)" doesn't
seem to be present at http://packages.qa.debian.org/9/9mount/news/ which
kinda lowers the chances of getting fixed properly, but I'd then rather
would like to see no link if no file is there than the (at least IMHO)
wrong link.


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

Bug#730682: patch: removal of -q switch from emacspeak.sh

[Paul Gevers]

Control: reopen -1

On 30-11-13 11:44, Jarek Czekalski wrote:
> Although the title says about q switch removal, it should not be done in
> a plain way. Please see the original patch at [1].

Thanks for verifying.

> If q switch is removed and INITSTR is left unchanged, it results in
> running the emacs user init file twice. Once normally, and once through
> INITSTR. And it's imposssible to turn it off using "emacspeak -q".

I see.

> Actually now we have a new bug in Emacspeak 39, but it's originated
> here, so I don't submit a new entry.

Indeed. As you can see on the first line of this message, you could have
reopened it yourself. See also [2].

Paul

[2] http://www.debian.org/Bugs/server-control





signature.asc
Description: OpenPGP digital signature

Bug#730860: base: FONTS ARE STILL NOT SHARP

[John Smith]

Package: base
Severity: important

Dear Maintainer,

fonts on this debian based distros look like shit. It is totally annoying that 
after years debian people still do not understand that fonts are a very 
important part of the user interface - bad fonts are actively hurting the 
health of your users. 

Pleaase stop working on anything else and finally fix these broken fonts. Not 
only do they look unbelievable primitive, it is a threat to public health.

Thanks,
John Smith






-- System Information:
Debian Release: Kali Linux 1.0
  APT prefers testing
  APT policy: (1, 'testing')
Architecture: amd64 (x86_64)

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


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

Bug#689854: RFA: pmount -- mount removable devices as normal user

[Axel Beckert]

Hi,

Simon McVittie wrote:
> It might be worth noting that GNOME, LXDE and XFCE in at least wheezy do not
> use pmount (they all appear to use udisks via gvfs), and neither does KDE
> (it appears to use udisks via Solid).

People who use pmount these days probably use it on purpose and do not
want to use DE bloat like udisks or udisks2.

> Only a few things still depend on pmount:

I somehow dislike the words "only" and "still" in that sentence.

Kan-Ru Chen wrote:
> I'm still using pmount heavily and will not switch to other solutions in
> the foreseeable future

Same here, except for the "heavily". Don't have to mount external
block devices that often. But I strongly prefer to do it on the
command-line and pmount is a very convenient way to do that, despite
it seems to be initially developed to server as backend for GUI/DE
stuff. (Congrats to the upstream authors for having managed that
balancing act. :-)

> so I'm interested to join the maintenance of this package and the
> upstream.

I must admit, I'd probably mostly help with packaging and less with
upstream. But I'd jump in before pmount is at risk of being removed
from Debian.

pmount seems to be currently maintained as Alioth project, but I
wonder if collab-maint would be better for it in this state to attract
more spontaneous contributions and contributors.

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#730861: fretsonfire: does not launch because of wrong PngImagePlugin import

[Markus Koschany]

Package: fretsonfire
Version: 1.3.110.dfsg-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

fretsonfire still does not launch because of a deprecated import for
PngImagePluging in textures.py. This was already reported as bug

http://bugs.debian.org/729209

and supposed to be fixed by the latest revision of python-imaging.
Unfortunately this is not the case hence I suggest to apply Jeremy
Laine's patch and to fix the import error in fretsonfire.

I can confirm that the attached patch fixes the issue.

Regards,

Markus

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

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

Versions of packages fretsonfire depends on:
ii  fretsonfire-game1.3.110.dfsg-3
ii  fretsonfire-songs-muldjord  2.dfsg-1
ii  fretsonfire-songs-sectoid   1.dfsg-2

fretsonfire recommends no packages.

fretsonfire 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#730862: gdm3 fails with the "Oh No! Something went wrong" message with Xephyr and vncserver

[clohr]

Package: gdm3
Version: 3.8.4-6
Severity: normal
Tags: upstream

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

gdm3 works well on a real display. However I get the "Oh No! Something went
wrong" message when I use it with Xephyr or vncserver.
(I use GDM 3.8.4)

To get the problem:
1) edit  /etc/gdm3/daemon.conf  to add
[xdmcp]
Enable = true
2) then do:
   Xephyr -query localhost :1

Best regards
Christophe



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

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

Versions of packages gdm3 depends on:
ii  accountsservice  0.6.34-2
ii  adduser  3.113+nmu3
ii  dconf-cli0.18.0-1
ii  dconf-gsettings-backend  0.18.0-1
ii  debconf [debconf-2.0]1.5.52
ii  fluxbox [x-window-manager]   1.3.5-1
ii  fvwm [x-window-manager]  1:2.6.5.ds-3
ii  gir1.2-gdm3  3.8.4-6
ii  gnome-session [x-session-manager]3.8.4-3
ii  gnome-session-bin3.8.4-3
ii  gnome-session-flashback [x-session-manager]  3.6.2-2
ii  gnome-settings-daemon3.8.5-2
ii  gnome-shell  3.8.4-5
ii  gnome-terminal [x-terminal-emulator] 3.10.1-1
ii  gsettings-desktop-schemas3.8.2-2
ii  libaccountsservice0  0.6.34-2
ii  libatk1.0-0  2.10.0-2
ii  libaudit11:2.3.2-2
ii  libc62.17-93
ii  libcairo-gobject21.12.16-2
ii  libcairo21.12.16-2
ii  libcanberra-gtk3-0   0.30-2
ii  libcanberra0 0.30-2
ii  libgdk-pixbuf2.0-0   2.28.2-1
ii  libgdm1  3.8.4-6
ii  libglib2.0-0 2.36.4-1
ii  libglib2.0-bin   2.36.4-1
ii  libgtk-3-0   3.8.4-1
ii  libpam-modules   1.1.3-9
ii  libpam-runtime   1.1.3-9
ii  libpam-systemd   204-5
ii  libpam0g 1.1.3-9
ii  libpango-1.0-0   1.36.0-1
ii  libpangocairo-1.0-0  1.36.0-1
ii  librsvg2-common  2.40.0-1
ii  libselinux1  2.2.1-1
ii  libwrap0 7.6.q-24
ii  libx11-6 2:1.6.2-1
ii  libxau6  1:1.0.8-1
ii  libxdmcp61:1.1.1-1
ii  libxrandr2   2:1.4.1-1
ii  lsb-base 4.1+Debian12
ii  metacity [x-window-manager]  1:2.34.13-1
ii  miwm [x-window-manager]  1.1-3
ii  mutter [x-window-manager]3.8.4-2
ii  terminator [x-terminal-emulator] 0.97-2
ii  twm [x-window-manager]   1:1.0.6-1
ii  upower   0.9.23-2+b1
ii  x11-common   1:7.7+4
ii  x11-xserver-utils7.7+1
ii  xterm [x-terminal-emulator]  297-1

Versions of packages gdm3 recommends:
ii  at-spi2-core   2.10.1-1
ii  desktop-base   7.0.3
ii  gnome-icon-theme   3.10.0-1
ii  gnome-icon-theme-symbolic  3.10.1-1
ii  x11-xkb-utils  7.7~1
ii  xserver-xephyr 2:1.14.3-4
ii  xserver-xorg   1:7.7+4
ii  zenity 3.8.0-1

Versions of packages gdm3 suggests:
pn  gnome-orca
ii  libpam-gnome-keyring  3.8.2-2

-- Configuration Files:
/etc/gdm3/daemon.conf changed:
[daemon]
[security]
[xdmcp]
Enable = true
[greeter]
[chooser]
[debug]


-- debconf information:
  gdm3/daemon_name: /usr/sbin/gdm3
* shared/default-x-display-manager: gdm3


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

Bug#730861: fretsonfire: does not launch because of wrong PngImagePlugin import

[Markus Koschany]

diff -Nru fretsonfire-1.3.110.dfsg/debian/changelog 
fretsonfire-1.3.110.dfsg/debian/changelog
--- fretsonfire-1.3.110.dfsg/debian/changelog   2012-01-01 06:48:51.0 
+0100
+++ fretsonfire-1.3.110.dfsg/debian/changelog   2013-11-30 13:06:53.0 
+0100
@@ -1,3 +1,11 @@
+fretsonfire (1.3.110.dfsg-4) unstable; urgency=low
+
+  * Team upload.
+  * Add deprecated-PIL-imports.patch and use the correct way to import
+PngImagePlugin. Thanks to Jeremy Lainé for the patch. (Closes: #730861)
+
+ -- Markus Koschany   Sat, 30 Nov 2013 13:06:39 +0100
+
 fretsonfire (1.3.110.dfsg-3) unstable; urgency=low
 
   * Team upload.
diff -Nru fretsonfire-1.3.110.dfsg/debian/patches/deprecated-PIL-imports.patch 
fretsonfire-1.3.110.dfsg/debian/patches/deprecated-PIL-imports.patch
--- fretsonfire-1.3.110.dfsg/debian/patches/deprecated-PIL-imports.patch
1970-01-01 01:00:00.0 +0100
+++ fretsonfire-1.3.110.dfsg/debian/patches/deprecated-PIL-imports.patch
2013-11-30 13:06:53.0 +0100
@@ -0,0 +1,21 @@
+From: Jeremy Lainé 
+Date: Sat, 30 Nov 2013 12:45:13 +0100
+Subject: deprecated PIL imports
+
+---
+ src/Texture.py | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/Texture.py b/src/Texture.py
+index 51509f5..de63aec 100644
+--- a/src/Texture.py
 b/src/Texture.py
+@@ -27,7 +27,7 @@ import Config
+ import Image
+ import pygame
+ import StringIO
+-import PngImagePlugin
++from PIL import PngImagePlugin
+ from OpenGL.GL import *
+ from OpenGL.GLU import *
+ from Queue import Queue, Empty
diff -Nru fretsonfire-1.3.110.dfsg/debian/patches/series 
fretsonfire-1.3.110.dfsg/debian/patches/series
--- fretsonfire-1.3.110.dfsg/debian/patches/series  2009-05-11 
17:51:11.0 +0200
+++ fretsonfire-1.3.110.dfsg/debian/patches/series  2013-11-30 
13:06:53.0 +0100
@@ -5,3 +5,4 @@
 fix_window_height_bug.patch
 keep_sound_when_failed.patch
 credits_music.patch
+deprecated-PIL-imports.patch


signature.asc
Description: OpenPGP digital signature

Bug#730864: evince-gtk: History navigation buttons greyed out

[Torquil Macdonald Sørensen]

Package: evince-gtk
Version: 3.10.0-1
Severity: normal

The "Go to previous history item" and "Go to next history item" are greyed
out, and therefore non-functional.

Best regards
Torquil Sørensen

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

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

Versions of packages evince-gtk 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
ii  libevview3-3   3.10.0-1
ii  libgail-3-03.8.6-1
ii  libgdk-pixbuf2.0-0 2.28.2-1
ii  libglib2.0-0   2.36.4-1
ii  libgtk-3-0 3.8.6-1
ii  libice62:1.0.8-2
ii  libpango-1.0-0 1.36.0-1
ii  libpangocairo-1.0-01.36.0-1
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-gtk recommends:
ii  dbus-x11  1.6.18-1

Versions of packages evince-gtk suggests:
pn  gvfs  
pn  nautilus  
ii  poppler-data  0.4.6-4
pn  unrar 

-- 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#730865: mate-dialogs: Please ship zenity replacement

[martintxo]

Package: mate-dialogs
Version: 1.6.2-1
Severity: wishlist

Dear Maintainer,

In http://repo.mate-desktop.org/debian/pool/main/m/mate-dialogs/ there is a
mate-dialogs-gnome package. With this you can replace the zenity package. This
offer a zenity package "provides" field and a zenity binary (or simbolic link,
I'm not sure).

Please considere shipping mate-dialogs-gnome package for zenity replacement.
Thanks in advance. Greetings. Martintxo.

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

Kernel: Linux 3.11.0
Locale: LANG=eu_ES.UTF-8, LC_CTYPE=eu_ES.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to eu_ES.UTF-8) Shell: /bin/sh linked to /bin/dash

Versions of packages mate-dialogs depends on:
ii  libatk1.0-0  2.10.0-2
ii  libc62.17-93
ii  libcairo21.12.16-2
ii  libfontconfig1   2.11.0-1
ii  libfreetype6 2.4.9-1.1
ii  libgdk-pixbuf2.0-0   2.28.2-1
ii  libglib2.0-0 2.36.4-1
ii  libgtk2.0-0  2.24.22-1
ii  libnotify4   0.7.6-1
ii  libpango-1.0-0   1.36.0-1
ii  libpangocairo-1.0-0  1.36.0-1
ii  libpangoft2-1.0-01.36.0-1
ii  libx11-6 2:1.6.2-1
ii  mate-dialogs-common  1.6.2-1

mate-dialogs recommends no packages.

mate-dialogs suggests no packages.

-- no debconf information





Sustrai Erakuntza: respuesta jurídico-técnica a proyectos insostenibles.
  proiektu jasangaitzei erantzun juridiko-teknikoa.
  http://www.fundacionsustrai.org
  http://www.sustraierakuntza.org


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

Bug#730865: mate-dialogs: Please ship zenity replacement

[John Paul Adrian Glaubitz]

Hello Martintxo!

On 11/30/2013 01:23 PM, martintxo wrote:
> Please considere shipping mate-dialogs-gnome package for zenity replacement.
> Thanks in advance. Greetings. Martintxo.

The packaging of Mate is still work-in-progress and the fact that
mate-dialogs-gnome is missing doesn't mean we don't package it but
that we haven't packaged it yet.

Mate consists of over 50 single packages and it takes some time to get
them into Debian, please be patient.

Unless the other Mate maintainers object, I'd like to close this bug
report as invalid.

Thanks,

Adrian

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


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

Bug#730845: gpsd: modifies conffiles (policy 10.7.3): /etc/default/gpsd

[Bernd Zeimetz]

severity 730845 minor
tags 730845 wontfix
thanks

Hi,

> during a test with piuparts I noticed your package modifies conffiles.
> This is forbidden by the policy, see
> http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files

no, it actually does not modify them but instead it keeps the formerly debconf
generated conf file - which was not a conffile before. As letting dpkg handle it
by asking the user what to do resulted in a serious bug from you, I've ensured
that the file stays where it is and the user is not being asked at install time
(which is the better behaviour definitely). And btw - the way the debconf stuff
was handled before in the package (it was taken over from the former maintainer
by me) was rc buggy, too.


You might want to modify piuparts to check if there actually existed a (debconf)
generated file before assuming this is a bug.


Cheers,

Bernd

-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F


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

Bug#729359: RFS: mtink/1.0.16-8 [QA] -- Status monitor tool for Epson inkjet printers

[Paul Gevers]

Control: -1 pending

On 30-11-13 11:05, Graham Inggs wrote:
> I've pushed some commits to the git on collab-maint.
> 
> I added a comment about the overridden Lintian spelling error
> warnings, rewrote the package descriptions, merged the changes I had
> made in d/control into d/control.in and regenerated d/control, and
> updated d/watch.

Looks good now, except that I get:
P: mtink source: duplicate-in-relation-field in source build-depends:
debhelper, debhelper (>= 8)

I removed the non-versioned one from the control file, but please check
how to make the generation of the control file do the right thing.

> I did find Ubuntu bug LP: #810871 was the same as Debian bug #716543
> and marked it accordingly.

Nice.

Building and uploading. I push my changes to git and tag it.

Paul




signature.asc
Description: OpenPGP digital signature

Bug#724931: Please include the patch in git

[Andreas Cadhalpun]

Hi,

I have researched how to include the needed modules in the initrd.

If I understand it correctly, it would be possible to add the modules as 
dependencies of cdrom-detect.
But that would not be feasible, because the kernel modules have the 
version of the kernel in their name and therefore the dependencies would 
have to be updated every time a new kernel is released.


Instead I think the best way is to change the config files for the 
debian-installer [1] that determine what udebs are included in which 
initrd. They reside in installer/build/pkg-lists.


For the modules needed for loopmount I attached a patch against the 
debian-installer. In this patch I just added the loop-, ext4-, ntfs- and 
udf-modules to all config files that include cdrom-detect. This comes 
close to making them dependencies of cdrom-detect, but it is much 
easier, since in these config files one can use the variable 
${kernel:Version} and doesn't have to update that manually.


Please include that patch in the debian-installer and then release the 
new versions of cdrom-detect, apt-setup, hw-detect and mountmedia.


Best regards,
Andreas


1: http://anonscm.debian.org/gitweb/?p=d-i/debian-installer.git;a=tree
diff -rup debian-installer.orig/installer/build/pkg-lists/cd_drivers/common debian-installer/installer/build/pkg-lists/cd_drivers/common
--- debian-installer.orig/installer/build/pkg-lists/cd_drivers/common	2013-11-29 23:57:37.780913000 +0100
+++ debian-installer/installer/build/pkg-lists/cd_drivers/common	2013-11-30 12:37:18.882104469 +0100
@@ -3,3 +3,11 @@ cdrom-retriever
 disk-detect
 cdrom-detect
 file-preseed
+
+# This is for cdrom-detect to be able to loopmount an ISO.
+loop-modules-${kernel:Version}
+
+# This is to enable loopmount/usb-hdd from common non-fat file systems:
+ext4-modules-${kernel:Version}
+ntfs-modules-${kernel:Version}
+udf-modules-${kernel:Version}
diff -rup debian-installer.orig/installer/build/pkg-lists/cdrom/common debian-installer/installer/build/pkg-lists/cdrom/common
--- debian-installer.orig/installer/build/pkg-lists/cdrom/common	2013-11-29 23:57:37.780913000 +0100
+++ debian-installer/installer/build/pkg-lists/cdrom/common	2013-11-30 12:37:30.274111670 +0100
@@ -31,3 +31,11 @@ save-logs
 mountmedia
 
 libfribidi0-udeb
+
+# This is for cdrom-detect to be able to loopmount an ISO.
+loop-modules-${kernel:Version}
+
+# This is to enble loopmount/usb-hdd from common non-fat file systems:
+ext4-modules-${kernel:Version}
+ntfs-modules-${kernel:Version}
+udf-modules-${kernel:Version}
diff -rup debian-installer.orig/installer/build/pkg-lists/cdrom-apus/common debian-installer/installer/build/pkg-lists/cdrom-apus/common
--- debian-installer.orig/installer/build/pkg-lists/cdrom-apus/common	2013-11-29 23:57:37.780913000 +0100
+++ debian-installer/installer/build/pkg-lists/cdrom-apus/common	2013-11-30 12:37:40.694118260 +0100
@@ -24,3 +24,11 @@ save-logs
 mountmedia
 
 libfribidi0-udeb
+
+# This is for cdrom-detect to be able to loopmount an ISO.
+loop-modules-${kernel:Version}
+
+# This is to enable loopmount/usb-hdd from common non-fat file systems:
+ext4-modules-${kernel:Version}
+ntfs-modules-${kernel:Version}
+udf-modules-${kernel:Version}

Bug#724330: tagging 672066, reassign 652797 to simgear, fixed 652797 in 2.4.0-1.1, tagging 652797 ...

[Julien Cristau]

Control: notfound -1 0.1.1-1
Control: close -1 0.1.1-1

On Wed, Nov 27, 2013 at 13:06:34 +0100, Andreas Beckmann wrote:

> found 724330 0.1.1-1

Err, no.  That bug was fixed.  If there's a new issue then file a new
bug.  Also these control@ messages with a lot of unrelated changes to
bugs that aren't yours and 0 explanation are extremely annoying.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#728918: intel

[westlake]

I believe when using intel as a user, especially for on-processor 
graphics like Haswell and Sandy, I got improved driver results when 
using the latest microcode (video gfx acceleration is one. My i5 4670k 
processor was new this year, and the latest microcode came out around 
Aug 2013..  Gfx acceleration wasn't working with the packaged outdated 
microcode of a few months older, but furthermore in order for me to use 
proper working Haswell, I had to dive a bit into the testing branch, as 
intel is making a lot of new work for it's latest HD-capable processors)


the command I use iucode-tool -K microcode.dat,

microcode.dat is inside tarballed file but is not usable for the 
microcode service loader without extracting it  (you're pretty much 
extracting the tarball which yields one file, then extracting/pulling an 
arragenment of binary snippets for different processors from 
microcode.dat, there's a way to extract just for your processor, if 
interested for more elaboration, I made a post over here 
https://plus.google.com/105696767572828808697/posts/fSMY3kT4c3s )


There's also this
https://01.org/linuxgraphics/community?qt-projects_aggregated_links=1
 ,but I would definitely include the processor type (eg, for me I'm 
using an intel i5 "4670k".. The processor should be spottable somewhere 
with dmidecode or cat /proc/cpuinfo (not sure if they can take debian 
reports)


Hopefully this helps :)


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

Bug#730552: provide xserver-xorg-source package for building 3rd party software (e.g. VNC) reusing XOrg codebase

[Julien Cristau]

On Tue, Nov 26, 2013 at 09:09:54 -0500, Yaroslav Halchenko wrote:

> Package: xserver-xorg
> Version: 1:7.7+3
> Severity: wishlist
> 
> 
> https://alioth.debian.org/projects/pkg-tigervnc team works on packaging
> TigerVNC for Debian (ITP - #650394).  Unfortunately (or for some might be
> -- fortunately) our initial upload to Debian proper was rejected (in 18 Apr
> 2013) with the main concern being shipping convenience copies of Xorg to build
> TigerVNC.  And suggestion was made to seek collaboration with Debian X Strike
> Force so that Debian could provide a 'proper' xserver-xorg-source package
> providing sources of the XOrg so TigerVNC could be built against them (which
> should simplify/secure its maintenance in the long term).
> 
> Since better later than never, I have decided to file this wishlist to discuss
> such a possibility.  do you see any particular concerns against?  would you
> prefer a patch or work it our yourself?
> 
Please provide a patch.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#730351: xorg: Fresh Jessie, same problem

[Helmar Schütz]

Package: xorg
Followup-For: Bug #730351

Because my system is really unstable since I encountered this bug, I tried
wiping everything and installed Jessie from scratch. Turns out I get the same
behaviour, just worse. Now gnome-shell as well as xorg go crazy with CPU usage.
I don't have the xorg package installed though, so this is probably the wrong
thread to have this bug posted. It probably has to go to xserver-xorg? I would
really appreciate some help.



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

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

Versions of packages xserver-xorg depends on:
ii  libc6 2.17-93
ii  x11-xkb-utils 7.7~1
ii  xkb-data  2.5.1-3
ii  xserver-xorg-core 2:1.14.3-4
ii  xserver-xorg-input-all1:7.7+4
ii  xserver-xorg-input-evdev [xorg-driver-input]  1:2.8.2-1
ii  xserver-xorg-input-mouse [xorg-driver-input]  1:1.9.0-1+b1
ii  xserver-xorg-input-synaptics [xorg-driver-input]  1.7.1-2+b1
ii  xserver-xorg-input-vmmouse [xorg-driver-input]1:13.0.0-1+b1
ii  xserver-xorg-input-wacom [xorg-driver-input]  0.23.0+20131011-1
ii  xserver-xorg-video-all1:7.7+4
ii  xserver-xorg-video-ati [xorg-driver-video]1:7.2.0-1+b2
ii  xserver-xorg-video-cirrus [xorg-driver-video] 1:1.5.2-1+b1
ii  xserver-xorg-video-fbdev [xorg-driver-video]  1:0.4.4-1
ii  xserver-xorg-video-intel [xorg-driver-video]  2:2.21.15-1+b2
ii  xserver-xorg-video-mach64 [xorg-driver-video] 6.9.4-1+b1
ii  xserver-xorg-video-mga [xorg-driver-video]1:1.6.2-1+b1
ii  xserver-xorg-video-modesetting [xorg-driver-video]0.8.0-1+b2
ii  xserver-xorg-video-neomagic [xorg-driver-video]   1:1.2.8-1
ii  xserver-xorg-video-nouveau [xorg-driver-video]1:1.0.10-1
ii  xserver-xorg-video-openchrome [xorg-driver-video] 1:0.3.3-1
ii  xserver-xorg-video-qxl [xorg-driver-video]0.1.0-2.1
ii  xserver-xorg-video-r128 [xorg-driver-video]   6.9.1-1
ii  xserver-xorg-video-radeon [xorg-driver-video] 1:7.2.0-1+b2
ii  xserver-xorg-video-savage [xorg-driver-video] 1:2.3.7-2
ii  xserver-xorg-video-siliconmotion [xorg-driver-video]  1:1.7.7-2
ii  xserver-xorg-video-sisusb [xorg-driver-video] 1:0.9.6-2
ii  xserver-xorg-video-tdfx [xorg-driver-video]   1:1.4.5-1
ii  xserver-xorg-video-trident [xorg-driver-video]1:1.3.6-2
ii  xserver-xorg-video-vesa [xorg-driver-video]   1:2.3.3-1+b1
ii  xserver-xorg-video-vmware [xorg-driver-video] 1:13.0.1-2

Versions of packages xserver-xorg recommends:
ii  libgl1-mesa-dri  9.2.2-1


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

Bug#718624: The 'Type' is still set to 'notify'

[Andrei POPESCU]

Control: reopen -1

Hi,

The submitter also mentioned that 'Type' should not be 'notify' and 
indeed the daemon fails to start if it is set like this. I just removed 
the line and the daemon started correctly.

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


signature.asc
Description: Digital signature

Bug#720385: minetest: game crashes with floating point exception

[Руслан Зиганшин]

Sorry, it was record "language = EN" in file minetest.conf


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

[Juliusz Chroboczek]

Confirmed with the upstream version, but only when
FT_CONFIG_OPTION_SUBPIXEL_RENDERING is enabled, which is the case in
the Debian build but not in the default upstream build.

-- Juliusz


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

Bug#730866: xpdf: Uninstallable

[Torquil Macdonald Sørensen]

Package: xpdf
Version: 3.03-11
Severity: grave
Justification: renders package unusable

xpdf seems to be uninstallable:

$ apt-get istall xpdf
..
..
..
The following packages have unmet dependencies:
libatk-wrapper-java-jni : Depends: libcairo2 (>= 1.2.4) but it is not going to 
be installed
Depends: libgtk2.0-0 (>= 2.12.0) but it is not going to be installed
Depends: libpango-1.0-0 (>= 1.14.0) but it is not going to be installed
Depends: libpangocairo-1.0-0 (>= 1.14.0) but it is not going to be installed
xpdf : Depends: libpoppler19 (>= 0.18.4) but it is not going to be installed
Depends: libxm4 (>= 2.3.4) but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

Best regards
Torquil Sørensen

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

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


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

Bug#721600: udev rules don't get applied, resulting in incorrect device ownership

[Alexander Kadlec]

Package: nut-server
Version: 2.6.4-2.3
Followup-For: Bug #721600

Dear Maintainer,

Just made an install of Debian 7.2 from scratch and still had this problem.
The usb device has incorrect permissions, so I had to fix it manually.
I'm not sure if /etc/udev/rules.d/52_nut-usbups.rules should be there or not
(it was NOT present in my system), but the fact is that usb device has
 incorrect permissions after install.



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

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

Versions of packages nut-server depends on:
ii  adduser3.113+nmu3
ii  libc6  2.13-38
ii  libupsclient1  2.6.4-2.3
ii  libusb-0.1-4   2:0.1.12-20+nmu1
ii  libwrap0   7.6.q-24
ii  lsb-base   4.1+Debian8+deb7u1
ii  nut-client 2.6.4-2.3
ii  udev   175-7.2

nut-server recommends no packages.

Versions of packages nut-server suggests:
pn  nut-cgi   
pn  nut-dev   
pn  nut-snmp  
pn  nut-xml   

-- Configuration Files:
/etc/nut/ups.conf [Errno 13] Permission denied: u'/etc/nut/ups.conf'
/etc/nut/upsd.conf [Errno 13] Permission denied: u'/etc/nut/upsd.conf'
/etc/nut/upsd.users [Errno 13] Permission denied: u'/etc/nut/upsd.users'

-- 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#730867: iceweasel: ssl_error_no_cypher_overlap error when using ipv6-enabled server with sslv3 disabled

[Pierre Emeriaud]

Package: iceweasel
Version: 25.0-1
Severity: important
Tags: ipv6

When using ipv6, iceaweasel SSL hello is SSLv3, whereas it offers TLSv1 when 
using ipv4.

This leeds to the ssl_error_no_cypher_overlap error messages if the server has 
SSLv3 disabled. 

This behavior is not seen with other packaging of Firefox, ie Arch's and 
Windows. 



-- Package-specific info:

-- Extensions information
Name: Adblock Plus
Location: ${PROFILE_EXTENSIONS}/{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}.xpi
Status: enabled

Name: au-revoir-utm
Location: ${PROFILE_EXTENSIONS}/jid1-yrtlfkrtmbr...@jetpack.xpi
Status: enabled

Name: Français Language Pack locale
Location: 
/usr/lib/iceweasel/browser/extensions/langpack...@iceweasel.mozilla.org.xpi
Package: iceweasel-l10n-fr
Status: enabled

Name: Ghostery
Location: ${PROFILE_EXTENSIONS}/fire...@ghostery.com.xpi
Status: enabled

Name: NoScript
Location: ${PROFILE_EXTENSIONS}/{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi
Status: enabled

Name: Thème par défaut theme
Location: 
/usr/lib/iceweasel/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}
Package: iceweasel
Status: enabled

Name: YSlow
Location: ${PROFILE_EXTENSIONS}/ys...@yahoo-inc.com.xpi
Status: enabled

-- Plugins information
Name: Shockwave Flash (11,2,202,310)
Location: /usr/lib/flashplugin-nonfree/libflashplayer.so
Status: enabled

Name: VLC Web Plugin
Location: /usr/lib/mozilla/plugins/libvlcplugin.so
Package: browser-plugin-vlc
Status: enabled


-- Addons package information
ii  browser-plugin 2.0.6-2  amd64multimedia plugin for web browser
ii  iceweasel  25.0-1   amd64Web browser based on Firefox
ii  iceweasel-l10n 1:25.0-1 all  French language package for Icewe

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

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

Versions of packages iceweasel depends on:
ii  debianutils 4.4
ii  fontconfig  2.11.0-1
ii  libc6   2.17-93
ii  libgdk-pixbuf2.0-0  2.28.2-1
ii  libglib2.0-02.36.4-1
ii  libgtk2.0-0 2.24.22-1
ii  libnspr42:4.10.2-1
ii  libnspr4-0d 2:4.10.2-1
ii  libsqlite3-03.8.1-1
ii  libstdc++6  4.8.2-1
ii  procps  1:3.3.4-2
ii  xulrunner-25.0  25.0-1

iceweasel recommends no packages.

Versions of packages iceweasel suggests:
pn  fonts-mathjax  
pn  fonts-oflb-asana-math  
pn  fonts-stix | otf-stix  
ii  libgssapi-krb5-2   1.11.3+dfsg-3
pn  mozplugger 

Versions of packages xulrunner-25.0 depends on:
ii  libasound21.0.27.2-3
ii  libatk1.0-0   2.10.0-2
ii  libbz2-1.01.0.6-5
ii  libc6 2.17-93
ii  libcairo2 1.12.16-2
ii  libdbus-1-3   1.6.18-1
ii  libdbus-glib-1-2  0.100.2-1
ii  libevent-2.0-52.0.21-stable-1
ii  libfontconfig12.11.0-1
ii  libfreetype6  2.4.9-1.1
ii  libgcc1   1:4.8.2-1
ii  libgdk-pixbuf2.0-02.28.2-1
ii  libglib2.0-0  2.36.4-1
ii  libgtk2.0-0   2.24.22-1
ii  libhunspell-1.3-0 1.3.2-6
ii  libmozjs25d   25.0-1
ii  libnspr4  2:4.10.2-1
ii  libnss3   2:3.15.3-1
ii  libpango-1.0-01.36.0-1
ii  libpixman-1-0 0.30.2-1
ii  libsqlite3-0  3.8.1-1
ii  libstartup-notification0  0.12-3
ii  libstdc++64.8.2-1
ii  libvpx1   1.2.0-2
ii  libx11-6  2:1.6.2-1
ii  libxext6  2:1.3.2-1
ii  libxrender1   1:0.9.8-1
ii  libxt61:1.1.4-1
ii  zlib1g1:1.2.8.dfsg-1

Versions of packages xulrunner-25.0 suggests:
ii  libcanberra0  0.30-2
ii  libgnomeui-0  2.24.5-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#730868: freeciv: New upstream version 2.4.1 available

[Jacob Nevins]

Package: freeciv
Severity: wishlist

We (upstream) are keen that 2.4.1 should get into Debian reasonably
quickly, since it fixes some notable bugs since the currently packaged
2.4.0. Details of the changes at
.


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

Bug#722084: lintian: [checks] Add Ruby pkg team checks to lintian

[Jonas Genannt]

Hello Niels,

thanks for your report on my package and sorry about the delay.

> This particular tag looks like a case of depends-on-obsolete-package and
> its sister tag, build-depends-on-obsolete-package.  Would you be okay
> with us just adding ruby1.8 to data/fields/obsolete-packages?

yes you are right. I have added a first new patch for lintian. This adds 
ruby1.8 and
libruby1.8 to the list of obsolete packages.

It would be nice if you can include that patch into the next release, this will 
make the
removal of ruby 1.8 easier.

I will open new bug report for the other features/checks for the Ruby Pkg.

Thanks,
Jonasdiff --git a/data/fields/obsolete-packages b/data/fields/obsolete-packages
index c70a2a0..f12071d 100644
--- a/data/fields/obsolete-packages
+++ b/data/fields/obsolete-packages
@@ -62,6 +62,8 @@ default-jdk-builddep
 
 # Last seen in Wheezy
 fuse-utils
+ruby1.8
+libruby1.8
 
 # See: http://wiki.debian.org/Teams/DebianPerlGroup/OpenTasks/Transitions/DigestSHA1ToDigestSHA
 libdigest-sha1-perl

Bug#725046: Bugs in packages meep-* (fwd)

[Thorsten Alteholz]

On Sat, 30 Nov 2013, Adam D. Barratt wrote:

I've marked them all for rejection, so it's just waiting for dak to
process that request.


Ok, thanks alot, the new upload is on its way ...

  Thorsten


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

Bug#730781: ibus-chewing: CVE-2013-4509

[陳昌倬]

Hi,

I just create a patch for ibus-chewing CVE-2013-4509 [1]. Please help to
review and upload it, thanks.

[1] https://mentors.debian.net/package/ibus-chewing
-- 
ChangZhuo Chen (陳昌倬) 
Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D


signature.asc
Description: Digital signature

Bug#728361: [Pkg-xfce-devel] Bug#728361: consolekit and libpam-systemd together

[Yves-Alexis Perez]

On jeu., 2013-11-28 at 22:43 +0100, Yves-Alexis Perez wrote:
> On jeu., 2013-11-28 at 22:38 +0100, Pascal Dormeau wrote:
> > On Thu, 28 Nov 2013 22:35:10 +0100
> > Yves-Alexis Perez  wrote:
> > 
> > > > BTW, this is unrelated because it affects lightdm and xfce4-session
> > > > versions already in archive, when libpam-systemd  is installed, if I
> > > > leave a session and log in again, loginctl shows previous sessions
> > > > on the same seat. Example:
> > 
> > > > I would have expected seeing only one session for the user (assuming
> > > > previous sessions have ended). I do not know if it is the normal
> > > > behavior or not and I do not know who to blame (lightdm or
> > > > xfce-session ?). I can open a bug report for that if you wish.
> > > 
> > > Indeed. Something is not cleaning the logind session, I guess. It does
> > > happen with an unpatched lightdm and libpam-systemd?
> > yes, with unpatched lightdm and libpam-systemd installed
> 
> So it might be worth asking systemd people. I don't have any knowledge
> of systemd, but here (afaict) the logind session is setup by
> libpam-systemd (not lightdm) and I /guess/ it should also be responsible
> for the logind session teardown.

Upstream comment on the patch:
https://bugs.launchpad.net/lightdm/+bug/1246770/comments/12

It might be worth asking systemd people about that compatibility layer
too.

Regards,
-- 
Yves-Alexis


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

Bug#602562: Can't see city sizes on white nation

[Jacob Nevins]

This should be closed now that 2.4.0-1 has hit the archive.
(But I'll leave actually closing it to the package maintainers.)


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

Bug#730869: Please upgrade python-pywcs from 1.11 to 1.10.1 or better

[Sergio Gelato]

Package: python-pywcs
Version: 1.11-1
Severity: wishlist

Judging from the upstream svn repository, development of this package is
continuing on the 1.10 branch. Trunk setup.cfg currently has
version = 1.10.3.dev
Version 1.11 is based on svn r2432, version 1.10.1 (tag pywcs.release_1.10.1)
on the much newer r3298. Some dependent packages (not yet in Debian but
available through pypi.python.org) build-depend on lib/pywcs/hooks.py (r3164)
which is not available on the 1.11 branch.

Version 1.10.2 can be found on the release_2013-03 branch; changes were merged
back into trunk at r3530.

I have been unable to find either a 1.11 maintenance or a 1.12 development
branch. I did find a statement at https://trac.assembla.com/astrolib concerning
future direction for this package and (somewhat ambiguously) identifying 1.10
as the current version.

I note in passing that the Source URL in the copyright file now leads to a
request to "[p]lease update your bookmarks to point directly at the
AstroLib Trac Wiki page", accompanied by a broken hyperlink. Surely one
can do better than that.


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

Bug#700222: freeciv-server: irrigation of swamps broken

[Jacob Nevins]

I wrote:
> : all progress on projects is lost when
> loading a savegame into 2.2.1.
> 
> So, was there one or more save/load cycles between these two turns?
> 
> If this is the case, then you'll see a different situation to me when
> you load those savegames. The bug is that progress is lost on load, so
> loading into a newer version of Freeciv, progress is not lost. I loaded
> into 2.2.7, as the 2.2.x version I had to hand. So I predict that when
> you load these savegames into 2.2.1, you're seeing the full 15 turns
> left in both cases. Is that correct?

I did the experiment myself with vanilla 2.2.1, and it behaves as I say.
So, I'm reasonably convinced upstream bug 16209 is behind this.

In the absence of further information from the original submitter, I
recommend this bug is marked as fixed by 2.2.2-1 and closed.
(But I leave actually doing so to the package maintainers.)

The only Debian release still affected by bug 16209 is
squeeze=oldstable.


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

Bug#730423: qtchooser: could not find a Qt installation of

[Lisandro Damián Nicanor Pérez Meyer]

On Tuesday 26 November 2013 15:46:21 Gregory Sharp wrote:
[snip] 
> Thank you Lisandro for the very clear explanation.
> 
> 
> I search a little, it seems xfce4 which sets XDG_CONFIG_DIRS
> in the script /usr/bin/startxfce4.  Do you think it is an
> 
> incorrect choice by xfce to set this variable,

To tell you the truth: I don't know. For the discussions I have read so far, 
it's not a very clear thing. So far KDE does not sets it, but it could start 
doing it at any point.

> or maybe they should also append your qtchooser directories?

If you can workaround it like this, the better.

> It is a problem that qmake and other executables aren't working. 
> Nevertheless, it is difficult for me to suggest how to resolve. 

Same for me. We (the Qt/KDE team) have been trying to personally reach 
qtchooser's uptream to talk about this issue face to face, but so far it has 
not been possible.

Kinds regards, Lisandro.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#730870: pu: unifont -- RoM; NMU Version in Stable Undoes Ubuntu Fix

[unifoundry]

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

I am requesting that the version of package Unifont in Testing, unifont
1:5.1.20080914-4, be included in the upcoming Wheezy point release
primarily to align with Colin Watson's wishes for Ubuntu.  Before the
NMU was uploaded to Debian this year, Colin made the following change in
the Unifont package on Ubuntu, for Ubuntu:

unifont (1:5.1.20080914-1.1ubuntu1) precise; urgency=low

  * Use maintscript support in dh_installdeb rather than writing out
dpkg-maintscript-helper commands by hand.  We now simply Pre-Depend
on a
new enough version of dpkg rather than using
'dpkg-maintscript-helper
supports' guards, leading to more predictable behaviour on upgrades.
 -- Colin WatsonMon, 13 Feb 2012 13:43:00
+

The Debian NMU of Unifont made its way to Ubuntu and did not incorporate
Colin's fix, so the upload had the effect of removing his fix from
Ubuntu.  The Unifont version in Testing does incorporate his fix, and
closed a bug that he filed on Debian (#659730) requesting this change.

These other significant changes were made in the version in Testing:

* Changed Section: to "fonts" for most debian/control entries to conform
to current Policy; the older "x11" (and now incorrect) Section entries
thus no longer need overriding.

* Updated packaging to conform to the policy version suitable for Wheezy
Stable (3.9.4), notably for the revised font handling requirements.

* Added hardening to debian/rules.

Allowing this update into Stable will harmonize what is in Debian with
what Colin Watson wanted in Ubuntu; it will use a debian/control file
that does not require Section overrides during building; and it will use
hardening.

I am attaching the changelog.

Thanks,


Paul Hardy

unifont (1:5.1.20080914-4) unstable; urgency=low

  * debian/control changes:
- Updated packaging to conform to Debian Policy version 3.9.4.
- Section tag is listed for each package; unifont-bin is in
  Section x11, and all other packages are in fonts.
- Added explicit Depends entry for xfonts-utils for each package,
  as per Debian Policy Manual 3.9.4 Section 11.8.5, "Packages
  providing fonts", item 9.
- Added Depends for fontforge to unifont-bin; removed weaker
  Suggests for fontforge from unifont-bin.
  * debian/rules - CPPFLAGS is now declared and used, for hardening.

 -- Paul Hardy   Thu, 14 Nov 2013 05:16:42 -0800

unifont (1:5.1.20080914-3) unstable; urgency=low

  * Changed debian/control unifont Section entry from "x11" to "fonts".
  * Changed debian/control Depends entries for unifont and ttf-unifont
to add "Depends: ${misc:Depends}".
  * Corrected changelog entries for 1:5.1.20080914-2.
  * debian/rules uses dpkg-buildflags to set CFLAGS & LDFLAGS, for
hardening.

 -- Paul Hardy   Sun, 10 Nov 2013 19:55:48 -0800

unifont (1:5.1.20080914-2) unstable; urgency=low

  [ Colin Watson ]
  * Use maintscript support in dh_installdeb rather than writing out
dpkg-maintscript-helper commands by hand.  We now simply Pre-Depend on a
new enough version of dpkg rather than using 'dpkg-maintscript-helper
supports' guards, leading to more predictable behaviour on upgrades.
(Closes: #659730)

  [ Paul Hardy ]
  * Applied above changes that Colin Watson provided in bug report,
simplifying debian/ file structure and making the Unifont package
more suitable for Ubuntu.  The one exception is I didn't create
the ttf-unifont.maintscript file, because /etc/defoma/ no longer
exists on Debian or Ubuntu.
  * debian/copyright - updated copyright and licensing information to
reflect the latest source code changes and license agreements.
  * debian/README.Debian - minor change now that Etch is no longer
the current release.
  * README - updated documentation to cover font modifications and the
latest license agreements.
  * Corrected changelog entries for 1:5.1.20080808-1 and 1:5.1.20080914-1.2.
  * debian/control changes:
- Build-Depends: debhelper (>= 8.1.0~), per Colin Watson's above changes.
- No separate uploaders.
  * Created debian/source/format file.
  * Removed debian/TODO file as it referred to defoma, which is no longer used.
  * debian/watch now looks at ftp.gnu.org for upstream releases.
  * Accept NMU of Christian Perrier.  (Closes: #634981)
  * Accept NMUs of Paul Wise and Samuel Bronson.  (Closes: #697999, #698067)

 -- Paul Hardy   Fri, 01 Nov 2013 18:39:56 -0700

unifont (1:5.1.20080914-1.3) unstable; urgency=low

  * Non-maintainer upload.
  * debian/rules: Split and inline "install" target into "binary-arch" and
"binary-indep" and adjust dependencies.  (Without this,
"dpkg-buildpackage -B" ends up running the build-indep rules and dying
on the buildds.)
  * debian/rules: Also fix so dpkg-buildpackage -j works, and only builds
the font files once.

 -- Samuel Bronson   Sat, 12 Jan 2013 13:09:

Bug#727708: systemd (security) bugs (was: init system question)

[Moritz Mühlenhoff]

On Thu, Nov 28, 2013 at 08:07:16PM -0600, Steve Langasek wrote:
> All distributions "care" about not having security issues in their code, but
> that's not the same thing as actually doing the work to audit the code.  In
> practice this only happens when dedicated resources are turned on the code
> in question, and having more companies using the code does not magically
> make that happen.

[I took care of the systemd DSA people are referring to]

The issue people are talking about were discovered during a review of
the Red Hat Product Security Team (most likely triggered by the inclusion
of systemd into RHEL7).
So in fact having more companies use the code exactly made that magically
happen.

For every complex code base a thorough review will unveil security-related
implementation bugs and the ones found for systemd are not exactly earth-
shattering.

More review and more usage will lead to more bugs being found, we should
rather applaud Red Hat for investing resources and be diligent. After all
Red Hat is the only distro staffing a proactive product security team
(from which everyone is profiting outside of RH as well). I don't consider
the lack of reported security issues for the contenders as a credible 
indication of them being more secure.

FWIW, the main reason I'm personally in favour of adopting systemd is precisely 
security (in terms of sandboxing and restricting services). See
http://0pointer.de/blog/projects/security.html for some pointers.

[EOD from me due to a lack of time, but that needed to be said]

Cheers,
Moritz


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

Bug#730865: mate-dialogs: Please ship zenity replacement

[Martintxo]

OK. I think that all mate-dialogs packages were be build alltogether :-D. No
problem !!

Btw. I'm now using the debian official mate-dialog packages like a zenity
replacement in a Jessie box, with icewm as wm. I only make the following
simbolic link:
lrwxrwxrwx 1 root root 19 aza 30 12:30 /usr/bin/zenity -> /usr/bin/matedialog
and all is working without trouble.

Keep in this packaging effort !!. Many thanks. Greetings. Mtx.

2013/11/30 13:32 (lr.) eguna,
John Paul Adrian Glaubitz (e)k idatzi zuen:

> Hello Martintxo!
> 
> On 11/30/2013 01:23 PM, martintxo wrote:
> > Please considere shipping mate-dialogs-gnome package for zenity replacement.
> > Thanks in advance. Greetings. Martintxo.
> 
> The packaging of Mate is still work-in-progress and the fact that
> mate-dialogs-gnome is missing doesn't mean we don't package it but
> that we haven't packaged it yet.
> 
> Mate consists of over 50 single packages and it takes some time to get
> them into Debian, please be patient.
> 
> Unless the other Mate maintainers object, I'd like to close this bug
> report as invalid.
> 
> Thanks,
> 
> Adrian
> 
> -- 
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Sustrai Erakuntza: respuesta jurídico-técnica a proyectos insostenibles.
  proiektu jasangaitzei erantzun juridiko-teknikoa.
  http://www.fundacionsustrai.org
  http://www.sustraierakuntza.org


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

Bug#725978: bug

[jerigondor]

I have the same problem. When a CD/DVD is inserted, nothing is happend.
My system is Debian testing with 3.11-2-686-pae.
And now, what can I do to mount my drive?


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

Bug#691812: udevil -- flexible CLI tool

[Tsu Jan]

Now, it's needed even with KDE-4.11, where auto-mount doesn't work by default. 
A nifty app indeed!


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

Bug#730781: ibus-chewing: CVE-2013-4509

[Osamu Aoki]

Hi,

On Sat, Nov 30, 2013 at 10:44:07PM +0800, ChangZhuo Chen wrote:
> Hi,
> 
> I just create a patch for ibus-chewing CVE-2013-4509 [1]. Please help to
> review and upload it, thanks.
> 
> [1] https://mentors.debian.net/package/ibus-chewing

Looks good to me as first glance.

As above page mention fix these 2 things.

Please add yourself as uploader (Yes, you still need sponsor but this is
not NMU) or add “ * Team upload.”  in changelog if you are joining to
maintain this. https://wiki.debian.org/TeamUpload

Also, Someone wrote an updated debian/watch file you may want to include
in the package. See http://packages.qa.debian.org/i/ibus-chewing.html

Osamu


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

Bug#730713: lintian: Detect also the typo supress

[Bastien ROUCARIES]

control: tags -1 + pending

On Thu, Nov 28, 2013 at 4:07 PM, Sylvestre Ledru  wrote:
> Package: lintian
> Version: 2.5.17
> Severity: minor
>
> Hello,
>
> The attached patch add supress => suppress in the list of spelling mistakes
> Update the related test
> Fix that typo in the source code of Lintian
>
> Thanks

Merged thanks
>
>
> -- System Information:
> Debian Release: jessie/sid
>   APT prefers testing
>   APT policy: (600, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
> 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages lintian depends on:
> ii  binutils   2.23.52.20130828-1
> ii  bzip2  1.0.6-5
> ii  diffstat   1.55-3
> ii  file   1:5.14-2
> ii  gettext0.18.3.1-1
> ii  hardening-includes 2.3
> 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.34-1+b1
> ii  libdpkg-perl   1.16.10
> ii  libemail-valid-perl0.190-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   1.2000-1
> ii  liburi-perl1.60-1
> ii  man-db 2.6.5-2
> ii  patchutils 0.3.2-2
> ii  perl [libdigest-sha-perl]  5.18.1-3
> ii  t1utils1.37-2
>
> Versions of packages lintian recommends:
> pn  libperlio-gzip-perl 
> ii  perl-modules [libautodie-perl]  5.18.1-3
>
> Versions of packages lintian suggests:
> pn  binutils-multiarch 
> ii  dpkg-dev   1.16.10
> ii  libhtml-parser-perl3.71-1+b1
> ii  libtext-template-perl  1.45-2
> ii  xz-utils   5.1.1alpha+20120614-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#727708: systemd (security) bugs (was: init system question)

[Lars Wirzenius]

On Sat, Nov 30, 2013 at 04:07:17PM +0100, Moritz Mühlenhoff wrote:
> [EOD from me due to a lack of time, but that needed to be said]

And thank you for saying it.

-- 
http://www.cafepress.com/trunktees -- geeky funny T-shirts
http://gtdfh.branchable.com/ -- GTD for hackers


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

Bug#730827: ITP: light-locker -- simple screen locker for LightDM display manager

[Steve Cotton]

On Fri, Nov 29, 2013 at 22:36 +0100, Yves-Alexis Perez wrote:
>   Description : simple screen locker for LightDM display manager
> 
> light-locker is a simple locker that aims to have simple, sane, secure
> defaults and be well integrated with the desktop while not carrying any
> desktop-specific dependencies.

I suggest changing "locker" to "locking screensaver" in the long
description.  Both for people thinking "what kind of locker" and
people searching for screensaver packages.

Cheers,
Steve


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

Bug#730872: /lib/udev/rules.d/60-gnupg.rules: please add 08e6:34ec to /lib/udev/rules.d/60-gnupg.rules

[Yves-Alexis Perez]

Package: gnupg
Version: 1.4.15-1.1
Severity: normal
File: /lib/udev/rules.d/60-gnupg.rules

Hi,

I have an ExpressCard smartcard reader from Gemalto:

Bus 002 Device 008: ID 08e6:34ec Gemplus Compact Smart Card Reader Writer


which I use with gnupg(2) with an OpenPGP smartcard. Correct permissions
on the devices (using acls) can be provided by consolekit
(/lib/udev/rules.d/70-udev-acl.rules) or systemd
(/lib/udev/rules.d/70-uaccess.rules), assuming the ID_SMARTCARD_READER
property is present on the device.

It's done correctly already for two Gemalto readers (3478 and 34c2) but
mine is missing. Would it be possible to add that line:

ATTR{idVendor}=="08e6", ATTR{idProduct}=="34ec", ENV{ID_SMARTCARD_READER}="1",  
ENV{ID_SMARTCARD_READER_DRIVER}="gnupg"

Thanks in advance,
-- 
Yves-Alexis Perez


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

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

Versions of packages gnupg depends on:
ii  gpgv  1.4.15-1.1
ii  libbz2-1.01.0.6-5
ii  libc6 2.17-97
ii  libreadline6  6.2+dfsg-0.1
ii  libusb-0.1-4  2:0.1.12-23.3
ii  zlib1g1:1.2.8.dfsg-1

Versions of packages gnupg recommends:
pn  gnupg-curl 
ii  libldap-2.4-2  2.4.31-1+nmu2+b1

Versions of packages gnupg suggests:
ii  eog   3.10.1-2
pn  gnupg-doc 
ii  imagemagick   8:6.7.7.10-6
ii  libpcsclite1  1.8.10-1

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/bin/gpg (from gnupg package)


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

Bug#730827: ITP: light-locker -- simple screen locker for LightDM display manager

[Yves-Alexis Perez]

On sam., 2013-11-30 at 15:43 +, Steve Cotton wrote:
> On Fri, Nov 29, 2013 at 22:36 +0100, Yves-Alexis Perez wrote:
> >   Description : simple screen locker for LightDM display manager
> > 
> > light-locker is a simple locker that aims to have simple, sane, secure
> > defaults and be well integrated with the desktop while not carrying any
> > desktop-specific dependencies.
> 
> I suggest changing "locker" to "locking screensaver" in the long
> description.  Both for people thinking "what kind of locker" and
> people searching for screensaver packages.
> 
It's not a screensaver so I'm a  bit reluctant to add it here, but I've
changed to “screen locker” to mimic the small description.

Regards,
-- 
Yves-Alexis


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

Bug#730836: higan: Setting video driver to OpenGL causes higan to crash on startup

[Tobias Hansen]

Hi,

thanks for your bug report. Higan requires OpenGL 3.2 or higher to use
OpenGL. The error handling is bad and I know from correspondence with
upstream that the next version will improve upon this point.

Cheers,
Tobias


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

Bug#730714: lintian: Tag openjdk-6-jdk and openjdk-6-jre as obsolete

[Bastien ROUCARIES]

control: tags -1 + pending

With a few minor modification done

On Thu, Nov 28, 2013 at 4:15 PM, Sylvestre Ledru  wrote:
> Package: lintian
> Version: 2.5.17
> Severity: normal
>
> Hello,
>
> The attached patch tags openjdk-6-jdk, openjdk-6-jre and 
> openjdk-6-jre-headless as obsolete (See #720911).
> It is one of the goal for Jessie.
> The patch also tags java-compiler as not recommended and propose the usage
> of defaul-jdk.
>
> Tests are provided in the patch
>
> Thanks,
> Sylvestre
>
> -- System Information:
> Debian Release: jessie/sid
>   APT prefers testing
>   APT policy: (600, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
> 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages lintian depends on:
> ii  binutils   2.23.52.20130828-1
> ii  bzip2  1.0.6-5
> ii  diffstat   1.55-3
> ii  file   1:5.14-2
> ii  gettext0.18.3.1-1
> ii  hardening-includes 2.3
> 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.34-1+b1
> ii  libdpkg-perl   1.16.10
> ii  libemail-valid-perl0.190-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   1.2000-1
> ii  liburi-perl1.60-1
> ii  man-db 2.6.5-2
> ii  patchutils 0.3.2-2
> ii  perl [libdigest-sha-perl]  5.18.1-3
> ii  t1utils1.37-2
>
> Versions of packages lintian recommends:
> pn  libperlio-gzip-perl 
> ii  perl-modules [libautodie-perl]  5.18.1-3
>
> Versions of packages lintian suggests:
> pn  binutils-multiarch 
> ii  dpkg-dev   1.16.10
> ii  libhtml-parser-perl3.71-1+b1
> ii  libtext-template-perl  1.45-2
> ii  xz-utils   5.1.1alpha+20120614-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#718711: atlas-cpp: ftbfs on armhf: update symbols file

[Andreas Moog]

 subscribe

Hello there,

I wanted to ask about the status of this bug? It is marked as "pending"
but as far as I can see there was no upload or further activity since
August.

Thanks for your time.

Cheers,
  Andreas

-- 
Andreas Moog, Berliner Str. 29, 36205 Sontra/Germany
PGP-encrypted mails preferred (Key-ID: 74DE6624)
PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624



signature.asc
Description: OpenPGP digital signature

Bug#730147: llvm-3.3: Shared object libs matching static missing

[Sylvestre Ledru]

Hello Marc,

On 22/11/2013 00:13, Marc J. Driftmeyer wrote:
> Package: llvm-3.3
> Version: 1:3.3-13
> Severity: normal
>
> Dear Maintainer,
>
> Could we please build out for both shared and static libs on LLVM/Clang for 
> at least 3.4 and moving forward?
>
For now, we have
http://packages.debian.org/sid/amd64/llvm-3.3-dev/filelist

Could you detail a bit more what you expect ? :)

Thanks
Sylvestre


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

Bug#730871: general: Filesystem? Some problems with sizes of files.

[Konstantin Khomoutov]

On Sat, 30 Nov 2013 19:37:41 +0400
Евгений Просветов  wrote:

> When I copied 15.2G file to free 64G flash, I've encountered the next
> error:
> 
> root@home-desktop:~# cp backup272291.tar /media/84D0-F52A/
> cp: запись «/media/84D0-F52A/backup272291.tar»: Файл слишком
> велик
> cp: не удалось расширить
> «/media/84D0-F52A/backup272291.tar»: Файл слишком велик
> 
> (Cannot "expand" the file, it's too big). Here is the source file
> properties:
> 
> root@home-desktop:~# ls -l backup272291.tar
> -rw-r--r-- 1 root root 15195166720 ноя 30 18:30 backup272291.tar
[...]
> /dev/sdb1 60G
> 4,1G 56G7% /media/84D0-F52A
> 
> (Only 4.1G of 60G is filled on /dev/sdb1 now).
> My LXDE filemanager (pcmanfm) declares, that size of the file on
> flash is 4.3G, but its size "on the disk" is more then 137G. What
> does it mean and how is it possible for 64G drive? And what is the
> operation "to expand the file" which is failed?

May be the file you're trying to copy is sparse [1]?  GNU tar does
support this.  Flash drives typically contain FAT32 on them which
doesn't support sparse files, so when copying such a file from a "real"
file system to FAT32 the kernel's copying routine has to "stuff" the
file.

Try running

$ du --apparent-size -h backup272291.tar

to see how much disk space it's worth taking into account its
sparseness, if any.

1. http://en.wikipedia.org/wiki/Sparse_file


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

Bug#730873: seed: FTBFS on big endian architectures

[Andreas Beckmann]

Package: seed
Version: 3.8.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

seed FTBFS on mips, powerpc, s390x, sparc with similar errors:

https://buildd.debian.org/status/package.php?p=seed

Making all in readline
make[5]: Entering directory `/«PKGBUILDDIR»/doc/modules/readline'
.../../../src/seed ../../../doc/modules/make-functions.js 
../../../doc/modules/readline/readline.js > 
../../../doc/modules/readline/readline-funcs.xml
/bin/bash: line 1: 24968 Segmentation fault  ../../../src/seed 
../../../doc/modules/make-functions.js 
../../../doc/modules/readline/readline.js > 
../../../doc/modules/readline/readline-funcs.xml
make[5]: *** [readline-funcs.xml] Error 139
make[5]: Leaving directory `/«PKGBUILDDIR»/doc/modules/readline'
make[4]: *** [all-recursive] Error 1


Andreas


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

Bug#730871: general: Filesystem? Some problems with sizes of files.

[Thomas Goirand]

On 11/30/2013 11:56 PM, Konstantin Khomoutov wrote:
> May be the file you're trying to copy is sparse [1]?  GNU tar does
> support this.  Flash drives typically contain FAT32 on them which
> doesn't support sparse files, so when copying such a file from a "real"
> file system to FAT32 the kernel's copying routine has to "stuff" the
> file.
> 
> Try running
> 
> $ du --apparent-size -h backup272291.tar
> 
> to see how much disk space it's worth taking into account its
> sparseness, if any.
> 
> 1. http://en.wikipedia.org/wiki/Sparse_file

If it was FAT32, then it wouldn't even accept files bigger than 2GB.
That is by the way an information which we miss here: what kind of
filesystem is on that flash medium?

Thomas


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

Bug#730874: ceilometer: please switch (Build-)Depends to python-msgpack

[Andreas Beckmann]

Package: ceilometer
Version: 2013.2-2
Severity: important

Hi,

msgpack-python has changed its name to python-msgpack.
Even if the new package Provides: msgpack-python this does not seem to
be sufficient to allow automatic removal of the old package from the
archive.


Andreas


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

Bug#730870: pu: unifont -- RoM; NMU Version in Stable Undoes Ubuntu Fix

[unifoundry]

user release.debian@packages.debian.org
usertags 730870 pu
thanks



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

Bug#730875: salt: please switch (Build-)Depends to python-msgpack

[Andreas Beckmann]

Package: salt
Version: 0.17.2-2
Severity: important

Hi,

msgpack-python has changed its name to python-msgpack.
Even if the new package Provides: msgpack-python this does not seem to
be sufficient to allow automatic removal of the old package from the
archive.


Andreas


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

Bug#712982: RFS: peg/0.1.11-1 -- recursive-descent parser generators for C

[Jakub Wilk]

* Giulio Paci , 2013-11-29, 17:13:

What do you mean by "Drop manpages"?
I dropped the manpages file. Do you think is ok to rephrase the entry as "Drop 
manpages file"?


I'd write something akin "Drop debian/manpages. Upstream makefile now takes 
care of installing the manpages, so the is no longer needed."


Apparently upstream released a new tarball with some changes, without updating 
the version number. I will inform upstream to avoid it in future.


Very well.

I am going to update the content in git accordingly to latest 0.1.13 package 
and let you know when it is ready.


OK.


Could it be uploaded to unstable instead of experimental?

I think so.


Let's do it then. :)

--
Jakub Wilk


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

Bug#728468: kupfer: uses deprecated keyring.backend.$keyring

[Sebastian Ramacher]

Hi maintainer

On 2013-11-01 17:04:24, Sebastian Ramacher wrote:
> In python-keyring 1.1 the keyrings from keyring.backend have been moved
> into separate modules in keyring.backends and added compatibility
> imports in keyring.backend. In python-keyring 3.0 these compatibility
> imports have been removed. kupfer still uses keyrings from
> keyring.backend and needs to be adopted for the new naming scheme.
> 
> Please apply the attached patch to make kupfer compatible with
> python-keyring 3.0 and later. python-keyring 3.2 is available in
> experimental so that you can test the patch.

Are there any news regarding this bug? We would like to upload
python-keyring 3.2.1 to unstable soon, but that's blocked by this bug.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#730876: pristine-tar: cannot reproduce antpm_1.12.orig.tar.xz

[kristof.ralov...@gmail.com]

Subject: pristine-tar: cannot reproduce antpm_1.12.orig.tar.xz
Package: pristine-tar
Version: 1.30
Severity: important

Dear Maintainer,

I cannot reproduce antpm_1.12.orig.tar.xz under debian unstable.

Reproduction works under both:
- i386 debian stable with tar 1.26-dfsg-0.1, pristine-tar 1.25+deb7u1
- amd63 ubuntu 13.04 with tar 1.26-dfsg5, pristine-tar 1.26

The below is output from the pristine-tar failing under debian unstable:

user@debian:~/antpm$ pristine-tar -vdk checkout antpm_1.12.orig.tar.xz
pristine-tar: git archive --format=tar
c2a3df1f2ea0686a4276facb73ba0e56f2aaf942 | (cd
'/tmp/pristine-tar.hfvN6LMyRh' && tar x)
pristine-tar: tar xf /tmp/pristine-tar.rOykflrD2U/tmpin -C
/tmp/pristine-tar.0QNqWhyZZD
pristine-tar: set subdir to .travis.yml
pristine-tar: found file not in subdir .travis.yml: LICENSE
pristine-tar: mv /tmp/pristine-tar.hfvN6LMyRh
/tmp/pristine-tar.S3a_fNeIj3/workdir
pristine-tar: tar cf /tmp/pristine-tar.S3a_fNeIj3/recreatetarball --owner 0
--group 0 --numeric-owner -C /tmp/pristine-tar.S3a_fNeIj3/workdir
--no-recursion --mode 0644 --files-from
/tmp/pristine-tar.S3a_fNeIj3/manifest
pristine-tar: xdelta patch /tmp/pristine-tar.0QNqWhyZZD/delta
/tmp/pristine-tar.S3a_fNeIj3/recreatetarball
/tmp/pristine-tar.yitFG16I0j/antpm_1.12.orig.tar.xz.tmp
xdelta: expected from file (/tmp/pristine-tar.S3a_fNeIj3/recreatetarball)
of length 2856960 bytes
pristine-tar: tar cf /tmp/pristine-tar.S3a_fNeIj3/recreatetarball --owner 0
--group 0 --numeric-owner -C /tmp/pristine-tar.S3a_fNeIj3/workdir
--no-recursion --mode 0644 --files-from
/tmp/pristine-tar.S3a_fNeIj3/manifest
pristine-tar: xdelta patch /tmp/pristine-tar.0QNqWhyZZD/delta
/tmp/pristine-tar.S3a_fNeIj3/recreatetarball
/tmp/pristine-tar.yitFG16I0j/antpm_1.12.orig.tar.xz.tmp
xdelta: expected from file (/tmp/pristine-tar.S3a_fNeIj3/recreatetarball)
of length 2856960 bytes
pristine-tar: set subdir to .travis.yml
pristine-tar: found file not in subdir .travis.yml: LICENSE
pristine-tar: mv /tmp/pristine-tar.S3a_fNeIj3/workdir
/tmp/pristine-tar.gWVKlPjddY/workdir
pristine-tar: tar cf /tmp/pristine-tar.gWVKlPjddY/recreatetarball --owner 0
--group 0 --numeric-owner -C /tmp/pristine-tar.gWVKlPjddY/workdir
--no-recursion --mode 0644 --files-from
/tmp/pristine-tar.gWVKlPjddY/manifest -H gnu
pristine-tar: xdelta patch /tmp/pristine-tar.0QNqWhyZZD/delta
/tmp/pristine-tar.gWVKlPjddY/recreatetarball
/tmp/pristine-tar.yitFG16I0j/antpm_1.12.orig.tar.xz.tmp
xdelta: expected from file (/tmp/pristine-tar.gWVKlPjddY/recreatetarball)
of length 2856960 bytes
pristine-tar: set subdir to .travis.yml
pristine-tar: found file not in subdir .travis.yml: LICENSE
pristine-tar: mv /tmp/pristine-tar.gWVKlPjddY/workdir
/tmp/pristine-tar.CkBGKHNiCU/workdir
pristine-tar: tar cf /tmp/pristine-tar.CkBGKHNiCU/recreatetarball --owner 0
--group 0 --numeric-owner -C /tmp/pristine-tar.CkBGKHNiCU/workdir
--no-recursion --mode 0644 --files-from
/tmp/pristine-tar.CkBGKHNiCU/manifest -H posix
pristine-tar: xdelta patch /tmp/pristine-tar.0QNqWhyZZD/delta
/tmp/pristine-tar.CkBGKHNiCU/recreatetarball
/tmp/pristine-tar.yitFG16I0j/antpm_1.12.orig.tar.xz.tmp
xdelta: expected from file (/tmp/pristine-tar.CkBGKHNiCU/recreatetarball)
of length 2856960 bytes
pristine-tar: Failed to reproduce original tarball. Please file a bug
report.
pristine-tar: failed to generate tarball


antpm sources are available under
http://anonscm.debian.org/gitweb/?p=pkg-running/antpm.git;a=summary

Maybe this is similar to debian bug #726963 ?



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

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

Versions of packages pristine-tar depends on:
ii  libbz2-1.01.0.6-5
ii  libc6 2.17-97
ii  perl-modules  5.18.1-4
ii  tar   1.27-3
ii  xdelta1.1.3-9
ii  zlib1g1:1.2.8.dfsg-1

Versions of packages pristine-tar recommends:
ii  bzip2 1.0.6-5
ii  pbzip21.1.8-1
ii  xz-utils  5.1.1alpha+20120614-2

pristine-tar suggests no packages.

-- no debconf information

Bug#728470: python-novaclient: uses deprecated keyring.backend.$keyring

[Sebastian Ramacher]

Hi maintainer!

On 2013-11-01 17:11:37, Sebastian Ramacher wrote:
> In python-keyring 1.1 the keyrings from keyring.backend have been moved
> into separate modules in keyring.backends and compatibility imports have
> been added in keyring.backend. In python-keyring 3.0 these compatibility
> imports have been removed. python-novaclient still uses keyrings from
> keyring.backend and needs to be adopted for the new naming scheme.
> 
> Please apply the attached patch to make python-novaclient compatible
> with python-keyring 3.0 and later. Please also adjust dependencies on
> python-keyring if necessary. python-keyring 3.2 is available in
> experimental so that you can test the patch.

Are there any news regarding this bug? We would like to upload
python-keyring 3.2.1 to unstable soon, but that's blocked by this bug.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#730871: general: Filesystem? Some problems with sizes of files.

[Konstantin Khomoutov]

On Sun, 01 Dec 2013 00:13:06 +0800
Thomas Goirand  wrote:

> > May be the file you're trying to copy is sparse [1]?  GNU tar does
> > support this.  Flash drives typically contain FAT32 on them which
> > doesn't support sparse files, so when copying such a file from a
> > "real" file system to FAT32 the kernel's copying routine has to
> > "stuff" the file.
[...]
> If it was FAT32, then it wouldn't even accept files bigger than 2GB.

4 GiB - 1 byte, actually.  But you're correct on this anyway.


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

Bug#730871: general: Filesystem? Some problems with sizes of files.

[Konstantin Khomoutov]

On Sun, 01 Dec 2013 00:13:06 +0800
Thomas Goirand  wrote:

> If it was FAT32, then it wouldn't even accept files bigger than 2GB.
> That is by the way an information which we miss here: what kind of
> filesystem is on that flash medium?

Oh, by the way, the OP had this observation after copying failed:

> /dev/sdb1 60G
> 4,1G 56G7% /media/84D0-F52A
>
> (Only 4.1G of 60G is filled on /dev/sdb1 now).

Isn't this the 4GiB FAT32 limit (plus the file alocation overhead
accounting for another 0.1GiB) here?  That is, file copying might has
stopped just after hitting the max file size limit.

Regarding the original error messages (in Russian):

>root@home-desktop:~# cp backup272291.tar /media/84D0-F52A/
> cp: запись «/media/84D0-F52A/backup272291.tar»: Файл слишком велик

This one is "cp: write «...»: file is too large"

> cp: не удалось расширить «/media/84D0-F52A/backup272291.tar»: Файл
> слишком велик

This one inedded uses the verb "расширить" which does translate from
Russian as "to expand", and that what had deluded me into thinking
we're seeing a sparse file limit.
Might be a coreutils localization issue in fact.


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

Bug#725729: abootimg: will produce non-functional images on a big-endian machine

[Gilles Grandou]

On 07/10/2013 20:52, Simon McVittie wrote:

Package: abootimg
Version: 0.6-1
Severity: normal
Tags: upstream

By inspection of its source code, abootimg has the same bug as Android
mkbootimg: because it writes host structs directly into the file,
if the size or endianness of any of the integers in those structs does
not match the expected size/endianness (4-byte int, little-endian),
the image will be misinterpreted by the Android device.


I agree, but as I don't have any big-endian system under my hand, I 
won't be able to test it. Patches are welcome ;)



Another possibility would be to only build abootimg on little-endian
platforms (any-i386, any-amd64, armel, armhf, mipsel etc., but not
powerpc).


It would make sense. I don't see any usage case where you would like to 
manipulate Android boot image from a bigendian host...


Thanks,
Gilles.


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

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

[Sebastian Ramacher]

Control: tags -1 + moreinfo unreproducible

On 2013-11-05 15:39:41, Florian Birée wrote:
> Package: dwb
> Version: 20130503hg-2
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
>* What led up to the situation?
>
>Browsing the web, the problem appear on a lot of situations (website, 
> number
>of tabs).
>
>I reproduce it by opening http://fr.wikipedia.org/, then opening one link
>on it in a new tab.
>
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
>I tried to run dwb with the default configuration (i.e. by removing my
>~/.config/dwb/): same problem.
>  
>* What was the outcome of this action?
>
>A crash with a segmentation fault (see the output).
>
>* What outcome did you expect instead?
>
>A working browser ;-)

I tried to reproduce the crash but I wasn't able to. Does this work with
other webkit based browsers?

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

Regards
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#730877: debian-handbook: FTBFS: No such file or directory at /usr/lib/perl5/XML/Parser/Expat.pm line 470

[David Suárez]

Source: debian-handbook
Version: 6.0+20121031
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131128 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory `/«BUILDDIR»/debian-handbook-6.0+20121031'
> publican build --publish --formats=html --langs=en-US
> Use of uninitialized value in concatenation (.) or string at 
> /usr/bin/publican line 735,  line 13.
> 
> No such file or directory at /usr/lib/perl5/XML/Parser/Expat.pm line 470.
>  at line 123, column 0, byte 4432
> Handler couldn't resolve external entity at line 123, column 0, byte 4432
> error in processing external entity reference at line 123, column 0, byte 4432
> error in processing external entity reference at line 3, column 1, byte 163 
> at /usr/lib/perl5/XML/Parser.pm line 187.
> Setting up en-US
>   Processing file tmp/en-US/xml/Common_Content/Conventions.xml -> 
> tmp/en-US/xml/Common_Content/Conventions.xml
>   Processing file tmp/en-US/xml/Common_Content/Feedback.xml -> 
> tmp/en-US/xml/Common_Content/Feedback.xml
>   Processing file tmp/en-US/xml/Common_Content/Legal_Notice.xml -> 
> tmp/en-US/xml/Common_Content/Legal_Notice.xml
>   Processing file tmp/en-US/xml/Common_Content/Program_Listing.xml -> 
> tmp/en-US/xml/Common_Content/Program_Listing.xml
>   Processing file tmp/en-US/xml/Common_Content/Revision_History.xml -> 
> tmp/en-US/xml/Common_Content/Revision_History.xml
>   Processing file tmp/en-US/xml_tmp/00a_preface.xml -> 
> tmp/en-US/xml/00a_preface.xml
>   Processing file tmp/en-US/xml_tmp/00b_foreword.xml -> 
> tmp/en-US/xml/00b_foreword.xml
>   Processing file tmp/en-US/xml_tmp/01_the-debian-project.xml -> 
> tmp/en-US/xml/01_the-debian-project.xml
>   Processing file tmp/en-US/xml_tmp/02_case-study.xml -> 
> tmp/en-US/xml/02_case-study.xml
>   Processing file tmp/en-US/xml_tmp/03_existing-setup.xml -> 
> tmp/en-US/xml/03_existing-setup.xml
>   Processing file tmp/en-US/xml_tmp/04_installation.xml -> 
> tmp/en-US/xml/04_installation.xml
>   Processing file tmp/en-US/xml_tmp/05_packaging-system.xml -> 
> tmp/en-US/xml/05_packaging-system.xml
>   Processing file tmp/en-US/xml_tmp/06_apt.xml -> tmp/en-US/xml/06_apt.xml
>   Processing file tmp/en-US/xml_tmp/07_solving-problems.xml -> 
> tmp/en-US/xml/07_solving-problems.xml
>   Processing file tmp/en-US/xml_tmp/08_basic-configuration.xml -> 
> tmp/en-US/xml/08_basic-configuration.xml
>   Processing file tmp/en-US/xml_tmp/09_unix-services.xml -> 
> tmp/en-US/xml/09_unix-services.xml
>   Processing file tmp/en-US/xml_tmp/10_network-infrastructure.xml -> 
> tmp/en-US/xml/10_network-infrastructure.xml
>   Processing file tmp/en-US/xml_tmp/11_network-services.xml -> 
> tmp/en-US/xml/11_network-services.xml
>   Processing file tmp/en-US/xml_tmp/12_advanced-administration.xml -> 
> tmp/en-US/xml/12_advanced-administration.xml
>   Processing file tmp/en-US/xml_tmp/13_workstation.xml -> 
> tmp/en-US/xml/13_workstation.xml
>   Processing file tmp/en-US/xml_tmp/14_security.xml -> 
> tmp/en-US/xml/14_security.xml
>   Processing file tmp/en-US/xml_tmp/15_debian-packaging.xml -> 
> tmp/en-US/xml/15_debian-packaging.xml
>   Processing file tmp/en-US/xml_tmp/70_conclusion.xml -> 
> tmp/en-US/xml/70_conclusion.xml
>   Processing file tmp/en-US/xml_tmp/90_derivative-distributions.xml -> 
> tmp/en-US/xml/90_derivative-distributions.xml
>   Processing file tmp/en-US/xml_tmp/92_short-remedial-course.xml -> 
> tmp/en-US/xml/92_short-remedial-course.xml
>   Processing file tmp/en-US/xml_tmp/Author_Group.xml -> 
> tmp/en-US/xml/Author_Group.xml
>   Processing file tmp/en-US/xml_tmp/Book_Info.xml -> 
> tmp/en-US/xml/Book_Info.xml
>   Processing file tmp/en-US/xml_tmp/Revision_History.xml -> 
> tmp/en-US/xml/Revision_History.xml
>   Processing file tmp/en-US/xml_tmp/debian-handbook.xml -> 
> tmp/en-US/xml/debian-handbook.xml
> Beginning work on en-US
> DTD Validation OK
>   Starting html
> make[1]: *** [override_dh_auto_build] Error 2

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/11/28/debian-handbook_6.0+20121031_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


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

Bug#730882: grilo-plugins: FTBFS: Tests errors

[David Suárez]

Source: grilo-plugins
Version: 0.2.9-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131128 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[3]: Entering directory `/«PKGBUILDDIR»/tests/tmdb'
> TEST: test_tmdb_fast_resolution... (pid=27710)
> **
> ERROR:test_tmdb_fast_resolution.c:73:test_fast_resolution: assertion failed 
> (error == NULL): Could not find mock content Key file does not have group 
> 'http://api.themoviedb.org/3/configuration?api_key=TMDB_TEST_API_KEY' 
> (grilo.error.general, 5)
>   /tmdb/fast-resolution:   FAIL
> GTester: last random seed: R02S6af8b2536f22254b652086939bc2f3eb
> /bin/bash: line 1: 27709 Terminated  gtester --verbose 
> test_tmdb_fast_resolution test_tmdb_fast_resolution_by_id 
> test_tmdb_full_resolution test_tmdb_missing_configuration 
> test_tmdb_preconditions
> make[3]: *** [test-nonrecursive] Error 143
> /bin/bash: line 2: exit: test-nonrecursive: numeric argument required
> make[2]: *** [test] Error 255
> /bin/bash: line 2: exit: test-nonrecursive: numeric argument required
> make[1]: *** [test] Error 255
> dh_auto_test: make -j1 test returned exit code 2

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/11/28/grilo-plugins_0.2.9-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


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

Bug#730879: chkconfig: FTBFS: dpkg-buildpackage: error: dpkg-source -b chkconfig-11.4-54.60.1 gave error exit status 255

[David Suárez]

Source: chkconfig
Version: 11.4-54.60.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131128 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory `/«PKGBUILDDIR»'
> rm -rf /«PKGBUILDDIR»/tmp/
> dh_clean
> make[1]: Leaving directory `/«PKGBUILDDIR»'
>  dpkg-source -b chkconfig-11.4-54.60.1
> dpkg-source: error: can't build with source format '3.0 (native)': native 
> package version may not have a revision
> dpkg-buildpackage: error: dpkg-source -b chkconfig-11.4-54.60.1 gave error 
> exit status 255
> 
> Build finished at 20131128-0207

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/11/28/chkconfig_11.4-54.60.1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


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

Bug#730880: stompserver: FTBFS: Hard dependency on ruby1.8

[David Suárez]

Source: stompserver
Version: 0.9.9gem-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131128 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  fakeroot debian/rules binary
> dh binary --buildsystem=ruby --with ruby
>dh_testroot -O--buildsystem=ruby
>dh_prep -O--buildsystem=ruby
>dh_installdirs -O--buildsystem=ruby
>dh_auto_install -O--buildsystem=ruby
> /usr/lib/ruby/vendor_ruby/gem2deb.rb:17: warning: setting 
> Encoding.default_external
> /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:31: warning: method redefined; 
> discarding old visit_String
> /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:4: warning: previous definition of 
> visit_String was here
> /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:39: warning: method redefined; 
> discarding old register
> /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:12: warning: previous definition 
> of register was here
> /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:43: warning: method redefined; 
> discarding old format_time
> /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:16: warning: previous definition 
> of format_time was here
> /usr/lib/ruby/1.9.1/rubygems/syck_hack.rb:115: warning: method redefined; 
> discarding old to_s
> /usr/lib/ruby/1.9.1/rubygems/syck_hack.rb:44: warning: previous definition of 
> to_s was here
>   Entering dh_ruby --install
> install -d /«PKGBUILDDIR»/debian/stompserver/usr/bin
> install -D -m755 /«PKGBUILDDIR»/bin/stompserver 
> /«PKGBUILDDIR»/debian/stompserver/usr/bin/stompserver
> install -d /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby
> install -D -m644 /«PKGBUILDDIR»/lib/stomp_server.rb 
> /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server.rb
> install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/test_server.rb 
> /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/test_server.rb
> install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/protocols/http.rb 
> /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/protocols/http.rb
> install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/protocols/stomp.rb 
> /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/protocols/stomp.rb
> install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/queue.rb 
> /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/queue.rb
> install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/queue/activerecord_queue.rb 
> /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/queue/activerecord_queue.rb
> install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/queue/ar_message.rb 
> /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/queue/ar_message.rb
> install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/queue/dbm_queue.rb 
> /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/queue/dbm_queue.rb
> install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/queue/file_queue.rb 
> /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/queue/file_queue.rb
> install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/queue/memory_queue.rb 
> /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/queue/memory_queue.rb
> install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/queue_manager.rb 
> /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/queue_manager.rb
> install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/stomp_auth.rb 
> /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/stomp_auth.rb
> install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/stomp_frame.rb 
> /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/stomp_frame.rb
> install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/stomp_id.rb 
> /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/stomp_id.rb
> install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/stomp_user.rb 
> /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/stomp_user.rb
> install -D -m644 /«PKGBUILDDIR»/lib/stomp_server/topic_manager.rb 
> /«PKGBUILDDIR»/debian/stompserver/usr/lib/ruby/vendor_ruby/stomp_server/topic_manager.rb
> /usr/lib/ruby/vendor_ruby/gem2deb.rb:52:in `system': can't convert nil into 
> String (TypeError)
>   from /usr/lib/ruby/vendor_ruby/gem2deb.rb:52:in `run'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:138:in 
> `run_tests_for_version'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:129:in `block in 
> run_tests'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:128:in `each'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:128:in `run_tests'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:72:in `install'
>   from /usr/bin/dh_ruby:69:in `block (2 levels) in '
>   from /usr/lib/ruby/1.9.1/optparse.rb:1360:in `call'
>   from /usr/lib/ruby/1.9.1/optparse.rb:1360:in `block in parse_in_order

Bug#730878: jgit: FTBFS: /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/debug/DiffAlgorithms.java:[120,52] error: cannot find symbol

[David Suárez]

Source: jgit
Version: 3.1.0-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131128 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully): 
> main:
>  [copy] Copying 1 file to 
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/target/META-INF
> [INFO] Executed tasks
> [INFO] [resources:resources {execution: default-resources}]
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 3 resources
> [INFO] Copying 1 resource
> [INFO] [compiler:compile {execution: default-compile}]
> [INFO] Compiling 62 source files to 
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/target/classes
> [INFO] -
> [ERROR] COMPILATION ERROR : 
> [INFO] -
> [ERROR] 
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/RevWalkTextBuiltin.java:[127,48]
>  error: cannot find symbol
> [ERROR]   symbol:   method multiValued()
>   location: @interface Option
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/Show.java:[90,48]
>  error: cannot find symbol
> [ERROR]   symbol:   method multiValued()
>   location: @interface Option
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/debug/TextHashFunctions.java:[253,26]
>  error: cannot find symbol
> [ERROR]   symbol:   method multiValued()
>   location: @interface Option
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/debug/TextHashFunctions.java:[256,26]
>  error: cannot find symbol
> [ERROR]   symbol:   method multiValued()
>   location: @interface Option
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/debug/TextHashFunctions.java:[262,52]
>  error: cannot find symbol
> [ERROR]   symbol:   method multiValued()
>   location: @interface Option
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/Status.java:[74,48]
>  error: cannot find symbol
> [ERROR]   symbol:   method multiValued()
>   location: @interface Option
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/LsTree.java:[69,49]
>  error: cannot find symbol
> [ERROR]   symbol:   method multiValued()
>   location: @interface Option
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/Diff.java:[92,49]
>  error: cannot find symbol
> [ERROR]   symbol:   method multiValued()
>   location: @interface Option
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/Daemon.java:[78,108]
>  error: cannot find symbol
> [ERROR]   symbol:   method multiValued()
>   location: @interface Option
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/Daemon.java:[81,110]
>  error: cannot find symbol
> [ERROR]   symbol:   method multiValued()
>   location: @interface Option
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/Daemon.java:[84,121]
>  error: cannot find symbol
> [ERROR]   symbol:   method multiValued()
>   location: @interface Option
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/Daemon.java:[87,122]
>  error: cannot find symbol
> [ERROR]   symbol:   method multiValued()
>   location: @interface Option
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/DiffTree.java:[72,48]
>  error: cannot find symbol
> [ERROR]   symbol:   method multiValued()
>   location: @interface Option
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/debug/DiffAlgorithms.java:[114,31]
>  error: cannot find symbol
> [ERROR]   symbol:   method multiValued()
>   location: @interface Option
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/debug/DiffAlgorithms.java:[120,52]
>  error: cannot find symbol
> [ERROR]   symbol:   method multiValued()
>   location: @interface Option
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/opt/CmdLineParser.java:[187,3]
>  error: no suitable constructor found for 
> OptionDef(String,String,boolean,Class,boolean)
> [INFO] 16 errors 
> [INFO] -
> [INFO] 
> 
> [ERROR] BUILD FAILURE
> [INFO] 
> 
> [INFO] Compilation failure
> 
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/RevWalkTextBuiltin.java:[127,48]
>  error: cannot find symbol
>   symbol:   method multiValued()
>   location: @interface Option
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/Show.java:[90,48]
>  error: cannot find symbol
>   symbol:   method multiValued()
>   location: @interface Option
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/debug/TextHashFunctions.java:[253,26]
>  error: cannot find symbol
>   symbol:   method multiValued()
>   location: @interface Option
> /«PKGBUILDDIR»/org.eclipse.jgit.pgm/src/org/eclipse/jgit/pgm/debug/TextHashFunctions.java:[256,26]
>  error: ca

Bug#730883: linux-tools: FTBFS: b-d on libiberty-dev instead of binutils-dev

[David Suárez]

Source: linux-tools
Version: 3.11-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131128 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Due to the switch of libiberty to his own package (libiberty|libiberty-dev).

Relevant part (hopefully):
> gcc -I/«PKGBUILDDIR»/include  -o modpost.real-msb-64 file2alias.real-msb-64.o 
> modpost.real-msb-64.o sumversion.real-msb-64.o
> make[6]: Leaving directory `/«PKGBUILDDIR»/debian/build/scripts/mod'
> make[5]: Leaving directory `/«PKGBUILDDIR»/debian/build/scripts/mod'
> make[4]: Leaving directory `/«PKGBUILDDIR»/debian/build/scripts'
> Making all in tools
> make[4]: Entering directory `/«PKGBUILDDIR»/debian/build/tools'
> Making all in perf
> make[5]: Entering directory `/«PKGBUILDDIR»/debian/build/tools/perf'
> mkdir out
> /usr/bin/make prefix=/usr perfexecdir=share/perf_3.11-core NO_GTK2=1 
> NO_PERL=1 V=2 HAVE_CPLUS_DEMANGLE=1 ARCH=x86_64 EXTRA_WARNINGS=-Wno-error 
> NO_LIBUNWIND= -C /«PKGBUILDDIR»/tools/perf 
> O=/«PKGBUILDDIR»/debian/build/tools/perf/out all VERSION=3.11
> CHK -fstack-protector-all
> CHK -Wstack-protector
> CHK -Wvolatile-register-var
> CHK -D_FORTIFY_SOURCE=2
> CHK bionic
> CHK libelf
> CHK libdw
> CHK -DLIBELF_MMAP
> CHK -DLIBELF_MMAP
> CHK libunwind
> CHK libaudit
> CHK libslang
> CHK perl
> CHK python
> CHK python version
> CHK -DHAVE_STRLCPY
> CHK -DHAVE_ON_EXIT
> CHK -DBACKTRACE_SUPPORT
> CHK libnuma
> make[6]: Entering directory `/«PKGBUILDDIR»/tools/perf'
> config/Makefile:419: No numa.h found, disables 'perf bench numa mem' 
> benchmark, please install numa-libs-devel or libnuma-dev
> MKDIR /«PKGBUILDDIR»/debian/build/tools/perf/out/arch
> MKDIR /«PKGBUILDDIR»/debian/build/tools/perf/out/arch/x86/util
> MKDIR /«PKGBUILDDIR»/debian/build/tools/perf/out/bench
> MKDIR 
> /«PKGBUILDDIR»/debian/build/tools/perf/out/scripts/perl/Perf-Trace-Util
> MKDIR 
> /«PKGBUILDDIR»/debian/build/tools/perf/out/scripts/python/Perf-Trace-Util
> MKDIR /«PKGBUILDDIR»/debian/build/tools/perf/out/tests
> MKDIR /«PKGBUILDDIR»/debian/build/tools/perf/out/ui
> MKDIR /«PKGBUILDDIR»/debian/build/tools/perf/out/ui/browsers
> MKDIR /«PKGBUILDDIR»/debian/build/tools/perf/out/ui/stdio
> MKDIR /«PKGBUILDDIR»/debian/build/tools/perf/out/ui/tui
> MKDIR /«PKGBUILDDIR»/debian/build/tools/perf/out/util
> MKDIR /«PKGBUILDDIR»/debian/build/tools/perf/out/util/scripting-engines
> GEN /«PKGBUILDDIR»/debian/build/tools/perf/out/common-cmds.h
> * new build flags or prefix
> PERF_VERSION = 3.11.0
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/perf.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-annotate.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-bench.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/bench/sched-messaging.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/bench/sched-pipe.o
> CC 
> /«PKGBUILDDIR»/debian/build/tools/perf/out/bench/mem-memcpy-x86-64-asm.o
> CC 
> /«PKGBUILDDIR»/debian/build/tools/perf/out/bench/mem-memset-x86-64-asm.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/bench/mem-memcpy.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/bench/mem-memset.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-diff.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-evlist.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-help.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-sched.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-buildid-list.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-buildid-cache.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-list.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-record.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-report.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-stat.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-timechart.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-top.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-script.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-probe.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-kmem.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-lock.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-kvm.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-inject.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/tests/builtin-test.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-mem.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/builtin-trace.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/util/abspath.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf/out/util/alias.o
> CC /«PKGBUILDDIR»/debian/build/tools/perf

Bug#730886: maven-stapler-plugin: FTBFS: Missing required artifact: org.apache.maven.plugins:maven-compiler-plugin:jar:2.0.2

[David Suárez]

Source: maven-stapler-plugin
Version: 1.16-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131128 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> /usr/share/maven-debian-helper/copy-repo.sh /«PKGBUILDDIR»/debian
> mh_patchpoms -plibmaven-stapler-plugin-java --debian-build --keep-pom-version 
> --maven-repo=/«PKGBUILDDIR»/debian/maven-repo 
> touch debian/stamp-poms-patched
> # before-build target may be used to unpatch the pom files, so we need to 
> check if
> # patching the pom files is needed here, normally not
> if [ ! -f pom.xml.save ]; then \
>   /usr/bin/make -f debian/rules patch-poms; \
>   fi
> cd . && /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven2/boot/classworlds.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dproperties.file.manual=/«PKGBUILDDIR»/debian/maven.properties 
> -Dclassworlds.conf=/etc/maven2/m2-debian.conf 
> org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml 
> -Dmaven.repo.local=/«PKGBUILDDIR»/debian/maven-repo  package
> [INFO] 
> NOTE: Maven is executing in offline mode. Any artifacts not already in your 
> local
> repository will be inaccessible.
> 
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Building Maven Stapler plugin
> [INFO]task-segment: [package]
> [INFO] 
> 
> [WARNING] POM for 
> 'org.codehaus.plexus:plexus-compiler-javac:pom:debian:compile' is invalid.
> 
> Its dependencies (if any) will NOT be available to the current build.
> [WARNING] POM for 
> 'org.codehaus.plexus:plexus-compiler-api:pom:debian:compile' is invalid.
> 
> Its dependencies (if any) will NOT be available to the current build.
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Failed to resolve artifact.
> 
> Missing:
> --
> 1) org.apache.maven.plugins:maven-compiler-plugin:jar:2.0.2
> 
>   Try downloading the file manually from the project website.
> 
>   Then, install it using the command: 
>   mvn install:install-file -DgroupId=org.apache.maven.plugins 
> -DartifactId=maven-compiler-plugin -Dversion=2.0.2 -Dpackaging=jar 
> -Dfile=/path/to/file
> 
>   Alternatively, if you host your own repository you can deploy the file 
> there: 
>   mvn deploy:deploy-file -DgroupId=org.apache.maven.plugins 
> -DartifactId=maven-compiler-plugin -Dversion=2.0.2 -Dpackaging=jar 
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> 
>   Path to dependency: 
>   1) org.kohsuke.stapler:maven-stapler-plugin:maven-plugin:1.16
>   2) org.apache.maven.plugins:maven-compiler-plugin:jar:2.0.2
> 
> --
> 1 required artifact is missing.
> 
> for artifact: 
>   org.kohsuke.stapler:maven-stapler-plugin:maven-plugin:1.16
> 
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2),
>   maven2-repository.dev.java.net (http://download.java.net/maven/2/)
> 
> 
> 
> NOTE: Maven is executing in offline mode. Any artifacts not already in your 
> local
> repository will be inaccessible.
> 
> 
> [INFO] 
> 
> [INFO] For more information, run Maven with the -e switch
> [INFO] 
> 
> [INFO] Total time: 2 seconds
> [INFO] Finished at: Thu Nov 28 01:53:51 UTC 2013
> [INFO] Final Memory: 9M/58M
> [INFO] 
> 
> make: *** [mvn-build] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/11/28/maven-stapler-plugin_1.16-4_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


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