Bug#759094: marked as done (matplotlib: Please update to use wxpython3.0)

[Debian Bug Tracking System]

Your message dated Thu, 16 Oct 2014 06:49:49 +
with message-id 
and subject line Bug#759094: fixed in matplotlib 1.4.1~rc1-1
has caused the Debian Bug report #759094,
regarding matplotlib: Please update to use wxpython3.0
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.)


-- 
759094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759094
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: matplotlib
Version: 1.3.1-2
Severity: important
Tags: sid jessie
User: freewx-ma...@lists.alioth.debian.org
Usertags: wxpy3.0
Control: block 755757 by -1

We're aiming to migrate the archive to using wxpython3.0 instead of
wxwidgets2.8, and hope to drop wxwidgets2.8 before jessie is released.
This transition is already underway, and is being tracked by the release
team here:

https://release.debian.org/transitions/html/wxpython3.0.html

The wxPython 3.0 API mostly adds to the wxPython2.8 API.  Many packages
work with wxPython 3.0 without any changes, but there are a few
incompatibilities.  For example, wx.Color is no longer supported as
an alias for wx.Colour, and some constants which were deprecated in 2.8
have been removed.  All the removed constants I'm aware of were set to 0
in wxPython 2.8, so removing them is still compatible with 2.8.

To assist updating to wxPython 3.0, I've put together a script which
will help make the mechanical changes required.  This is in a git repo
on collab-maint along with a README about using it and updating packages
for wxPython 3.0 in general:

http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git

The script has some options to control the sorts of changes it makes -
see the README and --help output for more information - you can view
the latest version of the README online here:

http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README

I've developed this script by trying to convert 20+ packages.  Please
try it out on your package - in many cases, it should be enough to get
your package working (if it doesn't already) - if it does, please upload
(and close this bug).

If the script doesn't do the job, please let me know (or improve the
script if you can figure out what it needs to do to get your package
working).

Another issue you may hit is that wxWidgets 3.0 now defaults to enabling
its "WXDEBUG" checks for incorrect API usage, so some applications will
emit scary sounding "assertion failures".  These are unlikely to
actually be new, just in a default build of 2.8, such incorrect uses
were handled quietly behind the scenes.  Sometimes these are easy to
fix, but if not you can easily patch the application to tell wx 3.0 to
handle them in the same way wx 2.8 does - details of how to do so are in
the README:

http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README

I'm happy to sponsor uploads for this transition, though if you have an
active sponsor already check with them first - I don't want to tread on
anyone's toes.

Cheers,
Olly
--- End Message ---
--- Begin Message ---
Source: matplotlib
Source-Version: 1.4.1~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 759...@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: SHA1

Format: 1.8
Date: Thu, 16 Oct 2014 00:17:18 +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.4.1~rc1-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 
(Pyt

Processed: Re: Bug#765555: cdimage.debian.org: debian-testing-i386-lxde-CD DL via Jigdo does not boot, "no Kernel found"

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 765458
Bug #76 [cdimage.debian.org] cdimage.debian.org: 
debian-testing-i386-lxde-CD DL via Jigdo does not boot, "no Kernel found"
76 was not blocked by any bugs.
76 was not blocking any bugs.
Added blocking bug(s) of 76: 765458

-- 
76: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=76
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#762789: proposed fix for ppp CVE-2014-3158

[Raphael Hertzog]

On Thu, 16 Oct 2014, Andrew Bartlett wrote:
> On Thu, 2014-10-16 at 02:30 +0200, Marco d'Itri wrote:
> > On Oct 16, Andrew Bartlett  wrote:
> > 
> > > Thanks.  How do you wish to proceed?
> > I suggest that you just upload the package.
> 
> Just to be clear, I'm not (yet) a Debian Maintainer, so I don't have
> upload rights, or the right to send out the DLA.  

If Marco doesn't want to do it, let me know and I can take care of the
upload + announce for squeeze-lts.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/


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

Bug#764817: Bug confirmed and fixe validated

[Eric Valette]

Thanks Laurent for posting the/a solution.

-- eric


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

Bug#765544: marked as done (python-cryptography: FTBFS with openssl 1.0.1j)

[Debian Bug Tracking System]

Your message dated Thu, 16 Oct 2014 05:04:20 +
with message-id 
and subject line Bug#765544: fixed in python-cryptography 0.6.1-1
has caused the Debian Bug report #765544,
regarding python-cryptography: FTBFS with openssl 1.0.1j
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.)


-- 
765544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-cryptography
Version: 0.6-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

OpenSSL 1.0.1j includes some incompatible changes in the public API; 
specifically, certain APIs now return a different error in some cases. This 
causes a test suite failure while building cryptography.

(I am packaging the new upstream release, 0.6.1, which fixes this issue)

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

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

Versions of packages python-cryptography depends on:
ii  libc6 2.19-11
ii  libssl1.0.0   1.0.1j-1
ii  python2.7.8-1
ii  python-cffi   0.8.6-1
ii  python-pkg-resources  5.5.1-1
ii  python-six1.8.0-1
pn  python:any

python-cryptography recommends no packages.

Versions of packages python-cryptography suggests:
pn  python-cryptography-doc  
ii  python-cryptography-vectors  0.6-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python-cryptography
Source-Version: 0.6.1-1

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

