Bug#753542: Bug#753444: Bug#753542: perl-base - Segfaults in libperl.so.5.18

[Emilio Pozuelo Monfort]

On 07/07/14 10:49, Emilio Pozuelo Monfort wrote:
> On 07/07/14 09:31, Aurelien Jarno wrote:
>> On Sat, Jul 05, 2014 at 07:15:56PM +0200, Emilio Pozuelo Monfort wrote:
>>> That said, feel free to upload perl now.
>>
>> It has been uploaded, and is now installed on all s390x buildds.
> 
> Thanks. I have scheduled a bunch of binNMUs.

I scheduled all of them, and there are a few failures:

https://release.debian.org/transitions/html/perlapi-5.18.2d-s390x.html

However the main blocker right now is the perl/mips FTBFS.

Emilio


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

Bug#753699: lynx: Alert!: This client does not contain support for HTTPS URLs.

[Atsuhito Kohda]

Hi Andreas and Thorsten,

On Fri, 4 Jul 2014 20:09:52 +0200, Andreas Metzler wrote:

> Looks like lynx-cur is missing a build-dependency on
> libgcrypt20-dev as a hotfix or better use gnutls_rnd() instead of
> gcry_randomize() and stop linking against gcrypt. (Totally untested,
> no guarantees patch attached.)

I only added libgcrypt20-dev to B-D and built the package, then
it seems lynx works fine so I uploaded the package.  
But if your patch is necessary to fix the problem properly, 
please let me know.

Best regards,   2014-7-8(Tue)

-- 
 Debian Developer - much more I18N of Debian
 Atsuhito Kohda 
 Department of Math., Univ. of Tokushima


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

Bug#754157: gnuplot: file conflict with gnuplot-x11

[Sven Joachim]

Package: gnuplot
Version: 4.6.5-5
Severity: serious

There was a problem when installing your package (sorry for the German):

,
| Entpacken von gnuplot (4.6.5-5) über (4.6.5-4) ...
| dpkg: Fehler beim Bearbeiten des Archivs 
/var/cache/apt/archives/gnuplot_4.6.5-5_all.deb (--unpack):
|  Versuch, »/usr/share/gnuplot/pm3d/colorpts.awk« zu überschreiben, welches 
auch in Paket gnuplot-x11 4.6.5-4 ist
`

After upgrading gnuplot-x11 to 4.6.5-5 the error went away, so it might
be just a missing Replaces.


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

Kernel: Linux 3.14.11-nouveau (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 gnuplot depends on:
iu  gnuplot-x11  4.6.5-5

gnuplot recommends no packages.

Versions of packages gnuplot suggests:
pn  feedgnuplot  
ii  gnuplot-doc  4.6.5-5
pn  libgnuplot-iostream-dev  
pn  python-gnuplot   

-- no debconf information


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

Bug#754158: blueman: blueman-applet says pulseaudio is too old

[Łukasz Stelmach]

Package: blueman
Version: 1.23-1
Severity: grave

Dear Maintainer,

blueman-applet fails to start and prints the following message

--8<---cut here---start->8---
blueman-applet version 1.22 starting
Using gconf config backend
Using gconf config backend
Using gconf config backend
Using gconf config backend
Using gconf config backend
Using gconf config backend
Using gconf config backend
Using gconf config backend
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/blueman/plugins/BasePlugin.py", line 
65, in _load
self.on_load(parent)
  File "/usr/lib/python2.7/dist-packages/blueman/plugins/applet/PulseAudio.py", 
line 173, in on_load
raise Exception("PulseAudio too old, required 0.9.15 or higher")
Exception: PulseAudio too old, required 0.9.15 or higher
Using gconf config backend
Using gconf config backend
Using gconf config backend
Deleting plugin instance 

--8<---cut here---end--->8---

It looks like the code in PulseAudio.py that checks the version number
is too simple

--8<---cut here---start->8---
if version[2] < 15:
raise Exception("PulseAudio too old, required 0.9.15 or 
higher")
--8<---cut here---end--->8---

The version reported by the blueman.main.PulseAudioUtils module is "[4,
0, 0]"

--8<---cut here---start->8---
Python 2.7.3 (default, Mar 13 2014, 11:03:55) 
[GCC 4.7.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from blueman.main.PulseAudioUtils import PulseAudioUtils, EventType
>>> foo=PulseAudioUtils()
_
pa_context_event 
(/usr/lib/python2.7/dist-packages/blueman/main/PulseAudioUtils.py:159)
1 
_
pa_context_event 
(/usr/lib/python2.7/dist-packages/blueman/main/PulseAudioUtils.py:159)
5 
>>> foo.GetVersion()
[4, 0, 0]
>>>
--8<---cut here---end--->8---

The problem is fiexed in the trunk version of blueman

http://bazaar.launchpad.net/~blueman/blueman/trunk/view/head:/blueman/plugins/applet/PulseAudio.py#L180

as well as 1.23-git201312311147-1~bpo70+1 in wheezy-backports.

-- System Information:
Debian Release: 7.5
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (900, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: armel

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

Versions of packages blueman depends on:
ii  bluez 4.99-2
ii  dbus  1.6.8-1+deb7u3
ii  gnome-icon-theme  3.4.0-2
ii  libatk1.0-0   2.4.0-2
ii  libbluetooth3 4.99-2
ii  libc6 2.13-38+deb7u1
ii  libcairo2 1.12.2-3
ii  libfontconfig12.9.0-7.1
ii  libfreetype6  2.4.9-1.1
ii  libgdk-pixbuf2.0-02.26.1-1
ii  libglib2.0-0  2.33.12+really2.32.4-5
ii  libgtk2.0-0   2.24.10-2
ii  libpango1.0-0 1.30.0-1
ii  libpython2.7  2.7.3-6+deb7u2
ii  librsvg2-common   2.36.1-2
ii  libstartup-notification0  0.12-1
ii  notify-osd [notification-daemon]  0.9.34-2
ii  obex-data-server  0.4.5-1+b3
ii  python2.7.3-4+deb7u1
ii  python-dbus   1.1.1-1
ii  python-gi 3.2.2-2
ii  python-gtk2   2.24.0-3+b1
ii  python-notify 0.1.1-3
ii  python2.7 2.7.3-6+deb7u2

Versions of packages blueman recommends:
ii  libpulse-mainloop-glib0  4.0-6~bpo7+1
ii  policykit-1  0.105-3
ii  python-gconf 2.28.1+dfsg-1

blueman suggests no packages.

-- no debconf information

-- 
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics


pgpzfsfEZFFv4.pgp
Description: PGP signature

Bug#740574: libtirpc1: Still causes statd from the nfs-common package to fail

[Matteo Checcucci]

As reported by others, downgrading to libtirpc1/0.2.2-5 and libc6/2.19-1
(and restarting rpcbind, nfs-common, and nfs-kernel-server) makes the
issue vanish.

I think this bug is grave, since it prevents NFS from working.



Everything works with libtirpc1/0.2.3-2 and libc6/2.19-4
Thank you


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

Bug#753444: Bug#753542: Bug#753444: Bug#753542: perl-base - Segfaults in libperl.so.5.18

[Niko Tyni]

On Tue, Jul 08, 2014 at 09:43:14AM +0200, Emilio Pozuelo Monfort wrote:

> https://release.debian.org/transitions/html/perlapi-5.18.2d-s390x.html
> 
> However the main blocker right now is the perl/mips FTBFS.

For the record, I'm aware of this but it's currently difficult to find
the time.  The quick fix is probably to build with gcc-4.8 on mips or
something like that.
-- 
Niko Tyni   nt...@debian.org


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

Bug#753901: marked as done (python-tk: linker error when importing Tkinter. Cannot find libblt2.4)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jul 2014 09:36:14 +
with message-id 
and subject line Bug#753901: fixed in python-stdlib-extensions 2.7.8-1
has caused the Debian Bug report #753901,
regarding python-tk: linker error when importing Tkinter. Cannot find libblt2.4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
753901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-tk
Version: 2.7.7-2
Severity: grave
Tags: d-i
Justification: renders package unusable


Dear Maintainer,


I just did a system update from within Synaptic, with the following changes:
--
Start-Date: 2014-07-05  21:41:36
Commandline: /usr/sbin/synaptic /usr/sbin/synaptic
Install: libgnutls28-dev:amd64 (3.2.15-2, automatic), libgnutls-xssl0:amd64
(3.2.15-2, automatic), nettle-dev:amd64 (2.7.1-2+b1, automatic),
libgnutlsxx28:amd64 (3.2.15-2, automatic)
Upgrade: libopencv-core2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1),
libqt5concurrent5:amd64 (5.3.1+dfsg-2, 5.3.1+dfsg-3), libopencv-
videostab2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1), qt5-qmake:amd64
(5.3.1+dfsg-2, 5.3.1+dfsg-3), libopencv-ml2.4:amd64 (2.4.8+dfsg1-2.2,
2.4.9+dfsg-1), libpython2.7-stdlib:amd64 (2.7.7-2, 2.7.8-1), glib-networking-
common:amd64 (2.40.1-1, 2.40.1-2), luatex:amd64 (2014.20140528.34243-3,
2014.20140528.34243-4), libopencv-photo2.4:amd64 (2.4.8+dfsg1-2.2,
2.4.9+dfsg-1), qt5-default:amd64 (5.3.1+dfsg-2, 5.3.1+dfsg-3), libopencv-
video2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1), libqt5sql5-sqlite:amd64
(5.3.1+dfsg-2, 5.3.1+dfsg-3), libgnomevfs2-dev:amd64 (2.24.4-4, 2.24.4-6),
pv:amd64 (1.2.0-1, 1.5.3-1), qtbase5-dev-tools:amd64 (5.3.1+dfsg-2,
5.3.1+dfsg-3), mksh:amd64 (50-1, 50-3), libpod-plainer-perl:amd64 (1.03-1,
1.04-1), libqt5sql5:amd64 (5.3.1+dfsg-2, 5.3.1+dfsg-3), libopencv-
legacy2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1), libxmmsclient6:amd64
(0.8+dfsg-10, 0.8+dfsg-11), libtirpc1:amd64 (0.2.3-1, 0.2.3-2),
libqt5core5a:amd64 (5.3.1+dfsg-2, 5.3.1+dfsg-3), python2.7:amd64 (2.7.7-2,
2.7.8-1), libopencv-ts2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1), libopencv-
features2d2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1), libxmmsclient-glib1:amd64
(0.8+dfsg-10, 0.8+dfsg-11), libopencv-objdetect2.4:amd64 (2.4.8+dfsg1-2.2,
2.4.9+dfsg-1), libflite1:amd64 (1.4-release-8, 1.4-release-10), liburi-
perl:amd64 (1.60-1, 1.61-1), libqt5xml5:amd64 (5.3.1+dfsg-2, 5.3.1+dfsg-3),
libwww-perl:amd64 (6.06-1, 6.07-1), xmms2-icon:amd64 (0.8+dfsg-10,
0.8+dfsg-11), libopencv-imgproc2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1),
libpython2.7-dev:amd64 (2.7.7-2, 2.7.8-1), libqt5test5:amd64 (5.3.1+dfsg-2,
5.3.1+dfsg-3), binutils:amd64 (2.24.51.20140617-1, 2.24.51.20140704-1),
libqt5printsupport5:amd64 (5.3.1+dfsg-2, 5.3.1+dfsg-3), texlive-binaries:amd64
(2014.20140528.34243-3+b1, 2014.20140528.34243-4), libopencv-gpu2.4:amd64
(2.4.8+dfsg1-2.2, 2.4.9+dfsg-1), libpython2.7:amd64 (2.7.7-2, 2.7.8-1), python-
sip:amd64 (4.16.1+dfsg-1, 4.16.2+dfsg-1), libsamplerate0-dev:amd64 (0.1.8-7,
0.1.8-8), libgnomevfs2-common:amd64 (2.24.4-4, 2.24.4-6), libsynctex1:amd64
(2014.20140528.34243-3+b1, 2014.20140528.34243-4), libkpathsea6:amd64
(2014.20140528.34243-3+b1, 2014.20140528.34243-4), libqt5widgets5:amd64
(5.3.1+dfsg-2, 5.3.1+dfsg-3), libopencv-ocl2.4:amd64 (2.4.8+dfsg1-2.2,
2.4.9+dfsg-1), libgnomevfs2-extra:amd64 (2.24.4-4, 2.24.4-6),
python2.7-dev:amd64 (2.7.7-2, 2.7.8-1), libgnomevfs2-0:amd64 (2.24.4-4,
2.24.4-6), libopencv-highgui2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1),
blt:amd64 (2.4z-9, 2.5.3-2), libopencv-calib3d2.4:amd64 (2.4.8+dfsg1-2.2,
2.4.9+dfsg-1), python2.7-minimal:amd64 (2.7.7-2, 2.7.8-1), libopencv-
stitching2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1), libqt5dbus5:amd64
(5.3.1+dfsg-2, 5.3.1+dfsg-3), libopencv-superres2.4:amd64 (2.4.8+dfsg1-2.2,
2.4.9+dfsg-1), libqt5gui5:amd64 (5.3.1+dfsg-2, 5.3.1+dfsg-3), libopencv-
contrib2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1), libqt5network5:amd64
(5.3.1+dfsg-2, 5.3.1+dfsg-3), libtasn1-6:amd64 (3.7-1, 4.0-2), glib-networking-
services:amd64 (2.40.1-1, 2.40.1-2), libptexenc1:amd64
(2014.20140528.34243-3+b1, 2014.20140528.34243-4), glib-networking:amd64
(2.40.1-1, 2.40.1-2), libopencv-flann2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1),
libpython2.7-minimal:amd64 (2.7.7-2, 2.7.8-1), qtbase5-dev:amd64 (5.3.1+dfsg-2,
5.3.1+dfsg-3), libsamplerate0:amd64 (0.1.8-7, 0.1.8-8), libtasn1-6-dev:amd64
(3.7-1, 4.0-2)
Remove: libgnutls-dev:amd64 (2.12.23-17)
End-Date: 2014-07-05  21:42:47
--
However, Tk applications no l

Bug#753902: marked as done (python-tk: linker error when importing Tkinter. Cannot find libblt2.4)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jul 2014 09:36:14 +
with message-id 
and subject line Bug#753901: fixed in python-stdlib-extensions 2.7.8-1
has caused the Debian Bug report #753901,
regarding python-tk: linker error when importing Tkinter. Cannot find libblt2.4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
753901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-tk
Version: 2.7.7-2
Severity: grave
Tags: d-i
Justification: renders package unusable

Dear Maintainer,


I just did a system update from within Synaptic, with the following changes:
--
Start-Date: 2014-07-05  21:41:36
Commandline: /usr/sbin/synaptic /usr/sbin/synaptic
Install: libgnutls28-dev:amd64 (3.2.15-2, automatic), libgnutls-xssl0:amd64
(3.2.15-2, automatic), nettle-dev:amd64 (2.7.1-2+b1, automatic),
libgnutlsxx28:amd64 (3.2.15-2, automatic)
Upgrade: libopencv-core2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1),
libqt5concurrent5:amd64 (5.3.1+dfsg-2, 5.3.1+dfsg-3), libopencv-
videostab2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1), qt5-qmake:amd64
(5.3.1+dfsg-2, 5.3.1+dfsg-3), libopencv-ml2.4:amd64 (2.4.8+dfsg1-2.2,
2.4.9+dfsg-1), libpython2.7-stdlib:amd64 (2.7.7-2, 2.7.8-1), glib-networking-
common:amd64 (2.40.1-1, 2.40.1-2), luatex:amd64 (2014.20140528.34243-3,
2014.20140528.34243-4), libopencv-photo2.4:amd64 (2.4.8+dfsg1-2.2,
2.4.9+dfsg-1), qt5-default:amd64 (5.3.1+dfsg-2, 5.3.1+dfsg-3), libopencv-
video2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1), libqt5sql5-sqlite:amd64
(5.3.1+dfsg-2, 5.3.1+dfsg-3), libgnomevfs2-dev:amd64 (2.24.4-4, 2.24.4-6),
pv:amd64 (1.2.0-1, 1.5.3-1), qtbase5-dev-tools:amd64 (5.3.1+dfsg-2,
5.3.1+dfsg-3), mksh:amd64 (50-1, 50-3), libpod-plainer-perl:amd64 (1.03-1,
1.04-1), libqt5sql5:amd64 (5.3.1+dfsg-2, 5.3.1+dfsg-3), libopencv-
legacy2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1), libxmmsclient6:amd64
(0.8+dfsg-10, 0.8+dfsg-11), libtirpc1:amd64 (0.2.3-1, 0.2.3-2),
libqt5core5a:amd64 (5.3.1+dfsg-2, 5.3.1+dfsg-3), python2.7:amd64 (2.7.7-2,
2.7.8-1), libopencv-ts2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1), libopencv-
features2d2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1), libxmmsclient-glib1:amd64
(0.8+dfsg-10, 0.8+dfsg-11), libopencv-objdetect2.4:amd64 (2.4.8+dfsg1-2.2,
2.4.9+dfsg-1), libflite1:amd64 (1.4-release-8, 1.4-release-10), liburi-
perl:amd64 (1.60-1, 1.61-1), libqt5xml5:amd64 (5.3.1+dfsg-2, 5.3.1+dfsg-3),
libwww-perl:amd64 (6.06-1, 6.07-1), xmms2-icon:amd64 (0.8+dfsg-10,
0.8+dfsg-11), libopencv-imgproc2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1),
libpython2.7-dev:amd64 (2.7.7-2, 2.7.8-1), libqt5test5:amd64 (5.3.1+dfsg-2,
5.3.1+dfsg-3), binutils:amd64 (2.24.51.20140617-1, 2.24.51.20140704-1),
libqt5printsupport5:amd64 (5.3.1+dfsg-2, 5.3.1+dfsg-3), texlive-binaries:amd64
(2014.20140528.34243-3+b1, 2014.20140528.34243-4), libopencv-gpu2.4:amd64
(2.4.8+dfsg1-2.2, 2.4.9+dfsg-1), libpython2.7:amd64 (2.7.7-2, 2.7.8-1), python-
sip:amd64 (4.16.1+dfsg-1, 4.16.2+dfsg-1), libsamplerate0-dev:amd64 (0.1.8-7,
0.1.8-8), libgnomevfs2-common:amd64 (2.24.4-4, 2.24.4-6), libsynctex1:amd64
(2014.20140528.34243-3+b1, 2014.20140528.34243-4), libkpathsea6:amd64
(2014.20140528.34243-3+b1, 2014.20140528.34243-4), libqt5widgets5:amd64
(5.3.1+dfsg-2, 5.3.1+dfsg-3), libopencv-ocl2.4:amd64 (2.4.8+dfsg1-2.2,
2.4.9+dfsg-1), libgnomevfs2-extra:amd64 (2.24.4-4, 2.24.4-6),
python2.7-dev:amd64 (2.7.7-2, 2.7.8-1), libgnomevfs2-0:amd64 (2.24.4-4,
2.24.4-6), libopencv-highgui2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1),
blt:amd64 (2.4z-9, 2.5.3-2), libopencv-calib3d2.4:amd64 (2.4.8+dfsg1-2.2,
2.4.9+dfsg-1), python2.7-minimal:amd64 (2.7.7-2, 2.7.8-1), libopencv-
stitching2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1), libqt5dbus5:amd64
(5.3.1+dfsg-2, 5.3.1+dfsg-3), libopencv-superres2.4:amd64 (2.4.8+dfsg1-2.2,
2.4.9+dfsg-1), libqt5gui5:amd64 (5.3.1+dfsg-2, 5.3.1+dfsg-3), libopencv-
contrib2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1), libqt5network5:amd64
(5.3.1+dfsg-2, 5.3.1+dfsg-3), libtasn1-6:amd64 (3.7-1, 4.0-2), glib-networking-
services:amd64 (2.40.1-1, 2.40.1-2), libptexenc1:amd64
(2014.20140528.34243-3+b1, 2014.20140528.34243-4), glib-networking:amd64
(2.40.1-1, 2.40.1-2), libopencv-flann2.4:amd64 (2.4.8+dfsg1-2.2, 2.4.9+dfsg-1),
libpython2.7-minimal:amd64 (2.7.7-2, 2.7.8-1), qtbase5-dev:amd64 (5.3.1+dfsg-2,
5.3.1+dfsg-3), libsamplerate0:amd64 (0.1.8-7, 0.1.8-8), libtasn1-6-dev:amd64
(3.7-1, 4.0-2)
Remove: libgnutls-dev:amd64 (2.12.23-17)
End-Date: 2014-07-05  21:42:47
--
However, Tk applications no lo

Processed: severity of 754162 is serious, merging 754157 754162

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 754162 serious
Bug #754162 [gnuplot] gnuplot: trying to overwrite file from gnuplot-x11 4.6.5-4
Severity set to 'serious' from 'normal'
> merge 754157 754162
Bug #754157 [gnuplot] gnuplot: file conflict with gnuplot-x11
Bug #754162 [gnuplot] gnuplot: trying to overwrite file from gnuplot-x11 4.6.5-4
Merged 754157 754162
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
754157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754157
754162: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#329192: sortof fixed upstream

[David Bremner]

According to NEWS:

nullmailer 1.12 adds a quadratic backoff for resend times.

Would people consider this a fix?

d


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

Bug#746589: [kdm] Time to Get on With This!

[d_baron]

This is apparently no widely reported--otherwise the hue-and-cry across 
Debian-KDE-land would be deafening :-)

What do I and the original reporter have in common? We both started out with a 
relatively recent Debian installer, he 7.4, I  7.5. And then, we both wanted to 
upgrade it. Bingo.

I do not know how he set his up but I used a multi-partition install and not 
wanting one-big-physical-partition, did not use LVM (probably an error!). 
Unfortunately, the Debian installer does not let me set this up the way I would 
want to do so. Throws 90% of the space to home and gives small partitions for 
everything else. So ...

/usr has little room for expansion. May rbind or symlink /usr/local off on that 
oversized /home or another platter. I remember doing all kinds of tricks like 
this when I had all of Debian on an 8gig partition. With one terra, I though 
all this stuff was behind me!

/opt -- no room for this at all. So ... same trick.

These have little to do with KDE, however. What about /var? This partition 
begins to fill up, with emails, with logs, etc., until it is pretty darned 
full. I have had the email system grind to a halt because humongous logs 
filling the /var partition. KDE still functioned, however. That was KDE3.

So, did the original reporter have separate partitions by the installer? How 
long before the issue started showing up? How much free space (if there be any 
minimum) does KDE require to log in and start the session? Problem is the /var 
has loads of smaller stuff. My one choice would be to symlink or rbind 
/var/mail (presently 40meg, too big, this may be in error due to kmail as well).

Cheap enough to try but would like some input here before.
‭‮

Bug#754171: sogo: build dependencies uninstallable

[Emilio Pozuelo Monfort]

Source: sogo
Version: 2.2.5-1
Severity: serious

Your package can't be rebuilt because the build dependencies are
uninstallable:

sogo build-depends on:
- liblasso3-dev
liblasso3-dev depends on:
- libxmlsec1-dev
libxmlsec1-dev depends on:
- libgnutls28-dev
sogo build-depends on:
- libgnutls-dev
libgnutls28-dev conflicts with:
- --virtual-gnutls-dev

Switching sogo from libgnutls-dev to libgnutls28-dev should probably
fix this.

Emilio


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

Bug#752944: marked as done (ruby-webmock: FTBFS - 210 tests failing)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jul 2014 11:34:06 +
with message-id 
and subject line Bug#752944: fixed in ruby-webmock 1.18.0-1
has caused the Debian Bug report #752944,
regarding ruby-webmock: FTBFS - 210 tests failing
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
752944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752944
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-webmock
Version: 1.17.4-2
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
Running tests for ruby2.1 using debian/ruby-tests.rake ...
/usr/bin/ruby2.1 -S rspec spec/acceptance/curb/curb_spec.rb 
spec/acceptance/em_http_request/em_http_request_spec.rb 
spec/acceptance/excon/excon_spec.rb spec/acceptance/http_gem/http_gem_spec.rb 
spec/acceptance/httpclient/httpclient_spec.rb 
spec/acceptance/net_http/net_http_spec.rb 
spec/acceptance/net_http/real_net_http_spec.rb 
spec/acceptance/typhoeus/typhoeus_hydra_spec.rb spec/quality_spec.rb 
spec/unit/api_spec.rb spec/unit/errors_spec.rb 
spec/unit/http_lib_adapters/http_lib_adapter_registry_spec.rb 
spec/unit/http_lib_adapters/http_lib_adapter_spec.rb 
spec/unit/matchers/hash_including_matcher_spec.rb 
spec/unit/rack_response_spec.rb spec/unit/request_execution_verifier_spec.rb 
spec/unit/request_pattern_spec.rb spec/unit/request_registry_spec.rb 
spec/unit/request_signature_spec.rb spec/unit/request_stub_spec.rb 
spec/unit/response_spec.rb spec/unit/stub_registry_spec.rb 
spec/unit/stub_request_snippet_spec.rb spec/unit/util/hash_counter_spec.rb 
spec/unit/util/hash_keys_stringifier_spec.rb spec/unit/util/headers_spec.rb 
spec/unit/util/json_spec.rb spec/unit/util/query_mapper_spec.rb 
spec/unit/util/uri_spec.rb spec/unit/util/version_checker_spec.rb 
spec/unit/webmock_spec.rb -c -f progress -r ./spec/spec_helper.rb
Run options:
  include {:focus=>true}
  exclude {:without_webmock=>true}

All examples were filtered out; ignoring {:focus=>true}
[...]
Failures:

  1) HTTP Gem with WebMock allows a response with multiple values for the same 
header to be recorded and played back exactly as-is
 Failure/Error: real_response = http_request(:get, webmock_server_url)
 NoMethodError:
   undefined method `response' for #
 # ./spec/acceptance/http_gem/http_gem_spec_helper.rb:7:in `http_request'
 # ./spec/acceptance/shared/complex_cross_concern_behaviors.rb:7:in `block 
