Processed: closing 758506

[Debian Bug Tracking System]

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

> close 758506
Bug #758506 [pianobar] Fix for TLS read/handshake error
Marked Bug as done
> thanks
Stopping processing here.

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


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

Bug#778449: marked as done (botch FTBFS on architectures without ocamlopt due to timeout)

[Debian Bug Tracking System]

Your message dated Sun, 15 Feb 2015 07:18:48 +
with message-id 
and subject line Bug#778449: fixed in botch 0.6-1~experimental2
has caused the Debian Bug report #778449,
regarding botch FTBFS on architectures without ocamlopt due to timeout
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.)


-- 
778449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: botch
Version: 0.6-1~experimental1
Severity: serious
Justification: fails to build from source

Hi,

botch FTBFS on arm64, mips, mipsel and s390x because the testsuite run
is killed after a timeout.

This is because these platforms do not provide native ocaml and thus
running the testsuite will take several hours.

cheers, josch
--- End Message ---
--- Begin Message ---
Source: botch
Source-Version: 0.6-1~experimental2

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

Debian distribution maintenance software
pp.
Johannes Schauer  (supplier of updated botch 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, 15 Feb 2015 08:04:35 +0100
Source: botch
Binary: botch botch-doc
Architecture: source amd64 all
Version: 0.6-1~experimental2
Distribution: experimental
Urgency: medium
Maintainer: Johannes Schauer 
Changed-By: Johannes Schauer 
Description:
 botch  - Bootstrapping helper
 botch-doc  - Bootstrapping helper - documentation
Closes: 778449
Changes:
 botch (0.6-1~experimental2) experimental; urgency=medium
 .
   * do not explicitly set `dh_gencontrol -- -Vocaml:Depends` already done by
 dh-ocaml
   * do not run test suite without ocamlopt as that will make the build get
 killed by a timeout (closes: #778449)
   * add dh --with ocaml
   * include /usr/share/ocaml/ocamlvars.mk for OCAML_HAVE_OCAMLOPT
   * Build-Depend on dh-ocaml
   * add lintian overrides for hardening and strip errors
Checksums-Sha1:
 d42b4b5382e28e882059dc36f15d90ba8cef723d 2270 botch_0.6-1~experimental2.dsc
 b3f7019ab0b3af08e296c02955468f250528af33 13764 
botch_0.6-1~experimental2.debian.tar.xz
 7b549f411919bb6227e750fddc94339031952f15 5388932 
botch_0.6-1~experimental2_amd64.deb
 43bdfaad06929d2ee898e1b04c2b18836e803faf 76354 
botch-doc_0.6-1~experimental2_all.deb
Checksums-Sha256:
 2a7f2ebf4e42f6523a74ad9570467652b4599d6a3de908668be2ad760eb0ef29 2270 
botch_0.6-1~experimental2.dsc
 947deaa896bb3b8f688af6ab340286597f58b17b8406514d73e7451912ba7fec 13764 
botch_0.6-1~experimental2.debian.tar.xz
 7fe720a09f10400930371c4650308a09f14d131fea955230ed1ea5085671a177 5388932 
botch_0.6-1~experimental2_amd64.deb
 3f6b54e7cb2d57118d5acc3970b4d88f1214c59a7dc609248bf53a0361580947 76354 
botch-doc_0.6-1~experimental2_all.deb
Files:
 163f0a8a1c86cc2515ea8e6132e744dc 2270 utils optional 
botch_0.6-1~experimental2.dsc
 9d4950653d6db9ff649669ac636cdd60 13764 utils optional 
botch_0.6-1~experimental2.debian.tar.xz
 5bb6b3823aaae639154629ae4787e9bc 5388932 utils optional 
botch_0.6-1~experimental2_amd64.deb
 a43fb75318ea8893fb8eb05f07d6f23f 76354 doc optional 
botch-doc_0.6-1~experimental2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJU4EXYAAoJEPLLpcePvYPhpkkQAInZDEGEVrPHQthmJhEGuE08
Nn0JEipaXn1PSacIxzzLa9bNcnow20UQ1McpznD2FolX49APDnhcShsMjhIbltKf
WUv5TQB3Rkz/wL5Wwmcj0VTIQwWb9htv/DzvRLSRXC7mOlb1wbed9O8hzcLLo0Cr
nLiGafC48LTKJrqnmG73Wep9n7iybsxozLHc76Q8wjjx1AIjjK1HxgoA/l0oeT0Y
DR5MFeDro/eLAQTfySLBetUJRNGyneNN1z8bhcpRKWe8JhesVnBYW1CgV4kcX30V
1d6DjoIQ7Xvkhji0jVSJ1KZt2pLtE4F0Dj1zOwIFOrFJT6Z9B/pABsvM1YPTNMpj
6jhS65jClza3GznT0YoaIBTo4MqrcfJx102E7tMHsFxOTWnxSa9xBXMEUZcjSLhC
M0yL5Xy+QZc61XwFVLIkNBxj9wAgu/E4oUDOx2jRaIaVKFWwEhAJaRroBa0v02/+
c/xM2Cw0w5TTLfczlg+jXiVA0GNMR9SglCw9L6OJyNwGqkANpoA1sKaQlmlXFS/I
4+QU6bNqmTAeZ4wjhwNZV66CDQtpTUDxpSD/p+GGvEDAjkntOnBRhKG3mX6MYQj5
T3XpjjuVGE6+UKSnkY9/JQl90dVzPCiadxYxt9zXicR0EdrdurqNJSz2doKsFcfu
mIHkJgek5QRkmBJ9AFJE
=Xu0C
-END PGP SIGNATURE End Message ---

Bug#778449: botch FTBFS on architectures without ocamlopt due to timeout

[Johannes Schauer]

Package: botch
Version: 0.6-1~experimental1
Severity: serious
Justification: fails to build from source

Hi,

botch FTBFS on arm64, mips, mipsel and s390x because the testsuite run
is killed after a timeout.

This is because these platforms do not provide native ocaml and thus
running the testsuite will take several hours.

cheers, josch


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

Processed: Re: Bug#777583: Incorrect debian/copyright for smartmontools

[Debian Bug Tracking System]

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

> retitle 777583 incorrect debian/copyright for smartmontools violates Debian 
> policy
Bug #777583 [smartmontools] debian/copyright for smartmontools is too 
restrictive
Changed Bug title to 'incorrect debian/copyright for smartmontools violates 
Debian policy' from 'debian/copyright for smartmontools is too restrictive'
> severity 777583 serious
Bug #777583 [smartmontools] incorrect debian/copyright for smartmontools 
violates Debian policy
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.

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


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

Processed: tagging 769351

[Debian Bug Tracking System]

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

> tags 769351 + help
Bug #769351 [src:docker.io] docker.io: statically linked against libc6 without 
a Built-Using: field
Added tag(s) help.
> thanks
Stopping processing here.

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


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

Processed: [/master] Fix permissions on /var/lib/deluged/config/ in deluged.postinst and properly remove all dpkg-statoverrides in deluged.postrm (Closes: #770628).

[Debian Bug Tracking System]

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

> tag 770628 pending
Bug #770628 [deluged] deluged: Starting daemon has no effect
Added tag(s) pending.
> thanks
Stopping processing here.

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


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

Bug#770628: [/master] Fix permissions on /var/lib/deluged/config/ in deluged.postinst and properly remove all dpkg-statoverrides in deluged.postrm (Closes: #770628).

[Andrew Starr-Bochicchio]

tag 770628 pending
thanks

Date: Sat Feb 14 17:35:08 2015 -0500
Author: Andrew Starr-Bochicchio 
Commit ID: 8541e8f2f4aa15296376b6d514b7acd774a1ed98
Commit URL: 
https://anonscm.debian.org/cgit/collab-maint/deluge.git;a=commitdiff;h=8541e8f2f4aa15296376b6d514b7acd774a1ed98
Patch URL: 
https://anonscm.debian.org/cgit/collab-maint/deluge.git;a=commitdiff_plain;h=8541e8f2f4aa15296376b6d514b7acd774a1ed98

Fix permissions on /var/lib/deluged/config/ in deluged.postinst and 
properly remove all dpkg-statoverrides in deluged.postrm (Closes: #770628).

  


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

Processed: Re: Processed: severity of 770628 is normal

[Debian Bug Tracking System]

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

> severity 770628 critical
Bug #770628 [deluged] deluged: Starting daemon has no effect
Severity set to 'critical' from 'normal'
> thanks
Stopping processing here.

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


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

Bug#777518: Bug#777520: patch: regression causes u-boot to FTBFS

[GCS]

Hi Vagrant,

On Mon, Feb 9, 2015 at 4:27 AM, Vagrant Cascadian  wrote:
> Package: patch
> Version: 2.7.4-1
> Severity: serious
> Justification: causes FTBFS in other packages
> Control: affects -1 u-boot
>
> $ dpkg-source -x u-boot_2014.10+dfsg1-2.dsc
> dpkg-source: warning: failed to verify signature on 
> ./u-boot_2014.10+dfsg1-2.dsc
[...]
> dpkg-source: info: restoring quilt backup files for 
> cubox-i/cubox-i-support.diff
> dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E -b -B 
> .pc/cubox-i/cubox-i-support.diff/ --reject-file=- < 
> u-boot-2014.10+dfsg1/debian/patches/cubox-i/cubox-i-support.diff gave error 
> exit status 1
[...]
> I may be able to work around the issue in u-boot by adjusting the
> patch, but this may affect other packages as well and result in FTBFS
> in security updates and binNMUs.
 Still, I think it's u-boot that should fix its Debian patch. The
relevant part of 'cubox-i-support.diff':
-- cut --
diff --git a/tools/logos/solidrun.bmp b/tools/logos/solidrun.bmp
new file mode 100644
index 000..93db1f8
Binary files /dev/null and b/tools/logos/solidrun.bmp differ
-- cut --
 In this case patch is right, as tools/logos/solidrun.bmp is already
exists while the patch file segment states the previous state should
be a non-existent file (/dev/null). Please fix your patch file.

Regards,
Laszlo/GCS


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

Bug#776683: snmpd: SNMPd still tries to query PCI Bus

[gregor herrmann]

Control: tag -1 + unreproducible moreinfo

On Sat, 31 Jan 2015 00:25:00 +0100, Piotr Gorski wrote:

> I have VPS form OVH running Debian Jessie. Few hours ago I've
> installed snmpd to monitor my network interfaces but snmpd can't
> start. When I try starting it with /etc/init.d/snmpd start it says:
> 
> root@vps:~# /etc/init.d/snmpd restart
> [] Restarting SNMP services::pcilib: Cannot open /proc/bus/pci

I've tried this now on a machine without /proc/bus/pci [0], and I get
the same message but ...
 
> After some research I've found that this bug was submitted to
> Debian Bugs as #745956 and #745919. Each bug is closed but error
> remains active making snmpd unusable on systems without PCI bus
> (each VPS server for example).

... unlike these reports, there's only this one error and not two;
and snmpd is running; and I can talk to it. [1]

So it looks like this is a bit ugly and confusing but not a real
problem.


Could you please check again if snmpd is actually not running/working
for your?


Cheers,
gregor


[0]
Raspberry Pi B, admittedly running Raspbian not Debian but snmpd has
the same version

[1]
% snmpwalk -Os -c public -v 1 localhost .1.3.6.1.2.1.1.1
iso.3.6.1.2.1.1.1.0 = STRING: "Linux guinan 3.12.20+ #14 PREEMPT Sun Jun 1 
16:09:41 CEST 2014 armv6l"

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Anouar Brahem: Les ailes du Bourak


signature.asc
Description: Digital Signature

Processed: Re: Bug#776683: snmpd: SNMPd still tries to query PCI Bus

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + unreproducible moreinfo
Bug #776683 [snmpd] snmpd: SNMPd still tries to query PCI Bus
Added tag(s) unreproducible and moreinfo.

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


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

Bug#775691: matplotlib: printf buffer overrun

[Michael Gilbert]

On Sat, Feb 14, 2015 at 12:22 PM, Sandro Tosi  wrote:
> On Sat, Feb 14, 2015 at 5:13 PM, Michael Gilbert  wrote:
>> On Sat, Feb 14, 2015 at 12:03 PM, Sandro Tosi wrote:
 Don't the NMU guidelines [0] say otherwise when there is no maintainer
 activity for more than 7 days?
>>>
>>> like they say "Have you clearly expressed your intention to NMU, at
>>> least in the BTS? It is also a good idea to try to contact the
>>> maintainer by other means (private email, IRC)."
>>
>> devref also says [1] "When someone NMUs your package, this means they
>> want to help you to keep it in good shape. This gives users fixed
>> packages faster."
>>
>> I intended no offense with the NMU, the goal was simply to fix yet
>> another longstanding unfixed jessie security issue [2], but I will try
>> to keep it in mind the next time I look into a matplotlib issue.
>
> you cannot shield yourself with NMU rules, be shown that you didnt
> fully follow the same rules you mentioned and come up with "I mean no
> offence";

I can defend the NMU on merit also, but yes I mean no offense at all
regardless of what the rules and procedures actually are.

> in particular because you also followed it up with relteam
> to get mpl unblocked,

My goal adding to the discussion there was to help make the case for
getting 1.4 accepted into testing.  Now that all of it's RC bugs are
fixed, the release team may be more willing to consider that.

> where you are supposed to get an approval before
> the upload

Nowhere does the release team state that as a requirement for uploads
to unstable [0].  In actuality they have zero jurisdiction over
unstable.

You might be thinking of TPU?

> (and you cannot even imagine how frustrated I am that mpl
> wont make it into Jessie, for just 1 day, because I tried to do things
> by the book)

Is there discussion elsewhere that led to that conclusion?  I don't
see anything in #debian-release.

I respect the frustration that you feel, but I think it may be
misplaced.  My goal is to help you get 1.4 into testing, so maybe we
could work together instead of arguing over semantics?

Best wishes,
Mike

[0] https://release.debian.org/jessie/freeze_policy.html


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

Bug#777518: Changes in patch block fixing u-boot FTBFS

[Vagrant Cascadian]

Control: block 777518 by 777520

Well, mostly block. There may be a workaround by fixing the patch, but
it's unclear weather the workaround has other impacts...

live well,
  vagrant


signature.asc
Description: PGP signature

Processed: Changes in patch block fixing u-boot FTBFS

[Debian Bug Tracking System]

Processing control commands:

> block 777518 by 777520
Bug #777518 [u-boot] u-boot: FTBFS with "patch" 2.7.3-1+ in sid
777518 was not blocked by any bugs.
777518 was not blocking any bugs.
Added blocking bug(s) of 777518: 777520

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


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

Bug#775691: matplotlib: printf buffer overrun

[Sandro Tosi]

On Sat, Feb 14, 2015 at 5:13 PM, Michael Gilbert  wrote:
> On Sat, Feb 14, 2015 at 12:03 PM, Sandro Tosi wrote:
>>> Don't the NMU guidelines [0] say otherwise when there is no maintainer
>>> activity for more than 7 days?
>>
>> like they say "Have you clearly expressed your intention to NMU, at
>> least in the BTS? It is also a good idea to try to contact the
>> maintainer by other means (private email, IRC)."
>
> devref also says [1] "When someone NMUs your package, this means they
> want to help you to keep it in good shape. This gives users fixed
> packages faster."
>
> I intended no offense with the NMU, the goal was simply to fix yet
> another longstanding unfixed jessie security issue [2], but I will try
> to keep it in mind the next time I look into a matplotlib issue.

you cannot shield yourself with NMU rules, be shown that you didnt
fully follow the same rules you mentioned and come up with "I mean no
offence"; in particular because you also followed it up with relteam
to get mpl unblocked, where you are supposed to get an approval before
the upload (and you cannot even imagine how frustrated I am that mpl
wont make it into Jessie, for just 1 day, because I tried to do things
by the book)

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


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

Bug#775691: matplotlib: printf buffer overrun

[Michael Gilbert]

On Sat, Feb 14, 2015 at 12:03 PM, Sandro Tosi wrote:
>> Don't the NMU guidelines [0] say otherwise when there is no maintainer
>> activity for more than 7 days?
>
> like they say "Have you clearly expressed your intention to NMU, at
> least in the BTS? It is also a good idea to try to contact the
> maintainer by other means (private email, IRC)."

devref also says [1] "When someone NMUs your package, this means they
want to help you to keep it in good shape. This gives users fixed
packages faster."

I intended no offense with the NMU, the goal was simply to fix yet
another longstanding unfixed jessie security issue [2], but I will try
to keep it in mind the next time I look into a matplotlib issue.

Best wishes,
Mike

[1] 
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu-maintainer
[2] https://security-tracker.debian.org/tracker/status/release/testing


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

Bug#775691: matplotlib: printf buffer overrun

[Sandro Tosi]

On Sat, Feb 14, 2015 at 5:01 PM, Michael Gilbert  wrote:
> On Sat, Feb 14, 2015 at 4:59 AM, Sandro Tosi wrote:
>> how about using a delayed queue instead of having uploaded straight to 
>> unstable?
>
> Don't the NMU guidelines [0] say otherwise when there is no maintainer
> activity for more than 7 days?

like they say "Have you clearly expressed your intention to NMU, at
least in the BTS? It is also a good idea to try to contact the
maintainer by other means (private email, IRC)."

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


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

Processed: user debian-secur...@lists.debian.org, usertagging 778387, retitle 778387 to cups: CVE-2014-9679 ...

[Debian Bug Tracking System]

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

> user debian-secur...@lists.debian.org
Setting user to debian-secur...@lists.debian.org (was car...@debian.org).
> usertags 778387 + tracked
There were no usertags set.
Usertags are now: tracked.
> retitle 778387 cups: CVE-2014-9679
Bug #778387 [cups] CVE-2014-9679
Changed Bug title to 'cups: CVE-2014-9679' from 'CVE-2014-9679'
> tags 778387 + upstream fixed-upstream
Bug #778387 [cups] cups: CVE-2014-9679
Added tag(s) upstream and fixed-upstream.
> found 778387 1.7.5-10
Bug #778387 [cups] cups: CVE-2014-9679
Marked as found in versions cups/1.7.5-10.
> fixed 778387 2.0.2-1
Bug #778387 [cups] cups: CVE-2014-9679
Marked as fixed in versions cups/2.0.2-1.
> thanks
Stopping processing here.

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


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

Bug#777439: Jessie DI-rc1 amd64 after installation no network interfaces

[Holger Wansing]

Hi,

Heiko Ernst  wrote:
> this is my installer syslog
[...]
> Feb 10 07:52:49 debootstrap: Creating /etc/network/interfaces.

Hmm, at the beginning of the installation, /etc/network/interfaces is
created and apparently works (OP did not complain about network
problems _during_installation_ ).

But at the end of install:

> Feb 10 08:14:44 finish-install: info: Running /usr/lib/finish-
> install.d/55netcfg-copy-config
> Feb 10 08:14:45 netcfg[29439]: INFO: Starting netcfg v.1.127 (built 
> 20150104-2209)
> Feb 10 08:14:45 netcfg[29439]: INFO: Starting netcfg v.1.127 (built 
> 20150104-2209)
> Feb 10 08:14:45 netcfg[29439]: DEBUG: No interface given; clearing 
> /etc/network/interfaces
> Feb 10 08:14:45 netcfg[29439]: DEBUG: Writing informative header
> Feb 10 08:14:45 netcfg[29439]: DEBUG: Success!
> Feb 10 08:14:45 netcfg[29439]: DEBUG: Writing loopback interface
> Feb 10 08:14:45 netcfg[29439]: DEBUG: Success!

/etc/network/interfaces is wiped out!
This shouldn't have happened in a shell-only install ...


Holger

-- 

Created with Sylpheed 3.2.0 under
D E B I A N   L I N U X   7 . 0   W H E E Z Y !

Registered Linux User #311290 - https://linuxcounter.net/



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

Bug#778344: marked as done (python3-softlayer: Uneeded version mismatch between requires and archive keeps SL from working)

[Debian Bug Tracking System]

Your message dated Sat, 14 Feb 2015 17:03:57 +
with message-id 
and subject line Bug#778344: fixed in python-softlayer 3.2.0-2
has caused the Debian Bug report #778344,
regarding python3-softlayer: Uneeded version mismatch between requires and 
archive keeps SL from working
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.)


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

Dear Maintainer,

   * What led up to the situation?

I ran the SL command.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
$ SL

   * What was the outcome of this action?

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pkg_resources.py", line 449, in 
_build_master
ws.require(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources.py", line 745, in require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3/dist-packages/pkg_resources.py", line 644, in resolve
raise VersionConflict(dist, req)
pkg_resources.VersionConflict: (docopt 0.6.2 (/usr/lib/python3/dist-packages), 
Requirement.parse('docopt==0.6.1'))

   * What outcome did you expect instead?

I checked and there aren't any incompatible changes in docopt 0.6.2, so the ==
constraint should be changed to >= so the package will work.
--- End Message ---
--- Begin Message ---
Source: python-softlayer
Source-Version: 3.2.0-2

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated python-softlayer 
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, 13 Feb 2015 16:13:11 -0500
Source: python-softlayer
Binary: python-softlayer python3-softlayer
Architecture: source all
Version: 3.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Scott Kitterman 
Description:
 python-softlayer - Python client for SoftLayer API (Python 2)
 python3-softlayer - Python client for SoftLayer API (Python 3)
Closes: 777337 778279 778344
Changes:
 python-softlayer (3.2.0-2) unstable; urgency=medium
 .
   * Fix docopt version in requires to SL will start (Closes: #778344)
   * Fix python-softlayer postinst/postrm file names to that alternatives works
 and SL is properly provided by python-softlayer (Closes: #778279)
   * Agreed maintainer change to Debian Python Modules Team (Closes: #777337)
   * Add Vcs-* for DPMT repository
Checksums-Sha1:
 42f5ebc3cfc04d36a9543e2a2f31d4a871acdc71 2194 python-softlayer_3.2.0-2.dsc
 35788ef9c6aea03fdb6616a038bae52de369233e 3564 
python-softlayer_3.2.0-2.debian.tar.xz
 a8c5d559c195a22a6f458ef5c6a9ee189a56cb2f 0 python-softlayer_3.2.0-2_all.deb
 0f5dbfaed3f34aef26070278f4dae40ffbd525fd 77932 
python3-softlayer_3.2.0-2_all.deb
Checksums-Sha256:
 7c1a8fe0444ae41f82ddb3b6e6af1fb0cf257784acce1dffc1de48122335672d 2194 
python-softlayer_3.2.0-2.dsc
 e4875b9ab9b474b9702fa8f97970e2287fad82bcb1d17addd8ce5a2c310b5b19 3564 
python-softlayer_3.2.0-2.debian.tar.xz
 d5d734eae9edae2d4c81fd97352189f4be86c37c9215ce47939f0932f7dd2fb6 0 
python-softlayer_3.2.0-2_all.deb
 6e51b495be2080fcaa099cb7eb5b282376376f7344c4a1d5f87f27946249ab92 77932 
python3-softlayer_3.2.0-2_all.deb
Files:
 a6b0d02f96e754fa2111753f84b45e21 2194 python optional 
python-softlayer_3.2.0-2.dsc
 51c7b553c6a7abb50e156ece762f8fd3 3564 python optional 
python-softlayer_3.2.0-2.debian.tar.xz
 9c40dd56637cf5ecaa7e8b33d2a47d09 0 python optional 
python-softlayer_3.2.0-2_all.deb
 6b35477bd3f4716fac85ddcf0b49da6a 77932 python optional 
python3-softlayer_3.2.0-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJU331fAAoJEHjX3vua1Zrx1UUQAK2g+M34IMdtpvvHw81D8OAb
ZTYClBV7CVCWCGlTQ9EeCVuIBTe6jJPRPrvq6QJN96QPFCqiivQ1/PtIsKRVh6c2
N6moe/9hFwITJYjxR+pVUus84L6t/uh+zYDmw67ELsRqdUwtCUvYklv4zYNgzRfY
q9rFJj

Bug#775691: matplotlib: printf buffer overrun

[Michael Gilbert]

On Sat, Feb 14, 2015 at 4:59 AM, Sandro Tosi wrote:
> how about using a delayed queue instead of having uploaded straight to 
> unstable?

Don't the NMU guidelines [0] say otherwise when there is no maintainer
activity for more than 7 days?

Best wishes,
Mike

[0] 
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu-guidelines


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

Processed: found 778387 in 1.5.3-5, bug 778387 is forwarded to https://www.cups.org/str.php?L4551

[Debian Bug Tracking System]

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

> found 778387 1.5.3-5
Bug #778387 [cups] cups: CVE-2014-9679
Marked as found in versions cups/1.5.3-5.
> forwarded 778387 https://www.cups.org/str.php?L4551
Bug #778387 [cups] cups: CVE-2014-9679
Set Bug forwarded-to-address to 'https://www.cups.org/str.php?L4551'.
> thanks
Stopping processing here.

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


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

Bug#778374: Is php5 a good candidate for “minor” release bump? (was: [php-maint] Bug#768509: debian-edu-config: After upgrading a Wheezy main-server to Debian 7.7 the Gosa gui fails to connect to LDAP

[David Prévot]

Hi,

[Bug#778374: php5 5.6.5 fully breaks Horde packages in Debian jessie]
reminded me of this not so old message:

Le 18/11/2014 12:36, Ondřej Surý a écrit :
> On Tue, Nov 18, 2014, at 03:28, David Prévot wrote:
>> [ Adding php maintainers, security team and release team to the loop. ]

>> Le 09/11/2014 17:45, Wolfgang Schweer a écrit :
>>
>> [ About a severe issue that recently popped up. ]
>>
>>> Seems to be that the update from php version 5.4.4 to 5.4.34 (new 
>>> upstream release) caused the problem.
[…]
>> I do understand that safely backporting (security) patches may be hard
>> sometime, but that’s part of what (used to) make the quality and
>> robustness reputation of Debian, and it would be nice to only use such
>> upgrade to new (minor) version as a last resort only. Potentially
>> breaking user scripts on security updates is bad, but risking to break
>> package distributed in stable sounds even worse.
[…]
> Upgrading to the last minor version is not a last resort

Can this be revised, please?

Regards

David



signature.asc
Description: OpenPGP digital signature

Bug#776094: marked as forwarded (dovecot-imapd: corrupts mailbox after trying to retrieve it)

[Debian Bug Tracking System]

Your message dated Sat, 14 Feb 2015 15:23:04 +0100 (CET)
with message-id 
has caused the   report #776094,
regarding dovecot-imapd: corrupts mailbox after trying to retrieve it
to be marked as having been forwarded to the upstream software
author(s) dove...@dovecot.org

(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.)


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

I wrote about this three weeks ago but got no answer. I'm going to
officially "forward" the Debian bug this time, with all the details.

The test case is just 840 bytes long. Please give it a try.

-- Forwarded message --
From: Santiago Vila 
To: sub...@bugs.debian.org
Date: Fri, 23 Jan 2015 22:32:28 +0100 (CET)
Subject: dovecot-imapd: corrupts mailbox after trying to retrieve it

Package: dovecot-imapd
Version: 1:2.2.13-11
Severity: serious

The following mbox folder, when put in $HOME/mail, becomes corrupted after
trying to retrieve it with fetchmail.

The problem may be reproduced by using the same machine as server and client:

* Put "inbox-b" in $HOME/mail

* Put this in $HOME/.fetchmailrc

server localhost proto imap port 143:
 user "someuser"
 pass "thepassword"
  
* Retrieve email using this command line:

fetchmail -a localhost --folder inbox-b -m "true"


Note: By looking at the "true" above it is clear that whatever
fetchmail does with the message is not important at all.


You will see something like this:

12 messages for someuser at localhost (folder inbox-b).
reading message someuser@localhost:1 of 12 (171 header octets) (3 body octets) 
flushed
reading message someuser@localhost:2 of 12 (245 header octets) (3 body octets) 
flushed
reading message someuser@localhost:3 of 12 (245 header octets) (3 body octets) 
flushed
reading message someuser@localhost:4 of 12 (245 header octets) (3 body octets) 
flushed
reading message someuser@localhost:5 of 12 (245 header octets) (3 body octets) 
flushed
reading message someuser@localhost:6 of 12 (171 header octets) (3 body octets) 
flushed
reading message someuser@localhost:7 of 12 (171 header octets) (3 body octets) 
flushed
reading message someuser@localhost:8 of 12 (245 header octets) (3 body octets) 
flushed
reading message someuser@localhost:9 of 12 (245 header octets) (3 body octets) 
flushed
reading message someuser@localhost:10 of 12 (245 header octets) (3 body octets) 
flushed
reading message someuser@localhost:11 of 12 (245 header octets) (3 body octets) 
flushed
reading message someuser@localhost:12 of 12 (273 header octets)fetchmail: 
incorrect header line found - see manpage for bad-header option
 not flushed


And in fact "inbox-b" in the server is now like this:

[...]
>From r...@example.com  Tue Jan 13 10:18:20 2015
rstuvwxyzabcdefghijklmnopqrstuvw...@example.com
To: a...@example.com
Subject: a
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Message-Id: <20150113091737.b5ada5f...@example.com>
Date: Tue, 13 Jan 2015 10:17:25 +0100 (CET)
X-UID: 16035
Status: O

a


Note how the From: line has been truncated from its original state.


I have been suffering from this problem for months. At first I believed
it was some misbehaving procmail/formail recipe I had on the server,
but that's not the case as this example shows.

Thanks.

inbox-b.gz
Description: application/gzip
--- End Message ---

Bug#776094: dovecot-imapd: corrupts mailbox after trying to retrieve it (fwd)

[Santiago Vila]

Hello.

I wrote about this three weeks ago but got no answer. I'm going to
officially "forward" the Debian bug this time, with all the details.

The test case is just 840 bytes long. Please give it a try.

-- Forwarded message --
From: Santiago Vila 
To: sub...@bugs.debian.org
Date: Fri, 23 Jan 2015 22:32:28 +0100 (CET)
Subject: dovecot-imapd: corrupts mailbox after trying to retrieve it

Package: dovecot-imapd
Version: 1:2.2.13-11
Severity: serious

The following mbox folder, when put in $HOME/mail, becomes corrupted after
trying to retrieve it with fetchmail.

The problem may be reproduced by using the same machine as server and client:

* Put "inbox-b" in $HOME/mail

* Put this in $HOME/.fetchmailrc

server localhost proto imap port 143:
 user "someuser"
 pass "thepassword"
  
* Retrieve email using this command line:

fetchmail -a localhost --folder inbox-b -m "true"


Note: By looking at the "true" above it is clear that whatever
fetchmail does with the message is not important at all.


You will see something like this:

12 messages for someuser at localhost (folder inbox-b).
reading message someuser@localhost:1 of 12 (171 header octets) (3 body octets) 
flushed
reading message someuser@localhost:2 of 12 (245 header octets) (3 body octets) 
flushed
reading message someuser@localhost:3 of 12 (245 header octets) (3 body octets) 
flushed
reading message someuser@localhost:4 of 12 (245 header octets) (3 body octets) 
flushed
reading message someuser@localhost:5 of 12 (245 header octets) (3 body octets) 
flushed
reading message someuser@localhost:6 of 12 (171 header octets) (3 body octets) 
flushed
reading message someuser@localhost:7 of 12 (171 header octets) (3 body octets) 
flushed
reading message someuser@localhost:8 of 12 (245 header octets) (3 body octets) 
flushed
reading message someuser@localhost:9 of 12 (245 header octets) (3 body octets) 
flushed
reading message someuser@localhost:10 of 12 (245 header octets) (3 body octets) 
flushed
reading message someuser@localhost:11 of 12 (245 header octets) (3 body octets) 
flushed
reading message someuser@localhost:12 of 12 (273 header octets)fetchmail: 
incorrect header line found - see manpage for bad-header option
 not flushed


And in fact "inbox-b" in the server is now like this:

[...]
>From r...@example.com  Tue Jan 13 10:18:20 2015
rstuvwxyzabcdefghijklmnopqrstuvw...@example.com
To: a...@example.com
Subject: a
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Message-Id: <20150113091737.b5ada5f...@example.com>
Date: Tue, 13 Jan 2015 10:17:25 +0100 (CET)
X-UID: 16035
Status: O

a


Note how the From: line has been truncated from its original state.


I have been suffering from this problem for months. At first I believed
it was some misbehaving procmail/formail recipe I had on the server,
but that's not the case as this example shows.

Thanks.

inbox-b.gz
Description: application/gzip

Bug#778387: CVE-2014-9679

[Moritz Muehlenhoff]

Package: cups
Severity: grave
Tags: security

This was assigned CVE-2014-9679 and is fixed in experimental
already: https://www.cups.org/str.php?L4551

Cheers,
Moritz


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

Bug#774437: marked as done (ovirt-guest-agent: fails in preinst due to hardcoded uid and gid values)

[Debian Bug Tracking System]

Your message dated Sat, 14 Feb 2015 13:04:27 +
with message-id 
and subject line Bug#774437: fixed in ovirt-guest-agent 1.0.10.2.dfsg-2
has caused the Debian Bug report #774437,
regarding ovirt-guest-agent: fails in preinst due to hardcoded uid and gid 
values
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.)


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

Package: ovirt-guest-agent
Version: 1.0.10.2.dfsg-1
Severity: serious

It hardcodes them as 175. The uid was not taken, but the gid was so the 
package installation failed. Funnily enough, I was trying to fix 
#767028 at the time.


Best regards,
--
Cameron Norman
--- End Message ---
--- Begin Message ---
Source: ovirt-guest-agent
Source-Version: 1.0.10.2.dfsg-2

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated 
ovirt-guest-agent 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: Sat, 14 Feb 2015 08:52:29 +
Source: ovirt-guest-agent
Binary: ovirt-guest-agent
Architecture: source all
Version: 1.0.10.2.dfsg-2
Distribution: unstable
Urgency: low
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 ovirt-guest-agent - daemon that resides within guest virtual machines
Closes: 767028 774437
Changes:
 ovirt-guest-agent (1.0.10.2.dfsg-2) unstable; urgency=low
 .
   * Rework useradd logic not to fail if gid 175 already present
 (closes: #774437).
   * Fix self-test failures with unreadable /proc .
   * Add dh-python to Build-Depends to prevent possible FTBFS.
 .
   [ Cameron Norman  ]
   * Do not use udevadm in chroot (closes: #767028).
Checksums-Sha1:
 4660bb2655ec3a6bc82ba98b242c6f9537878027 1948 
ovirt-guest-agent_1.0.10.2.dfsg-2.dsc
 d1656fb82c222156f37e7392afd41f1c237094ba 5604 
ovirt-guest-agent_1.0.10.2.dfsg-2.debian.tar.xz
 9d2d4f507413909378f48f9523014efc3225aa47 40430 
ovirt-guest-agent_1.0.10.2.dfsg-2_all.deb
Checksums-Sha256:
 0c115b0ac5b2b142bdeea6e18503246a5e3344640f6578b7adb468421a2fb180 1948 
ovirt-guest-agent_1.0.10.2.dfsg-2.dsc
 d13149668ebaafcc6c274a7c60b9b1ae8379bf3b2b905e3e3cad6ab6ba27b0c7 5604 
ovirt-guest-agent_1.0.10.2.dfsg-2.debian.tar.xz
 4b39227755462c1b622811ebf0b64d24338909c4a9ae855f17db32e0fa8fcc75 40430 
ovirt-guest-agent_1.0.10.2.dfsg-2_all.deb
Files:
 71ff10e103f2b92b50e7f77a776133b9 1948 utils extra 
ovirt-guest-agent_1.0.10.2.dfsg-2.dsc
 f1df48ed936cf9d5dd1d058f8e59b0ad 5604 utils extra 
ovirt-guest-agent_1.0.10.2.dfsg-2.debian.tar.xz
 e4b739f01926a4b9246847d1c65696c3 40430 utils extra 
ovirt-guest-agent_1.0.10.2.dfsg-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJU30bFAAoJENzjEOeGTMi/doYP/j3ACcGJERA8dR6dNdVJp2j+
Qq6WC6nErPEwFlcNDSZvSEc7/FIo74vVza8RvTT4uFW+D5QsuI34b0D5ckcpSsQC
cILAx4mReWBjwPHAuzifLWYu9Hl/aKYe+dQAMMAQmXs+d3RRuK6t6bxrqdLj6Z4/
cSV5wk834HCVmpKHqHtpBEzvikMrMM0z+ntl8U13kxJ+FFL5n1LkQLihpcjlXWNj
naOi5o/R7ZbkJkwgXvwRKLuVC1CKcAuWxzox2s5u3oPnTNvWLeQLwHsBTGAeCuTY
UyhpL7eU7YI+GZYR/mvt2h7JgbzfWOA2RQsJVN4zINe6uFgraaJeuOKjK0/A8/bV
y5H6Bojnqefc5jbRM15VEMXS+Dvkx+o/UTImlSuSphinuh+8z/txcLzIwmRx+H68
ArEvpAs2GU1qLUQCBXdbZqKCtj4qkhhmREitUAg7IBX3z3bO2qXBBd1L9R9SdLNv
KvCPetxKzZKr3xeuVAKz/r7L2YLkr72Mg4KGdjoABxsNQtJXYBPG+RJbBBERaJXT
xHCF26ecaf9w0xhNgZyE8IiXrfbyq9umRYsUKkKyolhIEMDUMhWOzVn3moucqknr
IdIVySRFrGvn+/1OoSSWamnw8eq/aLwvxHf8hRbd31zIppUCLNm1D43iCSNCvP9h
zeUy4Nq6Xr0eQW+EVlpY
=+jA3
-END PGP SIGNATURE End Message ---

Bug#767028: marked as done (ovirt-guest-agent: doesn't work on hosts)

[Debian Bug Tracking System]

Your message dated Sat, 14 Feb 2015 13:04:27 +
with message-id 
and subject line Bug#767028: fixed in ovirt-guest-agent 1.0.10.2.dfsg-2
has caused the Debian Bug report #767028,
regarding ovirt-guest-agent: doesn't work on hosts
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.)


-- 
767028: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ovirt-guest-agent
Version: 1.0.10.1.dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi, 

during a test with piuparts I noticed your package failed to install. As per 
definition of the release team this makes the package too buggy for a 
release, thus the severity.

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

  The following NEW packages will be installed:
ovirt-guest-agent
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 39.0 kB of archives.
  After this operation, 92.2 kB of additional disk space will be used.
  Get:1 http://mirror.bm.debian.org/debian/ jessie/main ovirt-guest-agent all 
1.0.10.1.dfsg-1 [39.0 kB]
  debconf: delaying package configuration, since apt-utils is not installed
  Fetched 39.0 kB in 0s (417 kB/s)
  Selecting previously unselected package ovirt-guest-agent.
  (Reading database ... 10034 files and directories currently installed.)
  Preparing to unpack .../ovirt-guest-agent_1.0.10.1.dfsg-1_all.deb ...
  Unpacking ovirt-guest-agent (1.0.10.1.dfsg-1) ...
  Setting up ovirt-guest-agent (1.0.10.1.dfsg-1) ...
  dpkg: error processing package ovirt-guest-agent (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   ovirt-guest-agent
  E: Sub-process /usr/bin/dpkg returned an error code (1)

I'm aware that this looks pretty much similar to #754789 which was fixed in 
1.0.10.1.dfsg-1, but now the "/var/lib/dpkg/info/ovirt-guest-agent.postinst: 
line 4: udevadm: command not found" is gone / not visible...


cheers,
Holger
Start: 2014-10-17 20:22:43 UTC

Package: ovirt-guest-agent
Version: 1.0.10.1.dfsg-1
Installed-Size: 90
Maintainer: Laszlo Boszormenyi (GCS) 
Architecture: all
Depends: python:any (>= 2.6.6-7~), udev, python-apt, python-dbus, python-ethtool, usermode, qemu-guest-agent
Description: oVirt Guest Agent
Homepage: http://www.ovirt.org/Ovirt_guest_agent
Description-md5: 2737be45d3cf8eabb6d3a39e2d1df583
Section: utils
Priority: extra
Filename: pool/main/o/ovirt-guest-agent/ovirt-guest-agent_1.0.10.1.dfsg-1_all.deb
Size: 38950
MD5sum: 43fb923a921b0e03625cc32fc34476ea
SHA1: e91478c08a2efb71962451e1d81054857e251c30
SHA256: 9082bc2d770d356eea61f9e98ce12c07cca73eadff32fa7ee92c2fac451a0f3f

Executing: sudo env PYTHONPATH=/srv/piuparts.debian.org/lib/python2.7/dist-packages timeout -s INT -k 5m 35m /srv/piuparts.debian.org/sbin/piuparts --skip-logrotatefiles-test --warn-on-others --scriptsdir /etc/piuparts/scripts --no-eatmydata --allow-database --warn-on-leftovers-after-purge --mirror 'http://mirror.bm.debian.org/debian/ main' --tmpdir /srv/piuparts.debian.org/tmp --arch amd64 -b /srv/piuparts.debian.org/slave/basetgz/jessie_amd64.tar.gz -d jessie --no-upgrade-test --apt ovirt-guest-agent=1.0.10.1.dfsg-1
0m0.0s INFO: --
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of this logfile.
0m0.0s INFO: FAQ available at https://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: The FAQ also explains how to contact us in case you think piuparts is wrong.
0m0.0s INFO: --
0m0.0s INFO: piuparts version 0.59 starting up.
0m0.0s INFO: Command line arguments: /srv/piuparts.debian.org/sbin/piuparts --skip-logrotatefiles-test --warn-on-others --scriptsdir /etc/piuparts/scripts --no-eatmydata --allow-database --warn-on-leftovers-after-purge --mirror 'http://mirror.bm.debian.org/debian/ main' --tmpdir /srv/piuparts.debian.org/tmp --arch amd64 -b /srv/piuparts.debian.org/slave/basetgz/jessie_amd64.tar.gz -d jessie --no-upgrade-test --apt ovirt-guest-agent=1.0.10.1.dfsg-1
0m0.0s INFO: Running on: Linux piu-slave-bm-a 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64
0m0.0s DEBUG: Created temporary directory /srv/piuparts.debian.org/tmp/tmp2izDRR
0m0.0s DEBUG: Unpacking /srv/piuparts.debian.org/slave/basetgz/jessie_amd64.tar.gz into /srv/piuparts.debian.org/tmp/tmp2izDRR
0m0.0s DEBUG: Starting command: ['tar', '-C', '/srv/piuparts.debian.org/tmp/tmp2izDRR', '-zxf', 

Bug#778343: marked as done (xymon: Severe memory leaks in xymond)

[Debian Bug Tracking System]

Your message dated Sat, 14 Feb 2015 12:33:52 +
with message-id 
and subject line Bug#778343: fixed in xymon 4.3.17-6
has caused the Debian Bug report #778343,
regarding xymon: Severe memory leaks in xymond
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.)


-- 
778343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xymon
Version: 4.3.17-5
Severity: serious
Tags: patch pending fixed-upstream

Before christmas, I've setup a new Jessie installation with Xymon. Since
two or three weeks ago that installation is fed with all the monitoring
data our current and Wheezy based production monitoring server gets.
After approximately one week without restart, the xymond process on the
Jessie installation grew to 15 GB of memory usage.

Valgrind showed chunks of ca. 9 MB and 3.5 MB getting lost. Xymons
typical activity interval is 5 minutes. (The 9 MB sound realistic:
Summing up 9 MB every 5 minutes for a week would get 17.7 GB.)

How quick the memory usage grows seems to depend on the installation
and/or usage, too. I also have a 4.3.17-2 backport running on Wheezy for
many months, and we only had a single case where it ran long enough (3
months without restart) so that the memory usage grew in areas where we
noticed something. But that installation has way fewer hosts to monitor
and hence fewer messages to handle (2 vs 28 incoming messages per
second), so the memory leak didn't become that obvious as it is now.

And the memory leak has been fixed upstream with their recent 4.3.18
release (03-Feb-2015). The 4.3.18 upstream changelog contains the
following changelog entry:

  - xymond: Fix memory leak

With cherry-picking the following two patches from upstream's 4.3.18
branch in SVN, the memory usage of the same installation stayed around
256 MB of RAM usage (fluctuating between 247 MB and 263 MB) after three
hours despite it grew to over 300 MB after less than 30 minutes before.

And Valgrind seems happy since then, too.

Description:Fix memory leak in acknowledge handling.
 Cherry-picked from the 4.3.18 upstream release.
Origin: http://sourceforge.net/p/xymon/code/7488/
Applied-Upstream: http://sourceforge.net/p/xymon/code/7488/
Reviewed-by: Axel Beckert 

Index: xymon/xymond/xymond.c
===
--- xymon.orig/xymond/xymond.c  2015-02-13 15:38:17.0 +0100
+++ xymon/xymond/xymond.c   2015-02-13 15:40:05.0 +0100
@@ -2365,6 +2365,8 @@
if (zombie->dismsg) xfree(zombie->dismsg);
if (zombie->ackmsg) xfree(zombie->ackmsg);
if (zombie->grouplist) xfree(zombie->grouplist);
+   if (zombie->lastchange) xfree(zombie->lastchange);
+   if (zombie->testflags) xfree(zombie->testflags);
flush_acklist(zombie, 1);
xfree(zombie);
dbgprintf("<- free_log_t\n");

Description: Set an initial size for the xymondlog output
 Cherry-picked from the 4.3.18 upstream release.
 .
 Original commit message: "xymond: Set an initial size for the
 xymondlog output, to avoid realloc'ing the buffer too much. Fix a
 valgrind complaint. JC Cleaver"
 .
 Despite the harmless sounding commit message, this seems to fix a
 severe memory leak. Without this patch, valgrind reported the loss of
 about 12 MB every five minutes on a bigger installation.
Origin: http://sourceforge.net/p/xymon/code/7489/
Applied-Upstream: http://sourceforge.net/p/xymon/code/7489/

Index: xymon/xymond/xymond.c
===
--- xymon.orig/xymond/xymond.c  2015-02-13 16:50:42.0 +0100
+++ xymon/xymond/xymond.c   2015-02-13 17:21:42.0 +0100
@@ -3679,12 +3679,13 @@
}
 
xfree(msg->buf);
-   logdata = generate_outbuf(NULL, logfields, h, log, 
acklevel);
+   logdata = newstrbuffer(20480);
+   logdata = generate_outbuf(&logdata, logfields, h, log, 
acklevel);
addtobuffer(logdata, msg_data(log->message, 0));
 
msg->doingwhat = RESPONDING;
msg->buflen = STRBUFLEN(logdata);
-   msg->bufp = grabstrbuffer(logdata);
+   msg->bufp = msg->buf = grabstrbuffer(logdata);
}
 
clear_filter(logfilter);

I intend to upload 4.3.17-6 with these two patches, the added CVE-ID for
the previous upload and one translation update. I will initially upload
it to the DELAYED queue and will

Processed: your mail

[Debian Bug Tracking System]

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

> severity 777689 important
Bug #777689 [libanthy0] anthy: missing EOL in records file causes infinite loop 
that prevents GTK programs from starting
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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


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

Processed: iceweasel: cannot reproduce

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #776747 [iceweasel] iceweasel 35 crashes frequently
Severity set to 'important' from 'grave'

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


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

Bug#777540: policy violation in libhtp

[Hilko Bengen]

* Ralph J.Mayer:

> Should I also file a bug against lintian to remove the "upstream
> soname version is not correct" override?

No, the wrong override that hides the problem from Lintian is part of
the libhtp source package itself:

,[ libhtp-0.5.15/debian/overrides/libhtp1 ]
| # upstream soname version is not correct ...
| libhtp1: package-name-doesnt-match-sonames libhtp-0.5.15-1
`

Cheers,
-Hilko


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

Bug#776747: iceweasel: cannot reproduce

[Claudio Moretti]

Control: severity -1 important

Hi,

I've installed Iceweasel 35.0.1-1 this morning, and so far I didn't get a 
single crash.
I believe the severity of this should be downgraded to, at least 
"important" (as it doesn't affect everyone).

Please be aware that this bug shows up from apt-listbugs when upgrading 
Iceweasel (hence my request of lowering the severity).

Thanks,

Claudio
Control: severity -1 importantHi,I've installed Iceweasel 35.0.1-1 this morning, and so far I didn't get a single crash.I believe the severity of this should be downgraded to, at least "important" (as it doesn't affect everyone).Please be aware that this bug shows up from apt-listbugs when upgrading Iceweasel (hence my request of lowering the severity).Thanks,Claudio


signature.asc
Description: Digital signature

Processed: Re: Bug#777583: Incorrect debian/copyright for smartmontools

[Debian Bug Tracking System]

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

> retitle 777583 debian/copyright for smartmontools is too restrictive
Bug #777583 [smartmontools] incorrect debian/copyright for smartmontools 
violates Debian policy
Changed Bug title to 'debian/copyright for smartmontools is too restrictive' 
from 'incorrect debian/copyright for smartmontools violates Debian policy'
> severity 777583 wishlist
Bug #777583 [smartmontools] debian/copyright for smartmontools is too 
restrictive
Severity set to 'wishlist' from 'serious'
> thanks
Stopping processing here.

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


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

Bug#778374: [pkg-horde] Bug#778374: php5 5.6.5 fully breaks Horde packages in Debian jessie

[Mike Gabriel]

Hi,



The attached patch against php5 allows Horde to start again.

With that patched php5 version on my Debian jessie system, IMP   
(Horde's mail client) seems to work ok again. However, I also see   
regressions in Kronolith (calenadaring tool), Turba (address book)  
and  Nag (task planner). I will investigate this further later today.


Just a short update notice. After having given my Horde instance some  
time to "recover" (invalidate cashes and such stuff), the complete  
Horde system is back in play and works nicely with my patch 5.6.5.


Please dearly consider reverting my sent-in patch in the current php5  
version in jessie/unstable.


Thanks,
Mike
--

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

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

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


pgpJfgzrTsS3C.pgp
Description: Digitale PGP-Signatur

Bug#775691: marked as done (matplotlib: CVE-2013-1424: printf buffer overrun)

[Debian Bug Tracking System]

Your message dated Sat, 14 Feb 2015 11:19:07 +
with message-id 
and subject line Bug#775691: fixed in matplotlib 1.4.3~rc1-1
has caused the Debian Bug report #775691,
regarding matplotlib: CVE-2013-1424: printf buffer overrun
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.)


-- 
775691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775691
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:matplotlib
version: 0.99.3-1
severity: serious
tag: security, patch

Matt Giuca reported a matplotlib buffer overrun to the private
security team request tracker in 2013, which ended up falling through
the cracks at the time.  See below for the original message and a
proposed patch attached.

On Wed, Jan 23, 2013 at 11:21:14PM +, Matt Giuca via RT wrote:
> The bug is in 
> src/mplutils.cpp.
> The Printf::Printf constructor accepts an arbitrary format string and
> values, and dumps it into a 1024-byte buffer with vsprintf. This is
> obviously not safe, as the user can simply supply enough bytes to overflow
> the 1024-byte buffer.
>
> The bug can be exploited from Python code, through a number of
> Python-exposed functions that call Printf. The most obvious entry-point I
> can find is ft2font.FT2Font constructor:
>
> >>> from matplotlib import ft2font
> >>> ft2font.FT2Font('x' * 2048)
> *** glibc detected *** python: free(): invalid next size (normal):
> 0x029f1480 ***
>
> There are several other Python functions that call Printf with
> user-supplied data, but this is the cleanest one.
>
> As for what this can be used for: I'm not an expert in exploiting
> vulnerabilities, but it allows any user who can supply either Python code
> to be executed, or certain specific strings such as the name of a font, to
> write an arbitrary number of bytes to a location on the heap, and I know
> that that can potentially be used to compromise a machine.
diff --git a/lib/matplotlib/__init__.py b/lib/matplotlib/__init__.py
index c7e3141..37feb20 100644
--- a/lib/matplotlib/__init__.py
+++ b/lib/matplotlib/__init__.py
@@ -1114,6 +1114,7 @@ default_test_modules = [
 'matplotlib.tests.test_lines',
 'matplotlib.tests.test_mathtext',
 'matplotlib.tests.test_mlab',
+'matplotlib.tests.test_mplutils',
 'matplotlib.tests.test_patches',
 'matplotlib.tests.test_pickle',
 'matplotlib.tests.test_rcparams',
diff --git a/lib/matplotlib/tests/test_mplutils.py b/lib/matplotlib/tests/test_mplutils.py
new file mode 100644
index 000..e37e41c
--- /dev/null
+++ b/lib/matplotlib/tests/test_mplutils.py
@@ -0,0 +1,12 @@
+from __future__ import print_function
+from nose.tools import assert_raises
+from matplotlib import ft2font
+from matplotlib.testing.decorators import knownfailureif
+import sys
+
+def test_printf_buffer():
+"""Tests Printf for buffer overrun."""
+# Use ft2font.FT2Font, which indirectly calls the Printf function in
+# mplutils.cpp.
+# Expect a RuntimeError, since the font is not found.
+assert_raises(RuntimeError, ft2font.FT2Font, 'x' * 2048)
diff --git a/src/mplutils.cpp b/src/mplutils.cpp
index febb97a..af3a2f3 100644
--- a/src/mplutils.cpp
+++ b/src/mplutils.cpp
@@ -18,7 +18,10 @@ Printf::Printf(const char *fmt, ...)
 {
 va_list ap;
 va_start(ap, fmt);
-vsprintf(buffer, fmt, ap);
+vsnprintf(buffer, 1024, fmt, ap);
+// Null-terminate the string. Non-standard C implementations (e.g.,
+// Microsoft Visual C++) do not do this automatically.
+buffer[1023] = '\0';
 va_end(ap);  // look ma - I rememberd it this time
 }
 
--- End Message ---
--- Begin Message ---
Source: matplotlib
Source-Version: 1.4.3~rc1-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 775...@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: Sat, 14 Feb 2015 00:08:01 +
Source: matplotlib
Binary: python-matplotlib python

Processed: policy violation in libhtp

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 policy violation - SONAME mismatch
Bug #777540 [libhtp1] libhtp1: possible library policy violation
Changed Bug title to 'policy violation - SONAME mismatch' from 'libhtp1: 
possible library policy violation'

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


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

Bug#777540: policy violation in libhtp

[Ralph J.Mayer]

Control: retitle -1 policy violation - SONAME mismatch

Hi Hlko,

thx for confirming.

Should I also file a bug against lintian to remove the "upstream soname version 
is not correct"
 override?


Best regards
rm

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

Bug#778373: marked as done (botch FTBFS on 32 bit architectures)

[Debian Bug Tracking System]

Your message dated Sat, 14 Feb 2015 10:19:53 +
with message-id 
and subject line Bug#778373: fixed in botch 0.6-1~experimental1
has caused the Debian Bug report #778373,
regarding botch FTBFS on 32 bit architectures
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.)


-- 
778373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: botch
Version: 0.5-1~experimental3
Severity: serious
Justification: fails to build from source

Hi,

botch currently FTBFS on 32 bit arches while succeeding on 64 bit
arches.

The problem is, that the ocaml parts assign unique vertex/edge ids based
on their order in the input GraphML but networkx will store GraphML
nodes and edges in random order.

To combat the random-ness, PYTHONHASHSEED=0 has been set but that only
leads to the same hash within 32 bit and 64 bit arches but not to the
same hash for both together.

See http://bugs.python.org/issue22621 for an explanation why this will
not be fixed in Python.

So instead, the ocaml code should be made to work irrespective of the
order of the nodes and edges in the input XML.

cheers, josch
--- End Message ---
--- Begin Message ---
Source: botch
Source-Version: 0.6-1~experimental1

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

Debian distribution maintenance software
pp.
Johannes Schauer  (supplier of updated botch 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: Sat, 14 Feb 2015 10:56:50 +0100
Source: botch
Binary: botch botch-doc
Architecture: source amd64 all
Version: 0.6-1~experimental1
Distribution: experimental
Urgency: medium
Maintainer: Johannes Schauer 
Changed-By: Johannes Schauer 
Description:
 botch  - Bootstrapping helper
 botch-doc  - Bootstrapping helper - documentation
Closes: 778373
Changes:
 botch (0.6-1~experimental1) experimental; urgency=medium
 .
   * New upstream release (closes: #778373)
Checksums-Sha1:
 78e6b0ebc6d6f7741fbe10ba6ccfb50d210b73b1 2260 botch_0.6-1~experimental1.dsc
 92b9494a72251a3e0446c62065f7ab0b59aa4fc5 28976304 botch_0.6.orig.tar.xz
 b5416afcf8d59abf826249870fe39d04f1d5 13600 
botch_0.6-1~experimental1.debian.tar.xz
 8e23becfb8d5b80211b79d62d327214f46c98596 5416764 
botch_0.6-1~experimental1_amd64.deb
 10be2b1969d87fa579f6cefebf54e32346c350b2 76124 
botch-doc_0.6-1~experimental1_all.deb
Checksums-Sha256:
 1f7d341752fb3cf5746fe6dbecd36ad891b4d31f339c960fc1ac1ad143f44554 2260 
botch_0.6-1~experimental1.dsc
 fe09fd1c684ea92ba1894cd1e35292bcd599ae5974f892895fdf8a1b26cc155e 28976304 
botch_0.6.orig.tar.xz
 5e3d5ba29cbc69227576cf72321eca5789d5acc21fcf3ae52b5afcbd679a0f77 13600 
botch_0.6-1~experimental1.debian.tar.xz
 8276671bda1ba13f30483d1398bd55f8e68a1837e716d0a655bd03d89c067250 5416764 
botch_0.6-1~experimental1_amd64.deb
 d287204eeecb5e8bd42040e80c60a1cca9a6fe2b62199c0c02b008481aa1b5a2 76124 
botch-doc_0.6-1~experimental1_all.deb
Files:
 d892327f7fd6152b5011024b9635bed1 2260 utils optional 
botch_0.6-1~experimental1.dsc
 7f0187fabb4f6b6975b753000e849bb5 28976304 utils optional botch_0.6.orig.tar.xz
 f199e33d2072b742626adc8cb880b17a 13600 utils optional 
botch_0.6-1~experimental1.debian.tar.xz
 93d50378ac5e676b0db688ac01d4e6dc 5416764 utils optional 
botch_0.6-1~experimental1_amd64.deb
 3d05cd994015bd68fa368c0f0f65e363 76124 doc optional 
botch-doc_0.6-1~experimental1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJU3xyeAAoJEPLLpcePvYPhftMP/Rtc/Oi6U64lzvmrGTtqngNT
1QhT76i66ONYw+S01/ZMjE4BKd144AknyRHDqSgZRz26OhqIKcRH3eG2Hurz9UtU
DD/KG3aPMhfblPIt6UoA6BEw8fsaDQ+k6ZUN8Kvt8q5adnhDUE5SpTDPYBmlpkeY
szGOqokPA+5uHDCQ79HxaBkOMuvaWHvaiWTIvF3GJTYpg8na5Y834rWyzw+OvH7E
YEcJG6WVcEBOMzNqKP6m6yJK8FipLkUfcB4fFngdmCktnUvbcuIAz1lYTpfHvGPP
AAD/rBpaziESRzB0WRuym9k7Rk7gZ83BmBKSNWwh5uRfKV4fFdJdjszdUQcnVTXt
LBHgyclL30ZME5LAQfjsqKxy4KLktbsJJ1aWjIMwL8EOkMBlcHVtiC9T2T5kz+Q1
Vhieo6VTqCyLEW07FXSZQTk1jP03jTVSP5Xzw+gm1ua+t31y2YNhlvrJt4JWItQC
IlWoVZ7mqW0nJpkVBYIv9b7VKC/MSh+QUMXL/sqIFqSR/e99jnzYR4W761e3MuGn
bfo7LlMmdKuNArzNSUOgCOwGRN2PZ

Bug#775691: matplotlib: printf buffer overrun

[Sandro Tosi]

how about using a delayed queue instead of having uploaded straight to unstable?

On Sat, Feb 14, 2015 at 1:35 AM, Michael Gilbert  wrote:
> Hi,
>
> I've uploaded an nmu fixing this issue.  Please see attached patch.
>
> Best wishes,
> Mike



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


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

Bug#778375: apt-transport-https: segfaults

[Kurt Roeckx]

Package: apt-transport-https
Version: 1.0.9.6
Severity: serious

Hi,

When I try to download something over https apt just segfaults:
https[7809]: segfault at 69 ip 7f523b8cbb03 sp 7fff432589e0 error 4 in 
https[7f523b8c+12000]


Kurt


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

Processed: Re: Bug#778374: php5 5.6.5 fully breaks Horde packages in Debian jessie

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #778374 [php5-common] php5 5.6.5 fully breaks Horde packages in Debian 
jessie
Added tag(s) patch.

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


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

Bug#778374: php5 5.6.5 fully breaks Horde packages in Debian jessie

[Mike Gabriel]

Control: tag -1 patch

Hi,

On  Sa 14 Feb 2015 08:45:19 UTC, Mike Gabriel wrote:


Package: php5-common
Version: 5.6.5+dfsg-1
Severity: grave
Tags: upstream


Dear PHP5 maintainers,

the latest migration of php5 to Debian jessie unfortunately broke the
complete Horde5 software that is in Debian jessie.

The latest php5 upstream branches (5.5 and 5.6) introduced a severe
regression as discussed at [1].

I am currently test-building a PHP 5.6.5+dfsg-1.1 with that patch
reverted. I will get back to you soon, if that fixes the observed
issue.

Breaking Horde5 means: no communication via IMAP with an MDA (IMAP
server) is possible anymore.

light+love,
Mike


[1] https://bugs.php.net/bug.php?id=68948


The attached patch against php5 allows Horde to start again.

With that patched php5 version on my Debian jessie system, IMP  
(Horde's mail client) seems to work ok again. However, I also see  
regressions in Kronolith (calenadaring tool), Turba (address book) and  
Nag (task planner). I will investigate this further later today.


Mike
--

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

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

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
reverted:
--- a/ext/standard/tests/file/bug68532.phpt
+++ /dev/null
@@ -1,25 +0,0 @@
---TEST--
-Bug #68532: convert.base64-encode omits padding bytes
---FILE--
-
---CLEAN--
-
---EXPECT--
-memoryStream = dGVzdA==
-fileStream = dGVzdA==
--- a/ext/standard/tests/file/stream_rfc2397_007.phpt
+++ b/ext/standard/tests/file/stream_rfc2397_007.phpt
@@ -95,7 +95,6 @@
 bool(false)
 ===GETC===
 string(1) "5"
-bool(false)
 int(6)
 bool(true)
 ===REWIND===
--- a/main/streams/memory.c
+++ b/main/streams/memory.c
@@ -87,19 +87,15 @@
 	php_stream_memory_data *ms = (php_stream_memory_data*)stream->abstract;
 	assert(ms != NULL);
 
-	if (ms->fpos == ms->fsize) {
+	if (ms->fpos + count >= ms->fsize) {
+		count = ms->fsize - ms->fpos;
 		stream->eof = 1;
-		count = 0;
-	} else {
-		if (ms->fpos + count >= ms->fsize) {
-			count = ms->fsize - ms->fpos;
-		}
-		if (count) {
-			assert(ms->data!= NULL);
-			assert(buf!= NULL);
-			memcpy(buf, ms->data+ms->fpos, count);
-			ms->fpos += count;
-		}
+	}
+	if (count) {
+		assert(ms->data!= NULL);
+		assert(buf!= NULL);
+		memcpy(buf, ms->data+ms->fpos, count);
+		ms->fpos += count;
 	}
 	return count;
 }


pgpICL5X7yiqs.pgp
Description: Digitale PGP-Signatur

Bug#778374: php5 5.6.5 fully breaks Horde packages in Debian jessie

[Mike Gabriel]

Package: php5-common
Version: 5.6.5+dfsg-1
Severity: grave
Tags: upstream


Dear PHP5 maintainers,

the latest migration of php5 to Debian jessie unfortunately broke the
complete Horde5 software that is in Debian jessie.

The latest php5 upstream branches (5.5 and 5.6) introduced a severe
regression as discussed at [1].

I am currently test-building a PHP 5.6.5+dfsg-1.1 with that patch
reverted. I will get back to you soon, if that fixes the observed
issue.

Breaking Horde5 means: no communication via IMAP with an MDA (IMAP
server) is possible anymore.

light+love,
Mike


[1] https://bugs.php.net/bug.php?id=68948


-- Package-specific info:
 Additional PHP 5 information 

 PHP 5 SAPI (php5query -S): 
cli
apache2

 PHP 5 Extensions (php5query -M -v): 
imap (Enabled for cli by maintainer script)
imap (Enabled for apache2 by maintainer script)
pdo (Enabled for cli by maintainer script)
pdo (Enabled for apache2 by maintainer script)
opcache (Enabled for cli by maintainer script)
opcache (Enabled for apache2 by maintainer script)
mysql (Enabled for cli by maintainer script)
mysql (Enabled for apache2 by maintainer script)
curl (Enabled for cli by maintainer script)
curl (Enabled for apache2 by maintainer script)
mysqli (Enabled for cli by maintainer script)
mysqli (Enabled for apache2 by maintainer script)
pdo_sqlite (Enabled for cli by maintainer script)
pdo_sqlite (Enabled for apache2 by maintainer script)
ldap (Enabled for cli by maintainer script)
ldap (Enabled for apache2 by maintainer script)
pdo_mysql (Enabled for cli by maintainer script)
pdo_mysql (Enabled for apache2 by maintainer script)
imagick (Enabled for cli by maintainer script)
imagick (Enabled for apache2 by maintainer script)
intl (Enabled for cli by maintainer script)
intl (Enabled for apache2 by maintainer script)
json (Enabled for cli by maintainer script)
json (Enabled for apache2 by maintainer script)
gd (Enabled for cli by maintainer script)
gd (Enabled for apache2 by maintainer script)
mcrypt (Enabled for cli by maintainer script)
mcrypt (Enabled for apache2 by maintainer script)
readline (Enabled for cli by maintainer script)
readline (Enabled for apache2 by maintainer script)
sqlite3 (Enabled for cli by maintainer script)
sqlite3 (Enabled for apache2 by maintainer script)

 Configuration files: 
 /etc/php5/mods-available/pdo.ini 
extension=pdo.so

 /etc/php5/mods-available/opcache.ini 
zend_extension=opcache.so


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages php5 depends on:
ii  libapache2-mod-php5  5.6.5+dfsg-1
ii  php5-common  5.6.5+dfsg-1

php5 recommends no packages.

php5 suggests no packages.

Versions of packages php5-common depends on:
ii  libc6   2.19-13
ii  lsof4.86+dfsg-1
ii  psmisc  22.21-2
ii  sed 4.2.2-4+b1
ii  ucf 3.0030

Versions of packages php5-common suggests:
pn  php5-user-cache  

-- no debconf information


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

Bug#777583: Incorrect debian/copyright for smartmontools

[Giuseppe Iuculano]

retitle -1 debian/copyright for smartmontools is too restrictive
severity -1 wishlist




Il 14/02/2015 06:57, Mark H Weaver ha scritto:
> Every package must be accompanied by a verbatim copy of its
>   copyright information and distribution license in the file
>   /usr/share/doc//copyright.
> 
> Note the word "verbatim".  Therefore, smartmontools clearly violates a
> "must" directive of Debian policy, and so this bug should have severity
> "serious" as per .


The README file says:

== COPYING ==
Copyright (C) 2002-9 Bruce Allen

Copyright (C) 2004-14 Christian Franke


This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2, or (at your option) any
later version.


Cheers,
Giuseppe.


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

Bug#778373: botch FTBFS on 32 bit architectures

[Johannes Schauer]

Package: botch
Version: 0.5-1~experimental3
Severity: serious
Justification: fails to build from source

Hi,

botch currently FTBFS on 32 bit arches while succeeding on 64 bit
arches.

The problem is, that the ocaml parts assign unique vertex/edge ids based
on their order in the input GraphML but networkx will store GraphML
nodes and edges in random order.

To combat the random-ness, PYTHONHASHSEED=0 has been set but that only
leads to the same hash within 32 bit and 64 bit arches but not to the
same hash for both together.

See http://bugs.python.org/issue22621 for an explanation why this will
not be fixed in Python.

So instead, the ocaml code should be made to work irrespective of the
order of the nodes and edges in the input XML.

cheers, josch


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