Debian distribution maintenance software
pp.
Tristan Seligmann  (supplier of updated 
python-cryptography 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: Thu, 16 Oct 2014 06:45:38 +0200
Source: python-cryptography
Binary: python-cryptography python3-cryptography python-cryptography-doc
Architecture: source amd64 all
Version: 0.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: Tristan Seligmann 
Changed-By: Tristan Seligmann 
Description:
 python-cryptography - Python library exposing cryptographic recipes and 
primitives (Pyt
 python-cryptography-doc - Python library exposing cryptographic recipes and 
primitives (doc
 python3-cryptography - Python library exposing cryptographic recipes and 
primitives (Pyt
Closes: 765544
Changes:
 python-cryptography (0.6.1-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fixes FTBFS with OpenSSL 1.0.1j caused by API change (closes: #765544).
 - No other upstream changes that affect Debian.
   * Bump Standard-Version to 3.9.6 (no changes).
Checksums-Sha1:
 4d7d8c4d2fccbe9313c1db9e27abb99deb163486 2653 python-cryptography_0.6.1-1.dsc
 ebebd789e70a9106095a693a031fd3f2f1a44026 236721 
python-cryptography_0.6.1.orig.tar.gz
 0b1ca61d7c1e684dca3f55fea28994aad89e4ca7 22268 
python-cryptography_0.6.1-1.debian.tar.xz
 8e433417a6bd829ffa20c56cad53ed5aff9c11d9 165088 
python-cryptography_0.6.1-1_amd64.deb
 8fb40d07fc35ce8db3c2c4cdd9128118d1578a65 163808 
python3-cryptography_0.6.1-1_amd64.deb
 4c010a595b8bc99a2ec08a7e2c311f0e5ba5084b 70880 
python-cryptography-doc_0.6.1-1_all.deb
Checksums-Sha256:
 f95c7014baf2fe28adf447409e834ef2d95be17d1ec6ebc37bf73d24535ae3fe 2653 
python-cryptography_0.6.1-1.dsc
 024910130a01eda0ce969764d893d2e397168ebb94181ca1ea3e23e19912329e 236721 
python-cryptography_0.6.1.orig.tar.gz
 d6bc614e2aaf7f4830d24e82306dddf5e4e1ce42117663f9fd84a5bf5d696ec0 22268 
python-cryptography_0.6.1-1.debian.tar.xz
 a9c59d6d6a16ab45157377ffdb6db2e7ae0534308f09675d631bfc542983a9d5 165088 
python-cryptography_0.6.1-1_amd64.deb
 20d157358e4613c4091a8298a1a4aeb15d115e0901c0e164ef4a9b3cc5401bb3 163808 
python3-cryptography_0.6.1-1_amd64.deb
 21c9ae4ed062e1057bda911351d25ad2d552f867909c45bad9f70dc6ea82b62d 70

Bug#765544: python-cryptography: FTBFS with openssl 1.0.1j

[Tristan Seligmann]

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

OpenSSL 1.0.1j includes some incompatible changes in the public API; 
specifically, certain APIs now return a different error in some cases. This 
causes a test suite failure while building cryptography.

(I am packaging the new upstream release, 0.6.1, which fixes this issue)

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

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

Versions of packages python-cryptography depends on:
ii  libc6 2.19-11
ii  libssl1.0.0   1.0.1j-1
ii  python2.7.8-1
ii  python-cffi   0.8.6-1
ii  python-pkg-resources  5.5.1-1
ii  python-six1.8.0-1
pn  python:any

python-cryptography recommends no packages.

Versions of packages python-cryptography suggests:
pn  python-cryptography-doc  
ii  python-cryptography-vectors  0.6-1

-- no debconf information


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

Processed: bug 765142 is forwarded to https://bugs.launchpad.net/beautifulsoup/+bug/1375721

[Debian Bug Tracking System]

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

> forwarded 765142 https://bugs.launchpad.net/beautifulsoup/+bug/1375721
Bug #765142 [src:beautifulsoup4] beautifulsoup4: FTBFS: Tests failures
Set Bug forwarded-to-address to 
'https://bugs.launchpad.net/beautifulsoup/+bug/1375721'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
765142: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765142
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#765473: dovecot-common: Dovecot (previous to V2.1) doesn't allow to disable SSLv3 which is bad: CVE-2014-3566

[Thijs Kinkhorst]

On Wed, October 15, 2014 16:30, Henrik Langos wrote:
> Hi Thijs,
>
> On 10/15/14 14:26, Thijs Kinkhorst wrote:
>> On Wed, October 15, 2014 14:07, Henrik Langos wrote:
>>> There is a simple one line patch available for dovecot 2.0.
>>> Maybe a similar way exists for 1.2.
>> Do you have a pointer to this patch?
>>
>>
>> Thijs
>
> Sure.. Sorry, thought I had put them in the initial report:
>
> Here's the patch:
> http://www.dovecot.org/pipermail/dovecot/2014-October/098244.html
>
>
> There is also a statement that pop/imap might be harder/impossible to
> exploit but I wouldn't buy that just yet:
> http://www.dovecot.org/pipermail/dovecot/2014-October/098248.html

Thanks. But the patch does not make SSLv3 configurable, it just blocks it
in a hardcoded way. This may be acceptable to some, but I'm reluctant to
release this patch through the LTS security channel, because there's no
way to avoid any breakage by admins except for not installing the update.
Especially because, contrary to web browsers, we do not have a clear
picture of the state of SSL/TLS version support in mail clients out there,
so the impact is hard to measure.


Thijs


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

Bug#763314: Bug#763371: gftp crashes when connecting to site with error "Attempt to unlock mutex that was not locked"

[Terry Watt]

This bug resolved for me a couple of days ago, after updating GTK+2.0 to 
2.25.1.  That release appears to have addressed similar bugs in various other 
packages, and fixed the issue with gFTP as well.



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

Bug#762789: proposed fix for ppp CVE-2014-3158

[Andrew Bartlett]

On Thu, 2014-10-16 at 02:30 +0200, Marco d'Itri wrote:
> On Oct 16, Andrew Bartlett  wrote:
> 
> > Thanks.  How do you wish to proceed?
> I suggest that you just upload the package.

Just to be clear, I'm not (yet) a Debian Maintainer, so I don't have
upload rights, or the right to send out the DLA.  

In particular, I was trying to understand how would you like the
sid/jessie/wheezy part done.

Thanks,

Andrew Bartlett

-- 
Andrew Bartlett
http://samba.org/~abartlet/
Authentication Developer, Samba Team  http://samba.org
Samba Developer, Catalyst IT  http://catalyst.net.nz/services/samba





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

Bug#765540: missing symbol

[Ivan Sergio Borgonovo]

Package: grub-pc
Version: 2.02~beta2-14
Severity: grave

after upgrading grub from 2.00-22 -> 2.02~beta2-14 I was left in rescue
grub console with an error about missing symbol (something related to
color).

After trying to resurrect the system I
insmod linux
in grub console and I was greeted with the same error again.

I had to boot with a rescue usb and downgrade grub.

Please be patient if you need I report the exact error.

thanks

-- 
Ivan Sergio Borgonovo
http://www.webthatworks.it


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

Bug#765314: mrpt: FTBFS on all non-x86-based architectures

[Olly Betts]

On Wed, Oct 15, 2014 at 01:40:43PM +0200, Jose Luis Blanco wrote:
> I would add a third patch to fix (avoid) errors in hurd. If you have
> the possibility of adding it it would be great!
> 
> So, these are the 3 patches:
> https://github.com/jlblancoc/mrpt/commit/693bebedac9234fa00304a26aa854f54dc4d674f
> https://github.com/jlblancoc/mrpt/commit/bb294b9c7a9aef3b4bbbdc89811e7873805eba19
> https://github.com/jlblancoc/mrpt/commit/c81effd1228234e2ed17caf0ef22f0caee6b
> 
> Can be downloaded as git diffs as well:
> 
> https://github.com/jlblancoc/mrpt/commit/693bebedac9234fa00304a26aa854f54dc4d674f.diff
> https://github.com/jlblancoc/mrpt/commit/bb294b9c7a9aef3b4bbbdc89811e7873805eba19.diff
> https://github.com/jlblancoc/mrpt/commit/c81effd1228234e2ed17caf0ef22f0caee6b.diff

I don't mind making another NMU, but since mrpt takes an hour to build,
I'd prefer to try to fix all the architectures at once, and mipsel has
also failed to build with an internal compiler error:

https://buildd.debian.org/status/fetch.php?pkg=mrpt&arch=mipsel&ver=1%3A1.2.2-1.1&stamp=1413406454

> > On Wed, Oct 15, 2014 at 7:31 AM, Jose Luis Blanco
> >  wrote:
> >> Any recommendation about how to test it locally on s390x? qemu or alike?

I've not tried qemu myself - I'd guess it's likely to take quite a while
to build under qemu though.

You can request guest access to the debian porter boxes:

https://dsa.debian.org/doc/guest-account/

Not sure if you're a DM or in NM, but if not you'll need to get a DD to
sponsor the request.  It's probably most appropriate to get your usual
upload sponsor to send in the request, but I guess I can if he/she isn't
available.

> >> A partner got it tested in a physical mips device before submitting,
> >> so hopefully it will work there...

It's not yet tried to build there yet.

Cheers,
Olly


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

Processed: your mail

[Debian Bug Tracking System]

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

> close 733556 1.6.2-9
Bug #733556 [wine] wine: binfmt-support got lost
There is no source info for the package 'wine' at version '1.6.2-9' with 
architecture ''
Unable to make a source version for version '1.6.2-9'
Marked as fixed in versions 1.6.2-9.
Bug #733556 [wine] wine: binfmt-support got lost
Marked Bug as done
> close 762044 1.6.2-9
Bug #762044 [src:wine] wine: drop references to wine-doc (removed) in 
debian/control
The source 'wine' and version '1.6.2-9' do not appear to match any binary 
packages
Marked as fixed in versions wine/1.6.2-9.
Bug #762044 [src:wine] wine: drop references to wine-doc (removed) in 
debian/control
Marked Bug as done
> close 751450 1.6.2-9
Bug #751450 [wine] wine multiarch warning is missing a step
There is no source info for the package 'wine' at version '1.6.2-9' with 
architecture ''
Unable to make a source version for version '1.6.2-9'
Marked as fixed in versions 1.6.2-9.
Bug #751450 [wine] wine multiarch warning is missing a step
Marked Bug as done
> close 764110 1.6.2-9
Bug #764110 [src:wine] wine: build-dependency on libgnutls-dev
The source 'wine' and version '1.6.2-9' do not appear to match any binary 
packages
Marked as fixed in versions wine/1.6.2-9.
Bug #764110 [src:wine] wine: build-dependency on libgnutls-dev
Marked Bug as done
> close 760696 1.6.2-9
Bug #760696 [src:wine] Please make the transitional packages deborphan compliant
The source 'wine' and version '1.6.2-9' do not appear to match any binary 
packages
Marked as fixed in versions wine/1.6.2-9.
Bug #760696 [src:wine] Please make the transitional packages deborphan compliant
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
733556: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733556
751450: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751450
760696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760696
762044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762044
764110: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764110
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#765072: marked as done (debian-faq: Build-Depends-Indep missing texlive-lang-....)

[Debian Bug Tracking System]

Your message dated Thu, 16 Oct 2014 00:49:16 +
with message-id 
and subject line Bug#765072: fixed in debian-faq 5.0.3
has caused the Debian Bug report #765072,
regarding debian-faq: Build-Depends-Indep missing texlive-lang-
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.)


-- 
765072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-faq
Version: 5.0.2
Severity: serious
Tags: patch
Justification: FTBFS

Fails to build under pbuilder.


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

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

debian-faq depends on no packages.

debian-faq recommends no packages.

Versions of packages debian-faq suggests:
ii  evince-gtk [postscript-viewer]   3.12.2-1
ii  ghostscript [postscript-viewer]  9.06~dfsg-1
ii  iceweasel [www-browser]  31.1.0esr-1
ii  links [www-browser]  2.8-2+b1
ii  lynx-cur [www-browser]   2.8.9dev1-2
ii  w3m [www-browser]0.5.3-17
--- old/debian/control	2012-03-27 06:47:44.0 +1000
+++ new/debian/control	2014-10-13 19:42:19.454504062 +1000
@@ -6,7 +6,11 @@
  Joost van Baal , Simon Paillard 
 Build-Depends: debhelper (>= 5)
 Build-Depends-Indep: debiandoc-sgml, texlive (>= 2007-11), texlive-latex-extra,
- texlive-lang-cyrillic, latex-cjk-chinese,
+ texlive-lang-chinese, texlive-lang-cyrillic, texlive-lang-english,
+ texlive-lang-french, texlive-lang-german, texlive-lang-italian,
+ texlive-lang-other, texlive-lang-polish, texlive-lang-portuguese,
+ texlive-lang-spanish,
+ latex-cjk-chinese,
  latex-cjk-chinese-arphic-bkai00mp, latex-cjk-chinese-arphic-bsmi00lp,
  latex-cjk-chinese-arphic-gbsn00lp, latex-cjk-chinese-arphic-gkai00mp,
  ghostscript, po4a
--- End Message ---
--- Begin Message ---
Source: debian-faq
Source-Version: 5.0.3

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

Debian distribution maintenance software
pp.
Javier Fernández-Sanguino Peña  (supplier of updated 
debian-faq package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 15 Oct 2014 22:43:52 +0200
Source: debian-faq
Binary: debian-faq debian-faq-de debian-faq-fr debian-faq-it debian-faq-ru 
debian-faq-zh-cn
Architecture: source all
Version: 5.0.3
Distribution: unstable
Urgency: low
Maintainer: Javier Fernandez-Sanguino Peña 
Changed-By: Javier Fernández-Sanguino Peña 
Description:
 debian-faq - Debian Frequently Asked Questions
 debian-faq-de - Debian Frequently Asked Questions, in German
 debian-faq-fr - Debian Frequently Asked Questions, in French
 debian-faq-it - Debian Frequently Asked Questions, in Italian
 debian-faq-ru - Debian Frequently Asked Questions, in Russian
 debian-faq-zh-cn - Debian Frequently Asked Questions, in Chinese
Closes: 452387 500447 503897 548453 662206 684003 692895 714387 721112 721207 
721281 721684 721685 724039 725586 761584 765072 765073
Changes:
 debian-faq (5.0.3) unstable; urgency=low
 .
   [ Simon Paillard ]
   * Fix typo in French translation, thanks Filipus Klutiero (Closes: #721684)
 .
   [ David Prévot ]
   * Workaround #725931 (po4a became disrespectful about tag order)
 (Closes: #725586)
 .
   [ Joost van Baal-Ilić ]
   * Remove section on package termcap-compat: not shipped any more since 2005.
 Thanks to Joseph Lenox (Closes: #714387)
   * "Debian Developer" is not "Debian developer", refer to
 http://www.debian.org/intro/help (Closes: #721207)
 .
   [ Javier Fernández-Sanguino ]
   * Acknowledge NMU (Closes: #765072, #725586, #765073)
   * uptodate.sgml: Change aptitude dist-upgrade to full-upgrade
 (Closes: #684003)
   * faqstatic.ent: Change release number to just '7'. The release numbering
 scheme changed in wheezy, release is now only the major number only

Bug#725586: marked as done (debian-faq: FTBFS: make[1]: *** [po4a-translate] Error )

[Debian Bug Tracking System]

Your message dated Thu, 16 Oct 2014 00:49:16 +
with message-id 
and subject line Bug#725586: fixed in debian-faq 5.0.3
has caused the Debian Bug report #725586,
regarding debian-faq: FTBFS: make[1]: *** [po4a-translate] Error 
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.)


-- 
725586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725586
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debian-faq
Version: 5.0.2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131006 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> test -f Makefile -a -f debian/rules
> /usr/bin/make po4a-translate html text ps pdf langs="de fr it ru zh_CN"
> make[1]: Entering directory `/«PKGBUILDDIR»'
> echo "" > faqdynamic.ent
> if [ -f debian/changelog ]; then \
>   echo " '^Version: ' | sed 's/^Version: *//'`\">" >> faqdynamic.ent; \
> else \
>   echo "" >> faqdynamic.ent; \
> fi
> po4a --keep 0 --previous --rm-backups po4a/po4a.cfg # --localized-charset 
> UTF-8
> No candidate position for the addendum po4a/add_fr/commentaires.add.
> Addendum po4a/add_fr/commentaires.add does NOT apply to fr/debian-faq.sgml 
> (translation discarded).
> make[1]: *** [po4a-translate] Error 255

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/10/06/debian-faq_5.0.2_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Javier Fernández-Sanguino Peña  (supplier of updated 
debian-faq package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 15 Oct 2014 22:43:52 +0200
Source: debian-faq
Binary: debian-faq debian-faq-de debian-faq-fr debian-faq-it debian-faq-ru 
debian-faq-zh-cn
Architecture: source all
Version: 5.0.3
Distribution: unstable
Urgency: low
Maintainer: Javier Fernandez-Sanguino Peña 
Changed-By: Javier Fernández-Sanguino Peña 
Description:
 debian-faq - Debian Frequently Asked Questions
 debian-faq-de - Debian Frequently Asked Questions, in German
 debian-faq-fr - Debian Frequently Asked Questions, in French
 debian-faq-it - Debian Frequently Asked Questions, in Italian
 debian-faq-ru - Debian Frequently Asked Questions, in Russian
 debian-faq-zh-cn - Debian Frequently Asked Questions, in Chinese
Closes: 452387 500447 503897 548453 662206 684003 692895 714387 721112 721207 
721281 721684 721685 724039 725586 761584 765072 765073
Changes:
 debian-faq (5.0.3) unstable; urgency=low
 .
   [ Simon Paillard ]
   * Fix typo in French translation, thanks Filipus Klutiero (Closes: #721684)
 .
   [ David Prévot ]
   * Workaround #725931 (po4a became disrespectful about tag order)
 (Closes: #725586)
 .
   [ Joost van Baal-Ilić ]
   * Remove section on package termcap-compat: not shipped any more since 2005.
 Thanks to Joseph Lenox (Closes: #714387)
   * "Debian Developer" is not "Debian developer", refer to
 http://www.debian.org/intro/help (Closes: #721207)
 .
   [ Javier Fernández-Sanguino ]
   * Acknowledge NMU (Closes: #765072, #725586, #765073)
   * uptodate.sgml: Change aptitude dist-upgrade to full-upgrade
 (Closes: #684003)
   * faqstatic.ent: Change release number to just '7'. The release numbering
 scheme changed in wheezy, release is now only the major number only.
 (Closes: #721685)
   * basic_defs.sgml: Change 'cooperative statement' and replace with the
 definition used in https://www.debia

Bug#762789: proposed fix for ppp CVE-2014-3158

[Marco d'Itri]

On Oct 16, Andrew Bartlett  wrote:

> Thanks.  How do you wish to proceed?
I suggest that you just upload the package.

-- 
ciao,
Marco


signature.asc
Description: Digital signature

Bug#762832: fcitx: FTBFS: cp: cannot stat 'debian/tmp/usr/lib/girepository-1.0/Fcitx-1.0.typelib': No such file or directory

[Kenshi Muto]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

Is there any update for this bug#762832?

mlterm depends fcitx, and I got a message from Release team;
"mlterm 3.3.8-1 is marked for autoremoval from testing on 2014-11-13".

Thanks,
- -- 
Kenshi Muto
km...@debian.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.9 

iQIcBAEBCgAGBQJUPw8lAAoJEB0hyD3EUuD8rGQP/1vXiCDo/j1ZE/LBPMxy/F6w
95TQczAAu/okG9zj6ypMY8otdQopej9/mkCzTzIdsui7gt7j7e37R+xlJ1SGn0E4
WUxlZqH5yzbk8fW1k9+tBHfHBycY/AVKm2B3/Vd4Fsbr2SVS9ixJ9ZWe+2RwJ7Jk
5VbFJLyfuB6Lo1iM67wA57I8IBBMZJrVo+Ej+RCZcP+CNO4yt/p/e5G+i/CpmWcu
THowiyyRzJ3OzFjBpg5HvEqZy55rV9/eD4meTp2aJE2ZSttIDC7HeGdzs2IuNX0H
xHK4UrIBTGbxQ1RHIRuoSrul5xfnmk5O/f0jiAXLnU7lFJbOPF2HaNuZT48XYKoA
sLEpRXuZc05ki+B5R7X8XBUk4hqvTiyrwIm9o/obBsMj2Duk/g8Ucz3cp2MXKHWz
9uk87bkHvBoDG/XjSBmTj7Zpf/FyUxjgeqomoofyT1hx6fSrcTOYsOzvx3gGdKUJ
21BtkuheF7j6eFxgcWvwVePE1zQVi/5SXfTBiN+4NFFk6Uy87HNYecQrsE+ksySV
KtKBWdUnsE7gd6xje3oQ/SEpqtqjwqLPmu+AIwbiA+n7o6lO1SEDQ3VPWv2ml1CJ
uvID/tQbVzZlkPQHmWen4o20jHOtIq6muKN5Q/68rnm17gFaiE73SDk2AINZlP6o
FpRBxVXdiokpNLScKCcj
=M0vl
-END PGP SIGNATURE-


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

Bug#762789: proposed fix for ppp CVE-2014-3158

[Andrew Bartlett]

On Thu, 2014-10-16 at 01:36 +0200, Marco d'Itri wrote:
> On Oct 16, Andrew Bartlett  wrote:
> 
> > I've prepared a a fix for CVE-2014-3158, an integer overflow potentially
> > permitting a user in the dip group to abuse the privileges of the setuid
> > root pppd binary by supplying a very, very long options line in
> > ~/.ppprc.
> Is this actually known to be exploitable?

This is the one bit I haven't proven yet.  I didn't have the patience to
generate a 2G config line to test, but it will read the user's .ppprc
file while setuid.

The variable the user could overflow is on the stack, so I'm assuming
all the usual stack smashing attacks apply. 

> If you believe that it is worth fixing then your changes look fine to 
> me.

Thanks.  How do you wish to proceed?

Andrew Bartlett

-- 
Andrew Bartlett
http://samba.org/~abartlet/
Authentication Developer, Samba Team  http://samba.org
Samba Developer, Catalyst IT  http://catalyst.net.nz/services/samba





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

Processed: bug 765125 is forwarded to https://mail-archives.apache.org/mod_mbox/perl-embperl/201410.mbox/%3C20141015235410.GZ5405%40sym.noone.org%3E

[Debian Bug Tracking System]

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

> forwarded 765125 
> https://mail-archives.apache.org/mod_mbox/perl-embperl/201410.mbox/%3C20141015235410.GZ5405%40sym.noone.org%3E
Bug #765125 [src:libembperl-perl] libembperl-perl: FTBFS: Tests failures
Set Bug forwarded-to-address to 
'https://mail-archives.apache.org/mod_mbox/perl-embperl/201410.mbox/%3C20141015235410.GZ5405%40sym.noone.org%3E'.
> thanks
Stopping processing here.

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

debian-bugs-rc@lists.debian.org

[Antoine Beaupré]

On 2014-10-14 05:54:57, Holger Levsen wrote:
> control: tags -1 + pending
>
> Hi,
>
> fixed in git by Steve,  thanks!
>
> 2.0.22-1 should arrive soon...

Any idea when 2.0.22 will be released? It doesn't seem to be shipped
even upstream...

In my mind, this should be fixed in jessie at least...

a.

-- 
Il n'existe aucune limite sacrée ou non à l'action de l'homme dans
l'univers. Depuis nos origines nous avons le choix: être aveuglé par
la vérité ou coudre nos paupières.
- [no one is innocent]


pgpvCOSFAKtAk.pgp
Description: PGP signature

Bug#765125: libembperl-perl: FTBFS: Tests failures

[Axel Beckert]

Control: tag -1 + upstream

Hi,

some more details:

Axel Beckert wrote:
> gregor herrmann wrote:
> > It builds with CGI.pm 3.x from perl core but not if I add
> > libcgi-pm-perl as a build dependency.
> 
> The line causing the failure is
> 
> do { $cgiok = $CGI::VERSION > 2.45 ; @info = sort keys %{$fdat{-upload}} ; 
> $cgiok?"@info":'Content-Disposition Content-Type' }
> 
> In both cases $cgiok should be true:
> 
> → perl -MCGI -E 'say $CGI::VERSION'
> 4.06
> → perl -I/usr/share/perl/5.20.1 -MCGI -E 'say $CGI::VERSION'
> 3.65
> 
> So the difference is the amount of meta data in the $fdat{-upload}
> hashref (which is likely generated by CGI.pm).

The actual difference is the following (expected pattern may include
regular expressions):

+++ test/tmp/out.htm2014-10-16 01:21:07.288697841 +0200
@@ -3,17 +3,15 @@
 
 Embperl Tests - File-Upload
 
-
 Embperl Tests - File-Upload
 
-Content-Disposition Content-Type
-^Filename:   \d*upload-filename
-Content-Type:  test/plain
-^CGI-Version
-^cgiok   
-filehandle: Fh
-Info:  Content-Disposition = form-data; name="upload"; 
filename="12upload-filename"
-Content-Type = test/plain
+
+Filename:   12upload-filename
+Content-Type:  
+CGI-Version:4.06
+cgiok   1
+filehandle:CGI::File::Temp
+Info:
 no:   1
 size: 2048
 no:   2
@@ -27,7 +25,7 @@
 buflen: 8219
 Your file has the content
 --
-f1=abc1
+f1=abc1
[...]

> It seems as if CGI 3.65 outputs the very same values which the
> fallback test outputs if no CGI.pm at all is available, while CGI 4.x
> seems to have more keys in there, unexpected by the test.

Actually it does not have more keys in there but less -- namely none.
And this again doesn't look as good anymore.

Actually the whole %fdat now only contains this:

$VAR1 = {
  'content' => 'Hi there!',
  'multval' => 'A   B   C',
  'single' => 'S',
  'upload' => bless( \*{'File::Temp::$fh'}, 'CGI::File::Temp' )
};

This is likely related to these CGI.pm changes in 4.04:

- this release removes some long deprecated modules/functions and
  includes refactoring to the temporary file handling in CGI.pm. if
  you are doing anything out of the ordinary with regards to temp
  files you should test your code before deploying this update as
  temp files may no longer be stored in previously used locations

[...]

- test case for RT #55166 - calling Vars to get the filename does not return
  a filehandle, so this cannot be used in the call to uploadinfo, also
  update documentation for the uploadInfo to show that ->Vars should not be
  used to get the filename for this method
[...]
- add procedural call tests for upload and uploadInfo to confirm these work
  as should (RT #91136)

Then again this error happened while testing Embperl's mod_perl
backend, not in the CGI one... But IIRC file upload handling in
Embperl are generally outsourced to CGI.pm...

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-|  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5


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

Processed: Re: Bug#765125: libembperl-perl: FTBFS: Tests failures

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + upstream
Bug #765125 [src:libembperl-perl] libembperl-perl: FTBFS: Tests failures
Added tag(s) upstream.

-- 
765125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765125
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#762789: proposed fix for ppp CVE-2014-3158

[Andrew Bartlett]

I've prepared a a fix for CVE-2014-3158, an integer overflow potentially
permitting a user in the dip group to abuse the privileges of the setuid
root pppd binary by supplying a very, very long options line in
~/.ppprc.

Please review the attached debdiff for squeeze-lts (the other
distributions also need a fix).

This is my first fix for squeeze-lts, so I'm using this lower-impact
issue to learn the ropes, so feedback most welcome.  I'm also not yet a
Debian Maintainer, but will apply for that soon so I can also do the
announcement next time. 

Thanks!

Andrew Bartlett
-- 
Andrew Bartlett
http://samba.org/~abartlet/
Authentication Developer, Samba Team  http://samba.org
Samba Developer, Catalyst IT  http://catalyst.net.nz/services/samba



diff -u ppp-2.4.5/debian/changelog ppp-2.4.5/debian/changelog
--- ppp-2.4.5/debian/changelog
+++ ppp-2.4.5/debian/changelog
@@ -1,3 +1,12 @@
+ppp (2.4.5-4+deb6u1) squeeze-lts; urgency=high
+
+  * Non-maintainer upload.
+  * Backport fix for CVE-2014-3158 (Bug: 762789 integer overflow in 
+option parsing) from 
+https://github.com/paulusmack/ppp/commit/7658e8257183f062dc01f87969c140707c7e52cb
+
+ -- Andrew Bartlett   Wed, 15 Oct 2014 23:00:47 +
+
 ppp (2.4.5-4) unstable; urgency=low
 
   * Make sure to actually rebuild pppd for the udeb instead of using the
diff -u ppp-2.4.5/debian/patches/series ppp-2.4.5/debian/patches/series
--- ppp-2.4.5/debian/patches/series
+++ ppp-2.4.5/debian/patches/series
@@ -1,5 +1,6 @@
 # pulled from upstream
 git-20100307
+CVE-2014-3158.patch
 
 # to be merged upstream
 pppoatm_no_modprobe
only in patch2:
unchanged:
--- ppp-2.4.5.orig/debian/patches/CVE-2014-3158.patch
+++ ppp-2.4.5/debian/patches/CVE-2014-3158.patch
@@ -0,0 +1,55 @@
+From 7658e8257183f062dc01f87969c140707c7e52cb Mon Sep 17 00:00:00 2001
+From: Paul Mackerras 
+Date: Fri, 1 Aug 2014 16:05:42 +1000
+Subject: [PATCH] pppd: Eliminate potential integer overflow in option parsing
+
+When we are reading in a word from an options file, we maintain a count
+of the length we have seen so far in 'len', which is an int.  When len
+exceeds MAXWORDLEN - 1 (i.e. 1023) we cease storing characters in the
+buffer but we continue to increment len.  Since len is an int, it will
+wrap around to -2147483648 after it reaches 2147483647.  At that point
+our test of (len < MAXWORDLEN-1) will succeed and we will start writing
+characters to memory again.
+
+This may enable an attacker to overwrite the heap and thereby corrupt
+security-relevant variables.  For this reason it has been assigned a
+CVE identifier, CVE-2014-3158.
+
+This fixes the bug by ceasing to increment len once it reaches MAXWORDLEN.
+
+Reported-by: Lee Campbell 
+Signed-off-by: Paul Mackerras 
+---
+ pppd/options.c | 10 ++
+ 1 file changed, 6 insertions(+), 4 deletions(-)
+
+diff --git a/pppd/options.c b/pppd/options.c
+index 45fa742..e9042d1 100644
+--- a/pppd/options.c
 b/pppd/options.c
+@@ -1289,9 +1289,10 @@ getword(f, word, newlinep, filename)
+ 	/*
+ 	 * Store the resulting character for the escape sequence.
+ 	 */
+-	if (len < MAXWORDLEN-1)
++	if (len < MAXWORDLEN) {
+ 		word[len] = value;
+-	++len;
++		++len;
++	}
+ 
+ 	if (!got)
+ 		c = getc(f);
+@@ -1329,9 +1330,10 @@ getword(f, word, newlinep, filename)
+ 	/*
+ 	 * An ordinary character: store it in the word and get another.
+ 	 */
+-	if (len < MAXWORDLEN-1)
++	if (len < MAXWORDLEN) {
+ 	word[len] = c;
+-	++len;
++	++len;
++	}
+ 
+ 	c = getc(f);
+ }


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

Bug#762789: proposed fix for ppp CVE-2014-3158

[Marco d'Itri]

On Oct 16, Andrew Bartlett  wrote:

> I've prepared a a fix for CVE-2014-3158, an integer overflow potentially
> permitting a user in the dip group to abuse the privileges of the setuid
> root pppd binary by supplying a very, very long options line in
> ~/.ppprc.
Is this actually known to be exploitable?
If you believe that it is worth fixing then your changes look fine to 
me.

-- 
ciao,
Marco


signature.asc
Description: Digital signature

debian-bugs-rc@lists.debian.org

[John Platter]

I am trying to install Munin on Ubuntu 14 but the web server does not work. The 
error is, as mentioned before in this ticket, always  

I noticed that it is fixed in Git:) But when I make/make install it locally on 
the Ubuntu server then the binaries, config files, apache examples etc. are 
written in completely different directories, compared to an apt-get install and 
I cannot get it to work either.

When do you think the new version will be available for installing using 
apt-get on Ubuntu 14? For the moment I have to put this project on hold.

--
Rolf.


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

Bug#765125: libembperl-perl: FTBFS: Tests failures

[Axel Beckert]

Hi,

gregor herrmann wrote:
> It builds with CGI.pm 3.x from perl core but not if I add
> libcgi-pm-perl as a build dependency.

The line causing the failure is

do { $cgiok = $CGI::VERSION > 2.45 ; @info = sort keys %{$fdat{-upload}} ; 
$cgiok?"@info":'Content-Disposition Content-Type' }

In both cases $cgiok should be true:

→ perl -MCGI -E 'say $CGI::VERSION'
4.06
→ perl -I/usr/share/perl/5.20.1 -MCGI -E 'say $CGI::VERSION'
3.65

So the difference is the amount of meta data in the $fdat{-upload}
hashref (which is likely generated by CGI.pm).

It seems as if CGI 3.65 outputs the very same values which the
fallback test outputs if no CGI.pm at all is available, while CGI 4.x
seems to have more keys in there, unexpected by the test.

While I think that colon and "" in there look suspicious, I
currently assume that this test failure shows no functionality issues,
just some unexpected but likely non-breaking, i.e. backwards API
expansion -- just the test is not written with that in mind.

I'll do some further testin (checking where the colon and "" come
from), but I expect that this can be fixed by Build-Conflicting with
libcgi-pm-perl, at least for now.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-|  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5


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

Bug#765473: dovecot patch

[Kevin Fernandez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi

Here is the patch by Timo Sirainen:
http://dovecot.org/pipermail/dovecot/attachments/20141014/0c46af0d/attachment.obj

And his message:
http://www.dovecot.org/pipermail/dovecot/2014-October/098244.html

Best,

Kevin
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iJwEAQEIAAYFAlQ+/ugACgkQRrmQIkT52vz3mAP/UemEh0uUnmCxUJdrkP2NL4Ez
baBPglxuDuiclYMgCrwqjTt1xIV9gSs5NDbrrCRApcBAiYQaEFOlbg8B9Le32C08
17ySw3Gdp17f2lGfY+rW02IbNSqKIX0FyNtR0nk58e1kZtDXFhA3Adw7C4WWP34d
9bF3UGSoMD9mDnockfs=
=0YBR
-END PGP SIGNATURE-


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

Bug#746128: marked as done (obexd: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 22:52:06 +
with message-id 
and subject line Bug#746128: fixed in obexd 0.48-2.1
has caused the Debian Bug report #746128,
regarding obexd: FTBFS: Tests failures
to be marked as done.

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

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


-- 
746128: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: obexd
Version: 0.48-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140426 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>
> /gobex/null_io: OK
> /gobex/basic: OK
> /gobex/ref_unref: OK
> /gobex/test_disconnect: OK
> /gobex/test_recv_connect_stream: OK
> /gobex/test_recv_connect_pkt: OK
> 
> (./unit/test-gobex:17157): GLib-CRITICAL **: Source ID 11 was not found when 
> attempting to remove it
> /bin/bash: line 5: 17157 Trace/breakpoint trap   ${dir}$tst
> /gobex/test_send_connect_stream: FAIL: unit/test-gobex
> /gobex/test_conn_req: OK
> 
> (./unit/test-gobex-transfer:17162): GLib-CRITICAL **: Source ID 7 was not 
> found when attempting to remove it
> /bin/bash: line 5: 17162 Trace/breakpoint trap   ${dir}$tst
> /gobex/test_conn_rsp: FAIL: unit/test-gobex-transfer
> ===
> make[2]: *** [check-TESTS] Error 12 of 5 tests failed
> 
> ===
> make[1]: *** [check-am] Error 2
> dh_auto_test: make -j1 check returned exit code 2

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/04/26/obexd_0.48-2_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Tobias Hansen  (supplier of updated obexd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 15 Oct 2014 23:59:01 +0200
Source: obexd
Binary: obexd-client obexd-server
Architecture: source amd64
Version: 0.48-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Bluetooth Maintainers 

Changed-By: Tobias Hansen 
Description:
 obexd-client - D-Bus OBEX client
 obexd-server - D-Bus OBEX server
Closes: 746128
Changes:
 obexd (0.48-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Include patch test-avoid-double-source-removals.patch
 from Ubuntu to avoid double source removals during tests.
 (Closes: #746128)
Checksums-Sha1:
 9685eb29aa2be5e3ad999dac4baefc589cabaa9e 2099 obexd_0.48-2.1.dsc
 f1d84d60332c14464c62830cc9bba58ae7f9b362 4808 obexd_0.48-2.1.debian.tar.xz
 af49fe1dde6d535508ebb92fe1b85c49a302d348 77968 obexd-client_0.48-2.1_amd64.deb
 ef0996c40e91b2c3a0f86d57eacaa9d4bf0bdc64 90546 obexd-server_0.48-2.1_amd64.deb
Checksums-Sha256:
 df0275440dc31aad85c8e5a792d8cbced19b160aed466da3fca5914c8a12db1c 2099 
obexd_0.48-2.1.dsc
 1e02c12ef55e0b2c5052cf9fd97c6d5eb67c36cd92df178f12e76c7a5fc47c6a 4808 
obexd_0.48-2.1.debian.tar.xz
 5206d7df17d26632fcf23beafde631d5f5a98049961ac7b3547d0cbbc36bea61 77968 
obexd-client_0.48-2.1_amd64.deb
 5c415aa53c3a1e305e0bd0f395277ec99ea0a10186c2f87ad99bfd0b9650d1df 90546 
obexd-server_0.48-2.1_amd64.deb
Files:
 24d92fefc6a50948f8939c486b7c95c8 2099 admin optional obexd_0.48-2.1.dsc
 ddaeec2b527d3ed8a17d90ccc4849be9 4808 admin optional 
obexd_0.48-2.1.debian.tar.xz
 0a7bd49de606aa26cf7a5368ee4cdde3 77968 admin optional 
obexd-client_0.48-2.1_amd64.deb
 2a22e67d28868f49e94e79bc6360269f 90546 admin optional 
obexd-server_0.48-2.1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJUPvK0AAoJEIyCFp2Ozs0qUaIQAIFw44kL0S1rXEZsmXacn7sr
Io8M

Bug#765293: marked as done (gnunet: FTBFS on kfreebsd-*: error: malloc_np.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 22:21:43 +
with message-id 
and subject line Bug#765293: fixed in gnunet 0.10.1-2
has caused the Debian Bug report #765293,
regarding gnunet: FTBFS on kfreebsd-*: error: malloc_np.h: No such file or 
directory
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.)


-- 
765293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnunet
Version: 0.10.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

gnunet failed to build on kfreebsd-*:
|   CC   common_allocation.lo
| In file included from common_allocation.c:26:0:
| ../../src/include/platform.h:223:0: warning: "__BYTE_ORDER" redefined
|  #define __BYTE_ORDER BYTE_ORDER
|  ^
| In file included from /usr/include/endian.h:36:0,
|  from /usr/include/x86_64-kfreebsd-gnu/sys/types.h:216,
|  from ../../src/include/platform.h:48,
|  from common_allocation.c:26:
| /usr/include/x86_64-kfreebsd-gnu/bits/endian.h:7:0: note: this is the 
location of the previous definition
|  #define __BYTE_ORDER __LITTLE_ENDIAN
|  ^
| In file included from common_allocation.c:26:0:
| ../../src/include/platform.h:224:0: warning: "__BIG_ENDIAN" redefined
|  #define __BIG_ENDIAN BIG_ENDIAN
|  ^
| In file included from /usr/include/x86_64-kfreebsd-gnu/sys/types.h:216:0,
|  from ../../src/include/platform.h:48,
|  from common_allocation.c:26:
| /usr/include/endian.h:32:0: note: this is the location of the previous 
definition
|  #define __BIG_ENDIAN 4321
|  ^
| common_allocation.c:201:23: fatal error: malloc_np.h: No such file or 
directory
|  #include 
|^
| compilation terminated.
| make[4]: *** [common_allocation.lo] Error 1
| Makefile:2229: recipe for target 'common_allocation.lo' failed

For a full build log see
https://buildd.debian.org/status/fetch.php?pkg=gnunet&arch=kfreebsd-amd64&ver=0.10.1-1&stamp=1412460116.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: gnunet
Source-Version: 0.10.1-2

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

Debian distribution maintenance software
pp.
Bertrand Marc  (supplier of updated gnunet package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 15 Oct 2014 21:44:26 +0200
Source: gnunet
Binary: gnunet gnunet-client gnunet-common gnunet-dbg gnunet-server gnunet-dev
Architecture: source all
Version: 0.10.1-2
Distribution: unstable
Urgency: medium
Maintainer: Bertrand Marc 
Changed-By: Bertrand Marc 
Description:
 gnunet - secure, trust-based peer-to-peer framework (meta)
 gnunet-client - transitional dummy package
 gnunet-common - transitional dummy package
 gnunet-dbg - secure, trust-based peer-to-peer framework (debug)
 gnunet-dev - secure, trust-based peer-to-peer framework (development)
 gnunet-server - transitional dummy package
Closes: 765293
Changes:
 gnunet (0.10.1-2) unstable; urgency=medium
 .
   * Put the upstream signing key in debian/upstream/signing-key.asc and remove
 debian/source/include-binaries.
   * debian/control: update homepage as www.gnunet.org does not work anymore.
   * Fix FTBFS on kfreebsd (Closes: #765293). Thanks to Steven Chamberlain for
 testing it.
 + Add a patch to check properly the existence of malloc_np.h.
 + debian/rules: remove the file selection on kfreebsd as all binaries are
   built now.
   * debian/rules: use debhelpers -indep and -arch targets to make sure nothing
 is built unnecessary on an arch-indep build.
Checksums-Sha1:
 b687d71f1319a36dbb23356b91e6f58560e1b241 2611 gnunet_0.10.1-2.dsc
 21ff92ad1940ce35ca5b40fbb5c38be06462ab01 37816 gnunet_0.10.1-2.debian.tar.xz
 93f08b7f9cf247f1ed556a42b8a46f4dc7289bff 111962 gnunet-client_0.10.1-2_all.deb
 d74c2ee994b224ee285b66be5131ce4becc3b5fd 111962 gnunet-common_0.10.1-2_all.deb
 a89334ccadc019938fd604161dad5656af0

Bug#725714: Partial fix using hw-setup for the missing firmware problem in d-i?

[Ben Hutchings]

On Wed, 2014-10-15 at 22:39 +0200, Petter Reinholdtsen wrote:
> [Ben Hutchings]
> > Again, this is not a workaround, this is the only fix there will be for
> > that bug.  The only thing that may change in the kernel to make this
> > easier is that it will do structured logging so in theory you don't need
> > to use grep, cut, etc.  In practice, as this is all shell scripts, you
> > will probably have to do similar grepping to read the structured log
> > information.
> 
> I reworded the comment. :)
> 
> > dmesg | sed -rn 's/^(\[[^]]*\] )?([^ ]+) [^ ]+: firmware: failed to load 
> > ([^ ]+) .*/\2 \3/p' > $fwlist
> > 
> > This avoids using magic numbers; also we don't have to assume that log
> > timestamps are enabled.
> 
> Good idea.  Included in the patch.
> 
> > Keep the 'in'.
> 
> Ah, fixed.
> 
> I've tested the patch just now, and it seem to be working as it
> should, so I committed it into the hw-detect git repository.

Thanks; glad to have this finally fixed. :-)

Ben.

-- 
Ben Hutchings
Horngren's Observation:
   Among economists, the real world is often a special case.


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

Bug#765037: openjdk-7: apt tool is needed by reverse dependencies

[Emmanuel Bourg]

This change also breaks jitsi.


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

Processed: severity of 765475 is important

[Debian Bug Tracking System]

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

> severity 765475 important
Bug #765475 [chromium] Still missing API into chromium browser
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

[Debian Bug Tracking System]

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

> block 759835 by 765037
Bug #759835 [src:jitsi] jitsi: FTBFS:   [javadoc] 
/«PKGBUILDDIR»/lib/src/jsip/src/gov/nist/javax/sip/header/AuthenticationHeader.java:443:
 error: unmappable character for encoding ASCII
759835 was not blocked by any bugs.
759835 was not blocking any bugs.
Added blocking bug(s) of 759835: 765037
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
759835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759835
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: notfound 759146 in 0.2.7.1-3

[Debian Bug Tracking System]

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

> notfound 759146 0.2.7.1-3
Bug #759146 {Done: Olly Betts } [phatch] [phatch] Phatch 
doesn't work with python-imaging and python-pil 2.5.1-x or 2.5.3-x
No longer marked as found in versions phatch/0.2.7.1-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
759146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759146
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#763855: marked as done (xchat FTBFS on ppc64el, hurd, kfreebsd)

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 21:33:38 +
with message-id 
and subject line Bug#763855: fixed in xchat 2.8.8-7.2
has caused the Debian Bug report #763855,
regarding xchat FTBFS on ppc64el, hurd, kfreebsd
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.)


-- 
763855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xchat
Version: 2.8.8-7.1
Severity: serious

Hi,

xchat FTBFS on three different architectures, one of them being a
release architecture it built before. The error is the same everywhere:
> /usr/bin/ld: plugin-tray.o: undefined reference to symbol 'g_module_symbol'
while linking xchat

That seems to come from linktool not using the right DSOs. If I copy
the linking command from the x86-build and do that by hand, I could
continue to build the binary packages.


Andi
--- End Message ---
--- Begin Message ---
Source: xchat
Source-Version: 2.8.8-7.2

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

Debian distribution maintenance software
pp.
Jonathan Wiltshire  (supplier of updated xchat package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 13 Oct 2014 20:56:21 +0100
Source: xchat
Binary: xchat xchat-common
Architecture: source all amd64
Version: 2.8.8-7.2
Distribution: unstable
Urgency: medium
Maintainer: Davide Puricelli (evo) 
Changed-By: Jonathan Wiltshire 
Description:
 xchat  - IRC client for X similar to AmIRC
 xchat-common - Common files for X-Chat
Closes: 726132 763855
Changes:
 xchat (2.8.8-7.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Don't strip -lgmodule-2.0 from RDYNAMIC_LIBS. Patch from
 Svante Signell 
 (Closes: #726132, #763855)
Checksums-Sha1:
 46c22bfb07d1af76f4f9fbaca96269f91f190acd 2056 xchat_2.8.8-7.2.dsc
 74e58541f9afe156148ce95fcbd7d6058596f96d 81576 xchat_2.8.8-7.2.debian.tar.xz
 e05e1b6182161dad02eda13db894ffa86e7bf53c 546854 xchat-common_2.8.8-7.2_all.deb
 5e9bab6becb84953c3efea954a7b69f85d53f23a 293768 xchat_2.8.8-7.2_amd64.deb
Checksums-Sha256:
 37795b939f67d600243127cada508833cecee297e11aba752af147b38280d5e5 2056 
xchat_2.8.8-7.2.dsc
 052e2c4f3ffe33cd1b2f3b4b71d96018dacb95b915c262d7aff54b8b3c3f4035 81576 
xchat_2.8.8-7.2.debian.tar.xz
 79ff429f7494a303a2177aaf754e346645483e31a6e6bee2da26176a5377bf78 546854 
xchat-common_2.8.8-7.2_all.deb
 45db84a5fd0f815ce9204e5388debea50e3a9f4c2a8b4245059f383064584b30 293768 
xchat_2.8.8-7.2_amd64.deb
Files:
 bd804e0689586ccbd90c71260df7ac14 2056 net optional xchat_2.8.8-7.2.dsc
 bc673451b6786d605480fedf05295689 81576 net optional 
xchat_2.8.8-7.2.debian.tar.xz
 b44ad0efdda70d9896e8eef011cbdd21 546854 net optional 
xchat-common_2.8.8-7.2_all.deb
 7f80a8f081301239b38a1e95da683985 293768 net optional xchat_2.8.8-7.2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJUPDKFAAoJEFC7AtTIpr9ho6MP/RckNrc3bRgm4jy+OxBeSJPr
M7TtMoqbus6SdpplAJ4lXBd0sZS1g70fsIvAWzSOJm98+gfI5QSyUrMKga8TeENe
3Mqnz4CQMQwS6b2qTGcEBM89XdERKCTa2PTHVFcpD4K6mVzHt02F5MBs/1svmQdr
UOCc4YcVrJic23d4Ya8h91XvrKWlH6ByEkbbLAZ1D64fWwwCfmV0HyneAxKdyy/Q
H4Ear4G4RKYjSD23vCKjNdjcr4N8H182ZGDxnaVDnd4/Gu1XQYhJzxw/HhFce3rP
qm6P1J870q3GeNxO6FCapGhihpHyfrXh3mjkZvfYx8KMofqp09QcG14/j6be65Tx
LgXs6n8r9W48ARiHaxaxwBPyTkPA7qWp9pwAWXR+MWtDLSnm2Gn0SJA1x1ZF2fDB
9wRvmOTP+c+tXXUqy0gIrxJm7eeg86nyMEY9pqLOnXJExRH0wSbMBPhzQZBF6LQG
YVfC1x5O0VpXWOYSRxOvV/vkdsDeUb0u9PKZeZOyYVqv0AIHlOba4FPP0L3THa9I
HFUskLgMNHzj5XHdkpdOX+T/UzTa9WwO2CcQhF3v4G4fn8zEbDrx+niwODXn8Xhc
+gsYxOlRLgHEBO1MalphJpZYgrX/4dZbR3I4r4yG3yym0iVVi1AoO6ALKQBBd+tU
s7diYhFsUKv2dqIrUlWU
=LYkG
-END PGP SIGNATURE End Message ---

Bug#765163: marked as done (lua-lgi: FTBFS: regress.c:2:20: fatal error: config.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 21:29:37 +
with message-id 
and subject line Bug#765163: fixed in lua-lgi 0.8.0-2
has caused the Debian Bug report #765163,
regarding lua-lgi: FTBFS: regress.c:2:20: fatal error: config.h: No such file 
or directory
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.)


-- 
765163: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765163
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lua-lgi
Version: 0.8.0-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> cc -fPIC   -pthread -I/usr/include/cairo -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng12 
> -I/usr/include/gobject-introspection-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -g -O2 -fstack-protector-strong 
> -Wformat -Werror=format-security -c -o regress.o 
> /usr/share/gobject-introspection-1.0/tests/regress.c
> /usr/share/gobject-introspection-1.0/tests/regress.c:2:20: fatal error: 
> config.h: No such file or directory
>  #include "config.h"
> ^
> compilation terminated.
> make[2]: *** [regress.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/10/12/lua-lgi_0.8.0-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Enrico Tassi  (supplier of updated lua-lgi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 15 Oct 2014 22:14:29 +0200
Source: lua-lgi
Binary: lua-lgi lua-lgi-dev lua-lgi-dbg
Architecture: source amd64
Version: 0.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Enrico Tassi 
Changed-By: Enrico Tassi 
Description:
 lua-lgi- Lua bridge to GObject based libraries
 lua-lgi-dbg - Lua bridge to GObject based libraries
 lua-lgi-dev - lgi development files for the Lua language
Closes: 765103 765163
Changes:
 lua-lgi (0.8.0-2) unstable; urgency=medium
 .
   * Patch to create, on the fly, an empty config.h.  Works around bug
   https://bugzilla.gnome.org/show_bug.cgi?id=737275
 and closes: #765103, #765163.
Checksums-Sha1:
 3a19d5d2f0ce3d0c15c78346ec30e9eaaa7c3d4f 2041 lua-lgi_0.8.0-2.dsc
 8611b896afca846216a3dc50d1e0a1da379a6297 4484 lua-lgi_0.8.0-2.debian.tar.xz
 6f2407be88e2aea456e3c1cda1497725d5c49e87 87776 lua-lgi_0.8.0-2_amd64.deb
 d30ac98b85b37fff82eeabea93f1a7d6db231484 192294 lua-lgi-dev_0.8.0-2_amd64.deb
 b99dc7e6dd58fc3def6e165a821e1b4c42b0ff22 153732 lua-lgi-dbg_0.8.0-2_amd64.deb
Checksums-Sha256:
 2b019ac68e632aa0899baf60e0e971e6eb52b17d7ca35aaf8f8b76dbccc2e978 2041 
lua-lgi_0.8.0-2.dsc
 166b0907a90988931cb8a7d5fd4c803c36be1c3f8ae5a73864073d760ff13e69 4484 
lua-lgi_0.8.0-2.debian.tar.xz
 a8bb5d336afb58116b4cab9ae487da672dc2378920f0b5c3d6a9eeb3b2446e8d 87776 
lua-lgi_0.8.0-2_amd64.deb
 4990ccd5204f534cb579fdcfb1ab685ec3908575f6ddf1b887dcf84443d9881f 192294 
lua-lgi-dev_0.8.0-2_amd64.deb
 a3dee826510e0332872fd04594d72ff3bf915b9e9af290a76a9fee5e1c9abe3e 153732 
lua-lgi-dbg_0.8.0-2_amd64.deb
Files:
 965efb7e4b1770a212bc5a5e9a0cd48b 2041 interpreters optional lua-lgi_0.8.0-2.dsc
 06716f49a6db80575368a3403cc0238f 4484 interpreters optional 
lua-lgi_0.8.0-2.debian.tar.xz
 e980680588c57a2b63ba57de4d9b5a03 87776 interpreters optional 
lua-lgi_0.8.0-2_amd64.deb
 dc39d85ec5c0665a1ff4bfde32afcac3 192294 libdevel optional 
lua-lgi-dev_0.8.0-2_amd64.deb
 23da1aee9673a34ebedc442b768d

Bug#765103: marked as done (lua-lgi: FTBFS - config.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 21:29:37 +
with message-id 
and subject line Bug#765103: fixed in lua-lgi 0.8.0-2
has caused the Debian Bug report #765103,
regarding lua-lgi: FTBFS - config.h: No such file or directory
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.)


-- 
765103: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lua-lgi
Version: 0.8.0-1
Severity: serious
Usertags: goto-cc

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

[...]
   debian/rules override_dh_auto_test
make[1]: Entering directory 
'/srv/jenkins-slave/workspace/sid-goto-cc-lua-lgi/lua-lgi-0.8.0'
if [ `dpkg-architecture -qDEB_BUILD_ARCH` != s390x ]; then \
  make -C tests all; \
  GI_TYPELIB_PATH=tests LD_LIBRARY_PATH=tests xvfb-run dh_auto_test; \
fi
make[2]: Entering directory 
'/srv/jenkins-slave/workspace/sid-goto-cc-lua-lgi/lua-lgi-0.8.0/tests'
pkg-config --exists 'gio-2.0 cairo cairo-gobject gobject-introspection-1.0 
gmodule-2.0 libffi >= 0.10.8' --print-errors
touch .depcheck
cc -fPIC   -pthread -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng12 
-I/usr/include/gobject-introspection-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -c -o regress.o 
/usr/share/gobject-introspection-1.0/tests/regress.c
/usr/share/gobject-introspection-1.0/tests/regress.c:2:20: fatal error: 
config.h: No such file or directory
 #include "config.h"
^
compilation terminated.
Makefile:67: recipe for target 'regress.o' failed
make[2]: *** [regress.o] Error 1
make[2]: Leaving directory 
'/srv/jenkins-slave/workspace/sid-goto-cc-lua-lgi/lua-lgi-0.8.0/tests'

Making target test for debian/lua5.2.dh-lua.conf
** lua dynamic (5.2) *
[...]
gireg   : FAILED 113 of 114 tests
marshal : all 1 tests passed.
corocbk : all 3 tests passed.
record  : all 1 tests passed.
gobject : all 14 tests passed.
glib: all 4 tests passed.
variant : all 15 tests passed.
dbus: all 2 tests passed.
gtk : all 21 tests passed.
cairo   : all 12 tests passed.
pango   : all 1 tests passed.
/usr/share/dh-lua/make/dh-lua.Makefile.single:288: recipe for target 
'test-lua-dynamic-real' failed
make[3]: *** [test-lua-dynamic-real] Error 1
/usr/share/dh-lua/make/dh-lua.Makefile.multiple:12: recipe for target 'test' 
failed
make[2]: *** [test] Error 1
dh_auto_test: make --no-print-directory -f 
/usr/share/dh-lua/make/dh-lua.Makefile.multiple test returned exit code 2
debian/rules:12: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
make[1]: Leaving directory 
'/srv/jenkins-slave/workspace/sid-goto-cc-lua-lgi/lua-lgi-0.8.0'
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 2


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

Best,
Michael


lua-lgi-build-log.txt.gz
Description: application/gunzip


pgpI5nMz9vNHi.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: lua-lgi
Source-Version: 0.8.0-2

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

Debian distribution maintenance software
pp.
Enrico Tassi  (supplier of updated lua-lgi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 15 Oct 2014 22:14:29 +0200
Source: lua-lgi
Binary: lua-lgi lua-lgi-dev lua-lgi-dbg
Architecture: source amd64
Version: 0.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Enrico Tassi 
Changed-By: Enrico Tassi 
Description:
 lua-lgi- Lua bridge to GObject based libraries
 lua-lgi-dbg - Lua bridge to GObject based libraries
 lua-lgi-dev - lgi development files for the Lua language
Closes: 765103 765163
Changes:
 lua-lgi (0.8.0-2) unstable; urgency=medium
 .
   * Patch to create

Bug#725714: Partial fix using hw-setup for the missing firmware problem in d-i?

[Petter Reinholdtsen]

[Joey Hess]
> Looking at dmesg might fail if something is spamming it and the message
> drops out of the ring buffer. Maybe it would be better to look in syslog?

I am aware of it.  I do believe the new method is a huge step forward
and am unsure if it is worth it to use the syslog instead.  If
something is spamming dmesg, the syslog will become very large and the
grep very slow, and that might be a bigger problem than some missed
firmware requests.

> The modinfo check, which has been removed, avoids that problem,
> although it doesn't work for some modules that don't load at all
> when missing firmware. I don't know how many modules have that
> behavior, but if most of them don't, the modinfo check seems worth
> keeping as more robust for the modules it does work for.

My testing on four different laptop types indicated that the modinfo
check never found anything the dmesg check didn't, and most often
missed the interesting wifi card modules.  This was the background for
dropping the modinfo method.

-- 
Happy hacking
Petter Reinholdtsen


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

Bug#725714: Partial fix using hw-setup for the missing firmware problem in d-i?

[Joey Hess]

Petter Reinholdtsen wrote:
> Here is another draft, this time also providing the module name.  I
> dropped the code looking in /proc/modules, as three ways to find
> firmware seem a bit too much.

Looking at dmesg might fail if something is spamming it and the message
drops out of the ring buffer. Maybe it would be better to look in syslog?

The modinfo check, which has been removed, avoids that problem,
although it doesn't work for some modules that don't load at all when
missing firmware. I don't know how many modules have that behavior, but
if most of them don't, the modinfo check seems worth keeping as more
robust for the modules it does work for.

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#764310: manpages-dev and libcerf-doc: error when trying to install together

[Eugen Wintersberger]

Hi, 

On Mon, 2014-10-13 at 21:40 +0200, Simon Paillard wrote: 
> Hi,
> 
> On Thu, Oct 09, 2014 at 10:27:23AM +0200, Joachim Wuttke wrote:
> > As upstream maintainer of libcerf, I would like to express
> > a clear preference for solving the conflict by withdrawing
> > cerf.3 and cerfc.3 from manpages-dev.
> 
> Next manpages Debian upload will stop installing both cerf.3 cerfc.3.

Ok - this issue seems to be solved.

> 
> But there is a naming conflict, as the functions names are reserved by C99.

Good point. I have no idea how to proceed with this. Although, I would
agree with Joachim (see below) that for the time beeing libcerf can be
considered a complement to glibc. In addition, once glibc provides the
functionality the C99 standard demands, the transition from libcerf to
glibc would be easy as the names are function names are already correct.

Ok - this is my pragmatic point of view. Is there an official policy how
to deal with such issues?

> 
> > On the contrary, libcerf complements glibc in providing a missing
> > implementation.  Should glibc one day provide an official implementation,
> > then the two functions will be immediately withdrawn from libcerf.

regards
  Eugen



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

Processed: Re: [request-tracker-maintainers] Bug#765477: Bug#765477: Bug#765477: request-tracker4: FTBFS - unexpected warnings

[Debian Bug Tracking System]

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

> reassign 765477 libhtml-mason-perl
Bug #765477 [request-tracker4] request-tracker4: FTBFS - unexpected warnings
Bug reassigned from package 'request-tracker4' to 'libhtml-mason-perl'.
No longer marked as found in versions request-tracker4/4.2.7-1.
Ignoring request to alter fixed versions of bug #765477 to the same values 
previously set
> retitle 765477 libhtml-mason-perl: CGI.pm warnings about param()
Bug #765477 [libhtml-mason-perl] request-tracker4: FTBFS - unexpected warnings
Changed Bug title to 'libhtml-mason-perl: CGI.pm warnings about param()' from 
'request-tracker4: FTBFS - unexpected warnings'
> affects 765477 request-tracker4
Bug #765477 [libhtml-mason-perl] libhtml-mason-perl: CGI.pm warnings about 
param()
Added indication that 765477 affects request-tracker4
> forwarded 765477 https://rt.cpan.org/Public/Bug/Display.html?id=99520
Bug #765477 [libhtml-mason-perl] libhtml-mason-perl: CGI.pm warnings about 
param()
Ignoring request to change the forwarded-to-address of bug#765477 to the same 
value
> tags 765477 + patch upstream
Bug #765477 [libhtml-mason-perl] libhtml-mason-perl: CGI.pm warnings about 
param()
Added tag(s) upstream and patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
765477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765477
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#765477: [request-tracker-maintainers] Bug#765477: Bug#765477: Bug#765477: request-tracker4: FTBFS - unexpected warnings

[Dominic Hargreaves]

reassign -1 libhtml-mason-perl
retitle -1 libhtml-mason-perl: CGI.pm warnings about param()
affects -1 request-tracker4
forwarded -1 https://rt.cpan.org/Public/Bug/Display.html?id=99520
tags -1 + patch upstream
thanks

On Wed, Oct 15, 2014 at 03:55:46PM -0400, Kevin Falcone wrote:
> On Wed, Oct 15, 2014 at 03:07:38PM -0400, Kevin Falcone wrote:
> > 
> > I'll open an rt.cpan.org bug later if I have a chance (I'm not sure if
> > you also need a bug against the libhtml-mason-perl package in sid).
> 
> I've opened
> https://rt.cpan.org/Public/Bug/Display.html?id=99520
> 
> with a naive patch that causes RT to pass tests for me locally.

Thanks for the investigation and patch! Setting bug metadata
appropriately.

Cheers,
Dominic.


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

Bug#765526: libc6: Segfault after upgrade

[Botka Istvan]

Package: libc6
Version: 2.13-38+deb7u5
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I've upgraded libc6, libc-bin libc6-amd64 packages from
libc6_2.13-38+deb7u4 to libc6_2.13-38+deb7u5 and I've got a lot of segfault.
-http backend of apt
-mysql
-postfix

I had to downgrade the libc-bin, libc6, libc6-amd64 packages to
2.13-38+deb7u4 level to make my system works again.




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

Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages libc6 depends on:
ii  libc-bin  2.13-38+deb7u4
ii  libgcc1   1:4.7.2-5

Versions of packages libc6 recommends:
ii  libc6-i686  2.13-38+deb7u5

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.49
pn  glibc-doc  
ii  locales2.13-38+deb7u5

-- debconf information:
* glibc/upgrade: true
  glibc/disable-screensaver:
  glibc/restart-failed:
* glibc/restart-services:
* libraries/restart-without-asking: true


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

Bug#725714: Partial fix using hw-setup for the missing firmware problem in d-i?

[Petter Reinholdtsen]

[Ben Hutchings]
> Again, this is not a workaround, this is the only fix there will be for
> that bug.  The only thing that may change in the kernel to make this
> easier is that it will do structured logging so in theory you don't need
> to use grep, cut, etc.  In practice, as this is all shell scripts, you
> will probably have to do similar grepping to read the structured log
> information.

I reworded the comment. :)

> dmesg | sed -rn 's/^(\[[^]]*\] )?([^ ]+) [^ ]+: firmware: failed to load ([^ 
> ]+) .*/\2 \3/p' > $fwlist
> 
> This avoids using magic numbers; also we don't have to assume that log
> timestamps are enabled.

Good idea.  Included in the patch.

> Keep the 'in'.

Ah, fixed.

I've tested the patch just now, and it seem to be working as it
should, so I committed it into the hw-detect git repository.

-- 
Happy hacking
Petter Reinholdtsen


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

Bug#765524: libmagics++-dev: Changes in headers cause FTBFS in metview

[Alastair McKinstry]

Package: libmagics++-dev
Version: 2.22.7.dfsg.1-2
Severity: serious
Justification: Policy 8.4

This RC bug is to prevent this version from progressing to testing;
the new build system in this version breaks the include files that
are shipped such that other packages (metview) will not build

In particular see #765130

-- System Information:
Debian Release: 7.6
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: powerpc (ppc)

Kernel: Linux 2.6.32-5-powerpc
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to ga_IE.UTF-8)
Shell: /bin/sh linked to /bin/bash


-- 
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#756777: Dirac FTBFS on armhf and blocks migration of arm64 fix.

[Debian Bug Tracking System]

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

> Found 756777 1.0.2-6
Bug #756777 [src:dirac] dirac: FTBFS on armhf
Marked as found in versions dirac/1.0.2-6.
> Thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
756777: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756777
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#756777: Dirac FTBFS on armhf and blocks migration of arm64 fix.

[peter green]

Found 756777 1.0.2-6
Thanks

I've just tested and found that building with gcc/g++ 4.8 fixes the build. 
Using 4.8 also requires switching from strong to regular stack protector. This

can be done with the following

export 
CC=gcc-4.8  
export 
CXX=g++-4.8 
export 
DEB_CFLAGS_MAINT_STRIP=-fstack-protector-strong 
export 
DEB_CFLAGS_MAINT_APPEND=-fstack-protector   
export 
DEB_CXXFLAGS_MAINT_STRIP=-fstack-protector-strong   
export DEB_CXXFLAGS_MAINT_APPEND=-fstack-protector


If noone proposes a better soloution in the next couple of days I'll 
wrap this

in appropriate conditional logic and upload it as a NMU.

Sebastian Ramacher wrote:

On 2014-10-13 03:29:19, peter green wrote:
  

Found 756777 1.0.2-6
Thanks


| Checking encode and decode of colourbars
|
|   2: colourbars  FAILED (colourbars.at:7)
|
  

I've just reproduced this locally with both sid's version in sid and
jessie's version in jessie. So this doesn't appear to be related to the
change in the sid package but related to some change in the build
environment. If I had to guess i'd say a computer



I think it's a toolchain bug. I did debug the issue some time after
filing the bug report, but forgot to report my findings to the bug. The
same version built fine in a wheezy chroot on harris, but fails in a
unstable chroot.

Here is the backtrace I got at the time:

#0  dirac::PictureCompressor::SelectQuantisers (this=this@entry=0x207ccc4, coeff_data=..., bands=..., lambda=lambda@entry=6.25, est_bits=..., 
cb_mode=QUANT_SINGLE, pp=..., csort=csort@entry=dirac::Y_COMP) at picture_compress.cpp:632
#1  0x00036d94 in dirac::PictureCompressor::CodeResidue (this=this@entry=0x207ccc4, my_buffer=..., pnum=, 
p_picture_byteio=p_picture_byteio@entry=0x20e4ae8) at picture_compress.cpp:449

#2  0x000232ee in dirac::SequenceCompressor::CompressNextPicture 
(this=0x207cba8) at seq_compress.cpp:447
#3  0x00018e72 in DiracEncoder::CompressNextPicture (this=this@entry=0x207c400) 
at dirac_encoder.cpp:607
#4  0x0001b122 in CompressNextPicture (this=0x207c400) at dirac_encoder.cpp:1141
#5  dirac_encoder_output (encoder=0x207c240) at dirac_encoder.cpp:1106
#6  0x00014b20 in main (argc=, argv=) at 
encmain.cpp:1234

The offending line is "est_bits[b] = SelectMultiQuants( coeff_data ,
bands , b, lambda, ...". Printing b (or another index somewhere up the
call trace - I don't remember exactly) immediately before this line,
makes the crash go away. This makes me think gcc fails at optimizing the
code and generates broken output.

I didn't debug it any further.

Cheers
  



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

Bug#765174: [PATCH] Don't call modperl_threaded_mpm() et al. from XS code

[Steve Hay]

On 15 October 2014 09:20, Niko Tyni  wrote:
> r594345 (and later r1241983 and r1245916, all merged into trunk with
> r1602105) modified modperl_trace() to call functions that are provided
> by mod_perl.c. However, the same code is compiled into the APR XS module
> without mod_perl.o linkage, so we end up with missing symbols in APR.so.
>
> % objdump -T blib/arch/auto/APR/APR.so|grep UND|grep modperl
>   D  *UND*    
> modperl_is_running
>   D  *UND*    
> modperl_threaded_mpm
>   D  *UND*    
> modperl_threads_started
>
> For the most part these missing symbols don't matter when modperl_trace()
> doesn't actually get called, but CPAN modules like Apache-Gallery that
> use APR and run their suites with PERL_DL_NONLAZY=1 now fail their tests
> because of this.
>
> Guard the problematic invocations with #ifndef MP_IN_XS, which is
> defined for the XS module builds.
>
> Bug-Debian: https://bugs.debian.org/765174
> ---
>  src/modules/perl/modperl_common_log.c | 2 ++
>  1 file changed, 2 insertions(+)
>

Thanks, committed in revision 1632172.


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

Bug#759745: gdm3: Unable to login post-upgrade without systemd-sysv installed

[Michael Biebl]

Hi,

Am 15.10.2014 um 22:11 schrieb Michael Biebl:
> Am 15.10.2014 um 21:40 schrieb Cameron Norman:
>> Hello,
>>
>> A bug was recently fixed in cgmanager that may have caused the issue you
>> are describing. Does upgrading your cgmanager and systemd-shim versions
>> to those in Sid (0.33-2 and 8-3, respectively) solve this issue? If you
>> are unable to upgrade those packages, you can try to add
>> `cgroup_enable=memory` to the kernel command line and see if that fixes
>> the issue.
> 
> And unfortunately, no, with the latest cgmanager and systemd-shim, gdm
> still fails to start.

Ok, I need to take that back.
While gdm failed the first time I rebooted with the new
cgmanager/systemd-shim, I did a couple more reboots and now it starts
properly and I can login successfully.





signature.asc
Description: OpenPGP digital signature

Bug#765293: gnunet: FTBFS on kfreebsd-*: error: malloc_np.h: No such file or directory

[Bertrand Marc]

Le 14/10/2014 23:17, Steven Chamberlain a écrit :
> Yes it does build fine with those lines removed.  (build log attached)

Thanks a lot ! I have just uploaded a new revision to mentors, this
should be fixed in a couple of days.

Regards,
Bertrand




signature.asc
Description: OpenPGP digital signature

Bug#759745: gdm3: Unable to login post-upgrade without systemd-sysv installed

[Michael Biebl]

Hi Cameron

Am 15.10.2014 um 21:40 schrieb Cameron Norman:
> Hello,
> 
> A bug was recently fixed in cgmanager that may have caused the issue you
> are describing. Does upgrading your cgmanager and systemd-shim versions
> to those in Sid (0.33-2 and 8-3, respectively) solve this issue? If you
> are unable to upgrade those packages, you can try to add
> `cgroup_enable=memory` to the kernel command line and see if that fixes
> the issue.

This issue is trivial to reproduce, so it's not strictly necessary to
ask the bug submitter.

And unfortunately, no, with the latest cgmanager and systemd-shim, gdm
still fails to start.

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



signature.asc
Description: OpenPGP digital signature

Bug#765352: marked as done (wpa: arbitrary command execution via action scripts)

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 19:53:22 +
with message-id 
and subject line Bug#765352: fixed in wpa 2.3-1
has caused the Debian Bug report #765352,
regarding wpa: arbitrary command execution via action scripts
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.)


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

Hi,
the following vulnerability was published for wpa. It affects both
wpa-supplicant and hostapd:

CVE-2014-3686[0]:
action script execution vulnerability

>From https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-3686:
> Jouni Malinen discovered that a string supplied from a remote device could
> be supplied to a system() call in wpa_cli or hostapd_cli when running an
> action script (with the "-a" option), resulting in arbitrary command
> execution. This issue could also be triggered by an attacker within radio
> range.
> 
> Patches are available from the following:
> http://w1.fi/security/2014-1/

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3686
https://security-tracker.debian.org/tracker/CVE-2014-3686
Please adjust the affected versions in the BTS as needed.


-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/
--- End Message ---
--- Begin Message ---
Source: wpa
Source-Version: 2.3-1

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

Debian distribution maintenance software
pp.
Stefan Lippers-Hollmann  (supplier of updated wpa package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Oct 2014 21:29:37 +0200
Source: wpa
Binary: hostapd wpagui wpasupplicant wpasupplicant-udeb
Architecture: source amd64
Version: 2.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian wpasupplicant Maintainers 

Changed-By: Stefan Lippers-Hollmann 
Description:
 hostapd- IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator
 wpagui - graphical user interface for wpa_supplicant
 wpasupplicant - client support for WPA and WPA2 (IEEE 802.11i)
 wpasupplicant-udeb - Client support for WPA and WPA2 (IEEE 802.11i) (udeb)
Closes: 763775 765352
Changes:
 wpa (2.3-1) unstable; urgency=medium
 .
   * New upstream release:
 - fixed by the new upstream version:
   + wpa: arbitrary command execution via action scripts (Closes: #765352).
 wpasupplicant: fixed wpa_cli action script execution to use more
 robust mechanism (CVE-2014-3686).
 hostapd: fixed hostapd_cli action script execution to use more robust
 mechanism (CVE-2014-3686).
   + wpasupplicant: MAC addressing changing broken after updating to 2.2-1
 (Closes: #763775).
   + drop ap_config_c_fix-typo-for-capabilities, applied upstream.
 - backport "Include ieee802_11_common.c in wpa_supplicant build
   unconditionally" from HEAD, to fix a newly introduced FTBS on, at least,
   kfreebsd.
   * bump standards version to 3.9.6, no changes necessary.
Checksums-Sha1:
 f84a1b26453e639ea01c6a966ccc40428d235e46 2468 wpa_2.3-1.dsc
 7737a4306195ffaba8bb6777e2ede5a4a25e3ca0 1735544 wpa_2.3.orig.tar.xz
 5b59f88d07e341415f289b9ca7b15bdc12fe5e10 74784 wpa_2.3-1.debian.tar.xz
 2c235bf77693c257e664ac0512e2e2a0bb898437 538478 hostapd_2.3-1_amd64.deb
 cceabab4b5a548db07a0cce2447fa08a458dceba 344460 wpagui_2.3-1_amd64.deb
 7a37dd4727c8e9ad319822b40f2e980055112794 915312 wpasupplicant_2.3-1_amd64.deb
 181c2790d71dc1d5c78008cc0b54918243af524f 222410 
wpasupplicant-udeb_2.3-1_amd64.udeb
Checksums-Sha256:
 818717ed777b906e9807098511b7415d2c2c5b68dbc96d224064713acd326d1b 2468 
wpa_2.3-1.dsc
 3d96034fa9e042c8aacb0812d8b2ab3d4c9aa6fc410802b4ee0da311e51c3eb3 1735544 
wpa_2.3.orig.tar.xz
 b05e2f75fbf9891df9681

Bug#765477: [request-tracker-maintainers] Bug#765477: Bug#765477: request-tracker4: FTBFS - unexpected warnings

[Kevin Falcone]

On Wed, Oct 15, 2014 at 03:07:38PM -0400, Kevin Falcone wrote:
> 
> I'll open an rt.cpan.org bug later if I have a chance (I'm not sure if
> you also need a bug against the libhtml-mason-perl package in sid).

I've opened
https://rt.cpan.org/Public/Bug/Display.html?id=99520

with a naive patch that causes RT to pass tests for me locally.

-kevin


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

Bug#764322: closed by Ondřej Surý (Bug#764322: fixed in libjpeg-turbo 1:1.3.1-6)

[Bill Allombert]

On Tue, Oct 07, 2014 at 09:24:36AM +, Debian Bug Tracking System wrote:
> Changes:
>  libjpeg-turbo (1:1.3.1-6) unstable; urgency=medium
>  .
>* Changes Breaks: libjpeg-progs to Conflicts: libjpeg-progs and drop
>  Replaces: libjpeg-progs (Closes: #764322)

For what it is worth, the Conflict does not alleviate the need for the
Replaces: since the file conflicts are resolved before the Conflicts are taken
into account.

If someone has installed libjpeg-progs in wheezy and try to install
libjpeg-turbo-progs they might still get a dpkg error (depending on
the installation order).

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


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

Processed: tagging 765477, bug 765477 is forwarded to https://rt.cpan.org/Public/Bug/Display.html?id=99520

[Debian Bug Tracking System]

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

> tags 765477 + confirmed
Bug #765477 [request-tracker4] request-tracker4: FTBFS - unexpected warnings
Added tag(s) confirmed.
> forwarded 765477 https://rt.cpan.org/Public/Bug/Display.html?id=99520
Bug #765477 [request-tracker4] request-tracker4: FTBFS - unexpected warnings
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Public/Bug/Display.html?id=99520'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
765477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765477
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#764318: marked as done (libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs)

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 21:42:14 +0200
with message-id <20141015194214.GA15545@yellowpig>
and subject line Re: Bug#764318: libjpeg-progs: trying to overwrite 
'/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs
has caused the Debian Bug report #764318,
regarding libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', 
also in libjpeg-turbo-progs
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.)


-- 
764318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjpeg-progs
Version: 1:1.3.1-3
Severity: grave
Justification: renders package unusable

libjpeg-progs can't be upgraded:

Unpacking libjpeg-progs (1:9a-2) over (1:1.3.1-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/libjpeg-progs_1%3a9a-2_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package 
libjpeg-turbo-progs 1:1.3.1-3
Processing triggers for man-db (2.7.0.2-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_amd64.deb

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

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

Versions of packages libjpeg-progs depends on:
ii  libjpeg-turbo-progs  1:1.3.1-3

libjpeg-progs recommends no packages.

libjpeg-progs suggests no packages.

-- debconf-show failed

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
On Tue, Oct 07, 2014 at 10:11:30AM +0200, Vincent Lefevre wrote:
> Package: libjpeg-progs
> Version: 1:1.3.1-3
> Severity: grave
> Justification: renders package unusable
> 
> libjpeg-progs can't be upgraded:
> 
> Unpacking libjpeg-progs (1:9a-2) over (1:1.3.1-3) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_amd64.deb (--unpack):
>  trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in 
> package libjpeg-turbo-progs 1:1.3.1-3
> Processing triggers for man-db (2.7.0.2-1) ...
> Errors were encountered while processing:
>  /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_amd64.deb

Hello Vincent,

As far as I understand this issue was fixed in libjpeg-turbo-progs 1:1.3.1-6

Thus, closing this report.
Cheers,
-- 
Bill. 

Imagine a large red swirl here. --- End Message ---

Bug#759745: gdm3: Unable to login post-upgrade without systemd-sysv installed

[Cameron Norman]

Hello,

A bug was recently fixed in cgmanager that may have caused the issue 
you are describing. Does upgrading your cgmanager and systemd-shim 
versions to those in Sid (0.33-2 and 8-3, respectively) solve this 
issue? If you are unable to upgrade those packages, you can try to add 
`cgroup_enable=memory` to the kernel command line and see if that fixes 
the issue.


Thanks for taking the time,
--
Cameron Norman

Processed: Re: Bug#765434: man-db install-triggers broken

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 dpkg
Bug #765434 [man-db] man-db install-triggers broken
Bug reassigned from package 'man-db' to 'dpkg'.
No longer marked as found in versions man-db/2.7.0.2-2.
Ignoring request to alter fixed versions of bug #765434 to the same values 
previously set

-- 
765434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765434
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#765434: man-db install-triggers broken

[Guillem Jover]

Control: reassign -1 dpkg

On Wed, 2014-10-15 at 15:45:57 +0200, Guillem Jover wrote:
> On Wed, 2014-10-15 at 08:42:57 +0200, Helmut Grohne wrote:
> > On Wed, Oct 15, 2014 at 08:24:13AM +0300, Antti Järvinen wrote:
> > > upgrade to man-db fails to install. According to error message it may be 
> > > that 
> > > the problem itself is in some other package or in dependencies between 
> > > the 
> > > packages. Output from "apt-get dist-upgrade" goes like this:
> > 
> > Failure to install or upgrade is a serious issue.
> > 
> > > Processing triggers for man-db (2.7.0.2-2) ...
> > > dpkg: cycle found while processing triggers:
> > >  chain of packages whose triggers are or may be responsible:
> > >   libgdk-pixbuf2.0-0:i386 -> doc-base
> > >  packages' pending triggers which are or may be unresolvable:
> > >   doc-base: /usr/share/doc-base
> > >   menu: /usr/share/menu
> > >   libgdk-pixbuf2.0-0:i386: 
> > > /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders
> > >   hal: /usr/share/hal/fdi
> > > dpkg: error processing package doc-base (--unpack):
> > >  triggers looping, abandoned
> > > ..
> > > 
> > > and man-db is left unconfigured. I have doc-base 0.10.6, menu 2.1.47, 
> > > libgdk-pixbuf2 2.31.1-2 and hal 0.5.14-8.
> > 
> > I guess that the bug is not in man-db though, because the fix for
> > similar packages was to switch from "interest" to "interest-noawait",
> > but man-db already uses the latter for a while. Thus I am inviting
> > Guillem Jover to look at the issue and reassign the bug.

> Thanks for the heads up. I'm checking right now if this is actually a
> trigger cycle, or if it's a problem with dpkg itself, which is checking
> cycles before depenendencies, and might be causing this. Something I
> didn't commit at the time because it was getting into infinite loops
> otherwise, but maybe that was with some other implementation, cannot
> remember now, doing the change and running some tests.
> 
> Will be reassigning to the correct package, later today.

Because I'm pretty sure this is not a problem in man-db, but I've not
been feeling well today, I'm preemtively reassigning it to dpkg for
now (to not block man-db from migrating), go to sleep, and finish the
testing with the patched dpkg tomorrow. If this happens to end up being
a problem somewhere else, I'll reassign accordingly.

Thanks,
Guillem


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

Bug#765475: Still missing API into chromium browser

[raphael]

Package: chromium
Version: 38.0.2125.101-2
Followup-For: Bug #765475

Hi,

Chromium complains on missing google API keys, which leads in non working 
flash, and surely other features.
Thanks

Raphael


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

Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to fr_FR.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages chromium depends on:
ii  libasound2   1.0.28-1
ii  libc62.19-11
ii  libcairo21.12.16-5
ii  libcap2  1:2.24-6
ii  libcups2 1.7.5-4
ii  libdbus-1-3  1.8.8-2
ii  libexpat12.1.0-6
ii  libfontconfig1   2.11.0-6.1
ii  libfreetype6 2.5.2-2
ii  libgdk-pixbuf2.0-0   2.31.1-2
ii  libglib2.0-0 2.42.0-2
ii  libgnome-keyring03.12.0-1
ii  libgtk2.0-0  2.24.25-1
ii  libharfbuzz0b0.9.35-1
ii  libjpeg8 8d1-1
ii  libnspr4 2:4.10.7-1
ii  libnspr4-0d  2:4.10.7-1
ii  libnss3  2:3.17.1-1
ii  libpango-1.0-0   1.36.8-2
ii  libpangocairo-1.0-0  1.36.8-2
ii  libpci3  1:3.2.1-3
ii  libspeechd2  0.8-6
ii  libspeex11.2~rc1.2-1
ii  libsrtp0 1.4.5~20130609~dfsg-1.1
ii  libstdc++6   4.9.1-16
ii  libudev1 215-5+b1
ii  libx11-6 2:1.6.2-3
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1
ii  libxdamage1  1:1.1.4-2
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.1-2
ii  libxi6   2:1.7.4-1
ii  libxml2  2.9.1+dfsg1-4
ii  libxrandr2   2:1.4.2-1
ii  libxrender1  1:0.9.8-1
ii  libxslt1.1   1.1.28-2+b1
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1
ii  xdg-utils1.1.0~rc1+git20111210-7.1

chromium recommends no packages.

Versions of packages chromium suggests:
ii  chromium-inspector  38.0.2125.101-2
ii  chromium-l10n   38.0.2125.101-2

-- no debconf information


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

Bug#765477: [request-tracker-maintainers] Bug#765477: request-tracker4: FTBFS - unexpected warnings

[Kevin Falcone]

On Wed, Oct 15, 2014 at 01:54:50PM +0100, Michael Tautschnig wrote:
> Version: 4.2.7-1
> 
> During a rebuild of all Debian packages in a clean sid chroot (using 
> cowbuilder
> and pbuilder) the build failed with the following error.
> # got warning: CGI::param called in list context from package 
> HTML::Mason::Utils line 48, this can lead to vulnerabilities. See the warning 
> in "Fetching the value or values of a single named parameter" at 
> /usr/share/perl5/CGI.pm line 425.

This looks like sid contains a new enough CGI.pm to have a warning
about param in list context (later than 4.05), but HTML::Mason hasn't
been updated to tell CGI.pm to be quiet.

https://packages.debian.org/unstable/perl/libcgi-pm-perl

HTML::Mason needs to patch in 
https://metacpan.org/pod/CGI#Fetching-the-value-or-values-of-a-single-named-parameter

Looking at the code, it doesn't fall prey to the vulnerability that I
can see.  

# @methods is some combination of param and url_param
# depending on submission method
my @values = map { $q->$_($key) } @methods;
$args{$key} = @values == 1 ? $values[0] : \@values;

local'ing in the CGI.pm "stop warning" variable seems fine.

Not something we can really fix at the RT level, but certainly
something that should end up being fixed in HTML::Mason.

I'll open an rt.cpan.org bug later if I have a chance (I'm not sure if
you also need a bug against the libhtml-mason-perl package in sid).

-kevin


pgpPuTA6EKOKL.pgp
Description: PGP signature

Bug#765505: marked as done ([libavcodec54] depends on libx264-123 which is not installable)

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 20:39:20 +0200
with message-id <20141015183920.ga8...@ramacher.at>
and subject line Re: Bug#765505: [libavcodec54] depends on libx264-123 which is 
not installable
has caused the Debian Bug report #765505,
regarding [libavcodec54] depends on libx264-123 which is not installable
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.)


-- 
765505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libavcodec54
Version: 6:9.10-2
Severity: serious

--- Please enter the report below this line. ---

libavcodec54] depends on libx264-123 which is not installable please
fix.

Greetings 

Andreas Hausmann

--- System information. ---
Architecture: amd64
Kernel:   Linux 3.16-2.towo.3-siduction-amd64

Debian Release: jessie/sid
  500 unstablehttp.debian.net 
  500 unstableftp.uni-stuttgart.de 
  500 unstablecdn.debian.net 
  500 stable  deb.opera.com 
  100 wheezy-backports ftp.debian.org 
  100 unstableftp.uni-stuttgart.de 
1 experimentalcdn.debian.net 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---
On 2014-10-15 19:04:27, Andreas Hausmann wrote:
> Package: libavcodec54
> Version: 6:9.10-2
> Severity: serious
> 
> --- Please enter the report below this line. ---
> 
> libavcodec54] depends on libx264-123 which is not installable please
> fix.

This package has been replaced by libavcodec55 and later libavcodec56
some time ago. Closing at is no longer in the archive.

Cheers
-- 
Sebastian Ramacher


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

Bug#765458: marked as done (apt: broken cdrom support, breaking installation from weekly ISO images)

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 18:33:50 +
with message-id 
and subject line Bug#765458: fixed in apt 1.1~exp7
has caused the Debian Bug report #765458,
regarding apt: broken cdrom support, breaking installation from weekly ISO 
images
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.)


-- 
765458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 1.0.9.2
Severity: serious
Tags: d-i
Justification: breaks d-i

[ X-D-Cc: debian-boot@, please keep it in the loop when replying. ]

Hi,

we received several bug reports about weekly installation images being
unable to find a kernel package to install on the freshly debootstrapped
system. I've been able to replicate this issue with apt 1.9.0.2. Various
checks performed within the /target chroot in the installer context
include:
 - sources.list is containing a well-formed cdrom deb line;
 - moving this file away and running "apt-cdrom add" adds it back;
 - apt-get update fails to proceed, and no Packages file ends up under
   /var/lib/apt/lists/, which explains d-i's failure to find a kernel
   package to install.
 - downgrading apt, apt-utils, libapt-inst1.5, libapt-pkg4.12 to their
   1.0.9.1 versions makes it possible to run apt-get update, even if
   its output isn't very encouraging (it's attached), and the expected
   Packages file pops up under /var/lib/apt/lists/;
 - since I don't want to screw up with apt's internal data under
   /var/lib/apt/, I can't confirm whether the output with downgraded
   *apt* packages is a result of various runs with the new and the old
   versions, or something else.

I'll try to figure out whether 801745284905e7962aa77a9f37a6b4e7fcdc19d0
and/or d916e2a93b798e29d342e9498266767c5be8e2a5 are responsible for
this, but the fact apt is pulled during debootstrap might make the
debian-cd tweak for including local packages a bit less straightforward
than usual.

Mraw,
KiBi.
Ign cdrom://[Debian GNU/Linux 8.0 _Jessie_ - Unofficial amd64 NETINST Binary-1 
20141015-09:12] jessie InRelease
Ign cdrom://[Debian GNU/Linux 8.0 _Jessie_ - Unofficial amd64 NETINST Binary-1 
20141015-09:12] jessie Release.gpg
Ign cdrom://[Debian GNU/Linux 8.0 _Jessie_ - Unofficial amd64 NETINST Binary-1 
20141015-09:12] jessie Release
Ign cdrom://[Debian GNU/Linux 8.0 _Jessie_ - Unofficial amd64 NETINST Binary-1 
20141015-09:12] jessie/main amd64 Packages/DiffIndex
Err cdrom://[Debian GNU/Linux 8.0 _Jessie_ - Unofficial amd64 NETINST Binary-1 
20141015-09:12] jessie/main amd64 Packages
  
Err cdrom://[Debian GNU/Linux 8.0 _Jessie_ - Unofficial amd64 NETINST Binary-1 
20141015-09:12] jessie/main amd64 Packages
  
Err cdrom://[Debian GNU/Linux 8.0 _Jessie_ - Unofficial amd64 NETINST Binary-1 
20141015-09:12] jessie/main amd64 Packages
  
Err cdrom://[Debian GNU/Linux 8.0 _Jessie_ - Unofficial amd64 NETINST Binary-1 
20141015-09:12] jessie/main amd64 Packages
  
Ign cdrom://[Debian GNU/Linux 8.0 _Jessie_ - Unofficial amd64 NETINST Binary-1 
20141015-09:12] jessie/main Translation-en
Err cdrom://[Debian GNU/Linux 8.0 _Jessie_ - Unofficial amd64 NETINST Binary-1 
20141015-09:12] jessie/main amd64 Packages
  Failed to stat - stat (2: No such file or directory)
W: Failed to fetch 
copy:/var/lib/apt/lists/partial/Debian%20GNU_Linux%208.0%20%5fJessie%5f%20-%20Unofficial%20amd64%20NETINST%20Binary-1%2020141015-09:12_dists_jessie_main_binary-amd64_Packages
  Failed to stat - stat (2: No such file or directory)

E: Some index files failed to download. They have been ignored, or old ones 
used instead.
--- End Message ---
--- Begin Message ---
Source: apt
Source-Version: 1.1~exp7

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

Debian distribution maintenance software
pp.
David Kalnischkies  (supplier of updated apt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 15 Oct 2014 20:12:15 +0200
Source: apt
Binary: apt libapt-pkg4.14 libapt-inst1.6 ap

Bug#765458: marked as done (apt: broken cdrom support, breaking installation from weekly ISO images)

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 18:18:55 +
with message-id 
and subject line Bug#765458: fixed in apt 1.0.9.3
has caused the Debian Bug report #765458,
regarding apt: broken cdrom support, breaking installation from weekly ISO 
images
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.)


-- 
765458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 1.0.9.2
Severity: serious
Tags: d-i
Justification: breaks d-i

[ X-D-Cc: debian-boot@, please keep it in the loop when replying. ]

Hi,

we received several bug reports about weekly installation images being
unable to find a kernel package to install on the freshly debootstrapped
system. I've been able to replicate this issue with apt 1.9.0.2. Various
checks performed within the /target chroot in the installer context
include:
 - sources.list is containing a well-formed cdrom deb line;
 - moving this file away and running "apt-cdrom add" adds it back;
 - apt-get update fails to proceed, and no Packages file ends up under
   /var/lib/apt/lists/, which explains d-i's failure to find a kernel
   package to install.
 - downgrading apt, apt-utils, libapt-inst1.5, libapt-pkg4.12 to their
   1.0.9.1 versions makes it possible to run apt-get update, even if
   its output isn't very encouraging (it's attached), and the expected
   Packages file pops up under /var/lib/apt/lists/;
 - since I don't want to screw up with apt's internal data under
   /var/lib/apt/, I can't confirm whether the output with downgraded
   *apt* packages is a result of various runs with the new and the old
   versions, or something else.

I'll try to figure out whether 801745284905e7962aa77a9f37a6b4e7fcdc19d0
and/or d916e2a93b798e29d342e9498266767c5be8e2a5 are responsible for
this, but the fact apt is pulled during debootstrap might make the
debian-cd tweak for including local packages a bit less straightforward
than usual.

Mraw,
KiBi.
Ign cdrom://[Debian GNU/Linux 8.0 _Jessie_ - Unofficial amd64 NETINST Binary-1 
20141015-09:12] jessie InRelease
Ign cdrom://[Debian GNU/Linux 8.0 _Jessie_ - Unofficial amd64 NETINST Binary-1 
20141015-09:12] jessie Release.gpg
Ign cdrom://[Debian GNU/Linux 8.0 _Jessie_ - Unofficial amd64 NETINST Binary-1 
20141015-09:12] jessie Release
Ign cdrom://[Debian GNU/Linux 8.0 _Jessie_ - Unofficial amd64 NETINST Binary-1 
20141015-09:12] jessie/main amd64 Packages/DiffIndex
Err cdrom://[Debian GNU/Linux 8.0 _Jessie_ - Unofficial amd64 NETINST Binary-1 
20141015-09:12] jessie/main amd64 Packages
  
