Bug#797554: libzrtpcpp: GPL linked with OpenSSL without exception

[Niels Thykier]

On Mon, 31 Aug 2015 14:41:04 +0100 Dimitri John Ledkov
 wrote:
> Severity: serious
> Package: libzrtpcpp
> Version: 2.3.4-1
> 
> The packae is GPLv3, yet it links with OpenSSL without an exception.
> 
> Hence it is not-free.
> 
> Regards,
> 
> Dimitri.
> 
> 

I think you mean "non-distributable" (which is worse than "non-free").

Thanks,
~Niels

Bug#800617: Fails to provide secrets

[peter]

On Sat, 03 Oct 2015 22:04:21 +0200 Mikhail Morfikov 
 wrote:

> Package: gnome-keyring
> Version: 3.18.0-1
> Followup-For: Bug #800617

> So I upgraded everything to sid version as it was before, and then I
> noticed that there's a new version of config files in
> /etc/xdg/autostart/ -- those with gnome* in their name. I had also
> some files in the ~/.config/autostart/ directory, so I removed them
> completely. After reboot, everything seems to be working as it supposed
> to.
>


Thanks for the information

After upgrading I removed  3 /etc/xdg/autostart/ -- those with gnome* in 
their name files


I did not have any  ~/.config/autostart/  files applicable to gnome*

I too seem to have everything ok now with browser and shutdown

cheers

Peter

Bug#800629: telepathy-qt FTBFS: fatal error: gst/gstconfig.h: No such file or directory

[Alexandr Akulich]

Hello.

Probably this patch would help:
http://cgit.freedesktop.org/telepathy/telepathy-qt/commit/?id=ec4a3d62b68a57254515f01fc5ea3325ffb1dbfb

Bug#801078: elpa-js2-mode: js2-mode uninstallable due to wrong Breaks in elpa-js2-mode

[Vincent Bernat]

 ❦  6 octobre 2015 00:32 +0200, Axel Beckert  :

> js2-mode in Debian unstable is currently uninstallable as it depends on
> elpa-js2-mode and elpa-js2-mode has a "Breaks: js2-mode (<< 20150909-1)"
> instead of a "Breaks: js2-mode (<< 0~20150909-1)". (Note the missing
> "0~" in the first string.)

I don't remember why I did add the Breaks in the first place (the new
package doesn't share files with the old one). I'll upload a fix
shortly. Sorry for the inconvenience.
-- 
Avoid unnecessary branches.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Bug#777511: linux-image-3.16: md: bug with re-adding a partially recovered device to a mirror

[Joe Lawrence]

Stratus encountered a similar MD RAID1 bug here:

  https://www.marc.info/?l=linux-raid&m=143619993921782&w=4

and posted a potential fix here:

  https://www.marc.info/?l=linux-raid&m=143811224629816&w=4

Any feedback on the upstream report/patch would be greatly appreciated.

Thanks,

-- Joe

Processed: Re: Bug#799240: cclive: Invalid pointer

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #799240 [cclive] cclive: Invalid pointer
Severity set to 'important' from 'grave'

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

Bug#799240: cclive: Invalid pointer

[Olly Betts]

Control: severity -1 important

On Thu, Sep 17, 2015 at 07:44:45AM +0200, Martin Haase wrote:
> This is what II get when I try to leech a video from youtube:
>  Error in cclive': free(): invalid pointer: 0x00658a38

Works for me, using the same version as the submitter:

$ cclive https://www.youtube.com/watch?v=gAc8-YDzWZw
Checking ... ... ... Bird Dance Little Morepork.  0.00M  []
[---]0.0M   0.0K/s  00:00:14
$ dpkg -l cclive
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  
Architecture Description
+++-==---==
ii  cclive 0.7.16-2.1+b1
amd64lightweight command line video extraction tool

> Severity: grave
> Justification: renders package unusable

It works for me at least, so lowering severity.

Martin, I'd suggest providing a URL which fails for you.

Cheers,
Olly

Bug#797095: marked as done (amd64: netboot 2015-04-22, 2015-06-04, 2015-08-13 fail, wheezy succeeds)

[Debian Bug Tracking System]

Your message dated Tue, 06 Oct 2015 01:50:02 +0200
with message-id <56130caa.9080...@debian.org>
and subject line Re: amd64: netboot 2015-04-22, 2015-06-04, 2015-08-13 fail, 
wheezy succeeds
has caused the Debian Bug report #797095,
regarding amd64: netboot 2015-04-22, 2015-06-04, 2015-08-13 fail, wheezy 
succeeds
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.)


-- 
797095: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: 20150422+deb8u1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

summary
---
amd64 netboot wheezy  2015-01-05 works
amd64 netboot jessie  2015-04-22 fails
amd64 netboot jessie  2015-06-04 fails
amd64 netboot stretch 2015-08-13 fails

details
---
Have a 40-node cluster.

Started With wheezy: Head node + 2 compute nodes up
  compute nodes installed via dhcp and tftp from wheezy netboot

Upgraded head node and compute nodes, each separately, to jessie

Trying to install another compute node via dhcp, tftp, and netboot
(Using the same framework on head that worked for wheezy)

using netboot  2015-08-13 - something creates a reboot loop
syslog on head shows

 (start) syslog 
Aug 27 14:29:09 geodyncomp2 in.tftpd[26229]: RRQ from 10.2.81.13 filename
  pxelinux.0
Aug 27 14:29:09 geodyncomp2 in.tftpd[26229]: tftp: client does not accept 
options
Aug 27 14:29:09 geodyncomp2 in.tftpd[26230]: RRQ from 10.2.81.13 filename
  pxelinux.0
Aug 27 14:30:51 geodyncomp2 dhcpd: DHCPDISCOVER from 00:30:48:f6:d4:6c via eth0
Aug 27 14:30:51 geodyncomp2 dhcpd: unexpected ICMP Echo Reply from 10.2.80.237
Aug 27 14:30:51 geodyncomp2 dhcpd: unexpected ICMP Echo Reply from 10.2.80.237
Aug 27 14:30:52 geodyncomp2 dhcpd: DHCPOFFER on 10.2.81.13 to 00:30:48:f6:d4:6c
  via eth0
Aug 27 14:30:59 geodyncomp2 dhcpd: DHCPREQUEST for 10.2.81.13 (10.2.81.1)
  from 00:30:48:f6:d4:6c via eth0
Aug 27 14:30:59 geodyncomp2 dhcpd: DHCPACK on 10.2.81.13 to 00:30:48:f6:d4:6c
  via eth0
...the reset happens here...or the bios retries...or something
Aug 27 14:30:59 geodyncomp2 in.tftpd[26691]: RRQ from 10.2.81.13 filename
  pxelinux.0
Aug 27 14:30:59 geodyncomp2 in.tftpd[26691]: tftp: client does not accept 
options
Aug 27 14:30:59 geodyncomp2 in.tftpd[26692]: RRQ from 10.2.81.13 filename
  pxelinux.0
 (end) syslog =

netboot 2015-06-04 fails with different results (yes, I can provide details)

netboot 2015-04-22 fails with different results (yes, I can provide details)

netboot 2015-01-05, wheezy, works

The version is reported as 20150422+deb8u1, which I believe is dated 2015-06-04.

My system is jessie.
Not knowing how to change sources.list to just get that one package from 
stretch,
I downloaded the netboot images.
-rw-r--r-- 1  19368308 Aug 27 01:33 netboot_jessie_2015-04-22.tar.gz
-rw-r--r-- 1  38576779 Aug 27 09:28 netboot_jessie_2015-06-04_gtk.tar.gz
-rw-r--r-- 1  19370121 Aug 27 09:26 netboot_jessie_2015-06-04.tar.gz
-rw-r--r-- 1  21360976 Aug 27 14:21 netboot_stretch_2015-08-13.tar.gz

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

Thank you,
Dogulas.
--- End Message ---
--- Begin Message ---
On Sun, 6 Sep 2015 14:43:25 -0300 Douglas Guptill
 wrote:
> Wrong.  my bad.  no bug.

> Using a 'default' file written according to the specs for syslinux
> version 6.03, I get an automated, unattended, preseeded install.
> 
> Sorry for the noise.

OK, closing the bug.


Andreas--- End Message ---

Bug#800920:

[Florian Uekermann]

Good/bad news.

Good: I made a fresh install, which fixed the problem. I usually don't do that, 
but I really need this machine to work and I am particularly interested in the 
latest driver updates.

Bad: I meant to save a backup of the system to compare it afterwards and find 
out what was causing that segfault. Unfortunately I botched that part.

I am very sorry about the last part, I guess you can close this, since there is 
no real hope of reproducing that on my side now.

In the process of investigating this, I played a bit with the debs on AMDs 
website. As you are obviously aware (since you have patches to fix it), their 
dkms stuff does not compile with recent kernels. Is there a strong reason why 
those patches never made it upstream?

Best regards,
Florian

Bug#787959: [backintime-common] backintime failed to start: No such file or directory

[Germar Reitze]

Version 1.1.8 is now available which will not depend on initscripts
anymore.


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

Bug#799948: glx-alternatives_0.6.1_source.changes ACCEPTED into unstable

[Diederik de Haas]

