Processed: Fwd: Bug#760810: [quassel-client] quasselclient fails to start

2014-09-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 760810 normal
Bug #760810 [quassel-client] [quassel-client] quasselclient fails to start
Severity set to 'normal' from 'grave'
 quit
Stopping processing here.

Please contact me if you need assistance.
-- 
760810: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760810
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#760810: [quassel-client] quasselclient fails to start

2014-09-23 Thread Thomas Müller
Hi,

I cannot reproduce this on my system which is testing/sid.

Can you please retest with the latest phonon packages, because meanwhile 
4:4.8.0-1 arrived in testing?

Thanks a lot,

Thomas


Am Montag, den 08.09.2014 um 6:01 schrieb Keshav Kini:
 Package: quassel-client
 Version: 0.10.0-2
 Severity: grave
 
 --- Please enter the report below this line. ---
 
 `quasselclient` recently fails to start on debian sid:
 
 fs@erdos ~ $ quasselclient
 
 (quasselclient:12158): GLib-GObject-WARNING **: cannot register existing
 type 'GstObject'
 
 (quasselclient:12158): GLib-CRITICAL **: g_once_init_leave: assertion
 'result != 0' failed
 
 (quasselclient:12158): GLib-GObject-CRITICAL **: g_type_register_static:
 assertion 'parent_type  0' failed
 
 (quasselclient:12158): GLib-CRITICAL **: g_once_init_leave: assertion
 'result != 0' failed
 
 (quasselclient:12158): GStreamer-CRITICAL **:
 gst_plugin_feature_get_name: assertion 'GST_IS_PLUGIN_FEATURE (feature)'
 failed
 ^\Quit
 
 Googling assertion 'GST_IS_PLUGIN_FEATURE (feature)' failed yields a
 bunch of similar-sounding failures of other programs, seemingly related
 to phonon integration with gstreamer, or something.
 
 --- System information. ---
 Architecture: amd64
 Kernel:   Linux 3.14-2-amd64
 
 Debian Release: jessie/sid
   500 unstableftp.us.debian.org
   500 sid linux.dropbox.com
 
 --- Package information. ---
 Depends(Version) | Installed
 -+-==
 libc6  (= 2.14) | 2.19-10
 libdbusmenu-qt2   (= 0.3.2) | 0.9.2-1
 libgcc1 (= 1:4.1.1) | 1:4.9.1-12
 libindicate-qt1   (= 0.2.5) | 0.2.5.91-5
 libphonon4  (= 4:4.2.0) | 4:4.7.2-1
 libqt4-dbus (= 4:4.6.1) | 4:4.8.6+git64-g5dc8b2b+dfsg-2
 libqt4-network  (= 4:4.6.1) | 4:4.8.6+git64-g5dc8b2b+dfsg-2
 libqt4-xmlpatterns  (= 4:4.5.3) | 4:4.8.6+git64-g5dc8b2b+dfsg-2
 libqtcore4  (= 4:4.8.0) | 4:4.8.6+git64-g5dc8b2b+dfsg-2
 libqtgui4   (= 4:4.8.0) | 4:4.8.6+git64-g5dc8b2b+dfsg-2
 libqtwebkit4   (= 2.1.0~2011week13) | 2.3.2.dfsg-3
 libstdc++6(= 4.4.0) | 4.9.1-12
 phonon   | 4:4.7.2-1
 zlib1g  (= 1:1.1.4) | 1:1.2.8.dfsg-2
 quassel-data(= 0.10.0-2) | 0.10.0-2
 dbus-x11 | 1.8.6-2
 gawk | 1:4.1.1+dfsg-1
 
 
 Package's Recommends field is empty.
 
 Package's Suggests field is empty.
 


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



Bug#740942: [samba] /etc/init.d/samba forbit systemd shutdown system

2014-09-23 Thread Cesare Leonardi
Package: samba
Version: 2:4.1.11+dfsg-1
Followup-For: Bug #740942

I'm experiencing the same problem: 5 minute to shutdown samba service
and the same if i try to stop it on the command line.
I believed it was related to the fact that i use samba also to login in
an active domain but this bug report makes me think it could be
unrelated.

I'm not 100% sure, but i think i'm experiencing this since the latest
upgrade to systemd 215-4.

From this bug report i still haven't get what is the reason for this
delay and i'm currently unable to workaround it.

Let me know if you need any other infos, config file or else.

Cesare.


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