Err cdrom://[Debian GNU/Linux 8.0 _Jessie_ - Unofficial amd64 NETINST Binary-1 
20141015-09:12] jessie/main amd64 Packages
  
Err cdrom://[Debian GNU/Linux 8.0 _Jessie_ - Unofficial amd64 NETINST Binary-1 
20141015-09:12] jessie/main amd64 Packages
  
Err cdrom://[Debian GNU/Linux 8.0 _Jessie_ - Unofficial amd64 NETINST Binary-1 
20141015-09:12] jessie/main amd64 Packages
  
Ign cdrom://[Debian GNU/Linux 8.0 _Jessie_ - Unofficial amd64 NETINST Binary-1 
20141015-09:12] jessie/main Translation-en
Err cdrom://[Debian GNU/Linux 8.0 _Jessie_ - Unofficial amd64 NETINST Binary-1 
20141015-09:12] jessie/main amd64 Packages
  Failed to stat - stat (2: No such file or directory)
W: Failed to fetch 
copy:/var/lib/apt/lists/partial/Debian%20GNU_Linux%208.0%20%5fJessie%5f%20-%20Unofficial%20amd64%20NETINST%20Binary-1%2020141015-09:12_dists_jessie_main_binary-amd64_Packages
  Failed to stat - stat (2: No such file or directory)