(2 levels) in '


(and 209 further failures follow)


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.

Best,
Michael


ruby-webmock-build-log.txt.gz
Description: application/gunzip


pgpB3ysf0TBK1.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-webmock
Source-Version: 1.18.0-1

We believe that the bug you reported is fixed in the latest version of
ruby-webmock, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 752...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-webmock package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Jul 2014 13:21:22 +0200
Source: ruby-webmock
Binary: ruby-webmock
Architecture: source all
Version: 1.18.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Description:
 ruby-webmock - library for stubbing HTTP requests in Ruby
Closes: 752944
Changes:
 ruby-webmock (1.18.0-1) unstable; urgency=medium
 .
   * Team upload
   * Imported Upstream version 1.18.0
 - now compatible with ruby-http >= 0.6.0, which fixes
   the failure to build from source (Closes: #752944)
Checksums-Sha1:
 e84394d1e9832d43ec2b3f20b698798562c71a0f 2360 ruby-webmock_1.18.0-1.dsc
 0808cf907f9c5d37074a7afd6e5132443a081227 92724 ruby-webmock_1.18.0.orig.tar.gz
 4a4832cfb9a0791abc79046fa54ae1409b7737d1 4640 
ruby-webmock_1.18.0-1.debian.tar.xz
 58b386a672e0924805c69a42b22ce5b45644f921 41020 ruby-webmock_1.18.0-1_all.deb
Checks

Bug#754176: stumpwm: Startup script fails if user has no ~/.stumpwmrc.

[Emilio Lopes]

Package: stumpwm
Version: 2:0.9.8-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I've just installed stumpwm and typed `stumpwm' (without the quotes)
on a terminal to start the window manager.  I've got a error message
from `grep':

   grep: /home/lopes/.stumpwmrc: No such file or directory

Creating an empty file (using `touch') "solved" the problem.

Thank you for your time.

 Emilio

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

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

Versions of packages stumpwm depends on:
ii  cl-ppcre  2.0.3-1
ii  clisp-module-clx  1:2.49-8.2

Versions of packages stumpwm recommends:
ii  cl-asdf  2:3.0.3-1

Versions of packages stumpwm suggests:
ii  iceweasel [www-browser]  30.0-2
ii  info [info-browser]  5.2.0.dfsg.1-4
ii  menu 2.1.47
ii  rlwrap   0.37-5
pn  slime
ii  w3m [www-browser]0.5.3-16
ii  x11-utils7.7+1
ii  xterm [x-terminal-emulator]  308-1

-- no debconf information


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

Bug#754177: stumpwm does not work if `cl-asdf' is not installed.

[Emilio Lopes]

Package: stumpwm
Version: 2:0.9.8-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

after installing `stumpwm' I could not start the window manager.  There
was some error message mentioning `asdf', which was *not* installed.

Note that `cl-asdf' is not `required' by `stumpwm', just `recommended'.

After `cl-asdf' was installed, I could start `stumpwm' as expected.

Thank you for your time!

 Emilio

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

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

Versions of packages stumpwm depends on:
ii  cl-ppcre  2.0.3-1
ii  clisp-module-clx  1:2.49-8.2

Versions of packages stumpwm recommends:
ii  cl-asdf  2:3.0.3-1

Versions of packages stumpwm suggests:
ii  iceweasel [www-browser]  30.0-2
ii  info [info-browser]  5.2.0.dfsg.1-4
ii  menu 2.1.47
ii  rlwrap   0.37-5
pn  slime
ii  w3m [www-browser]0.5.3-16
ii  x11-utils7.7+1
ii  xterm [x-terminal-emulator]  308-1

-- no debconf information


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

Bug#747777: marked as done (nqp: FTBFS: error: no previous prototype for 'dcGetErrorString')

[Debian Bug Tracking System]

Your message dated Tue, 08 Jul 2014 12:18:40 +
with message-id 
and subject line Bug#74: fixed in nqp 2014.04-1
has caused the Debian Bug report #74,
regarding nqp: FTBFS: error: no previous prototype for 'dcGetErrorString'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
74: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=74
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nqp
Version: 2014.03-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140510 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):
> gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
> -Werror=format-security -D_FORTIFY_SOURCE=2 -DHASATTRIBUTE_CONST  
> -DHASATTRIBUTE_DEPRECATED  -DHASATTRIBUTE_MALLOC  -DHASATTRIBUTE_NONNULL  
> -DHASATTRIBUTE_NORETURN  -DHASATTRIBUTE_PURE  -DHASATTRIBUTE_UNUSED  
> -DHASATTRIBUTE_WARN_UNUSED_RESULT  -DHASATTRIBUTE_HOT  -DHASATTRIBUTE_COLD  
> -DHAS_GETTEXT -fPIC -g -falign-functions=16 -funit-at-a-time 
> -fexcess-precision=standard -maccumulate-outgoing-args -Wall -Wextra 
> -Waggregate-return -Wcast-qual -Wdisabled-optimization -Wdiv-by-zero 
> -Wendif-labels -Wformat-extra-args -Wformat-nonliteral -Wformat-security 
> -Wformat-y2k -Wimplicit -Wimport -Winit-self -Winline -Winvalid-pch 
> -Wjump-misses-init -Wlogical-op -Werror=missing-braces 
> -Werror=missing-declarations -Wno-missing-format-attribute 
> -Wmissing-include-dirs -Wmultichar -Wpacked -Wpointer-arith -Wreturn-type 
> -Wsequence-point -Wsign-compare -Wstrict-aliasing -Wstrict-aliasing=2 
> -Wswitch -Wswitch-default -Werror=undef -Wno-unused -Wvariadic-macros 
> -Wwrite-strings -Wstack-usage=500 -Wc++-compat 
> -Werror=declaration-after-statement -Werror=implicit-function-declaration 
> -Werror=missing-prototypes -Werror=nested-externs 
> -Werror=old-style-definition -Werror=strict-prototypes -fvisibility=hidden   
> -Wno-strict-prototypes -O3 -fPIC -O3 -fPIC -D_FORTIFY_SOURCE=2  -c 
> dyncall_api.c -o dyncall_api.o
> dyncall_api.c:159:13: error: no previous prototype for 'dcGetErrorString' 
> [-Werror=missing-prototypes]
>  const char* dcGetErrorString(int mode)
>  ^
> cc1: some warnings being treated as errors
> make[4]: *** [dyncall_api.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/05/10/nqp_2014.03-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.
--- End Message ---
--- Begin Message ---
Source: nqp
Source-Version: 2014.04-1

We believe that the bug you reported is fixed in the latest version of
nqp, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 747...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dominique Dumont  (supplier of updated nqp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 08 Jul 2014 13:21:49 +0200
Source: nqp
Binary: nqp
Architecture: source amd64
Version: 2014.04-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rakudo Maintainers 
Changed-By: Dominique Dumont 
Description:
 nqp- Not Quite Perl compiler
Closes: 74 749499
Changes:
 nqp (2014.04-1) unstable; urgency=medium
 .
   * Imported Upstream version 2014.04
   * added patch to fix missing prototypes error
 (Closes: #74, #749499)
Checksums-Sha1:
 f1ce37f654656cf006ad810cadb5c8ba34b5404d 1947 nqp_2014.04-1.dsc
 24d3d73f4aa612e08e6ab8ce7d538f7b1312fff2 5062515 nqp_2014.04.orig.tar.gz
 53f912f1ae07fb430ac26c2a09cb286facccb4c2 9356 nqp_2014.04-1.debian.tar.xz
 3e65f03d2bbb271471a3c6fc176ca0836cd92451 758580 nqp_2014.04-1_amd64.deb
Checksums-Sha256:
 ee343e67eba7e2a3fda70920a842fd37e1c3459aef2cc325004eb65b2a8db4ef 1947 
nqp_2014.04-1.dsc
 2ca01646f0f28c3608ecd62

Bug#749499: marked as done (nqp: uninstallable in sid)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jul 2014 12:18:40 +
with message-id 
and subject line Bug#749499: fixed in nqp 2014.04-1
has caused the Debian Bug report #749499,
regarding nqp: uninstallable in sid
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
749499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nqp
Version: 2014.03-1
Severity: serious
Tags: jessie sid

Hi,

nqp depends on parrotapi-6.0.0 which is not found in sid.

Only parrotapi-6.3.0 seems to be available, provided by parrot-minimal.

Thanks.

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

Kernel: kFreeBSD 9.0-2-amd64-xenhvm
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: nqp
Source-Version: 2014.04-1

We believe that the bug you reported is fixed in the latest version of
nqp, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 749...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dominique Dumont  (supplier of updated nqp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 08 Jul 2014 13:21:49 +0200
Source: nqp
Binary: nqp
Architecture: source amd64
Version: 2014.04-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rakudo Maintainers 
Changed-By: Dominique Dumont 
Description:
 nqp- Not Quite Perl compiler
Closes: 74 749499
Changes:
 nqp (2014.04-1) unstable; urgency=medium
 .
   * Imported Upstream version 2014.04
   * added patch to fix missing prototypes error
 (Closes: #74, #749499)
Checksums-Sha1:
 f1ce37f654656cf006ad810cadb5c8ba34b5404d 1947 nqp_2014.04-1.dsc
 24d3d73f4aa612e08e6ab8ce7d538f7b1312fff2 5062515 nqp_2014.04.orig.tar.gz
 53f912f1ae07fb430ac26c2a09cb286facccb4c2 9356 nqp_2014.04-1.debian.tar.xz
 3e65f03d2bbb271471a3c6fc176ca0836cd92451 758580 nqp_2014.04-1_amd64.deb
Checksums-Sha256:
 ee343e67eba7e2a3fda70920a842fd37e1c3459aef2cc325004eb65b2a8db4ef 1947 
nqp_2014.04-1.dsc
 2ca01646f0f28c3608ecd62dd2127a69b46f99b9949a1a7801f9136bbceb9395 5062515 
nqp_2014.04.orig.tar.gz
 5461465e56d92db347d76ba59636e4686e7e48fd4cc4eac5e3be1ec23514f8e0 9356 
nqp_2014.04-1.debian.tar.xz
 f7b4f14cd72ebfe9f67d3905fc6a7331372fab4d938d692f45fcce739edeaaf7 758580 
nqp_2014.04-1_amd64.deb
Files:
 6d4724335e61fbfa4da6a1f2ba5bfd02 758580 interpreters optional 
nqp_2014.04-1_amd64.deb
 f1089f8af8a827a927727590c6692560 1947 interpreters optional nqp_2014.04-1.dsc
 9a7b8448720713c968338e93e1f0c984 5062515 interpreters optional 
nqp_2014.04.orig.tar.gz
 0513bd0ee536e903d5fed9b56709f844 9356 interpreters optional 
nqp_2014.04-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJTu9v0AAoJEMMfT9lJqyts6UQP/0ye+Y763VlAGnsFW36rGCVZ
iOmnv81Ct5+mf0SYQDB1b4tTCTE93CuUIzutAoEk2nSq8BB76VLSJl23SX9vDO4z
StaHOpZ3sKF+APr8fCqnBqEzj9Sn73uk5zZFirPZlx49l9Rdyioge2FQikeWMXoQ
hetbH/JdK3lujsj68/38ygnLHALtYczrt0uZRuEtv1drG5Z/uYdHEBs8r6nO+1el
EJxuAlYil/VL4ESutjoZN/DeiTc8Mti1ujIVdCQQNaMJRANuu2iS/2LILVyyipxM
c1tRvlCW5mQgf4mOAn2frLSNKFVA6UbPLGSDdFnOmRyVj/r2pRC5mtKmMrNUbcVP
tF41UWoJamzw/tqHV4d3IHYMHERXmfH2UBfwUU/5r/VbwM3ExA4OkIJHd+eAhz+m
LaLsC5AjXc4FCOfsXuy6juE2LpHDTWiHcjyJcz5oOMao29zEOJeJTMKh+UCMjYR9
Z/Bp1rskWPL/SJiyEUZpBCQU2prxzIKsqQcBndsUy0yLfGptuOZz8RvwsZwaJLO6
YFfREC9Mi25ht2VX78q9BBeL3+slsfRAKfcmHN/TuWalVCpCecjCLMjCTjUVh41F
/hCGeWUIyz0qe95fDaGYK4kcyu1bxz5eHVVYuksVE7b+6v5bZhM2vRCUoVfHZmyq
b6seRJ1odX+JLAvanBD+
=FMe+
-END PGP SIGNATURE End Message ---

Bug#754182: chromium-browser: FTBFS on amd64

[Bill Allombert]

Package: chromium-browser
Version: 35.0.1916.153-2
Severity: serious

Hello Debian Chromium Maintainers,

chromium-browser FTBFS on amd64.

The full buildlog is available at


The error message is

chrome/renderer/pepper/pepper_pdf_host.cc:16:33: fatal error: 
grit/webkit_strings.h: No such file or directory
 #include "grit/webkit_strings.h"
 ^
compilation terminated.
chrome/renderer.target.mk:469: recipe for target 
'out/Release/obj.target/renderer/chrome/renderer/pepper/pepper_pdf_host.o' 
failed
make[1]: *** 
[out/Release/obj.target/renderer/chrome/renderer/pepper/pepper_pdf_host.o] 
Error 1
make[1]: Leaving directory '/tmp/buildd/chromium-browser-35.0.1916.153/src'
/usr/share/cdbs/1/class/makefile.mk:47: recipe for target 
'debian/stamp-makefile-build' failed
make: *** [debian/stamp-makefile-build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
E: Failed autobuilding of package

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


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

Bug#753913: irssi: unable to connect to any server

[Gerfried Fuchs]

severity 753913 normal
tag 753913 + moreinfo unreproducible
thanks

* Ian Zimmerman  [2014-07-06 08:34:36 CEST]:
> Trying to connect to any server whatsoever, I get this:
> 
> 23:30 -!- Irssi: Looking up chat.freenode.net
> 23:30 -!- Irssi: Connecting to chat.freenode.net [195.148.124.79] port 6667
> 23:30 -!- Irssi: Unable to connect server chat.freenode.net port 6667 
> [Invalid argument]

 Works for me, and seemingly for lots of other people too.  If you say
"any server whatsoever", what ones did you try, and on which ports?

> Here is the relevant piece of strace log:
> 
> socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 4
> fcntl(4, F_SETFL, O_RDONLY|O_NONBLOCK)  = 0
> setsockopt(4, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
> setsockopt(4, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
> bind(4, {sa_family=AF_INET, sin_port=htons(0), 
> sin_addr=inet_addr("127.0.1.1")}, 16) = 0
> connect(4, {sa_family=AF_INET, sin_port=htons(6667), 
> sin_addr=inet_addr("82.96.64.4")}, 16) = -1 EINVAL (Invalid argument)

 Does networking work on that machine for you at all?  Do you have any
specific port filters/blocking?  Did you try other ports beside 6667?
Like, freenode supports port 8000 too.

 Thanks for any further information you can offer,
Rhonda
-- 
Fühlst du dich mutlos, fass endlich Mut, los  |
Fühlst du dich hilflos, geh raus und hilf, los| Wir sind Helden
Fühlst du dich machtlos, geh raus und mach, los   | 23.55: Alles auf Anfang
Fühlst du dich haltlos, such Halt und lass los|


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

Processed: Re: Bug#753913: irssi: unable to connect to any server

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 753913 normal
Bug #753913 [irssi] irssi: unable to connect to any server
Severity set to 'normal' from 'grave'
> tag 753913 + moreinfo unreproducible
Bug #753913 [irssi] irssi: unable to connect to any server
Added tag(s) unreproducible and moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
753913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753913
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#753705: conky: FTBFS with audacious 3.5: libaudclient removed

[Colin Watson]

On Sat, Jul 05, 2014 at 07:54:43PM -0700, Vincent Cheng wrote:
> On Fri, Jul 4, 2014 at 6:20 AM, Colin Watson  wrote:
> > conky fails to build with audacious 3.5-1 in unstable:
> >
> >   configure: error: Package requirements (audacious >= 1.4.0 audclient 
> > dbus-glib-1 glib-2.0 gobject-2.0) were not met:
> >
> >   No package 'audclient' found
> >
> > http://audacious-media-player.org/news/27-audacious-3-5-released says
> > that libaudclient has been removed upstream, apparently in favour of
> > newer GDBus-based code.  Perhaps it's possible to adapt conky to that?
> 
> Thanks for the bug report!
> 
> It looks like upstream hasn't done any porting work to drop
> libaudclient, and nobody else has done so either; e.g. Fedora has gone
> ahead and just dropped audacious support [1], so I plan on doing the
> same thing soon unless someone steps up with a patch.

Thanks.  That sounds reasonable - please do.

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


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

Bug#753192: marked as done (mesa-demos: FTBFS: drawtex.c:34: undefined reference to `glDrawTexfOES')

[Debian Bug Tracking System]

Your message dated Tue, 08 Jul 2014 13:19:39 +
with message-id 
and subject line Bug#753192: fixed in mesa-demos 8.2.0-1
has caused the Debian Bug report #753192,
regarding mesa-demos: FTBFS: drawtex.c:34: undefined reference to 
`glDrawTexfOES'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
753192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753192
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mesa-demos
Version: 8.1.0-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140628 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):
> gcc -DPACKAGE_NAME=\"mesa-demos\" -DPACKAGE_TARNAME=\"mesa-demos\" 
> -DPACKAGE_VERSION=\"8.1.0\" -DPACKAGE_STRING=\"mesa-demos\ 8.1.0\" 
> -DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi\?product=Mesa\&component=Demos\";
>  -DPACKAGE_URL=\"\" -DPACKAGE=\"mesa-demos\" -DVERSION=\"8.1.0\" 
> -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 
> -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 
> -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" 
> -DDEMOS_DATA_DIR=\"../data/\" -DDEMOS_DATA_DIR=\"../data/\" -I.   
> -D_FORTIFY_SOURCE=2  -I/usr/include/libdrm   -I../../../src/egl/eglut -g -O2 
> -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
> -c -o drawtex.o drawtex.c
> /bin/bash ../../../libtool  --tag=CC   --mode=link gcc  -I/usr/include/libdrm 
>   -I../../../src/egl/eglut -g -O2 -fstack-protector --param=ssp-buffer-size=4 
> -Wformat -Werror=format-security -lGLESv1_CM  -lEGL  -lm -Wl,-z,relro -o 
> drawtex_screen drawtex.o ../eglut/libeglut_screen.la 
> libtool: link: gcc -I/usr/include/libdrm -I../../../src/egl/eglut -g -O2 
> -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
> -Wl,-z -Wl,relro -o drawtex_screen drawtex.o  -lGLESv1_CM -lm 
> ../eglut/.libs/libeglut_screen.a -lEGL
> drawtex.o: In function `draw':
> /«PKGBUILDDIR»/src/egl/opengles1/drawtex.c:34: undefined reference to 
> `glDrawTexfOES'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/06/28/mesa-demos_8.1.0-2_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.
--- End Message ---
--- Begin Message ---
Source: mesa-demos
Source-Version: 8.2.0-1

We believe that the bug you reported is fixed in the latest version of
mesa-demos, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 753...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated mesa-demos package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 08 Jul 2014 15:00:10 +0200
Source: mesa-demos
Binary: mesa-utils mesa-utils-extra
Architecture: source amd64
Version: 8.2.0-1
Distribution: sid
Urgency: high
Maintainer: Debian X Strike Force 
Changed-By: Julien Cristau 
Description:
 mesa-utils - Miscellaneous Mesa GL utilities
 mesa-utils-extra - Miscellaneous Mesa utilies (opengles, egl)
Closes: 753192
Changes:
 mesa-demos (8.2.0-1) unstable; urgency=high
 .
   [ Andreas Boll ]
   * New upstream release.
 - drawtex: resolve glDrawTexfOES extension function (Closes: #753192).
 .
   [ Julien Cristau ]
   * Add pgpsigurlmangle option to debian/watch, and add
 debian/upstream/signing-key.asc to let uscan verify tarball sigs.
   * High urgency upload for RC bug fix.
Checksums-Sha1:
 1af61d524cce013049486f9279aed1954b8f5230 2217 mesa-demos_8.2.0-1.dsc
 d15728d32d5cc6078decbac7f425dc8ee81a8e12 11759868 mesa-demos_8.2.0.orig.tar.gz
 fdd7797cb5e28d2a185eb5995c383ddb445e76b8 87177 mesa-demos_8.2.0-1.diff.gz
 e1a2f89ea85ed376ede9

Bug#753699: lynx: Alert!: This client does not contain support for HTTPS URLs.

[Thorsten Glaser]

Atsuhito Kohda dixit:

>it seems lynx works fine so I uploaded the package.  

Yes, this seems to work better now. Thank you.

bye,
//mirabilos
-- 
(gnutls can also be used, but if you are compiling lynx for your own use,
there is no reason to consider using that package)
-- Thomas E. Dickey on the Lynx mailing list, about OpenSSL


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

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 747548 + pending
Bug #747548 [python-gamera] python-gamera: memory leak
Added tag(s) pending.
> tag 629177 + pending
Bug #629177 [wnpp] ITA: gamera -- framework for building document analysis
Added tag(s) pending.
> tag 736004 + pending
Bug #736004 [src:gamera] please build-depend on libtiff-dev, not libtiff4-dev
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
629177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629177
736004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736004
747548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Processed: librime: FTBFS on armel: std::future is broken

[Debian Bug Tracking System]

Processing control commands:

> block 753079 by -1
Bug #753079 [release.debian.org] transition: librime
753079 was not blocked by any bugs.
753079 was not blocking any bugs.
Added blocking bug(s) of 753079: 754199

-- 
753079: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753079
754199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#753993: lyx: SIGSEGV when saving a new LyX file resulting in data loss

[Ben Goodrich]

After doing a reconfigure under the Tools menu, I am no longer able to
reproduce either issue, so you probably should downgrade the severity of
the bug report. Possibly the issue would go away on the next LyX upload.

Thanks,
Ben

Bug#754199: librime: FTBFS on armel: std::future is broken

[Emilio Pozuelo Monfort]

Source: librime
Severity: serious
Control: block 753079 by -1

librime failed to build on armel because of the std::future brokenness on
that platform, see #727621.

https://buildd.debian.org/status/fetch.php?pkg=librime&arch=armel&ver=1.1%2Bdfsg-2&stamp=1404754412

This is blocking the librime transition.

Emilio


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

Bug#754201: Potential SQL injection in the ORDER implementation of Zend_Db_Select (ZF2014-04)

[David Prévot]

Package: zendframework
Version: 1.12.5-0.1
Severity: grave
Tags: security upstream patch

Affected versions: v1.12.0 up to v1.12.6 (Squeeze and Wheezy are not
affected)
Upstream security issue:
http://framework.zend.com/security/advisory/ZF2014-04
Upstream patch:

https://github.com/zendframework/zf1/commit/da09186c60b9168520e994af4253fba9c19c2b3d

Regards

David


signature.asc
Description: Digital signature

Processed: limit source to zendframework, tagging 754201

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source zendframework
Limiting to bugs with field 'source' containing at least one of 'zendframework'
Limit currently set to 'source':'zendframework'

> tags 754201 + pending
Bug #754201 [zendframework] Potential SQL injection in the ORDER implementation 
of Zend_Db_Select (ZF2014-04)
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
754201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Processed: Re: Bug#754199: librime: FTBFS on armel: std::future is broken

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 754199 by 727621
Bug #754199 [src:librime] librime: FTBFS on armel: std::future is broken
754199 was not blocked by any bugs.
754199 was blocking: 753079
Added blocking bug(s) of 754199: 727621
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
754199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#753963: [gsoap] Some sources are not included in your package

[Mattias Ellert]

sön 2014-07-06 klockan 19:14 + skrev bastien ROUCARIES:
> Package: gsoap
> Version: 2.8.16-3
> user: lintian-ma...@debian.org
> usertags: source-is-missing
> severity: serious
> X-Debbugs-CC: ftpmas...@debian.org
> 
> Hi,
> 
> Your package seems to include some files that lack sources
> in prefered forms of modification:
> 
> gsoap/bin/linux386/soapcpp2
> gsoap/bin/linux386/wsdl2h
> gsoap/doc/dom/html/jquery.js
> gsoap/doc/httpda/html/jquery.js
> gsoap/doc/wsa/html/jquery.js
> gsoap/doc/wsdd/html/jquery.js
> gsoap/doc/wsrm/html/jquery.js
> gsoap/doc/wsse/html/jquery.js
> gsoap/doc/xml-rpc-json/html/jquery.js
> gsoap/samples/databinding/html/jquery.js
> 
> You override this warning using this file:
> # These binaries are not used during the build nor are they packaged
> source-is-missing gsoap/bin/linux386/*
> # These bundled copies of jquery.js are replaced by symlinks during the build
> source-is-missing gsoap/doc/*/html/jquery.js
> source-is-missing gsoap/samples/databinding/html/jquery.js

The code for precompiled binaries in upstream's distribution are in the
sources. If they were not it would not be possible to compile the
version of the binaries that are installed from the sources.

The source for soapcpp2 is ./gsoap/src
The source for wsdl2h is ./gsoap/wsdl

So the sources are not missing.

Regarding the jquery.js files I am not sure what to say. These jquery.js
files are part of doxygen generated documentation that is pre-generated
by upstream and included in their source distribution.

When lintian started to complain about the presence of the jquery.js
files in the documentation I made lintian no longer complain about that
by replacing them with symlinks to debian's system version. This of
course only works if the debian system jquery.js is compatible with the
jquery.js that doxygen provides as part if the documentation it
generates. I have since then found that this is not the case and that
replacing the doxygen jquery.js with debian's version is a broken
solution to the problem.

The /usr/share/doc/doxygen/README.jquery file says a lot of things, but
ends with:

"It is not considered a problem for Doxygen or packages using Doxygen to
embed jquery. In fact replacing the `jquery.js` file created by Doxygen
likely results in broken documentation. Packages doing that are buggy.
Lintian will have to learn that a `jquery.js` embedded by Doxygen is a
normal thing."

So in order to implement the recommendations from the doxygen maintainer
I should revert my attempt to make lintian happy by replacing the
jquery.js with a symlink.

The jquery.js that is part of the documentation is the one that is
embedded in the doxygen binary on the computer that is generating the
documentation. So this will either be the copy of doxygen that is
installed on the upstream developer's machine when the documentation is
generated (in case the doxygen generated documentation is pre-generated
and part of the sources) or the copy of doxygen in the package build
root (in case the doxygen documentation is generated or regenerated as
part of the build).

The source of this jquery.js file will never be part of the source
package of the package that installs it. It will always come from an
embedded copy inside doxygen which, at least at present, can not be
replaced by the debian system version.

Do the ftp-masters as a collective have a consensus point of view on
doxygen generated documentation? Is packaging of pre-generated
documentation that is part of upstream's sources acceptable, or must all
doxygen generated documentation be regenerated as part of the package
build? If packaging of pre-generated documentation is allowed, then
having jsquery.js files in the source tarball must be allowed. If all
copies of jquery.js must be purged from all source tarballs this means
the all pre-generated doxygen documentation is banned.

Mattias



smime.p7s
Description: S/MIME cryptographic signature

Bug#754205: poedit: When updating the catalog I get the alert 'An assertion failed'

[Henri Schumacher]

Package: poedit
Version: 1.5.4-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?
Updating the catalog from PHP sources.
* What was the outcome of this action?
Getting an alert 'An assertion failed' with following content:

ASSERT INFO:
/usr/include/wx-3.0/wx/strvararg.h(456): assert "(argtype &
(wxFormatStringSpecifier::value)) == argtype" failed in wxArgNormalizer():
format specifier doesn't match argument type

BACKTRACE:
[1] wxFileName::~wxFileName()
[2] wxFormatString::~wxFormatString()
[3] wxFormatString::~wxFormatString()
[4] wxSizer::Add(wxWindow*, int, int, int, wxObject*)
[5] wxSizer::Add(wxWindow*, int, int, int, wxObject*)
[6] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&,
wxEvent&) const
[7] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&,
wxEvtHandler*, wxEvent&)
[8] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[9] wxEvtHandler::TryHereOnly(wxEvent&)
[10] wxEvtHandler::ProcessEventLocally(wxEvent&)
[11] wxEvtHandler::ProcessEvent(wxEvent&)
[12] wxWindowBase::TryAfter(wxEvent&)
[13] wxEvtHandler::SafelyProcessEvent(wxEvent&)
[14] wxToolBarBase::OnLeftClick(int, bool)
[15] g_signal_emit_valist
[16] g_signal_emit_by_name
[17] g_signal_emit_valist
[18] g_signal_emit
[19] g_closure_invoke
[20] g_signal_emit_valist
[21] g_signal_emit
[22] g_closure_invoke
[23] g_signal_emit_valist
[24] g_signal_emit
[25] gtk_propagate_event
[26] gtk_main_do_event
[27] g_main_context_dispatch
[28] g_main_loop_run
[29] gtk_main
[30] wxGUIEventLoop::DoRun()
[31] wxEventLoopBase::Run()
[32] wxAppConsoleBase::MainLoop()
[33] wxEntry(int&, wchar_t**)
[34] __libc_start_main


   * What outcome did you expect instead?
Updating the PO catalog:



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

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

Versions of packages poedit depends on:
ii  gettext  0.18.3.2-3
ii  libatk1.0-0  2.12.0-1
ii  libc62.19-4
ii  libcairo21.12.16-2
ii  libdb5.3++   5.3.28-5
ii  libfontconfig1   2.11.0-5
ii  libfreetype6 2.5.2-1
ii  libgcc1  1:4.9.0-7
ii  libgdk-pixbuf2.0-0   2.30.7-1
ii  libglib2.0-0 2.40.0-3
ii  libgtk2.0-0  2.24.24-1
ii  libgtkspell0 2.0.16-1
ii  libpango-1.0-0   1.36.3-1
ii  libpangocairo-1.0-0  1.36.3-1
ii  libpangoft2-1.0-01.36.3-1
ii  libstdc++6   4.9.0-7
ii  libwxbase3.0-0   3.0.1-2
ii  libwxgtk3.0-03.0.1-2

poedit recommends no packages.

poedit suggests no packages.

-- no debconf information


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

Bug#754171: marked as done (sogo: build dependencies uninstallable)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jul 2014 17:20:41 +
with message-id 
and subject line Bug#754171: fixed in sogo 2.2.5-2
has caused the Debian Bug report #754171,
regarding sogo: build dependencies uninstallable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
754171: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sogo
Version: 2.2.5-1
Severity: serious

Your package can't be rebuilt because the build dependencies are
uninstallable:

sogo build-depends on:
- liblasso3-dev
liblasso3-dev depends on:
- libxmlsec1-dev
libxmlsec1-dev depends on:
- libgnutls28-dev
sogo build-depends on:
- libgnutls-dev
libgnutls28-dev conflicts with:
- --virtual-gnutls-dev

Switching sogo from libgnutls-dev to libgnutls28-dev should probably
fix this.

Emilio
--- End Message ---
--- Begin Message ---
Source: sogo
Source-Version: 2.2.5-2

We believe that the bug you reported is fixed in the latest version of
sogo, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 754...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeroen Dekkers  (supplier of updated sogo package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 08 Jul 2014 14:20:53 +0200
Source: sogo
Binary: sogo sogo-common sogo-dbg sogo-openchange
Architecture: source amd64 all
Version: 2.2.5-2
Distribution: unstable
Urgency: medium
Maintainer: Jeroen Dekkers 
Changed-By: Jeroen Dekkers 
Description:
 sogo   - Scalable groupware server
 sogo-common - Scalable groupware server - common files
 sogo-dbg   - Scalable groupware server - debugging symbols
 sogo-openchange - Scalable groupware server - OpenChange backend
Closes: 754171
Changes:
 sogo (2.2.5-2) unstable; urgency=medium
 .
   * [7613c6cc] Build-depend on libgnutls28-dev. (Closes: #754171)
Checksums-Sha1:
 6a5abd72dec3f73a4b491f3477004bdd0091db87 1889 sogo_2.2.5-2.dsc
 02a1bbd2d3aa81eeb573b9ed7475de85c037fee2 15120 sogo_2.2.5-2.debian.tar.xz
 f1761eb2163dd196f9f24dfff5ef74b1f79090b7 1923556 sogo_2.2.5-2_amd64.deb
 fec6897324bc56dc3d9ab909501da88a5221216a 1678750 sogo-common_2.2.5-2_all.deb
 567c887430ff94577c402430dd520f750127bf23 4064826 sogo-dbg_2.2.5-2_amd64.deb
 4a6478aeeeb28c9d83164dc708b853ec6c98db89 1120466 
sogo-openchange_2.2.5-2_amd64.deb
Checksums-Sha256:
 17d37964a0fefc4777b0544fb97282d66b0ad546384113cac5952f81589b0107 1889 
sogo_2.2.5-2.dsc
 0b147a636f2c1d576a3608c55522f83e30a2e1c237ae2d4b7ae658dfeb736dba 15120 
sogo_2.2.5-2.debian.tar.xz
 7b841271a5dcb364ecb3afffe73890ab32c4acc3aba3a2ba46c02585585df070 1923556 
sogo_2.2.5-2_amd64.deb
 6a04bdfb50d4a954f4756de6f11e81b3d03c9202adf1f08dde765f9b3518d430 1678750 
sogo-common_2.2.5-2_all.deb
 eb9b734306fcc795d580edc435cf4272176500da96c14c41bb9464c2b9ff 4064826 
sogo-dbg_2.2.5-2_amd64.deb
 da9513599cdd704e393fd2ebffa45b7851d17f1c1badd16165fd3a8e58505e48 1120466 
sogo-openchange_2.2.5-2_amd64.deb
Files:
 753d18a1910359adbb0287599c6e5d14 1923556 mail optional sogo_2.2.5-2_amd64.deb
 30b0254d2eee1c2423d6ef22cc0049c7 1678750 mail optional 
sogo-common_2.2.5-2_all.deb
 ccacdda339bfefdc3131a7919af9a58f 4064826 debug extra sogo-dbg_2.2.5-2_amd64.deb
 c54803bfd59b814d88d31d0c16fe1631 1120466 mail optional 
sogo-openchange_2.2.5-2_amd64.deb
 6790551806ed4f1e9d74918eb2c5a48e 1889 mail optional sogo_2.2.5-2.dsc
 c6ad6527bf5680996353397af980c7ff 15120 mail optional sogo_2.2.5-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJTvCWeAAoJEDGCUpfTb5CBp7UIAKO0VMuJLDTufMXZ/GTYNlVy
Glc0bswM6hBX6M/DCpR5hRUfrxN2ODYbyFiEFwpuZtsTdQEdk5i+/kK93AiV72d7
B7b9nIlY2+hWg//2WkWMSUirDIA84q+7j8e2/OZgfoBUovwcF7yVFFHhOXT46qTD
s2Xm9dpfnEdW0rdLQzw3klpk4torAhynT3AUn4uIompqFSROE5YmbenBENuPXj9P
PFqWBARbsjWk/CjHVE2qaOLW/9ITM3dxcagMjETeCMIOpVdeoKKJzlB8Y/1AL6QB
ZOIHkHitLkO835aI/MPhr3HL9u5QCtWHEVlRSK30WTEiUxs2beuBAQNmsVP7Gmc=
=cKbV
-END PGP SIGNATURE End Message ---

Bug#753699: lynx: Alert!: This client does not contain support for HTTPS URLs.

[Andreas Metzler]

On 2014-07-08 Atsuhito Kohda  wrote:
> On Fri, 4 Jul 2014 20:09:52 +0200, Andreas Metzler wrote:

> > Looks like lynx-cur is missing a build-dependency on
> > libgcrypt20-dev as a hotfix or better use gnutls_rnd() instead of
> > gcry_randomize() and stop linking against gcrypt. (Totally untested,
> > no guarantees patch attached.)

> I only added libgcrypt20-dev to B-D and built the package, then
> it seems lynx works fine so I uploaded the package.  
> But if your patch is necessary to fix the problem properly, 
> please let me know.

Hello Atsuhito,

thanks for fixing the issue.

it is less a "necessary" than a "I think it is ugly". ;-) Afaict (but
please take this with a grain of salt) lynx is only using a single
gcrypt function, and gnutls would provide something equivalent. So by
using the gnutls function the external dependency could be avoided.
Imho this should be fixed upstream.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


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

Bug#754201: Potential SQL injection in the ORDER implementation of Zend_Db_Select (ZF2014-04)

[Salvatore Bonaccorso]

Hi David,

On Tue, Jul 08, 2014 at 12:32:11PM -0400, David Prévot wrote:
> Package: zendframework
> Version: 1.12.5-0.1
> Severity: grave
> Tags: security upstream patch
> 
> Affected versions: v1.12.0 up to v1.12.6 (Squeeze and Wheezy are not
> affected)

I have not looked in detail about the reason, but could you clarify if
this is true for wheezy and squeeze? It looks same code is present at
least in wheezy here[1].

 [1] 
http://sources.debian.net/src/zendframework/1.11.13-1.1/library/Zend/Db/Select.php#L604

Regards,
Salvatore


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

Bug#754208: uninstallable: depends on libice6

[Cyril Brulebois]

Package: libatspi0-udeb
Version: 2.12.0-1
Severity: grave
Justification: renders package unusable

Hi,

there's a new dependency, libice6, which has no udeb; your package is
therefore not installable.

Mraw,
KiBi.


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

Processed: zendframework: diff for NMU version 1.12.7-0.1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 754201 + pending
Bug #754201 [zendframework] Potential SQL injection in the ORDER implementation 
of Zend_Db_Select (ZF2014-04)
Ignoring request to alter tags of bug #754201 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
754201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#754201: Potential SQL injection in the ORDER implementation of Zend_Db_Select (ZF2014-04)

[David Prévot]

Control: found -1 1.11.13-1.1

Hi Salvatore,

> On Tue, Jul 08, 2014 at 12:32:11PM -0400, David Prévot wrote:
>> Package: zendframework
>> Version: 1.12.5-0.1

>> Affected versions: v1.12.0 up to v1.12.6 (Squeeze and Wheezy are not
>> affected)
>
> I have not looked in detail about the reason

Seems like I incorrectly trusted the following source without verifying
it, sorry about that, and thank you for your double check:

https://github.com/sensiolabs/security-advisories/commit/023c95824fc9991d1c6d56aaf54cb3cb485386b1

Regards

David


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

Processed: Re: Bug#754201: Potential SQL injection in the ORDER implementation of Zend_Db_Select (ZF2014-04)

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.11.13-1.1
Bug #754201 [zendframework] Potential SQL injection in the ORDER implementation 
of Zend_Db_Select (ZF2014-04)
Marked as found in versions zendframework/1.11.13-1.1.

-- 
754201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#754209: gambas3: FTBFS on amd64

[Bill Allombert]

Package: gambas3
Version: 3.5.2-2
Severity: serious

Hello Gambas maintainers,

gambas3 FTBFS on amd64.

The full buildlog is available at


Summary:

=== configuring in gb.jit (/tmp/buildd/gambas3-3.5.2/gb.jit)
...
checking for LLVM - version >= 3.1... ./configure: line 16991: test: 3.2: 
integer expression expected
no
configure: WARNING: gb.jit is disabled
...
||
|| THESE COMPONENTS ARE DISABLED:
|| - gb.jit
||
...
dh_install: gambas3-gb-jit missing files (usr/lib/gambas3/gb.jit.*), aborting
debian/rules:75: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 255
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Failed autobuilding of package

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


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

Bug#754212: sogo: FTBFS on powerpc and s390x: test failures

[Emilio Pozuelo Monfort]

Source: sogo
Version: 2.2.5-2
Severity: serious

Your package failed to build on powerpc and s390x (and sparc) with test
failures:

../obj/sogo-tests
2014-07-08 17:31:56.415 sogo-tests[13674] File NSBundle.m: 880. In 
+[NSBundle(Private) _addFrameworkFromClass:] Could not find framework SOGo in 
any standard location
..F2014-07-08 17:31:56.420 sogo-tests[13674] Note: Using UTF-8 as URL encoding 
in NGExtensions.
FF..F
==
FAIL: test_rendering (TestVersit.m:86)
--
string 'ELEM:NAMED2=1\,2\,3;NAMED3=text1\;text2;NAMED1=1,2,3
' elements not the same as in 
'ELEM:NAMED1=1,2,3;NAMED2=1\,2\,3;NAMED3=text1\;text2'

==
FAIL: test_stringByEscapingURL (TestNSString+URLEscaping.m:50)
--
string 'sogo+test' badly escaped: 'sogo%2Btest' (expected 'sogo+test')

==
FAIL: test_occurrenceForDate_ (TestiCalTimeZonePeriod.m:84)
--
test 0: seconds do not match: delta = -18000

==
FAIL: test_generateDataForHeaderFieldNamed_value_ 
(TestNGMimeAddressHeaderFieldGenerator.m:79)
--
received 'wolfg...@test.com,
   wolfg...@test.com' instead of '"" ' 
for '"" '

--
Ran 15 tests

FAILED (4 failures, 0 errors)
make[3]: *** [check] Error 1

See https://buildd.debian.org/status/logs.php?pkg=sogo&ver=2.2.5-2 for the
full logs.

Emilio


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

Bug#754176: marked as done (stumpwm: Startup script fails if user has no ~/.stumpwmrc.)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jul 2014 18:34:13 +
with message-id 
and subject line Bug#754176: fixed in stumpwm 2:0.9.8-4
has caused the Debian Bug report #754176,
regarding stumpwm: Startup script fails if user has no ~/.stumpwmrc.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
754176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754176
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: stumpwm
Version: 2:0.9.8-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I've just installed stumpwm and typed `stumpwm' (without the quotes)
on a terminal to start the window manager.  I've got a error message
from `grep':

   grep: /home/lopes/.stumpwmrc: No such file or directory

Creating an empty file (using `touch') "solved" the problem.

Thank you for your time.

 Emilio

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

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

Versions of packages stumpwm depends on:
ii  cl-ppcre  2.0.3-1
ii  clisp-module-clx  1:2.49-8.2

Versions of packages stumpwm recommends:
ii  cl-asdf  2:3.0.3-1

Versions of packages stumpwm suggests:
ii  iceweasel [www-browser]  30.0-2
ii  info [info-browser]  5.2.0.dfsg.1-4
ii  menu 2.1.47
ii  rlwrap   0.37-5
pn  slime
ii  w3m [www-browser]0.5.3-16
ii  x11-utils7.7+1
ii  xterm [x-terminal-emulator]  308-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: stumpwm
Source-Version: 2:0.9.8-4

We believe that the bug you reported is fixed in the latest version of
stumpwm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 754...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Milan Zamazal  (supplier of updated stumpwm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 08 Jul 2014 20:10:48 +0200
Source: stumpwm
Binary: stumpwm
Architecture: source all
Version: 2:0.9.8-4
Distribution: unstable
Urgency: low
Maintainer: Debian Common Lisp Team 

Changed-By: Milan Zamazal 
Description:
 stumpwm- tiling, keyboard driven Common Lisp window manager
Closes: 754176 754180
Changes:
 stumpwm (2:0.9.8-4) unstable; urgency=low
 .
   * Don't print errors when LISP is not set and ~/.stumpwmrc doesn't exist;
 closes: #754176.
   * Upstream version number updated; closes: #754180.
Checksums-Sha1:
 3689d042a8d92a2f1b34fac9e33765bd2f0fa5a2 1440 stumpwm_0.9.8-4.dsc
 a16eb456e7fd8657504773aac4536b029d42a6eb 97024 stumpwm_0.9.8-4.debian.tar.xz
 e00a277029f6dbef2719bd98b1eb6e3dfff66eb4 290368 stumpwm_0.9.8-4_all.deb
Checksums-Sha256:
 8a4578475aac6d055e0f73ebb9c2f281ce0210b8be944e4db1489cc11e1afd00 1440 
stumpwm_0.9.8-4.dsc
 54c7b2fa5e32fd6fbf76f241eb014e63cea2956d8c5e44f5c1da46a68264a945 97024 
stumpwm_0.9.8-4.debian.tar.xz
 7e8c5b3c200103ee444a83ec394e83fbb07012ab5a8813b3bc0438f5e1ced045 290368 
stumpwm_0.9.8-4_all.deb
Files:
 55652c6460030dff92f14ce8993e4529 290368 x11 optional stumpwm_0.9.8-4_all.deb
 b0b43631408fdca00974d90cdf9e07ac 1440 x11 optional stumpwm_0.9.8-4.dsc
 46719d0b88175bb614fe4b8caa28dde0 97024 x11 optional 
stumpwm_0.9.8-4.debian.tar.xz

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

iEYEARECAAYFAlO8NvwACgkQkSkk/j3Cm0FDaACg2cc229VJPI8Gh1yZKtWkEdgI
qNkAnjLMtiH+5v5WOEA90Rv5Sm2xluPk
=9dCK
-END PGP SIGNATURE End Message ---

Bug#754214: openjdk-7: FTBFS on kfreebsd-*

[Steven Chamberlain]

Package: src:openjdk-7
Version: 7u60-2.5.0-1
Severity: serious
User: debian-...@lists.debian.org
Usertags: kfreebsd

Hi,

Upstream openjdk-7 has introduced a large patchset supporting IBM AIX.
There's some overlap between that and our kFreeBSD patches.  I'm
working to fix this and provide updated patches really soon.

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

Kernel: kFreeBSD 9.0-2-amd64-xenhvm-ipsec
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


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

Processed: Re: Bug#753783: xf86-video-glamo: FTBFS against xserver 1.16

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #753783 [src:xf86-video-glamo] xf86-video-glamo: FTBFS against xserver 1.16
Severity set to 'serious' from 'important'

-- 
753783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#754177: stumpwm does not work if `cl-asdf' is not installed.

[Milan Zamazal]

> "EL" == Emilio Lopes  writes:

EL> after installing `stumpwm' I could not start the window manager.  There
EL> was some error message mentioning `asdf', which was *not* installed.

EL> Note that `cl-asdf' is not `required' by `stumpwm', just `recommended'.

EL> After `cl-asdf' was installed, I could start `stumpwm' as expected.

Stumpwm can run on different Common Lisp implementations and perhaps not
all of them require cl-asdf to run Stumpwm.  So Stumpwm shouldn't depend
on cl-asdf.  Recommended packages should be installed unless you know
what you're doing, see Debian Policy:

  The `Recommends' field should list packages that would be found
  together with this one in all but unusual installations.

So I'd say `Recommends: cl-asdf' is OK here.  Do you think otherwise?


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

Bug#754218: boot hangs forever on LSB job "raise network interfaces"

[Stefano Zacchiroli]

Package: systemd
Version: 204-14
Severity: serious

I've rebooted today my laptop (Debian testing) and it failed to boot, hanging
forever on the message:

  [ ***  ] A start job is running for LSB: Raise network interfaces.

with the 3 asterisks moving back and forth.

I've been using systemd-sysv since several months now, and this is the first
time I've stumbled upon this (even though I do not boot that often, on average
every 2 weeks or so).

I've tried various workarounds (including /etc/network/interfaces) but the only
actual "solution" I've found it to manually remove systemd-sysv, install back
systemd-shim and sysvinit{,-core}; with that the laptop boots again. If I now
manually try to boot using systemd (passing init=/bin/systemd directly to the
kernel command line), the boot hangs again.

Note that I went through #746358 ("boot hangs if /etc/fstab contains an NFS
mount") and it does *not* appear to be the same issue. For one thing I do not
have any NFS entry in /etc/fstab (the closest I have is an autofs entry);
additionally, the fix discussed on the bug report *is* present on my laptop, to
no avail.

I attach both /etc/fstab and /etc/network/interfaces, hoping they are useful.

Thanks for maintaining systemd in Debian, "systemctl status" is so cool that I
can't wait to get it back on my laptop :)

Cheers.

-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  acl  2.2.52-1
ii  adduser  3.113+nmu3
ii  initscripts  2.88dsf-53.2
ii  libacl1  2.2.52-1
ii  libaudit11:2.3.7-1
ii  libc62.19-4
ii  libcap2  1:2.22-1.2
ii  libcap2-bin  1:2.22-1.2
ii  libcryptsetup4   2:1.6.4-4
ii  libdbus-1-3  1.8.6-1
ii  libgcrypt11  1.5.3-4
ii  libkmod2 16-2
ii  liblzma5 5.1.1alpha+20120614-2
ii  libpam0g 1.1.8-3
ii  libselinux1  2.3-1
ii  libsystemd-daemon0   204-14
ii  libsystemd-journal0  204-14
ii  libsystemd-login0204-14
ii  libudev1 204-14
ii  libwrap0 7.6.q-25
ii  sysv-rc  2.88dsf-53.2
ii  udev 204-14
ii  util-linux   2.20.1-5.8

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

Versions of packages systemd suggests:
pn  systemd-ui  

-- no debconf information

0 overridden configuration files found.
==> 
/var/lib/systemd/deb-systemd-helper-enabled/sysinit.target.wants/plymouth-read-write.service
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/sysinit.target.wants/plymouth-start.service
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/lvm2-activation.service.dsh-also <==
/etc/systemd/system/local-fs.target.wants/lvm2-activation.service

==> 
/var/lib/systemd/deb-systemd-helper-enabled/bluetooth.target.wants/bluetooth.service
 <==

==> /var/lib/systemd/deb-systemd-helper-enabled/puppetmaster.service.dsh-also 
<==
/etc/systemd/system/multi-user.target.wants/puppetmaster.service

==> 
/var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.ModemManager1.service
 <==

==> /var/lib/systemd/deb-systemd-helper-enabled/sshd.service <==

==> /var/lib/systemd/deb-systemd-helper-enabled/bluetooth.service.dsh-also <==
/etc/systemd/system/bluetooth.target.wants/bluetooth.service
/etc/systemd/system/dbus-org.bluez.service

==> 
/var/lib/systemd/deb-systemd-helper-enabled/kexec.target.wants/plymouth-kexec.service
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/NetworkManager-wait-online.service.dsh-also
 <==
/etc/systemd/system/multi-user.target.wants/NetworkManager-wait-online.service

==> /var/lib/systemd/deb-systemd-helper-enabled/avahi-daemon.socket.dsh-also <==
/etc/systemd/system/sockets.target.wants/avahi-daemon.socket

==> 
/var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/lvm2-lvmetad.socket
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/cups.socket <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/avahi-daemon.socket
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/acpi-fakekey.socket
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.Avahi.service 
<==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.NetworkManager.service
 <==

==> /var/lib/systemd/deb-systemd-helper-enabled/plymouth-kexec.service.dsh-also 
<==
/etc/systemd/system/kexec.target.wants/plymouth-kexec.service

==> /var/lib/systemd/deb-systemd-helper-enabled/plymouth.service <==

==> /var/lib/systemd/deb-systemd-helper-enabled/syslog.service <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.targ

Processed: virtualbox: FTBFS with GCC 4.9 as default

[Debian Bug Tracking System]

Processing control commands:

> block 753781 by -1
Bug #753781 [release.debian.org] transition: xserver 1.16
753781 was blocked by: 753783 751082
753781 was not blocking any bugs.
Added blocking bug(s) of 753781: 754220

-- 
753781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753781
754220: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#754220: virtualbox: FTBFS with GCC 4.9 as default

[Emilio Pozuelo Monfort]

Package: virtualbox
Version: 4.3.12-dfsg-1
Severity: serious
Control: block 753781 by -1

Your package fails to build now that GCC points to 4.9:

Checking for gcc: 
  ** gcc version 4.9 found, expected gcc 3.x with x>1 or gcc 4.x with 0https://buildd.debian.org/status/logs.php?pkg=virtualbox&ver=4.3.12-dfsg-1%2Bb1

This blocks the rebuilds for the new xserver 1.16.

Emilio


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

Bug#754221: xf86-video-msm: FTBFS against xserver 1.16

[Emilio Pozuelo Monfort]

Package: xf86-video-msm
Version: 1.0.1+git20100122.5f7df591-4
Severity: serious
Control: block

Your package fails to build against the new xserver 1.16:

https://buildd.debian.org/status/logs.php?pkg=xf86-video-msm&ver=1.0.1%2Bgit20100122.5f7df591-4%2Bb2

A patch should be trivial, similar to the one for xf86-video-glamo, see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753783

Emilio


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

Bug#754218: Acknowledgement (boot hangs forever on LSB job "raise network interfaces")

[Stefano Zacchiroli]

Ooops, forgot /etc/network/interfaces (although there isn't much to be
seen in there).

Cheers.
-- 
Stefano Zacchiroli  . . . . . . .  z...@upsilon.cc . . . . o . . . o . o
Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o
Former Debian Project Leader  . . @zack on identi.ca . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
# This is an autoconfigured IPv6 interface
iface eth0 inet6 auto

Processed: Re: Processed (with 1 errors): xf86-video-msm: FTBFS against xserver 1.16

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 753781 by 754221
Bug #753781 [release.debian.org] transition: xserver 1.16
753781 was blocked by: 753783 754220 751082
753781 was not blocking any bugs.
Added blocking bug(s) of 753781: 754221
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
753781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#754218: boot hangs forever on LSB job "raise network interfaces"

[Michael Biebl]

Am 08.07.2014 21:20, schrieb Stefano Zacchiroli:
> Package: systemd
> Version: 204-14
> Severity: serious
> 
> I've rebooted today my laptop (Debian testing) and it failed to boot, hanging
> forever on the message:
> 
>   [ ***  ] A start job is running for LSB: Raise network interfaces.

Did you actually wait forever, i.e. at least 90 seconds which is the
usual timeout for devices to appear or services to start?

Can you please try the following:
systemctl enable debug-shell.service

This allows you to switch to tty9 very early during boot and inspect the
system.

A systemctl list-jobs and ps aux output might be helpful in this case.

Booting with systemd.log_level=debug and the journalctl -alb output
would be great as well.

Could you also please tar up /etc/network/interfaces, /etc/network/*,
/etc/dhcp*, /etc/rc?.d/ and /etc/init.d.

This might give us further clues.

Thanks and sorry for the inconvenience.


Michael



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



signature.asc
Description: OpenPGP digital signature

Bug#754212: marked as done (sogo: FTBFS on powerpc and s390x: test failures)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jul 2014 19:49:46 +
with message-id 
and subject line Bug#754212: fixed in sogo 2.2.5-3
has caused the Debian Bug report #754212,
regarding sogo: FTBFS on powerpc and s390x: test failures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
754212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sogo
Version: 2.2.5-2
Severity: serious

Your package failed to build on powerpc and s390x (and sparc) with test
failures:

../obj/sogo-tests
2014-07-08 17:31:56.415 sogo-tests[13674] File NSBundle.m: 880. In 
+[NSBundle(Private) _addFrameworkFromClass:] Could not find framework SOGo in 
any standard location
..F2014-07-08 17:31:56.420 sogo-tests[13674] Note: Using UTF-8 as URL encoding 
in NGExtensions.
FF..F
==
FAIL: test_rendering (TestVersit.m:86)
--
string 'ELEM:NAMED2=1\,2\,3;NAMED3=text1\;text2;NAMED1=1,2,3
' elements not the same as in 
'ELEM:NAMED1=1,2,3;NAMED2=1\,2\,3;NAMED3=text1\;text2'

==
FAIL: test_stringByEscapingURL (TestNSString+URLEscaping.m:50)
--
string 'sogo+test' badly escaped: 'sogo%2Btest' (expected 'sogo+test')

==
FAIL: test_occurrenceForDate_ (TestiCalTimeZonePeriod.m:84)
--
test 0: seconds do not match: delta = -18000

==
FAIL: test_generateDataForHeaderFieldNamed_value_ 
(TestNGMimeAddressHeaderFieldGenerator.m:79)
--
received 'wolfg...@test.com,
   wolfg...@test.com' instead of '"" ' 
for '"" '

--
Ran 15 tests

FAILED (4 failures, 0 errors)
make[3]: *** [check] Error 1

See https://buildd.debian.org/status/logs.php?pkg=sogo&ver=2.2.5-2 for the
full logs.

Emilio
--- End Message ---
--- Begin Message ---
Source: sogo
Source-Version: 2.2.5-3

We believe that the bug you reported is fixed in the latest version of
sogo, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 754...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeroen Dekkers  (supplier of updated sogo package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 08 Jul 2014 21:12:12 +0200
Source: sogo
Binary: sogo sogo-common sogo-dbg sogo-openchange
Architecture: source amd64 all
Version: 2.2.5-3
Distribution: unstable
Urgency: medium
Maintainer: Jeroen Dekkers 
Changed-By: Jeroen Dekkers 
Description:
 sogo   - Scalable groupware server
 sogo-common - Scalable groupware server - common files
 sogo-dbg   - Scalable groupware server - debugging symbols
 sogo-openchange - Scalable groupware server - OpenChange backend
Closes: 754212
Changes:
 sogo (2.2.5-3) unstable; urgency=medium
 .
   * [a0105ea6] Disable buggy TestVersit unit test. (Closes: #754212)
Checksums-Sha1:
 f2896803d0ff1fccd25f73d166ad25ccf5ee63a8 1889 sogo_2.2.5-3.dsc
 1a6121183bf26d2ee2e316785e804037353e2aa3 15316 sogo_2.2.5-3.debian.tar.xz
 8f1cd607b5bfd760fbeb10a89decb39f52c01a06 1923558 sogo_2.2.5-3_amd64.deb
 c56e76ed6cf67975f92fdc32e2b62e49680e866f 1678790 sogo-common_2.2.5-3_all.deb
 aa4212a27f2042c009f286d3517681516d05f8f3 4065902 sogo-dbg_2.2.5-3_amd64.deb
 6f1a65d4fcd5b3ae68cce481d62213304e395cfb 1120538 
sogo-openchange_2.2.5-3_amd64.deb
Checksums-Sha256:
 ff45097bba1b7f1f3e231aa12b13e52841d88a88772ca95206c26afe014abb83 1889 
sogo_2.2.5-3.dsc
 af1eeb6682d0dc2c7528d9631770db3db4faabdae6369857d5712739892b96fd 15316 
sogo_2.2.5-3.debian.tar.xz
 426085bff3f2ab521dc1bf68f5bc93356b96918195b2cfa8f3f22a16c978db74 1923558 
sogo_2.2.5-3_amd64.deb
 dd95930780c6eb3442c041aab8a9c0111a35250586e45eab3087982ab21241da 1678790 
sogo-common_2.2.5-3_all.deb
 26f352fb1

Bug#754054: perl: FTBFS on mips: Bad mojo! at make_patchnum.pl line 111.

[Niko Tyni]

On Mon, Jul 07, 2014 at 08:00:37AM +0300, Niko Tyni wrote:
> Package: perl
> Version: 5.18.2-5
> Severity: serious
> X-Debbugs-Cc: debian-m...@lists.debian.org
> 
> The perl package failed to build on mips:
>  
> LD_LIBRARY_PATH=/build/perl\-sdOt09/perl\-5.18.2${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH
>   ./miniperl -Ilib make_patchnum.pl
>  Bad mojo! at make_patchnum.pl line 111.

> This is reproducible on gabrielli.

A test case would be

  gabrielli% cat ~/t.pl
  print ( (q{foo'} =~ /[^']+'/) ?  "ok\n" : "not ok\n" );
  gabrielli% perl ~/t.pl
  ok
  gabrielli% ./miniperl ~/t.pl
  not ok

This is a shared build; the static build doesn't exhibit the bug and
passes the full test suite. The bug only shows up with -fPIC.

An educated guess narrowed it down to regcomp.c. The above test fails
when regcomp.c is built with gcc-4.9 at -O2 but works with gcc-4.9 at
-O0 and gcc-4.8 at -O2.

I'll patch the package to lower the optimization level of regcomp.c
for now.  Assuming a test build succeeds on gabrielli, I hope to upload
tomorrow.

Distilling a proper gcc bug report about this seems rather arduous, and
I don't really expect to get around to it. Help from the MIPS porters
on that would be appreciated.
-- 
Niko Tyni   nt...@debian.org


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

Bug#754158: blueman: blueman-applet says pulseaudio is too old

[Christopher Schramm]

Hi Łukasz,

this is a known problem of  the wheezy version. As you mentioned you can use 
the backports version to make it work. What's the intention of your bug report?

Cheers

Bug#754218: boot hangs forever on LSB job "raise network interfaces"

[Stefano Zacchiroli]

On Tue, Jul 08, 2014 at 09:32:43PM +0200, Michael Biebl wrote:
> Did you actually wait forever, i.e. at least 90 seconds which is the
> usual timeout for devices to appear or services to start?

Obviously I didn't wait *forever* :), but yes, I did wait past usual
network timeouts. To be sure, I've just tried again, and after 10+
minutes the boot was still hanging.

The good news is...

> Can you please try the following:
> systemctl enable debug-shell.service

...thanks to this, which I didn't know about, I've tracked down the
culprit to my /etc/network/if-up.d/local-firewall script, which reads:


#!/bin/sh
# This file is managed by Puppet, local modifications will be overwritten

FIREWALL=shorewall
FIREWALL6=shorewall6

service $FIREWALL restart
service $FIREWALL6 restart


After a couple of killall local-firewall (one for each service
invocation, evidently) the boot continued and reached completion
properly.

> A systemctl list-jobs and ps aux output might be helpful in this case.

Both attached, just in case, but the cause seems to be clear.

Now the questions/comments:

- I've had that script since ever, basically, and it used to work fine
  in the past, both before and after switching to systemd as init. I'm
  not sure why/when it stopped working.

- As a mere user, the above script is perfectly reasonable, I *do* want
  to restart my firewall every time my network interface is brought up,
  and AFAICT I'm using the right "API" to do so.

HTH,
Cheers.
-- 
Stefano Zacchiroli  . . . . . . .  z...@upsilon.cc . . . . o . . . o . o
Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o
Former Debian Project Leader  . . @zack on identi.ca . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »
  1 graphical.target start waiting
  2 multi-user.targetstart waiting
  3 basic.target start waiting
  4 sysinit.target   start waiting
 64 networking.service   start running
 65 network.target   start waiting
 67 rpcbind.service  start waiting
 68 rpcbind.target   start waiting
 71 shorewall.servicestart waiting
 73 shorewall6.service   start waiting
 74 nfs-common.service   start waiting
 77 sockets.target   start waiting
 79 cups.socket  start waiting
 80 acpid.socket start waiting
 81 avahi-daemon.socket  start waiting
 82 acpi-fakekey.socket  start waiting
 85 dbus.socket  start waiting
 86 timers.targetstart waiting
 87 systemd-tmpfiles-clean.timer start waiting
 88 paths.target start waiting
 89 console-kit-log-system-start.service start waiting
 90 uptimed.service  start waiting
 91 avahi-daemon.service start waiting
 92 atd.service  start waiting
 93 binfmt-support.service   start waiting
 94 cups.pathstart waiting
 97 cups-browsed.service start waiting
 98 cups.service start waiting
 99 ModemManager.service start waiting
100 plymouth-quit-wait.service   start waiting
101 ssh.service  start waiting
102 NetworkManager.service   start waiting
103 cron.service start waiting
104 privoxy.service  start waiting
105 plymouth-quit.servicestart waiting
106 anacron.service  start waiting
107 rsyslog.service  start waiting
110 rc-local.service start waiting
111 systemd-user-sessions.servicestart waiting
113 getty.target start waiting
114 getty@tty1.service   start waiting
115 dbus.service start waiting
116 systemd-logind.service   start waiting
117 systemd-update-utmp-runlevel.service start waiting
118 speech-dispatcher.servicestart waiting
119 gdomap.service   start waiting
120 puppetqd.service start waiting
121 gdm3.service start waiting
122 x-display-manager.target start waiting
123 acpi-support.service start waiting
124 bootlogs.service start waiting
125 apache2.service  start waiting
126 sysfsutils.service   start waiting
127 ntp.service  start waiting
128 dictd.servicestart waiting
129 minissdpd.servicestart waiti

Bug#751425: maplev.el (ERROR: install script from emacs-goodies-el package failed)

[Peter S Galbraith]

I was thinking of simply removing maplev.el from the package since it's
so old and maybe obsolete, but I just found a version of maplev.el
modified in March 2013 from the upstream author at
https://github.com/JoeRiel/maplev.  Maybe there's hope for it.

However it still contains the line
 (require 'abbrevlist)

used for `list-one-abbrev-table' in `maplev-abbrev-help'.  But
`list-one-abbrev-table' is an autoload.  The require line could be
commented out to see if that changes anything.  I doubt it, since
byte-compiling the file from emacs24 yields no errors for me, only a few
warnings:

,
| Compiling file /usr/share/emacs24/site-lisp/emacs-goodies-el/maplev.el at Tue 
Jul  8 13:50:57 2014
| maplev.el:131:1:Warning: cl package required at runtime
| 
| In maplev-fill-paragraph:
| maplev.el:1628:4:Warning: value returned from (make-string (/ (current-column)
| tab-width) 9) is unused
| 
| In maplev-mode:
| maplev.el:1823:9:Warning: assignment to free variable
| `imenu-default-create-index-function'
| 
| In maplev-cmaple--clear-buffer:
| maplev.el:3479:8:Warning: Use `with-current-buffer' rather than
| save-excursion+set-buffer
| 
| In maplev-cmaple-mode:
| maplev.el:3580:9:Warning: `comint-use-prompt-regexp-instead-of-fields' is an
| obsolete variable (as of 22.1); use `comint-use-prompt-regexp' instead.
| 
| In maplev-mint-region:
| maplev.el:4672:37:Warning: Use `with-current-buffer' rather than
| save-excursion+set-buffer
| maplev.el:4674:19:Warning: Use `with-current-buffer' rather than
| save-excursion+set-buffer
| 
| In end of data:
| maplev.el:4893:1:Warning: the function `x-get-cut-buffer' is not known to be
| defined.
`

-- 
Peter


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

Bug#752762: load-module module-alsa-sink freezes display

[Felipe Sateler]

On 6 Jul 2014 14:48, "Michael Meskes"  wrote:
>
> > If a client tries to repeatedly connect then yes, it could respawn
> > pulseaudio pretty fast. But this seems unlikely, given that the log
> > does not show multiple messages. What happens if you have the wrong
> > line and disable autospawn?
>
> Then it works.

Ok, so it seems the problem is indeed autospawn related. I think
something within your session startup sequence cannot handle
pulseaudio dying. Do oy


> > > Honestly I haven't checked since finding my problem, but it may also
> > > have to do with a non-existing default sink. Anyway, I shall try again and
> > > report back.
> >
> > Please do so, also trying with a disabled autospawn.
>
> Bad idea, the misconfigured default-sink was not reason for my problems as 
> just
> "enabling" the alsa sink module created the same problem again. My screen
> stayed black again. At the very same moment I had, like, seven pulseaudio
> processes running at the same time, albeit no log entry at all this time.

Hmm, there seems to be some sort of race at pa startup, with multiple
pa daemons getting autospawned. But are there any more logs in syslog
(after the crash)? Because it seems strange to me that pa won't log
anymore if the config is the problem.

If you can reproduce this again, can you open a VT or ssh into your
system or otherwise poke into the pulseaudio daemons? Please install
the dbg packages and then try to get a backtrace of each of the
pulseaudio daemons (`gdb -p $pid`). Also please post the output of `ps
aux | grep pulseaudio` (before running gdb).


> However, I did manager to lose all my desktop configuration this time. I guess
> the next time I try I better use a test user. :)

:( I'm sorry to hear that.


Saludos,
Felipe Sateler


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

Bug#752836: marked as done (gnash: build-depends on xulrunner-dev which is gone)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jul 2014 21:36:17 +
with message-id 
and subject line Bug#752836: fixed in gnash 0.8.11~git20140708-1
has caused the Debian Bug report #752836,
regarding gnash: build-depends on xulrunner-dev which is gone
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
752836: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnash
Severity: serious

gnash build-depends on xulrunner-dev, which is no longer built by
src:iceweasel. If you use it for libxul or mozilla-plugin, that is
now in iceweasel-dev. If you were using mozilla-js, you may want to
look at src:mozjs24.

Emilio 
--- End Message ---
--- Begin Message ---
Source: gnash
Source-Version: 0.8.11~git20140708-1

We believe that the bug you reported is fixed in the latest version of
gnash, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 752...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gabriele Giacone <1o5g4...@gmail.com> (supplier of updated gnash package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 08 Jul 2014 20:32:19 +0200
Source: gnash
Binary: gnash-common gnash klash gnash-tools gnash-cygnal browser-plugin-gnash 
konqueror-plugin-gnash python-gtk-gnash gnash-ext-fileio gnash-ext-mysql 
gnash-ext-lirc gnash-dev gnash-dbg gnash-doc gnash-common-opengl gnash-opengl 
klash-opengl swfdec-mozilla swfdec-gnome mozilla-plugin-gnash
Architecture: source i386 all
Version: 0.8.11~git20140708-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Flash Team 
Changed-By: Gabriele Giacone <1o5g4...@gmail.com>
Description:
 browser-plugin-gnash - GNU Shockwave Flash (SWF) player - Plugin for Mozilla 
and derivat
 gnash  - GNU Shockwave Flash (SWF) player
 gnash-common - GNU Shockwave Flash (SWF) player - Common files/libraries
 gnash-common-opengl - dummy package for gnash-common-opengl removal
 gnash-cygnal - GNU Shockwave Flash (SWF) player - Media server
 gnash-dbg  - GNU Shockwave Flash (SWF) player - Debug symbols
 gnash-dev  - GNU Shockwave Flash (SWF) player - Development files
 gnash-doc  - GNU Shockwave Flash (SWF) player - API documentation
 gnash-ext-fileio - GNU Shockwave Flash (SWF) player - Fileio extension
 gnash-ext-lirc - GNU Shockwave Flash (SWF) player - LIRC extension
 gnash-ext-mysql - GNU Shockwave Flash (SWF) player - MySQL extension
 gnash-opengl - dummy package for gnash-opengl removal
 gnash-tools - GNU Shockwave Flash (SWF) player - Command-line Tools
 klash  - GNU Shockwave Flash (SWF) player - Standalone player for KDE
 klash-opengl - dummy package for klash-opengl removal
 konqueror-plugin-gnash - GNU Shockwave Flash (SWF) player - Plugin for 
Konqueror
 mozilla-plugin-gnash - dummy package for renaming to browser-plugin-gnash
 python-gtk-gnash - GNU Shockwave Flash (SWF) player - Python bindings
 swfdec-gnome - dummy package for transition to Gnash
 swfdec-mozilla - dummy package for transition to browser-plugin-gnash
Closes: 752836
Changes:
 gnash (0.8.11~git20140708-1) unstable; urgency=medium
 .
   * New upstream snapshot.
 + Remove libboost-thread-dev B-D, switched to std::thread.
   * Add --enable-sound=none configure option on hurd.
   * Make testsuite failures more verbose.
   * Switch from xulrunner-dev to npapi-sdk-dev B-D (Closes: #752836).
Checksums-Sha1:
 56d5d84493561157c56af2cc9ef3f772b3243ec3 3516 gnash_0.8.11~git20140708-1.dsc
 51832907ccac29b835017a97e786bd91a9e18a6d 4027384 
gnash_0.8.11~git20140708.orig.tar.xz
 7907856f566f3943a67ee347f6806978d89bd88b 31992 
gnash_0.8.11~git20140708-1.debian.tar.xz
 c8b380fa0bc22201158993c16d34ee19a1c5623c 1924816 
gnash-common_0.8.11~git20140708-1_i386.deb
 da0eae8b403effd7ae0bbd9f5aae3a9cbb536b4b 182464 
gnash_0.8.11~git20140708-1_i386.deb
 d087f08b31f65b0a79122a8027aa7f13f909a939 176782 
klash_0.8.11~git20140708-1_i386.deb
 e131f8e02dc6b876ab03e75e27bd99a68fdd32d1 121686 
gnash-tools_0.8.11~git20140708-1_i386.deb
 cde5525f8067576d7dc7e796a83a823019697159 401582 
gnash-cygnal_0.8.11~git20140708-1_i386.deb
 0ac05fe52fde5d85ec4d2b6d48ff8be98fe3a7e7 117772 
browser-pl

Bug#751259: marked as done (webkitgtk FTBFS on armel/armhf)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jul 2014 21:42:06 +
with message-id 
and subject line Bug#751259: fixed in webkitgtk 2.4.4-1
has caused the Debian Bug report #751259,
regarding webkitgtk FTBFS on armel/armhf
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
751259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751259
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: webkitgtk
Version: 2.4.3-2
Severity: serious
Justification: FTBFS

Hi,

It seems libgl1-mesa-dev will be pulled in regardless:

dd-schroot-cmd -c sid_armhf-dchroot-7101d185-7aa9-42e0-a68c-0bbf3271b410 
apt-get build-dep webkitgtk
...
  libgirepository-1.0-1 libgirepository1.0-dev libgl1-mesa-dev libgl1-mesa-glx
  libglapi-mesa libgles2-mesa libgles2-mesa-dev libglib2.0-0 libglib2.0-bin
...

So a build-conflicts: libgl1-mesa-dev [armel armhf] would be needed, or the 
sources
need to accomodate the possibility of both installed. Since with freeadreno and 
nouveau
drivers coming to arm, there are also full opengl drivers for arm, this kind of 
arch based
detection is a bit frowned upon.

If armel/armhf go gles, please check that all packages building upon webkitgkt 
still work
on arm after the change.

See http://people.debian.org/~public_html/webkitgtk_armhf.log for build log:

In file included from 
../Source/WebCore/platform/graphics/egl/GLContextEGL.cpp:32:0:
../Source/ThirdParty/ANGLE/include/GLES2/gl2.h:39:26: error: 'GLsizeiptr' has a 
previous declaration as 'typedef khronos_ssize_t GLsizeiptr'
 typedef khronos_ssize_t  GLsizeiptr;
  ^
In file included from /usr/include/GL/gl.h:2059:0,
 from /usr/include/GL/glx.h:32,
 from /usr/include/cairo/cairo-gl.h:96,
 from 
../Source/WebCore/platform/graphics/egl/GLContextEGL.cpp:39:
/usr/include/GL/glext.h:469:19: error: conflicting declaration 'typedef 
ptrdiff_t GLintptr'
 typedef ptrdiff_t GLintptr;
   ^
In file included from 
../Source/WebCore/platform/graphics/egl/GLContextEGL.cpp:32:0:
../Source/ThirdParty/ANGLE/include/GLES2/gl2.h:38:26: error: 'GLintptr' has a 
previous declaration as 'typedef khronos_intptr_t GLintptr'
 typedef khronos_intptr_t GLintptr;
  ^
GNUmakefile:64748: recipe for target 
'Source/WebCore/platform/graphics/egl/libWebCoreGtk_la-GLContextEGL.lo' failed
make[2]: *** 
[Source/WebCore/platform/graphics/egl/libWebCoreGtk_la-GLContextEGL.lo] Error 1
make[2]: *** Waiting for unfinished jobs
mv -f Source/WebCore/plugins/gtk/.deps/libWebCoreGtk_la-PluginViewGtk.Tpo 
Source/WebCore/plugins/gtk/.deps/libWebCoreGtk_la-PluginViewGtk.Plo
make[2]: Leaving directory '/home/riku/webkitgtk-2.4.3/build-2.0'
--- End Message ---
--- Begin Message ---
Source: webkitgtk
Source-Version: 2.4.4-1

We believe that the bug you reported is fixed in the latest version of
webkitgtk, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 751...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alberto Garcia  (supplier of updated webkitgtk package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 08 Jul 2014 17:25:22 +0300
Source: webkitgtk
Binary: libjavascriptcoregtk-1.0-0 libjavascriptcoregtk-1.0-dev 
libjavascriptcoregtk-1.0-0-dbg libwebkitgtk-1.0-0 libwebkit-dev 
libwebkitgtk-dev libwebkitgtk-1.0-common libwebkitgtk-1.0-0-dbg 
libjavascriptcoregtk-3.0-0 libjavascriptcoregtk-3.0-dev 
libjavascriptcoregtk-3.0-0-dbg libjavascriptcoregtk-3.0-bin 
gir1.2-javascriptcoregtk-3.0 libwebkitgtk-3.0-0 libwebkitgtk-3.0-dev 
libwebkitgtk-3.0-common libwebkitgtk-3.0-0-dbg gir1.2-webkit-3.0 
libwebkit2gtk-3.0-25 libwebkit2gtk-3.0-dev libwebkit2gtk-3.0-25-dbg 
gir1.2-webkit2-3.0 libwebkitgtk-common-dev
Architecture: source all amd64
Version: 2.4.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian WebKit Maintainers 

Changed-By: Alberto Garcia 
Description:
 gir1.2-javascriptcoregtk-3.0 - JavaScript engine library from WebKitGTK+ - 
GObject introspection
 gir1.2-webkit-3.0 - Web content engine library for GTK+ - GObject 
introspection data
 gir1.2-webkit2-3.0 - WebKit2 API layer fo

Bug#754232: Should miro be removed from the archive?

[Moritz Muehlenhoff]

Package: miro
Severity: serious

Should miro be removed from the archive?

- Last maintainer upload 2.5 years ago
- Removed from testing 9 months ago
- Totally outdated (current upstream is 6)

Unless some disagrees, I'll reassign to ftp.debian.org in a few weeks.

Cheers,
Moritz


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

Bug#752209: About calligra icc profiles packaging.

[Raúl Sánchez Siles]

  Hi:

  Thanks for the report. I've checked the fogra27l.icm file details. It indeed 
matches the one provided by the (nonfree) icc-profiles. Anyway, according to 
iccdump:

iccdump  plugins/colorengines/lcms2/colorprofiles/data/fogra27l.icm

[...]
tag 1:
  sig  'cprt'
  type 'text'
  offset   396
  size 22
Text:
  No. chars = 14
0x: Public Domain
[...]

  So I think we can consider this file as Public Domain. As you say, it is not 
licensed under the same terms as the rest of the package but I don't think 
this make the whole package fails to comply with the Debian policy.

  Anyway, copyright file may be adjusted and maybe we should add and support 
dependency on icc-profiles* packages.

  As an extra, I'm adding some information iccdump provided and which we 
should verify with upstream:

krita/data/profiles/WideGamut.icm (No copyright)
krita/data/profiles/sRGB.icm (No copyright)
krita/data/profiles/scRGB.icm (© Cyrille Berger)
krita25_lcms-builtin-sRGB_g100-truegamma.icc (v4 not supported by iccdump)
plugins/colorengines/lcms2/colorprofiles/data/fogra27l.icm (public domain)
plugins/colorengines/lcms2/colorprofiles/data/CMY.icm (copyright Sun 
Microsystems, 1996)


  Regards,
-- 
 Raúl Sánchez Siles
->Proud Debian user<-
Linux registered user #416098


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

Bug#754218: boot hangs forever on LSB job "raise network interfaces"

[Stefano Zacchiroli]

On Tue, Jul 08, 2014 at 10:50:27PM +0200, Stefano Zacchiroli wrote:
> #!/bin/sh
[...]
> service $FIREWALL restart
> service $FIREWALL6 restart
> 
> 
> After a couple of killall local-firewall (one for each service
> invocation, evidently) the boot continued and reached completion
> properly.

Actually, that doesn't make sense. Because of course either the first
killall has killed the script and the second service is not executed; or
it didn't, but then why the second did?  So I'm still unsure about why
the killall(s) made the boot complete successfully.

If this detail is important, please let me know; I can debug it more
thoroughly (e.g., by noting down PIDs).

Cheers.
-- 
Stefano Zacchiroli  . . . . . . .  z...@upsilon.cc . . . . o . . . o . o
Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o
Former Debian Project Leader  . . @zack on identi.ca . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »


signature.asc
Description: Digital signature

Processed: 747214 is also present in testing

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 747214 1.47.11-1
Bug #747214 [espeak] missing license / non-free files
Marked as found in versions espeak/1.47.11-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
747214: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747214
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#752949: marked as done (xf86-video-glamo: FTBFS - patches/ftbfs-gcc-4.7.diff isn't a valid patch)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jul 2014 22:25:28 +
with message-id 
and subject line Bug#752949: fixed in xf86-video-glamo 
0.0.0+20110719.gitcb9ed170-2
has caused the Debian Bug report #752949,
regarding xf86-video-glamo: FTBFS - patches/ftbfs-gcc-4.7.diff isn't a valid 
patch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
752949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752949
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xf86-video-glamo
Version: 0.0.0+20110719.gitcb9ed170-1
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
I: Running /usr/bin/dpkg-buildpackage -rfakeroot -us -uc ${DEBBUILDOPTS}
dpkg-buildpackage: source package xf86-video-glamo
dpkg-buildpackage: source version 0.0.0+20110719.gitcb9ed170-1
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Gilles Filippini 
 dpkg-source --before-build xf86-video-glamo-0.0.0+20110719.gitcb9ed170
dpkg-buildpackage: host architecture amd64
dpkg-source: error: expected ^--- in line 3 of diff 
`xf86-video-glamo-0.0.0+20110719.gitcb9ed170/debian/patches/ftbfs-gcc-4.7.diff'
dpkg-buildpackage: error: dpkg-source --before-build 
xf86-video-glamo-0.0.0+20110719.gitcb9ed170 gave error exit status 25


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.

Best,
Michael


xf86-video-glamo-build-log.txt.gz
Description: application/gunzip


pgpUgzjzYN6Qi.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: xf86-video-glamo
Source-Version: 0.0.0+20110719.gitcb9ed170-2

We believe that the bug you reported is fixed in the latest version of
xf86-video-glamo, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 752...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gilles Filippini  (supplier of updated xf86-video-glamo 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 08 Jul 2014 23:32:30 +0200
Source: xf86-video-glamo
Binary: xserver-xorg-video-glamo
Architecture: source i386
Version: 0.0.0+20110719.gitcb9ed170-2
Distribution: unstable
Urgency: medium
Maintainer: Debian freesmartphone.org Team 

Changed-By: Gilles Filippini 
Description:
 xserver-xorg-video-glamo - X.Org X server -- SMedia Glamo display driver
Closes: 752949 753783
Changes:
 xf86-video-glamo (0.0.0+20110719.gitcb9ed170-2) unstable; urgency=medium
 .
   * Fix patch format for ftbfs-gcc-4.7.diff (closes: #752949; thanks
 Juhani Numminen)
   * New patch const-qualifier.patch: fix FTBFS against xserver 1.16
 (closes: #753783; thanks Emilio Pozuelo Monfort)
   * Bump Standards-Version to 3.9.5 (no changes)
Checksums-Sha1:
 e400aa438616817b5b055b106c914a4cc98081ce 2143 
xf86-video-glamo_0.0.0+20110719.gitcb9ed170-2.dsc
 3e1d4d49f2e246ae7aeae1a570d708c71b35b72e 7704 
xf86-video-glamo_0.0.0+20110719.gitcb9ed170-2.debian.tar.xz
 f9ca1609e60dfcce06bfb4c1d931f65062beed40 17670 
xserver-xorg-video-glamo_0.0.0+20110719.gitcb9ed170-2_i386.deb
Checksums-Sha256:
 e1d4958c8e81bdc0399976dd9ea5a9c2df10a356fa70463cdd3e9439dcf2b1de 2143 
xf86-video-glamo_0.0.0+20110719.gitcb9ed170-2.dsc
 5d963985a0bc6886be6c47005a27e2b562e14404304d48800976acc16da64897 7704 
xf86-video-glamo_0.0.0+20110719.gitcb9ed170-2.debian.tar.xz
 81048faa201621ce2cd35a2e951838a48d5c6678339d67f553debbc1e4f7c5dc 17670 
xserver-xorg-video-glamo_0.0.0+20110719.gitcb9ed170-2_i386.deb
Files:
 ede1b88def3549c377f4040e00f76bf5 17670 x11 optional 
xserver-xorg-video-glamo_0.0.0+20110719.gitcb9ed170-2_i386.deb
 bb5bca36d100849fe249935260d54e78 2143 x11 optional 
xf86-video-glamo_0.0.0+20110719.gitcb9ed170-2.dsc
 07f7cb5a186f0f3615c0eff90a476e24 7704 x11 optional 
xf86-video-glamo_0.0.0+20110719.gitcb9ed170-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJTvGWTAAoJEO/obGx//s+DGIcH/3GESCvPTu9DLrhR2FXfw9uy
+IF11hzbGVhU+hEdDPdnSyo+xULdg89/g+g5zJP+u5KjEaNwS2uLph2noSI70myv
LgvX+ODWANjUXDpKxQGNmSHBDecaHTqtS3oU45KVp5Qa2IbXivX

Bug#753783: marked as done (xf86-video-glamo: FTBFS against xserver 1.16)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jul 2014 22:25:28 +
with message-id 
and subject line Bug#753783: fixed in xf86-video-glamo 
0.0.0+20110719.gitcb9ed170-2
has caused the Debian Bug report #753783,
regarding xf86-video-glamo: FTBFS against xserver 1.16
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
753783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xf86-video-glamo
Version: 0.0.0+20110719.gitcb9ed170-1
Severity: important
Tags: patch
Control: block 753781 by -1

xf86-video-glamo fails to build against xserver 1.16, which we plan
to upload to sid soon, see #753781.

The build error is:

.../../src/glamo-driver.c: In function 'GlamoPreInit':
.../../src/glamo-driver.c:499:32: error: assignment discards 'const' qualifier 
from pointer target type [-Werror]
 pGlamo->jbt6k74_state_path = xf86GetOptValString(pGlamo->Options,
^
cc1: all warnings being treated as errors

The attached patch fixes the build failure.

Emilio
--- a/src/glamo.h
+++ b/src/glamo.h
@@ -145,7 +145,7 @@
 #endif
 
 #ifdef JBT6K74_SET_STATE
-char *jbt6k74_state_path;
+const char *jbt6k74_state_path;
 char saved_jbt6k74_state[14];
 #endif
 
--- End Message ---
--- Begin Message ---
Source: xf86-video-glamo
Source-Version: 0.0.0+20110719.gitcb9ed170-2

We believe that the bug you reported is fixed in the latest version of
xf86-video-glamo, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 753...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gilles Filippini  (supplier of updated xf86-video-glamo 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 08 Jul 2014 23:32:30 +0200
Source: xf86-video-glamo
Binary: xserver-xorg-video-glamo
Architecture: source i386
Version: 0.0.0+20110719.gitcb9ed170-2
Distribution: unstable
Urgency: medium
Maintainer: Debian freesmartphone.org Team 

Changed-By: Gilles Filippini 
Description:
 xserver-xorg-video-glamo - X.Org X server -- SMedia Glamo display driver
Closes: 752949 753783
Changes:
 xf86-video-glamo (0.0.0+20110719.gitcb9ed170-2) unstable; urgency=medium
 .
   * Fix patch format for ftbfs-gcc-4.7.diff (closes: #752949; thanks
 Juhani Numminen)
   * New patch const-qualifier.patch: fix FTBFS against xserver 1.16
 (closes: #753783; thanks Emilio Pozuelo Monfort)
   * Bump Standards-Version to 3.9.5 (no changes)
Checksums-Sha1:
 e400aa438616817b5b055b106c914a4cc98081ce 2143 
xf86-video-glamo_0.0.0+20110719.gitcb9ed170-2.dsc
 3e1d4d49f2e246ae7aeae1a570d708c71b35b72e 7704 
xf86-video-glamo_0.0.0+20110719.gitcb9ed170-2.debian.tar.xz
 f9ca1609e60dfcce06bfb4c1d931f65062beed40 17670 
xserver-xorg-video-glamo_0.0.0+20110719.gitcb9ed170-2_i386.deb
Checksums-Sha256:
 e1d4958c8e81bdc0399976dd9ea5a9c2df10a356fa70463cdd3e9439dcf2b1de 2143 
xf86-video-glamo_0.0.0+20110719.gitcb9ed170-2.dsc
 5d963985a0bc6886be6c47005a27e2b562e14404304d48800976acc16da64897 7704 
xf86-video-glamo_0.0.0+20110719.gitcb9ed170-2.debian.tar.xz
 81048faa201621ce2cd35a2e951838a48d5c6678339d67f553debbc1e4f7c5dc 17670 
xserver-xorg-video-glamo_0.0.0+20110719.gitcb9ed170-2_i386.deb
Files:
 ede1b88def3549c377f4040e00f76bf5 17670 x11 optional 
xserver-xorg-video-glamo_0.0.0+20110719.gitcb9ed170-2_i386.deb
 bb5bca36d100849fe249935260d54e78 2143 x11 optional 
xf86-video-glamo_0.0.0+20110719.gitcb9ed170-2.dsc
 07f7cb5a186f0f3615c0eff90a476e24 7704 x11 optional 
xf86-video-glamo_0.0.0+20110719.gitcb9ed170-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJTvGWTAAoJEO/obGx//s+DGIcH/3GESCvPTu9DLrhR2FXfw9uy
+IF11hzbGVhU+hEdDPdnSyo+xULdg89/g+g5zJP+u5KjEaNwS2uLph2noSI70myv
LgvX+ODWANjUXDpKxQGNmSHBDecaHTqtS3oU45KVp5Qa2IbXivXSpWcZzs3S7A+T
4llEvgu0s2++2cDUvpbRcPGIaoMra/f48McM7HQaeAOOq3I3W/5sI8GwhM9XH5pg
b0wLcygA/rks+bzAWmJD/MIjNOZUoFpJArk0JvmSAwTDNs4zsaoIvFxHc97faGro
7ncMR3zIVi1MSPoPD8nu37zZGS2ZFvBpfjqsoHDJ2mZWQgiX5DR6R9C7cDBh2Ek=
=7jUm
-END PGP SIGNATURE End Message ---

Processed: limit source to yate, tagging 750272

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #yate (5.3.0-1-1) UNRELEASED; urgency=low
> #
> #  * Apply upstream patches to properly place files in multiarch pathes
> #(Closes: #750272).
> #
> limit source yate
Limiting to bugs with field 'source' containing at least one of 'yate'
Limit currently set to 'source':'yate'

> tags 750272 + pending
Bug #750272 [src:yate] yate: FTBFS: dh_install: yate-pgsql missing files 
(usr/lib/*/yate/server/pgsqldb.yate), aborting
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
750272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#753699: lynx: Alert!: This client does not contain support for HTTPS URLs.

[Thomas Dickey]

On Tue, Jul 08, 2014 at 07:22:39PM +0200, Andreas Metzler wrote:
> On 2014-07-08 Atsuhito Kohda  wrote:
> > On Fri, 4 Jul 2014 20:09:52 +0200, Andreas Metzler wrote:
> 
> > > Looks like lynx-cur is missing a build-dependency on
> > > libgcrypt20-dev as a hotfix or better use gnutls_rnd() instead of
> > > gcry_randomize() and stop linking against gcrypt. (Totally untested,
> > > no guarantees patch attached.)
> 
> > I only added libgcrypt20-dev to B-D and built the package, then
> > it seems lynx works fine so I uploaded the package.  
> > But if your patch is necessary to fix the problem properly, 
> > please let me know.
> 
> Hello Atsuhito,
> 
> thanks for fixing the issue.
> 
> it is less a "necessary" than a "I think it is ugly". ;-) Afaict (but
> please take this with a grain of salt) lynx is only using a single
> gcrypt function, and gnutls would provide something equivalent. So by
> using the gnutls function the external dependency could be avoided.
> Imho this should be fixed upstream.

probably (at least, to ensure that the given function is present, etc).

-- 
Thomas E. Dickey 
http://invisible-island.net
ftp://invisible-island.net


signature.asc
Description: Digital signature

Bug#746589: marked as done (kdm: DBUS connection error after apt-get dist-upgrade (from deb.7.4))

[Debian Bug Tracking System]

Your message dated Wed, 9 Jul 2014 00:25:06 +0200
with message-id <20140708222506.gb4...@gnuservers.com.ar>
and subject line Re: Bug#746589: [kdm] Not enough information to work on this 
bug
has caused the Debian Bug report #746589,
regarding kdm: DBUS connection error after apt-get dist-upgrade (from deb.7.4)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
746589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kdm
Version: 4:4.8.4-6
Severity: grave
Justification: renders package unusable

Dear Maintainer,
on the clean install (debian 7.4.*):
gnome and other utils/pkgs worked best.
At some time i'm installed asterisk, that asks me distrib, that i hav'nt any 
more, and i was been need update system by apt-get dist-upgrade
After rebooting, gnome was stopped interract with mouse/keyboard (but utils 
interract at some case).
then i'm triyng >apt-get install kde
kde installed, but starting X with kde gives same result.
in /var/log/kdm.log i'm seen the next:
--- End Message ---
--- Begin Message ---
Control: severity -1 normal

Hello,

Unfortunately, we are not in a position to help with many unrelated issues as
are reported in this bug.

The original reporter had issues with their input (mouse and keyboard) before
installing KDE, and after that reported that KDE had the same issues. This
could be caused by any number of reasons, most likely hardware related. It's
impossible for us to do anything about it, since we can't reproduce this.

The second report seems to be quite a different problem. It's not clear at all
what the specific symptoms of this problem are. The fact that the partitions
were not allocated as desired is completely unrelated to KDE, kdm, X, etc.

If you have specific issues with a specific package, please open a new bug
describing a way to reproduce the problem (and please open one bug per issue).

Thanks.
-- 
"Inside every large problem is a small problem struggling to get out."
-- Hoare's Law of Large Problems
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature
--- End Message ---

Processed: kfreebsd-9: SCTP kernel memory disclosures (CVE-2014-3953)

[Debian Bug Tracking System]

Processing control commands:

> found -1 kfreebsd-9/9.2-2
Bug #754237 [src:kfreebsd-9] kfreebsd-9: SCTP kernel memory disclosures 
(CVE-2014-3953)
Marked as found in versions kfreebsd-9/9.2-2.

-- 
754237: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#754237: kfreebsd-9: SCTP kernel memory disclosures (CVE-2014-3953)

[Steven Chamberlain]

Package: src:kfreebsd-9
Version: 9.0-10+deb70.7
Severity: grave
Tags: security upstream
Control: found -1 kfreebsd-9/9.2-2

Hi,

FreeBSD-SA-14:17.kmem describes kernel memory disclosures in
SCTP control messages:

http://security.freebsd.org/advisories/FreeBSD-SA-14:17.kmem.asc
> [...] the process may be able to retrieve 2 bytes of kernel memory
> for all three control messages, plus 92 bytes for SCTP_SNDRCV and 76
> bytes for SCTP_EXTRCV.  If the local process is permitted to receive
> SCTP notification, a maximum of 112 bytes of kernel memory may be
> returned to userland.

I think this affects all our kernels including 8.3 and 9.0 in wheezy.

I'm not sure if SCTP must be configured by a superuser first, but for
now I'll assume any nonprivileged user might be able to exploit this.

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

Kernel: kFreeBSD 9.0-2-amd64-xenhvm-ipsec
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


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

Bug#747309: marked as done (CVE-2014-0191)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jul 2014 23:04:21 +
with message-id 
and subject line Bug#747309: fixed in libxml2 2.9.1+dfsg1-4
has caused the Debian Bug report #747309,
regarding CVE-2014-0191
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
747309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libxml2
Version: 2.9.1+dfsg1-3
Severity: grave
Tags: security

Hi,
from oss-security. This was assigned CVE-2014-0191

| It was discovered that libxml2, a library providing support to read,
| modify and write XML files, incorrectly performs entity substituton in
| the doctype prolog, even if the application using libxml2 disabled any
| entity substitution. A remote attacker could provide a
| specially-crafted XML file that, when processed, would lead to the
| exhaustion of CPU and memory resources or file descriptors.
| 
| This issue was discovered by Daniel Berrange of Red Hat.

Fix:
https://git.gnome.org/browse/libxml2/commit/?id=9cd1c3cfbd32655d60572c0a413e017260c854df

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: libxml2
Source-Version: 2.9.1+dfsg1-4

We believe that the bug you reported is fixed in the latest version of
libxml2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 747...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aron Xu  (supplier of updated libxml2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 09 Jul 2014 05:40:15 +0800
Source: libxml2
Binary: libxml2 libxml2-utils libxml2-utils-dbg libxml2-dev libxml2-dbg 
libxml2-doc python-libxml2 python-libxml2-dbg
Architecture: source amd64 all
Version: 2.9.1+dfsg1-4
Distribution: unstable
Urgency: low
Maintainer: Debian XML/SGML Group 
Changed-By: Aron Xu 
Description:
 libxml2- GNOME XML library
 libxml2-dbg - Debugging symbols for the GNOME XML library
 libxml2-dev - Development files for the GNOME XML library
 libxml2-doc - Documentation for the GNOME XML library
 libxml2-utils - XML utilities
 libxml2-utils-dbg - XML utilities (debug extension)
 python-libxml2 - Python bindings for the GNOME XML library
 python-libxml2-dbg - Python bindings for the GNOME XML library (debug 
extension)
Closes: 738080 742350 747309 753005
Changes:
 libxml2 (2.9.1+dfsg1-4) unstable; urgency=low
 .
   [ Christian Svensson ]
   * Do not build-depend on readline (Closes: #742350)
 .
   [ Daniel Schepler ]
   * Patch to bootstrap without python (Closes: #738080)
 .
   [ Helmut Grohne ]
   * Drop unneeded B-D on perl and binutils (Closes: #753005)
 .
   [ Adam Conrad ]
   * Actually run dh_autoreconf, which the old/new mixed rules file misses.
 .
   [ Matthias Klose ]
   * Add patch to fix python multiarch issue
   * Allow the package to cross-build by tweaking B-Ds on python
   * Set PYTHON_LIBS for cross builds
 .
   [ Aron Xu ]
   * Use correct $CC
   * Configure udeb without python
   * New round of cherry-picking upstream fixes
 - Includes fixes for CVE-2014-0191 (Closes: #747309).
   * Call prename with -vf
   * Require python-all-dev (>= 2.7.5-5~)
   * Bump std-ver: 3.9.4 -> 3.9.5, no change
Checksums-Sha1:
 a7101936e0888d1bb4a7087a5edf5db67ef22092 2220 libxml2_2.9.1+dfsg1-4.dsc
 6ceda384b5ad36bc187cb55fd684f97825208c5d 32980 
libxml2_2.9.1+dfsg1-4.debian.tar.xz
 5cf24aa29f6ac7b1b2b47dad9f5fdcf6cf41a79e 797136 libxml2_2.9.1+dfsg1-4_amd64.deb
 a416d9caa4a578e01d59338e6e7c4922d73c4936 90582 
libxml2-utils_2.9.1+dfsg1-4_amd64.deb
 d787620b73ac7c1ba9793a55376fe98684f8a6e8 120646 
libxml2-utils-dbg_2.9.1+dfsg1-4_amd64.deb
 46e4276f39c0db656b24044ca1f8ec1def7228c6 689202 
libxml2-dev_2.9.1+dfsg1-4_amd64.deb
 ae50b5fb8d9b2770372d21d18dc4e243c86c5635 1221708 
libxml2-dbg_2.9.1+dfsg1-4_amd64.deb
 e698d9b5413e08901c2ba62dbe24a3071cf8275b 810830 
libxml2-doc_2.9.1+dfsg1-4_all.deb
 2679a421b2f54c1022d847870b7b41fb046e2256 189772 
python-libxml2_2.9.1+dfsg1-4_amd64.deb
 90f13f94c208bd453a2abbec2bf733a986811057 310280 
python-libxml2-dbg_2.9.1+dfsg1-4_amd64.deb
Checksums-Sha256:
 f2058399dd598168a9edd07efef21d3f216dd7a9e7a85a4cbbef8068c9fc2b8c 2220 
libxml2_2.9

Bug#754199: [Pkg-ime-devel] Bug#754199: librime: FTBFS on armel: std::future is broken

[Aron Xu]

On Wed, Jul 9, 2014 at 12:25 AM, Emilio Pozuelo Monfort
 wrote:
> Source: librime
> Severity: serious
> Control: block 753079 by -1
>
> librime failed to build on armel because of the std::future brokenness on
> that platform, see #727621.
>
> https://buildd.debian.org/status/fetch.php?pkg=librime&arch=armel&ver=1.1%2Bdfsg-2&stamp=1404754412
>
> This is blocking the librime transition.
>
> Emilio

In such case, do you mind us uploading new upstream releases of
fcitx-rime/ibus-rime into unstable right now?


-- 
Regards,
Aron Xu


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

Bug#754218: boot hangs forever on LSB job "raise network interfaces"

[Michael Biebl]

Am 08.07.2014 22:50, schrieb Stefano Zacchiroli:
> Now the questions/comments:
> 
> - I've had that script since ever, basically, and it used to work fine
>   in the past, both before and after switching to systemd as init. I'm
>   not sure why/when it stopped working.
> 
> - As a mere user, the above script is perfectly reasonable, I *do* want
>   to restart my firewall every time my network interface is brought up,
>   and AFAICT I'm using the right "API" to do so.

I had a look at the shorewall(6) init script. It has

# Required-Start:$network $remote_fs


Now, $network is provided by the networking init script. As long as this
init script is not fully started, $network (or network.target) is not
yet available.

You've started shorewall as part of the if-up up, when $network is not
yet available, thus there is a dead lock.

So, it's actually exactly the same problem as with the NFS hook.


sysvinit doesn't bother, as it doesn't consider such dynamic
dependencies during runtime whereas systemd does.

What has changed is, that systemd_204-9 gained support for LSB system
facilities, i.e. now it understands that /etc/init.d/networking provides
$network.

This is most likely the reason you didn't see it in the past.

So, what to do about this: I'd say it's a bug to (re)start a SysV init
script from an if-up.d hook without actually checking if the service is
actually already runnig.
Because you simply disregard any dependencies which have been specified
in the LSB header.

It's problematic in general to (re)start SysV init scripts from any hook
(if-up.d, dhcp etc), since you can't ensure at that point that its
dependencies are actually all available.

I personally would consider this a local (mis)configuration which simply
didn't show up with sysvinit which only computes dependencies at install
time and only between init scripts in /etc/rc?.d/



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



signature.asc
Description: OpenPGP digital signature

Bug#754218: boot hangs forever on LSB job "raise network interfaces"

[Michael Biebl]

Am 09.07.2014 01:14, schrieb Michael Biebl:
> So, what to do about this: I'd say it's a bug to (re)start a SysV init
> script from an if-up.d hook without actually checking if the service is
> actually already runnig.
> Because you simply disregard any dependencies which have been specified
> in the LSB header.

You'd need something like systemd's try-restart, i.e. only restart a
service if already running.

Something like
service shorewall status && service shorewall restart

should have a similar effect.

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



signature.asc
Description: OpenPGP digital signature

Bug#754199: Bug#753079: [Pkg-ime-devel] Bug#754199: librime: FTBFS on armel: std::future is broken

[Emilio Pozuelo Monfort]

On 09/07/14 01:13, Aron Xu wrote:
> On Wed, Jul 9, 2014 at 12:25 AM, Emilio Pozuelo Monfort
>  wrote:
>> Source: librime
>> Severity: serious
>> Control: block 753079 by -1
>>
>> librime failed to build on armel because of the std::future brokenness on
>> that platform, see #727621.
>>
>> https://buildd.debian.org/status/fetch.php?pkg=librime&arch=armel&ver=1.1%2Bdfsg-2&stamp=1404754412
>>
>> This is blocking the librime transition.
>>
>> Emilio
> 
> In such case, do you mind us uploading new upstream releases of
> fcitx-rime/ibus-rime into unstable right now?

Looks like this is going to be stuck for a while, so that should be alright.

Emilio


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

Bug#754218: boot hangs forever on LSB job "raise network interfaces"

[Michael Biebl]

Am 09.07.2014 01:14, schrieb Michael Biebl:
> Am 08.07.2014 22:50, schrieb Stefano Zacchiroli:
>> Now the questions/comments:
>>
>> - I've had that script since ever, basically, and it used to work fine
>>   in the past, both before and after switching to systemd as init. I'm
>>   not sure why/when it stopped working.
>>
>> - As a mere user, the above script is perfectly reasonable, I *do* want
>>   to restart my firewall every time my network interface is brought up,
>>   and AFAICT I'm using the right "API" to do so.

Running within the context of an if-up.d hook you make an explicit
assumption that $network is already provided, which is probably reasonable.

Strictly speaking though, the LSB $network facility is defined in
/etc/insserv.conf when the networking (or the old ifupdown) SysV init
script has been fully started, which is not the case during the inital
start of that script.

I'm not sure how to address this. Either the hooks are fixed to not make
this assumption, or the "bring network up" phase proving $network and
"run if-up.d hooks" are split into two different SysV init scripts.

The latter is probably not feasable.






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



signature.asc
Description: OpenPGP digital signature

Bug#753488: marked as done (cairo-dock-plug-ins: FTBFS in s390x because of uninstallable build-depend libgnutls-dev)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jul 2014 23:34:21 +
with message-id 
and subject line Bug#753488: fixed in cairo-dock-plug-ins 3.3.2-3.2
has caused the Debian Bug report #753488,
regarding cairo-dock-plug-ins: FTBFS in s390x because of uninstallable 
build-depend libgnutls-dev
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
753488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cairo-dock-plug-ins
Severity: serious

Hi maintainers,

Build logs shows subject's problem:
https://buildd.debian.org/status/package.php?p=cairo-dock-plug-ins

Switching from libgnutls-dev to libgnutls28-dev in Build-Depends 
should fix this, though I've not checked it :)

best regards,

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

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: cairo-dock-plug-ins
Source-Version: 3.3.2-3.2

We believe that the bug you reported is fixed in the latest version of
cairo-dock-plug-ins, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 753...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emilio Pozuelo Monfort  (supplier of updated 
cairo-dock-plug-ins package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 08 Jul 2014 22:44:54 +0200
Source: cairo-dock-plug-ins
Binary: cairo-dock-plug-ins cairo-dock-plug-in-data 
cairo-dock-alsamixer-plug-in cairo-dock-animated-icons-plug-in 
cairo-dock-cairo-penguin-plug-in cairo-dock-clipper-plug-in 
cairo-dock-clock-plug-in cairo-dock-dbus-plug-in 
cairo-dock-dbus-plug-in-interface-python cairo-dock-dbus-plug-in-interface-ruby 
cairo-dock-dbus-plug-in-interface-mono cairo-dock-dbus-plug-in-interface-vala 
cairo-dock-desklet-rendering-plug-in cairo-dock-dialog-rendering-plug-in 
cairo-dock-drop-indicator-plug-in cairo-dock-dustbin-plug-in 
cairo-dock-icon-effect-plug-in cairo-dock-illusion-plug-in 
cairo-dock-logout-plug-in cairo-dock-motion-blur-plug-in 
cairo-dock-netspeed-plug-in cairo-dock-powermanager-plug-in 
cairo-dock-quick-browser-plug-in cairo-dock-rendering-plug-in 
cairo-dock-shortcuts-plug-in cairo-dock-showdesktop-plug-in 
cairo-dock-showmouse-plug-in cairo-dock-slider-plug-in cairo-dock-stack-plug-in 
cairo-dock-switcher-plug-in cairo-dock-systray-plug-in cairo-dock-tomboy-plug-in
 cairo-dock-toons-plug-in cairo-dock-weather-plug-in cairo-dock-wifi-plug-in 
cairo-dock-xgamma-plug-in cairo-dock-gmenu-plug-in 
cairo-dock-keyboard-indicator-plug-in cairo-dock-terminal-plug-in 
cairo-dock-mail-plug-in cairo-dock-rssreader-plug-in 
cairo-dock-system-monitor-plug-in cairo-dock-dnd2share-plug-in 
cairo-dock-musicplayer-plug-in cairo-dock-gnome-integration-plug-in 
cairo-dock-kde-integration-plug-in cairo-dock-xfce-integration-plug-in 
cairo-dock-weblets-plug-in cairo-dock-folders-plug-in 
cairo-dock-impulse-plug-in cairo-dock-messaging-menu-plug-in 
cairo-dock-recent-events-plug-in
 cairo-dock-remote-control-plug-in
Architecture: source all amd64
Version: 3.3.2-3.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Cairo-dock Maintainers 

Changed-By: Emilio Pozuelo Monfort 
Description:
 cairo-dock-alsamixer-plug-in - Cairo-dock - Alsamixer plug-in
 cairo-dock-animated-icons-plug-in - Cairo-dock - Animated icons plug-in
 cairo-dock-cairo-penguin-plug-in - Cairo-dock - Cairo-Penguin plug-in
 cairo-dock-clipper-plug-in - Cairo-dock - Clipper plug-in
 cairo-dock-clock-plug-in - Cairo-dock - Clock plug-in
 cairo-dock-dbus-plug-in - Cairo-dock - Dbus plug-in
 cairo-dock-dbus-plug-in-interface-mono - Cairo-dock - library of D-Bus 
interface for mono
 cairo-dock-dbus-plug-in-interface-python - Cairo-dock - library of D-Bus 
interface for Python
 cairo-dock-dbus-plug-in-interface-ruby - Cairo-dock - library of D-Bus 
interface for ruby
 cairo-dock-dbus-plug-in-interface-vala - Cairo-dock - library of D-Bus 
interface for vala
 cairo-dock-desklet-rendering

Bug#754218: boot hangs forever on LSB job "raise network interfaces"

[Michael Biebl]

Am 09.07.2014 01:28, schrieb Michael Biebl:

> Running within the context of an if-up.d hook you make an explicit
> assumption that $network is already provided, which is probably reasonable.
> 
> Strictly speaking though, the LSB $network facility is defined in
> /etc/insserv.conf when the networking (or the old ifupdown) SysV init
> script has been fully started, which is not the case during the inital
> start of that script.
> 
> I'm not sure how to address this. Either the hooks are fixed to not make
> this assumption, or the "bring network up" phase proving $network and
> "run if-up.d hooks" are split into two different SysV init scripts.
> 
> The latter is probably not feasable.

And it doesn't address the issue that the service which is (re)started
from the hook has other dependencies.

Say the shorewall service has other dependencies like e.g. mysql,
because it stores its rules there (yeah, I made that up :-) ). If you
now restart shorewall from the if-up.d hook it will be started during
rcS (i.e. early boot) completely disregarding the dependency on mysql.




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



signature.asc
Description: OpenPGP digital signature

Bug#753488: cairo-dock-plug-ins: FTBFS in s390x because of uninstallable build-depend libgnutls-dev

[Emilio Pozuelo Monfort]

Dear maintainer,

I have NMU'ed cairo-dock-plug-ins switching it to gnutls28 as its build
dependencies were uninstallable on all arches, preventing it from being rebuilt
and finishing the libetpan transition. The nmu diff is attached.

Regards,
Emilio
diff -Nru cairo-dock-plug-ins-3.3.2/debian/changelog cairo-dock-plug-ins-3.3.2/debian/changelog
--- cairo-dock-plug-ins-3.3.2/debian/changelog	2014-04-26 17:57:23.0 +0200
+++ cairo-dock-plug-ins-3.3.2/debian/changelog	2014-07-08 22:44:57.0 +0200
@@ -1,3 +1,11 @@
+cairo-dock-plug-ins (3.3.2-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build depend on libgnutls28-dev to make the package buildable
+again. Closes: #753488.
+
+ -- Emilio Pozuelo Monfort   Tue, 08 Jul 2014 22:44:54 +0200
+
 cairo-dock-plug-ins (3.3.2-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru cairo-dock-plug-ins-3.3.2/debian/control cairo-dock-plug-ins-3.3.2/debian/control
--- cairo-dock-plug-ins-3.3.2/debian/control	2014-04-26 17:52:42.0 +0200
+++ cairo-dock-plug-ins-3.3.2/debian/control	2014-07-08 22:21:54.0 +0200
@@ -20,7 +20,7 @@
  libglib2.0-dev,
  libglu1-mesa-dev | libglu-dev,
  libgnome-menu-3-dev,
- libgnutls-dev,
+ libgnutls28-dev,
  libgtk-3-dev,
  libical-dev,
  libido3-0.1-dev,

Bug#753488: [Pkg-cairo-dock-devel] Bug#753488: cairo-dock-plug-ins: FTBFS in s390x because of uninstallable build-depend libgnutls-dev

[Nobuhiro Iwamatsu]

Hi,

Please upload.
Thanks for your work.

Best regards,
  Nobuhiro

2014-07-09 8:39 GMT+09:00 Emilio Pozuelo Monfort :
> Dear maintainer,
>
> I have NMU'ed cairo-dock-plug-ins switching it to gnutls28 as its build
> dependencies were uninstallable on all arches, preventing it from being 
> rebuilt
> and finishing the libetpan transition. The nmu diff is attached.
>
> Regards,
> Emilio
>
> ___
> Pkg-cairo-dock-devel mailing list
> pkg-cairo-dock-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-cairo-dock-devel



-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6


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

Bug#754237: RFC: disable SCTP in Debian's kFreeBSD?

[Steven Chamberlain]

Hi,

SCTP, an IP transport protocol, is enabled by default in upstream
FreeBSD's GENERIC config:

> # SCTP is a NEW transport protocol defined by
> # RFC2960 updated by RFC3309 and RFC3758 [...]
> options SCTP

(Although RFC2960 was published in 2000, so it is not so new any more.)
 To date I've never configured SCTP on any servers before, or knowingly
used it on any other systems.  "The SCTP web site", sctp.org, had no
news entries after 2004 and seems to have gone offline.

Linux has SCTP support.  Debian has some command-line tools for that and
a library, each with around 5000 popcon users:
https://qa.debian.org/popcon.php?package=lksctp-tools

FreeBSD's SCTP support seems to be a reference implementation by Cisco.
 Another implementation by the KAME Project had an OpenBSD port, but
seems that never quite made it into the tree.

Support for SCTP seems notably missing from Microsoft Windows:
https://stackoverflow.com/questions/2153700

There exists some backward-compatibility mechanism to run SCTP over UDP
sockets if that's needed.


In wheezy, we've patched a kernel memory disclosure vulnerability that
was remotely exploitable if SCTP sockets were used. (CVE-2013-5209)

STABLE-9 quietly fixed jailed processes being able to see or use SCTP
source addresses that should not have been available to them:
http://svnweb.freebsd.org/base?view=revision&revision=267674

We now have a local kernel memory disclosure bug (CVE-2014-3953) - I'm
unsure if SCTP must be in use to exploit it - but the patch will not
apply cleanly to 9.0 and 8.3 that we have in wheezy, so would need
backporting by us.


I wonder if it is worth it?  Is SCTP really used by us, even close to
working or desirable to anyone?

A search for Debian packages with "sctp" in the name shows binary
packages that have only built on linux-any arches:
https://packages.debian.org/search?keywords=sctp

I've used Debian Code Search to look for potential users:
http://codesearch.debian.net/search?q=include.*sctp\.h
and found these:
* openssl - is disabled by OPENSSL_NO_SCTP, which is default
* iceweasel/icedove - kfreebsd buildd logs don't mention it, linux does
* libav - I don't see any mention in the buildd log
* chromium-browser - wasn't in wheezy
* openjdk-7 - wasn't in wheezy

* about a dozen other packages I thought were less interesting than the
above, didn't bother to check if SCTP was really implemented/supported

* SCTP was mentioned in lots of network diagnostic tools e.g. wireshark,
nmap, ns2 - but what is the point of that if not using the protocol for
anything?


So I'm obviously asking here - could we just drop SCTP from the default
kernel config?  In jessie/sid?  Even in wheezy-security?

Thanks for reading!
Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


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

Processed: unmerging 752386

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unmerge 752386
Bug #752386 [src:bzr] bzr: commit to sftp repo is broken
Bug #750347 [src:bzr] FTBFS: incompatibilities in new paramiko breaks sftp 
support
Disconnected #752386 from all other report(s).
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
750347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750347
752386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Processed: forcibly merging 750347 752386

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 750347 752386
Bug #750347 [src:bzr] FTBFS: incompatibilities in new paramiko breaks sftp 
support
Bug #752386 [src:bzr] bzr: commit to sftp repo is broken
Merged 750347 752386
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
750347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750347
752386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#754244: guncat: FTBFS: tput: No value for $TERM and no -T specified

[Aaron M. Ucko]

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

Builds of guncat in minimal environments (as on the autobuilders) have
been failing:

  ./build program
  touch version.cc
  gcc -E VERSION.h | grep -v '#' | sed 's/\"//g' > release.yo
  icmbuild program 
  tput clear
  tput: No value for $TERM and no -T specified
  system - failure of system call (status 512)
  system - failure of system call (status 512)
  system - failure of system call (status 256)
  make: *** [build-stamp] Error 1

The problem appears to be that icmconf defines CLS, enabling a dubious
(at the very least, overly brittle) feature of icmbuild.  Could you
please take a look?

Thanks!


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

Bug#754249: fglrx-driver: incompatible with xserver 1.16 (xorg-video-abi-18)

[Julien Cristau]

Source: fglrx-driver
Version: 1:14.4.2-1
Severity: serious
Justification: uninstallable
Tags: upstream

Hi,

fglrx needs an update to be compatible with new xserver.

Cheers,
Julien


signature.asc
Description: Digital signature

Processed: retitle 751082 to nvidia-graphics-drivers: incompatible with xserver 1.16 ..., cloning 751082 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 751082 nvidia-graphics-drivers: incompatible with xserver 1.16
Bug #751082 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: Please 
package 337.25 in experimental as it should support Xorg 1.16.
Changed Bug title to 'nvidia-graphics-drivers: incompatible with xserver 1.16' 
from 'nvidia-graphics-drivers: Please package 337.25 in experimental as it 
should support Xorg 1.16.'
> severity 751082 serious
Bug #751082 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: incompatible 
with xserver 1.16
Severity set to 'serious' from 'important'
> clone 751082 -1 -2
Bug #751082 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: incompatible 
with xserver 1.16
Bug 751082 cloned as bugs 754250-754251
754250 was not blocked by any bugs.
754250 was blocking: 753781
Added blocking bug(s) of 754250: 753781
754251 was not blocked by any bugs.
754251 was blocking: 753781
Added blocking bug(s) of 754251: 753781
> reassign -1 nvidia-graphics-drivers-legacy-173xx 173.14.39-2
Bug #754250 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: incompatible 
with xserver 1.16
Bug reassigned from package 'src:nvidia-graphics-drivers' to 
'nvidia-graphics-drivers-legacy-173xx'.
Ignoring request to alter found versions of bug #754250 to the same values 
previously set
Ignoring request to alter fixed versions of bug #754250 to the same values 
previously set
Bug #754250 [nvidia-graphics-drivers-legacy-173xx] nvidia-graphics-drivers: 
incompatible with xserver 1.16
There is no source info for the package 'nvidia-graphics-drivers-legacy-173xx' 
at version '173.14.39-2' with architecture ''
Unable to make a source version for version '173.14.39-2'
Marked as found in versions 173.14.39-2.
> reassign -2 nvidia-graphics-drivers-legacy-304xx 304.121-1
Bug #754251 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: incompatible 
with xserver 1.16
Bug reassigned from package 'src:nvidia-graphics-drivers' to 
'nvidia-graphics-drivers-legacy-304xx'.
Ignoring request to alter found versions of bug #754251 to the same values 
previously set
Ignoring request to alter fixed versions of bug #754251 to the same values 
previously set
Bug #754251 [nvidia-graphics-drivers-legacy-304xx] nvidia-graphics-drivers: 
incompatible with xserver 1.16
There is no source info for the package 'nvidia-graphics-drivers-legacy-304xx' 
at version '304.121-1' with architecture ''
Unable to make a source version for version '304.121-1'
Marked as found in versions 304.121-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
751082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751082
754250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754250
754251: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#749028:

[Ludovic Lebègue]

reassign 749028 policykit-1 0.112-1
fixed 749028 0.112-2
thanks



The problem was fixed after upgrading in experimental :


Here is the apt log

Start-Date: 2014-07-09  08:12:26

Commandline: apt upgrade -t experimental
Install: libcdr-0.0-0:amd64 (0.0.16-1, automatic),
libreoffice-style-crystal:amd64 (4.3.0~rc2-1, automatic),
libreoffice-style-oxygen:amd64 (4.3.0~rc2-1, automatic),
libreoffice-style-sifr:amd64 (4.3.0~rc2-1, automatic),
libreoffice-style-hicontrast:amd64 (4.3.0~rc2-1, automatic),
libvisio-0.0-0:amd64 (0.0.31-1+b1, automatic),
libpackage-constants-perl:amd64 (0.04-1, automatic)

Upgrade: exim4-base:amd64 (4.83~RC2-1, 4.83~RC3-1),
p11-kit-modules:amd64 (0.20.2-5, 0.20.3-1), libreoffice-l10n-en-gb:amd64
(4.3.0~rc1-1, 4.3.0~rc2-1), libp11-kit0:amd64 (0.20.2-5, 0.20.3-1),
libreoffice-sdbc-hsqldb:amd64 (4.3.0~rc1-1, 4.3.0~rc2-1),
libreoffice-style-tango:amd64 (4.3.0~rc1-1, 4.3.0~rc2-1), ure:amd64
(4.3.0~rc1-1, 4.3.0~rc2-1), libreoffice-writer:amd64 (4.3.0~rc1-1,
4.3.0~rc2-1), libreoffice-draw:amd64 (4.3.0~rc1-1, 4.3.0~rc2-1),
libreoffice-core:amd64 (4.3.0~rc1-1, 4.3.0~rc2-1), policykit-1:amd64
(0.112-1, 0.112-2), libreoffice-style-galaxy:amd64 (4.3.0~rc1-1,
4.3.0~rc2-1), libreoffice-evolution:amd64 (4.3.0~rc1-1, 4.3.0~rc2-1),
libreoffice-base-core:amd64 (4.3.0~rc1-1, 4.3.0~rc2-1),
libreoffice-officebean:amd64 (4.3.0~rc1-1, 4.3.0~rc2-1),
libreoffice-base:amd64 (4.3.0~rc1-1, 4.3.0~rc2-1), exim4:amd64
(4.83~RC2-1, 4.83~RC3-1), p11-kit:amd64 (0.20.2-5, 0.20.3-1),
xserver-xorg-input-evdev:amd64 (2.8.2-1+b2, 2.9.0-1), bluez:amd64
(5.19-1~exp0, 5.21-1~exp0), libreoffice-gtk:amd64 (4.3.0~rc1-1,
4.3.0~rc2-1), libreoffice-java-common:amd64 (4.3.0~rc1-1, 4.3.0~rc2-1),
libpolkit-gobject-1-0:amd64 (0.112-1, 0.112-2),
xserver-xorg-video-modesetting:amd64 (0.9.0-1+b1, 0.9.0-1+exp1),
libreoffice-base-drivers:amd64 (4.3.0~rc1-1, 4.3.0~rc2-1),
libreoffice-impress:amd64 (4.3.0~rc1-1, 4.3.0~rc2-1), uno-libs3:amd64
(4.3.0~rc1-1, 4.3.0~rc2-1), libreoffice-avmedia-backend-gstreamer:amd64
(4.3.0~rc1-1, 4.3.0~rc2-1), fonts-opensymbol:amd64 (102.6
+LibO4.3.0~rc1-1, 102.6+LibO4.3.0~rc2-1), libpolkit-agent-1-0:amd64
(0.112-1, 0.112-2), libreoffice-sdbc-firebird:amd64 (4.3.0~rc1-1,
4.3.0~rc2-1), inkscape:amd64 (0.91~pre0-1, 0.91~pre1-1),
python3-uno:amd64 (4.3.0~rc1-1, 4.3.0~rc2-1), libreoffice-math:amd64
(4.3.0~rc1-1, 4.3.0~rc2-1), libreoffice:amd64 (4.3.0~rc1-1,
4.3.0~rc2-1), libp11-kit-dev:amd64 (0.20.2-5, 0.20.3-1),
libreoffice-gnome:amd64 (4.3.0~rc1-1, 4.3.0~rc2-1),
exim4-daemon-light:amd64 (4.83~RC2-1, 4.83~RC3-1), libbluetooth3:amd64
(5.19-1~exp0, 5.21-1~exp0), libreoffice-report-builder-bin:amd64
(4.3.0~rc1-1, 4.3.0~rc2-1), libreoffice-help-en-us:amd64 (4.3.0~rc1-1,
4.3.0~rc2-1), libreoffice-common:amd64 (4.3.0~rc1-1, 4.3.0~rc2-1),
exim4-config:amd64 (4.83~RC2-1, 4.83~RC3-1), insserv:amd64 (1.14.0-5,
1.16.0-5), libreoffice-calc:amd64 (4.3.0~rc1-1, 4.3.0~rc2-1)
End-Date: 2014-07-09  08:14:05

It is unlikely related to gnome-shell as it was not upgraded.
libreoffice (and uno, ure), inkscape, exim4, bluez, libbluetooth3,
fonts-opensymbol, libvisio, libpackages-constant-perl would be far
fetched candidates.

Removing them from history there is still left : 

Start-Date: 2014-07-09  08:12:26
Commandline: apt upgrade -t experimental

Upgrade: p11-kit-modules:amd64 (0.20.2-5, 0.20.3-1),  libp11-kit0:amd64
(0.20.2-5, 0.20.3-1),  policykit-1:amd64 (0.112-1, 0.112-2),
p11-kit:amd64 (0.20.2-5, 0.20.3-1), libpolkit-gobject-1-0:amd64
(0.112-1, 0.112-2), libpolkit-agent-1-0:amd64 (0.112-1, 0.112-2),
libp11-kit-dev:amd64 (0.20.2-5, 0.20.3-1), insserv:amd64 (1.14.0-5,
1.16.0-5)
End-Date: 2014-07-09  08:14:05


My bet is on policykit-1

Perhaps I'm wrong. Please reassign accordingly.

Regards
Ludovic







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

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 749028 policykit-1 0.112-1
Bug #749028 [gnome-shell] gnome-shell : Authentication pop-up not displayed
Bug reassigned from package 'gnome-shell' to 'policykit-1'.
No longer marked as found in versions gnome-shell/3.12.2-1, 
gnome-shell/3.12.2-2, and gnome-shell/3.8.4-8.1.
Ignoring request to alter fixed versions of bug #749028 to the same values 
previously set
Bug #749028 [policykit-1] gnome-shell : Authentication pop-up not displayed
Marked as found in versions policykit-1/0.112-1.
> fixed 749028 0.112-2
Bug #749028 [policykit-1] gnome-shell : Authentication pop-up not displayed
Marked as fixed in versions policykit-1/0.112-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
749028: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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