Kernel: Linux 3.16-2-amd64 (SMP w/2 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 samba depends on:
ii  adduser  3.113+nmu3
ii  dpkg 1.17.13
ii  libasn1-8-heimdal1.6~rc2+dfsg-8
ii  libbsd0  0.7.0-2
ii  libc62.19-11
ii  libcomerr2   1.42.12-1
ii  libhdb9-heimdal [heimdal-hdb-api-8]  1.6~rc2+dfsg-8
ii  libkdc2-heimdal  1.6~rc2+dfsg-8
ii  libkrb5-26-heimdal   1.6~rc2+dfsg-8
ii  libldb1  1:1.1.17-1
ii  libpam-modules   1.1.8-3.1
ii  libpam-runtime   1.1.8-3.1
ii  libpopt0 1.16-10
ii  libpython2.7 2.7.8-7
ii  libroken18-heimdal   1.6~rc2+dfsg-8
ii  libtalloc2   2.1.1-2
ii  libtdb1  1.3.0-1.1
ii  libtevent0   0.9.21-1
ii  lsb-base 4.1+Debian13
ii  multiarch-support2.19-11
ii  procps   1:3.3.9-7
ii  python   2.7.8-1
ii  python-dnspython 1.12.0-1
ii  python-ntdb  1.0-5
ii  python-samba 2:4.1.11+dfsg-1
pn  python2.7:anynone
ii  samba-common 2:4.1.11+dfsg-1
ii  samba-common-bin 2:4.1.11+dfsg-1
ii  samba-dsdb-modules   2:4.1.11+dfsg-1
ii  samba-libs   2:4.1.11+dfsg-1
ii  tdb-tools1.3.0-1.1
ii  update-inetd 4.43

Versions of packages samba recommends:
ii  attr   1:2.4.47-2
ii  logrotate  3.8.7-1
ii  samba-vfs-modules  2:4.1.11+dfsg-1

Versions of packages samba suggests:
ii  bind9  1:9.9.5.dfsg-4
ii  bind9utils 1:9.9.5.dfsg-4
pn  ctdb   none
pn  ldb-tools  none
ii  ntp1:4.2.6.p5+dfsg-3.1
pn  smbldap-tools  none
ii  winbind2:4.1.11+dfsg-1

-- debconf information:
  samba-common/title:
  samba/run_mode: daemons


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



Bug#762529: bordeaux-threads: maintainer address bounces

2014-09-23 Thread Ansgar Burchardt
Source: bordeaux-threads
Version: 0.8.3-1
Severity: serious
X-Debbugs-Cc: d...@tapoueh.org

[ CCed last uploader. ]

The maintainer address bounces, see below.

Ansgar

Mail Delivery System mailer-dae...@muffat.debian.org writes:
 This message was created automatically by mail delivery software.

 A message that you sent could not be delivered to one or more of its
 recipients. This is a permanent error. The following address(es) failed:

   nowhere@levallois.eu.org
 retry timeout exceeded

 -- This is a copy of the message, including all the headers. --

[...]
 From: Debian FTP Masters ftpmas...@ftp-master.debian.org
 To: Pierre THIERRY nowhere@levallois.eu.org, Dimitri Fontaine 
 d...@tapoueh.org,  m...@debian.org
[...]
 Subject: bordeaux-threads_0.8.3-1_amd64.changes ACCEPTED into unstable
 Message-Id: e1xufah-0006fp...@franck.debian.org
 Date: Thu, 18 Sep 2014 17:33:33 +


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



Bug#762520: clearlooks-phenix-theme: theme is completely broken since the last GTK update

2014-09-23 Thread Andrew Shadura
Hello,

On Tue, 23 Sep 2014 04:04:33 +0200
Christoph Anton Mitterer cales...@scientia.net wrote:

 I guess since the most recent upgrade of GTK the theme is completely
 broken.
 
 Most important, checkboxes and radio buttons are no longer displayed,
 you just see an empty space where they should be.
 When you click them, you can see the check for a few milliseconds,
 than it becomes invisible again.
 
 Further, the colours seem to no longer match, as the attached
 screenshot should show quite well, the default background seems to be
 white now, while the the background for frames, radio buttons and
 check boxes is still the proper grey.
 
 The screenshots are from cinnamon,... under gnome classic, I've seen
 that also some grey tones seem to no longer match (again grey tone of
 check boxes/etc. vs. the default background grey).

Oh. WHY?! Why do they do this AGAIN and AGAIN?! Why just one breakage
per year is NOT ENOUGH?!

Okay, I'll try to fix it when I have more time. Thanks for the report.

-- 
Cheers,
  Andrew


signature.asc
Description: PGP signature


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

2014-09-23 Thread Steve Langasek
On Tue, Sep 23, 2014 at 09:25:33AM +0700, Theppitak Karoonboonyanan wrote:
 Package: libfreetype6
 Version: 2.5.2-2
 Followup-For: Bug #730742
 Control: reopen -1

 Dear Maintainer,

 I also prefer Adobe rasterizer, to the point that my font packages,
 namely fonts-tlwg-*, have switched from TTF to OTF due to the improved
 quality it provides. The result was better control on glyph shapes
 (because the fonts are developed using cubic splines) with smaller
 installation size.

 Switching back to the old engine causes regression on my fonts, especially
 on terminal with dark background:

 New engine: 
 http://linux.thai.net/~thep/shots/20140923-tlwgtypo-new-engine-2.png
 Old engine: 
 http://linux.thai.net/~thep/shots/20140923-tlwgtypo-old-engine-2.png

 New engine: 
 http://linux.thai.net/~thep/shots/20140923-tlwgtypo-new-engine-1.png
 Old engine: 
 http://linux.thai.net/~thep/shots/20140923-tlwgtypo-old-engine-1.png

 So, I agree with Jason Pleau that Adobe engine is preferred.

 However, instead of providing alternative packages, I think the patch
 should be reverted and the poorly-hinted Cantarell font be fixed instead,
 as pointed out here in upstream mailing list (according to BubuXP's
 comment #118 above):

   https://lists.nongnu.org/archive/html/freetype/2014-01/msg00011.html

 I've checked Cantarell font, and its hints are really poor as described.

 I'm reopening the bug, so the discussion can be continued.

So if this is only a problem with the GNOME3 default font, please get that
font fixed in Debian, after which I am willing to reinstate the Adobe
engine.  But I'm not willing to enable it while it represents a regression
vs. wheezy for a significant number of our desktop users.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: Digital signature


Bug#762531: nginx-common: test function doesn't set ULIMIT

2014-09-23 Thread shugen
Package: nginx-common
Version: 1.2.1-2.2+wheezy2
Severity: serious
Justification: must

Dear Maintainer,
our nginx configuration at startup opens many files (many vhost etc). Normally 
is not a problem, we can set ULIMIT in nginx default, but function test will 
starts before that and returns an error. We temporarily solved this problem by 
moving ULIMIT before the test function.

Best Regards

-- System Information:
Debian Release: 7.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.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#762547: oss-compat: Upgrade to compat_2+deb7u1 fails during configure

2014-09-23 Thread Andreas Sundstrom
Package: oss-compat
Version: 2+deb7u1
Severity: serious
Justification: Policy 6.1

Dear Maintainer,
I just upgraded my machine and that included oss-compat.
During the dpkg configuration phase it failed.

Here's the output from the session:
(Reading database ... 271246 files and directories currently installed.)
Preparing to replace libsnmp-base 5.4.3~dfsg-2.8 (using 
.../libsnmp-base_5.4.3~dfsg-2.8+deb7u1_all.deb) ...
Unpacking replacement libsnmp-base ...
Preparing to replace libsnmp-dev 5.4.3~dfsg-2.8 (using 
.../libsnmp-dev_5.4.3~dfsg-2.8+deb7u1_amd64.deb) ...
Unpacking replacement libsnmp-dev ...
Preparing to replace libsnmp-perl 5.4.3~dfsg-2.8 (using 
.../libsnmp-perl_5.4.3~dfsg-2.8+deb7u1_amd64.deb) ...
Unpacking replacement libsnmp-perl ...
Preparing to replace libsnmp15 5.4.3~dfsg-2.8 (using 
.../libsnmp15_5.4.3~dfsg-2.8+deb7u1_amd64.deb) ...
Unpacking replacement libsnmp15 ...
Preparing to replace snmp 5.4.3~dfsg-2.8 (using 
.../snmp_5.4.3~dfsg-2.8+deb7u1_amd64.deb) ...
Unpacking replacement snmp ...
Preparing to replace oss-compat 2 (using .../oss-compat_2+deb7u1_amd64.deb) ...
Unpacking replacement oss-compat ...
Processing triggers for man-db ...
Setting up libsnmp-base (5.4.3~dfsg-2.8+deb7u1) ...
Setting up libsnmp15 (5.4.3~dfsg-2.8+deb7u1) ...
Setting up libsnmp-perl (5.4.3~dfsg-2.8+deb7u1) ...
Setting up libsnmp-dev (5.4.3~dfsg-2.8+deb7u1) ...
Setting up snmp (5.4.3~dfsg-2.8+deb7u1) ...
Setting up oss-compat (2+deb7u1) ...
cp: missing destination file operand after `/lib/oss-compat/linux'
Try `cp --help' for more information.
dpkg: error processing oss-compat (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 oss-compat
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up oss-compat (2+deb7u1) ...
cp: missing destination file operand after `/lib/oss-compat/linux'
Try `cp --help' for more information.
dpkg: error processing oss-compat (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 oss-compat


My guess is that the problem is in:
/var/lib/dpkg/info/oss-compat.postinst

On line 36:
[ -f ${curconffile} ]  [ $(md5sum ${curconffile} | cut -d\  -f1) = 
88222606b0a3ba8b0825c5000c754e6f ]  cp /lib/oss-compat/linux ${conffile}

${conffile} is not mentioned in any other places in that script, so if it's not 
being set somewhere else that would be the reason for the cp command to fail.

I have not yet tried to fix the issue but I suspect that a purge/re-install 
would to the trick..


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

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

Versions of packages oss-compat depends on:
ii  kmod  9-3

oss-compat recommends no packages.

oss-compat 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#762551: jumpnbump-levels: Package has no uploaders

2014-09-23 Thread Vincent Cheng
Source: jumpnbump-levels
Version: 20091107
Severity: serious
Justification: Policy 5.6.3

Dear Maintainer,

jumpnbump-levels does not currently have any human uploaders. This is a
violation of a must directive in Policy 5.6.3 [1], hence it is a RC bug.

Regards,
Vincent

[1] 
https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-controlfieldslist


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



Bug#740942: [samba] /etc/init.d/samba forbit systemd shutdown system

2014-09-23 Thread Cesare Leonardi
Package: samba
Version: 2:4.1.11+dfsg-1
Followup-For: Bug #740942

Some notes.
On shutdown/reboot, occasionally i see this message from systemd,
with a countdown and a moving asterisk:
-
A stop job is running for LSB: ensure samba daemons are started (nmbd
and smbd) ( 3 min 2 s / 5 min )
-
But normally it's just silent.

Launching this:
date ; systemctl stop samba ; date
In /var/log/syslog i see:
Sep 23 08:58:26 barone systemd[1]: samba.service stopping timed out. 
Terminating.
Sep 23 08:58:26 barone samba[1324]: Stopping samba-ad-dc (via systemctl): 
samba-ad-dc.service
Sep 23 08:58:26 barone systemd[1]: Unit samba.service entered failed state.
Sep 23 08:58:27 barone samba-ad-dc[1383]: Stopping Samba AD DC daemon: samba.

On the command line, the delay happens with both these commands:
systemctl stop samba
service samba stop

But with the old way there is no delay and there is some informative output:
/etc/init.d/samba stop
* Stopping samba-ad-dc (via systemctl): samba-ad-dc.service
* Stopping smbd (via systemctl): smbd.service
* Stopping nmbd (via systemctl): nmbd.service

Launching the previous commands like that:
date ; /etc/init.d/samba-ad-dc stop ; date; sleep 2 ; /etc/init.d/smbd stop ; 
date ; sleep 2 ; /etc/init.d/nmbd stop ; date
mar 23 set 2014, 09.13.26, CEST
[ ok ] Stopping samba-ad-dc (via systemctl): samba-ad-dc.service.
mar 23 set 2014, 09.13.27, CEST
[ ok ] Stopping smbd (via systemctl): smbd.service.
mar 23 set 2014, 09.13.30, CEST
[ ok ] Stopping nmbd (via systemctl): nmbd.service.
mar 23 set 2014, 09.13.33, CEST

In /var/log/syslog i see some moessages:
Sep  3 09:13:27 barone samba-ad-dc[1661]: Stopping Samba AD DC daemon: samba.
Sep 23 09:13:29 barone smbd[1311]:   STATUS=daemon 'smbd' finished starting up 
and ready to serve connectionsFailed to delete pidfile /var/run/samba/smbd.pid. 
Error was No such file or directory
Sep 23 09:13:30 barone smbd[1694]: Stopping SMB/CIFS daemon: smbd.
Sep 23 09:13:32 barone nmbd[1280]:   STATUS=daemon 'nmbd' finished starting up 
and ready to serve connectionsGot SIGTERM: going down...
Sep 23 09:13:33 barone nmbd[1727]: Stopping NetBIOS name server: nmbd.

Moreover, the following separate commands shows no delay:
systemctl stop samba-ad-dc.service
systemctl stop smbd.service
systemctl stop nmbd.service
But if after those i run the following (namely with the three services
already stopped), it just delay for 5 min as usual:
systemctl stop samba

The following doesn't help either:
systemctl stop winbind
systemctl stop samba

Cesare.


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

Kernel: Linux 3.16-2-amd64 (SMP w/2 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 samba depends on:
ii  adduser  3.113+nmu3
ii  dpkg 1.17.13
ii  libasn1-8-heimdal1.6~rc2+dfsg-8
ii  libbsd0  0.7.0-2
ii  libc62.19-11
ii  libcomerr2   1.42.12-1
ii  libhdb9-heimdal [heimdal-hdb-api-8]  1.6~rc2+dfsg-8
ii  libkdc2-heimdal  1.6~rc2+dfsg-8
ii  libkrb5-26-heimdal   1.6~rc2+dfsg-8
ii  libldb1  1:1.1.17-1
ii  libpam-modules   1.1.8-3.1
ii  libpam-runtime   1.1.8-3.1
ii  libpopt0 1.16-10
ii  libpython2.7 2.7.8-7
ii  libroken18-heimdal   1.6~rc2+dfsg-8
ii  libtalloc2   2.1.1-2
ii  libtdb1  1.3.0-1.1
ii  libtevent0   0.9.21-1
ii  lsb-base 4.1+Debian13
ii  multiarch-support2.19-11
ii  procps   1:3.3.9-7
ii  python   2.7.8-1
ii  python-dnspython 1.12.0-1
ii  python-ntdb  1.0-5
ii  python-samba 2:4.1.11+dfsg-1
pn  python2.7:anynone
ii  samba-common 2:4.1.11+dfsg-1
ii  samba-common-bin 2:4.1.11+dfsg-1
ii  samba-dsdb-modules   2:4.1.11+dfsg-1
ii  samba-libs   2:4.1.11+dfsg-1
ii  tdb-tools1.3.0-1.1
ii  update-inetd 4.43

Versions of packages samba recommends:
ii  attr   1:2.4.47-2
ii  logrotate  3.8.7-1
ii  samba-vfs-modules  2:4.1.11+dfsg-1

Versions of packages samba suggests:
ii  bind9  1:9.9.5.dfsg-4
ii  bind9utils 1:9.9.5.dfsg-4
pn  ctdb   none
pn  ldb-tools  none
ii  ntp1:4.2.6.p5+dfsg-3.1
pn  smbldap-tools  none
ii  winbind2:4.1.11+dfsg-1

-- debconf information:
  samba/run_mode: 

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

2014-09-23 Thread BubuXP
Il 23/set/2014 08:51 Steve Langasek vor...@debian.org ha scritto:

 So if this is only a problem with the GNOME3 default font, please get that
 font fixed in Debian, after which I am willing to reinstate the Adobe
 engine.  But I'm not willing to enable it while it represents a regression
 vs. wheezy for a significant number of our desktop users.

So why not changing only the default UI font in GNOME until Cantarell gets
fixed, instead of disabling a nice improvement like that?
Droid or DejaVu could be a valid substitute in the meanwhile.


Bug#755610: marked as done (lava-server: Please ensure it works with Django 1.7)

2014-09-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Sep 2014 10:20:01 +
with message-id e1xwnct-0002tz...@franck.debian.org
and subject line Bug#755610: fixed in lava-server 2014.08.2-1
has caused the Debian Bug report #755610,
regarding lava-server: Please ensure it works with Django 1.7
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.)


-- 
755610: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: lava-server
Version: 2014.06.14.17-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django17

Hello,

your package lava-server depends on python-django. As you might
know, Django 1.7 will be soon available and as each new upstream major
version, it brings many changes, some of them which are backwards
incompatible (after a deprecation period covering 2 major versions):
https://docs.djangoproject.com/en/1.7/releases/1.7/
https://docs.djangoproject.com/en/1.7/releases/1.7/#backwards-incompatible-changes-in-1-7

We intend to upload Django 1.7 to unstable as soon as it is available
because we really want the latest version in jessie and the freeze is
approaching fast. In preparation of that, I have uploaded a release
candidate in experimental.

Please test your package against Django 1.7 in experimental. If a new
upstream version of your package is required, please package it now.
If you can't upload it to unstable because it only works with Django 1.7,
feel free to upload it to experimental too.

If the current package works fine, please close this bug (or retitle it as
a suggestion to implement Python 3 support and drop its severity to
wishlist[1]). If it's broken, please tag it as confirmed. If it's not
broken, but would benefit from further work, please tag it as confirmed
but reduce the severity.

If you have experimental in your sources.list you can install the latest
version easily:
$ sudo apt-get install -t experimental python-django python3-django

[1] We have recently added Python 3 support with the addition of
python3-django. Consider doing the same if your package is a Django
application/library.

Thank you for your help!

PS: I will raise the confirmed bugs that are still of severity
important to serious once we upload Django 1.7 to unstable.
---End Message---
---BeginMessage---
Source: lava-server
Source-Version: 2014.08.2-1

We believe that the bug you reported is fixed in the latest version of
lava-server, 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 755...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Neil Williams codeh...@debian.org (supplier of updated lava-server 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: Wed, 17 Sep 2014 10:24:09 -0700
Source: lava-server
Binary: lava-server lava lava-dev lava-server-doc
Architecture: source all
Version: 2014.08.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian LAVA team pkg-linaro-lava-de...@lists.alioth.debian.org
Changed-By: Neil Williams codeh...@debian.org
Description:
 lava   - Linaro Automated Validation Architecture metapackage
 lava-dev   - Linaro Automated Validation Architecture developer support
 lava-server - Linaro Automated Validation Architecture server
 lava-server-doc - Linaro Automated Validation Architecture documentation
Closes: 755610
Changes:
 lava-server (2014.08.2-1) unstable; urgency=medium
 .
   * New production release includes fixes for multinode tagging,
 multinode slave capability and documentation, fixup time
 display in various places to be more human readable,
 make test selection on image reports persistent and add
 skipped and unknown test count to totals in image reports.
   * Migrate to Django 1.7 support (Closes: #755610)
   * Fix machine-readable sections of copyright lines
Checksums-Sha1:
 7634de0b7018a5adf132d47bb5da9499b86a2b14 2393 lava-server_2014.08.2-1.dsc
 d0242dbace17ea2f220bd562fba226da3fa4f3b5 7033361 
lava-server_2014.08.2.orig.tar.gz
 bff5fc2df6526716f0b7e081846a2724099fffc5 26912 
lava-server_2014.08.2-1.debian.tar.xz
 0277bdd9f8ffa51fc09d84d71044a8ef84e09c17 834108 lava-server_2014.08.2-1_all.deb
 

Bug#760658: marked as done (Bad pkgconfig file = FTBFS other package)

2014-09-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Sep 2014 10:19:17 +
with message-id e1xwnbl-0002a9...@franck.debian.org
and subject line Bug#760658: fixed in dolfin 1.4.0+dfsg-4
has caused the Debian Bug report #760658,
regarding Bad pkgconfig file = FTBFS other package
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.)


-- 
760658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760658
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
package: libdolfin-dev
version: 1.4.0+dfsg-3
severity: serious

Your pkg-config file include some directive that could lead to FTFBS
other package (BTW you have wrongly added lintian override):

O usr/lib/x86_64-linux-gnu/pkgconfig/dolfin.pc -Werror=format-security
O usr/lib/x86_64-linux-gnu/pkgconfig/dolfin.pc -O2
O usr/lib/x86_64-linux-gnu/pkgconfig/dolfin.pc -g
O usr/lib/x86_64-linux-gnu/pkgconfig/dolfin.pc -D_FORTIFY_SOURCE=2
O usr/lib/x86_64-linux-gnu/pkgconfig/dolfin.pc -frounding-math

Bastien
---End Message---
---BeginMessage---
Source: dolfin
Source-Version: 1.4.0+dfsg-4

We believe that the bug you reported is fixed in the latest version of
dolfin, 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 760...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Johannes Ring joha...@simula.no (supplier of updated dolfin 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: Mon, 22 Sep 2014 14:35:34 +0200
Source: dolfin
Binary: libdolfin-dev libdolfin1.4 libdolfin1.4-dbg python-dolfin 
python-dolfin-dbg dolfin-doc dolfin-bin
Architecture: source amd64 all
Version: 1.4.0+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 
debian-science-maintain...@lists.alioth.debian.org
Changed-By: Johannes Ring joha...@simula.no
Description:
 dolfin-bin - Executable scripts for DOLFIN
 dolfin-doc - Documentation and demo programs for DOLFIN
 libdolfin-dev - Shared links and header files for DOLFIN
 libdolfin1.4 - Shared libraries for DOLFIN
 libdolfin1.4-dbg - Shared libraries with debugging symbols for DOLFIN
 python-dolfin - Python interface for DOLFIN
 python-dolfin-dbg - Python extension modules for DOLFIN with debugging symbols
Closes: 760658
Changes:
 dolfin (1.4.0+dfsg-4) unstable; urgency=medium
 .
   * debian/control: Disable libcgal-dev on i386, mipsel and sparc.
   * debian/rules: Remove bad directives in pkg-config file dolfin.pc
 (closes: #760658).
   * Remove debian/libdolfin-dev.lintian-overrides.
Checksums-Sha1:
 582d51c04c58c79b4547e4b991b16ac85e422b84 3010 dolfin_1.4.0+dfsg-4.dsc
 2aae921b0d7ddbe688362240ccdf2730e7638d34 115340 
dolfin_1.4.0+dfsg-4.debian.tar.xz
 9bdd33cdd8b4ccb07040aeac8dcab38250a10918 242616 
libdolfin-dev_1.4.0+dfsg-4_amd64.deb
 5fb5e2a30f7705c91451edeb37268d12851ade61 3420682 
libdolfin1.4_1.4.0+dfsg-4_amd64.deb
 703f69ea69bb6223dcaab213a33d9b87dbfbf730 51413456 
libdolfin1.4-dbg_1.4.0+dfsg-4_amd64.deb
 54db820663a9a33f38f5440a8da348cf2795242c 1237670 
python-dolfin_1.4.0+dfsg-4_amd64.deb
 1d4adfd7981cc745741acc14965e179871831fad 8683244 
python-dolfin-dbg_1.4.0+dfsg-4_amd64.deb
 c0f08d5fa0fdce1bf100ee611d3c3ed8ea478a64 2261912 
dolfin-doc_1.4.0+dfsg-4_all.deb
 662968dcf59d85c32b34d4d9ed8e3b82a78f9912 43954 dolfin-bin_1.4.0+dfsg-4_all.deb
Checksums-Sha256:
 e0c8a383b031ed996a82206dbf4693662ea51efb67e9820028ad03b528be19e2 3010 
dolfin_1.4.0+dfsg-4.dsc
 0c73727c528876e74344a4b14b4b0baab1c8f34ce147f761e229d0cc538bfdbc 115340 
dolfin_1.4.0+dfsg-4.debian.tar.xz
 9a40601b31e26881a379b1d6541cb9163dd1870ab4555b7b3393b8a6f18c70fa 242616 
libdolfin-dev_1.4.0+dfsg-4_amd64.deb
 162c8166203f8b2d1b026196060a00d4143ae846520283e7325d81028187181b 3420682 
libdolfin1.4_1.4.0+dfsg-4_amd64.deb
 cdae05a5e9834ae8d2ac4a88cc1c5d3745f2e78aa65a6608b3efcc245d5513f2 51413456 
libdolfin1.4-dbg_1.4.0+dfsg-4_amd64.deb
 aa9e77ca40d584f9db4791de1591eccaa756311ad5a7bb31b4a72fa178fd399b 1237670 
python-dolfin_1.4.0+dfsg-4_amd64.deb
 3a245b054b08c10e6f0781a94ed01aca7244fb1f730cc9753297b5ce8b46af8f 8683244 
python-dolfin-dbg_1.4.0+dfsg-4_amd64.deb
 c9d44a98b2341ae2896d656f3f0d2a895e88e9004aa4823a7f262b1de43cc207 2261912 
dolfin-doc_1.4.0+dfsg-4_all.deb
 

Processed: Forwarded address

2014-09-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 forwarded 699325 http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8705
Bug #699325 [emacs24] emacs24: crashes in getenv.c just after starting it
Bug #762438 [emacs24] libgtk-3-0: makes emacs crash (Segmentation fault) when 
called from a git or svn directory
Set Bug forwarded-to-address to 
'http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8705'.
Set Bug forwarded-to-address to 
'http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8705'.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
699325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699325
762438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762438
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: tagging 762547

2014-09-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 762547 + pending
Bug #762547 [oss-compat] oss-compat: Upgrade to compat_2+deb7u1 fails during 
configure
Added tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
762547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762547
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: tagging 757605

2014-09-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 # fixed in NEW
 tags 757605 + pending
Bug #757605 [libfreerdp1] libfreerdp1: changes to soname cause remmina RDP 
plugin to fail
Bug #757926 [libfreerdp1] ABI changes in libfreerdp1 makes other software break
Added tag(s) pending.
Added tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
757605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757605
757926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757926
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#757926: marked as done (ABI changes in libfreerdp1 makes other software break)

2014-09-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Sep 2014 12:00:12 +
with message-id e1xwolq-0003wc...@franck.debian.org
and subject line Bug#757605: fixed in freerdp 
1.1.0~git20140921.1.440916e+dfsg1-1
has caused the Debian Bug report #757605,
regarding ABI changes in libfreerdp1 makes other software break
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.)


-- 
757605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libfreerdp1
Version: 1.1.0~git20140809.1.b07a5c1+dfsg-1
Severity: grave


Dear Maintainer,

with latest changes in FreeRDP, libfreerdp1 changes its internal structure,
causing depenent packages to fail to load.

remmina is an example of this (see #757821), it requires some of the objects
provided by libfreerdp1, but these are not available anymore:

$ ldd /usr/lib/remmina/plugins/remmina-plugin-rdp.so | grep found
libfreerdp-core.so.1.0 = not found
libfreerdp-gdi.so.1.0 = not found
libfreerdp-kbd.so.1.0 = not found
libfreerdp-codec.so.1.0 = not found
libfreerdp-channels.so.1.0 = not found
$

I'm not sure whether FreeRDP SONAME should have been bumped upstream, but the
changes introduced in the latest versions uploaded to Debian are breaking other
software in the archive.

Cheers,
Luca
---End Message---
---BeginMessage---
Source: freerdp
Source-Version: 1.1.0~git20140921.1.440916e+dfsg1-1

We believe that the bug you reported is fixed in the latest version of
freerdp, 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 757...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel sunwea...@debian.org (supplier of updated freerdp 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: Mon, 22 Sep 2014 21:40:55 +0200
Source: freerdp
Binary: freerdp-x11 libfreerdp-cache1.1 libfreerdp-client1.1 
libfreerdp-codec1.1 libfreerdp-common1.1.0 libfreerdp-core1.1 
libfreerdp-crypto1.1 libfreerdp-gdi1.1 libfreerdp-locale1.1 
libfreerdp-primitives1.1 libfreerdp-rail1.1 libfreerdp-utils1.1 
libwinpr-asn1-0.1 libwinpr-bcrypt0.1 libwinpr-credentials0.1 libwinpr-credui0.1 
libwinpr-crt0.1 libwinpr-crypto0.1 libwinpr-dsparse0.1 libwinpr-environment0.1 
libwinpr-error0.1 libwinpr-file0.1 libwinpr-handle0.1 libwinpr-heap0.1 
libwinpr-input0.1 libwinpr-interlocked0.1 libwinpr-io0.1 libwinpr-library0.1 
libwinpr-path0.1 libwinpr-pipe0.1 libwinpr-pool0.1 libwinpr-registry0.1 
libwinpr-rpc0.1 libwinpr-sspi0.1 libwinpr-sspicli0.1 libwinpr-synch0.1 
libwinpr-sysinfo0.1 libwinpr-thread0.1 libwinpr-timezone0.1 libwinpr-utils0.1 
libwinpr-winhttp0.1 libwinpr-winsock0.1 libxfreerdp-client1.1 
libfreerdp-plugins-standard libfreerdp-dev libwinpr-dev freerdp-x11-dbg 
libxfreerdp-client-dbg libfreerdp-dbg libwinpr-dbg
 libfreerdp-plugins-standard-dbg
Architecture: source amd64
Version: 1.1.0~git20140921.1.440916e+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Mike Gabriel sunwea...@debian.org
Changed-By: Mike Gabriel sunwea...@debian.org
Description:
 freerdp-x11 - RDP client for Windows Terminal Services (X11 client)
 freerdp-x11-dbg - RDP client for Windows Terminal Services (X11 client, debug 
symbo
 libfreerdp-cache1.1 - Free Remote Desktop Protocol library (cache library)
 libfreerdp-client1.1 - Free Remote Desktop Protocol library (client library)
 libfreerdp-codec1.1 - Free Remote Desktop Protocol library (codec library)
 libfreerdp-common1.1.0 - Free Remote Desktop Protocol library (common library)
 libfreerdp-core1.1 - Free Remote Desktop Protocol library (core library)
 libfreerdp-crypto1.1 - Free Remote Desktop Protocol library (freerdp-crypto 
library)
 libfreerdp-dbg - Free Remote Desktop Protocol library (debug symbols)
 libfreerdp-dev - Free Remote Desktop Protocol library (development files)
 libfreerdp-gdi1.1 - Free Remote Desktop Protocol library (GDI library)
 libfreerdp-locale1.1 - Free Remote Desktop Protocol library (locale library)
 libfreerdp-plugins-standard - RDP client for Windows Terminal Services 
(plugins)
 libfreerdp-plugins-standard-dbg - RDP client for Windows Terminal Services 
(plugins debug)
 

Bug#757605: marked as done (libfreerdp1: changes to soname cause remmina RDP plugin to fail)

2014-09-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Sep 2014 12:00:12 +
with message-id e1xwolq-0003wc...@franck.debian.org
and subject line Bug#757605: fixed in freerdp 
1.1.0~git20140921.1.440916e+dfsg1-1
has caused the Debian Bug report #757605,
regarding libfreerdp1: changes to soname cause remmina RDP plugin to fail
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.)


-- 
757605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libfreerdp1
Version: 1.1.0~git20140808.1.7b5cd86+dfsg-1
Severity: important

Hi!

This new version from git changes the soname of the library which causes the
rdp-plugin of remmina to fail:

ldd /usr/lib/remmina/plugins/remmina-plugin-rdp.so
  [...]
libfreerdp-core.so.1.0 = not found
libfreerdp-gdi.so.1.0 = not found
libfreerdp-kbd.so.1.0 = not found
libfreerdp-codec.so.1.0 = not found
libfreerdp-channels.so.1.0 = not found
  [...]

I guess vlc-nox and libguac-client-rdp0 will be affected as well.

Grüße,
Sven.

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

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

Versions of packages libfreerdp1 depends on:
ii  libc6  2.19-7
ii  libjpeg8   8d1-1
ii  libssl1.0.01.0.1i-1
ii  libx11-6   2:1.6.2-2
ii  libxcursor11:1.1.14-1
ii  libxext6   2:1.3.2-1
ii  libxi6 2:1.7.4-1
ii  libxinerama1   2:1.1.3-1
ii  libxkbfile11:1.0.8-1
ii  libxrender11:0.9.8-1
ii  libxv1 2:1.0.10-1
ii  multiarch-support  2.19-7
ii  zlib1g 1:1.2.8.dfsg-1

libfreerdp1 recommends no packages.

Versions of packages libfreerdp1 suggests:
ii  freerdp-x11  1.1.0~git20140808.1.7b5cd86+dfsg-1

-- no debconf information
---End Message---
---BeginMessage---
Source: freerdp
Source-Version: 1.1.0~git20140921.1.440916e+dfsg1-1

We believe that the bug you reported is fixed in the latest version of
freerdp, 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 757...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel sunwea...@debian.org (supplier of updated freerdp 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: Mon, 22 Sep 2014 21:40:55 +0200
Source: freerdp
Binary: freerdp-x11 libfreerdp-cache1.1 libfreerdp-client1.1 
libfreerdp-codec1.1 libfreerdp-common1.1.0 libfreerdp-core1.1 
libfreerdp-crypto1.1 libfreerdp-gdi1.1 libfreerdp-locale1.1 
libfreerdp-primitives1.1 libfreerdp-rail1.1 libfreerdp-utils1.1 
libwinpr-asn1-0.1 libwinpr-bcrypt0.1 libwinpr-credentials0.1 libwinpr-credui0.1 
libwinpr-crt0.1 libwinpr-crypto0.1 libwinpr-dsparse0.1 libwinpr-environment0.1 
libwinpr-error0.1 libwinpr-file0.1 libwinpr-handle0.1 libwinpr-heap0.1 
libwinpr-input0.1 libwinpr-interlocked0.1 libwinpr-io0.1 libwinpr-library0.1 
libwinpr-path0.1 libwinpr-pipe0.1 libwinpr-pool0.1 libwinpr-registry0.1 
libwinpr-rpc0.1 libwinpr-sspi0.1 libwinpr-sspicli0.1 libwinpr-synch0.1 
libwinpr-sysinfo0.1 libwinpr-thread0.1 libwinpr-timezone0.1 libwinpr-utils0.1 
libwinpr-winhttp0.1 libwinpr-winsock0.1 libxfreerdp-client1.1 
libfreerdp-plugins-standard libfreerdp-dev libwinpr-dev freerdp-x11-dbg 
libxfreerdp-client-dbg libfreerdp-dbg libwinpr-dbg
 libfreerdp-plugins-standard-dbg
Architecture: source amd64
Version: 1.1.0~git20140921.1.440916e+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Mike Gabriel sunwea...@debian.org
Changed-By: Mike Gabriel sunwea...@debian.org
Description:
 freerdp-x11 - RDP client for Windows Terminal Services (X11 client)
 freerdp-x11-dbg - RDP client for Windows Terminal Services (X11 client, debug 
symbo
 libfreerdp-cache1.1 - Free Remote Desktop Protocol library (cache library)
 libfreerdp-client1.1 - Free Remote Desktop Protocol library (client library)
 libfreerdp-codec1.1 - Free Remote Desktop Protocol library (codec library)
 

Bug#759843: node-mapnik: FTBFS: vector_tile_processor.hpp:48:38: fatal error: mapnik3x_compatibility.hpp: No such file or directory

2014-09-23 Thread peter green
This looks like a manifestation of 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761429



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



Processed: jessie

2014-09-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tag 762551 + wheezy-ignore
Bug #762551 [src:jumpnbump-levels] jumpnbump-levels: Package has no uploaders
Added tag(s) wheezy-ignore.
 tag 744736 + wheezy-ignore
Bug #744736 [t1utils] t1utils: Maintainer address bounces
Added tag(s) wheezy-ignore.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
744736: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744736
762551: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762551
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#762520: clearlooks-phenix-theme: theme is completely broken since the last GTK update

2014-09-23 Thread Christoph Anton Mitterer
On Tue, 2014-09-23 at 08:37 +0200, Andrew Shadura wrote: 
 Oh. WHY?! Why do they do this AGAIN and AGAIN?! Why just one breakage
 per year is NOT ENOUGH?!
Frankly, I guess because they're idiots ;-)


 Okay, I'll try to fix it when I have more time. Thanks for the report.
Thanks a lot... :)

Attached is an image where one can see at least one other issue:
The grey from the Clipboard size section is probably wrong... and when
I hover over the checkbox items above (where one cannot see the check
boxes ;.) )... they also change their grey to something slightly
brighter, I mean the whole section changes it's grey.



Cheers,
Chris.


smime.p7s
Description: S/MIME cryptographic signature


Bug#759843: [Pkg-javascript-devel] Bug#759843: node-mapnik: FTBFS: vector_tile_processor.hpp:48:38: fatal error: mapnik3x_compatibility.hpp: No such file or directory

2014-09-23 Thread Jérémy Lal
Le mardi 23 septembre 2014 à 13:28 +0100, peter green a écrit :
 This looks like a manifestation of 
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761429

Thank you for bringing this.

Note that i won't lift a finger until mapnik 2.3 is out, which is
(according to upstream [0]) due to be soon.


[0]
https://github.com/mapnik/mapnik/issues/2425#issuecomment-56335743


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



Bug#762588: glib-networking: FTBFS[kfreebsd]: testsuite race conditions

2014-09-23 Thread Steven Chamberlain
Package: glib-networking
Version: 2.41.92-2
Severity: serious
User: debian-...@lists.debian.org
Usertags: kfreebsd

Hi,

glib-networking has failed 4 attempts to build on kfreebsd-amd64 due to
testsuite errors.

Firstly, please `export VERBOSE=1` before running `make check`.  There
is much more detail recorded about failures than is currently output in
the build log.

I was able to reproduce issues locally about 15% of the time, suggesting
a race condition, in three different tests:

/tls/connection/client-auth-rehandshake: **
GLib-Net:ERROR:connection.c:413:on_client_connection_close_finish: 
assertion failed (error == NULL): Error closing socket: Connection reset by 
peer (g-io-error-quark, 0)
Aborted

/tls/connection/read-time-out-then-write: **
GLib-Net:ERROR:connection.c:217:on_server_close_finish: assertion failed 
(error == NULL): Error closing socket: Connection reset by peer 
(g-io-error-quark, 0)
Aborted

/tls/connection/close-during-handshake: **
GLib-Net:ERROR:connection.c:215:on_server_close_finish: assertion failed: 
(error != NULL)
Aborted

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-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#749360: lletters: FTBFS - Makefile:206: *** missing separator (did you mean TAB instead of 8 spaces?).

2014-09-23 Thread Markus Koschany
Control: tags -1 patch

I am attaching a debdiff with patches and fixes for several bugs of
lletters. There are more Lintian warnings to fix but I leave this to
someone else who wants to build upon those patches in the future.

Changelog:


* QA upload.
* Set maintainer address to Debian QA Group packa...@qa.debian.org.
* Add ${misc:Depends} substvar.
* Fix FTBFS because of missing separators in intl/Makefile.in.
  (Closes: #749360)
* Build with autotools-dev and fix FTBFS on newer architectures due to
  outdated config.sub and config.guess files. (Closes: #727450, #538667)
* Fix program stops responding while playing sound by replacing type
  long with uint32_t. Thanks q1we...@i.com.ua for the patch.
  (Closes: #701852)
* Fix application terminates when clicking A, B or H. Thanks to
  Prathibha B for the report and patch. (Closes: #712845)
* Use compat level 9 and require debhelper = 9.
* Use source format 1.0 explicitly by adding a source directory and
  format file to the debian directory.
* Remove superfluous postrm.debhelper and postinst.debhelper file.
* Create a valid desktop file and add a comment in German.

Regards,

Markus
diff -u lletters-0.1.95+gtk2/lln.c lletters-0.1.95+gtk2/lln.c
--- lletters-0.1.95+gtk2/lln.c
+++ lletters-0.1.95+gtk2/lln.c
@@ -141,10 +141,11 @@
   lang = strtok(getenv (LANG), _);
 //  lang = strtok(lang, _);
 
-  if (!lang)
+  if (!lang || strcmp(lang, en) == 0 )
 {
-   /* LANG is not set */
-   printf(_(LANG environment is not set, using defaults.\n));
+   if (!lang)
+   /* LANG is not set */
+   printf(_(LANG environment is not set, using 
defaults.\n));
/* if $LANG-specific dir doesn't exist... */
asprintf (lln_image_dir, %s/lletters/images/, DATADIR);
/* Set soundfile directory. Kirk Ismay */
diff -u lletters-0.1.95+gtk2/wav_play.c lletters-0.1.95+gtk2/wav_play.c
--- lletters-0.1.95+gtk2/wav_play.c
+++ lletters-0.1.95+gtk2/wav_play.c
@@ -112,11 +112,14 @@
 
if (i = init_dsp(file_info) != 0){
fprintf(stderr,Cannot initialize DSP\n);
+   #undef SOUND
+/*
 #ifdef SOUND
exit(0);
 #endif 
+*/
}
-   
+   else {
report();
 
 #ifdef GSM 
@@ -136,0 +140 @@
+}
diff -u lletters-0.1.95+gtk2/debian/lletters.desktop 
lletters-0.1.95+gtk2/debian/lletters.desktop
--- lletters-0.1.95+gtk2/debian/lletters.desktop
+++ lletters-0.1.95+gtk2/debian/lletters.desktop
@@ -1,6 +1,5 @@
 [Desktop Entry]
 Version=1.0
-Encoding=UTF-8
 Type=Application
 Name=Linux Letters and Numbers
 Name[es]=Linux Letras y Números
@@ -12,8 +11,6 @@
-Icon=lletters.xpm
-
-FilePattern=lletters
+Comment[de]=Buchstaben-Lernspiel für kleine Kinder
+Icon=lletters
 Exec=lletters
 Terminal=false
 StartupNotify=false
-
-Categories=Application;Game;Education;KidsGame;2DGraphics;
+Categories=Game;Education;KidsGame;2DGraphics;
reverted:
--- lletters-0.1.95+gtk2/debian/postinst.debhelper
+++ lletters-0.1.95+gtk2.orig/debian/postinst.debhelper
@@ -1,3 +0,0 @@
-# Automatically added by dh_installmenu
-if [ $1 = configure ]  [ -x /usr/bin/update-menus ]; then update-menus ; 
fi
-# End automatically added section
diff -u lletters-0.1.95+gtk2/debian/changelog 
lletters-0.1.95+gtk2/debian/changelog
--- lletters-0.1.95+gtk2/debian/changelog
+++ lletters-0.1.95+gtk2/debian/changelog
@@ -1,3 +1,24 @@
+lletters (0.1.95+gtk2-4) unstable; urgency=medium
+
+  * QA upload.
+  * Set maintainer address to Debian QA Group packa...@qa.debian.org.
+  * Add ${misc:Depends} substvar.
+  * Fix FTBFS because of missing separators in intl/Makefile.in.
+(Closes: #749360)
+  * Build with autotools-dev and fix FTBFS on newer architectures due to
+outdated config.sub and config.guess files. (Closes: #727450, #538667)
+  * Fix program stops responding while playing sound by replacing type long
+with uint32_t. Thanks q1we...@i.com.ua for the patch. (Closes: #701852)
+  * Fix application terminates when clicking A, B or H. Thanks to Prathibha B
+for the report and patch. (Closes: #712845)
+  * Use compat level 9 and require debhelper = 9.
+  * Use source format 1.0 explicitly by adding a source directory and format
+file to the debian directory.
+  * Remove superfluous postrm.debhelper and postinst.debhelper file.
+  * Create a valid desktop file and add a comment in German.
+
+ -- Markus Koschany a...@gambaru.de  Tue, 23 Sep 2014 14:26:55 +0200
+
 lletters (0.1.95+gtk2-3.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u lletters-0.1.95+gtk2/debian/compat lletters-0.1.95+gtk2/debian/compat
--- lletters-0.1.95+gtk2/debian/compat
+++ lletters-0.1.95+gtk2/debian/compat
@@ -1 +1 @@
-4
+9
diff -u lletters-0.1.95+gtk2/debian/control lletters-0.1.95+gtk2/debian/control
--- lletters-0.1.95+gtk2/debian/control
+++ lletters-0.1.95+gtk2/debian/control
@@ -1,13 +1,13 @@
 Source: lletters
 Section: games
 Priority: extra

Processed: Re: lletters: FTBFS - Makefile:206: *** missing separator (did you mean TAB instead of 8 spaces?).

2014-09-23 Thread Debian Bug Tracking System
Processing control commands:

 tags -1 patch
Bug #749360 [lletters] lletters: FTBFS - Makefile:206: *** missing separator 
(did you mean TAB instead of 8 spaces?).
Added tag(s) patch.

-- 
749360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749360
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#762591: freerdp: FTBFS on several arches: test suite errors

2014-09-23 Thread Emilio Pozuelo Monfort
Source: freerdp
Version: 1.1.0~git20140921.1.440916e+dfsg1-1
Severity: serious

See 
https://buildd.debian.org/status/logs.php?pkg=freerdpver=1.1.0~git20140921.1.440916e%2Bdfsg1-1

Emilio


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



Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron

2014-09-23 Thread David L. Craig
On 14Sep23:0023+0200, Michael Biebl wrote:

 Yeah, this would be perfect

By way of a feasibility test, I had virt-manager
Shut Down == Save the a762146 vm at its ready for
first login state and have put the tarball of the
124MB file it created in /var/lib/libvirt/qemu/save
up at
http://dlc.casita.net/~dlc/762146/a762146.vmsave.test.tar
for you to retrieve. I expect you will also need the
hard drive image which compressed into 5.3 GB, so we
have a logistical difficulty there.  I am attaching
the domain xml and parted print free output in sectors
for the virtual disk.
-- 
not cent from sell
May the LORD God bless you exceedingly abundantly!

Dave_Craig__
So the universe is not quite as you thought it was.
 You'd better rearrange your beliefs, then.
 Because you certainly can't rearrange the universe.
__--from_Nightfall_by_Asimov/Silverberg_


a762146.xml.tar
Description: Unix tar archive
Model: ATA QEMU HARDDISK (scsi)
Disk /dev/sdb: 4096s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start  EndSize   File system Name  Flags
34s2047s  2014s  Free Space
 1  2048s  3905535s   3903488s   linux-swap(v1)  VS
 2  3905536s   40957951s  37052416s  ext4VV
40957952s  40959966s  2015s  Free Space



signature.asc
Description: Digital signature


Bug#762592: apper Unable to open database read-only in current debian testing

2014-09-23 Thread tim schmidt
Package: apper
Version: 0.9.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

lastest update to apper in debian testing resulted in the following error on 
startup:

Unable to open database read-only: Database action 'prepare app insert 
statement' failed:
 SQL logic error or missing database (table applications has no column named 
unique_name)

This renders apper unusable.

Deleting the Listaller cache DB seemed to fix the problem for me. command used:

rm -r /var/lib/listaller/db/




-- 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-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages apper depends on:
ii  apper-data   0.9.1-1
ii  kde-runtime  4:4.14.0-2
ii  libappstream10.7.1-1
ii  libc62.19-11
ii  libdebconf-kde0  0.3-1
ii  libgcc1  1:4.9.1-14
ii  libgee-0.8-2 0.14.0-2
ii  libglib2.0-0 2.40.0-5
ii  libkcmutils4 4:4.14.1-1
ii  libkdecore5  4:4.14.1-1
ii  libkdeui54:4.14.1-1
ii  libkemoticons4   4:4.14.1-1
ii  libkidletime44:4.14.1-1
ii  libkio5  4:4.14.1-1
ii  libkprintutils4  4:4.14.1-1
ii  libkutils4   4:4.14.1-1
ii  libkworkspace4abi2   4:4.11.11-2
ii  liblistaller-glib0   0.5.9-2
ii  libpackagekitqt4-0   0.9.2-4
ii  libqt4-dbus  4:4.8.6+git64-g5dc8b2b+dfsg-2
ii  libqt4-declarative   4:4.8.6+git64-g5dc8b2b+dfsg-2
ii  libqt4-network   4:4.8.6+git64-g5dc8b2b+dfsg-2
ii  libqt4-sql   4:4.8.6+git64-g5dc8b2b+dfsg-2
ii  libqt4-svg   4:4.8.6+git64-g5dc8b2b+dfsg-2
ii  libqt4-xml   4:4.8.6+git64-g5dc8b2b+dfsg-2
ii  libqt4-xmlpatterns   4:4.8.6+git64-g5dc8b2b+dfsg-2
ii  libqtcore4   4:4.8.6+git64-g5dc8b2b+dfsg-2
ii  libqtgui44:4.8.6+git64-g5dc8b2b+dfsg-2
ii  libsolid44:4.14.1-1
ii  libstdc++6   4.9.1-14
ii  packagekit   0.9.5-2
ii  policykit-1-gnome0.105-2
ii  polkit-kde-1 0.99.1-1
ii  software-properties-kde  0.92.25debian1

Versions of packages apper recommends:
ii  appstream-index  0.7.1-1

Versions of packages apper suggests:
pn  debconf-kde-helper  none
ii  listaller   0.5.9-2

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



Processed: forward to upstream.

2014-09-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 forwarded 759044 https://github.com/Tribler/tribler/issues/875
Bug #759044 [src:tribler] tribler: Please update to use wxpython3.0
Set Bug forwarded-to-address to 'https://github.com/Tribler/tribler/issues/875'.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
759044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759044
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#759044: forward to upstream.

2014-09-23 Thread Ying-Chun Liu (PaulLiu)
forwarded 759044 https://github.com/Tribler/tribler/issues/875
thanks

-- 
PaulLiu (劉穎駿)
E-mail: Ying-Chun Liu (PaulLiu) paul...@debian.org



signature.asc
Description: OpenPGP digital signature


Bug#762547: Same for me...

2014-09-23 Thread Ant
I got the same results just a few minutes ago. :(


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



Bug#762484: blas: FTBFS on *i386: xscblat1 subtests fail

2014-09-23 Thread Sébastien Villemot
Le lundi 22 septembre 2014 à 14:39 -0400, Aaron M. Ucko a écrit :
 Source: blas
 Version: 1.2.20110419-7
 Severity: serious
 Justification: fails to build from source (but built successfully in the past)
 
 Builds of blast for all *i386 architectures have been failing because many
 of xscblat1's subtests don't quite yield the expected results; see, e.g.,
 https://buildd.debian.org/status/fetch.php?pkg=blasarch=i386ver=1.2.20110419-8stamp=1411393601
 
 Could you please take a look?

The trigger of the failure is the move from gfortran 4.8 to 4.9. More
precisely, the -fno-whole-file option was dropped in gfortran 4.9 (it is
still accepted but does nothing), and this option was required to make
the tests pass.

I am now investigating why this option was needed in the first place,
and how to work around this removal.

-- 
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://www.dynare.org/sebastien
  `-  GPG Key: 4096R/381A7594



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


Bug#756155: ReferenceError: CKEDITOR is not defined

2014-09-23 Thread Louis-David Mitterrand
Package: ckeditor
Version: 4.4.4+dfsg1-1
Followup-For: Bug #756155

Hi,

Now I get this error 

NetworkError: 404 Not Found - 
http://cruise.marcus.apartia.fr/javascript/ckeditor/core/loader.js

There is no loader.js on your package.

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

Kernel: Linux 3.17-rc5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_IE@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages ckeditor depends on:
ii  libjs-highlight  8.2+ds-1
ii  libjs-swfobject  2.2+dfsg-1

Versions of packages ckeditor recommends:
ii  javascript-common  11

ckeditor 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#721421: libdevel-bt-perl: FTBFS on armel, hurd-i386, kfreebsd-amd64

2014-09-23 Thread Leon Timmermans
On Mon, Sep 22, 2014 at 12:21 AM, gregor herrmann gre...@debian.org wrote:

 Here we go:

 That's armhf on a Debian box in an unstable chroot:

 (sid_armhf-dchroot)gregoa@harris:~$ (echo r; echo bt; echo quit) | gdb
 --args perl -e 'unpack p, pack L!, 1' | egrep '^#'
 #1  0xb6f3f048 in Perl_newSVpv () from
 /usr/lib/arm-linux-gnueabihf/libperl.so.5.20
 #2  0x00040002 in ?? ()


That looks wrong to me. Does a debugging perl show the same result?

Leon


Bug#759324: [libdbd-oracle-perl] conflicts with perl-5.20

2014-09-23 Thread gregor herrmann
On Mon, 22 Sep 2014 17:06:19 -0500, Julián Moreno Patiño wrote:

 Sorry for the late reply. I can build it on amd64. 

Whatever we decide -- so far the package is available on amd64 and
i386; the latter is no probelm technically with an i386 chroot on
amd64, it just doubles the work. I guess going back to one
architecture would not be the best way ...


Cheers,
gregor


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


signature.asc
Description: Digital Signature


Bug#762463: gnome-shell-extensions: broken on unstable (and experimental)

2014-09-23 Thread Emilio Pozuelo Monfort
On 22/09/14 17:45, Antonio Terceiro wrote:
 Package: gnome-shell-extensions
 Version: 3.13.91-1
 Severity: grave
 Justification: renders package unusable
 
 With gnome-shell 3.13.92-1 currently in unstable, no extensions in
 gnome-shell-extensions will work.
 
 Downloading the source for gnome-shell-extensions, running
 uscan+uupdate, building and installing a package from the 3.13.92
 upstream source makes all my extensions work again.

3.14 just got uploaded to sid. Can you verify that that version works fine?

Thanks,
Emilio


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



Bug#721421: libdevel-bt-perl: FTBFS on armel, hurd-i386, kfreebsd-amd64

2014-09-23 Thread gregor herrmann
On Tue, 23 Sep 2014 17:31:52 +0200, Leon Timmermans wrote:

  That's armhf on a Debian box in an unstable chroot:
 
  (sid_armhf-dchroot)gregoa@harris:~$ (echo r; echo bt; echo quit) | gdb
  --args perl -e 'unpack p, pack L!, 1' | egrep '^#'
  #1  0xb6f3f048 in Perl_newSVpv () from
  /usr/lib/arm-linux-gnueabihf/libperl.so.5.20
  #2  0x00040002 in ?? ()
 
 That looks wrong to me. Does a debugging perl show the same result?

Let's see: Same machine, same chroot, this time with perl-debug
installed:

(sid_armhf-dchroot)gregoa@harris:~$ (echo r; echo bt; echo quit) | gdb --args 
perl -e 'unpack p, pack L!, 1' | egrep '^#'
#1  0xb6f3f048 in Perl_newSVpv (my_perl=0x22008, s=0x1 error: Cannot access 
memory at address 0x1, len=0)
#2  0x00040002 in ?? ()

FTR:
$ perl -v

This is perl 5, version 20, subversion 1 (v5.20.1) built for 
arm-linux-gnueabihf-thread-multi-64int
(with 37 registered patches, see perl -V for more detail)


Cheers,
gregor

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


signature.asc
Description: Digital Signature


Bug#762484: marked as done (blas: FTBFS on *i386: xscblat1 subtests fail)

2014-09-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Sep 2014 16:03:44 +
with message-id e1xwsz6-00086e...@franck.debian.org
and subject line Bug#762484: fixed in blas 1.2.20110419-9
has caused the Debian Bug report #762484,
regarding blas: FTBFS on *i386: xscblat1 subtests fail
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.)


-- 
762484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: blas
Version: 1.2.20110419-7
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of blast for all *i386 architectures have been failing because many
of xscblat1's subtests don't quite yield the expected results; see, e.g.,
https://buildd.debian.org/status/fetch.php?pkg=blasarch=i386ver=1.2.20110419-8stamp=1411393601

Could you please take a look?

Thanks!
---End Message---
---BeginMessage---
Source: blas
Source-Version: 1.2.20110419-9

We believe that the bug you reported is fixed in the latest version of
blas, 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 762...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sébastien Villemot sebast...@debian.org (supplier of updated blas 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, 23 Sep 2014 15:44:38 +
Source: blas
Binary: libblas3 libblas-common libblas3gf libblas-dev libblas-test libblas-doc
Architecture: source amd64 all
Version: 1.2.20110419-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 
debian-science-maintain...@lists.alioth.debian.org
Changed-By: Sébastien Villemot sebast...@debian.org
Description:
 libblas-common - Dependency package for all BLAS implementations
 libblas-dev - Basic Linear Algebra Subroutines 3, static library
 libblas-doc - Basic Linear Algebra Subroutines 3, documentation
 libblas-test - Basic Linear Algebra Subroutines 3, testing programs
 libblas3   - Basic Linear Algebra Reference implementations, shared library
 libblas3gf - Transitional package for libblas
Closes: 762484
Changes:
 blas (1.2.20110419-9) unstable; urgency=medium
 .
   * On any-i386 and m68k, compile test programs with -ffloat-store. This
 has become necessary with gfortran 4.9 (maybe because the
 -fno-whole-file option has been removed, though I don't really
 understand the interaction of both options). (Closes: #762484)
Checksums-Sha1:
 d532eea419c7103b0374fe7bcc24dec1d5d56f2d 2287 blas_1.2.20110419-9.dsc
 df16ff97aa1387953b8879bf75e2c571d2263c64 46124 
blas_1.2.20110419-9.debian.tar.xz
 09fcad9d2bac2d14c5c4d879b6b8474e92a4d947 8564 libblas3gf_1.2.20110419-9_all.deb
 a239b03f49a8a676f80533d45ec75d5429269210 391880 
libblas-doc_1.2.20110419-9_all.deb
Checksums-Sha256:
 b9aec8262564cf97a7ee590f30bb3317c953b683a045c52ddf6257dcc12da13a 2287 
blas_1.2.20110419-9.dsc
 4a282d9db03dce0e56ee27022187fb2996cee8daa65d33d869315163de9ea448 46124 
blas_1.2.20110419-9.debian.tar.xz
 2c1c404ae44f3167afae9cf2caf48ce2d986795b54145ba604480738ffb853c6 8564 
libblas3gf_1.2.20110419-9_all.deb
 60724635ca5036fc633983cc4344b3f87861c3f58a920b7c476c2add010fc820 391880 
libblas-doc_1.2.20110419-9_all.deb
Files:
 e71dc1b1e15affb0e876750d719c5e46 8564 oldlibs optional 
libblas3gf_1.2.20110419-9_all.deb
 585bd742b43728cf580409bf01f05535 391880 doc optional 
libblas-doc_1.2.20110419-9_all.deb
 457cb83834375f198753887240df2b1d 2287 libs optional blas_1.2.20110419-9.dsc
 c0f394b27d60047f6c1d506600a1a371 46124 libs optional 
blas_1.2.20110419-9.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJUIZeXAAoJECzs6TUOzr5KryIP/1m8NxNeZAJgDvkuRzt98I4g
+4T1uW2Nuyj5ykudyuhp9YCx/5UmxYhcT88DybmQrCH98CW8u1lunPrjBWFoxeGz
SOe+FN7AUKEaije4K0tDOeK6CAx3jgEkcAXpM6aGOu/eEP+bAaLzCbVjApUFGQut
qwGSItOegN/0UHV5PpJWY3F5iSrk7g8C5SLKmXnCGZdupzA1IlfxTFwBrDIQGA+O
V2pcpxahpEd2anxIz478GjGGGH6I4uQGmBZUr5JhkeDStg3Vq+k40FJpYW5/f9H5
kYKQaHHwzpHOcy1AXuurIJxjEb/xW5l7+Xo0XGZrLhK8BKz85IeFrxbOZc7OTYZJ
Md+0LSBYA0sbgORlbbcjA6+ZZMuDDlcezq6872OuxCH98pS/KA00eU3n1DkVHcmF
qJxgKVFOQG4jgybeIvCPXbb5EzvUzIeu+lxpwaVKOjT7PHB4Q9vyU0zssRcUo2OU

Bug#759146: (no subject)

2014-09-23 Thread Guillermo Espertino
Bug #757247 should be merged with this, as it appears that the problem
described has the same origin.
Also, the patch to python-PIL suggested in that bug report fixes this issue.


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



Bug#762307: grub2: FTBFS on mipsel: objcopy:none_decompress.img[.text]: File truncated

2014-09-23 Thread Colin Watson
On Sun, Sep 21, 2014 at 01:39:29AM +0200, Cyril Brulebois wrote:
 your package started FTBFSing on mipsel with 2.02~beta2-12, confirmed on
 2.02~beta2-13. Hopefully pasting the right lines, sorry if the parallel
 build makes that inaccurate:
 | gcc-4.9 -DHAVE_CONFIG_H -I. -I../../../grub-core -I..  
 -Wno-unused-but-set-variable -Wall -W -I../../../include -I../include  
 -DGRUB_CPU_MIPSEL=1 -DGRUB_MACHINE_MIPS_LOONGSON=1 
 -DGRUB_MACHINE=MIPS_LOONGSON -nostdinc -isystem 
 /usr/lib/gcc/mipsel-linux-gnu/4.9/include 
 -DGRUB_FILE=\boot/mips/loongson/fuloong2f.S\ -I. -I../../../grub-core -I.. 
 -I../../.. -I../../../include -I../include 
 -I../../../grub-core/lib/libgcrypt-grub/src/ -g 
 -DGRUB_FILE=\boot/mips/loongson/fuloong2f.S\ -I. -I../../../grub-core -I.. 
 -I../../.. -I../../../include -I../include 
 -I../../../grub-core/lib/libgcrypt-grub/src/ -DASM_FILE=1 -c -o 
 boot/mips/loongson/fwstart_fuloong2f_image-fuloong2f.o `test -f 
 'boot/mips/loongson/fuloong2f.S' || echo 
 '../../../grub-core/'`boot/mips/loongson/fuloong2f.S
 | if test x0 = x1; then   ../grub-macho2img none_decompress.image 
 none_decompress.img; else   objcopy  -O binary  --strip-unneeded -R .note -R 
 .comment -R .note.gnu.build-id -R .reginfo -R .rel.dyn -R 
 .note.gnu.gold-version none_decompress.image none_decompress.img; fi
 | BFD: Warning: Writing section `.text' to huge (ie negative) file offset 
 0x7fcfff48.
 | BFD: Warning: Writing section `.data' to huge (ie negative) file offset 
 0x7fd003d8.
 | objcopy:none_decompress.img[.text]: File truncated
 | make[5]: *** [none_decompress.img] Error 1
 | make[5]: *** Waiting for unfinished jobs
 | Makefile:41812: recipe for target 'none_decompress.img' failed

Looks like
https://lists.gnu.org/archive/html/grub-devel/2014-08/msg00021.html (and
https://lists.gnu.org/archive/html/grub-devel/2014-09/msg00037.html) was
actually a general mips* problem triggered by new binutils.  Chasing
this down on grub-devel.

-- 
Colin Watson   [cjwat...@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#760191: Fixed

2014-09-23 Thread Soren Stoutner
An update to the latest packages from testing appears to have fixed this 
problem for me.  I have not yet exhaustively checked for remaining errors, but 
I an now receiving new emails.

-- 
Soren Stoutner
so...@stoutner.com
623-262-6169


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



Bug#760191: Fixed

2014-09-23 Thread Milko Krachounov
On 23 September 2014 09:15:32 Soren Stoutner wrote:
 An update to the latest packages from testing appears to have fixed this
 problem for me.  I have not yet exhaustively checked for remaining errors,
 but I an now receiving new emails.

Yes. The bug appears to be fixed now. After an upgrade the problem is gone for 
me as well, on both machines and with all three mail servers where I was 
experiencing the problem. 

I include the full list of packages that have been upgraded in the batch that 
fixed it. I realise it's a bit too extensive, but I'm not sure which packages 
might have caused the problem, so I include everything for reference.

Also some packages aren't from the official Debian archives (they come from 
Deb Multimedia), but they are all unrelated to Akonadi and KMail. I hope they 
are not an issue. :)

2014-09-23 03:13:21 status installed dbus:amd64 1.8.6-2
2014-09-23 03:13:22 status installed man-db:amd64 2.6.7.1-1
2014-09-23 03:13:41 status installed hicolor-icon-theme:all 0.13-1
2014-09-23 03:13:42 status installed libmbim-glib0:amd64 1.8.0-1
2014-09-23 03:13:44 status installed libc-bin:amd64 2.19-11
2014-09-23 03:14:02 status installed man-db:amd64 2.6.7.1-1
2014-09-23 03:14:05 status installed menu:amd64 2.1.47
2014-09-23 03:14:09 status installed mime-support:all 3.56
2014-09-23 03:14:10 status installed desktop-file-utils:amd64 0.22-1
2014-09-23 03:14:12 status installed hicolor-icon-theme:all 0.13-1
2014-09-23 03:14:13 status installed libprotobuf8:amd64 2.5.0-9
2014-09-23 03:14:14 status installed libc-bin:amd64 2.19-11
2014-09-23 03:14:35 status installed man-db:amd64 2.6.7.1-1
2014-09-23 03:14:36 status installed menu:amd64 2.1.47
2014-09-23 03:14:37 status installed mime-support:all 3.56
2014-09-23 03:14:37 status installed desktop-file-utils:amd64 0.22-1
2014-09-23 03:14:40 status installed hicolor-icon-theme:all 0.13-1
2014-09-23 03:14:41 status installed libvlccore7:amd64 1:2.1.5-dmo2
2014-09-23 03:14:42 status installed libc-bin:amd64 2.19-11
2014-09-23 03:18:23 status installed man-db:amd64 2.6.7.1-1
2014-09-23 03:19:14 status installed shared-mime-info:amd64 1.3-1
2014-09-23 03:19:15 status installed libglib2.0-0:i386 2.40.0-5
2014-09-23 03:19:16 status installed libglib2.0-0:amd64 2.40.0-5
2014-09-23 03:19:19 status installed hicolor-icon-theme:all 0.13-1
2014-09-23 03:19:20 status installed mime-support:all 3.56
2014-09-23 03:19:21 status installed desktop-file-utils:amd64 0.22-1
2014-09-23 03:19:34 status installed cups:amd64 1.7.5-1
2014-09-23 03:19:35 status installed menu:amd64 2.1.47
2014-09-23 03:19:35 status installed dbus:amd64 1.8.6-2
2014-09-23 03:19:37 status installed doc-base:all 0.10.6
2014-09-23 03:19:45 status installed python-support:all 1.0.15
2014-09-23 03:19:47 status installed libmbim-glib4:amd64 1.10.0-2
2014-09-23 03:19:47 status installed libmbim-proxy:amd64 1.10.0-2
2014-09-23 03:19:48 status installed libmm-glib0:amd64 1.4.0-1
2014-09-23 03:19:48 status installed libqmi-glib1:amd64 1.10.2-2
2014-09-23 03:19:48 status installed libqmi-proxy:amd64 1.10.2-2
2014-09-23 03:19:50 status installed libprotobuf9:amd64 2.6.0-3
2014-09-23 03:19:51 status installed mosh:amd64 1.2.4a-1+b2
2014-09-23 03:19:51 status installed libphonenumber6:amd64 6.3~svn698-3+b1
2014-09-23 03:19:51 status installed libavutil54:amd64 10:2.4-dmo1
2014-09-23 03:19:52 status installed libavutil54:i386 10:2.4-dmo1
2014-09-23 03:19:52 status installed libmp3lame0:amd64 1:3.99.5-dmo3
2014-09-23 03:19:53 status installed libmp3lame0:i386 1:3.99.5-dmo3
2014-09-23 03:19:53 status installed libswresample1:i386 10:2.4-dmo1
2014-09-23 03:19:53 status installed libswresample1:amd64 10:2.4-dmo1
2014-09-23 03:19:54 status installed libx265-31:i386 1.3-dmo1
2014-09-23 03:19:54 status installed libzvbi0:i386 0.2.33-7
2014-09-23 03:19:55 status installed libavcodec56:i386 10:2.4-dmo1
2014-09-23 03:19:56 status installed libavcodec56:amd64 10:2.4-dmo1
2014-09-23 03:19:56 status installed libchromaprint0:amd64 1.2-dmo2
2014-09-23 03:19:56 status installed clementine:amd64 1.2.3+dfsg-2+b1
2014-09-23 03:19:57 status installed libavformat56:amd64 10:2.4-dmo1
2014-09-23 03:19:57 status installed liblircclient0:amd64 0.9.0~pre1-1.1
2014-09-23 03:19:58 status installed libpostproc53:amd64 10:2.4-dmo1
2014-09-23 03:19:59 status installed libswscale3:amd64 10:2.4-dmo1
2014-09-23 03:19:59 status installed libvcdinfo0:amd64 0.7.24+dfsg-0.2
2014-09-23 03:20:00 status installed vlc-data:all 1:2.2.0~pre3-dmo2
2014-09-23 03:20:00 status installed libvlccore8:amd64 1:2.2.0~pre3-dmo2
2014-09-23 03:20:01 status installed libvlc5:amd64 1:2.2.0~pre3-dmo2
2014-09-23 03:20:01 status installed vlc-nox:amd64 1:2.2.0~pre3-dmo2
2014-09-23 03:20:01 status installed vlc:amd64 1:2.2.0~pre3-dmo2
2014-09-23 03:20:02 status installed vlc-plugin-notify:amd64 1:2.2.0~pre3-dmo2
2014-09-23 03:20:02 status installed vlc-plugin-pulse:all 1:2.2.0~pre3-dmo2
2014-09-23 03:20:02 status installed phonon-backend-vlc:amd64 1:0.8.0-dmo2

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

2014-09-23 Thread Steve Langasek
On Tue, Sep 23, 2014 at 10:47:11AM +0200, BubuXP wrote:
 Il 23/set/2014 08:51 Steve Langasek vor...@debian.org ha scritto:

  So if this is only a problem with the GNOME3 default font, please get that
  font fixed in Debian, after which I am willing to reinstate the Adobe
  engine.  But I'm not willing to enable it while it represents a regression
  vs. wheezy for a significant number of our desktop users.

 So why not changing only the default UI font in GNOME until Cantarell gets
 fixed, instead of disabling a nice improvement like that?
 Droid or DejaVu could be a valid substitute in the meanwhile.

I don't control what fonts the GNOME maintainers are using.  You'll need to
take this up with them with a bug report on the relevant packages.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: Digital signature


Bug#762604: base: debian testing and unstable don't work with a 486 PC

2014-09-23 Thread Cédric Roux
Package: base
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

I need to boot a linux system on my old 486 to access the parallel
port to do some JTAG debugging.

I use my recent PC as a NFS root server.
I ran:
  debootstrap --arch=i386 stable /tmp/debian.stable
  debootstrap --arch=i386 testing /tmp/debian.testing
  debootstrap --arch=i386 unstable /tmp/debian.unstable
And served those directories to the 486, the one after the other.

Debian stable is working.
Debian testing is not.
Debian unstable is not.

Running ls crashes with illegal instruction.
I found out that the illegal instruction is cpuid (this one
does not exist on 486 PC) which is in libpthread.so, function
__get_cpu_features.

Why is that called? I don't know. It should not.

I tried to recompile the whole gnu libc beast to not include that
function, but failed. I skip the details, I surely did something
wrong. And I don't have much time nor energy for that thing.

So I report the problem to you, just in case you plan to turn
testing into stable, because that would mean that debian will
not work on 486 PC anymore.

Maybe someone somewhere knows what to do and cares enough to
fix things. My bet is that the gnu libc thinks it will run
on at least a 586 and includes code for such computer. Is it
something in the configure of libc? Is it something with your
configuration of gcc (I see include/cpuid.h down in /usr/lib/gcc,
I suspect it should not be here, but I really don't know).
Well, I don't know.

In any case, please don't turn current testing into stable. That
would mean no more debian on 486.

In the future, if you think you fixed this problem, let me know so
I can try with my 486. (Why do some neurons up in my brain shoot
high levels of dopamine and serotonin when I read that previous
sentence, I don't know.)

Anyway, so be it. I did my part.

The following system information is from my recent PC and is
unrelated to the 486 at all, left here because, hum, why not.

Regards,
Cédric.

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

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


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



Processed: tagging 759825

2014-09-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 759825 + patch
Bug #759825 [src:audtty] audtty: FTBFS: main.c:20:31: fatal error: 
audacious/audctrl.h: No such file or directory
Added tag(s) patch.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
759825: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759825
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: severity of 762598 is grave

2014-09-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 # unusable
 severity 762598 grave
Bug #762598 {Done: Axel Beckert a...@debian.org} [libswitch-perl] 
libswitch-perl: use Switch tries to call a method on an unblessed reference
Severity set to 'grave' from 'important'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
762598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762598
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#754639: marked as done (beast-mcmc: missing build for i386)

2014-09-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Sep 2014 19:55:05 +0200
with message-id 20140923175505.gb31...@an3as.eu
and subject line Will not be distributed on other than amd64 architecture
has caused the Debian Bug report #754639,
regarding beast-mcmc: missing build for i386
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.)


-- 
754639: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: beast-mcmc
Version: 1.7.5-1
Severity: serious
Justification: FTBFS

Hi,

your package build-depends on libcolt-java which is in non-free; leading
to its being BD-Uninstallable:
  https://buildd.debian.org/status/package.php?p=beast-mcmcsuite=sid

This means you're missing an i386 build, and that prevents migration.
Recording this through this bug report accordingly.

Mraw,
KiBi.
---End Message---
---BeginMessage---
Hi,

the i386 build was removed from testing so this bug is not relevant any
more and is closed hereby.

Kind regards

   Andreas.

-- 
http://fam-tille.de---End Message---


Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron

2014-09-23 Thread David L. Craig
On 14Sep23:0956-0400, David L. Craig wrote:

 By way of a feasibility test, I had virt-manager
 Shut Down == Save the a762146 vm at its ready for
 first login state and have put the tarball of the
 124MB file it created in /var/lib/libvirt/qemu/save
 up at
 http://dlc.casita.net/~dlc/762146/a762146.vmsave.test.tar
 for you to retrieve. I expect you will also need the
 hard drive image which compressed into 5.3 GB, so we
 have a logistical difficulty there.  I am attaching
 the domain xml and parted print free output in sectors
 for the virtual disk.

Scratch that--those files were taking up too much space.
Instead, I offer you an invitation to send me an encrypted
email to which I will likewise reply with the details of
how to SFTP the files (522MB, but you should get at least
4 MB/sec bandwidth from this end) for the actual vm
condition you requested (even better--I did an
  aptitude --download-only --dist-upgrade
prior to the save).  Also, I ran it beforehand in the
constrained configuration (1 GB root, no swap) to ensure
this fails identically, and it obliged me.

I hope this works, er, you can get a successful test.
-- 
not cent from sell
May the LORD God bless you exceedingly abundantly!

Dave_Craig__
So the universe is not quite as you thought it was.
 You'd better rearrange your beliefs, then.
 Because you certainly can't rearrange the universe.
__--from_Nightfall_by_Asimov/Silverberg_


signature.asc
Description: Digital signature


Bug#762547: oss-compat: Upgrade to compat_2+deb7u1 fails during configure

2014-09-23 Thread Juhani Karlsson

Same error here, purge and reinstall fixed.



apt-get update  apt-get -u dist-upgrade
Hit ftp://ftp.fi.debian.org wheezy Release.gpg
Get:1 http://dl.google.com stable Release.gpg [198 B]
...
...
...
...
Ign http://download.virtualbox.org wheezy/contrib Translation-en
Ign http://download.virtualbox.org wheezy/contrib Translation-fi
Fetched 2 738 B in 6s (442 B/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  apt apt-doc apt-utils libapt-inst1.5 libapt-pkg4.12 libsnmp-base 
libsnmp15 oss-compat

8 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/6 250 kB of archives.
After this operation, 105 kB disk space will be freed.
Do you want to continue [Y/n]?
Retrieving bug reports... 0%
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
serious bugs of oss-compat (2 - 2+deb7u1) tagged as pending a fix
 #762547 - oss-compat: Upgrade to compat_2+deb7u1 fails during configure
Summary:
 oss-compat(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...]
Reading changelogs...
(Reading database ... 24 files and directories currently installed.)
Preparing to replace libapt-pkg4.12:i386 0.9.7.9+deb7u4 (using 
.../libapt-pkg4.12_0.9.7.9+deb7u5_i386.deb) ...

Unpacking replacement libapt-pkg4.12:i386 ...
Setting up libapt-pkg4.12:i386 (0.9.7.9+deb7u5) ...
(Reading database ... 24 files and directories currently installed.)
Preparing to replace apt 0.9.7.9+deb7u4 (using 
.../apt_0.9.7.9+deb7u5_i386.deb) ...

Unpacking replacement apt ...
Processing triggers for man-db ...
Setting up apt (0.9.7.9+deb7u5) ...
gpg: key B98321F9: Squeeze Stable Release Key 
debian-rele...@lists.debian.org not changed
gpg: key 473041FA: Debian Archive Automatic Signing Key (6.0/squeeze) 
ftpmas...@debian.org not changed
gpg: key 65FFB764: Wheezy Stable Release Key 
debian-rele...@lists.debian.org not changed
gpg: key 46925553: Debian Archive Automatic Signing Key (7.0/wheezy) 
ftpmas...@debian.org not changed

gpg: Total number processed: 4
gpg:  unchanged: 4
(Reading database ... 24 files and directories currently installed.)
Preparing to replace libapt-inst1.5:i386 0.9.7.9+deb7u4 (using 
.../libapt-inst1.5_0.9.7.9+deb7u5_i386.deb) ...

Unpacking replacement libapt-inst1.5:i386 ...
Preparing to replace apt-utils 0.9.7.9+deb7u4 (using 
.../apt-utils_0.9.7.9+deb7u5_i386.deb) ...

Unpacking replacement apt-utils ...
Preparing to replace apt-doc 0.9.7.9+deb7u4 (using 
.../apt-doc_0.9.7.9+deb7u5_all.deb) ...

Unpacking replacement apt-doc ...
Preparing to replace libsnmp-base 5.4.3~dfsg-2.8 (using 
.../libsnmp-base_5.4.3~dfsg-2.8+deb7u1_all.deb) ...

Unpacking replacement libsnmp-base ...
Preparing to replace libsnmp15 5.4.3~dfsg-2.8 (using 
.../libsnmp15_5.4.3~dfsg-2.8+deb7u1_i386.deb) ...

Unpacking replacement libsnmp15 ...
Preparing to replace oss-compat 2 (using 
.../oss-compat_2+deb7u1_i386.deb) ...

Unpacking replacement oss-compat ...
Processing triggers for man-db ...
Setting up libapt-inst1.5:i386 (0.9.7.9+deb7u5) ...
Setting up apt-utils (0.9.7.9+deb7u5) ...
Setting up apt-doc (0.9.7.9+deb7u5) ...
Setting up libsnmp-base (5.4.3~dfsg-2.8+deb7u1) ...
Setting up libsnmp15 (5.4.3~dfsg-2.8+deb7u1) ...
Setting up oss-compat (2+deb7u1) ...
cp: missing destination file operand after `/lib/oss-compat/linux'
Try `cp --help' for more information.
dpkg: error processing oss-compat (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 oss-compat
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@abcdef:~#



apt-get update  apt-get -u dist-upgrade
Hit http://security.debian.org wheezy/updates Release.gpg
Hit ftp://ftp.fi.debian.org wheezy Release.gpg
...
...
...
...
Ign http://download.virtualbox.org wheezy/contrib Translation-en
Ign http://download.virtualbox.org wheezy/contrib Translation-fi
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]?
Setting up oss-compat (2+deb7u1) ...
cp: missing destination file operand after `/lib/oss-compat/linux'
Try `cp --help' for more information.
dpkg: error processing oss-compat (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 oss-compat
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@abcdef:~#



root@abcdef:~# apt-get remove oss-compat --purge
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  oss-compat*
0 upgraded, 0 newly installed, 1 to remove and 0 not 

Bug#741813: fence-agents: NMU diff for bug#741813

2014-09-23 Thread Aurelien Jarno
Hi,

I have just done an NMU of fence-agents to fix this long standing bug.
You will find the corresponding diff attached.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


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



Bug#741813: fence-agents: NMU diff for bug#741813

2014-09-23 Thread Aurelien Jarno
Hi,

I have just done an NMU of fence-agents to fix this long standing bug.
You will find the corresponding diff attached.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
diff -Nru fence-agents-4.0.7.1/debian/changelog fence-agents-4.0.7.1/debian/changelog
--- fence-agents-4.0.7.1/debian/changelog	2014-02-21 14:20:50.0 +0100
+++ fence-agents-4.0.7.1/debian/changelog	2014-09-23 20:58:24.0 +0200
@@ -1,3 +1,10 @@
+fence-agents (4.0.7.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add libxml2-utils to Build-Depends to get xmllint (Closes: #741813).
+
+ -- Aurelien Jarno aure...@debian.org  Tue, 23 Sep 2014 20:58:23 +0200
+
 fence-agents (4.0.7.1-2) unstable; urgency=medium
 
   * New upstream release 
diff -Nru fence-agents-4.0.7.1/debian/control fence-agents-4.0.7.1/debian/control
--- fence-agents-4.0.7.1/debian/control	2014-02-21 14:20:32.0 +0100
+++ fence-agents-4.0.7.1/debian/control	2014-09-23 21:00:37.0 +0200
@@ -17,6 +17,7 @@
python-pycurl,
python-suds,
xsltproc,
+   libxml2-utils,
libnet-telnet-perl,
 	   dh-autoreconf,
 	   hardening-wrapper


Bug#762547: oss-compat: Upgrade to compat_2+deb7u1 fails during configure

2014-09-23 Thread Ant
Awesome. That worked for me too! It seems like left overs were 
messing with the upgrade. Thanks. :)


On Tue, Sep 23, 2014 at 10:01:17PM +0300, Juhani Karlsson wrote:
 Same error here, purge and reinstall fixed.
 
 
 
 apt-get update  apt-get -u dist-upgrade
 Hit ftp://ftp.fi.debian.org wheezy Release.gpg
 Get:1 http://dl.google.com stable Release.gpg [198 B]
 ...
 ...
 ...
 ...
 Ign http://download.virtualbox.org wheezy/contrib Translation-en
 Ign http://download.virtualbox.org wheezy/contrib Translation-fi
 Fetched 2 738 B in 6s (442 B/s)
 Reading package lists... Done
 Reading package lists... Done
 Building dependency tree
 Reading state information... Done
 Calculating upgrade... Done
 The following packages will be upgraded:
   apt apt-doc apt-utils libapt-inst1.5 libapt-pkg4.12 libsnmp-base libsnmp15
 oss-compat
 8 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
 Need to get 0 B/6 250 kB of archives.
 After this operation, 105 kB disk space will be freed.
 Do you want to continue [Y/n]?
 Retrieving bug reports... 0%
 Retrieving bug reports... Done
 Parsing Found/Fixed information... Done
 serious bugs of oss-compat (2 - 2+deb7u1) tagged as pending a fix
  #762547 - oss-compat: Upgrade to compat_2+deb7u1 fails during configure
 Summary:
  oss-compat(1 bug)
 Are you sure you want to install/upgrade the above packages? [Y/n/?/...]
 Reading changelogs...
 (Reading database ... 24 files and directories currently installed.)
 Preparing to replace libapt-pkg4.12:i386 0.9.7.9+deb7u4 (using
 .../libapt-pkg4.12_0.9.7.9+deb7u5_i386.deb) ...
 Unpacking replacement libapt-pkg4.12:i386 ...
 Setting up libapt-pkg4.12:i386 (0.9.7.9+deb7u5) ...
 (Reading database ... 24 files and directories currently installed.)
 Preparing to replace apt 0.9.7.9+deb7u4 (using
 .../apt_0.9.7.9+deb7u5_i386.deb) ...
 Unpacking replacement apt ...
 Processing triggers for man-db ...
 Setting up apt (0.9.7.9+deb7u5) ...
 gpg: key B98321F9: Squeeze Stable Release Key
 debian-rele...@lists.debian.org not changed
 gpg: key 473041FA: Debian Archive Automatic Signing Key (6.0/squeeze)
 ftpmas...@debian.org not changed
 gpg: key 65FFB764: Wheezy Stable Release Key
 debian-rele...@lists.debian.org not changed
 gpg: key 46925553: Debian Archive Automatic Signing Key (7.0/wheezy)
 ftpmas...@debian.org not changed
 gpg: Total number processed: 4
 gpg:  unchanged: 4
 (Reading database ... 24 files and directories currently installed.)
 Preparing to replace libapt-inst1.5:i386 0.9.7.9+deb7u4 (using
 .../libapt-inst1.5_0.9.7.9+deb7u5_i386.deb) ...
 Unpacking replacement libapt-inst1.5:i386 ...
 Preparing to replace apt-utils 0.9.7.9+deb7u4 (using
 .../apt-utils_0.9.7.9+deb7u5_i386.deb) ...
 Unpacking replacement apt-utils ...
 Preparing to replace apt-doc 0.9.7.9+deb7u4 (using
 .../apt-doc_0.9.7.9+deb7u5_all.deb) ...
 Unpacking replacement apt-doc ...
 Preparing to replace libsnmp-base 5.4.3~dfsg-2.8 (using
 .../libsnmp-base_5.4.3~dfsg-2.8+deb7u1_all.deb) ...
 Unpacking replacement libsnmp-base ...
 Preparing to replace libsnmp15 5.4.3~dfsg-2.8 (using
 .../libsnmp15_5.4.3~dfsg-2.8+deb7u1_i386.deb) ...
 Unpacking replacement libsnmp15 ...
 Preparing to replace oss-compat 2 (using .../oss-compat_2+deb7u1_i386.deb)
 ...
 Unpacking replacement oss-compat ...
 Processing triggers for man-db ...
 Setting up libapt-inst1.5:i386 (0.9.7.9+deb7u5) ...
 Setting up apt-utils (0.9.7.9+deb7u5) ...
 Setting up apt-doc (0.9.7.9+deb7u5) ...
 Setting up libsnmp-base (5.4.3~dfsg-2.8+deb7u1) ...
 Setting up libsnmp15 (5.4.3~dfsg-2.8+deb7u1) ...
 Setting up oss-compat (2+deb7u1) ...
 cp: missing destination file operand after `/lib/oss-compat/linux'
 Try `cp --help' for more information.
 dpkg: error processing oss-compat (--configure):
  subprocess installed post-installation script returned error exit status 1
 Errors were encountered while processing:
  oss-compat
 E: Sub-process /usr/bin/dpkg returned an error code (1)
 root@abcdef:~#
 
 
 
 apt-get update  apt-get -u dist-upgrade
 Hit http://security.debian.org wheezy/updates Release.gpg
 Hit ftp://ftp.fi.debian.org wheezy Release.gpg
 ...
 ...
 ...
 ...
 Ign http://download.virtualbox.org wheezy/contrib Translation-en
 Ign http://download.virtualbox.org wheezy/contrib Translation-fi
 Reading package lists... Done
 Building dependency tree
 Reading state information... Done
 Calculating upgrade... Done
 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
 1 not fully installed or removed.
 After this operation, 0 B of additional disk space will be used.
 Do you want to continue [Y/n]?
 Setting up oss-compat (2+deb7u1) ...
 cp: missing destination file operand after `/lib/oss-compat/linux'
 Try `cp --help' for more information.
 dpkg: error processing oss-compat (--configure):
  subprocess installed post-installation script returned error exit status 1
 Errors were encountered while processing:
  oss-compat
 E: Sub-process /usr/bin/dpkg returned an error code (1)
 

Bug#741813: marked as done (fence-agents: FTBFS: /bin/bash: line 3: xmllint: command not found)

2014-09-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Sep 2014 19:18:52 +
with message-id e1xwvbw-ua...@franck.debian.org
and subject line Bug#741813: fixed in fence-agents 4.0.7.1-2.1
has caused the Debian Bug report #741813,
regarding fence-agents: FTBFS: /bin/bash: line 3: xmllint: command not found
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.)


-- 
741813: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: fence-agents
Version: 4.0.7.1-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140315 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
 make[5]: Entering directory `/«PKGBUILDDIR»/fence/agents/xenapi'
 bash ../../../scripts/fenceparse \
   ../../../make/copyright.cf REDHAT_COPYRIGHT \
   UNKNOWN \
   /«PKGBUILDDIR»/fence/agents/xenapi fence_xenapi | \
   sed \
   -e 's#@''FENCEAGENTSLIBDIR@#/usr/share/fence#g' \
   -e 's#@''SNMPBIN@#/usr/bin#g' \
   -e 's#@''LOGDIR@#/var/log/cluster#g' \
   -e 's#@''SBINDIR@#/usr/sbin#g' \
   -e 's#@''LIBEXECDIR@#/usr/lib/fence-agents#g' \
   -e 's#@''IPMITOOL_PATH@#/usr/bin/ipmitool#g' \
   -e 's#@''AMTTOOL_PATH@#/usr/bin/amttool#g' \
   -e 's#@''GNUTLSCLI_PATH@#/usr/bin/gnutls-cli#g' \
fence_xenapi
 if [ 0 -eq `echo fence_xenapi.py | grep fence_  /dev/null; echo $?` ]; 
 then \
   
 PYTHONPATH=/«PKGBUILDDIR»/fence/agents/xenapi/../lib:/«PKGBUILDDIR»/fence/agents/xenapi/../lib
  ../../../fence/agents/lib/check_used_options.py fence_xenapi; \
   else true ; fi
 set -e  \
   
 PYTHONPATH=/«PKGBUILDDIR»/fence/agents/xenapi/../lib:/«PKGBUILDDIR»/fence/agents/xenapi/../lib
  \
   python fence_xenapi ../../../fence/agents/lib/fence2man.xsl -o 
 metadata  .fence_xenapi.8.tmp  \
   xmllint --noout --relaxng 
 /«PKGBUILDDIR»/fence/agents/xenapi/../lib/metadata.rng .fence_xenapi.8.tmp  
 \
   xsltproc ../../../fence/agents/lib/fence2man.xsl .fence_xenapi.8.tmp  
 fence_xenapi.8
 /bin/bash: line 3: xmllint: command not found
 make[5]: *** [fence_xenapi.8] Error 127

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/03/15/fence-agents_4.0.7.1-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---
---BeginMessage---
Source: fence-agents
Source-Version: 4.0.7.1-2.1

We believe that the bug you reported is fixed in the latest version of
fence-agents, 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 741...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno aure...@debian.org (supplier of updated fence-agents 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, 23 Sep 2014 20:58:23 +0200
Source: fence-agents
Binary: fence-agents
Architecture: source
Version: 4.0.7.1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers 
debian-ha-maintain...@lists.alioth.debian.org
Changed-By: Aurelien Jarno aure...@debian.org
Description:
 fence-agents - Fence Agents for Red Hat Cluster
Closes: 741813
Changes:
 fence-agents (4.0.7.1-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add libxml2-utils to Build-Depends to get xmllint (Closes: #741813).
Checksums-Sha1:
 fd708249bdb1c16a58ccad16ab29f00a2ac93586 2098 fence-agents_4.0.7.1-2.1.dsc
 ead9578f0d7ca5433746ca88b230f39afda6b864 3004 
fence-agents_4.0.7.1-2.1.debian.tar.xz
Checksums-Sha256:
 a9831e9ceae3f63996267c7c314c9ebf6fe002a34087ab8423f6f22d77c88940 2098 
fence-agents_4.0.7.1-2.1.dsc
 ef5ed44965ce109c88ff0f2528af3bead77a4cfb1093e05d141310f42e389133 3004 

Bug#762547: marked as done (oss-compat: Upgrade to compat_2+deb7u1 fails during configure)

2014-09-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Sep 2014 19:17:05 +
with message-id e1xwvad-mn...@franck.debian.org
and subject line Bug#762547: fixed in oss-compat 2+deb7u2
has caused the Debian Bug report #762547,
regarding oss-compat: Upgrade to compat_2+deb7u1 fails during configure
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.)


-- 
762547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: oss-compat
Version: 2+deb7u1
Severity: serious
Justification: Policy 6.1

Dear Maintainer,
I just upgraded my machine and that included oss-compat.
During the dpkg configuration phase it failed.

Here's the output from the session:
(Reading database ... 271246 files and directories currently installed.)
Preparing to replace libsnmp-base 5.4.3~dfsg-2.8 (using 
.../libsnmp-base_5.4.3~dfsg-2.8+deb7u1_all.deb) ...
Unpacking replacement libsnmp-base ...
Preparing to replace libsnmp-dev 5.4.3~dfsg-2.8 (using 
.../libsnmp-dev_5.4.3~dfsg-2.8+deb7u1_amd64.deb) ...
Unpacking replacement libsnmp-dev ...
Preparing to replace libsnmp-perl 5.4.3~dfsg-2.8 (using 
.../libsnmp-perl_5.4.3~dfsg-2.8+deb7u1_amd64.deb) ...
Unpacking replacement libsnmp-perl ...
Preparing to replace libsnmp15 5.4.3~dfsg-2.8 (using 
.../libsnmp15_5.4.3~dfsg-2.8+deb7u1_amd64.deb) ...
Unpacking replacement libsnmp15 ...
Preparing to replace snmp 5.4.3~dfsg-2.8 (using 
.../snmp_5.4.3~dfsg-2.8+deb7u1_amd64.deb) ...
Unpacking replacement snmp ...
Preparing to replace oss-compat 2 (using .../oss-compat_2+deb7u1_amd64.deb) ...
Unpacking replacement oss-compat ...
Processing triggers for man-db ...
Setting up libsnmp-base (5.4.3~dfsg-2.8+deb7u1) ...
Setting up libsnmp15 (5.4.3~dfsg-2.8+deb7u1) ...
Setting up libsnmp-perl (5.4.3~dfsg-2.8+deb7u1) ...
Setting up libsnmp-dev (5.4.3~dfsg-2.8+deb7u1) ...
Setting up snmp (5.4.3~dfsg-2.8+deb7u1) ...
Setting up oss-compat (2+deb7u1) ...
cp: missing destination file operand after `/lib/oss-compat/linux'
Try `cp --help' for more information.
dpkg: error processing oss-compat (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 oss-compat
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up oss-compat (2+deb7u1) ...
cp: missing destination file operand after `/lib/oss-compat/linux'
Try `cp --help' for more information.
dpkg: error processing oss-compat (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 oss-compat


My guess is that the problem is in:
/var/lib/dpkg/info/oss-compat.postinst

On line 36:
[ -f ${curconffile} ]  [ $(md5sum ${curconffile} | cut -d\  -f1) = 
88222606b0a3ba8b0825c5000c754e6f ]  cp /lib/oss-compat/linux ${conffile}

${conffile} is not mentioned in any other places in that script, so if it's not 
being set somewhere else that would be the reason for the cp command to fail.

I have not yet tried to fix the issue but I suspect that a purge/re-install 
would to the trick..


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

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

Versions of packages oss-compat depends on:
ii  kmod  9-3

oss-compat recommends no packages.

oss-compat suggests no packages.

-- no debconf information
---End Message---
---BeginMessage---
Source: oss-compat
Source-Version: 2+deb7u2

We believe that the bug you reported is fixed in the latest version of
oss-compat, 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 762...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stephen Kitt sk...@debian.org (supplier of updated oss-compat 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, 23 Sep 2014 10:40:38 +0200
Source: oss-compat
Binary: oss-compat

Processed: your mail

2014-09-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tag 755588 + pending
Bug #755588 [src:django-auth-ldap] django-auth-ldap: Please ensure it works 
with Django 1.7
Added tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
755588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755588
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#721421: libdevel-bt-perl: FTBFS on armel, hurd-i386, kfreebsd-amd64

2014-09-23 Thread Niko Tyni
On Tue, Sep 23, 2014 at 05:50:00PM +0200, gregor herrmann wrote:
 On Tue, 23 Sep 2014 17:31:52 +0200, Leon Timmermans wrote:
 
   That's armhf on a Debian box in an unstable chroot:
  
   (sid_armhf-dchroot)gregoa@harris:~$ (echo r; echo bt; echo quit) | gdb
   --args perl -e 'unpack p, pack L!, 1' | egrep '^#'
   #1  0xb6f3f048 in Perl_newSVpv () from
   /usr/lib/arm-linux-gnueabihf/libperl.so.5.20
   #2  0x00040002 in ?? ()
  
  That looks wrong to me. Does a debugging perl show the same result?
 
 Let's see: Same machine, same chroot, this time with perl-debug
 installed:
 
 (sid_armhf-dchroot)gregoa@harris:~$ (echo r; echo bt; echo quit) | gdb --args 
 perl -e 'unpack p, pack L!, 1' | egrep '^#'
 #1  0xb6f3f048 in Perl_newSVpv (my_perl=0x22008, s=0x1 error: Cannot access 
 memory at address 0x1, len=0)
 #2  0x00040002 in ?? ()

I've reproduced this armhf issue and filed #762620 against gdb about it.
I think removing the armhf binaries of libdevel-bt-perl is a reasonable
workaround for this, but let's give the gdb maintainer a bit of time
to investigate first. (Removing the binaries would mean that we don't
provide an armhf version of the package unless it starts working again.)

I also had a look at the mips one, and there the problem doesn't seem
to be with the backtrace, as running gdb separately works as expected.
However, running perl with -d:bt doesn't seem to do anything. It looks
like the host is just too slow; inserting a 'sleep(1)' just before the
thread apply all backtrace command in stack_trace() fixes it for
me. Perhaps the code should just check that the fd is ready for writing?
-- 
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#762463: marked as done (gnome-shell-extensions: broken on unstable (and experimental))

2014-09-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Sep 2014 17:34:17 -0300
with message-id 20140923203417.ga...@debian.org
and subject line Re: Bug#762463: gnome-shell-extensions: broken on unstable 
(and experimental)
has caused the Debian Bug report #762463,
regarding gnome-shell-extensions: broken on unstable (and experimental)
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.)


-- 
762463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: gnome-shell-extensions
Version: 3.13.91-1
Severity: grave
Justification: renders package unusable

With gnome-shell 3.13.92-1 currently in unstable, no extensions in
gnome-shell-extensions will work.

Downloading the source for gnome-shell-extensions, running
uscan+uupdate, building and installing a package from the 3.13.92
upstream source makes all my extensions work again.

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

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

Versions of packages gnome-shell-extensions depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.20.0-2
ii  gir1.2-gtop-2.0  2.28.5-2
ii  gnome-session3.12.1-3
ii  gnome-shell  3.13.92-1
ii  gvfs 1.20.3-1

Versions of packages gnome-shell-extensions recommends:
ii  gnome-tweak-tool  3.12.0-2

gnome-shell-extensions suggests no packages.

-- no debconf information

-- 
Antonio Terceiro terce...@debian.org


signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
On Tue, Sep 23, 2014 at 05:44:44PM +0200, Emilio Pozuelo Monfort wrote:
 On 22/09/14 17:45, Antonio Terceiro wrote:
  Package: gnome-shell-extensions
  Version: 3.13.91-1
  Severity: grave
  Justification: renders package unusable
  
  With gnome-shell 3.13.92-1 currently in unstable, no extensions in
  gnome-shell-extensions will work.
  
  Downloading the source for gnome-shell-extensions, running
  uscan+uupdate, building and installing a package from the 3.13.92
  upstream source makes all my extensions work again.
 
 3.14 just got uploaded to sid. Can you verify that that version works fine?

It does, thanks.

Am I confused, or we do have GNOME 3.14 before the actual upstream
release announcement? That looks awesome, thanks a lot! :-)

-- 
Antonio Terceiro terce...@debian.org


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


Processed: severity of 753684 is normal

2014-09-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 753684 normal
Bug #753684 [ifupdown] ifupdown: Dead symlinks in /etc/network/if-pre-up.d 
block networking
Severity set to 'normal' from 'serious'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
753684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753684
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: severity of 727073 is normal

2014-09-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 727073 normal
Bug #727073 [ifupdown] ifupdown: current version somehow brings the ifaces up 
too late
Severity set to 'normal' from 'critical'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
727073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727073
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#762630: radiotray: Segmentation fault after upgrade to GNOME 3.14: Attempt to unlock mutex that was not locked

2014-09-23 Thread Paul Menzel
Package: radiotray
Version: 0.7.3-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Debian folks,


upgrading GNOME Shell from 3.12.2-3 to 3.13.92-1 (3.14-1) – and the
related packages – RadioTray crashes with `SIGABRT`. The core dump file
does not help.

Core was generated by `/usr/bin/python /usr/bin/radiotray'.
Program terminated with signal SIGABRT, Aborted.
#0  0xb771dd4c in __kernel_vsyscall ()
(gdb) t a a bt

Thread 1 (LWP 11731):
#0  0xb771dd4c in __kernel_vsyscall ()
#1  0xb74d8267 in ?? ()
#2  0xb7651000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

The only error message I see is: `Attempt to unlock mutex that was not locked`.


Thanks,

Paul

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

Kernel: Linux 3.16-2-686-pae (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/bash

Versions of packages radiotray depends on:
ii  gstreamer0.10-plugins-base  0.10.36-2
ii  gstreamer0.10-plugins-good  0.10.31-3+nmu4
ii  gstreamer0.10-plugins-ugly  0.10.19-2.1
ii  python  2.7.8-1
ii  python-dbus 1.2.0-2+b3
ii  python-glade2   2.24.0-4
ii  python-gobject  3.12.2-1
ii  python-gst0.10  0.10.22-3
ii  python-gtk2 2.24.0-4
ii  python-lxml 3.4.0-1
ii  python-notify   0.1.1-3
ii  python-xdg  0.25-4

radiotray recommends no packages.

radiotray suggests no packages.

-- no debconf information


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


Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron

2014-09-23 Thread David L. Craig
Another datum: I decided to try switching back to
systemd-sysv on my primary bare-metal Sid and the
update was textbook:

ii  libpam-systemd:amd64  215-4
ii  libsystemd-id128-0:amd64  215-4
ii  libsystemd-journal0:amd64 215-4
ii  libsystemd-login0:amd64   215-4
ii  libsystemd-login0:i386215-4
ii  libsystemd0:amd64 215-4
ii  libsystemd0:i386  215-4
ii  systemd   215-4
ii  systemd-shim  8-2
ii  systemd-sysv  215-4
ii  systemd-ui3-2
-- 
not cent from sell
May the LORD God bless you exceedingly abundantly!

Dave_Craig__
So the universe is not quite as you thought it was.
 You'd better rearrange your beliefs, then.
 Because you certainly can't rearrange the universe.
__--from_Nightfall_by_Asimov/Silverberg_


signature.asc
Description: Digital signature


Bug#762403: gtk+ build failures

2014-09-23 Thread Andreas Henriksson
Hello!

For the record, the build failure on armel, arm64 and mipsel
is because of the gtk-reftest test failing.

(On mips the build seems to hang and eventually get killed
for unknown reason.)

A test build has been performed on armel schroot on a porter
box (abel) and the problem is reproducible.
As can be seen in the attached output from gtk-reftest there
are spurious pixels in the output.
A brief discussion with upstream developer Benjamin Otte
suggested that one possible cause for this might be
(incorrect/failing?) optimizations in pixman being
different on different architectures, but real investigation
is needed.

Other non-armel failing architectures have not been tested.

Regards,
Andreas Henriksson


Bug#760191: marked as done (akonadi-server: After upgrade 1.13.0-1 of akonadi-server, no new mail in IMAP folders is ever read)

2014-09-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Sep 2014 23:50:01 +0200
with message-id 20140923215001.gm14...@gnuservers.com.ar
and subject line Re: Bug#760191: Fixed
has caused the Debian Bug report #760191,
regarding akonadi-server: After upgrade 1.13.0-1 of akonadi-server, no new mail 
in IMAP folders is ever read
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.)


-- 
760191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: akonadi-server
Version: 1.13.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After upgrading two jessie machines to newest akonadi (1.13.0) and KDE, as well 
as libqt4-sql-mysql (4.8.6+git49-gbc62005+dfsg-1), any mails received since the 
upgrade (2014-08-29 and this morning, respectively) are not seen by kmail. 
There are no relevant errors in the akonadi error log (note to self: stop 
trying to use it, it is never going to get better), I cannot give any more 
details. I suspect the bug is triggered by libqt4-sql-mysql, because checking 
my last email timestamps would seem to correspond with it (it was pushed later 
than the other packages), but I have no way to tell for sure.

I have the following in a past akonadi server log, but it isn't present in any 
current one:
Control process died, committing suicide!

Also, akonadi control log contains the following on both machines, but it seems 
unrelated:
Executable akonadi_nepomuk_feeder for agent akonadi_nepomuk_feeder could 
not be found! 
Executable akonadi_folderarchive_agent for agent 
akonadi_folderarchive_agent could not be found! 

I manually ran mysql_upgrade on one of the machines, because MySQL was 
complaining about outdated tables. The other has not displayed any difference 
in logs. 

My mysql is version 5.5.37-1 (missing from the report below for some reason).

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

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

Versions of packages akonadi-server depends on:
ii  akonadi-backend-mysql   1.13.0-1
ii  libakonadiprotocolinternals11.13.0-1
ii  libboost-program-options1.55.0  1.55.0+dfsg-2
ii  libc6   2.19-9
ii  libgcc1 1:4.9.1-4
ii  libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-1
ii  libqt4-network  4:4.8.6+git64-g5dc8b2b+dfsg-1
ii  libqt4-sql  4:4.8.6+git64-g5dc8b2b+dfsg-1
ii  libqt4-xml  4:4.8.6+git64-g5dc8b2b+dfsg-1
ii  libqtcore4  4:4.8.6+git64-g5dc8b2b+dfsg-1
ii  libqtgui4   4:4.8.6+git64-g5dc8b2b+dfsg-1
ii  libstdc++6  4.9.1-4

akonadi-server recommends no packages.

Versions of packages akonadi-server suggests:
ii  akonadi-backend-mysql   1.13.0-1
pn  akonadi-backend-postgresql  none
pn  akonadi-backend-sqlite  none

-- no debconf information
---End Message---
---BeginMessage---
Version: 1.13.0-2

Hi,

Ok, clossing the bug the as it has been reported as fixed. Although I doubt
the changes in 1.13.0-2 are really related to this bug, I think the real
problem was in kdepim-runtime.

Happy hacking,
-- 
Executive ability is deciding quickly and getting somebody else to do the
work.
-- Pollard's Postulate
Saludos /\/\ /\  `/


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


Bug#679607: python-pywbem and sblim-wbemcli: error when trying to install together

2014-09-23 Thread Ferenc Wagner
Ferenc Wagner wf...@niif.hu writes:

 Ferenc Wagner wf...@niif.hu writes:

 Ferenc Wagner wf...@niif.hu writes:

 Bernd Zeimetz be...@bzed.de writes:

 I'm preparing a new upload of sblim-wbemcli.  Shall I rename the
 contained wbemcli binary, or do you still plan letting me use that
 name?

 given the low popcon and pywebem not being devleoped by upstream
 anymore, I think it would be okay for you to take the name, if we find
 a proper way to let people know about it. I guess pywbem could ship
 wbemcli.py instead, then it would be obvious.

 I agree.

 What would you think about a debconf notice which is displayed only to
 those who have python-wbem installed? or something like that?
 Do you have better ideas?

 I could most certainly add a notice like that.  However, this is
 actually a change in pywbem, thus I feel like it should be documented
 there.  I also think a NEWS entry would be more than enough, as the
 current wbemcli binary in pywbem looks more like an example than a
 readily usable utility, so I don't expect a wide affected user base.

 If the above plan does not work for you, please let me know.  I'm still
 holding back a new upload with some bugfixes.

 Could you please provide some feedback on this issue, so that we can
 make progress with this bug?  You seemed to kindly agree to rename the
 binary in python-pywbem.  If you still do, please reassing this bug to
 python-pywbem.  If not, please state it, and I'll take care of it in
 sblim-wbemcli.

Hi Bernd,

Please, pretty please express your current opinion on this bug.  Freeze
is approaching quickly, it would be a shame to miss it again.  Will you
rename the wbemcli binary in python-pywbem?  If yes, or if you don't
want to ship python-pywbem in jessie, please reassign this bug to it.
Otherwise please drop me a note and I'll reassign this bug to
sblim-wbemcli and fix it there.
-- 
Looking forward to hearing from you soon,
Feri.


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



Bug#762638: missing source: Configure

2014-09-23 Thread Helmut Grohne
Package: src:perl
Version: 5.20.1-1
Severity: serious
Justification: missing source
User: helm...@debian.org
Usertags: rebootstrap

Dear perl maintainers,

I approach you with a difficult matter. The Configure script
distributed with the perl source package claims that it is being
generated. Porting/pumpkin.pod claims that Configure can be re-created
by invoking metaconfig -m. Indeed, there is a metaconfig binary in the
dist package. Running it on the perl tree does create a Configure that
remotely resembles the shipped Configure with a diff of about 18000
lines (75%). In the recreated Configure many tests are missing and perl
won't build. It seems that perl's Configure cannot be recreated from
Debian sources.

These observations let me conclude that the perl package - in spirit -
violates the DFSG by not providing the sources for Configure. I still
hope that this conclusion is flawed and ask you to adjust the severity
accordingly.

Helmut


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



Processed: found 762638 in 5.20.0-6

2014-09-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 # this should avoid that this surely not new issue interacts with the current 
 perl mini-transition
 found 762638 5.20.0-6
Bug #762638 [src:perl] missing source: Configure
Marked as found in versions perl/5.20.0-6.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
762638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762638
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#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron

2014-09-23 Thread David L. Craig
On 14Sep23:1719-0400, David L. Craig wrote:

 Another datum: I decided to try switching back to
 systemd-sysv on my primary bare-metal Sid and the
 update was textbook:
 
 ii  libpam-systemd:amd64  215-4
 ii  libsystemd-id128-0:amd64  215-4
 ii  libsystemd-journal0:amd64 215-4
 ii  libsystemd-login0:amd64   215-4
 ii  libsystemd-login0:i386215-4
 ii  libsystemd0:amd64 215-4
 ii  libsystemd0:i386  215-4
 ii  systemd   215-4
 ii  systemd-shim  8-2
 ii  systemd-sysv  215-4
 ii  systemd-ui3-2

So I tried running the test case on the bare metal again,
but it still fails. :-(
-- 
not cent from sell
May the LORD God bless you exceedingly abundantly!

Dave_Craig__
So the universe is not quite as you thought it was.
 You'd better rearrange your beliefs, then.
 Because you certainly can't rearrange the universe.
__--from_Nightfall_by_Asimov/Silverberg_


signature.asc
Description: Digital signature


Bug#762638: missing source: Configure

2014-09-23 Thread Dominic Hargreaves
[resending to the bug, sorry about the duplicate]

On Wed, Sep 24, 2014 at 12:18:06AM +0200, Helmut Grohne wrote:

 I approach you with a difficult matter. The Configure script
 distributed with the perl source package claims that it is being
 generated. Porting/pumpkin.pod claims that Configure can be re-created
 by invoking metaconfig -m. Indeed, there is a metaconfig binary in the
 dist package. Running it on the perl tree does create a Configure that
 remotely resembles the shipped Configure with a diff of about 18000
 lines (75%). In the recreated Configure many tests are missing and perl
 won't build. It seems that perl's Configure cannot be recreated from
 Debian sources.
 
 These observations let me conclude that the perl package - in spirit -
 violates the DFSG by not providing the sources for Configure. I still
 hope that this conclusion is flawed and ask you to adjust the severity
 accordingly.

metaconfig is meant to be run according to this recipe:

http://perl5.git.perl.org/metaconfig.git/blob/HEAD:/README

it won't be a perfect match, as manual patching of the file is
allowed (see the comments) and indeed we patch Configure in the
Debian package.

We could certainly document this better (in README.source) but I am
not convinced that this deserves RC severity.

Dominic.


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



Bug#759843: [Pkg-javascript-devel] Bug#759843: node-mapnik: FTBFS: vector_tile_processor.hpp:48:38: fatal error: mapnik3x_compatibility.hpp: No such file or directory

2014-09-23 Thread Robert Edmonds
clone 759843 -1
reassign -1 mapnik-vector-tile
found -1 0.5.1+dfsg-1
severity -1 serious
block 759843 by -1
block 761429 by -1
thanks

Jérémy Lal wrote:
 Le mardi 23 septembre 2014 à 13:28 +0100, peter green a écrit :
  This looks like a manifestation of 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761429
 
 Thank you for bringing this.

No, this is not caused by #761429.  Actually, this blocks the protobuf
transition.

The problem is that these header files shipped by mapnik-vector-tile
have unconditional #include's of mapnik3x_compatibility.hpp:

mapnik-vector-tile: /usr/include/vector_tile_backend_pbf.hpp
mapnik-vector-tile: /usr/include/vector_tile_datasource.hpp
mapnik-vector-tile: /usr/include/vector_tile_processor.hpp

mapnik3x_compatibility.hpp is shipped in src:mapnik-vector-tile but is
not installed in the binary:

http://sources.debian.net/src/mapnik-vector-tile/0.5.1%2Bdfsg-1/src/mapnik3x_compatibility.hpp/

http://sources.debian.net/src/mapnik-vector-tile/0.5.1%2Bdfsg-1/debian/install/

This doesn't work, of course.  mapnik-vector-tile's reverse build
dependencies are broken because of this (i.e., node-mapnik, #759843).

 Note that i won't lift a finger until mapnik 2.3 is out, which is
 (according to upstream [0]) due to be soon.

Since this blocks an ongoing library transition [0], I would be happy to
NMU mapnik-vector-tile, since the fix is trivial.

[0] https://release.debian.org/transitions/html/auto-protobuf.html

-- 
Robert Edmonds
edmo...@debian.org


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



Processed: Re: [Pkg-javascript-devel] Bug#759843: node-mapnik: FTBFS: vector_tile_processor.hpp:48:38: fatal error: mapnik3x_compatibility.hpp: No such file or directory

2014-09-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 clone 759843 -1
Bug #759843 [src:node-mapnik] node-mapnik: FTBFS: 
vector_tile_processor.hpp:48:38: fatal error: mapnik3x_compatibility.hpp: No 
such file or directory
Bug 759843 cloned as bug 762643
 reassign -1 mapnik-vector-tile
Bug #762643 [src:node-mapnik] node-mapnik: FTBFS: 
vector_tile_processor.hpp:48:38: fatal error: mapnik3x_compatibility.hpp: No 
such file or directory
Bug reassigned from package 'src:node-mapnik' to 'mapnik-vector-tile'.
No longer marked as found in versions node-mapnik/1.2.3-1.
Ignoring request to alter fixed versions of bug #762643 to the same values 
previously set
 found -1 0.5.1+dfsg-1
Bug #762643 [mapnik-vector-tile] node-mapnik: FTBFS: 
vector_tile_processor.hpp:48:38: fatal error: mapnik3x_compatibility.hpp: No 
such file or directory
Marked as found in versions mapnik-vector-tile/0.5.1+dfsg-1.
 severity -1 serious
Bug #762643 [mapnik-vector-tile] node-mapnik: FTBFS: 
vector_tile_processor.hpp:48:38: fatal error: mapnik3x_compatibility.hpp: No 
such file or directory
Ignoring request to change severity of Bug 762643 to the same value.
 block 759843 by -1
Bug #759843 [src:node-mapnik] node-mapnik: FTBFS: 
vector_tile_processor.hpp:48:38: fatal error: mapnik3x_compatibility.hpp: No 
such file or directory
759843 was not blocked by any bugs.
759843 was not blocking any bugs.
Added blocking bug(s) of 759843: 762643
 block 761429 by -1
Bug #761429 {Done: Robert Edmonds edmo...@debian.org} 
[src:mapnik-vector-tile] mapnik-vector-tile: new upload needed for protobuf 
2.6.0 transition
761429 was not blocked by any bugs.
761429 was blocking: 760343
Added blocking bug(s) of 761429: 762643
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
759843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759843
761429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761429
762643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762643
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#759843: [Pkg-javascript-devel] Bug#759843: node-mapnik: FTBFS: vector_tile_processor.hpp:48:38: fatal error: mapnik3x_compatibility.hpp: No such file or directory

2014-09-23 Thread Robert Edmonds
tags 759843 pending
tags 762643 pending
thanks

Robert Edmonds wrote:
 Since this blocks an ongoing library transition [0], I would be happy to
 NMU mapnik-vector-tile, since the fix is trivial.

Hi,

I've uploaded mapnik-vector-tile 0.5.1+dfsg-1.3 to DELAYED/3.  This
fixes #762643 (the lack of mapnik3x_compatibility.hpp in
mapnik-vector-tile) and #759843 (the FTBFS in mapnik-vector-tile's
reverse build dependency caused by #762643).  The debdiff is attached.

This allows node-mapnik to build again, which will allow the protobuf
transition (#760343) to continue.

-- 
Robert Edmonds
edmo...@debian.org
diff -Nru mapnik-vector-tile-0.5.1+dfsg/debian/changelog mapnik-vector-tile-0.5.1+dfsg/debian/changelog
--- mapnik-vector-tile-0.5.1+dfsg/debian/changelog	2014-08-20 17:06:54.0 -0400
+++ mapnik-vector-tile-0.5.1+dfsg/debian/changelog	2014-09-23 21:28:52.0 -0400
@@ -1,3 +1,20 @@
+mapnik-vector-tile (0.5.1+dfsg-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Actually ship mapnik3x_compatibility.hpp. (Closes: #762643, #759843.)
+
+ -- Robert Edmonds edmo...@debian.org  Tue, 23 Sep 2014 21:28:10 -0400
+
+mapnik-vector-tile (0.5.1+dfsg-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * No sourceful changes; rebuild against the latest protobuf-compiler due to
+the transition in #760343. (Closes: #761429)
+  * (Second try: the upload of 0.5.1+dfsg-1.1 was eaten by the archive
+software due to my key being replaced after the upload to DEFERRED.)
+
+ -- Robert Edmonds edmo...@debian.org  Tue, 23 Sep 2014 11:54:40 -0400
+
 mapnik-vector-tile (0.5.1+dfsg-1) unstable; urgency=medium
 
   * Upstream update
diff -Nru mapnik-vector-tile-0.5.1+dfsg/debian/install mapnik-vector-tile-0.5.1+dfsg/debian/install
--- mapnik-vector-tile-0.5.1+dfsg/debian/install	2013-08-29 07:13:43.0 -0400
+++ mapnik-vector-tile-0.5.1+dfsg/debian/install	2014-09-23 20:50:32.0 -0400
@@ -1 +1,2 @@
+src/mapnik3x_compatibility.hpp usr/include
 src/vector_tile* usr/include


Processed: Re: [Pkg-javascript-devel] Bug#759843: node-mapnik: FTBFS: vector_tile_processor.hpp:48:38: fatal error: mapnik3x_compatibility.hpp: No such file or directory

2014-09-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 759843 pending
Bug #759843 [src:node-mapnik] node-mapnik: FTBFS: 
vector_tile_processor.hpp:48:38: fatal error: mapnik3x_compatibility.hpp: No 
such file or directory
Added tag(s) pending.
 tags 762643 pending
Bug #762643 [mapnik-vector-tile] node-mapnik: FTBFS: 
vector_tile_processor.hpp:48:38: fatal error: mapnik3x_compatibility.hpp: No 
such file or directory
Added tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
759843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759843
762643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762643
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: retitle 762643 to mapnik-vector-tile: doesn't ship its mapnik3x_compatibility.hpp file

2014-09-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 retitle 762643 mapnik-vector-tile: doesn't ship its 
 mapnik3x_compatibility.hpp file
Bug #762643 [mapnik-vector-tile] node-mapnik: FTBFS: 
vector_tile_processor.hpp:48:38: fatal error: mapnik3x_compatibility.hpp: No 
such file or directory
Changed Bug title to 'mapnik-vector-tile: doesn't ship its 
mapnik3x_compatibility.hpp file' from 'node-mapnik: FTBFS: 
vector_tile_processor.hpp:48:38: fatal error: mapnik3x_compatibility.hpp: No 
such file or directory'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
762643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762643
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#762647: samtools: FTBFS: test suite errors

2014-09-23 Thread Aaron M. Ucko
Source: samtools
Version: 1.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

The builds of samtools for arm64 and ppc64el both failed because
the first samtools faidx test hit the autobuilders' activity timeout.
Given that these timeouts are generous (300 minutes for arm64, 150 for
ppc64el), I suspect the test managed to hang on those systems.

Meanwhile, the other builds attempted so far all encountered
unexpected test failures -- 2 on kfreebsd-amd64, and 95 each on i386,
kfreebsd-i386, and mipsel.

Could you please take a look?  You can find the logs at
https://buildd.debian.org/status/logs.php?pkg=samtoolsver=1.0-1

Thanks!


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



Bug#762647: [Debian-med-packaging] Bug#762647: samtools: FTBFS: test suite errors

2014-09-23 Thread Charles Plessy
Le Tue, Sep 23, 2014 at 11:20:15PM -0400, Aaron M. Ucko a écrit :
 
 The builds of samtools for arm64 and ppc64el both failed because
 the first samtools faidx test hit the autobuilders' activity timeout.
 Given that these timeouts are generous (300 minutes for arm64, 150 for
 ppc64el), I suspect the test managed to hang on those systems.
 
 Meanwhile, the other builds attempted so far all encountered
 unexpected test failures -- 2 on kfreebsd-amd64, and 95 each on i386,
 kfreebsd-i386, and mipsel.

Hi Aaron,

regarding the test failures on the ‘stats’ command (2 unit failures), I
reported the issue upstream and will implement a workaround if necessary.

https://github.com/samtools/samtools/issues/300

The other failures and timeouts are probably symptoms of non-portability
outside amd64.  Some porters have contacted upstream on endianness issues, but
I do not know if the problem is likely to be solved in the short term.

https://github.com/samtools/samtools/issues/268

Have a nice day,

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


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



Bug#762647: [Debian-med-packaging] Bug#762647: samtools: FTBFS: test suite errors

2014-09-23 Thread Aaron M. Ucko
Charles Plessy ple...@debian.org writes:

 The other failures and timeouts are probably symptoms of non-portability
 outside amd64.  Some porters have contacted upstream on endianness issues, but
 I do not know if the problem is likely to be solved in the short term.

Hi, Charles; thanks for the quick response!  FWIW, the three
architectures with 95 failures were all little-endian, but 32-bit.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu


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