E: Some index files failed to download. They have been ignored, or old ones 
used instead.
--- End Message ---
--- Begin Message ---
Source: apt
Source-Version: 1.0.9.3

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

Debian distribution maintenance software
pp.
Michael Vogt  (supplier of updated apt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 15 Oct 2014 19:49:38 +0200
Source: apt
Binary: apt libapt-pkg4.12 libapt-inst1.5 apt-doc liba

Bug#764814: freecad downloads and executes code

[Yorik van Havre]

Hi Anton,

No, not directly... It's just an example of how to do it.
But Francesco doesn't like that solution, and I'm afraid we're
again embarking in a long-term issue if I apply the solution
from the patch.

I wonder if it's not easier to simply disable the
whole DXF import/export, and indicate to users how to add
it themselves.

Cheers
Yorik

Processed: Re: Bug#764814: freecad downloads and executes code

[Debian Bug Tracking System]

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

> forwarded 764814 http://freecadweb.org/tracker/view.php?id=1785
Bug #764814 [freecad] freecad downloads and executes code
Set Bug forwarded-to-address to 
'http://freecadweb.org/tracker/view.php?id=1785'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
764814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764814
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#764814: freecad downloads and executes code

[Anton Gladky]

forwarded 764814 http://freecadweb.org/tracker/view.php?id=1785
thanks

Yorik, there is a patch attached on FreeCAD bugtracker. Can it be
applied?

Thanks

Anton


2014-10-11 19:43 GMT+02:00 Yorik van Havre :
> Hi,
>
> This download happens the first time a user wants to use the DXF
> import/export feature. Since the license of our DXF exporter is GPL, and
> other components of FreeCAD prevent from linking to GPL code (namely
> OpenCasCade and Coin3D) (the whole story is another Debian bug), we found
> this trick of moving the dxf exporter out of the FreeCAD sources, and
> placing it online, so it can be downloaded by users the first time they need
> it. We control that resource ourselves (FreeCAD developers), so I don't
> think there is a higher risk than if we included that code directly in the
> source...
>
> I really don't know what else we can do... Would showing a dialog saying:
> "Warning! FreeCAD will now download python code for the dxf exporter"
> satisfy you?
>
> Yorik
>
>
>
> --
> debian-science-maintainers mailing list
> debian-science-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers


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

Bug#763006: Fix known

[Tomas Sandven]

So this will be fixed soon, or should I find myself another launcher?

- Tomas

On Mon, 13 Oct 2014 15:22:31 +1100 Christopher James Halse Rogers <
ch...@cooperteam.net> wrote:
> Ah, yes.
>
> The old “glib changes mutex semantics” gambit.
>
> I'll prepare an upload and run the pkg-cli-apps sponsoring gauntlet :)

Bug#765505: [libavcodec54] depends on libx264-123 which is not installable

[Andreas Hausmann]

Package: libavcodec54
Version: 6:9.10-2
Severity: serious

--- Please enter the report below this line. ---

libavcodec54] depends on libx264-123 which is not installable please
fix.