On Monday 05 October 2015 21:20:25 Debian FTP Masters wrote:
> Source: glx-alternatives
> Binary: glx-diversions glx-alternative-mesa glx-alternative-nvidia
> glx-alternative-fglrx Architecture: source
> Version: 0.6.1
> Distribution: unstable
> ...
> * Temporarily disable the nvidia-drm-outputclass.conf slave alternative.
> (Closes: #799948)

How about bug nrs #800051, 800327, 800550 and 800705?
They looked like the same issue to me and most confirmed that adding the DM 
user to the video group fixed it (some haven't responded yet).

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

Processed: tagging 795851

[Debian Bug Tracking System]

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

> tags 795851 + pending
Bug #795851 [src:openjfx] openjfx: FTBFS with Gradle 2.5
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#801078: elpa-js2-mode: js2-mode uninstallable due to wrong Breaks in elpa-js2-mode

[Axel Beckert]

Package: elpa-js2-mode
Version: 0~20150909-1
Severity: serious

Dear Maintainer,

js2-mode in Debian unstable is currently uninstallable as it depends on
elpa-js2-mode and elpa-js2-mode has a "Breaks: js2-mode (<< 20150909-1)"
instead of a "Breaks: js2-mode (<< 0~20150909-1)". (Note the missing
"0~" in the first string.)

Bug#784070: is it maybe possible to settle dislikings and fix this bug?

[Francesco Poli]

On Sun, 04 Oct 2015 09:52:53 +0200 Paul Muster wrote:

> Dear Michael,
> 
> thanks for clarifying the situation.

Dear Michael,
first of all, I would like to join Paul in thanking you for your
helpful explanations.

I am too experiencing this same issue (bug #784070): after unplugging
one drive (in order to test a RAID1 setup), the machine fails to boot
and drops me to an initramfs shell.

> 
> > serverfault solution isn't exactly wrong, it is incomplete, it
> > does not cover a situation when you have slow-to-appear devices.
> > This solution, however, fixes the problem in this bugreport,
> > a problem which I introduced when I tried to address the problem
> > with slow-to-appear devices.  Ofcourse it is better to be able
> > to boot from a degraded raid than to be able to boot from slow
> > devices, esp. since the latter had a workaround.  So in this
> > sense, serverfault solution will fix _this_ bug.
> 
> so, couldn't you patch the package to fix the problem for all people
> that do not have "slow-to-appear devices"?

I would also like to encourage you to implement what you think is the
best solution for this really annoying bug.

> 
> 
> > But I also dislike doing work which is being thrown away by others,
> > since this is a pure waste of time/energy, and time is a very scarse
> > resource.  I don't want to do any work if I know this work will be
> > thrown away, and here, debian-installer people did throw my work
> > a) without a good reason and b) without actual rights for that.
> 
> Of course what you describe is extremely disappointing for you. Since I
> don't know what exactly happened: There should be a decision committee
> which listens to both sides and decides _for Debian_.

Michael, I am not sure I understand what happened: I don't see any
recent NMUs for package mdadm, hence I cannot see how d-i developers
could "throw your work away".

Anyway, the last resort strategy to address your disagreement with the
d-i developers could be referring it to the technical committee, as
Paul seems to suggest...
But, before doing so, I would try hard to talk to the d-i developers
and solve the disagreement in the most amicable way.

> 
> > So I stopped maintaining all software which is related to debian-installer,
> > because now I know it is just a waste of time.  As simple as that, and
> > there's nothing like dislike of someone in there, there's nothing
> > personal.
> 
> It's not obvious to me why a bug in mdadm can't be fixed because there
> is a conflict with the d-i maintainers. Why can d-i maintainers decide
> about mdadm?
> 
> > In short, I don't maintain mdadm anymore, so there's no reason to
> > ask me about it.
> 
> That would be very sad because it's a really important package.

Michael, I really hope you reconsider this decision, because we really
need a good and active mdadm package maintainer.

Otherwise, if you are absolutely unwilling to continue maintaining the
mdadm Debian package (as I said, I hope you reconsider!), then I think
you should officially search for someone willing to adopt the package...


Thanks for your time!


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpuPVHIXJQDy.pgp
Description: PGP signature

Processed: Re: Bug#785877: fixed in radiotray 0.7.3-4

[Debian Bug Tracking System]

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

> reopen 785877
Bug #785877 {Done: Elías Alejandro Año Mendoza } 
[src:radiotray] radiotray: Please update to GStreamer 1.x
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions radiotray/0.7.3-4.
> thanks
Stopping processing here.

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

Bug#785877: fixed in radiotray 0.7.3-4

[Moritz Mühlenhoff]

reopen 785877
thanks

>  radiotray (0.7.3-4) unstable; urgency=low
>  .
>* debian/control
>  + Updating to Gstreamer 1.x (Closes: #785877)

It still depends on python-gst0.10.

Cheers,
Moritz

Bug#769350: marked as done (prelink: statically linked against libc6 without a Built-Using: field)

[Debian Bug Tracking System]

Your message dated Mon, 05 Oct 2015 21:25:13 +
with message-id 
and subject line Bug#769350: fixed in prelink 0.0.20130503-1.1
has caused the Debian Bug report #769350,
regarding prelink: statically linked against libc6 without a Built-Using: field
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.)


-- 
769350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: prelink
Version: 0.0.20130503-1
Severity: serious
Tags: jessie-ignore

prelink provides /usr/sbin/prelink.bin which is statically linked
against libc6. According to Debian Policy §7.8 such a package MUST
list the glibc source package (and possibly others) in the Built-Using:
field.

Note: While this is a serious policy violation, it has been agreed with
the release team that this is not a blocker bug for the Jessie release.
That's why the jessie-ignore tag is added. This makes this bug non RC.


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: prelink
Source-Version: 0.0.20130503-1.1

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated prelink 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: Fri, 25 Sep 2015 21:26:07 +0200
Source: prelink
Binary: prelink execstack
Architecture: source amd64
Version: 0.0.20130503-1.1
Distribution: unstable
Urgency: medium
Maintainer: Geoffrey Thomas 
Changed-By: Laurent Bigonville 
Description:
 execstack  - ELF GNU_STACK program header editing utility
 prelink- ELF prelinking utility to speed up dynamic linking
Closes: 769350 769414
Changes:
 prelink (0.0.20130503-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add the Built-Using field (Closes: #769350)
   * Build-depends against libelf-dev instead of libelfg0-dev (Closes: #769414)
   * Drop debian/patches/ftbfs-no-copy-dt-needed.patch, this is not needed
 anymore and it was an issue in libselinux in the first place anyway
Checksums-Sha1:
 42893bd8767d0b8d9287f70fc1414f94952568a7 1500 prelink_0.0.20130503-1.1.dsc
 89f3376fef597cca0b1052fa6b65fbf7f0c47212 28420 
prelink_0.0.20130503-1.1.debian.tar.xz
 f5a4c1f925224bffea4893b14bf12a7723448e9f 75498 
execstack_0.0.20130503-1.1_amd64.deb
 8c5a345e8fec1e5575caad99c61a8f15eab8c93c 944644 
prelink_0.0.20130503-1.1_amd64.deb
Checksums-Sha256:
 6b7923eaad1fbc01527defed204cdf7032a44636edf3cfc3570af42d371c6019 1500 
prelink_0.0.20130503-1.1.dsc
 aa110ca590fd9bdec206e2148cec50babf92d2454b303773507f5e83a8dfd13a 28420 
prelink_0.0.20130503-1.1.debian.tar.xz
 c82f85a68cc2a7b3005e7f45accca7419a45cfe3f0fb141389911ee3f1aefc3c 75498 
execstack_0.0.20130503-1.1_amd64.deb
 e2c7d39ab936e38e73701d0b80b90af1ee164f12eb32fefa913757675b33c716 944644 
prelink_0.0.20130503-1.1_amd64.deb
Files:
 3e41608952035cf06196e229bf447cd5 1500 admin optional 
prelink_0.0.20130503-1.1.dsc
 9871b4078fb507e11a67728bc9197763 28420 admin optional 
prelink_0.0.20130503-1.1.debian.tar.xz
 8de909165ee20c429d873468dae82efe 75498 admin optional 
execstack_0.0.20130503-1.1_amd64.deb
 23b0aef7c5269d938930b0d4d7fe2c81 944644 admin optional 
prelink_0.0.20130503-1.1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJWBaByAAoJEB/FiR66sEPVufwH/iimLGjnrC7nqZ/H/k+evuLv
MOsmk/mqPo0dgp6WQuf80ddVAdFDPeNICwdRXlKivc+aFrDg79F07Le1LOhHoU6B
eE4z+Sf/Q9VhHckWdPV2EIFIcyp7k8ppvHhcticRk/EZRia15oL4io6P9L5dTo6L
jrjU7pOP3QRgrZVaFYKnRr4fVOYD5ReIQ6ijVYQP6b57EfALbXFqawlmPz8gUB2c
fhR4EJ37N7xlQpuNnD3rtWUDTN5LRmMdpx/Mao+HM4jVC9JUY7SHiIqoH6zeiKw2
OnixNYDbjoqbWPTii8g32AdTEioR0I7xkiJdWAfjnm3WD9NZMuUUTcDVCwDrAlI=
=uGYH
-END PGP SIGNATURE End Message ---

Bug#794854: marked as done (matplotlib: non DFSG file in the source package)

[Debian Bug Tracking System]

Your message dated Mon, 05 Oct 2015 21:24:23 +
with message-id 
and subject line Bug#794854: fixed in matplotlib 1.5.0~rc2-1
has caused the Debian Bug report #794854,
regarding matplotlib: non DFSG file in the source 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.)


-- 
794854: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: matplotlib
Version: 1.4.2-3.1
Severity: Serious
Justification: non DFSG file in the source package
User: locutusofb...@debian.org
Usertags: license-problem-non-free-img-lenna

Hi matplotlib Maintainer(s),
your package has been found to contain a copy of a non DFSG
file, that makes your package non DFSG.

This image (called lenna.jpg, or lena.jpg with some variants)
is an image of Lena Söderberg, photographed by Dwight Hooker,
cropped from the centerfold of the November 1972 issue of Playboy magazine.

This file is to be considered distributable but non free
(at the end of this bug report you will find a link to the lintian tag,
with a more complete description of the issue and references)

Below a list of the affected files:
- lib/matplotlib/mpl-data/sample_data/lena.jpg
- lib/matplotlib/mpl-data/sample_data/lena.png

note, I did stop checking for the all files as soon as I found one
good match, so they might be not all bad references, please update
this bug if not correct.

More information about this issue can be found on the
license-problem-non-free-img-lenna lintian tag [1] and Debian bug [2]

[1] https://lintian.debian.org/tags/license-problem-non-free-img-lenna.html
[2] https://bugs.debian.org/771191

thanks,

Gianfranco
--- End Message ---
--- Begin Message ---
Source: matplotlib
Source-Version: 1.5.0~rc2-1

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated matplotlib 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, 05 Oct 2015 20:24:36 +0100
Source: matplotlib
Binary: python-matplotlib python3-matplotlib python-matplotlib-data 
python-matplotlib-doc python-matplotlib-dbg python3-matplotlib-dbg
Architecture: source all amd64
Version: 1.5.0~rc2-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Description:
 python-matplotlib - Python based plotting system in a style similar to Matlab
 python-matplotlib-data - Python based plotting system (data package)
 python-matplotlib-dbg - Python based plotting system (debug extension)
 python-matplotlib-doc - Python based plotting system (documentation package)
 python3-matplotlib - Python based plotting system in a style similar to Matlab 
(Python
 python3-matplotlib-dbg - Python based plotting system (debug extension, Python 
3)
Closes: 788730 792310 794854
Changes:
 matplotlib (1.5.0~rc2-1) unstable; urgency=medium
 .
   * New upstream release candidate
 - Lena Söderberg image has been removed; Closes: #794854
 - include source for minified JS libraries; Closes: #788730
   * debian/rules
 - replace JS libraries in all the py3k version of the package; thanks to
   Barry Warsaw for the report and patch; Closes: #792310
   * debian/copyright
 - updated for new upstream code
   * debian/patches/*
 - refresh/remove patches for new uptream code
   * debian/control
 - add cycler to b-d (bin pkgs depends are detected by dh_python2)
 - add ipython to b-d, ipython_console_highlighting is required to build doc
   * debian/patches/10ef9a7e26dc34328b7ec7fd0ed2c2db6104b342.patch
 - upstream patch to fix Qt4/Qt5 detection (tests failed)
   * debian/patches/9bc518230684b3a8bb69af60e160f90e1091cd0c.patch
 - fix encoding for Stéfan van der Walt name, using a single-codepoint
   encoding (Matplotlib.pdf creation failed)
Checksums-Sha1:
 6be5fb43497a0267cb85c0da098f3980936e3672 3511 matplotlib_1.5.0~rc2-1.dsc
 718c58f62e82959449e10a455274339882674042 53304206 
matplotlib_1.5.0~rc2.orig.tar.gz
 6fbab07e55bf0b406ea17ace70af

Bug#792310: marked as done (matplotlib: FTBFS with multiple version of Python 3)

[Debian Bug Tracking System]

Your message dated Mon, 05 Oct 2015 21:24:23 +
with message-id 
and subject line Bug#792310: fixed in matplotlib 1.5.0~rc2-1
has caused the Debian Bug report #792310,
regarding matplotlib: FTBFS with multiple version of Python 3
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,

matplotlib fails to build from source when multiple versions of Python
3 are supported.  In Ubuntu we are working on the Python 3.5
transition and have an experimental PPA which defaults to Python 3.5
and keeps 3.4 enabled.  Eventually we'll do the same in Debian, so
it's important to fix this problem.

Attached is a patch that fixes the build, although I won't claim it's
the cleanest, or even the right-est fix.

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

Kernel: Linux 4.0.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJVpBuxAAoJEBJutWOnSwa/pxgQAIBS1n319b1UYZUCYrTM5HQ6
OXDE2b1+HrVyVYjp/7mqQBAzpI3kmNqHJHYmJl97ER/Y5axQTIBstxvVr3moDpna
PQk4+H+VOEyZx1Rt3JMlHggvSmUT6gu82Q695Fwj3m3BGXTGHs/YCAfKasCvPVWw
8Yonv/6arQ9YhfmZ3QkBPha8VuFCReX2cjLkwd6HOsZKeRxUsJ5p+iAzd14H4P5T
2yYewVLjbNNgB/76meJIWvTbKEfjZsNwbHeyLqCzjwalmF3XMdMl+/qQPzIM1aoz
9cissvRoHNpfjWVNWrHxq64UmF4DCgpuBbhYOcYlGqTXzfOYGHmlOnPOu3u4e5QU
TiOD4QDxAt7xaje7AcdCxHxbsQWdbVv7MFKpZbLQpfPbquwmngUmga5XpgurGAGc
Q+Qg+PgFKtVNVQhpq2n6iKLXg8nCwTBAggGA5Bklrw7o6PGaPgXB8jKP3MZ2fAkD
DFkb8j0Czs8F7DeGFTxkxsYuUtTTmOXysYB0dCsSeBm1hOCngpLH7QIe5ZyZEQiq
/5G8CSofr1+zuMd/l3PIGUCPmhfWQth7Wm1HmOXYCo9P831T2rDbDyYFiHJQyblB
LIcTJIMGfOVcbYwwGb/TKZSYmsegkmn6w+LZ6Z19S7Gu2YsxUXuUj8APCm/irhVi
h/O2mWRIuyfumuY4ZfHv
=bHlS
-END PGP SIGNATURE-
=== modified file 'debian/rules'
--- debian/rules	2014-09-12 01:09:53 +
+++ debian/rules	2015-07-13 18:13:24 +
@@ -143,6 +143,11 @@
 	dh_testdir
 	dh_testroot
 
+	-rm $(CURDIR)/debian/$(p3)/usr/lib/python3/dist-packages/matplotlib/backends/web_backend/jquery/js/jquery-1.7.1.min.js
+	-rm $(CURDIR)/debian/$(p3)/usr/lib/python3/dist-packages/matplotlib/backends/web_backend/jquery/js/jquery-ui.min.js
+	-rm $(CURDIR)/debian/$(p3)/usr/lib/python3/dist-packages/matplotlib/backends/web_backend/jquery/css/themes/base/jquery-ui.min.css
+
+
 	python$* ./setup.py install_lib \
 		-d $(CURDIR)/debian/$(p3)/usr/lib/python3/dist-packages/ --no-compile
 	python$* ./setup.py install_egg_info \
@@ -163,12 +168,14 @@
 	rm -rf $(CURDIR)/debian/$(p3dbg)/usr/lib/python3/dist-packages/matplotlib/backends/Matplotlib.nib/
 
 	# replace minified jquery with packaged version and hope it works
-	dh_link -ppython3-matplotlib usr/share/javascript/jquery/jquery.min.js \
-	  usr/lib/python3/dist-packages/matplotlib/backends/web_backend/jquery/js/jquery-1.7.1.min.js
-	dh_link -ppython3-matplotlib usr/share/javascript/jquery-ui/jquery-ui.min.js \
-	  usr/lib/python3/dist-packages/matplotlib/backends/web_backend/jquery/js/jquery-ui.min.js
-	dh_link  -ppython3-matplotlib usr/share/javascript/jquery-ui/css/smoothness/jquery-ui.min.css \
-	  usr/lib/python3/dist-packages/matplotlib/backends/web_backend/jquery/css/themes/base/jquery-ui.min.css
+	for i in $(PY3VERS); do \
+	dh_link -ppython3-matplotlib usr/share/javascript/jquery/jquery.min.js \
+	  usr/lib/python3/dist-packages/matplotlib/backends/web_backend/jquery/js/jquery-1.7.1.min.js; \
+	dh_link -ppython3-matplotlib usr/share/javascript/jquery-ui/jquery-ui.min.js \
+	  usr/lib/python3/dist-packages/matplotlib/backends/web_backend/jquery/js/jquery-ui.min.js; \
+	dh_link  -ppython3-matplotlib usr/share/javascript/jquery-ui/css/smoothness/jquery-ui.min.css \
+	  usr/lib/python3/dist-packages/matplotlib/backends/web_backend/jquery/css/themes/base/jquery-ui.min.css; \
+	done
 
 	touch $@
 

--- End Message ---
--- Begin Message ---
Source: matplotlib
Source-Version: 1.5.0~rc2-1

We believe that the bug you reported is fixed in the latest version of
matplotlib, 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 792...@bugs.debi

Bug#788730: marked as done ([src:matplotlib] Some sources are not included in your package)

[Debian Bug Tracking System]

Your message dated Mon, 05 Oct 2015 21:24:23 +
with message-id 
and subject line Bug#788730: fixed in matplotlib 1.5.0~rc2-1
has caused the Debian Bug report #788730,
regarding [src:matplotlib] Some sources are not included in your 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.)


-- 
788730: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:matplotlib 
Version:  1.4.2-3.1
user: lintian-ma...@debian.org
usertags: source-is-missing
severity: serious
X-Debbugs-CC: ftpmas...@debian.org

Hi,

Your package includes some files that seem to lack sources
in prefered forms of modification:
  
lib/matplotlib/backends/web_backend/jquery/js/jquery-ui.min.js
lib/matplotlib/backends/web_backend/jquery/js/jquery-1.7.1.min.js

According to Debian Free Software Guidelines [1] (DFSG) #2:
 "The program must include source code, and must allow distribution 
  in source code as well as compiled form."

In some cases this could also constitute a license violation for some
copyleft licenses such as the GNU GPL. (While sometimes the licence
allows not to ship the source, the DFSG always mandates source code.)

In order to solve this problem, you could:
1.  add the source files to "debian/missing-sources" directory.
2. repack the origin tarball and add the missing source files to it.

Both way satisfy the requirement to ship all source code. The second option
might be preferable due to the following reasons [2]:
 - Upstream can do it too and you could even supply a patch to them, thus
   full filling our social contract [3], see particularly §2.
 - If source and non-source are in different locations, ftpmasters may
   miss the source and (needlessly) reject the package.
 - The source isn't duplicated in every .diff.gz/.debian.tar.* (though
   this only really matters for larger sources).

You could also ask debian...@lists.debian.org or #debian-qa for more
guidance.

[1] https://www.debian.org/social_contract.en.html#guidelines
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736873#8
[3] https://www.debian.org/social_contract

signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: matplotlib
Source-Version: 1.5.0~rc2-1

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated matplotlib 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, 05 Oct 2015 20:24:36 +0100
Source: matplotlib
Binary: python-matplotlib python3-matplotlib python-matplotlib-data 
python-matplotlib-doc python-matplotlib-dbg python3-matplotlib-dbg
Architecture: source all amd64
Version: 1.5.0~rc2-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Description:
 python-matplotlib - Python based plotting system in a style similar to Matlab
 python-matplotlib-data - Python based plotting system (data package)
 python-matplotlib-dbg - Python based plotting system (debug extension)
 python-matplotlib-doc - Python based plotting system (documentation package)
 python3-matplotlib - Python based plotting system in a style similar to Matlab 
(Python
 python3-matplotlib-dbg - Python based plotting system (debug extension, Python 
3)
Closes: 788730 792310 794854
Changes:
 matplotlib (1.5.0~rc2-1) unstable; urgency=medium
 .
   * New upstream release candidate
 - Lena Söderberg image has been removed; Closes: #794854
 - include source for minified JS libraries; Closes: #788730
   * debian/rules
 - replace JS libraries in all the py3k version of the package; thanks to
   Barry Warsaw for the report and patch; Closes: #792310
   * debian/copyright
 - updated for new upstream code
   * debian/patches/*
 - refresh/remove patches for new uptream code
   * debian/control
 - add cycler to b-d (bin pkgs depends are detected by dh_python2)
 - add ipython to b-d, ipython_console_highlighting 

Processed: found 799948 in 0.6.90

[Debian Bug Tracking System]

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

> found 799948 0.6.90
Bug #799948 {Done: Andreas Beckmann } [glx-alternative-nvidia] 
glx-diversions: Upgrade to version 0.6.0 made sddm-greeter crash
Bug #800836 {Done: Andreas Beckmann } [glx-alternative-nvidia] 
glx-diversions: Upgrade to version 0.6.0 made sddm-greeter crash
There is no source info for the package 'glx-alternative-nvidia' at version 
'0.6.90' with architecture ''
Unable to make a source version for version '0.6.90'
Marked as found in versions 0.6.90 and reopened.
Marked as found in versions 0.6.90 and reopened.
> thanks
Stopping processing here.

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

Bug#800836: marked as done (glx-diversions: Upgrade to version 0.6.0 made sddm-greeter crash)

[Debian Bug Tracking System]

Your message dated Mon, 05 Oct 2015 21:20:25 +
with message-id 
and subject line Bug#799948: fixed in glx-alternatives 0.6.1
has caused the Debian Bug report #799948,
regarding glx-diversions: Upgrade to version 0.6.0 made sddm-greeter crash
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.)


-- 
799948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-legacy-340xx-driver
Version: 340.93-1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

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

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

Subject: Re: glx-diversions: Upgrade to version 0.6.0 made sddm-greeter crash

Package: nvidia-graphics-drivers-legacy-340xx
Version: 340.93-1
Followup-For: Bug #799948

Dear Maintainer,

Same problem here while upgrading from 340.76-6 to 340.93-1.
OTOH glx-diversions wasn't upgraded, but it really seems to be the same
problem.

Adding group video to the Debian-gdm user fixes the problem.

regards,
Nicolas

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'testing'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- Package-specific info:
uname -a:
Linux misaki 4.2.0-1-amd64 #1 SMP Debian 4.2.1-2 (2015-09-27) x86_64 GNU/Linux

/proc/version:
Linux version 4.2.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.9.3 
(Debian 4.9.3-4) ) #1 SMP Debian 4.2.1-2 (2015-09-27)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.93  Wed Aug 19 16:49:15 PDT 
2015
GCC version:  gcc version 4.9.3 (Debian 4.9.3-4) 

lspci 'VGA compatible controller [0300]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G86M [Quadro NVS 
135M] [10de:042b] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:01f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia

dmesg:
[0.00] Console: colour VGA+ 80x25
[0.264448] vgaarb: setting as boot device: PCI::01:00.0
[0.264448] vgaarb: device added: 
PCI::01:00.0,decodes=io+mem,owns=io+mem,locks=none
[0.264448] vgaarb: loaded
[0.264448] vgaarb: bridge control possible :01:00.0
[0.489509] Linux agpgart interface v0.103
[1.586071] [Firmware Bug]: Duplicate ACPI video bus devices for the same 
VGA controller, please try module parameter "video.allow_duplicates=1"if the 
current driver doesn't work.
[2.444345] nvidia: module license 'NVIDIA' taints kernel.
[2.472232] vgaarb: device changed decodes: 
PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[2.472734] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on 
minor 0
[2.472746] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  340.93  Wed Aug 
19 16:49:15 PDT 2015

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Oct  4 09:35 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   44 Oct  4 09:35 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1
lrwxrwxrwx 1 root root   41 Oct  4 09:35 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   41 Oct  4 09:35 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   43 Oct  4 09:35 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   43 Oct  4 09:35 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   57 Oct  4 09:35 
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   57 Oct  4 09:35 
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLE

Bug#799948: marked as done (glx-diversions: Upgrade to version 0.6.0 made sddm-greeter crash)

[Debian Bug Tracking System]

Your message dated Mon, 05 Oct 2015 21:20:25 +
with message-id 
and subject line Bug#799948: fixed in glx-alternatives 0.6.1
has caused the Debian Bug report #799948,
regarding glx-diversions: Upgrade to version 0.6.0 made sddm-greeter crash
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.)


-- 
799948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glx-diversions
Version: 0.5.1
Severity: normal

Earlier today I upgraded to version 0.6.0 of glx-diversions and
glx-alternative-mesa and glx-alternative-nvidia and after a reboot the
sddm-greeter crashed which made it impossible to start my KDE Plasma 5
desktop.
After downgrading to version 0.5.1 of those packages the sddm-greeter
did start and I'm now writing this bug report from Plasma 5.

I have 2 crash report from sddm-greeter and will attach to this bug
report later.

If you need more info and/or want me to do tests, let me know.

Regards,
  Diederik

-- Package-specific info:
Diversions:
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by 
glx-diversions
diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 
by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so to /usr/lib/mesa-diverted/libGLESv1_CM.so 
by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/libGLESv2.so to /usr/lib/mesa-diverted/libGLESv2.so by 
glx-diversions
diversion of /usr/lib/libGLESv2.so.2 to /usr/lib/mesa-diverted/libGLESv2.so.2 
by glx-diversions
diversion of /usr/lib/libGLESv2.so.2.0.0 t

Bug#785854: soundconverter: Please update to GStreamer 1.x

[Sebastian Ramacher]

On 2015-09-24 22:40:26, Moritz Muehlenhoff wrote:
> On Wed, May 20, 2015 at 07:08:43PM +0200, Sebastian Ramacher wrote:
> > Version: 3.0.0~alpha1-1
> > 
> > Hi Sebastian
> > 
> > On 2015-05-20 16:03:06, sl...@debian.org wrote:
> > > Source: soundconverter
> > > Severity: important
> > > User: sl...@debian.org
> > > Usertags: gstreamer0.10-removal
> > > 
> > > Hi maintainer,
> > > 
> > > your package soundconverter currently still depends on GStreamer
> > > 0.10.
> > > 
> > > GStreamer 0.10 is no longer maintained and supported by the upstream
> > > project since almost 3 years, and contains many known bugs that are
> > > fixed in the new 1.x release series of GStreamer. Next to many bug
> > > fixes, the new release series also contains many other improvements,
> > > new features and a more streamlined API.
> > > 
> > > For the next Debian release GStreamer 0.10 is planned to be removed,
> > > and if your package is not updated it might not be included in the
> > > release. Please update your package to use the new version as soon as
> > > possible.
> > 
> > Upstream is currently porting it to GStreamer 1.0. A first alpha release of 
> > the
> > part is already available in experimental.
> 
> gstreamer 0.10 is in the process of being removed. Is the version from
> experimental ready to move to unstable?

Sorry for the delay. I'll check that this weekend.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#801072: Should longomatch be removed?

[Moritz Muehlenhoff]

Package: longomatch
Severity: serious

The version is in the archive is totally oudated compared to
upstream and depends on gstreamer 0.10 legacy libs. popcon
usage is virtually non-existant.

Please update the package or reassign this bug to
ftp.debian.org for removal.

Cheers,
 Moritz

Bug#801071: Should this package be removed?

[Moritz Muehlenhoff]

Package: minirok
Severity: serious

Should minirok be removed? It hasn't seen an upload
since 2009, it's dead upstream (Debian maintainer is also
upstream), popcon usage is marginal and it relies on
obsolete gstreamer 0.10. Plus, there's plenty of alternatives
in the archive.

Please address the outstanding bugs or reassign this to
ftp.debian.org for removal.

Cheers,
Moritz

Bug#799449: [pkg-apparmor] Processed: severity of 799449 is serious

[Felix Geyer]

On Mon, 05 Oct 2015 21:27:58 +0200 intrigeri  wrote:
> Control: tag -1 + help
> 
> sarnold wants a stracktrace and says: "if you can get it to fail by
> hand, runniung it with gdb ought to do the trick, gdb ./tst_regex ;
> "run" "bt" iiirc.."
> 
> => anyone with access to mips* a porter box can do that and report
> back here. Help is welcome :)

Doesn't look very promising:

minkus% gdb tst_lib
GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "mips-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from tst_lib...done.
(gdb) run
Starting program: /home/fgeyer/apparmor-2.10/parser/tst_lib
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/mips-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x in ?? ()
(gdb) bt full
#0  0x in ?? ()
No symbol table info available.
#1  0x005537a0 in _PROCEDURE_LINKAGE_TABLE_ ()
No symbol table info available.
Backtrace stopped: frame did not save the PC


fwiw all parser/tst_* segfault the same way.

Felix

Processed: your mail

[Debian Bug Tracking System]

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

> tags 800922 + pending
Bug #800922 [libmicrospdy-dev] libmicrospdy-dev: fails to upgrade from 'jessie' 
- trying to overwrite /usr/lib/x86_64-linux-gnu/pkgconfig/libmicrospdy.pc
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#800959: marked as done (xserver-xorg-core: fails to upgrade with old version of x11-common installed)

[Debian Bug Tracking System]

Your message dated Mon, 5 Oct 2015 21:51:58 +0200
with message-id <20151005195158.gb14...@betterave.cristau.org>
and subject line Re: Bug#800959: xserver-xorg-core: fails to upgrade with old 
version of x11-common installed
has caused the Debian Bug report #800959,
regarding xserver-xorg-core: fails to upgrade with old version of x11-common 
installed
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.)


-- 
800959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-core
Version: 1.17.2-2
Severity: serious

Hi,

xserver-xorg-core does not upgrade to the version in experimental if
the old version of x11-common is installed.

# dpkg -l xserver-xorg x11-common xserver-xorg-core
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion  Architecture 
Description
+++-===---
ii  x11-common  1:7.7+9  all  X 
Window System (X.Org) infrastructure
ii  xserver-xorg1:7.7+9  amd64
X.Org X server
ii  xserver-xorg-core   2:1.17.2-1.1 amd64
Xorg X server - core server

# dpkg -i /var/cache/apt/archives/xserver-xorg_1%3a7.7+11_amd64.deb 
/var/cache/apt/archives/xserver-xorg-core_2%3a1.17.2-2_amd64.deb 
(Reading database ... 209469 files and directories currently installed.)
Preparing to unpack .../xserver-xorg_1%3a7.7+11_amd64.deb ...
Unpacking xserver-xorg (1:7.7+11) over (1:7.7+9) ...
Preparing to unpack .../xserver-xorg-core_2%3a1.17.2-2_amd64.deb ...
Unpacking xserver-xorg-core (2:1.17.2-2) over (2:1.17.2-1.1) ...
dpkg: error processing archive 
/var/cache/apt/archives/xserver-xorg-core_2%3a1.17.2-2_amd64.deb (--install):
 trying to overwrite '/usr/share/man/man5/Xwrapper.config.5.gz', which is also 
in package x11-common 1:7.7+9
dpkg: dependency problems prevent configuration of xserver-xorg:
 xserver-xorg depends on xserver-xorg-core (>= 2:1.17.2-2); however:
  Version of xserver-xorg-core on system is 2:1.17.2-1.1.

dpkg: error processing package xserver-xorg (--install):
 dependency problems - leaving unconfigured
Processing triggers for man-db (2.7.3-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/xserver-xorg-core_2%3a1.17.2-2_amd64.deb
 xserver-xorg

Thanks,
James

signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
On Mon, Oct  5, 2015 at 12:54:38 +0100, James Cowgill wrote:

> Package: xserver-xorg-core
> Version: 1.17.2-2
> Severity: serious
> 
> Hi,
> 
> xserver-xorg-core does not upgrade to the version in experimental if
> the old version of x11-common is installed.
> 
dupe of 797661, closing.

Cheers,
Julien


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

Processed: Re: [pkg-apparmor] Processed: severity of 799449 is serious

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + help
Bug #799449 [src:apparmor] apparmor: FTBFS: test suite segfaults on mips and 
mipsel
Added tag(s) help.

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

Bug#799449: [pkg-apparmor] Processed: severity of 799449 is serious

[intrigeri]

Control: tag -1 + help

sarnold wants a stracktrace and says: "if you can get it to fail by
hand, runniung it with gdb ought to do the trick, gdb ./tst_regex ;
"run" "bt" iiirc.."

=> anyone with access to mips* a porter box can do that and report
back here. Help is welcome :)

Processed: scilab: FTBFS on ppc64el

[Debian Bug Tracking System]

Processing control commands:

> block 798256 with -1
Bug #798256 [release.debian.org] transition: hdf5
798256 was not blocked by any bugs.
798256 was not blocking any bugs.
Added blocking bug(s) of 798256: 801060

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

Bug#801060: scilab: FTBFS on ppc64el

[Emilio Pozuelo Monfort]

Source: scilab
Version: 5.5.2-1.1
Severity: serious
Control: block 798256 with -1

Your package failed to build on ppc64el

Excerpt from the build log:

checking if jni.h can be included... yes
Looking for JNI libs with ppc64 as machine hardware name
Looking for /usr/lib/jvm/java-7-openjdk-ppc64el/jre/lib/ppc64/libjava.so
Looking for /usr/lib/jvm/java-7-openjdk-ppc64el/jre/lib/amd64/libjava.so
Looking for /usr/lib/jvm/java-7-openjdk-ppc64el/jre/lib/i386/client/libjvm.so
Looking for /usr/lib/jvm/java-7-openjdk-ppc64el/jre/bin/classic/libjvm.so
Looking for /usr/lib/jvm/java-7-openjdk-ppc64el/lib/jvm.lib
Looking for /usr/lib/jvm/java-7-openjdk-ppc64el/jre/lib/mipsel/libjava.so
configure: error: Could not detect the location of the Java
shared library. You will need to update java.m4
to add support for this JVM configuration.
/usr/share/cdbs/1/class/autotools.mk:42: recipe for target
'debian/stamp-autotools' failed

Full build log at
https://buildd.debian.org/status/fetch.php?pkg=scilab&arch=ppc64el&ver=5.5.2-1.1&stamp=1444066243

Cheers,
Emilio

Bug#801059: libxmu's debian/rules is not safe to execute in parallel

[Matthias Klose]

Package: src:libxmu
Version: 2:1.1.2-1
Severity: serious
Tags: sid stretch patch

seen in an Ubuntu test rebuild, however this may happen as well in a Debian 
build.

https://launchpadlibrarian.net/219669711/buildlog_ubuntu-wily-amd64.libxmu_2%3A1.1.2-1_BUILDING.txt.gz

the problem is that -j is added to MAKEFLAGS, and the binary-arch and 
binary-indep targets are executed in parallel.  The Ubuntu build now fails


dh_builddeb -s
[...]
dh_builddeb
dpkg-deb: building package 'libxmu6' in '../libxmu6_1.1.2-1_amd64.deb'.
tar: ./usr/lib/x86_64-linux-gnu/libXmu.so.6.2.0: file changed as we read it
dpkg-deb: error: subprocess tar -cf returned error exit status 1
[...]
debian/rules:101: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 1
make: *** Waiting for unfinished jobs

Every debhelper command for the architecture dependent packages are executed 
twice.

patch at
http://launchpadlibrarian.net/220316375/libxmu_2%3A1.1.2-1_2%3A1.1.2-1ubuntu1.diff.gz

(together with using dpkg-buildflags, maybe dh_autoreconf could be used as 
well).

Bug#800487: retext crashes with a SIGSEGV

[Dmitry Shachnev]

Hi Erik,

On Wed, 30 Sep 2015 17:53:56 -0700, Erik wrote:
> Looks like the error is file line number 27 in ../../src/xcb_out.c:160

Thanks for generating the stacktrace. Can you please try the attached patch?

You can apply it to installed package using:

  # patch /usr/share/retext/ReText/xsettings.py < 800487.patch

After that start ReText and test if the crash is still present.

Unfortunately I cannot reproduce this crash on Xfce, so I cannot test it
myself.

> FYI: Many python libraries were suddenly upgraded after the last day it
> worked.

Yes, because there was a rebuild to add Python 3.5 as supported version.
It should not change anything with regards to this bug.

Thanks in advance,

--
Dmitry Shachnevdiff --git a/ReText/xsettings.py b/ReText/xsettings.py
index 0f0ac2c..9cb2550 100644
--- a/ReText/xsettings.py
+++ b/ReText/xsettings.py
@@ -78,7 +78,7 @@ def get_raw_xsettings(display=0):
 	# open the connection
 	connection = xcb.xcb_connect(None, None)
 	error = xcb.xcb_connection_has_error(connection)
-	if error:
+	if error or not connection:
 		raise XSettingsError(_xcb_error_messages[error])
 
 	# get selection atom cookie


signature.asc
Description: OpenPGP digital signature

Processed: [bts-link] source package gtk-theme-config

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package gtk-theme-config
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #791548 (http://bugs.debian.org/791548)
> # Bug title: gtk-theme-config: clicking on Revert silently removes the user's 
> .gtkrc-2.0 file
> #  * https://bugs.launchpad.net/bugs/1473821
> #  * remote status changed: Triaged -> Fix-Released
> #  * closed upstream
> tags 791548 + fixed-upstream
Bug #791548 [gtk-theme-config] gtk-theme-config: clicking on Revert silently 
removes the user's .gtkrc-2.0 file
Added tag(s) fixed-upstream.
> usertags 791548 - status-Triaged
Usertags were: status-Triaged.
Usertags are now: .
> usertags 791548 + status-Fix-Released
There were no usertags set.
Usertags are now: status-Fix-Released.
> thanks
Stopping processing here.

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

Processed: Re: Processed: libvigraimpex: library transition is needed when GCC 5 is the default

[Debian Bug Tracking System]

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

> severity 794736 normal
Bug #794736 [release.debian.org] libvigraimpex: library transition is needed 
when GCC 5 is the default
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: .

[Debian Bug Tracking System]

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

> tags 798535 confirmed upstream
Bug #798535 [src:ruby-gsl] ruby-gsl ftbfs in unstable
Added tag(s) upstream and confirmed.
> forwarded 798535 https://github.com/SciRuby/rb-gsl/issues/22
Bug #798535 [src:ruby-gsl] ruby-gsl ftbfs in unstable
Set Bug forwarded-to-address to 'https://github.com/SciRuby/rb-gsl/issues/22'.
> thanks
Stopping processing here.

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

Processed: Bug#770369: Eterm on Jessie, Stretch and Sid does not run shell (fwd)

[Debian Bug Tracking System]

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

> severity 770369 serious
Bug #770369 [eterm] Eterm: does not run shell
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#801046: fatal: Out of memory, malloc failed (tried to allocate 524288000 bytes)

[PICCORO McKAY Lenz]

Package: git
Version: 1:1.7.10.4-1+wheezy1
Severity: grave
Tags: patch

Current version of git for wheeze and squeeze are unusable, does not
work as normal user
for make it work user must know the root password and swicht, sudo
does not work!

some related 
https://bitbucket.org/site/master/issues/4174/clone-pull-on-shared-hosting-with-limited

some sites offers some solutions:
http://stackoverflow.com/questions/8855317/git-push-out-of-memory-malloc-failed
but its on the server remote side, users does not manage servers will clone!

a example of problem behavior (and then a proposed solution and some
notes, see below):

intranet@sysmail00:~/Devel$ git clone
https://gitlab.com/mckaygerhard/simplecontrolasistencia.git
Cloning into 'simplecontrolasistencia'...
Username for 'https://gitlab.com': mckaygerhard
Password for 'https://mckaygerh...@gitlab.com':
fatal: Out of memory, malloc failed (tried to allocate 524288000 bytes)
fatal: Not a git repository: '/home/intranet/Devel/simplecontrolasistencia/.git'

But some sites said around a solutions, mention that change system values:
https://github.com/gitlabhq/gitlabhq/issues/3882#issuecomment-40053598
the following two comments seems solves the problem, but a consecuence
may happened
as :http://www.ericlin.me/git-broken-pipe-out-of-memory-error mentin
that if the buffer
does not return to normal value other problems may happened

So as the current git packages in squeeze and wheeze (including
backports) can be patched
to defaults to that values, the secnd proble are a consecuence around
up the value of buffer
lest see how now works for the configured values:

intranet@sysmail00:~/devel$ fatal: Not a git repository:
'/home/intranet/devel/simplecontrolasistencia/.git'
git clone https://gitlab.comgit config --global pack.threads 1
intranet@sysmail00:~/devel$ git config --global
core.packedGitWindowSize 157286400
intranet@sysmail00:~/devel$ git config --global core.packedGitLimit 157286400
intranet@sysmail00:~/devel$ git config --global core.windowMemory 157286400
intranet@sysmail00:~/devel$ git config --global pack.packSizeLimit 157286400
intranet@sysmail00:~/devel$ git config --global pack.deltaCacheSize 157286400
intranet@sysmail00:~/devel$ git config --global pack.windowMemory 157286400
intranet@sysmail00:~/devel$ git config --global http.postBuffer 157286400
intranet@sysmail00:~/devel$ git clone
https://gitlab.com/mckaygerhard/simplecontrolasistencia.git
Cloning into 'simplecontrolasistencia'...
Username for 'https://gitlab.com': mckaygerhard
Password for 'https://mckaygerh...@gitlab.com':
remote: Counting objects: 957, done.
remote: Compressing objects: 100% (606/606), done.
remote: Total 957 (delta 341), reused 907 (delta 321)
Receiving objects: 100% (957/957), 6.14 MiB | 37.00 KiB/s, done.
Resolving deltas: 100% (341/341), done.
Checking connectivity... done.
intranet@sysmail00:~/devel$


IF THE VALUES ARE NOT REESTABLISHED THIS HAPPENED:

git-remote-https(52011,0x7fff7011acc0) malloc: ***
mmap(size=18446744071938875392) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
git-remote-https(52011,0x7fff7011acc0) malloc: ***
mmap(size=18446744071938875392) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
fatal: Out of memory, malloc failed (tried to allocate
18446744071938872320 bytes)

NOTE THAT IF YOU MADE THIS AS ROOT THE CLONE WILL WORK! WITH ANY VALUES!

intranet@sysmail00:~/Devel$ su
Contraseña:
root@sysmail00:~/devel$ git config --global http.postBuffer 5242880
root@sysmail00:/home/intranet/devel# git clone
https://gitlab.com/mckaygerhard/simplecontrolasistencia.git
Cloning into 'simplecontrolasistencia'...
Username for 'https://gitlab.com': mckaygerhard
Password for 'https://mckaygerh...@gitlab.com':
remote: Counting objects: 957, done.
remote: Compressing objects: 100% (606/606), done.

In this case the total amount of retrieve data are not calculated
(6,14 Mb), but as normal user yes!.

-- System Information:
Debian Release: 7.7
  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/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages git depends on:
ii  git-man  1:1.7.10.4-1+wheezy1
ii  libc62.13-38+deb7u6
ii  libcurl3-gnutls  7.26.0-1+wheezy10
ii  liberror-perl0.17-1
ii  libexpat12.1.0-1+deb7u1
ii  perl-modules 5.14.2-21+deb7u2
ii  zlib1g   1:1.2.7.dfsg-13

Versions of packages git recommends:
ii  less 444-4
ii  openssh-client [ssh-client]  1:6.0p1-4+deb7u2
ii  patch2.6.1-3
ii  rsync3.0.9-4

Versions of packages git suggests:
ii  gettext-base  0.18.1.1-9
pn  git-arch  
pn  g

Processed: reassign 799948 to glx-alternative-nvidia

[Debian Bug Tracking System]

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

> reassign 799948 glx-alternative-nvidia 0.6.0
Bug #799948 [glx-diversions] glx-diversions: Upgrade to version 0.6.0 made 
sddm-greeter crash
Bug #800836 [glx-diversions] glx-diversions: Upgrade to version 0.6.0 made 
sddm-greeter crash
Bug reassigned from package 'glx-diversions' to 'glx-alternative-nvidia'.
Bug reassigned from package 'glx-diversions' to 'glx-alternative-nvidia'.
No longer marked as found in versions glx-alternatives/0.6.0 and 340.93-1.
No longer marked as found in versions glx-alternatives/0.6.0 and 340.93-1.
Ignoring request to alter fixed versions of bug #799948 to the same values 
previously set
Ignoring request to alter fixed versions of bug #800836 to the same values 
previously set
Bug #799948 [glx-alternative-nvidia] glx-diversions: Upgrade to version 0.6.0 
made sddm-greeter crash
Bug #800836 [glx-alternative-nvidia] glx-diversions: Upgrade to version 0.6.0 
made sddm-greeter crash
Marked as found in versions glx-alternatives/0.6.0.
Marked as found in versions glx-alternatives/0.6.0.
> thanks
Stopping processing here.

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

Processed: tagging 800462

[Debian Bug Tracking System]

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

> tags 800462 + pending
Bug #800462 [sddm-theme-maui] sddm-theme-maui: updating results in WHITE SCREEN 
and beeing unable to login
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#800934: linux-image-4.2.0-1-amd64: Kernel 4.2.0-1-amd64 does not boot

[Ben Hutchings]

Control: severity -1 important
Control: tag -1 moreinfo

On Mon, 05 Oct 2015 10:24:04 +0200 Stéphane Glondu  wrote:
> Package: src:linux
> Version: 4.2.1-2
> Severity: grave

No, this only applies to certain configurations.

> Dear Maintainer,
> 
> After installing linux-image-4.2.0-1-amd64, my laptop does not boot
> anymore. Attached is a picture of the screen. Booting with
> linux-image-4.1.0-2-amd64 still works (I am writing this bug report
> from said laptop).
> 
> Maybe it is related to encryption? My root filesystem is in a LVM
> logical volume, which is inside an encrypted LVM physical volume.
[...]

It's not the disk encryption; I think it's IPsec.

I think the crash is late enough that it will have been logged to
/var/log/messages, so please can you provide the full BUG/oops message
from there?

Ben.

-- 
Ben Hutchings
compatible: Gracefully accepts erroneous data from any source

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

Processed: Re: linux-image-4.2.0-1-amd64: Kernel 4.2.0-1-amd64 does not boot

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #800934 [src:linux] linux-image-4.2.0-1-amd64: Kernel 4.2.0-1-amd64 does 
not boot
Severity set to 'important' from 'grave'
> tag -1 moreinfo
Bug #800934 [src:linux] linux-image-4.2.0-1-amd64: Kernel 4.2.0-1-amd64 does 
not boot
Added tag(s) moreinfo.

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

Processed: merge

[Debian Bug Tracking System]

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

> reassign 800836 glx-diversions 0.6.0
Bug #800836 [nvidia-legacy-340xx-driver] glx-diversions: Upgrade to version 
0.6.0 made sddm-greeter crash
Bug reassigned from package 'nvidia-legacy-340xx-driver' to 'glx-diversions'.
No longer marked as found in versions 
nvidia-graphics-drivers-legacy-340xx/340.93-1.
Ignoring request to alter fixed versions of bug #800836 to the same values 
previously set
Bug #800836 [glx-diversions] glx-diversions: Upgrade to version 0.6.0 made 
sddm-greeter crash
Marked as found in versions glx-alternatives/0.6.0.
> severity 800836 grave
Bug #800836 [glx-diversions] glx-diversions: Upgrade to version 0.6.0 made 
sddm-greeter crash
Severity set to 'grave' from 'normal'
> merge 799948 800836
Bug #799948 [glx-diversions] glx-diversions: Upgrade to version 0.6.0 made 
sddm-greeter crash
Bug #800836 [glx-diversions] glx-diversions: Upgrade to version 0.6.0 made 
sddm-greeter crash
There is no source info for the package 'glx-diversions' at version '340.93-1' 
with architecture ''
Unable to make a source version for version '340.93-1'
Marked as found in versions 340.93-1.
Merged 799948 800836
> thanks
Stopping processing here.

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

Processed: affects 800923, affects 800925, tagging 800689

[Debian Bug Tracking System]

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

> affects 800923 + corosync-dev
Bug #800923 [libcorosync-common-dev] libcorosync-common-dev: fails to upgrade 
from 'jessie' - trying to overwrite /usr/include/corosync/corodefs.h
Added indication that 800923 affects corosync-dev
> affects 800925 + libatlas-cpp-0.6-dev
Bug #800925 {Done: Olek Wojnar } [libatlas-cpp-0.6-tools] 
libatlas-cpp-0.6-tools: fails to upgrade from 'jessie' - trying to overwrite 
/usr/bin/atlas_convert
Added indication that 800925 affects libatlas-cpp-0.6-dev
> tags 800689 + sid stretch
Bug #800689 [telepathy-glib] new glib makes it fail to build
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

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

Bug#794466: virtualbox: Virtualbox might not be suitable for testing

[Gianfranco Costamagna]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Clemens,

this bug has *nothing* to deal with your bug.

please open a new one.
thanks

Gianfranco

On Mon, 05 Oct 2015 08:34:01 +0200 Clemens Haupt Hohentrenk
 wrote:
> Package: virtualbox Version: 5.0.4-dfsg-4 Followup-For: Bug
> #794466
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where
> appropriate ***
> 
> * What led up to the situation?
> 
> Updateing yesterday didn't help
> 
> * What exactly did you do (or not do) that was effective (or 
> ineffective)?
> 
> Undating
> 
> * What was the outcome of this action?
> 
> The virtual machine 'Deppi-505' has terminated unexpectedly during
> startup with exit code 1 (0x1).
> 
> * What outcome did you expect instead?
> 
> Smooth working
> 
> 
> *** End of the template - remove these template lines ***
> 
> 
> -- System Information: Debian Release: stretch/sid APT prefers
> testing APT policy: (650, 'testing'), (600, 'unstable'), (500,
> 'oldstable-updates'), (500, 'oldstable') Architecture: i386 (i686)
> 
> Kernel: Linux 4.2.0-1-686-pae (SMP w/2 CPU cores) Locale:
> LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell:
> /bin/sh linked to /bin/dash Init: systemd (via
> /run/systemd/system)
> 
> Versions of packages virtualbox depends on: ii  adduser
> 3.113+nmu3 ii  libc62.19-22 ii  libcurl3-gnutls
> 7.44.0-2 ii  libgcc1  1:5.2.1-17 ii  libgsoap7
> 2.8.22-1 ii  libpng12-0   1.2.50-2+b2 ii  libpython2.7
> 2.7.10-4 ii  libsdl1.2debian  1.2.15-11 ii  libssl1.0.0
> 1.0.2d-1 ii  libstdc++6   5.2.1-17 ii  libvncserver1
> 0.9.10+dfsg-3 ii  libvpx2  1.4.0-4 ii  libx11-6
> 2:1.6.3-1 ii  libxcursor1  1:1.1.14-1+b1 ii  libxext6
> 2:1.3.3-1 ii  libxml2  2.9.2+zdfsg1-4 ii  libxmu6
> 2:1.1.2-1 ii  libxt6   1:1.1.4-1+b1 ii  python
> 2.7.9-1
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWEnyfAAoJEPNPCXROn13ZlDEP/0TzzSsbsRSmcGRHBuU3kgNC
MB9HghCVKNDUkU0B/cIglgWfzIdnQ8TtpYd85bZ29WOzZ9KkEDs+hqBqLQLUuAVJ
252kQkEfDvUleHMIMrgznc0obbtoQid/xijcs51QOMWOhOFAdIDgZKSfBhtXIL52
LTYcdXycLlMIsEYB2XUSl/qxDVVPU2orx1XHN765pNSXyy/+ltvenq9D0GQCaYME
Y51aRLxUvPZOHTCt//aBZq49/jG64eSYj8Pp33+mXaXlDy2NpN4V/wdw4gvBL0vH
tepZ8lArjwTI/BaEmmnNUPqodtgnNkJCNoKMFhrr+7xLL5KdULuMUUmgh5fOdQKm
bksLT8U1k/lglzr7dm5DVRqTP0Jjk92Cm5v6AcPjkuwbELXuEa24UP46CEof1AdF
8T8luOkvZwQE2+PobPOMRHyXp+lFjrWa/3v50u6gqRS3IdBhm4jUcAcOpeiLFtXk
Ddw9XlISpkn87nO1PejikhPLM3VoDFYGu/e0LqV8SDFdGPUeVy+ywV6srGQqdb5L
up103q3sjlp0KWBA81upXTglhSRZcm4PA879YMXJJYOBp9SDzjxN4lDe+dNStduq
Fhnzq/TqrQnjo5CY54GWT9arhO4j2nTTZKyjDC6EFEGD6Q9dyMoy4U7P9q1CXDrx
hAs5AztGpmJOzvNSRdLb
=7Z9D
-END PGP SIGNATURE-

Processed: singular-ui: fails to upgrade squeeze -> wheezy -> jessie -> stretch

[Debian Bug Tracking System]

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

> severity 800961 important
Bug #800961 [singular-ui] singular-ui: fails to upgrade squeeze -> wheezy -> 
jessie -> stretch
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: tagging 800923

[Debian Bug Tracking System]

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

> tags 800923 + pending
Bug #800923 [libcorosync-common-dev] libcorosync-common-dev: fails to upgrade 
from 'jessie' - trying to overwrite /usr/include/corosync/corodefs.h
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#800924: marked as done (uronode: fails to upgrade from 'jessie' - trying to overwrite /usr/share/man/man1/nodeusers.1.gz)

[Debian Bug Tracking System]

Your message dated Mon, 05 Oct 2015 12:48:44 +
with message-id 
and subject line Bug#800924: fixed in uronode 2.3.1-2
has caused the Debian Bug report #800924,
regarding uronode: fails to upgrade from 'jessie' - trying to overwrite 
/usr/share/man/man1/nodeusers.1.gz
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.)


-- 
800924: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: uronode
Version: 2.3.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package uronode.
  Preparing to unpack .../uronode_2.3.1-1_amd64.deb ...
  Unpacking uronode (2.3.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/uronode_2.3.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/nodeusers.1.gz', which is also in 
package ax25-node 0.3.2-7.4
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/uronode_2.3.1-1_amd64.deb


cheers,

Andreas


ax25-node=0.3.2-7.4_uronode=2.3.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: uronode
Source-Version: 2.3.1-2

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

Debian distribution maintenance software
pp.
Iain R. Learmonth  (supplier of updated uronode 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: Mon, 05 Oct 2015 13:28:37 +0100
Source: uronode
Binary: uronode
Architecture: source i386
Version: 2.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Iain R. Learmonth 
Description:
 uronode- Node front end for AX.25, NET/ROM, Rose and TCP
Closes: 800924
Changes:
 uronode (2.3.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Add Breaks+Replaces for ax25-node. (Closes: #800924)
Checksums-Sha1:
 32d1f6c28217d17fe7ede9b26fed2c9940d0193a 1566 uronode_2.3.1-2.dsc
 bac75d644fa25874fba23996a6e10b4be440dc0e 11176 uronode_2.3.1-2.debian.tar.xz
 983cf468e2ffb428679331616d9c9b79262dc2f1 105046 uronode_2.3.1-2_i386.deb
Checksums-Sha256:
 c630680ba1424806437d12e2c5baae7344967be836032bb39da7cd1ffbbd89d9 1566 
uronode_2.3.1-2.dsc
 8ded90499098e74b8d99371e3a49468d5158115f9169da141c4e25a16d952a61 11176 
uronode_2.3.1-2.debian.tar.xz
 f97680aa675d24cceb4bdea50094a7be752ad6bebf7dbcafa6026ffdb2826b6b 105046 
uronode_2.3.1-2_i386.deb
Files:
 c82eae02348a37bf510f8c1100ef3008 1566 hamradio optional uronode_2.3.1-2.dsc
 127603d8d45929b97ec979b732f4aeb6 11176 hamradio optional 
uronode_2.3.1-2.debian.tar.xz
 fb433de2e5961f729c8ea509f8bb250d 105046 hamradio optional 
uronode_2.3.1-2_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCgAGBQJWEm3PAAoJEMx+J398PcNN0ZUH/2CWABxME8JqN5/Ac8j7EM4U
YoZqsj9lhHUtsKhZisoYFSgXH9o89rPzRUaed4igbVDYuleJp/GOjglkwOOttVG/
fHzmqncSu3T7LljsLyVMyJuzbhEf+SdXD+wp7UGou7UOzXTaVIwMDDrNsm3hpB76
Uv42lSr1QtzXEahUL8uK4BATOQiW3fZXrN/7TmeqaBa2zu6Dzw5HrL2ya+6+d107
m+DkINrpSuopzPfLDqpOuJXFTfOpPAvTZ0tWwrINmfmtNlzYI2wWRd4qI9EA0sCj
Gd6GHjxAVFN7vfX0ZkL1/bzEWFPH6fGlRls9ztqo8ZEkalDOeVr6PZ5fJ6YyJQ0=
=z6Oq
-END PGP SIGNATURE End Message ---

Bug#800961: singular-ui: fails to upgrade squeeze -> wheezy -> jessie -> stretch

[Andreas Beckmann]

Package: singular-ui
Version: 4.0.2+ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'squeeze' to 'wheezy' to 'jessie'.
It installed fine in 'squeeze', and upgraded to 'wheezy' and 'jessie'
successfully, but then the upgrade to 'stretch' failed because it tries
to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package singular-ui.
  Preparing to unpack .../singular-ui_4.0.2+ds-1+b1_amd64.deb ...
  Unpacking singular-ui (4.0.2+ds-1+b1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/singular-ui_4.0.2+ds-1+b1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/Singular.1.gz', which is also in 
package singular 3-0-4-3.dfsg-3.1
  Selecting previously unselected package singular-modules:amd64.
  Preparing to unpack .../singular-modules_4.0.2+ds-1+b1_amd64.deb ...
  Unpacking singular-modules:amd64 (4.0.2+ds-1+b1) ...
  Preparing to unpack .../singular_4.0.2+ds-1+b1_amd64.deb ...
  Unpacking singular (4.0.2+ds-1+b1) over (3-0-4-3.dfsg-3.1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/singular-ui_4.0.2+ds-1+b1_amd64.deb

(There is no singular package in wheezy or jessie, so the one from
squeeze was kept installed.)


cheers,

Andreas


singular_4.0.2+ds-1+b1.log.gz
Description: application/gzip

Bug#800959: xserver-xorg-core: fails to upgrade with old version of x11-common installed

[James Cowgill]

Package: xserver-xorg-core
Version: 1.17.2-2
Severity: serious

Hi,

xserver-xorg-core does not upgrade to the version in experimental if
the old version of x11-common is installed.

# dpkg -l xserver-xorg x11-common xserver-xorg-core
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion  Architecture 
Description
+++-===---
ii  x11-common  1:7.7+9  all  X 
Window System (X.Org) infrastructure
ii  xserver-xorg1:7.7+9  amd64
X.Org X server
ii  xserver-xorg-core   2:1.17.2-1.1 amd64
Xorg X server - core server

# dpkg -i /var/cache/apt/archives/xserver-xorg_1%3a7.7+11_amd64.deb 
/var/cache/apt/archives/xserver-xorg-core_2%3a1.17.2-2_amd64.deb 
(Reading database ... 209469 files and directories currently installed.)
Preparing to unpack .../xserver-xorg_1%3a7.7+11_amd64.deb ...
Unpacking xserver-xorg (1:7.7+11) over (1:7.7+9) ...
Preparing to unpack .../xserver-xorg-core_2%3a1.17.2-2_amd64.deb ...
Unpacking xserver-xorg-core (2:1.17.2-2) over (2:1.17.2-1.1) ...
dpkg: error processing archive 
/var/cache/apt/archives/xserver-xorg-core_2%3a1.17.2-2_amd64.deb (--install):
 trying to overwrite '/usr/share/man/man5/Xwrapper.config.5.gz', which is also 
in package x11-common 1:7.7+9
dpkg: dependency problems prevent configuration of xserver-xorg:
 xserver-xorg depends on xserver-xorg-core (>= 2:1.17.2-2); however:
  Version of xserver-xorg-core on system is 2:1.17.2-1.1.

dpkg: error processing package xserver-xorg (--install):
 dependency problems - leaving unconfigured
Processing triggers for man-db (2.7.3-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/xserver-xorg-core_2%3a1.17.2-2_amd64.deb
 xserver-xorg

Thanks,
James

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

Bug#800957: waagent: fails to install due to insserv rejecting the script header

[Andreas Beckmann]

Package: waagent
Version: 2.1.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install due
to insserv rejecting the script header. Some notes are
available from at https://wiki.debian.org/LSBInitScripts

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package waagent.
  (Reading database ... 
(Reading database ... 12007 files and directories currently installed.)
  Preparing to unpack .../waagent_2.1.0-2_all.deb ...
  Unpacking waagent (2.1.0-2) ...
  Processing triggers for systemd (226-3) ...
  Setting up waagent (2.1.0-2) ...
  insserv: Service cloud-config has to be enabled to start service walinuxagent
  insserv: exiting now!
  update-rc.d: error: insserv rejected the script header
  dpkg: error processing package waagent (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for systemd (226-3) ...
  Errors were encountered while processing:
   waagent


cheers,

Andreas


waagent_2.1.0-2.log.gz
Description: application/gzip

Bug#800954: vdr-plugin-xine: FTBFS with vdr 2.2.0: error: invalid conversion from 'cPixmap*' to 'cPixmapMemory*'

[Andreas Beckmann]

Source: vdr-plugin-xine
Version: 0.9.4-13
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

vdr-plugin-xine cannot be built with vdr 2.2.0 in sid:

 debian/rules build
dh build --parallel
   dh_testdir -O--parallel
   dh_auto_configure -O--parallel
   debian/rules override_dh_auto_build
make[1]: Entering directory '/tmp/buildd/vdr-plugin-xine-0.9.4'
dh_auto_build -- all DVBDIR=/usr VDRDIR=/usr/include/vdr LIBDIR=. 
LOCALEDIR=debian/tmp/usr/share/locale
make -j1 all DVBDIR=/usr VDRDIR=/usr/include/vdr LIBDIR=. 
LOCALEDIR=debian/tmp/usr/share/locale
make[2]: Entering directory '/tmp/buildd/vdr-plugin-xine-0.9.4'
g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 
-fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
-D_LARGEFILE64_SOURCE -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xine"' 
-DFIFO_DIR=\"/tmp/vdr-xine\" -DVERIFY_BITMAP_DIRTY=0 -DSET_VIDEO_WINDOW 
`pkg-config --cflags libxine`  -I/usr/include/vdr/include xine.c
g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 
-fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
-D_LARGEFILE64_SOURCE -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xine"' 
-DFIFO_DIR=\"/tmp/vdr-xine\" -DVERIFY_BITMAP_DIRTY=0 -DSET_VIDEO_WINDOW 
`pkg-config --cflags libxine`  -I/usr/include/vdr/include xineDevice.c
xineDevice.c: In member function 'void 
PluginXine::cXineDevice::mainMenuTrampoline()':
xineDevice.c:4234:79: warning: ignoring return value of 'int asprintf(char**, 
const char*, ...)', declared with attribute warn_unused_result [-Wunused-result]
   ::asprintf(&msg, tr("Switching primary DVB to %s..."), m_plugin->Name());
   ^
xineDevice.c:4245:82: warning: ignoring return value of 'int asprintf(char**, 
const char*, ...)', declared with attribute warn_unused_result [-Wunused-result]
   ::asprintf(&msg, tr("Switched primary DVB back from %s"), 
m_plugin->Name());

  ^
g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 
-fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
-D_LARGEFILE64_SOURCE -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xine"' 
-DFIFO_DIR=\"/tmp/vdr-xine\" -DVERIFY_BITMAP_DIRTY=0 -DSET_VIDEO_WINDOW 
`pkg-config --cflags libxine`  -I/usr/include/vdr/include xineLib.c
xineLib.c: In member function 'uchar* 
PluginXine::cXineLib::execFuncGrabImage(const char*, int&, bool, int, int, 
int)':
xineLib.c:4305:21: warning: ignoring return value of 'int asprintf(char**, 
const char*, ...)', declared with attribute warn_unused_result [-Wunused-result]
 , outfd);
 ^
xineLib.c:4313:21: warning: ignoring return value of 'int asprintf(char**, 
const char*, ...)', declared with attribute warn_unused_result [-Wunused-result]
 , outfd);
 ^
g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 
-fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
-D_LARGEFILE64_SOURCE -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xine"' 
-DFIFO_DIR=\"/tmp/vdr-xine\" -DVERIFY_BITMAP_DIRTY=0 -DSET_VIDEO_WINDOW 
`pkg-config --cflags libxine`  -I/usr/include/vdr/include xineOsd.c
xineOsd.c: In member function 'void PluginXine::cXineOsd::callSendWindow(int, 
int, int, int, int, int, int, int, bool)':
xineOsd.c:501:47: error: invalid conversion from 'cPixmap*' to 'cPixmapMemory*' 
[-fpermissive]
   while (cPixmapMemory *pm = RenderPixmaps())
   ^
Makefile:105: recipe for target 'xineOsd.o' failed
make[2]: *** [xineOsd.o] Error 1
make[2]: Leaving directory '/tmp/buildd/vdr-plugin-xine-0.9.4'
dh_auto_build: make -j1 all DVBDIR=/usr VDRDIR=/usr/include/vdr LIBDIR=. 
LOCALEDIR=debian/tmp/usr/share/locale returned exit code 2
debian/rules:14: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/tmp/buildd/vdr-plugin-xine-0.9.4'
debian/rules:11: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


Andreas

Bug#800952: vdr-plugin-vcd: FTBFS with vdr 2.2.0: DeviceTrickSpeed API change

[Andreas Beckmann]

Source: vdr-plugin-vcd
Version: 0.9-22
Severity: serious
Tags: sid stretch
Justification: fails to build from source (but built successfully in the past)
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

vdr-plugin-vcd cannot be built with vdr 2.2.0 in sid:

 debian/rules build
dh build
   dh_testdir
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/tmp/buildd/vdr-plugin-vcd-0.9'
dh_auto_build -- all VDRDIR=/usr/include/vdr LIBDIR=. LOCALEDIR=locale
make -j1 all VDRDIR=/usr/include/vdr LIBDIR=. LOCALEDIR=locale
make[2]: Entering directory '/tmp/buildd/vdr-plugin-vcd-0.9'
g++ -fPIC -O2 -Wall -Woverloaded-virtual -c -DPLUGIN_NAME_I18N='"vcd"' 
-D_GNU_SOURCE -I/usr/include/vdr/include vcd.c
g++ -fPIC -O2 -Wall -Woverloaded-virtual -c -DPLUGIN_NAME_I18N='"vcd"' 
-D_GNU_SOURCE -I/usr/include/vdr/include functions.c
g++ -fPIC -O2 -Wall -Woverloaded-virtual -c -DPLUGIN_NAME_I18N='"vcd"' 
-D_GNU_SOURCE -I/usr/include/vdr/include menu.c
g++ -fPIC -O2 -Wall -Woverloaded-virtual -c -DPLUGIN_NAME_I18N='"vcd"' 
-D_GNU_SOURCE -I/usr/include/vdr/include player.c
player.c: In member function 'void cVcdPlayer::TrickSpeed(int)':
player.c:164:25: error: no matching function for call to 
'cVcdPlayer::DeviceTrickSpeed(int&)'
  DeviceTrickSpeed(sp);
 ^
In file included from player.h:27:0,
 from player.c:24:
/usr/include/vdr/player.h:30:8: note: candidate: void 
cPlayer::DeviceTrickSpeed(int, bool)
   void DeviceTrickSpeed(int Speed, bool Forward) { if (device) 
device->TrickSpeed(Speed, Forward); }
^
/usr/include/vdr/player.h:30:8: note:   candidate expects 2 arguments, 1 
provided
Makefile:61: recipe for target 'player.o' failed
make[2]: *** [player.o] Error 1
make[2]: Leaving directory '/tmp/buildd/vdr-plugin-vcd-0.9'
dh_auto_build: make -j1 all VDRDIR=/usr/include/vdr LIBDIR=. LOCALEDIR=locale 
returned exit code 2
debian/rules:12: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/tmp/buildd/vdr-plugin-vcd-0.9'
debian/rules:9: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2



Andreas

Processed: tagging 781103, found 788852 in 1.1.2-1, reassign 800929 to src:linux

[Debian Bug Tracking System]

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

> tags 781103 + sid stretch
Bug #781103 {Done: Timo Aaltonen } [libwacom2] libwacom2: 
Needs update for 3.17 and above
Added tag(s) sid and stretch.
> found 788852 1.1.2-1
Bug #788852 [liblognorm2] liblognorm2: removal of liblognorm2 makes files 
disappear from liblognorm1
Marked as found in versions liblognorm/1.1.2-1.
> reassign 800929 src:linux 3.16.7-ckt11-1+deb8u4
Bug #800929 [linux_source-3.16] linux_source-3.16: Scheduler prefers pinned 
tasks
Warning: Unknown package 'linux_source-3.16'
Bug reassigned from package 'linux_source-3.16' to 'src:linux'.
No longer marked as found in versions 3.16.7-ckt11-1+deb8u4.
Ignoring request to alter fixed versions of bug #800929 to the same values 
previously set
Bug #800929 [src:linux] linux_source-3.16: Scheduler prefers pinned tasks
Marked as found in versions linux/3.16.7-ckt11-1+deb8u4.
> thanks
Stopping processing here.

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

Bug#800950: mate-media-common has disappeared

[Andreas Beckmann]

Source: mate-media
Version: 1.10.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed mate-media is no longer
installable in sid since mate-media-common was accidently decrufted:


http://bugs.debian.org/800557

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

mate-media | 1.8.0+dfsg1-4 | all
mate-media-common | 1.8.0+dfsg1-4 | all
mate-media-common |   1.10.0-1 | all

--- Reason ---
RoQA; obsolete cruft binary
--


mate-media-common 1.10.0-1 should not have been in this list ... please
upload it again.


Andreas

Bug#779482: severity of 779482 is grave

[Gilles Filippini]

Markus Koschany a écrit le 05/10/2015 13:02 :
> Am 05.10.2015 um 12:48 schrieb Emmanuel Bourg:
>> Le 05/10/2015 12:18, Markus Koschany a écrit :
> I think it's ok to initially build with arch:any as long as there is
> sufficient support from upstream. However if it turns out that some
> arch-dependent packages are unusable and upstream does not intend to fix
> this, we should not claim that we can. I think restricting the build to
> supported architectures is sensible then.
> 
> Like I said I don't know if those architectures are supported now. Back
> in April Tony wrote that upstream has started to work on architecture
> support.
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779482#21
> 
> Perhaps something has changed in the latest version?

Yes, support was added for some architectures. Unfortunately not for
ppc64el.

BTW building gluegen2 for unsupported architectures leads to bugs like
#798652. It is quite misleading for our users to see scilab available on
ppc64el while not functional at all.

Thanks,

_g.



signature.asc
Description: OpenPGP digital signature

Processed: tagging 799280

[Debian Bug Tracking System]

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

> tags 799280 + pending
Bug #799280 [src:openjfx] Depends on gstreamer 0.10
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#779482: severity of 779482 is grave

[Markus Koschany]

Am 05.10.2015 um 12:48 schrieb Emmanuel Bourg:
> Le 05/10/2015 12:18, Markus Koschany a écrit :
> 
>> I think we should determine if upstream supports ppc64el. If not, it is
>> reasonable to remove ppc64el and other affected ports from the
>> Architecture field.
> 
> I don't know, for some packages we do not exclude the unsupported
> architectures explicitly so the builders can attempt the build and
> identify the portability issue. For example with openjfx, I initially
> restricted the build to i386/amd64 but I was later asked to remove the
> limitation (#765397).


I think it's ok to initially build with arch:any as long as there is
sufficient support from upstream. However if it turns out that some
arch-dependent packages are unusable and upstream does not intend to fix
this, we should not claim that we can. I think restricting the build to
supported architectures is sensible then.

Like I said I don't know if those architectures are supported now. Back
in April Tony wrote that upstream has started to work on architecture
support.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779482#21

Perhaps something has changed in the latest version?

Markus



signature.asc
Description: OpenPGP digital signature

Bug#779482: severity of 779482 is grave

[Emmanuel Bourg]

Le 05/10/2015 12:18, Markus Koschany a écrit :

> I think we should determine if upstream supports ppc64el. If not, it is
> reasonable to remove ppc64el and other affected ports from the
> Architecture field.

I don't know, for some packages we do not exclude the unsupported
architectures explicitly so the builders can attempt the build and
identify the portability issue. For example with openjfx, I initially
restricted the build to i386/amd64 but I was later asked to remove the
limitation (#765397).

Emmanuel Bourg

Bug#779482: severity of 779482 is grave

[Markus Koschany]

Am 05.10.2015 um 12:07 schrieb Emmanuel Bourg:
> On Sun, 04 Oct 2015 17:10:40 +0200 Gilles Filippini  wrote:
> 
>> Setting back severity to grave because ppc64el is an official
>> architecture since novembre 2014 and there is no point in providing
>> gluegen2 for ppc64el if it is unusable.
> 
> On the other hand, the affected architectures have a combined popcon of
> 0.3%. I don't think it's fair to push the severity to serious and risk a
> removal that would affect all the other architectures.

I think we should determine if upstream supports ppc64el. If not, it is
reasonable to remove ppc64el and other affected ports from the
Architecture field.

Regards,

Markus






signature.asc
Description: OpenPGP digital signature

Bug#800946: libunity-dev: please switch to libgee-0.8-dev

[Andreas Beckmann]

Package: libunity-dev
Version: 6.12.0-1~experimental1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable since libgee-dev is gone. According to #786454 this has been
replaced by libgee-0.8-dev.


Andreas

Bug#779482: severity of 779482 is grave

[Emmanuel Bourg]

On Sun, 04 Oct 2015 17:10:40 +0200 Gilles Filippini  wrote:

> Setting back severity to grave because ppc64el is an official
> architecture since novembre 2014 and there is no point in providing
> gluegen2 for ppc64el if it is unusable.

On the other hand, the affected architectures have a combined popcon of
0.3%. I don't think it's fair to push the severity to serious and risk a
removal that would affect all the other architectures.

Emmanuel Bourg

Bug#800920: [Pkg-fglrx-devel] Bug#800920: X segfaults during startup if fglrx is used

[Patrick Matthäi]

Am 05.10.2015 um 02:33 schrieb Florian Uekermann:

Upgrading to fglrx 1:15.9-1 on a fully upgraded stretch system led to the
following reproducible error (segfault) on X startup (xinit in this case):


Hi,

which was the last working version for you?

--
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 800941 https://bugzilla.gnome.org/show_bug.cgi?id=749314
Bug #800941 [src:glib2.0] regression in 2.46: can't restore a just-trashed file
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=749314'.
> tags 800941 stretch sid upstream
Bug #800941 [src:glib2.0] regression in 2.46: can't restore a just-trashed file
Added tag(s) stretch, sid, and upstream.
> affects 800941 caja nemo nautilus thunar
Bug #800941 [src:glib2.0] regression in 2.46: can't restore a just-trashed file
Added indication that 800941 affects caja, nemo, nautilus, and thunar
>
End of message, stopping processing here.

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

Bug#732723: cegui-mk2: Please upgrade OGRE dependency to 1.9 when upstream ready

[Muammar El Khatib]

On Sun, Sep 27, 2015 at 8:42 PM, Tobias Frost  wrote:
>> Yes. Go ahead. Today I contacted FTP masters because I think the
>> debian/copyright file is ok. I will keep you posted about it.
>>
>
> Recreated the repository in the meantime.


So far I haven't gotten a reply from FTP masters. The claimed the following:

> I found lots of files that are not mentioned in your debian/copyright:
>  doc/doxygen/falagard/fal_main.dox is GFDL
>  promo/* is CC-BY-SA
>  cegui/src/ScriptModules/Python/bindings/generate.py is GPL3
>  cegui/src/ScriptModules/Python/bindings/generators/__init__.py is GPL3
>  cegui/src/ScriptModules/Python/bindings/output/CEGUIOgreRenderer/* is BOOST
>  some fonts in datafiles/font/* have licenses as shown in 
> datafiles/fonts/Legal.txt

But those files were indeed included in the copyright file. See:

https://web.archive.org/web/20150907175032/https://ftp-master.debian.org/new/cegui-mk2_0.8.4-2.html

Regards,

-- 
Muammar El Khatib.
Linux user: 403107.
GPG Key = 71246E4A.
http://muammar.me | http://proyectociencia.org
  ,''`.
 : :' :
 `. `'
   `-

Bug#800668: iep ftbfs, missing build dependencies, still fails tests

[Matthias Klose]

[please reply to the submitter and/or the original sender of the email too]

> I can make a new upload with an explicit empty test target, will it
> solve your issue?

well, it certainly will succeed the build, however why not find out why it 
fails?

Bug#798725: marked as done (golang-github-vbatts-tar-split: FTBFS: B-D favors nonexistent packages over real ones)

[Debian Bug Tracking System]

Your message dated Mon, 05 Oct 2015 09:24:08 +
with message-id 
and subject line Bug#798725: fixed in golang-github-vbatts-tar-split 0.9.7-2
has caused the Debian Bug report #798725,
regarding golang-github-vbatts-tar-split: FTBFS: B-D favors nonexistent 
packages over real ones
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.)


-- 
798725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-vbatts-tar-split
Version: 0.9.7-1
Severity: serious
Justification: fails to build from source

Automatic builds of golang-github-vbatts-tar-split have been failing
because its build dependencies include

  golang-github-codegangsta-cli-dev | golang-codegangsta-cli-dev

and

  golang-github-sirupsen-logrus-dev | golang-logrus-dev

These terms are both technically satisfiable because
golang-codegangsta-cli-dev and golang-logrus-dev both exist in the
archive.  However, for the sake of reproducibility, the autobuilders
only ever try the first option (modulo explicit architectural
constraints), and consequently fail.  Please either remove the
references to golang-github-*-dev or swap them to appear after the
packages that are actually available.

Thanks!
--- End Message ---
--- Begin Message ---
Source: golang-github-vbatts-tar-split
Source-Version: 0.9.7-2

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

Debian distribution maintenance software
pp.
Tianon Gravi  (supplier of updated 
golang-github-vbatts-tar-split 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: Mon, 05 Oct 2015 01:40:31 -0700
Source: golang-github-vbatts-tar-split
Binary: tar-split golang-github-vbatts-tar-split-dev
Architecture: source
Version: 0.9.7-2
Distribution: unstable
Urgency: medium
Maintainer: pkg-go 
Changed-By: Tianon Gravi 
Description:
 golang-github-vbatts-tar-split-dev - tar archive assembly/disassembly (source)
 tar-split  - tar archive assembly/disassembly
Closes: 798725
Changes:
 golang-github-vbatts-tar-split (0.9.7-2) unstable; urgency=medium
 .
   * Swap Build-Depends relation order to appease buildds (Closes: #798725);
 thanks Aaron!
Checksums-Sha1:
 35042bd35015732acc359e96ef68bb2b8753bc0c 2373 
golang-github-vbatts-tar-split_0.9.7-2.dsc
 daac7db95f743ca10284d21c9e6d6bed29833d88 3416 
golang-github-vbatts-tar-split_0.9.7-2.debian.tar.xz
Checksums-Sha256:
 fdaea082ee7c244f9638a97c66a0cd3f0dab0229ac198629e31392827772db6f 2373 
golang-github-vbatts-tar-split_0.9.7-2.dsc
 abae2c9e46770b890b691ae15bc65ae6e8453ba3ca0e6c94a10875408d497309 3416 
golang-github-vbatts-tar-split_0.9.7-2.debian.tar.xz
Files:
 f5a79e9f0344684c414982d6b60eb640 2373 devel extra 
golang-github-vbatts-tar-split_0.9.7-2.dsc
 5d3cf4a07592b71b3e03a5f86d125d72 3416 devel extra 
golang-github-vbatts-tar-split_0.9.7-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWEjekAAoJEANqnCW/NX3U5cIP/jWC0HxyjZZqMZP8Kj5M5NmR
C6OyTGrZvDkKvlSH2Yr4Mt4qL+ialixFoW9n+aPF6tZCVf92pRRVLVj7lcW+9LlT
8jKC3sjb9H7wIvy3eAZ3iEZNZ5h1ZA2bQz3ef437mo6eJ5okWWCxhOBvLPRl+yXh
tsCcl53XuHRKbAorrMyqIuJD696JlmgoPRZ/h3Oh+W5wNiDr8ruZyvdJiJrrTluL
70ZixjJ/b67XI+CfYm4LHnzsz+Nm9pi9nl4MWtMmeQWxhMPAGUN+9VpwkIhiS41p
GH4l5pFfiYNfyLlwRk0EQZri5V5Q1MIm+uPmg4VFW+Dgy+2m36NXEW5gcpN/4ner
z7dYEb++5JS6+ykm1KsqT7vvjdl99Yk3Je00PQCqQ8gqInRGRCAIcFVktehmoIJy
m2S5Jhx1e606YCVmky+mEEewgnNz45KDkysjZxYspoI+pKFqKoOko+7AHkpmnKD4
9O4X8Be8ki1xYdjDoEknM2f9sV6MeaZQohI6GKhSqs5ramLwxf8V5QoEJwm3mUpZ
3yrfcKkeF1Y/mtGjzS4LPiKIPXmYqNFIvyP0WxfUfLC7lOcGOnErJ1calh7Ulzvd
67IOL21VlqN/ufaJjDBYJrGnPeQFIJ4XD9eSNiR4XTUggMCt8MCqVIbEniX7KAB0
SUNko0vUEGe9dlfZeEgm
=G1iJ
-END PGP SIGNATURE End Message ---

Bug#800941: regression in 2.46: can't restore a just-trashed file

[Vlad Orlov]

Source: glib2.0
Version: 2.46.0-2
Severity: critical
Justification: breaks functionality of many file managers

Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=749314
Control: tags -1 stretch sid upstream
Control: affects -1 caja nemo nautilus thunar


Steps to reproduce:
1. Move some file to trash using a file manager or gvfs-trash tool.
   Tested with the following file managers: Caja, Nemo, Nautilus, Thunar.
2. Browse trash and try to restore the file.

The file manager complains that it can't determine the original location
of the file, and so doesn't restore it. This is a regression in 2.46 since
restoring worked fine in 2.44.

The problem is that "trash::orig-path" and "trash::deletion-date" attributes
are not added to the trashed file. Without that the file manager can't
determine the original location of the file, and hence can't restore it.

You can check the file attributes by printing the moved file's info:
gvfs-info trash:///file_name

Check the upstream report [1] for more details.


[1] https://bugzilla.gnome.org/show_bug.cgi?id=749314

Processed: severity of 800689 is serious ...

[Debian Bug Tracking System]

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

> severity 800689 serious
Bug #800689 [telepathy-glib] new glib makes it fail to build
Severity set to 'serious' from 'normal'
> forwarded 800689 https://bugs.freedesktop.org/show_bug.cgi?id=92245
Bug #800689 [telepathy-glib] new glib makes it fail to build
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=92245'.
> thanks
Stopping processing here.

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

Bug#800937: fcml ftbfs on armel

[Matthias Klose]

Package: src:fcml
Version: 1.1.1-2
Severity: serious
Tags: sid stretch

fcml ftbfs on armel (built before there), failing the tests.

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

It also ftbfs on armhf and powerpc, and on Ubuntu only on i386

https://launchpad.net/ubuntu/+source/fcml/1.1.1-2

Some issue with 32bit little endian targets?

Processed: fixed 800798 in 3.18.0-4

[Debian Bug Tracking System]

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

> fixed 800798 3.18.0-4
Bug #800798 {Done: Simon McVittie } [gir1.2-gtk-3.0] gtk+3.0: 
Please add breaks for python(3)-gi << 3.18
Bug #800795 {Done: Simon McVittie } [gir1.2-gtk-3.0] 
quodlibet: does not start
Bug #800804 {Done: Simon McVittie } [gir1.2-gtk-3.0] New 
version 3.18.0 breaks virt-manager graphical console
Marked as fixed in versions gtk+3.0/3.18.0-4.
Marked as fixed in versions gtk+3.0/3.18.0-4.
Marked as fixed in versions gtk+3.0/3.18.0-4.
> thanks
Stopping processing here.

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

Processed: tags 799656

[Debian Bug Tracking System]

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

> tags 799656 stretch
Bug #799656 {Done: Daniel Pocock } [src:node-websocket] 
node-websocket: FTBFS: error: 'NanScope' was not declared in this scope
Added tag(s) stretch.
> stop
Stopping processing here.

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

Bug#800691: marked as done (wicd-curses: just became completely useless. See stacktrace)

[Debian Bug Tracking System]

Your message dated Mon, 05 Oct 2015 07:34:11 +
with message-id 
and subject line Bug#800693: fixed in wicd 1.7.2.4-4.2
has caused the Debian Bug report #800693,
regarding wicd-curses: just became completely useless. See stacktrace
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.)


-- 
800693: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wicd-curses
Version: 1.7.2.4-4.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

the curses interface refuses to start.

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

Kernel: Linux 4.2.1a (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages wicd-curses depends on:
ii  python2.7.9-1
ii  python-urwid  1.3.0-1+b1
ii  wicd-daemon   1.7.2.4-4.1

Versions of packages wicd-curses recommends:
ii  sudo  1.8.12-1

wicd-curses suggests no packages.

Versions of packages wicd-daemon depends on:
ii  adduser  3.113+nmu3
ii  dbus 1.10.0-3
ii  debconf  1.5.57
ii  ethtool  1:3.16-1
ii  iproute  1:4.1.1-1
ii  iputils-ping 3:20121221-5+b2
ii  isc-dhcp-client  4.3.3-3
ii  lsb-base 9.20150917
ii  net-tools1.60+git20150829.73cef8a-1
ii  psmisc   22.21-2.1
ii  python   2.7.9-1
ii  python-dbus  1.2.0-2+b4
ii  python-gobject   3.16.2-1
ii  python-wicd  1.7.2.4-4.1
ii  wireless-tools   30~pre9-8
ii  wpasupplicant2.3-2.1

Versions of packages wicd-daemon recommends:
ii  rfkill  0.5-1

Versions of packages wicd-daemon suggests:
pn  pm-utils  

Versions of packages python-wicd depends on:
ii  python  2.7.9-1

-- debconf information:
* wicd/users: salvo
Traceback (most recent call last):
  File "/usr/share/wicd/curses/wicd-curses.py", line 1063, in 
main()
  File "/usr/share/wicd/curses/wicd-curses.py", line 995, in main
ui.run_wrapper(run)
  File "/usr/lib/python2.7/dist-packages/urwid/display_common.py", line 757, in run_wrapper
return fn()
  File "/usr/share/wicd/curses/wicd-curses.py", line 88, in wrapper
return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 1003, in run
app = appGUI()
  File "/usr/share/wicd/curses/wicd-curses.py", line 591, in __init__
self.update_status()
  File "/usr/share/wicd/curses/wicd-curses.py", line 88, in wrapper
return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 734, in update_status
self.set_status):
  File "/usr/share/wicd/curses/wicd-curses.py", line 88, in wrapper
return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 161, in check_for_wireless
('$C', ip))
  File "/usr/share/wicd/curses/wicd-curses.py", line 781, in set_status
self.update_ui()
  File "/usr/share/wicd/curses/wicd-curses.py", line 88, in wrapper
return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 930, in update_ui
input_data = ui.get_input_nonblocking()
AttributeError: 'Screen' object has no attribute 'get_input_nonblocking'
--- End Message ---
--- Begin Message ---
Source: wicd
Source-Version: 1.7.2.4-4.2

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

Debian distribution maintenance software
pp.
Salvo 'LtWorf' Tomaselli  (supplier of updated wicd 
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: Sun, 04 Oct 2015 10:32:42 +0200
Source: wicd
Binary: wicd wicd-daemon wicd-gtk wicd-curses wicd-cli python-wicd
Architecture: source all
Version: 1.7.2.4-4.2
Distribution: unstable
Urgency: high
Maintainer: David Paleino 
Changed-By: Salvo 'LtWorf' Tomaselli 
Description:
 python-wicd - wired and wireless network manager - Python module
 wicd   - wired and wireless net

Bug#800693: marked as done (python-urwid: breaks wicd-curses)

[Debian Bug Tracking System]

Your message dated Mon, 05 Oct 2015 07:34:11 +
with message-id 
and subject line Bug#800693: fixed in wicd 1.7.2.4-4.2
has caused the Debian Bug report #800693,
regarding python-urwid: breaks wicd-curses
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.)


-- 
800693: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-urwid
Version: 1.3.0-1+b1
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

the new version breaks wicd-curses.

See attachment.

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

Kernel: Linux 4.2.1a (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python-urwid depends on:
ii  libc6   2.19-22
ii  python  2.7.9-1

python-urwid recommends no packages.

python-urwid suggests no packages.

-- no debconf information
Traceback (most recent call last):
  File "/usr/share/wicd/curses/wicd-curses.py", line 1063, in 
main()
  File "/usr/share/wicd/curses/wicd-curses.py", line 995, in main
ui.run_wrapper(run)
  File "/usr/lib/python2.7/dist-packages/urwid/display_common.py", line 757, in run_wrapper
return fn()
  File "/usr/share/wicd/curses/wicd-curses.py", line 88, in wrapper
return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 1003, in run
app = appGUI()
  File "/usr/share/wicd/curses/wicd-curses.py", line 591, in __init__
self.update_status()
  File "/usr/share/wicd/curses/wicd-curses.py", line 88, in wrapper
return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 734, in update_status
self.set_status):
  File "/usr/share/wicd/curses/wicd-curses.py", line 88, in wrapper
return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 161, in check_for_wireless
('$C', ip))
  File "/usr/share/wicd/curses/wicd-curses.py", line 781, in set_status
self.update_ui()
  File "/usr/share/wicd/curses/wicd-curses.py", line 88, in wrapper
return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 930, in update_ui
input_data = ui.get_input_nonblocking()
AttributeError: 'Screen' object has no attribute 'get_input_nonblocking'
--- End Message ---
--- Begin Message ---
Source: wicd
Source-Version: 1.7.2.4-4.2

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

Debian distribution maintenance software
pp.
Salvo 'LtWorf' Tomaselli  (supplier of updated wicd 
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: Sun, 04 Oct 2015 10:32:42 +0200
Source: wicd
Binary: wicd wicd-daemon wicd-gtk wicd-curses wicd-cli python-wicd
Architecture: source all
Version: 1.7.2.4-4.2
Distribution: unstable
Urgency: high
Maintainer: David Paleino 
Changed-By: Salvo 'LtWorf' Tomaselli 
Description:
 python-wicd - wired and wireless network manager - Python module
 wicd   - wired and wireless network manager - metapackage
 wicd-cli   - wired and wireless network manager - scriptable console client
 wicd-curses - wired and wireless network manager - Curses client
 wicd-daemon - wired and wireless network manager - daemon
 wicd-gtk   - wired and wireless network manager - GTK+ client
Closes: 800693
Changes:
 wicd (1.7.2.4-4.2) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Support newer python-urwid (Closes: #800693)
Checksums-Sha1:
 12cd58c7fa21d0ebd6a7776741f3ad7961dbd0fc 2118 wicd_1.7.2.4-4.2.dsc
 1cacf559469eea6629419b7a0b653e91c40b53ea 24452 wicd_1.7.2.4-4.2.debian.tar.xz
 7ed925635b8125c9b25cba0ffa4c7632908700ed 44816 python-wicd_1.7.2.4-4.2_all.deb
 d0ca5a7a0e64e9c4ca3a370e12336526f874e205 18920 wicd-cli_1.7.2.4-4.2_all.deb
 e5176b4967d2d4b753cbf63ff05d0490926062a5 42120 wicd-curses_1.7.2.4-4.2_all.deb
 7ac

Bug#800879: marked as done (libmetacity-private3a: failes to install if libmetacity-private3 is installed)

[Debian Bug Tracking System]

Your message dated Mon, 05 Oct 2015 07:19:41 +
with message-id 
and subject line Bug#800879: fixed in metacity 1:3.18.0-2
has caused the Debian Bug report #800879,
regarding libmetacity-private3a: failes to install if libmetacity-private3 is 
installed
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.)


-- 
800879: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800879
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmetacity-private3a
Version: 1:3.18.0-1
Severity: serious

Hi,

libmetacity-private3a does not install properly if libmetacity-private3
is already installed. When I retried this it suceeded because apt
decided to remove libmetacity-private3 first, but the first time I
upgraded the package and if is installed manually, it fails.

# dpkg -l libmetacity-private*
...
ii  libmetacity-private31:3.17.2-4

# dpkg -i /var/cache/apt/archives/libmetacity-private3a_1%3a3.18.0-1_amd64.deb 
Selecting previously unselected package libmetacity-private3a.
(Reading database ... 23001 files and directories currently installed.)
Preparing to unpack .../libmetacity-private3a_1%3a3.18.0-1_amd64.deb ...
Unpacking libmetacity-private3a (1:3.18.0-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libmetacity-private3a_1%3a3.18.0-1_amd64.deb 
(--install):
 trying to overwrite '/usr/lib/libmetacity-private.so.3.0.0', which is also in 
package libmetacity-private3 1:3.17.2-4
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libmetacity-private3a_1%3a3.18.0-1_amd64.deb

Thanks,
James

signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: metacity
Source-Version: 1:3.18.0-2

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated metacity 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, 05 Oct 2015 09:55:11 +0300
Source: metacity
Binary: metacity libmetacity-private3a metacity-common libmetacity-dev 
metacity-dbg
Architecture: source
Version: 1:3.18.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Dmitry Shachnev 
Description:
 libmetacity-dev - development files for the Metacity window manager
 libmetacity-private3a - library for the Metacity window manager
 metacity   - lightweight GTK+ window manager
 metacity-common - shared files for the Metacity window manager
 metacity-dbg - debugging symbols for the Metacity window manager
Closes: 800879
Changes:
 metacity (1:3.18.0-2) unstable; urgency=medium
 .
   * Fix version number in libmetacity-private3 Breaks/Replaces
 (closes: #800879).
Checksums-Sha1:
 1aedbec6c15a448191c31350e75dc8d2ff8bc6e2 2690 metacity_3.18.0-2.dsc
 a7ba37c4d9fe01efd41a60d7ed633098509cc0a1 18100 metacity_3.18.0-2.debian.tar.xz
Checksums-Sha256:
 9f35970a2e7586fafaa570ce3e17fc9f956daa1e8245979e8b609646f709eb5c 2690 
metacity_3.18.0-2.dsc
 ee4d7d3987d734f2bb7f06b11dd6bb9c78c835cb3228f207400a05cf27b95eb4 18100 
metacity_3.18.0-2.debian.tar.xz
Files:
 342fa1938e9ba767ae4867688dee33f1 2690 x11 optional metacity_3.18.0-2.dsc
 426a2821c1cfec452aedc26669bfc62e 18100 x11 optional 
metacity_3.18.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWEiAhAAoJENb+cQNj+F3TCBkP/1zEWr+xqrqxDjzD/KEU0gTQ
5j72o/W8FrSrBn2oNfUqyvKQ6k+OiGrZIa8TZordXUQJv1WAh3epQm61NwvQ2/kg
jrPuvNtncx+SWLx66ZiJnZn8B78imiQKQJUWQzq8zgnxzZdINAj2vIdbfaazkxjs
y8x7DrqScU+ctO9x0+KZiTEVfRF+dGLiECf07xSvAwzeEMTA0uCwObhP9/JATYY1
kUw9xcmBb1LxV2xlm2jRAt2YicRCdCZr6KO+lehlGewqSyXNfq9yKxPpU2eckpL+
KJXN97K7GGcOPzuRILfaTyCjLKW3FmrELC0ke+rHj3eKpH6DPqd5dwS6Dj3y8uIS
GNoSH+ktFSyKnLUkrj3ptmxJcK+He3fsAmNmi6ohn5VcWDXLMWJT6s9M/2+uH0eI
jFkZchsJCScPAW4UpsYmJ1aijGyj3OWokqP5ubFOvsFkakDix+gDMhj3xzxPSoSk
XCblvAYKX1l+cLuIK8U3R9e0eicpnhc0sz827D41TwYe+Diu/5q9gWFe7pGFBQmi
z1XB8GUDKk1/KsusWCUHsx+kyetZ14NrzUvCWSiwN8Bd4ZwQNut/01dlEUKaauXf
xHqGEA