Greetings 

Andreas Hausmann

--- System information. ---
Architecture: amd64
Kernel:   Linux 3.16-2.towo.3-siduction-amd64

Debian Release: jessie/sid
  500 unstablehttp.debian.net 
  500 unstableftp.uni-stuttgart.de 
  500 unstablecdn.debian.net 
  500 stable  deb.opera.com 
  100 wheezy-backports ftp.debian.org 
  100 unstableftp.uni-stuttgart.de 
1 experimentalcdn.debian.net 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.


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

Bug#765135: marked as done (gcc-4.9: FTBFS: find: `java': No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 19:06:41 +0200
with message-id <543ea9a1.2000...@debian.org>
and subject line Re: Bug#765135: gcc-4.9: FTBFS: find: `java': No such file or 
directory
has caused the Debian Bug report #765135,
regarding gcc-4.9: FTBFS: find: `java': No such file or directory
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.)


-- 
765135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765135
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-4.9
Version: 4.9.1-16
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/«PKGBUILDDIR»/build/x86_64-linux-gnu/libjava'
> rm -f src.zip
> here=`pwd`; \
> ( \
>   ( cd ../../../src/libjava/classpath; \
>   find java gnu javax org sun -name '*.java' -print | \
>   while read file; do \
> echo "x-C" | sed -e 's/^.//'; \
> echo ../../../src/libjava/classpath; \
> echo $file; \
>   done ); \
>   ( cd ../../../src/libjava/classpath/external/sax; \
>   find org -name '*.java' -print | \
>   while read file; do \
> echo "x-C" | sed -e 's/^.//'; \
> echo ../../../src/libjava/classpath/external/sax; \
> echo $file; \
>   done ); \
>   ( cd ../../../src/libjava/classpath/external/relaxngDatatype; \
>   find org -name '*.java' -print | \
>   while read file; do \
> echo "x-C" | sed -e 's/^.//'; \
> echo ../../../src/libjava/classpath/external/relaxngDatatype; \
> echo $file; \
>   done ); \
>   ( cd ../../../src/libjava/classpath/external/w3c_dom; \
>   find org -name '*.java' -print | \
>   while read file; do \
> echo "x-C" | sed -e 's/^.//'; \
> echo ../../../src/libjava/classpath/external/w3c_dom; \
> echo $file; \
>   done ); \
>   ( cd classpath; \
> find gnu java -name '*.java' -print | \
> while read file; do \
> echo "x-C" | sed -e 's/^.//'; \
> echo `pwd`; \
> echo $file; \
>   done ); \
> ) | \
> jar -cfM@ $here/src.zip
> find: `java': No such file or directory
> here=`pwd`; \
> ( \
>   ( cd ../../../src/libjava; \
>   find gnu java -name '*.java' -print | \
>   while read file; do \
> echo "x-C" | sed -e 's/^.//'; \
> echo ../../../src/libjava; \
> echo $file; \
>   done ); \
> ) | \
> jar -ufM@ $here/src.zip
> make[2]: Leaving directory '/«PKGBUILDDIR»/build/x86_64-linux-gnu/libjava'
> touch stamps/05-build-javasrc-stamp
> dh_testdir
> dh_testroot
> dh_installdirs -pgcj-4.9-source usr/share/java 
> /usr/lib/jvm/java-1.5.0-gcj-4.9-amd64
> cp -p /«PKGBUILDDIR»/build/x86_64-linux-gnu/libjava/src.zip \
>debian/gcj-4.9-source/usr/share/java/libgcj-src-4.9.zip
> dh_link -pgcj-4.9-source \
>   usr/share/java/libgcj-src-4.9.zip \
>   /usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/src.zip
> debian/dh_doclink -pgcj-4.9-source gcc-4.9-base
> WARNING: removing doc directory  gcj-4.9-source
> debian/dh_rmemptydirs -pgcj-4.9-source
> dh_compress -pgcj-4.9-source
> dh_fixperms -pgcj-4.9-source
> dh_gencontrol -pgcj-4.9-source -- -v4.9.1-16 '-Vlibgcc:Version=1:4.9.1-16' 
> '-Vgcc:Version=4.9.1-16' '-Vgcc:EpochVersion=1:4.9.1-16' 
> '-Vgcc:SoftVersion=4.9' '-Vgdc:Version=4.9.1-16' '-Vgcj:Version=4.9.1-16' 
> '-Vgcj:SoftVersion=4.9' '-Vgcj:BaseVersion=4.9' '-Vgnat:Version=4.9.1-16' 
> '-Vbinutils:Version=2.24.51.20141001' '-Vdep:libgcc=libgcc1 (>= 1:4.9.1-16)' 
> '-Vdep:libgccdev=libgcc-4.9-dev (>= 4.9.1-16)' '-Vdep:libgccbiarch=lib32gcc1 
> (>= 1:4.9.1-16), libx32gcc1 (>= 1:4.9.1-16)' 
> '-Vdep:libgccbiarchdev=lib32gcc-4.9-dev (= ${gcc:Version}), libx32gcc-4.9-dev 
> (= ${gcc:Version})' '-Vdep:libc=libc6 (>= 2.11)' '-Vdep:libcdev=libc6-dev (>= 
> 2.13-5)' '-Vdep:libcbiarch=${shlibs:Depends}' 
> '-Vdep:libcbiarchdev=libc6-dev-i386 (>= 2.11), libc6-dev-x32 (>= 2.11)' 
> '-Vdep:libunwinddev=' '-Vdep:libcxxbiarchdev=lib32stdc++-4.9-dev (= 
> ${gcc:Version}), libx32stdc++-4.9-dev (= ${gcc:Version})' 
> '-Vdep:libcxxbiarchdbg=lib32stdc++6-4.9-dbg (>= ${gcc:Version}), 
> libx32stdc++6-4.9-dbg (>= ${gcc:Version})' '-Vdep:libgnat=' 
> '-Vdep:ecj=ecj-gcj, libecj-java-gcj (>= 3.5.1)' '-Vdep:libcloog=' 
> '-Vgcc:multilib=gcc-4.9-multilib' '-Vgxx:multilib=g++-4.9-multilib' 
> '-Vgobjc:multilib=gobjc-4.9-multilib' 
> '-Vgobjcxx:multilib=gobjc++-4.9-multilib' 
> '-Vgfortran:multilib=gfortran-4.9-multilib' '-Vdep:gold=binutils-gold (>= 
> 2.24.51.20141001)' '-Vdep:libgomp=libgomp1 (>= ${gcc:Version})' 
> '-Vdep:libitm=libitm1 (>= ${gcc:Version})' '-Vdep

Bug#764493: python-eventlet 0.15.2-1 to Sid/Jessie

[GCS]

Hi,

Thomas packaged v0.15.2 and uploaded to experimental. In my opinion it
should be uploaded to Sid and let migrate to Jessie.
The rationale behind is the following:
- it handles connection socket timeouts and contains several
bugfixes[1] without adding too much new code,
- it doesn't have any bugreports against experimental,
- it's part of Fedora 20 and 21, as well as RHEL7 as EPEL (extra
package repository)[2] without any problem.

The sslwrap.diff fix that Matthias adds in #764493 [3] still applies
however. Should I upload it or do you have objections?

Cheers,
Laszlo/GCS
[1] https://github.com/eventlet/eventlet/blob/master/NEWS
[2] http://pkgs.fedoraproject.org/cgit/python-eventlet.git
[3] https://bugs.debian.org/764493


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

Bug#765187: marked as done (blender: FTBFS on s390x, ppc64el, arm64: error: cast from 'ccl::uchar* {aka unsigned char*}' to 'CUdeviceptr {aka unsigned int}' loses precision [-fpermissive])

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 15:36:29 +
with message-id 
and subject line Bug#765187: fixed in blender 2.72+dfsg1-2
has caused the Debian Bug report #765187,
regarding blender: FTBFS on s390x, ppc64el, arm64: error: cast from 
'ccl::uchar* {aka unsigned char*}' to 'CUdeviceptr {aka unsigned int}' loses 
precision [-fpermissive]
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.)


-- 
765187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: blender
Version: 2.72+dfsg1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

blender failed to build on s390x, ppc64el and arm64 with:
| [  7%] Building CXX object 
intern/cycles/bvh/CMakeFiles/cycles_bvh.dir/bvh_node.cpp.o
| cd /«BUILDDIR»/blender-2.72+dfsg1/obj-s390x-linux-gnu/intern/cycles/bvh && 
/usr/bin/c++   -DBOOST_ALL_NO_LIB -DCCL_NAMESPACE_BEGIN="namespace ccl {" 
-DCCL_NAMESPACE_END=} -DHAVE_STDBOOL_H -DWITH_CUDA -DWITH_MULTI -DWITH_OPENCL 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE 
-D__BIG_ENDIAN__ -Wredundant-decls -Wall -Wno-invalid-offsetof 
-Wno-sign-compare -Wlogical-op -Winit-self -Wmissing-include-dirs 
-Wno-div-by-zero -Wtype-limits -Wuninitialized -Wundef -Wmissing-declarations 
-g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-D_FORTIFY_SOURCE=2  -D__STDC_CONSTANT_MACROS -fopenmp -pipe -fPIC 
-funsigned-char -fno-strict-aliasing -ffast-math -Werror=float-conversion 
-isystem /usr/include/OpenImageIO -isystem /usr/include/OpenEXR 
-I/«BUILDDIR»/blender-2.72+dfsg1/intern/cycles/bvh/. 
-I/«BUILDDIR»/blender-2.72+dfsg1/intern/cycles/bvh/../kernel 
-I/«BUILDDIR»/blender-2.72+dfsg1/intern/cycles/bvh/../kernel/svm 
-I/«BUILDDIR»/blender-2.72+dfsg1/intern/cycles/bvh/../render 
-I/«BUILDDIR»/blender-2.72+dfsg1/intern/cycles/bvh/../util 
-I/«BUILDDIR»/blender-2.72+dfsg1/intern/cycles/bvh/../device-o 
CMakeFiles/cycles_bvh.dir/bvh_node.cpp.o -c 
/«BUILDDIR»/blender-2.72+dfsg1/intern/cycles/bvh/bvh_node.cpp
| /«BUILDDIR»/blender-2.72+dfsg1/intern/cycles/device/device_cuda.cpp: In 
member function 'virtual void 
ccl::CUDADevice::mem_copy_from(ccl::device_memory&, int, int, int, int)':
| /«BUILDDIR»/blender-2.72+dfsg1/intern/cycles/device/device_cuda.cpp:358:78: 
error: cast from 'ccl::uchar* {aka unsigned char*}' to 'CUdeviceptr {aka 
unsigned int}' loses precision [-fpermissive]
|  (CUdeviceptr)((uchar*)mem.device_pointer + 
offset), size));
|   
^
| /«BUILDDIR»/blender-2.72+dfsg1/intern/cycles/device/device_cuda.cpp:86:21: 
note: in definition of macro 'cuda_assert'
|CUresult result = stmt; \
|  ^
| make[3]: *** 
[intern/cycles/device/CMakeFiles/cycles_device.dir/device_cuda.cpp.o] Error 1
| intern/cycles/device/CMakeFiles/cycles_device.dir/build.make:103: recipe for 
target 'intern/cycles/device/CMakeFiles/cycles_device.dir/device_cuda.cpp.o' 
failed
| make[3]: Leaving directory 
'/«BUILDDIR»/blender-2.72+dfsg1/obj-s390x-linux-gnu'
| make[2]: *** [intern/cycles/device/CMakeFiles/cycles_device.dir/all] Error 2

See
https://buildd.debian.org/status/fetch.php?pkg=blender&arch=s390x&ver=2.72+dfsg1-1&stamp=1412753922
for the build log.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: blender
Source-Version: 2.72+dfsg1-2

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

Debian distribution maintenance software
pp.
Matteo F. Vescovi  (supplier of updated blender 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: Wed, 15 Oct 2014 15:01:57 +0200
Source: blender
Binary: blender blender-data blender-dbg
Architecture: source all
Version: 2.72+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Matteo F. Vescovi 
Description:
 blender- Very fast and versatile 

Bug#763657: marked as done (src:fsharp: Sourceless binaries in bootstrap)

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 15:37:54 +
with message-id 
and subject line Bug#763657: fixed in fsharp 3.1.1.26+dfsg2-1
has caused the Debian Bug report #763657,
regarding src:fsharp: Sourceless binaries in bootstrap
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.)


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

Package: src:fsharp
Version: 3.1.1.26+dfsg-1
Severity: serious

Dear Maintainer,

A number of the bootstrap binaries shipped in the F# source package are
not actually shipped as source (they appear to be part of other Git
repositories)

lib/bootstrap/
└── 2.0
├── FSharp.PowerPack.Build.Tasks.dll
├── FSharp.PowerPack.targets
├── FSharp.SRGen.Build.Tasks.dll
├── FSharp.SRGen.targets
├── fslex.exe
├── fssrgen.exe
└── fsyacc.exe

As well as needing to resolve the issue of "bad" binaries in bootstrap, 
it would be great to get fsyacc etc packaged properly, as other F# 
libraries require them for building.


-- System Information:
Debian Release: jessie/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 
'trusty'), (100, 'trusty-backports')

Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-36-generic (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: fsharp
Source-Version: 3.1.1.26+dfsg2-1

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

Debian distribution maintenance software
pp.
Jo Shields  (supplier of updated fsharp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 15 Oct 2014 12:49:07 +0100
Source: fsharp
Binary: fsharp libfsharp-core4.3-cil libfsharp-data-typeproviders4.3-cil
Architecture: source all
Version: 3.1.1.26+dfsg2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian CLI Applications Team 

Changed-By: Jo Shields 
Description:
 fsharp - functional-first programming language - compiler for the CLI
 libfsharp-core4.3-cil - functional-first programming language - core runtime 
library
 libfsharp-data-typeproviders4.3-cil - functional-first programming language - 
data integration library
Closes: 763657
Changes:
 fsharp (3.1.1.26+dfsg2-1) unstable; urgency=medium
 .
   * [f28700d] Actually delete unneeded binaries from +dfsg.orig.tar.gz
   * [6ffdf50] Include various additional sources from F# Power Pack which
 are needed for rebuilding the bootstrap
 (Closes: #763657)
   * [e41e70e] Forcibly convert fsproj files to UNIX line endings, because
 Debian tools go to absolute hell on mixed-ending source trees in git,
 and we need to patch them
   * [1370647] Imported Upstream version 3.1.1.26+dfsg2
   * [537d87b] Compile missing pieces of bootstrap
   * [0a73b56] Fix cli-common-dev build-dep to be backport-friendly
   * [182eda4] Add bootstrap-required binaries to fsharp binary package
Checksums-Sha1:
 e8dd2c64065fed7991b9fe8318709a351149e255 1899 fsharp_3.1.1.26+dfsg2-1.dsc
 234faa58d425e7c5a1edd708a126f4c474aa7bf5 11416736 
fsharp_3.1.1.26+dfsg2.orig.tar.gz
 223314320c98b1cf00c70258ae1df6b52391 174496 
fsharp_3.1.1.26+dfsg2-1.debian.tar.xz
 10b42fcb5db01edd40473ab9ee1e0f97551ee075 2853220 
fsharp_3.1.1.26+dfsg2-1_all.deb
 5145d2cc654a53fd4a4f2713b900fd608137e58b 486356 
libfsharp-core4.3-cil_3.1.1.26+dfsg2-1_all.deb
 7c10f26b5ca0c23b7838a2a840edd56add793f13 107484 
libfsharp-data-typeproviders4.3-cil_3.1.1.26+dfsg2-1_all.deb
Checksums-Sha256:
 fc683e9476b7308f4c0b2548e71eef91786065ff42ef1bbbd8ef390458d526d7 1899 
fsharp_3.1.1.26+dfsg2-1.dsc
 c768dc7f13e0bcd9a9293ba02ced217404961a5931f824d5471d3e4b484ff7b0 11416736 
fsharp_3.1.1.26+dfsg2.orig.tar.gz
 5916977535d921b73591c60cd14a734ad57a6c171df0b4c884eed67da16e39f1 174496 
fsharp_3.1.1.26+dfsg2-1.debian.tar.xz
 fd8a5b5c9e11c39927eb5d78165de2d561a4146540fc3e1f7c532e920fb67ba2 2853220 
fsharp_3.1.1.26+dfsg2-1_all.deb
 1e

Processed: severity of 765460 is serious

[Debian Bug Tracking System]

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

> severity 765460 serious
Bug #765460 [gnome-shell-extensions] gnome-shell-extensions: apps-menu 
extension not working after upgrade to 3.14
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
765460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765460
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#761556: (no subject)

[Breno Leitao]

This error is also blocking ppc64el bootstrap, because it fails to compile as
described above.

The ppc64el build log could be found at:

https://buildd.debian.org/status/fetch.php?pkg=pg-reorg&arch=ppc64el&ver=1.1.9-2&stamp=1410770668


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

Bug#761210: [Pkg-electronics-devel] Bug#746003: Bug#760986: RM: guile-1.8 -- ROM; replaced by guile-2.0

[Jonathan Wiltshire]

On 2014-10-15 08:37, أحمد المحمودي wrote:

On Sun, Oct 12, 2014 at 09:51:12PM -0500, Rob Browning wrote:

> g-wrap [1]

Only response wrt 2.0 is a mention of an upload that's been in
experimental for two years, but no response from the maintainer:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761210

Last non-experimental upload: 2012-05


---end quoted text---

  Can't this be experimental version be NMU'ed for unstable ?
  Btw, there is a patch in Ubuntu against g-wrap upload that is in
  experimental:
  https://patches.ubuntu.com/g/g-wrap/g-wrap_1.9.14-2ubuntu1.patch


I don't think that a random NMU of an experimental package is a good 
idea, unless someone is going to step up to maintain it properly.


--
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

 i have six years of solaris sysadmin experience, from
8->10. i am well qualified to say it is made from bonghits
layered on top of bonghits


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

Bug#765458: apt: broken cdrom support, breaking installation from weekly ISO images

[David Kalnischkies]

Hi,

On Wed, Oct 15, 2014 at 11:47:44AM +0200, Cyril Brulebois wrote:
> [ X-D-Cc: debian-boot@, please keep it in the loop when replying. ]

[Done, although I don't see the header… (bad mutt, bad).]


> we received several bug reports about weekly installation images being
> unable to find a kernel package to install on the freshly debootstrapped
> system. I've been able to replicate this issue with apt 1.9.0.2. Various

Is the "apt-get update" call from which you have included the output
a recent addition or was it 'always' there?

I am asking as 'apt-cdrom add' actually does the work of copying the
indexes to disk, which (should) mean that 'apt-get update' is a no-op,
making the call useless if cdroms are really the only possible source in
that stage.

That 'update' isn't really supposed to be called here is reinforced by
the ugly warnings/errors you showcase and which existed since ever. Our
only testcase covering apt-cdrom also doesn't include such a call…

Why that is the case, I have no idea, as I would expect at least some
people to have multiple sources, including cdrom, which would call for
an update, so that should really work without being scary (= assuming
warnings from apt are regarded as scary…).

The irony is that the suspected bad-boy 80174528 actually fixes this
longstanding problem as the regression was that apt exited nonzero, not
that it printed warnings (so much for scary).

The problematic commit is b0f4b486 (and therefore not a regression in
a security fix – everyone rejoice): While fine by itself, merged with
the suspected bad-boy we still have no warnings and a successful exit,
but our helpful list-cleanup kicks in removing files from the lists/
directory which seem to be orphaned given that it is looking e.g. for
a Packages.gz file and not for Packages as the part fixing up the
filename is skipped if a cdrom source is encountered.


The attached patch should merge both in a better working way, at least
that is what the testcase is promising me – which I have extended a bit
to cover a bit more ground, too. Nothing near proper testing though, so
someone giving it a proper testspin would be nice, but if that is too
hard I guess Michael could just upload it and let the world test it for
us (now that he doesn't have to fear another security upload).  ;)


Best regards

David Kalnischkies
commit 5afcfe2a51a9e47e95023b99bcab065d1975e950
Author: David Kalnischkies 
Date:   Wed Oct 15 15:56:53 2014 +0200

don't cleanup cdrom files in apt-get update

Regression from merging 801745284905e7962aa77a9f37a6b4e7fcdc19d0 and
b0f4b486e6850c5f98520ccf19da71d0ed748ae4. While fine by itself, merged
the part fixing the filename is skipped if a cdrom source is
encountered, so that our list-cleanup removes what seems to be orphaned
files.

Closes: 765458

diff --git a/apt-pkg/acquire-item.cc b/apt-pkg/acquire-item.cc
index 2401364..253cbda 100644
--- a/apt-pkg/acquire-item.cc
+++ b/apt-pkg/acquire-item.cc
@@ -1144,16 +1144,12 @@ void pkgAcqIndex::Done(string Message,unsigned long long Size,string Hash,
else
   Local = true;
 
-   // do not reverify cdrom sources as apt-cdrom may rewrite the Packages
-   // file when its doing the indexcopy
-   if (RealURI.substr(0,6) == "cdrom:" &&
-   StringToBool(LookupTag(Message,"IMS-Hit"),false) == true)
-  return;
-
// The files timestamp matches, for non-local URLs reverify the local
// file, for local file, uncompress again to ensure the hashsum is still
// matching the Release file
-   if (!Local && StringToBool(LookupTag(Message,"IMS-Hit"),false) == true)
+   bool const IsCDROM = RealURI.substr(0,6) == "cdrom:";
+   if ((Local == false || IsCDROM == true) &&
+	 StringToBool(LookupTag(Message,"IMS-Hit"),false) == true)
{
   // set destfile to the final destfile
   if(_config->FindB("Acquire::GzipIndexes",false) == false)
@@ -1162,7 +1158,10 @@ void pkgAcqIndex::Done(string Message,unsigned long long Size,string Hash,
  DestFile += URItoFileName(RealURI);
   }
 
-  ReverifyAfterIMS(FileName);
+  // do not reverify cdrom sources as apt-cdrom may rewrite the Packages
+  // file when its doing the indexcopy
+  if (IsCDROM == false)
+	 ReverifyAfterIMS(FileName);
   return;
}
string decompProg;
diff --git a/test/integration/test-apt-cdrom b/test/integration/test-apt-cdrom
index 8d8fdf1..44eccb7 100755
--- a/test/integration/test-apt-cdrom
+++ b/test/integration/test-apt-cdrom
@@ -66,22 +66,51 @@ CD_LABEL="$(echo "$ident" | grep "^Stored label:" | head -n1 | sed "s/^[^:]*: //
 testequal "CD::${CD_ID} \"${CD_LABEL}\";
 CD::${CD_ID}::Label \"${CD_LABEL}\";" cat rootdir/var/lib/apt/cdroms.list
 
-testequal 'Reading package lists...
+testcdromusage() {
+	touch rootdir/var/lib/apt/extended_states
+
+	testequal 'Reading package lists...
 Building dependency tree...
+Reading state information...
 The following NEW packages will be installed:
   testing
 0 upgra

Bug#761549: marked as done (open-axiom: FTBFS: internal compiler error: in cp_perform_integral_promotions, at cp/typeck.c:2066)

[Debian Bug Tracking System]

t
 libn32objc4 - Runtime library for GNU Objective-C applications (n32)
 libn32objc4-dbg - Runtime library for GNU Objective-C applications (n32 debug 
symbo
 libn32stdc++-4.9-dev - GNU Standard C++ Library v3 (development files)
 libn32stdc++6 - GNU Standard C++ Library v3 (n32)
 libn32stdc++6-4.9-dbg - GNU Standard C++ Library v3 (debugging files)
 libobjc-4.9-dev - Runtime library for GNU Objective-C applications 
(development fil
 libobjc4   - Runtime library for GNU Objective-C applications
 libobjc4-dbg - Runtime library for GNU Objective-C applications (debug symbols)
 libphobos-4.9-dev - Phobos D standard library
 libquadmath0 - GCC Quad-Precision Math Library
 libquadmath0-dbg - GCC Quad-Precision Math Library (debug symbols)
 libstdc++-4.9-dev - GNU Standard C++ Library v3 (development files)
 libstdc++-4.9-doc - GNU Standard C++ Library v3 (documentation files)
 libstdc++-4.9-pic - GNU Standard C++ Library v3 (shared library subset kit)
 libstdc++6 - GNU Standard C++ Library v3
 libstdc++6-4.9-dbg - GNU Standard C++ Library v3 (debugging files)
 libtsan0   - ThreadSanitizer -- a Valgrind-based detector of data races (runti
 libtsan0-dbg - ThreadSanitizer -- a Valgrind-based detector of data races 
(debug
 libubsan0  - UBSan -- undefined behaviour sanitizer (runtime)
 libubsan0-dbg - UBSan -- undefined behaviour sanitizer (debug symbols)
 libx32asan1 - AddressSanitizer -- a fast memory error detector (x32)
 libx32asan1-dbg - AddressSanitizer -- a fast memory error detector (x32 debug 
symbo
 libx32atomic1 - support library providing __atomic built-in functions (x32)
 libx32atomic1-dbg - support library providing __atomic built-in functions (x32 
debug
 libx32cilkrts5 - Intel Cilk Plus language extensions (x32)
 libx32cilkrts5-dbg - Intel Cilk Plus language extensions (x32 debug symbols)
 libx32gcc-4.9-dev - GCC support library (x32 development files)
 libx32gcc1 - GCC support library (x32)
 libx32gcc1-dbg - GCC support library (debug symbols)
 libx32gfortran-4.9-dev - Runtime library for GNU Fortran applications (x32 
development fil
 libx32gfortran3 - Runtime library for GNU Fortran applications (x32)
 libx32gfortran3-dbg - Runtime library for GNU Fortran applications (x32 debug 
symbols)
 libx32go5  - Runtime library for GNU Go applications (x32)
 libx32go5-dbg - Runtime library for GNU Go applications (x32 debug symbols)
 libx32gomp1 - GCC OpenMP (GOMP) support library (x32)
 libx32gomp1-dbg - GCC OpenMP (GOMP) support library (x32 debug symbols)
 libx32itm1 - GNU Transactional Memory Library (x32)
 libx32itm1-dbg - GNU Transactional Memory Library (x32 debug symbols)
 libx32lsan0 - LeakSanitizer -- a memory leak detector (x32)
 libx32lsan0-dbg - LeakSanitizer -- a memory leak detector (x32 debug symbols)
 libx32objc-4.9-dev - Runtime library for GNU Objective-C applications (x32 
development
 libx32objc4 - Runtime library for GNU Objective-C applications (x32)
 libx32objc4-dbg - Runtime library for GNU Objective-C applications (x32 debug 
symbo
 libx32quadmath0 - GCC Quad-Precision Math Library (x32)
 libx32quadmath0-dbg - GCC Quad-Precision Math Library (x32 debug symbols)
 libx32stdc++-4.9-dev - GNU Standard C++ Library v3 (development files)
 libx32stdc++6 - GNU Standard C++ Library v3 (x32)
 libx32stdc++6-4.9-dbg - GNU Standard C++ Library v3 (debugging files)
 libx32ubsan0 - UBSan -- undefined behaviour sanitizer (x32)
 libx32ubsan0-dbg - UBSan -- undefined behaviour sanitizer (x32 debug symbols)
Closes: 748681 761549
Changes:
 gcc-4.9 (4.9.1-17) unstable; urgency=medium
 .
   * Update to SVN 20141015 (r216240) from the gcc-4_9-branch.
 - Fix PR c++/63405 (ice) Closes: #761549.
 - Fix PR ipa/61144 (wrong code). Closes: #748681.
Checksums-Sha1:
 8a98dbf50d867b0546a9f8671f512c44fdcad23b 18582 gcc-4.9_4.9.1-17.dsc
 f6ec4701493ea00527ff1c477b300e9ea6ff0233 970079 gcc-4.9_4.9.1-17.diff.gz
 322fe07e86372c8f0bb9a362bc928200765a7d89 74307772 
gcc-4.9-source_4.9.1-17_all.deb
 9dbfb59b48fa0036d544ad02c5df00f05993f889 10348868 
gcj-4.9-jre-lib_4.9.1-17_all.deb
 96cea8acb28fefad793a72c527551b6a991c8cc5 11661536 
gcj-4.9-source_4.9.1-17_all.deb
 c70d8a8861a987f2b56bd6cc483542358169a55f 18865786 libgcj-doc_4.9.1-17_all.deb
 e95c01e22b3962a57130d3d77a66ea891aa54453 8006412 
libstdc++-4.9-doc_4.9.1-17_all.deb
 3b98eb69abe3da811eaadcfd27439c39d8e37e93 1443616 
gcc-4.9-locales_4.9.1-17_all.deb
 2555b062a18034feec32a385c270b55cf02ffa1a 157588 gcc-4.9-base_4.9.1-17_amd64.deb
 316c6d9487b66525b7868710fdc34e993017ed9f 39474 libgcc1_4.9.1-17_amd64.deb
 b9bd07f1ea8f90e71a22b801da079a71aba11ffe 85614 libgcc1-dbg_4.9.1-17_amd64.deb
 b8d05ba9a463b72a8fcce6f9b3200c6ad772c100 2061724 
libgcc-4.9-dev_4.9.1-17_amd64.deb
 f5b7e89cb8afa2654448db906f8138dd14a54535 47970 lib32gcc1_4.9.1-17_amd64.deb
 80f7bcc810009a7094759df6fb5e8668070fe266 84390 lib32gcc1-dbg_4.9.1-17_amd64.deb
 97615f6aacf4f7b28ea929849ccabad3946bc20d 1912430 
lib32gcc-4.9-dev_4.9.1-17_amd64.deb
 4d4fad81173e53c6c9e903462abccb1db4255e91 3864

Bug#765434: man-db install-triggers broken

[Guillem Jover]

Hi!

On Wed, 2014-10-15 at 08:42:57 +0200, Helmut Grohne wrote:
> Control: severity -1 serious
> 
> On Wed, Oct 15, 2014 at 08:24:13AM +0300, Antti Järvinen wrote:
> > upgrade to man-db fails to install. According to error message it may be 
> > that 
> > the problem itself is in some other package or in dependencies between the 
> > packages. Output from "apt-get dist-upgrade" goes like this:
> 
> Failure to install or upgrade is a serious issue.
> 
> > Processing triggers for man-db (2.7.0.2-2) ...
> > dpkg: cycle found while processing triggers:
> >  chain of packages whose triggers are or may be responsible:
> >   libgdk-pixbuf2.0-0:i386 -> doc-base
> >  packages' pending triggers which are or may be unresolvable:
> >   doc-base: /usr/share/doc-base
> >   menu: /usr/share/menu
> >   libgdk-pixbuf2.0-0:i386: 
> > /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders
> >   hal: /usr/share/hal/fdi
> > dpkg: error processing package doc-base (--unpack):
> >  triggers looping, abandoned
> > ..
> > 
> > and man-db is left unconfigured. I have doc-base 0.10.6, menu 2.1.47, 
> > libgdk-pixbuf2 2.31.1-2 and hal 0.5.14-8.
> 
> I guess that the bug is not in man-db though, because the fix for
> similar packages was to switch from "interest" to "interest-noawait",
> but man-db already uses the latter for a while. Thus I am inviting
> Guillem Jover to look at the issue and reassign the bug.

Thanks for the heads up. I'm checking right now if this is actually a
trigger cycle, or if it's a problem with dpkg itself, which is checking
cycles before depenendencies, and might be causing this. Something I
didn't commit at the time because it was getting into infinite loops
otherwise, but maybe that was with some other implementation, cannot
remember now, doing the change and running some tests.

Will be reassigning to the correct package, later today.

Thanks,
Guillem


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

Bug#765110: start-stop-daemon: no longer creates a PID file

[Guillem Jover]

Hi!

On Wed, 2014-10-15 at 12:53:05 +0200, Christoph Martin wrote:
> Am 13.10.2014 um 20:28 schrieb Guillem Jover:
> > This is certainly a regression in s-s-d. It does still create a pidfile
> > when using --background. I do have to wonder why the init script is not
> > using --background though, because otherwise any error from it will not
> > be noticed at all by the shell, because it detaches the process itself.
> > 
> > I'm fixing this for 1.17.19, but I'd advise to switch to use --background
> > anyway.

> We had to change to not use --background because otherwise the error
> messages of sks would get redirected to /dev/null. (See bug #651843)
> 
> Putting some garbage into /etc/sks/sksconf:
> 
> > # start-stop-daemon --start --oknodo --chuid debian-sks:debian-sks --exec 
> > /usr/sbin/sks -- db  
> > Fatal error: exception Not_found
> > _mcleanup: gmon.out: Permission denied
> 
> in contrast to
> 
> > # start-stop-daemon --start --oknodo --chuid debian-sks:debian-sks 
> > --background --exec /usr/sbin/sks -- db
> 
> would ouput no message but fail to start.

Ah, but you can use --no-close now (since dpkg 1.16.5). :)

Thanks,
Guillem


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

Bug#765477: request-tracker4: FTBFS - unexpected warnings

[Michael Tautschnig]

Package: request-tracker4
Version: 4.2.7-1
Severity: serious
Usertags: goto-cc

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

[...]
mkdir -p var
RT_TEST_PARALLEL_NUM=3 /usr/bin/make test-parallel
make[1]: Entering directory 
'/srv/jenkins-slave/workspace/sid-goto-cc-request-tracker4/request-tracker4-4.2.7'
RT_TEST_PARALLEL=1 /usr/bin/perl "-MApp::Prove" -e 'my $p = App::Prove->new(); 
$p->process_args("-wlrj3","--state=slow,save", "t"); exit( $p->run() ? 0 : 1 )'
No saved state, selection will be empty
[...]
#   Failed test 'no warnings emitted'
#   at 
/srv/jenkins-slave/workspace/sid-goto-cc-request-tracker4/request-tracker4-4.2.7/lib/RT/Test/Web.pm
 line 430.
#  got: '18'
# expected: '0'
# got warning: CGI::param called in list context from package 
HTML::Mason::Utils line 48, this can lead to vulnerabilities. See the warning 
in "Fetching the value or values of a single named parameter" at 
/usr/share/perl5/CGI.pm line 425.
# got warning: CGI::param called in list context from package 
HTML::Mason::Utils line 48, this can lead to vulnerabilities. See the warning 
in "Fetching the value or values of a single named parameter" at 
/usr/share/perl5/CGI.pm line 425.
# got warning: CGI::param called in list context from package 
HTML::Mason::Utils line 48, this can lead to vulnerabilities. See the warning 
in "Fetching the value or values of a single named parameter" at 
/usr/share/perl5/CGI.pm line 425.
# got warning: CGI::param called in list context from package 
HTML::Mason::Utils line 48, this can lead to vulnerabilities. See the warning 
in "Fetching the value or values of a single named parameter" at 
/usr/share/perl5/CGI.pm line 425.
# got warning: CGI::param called in list context from package 
HTML::Mason::Utils line 48, this can lead to vulnerabilities. See the warning 
in "Fetching the value or values of a single named parameter" at 
/usr/share/perl5/CGI.pm line 425.
# got warning: CGI::param called in list context from package 
HTML::Mason::Utils line 48, this can lead to vulnerabilities. See the warning 
in "Fetching the value or values of a single named parameter" at 
/usr/share/perl5/CGI.pm line 425.
# got warning: CGI::param called in list context from package 
HTML::Mason::Utils line 48, this can lead to vulnerabilities. See the warning 
in "Fetching the value or values of a single named parameter" at 
/usr/share/perl5/CGI.pm line 425.
# got warning: CGI::param called in list context from package 
HTML::Mason::Utils line 48, this can lead to vulnerabilities. See the warning 
in "Fetching the value or values of a single named parameter" at 
/usr/share/perl5/CGI.pm line 425.
# got warning: CGI::param called in list context from package 
HTML::Mason::Utils line 48, this can lead to vulnerabilities. See the warning 
in "Fetching the value or values of a single named parameter" at 
/usr/share/perl5/CGI.pm line 425.
# got warning: CGI::param called in list context from package 
HTML::Mason::Utils line 48, this can lead to vulnerabilities. See the warning 
in "Fetching the value or values of a single named parameter" at 
/usr/share/perl5/CGI.pm line 425.
# got warning: CGI::param called in list context from package 
HTML::Mason::Utils line 48, this can lead to vulnerabilities. See the warning 
in "Fetching the value or values of a single named parameter" at 
/usr/share/perl5/CGI.pm line 425.
# got warning: CGI::param called in list context from package 
HTML::Mason::Utils line 48, this can lead to vulnerabilities. See the warning 
in "Fetching the value or values of a single named parameter" at 
/usr/share/perl5/CGI.pm line 425.
# got warning: CGI::param called in list context from package 
HTML::Mason::Utils line 48, this can lead to vulnerabilities. See the warning 
in "Fetching the value or values of a single named parameter" at 
/usr/share/perl5/CGI.pm line 425.
# got warning: CGI::param called in list context from package 
HTML::Mason::Utils line 48, this can lead to vulnerabilities. See the warning 
in "Fetching the value or values of a single named parameter" at 
/usr/share/perl5/CGI.pm line 425.
# got warning: CGI::param called in list context from package 
HTML::Mason::Utils line 48, this can lead to vulnerabilities. See the warning 
in "Fetching the value or values of a single named parameter" at 
/usr/share/perl5/CGI.pm line 425.
# got warning: CGI::param called in list context from package 
HTML::Mason::Utils line 48, this can lead to vulnerabilities. See the warning 
in "Fetching the value or values of a single named parameter" at 
/usr/share/perl5/CGI.pm line 425.
# got warning: CGI::param called in list context from package 
HTML::Mason::Utils line 48, this can lead to vulnerabilities. See the warning 
in "Fetching the value or values of a single named parameter" at 
/usr/share/perl5/CGI.pm line 425.
# got warning: CGI::param called in list context from package 
HTML::Mason::Utils

Bug#765473: dovecot-common: Dovecot (previous to V2.1) doesn't allow to disable SSLv3 which is bad: CVE-2014-3566

[Thijs Kinkhorst]

On Wed, October 15, 2014 14:07, Henrik Langos wrote:
> There is a simple one line patch available for dovecot 2.0.
> Maybe a similar way exists for 1.2.

Do you have a pointer to this patch?


Thijs


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

Bug#764162: linux-image-3.16-2-kirkwood: [regression 3.14->3.16] file data corruption, via network

[Ian Campbell]

On Sun, 2014-10-12 at 23:46 +0200, Svenska wrote:
> > If you were able to try 3.16-1~exp1[0]
> > from snapshot.debian.org that might help rule that out.
> 
> I downloaded linux-image-3.16-trunk-kirkwood_3.16-1~exp1_armel.deb from 
> your link and flashed it into the NAS. I have not done a deeper 
> analysis, but it looks like the problem is gone.
> 
> For now, I will revert back to the known-working 3.14-2 (3.14.15-2) 
> anyway, but if you want me to test another binary image, I could do that 
> if given a week or two.
> 
> Hope this helps.

Thanks, it narrows it down to a change on the Debian side rather than a
generic 3.16 upgrade breakage.

Looking at the changelog the most plausible looking candidate is still
the enabling of CONFIG_HIGHMEM. Your system has far less RAM than I
would expect to need highmem though.

If you are comfortable building a kernel for yourself (see [0] for
details) then it might be interesting to try rebuilding without
CONFIG_HIGHMEM.

Ian.

[0] 
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official


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

Bug#765058: marked as done (iapws: FTBFS - ImportError: No module named setuptools)

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 21:20:58 +0900 (JST)
with message-id <20141015.212058.808028740543679819.tats%nob...@tats.iris.ne.jp>
and subject line Re: Bug#765058: iapws: FTBFS - ImportError: No module named 
setuptools
has caused the Debian Bug report #765058,
regarding iapws: FTBFS - ImportError: No module named setuptools
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.)


-- 
765058: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iapws
Version: 1.0.5-1
Severity: serious
Usertags: goto-cc

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

[...]
dh_auto_clean
Traceback (most recent call last):
  File "setup.py", line 1, in 
from setuptools import setup
ImportError: No module named setuptools
dh_auto_clean: python setup.py clean -a returned exit code 1
debian/rules:26: recipe for target 'override_dh_auto_clean' failed
make[1]: *** [override_dh_auto_clean] Error 1
make[1]: Leaving directory 
'/srv/jenkins-slave/workspace/sid-goto-cc-iapws/iapws-1.0.5'
debian/rules:11: recipe for target 'clean' failed
make: *** [clean] Error 2


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

Best,
Michael


iapws-build-log.txt.gz
Description: application/gunzip


pgpR__egF0Ysd.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: iapws
Source-Version: 1.0.5-2
Control: reopen 765068

Seems to fix #765058, not #765068.

Thanks,
--
Tatsuya Kinoshita


pgpt6704qAEdi.pgp
Description: PGP signature
--- End Message ---

Bug#765475: Still missing API into chromium browser

[Marco Maria Luciani]

Package: chromium
Version: 38.0.2125.101-2
Severity: Serious

Dear maintener

This version (38.0.2125.101-2)still missing Google API so some
features especially into google mail give me error message (especially
the videochat into hangouts not work) s

Please fix this

Have a nice day

Marco

Bug#765465: marked as done (encfs: FTBFS for mips/mipsel)

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 12:19:15 +
with message-id 
and subject line Bug#765465: fixed in encfs 1.7.4-4.1
has caused the Debian Bug report #765465,
regarding encfs: FTBFS for mips/mipsel
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.)


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


Package: encfs
Version: 1.7.4-4
Tags: sid patch
Severity: important
User: debian-mips-dev-disc...@lists.alioth.debian.org
Usertags: mips-patch




Package encfs FTBFS for mips and mipsel with an error:

> /bin/bash ../libtool --tag=CXX   --mode=link g++ -DRLOG_COMPONENT="encfs" 
> -I/usr/include  -DLOCALEDIR=\"/usr/share/locale\" -W -Wall -Wpointer-arith 
> -Wwrite-strings -g -O2 -Wformat -Werror=format-security -flto -flto -pthread  
> -version-info 6:1:0 -Wl,-z,relro -Wl,-z,now -flto -flto   -o libencfs.la 
> -rpath /usr/lib readpassphrase.lo base64.lo ConfigReader.lo ConfigVar.lo 
> Context.lo Cipher.lo CipherKey.lo FileIO.lo RawFileIO.lo BlockFileIO.lo 
> CipherFileIO.lo MACFileIO.lo NameIO.lo StreamNameIO.lo BlockNameIO.lo 
> NullNameIO.lo Interface.lo MemoryPool.lo NullCipher.lo DirNode.lo FileNode.lo 
> FileUtils.lo openssl.lo autosprintf.lo SSL_Cipher.lo -lrlog -lssl -lcrypto 
> -lboost_serialization -lboost_filesystem -lboost_system 
> libtool: link: g++ -shared -nostdlib 
> /usr/lib/gcc/mipsel-linux-gnu/4.9/../../../mipsel-linux-gnu/crti.o 
> /usr/lib/gcc/mipsel-linux-gnu/4.9/crtbeginS.o  .libs/readpassphrase.o 
> .libs/base64.o .libs/ConfigReader.o .libs/ConfigVar.o .libs/Context.o 
> .libs/Cipher.o .libs/CipherKey.o .libs/FileIO.o .libs/RawFileIO.o 
> .libs/BlockFileIO.o .libs/CipherFileIO.o .libs/MACFileIO.o .libs/NameIO.o 
> .libs/StreamNameIO.o .libs/BlockNameIO.o .libs/NullNameIO.o .libs/Interface.o 
> .libs/MemoryPool.o .libs/NullCipher.o .libs/DirNode.o .libs/FileNode.o 
> .libs/FileUtils.o .libs/openssl.o .libs/autosprintf.o .libs/SSL_Cipher.o   
> /usr/lib/librlog.so -lssl -lcrypto -lboost_serialization -lboost_filesystem 
> -lboost_system -L/usr/lib/gcc/mipsel-linux-gnu/4.9 
> -L/usr/lib/gcc/mipsel-linux-gnu/4.9/../../../mipsel-linux-gnu 
> -L/usr/lib/gcc/mipsel-linux-gnu/4.9/../../../../lib -L/lib/mipsel-linux-gnu 
> -L/lib/../lib -L/usr/lib/mipsel-linux-gnu -L/usr/lib/../lib 
> -L/usr/lib/gcc/mipsel-linux-gnu/4.9/../../.. -lstdc++ -lm -lc -lgcc_s 
> /usr/lib/gcc/mipsel-linux-gnu/4.9/crtendS.o 
> /usr/lib/gcc/mipsel-linux-gnu/4.9/../../../mipsel-linux-gnu/crtn.o  -pthread 
> -Wl,-z -Wl,relro -Wl,-z -Wl,now   -pthread -Wl,-soname -Wl,libencfs.so.6 -o 
> .libs/libencfs.so.6.0.1
> /usr/bin/ld: /tmp/cck84z9f.ltrans0.ltrans.o: relocation R_MIPS_HI16 against 
> `__gnu_local_gp' can not be used when making a shared object; recompile with 
> -fPIC
> /tmp/cck84z9f.ltrans0.ltrans.o: error adding symbols: Bad value
> collect2: error: ld returned 1 exit status


The reason for this error is the fact that fPIC flag is used for compiling but
not for linking.

Patch that adds fPIC flag for linking is attached.


Whit this patch I was able to successfully build encfs
for mips, mipsel and amd64.


Could you please consider including this patch?



Best Regards,
Dejan

diff -uNr encfs-1.7.4.orig/configure encfs-1.7.4/configure
--- encfs-1.7.4.orig/configure	2010-11-18 08:11:06.0 +
+++ encfs-1.7.4/configure	2014-10-14 12:06:32.0 +
@@ -13584,8 +13584,8 @@
   # Check if GNU C++ uses GNU ld as the underlying linker, since the
   # archiving commands below assume that GNU ld is being used.
   if test "$with_gnu_ld" = yes; then
-archive_cmds_CXX='$CC -shared -nostdlib $predep_objects $libobjs $deplibs $postdep_objects $compiler_flags ${wl}-soname $wl$soname -o $lib'
-archive_expsym_cmds_CXX='$CC -shared -nostdlib $predep_objects $libobjs $deplibs $postdep_objects $compiler_flags ${wl}-soname $wl$soname ${wl}-retain-symbols-file $wl$export_symbols -o $lib'
+archive_cmds_CXX='$CC -shared $pic_flag -nostdlib $predep_objects $libobjs $deplibs $postdep_objects $compiler_flags ${wl}-soname $wl$soname -o $lib'
+archive_expsym_cmds_CXX='$CC $pic_flag -shared -nostdlib $predep_objects $libobjs $deplibs $postdep_objects $compiler_flags ${wl}-soname $wl$soname ${wl}-retain-symbols-file $wl$export_symbols -o $lib'
 
 hardcode_libdir_flag_spec_CXX='${wl}-rpath ${wl}$libdir'
 export_dynamic_flag_spec_CXX='${wl}--export-dynamic'
diff -uNr encfs-1.7.4.orig/m4/libtool.m4 encfs-1.7.4/m4/libtool.m4
--- encfs-1.7.4.orig/m4/libtool.m4	2010-06-17 06:31:30.0 +00

Bug#765473: dovecot-common: Dovecot (previous to V2.1) doesn't allow to disable SSLv3 which is bad: CVE-2014-3566

[Henrik Langos]

Package: dovecot-common
Version: 1:1.2.15-7
Severity: grave
Tags: security squeeze upstream
Justification: user security hole

Hi there,

I guess everybody knows by now that CVE-2014-3566 changes the status
of SSLv3 from mostly-obsolete to mostly-broken.

Unfortunately dovecot previous to 2.1 doesn't distinguish between security
protocols and cyphers. Therefore simply disabling SSLv3 in dovecot.conf
like this

ssl_cipher_list = ALL:!LOW:!SSLv2:!SSLv3

will apparently disable all cyphers.

There is a simple one line patch available for dovecot 2.0.
Maybe a similar way exists for 1.2.

best regards
-henrik 


-- System Information:
Debian Release: 6.0.10
  APT prefers squeeze-lts
  APT policy: (500, 'squeeze-lts'), (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages dovecot-common depends on:
ii  adduser 3.112+nmu2   add and remove users and groups
ii  libbz2-1.0  1.0.5-6+squeeze1 high-quality block-sorting file co
ii  libc6   2.11.3-4+deb6u1  Embedded GNU C Library: Shared lib
ii  libcomerr2  1.41.12-4stable1 common error description library
ii  libdb4.84.8.30-2 Berkeley v4.8 Database Libraries [
ii  libgssapi-krb5-21.8.3+dfsg-4squeeze8 MIT Kerberos runtime libraries - k
ii  libk5crypto31.8.3+dfsg-4squeeze8 MIT Kerberos runtime libraries - C
ii  libkrb5-3   1.8.3+dfsg-4squeeze8 MIT Kerberos runtime libraries
ii  libldap-2.4-2   2.4.23-7.3   OpenLDAP libraries
ii  libmysqlclient165.1.73-1 MySQL database client library
ii  libpam-runtime  1.1.1-6.1+squeeze1   Runtime support for the PAM librar
ii  libpam0g1.1.1-6.1+squeeze1   Pluggable Authentication Modules l
ii  libpq5  8.4.22-0+deb6u1  PostgreSQL C client library
ii  libsqlite3-03.7.3-1  SQLite 3 shared library
ii  libssl0.9.8 0.9.8o-4squeeze17SSL shared libraries
ii  openssl 0.9.8o-4squeeze17Secure Socket Layer (SSL) binary a
ii  ucf 3.0025+nmu1  Update Configuration File: preserv
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

dovecot-common recommends no packages.

Versions of packages dovecot-common suggests:
pn  ntp(no description available)

-- 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#713841: marked as done (oss4-dkms: oss4-4.2-build2006 cp: stat failed /source/include/linux/limits.h)

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 12:04:03 +
with message-id 
and subject line Bug#713841: fixed in oss4 4.2-build2007-2.3
has caused the Debian Bug report #713841,
regarding oss4-dkms: oss4-4.2-build2006 cp: stat failed 
/source/include/linux/limits.h
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.)


-- 
713841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: oss4-dkms
Version: 4.2-build2006-2+deb7u1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

I've updated system ( apt-get update && apt-get dist-upgrade) new kernel was
installed 3.9-1-686-pae . After that no sound (from sound card) was on the
system.
Kernel packages were installed: linux-headers-3.9-1-686-pae, linux-source-3.9
to force oss4-dkms to build- without efect.

#cat /var/lib/dkms/oss4/4.2-build2006/build/make.log
sun, 23 jun 2013, 10:01:11 CEST
cp: cannot stat `/lib/modules/3.9-1-686-pae/source/include/linux/limits.h': No
such file or directory

Well its not there:
# ls -chal /lib/modules/3.9-1-686-pae/source/include/linux/|grep " li"
-rw-r--r--  1 root root  60K jun 22 18:33 libata.h
-rw-r--r--  1 root root  284 jun 22 18:33 libfdt_env.h
-rw-r--r--  1 root root  205 jun 22 18:33 libfdt.h
-rw-r--r--  1 root root 1,8K jun 22 18:33 libps2.h
-rw-r--r--  1 root root  374 jun 22 18:33 license.h
-rw-r--r--  1 root root 2,1K jun 22 18:33 linkage.h
-rw-r--r--  1 root root 2,1K jun 22 18:33 linux_logo.h
-rw-r--r--  1 root root 5,0K jun 22 18:33 lis3lv02d.h
-rw-r--r--  1 root root 4,1K jun 22 18:33 list_bl.h
-rw-r--r--  1 root root  21K jun 22 18:33 list.h
-rw-r--r--  1 root root 3,2K jun 22 18:33 list_nulls.h
-rw-r--r--  1 root root  238 jun 22 18:33 list_sort.h

# uname -r
3.9-1-686-pae

Please contact me with any additional information You may require for fixing
this issue.
I will deliver them ASAP.
Sincerely Herber Sylwester



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

Kernel: Linux 3.9-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages oss4-dkms depends on:
ii  dkms2.2.0.3-1.2
ii  linux-headers-2.6-686 [linux-headers]   2.6.38+34
ii  linux-headers-2.6.38-2-686 [linux-headers]  2.6.38-5
ii  linux-headers-2.6.39-2-686-pae [linux-headers]  2.6.39-3
ii  linux-headers-3.0.0-1-486 [linux-headers]   3.0.0-3
ii  linux-headers-3.0.0-1-686-pae [linux-headers]   3.0.0-3
ii  linux-headers-3.0.0-1-amd64 [linux-headers] 3.0.0-3
ii  linux-headers-3.1.0-1-486 [linux-headers]   3.1.8-2
ii  linux-headers-3.1.0-1-686-pae [linux-headers]   3.1.8-2
ii  linux-headers-3.1.0-1-amd64 [linux-headers] 3.1.8-2
ii  linux-headers-3.2.0-1-686-pae [linux-headers]   3.2.6-1
ii  linux-headers-3.2.0-2-686-pae [linux-headers]   3.2.20-1
ii  linux-headers-3.2.0-4-686-pae [linux-headers]   3.2.46-1
ii  linux-headers-3.9-1-486 [linux-headers] 3.9.6-1
ii  linux-headers-3.9-1-686-pae [linux-headers] 3.9.6-1
ii  linux-headers-3.9-1-amd64 [linux-headers]   3.9.6-1
ii  oss4-base   4.2-build2006-2+deb7u1

oss4-dkms recommends no packages.

oss4-dkms suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: oss4
Source-Version: 4.2-build2007-2.3

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated oss4 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 15 Oct 2014 13:56:56 +0200
Source: oss4
Binary: oss4-base oss4-gtk oss4-dkms oss4-source oss4-dev liboss4-salsa2 
liboss4-salsa-dev liboss4-salsa-asound2
Architecture: source all amd64
Version: 4.2-build2007-2.3
Distribution: unstable
Urgency: medium
Maintainer: Debian OSS4 Maintainers 

Chan

Processed: Re: debdiff for encfs_1.7.4-4.1

[Debian Bug Tracking System]

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

> severity 765465 serious
Bug #765465 [encfs] encfs: FTBFS for mips/mipsel
Severity set to 'serious' from 'important'
> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
765465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765465
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#761783: marked as done (oss4: libtool split: package needs a b-d on libtool-bin (or avoid using the libtool binary))

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 13:55:03 +0200
with message-id <543e6097.7010...@debian.org>
and subject line fixed in NMU
has caused the Debian Bug report #761783,
regarding oss4: libtool split: package needs a b-d on libtool-bin (or avoid 
using the libtool binary)
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.)


-- 
761783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:oss4
Version: 4.2-build2007-2.1
Severity: wishlist
User: debian-cr...@lists.debian.org
Usertags: libtool-split

As part of the effort to cross-build the archive, the libtool package
needs a split into an architecture independent part and an
architecture dpendent part (the latter only consisting of the libtool
binary).  The split is already done for jessie/sid, but to enable the
cross buildability, the dependency in libtool on libtool-bin needs to
be removed, and libtool-bin needs to depend on libtool instead.

The vast majority of packages using libtool via automake don't need
the libtool binary, and thus no changes in the build dependencies, however
about 60 source packages are using libtool directly, and need changes.

 - some packages just check for the libtool binary, and then don't
   use it for the build (but are using libtoolize instead).  Such
   usages are seen in a script called buildcheck.sh, and sometimes
   in autogen.sh scripts.  The solution for these cases is to patch
   these scripts to check for libtoolize instead of libtool, and
   not to introduce the new build dependency.

 - other packages just need the additional build dependency on
   libtool-bin.

To test your packages with the libtool-bin package removed, please use
the binaries found at

  deb https://people.debian.org/~doko/tmp/20140820 ./

It is not clear, if all of these changes can be done in time for
the jessie release, but it would be nice to have to be able to
cross-build more packages in jessie.

For questions and help please email the debian-cross ML.

For additional pointers please see
https://lists.debian.org/debian-devel-announce/2014/08/msg00013.html
and some discussion in the orignal issue filed for libtool (#682045).

The full build log can be found at:
http://people.debian.org/~doko/logs/20140912/failed-libtool/oss4_4.2-build2007-2.1_unstable_jdk-libtool.log
The last lines of the build log are at the end of this report.

[...]
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_midiloop 
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_midimix 
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_sblive 
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_sbpci 
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_sbxfi 
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_solo 
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_trident 
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_usb 
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_userdev 
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_via823x 
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_via97 
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_ymf7xx 
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
find build-tree/modules/oss4 -type f -exec chmod -x {} \;
touch stamp-source-oss4
sed -e 's#_VERSION_#4.2-build2007#' < debian/oss4-dkms.install.in > 
debian/oss4-dkms.install
sed -e 's#_VERSION_#4.2-build2007#' < debian/oss4-dkms.dkms.in > 
debian/oss4-dkms.dkms
rm -rf build-tree/modules/oss4/debian
mkdir -p build-tree/modules/oss4/debian
cp -r debian/m-a/* build-tree/modules/oss4/debian/
cp debian/copyright build-tree/modules/oss4/debian/
cp debian/changelog build-tree/modules/

Bug#713566: marked as done (guile-1.6: FTBFS: ld: guile.o: undefined reference to symbol 'lt_dlpreload_default')

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 11:49:24 +
with message-id 
and subject line Bug#745974: Removed package(s) from unstable
has caused the Debian Bug report #713566,
regarding guile-1.6: FTBFS: ld: guile.o: undefined reference to symbol 
'lt_dlpreload_default'
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.)


-- 
713566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: guile-1.6
Version: 1.6.8-10.3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Maybe you need to add explicitly the offending lib to LD flags.

Relevant part:
> x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I./.. -I../libguile-ltdl  
>   -g -O2 -Wall -Wmissing-prototypes -fno-strict-aliasing -MT guile.o -MD -MP 
> -MF .deps/guile.Tpo -c -o guile.o guile.c
> mv -f .deps/guile.Tpo .deps/guile.Po
> /bin/bash ../libtool --tag=CC   --mode=compile x86_64-linux-gnu-gcc 
> -DHAVE_CONFIG_H -I. -I.. -I.. -I./.. -I../libguile-ltdl-g -O2 -Wall 
> -Wmissing-prototypes -fno-strict-aliasing -MT alist.lo -MD -MP -MF 
> .deps/alist.Tpo -c -o alist.lo alist.c
> libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I./.. 
> -I../libguile-ltdl -g -O2 -Wall -Wmissing-prototypes -fno-strict-aliasing -MT 
> alist.lo -MD -MP -MF .deps/alist.Tpo -c alist.c  -fPIC -DPIC -o .libs/alist.o
> libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I./.. 
> -I../libguile-ltdl -g -O2 -Wall -Wmissing-prototypes -fno-strict-aliasing -MT 
> alist.lo -MD -MP -MF .deps/alist.Tpo -c alist.c -o alist.o >/dev/null 2>&1
> mv -f .deps/alist.Tpo .deps/alist.Plo
> /bin/bash ../libtool --tag=CC   --mode=compile x86_64-linux-gnu-gcc 
> -DHAVE_CONFIG_H -I. -I.. -I.. -I./.. -I../libguile-ltdl-g -O2 -Wall 
> -Wmissing-prototypes -fno-strict-aliasing -MT arbiters.lo -MD -MP -MF 
> .deps/arbiters.Tpo -c -o arbiters.lo arbiters.c
> libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I./.. 
> -I../libguile-ltdl -g -O2 -Wall -Wmissing-prototypes -fno-strict-aliasing -MT 
> arbiters.lo -MD -MP -MF .deps/arbiters.Tpo -c arbiters.c  -fPIC -DPIC -o 
> .libs/arbiters.o
> libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I./.. 
> -I../libguile-ltdl -g -O2 -Wall -Wmissing-prototypes -fno-strict-aliasing -MT 
> arbiters.lo -MD -MP -MF .deps/arbiters.Tpo -c arbiters.c -o arbiters.o 
> >/dev/null 2>&1
> mv -f .deps/arbiters.Tpo .deps/arbiters.Plo
> /bin/bash ../libtool --tag=CC   --mode=compile x86_64-linux-gnu-gcc 
> -DHAVE_CONFIG_H -I. -I.. -I.. -I./.. -I../libguile-ltdl-g -O2 -Wall 
> -Wmissing-prototypes -fno-strict-aliasing -MT async.lo -MD -MP -MF 
> .deps/async.Tpo -c -o async.lo async.c
> libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I./.. 
> -I../libguile-ltdl -g -O2 -Wall -Wmissing-prototypes -fno-strict-aliasing -MT 
> async.lo -MD -MP -MF .deps/async.Tpo -c async.c  -fPIC -DPIC -o .libs/async.o
> libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I./.. 
> -I../libguile-ltdl -g -O2 -Wall -Wmissing-prototypes -fno-strict-aliasing -MT 
> async.lo -MD -MP -MF .deps/async.Tpo -c async.c -o async.o >/dev/null 2>&1
> mv -f .deps/async.Tpo .deps/async.Plo
> /bin/bash ../libtool --tag=CC   --mode=compile x86_64-linux-gnu-gcc 
> -DHAVE_CONFIG_H -I. -I.. -I.. -I./.. -I../libguile-ltdl-g -O2 -Wall 
> -Wmissing-prototypes -fno-strict-aliasing -MT backtrace.lo -MD -MP -MF 
> .deps/backtrace.Tpo -c -o backtrace.lo backtrace.c
> libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I./.. 
> -I../libguile-ltdl -g -O2 -Wall -Wmissing-prototypes -fno-strict-aliasing -MT 
> backtrace.lo -MD -MP -MF .deps/backtrace.Tpo -c backtrace.c  -fPIC -DPIC -o 
> .libs/backtrace.o
> libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I./.. 
> -I../libguile-ltdl -g -O2 -Wall -Wmissing-prototypes -fno-strict-aliasing -MT 
> backtrace.lo -MD -MP -MF .deps/backtrace.Tpo -c backtrace.c -o backtrace.o 
> >/dev/null 2>&1
> mv -f .deps/backtrace.Tpo .deps/backtrace.Plo
> /bin/bash ../libtool --tag=CC   --mode=compile x86_64-linux-gnu-gcc 
> -DHAVE_CONFIG_H -I. -I.. -I.. -I./.. -I../libguile-ltdl-g -O2 -Wall 
> -Wmissing-prototypes -fno-strict-aliasing -MT boolean.lo -MD -MP -MF 
> .deps/boolean.Tpo -c -o boolean.lo boolean.c
> libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I./.. 

Bug#765469: python3-tornado: get_secure_cookie get incorrect value by setting set_secure_cookie

[Yavuz Selim Komur]

Package: python3-tornado
Version: 3.2.2-1
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

class abc(tornado.web.RequestHandler):
def get(self):
(stat, user) = self.check_remember()
if stat:
   do_action()
else:
   self.clear_cookie('remember')
   self.render('remember-post.html')

def post(self):
username = self.get_body_argument('username'):
if self.get_body_argument('remember'):
   val = json.dumps({'username': username, 'time': time.time()})
   self.set_secure_cookie('remember', value=val, expires_days=7)

def check_remember(self):
try:
remember_cookie = self.get_secure_cookie('remember', max_age_days=7)
except ValueError:
print('try get_cookie')
return False, ''

if remember_cookie is None:
return False, ''

try:
remember = json.loads(remember_cookie.decode())
except ValueError:
print('try json')
return False, ''

ret = (False, '')
if 'username' in remember and 'time' in remember:
if time.time() - remember['time'] > 7 * 24 * 60 * 60:
self.clear_cookie('remember')
ret = (False, '')
else:
username = remember['username']
val = json.dumps({'username': username, 'time': time.time()})
self.set_secure_cookie('remember', value=val, expires_days=7)
ret = (True, username)
return ret


Always get an Exception ValueError in json.loads  print try json and return

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

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

Versions of packages python3-tornado depends on:
ii  ca-certificates  20140927
ii  python3  3.4.2-1

python3-tornado recommends no packages.

python3-tornado suggests no packages.

-- no debconf information


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

Bug#764357: non-free file in package

[Tsukasa #01 (OI)]

I can't directly contribute to ssdeep because I saw the non-free source
code of edit_dist.c. So I decided to tweet this problem.

After I tweeted this problem on Twitter (in Japanese), @kikairoya (who
has not seen the source code of ssdeep and/or trn) wrote a program to
compute ssdeep version of Levenshtein distance.  He says he licenses the
source code under the terms of Boost Software License, version 1.0
(compatible with GPLv2+). I didn't even tell him the interface for
ssdeep so slight modification will be needed.

https://gist.github.com/kikairoya/58f996c36210ffc31e79

Anyway, is there any reason to make replacement cost in the ssdeep
version of edit_dist.c 3? I think a replacement will always have a cost
of 2 (because this can be achieved by character removal and insertion).

Thanks,
Tsukasa


-- 
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#764692: dns-flood-detector: FTBFS on kfreebsd-*

[Debian Bug Tracking System]

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

> clone 764692 -1
Bug #764692 [libc0.1-dev] glibc: removed __FAVOR_BSD from features.h
Bug 764692 cloned as bug 765468
> reassign -1 src:dns-flood-detector
Bug #765468 [libc0.1-dev] glibc: removed __FAVOR_BSD from features.h
Bug reassigned from package 'libc0.1-dev' to 'src:dns-flood-detector'.
No longer marked as found in versions glibc/2.19-11.
Ignoring request to alter fixed versions of bug #765468 to the same values 
previously set
> found -1 dns-flood-detector/1.20-2
Bug #765468 [src:dns-flood-detector] glibc: removed __FAVOR_BSD from features.h
Marked as found in versions dns-flood-detector/1.20-2.
> tags -1 + patch
Bug #765468 [src:dns-flood-detector] glibc: removed __FAVOR_BSD from features.h
Ignoring request to alter tags of bug #765468 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
764692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764692
765468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765468
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#764692: dns-flood-detector: FTBFS on kfreebsd-*

[Steven Chamberlain]

clone 764692 -1
reassign -1 src:dns-flood-detector
found -1 dns-flood-detector/1.20-2
tags -1 + patch
thanks

Hi,

> On 12/10/14 16:45, Steven Chamberlain wrote:
>> glibc-provided features.h no longer defines a __FAVOR_BSD macro, so the
>> BSD version of struct tcphdr in netinet/tcp.h cannot be used, [...]

> https://buildd.debian.org/status/fetch.php?pkg=dns-flood-detector&arch=kfreebsd-amd64&ver=1.20-2&stamp=1413149812

This problem with glibc 2.19 can be worked around in dns-flood-detector
with the attached patch.

(Although in the next release of glibc, it might no longer work, so
maybe libbsd-dev could provide a suitable netinet/tcp.h someday)

Thanks,
Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org
--- debian/rules.orig	2014-10-12 20:01:04.0 +0100
+++ debian/rules	2014-10-15 12:35:53.128715139 +0100
@@ -11,7 +11,7 @@
 CXXFLAGS:=$(shell dpkg-buildflags --get CXXFLAGS)
 LDFLAGS:=$(shell dpkg-buildflags --get LDFLAGS)
 
-CFLAGS += -D_BSD_SOURCE -Wall -g
+CFLAGS += -D_BSD_SOURCE -D__FAVOR_BSD -Wall -g
 LDLIBS += -lpcap -lpthread -lm
 
 ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))

Bug#707900: marked as done (guile-pg: please migrate to guile-2.0)

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 11:39:49 +
with message-id 
and subject line Bug#765388: Removed package(s) from unstable
has caused the Debian Bug report #707900,
regarding guile-pg: please migrate to guile-2.0
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.)


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

Package: guile-pg
Version: 0.16-5

Now that the freeze is over, I'm finally planning to remove guile-1.6
(and possibly guile-1.8) from Debian soon.  Please consider updating
guile-pg to guile-2.0.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
--- End Message ---
--- Begin Message ---
Version: 0.16-5+rm

Dear submitter,

as the package guile-pg has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/765388

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#765314: mrpt: FTBFS on all non-x86-based architectures

[Jose Luis Blanco]

I would add a third patch to fix (avoid) errors in hurd. If you have
the possibility of adding it it would be great!

So, these are the 3 patches:
https://github.com/jlblancoc/mrpt/commit/693bebedac9234fa00304a26aa854f54dc4d674f
https://github.com/jlblancoc/mrpt/commit/bb294b9c7a9aef3b4bbbdc89811e7873805eba19
https://github.com/jlblancoc/mrpt/commit/c81effd1228234e2ed17caf0ef22f0caee6b

Can be downloaded as git diffs as well:

https://github.com/jlblancoc/mrpt/commit/693bebedac9234fa00304a26aa854f54dc4d674f.diff
https://github.com/jlblancoc/mrpt/commit/bb294b9c7a9aef3b4bbbdc89811e7873805eba19.diff
https://github.com/jlblancoc/mrpt/commit/c81effd1228234e2ed17caf0ef22f0caee6b.diff

Best,
JL


On Wed, Oct 15, 2014 at 9:14 AM, Jose Luis Blanco
 wrote:
> Hi Olly,
>
> In theory, these patches should fix sparc & (I think) s390x:
>
> - 
> https://github.com/jlblancoc/mrpt/commit/693bebedac9234fa00304a26aa854f54dc4d674f
> -https://github.com/jlblancoc/mrpt/commit/bb294b9c7a9aef3b4bbbdc89811e7873805eba19
>
> But couldn't test it locally. Would you please try to attach them as
> patches for a new version 1.2.2-1.2??
>
> Best,
> JL
>
>
> On Wed, Oct 15, 2014 at 7:31 AM, Jose Luis Blanco
>  wrote:
>> Any recommendation about how to test it locally on s390x? qemu or alike?
>>
>> A partner got it tested in a physical mips device before submitting,
>> so hopefully it will work there...
>>
>> Thanks.
>>
>>
>> On Wed, Oct 15, 2014 at 7:00 AM, Olly Betts  wrote:
>>> Still not building everywhere:
>>>
>>> https://buildd.debian.org/status/package.php?p=mrpt
>>>
>>> It's never built on ppc64el, so that won't block testing migration (but
>>> it would be good to sort out).
>>>
>>> The failure on sparc isn't a big problem, as sparc isn't a release arch
>>> for jessie.
>>>
>>> And armel, mips, and mipsel are yet to attempt a build of this version.
>>>
>>> But the failure on s390x needs sorting out if mrpt is to make jessie -
>>> failure is in the testsuite:
>>>
>>> [ RUN  ] Synch.CriticalSections_Multi
>>> *** stack smashing detected ***: ./test_mrpt_base terminated
>>>
>>> For backtrace, etc see the tail end of:
>>>
>>> https://buildd.debian.org/status/fetch.php?pkg=mrpt&arch=s390x&ver=1%3A1.2.2-1.1&stamp=1413289418
>>>
>>> Cheers,
>>> Olly


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

Bug#731784: marked as done (bobot++: please migrate to guile-2.0)

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 11:37:43 +
with message-id 
and subject line Bug#765387: Removed package(s) from unstable
has caused the Debian Bug report #731784,
regarding bobot++: please migrate to guile-2.0
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.)


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

Package: bobot++
Version: 1:1.97-10.4

I'm trying to have guile-1.6 (and soon guile-1.8) removed from unstable,
please migrate to guile-2.0 (or at least guile-1.8) as soon as possible.

Oh, and if it helps, there appears to be an NMU in experimental for
guile-1.8.

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
--- End Message ---
--- Begin Message ---
Version: 1:1.97-10.4+rm

Dear submitter,

as the package bobot++ has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/765387

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#763488: marked as done (openjdk-6: Please change build dependency to libjpeg-dev (libjpeg-turbo transition))

[Debian Bug Tracking System]

Your message dated Wed, 15 Oct 2014 11:35:18 +
with message-id 
and subject line Bug#763488: fixed in openjdk-6 6b33-1.13.5-1
has caused the Debian Bug report #763488,
regarding openjdk-6: Please change build dependency to libjpeg-dev 
(libjpeg-turbo transition)
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.)


-- 
763488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjdk-6
Version: 6b32-1.13.4-4
Severity: important
Tags: patch
User: ond...@debian.org
Usertags: libjpeg-turbo-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

Debian is transitioning from IJG JPEG library (src:libjpeg8) to
libjpeg-turbo implementation (src:libjpeg-turbo)[1] of libjpeg62 API
with "decode from memory buffer" interface (jpeg_mem_{src,dest}).

Your package cannot be transitioned automatically as it explicitly
build depends on specific API/ABI (libjpeg8-dev) and this build
dependency needs to be changed to libjpeg-dev.  In most if not all
cases this should be sufficient to build against libjpeg-turbo.

I am in process of testing each package in question to compile against
libjpeg-turbo and I will provide a suitable patch for each package
when I will succeed.

On the other hand please note that the winter^Wfreeze is coming and
if your package is not updated in due time it might be NMUed by the
release team (or by me with the full ack of release team).

That also means that if you are OK with NMU then please respond to
this bug report and I will prepare and upload the recompiled packages
for you.

Cheers,
Ondrej

1. The full Technical Committee decision can be found here:
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717076#235

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

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

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJUKqrTXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHkHgP/1K0nvtCg+71ujbCB6231cCK
/qJvLvODDG8ZRbwya7U+iBTYE6BXlwDsUdtwMd1yOqEsNxmZReseAh4cfejFopaN
gIVYYjX9rLL5FJsvrmw2ZFZMxgMbAyiwsvBOWf2T18ivGpc2iELFgY4Ytb8dqlOY
s2vQuEL7cD5JDRGt1Bha4UgdvbiAL/KhNwN31r2Hv6AUaUV1qaqumHWZKYXzbw9M
DiDPmRLJnJEuSMBWhmgIpXaMHvHnJUaQFKLYCa8uqDNtJhlEgw7qlLbQhGEDv2Nu
4Kiiagh2vmqN7+es82IpAuS+/EAp8g+QZN6BHrMJbMwGJUEHBRySWZz1H64f5C9T
bIRbdCtUNmtRhA4v2JBOHkSGwKsMPuemA0SS/ArVWsouc2Pg4V+iMIb0qztXOLsv
gHPVBhgzSSiBj7GjUd/y1ie8N0u9nQea6pHrHAQk1q3JLTwnS7VGcbeNit69s85v
mU9lHrm4CBbuKrJKILaoo+oNPyusDjXE5YGlC8cwcrBXrQnfH4XIH40b9db6U1vw
9l7xL7Q8YzqBGP69UPlVtSsf60aouipaFq3lPBqbn/MAWUcalY1pO6Ms4NeXEx0m
bzf8Uu9RhUxhl2AU7jH4+6RSymOASPt2MFGSVaOcoB7RAfbtrcNj6fJvMp/xNG/G
50RE1cUoJyt3qXFiX/MF
=WzbK
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: openjdk-6
Source-Version: 6b33-1.13.5-1

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated openjdk-6 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 15 Oct 2014 09:43:32 +0200
Source: openjdk-6
Binary: openjdk-6-jdk openjdk-6-jre-headless openjdk-6-jre openjdk-6-jre-lib 
openjdk-6-demo openjdk-6-source openjdk-6-doc openjdk-6-dbg icedtea-6-jre-cacao 
icedtea-6-jre-jamvm openjdk-6-jre-zero
Architecture: source amd64 all
Version: 6b33-1.13.5-1
Distribution: unstable
Urgency: medium
Maintainer: OpenJDK Team 
Changed-By: Matthias Klose 
Description:
 icedtea-6-jre-cacao - Alternative JVM for OpenJDK, using Cacao
 icedtea-6-jre-jamvm - Alternative JVM for OpenJDK, using JamVM
 openjdk-6-dbg - Java runtime based on OpenJDK (debugging symbols)
 openjdk-6-demo - Java runtime based on OpenJDK (demos and examples)
 openjdk-6-doc - OpenJDK Development Ki

Bug#765110: start-stop-daemon: no longer creates a PID file

[Christoph Martin]

Am 13.10.2014 um 20:28 schrieb Guillem Jover:
> 
> This is certainly a regression in s-s-d. It does still create a pidfile
> when using --background. I do have to wonder why the init script is not
> using --background though, because otherwise any error from it will not
> be noticed at all by the shell, because it detaches the process itself.
> 
> I'm fixing this for 1.17.19, but I'd advise to switch to use --background
> anyway.
> 

We had to change to not use --background because otherwise the error
messages of sks would get redirected to /dev/null. (See bug #651843)

Putting some garbage into /etc/sks/sksconf:

> # start-stop-daemon --start --oknodo --chuid debian-sks:debian-sks --exec 
> /usr/sbin/sks -- db  
> Fatal error: exception Not_found
> _mcleanup: gmon.out: Permission denied

in contrast to

> # start-stop-daemon --start --oknodo --chuid debian-sks:debian-sks 
> --background --exec /usr/sbin/sks -- db

would ouput no message but fail to start.

Christoph

-- 

Christoph Martin, Zentrum für Datenverarbeitung, Uni-Mainz, Germany
 Anselm Franz von Bentzel-Weg 12, 55128 Mainz
 Telefon: +49(6131)3926337
 Instant-Messaging: Jabber: mar...@uni-mainz.de
  (Siehe http://www.zdv.uni-mainz.de/4010.php)
<>

signature.asc
Description: OpenPGP digital signature