Processed: tagging 638761

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 638761 - security
Bug #638761 [gtkmathview] gtkmathview: please remove t1lib dependency
Removed tag(s) security.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
638761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638761
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#736796: marked as done (menulibre: Menulibre doesn't start)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jan 2014 07:33:19 +
with message-id 
and subject line Bug#736796: fixed in menulibre 2.0.1-1
has caused the Debian Bug report #736796,
regarding menulibre: Menulibre doesn't start
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.)


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

Dear Maintainer,
when i try to start menulibre in console, i get these errors:

~$ menulibre -v

(menulibre:23090): Gtk-WARNING **: Theme parsing error: gtk.css:102:18: Not 
using units is deprecated. Assuming 'px'.

(menulibre:23090): Gtk-WARNING **: Theme parsing error: gtk.css:102:20: Not 
using units is deprecated. Assuming 'px'.
DEBUG:menulibre: set_up_logging() 'logging enabled'
WARNING:menulibre: getDefaultMenuPrefix() 'No menu prefix found, MenuLibre will 
not function properly.'
DEBUG:menulibre: __init__() 'Using menu: 
/home/luigi/.config/menus/applications.menu'
DEBUG:menulibre: block() 'Blocking history updates'
DEBUG:menulibre: unblock() 'Unblocking history updates'
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/menulibre/MenulibreApplication.py", line 
2247, in do_activate
self.win = MenulibreWindow(self)
  File "/usr/lib/python3/dist-packages/menulibre/MenulibreApplication.py", line 
338, in __init__
self.configure_application_treeview(builder)
  File "/usr/lib/python3/dist-packages/menulibre/MenulibreApplication.py", line 
614, in configure_application_treeview
selection.set_select_function(self.on_treeview_selection)
TypeError: set_select_function() takes exactly 3 arguments (2 given)

and i must kill the application with "killall menulibre", ctrl-c doesn't work.

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

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

Versions of packages menulibre depends on:
ii  gir1.2-gdkpixbuf-2.0  2.28.2-1+b1
ii  gir1.2-glib-2.0   1.36.0-2+b1
ii  gir1.2-gmenu-3.0  3.8.0-2
ii  gir1.2-gtk-3.03.8.6-1
ii  gnome-menus   3.8.0-2
ii  python3   3.3.2-17
ii  python3-gi3.10.2-2
pn  python3:any   

menulibre recommends no packages.

menulibre suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: menulibre
Source-Version: 2.0.1-1

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

Debian distribution maintenance software
pp.
Jackson Doak  (supplier of updated menulibre package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 27 Jan 2014 12:21:11 +1100
Source: menulibre
Binary: menulibre
Architecture: source all
Version: 2.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Jackson Doak 
Changed-By: Jackson Doak 
Description: 
 menulibre  - advanced FreeDesktop.org compliant menu editor
Closes: 736796
Changes: 
 menulibre (2.0.1-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #736796
   * debian/copyright: Use GPL3 rather than GPL3+
   * debian/control: Change section to utils
Checksums-Sha1: 
 7d9487bd0fb3cb5aacdde155ba647fbb64794083 2020 menulibre_2.0.1-1.dsc
 ed5feff975f648394a212e3e38d2f9ac290c4758 115100 menulibre_2.0.1.orig.tar.gz
 9a16a7ceab32a6ff9fe393ab00596f7d55be5e4b 2020 menulibre_2.0.1-1.debian.tar.xz
 818d7a7368e3bdedc9757c6a052c7e92de073930 60992 menulibre_2.0.1-1_all.deb
Checksums-Sha256: 
 d6d8a9c5295cfcea20ac0fed6b3f363f36b890e5e874a019757a35f5093b1c57 2020 
menulibre_2.0.1-1.dsc
 2ed31c3b7db2f83b790d90b4bf8b1c7346a2cc9eb6a5fc6eb5308b8ea6bbac9d 115100 
menulibre_2.0.1.orig.tar.gz
 68828f34eaedb187864e5b8cdfbbfe8d6bc2d1d85b3b23388afbdaeb7e806bfc 2020 
menulibre_2.0.1-1.debian.tar.xz
 ad5f2d054dc680f52c7410e87771703b64084812b8aa8a1a14552c0329a54336 

Processed: tagging 638760

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 638760 - security
Bug #638760 [grace] grace: please remove t1lib dependency
Removed tag(s) security.
>
End of message, stopping processing here.

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


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

Processed: tagging 736925

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 736925 - security
Bug #736925 [linux-patch-grsecurity2] Does not apply to current kernel versions 
(3.2.y, 3.12.y, 3.13)
Removed tag(s) security.
>
End of message, stopping processing here.

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


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

Processed: tagging 638756

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 638756 - security
Bug #638756 [vflib3] vflib3: please remove t1lib dependency
Removed tag(s) security.
>
End of message, stopping processing here.

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


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

Processed: tagging 579227

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 579227 - security
Bug #579227 [src:jscoverage] Embedded code copy: libmozjs
Removed tag(s) security.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
579227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579227
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#736413: [xmds-devel] missing licenses in debian/copyright

[Rafael Laboissiere]

* Graham Dennis  [2014-01-29 16:09]:


[snip]

I have rewritten the offending code, which I release under the same 
license as the rest of XMDS2, i.e. GPL2.


Great, thanks, this was the critical issue.  I will soon release a new 
version of the package with the changes, and xmds2 will hopefully be able 
to migrate into Debian testing.


Best,

Rafael


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

Bug#736413: [xmds-devel] missing licenses in debian/copyright

[Graham Dennis]

Hi Rafael,

> A bug with severity level "serious" has been filed against the Debian 
> package for xmds2, regarding the licensing conditions of several files. 
> You can find the details in http://bugs.debian.org/736413 (BTW, thanks to 
> Thorsten Alteholz, who had the patience of verifying the licensing 
> conditions of the files in the Debian xmds2 package).
> 
> The package is currently unsuitable for inclusion in Debian, because it 
> violates the DFSG (Debian Free Software Guidelines).  In order to avoid 
> the exclusion of xmds2, we must address the problems indicated in the bug 
> report:
> 
> * Thorsten Alteholz  [2014-01-23 13:03]:
> 
>> please add the licenses of xmds-2.2.0/documentation/_static/* to 
>> debian/copyright. Most of these files are not GFDL.
> 
> Files *.css and *.js come from third-party projects, like Sphinx, jQuery 
> and Underscore, which have DFSG-compliant licenses.  The file 
> pygments.css has no copyright notice, but I think it is generated by 
> Sphinx, so we are fine here.
> 
pygments.css is generated by Pygments, which is under a 2-clause BSD license: 
https://bitbucket.org/birkenfeld/pygments-main/src/3e451a3806d9215bae592d9c28321076e5e046ef/LICENSE?at=default

> There are several image files in documentation/_static/ whose licensing 
> conditions are not clear.  I think that most of them come from Sphinx. 
> As regards the ones specific from XMDS, like xmds_logo.png, I will assume 
> that they are released under the GFDL.
> 
The generic ones are produced by Sphinx, and the XMDS-specific ones are 
released under GFDL.

>> xmds-2.2.0/documentation/latex/tabulary.sty seems to be LPPL, can you 
>> please check that this is really under v1.3
> 
> I can address this issue by removing the *.sty and *.cls files from the 
> upstream tarball and repacking it.  At any rate, these files are not 
> needed for the xmds2-doc package.
> 

I have removed documentation/latex in our buildscript for release versions.  It 
will not be there in future versions.  The built PDF documentation will be in 
documentation/xmds2.pdf

>> Parts of Vectors/VectorInitialisationFromXSIL.tmpl and thus 
>> Vectors/VectorInitialisationFromXSIL.py are licensed under APSL which 
>> is not compatible with DFSG. Can you please check with upstream?
> 
> This is really annoying since the APSL is really DFSG-incompatible, see:
> 
> https://wiki.debian.org/DFSGLicenses#Licenses_that_are_DFSG-incompatible
> 
> If this issue cannot be addressed, then xmds2 will never migrate into 
> Debian stable.
> 
> If I understand correctly the situation, the C code scrap in 
> VectorInitialisationFromXSIL.tmpl that was imported from CFByteOrder.h 
> (which is released under the APSL v2), is included in the .cc file 
> generated by xmds2 only if the input simulation file contains:
> 
>  
> 
> Simulation files with the above definition only work if XMDS1 is 
> installed.  Do you think that we can drop the support for kind="xsil" in 
> the Debian package?  This would make the pacakge fully DFSG-compliant.
> 
> Another solution is to replace the offending parts of 
> VectorInitialisationFromXSIL.tmpl by some free code.
> 

I have rewritten the offending code, which I release under the same license as 
the rest of XMDS2, i.e. GPL2.

Cheers,
Graham

Bug#736969: (possible) CVE request: suPHP 0.7.2 release fixed a possible arbitrary code execution

[Salvatore Bonaccorso]

Hi

I do not have a commit reference for this: suPHP 0.7.2 release fixed a
security ssue that was introduced with the 0.7.0 release. From
Upstream[1]:

cut-cut-cut-cut-cut-cut-
suPHP 0.7.2 has been released.
This release fixes a security issue that was introduced with the 0.7.0
release. This issue affected the source-highlighting feature and could
only be exploited, if the suPHP_PHPPath option was set. In this case
local users which could create or edit .htaccess files could possibly
execute arbitrary code with the privileges of the user the webserver
was running as.
cut-cut-cut-cut-cut-cut-

Does this have already a CVE and/or should one be assigned?

suPHP is furthermore not anymore maintained upstream, see [3].

 [1] http://www.suphp.org/Home.html
 [2] http://bugs.debian.org/736969
 [3] https://lists.marsching.com/pipermail/suphp/2013-May/002554.html

Regards,
Salvatore


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

Bug#736969: New upstream version fixing security issue

[Moritz Muehlenhoff]

On Tue, Jan 28, 2014 at 10:15:39PM +0200, Adrian Bunk wrote:
> Package: src:suphp
> Version: 0.7.1-3
> Severity: serious
> Tags: security
> 
> >>From http://www.suphp.org/Home.html
> 
> suPHP 0.7.2 has been released.
> This release fixes a security issue that was introduced with the 0.7.0 
> release. This issue affected the source-highlighting feature and could only 
> be exploited, if the suPHP_PHPPath option was set. In this case local users 
> which could create or edit .htaccess files could possibly execute arbitrary 
> code with the privileges of the user the webserver was running as. 
> 
> I am not sure whether this warrants a DSA, but I've set the severity RC
> since not upgrading to a new point release that fixes a security bug for
> jessie would be stupid (Ubuntu has already upgraded the package for trusty).
> 
> Note that this package is orphaned, so a QA upload (that also fixes
> the maintainer field) is required.

Quoting from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731758 and
https://lists.marsching.com/pipermail/suphp/2013-May/002554.html upstream
is dead and we should go ahead with the removal from the archive.

Cheers,
Moritz


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

Bug#736739: [src:lemonldap-ng] Sourceless file

[Paul Wise]

On Wed, Jan 29, 2014 at 1:27 PM, Xavier wrote:

> This file is in the source tree only in this form : jqueryui.com
> provides customized files containing only wanted features. So if you
> want to drom this file in the source tree, debuild will have to download
> jquery-ui from Internet ?

Downloading from the Internet during build isn't acceptable.

Personally, I think what you should do is depend on the relevant
packages containing the chosen parts of the custom file (and package
any missing parts), register a dpkg trigger and generate a new JS file
whenever the chosen parts change. Either that or remove the JS from
the package.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


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

Bug#736739: [src:lemonldap-ng] Sourceless file

[Xavier]

Le 28/01/2014 09:37, Bastien ROUCARIES a écrit :
> 
> Le 28 janv. 2014 06:38, "Xavier"  > a écrit :
>>
>> Bastien wrote :
>> > Package: src:lemonldap-ng
>> > Version:  1.2.5-1
>> > Severity: serious
>> > User: debian...@lists.debian.org 
>> > Usertags: source-contains-prebuilt-javascript-object
>> > X-Debbugs-CC: ftpmas...@debian.org 
>> >
>> > I could not find the source of:
>> > lemonldap-ng 1.2.5-1 (source)
>> >
>> >
> lemonldap-ng-portal/example/skins/common/jquery-ui-1.8.5.custom.min.js
>> >
>>
> lemonldap-ng-manager/example/skins/default/js/jquery-ui-1.8.6.custom.min.js
>> >
>> > Bastien
>>
>> Hi Bastien,
>>
>> I've a little question, what kind of information do you want for this
>> object ? Also, why is it a serious bug ? d/copyright mentions the source
> Ftpmaster dors not consider minified JavaScript as preferred form of
> modification.
> 
> You should rebuilt it from true source .js.
> 
> In this case you should drop this file and repack the origin tar ball
> 
> See #debian-qa for help.
> 
> Bastien
>> Regards,
>> Xavier

This file is in the source tree only in this form : jqueryui.com
provides customized files containing only wanted features. So if you
want to drom this file in the source tree, debuild will have to download
jquery-ui from Internet ?


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

Bug#733250: marked as done (seqan: FTBFS - `.../debian/seqan-dev': No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jan 2014 05:19:48 +
with message-id 
and subject line Bug#733250: fixed in seqan 1.4.1-3
has caused the Debian Bug report #733250,
regarding seqan: FTBFS - `.../debian/seqan-dev': 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.)


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

Builds of seqan covering only its architecture-dependent binary packages
(as on the autobuilders, or with debuild -B) have been failing:

  find /«PKGBUILDDIR»/debian/seqan-dev  -type f -name LICENSE -delete
  find: `/«PKGBUILDDIR»/debian/seqan-dev': No such file or directory
  make[1]: *** [override_dh_install] Error 1
  make[1]: Leaving directory `/«PKGBUILDDIR»'
  make: *** [binary-arch] Error 2

Could you please arrange to clean debian/seqan-dev only if it actually
exists?

Thanks!
--- End Message ---
--- Begin Message ---
Source: seqan
Source-Version: 1.4.1-3

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated seqan package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 28 Jan 2014 09:09:09 +0100
Source: seqan
Binary: seqan-apps seqan-dev
Architecture: source amd64 all
Version: 1.4.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description: 
 seqan-apps - C++ library for the analysis of biological sequences
 seqan-dev  - C++ library for the analysis of biological sequences (development
Closes: 733250
Changes: 
 seqan (1.4.1-3) unstable; urgency=medium
 .
   * debian/rules:
  - Run test suite only on powerfull architectures (amd64)
at build time
   * deacticate test for apps splazers which fails since some point
 in time after uploading 1.4.1-2
 Closes: #733250
Checksums-Sha1: 
 bddccb9a56b0b0efc48197cad98ca5821a55a8fa 1424 seqan_1.4.1-3.dsc
 c3bfe25f9e135360b559610eb390ed7b1d5733ff 8112 seqan_1.4.1-3.debian.tar.xz
 833c356db4cb06edfc801775e4f3ee00a326bc9b 7394092 seqan-apps_1.4.1-3_amd64.deb
 be6097b20c71df404329eb7308630f0fe6618630 2615260 seqan-dev_1.4.1-3_all.deb
Checksums-Sha256: 
 2e3c30f4b7129ecd0d353d05673c2eac9ef3ef652011e1ecf8bffc27d784b342 1424 
seqan_1.4.1-3.dsc
 36b2628c43c1bb38b08a44d57e5e7c4412efaf1d650fd34593aae99fd08ae703 8112 
seqan_1.4.1-3.debian.tar.xz
 913bb84f2e13ad8952969590a59b6540962d7f6dde31d08c3ba20c65e2cecf03 7394092 
seqan-apps_1.4.1-3_amd64.deb
 659520a1597d5635be84c04527f8c3a9516108d6bcc85a52bde0ad01b1cbc9de 2615260 
seqan-dev_1.4.1-3_all.deb
Files: 
 104f4205e582b24dcaf6c7f7c51c6582 1424 science optional seqan_1.4.1-3.dsc
 13bf8787dd4c92684c840333802b1bb5 8112 science optional 
seqan_1.4.1-3.debian.tar.xz
 47329ae1544ffde89e8272e550e11d2d 7394092 science optional 
seqan-apps_1.4.1-3_amd64.deb
 32c12d835e4ef889c38479e8fe8a7197 2615260 libdevel optional 
seqan-dev_1.4.1-3_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlLoh+wACgkQYDBbMcCf01qyEACfc6KzY9o1bKhS7tH3F5Pu8F9X
EfoAnA25xT/M1Unu1tIrF3+L7httvoc4
=LJBk
-END PGP SIGNATURE End Message ---

Bug#735659: marked as done (remctl: ruby1.8 won't be available on Jessie)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jan 2014 04:48:30 +
with message-id 
and subject line Bug#735659: fixed in remctl 3.8-1
has caused the Debian Bug report #735659,
regarding remctl: ruby1.8 won't be available on Jessie
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.)


-- 
735659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: remctl
Severity: serious
User: debian-r...@lists.debian.org
Usertags: ruby18-removal

Dear maintainer,

remctl produces one or more binary packages that depends on ruby1.8,
or it uses ruby1.8 to build. ruby1.8 is unmaintainable at this point,
and we can't keep it for Jessie. We plan to request its removal in 4
weeks.

Recommendations for some common cases:

If your package contains Ruby programs that are hardcoded to use
ruby1.8, you need to port those to a more recent version. Please use
/usr/bin/ruby instead. Please do not change to /usr/bin/ruby1.9.1 

If your package calls `ruby1.8` during build, please make it call
`ruby` instead. If your scripts don't work with a newer Ruby, you
need to port them. Please do not change `ruby1.8` to `ruby1.9.1` as
it will require more work later when we want to get rid of ruby1.9.1
(and we will).

If your packages builds binary extensions for ruby1.8, you need to
remove those. Please consider building binary extensions for all
supported Ruby versions. You can get a list of supported Ruby
versions at runtime by build-depending on gem2deb and running

$ dh_ruby --print-supported

I'm flagging this bug as release critical, since it's impossible to
have ruby1.8 in the next release.

If you need advice on the best way to handle your package, please
feel free to get in touch with debian-r...@lists.debian.org 
--- End Message ---
--- Begin Message ---
Source: remctl
Source-Version: 3.8-1

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

Debian distribution maintenance software
pp.
Russ Allbery  (supplier of updated remctl 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, 28 Jan 2014 19:50:20 -0800
Source: remctl
Binary: libremctl1 libremctl-dev remctl-client remctl-server libnet-remctl-perl 
php5-remctl python-remctl ruby-remctl
Architecture: source i386
Version: 3.8-1
Distribution: unstable
Urgency: medium
Maintainer: Russ Allbery 
Changed-By: Russ Allbery 
Description: 
 libnet-remctl-perl - Perl client for Kerberos-authenticated command execution
 libremctl-dev - Development files for Kerberos-authenticated command execution
 libremctl1 - Library for Kerberos-authenticated command execution
 php5-remctl - PECL module for Kerberos-authenticated command execution
 python-remctl - Python extension for Kerberos-authenticated command execution
 remctl-client - Client for Kerberos-authenticated command execution
 remctl-server - Server for Kerberos-authenticated command execution
 ruby-remctl - Ruby extension for Kerberos-authenticated command execution
Closes: 735659 736578
Changes: 
 remctl (3.8-1) unstable; urgency=medium
 .
   * New upstream release.
 - remctld now uses libevent for the process event loop, which removes
   the need to poll for child exit and will make the server faster and
   more responsive.
 - Fill each MESSAGE_OUTPUT message from the server with the maximum
   allowed data per the protocol, rather than capping it artificially
   at 65000 octets.
 - Fix a minor server memory leak when processing help commands.
 - Fix a minor client memory leak on errors with protocol one commands.
 - Write out the server PID file atomically.
   * Start building the Ruby extension for Ruby 2.0 and stop building it
 for Ruby 1.8, which is being removed.  (Closes: #735659)
   * Add Depends on ruby | ruby-interpreter to ruby-remctl.  This is
 apparently standard for Ruby extensions, since it will pull in a
 version of Ruby that can use the extension if the Ruby versions of the
 extension match the providers of ruby-interpreter.
   * Drop Replaces

Processed: Re: python-pyhyphen: FTBFS: Permission denied: '/usr/lib/python2.7/dist-packages/hyphen/config.pyc'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream
Bug #642570 [src:python-pyhyphen] python-pyhyphen: FTBFS: Permission denied: 
'/usr/lib/python2.7/dist-packages/hyphen/config.pyc'
Added tag(s) fixed-upstream.

-- 
642570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642570
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#642570: python-pyhyphen: FTBFS: Permission denied: '/usr/lib/python2.7/dist-packages/hyphen/config.pyc'

[Hideki Yamane]

Control: tags -1 fixed-upstream

Hi,

 Upstream has already released version 2.0.4, and it wouldn't cause such
 error (if python-pyhyphen itself is installed). It seems to be not need any
 changes for package to update it.

 see https://pypi.python.org/pypi/PyHyphen


-- 
Hideki Yamane

Bug#736991: libc++: FTBFS on various architectures

[Andreas Beckmann]

Source: libc++
Version: 1.0~svn199600-1
Severity: serious
Justification: fails to build from source

Hi,

libc++ FTBFS on most architectures, including armel/armhf where it
previously built successfully.
https://buildd.debian.org/status/package.php?p=libc%2b%2b

>From the armel buildlog:

[...]
cd libcxx/lib; ./buildit; ln -s libc++.so.1.0 libc++.so;\
ln -s libc++.so.1.0 libc++.so.1;
+ clang++ -c -g -Os -fPIC -nostdinc++ -std=c++11 -fstrict-aliasing -Wall 
-Wextra -Wshadow -Wconversion -Wpadded -Wstrict-aliasing=2 -Wstrict-overflow=4 
-DLIBCXXABI -I../include -I../../libcxxabi/include ../src/algorithm.cpp
+ clang++ -c -g -Os -fPIC -nostdinc++ -std=c++11 -fstrict-aliasing -Wall 
-Wextra -Wshadow -Wconversion -Wpadded -Wstrict-aliasing=2 -Wstrict-overflow=4 
-DLIBCXXABI -I../include -I../../libcxxabi/include ../src/bind.cpp
+ clang++ -c -g -Os -fPIC -nostdinc++ -std=c++11 -fstrict-aliasing -Wall 
-Wextra -Wshadow -Wconversion -Wpadded -Wstrict-aliasing=2 -Wstrict-overflow=4 
-DLIBCXXABI -I../include -I../../libcxxabi/include ../src/chrono.cpp
+ clang++ -c -g -Os -fPIC -nostdinc++ -std=c++11 -fstrict-aliasing -Wall 
-Wextra -Wshadow -Wconversion -Wpadded -Wstrict-aliasing=2 -Wstrict-overflow=4 
-DLIBCXXABI -I../include -I../../libcxxabi/include ../src/condition_variable.cpp
+ clang++ -c -g -Os -fPIC -nostdinc++ -std=c++11 -fstrict-aliasing -Wall 
-Wextra -Wshadow -Wconversion -Wpadded -Wstrict-aliasing=2 -Wstrict-overflow=4 
-DLIBCXXABI -I../include -I../../libcxxabi/include ../src/debug.cpp
+ clang++ -c -g -Os -fPIC -nostdinc++ -std=c++11 -fstrict-aliasing -Wall 
-Wextra -Wshadow -Wconversion -Wpadded -Wstrict-aliasing=2 -Wstrict-overflow=4 
-DLIBCXXABI -I../include -I../../libcxxabi/include ../src/exception.cpp
+ clang++ -c -g -Os -fPIC -nostdinc++ -std=c++11 -fstrict-aliasing -Wall 
-Wextra -Wshadow -Wconversion -Wpadded -Wstrict-aliasing=2 -Wstrict-overflow=4 
-DLIBCXXABI -I../include -I../../libcxxabi/include ../src/future.cpp
+ clang++ -c -g -Os -fPIC -nostdinc++ -std=c++11 -fstrict-aliasing -Wall 
-Wextra -Wshadow -Wconversion -Wpadded -Wstrict-aliasing=2 -Wstrict-overflow=4 
-DLIBCXXABI -I../include -I../../libcxxabi/include ../src/hash.cpp
+ clang++ -c -g -Os -fPIC -nostdinc++ -std=c++11 -fstrict-aliasing -Wall 
-Wextra -Wshadow -Wconversion -Wpadded -Wstrict-aliasing=2 -Wstrict-overflow=4 
-DLIBCXXABI -I../include -I../../libcxxabi/include ../src/ios.cpp
In file included from ../src/ios.cpp:12:
In file included from ../include/ios:216:
In file included from ../include/__locale:15:
In file included from ../include/string:439:
In file included from ../include/algorithm:627:
In file included from ../include/memory:610:
.../include/atomic:662:17: error: cannot compile this atomic library call yet
{return __c11_atomic_fetch_add(&this->__a_, __op, __m);}
^~
1 error generated.
make[1]: Leaving directory `/build/libc++-0S_Ol2/libc++-1.0~svn199600'
   dh_auto_test -a
 fakeroot debian/rules binary-arch
dh binary-arch
   dh_testroot -a
   dh_prep -a
   dh_installdirs -a
   dh_auto_install -a
   dh_install -a
dh_install: libc++-dev missing files (libcxx/lib/*.a), aborting
make: *** [binary-arch] Error 2


The buildsystem seems broken since the build failure gets ignored.
Probably builtit.sh is missing a 'set -e' like is the multi-command in
the rules file. That should start with

  set -e ; cd somewhere ; ./doit ; ./domore


Andreas


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

Bug#727118: FTBFS on sparc due to a not c++11 capable default compiler

[Andreas Beckmann]

Control: found -1 2.0.6-1

On Friday, 17. January 2014 06:48:23 Jari Aalto wrote:
>  ccbuild (2.0.6-1) unstable; urgency=low
>  .
>* New upstream release
>  - libbobcat now requires --std=c++11
>(FTBFS serious; Closes: #727118).

ccbuild still FTBFS on sparc [1] (and ia64, but who cares) because the default 
g++ version there is still at 4.6 which does not support -std=c++11. You may 
need to add an explicit B-D: g++-4.8 [sparc ia64] and override the CXX 
variable in d/rules on these architectures.

[1] 
https://buildd.debian.org/status/fetch.php?pkg=ccbuild&arch=sparc&ver=2.0.6-1&stamp=1389940011

Andreas


-- 
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#727118: FTBFS on sparc due to a not c++11 capable default compiler

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.0.6-1
Bug #727118 {Done: Jari Aalto } [ccbuild] ccbuild: FTBFS 
on several architectures
Marked as found in versions ccbuild/2.0.6-1; no longer marked as fixed in 
versions ccbuild/2.0.6-1 and reopened.

-- 
727118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727118
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#736784: [src:shinken] Sourceless file

[Thibault Cohen]

After more researches, some files are already here :
-
/usr/share/pyshared/shinken/webui/plugins/eue/htdocs/js/videojs/video.min.js
  =>
/usr/share/pyshared/shinken/webui/plugins/eue/htdocs/js/videojs/video.js
-
/usr/share/pyshared/shinken/webui/plugins/eue/htdocs/js/jquery.lightbox-0.5.min.js
  =>
/usr/lib/python2.7/dist-packages/shinken/webui/plugins/eue/htdocs/js/jquery.lightbox-0.5.js

Could you confirm it ?

Thanks !


On 2014-01-26 16:05, bastien ROUCARIES wrote:
> Package: src:shinken
> Version: 1.4-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: source-contains-prebuilt-javascript-object
> X-Debbugs-CC: ftpmas...@debian.org
> 
> I could not find the source of:
> shinken 1.4-2 (source)
> shinken/webui/htdocs/js/jquery-1.6.4.min.js
> shinken/webui/htdocs/js/jquery-jsonp-2.2.1.min.js
> shinken/webui/htdocs/js/jquery-stupidtable.min.js
> shinken/webui/htdocs/js/jquery-ui-1.8.17.custom.min.js
> shinken/webui/htdocs/js/jquery.mobile-1.1.0.min.js
> shinken/webui/htdocs/js/spin.min.js
> shinken/webui/plugins/eue/htdocs/js/jquery.lightbox-0.5.min.js
> shinken/webui/plugins/eue/htdocs/js/videojs/video.min.js
> 
> Please add an override for:
> shinken/webui/htdocs/js/bootstrap.min.js
> 
> 
> 
> 
> Bastien
> 


-- 
Cordialement
--
Thibault Cohen
Leader de pratique Supervision,
Spécialiste supervision
Savoir-faire Linux Inc.
Tel: (514) 276-5468 #134


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

Bug#736608: qthid-fcd-controller: FTBFS on kfreebsd

[Steven Chamberlain]

Control: tags -1 + patch

Hi,

This could be fixed by building hid-libusb.c on kfreebsd-any.  I
don't know a specific qmake platform specifier for this, but the
patch below (unix but not linux) seems to work nicely, and with
some luck it might work for GNU/Hurd too.

Don't have a Funcube Dongle to test with, however...

--- a/qthid.pro2014-01-29 02:27:39.0 +
+++ b/qthid.pro2014-01-29 02:43:59.747094173 +
@@ -65,6 +65,10 @@
 #SOURCES += hid-libusb.c
 LIBS += -ludev
 SOURCES += hidraw.c
+} else:unix {
+CONFIG += link_pkgconfig
+PKGCONFIG += libusb-1.0
+SOURCES += hid-libusb.c
 }
 
 RESOURCES += \

Thanks,
-- 
Steven Chamberlain
ste...@pyro.eu.org


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

Processed: Re: Bug#736608: qthid-fcd-controller: FTBFS on kfreebsd

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #736608 [src:qthid-fcd-controller] qthid-fcd-controller: FTBFS on kfreebsd
Added tag(s) patch.

-- 
736608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736608
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#736660: smartmontools: FTBFS on kfreebsd (bsd/sys/cdefs.h: No such file or directory)

[Steven Chamberlain]

Control: tags -1 + patch

On 22:02, Julien Cristau wrote:
> during a binNMU smartmontools failed to build, see the logs at
> https://buildd.debian.org/status/package.php?p=smartmontools
> 
> > g++ -DHAVE_CONFIG_H -I.  -DBUILD_INFO='"(local build)"' 
> > -DSMARTMONTOOLS_SYSCONFDIR='"/etc"' 
> > -DSMARTMONTOOLS_DRIVEDBDIR='"/var/lib/smartmontools/drivedb"' 
> > -DSMARTMONTOOLS_SAVESTATES='"/var/lib/smartmontools/smartd."' 
> > -DSMARTMONTOOLS_ATTRIBUTELOG='"/var/lib/smartmontools/attrlog."'  -g 
> > -O2 -Wall -W -MT cciss.o -MD -MP -MF .deps/cciss.Tpo -c -o cciss.o cciss.cpp
> > cciss.cpp:28:29: fatal error: bsd/sys/cdefs.h: No such file or directory
> >  #  include 
> >  ^
> > compilation terminated.
> > make[2]: *** [cciss.o] Error 1

This is a missing dependency on libbsd-dev, only affecting kfreebsd.
It must have been brought in indirectly before through a dependency on
one of the freebsd-libs.

This patch would be the quickest way to fix this.  Though personally I
think the code there could use some cleanup.

--- a/debian/control  2013-09-05 13:53:56.0 +0100
+++ b/debian/control  2014-01-29 02:08:46.246113599 +
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Giuseppe Iuculano 
 Uploaders: Florian Maier 
-Build-Depends: debhelper (>= 7), libcam-dev [kfreebsd-i386 kfreebsd-amd64], 
automake1.10, autoconf, libcap-ng-dev [!kfreebsd-i386 !kfreebsd-amd64 
!hurd-i386 !sparc !avr32], libselinux1-dev [!kfreebsd-i386 !kfreebsd-amd64 
!hurd-i386], libusb2-dev [kfreebsd-i386 kfreebsd-amd64], hardening-wrapper
+Build-Depends: debhelper (>= 7), libcam-dev [kfreebsd-i386 kfreebsd-amd64], 
automake1.10, autoconf, libcap-ng-dev [!kfreebsd-i386 !kfreebsd-amd64 
!hurd-i386 !sparc !avr32], libselinux1-dev [!kfreebsd-i386 !kfreebsd-amd64 
!hurd-i386], libusb2-dev [kfreebsd-i386 kfreebsd-amd64], libbsd-dev 
[kfreebsd-i386 kfreebsd-amd64], hardening-wrapper
 Standards-Version: 3.9.4
 Vcs-Git: git://anonscm.debian.org/collab-maint/smartmontools.git
 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/smartmontools.git

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


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

Processed: Re: Bug#736660: smartmontools: FTBFS on kfreebsd (bsd/sys/cdefs.h: No such file or directory)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #736660 [src:smartmontools] smartmontools: FTBFS on kfreebsd 
(bsd/sys/cdefs.h: No such file or directory)
Ignoring request to alter tags of bug #736660 to the same tags previously set

-- 
736660: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736660
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#735116: apt-listbugs: […]/debian.rb:24:in `require': no such file to load -- debian_version (LoadError)

[Antonio Terceiro]

On Mon, Jan 20, 2014 at 11:49:17PM +0100, Francesco Poli wrote:
> On Mon, 20 Jan 2014 14:28:43 -0300 Antonio Terceiro wrote:
> 
> > On Sun, Jan 19, 2014 at 05:33:58PM +0100, Francesco Poli wrote:
> > > On Sun, 19 Jan 2014 10:33:43 +0100 Antonio Terceiro wrote:
> > > 
> > > > On Fri, Jan 17, 2014 at 11:18:46PM +0100, Francesco Poli wrote:
> > > [...]
> > > > > Could you please describe the chosen strategy?
> > > [...]
> > > > 
> > > > we will make the following change:
> > > > 
> > > > - librubyX.Y.Z depends on rubyX.Y.Z
> > > > - rubyX.Y.Z depends on ruby
> > > > - ruby depends on the default ruby
> > > > - ruby conflicts with all obsolete interpreters
> > > > 
> > > > so this will force ruby1.8 to be removed on upgrades.
> > > 
> > > Thanks for your reply, Antonio.
> > > 
> > > So this will force everyone using any version of Ruby to also have the
> > > default version, no matter what...
> > 
> > one bit I forgot: we also decided that we won't support more than one
> > version in stable releases, so the 'default' version is actually the
> > unique one.
> 
> I am not too happy to hear that: as far as I know, Debian gives more
> choice to users for other languages (such as Python, AWK, all GCC
> languages, ...).
> I hope this situation will improve in the future. I think that
> supporting at least a couple of major versions (a more mature one, used
> as default interpreter, and a more recent bleeding edge one) would be
> great.

Well, choices need people to support them. With 2 Ruby versions security
problems often need 6 different uploads¹ that have to be built and
tested, and I prefer to spend only half that time and spend the other
half doing other things in Debian. :)

¹ 2 versions x 3 suites (unstable, stable, oldstable)

Also, code that works Ruby 1.9 will mostly work with newer versions,
while the interpreter runtime gets better and better, so I don't see
much the point of keeping multiple versions around.

-- 
Antonio Terceiro 


signature.asc
Description: Digital signature

Bug#736957: marked as done (FTBFS[!linux]: ALSA MIDI not supported)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jan 2014 01:22:29 +0100
with message-id 

and subject line Re: Bug#736957: FTBFS[!linux]: ALSA MIDI not supported
has caused the Debian Bug report #736957,
regarding FTBFS[!linux]: ALSA MIDI not supported
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.)


-- 
736957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: drumkv1
Version: 0.3.6-1
Severity: serious
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd

Hi,

debian/rules runs configure with --enable-alsa-midi only on Linux.

Actually on kfreebsd-* and hurd it is necessary to do the opposite:
configure with --disable-alsa-midi, otherwise support for it is
wrongly autodetected due to the presence of salsa headers.

Please see attached patch fixing FTBFS.

Thanks!

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

Kernel: kFreeBSD 9.0-2-amd64-xenhvm
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- a/drumkv1-0.3.6/debian/rules	2013-09-10 15:46:03.0 +0100
+++ b/drumkv1-0.3.6/debian/rules	2014-01-28 19:06:56.433091722 +
@@ -15,6 +15,8 @@
 
 ifeq ($(DEB_HOST_ARCH_OS),linux)
 EXTRA_CONFIGURE_ARGS += --enable-alsa-midi
+else
+EXTRA_CONFIGURE_ARGS += --disable-alsa-midi
 endif
 
 ifeq ($(DEB_HOST_ARCH_CPU),amd64)
--- End Message ---
--- Begin Message ---
Closed with recent upload.
--- End Message ---

Bug#736960: marked as done (FTBFS[!linux]: ALSA MIDI not supported)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jan 2014 00:19:31 +
with message-id 
and subject line Bug#736960: fixed in synthv1 0.3.6-3
has caused the Debian Bug report #736960,
regarding FTBFS[!linux]: ALSA MIDI not supported
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.)


-- 
736960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: synthv1
Version: 0.3.6-1
Severity: serious
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd

Hi,

debian/rules runs configure with --enable-alsa-midi only on Linux.

Actually on kfreebsd-* and hurd it is necessary to do the opposite:
configure with --disable-alsa-midi, otherwise support for it is
wrongly autodetected due to the presence of salsa headers.

Please see attached patch fixing FTBFS.

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

Kernel: kFreeBSD 9.0-2-amd64-xenhvm
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- a/drumkv1-0.3.6/debian/rules	2013-09-10 15:46:03.0 +0100
+++ b/drumkv1-0.3.6/debian/rules	2014-01-28 19:06:56.433091722 +
@@ -15,6 +15,8 @@
 
 ifeq ($(DEB_HOST_ARCH_OS),linux)
 EXTRA_CONFIGURE_ARGS += --enable-alsa-midi
+else
+EXTRA_CONFIGURE_ARGS += --disable-alsa-midi
 endif
 
 ifeq ($(DEB_HOST_ARCH_CPU),amd64)
--- End Message ---
--- Begin Message ---
Source: synthv1
Source-Version: 0.3.6-3

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

Debian distribution maintenance software
pp.
Jaromír Mikeš  (supplier of updated synthv1 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, 29 Jan 2014 00:44:33 +0100
Source: synthv1
Binary: synthv1
Architecture: source amd64
Version: 0.3.6-3
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers 

Changed-By: Jaromír Mikeš 
Description: 
 synthv1- old-school polyphonic synthesizer
Closes: 736960
Changes: 
 synthv1 (0.3.6-3) unstable; urgency=low
 .
   * Fixed FTBS on kfreebsd-* and hurd. (Closes: #736960)
 Thanks to Steven Chamberlain 
Checksums-Sha1: 
 32e2e318d66e5f0700485df09dffbea21391545b 2086 synthv1_0.3.6-3.dsc
 77ae63da6dd8a2e135b04f164dfd83274020a176 3840 synthv1_0.3.6-3.debian.tar.xz
 6a049fc9dc56a0e570ab3bcde52e0077d01f9822 178474 synthv1_0.3.6-3_amd64.deb
Checksums-Sha256: 
 25f696b4dbd21acecd0f74e5dcb834b8a652a1b1336cc1e46d354bb1c5323a6a 2086 
synthv1_0.3.6-3.dsc
 d78cbce20f8044f8f5cb66c3848edefb0efa7c6bfd0a8fc3b4a5201ffb729610 3840 
synthv1_0.3.6-3.debian.tar.xz
 5782956fe89352332e61b4208189892385ab39b334feda19b9bd6df3b9d3eafd 178474 
synthv1_0.3.6-3_amd64.deb
Files: 
 6f19dc5886466ee043fa69b5237377a2 2086 sound optional synthv1_0.3.6-3.dsc
 8a91886cdbaf2cbd4c218fb4c9b42ba1 3840 sound optional 
synthv1_0.3.6-3.debian.tar.xz
 73d3bcfd771c7699dd55fdc7d659b2d4 178474 sound optional 
synthv1_0.3.6-3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJS6EhCAAoJEFsBlFXiuE+lcXoP/1Pb63max+ejwGzQLkECTGJI
0P0R9arxEggzt8wUY2vy740OfIsjeeYuL2rjiYuM35CrtcDd/rWpgLrTRB8GhS/G
wwYl6Tuh5+rrGO2/fwxYbMHUxLuNJmr9eGShWvoFOFBvQHGUSkExFA3mvcyp+Oal
wGw5lskGklfC6MvOYgY7kHUS5wUYBGgCZlOhKRXi1Ywvb8an8WGx8lRbvnGJ6EbJ
/9aK3u3yMpzzKtf+qK/Q1IIRRXufQ2FoyrdmRYA0FS6C+dtac7+9AhMrkNb4NXk/
DM9XuJrqFLFuYU0JjLEKbmIng2IyI/UUA+DYv5RIQwAIfmXb/ZledErf1YbKBt1T
wxV4DZ7CvHb3N7rN9gm3oBRp9r0JL/4cLwmyf/aKk3ydY+pQ9Z056p8t+Mt3Yb3I
WHp1SP7/zfOHpPaxo/ubWNnvKB9hGX/qyge7z5Bi4EzUebHimCC+QZoe2oWROa7o
KfawZ7E7AS16Ebkt1GCKeq3hWKQWMvXfUF3Gu1oHbKP8HRRbrb5gTjhFw1VP8fWZ
5B2FDIddpQRTAnNcnUsmEzdmjrqProGgRfdkytJFcMEa0/ujHizlGQ/8d6s/Ogpi
4UhGxn1BOhz2aZg2x5Y3DcKus2YHQDKiK0RL8GEeW8qtG7VPaQM+89AVZlurmKqP
ylmQy2Vi1axdD90Q30Op
=qfP2
-END PGP SIGNATURE End Message ---

Bug#736959: marked as done (FTBFS[!linux]: ALSA MIDI not supported)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jan 2014 00:19:20 +
with message-id 
and subject line Bug#736959: fixed in samplv1 0.3.6-3
has caused the Debian Bug report #736959,
regarding FTBFS[!linux]: ALSA MIDI not supported
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.)


-- 
736959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samplv1
Version: 0.3.6-2
Severity: serious
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd

Hi,

debian/rules runs configure with --enable-alsa-midi only on Linux.

Actually on kfreebsd-* and hurd it is necessary to do the opposite:
configure with --disable-alsa-midi, otherwise support for it is
wrongly autodetected due to the presence of salsa headers.

Please see attached patch fixing FTBFS.

Thanks!

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

Kernel: kFreeBSD 9.0-2-amd64-xenhvm
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- a/drumkv1-0.3.6/debian/rules	2013-09-10 15:46:03.0 +0100
+++ b/drumkv1-0.3.6/debian/rules	2014-01-28 19:06:56.433091722 +
@@ -15,6 +15,8 @@
 
 ifeq ($(DEB_HOST_ARCH_OS),linux)
 EXTRA_CONFIGURE_ARGS += --enable-alsa-midi
+else
+EXTRA_CONFIGURE_ARGS += --disable-alsa-midi
 endif
 
 ifeq ($(DEB_HOST_ARCH_CPU),amd64)
--- End Message ---
--- Begin Message ---
Source: samplv1
Source-Version: 0.3.6-3

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

Debian distribution maintenance software
pp.
Jaromír Mikeš  (supplier of updated samplv1 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, 29 Jan 2014 00:44:33 +0100
Source: samplv1
Binary: samplv1
Architecture: source amd64
Version: 0.3.6-3
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers 

Changed-By: Jaromír Mikeš 
Description: 
 samplv1- polyphonic sampler synthesizer
Closes: 736959
Changes: 
 samplv1 (0.3.6-3) unstable; urgency=low
 .
   * Fixed FTBS on kfreebsd-* and hurd. (Closes: #736959)
 Thanks to Steven Chamberlain 
Checksums-Sha1: 
 105844ca13fd435faef55c39dbf42e94122386bd 2086 samplv1_0.3.6-3.dsc
 770c6266601b0cdcc2ef9743ec0df4dab9c2f84e 3828 samplv1_0.3.6-3.debian.tar.xz
 7301b8ebec20018ae03b07b148f30b0e8e7deb75 185932 samplv1_0.3.6-3_amd64.deb
Checksums-Sha256: 
 c62941942199d79693563744375c1e95a1f438ab4528eef451c89d2a8be258ba 2086 
samplv1_0.3.6-3.dsc
 2e91d22a15104706c10a9b3267bf5fa4bead308f61083c8f6e8090cc85273fff 3828 
samplv1_0.3.6-3.debian.tar.xz
 a5cd95ec91d9fb4513f74a287b165c5a0166150c511937e3207cc59ac4a17f6e 185932 
samplv1_0.3.6-3_amd64.deb
Files: 
 452a262c4d27e9d46de558492335695b 2086 sound optional samplv1_0.3.6-3.dsc
 3ed53fd43b02f5f405f83d978d86769b 3828 sound optional 
samplv1_0.3.6-3.debian.tar.xz
 e85b57603cfb48be5e2c4e54998f7c37 185932 sound optional 
samplv1_0.3.6-3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJS6EbCAAoJEFsBlFXiuE+lR7wQAIekTUCAMvw+Hus1vHdimIsi
n+8S6qEQ8GYaUQGrURBIOyPXKTfjf3fkwFw9uHH1gPwcdEie4+A7RUKh84rJd/cB
OtmTPxd9oKMzeUEdHcDKpALtUnadd11cj98hipZybzH4Y2YlKlZ0LBarKnJKDWBz
C8frO7GVmcTOsLoTt0uhDJpFbM5zHVBaC3ymPCpkfEtqjj37Gkc7q1eMyFQEO+wl
g6dfKVOVx9DNLvkOHpOR/ss8KqRD1wDmyz3w/IaA/ibwrCB14sZmq6ASlhhlUiti
6yBXw1q3yxiHS702WqGgiVnCGplgwfEgwQ+JiYEMoTMyUYp3UILcLd/PXqzLDlaD
zP++PEWfKqA+eryNlu1ustUUIgvm7ZFbL3mScFiKclKA45cPDjpZgscQ0tREhMok
GharARe1O9Hw16zWsC0mtob68lin6dgLyCY4PTc5UpfA1Zu7gVH9cEaAyhkcBdca
xMEj4aKEaxiqE9gwySyGaiKePvOVC8P0JYlUKuM0+V5u9SOWShbqcmK9kN4i/NFN
Qgu2+PXZ6AdZjoLlI4rx7Sdfz1q1QN+Dfe+CMgBHI9AzW44wGY2TzoQszhHbJGnK
GdkBIlOxfDWSv9UfQeu1Y/8e3abeOYEsXWlzfbhiAO87Na//3Leh/BlmiP/Yrh1x
dh8FnAYjUSItMTHJ6SSg
=Y0lR
-END PGP SIGNATURE End Message ---

Bug#733368: marked as done (scorched3d: FTBFS: ../../launcher/wxdialogs/TrueTypeFont.h:28:31: fatal error: freetype/freetype.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jan 2014 23:34:34 +
with message-id 
and subject line Bug#733368: fixed in scorched3d 43.3.d+dfsg-1
has caused the Debian Bug report #733368,
regarding scorched3d: FTBFS: ../../launcher/wxdialogs/TrueTypeFont.h:28:31: 
fatal error: freetype/freetype.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.)


-- 
733368: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733368
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scorched3d
Version: 43.3+dfsg-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131226 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

On the new 2.5 version the headers are located at
'/usr/include/freetype2/ftglyph.h' instead of
'/usr/include/freetype2/freetype/ftglyph.h' like in previous versions.

Relevant part (hopefully):
> g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
> -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" 
> -DPACKAGE=\"scorched3d\" -DVERSION=\"43\" -DHAVE_OGG=1 -DHAVE_VSNPRINTF=1 
> -DHAVE_SNPRINTF=1 -DHAVE_VASPRINTF=1 -DHAVE_ASPRINTF=1 -DHAVE_ICONV=1 
> -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 
> -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 
> -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_UNISTD_H=1 -DHAVE_ICONV_H=1 -I.  
> -I../../common/porting -I../../common -I../../client -I../../server 
> -I../../launcher 
> -I/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-release-2.8 
> -I/usr/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ 
> -pthread -I/usr/include/freetype2 -I/usr/include/SDL -D_GNU_SOURCE=1 
> -D_REENTRANT -D_FORTIFY_SOURCE=2 -I/usr/X11R6/include -I/usr/X11R6 
> -I/usr/local/include  -g -O2 -fstack-protector --param=ssp-buffer-size=4 
> -Wformat -Werror=format-security -DS3D_DOCDIR=\"/usr/share/doc/scorched3d\" 
> -DS3D_DATADIR=\"/usr/share/games/scorched3d\" -DS3D_BINDIR=\"/usr/games\" -MT 
> MainDialog.o -MD -MP -MF .deps/MainDialog.Tpo -c -o MainDialog.o `test -f 
> '../wxdialogs/MainDialog.cpp' || echo './'`../wxdialogs/MainDialog.cpp
> In file included from ../wxdialogs/MainDialog.cpp:35:0:
> ../../launcher/wxdialogs/TrueTypeFont.h:28:31: fatal error: 
> freetype/freetype.h: No such file or directory
>  #include 
>^
> compilation terminated.
> make[4]: *** [MainDialog.o] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/12/26/scorched3d_43.3+dfsg-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: scorched3d
Source-Version: 43.3.d+dfsg-1

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

Debian distribution maintenance software
pp.
Juhani Numminen  (supplier of updated scorched3d 
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, 28 Jan 2014 21:08:39 +0200
Source: scorched3d
Binary: scorched3d scorched3d-dbg scorched3d-data
Architecture: source amd64 all
Version: 43.3.d+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Juhani Numminen 
Description: 
 scorched3d - 3D artillery game similar to Scorched Earth
 scorched3d-data - data files for Scorched3D game
 scorched3d-dbg - 3D artillery game similar to Scorched Earth, debug data
Closes: 733368
Changes: 
 scorched3d (43.3.d+dfsg-1) unstable; urgency=medium
 .
   [ Juhani Numminen ]
   * Team upload.
   * New upstream release.
   * Update debian/get-orig-source.sh:
 - Run the script in debian/rules get-orig-source target.
 - Us

Bug#735803: marked as done (pillow: FTBFS: dh_movefiles: debian/python3-pil/usr/lib/python3/dist-packages/PIL/_imagingtk.cpython-33m.so not found (supposed to put it in python3-pil.imagetk))

[Debian Bug Tracking System]

Your message dated Tue, 28 Jan 2014 23:33:51 +
with message-id 
and subject line Bug#735746: fixed in pillow 2.2.1-3.1
has caused the Debian Bug report #735746,
regarding pillow: FTBFS: dh_movefiles: 
debian/python3-pil/usr/lib/python3/dist-packages/PIL/_imagingtk.cpython-33m.so 
not found (supposed to put it in python3-pil.imagetk)
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.)


-- 
735746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pillow
Version: 2.2.1-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140114 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):
> running install
> running build
> running build_py
> running build_ext
> running install_lib
> creating /«PKGBUILDDIR»/debian/python3-sane
> creating /«PKGBUILDDIR»/debian/python3-sane/usr
> creating /«PKGBUILDDIR»/debian/python3-sane/usr/lib
> creating /«PKGBUILDDIR»/debian/python3-sane/usr/lib/python3
> creating /«PKGBUILDDIR»/debian/python3-sane/usr/lib/python3/dist-packages
> renaming extension _sane.cpython-33m.so -> 
> _sane.cpython-33m-x86_64-linux-gnu.so
> copying build/lib.linux-x86_64-3.3/_sane.cpython-33m.so -> 
> /«PKGBUILDDIR»/debian/python3-sane/usr/lib/python3/dist-packages/_sane.cpython-33m-x86_64-linux-gnu.so
> copying build/lib.linux-x86_64-3.3/sane.py -> 
> /«PKGBUILDDIR»/debian/python3-sane/usr/lib/python3/dist-packages
> byte-compiling 
> /«PKGBUILDDIR»/debian/python3-sane/usr/lib/python3/dist-packages/sane.py to 
> sane.cpython-33.pyc
> running install_egg_info
> Writing 
> /«PKGBUILDDIR»/debian/python3-sane/usr/lib/python3/dist-packages/pysane-2.0.egg-info
> incdir=$(python3.3 -c 'import sysconfig; 
> print(sysconfig.get_path("include"))'); \
>   mkdir -p debian/python3-pil/$incdir; \
>   install -o root -g root -m 644 \
>   libImaging/Imaging.h \
>   libImaging/ImPlatform.h \
>   libImaging/ImDib.h \
>   debian/python3-pil/$incdir
> abitag=.$(python3.3 -c "import sysconfig; 
> print(sysconfig.get_config_var('SOABI'))"); \
>   dh_movefiles -ppython3-pil.imagetk \
>   --sourcedir=debian/python3-pil \
>   usr/lib/python3/$(basename $(_py_=3.3; python${_py_#python*} -c 
> 'from distutils import sysconfig; 
> print(sysconfig.get_python_lib())'))/PIL/_imagingtk$abitag.so \
>   usr/lib/python3/$(basename $(_py_=3.3; python${_py_#python*} -c 
> 'from distutils import sysconfig; 
> print(sysconfig.get_python_lib())'))/PIL/ImageTk.py
> dh_movefiles: 
> debian/python3-pil/usr/lib/python3/dist-packages/PIL/_imagingtk.cpython-33m.so
>  not found (supposed to put it in python3-pil.imagetk)
> make: *** [install3-python3.3] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/01/14/pillow_2.2.1-3_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: pillow
Source-Version: 2.2.1-3.1

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

Debian distribution maintenance software
pp.
Jonathan Nieder  (supplier of updated pillow 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: Sun, 26 Jan 2014 14:39:10 -0800
Source: pillow
Binary: python-pil python-pil-dbg python-pil.imagetk python-pil.imagetk-dbg 
python-sane python-sane-dbg python3-pil python3-pil-dbg python3-pil.imagetk 
python3-pil.imagetk-dbg python3-sane python3-sane-dbg python-pil-doc 
python-imaging
Architecture: source all amd64
Version: 2.2.1-3.1
Distribution: unstable
Urgency: medium
Maintainer: 

Bug#735746: marked as done (pillow: FTBFS: _imagingtk.cpython-33m.so not found)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jan 2014 23:33:51 +
with message-id 
and subject line Bug#735746: fixed in pillow 2.2.1-3.1
has caused the Debian Bug report #735746,
regarding pillow: FTBFS: _imagingtk.cpython-33m.so not found
to be marked as done.

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

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


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

Hi,

pillow FTBFS like this:

...
Writing 
/home/rst/temp/debian/pillow-2.2.1/debian/python3-sane/usr/lib/python3/dist-packages/pysane-2.0.egg-info
incdir=$(python3.3 -c 'import sysconfig; 
print(sysconfig.get_path("include"))'); \
mkdir -p debian/python3-pil/$incdir; \
install -o root -g root -m 644 \
libImaging/Imaging.h \
libImaging/ImPlatform.h \
libImaging/ImDib.h \
debian/python3-pil/$incdir
abitag=.$(python3.3 -c "import sysconfig; 
print(sysconfig.get_config_var('SOABI'))"); \
dh_movefiles -ppython3-pil.imagetk \
--sourcedir=debian/python3-pil \
usr/lib/python3/$(basename $(_py_=3.3; python${_py_#python*} -c 
'from distutils import sysconfig; 
print(sysconfig.get_python_lib())'))/PIL/_imagingtk$abitag.so \
usr/lib/python3/$(basename $(_py_=3.3; python${_py_#python*} -c 
'from distutils import sysconfig; 
print(sysconfig.get_python_lib())'))/PIL/ImageTk.py
dh_movefiles: 
debian/python3-pil/usr/lib/python3/dist-packages/PIL/_imagingtk.cpython-33m.so 
not found (supposed to put it in python3-pil.imagetk)
make: *** [install3-python3.3] Error 1
...

See also the build logs of powerpcspe and ppc64 at
 http://buildd.debian-ports.org/status/package.php?p=pillow&suite=sid

I checked that the same happens on i386.

Roland


-- System Information:
Debian Release: 7.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: powerpcspe (ppc)

Kernel: Linux 3.9.0-dirty (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: pillow
Source-Version: 2.2.1-3.1

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

Debian distribution maintenance software
pp.
Jonathan Nieder  (supplier of updated pillow 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: Sun, 26 Jan 2014 14:39:10 -0800
Source: pillow
Binary: python-pil python-pil-dbg python-pil.imagetk python-pil.imagetk-dbg 
python-sane python-sane-dbg python3-pil python3-pil-dbg python3-pil.imagetk 
python3-pil.imagetk-dbg python3-sane python3-sane-dbg python-pil-doc 
python-imaging
Architecture: source all amd64
Version: 2.2.1-3.1
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Jonathan Nieder 
Description: 
 python-imaging - Python Imaging Library compatibility layer
 python-pil - Python Imaging Library (Pillow fork)
 python-pil-dbg - Python Imaging Library (debug extension)
 python-pil-doc - Examples for the Python Imaging Library
 python-pil.imagetk - Python Imaging Library - ImageTk Module (Pillow fork)
 python-pil.imagetk-dbg - Python Imaging Library - ImageTk Module (debug 
extension)
 python-sane - Python Imaging Library - SANE interface (Pillow fork)
 python-sane-dbg - Python Imaging Library - SANE interface (debug extension)
 python3-pil - Python Imaging Library (Python3)
 python3-pil-dbg - Python Imaging Library (Python3 debug extension)
 python3-pil.imagetk - Python Imaging Library - ImageTk Module (Python3)
 python3-pil.imagetk-dbg - Python Imaging Library - ImageTk Module (Python3 
debug extension)
 python3-sane - Python Imaging Library - SANE interface (Python3)
 python3-sane-dbg - Python Imaging Library - SANE interface (Python3 debug 
extension)
Closes: 735746
Changes: 
 pillow (2.2.1-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Adjust installation rules for python3 ex

Bug#736784: [src:shinken] Sourceless file

[Thibault Cohen]

On 2014-01-26 16:05, bastien ROUCARIES wrote:
> Package: src:shinken
> Version: 1.4-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: source-contains-prebuilt-javascript-object
> X-Debbugs-CC: ftpmas...@debian.org
> 
> I could not find the source of:
> shinken 1.4-2 (source)
> shinken/webui/htdocs/js/jquery-1.6.4.min.js
> shinken/webui/htdocs/js/jquery-jsonp-2.2.1.min.js
> shinken/webui/htdocs/js/jquery-stupidtable.min.js
> shinken/webui/htdocs/js/jquery-ui-1.8.17.custom.min.js
> shinken/webui/htdocs/js/jquery.mobile-1.1.0.min.js
> shinken/webui/htdocs/js/spin.min.js
> shinken/webui/plugins/eue/htdocs/js/jquery.lightbox-0.5.min.js
> shinken/webui/plugins/eue/htdocs/js/videojs/video.min.js
> 
> Please add an override for:
> shinken/webui/htdocs/js/bootstrap.min.js
> 
> 
> 
> 
> Bastien
> 


Hello !

Thanks for your report.

I will add all source file but I will delete the "eue" plugin (I just
didn't find all source files ...)

About the "bootstrap.min.js", what do you mean by "add an override" ?


Thanks

Thibault Cohen


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

Bug#733354: marked as done (gramophone2: FTBFS: GRAMophone.y:109:3: error: expected ';' before '}' token)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jan 2014 22:48:38 +
with message-id 
and subject line Bug#733354: fixed in gramophone2 0.8.13a-3
has caused the Debian Bug report #733354,
regarding gramophone2: FTBFS: GRAMophone.y:109:3: error: expected ';' before 
'}' token
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.)


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

Hi,

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

Relevant part (hopefully):
> gcc -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 
> -Wformat -Werror=format-security -O2 -lm -Wl,-z,relro -o gramophone2 
> GRAMophone.c\
>   grammyVM.c init.c midicode.c\
>   midifile.c expcode.c debug.c errors.c\
>   hash.c GRAMophone.tab.c
> In file included from GRAMophone.y:40:0:
> GRAMophone.l: In function 'yylex':
> GRAMophone.l:250:42: warning: cast to pointer from integer of different size 
> [-Wint-to-pointer-cast]
>yy_switch_to_buffer(
>   ^
> GRAMophone.y: In function 'yyparse':
> GRAMophone.y:109:3: error: expected ';' before '}' token
>}
>^
> GRAMophone.y:454:29: warning: cast to pointer from integer of different size 
> [-Wint-to-pointer-cast]
>  if(!(noteVarTempBis=(pnote_var)dhSearch(yytext, 0)) && 
>  ^
> GRAMophone.y:455:29: warning: cast to pointer from integer of different size 
> [-Wint-to-pointer-cast]
> !(noteVarTempBis=(pnote_var)dhSearch(yytext, 1)))  
>  ^
> GRAMophone.y:459:29: warning: cast to pointer from integer of different size 
> [-Wint-to-pointer-cast]
>  if(!(noteVarTempBis=(pnote_var)dhSearch(yytext, 1)))
>  ^
> make[1]: *** [default] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/12/26/gramophone2_0.8.13a-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: gramophone2
Source-Version: 0.8.13a-3

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

Debian distribution maintenance software
pp.
Francesco Namuri  (supplier of updated gramophone2 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, 28 Jan 2014 23:28:11 +0100
Source: gramophone2
Binary: gramophone2
Architecture: source amd64
Version: 0.8.13a-3
Distribution: unstable
Urgency: medium
Maintainer: Francesco Namuri 
Changed-By: Francesco Namuri 
Description: 
 gramophone2 - GRAMophone II is an algorithmic music generator
Closes: 733354
Changes: 
 gramophone2 (0.8.13a-3) unstable; urgency=medium
 .
   * switched to quilt patch system, migrated all the existing patches.
   * addes GRAMophone.y patch to fix a compilation issue. (Closes: #733354)
   * debian/control: Standards-Version updated to 3.9.5, no changes needed.
   * debian/rules: Added madro needed by quilt.
   * debian/control: updated maintainer entry, changed to my debian email.
Checksums-Sha1: 
 9129100f8f8cb0e86fe6b13ea89e8a054e3bf9ef 1779 gramophone2_0.8.13a-3.dsc
 1e44cb1f07e6c6761e025148e9db0b11cc21d542 2912 
gramophone2_0.8.13a-3.debian.tar.xz
 98af5763002679fd1945f6bca36a67ee1555d28e 55356 gramophone2_0.8.13a-3_amd64.deb
Checksums-Sha256: 
 5204c7c13179c3a7615414ad9f29d361b8eebf591f64bc949dfdeba1fbbdcc96 1779 
gramophone2_0.8.13a-3.dsc
 819cb56750bb5d4acba6df883b1bd58edea4fd39fbe5eebb1f23a69bd8ff

Bug#736334: marked as done (Sqlite3 backend not more working)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jan 2014 21:49:48 +
with message-id 
and subject line Bug#736656: fixed in libdbi-drivers 0.9.0-2
has caused the Debian Bug report #736656,
regarding Sqlite3 backend not more working
to be marked as done.

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

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


-- 
736656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnucash
Version: 1:2.6.0-1
Severity: grave

I use gnucash daily, with the sqlite3 backend for all my stuff. Today after
updating my this sid box, gnucash is not more able to load any sqlite3 gnucash
file (with a message like: no suitable backend found for file .gnucash).
All worked perfectly and my files are still usable on other sid boxes.
Even cleaning the guile cache gave no results.

Note: both testing and sid libdbd-sqlite3 backends give the problems.

Curiously the list of today upgrades on this box seem unrelated:

2014-01-22 09:41:47 upgrade djvulibre-bin:i386 3.5.25.4-2 3.5.25.4-3
2014-01-22 09:41:53 upgrade libdjvulibre-text:all 3.5.25.4-2 3.5.25.4-3
2014-01-22 09:41:57 upgrade libdjvulibre21:i386 3.5.25.4-2 3.5.25.4-3
2014-01-22 09:42:01 upgrade libffi6:i386 3.0.13-11 3.0.13-12
2014-01-22 09:42:04 upgrade slrn:i386 1.0.1-9 1.0.1-10
2014-01-22 09:42:10 upgrade djvulibre-desktop:all 3.5.25.4-2 3.5.25.4-3
2014-01-22 09:42:14 upgrade gnash:i386 0.8.11~git20130903-3 
0.8.11~git20140121+dfsg-1
2014-01-22 09:42:18 upgrade gnash-common:i386 0.8.11~git20130903-3 
0.8.11~git20140121+dfsg-1
2014-01-22 09:42:25 upgrade libdbi1:i386 0.8.4-6 0.9.0-1
2014-01-22 09:42:28 upgrade libdbd-sqlite3:i386 0.8.3-1+s-5+b1 0.9.0-1
2014-01-22 09:42:34 upgrade libio-socket-ssl-perl:all 1.965-1 1.966-1
2014-01-22 09:42:38 upgrade python-sphinx:all 1.2.1+dfsg-1 1.2.1+dfsg-2
2014-01-22 09:42:47 upgrade sphinx-common:all 1.2.1+dfsg-1 1.2.1+dfsg-2
2014-01-22 09:42:57 upgrade libjs-sphinxdoc:all 1.2.1+dfsg-1 1.2.1+dfsg-2
2014-01-22 09:42:59 upgrade python-opengl:all 3.0.1-1 3.0.2-1
2014-01-22 09:43:52 upgrade r-cran-foreign:i386 0.8.57-1 0.8.58-1
2014-01-22 09:43:56 upgrade sphinx-doc:all 1.2.1+dfsg-1 1.2.1+dfsg-2
2014-01-22 09:44:04 upgrade pqiv:i386 2.0-1 2.1.1-1
2014-01-22 09:48:37 upgrade libpoppler-glib8:i386 0.18.4-10 0.22.5-4
2014-01-22 09:48:39 upgrade libsane:i386 1.0.24-1.1 1.0.24-1.1+b1
2014-01-22 09:48:50 upgrade libpoppler-dev:i386 0.18.4-10 0.22.5-4
2014-01-22 09:48:52 upgrade libx264-dev:i386 3:0.140.2377+git1ca7bb9-dmo3 
3:0.142.2389+git956c8d8-dmo1
2014-01-22 09:48:53 upgrade poppler-utils:i386 0.18.4-10 0.22.5-4
2014-01-22 09:48:54 upgrade i3:i386 4.7-1 4.7.1-1
2014-01-22 09:48:55 upgrade i3-wm:i386 4.7-1 4.7.1-1
2014-01-22 12:23:14 upgrade libdbd-sqlite3:i386 0.9.0-1 0.8.3-1+s-5+b1 < 
downgrade, without result.

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

Kernel: Linux 3.12-1-686-pae (SMP w/1 CPU core)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnucash depends on:
ii  gnucash-common 1:2.6.0-1
ii  guile-2.0  2.0.9+1-1
ii  guile-2.0-libs 2.0.9+1-1
ii  libaqbanking34 5.3.1beta-2
ii  libc6  2.17-97
ii  libcairo2  1.12.16-2
ii  libcrypt-ssleay-perl   0.58-1+b1
ii  libdate-manip-perl 6.42-1
ii  libdbi10.9.0-1
ii  libfinance-quote-perl  1.18-1
ii  libgdk-pixbuf2.0-0 2.28.2-1+b1
ii  libglib2.0-0   2.36.4-1
ii  libgnome-keyring0  3.8.0-2
ii  libgnomecanvas2-0  2.30.3-2
ii  libgoffice-0.8-8   0.8.17-3
ii  libgtk2.0-02.24.22-1
ii  libgwengui-gtk2-0  4.9.0beta-1
ii  libgwenhywfar604.9.0beta-1
ii  libhtml-tableextract-perl  2.11-1
ii  libhtml-tree-perl  5.03-1
ii  libktoblzcheck1c2a 1.44-1
ii  libofx41:0.9.4-2.1
ii  libpango-1.0-0 1.36.0-1+b1
ii  libpangocairo-1.0-01.36.0-1+b1
ii  libpython2.7   2.7.6-5
ii  libwebkitgtk-1.0-0 2.2.3-1+b1
ii  libwww-perl6.05-2
ii  libx11-6   2:1.6.2-1
ii  libxml22.9.1+dfsg1-3
ii  libxslt1.1 1.1.28-2
ii  perl   5.18.2-2
ii  zlib1g 1:1.2.8.dfsg-1

Versions of packages gnucash recommends:
ii  gnucash-docs  2.6.0-1
ii  yelp  3.10.1-1

Versions of packages gnucash suggests:
pn  libdbd-mysql
pn  libdb

Bug#728139: brutefir: FTBFS on kfreebsd-i386: fftw_convolver.c:(.text+0x5288): undefined reference to `convolver_sse_convolve_add'

[Steven Chamberlain]

tags 728139 + patch
user debian-...@lists.debian.org
usertags 728139 kfreebsd
thanks

Hi,

This happens because, only on Linux i386, `-msse` is enabled and so
function convolver_sse_convolve_add is compiled.

Is that allowed by Debian policy?  A real 386 or 486 may not be able to
run it.

If `-msse` is not enabled, the code fails to build instead (as seen on
kfreebsd-i386) unless the attached patch is used.

Thanks,
Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org
--- brutefir-1.0l/fftw_convolver.c 2013-10-06 12:45:49.0 +0100
+++ brutefir-1.0l/fftw_convolver.c 2014-01-28 21:39:53.950114660 +
@@ -264,7 +264,7 @@
 memcpy(_d, output_cbuf, n_fft * sizeof(real_t));
 */
 switch (opt_code) {
-#if defined(__ARCH_IA32__) || defined(__ARCH_X86_64__)
+#if defined(__ARCH_X86_64__)
 case OPT_CODE_SSE:
convolver_sse_convolve_add(input_cbuf, coeffs, output_cbuf,
n_fft >> 3);

Processed: Re: Bug#728139: brutefir: FTBFS on kfreebsd-i386: fftw_convolver.c:(.text+0x5288): undefined reference to `convolver_sse_convolve_add'

[Debian Bug Tracking System]

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

> tags 728139 + patch
Bug #728139 [src:brutefir] brutefir: FTBFS on kfreebsd-i386: 
fftw_convolver.c:(.text+0x5288): undefined reference to 
`convolver_sse_convolve_add'
Added tag(s) patch.
> user debian-...@lists.debian.org
Setting user to debian-...@lists.debian.org (was ste...@pyro.eu.org).
> usertags 728139 kfreebsd
There were no usertags set.
Usertags are now: kfreebsd.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
728139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728139
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#736656: marked as done (libdbi-drivers: drivers not found anymore, due to multi-arch)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jan 2014 21:49:48 +
with message-id 
and subject line Bug#736656: fixed in libdbi-drivers 0.9.0-2
has caused the Debian Bug report #736656,
regarding libdbi-drivers: drivers not found anymore, due to multi-arch
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.)


-- 
736656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdbi-drivers
Version: 0.9.0-1
Severity: grave
Justification: renders package unusable

libdbi1 0.9.0-1 is built with a multi-arch, and will search for
drivers in a multi-arch directory, but the binaries produced from
libdbi-drivers still produce packages that use the old, non-multiarch
directory. This renders any software using libdbi unusable, as they
will not be able to find drivers.

(Originally reported by Matt Zagrabelny  on the
syslog-ng mailing list)

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

Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: libdbi-drivers
Source-Version: 0.9.0-2

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated libdbi-drivers 
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, 28 Jan 2014 21:58:15 +0100
Source: libdbi-drivers
Binary: libdbd-sqlite libdbd-sqlite3 libdbd-mysql libdbd-pgsql libdbd-freetds
Architecture: source amd64
Version: 0.9.0-2
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description: 
 libdbd-freetds - Freetds database server driver for libdbi
 libdbd-mysql - MySQL database server driver for libdbi
 libdbd-pgsql - PostgreSQL database server driver for libdbi
 libdbd-sqlite - SQLite database driver for libdbi
 libdbd-sqlite3 - SQLite3 database driver for libdbi
Closes: 736656
Changes: 
 libdbi-drivers (0.9.0-2) unstable; urgency=medium
 .
   [ Laszlo Boszormenyi ]
   * Multi-arch package (closes: #736656).
 .
   [ Prach Pongpanich ]
   * Remove obsolete debian/*.dir files.
   * Disable all tests if asked to via DEB_BUILD_OPTIONS .
Checksums-Sha1: 
 1bf277f3b61cd66d0238af8f9cc8d75e1f2d77a7 2443 libdbi-drivers_0.9.0-2.dsc
 3e8111f5f41f214ba08860a989bf885ee16d8553 9136 
libdbi-drivers_0.9.0-2.debian.tar.xz
 693e1c9d90895e90b0665ff89128f3f1b2660571 177666 libdbd-sqlite_0.9.0-2_amd64.deb
 6ed7752679427ec1b4649d82f2d20357bdcb192c 179680 
libdbd-sqlite3_0.9.0-2_amd64.deb
 9e46d9f14c320daae52132cc434786d5bf6e4a3f 151380 libdbd-mysql_0.9.0-2_amd64.deb
 8b8d7bb0a45e0a37ec80055c720f0e75f8701630 150046 libdbd-pgsql_0.9.0-2_amd64.deb
 5ae1dcf5bb04294da845fb90c785cd588f0aa423 17654 libdbd-freetds_0.9.0-2_amd64.deb
Checksums-Sha256: 
 5f81f726632f2a3630d97b4ed5f0169dace9c6da53c5bba6f3e45ec1ac8a23ca 2443 
libdbi-drivers_0.9.0-2.dsc
 4e815691486fcbb77afa771732bc359e53226f7164cce26eea8cf8a9e494a0d9 9136 
libdbi-drivers_0.9.0-2.debian.tar.xz
 941452495f6c4059374e50999e64bef291317aeb36076f9c326dae4262b7ef27 177666 
libdbd-sqlite_0.9.0-2_amd64.deb
 940ac9ae591f4e3845c2127323a6371230420abd2a32ed60b5f03cad1258ecf2 179680 
libdbd-sqlite3_0.9.0-2_amd64.deb
 287e0d7d62690de996830ac225146d50659db05cef672d0d9201f2a6913490aa 151380 
libdbd-mysql_0.9.0-2_amd64.deb
 c726214fd47aa6611876fae77ac45179e9842e7fdbba5435f996878d5ba22f4d 150046 
libdbd-pgsql_0.9.0-2_amd64.deb
 20608145e62854534ab2acb473c97b9f86bb071156f0c662ed15504e1d184e91 17654 
libdbd-freetds_0.9.0-2_amd64.deb
Files: 
 ff4d8759ecefdfc1f6bfd33a2823f975 2443 libs optional libdbi-drivers_0.9.0-2.dsc
 c6e50309ba19408eebdae29cb4652bee 9136 libs optional 
libdbi-drivers_0.9.0-2.debian.tar.xz
 8326bf00d9f5391b5ddffb4eb30da751 177666 libs optional 
libdbd-sqlite_0.9.0-2

Bug#735410: virtualbox: CVE-2013-5892 CVE-2014-0407 CVE-2014-0406 CVE-2014-0404

[Felix Geyer]

On 15.01.2014 09:19, Moritz Muehlenhoff wrote:
> Package: virtualbox
> Severity: grave
> Tags: security
> 
> http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html
> 
> Several vulnerabilities have been reported in VirtualBox. Details are scarce, 
> so
> please get in touch with upstream for more information on eventual backports
> to oldstable/stable. Judging from the CVSS scores this is likely only local
> denial of service, in that case we likely don't need a DSA.
> 
> CVE-2013-5892   
> CVE-2014-0407
> CVE-2014-0406
> CVE-2014-0404

Upstream kindly provided a patch that fixes the 4 CVEs. Attached are yet 
untested
debdiffs for wheezy and squeeze.
Do you want to handle this through a security update?
According to upstream the vulnerabilities are mostly about users on the VM 
being able
to crash their VM. No ways to execute code on the host are known.

> In addition CVE-2014-0405 seems to affect virtualbox-guest-additions-iso from 
> non-free

I guess we can't really fix that. The only option would be to upgrade the 
package
to 4.1.30 / 3.2.12.

Regards,
Felix
diff -Nru virtualbox-4.1.18-dfsg/debian/changelog 
virtualbox-4.1.18-dfsg/debian/changelog
--- virtualbox-4.1.18-dfsg/debian/changelog 2013-03-31 20:45:33.0 
+0200
+++ virtualbox-4.1.18-dfsg/debian/changelog 2014-01-28 21:18:42.0 
+0100
@@ -1,3 +1,11 @@
+virtualbox (4.1.18-dfsg-2+deb7u2) wheezy; urgency=high
+
+  * Apply fixes from the January 2014 security advisory. (Closes: #735410)
+- Add debian/patches/38-security-fixes-2014-01.patch
+- CVE-2013-5892, CVE-2014-0407, CVE-2014-0406, CVE-2014-0404
+
+ -- Felix Geyer   Tue, 28 Jan 2014 21:12:21 +0100
+
 virtualbox (4.1.18-dfsg-2+deb7u1) unstable; urgency=high
 
   * Fix build failure with the Debian wheezy kernel which backports the drm
diff -Nru virtualbox-4.1.18-dfsg/debian/patches/38-security-fixes-2014-01.patch 
virtualbox-4.1.18-dfsg/debian/patches/38-security-fixes-2014-01.patch
--- virtualbox-4.1.18-dfsg/debian/patches/38-security-fixes-2014-01.patch   
1970-01-01 01:00:00.0 +0100
+++ virtualbox-4.1.18-dfsg/debian/patches/38-security-fixes-2014-01.patch   
2014-01-28 21:20:29.0 +0100
@@ -0,0 +1,471 @@
+--- a/include/VBox/VMMDev.h
 b/include/VBox/VMMDev.h
+@@ -114,6 +114,10 @@
+ 
+ /** Maximum request packet size. */
+ #define VMMDEV_MAX_VMMDEVREQ_SIZE   _1M
++/** Maximum number of HGCM parameters. */
++#define VMMDEV_MAX_HGCM_PARMS   1024
++/** Maximum total size of hgcm buffers in one call. */
++#define VMMDEV_MAX_HGCM_DATA_SIZE   UINT32_C(0x7FFF)
+ 
+ /**
+  * VMMDev request types.
+--- a/src/VBox/Devices/Graphics/DevVGA_VBVA.cpp
 b/src/VBox/Devices/Graphics/DevVGA_VBVA.cpp
+@@ -613,6 +613,13 @@
+ 
+ if (fShape)
+ {
++ if (pShape->u32Width > 8192 || pShape->u32Height > 8192)
++ {
++ Log(("vbvaMousePointerShape: unsupported size %ux%u\n",
++   pShape->u32Width, pShape->u32Height));
++ return VERR_INVALID_PARAMETER;
++ }
++
+  cbPointerData = pShape->u32Width + 7) / 8) * pShape->u32Height + 
3) & ~3)
+  + pShape->u32Width * 4 * pShape->u32Height;
+ }
+--- a/src/VBox/Devices/VMMDev/VMMDev.cpp
 b/src/VBox/Devices/VMMDev/VMMDev.cpp
+@@ -795,6 +795,20 @@
+ 
+ #endif /* VBOX_WITH_PAGE_SHARING */
+ 
++static int vmmdevVerifyPointerShape(VMMDevReqMousePointer *pReq)
++{
++/* Should be enough for most mouse pointers. */
++if (pReq->width > 8192 || pReq->height > 8192)
++return VERR_INVALID_PARAMETER;
++
++uint32_t cbShape = (pReq->width + 7) / 8 * pReq->height; /* size of the 
AND mask */
++cbShape = ((cbShape + 3) & ~3) + pReq->width * 4 * pReq->height; /* + gap 
+ size of the XOR mask */
++if (RT_UOFFSETOF(VMMDevReqMousePointer, pointerData) + cbShape > 
pReq->header.size)
++return VERR_INVALID_PARAMETER;
++
++return VINF_SUCCESS;
++}
++
+ /**
+  * Port I/O Handler for the generic request interface
+  * @see FNIOMIOPORTOUT for details.
+@@ -1163,6 +1177,10 @@
+ /* forward call to driver */
+ if (fShape)
+ {
++pRequestHeader->rc = 
vmmdevVerifyPointerShape(pointerShape);
++if (RT_FAILURE(pRequestHeader->rc))
++break;
++
+ pThis->pDrv->pfnUpdatePointerShape(pThis->pDrv,
+fVisible,
+fAlpha,
+--- a/src/VBox/Devices/VMMDev/VMMDevHGCM.cpp
 b/src/VBox/Devices/VMMDev/VMMDevHGCM.cpp
+@@ -97,6 +97,9 @@
+  */
+ VBOXHGCMSVCPARM *paHostParms;
+ 
++/* Number of elements in paHostParms */
++uint32_t cHostParms;
++
+ /* Linear pointer parameters information. */
+ int cLinPtrs;
+ 
+@@ -250,8 +253,6 @@
+ {
+ int rc = VINF_SUCCESS;
+ 
+-AssertRelease (u32Size > 0);
+-
+ V

Processed: limit package to twinkle, fixed 736670 in 1:1.4.2-3, notfixed 736670 in 1.4.2-3

[Debian Bug Tracking System]

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

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

> fixed 736670 1:1.4.2-3
Bug #736670 {Done: Clint Adams } [twinkle] twinkle 
uninstallable: Depends: libucommon5 but it is not installable
Marked as fixed in versions twinkle/1:1.4.2-3.
> notfixed 736670 1.4.2-3
Bug #736670 {Done: Clint Adams } [twinkle] twinkle 
uninstallable: Depends: libucommon5 but it is not installable
There is no source info for the package 'twinkle' at version '1.4.2-3' with 
architecture ''
Unable to make a source version for version '1.4.2-3'
Ignoring request to alter fixed versions of bug #736670 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
736670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736670
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#724597: marked as done (python3-postgresql is broken with PostgreSQL 9.2+)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jan 2014 21:24:30 +
with message-id 
and subject line Bug#724597: fixed in py-postgresql 1.1.0-1
has caused the Debian Bug report #724597,
regarding python3-postgresql is broken with PostgreSQL 9.2+
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.)


-- 
724597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-postgresql
Version: 1.0.2-1
Severity: grave

python3-postgresql needs porting to PostgreSQL 9.2 and later, where
pg_stat_activity.procpid got renamed to "pid":

$ python3
Python 3.3.2+ (default, Aug  4 2013, 15:50:24) 
[GCC 4.8.1] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import postgresql
>>> db = postgresql.open("pq://localhost/postgres")
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/postgresql/__init__.py", line 88, in open
c.connect()
  File "/usr/lib/python3/dist-packages/postgresql/driver/pq3.py", line 2559, in 
connect
sd = self.sys.startup_data()
  File "/usr/lib/python3/dist-packages/postgresql/lib/__init__.py", line 398, 
in __getattr__
bs = BoundSymbol(sym, db)
  File "/usr/lib/python3/dist-packages/postgresql/lib/__init__.py", line 288, 
in __init__
ps = database.prepare(symbol)
  File "/usr/lib/python3/dist-packages/postgresql/driver/pq3.py", line 2352, in 
prepare
ps._fini()
  File "/usr/lib/python3/dist-packages/postgresql/driver/pq3.py", line 1460, in 
_fini
self.database._pq_complete()
  File "/usr/lib/python3/dist-packages/postgresql/driver/pq3.py", line 2599, in 
_pq_complete
self.typio.raise_error(x.error_message, cause = getattr(x, 'exception', 
None))
  File "/usr/lib/python3/dist-packages/postgresql/driver/pq3.py", line 507, in 
raise_error
self.raise_server_error(error_message, **kw)
  File "/usr/lib/python3/dist-packages/postgresql/driver/pq3.py", line 498, in 
raise_server_error
raise server_error
postgresql.exceptions.UndefinedColumnError: Spalte »procpid« existiert nicht
  CODE: 42703
  LOCATION: File 'parse_expr.c', line 768, in transformColumnRef from SERVER
  POSITION: 147
STATEMENT: [parsing]
  LINE:
FROM pg_catalog.pg_stat_activity WHERE procpid = pg_catalog.pg_backend_pid()
   ^ [line 6, character 40]
  statement_id: py:0x7f8b8055d9d0
  string:
SYMBOL: startup_data
  source:
SELECT
 pg_catalog.version()::text AS version,
 backend_start::text,
 client_addr::text,
 client_port::int
FROM pg_catalog.pg_stat_activity WHERE procpid = 
pg_catalog.pg_backend_pid()
UNION ALL SELECT
 pg_catalog.version()::text AS version,
 NULL::text AS backend_start,
 NULL::text AS client_addr,
 NULL::int AS client_port
LIMIT 1;
LIBRARY: /usr/share/python3-postgresql/libsys.sql
CONNECTION: [closed]
CONNECTOR: [Host] pq://cbe:***@localhost:5432/postgres
  category: None
DRIVER: postgresql.driver.pq3.Driver

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

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

Versions of packages python3-postgresql depends on:
ii  libc6 2.17-92+b1
ii  libjs-jquery  1.7.2+dfsg-3
ii  python3   3.3.2-15

python3-postgresql recommends no packages.

python3-postgresql suggests no packages.

-- no debconf information

Christoph
-- 
c...@df7cb.de | http://www.df7cb.de/


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: py-postgresql
Source-Version: 1.1.0-1

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated py-postgresql 
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

Fo

Bug#733110: wordnet: Please migrate to Ruby 2.0/1.9

[David Suárez]

El Martes, 28 de enero de 2014 16:55:02 Antonio Terceiro escribió:
> Control: tags -1 + patch
> 
> On Tue, Jan 28, 2014 at 07:39:56PM +0100, David Suárez wrote:
> > El Martes, 28 de enero de 2014 14:35:37 Andreas Tille escribió:
> > > Hi,
> > > 
> > > Dmitry E. Oboukhov has injected some Ruby 1.8 code into the wordnet
> > > packaging.  I personally do not speak Ruby and thus can not fix the
> > > problem in an other way than simply droping the goldendict-wordnet
> > > binary package (its data package is created in this way).
> > > 
> > > Since Dmitry has not (yet) respondet to this bug report I would like
> > > to ask the Ruby team to find a patch for the problem in the build
> > > system that fixes the following:
> > > 
> > > 
> > > WARNING: sentidx.vrb format error: ["pet%2:35:00::"]
> > > debian/wn-for-goldendict.rb:300:in `initialize': undefined method
> > > `times'
> > > for "\x01":String (NoMethodError) from
> > > debian/wn-for-goldendict.rb:158:in
> > > `new'
> > > 
> > > from debian/wn-for-goldendict.rb:158:in `get_data'
> > > from debian/wn-for-goldendict.rb:648:in `block (2 levels) in
> > > '
> > > 
> > > from debian/wn-for-goldendict.rb:647:in `each'
> > > 
> > > from debian/wn-for-goldendict.rb:647:in `block in '
> > > from debian/wn-for-goldendict.rb:644:in `foreach'
> > > from debian/wn-for-goldendict.rb:644:in `'
> > > 
> > > If I do not get any help I need to go the unfortunate route to kick
> > > goldendict support again.
> > 
> > The code it's trying to convert an hexadecimal string to an integer.
> > 
> > line 296  -> @w_cnt = [data[3]].pack('H2')[0]
> > changes to -> @w_cnt = data[3].hex
> 
> I don't think so ... he wants to replace pack(**)[0] with
> pack(**).bytes.first

Yep :)

But a c(a|u)t tells me, that the input for the pack's with width ("H2") are 
always 2 caracters long (zero padded) :p


David

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

Bug#736975: FTBFS[!linux]: SIGPWR not implemented

[Steven Chamberlain]

On 28/01/14 21:02, Steven Chamberlain wrote:
> Note that with this patch, it still fails the testsuite as I think
> debian/testsuite-kfreebsd.diff needs to be refreshed.

Attached is a refreshed debian/testsuite-kfreebsd.diff

The patch hunks for 'du' had been merged in upstream.

Thanks,
Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/testsuite/cpio.tests b/testsuite/cpio.tests
index 4cd441a..cef9bfc 100755
--- a/testsuite/cpio.tests
+++ b/testsuite/cpio.tests
@@ -28,6 +28,8 @@ hexdump="\
 
 user=$(id -u)
 group=$(id -g)
+# bsd groups
+group=$(ls -dn . | sed 's/  */ /g' | cut -d' ' -f 4)
 
 rm -rf cpio.testdir cpio.testdir2 2>/dev/null
 
diff --git a/testsuite/pidof.tests b/testsuite/pidof.tests
index 2a06d2b..405c14f 100755
--- a/testsuite/pidof.tests
+++ b/testsuite/pidof.tests
@@ -16,6 +16,7 @@ testing "pidof (exit with success)" "pidof pidof > /dev/null; echo \$?" \
 	"0\n" "" ""
 # We can get away with this because it says #!/bin/sh up top.
 
+true pidof.tests does not return anything on this system || \
 testing "pidof this" "pidof pidof.tests | grep -o -w $$" "$$\n" "" ""
 
 optional FEATURE_PIDOF_SINGLE
diff --git a/testsuite/tar.tests b/testsuite/tar.tests
index 7927020..d6dceba 100755
--- a/testsuite/tar.tests
+++ b/testsuite/tar.tests
@@ -120,6 +120,7 @@ Ok: 0
 SKIP=
 
 optional FEATURE_TAR_CREATE FEATURE_LS_SORTFILES
+true "no hardlinked symlinks" || \
 testing "tar symlinks mode" '\
 rm -rf input_* test.tar 2>/dev/null
 >input_file

Bug#735883: Unrreproducible bug in autopkg test

[Paul Wise]

On Tue, Jan 28, 2014 at 11:09 PM, Tomas Di Domenico wrote:

> [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735883

AFAICT your last mail in the bug thread indicates that you ran the
tests as root so it isn't surprising they succeeded. Check if the file
mentioned by the submitter is present in the system/chroot where you
ran the tests, if it is then you have reproduced the issue, tests
shouldn't modify the system that way.

You also never CCed the submitter so they didn't get any of the mails
in the bug. I would suggest CCing them and asking them how to
reproduce it.

As mentioned by Andreas the solution is to use the same arguments to
the test suite in the autopkgtest as you do in the build-time test:

PYTHONPATH=$(CURDIR):$(PYTHONPATH) PYTHONWARNINGS=d python
csb/test/app.py --generated-resources /tmp

vs

PYTHONWARNINGS=d $python test/app.py 2>&1

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


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

Bug#736975: FTBFS[!linux]: SIGPWR not implemented

[Steven Chamberlain]

Package: busybox
Version: 1:1.22.0-3
Severity: serious
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd

Hi,

busybox FTBFS trying to set up a signal handler for SIGPWR, which is
not used or defined on kfreebsd-* or hurd-i386.  The attached patch
would skip setting up this particular signal handler.

https://buildd.debian.org/status/fetch.php?pkg=busybox&arch=kfreebsd-amd64&ver=1%3A1.22.0-3&stamp=1390906915

Note that with this patch, it still fails the testsuite as I think
debian/testsuite-kfreebsd.diff needs to be refreshed.

Thanks.

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

Kernel: kFreeBSD 9.0-2-amd64-xenhvm
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Description:
 Only handle SIGPWR on platforms that implement it.
 .
 Fixes FTBFS on kfreebsd-* and hurd-i386
From: Steven Chamberlain 

Index: busybox-1.22.0/init/init.c
===
--- busybox-1.22.0.orig/init/init.c	2014-01-28 18:18:16.0 +
+++ busybox-1.22.0/init/init.c	2014-01-28 18:23:19.629099370 +
@@ -1137,7 +1137,9 @@
 		struct sigaction sa;
 
 		bb_signals(0
+#ifdef SIGPWR
 			+ (1 << SIGPWR)  /* halt */
+#endif
 			+ (1 << SIGUSR1) /* halt */
 			+ (1 << SIGTERM) /* reboot */
 			+ (1 << SIGUSR2) /* poweroff */

Bug#736964: [Pkg-xfce-devel] Bug#736964: [lightdm] Password is shown in cleart text while typing

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Tue, Jan 28, 2014 at 08:47:29PM +0100, Slavko wrote:
> Package: lightdm
> Version: 1.8.6-1
> Severity: grave
> 
> Hi,
> 
> after upgrade to this version i try to check, if the autologin timeout
> is working by now. While it is not working yet, i need to type the
> password and i see, that the login dialog shows my password while
> typing in clear text. No asterisks, no bullets, only clear text.

What exactly do you do? How did you configure lightdm? Can you take a
picture or something?
> 
> This is a problem, because it allows another people to see my password
> while typing, until i press enter (to login).

Regards,
- -- 
Yves-Alexis Perez
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBCgAGBQJS6BfDAAoJEG3bU/KmdcCllswH/AhOH43T8TIyupVJ7QuWwEfl
dBNT1F6px/P7ggBIsUEzW5U/SO2FVURWXneWOFF0kqCIg8lM4ShVPu59J6C9W8JL
bxGWOPHWfhVNB4H2908J1LJZUWPaky026Ps/n+zFC9MEmRrsjCMMZOeE+2VWeH5T
5Yn1uoYHx+9edYhe7XVen1PR/teEVRK91DFc2GHjdJH16F/CRpHwpvIxAchCTx7h
Su4raX8Jpvr3YT/0Bdl1ez5wDuWi3ez8CO9rMkFMGA+FLoE2QyRwBUT1SuJjDzxn
om2dVDZKQ2asx4r0PkbZ9a6zIUEqaNGp//YHEkXDpHck/TYVxqHCvasYxLRy9OU=
=31hK
-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#735764: lmms: FTBFS: Xft.h:39:22: fatal error: ft2build.h: No such file or directory

[Julien Cristau]

Control: reassign -1 src:lmms 0.4.10-2.3

On Mon, Jan 27, 2014 at 20:58:33 +0900, Hideki Yamane wrote:

> reassign 735764 src:xft
> thanks
> 
> Hi,
> 
>  It's another FTBFS with freetype 2.5.1
>  Probably this change would fix it.
> 
Absolutely not.  You just get to use xft correctly.

$ pkg-config --cflags xft
-I/usr/include/freetype2  

Cheers,
Julien


signature.asc
Description: Digital signature

Processed: Re: lmms: FTBFS: Xft.h:39:22: fatal error: ft2build.h: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:lmms 0.4.10-2.3
Bug #735764 [src:xft] lmms: FTBFS: Xft.h:39:22: fatal error: ft2build.h: No 
such file or directory
Bug reassigned from package 'src:xft' to 'src:lmms'.
Ignoring request to alter found versions of bug #735764 to the same values 
previously set
Ignoring request to alter fixed versions of bug #735764 to the same values 
previously set
Bug #735764 [src:lmms] lmms: FTBFS: Xft.h:39:22: fatal error: ft2build.h: No 
such file or directory
Marked as found in versions lmms/0.4.10-2.3.

-- 
735764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735764
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#736969: New upstream version fixing security issue

[Adrian Bunk]

Package: src:suphp
Version: 0.7.1-3
Severity: serious
Tags: security

>From http://www.suphp.org/Home.html

suPHP 0.7.2 has been released.
This release fixes a security issue that was introduced with the 0.7.0 release. 
This issue affected the source-highlighting feature and could only be 
exploited, if the suPHP_PHPPath option was set. In this case local users which 
could create or edit .htaccess files could possibly execute arbitrary code with 
the privileges of the user the webserver was running as. 

I am not sure whether this warrants a DSA, but I've set the severity RC
since not upgrading to a new point release that fixes a security bug for
jessie would be stupid (Ubuntu has already upgraded the package for trusty).

Note that this package is orphaned, so a QA upload (that also fixes
the maintainer field) is required.


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

Bug#733110: wordnet: Please migrate to Ruby 2.0/1.9

[David Suárez]

Hi again,

El Martes, 28 de enero de 2014 19:39:56 David Suárez escribió:
> The code it's trying to convert an hexadecimal string to an integer.
> 
> line 296  -> @w_cnt = [data[3]].pack('H2')[0]
> changes to -> @w_cnt = data[3].hex
> 
> Please, check if the generated files are the same :)

Complete patch attached (sorry I didn't have access to any machine until now).

I diff the output of the two versions and they are some minor changes in the 
word ordering (first upper then lowercase), eg:

> +Zealot
> + [m1][p]noun[/p][/m]
> + [m2] [trn]a member of an ancient Jewish sect in Judea in the first 
> century 
> who fought to the death against the Romans and who killed or persecuted Jews 
> who collaborated with the Romans[/trn][/m]
> + [m3][com][c darkgray]•[/c] [p]Hypernyms[/p]: <>, <>, 
<>[/com][/m]
>  zealot
>   [m1][p]noun[/p][/m]
>   [m2] [trn]a fervent and even militant proponent of something[/trn][/m]
> @@ -1276876,10 +1276880,6 @@
>   [m3][com][c dodgerblue]•[/c] [p]Derivationally related forms[/p]: 
<> [c darkgray](for: <>)[/c][/com][/m]
>   [m3][com][c darkgray]•[/c] [p]Hypernyms[/p]: <>, 
> <>, 
<>, <>[/com][/m]
>   [m3][com][c darkgray]•[/c] [p]Hyponyms[/p]: <>, <>, 
<>[/com][/m]
> -Zealot
> - [m1][p]noun[/p][/m]
> - [m2] [trn]a member of an ancient Jewish sect in Judea in the first 
> century 
who fought to the death against the Romans and who killed or persecuted Jews 
who collaborated with the Romans[/trn][/m]
> - [m3][com][c darkgray]•[/c] [p]Hypernyms[/p]: <>, <>, 
<>[/com][/m]
>  zealotry

This is caused by the sort at line 697:

> $CARDS.values.sort.each { |card|

I dunno this can be simply ignored.

David--- ../wn-for-goldendict.rb	2014-01-28 20:14:28.0 +0100
+++ debian/wn-for-goldendict.rb	2014-01-28 20:36:24.0 +0100
@@ -293,14 +293,14 @@
 @offset = data[0].to_i
 @lex_filenum = data[1]
 @pos = data[2]
-@w_cnt = [data[3]].pack('H2')[0]
+@w_cnt = data[3].hex #[data[3]].pack('H2')[0]
 @words = []
 i = 4
 @lex_ids = []
 @w_cnt.times {
   @words << data[i].gsub(/_/, ' ').gsub(/\s*\((p|a|ip)\)\s*$/, '')
   i += 1
-  @lex_ids << [data[i]].pack('h')[0]
+  @lex_ids << data[i].hex #[data[i]].pack('h')[0]
   i += 1
 }
 
@@ -362,8 +362,8 @@
 if (src_target == "")
   return other.words
 else
-  src = [src_target[0, 2]].pack('H2')[0]
-  target = [src_target[2, 2]].pack('H2')[0]
+  src = src_target[0, 2].hex #[src_target[0, 2]].pack('H2')[0]
+  target = src_target[2, 2].hex #[src_target[2, 2]].pack('H2')[0]
   h_src = words[src - 1]
   if (h_src == headword)
 return [other.words[target - 1]]
@@ -374,7 +374,7 @@
   end
   def get_frame_data(headword, frame)
 f_num = frame[0].to_i
-w_num = [frame[1]].pack('H2')[0]
+w_num = frame[1].hex #[frame[1]].pack('H2')[0]
 if (w_num == 0)
   return [$frames[f_num]]
 else

Processed: Re: Bug#733110: wordnet: Please migrate to Ruby 2.0/1.9

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #733110 [wordnet] wordnet: Please migrate to Ruby 2.0/1.9
Added tag(s) patch.

-- 
733110: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733110
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#733110: wordnet: Please migrate to Ruby 2.0/1.9

[Antonio Terceiro]

Control: tags -1 + patch

On Tue, Jan 28, 2014 at 07:39:56PM +0100, David Suárez wrote:
> El Martes, 28 de enero de 2014 14:35:37 Andreas Tille escribió:
> > Hi,
> > 
> > Dmitry E. Oboukhov has injected some Ruby 1.8 code into the wordnet
> > packaging.  I personally do not speak Ruby and thus can not fix the
> > problem in an other way than simply droping the goldendict-wordnet
> > binary package (its data package is created in this way).
> > 
> > Since Dmitry has not (yet) respondet to this bug report I would like
> > to ask the Ruby team to find a patch for the problem in the build
> > system that fixes the following:
> > 
> > 
> > WARNING: sentidx.vrb format error: ["pet%2:35:00::"]
> > debian/wn-for-goldendict.rb:300:in `initialize': undefined method `times'
> > for "\x01":String (NoMethodError) from debian/wn-for-goldendict.rb:158:in
> > `new'
> > from debian/wn-for-goldendict.rb:158:in `get_data'
> > from debian/wn-for-goldendict.rb:648:in `block (2 levels) in '
> > from debian/wn-for-goldendict.rb:647:in `each'
> > from debian/wn-for-goldendict.rb:647:in `block in '
> > from debian/wn-for-goldendict.rb:644:in `foreach'
> > from debian/wn-for-goldendict.rb:644:in `'
> > 
> > 
> > If I do not get any help I need to go the unfortunate route to kick
> > goldendict support again.
> 
> The code it's trying to convert an hexadecimal string to an integer.
> 
> line 296  -> @w_cnt = [data[3]].pack('H2')[0]
> changes to -> @w_cnt = data[3].hex

I don't think so ... he wants to replace pack(**)[0] with
pack(**).bytes.first

$ irb1.8
>> ['1'].pack('H2')[0]
=> 16
>> '1'.hex
=> 1
>> ['1'].pack('H2').bytes.first
=> 16

$ irb1.9.1
>> ['1'].pack('H2')[0]
=> "\x10" # <-- indexing the output of pack() in Ruby 1.9+ has a different 
semantics
>> '1'.hex
=> 1  # <-- not what you want
>> ['1'].pack('H2').bytes.first
=> 16 # <-- you want this

Try the attached patch. Please check the output files though.

-- 
Antonio Terceiro 
diff -Nru wordnet-3.0/debian/control wordnet-3.0/debian/control
--- wordnet-3.0/debian/control	2013-05-23 03:48:45.0 -0300
+++ wordnet-3.0/debian/control	2014-01-28 16:31:30.0 -0300
@@ -22,7 +22,7 @@
man-db,
libxss-dev,
libxft-dev,
-   ruby1.8,
+   ruby,
imagemagick
 Standards-Version: 3.9.4
 Vcs-Browser: http://svn.debian.org/wsvn/debian-science/packages/wordnet/trunk/
diff -Nru wordnet-3.0/debian/rules wordnet-3.0/debian/rules
--- wordnet-3.0/debian/rules	2013-05-23 04:23:46.0 -0300
+++ wordnet-3.0/debian/rules	2014-01-28 16:36:00.0 -0300
@@ -48,7 +48,7 @@
 	set -e; \
 	if dpkg-architecture -qDEB_BUILD_ARCH|grep -q 'mips\|arm\|s390'; then \
 		if test "$$FORCE_GOLDENDICT_BUILD" -gt 0; then \
-			ruby1.8 debian/wn-for-goldendict.rb > $@; \
+			ruby debian/wn-for-goldendict.rb > $@ || ($(RM) $@; false); \
 		else \
 			echo "Building of goldendict-wordnet dictionary was skipped"; \
 			echo "to build this package use environment variable"; \
@@ -56,5 +56,5 @@
 			touch $@; \
 		fi; \
 	else \
-		ruby1.8 debian/wn-for-goldendict.rb > $@; \
+		ruby debian/wn-for-goldendict.rb > $@ || ($(RM) $@; false); \
 	fi
diff -Nru wordnet-3.0/debian/wn-for-goldendict.rb wordnet-3.0/debian/wn-for-goldendict.rb
--- wordnet-3.0/debian/wn-for-goldendict.rb	2012-06-05 13:12:14.0 -0300
+++ wordnet-3.0/debian/wn-for-goldendict.rb	2014-01-28 16:42:32.0 -0300
@@ -293,14 +293,14 @@
 @offset = data[0].to_i
 @lex_filenum = data[1]
 @pos = data[2]
-@w_cnt = [data[3]].pack('H2')[0]
+@w_cnt = [data[3]].pack('H2').bytes.first
 @words = []
 i = 4
 @lex_ids = []
 @w_cnt.times {
   @words << data[i].gsub(/_/, ' ').gsub(/\s*\((p|a|ip)\)\s*$/, '')
   i += 1
-  @lex_ids << [data[i]].pack('h')[0]
+  @lex_ids << [data[i]].pack('h').bytes.first
   i += 1
 }
 
@@ -362,8 +362,8 @@
 if (src_target == "")
   return other.words
 else
-  src = [src_target[0, 2]].pack('H2')[0]
-  target = [src_target[2, 2]].pack('H2')[0]
+  src = [src_target[0, 2]].pack('H2').bytes.first
+  target = [src_target[2, 2]].pack('H2').bytes.first
   h_src = words[src - 1]
   if (h_src == headword)
 return [other.words[target - 1]]
@@ -374,7 +374,7 @@
   end
   def get_frame_data(headword, frame)
 f_num = frame[0].to_i
-w_num = [frame[1]].pack('H2')[0]
+w_num = [frame[1]].pack('H2').bytes.first
 if (w_num == 0)
   return [$frames[f_num]]
 else


signature.asc
Description: Digital signature

Bug#736434: marked as done ([src:gnucash] Sourceless file)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jan 2014 19:49:17 +
with message-id 
and subject line Bug#736434: fixed in gnucash 1:2.6.1-1
has caused the Debian Bug report #736434,
regarding [src:gnucash] Sourceless file
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.)


-- 
736434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gnucash
Version:   1:2.6.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: source-contains-prebuilt-javascript-object
X-Debbugs-CC: ftpmas...@debian.org

gnucash 1:2.6.0-1 (source)
src/report/jqplot/jquery.min.js


Bastien
--- End Message ---
--- Begin Message ---
Source: gnucash
Source-Version: 1:2.6.1-1

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

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated gnucash 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, 28 Jan 2014 20:17:00 +0100
Source: gnucash
Binary: gnucash gnucash-dbg gnucash-common python-gnucash
Architecture: source amd64 all
Version: 1:2.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: Sébastien Villemot 
Changed-By: Sébastien Villemot 
Description: 
 gnucash- personal and small-business financial-accounting software
 gnucash-common - common files for the financial-accounting software Gnucash
 gnucash-dbg - debugging symbols for the accounting software Gnucash
 python-gnucash - Gnucash interface for Python
Closes: 734148 736434
Changes: 
 gnucash (1:2.6.1-1) unstable; urgency=medium
 .
   * New upstream release.
 + tarball now includes the source of minified javascript file
   src/report/jqplot/jquery.min.js. (Closes: #736434)
 + column widths of the list of accounts are now correctly remembered.
   (Closes: #734148)
Checksums-Sha1: 
 3e7dd92295233e38db44b7a398d864ba5643b67b 2371 gnucash_2.6.1-1.dsc
 726ee08e95206ec3746a92efaa5281f27d6eacc8 10944714 gnucash_2.6.1.orig.tar.bz2
 3c409c10d67a6caae3366cdcba26d5c16ca08410 31512 gnucash_2.6.1-1.debian.tar.xz
 564b9a473dd64da16718fa76ff92a78efb0f0f07 2410302 gnucash_2.6.1-1_amd64.deb
 6e14568e326eedbb6f97f67c37110d78ac7dc216 6644682 gnucash-dbg_2.6.1-1_amd64.deb
 c226b5b3dffcd63821dce9d15860e34d1a564230 3358852 gnucash-common_2.6.1-1_all.deb
 2eb92972015182ff2359c5a358b57b2dc5a3610b 238150 
python-gnucash_2.6.1-1_amd64.deb
Checksums-Sha256: 
 cf3063f75ece0956f6382c4b37e157fe32a3f8a31a5a3db1a65c51712c2766b2 2371 
gnucash_2.6.1-1.dsc
 c9e66f84c7706e3c8e7a1c88dcd58c5c3d102e285012b51f5af25052502cd8a4 10944714 
gnucash_2.6.1.orig.tar.bz2
 aca8ecc895fffb14df03dbb5418db48437844f9673c567fde3927ca08e2e4f42 31512 
gnucash_2.6.1-1.debian.tar.xz
 f9114f0ed3e8636c1796a255dda3979ae4ed86b9616a84b3db4eee4a23337840 2410302 
gnucash_2.6.1-1_amd64.deb
 efacd046ced0be81fcf7188190b0223d16307b9fcdba68582ecf41a9a7d06758 6644682 
gnucash-dbg_2.6.1-1_amd64.deb
 ae90dcc3f1d36b5a636c793b462018d43883b4708b517520c20339636f6eafea 3358852 
gnucash-common_2.6.1-1_all.deb
 e684e38f293e4119474eb267a5a7e87b9102bea89686a71a032d496ecbadc79c 238150 
python-gnucash_2.6.1-1_amd64.deb
Files: 
 b2afd2087cf5fed683e2c0199676df3c 2371 gnome optional gnucash_2.6.1-1.dsc
 3723095e59aa2f58759fc62e6f43 10944714 gnome optional 
gnucash_2.6.1.orig.tar.bz2
 bc13a19e06a89249af61e078222f5e05 31512 gnome optional 
gnucash_2.6.1-1.debian.tar.xz
 4c4e58ef884887a188916165c4f79037 2410302 gnome optional 
gnucash_2.6.1-1_amd64.deb
 c7a57cdf6703a1a8d62e381be01000c8 6644682 debug extra 
gnucash-dbg_2.6.1-1_amd64.deb
 aba16f79100dcbe41e4047e81a94137d 3358852 gnome optional 
gnucash-common_2.6.1-1_all.deb
 f28d5c927254a6f33f0bcafcb2efd422 238150 python optional 
python-gnucash_2.6.1-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJS6AUVAAoJECzs6TUOzr5KUlwP/j1nxt/bTV58oMck4LJaItfM
taUP5dIGTbSH0wWP+uEipSdPHhGGhCUbUxLwoCIQY+Jw08AP1y4VzmEO4eki1d6G
QVYqGkuP+HpH+DQ6fak7jBiSR7B+mXsnrzGM7t+Xmj4i1ispIrEnlNF4HHSY1tNG
bz5E2McNHDZF6qIMl5tNGcyxIhYJ4zUX+6eN6v2z2Ph9O/DQELakShB4cTxefHCL
p9UEu

Bug#736964: [lightdm] Password is shown in cleart text while typing

[Slavko]

Package: lightdm
Version: 1.8.6-1
Severity: grave

Hi,

after upgrade to this version i try to check, if the autologin timeout
is working by now. While it is not working yet, i need to type the
password and i see, that the login dialog shows my password while
typing in clear text. No asterisks, no bullets, only clear text.

This is a problem, because it allows another people to see my password
while typing, until i press enter (to login).

regards

--- System information. ---
Architecture: amd64
Kernel:   Linux 3.12-1-amd64

Debian Release: jessie/sid
  500 wheezy-backports mozilla.debian.net 
  500 testing security.debian.org 
  500 testing ftp.cz.debian.org 
  500 stable  deb.opera.com 


--- Package information. ---
Depends (Version) | Installed
=-+-==
libc6   (>= 2.14) | 
libgcrypt11(>= 1.4.5) | 
libglib2.0-0  (>= 2.35.9) | 
libpam0g(>= 0.99.7.1) | 
libxcb1   | 
libxdmcp6 | 
debconf (>= 0.5)  | 
 OR debconf-2.0   | 
lightdm-gtk-greeter   | 
 OR lightdm-greeter   | 
dbus  | 
consolekit| 
adduser   | 


Recommends(Version) | Installed
===-+-===
xserver-xorg| 1:7.7+5


Suggests (Version) | Installed
==-+-===
accountsservice| 0.6.34-2
upower | 0.9.23-2+b1

-- 
Slavko
http://slavino.sk


signature.asc
Description: PGP signature

Bug#736914: [Pkg-e-devel] Bug#736914: missing licenses in debian/copyright

[Albin Tonnerre]

On Tue, Jan 28, 2014 at 11:07 AM, Thorsten Alteholz  wrote:
> Dear Maintainer,

Hi Thorsten,

> please add the MIT license of at least:
>   src/modules/evas/engines/psl1ght/rsxutil.c
>   src/modules/evas/engines/psl1ght/rsxutil.h
>   src/benchmarks/eina/city.cc
>   src/benchmarks/eina/city.h
>   src/lib/ecore_con/dns.c
>   src/lib/ecore_con/dns.h
>   parts of src/lib/eina/*
> to debian/copyright.

Thanks a lot, I'll make sure to fix that in the next upload.

One question regarding the files in src/lib/eina/*: except for one
(eina_str.c), the presence of the MIT license in those files is
because they say "This file incorporates work covered by the following
copyright and permission notices: " right after the text
of the LGPL license. In that case, is it enough to just mention
License: LPGL in debian/copyright? If it's not, do you know of any way
to specify multiple licenses for a single file using the DEP-5 format?
Reading the spec, I'm not really sure I see how one is supposed to do
that.

Thanks,
-- 
Albin


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

Processed: affects 736334

[Debian Bug Tracking System]

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

> affects 736334 + gnucash
Bug #736334 [src:libdbi-drivers] Sqlite3 backend not more working
Bug #736656 [src:libdbi-drivers] libdbi-drivers: drivers not found anymore, due 
to multi-arch
Added indication that 736334 affects gnucash
Added indication that 736656 affects gnucash
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
736334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736334
736656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736656
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#736959: FTBFS[!linux]: ALSA MIDI not supported

[Steven Chamberlain]

On 28/01/14 19:25, Cyril Brulebois wrote:
> Looks like the patch for #736957?

Yeah :)  Thanks for checking.

There's even another one coming...

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org



signature.asc
Description: OpenPGP digital signature

Bug#736960: FTBFS[!linux]: ALSA MIDI not supported

[Steven Chamberlain]

Package: synthv1
Version: 0.3.6-1
Severity: serious
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd

Hi,

debian/rules runs configure with --enable-alsa-midi only on Linux.

Actually on kfreebsd-* and hurd it is necessary to do the opposite:
configure with --disable-alsa-midi, otherwise support for it is
wrongly autodetected due to the presence of salsa headers.

Please see attached patch fixing FTBFS.

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

Kernel: kFreeBSD 9.0-2-amd64-xenhvm
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- a/drumkv1-0.3.6/debian/rules	2013-09-10 15:46:03.0 +0100
+++ b/drumkv1-0.3.6/debian/rules	2014-01-28 19:06:56.433091722 +
@@ -15,6 +15,8 @@
 
 ifeq ($(DEB_HOST_ARCH_OS),linux)
 EXTRA_CONFIGURE_ARGS += --enable-alsa-midi
+else
+EXTRA_CONFIGURE_ARGS += --disable-alsa-midi
 endif
 
 ifeq ($(DEB_HOST_ARCH_CPU),amd64)

Bug#736959: FTBFS[!linux]: ALSA MIDI not supported

[Cyril Brulebois]

Steven Chamberlain  (2014-01-28):
> Package: samplv1
> Version: 0.3.6-2
> Severity: serious
> Tags: patch
> User: debian-...@lists.debian.org
> Usertags: kfreebsd
> 
> Hi,
> 
> debian/rules runs configure with --enable-alsa-midi only on Linux.
> 
> Actually on kfreebsd-* and hurd it is necessary to do the opposite:
> configure with --disable-alsa-midi, otherwise support for it is
> wrongly autodetected due to the presence of salsa headers.
> 
> Please see attached patch fixing FTBFS.

Looks like the patch for #736957?

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#736959: FTBFS[!linux]: ALSA MIDI not supported

[Steven Chamberlain]

Package: samplv1
Version: 0.3.6-2
Severity: serious
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd

Hi,

debian/rules runs configure with --enable-alsa-midi only on Linux.

Actually on kfreebsd-* and hurd it is necessary to do the opposite:
configure with --disable-alsa-midi, otherwise support for it is
wrongly autodetected due to the presence of salsa headers.

Please see attached patch fixing FTBFS.

Thanks!

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

Kernel: kFreeBSD 9.0-2-amd64-xenhvm
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- a/drumkv1-0.3.6/debian/rules	2013-09-10 15:46:03.0 +0100
+++ b/drumkv1-0.3.6/debian/rules	2014-01-28 19:06:56.433091722 +
@@ -15,6 +15,8 @@
 
 ifeq ($(DEB_HOST_ARCH_OS),linux)
 EXTRA_CONFIGURE_ARGS += --enable-alsa-midi
+else
+EXTRA_CONFIGURE_ARGS += --disable-alsa-midi
 endif
 
 ifeq ($(DEB_HOST_ARCH_CPU),amd64)

Bug#736957: FTBFS[!linux]: ALSA MIDI not supported

[Steven Chamberlain]

Package: drumkv1
Version: 0.3.6-1
Severity: serious
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd

Hi,

debian/rules runs configure with --enable-alsa-midi only on Linux.

Actually on kfreebsd-* and hurd it is necessary to do the opposite:
configure with --disable-alsa-midi, otherwise support for it is
wrongly autodetected due to the presence of salsa headers.

Please see attached patch fixing FTBFS.

Thanks!

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

Kernel: kFreeBSD 9.0-2-amd64-xenhvm
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- a/drumkv1-0.3.6/debian/rules	2013-09-10 15:46:03.0 +0100
+++ b/drumkv1-0.3.6/debian/rules	2014-01-28 19:06:56.433091722 +
@@ -15,6 +15,8 @@
 
 ifeq ($(DEB_HOST_ARCH_OS),linux)
 EXTRA_CONFIGURE_ARGS += --enable-alsa-midi
+else
+EXTRA_CONFIGURE_ARGS += --disable-alsa-midi
 endif
 
 ifeq ($(DEB_HOST_ARCH_CPU),amd64)

Bug#736956: [src:libqglviewer] Non free file according to dfsg

[bastien ROUCARIES]

Package: src:libqglviewer
Severity: serious
Version:  2.5.0-1
User: debian...@debian.org
Usertags:  license-problem-md5sum-non-free-file
X-Debbugs-CC: ftpmas...@debian.org

these files are not free please remove from source
libqglviewer 2.5.0-1 (source)
doc/images/css.gif usual name is valid-css-blue.gif. The valid w3c icons could 
not be modified. See also http://www.w3.org/QA/Tools/Icons.
doc/images/xhtml.png usual name is valid-xhtml10-blue.png. The valid w3c icons 
could not be modified. See also http://www.w3.org/QA/Tools/Icons.


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

Bug#736954: [src:libmng] Non free file according to dfsg

[bastien ROUCARIES]

Package: src:libmng
Severity: serious
Version: 1.0.10-3
User: debian...@debian.org
Usertags:  license-problem-md5sum-non-free-file
X-Debbugs-CC: ftpmas...@debian.org

these files are not free please remove from source
libmng 1.0.10-3 (source)
contrib/msvc/mngview/sRGB.icm usual name is sRGB.icm. This file may not be 
distributed without fee if modified. See also http://bugs.debian.org/657281.


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

Bug#735921: marked as done (implicit declaration of function 'strcasestr' on 64bit targets)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jan 2014 18:50:13 +
with message-id 
and subject line Bug#735921: fixed in radare2 0.9.6-3
has caused the Debian Bug report #735921,
regarding implicit declaration of function 'strcasestr' on 64bit targets
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.)


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

gcc -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat -Werror=format-security -g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -MD -g -O2
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -MD
 -D_FORTIFY_SOURCE=2 -fPIC -g -Wall -D__UNIX__=1
-I/build/buildd/radare2-0.9.6/libr/include -DGIT_TAP=\"0.9.6\" -o str.o str.c
str.c: In function 'r_str_casestr':
str.c:977:2: warning: implicit declaration of function 'strcasestr'
[-Wimplicit-function-declaration]
  return strcasestr (a, b);
  ^
str.c:977:2: warning: return makes pointer from integer without a cast [enabled
by default]
Function `strcasestr' implicitly converted to pointer at str.c:977


Like an include missing.
--- End Message ---
--- Begin Message ---
Source: radare2
Source-Version: 0.9.6-3

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

Debian distribution maintenance software
pp.
David Martínez Moreno  (supplier of updated radare2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 28 Jan 2014 10:29:31 -0800
Source: radare2
Binary: radare2 radare2-plugins libradare2-0.9.6 libradare2-dev 
libradare2-0.9.6-dbg libradare2-common
Architecture: source amd64 all
Version: 0.9.6-3
Distribution: unstable
Urgency: medium
Maintainer: David Martínez Moreno 
Changed-By: David Martínez Moreno 
Description: 
 libradare2-0.9.6 - libraries from the radare2 suite
 libradare2-0.9.6-dbg - debug symbols for libraries from radare suite
 libradare2-common - arch independent files from the radare2 suite
 libradare2-dev - devel files from the radare2 suite
 radare2- free and advanced command line hexadecimal editor
 radare2-plugins - plugins for radare2
Closes: 735921
Changes: 
 radare2 (0.9.6-3) unstable; urgency=medium
 .
   * debian/patches/12_fix_strcasestr_declaration: Fixed a missing include,
 thanks to Matthias Klose for pointing it (closes: #735921).
Checksums-Sha1: 
 ffed41be84d1bd3194f1bcb39882dabffb8f5045 1644 radare2_0.9.6-3.dsc
 2101443d2f86ad4a72e97c58967a709d8afbd564 15300 radare2_0.9.6-3.debian.tar.xz
 05dbb7dbbbd5dcff76683a6e13a623c8946f4f87 131790 radare2_0.9.6-3_amd64.deb
 dd30fba5458a5f4b87591a938f429be21b8f2504 60404 
radare2-plugins_0.9.6-3_amd64.deb
 b0f5766deafc1fe0883d841068c81f4235ada3c4 1395178 
libradare2-0.9.6_0.9.6-3_amd64.deb
 1f12924e463a75d521e88cc020e833ab6ddb8e24 142958 
libradare2-dev_0.9.6-3_amd64.deb
 4f5539ab1dd2bdb139f545f8480c0714e3c3bc65 4443070 
libradare2-0.9.6-dbg_0.9.6-3_amd64.deb
 28ec49037b786eaf6cb1a75ce63532baf33220f3 172562 
libradare2-common_0.9.6-3_all.deb
Checksums-Sha256: 
 a525cf6be0cc97bd61880604a7c274b59457c6823089d5e0c928070d9c0ea1a5 1644 
radare2_0.9.6-3.dsc
 264ece64be93868dbdf09eb444bf55428cbbc1126d1ea1c47f4d4f7b2a12d073 15300 
radare2_0.9.6-3.debian.tar.xz
 016f9d21d6f40c80bd1eb0b1d69ceb63ca2c2b6c2e80a6d80d26372508a4 131790 
radare2_0.9.6-3_amd64.deb
 d121ac4f1431c9667f06de904bc0ba72114540af325a52615921e859c08f8d49 60404 
radare2-plugins_0.9.6-3_amd64.deb
 9f3828ca4c735656f11395cc0e44273e5290955cd852553340fe1d543a9531e5 1395178 
libradare2-0.9.6_0.9.6-3_amd64.deb
 f41bc16f24dd230bfa50e85cae69fb6cfaa6789cd24bbf131a2ac966d3a9fdbc 142958 
libradare2-dev_0.9.6-3_amd64.deb
 e5cb4deb1f9c4b4848560b44c85a15bcea15573e91b3b92977bb494b8aff6c2c 4443070 
libradare2-0.9.6-dbg_0.9.6-3_amd64.deb
 39f05518c76f6164d8128cac3583acd1f7a71d60fc06fbfe0e99c89d8e574edc 172562 
libradare2-common_0.9.6-3_all.d

Processed: reassign 736334 to src:libdbi-drivers, forcibly merging 736656 736334

[Debian Bug Tracking System]

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

> reassign 736334 src:libdbi-drivers 0.9.0-1
Bug #736334 [libdbi-drivers] Sqlite3 backend not more working
Bug reassigned from package 'libdbi-drivers' to 'src:libdbi-drivers'.
No longer marked as found in versions 0.9.0-1.
Ignoring request to alter fixed versions of bug #736334 to the same values 
previously set
Bug #736334 [src:libdbi-drivers] Sqlite3 backend not more working
Marked as found in versions libdbi-drivers/0.9.0-1.
> forcemerge 736656 736334
Bug #736656 [src:libdbi-drivers] libdbi-drivers: drivers not found anymore, due 
to multi-arch
Bug #736334 [src:libdbi-drivers] Sqlite3 backend not more working
Removed indication that 736334 affects gnucash
Merged 736334 736656
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
736334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736334
736656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736656
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#733110: wordnet: Please migrate to Ruby 2.0/1.9

[David Suárez]

El Martes, 28 de enero de 2014 14:35:37 Andreas Tille escribió:
> Hi,
> 
> Dmitry E. Oboukhov has injected some Ruby 1.8 code into the wordnet
> packaging.  I personally do not speak Ruby and thus can not fix the
> problem in an other way than simply droping the goldendict-wordnet
> binary package (its data package is created in this way).
> 
> Since Dmitry has not (yet) respondet to this bug report I would like
> to ask the Ruby team to find a patch for the problem in the build
> system that fixes the following:
> 
> 
> WARNING: sentidx.vrb format error: ["pet%2:35:00::"]
> debian/wn-for-goldendict.rb:300:in `initialize': undefined method `times'
> for "\x01":String (NoMethodError) from debian/wn-for-goldendict.rb:158:in
> `new'
> from debian/wn-for-goldendict.rb:158:in `get_data'
> from debian/wn-for-goldendict.rb:648:in `block (2 levels) in '
> from debian/wn-for-goldendict.rb:647:in `each'
> from debian/wn-for-goldendict.rb:647:in `block in '
> from debian/wn-for-goldendict.rb:644:in `foreach'
> from debian/wn-for-goldendict.rb:644:in `'
> 
> 
> If I do not get any help I need to go the unfortunate route to kick
> goldendict support again.

The code it's trying to convert an hexadecimal string to an integer.

line 296  -> @w_cnt = [data[3]].pack('H2')[0]
changes to -> @w_cnt = data[3].hex

Please, check if the generated files are the same :)

David


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

Processed (with 1 errors): Re: Bug#736334: Sqlite3 backend not more working

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libdbi-drivers 0.9.0-1
Bug #736334 [gnucash] Sqlite3 backend not more working
Bug reassigned from package 'gnucash' to 'libdbi-drivers'.
No longer marked as found in versions gnucash/1:2.6.0-1.
Ignoring request to alter fixed versions of bug #736334 to the same values 
previously set
Bug #736334 [libdbi-drivers] Sqlite3 backend not more working
There is no source info for the package 'libdbi-drivers' at version '0.9.0-1' 
with architecture ''
Unable to make a source version for version '0.9.0-1'
Marked as found in versions 0.9.0-1.
> forcemerge 736656 -1
Bug #736656 [src:libdbi-drivers] libdbi-drivers: drivers not found anymore, due 
to multi-arch
Unable to merge bugs because:
package of #736334 is 'libdbi-drivers' not 'src:libdbi-drivers'
Failed to forcibly merge 736656: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x38c2508)', 
'requester', 'Sébastien Villemot ', 'request_addr', 
'736334-sub...@bugs.debian.org', 'request_msgid', 
'<1390934125.23979.76.ca...@rama.villemot.name>', 'request_subject', ...) 
called at /usr/local/lib/site_perl/Debbugs/Control/Service.pm line 552
eval {...} called at 
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 551
Debbugs::Control::Service::control_line('line', 'forcemerge 736656 -1', 
'clonebugs', 'HASH(0x38d9af8)', 'limit', 'HASH(0x38d9d20)', 
'common_control_options', 'ARRAY(0x38d9df8)', 'errors', ...) called at 
/usr/lib/debbugs/process line 1039

> affects -1 + gnucash
Bug #736334 [libdbi-drivers] Sqlite3 backend not more working
Added indication that 736334 affects gnucash

-- 
736334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736334
736656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736656
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#736334: Sqlite3 backend not more working

[Sébastien Villemot]

Control: reassign -1 libdbi-drivers 0.9.0-1
Control: forcemerge 736656 -1
Control: affects -1 + gnucash

Le mercredi 22 janvier 2014 à 17:45 +0100, Francesco P. Lovergine a
écrit :

> Ah right, it works by downgrading both libdbd-sqlite3 AND libdbi1.

This is indeed a bug in libdbd-sqlite3. Reassigning and merging
accordingly.

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



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

Bug#732151: marked as done (postgis: FTBFS on various architectures)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jan 2014 19:13:45 +0100
with message-id <52e7f359.1070...@bluegap.ch>
and subject line Re: postgis: FTBFS on various architectures
has caused the Debian Bug report #732151,
regarding postgis: FTBFS on various architectures
to be marked as done.

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

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


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

Hi,

see the build logs at
https://buildd.debian.org/status/package.php?p=postgis

postgis fails to build on armel armhf mips mipsel powerpc s390x and
sparc.

Cheers,
Julien


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: postgis
Version: 2.1.1-4

The big-endian issues have been resolved in 2.1.1-4. However, on mipsel
the test suite failed due to Postgres crashing. I'm not sure of the root
cause of that, but manually building on mipsel worked just fine, now.

I suspect an installation specific issue, possibly intermittent - not
related to the postgis source itself.

According to the buildd logs, the package now builds on all other
architectures that postgis-1.5.2 did (i.e. all except for hurd).
Therefore, I'm now closing this bug to finally allow 2.1.1-5 to migrate
to testing.

Regards

Markus Wanner



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#736949: FTBFS[kfreebsd-*]: preprocessor syntax error

[Steven Chamberlain]

Package: acct
Version: 6.5.5-2
Severity: serious
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd

Hi,

There is a fairly obvious preprocessor syntax error here:

--- a/acct-6.5.5/files.h.in 2014-01-28 18:02:54.0 +
+++ b/acct-6.5.5/files.h.in 2014-01-28 18:04:55.407058583 +
@@ -18,7 +18,7 @@
 # include 
 # if defined __FreeBSD__ || defined __FreeBSD_kernel__
 #  include 
-#  if __FreeBSD_kernel__
+#  if defined __FreeBSD_kernel__
 #   define __FreeBSD_version __FreeBSD_kernel_version
 #  endif /* __FreeBSD_kernel__ */
 #  if __FreeBSD_version >= 700100 /* FreeBSD 7.0-STABLE */

The above patch fixes the FTBFS seen on kfreebsd-*:
https://buildd.debian.org/status/fetch.php?pkg=acct&arch=kfreebsd-amd64&ver=6.5.5-2&stamp=1390761987

Thanks.

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

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


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

Bug#713297: polyorb: FTBFS: CosEventChannelAdmin.idl:24:31: "CosEventComm" is undefined

[Ludovic Brenta]

Email forwarded from Pavel Zhukov:

Hi debian ada team! ,

First of all I'm not familar with debian bug tracking system (sorry  
about that).
I hit the same issue as described in  
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713297 while building  
polyorb for fedora (with gcc 4.8).

The patch [1] fixed issue for me and it was accepted by Adacore. Feel  
free to use one :)

--
Pavel

[1]
--- a/configure 2014-01-27 23:38:14.944966528 +0100
+++ b/configure 2014-01-27 23:38:28.841024943 +0100
@@ -5641,7 +5641,7 @@
case "$CXXCPP" in
  *g++*)
if test "${CXXCPPFLAGS}" = ""; then
-IDLCPPFLAGS="-x c++ -ansi"
+IDLCPPFLAGS="-x c++ -ansi -ffreestanding"
  # Options to use GNU C++ preprocessor as IDL preprocessor
  # -x c++   force C++ preprocessor mode (even though it cannot be
  #  inferred from filename extension .idl)
--- a/support/idlcpp.m4 2014-01-27 23:37:44.230837412 +0100
+++ b/support/idlcpp.m4 2014-01-27 23:38:04.278921691 +0100
@@ -38,7 +38,7 @@
case "$CXXCPP" in
  *g++*)
if test "${CXXCPPFLAGS}" = ""; then
-IDLCPPFLAGS="-x c++ -ansi"
+IDLCPPFLAGS="-x c++ -ansi -ffreestanding"
  # Options to use GNU C++ preprocessor as IDL preprocessor
  # -x c++   force C++ preprocessor mode (even though it cannot be
  #  inferred from filename extension .idl)


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

Bug#733116: marked as done (libjs-leaflet-markercluster: Does not work with current libjs-leaflet)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jan 2014 18:03:39 +
with message-id 
and subject line Bug#733116: fixed in leaflet-markercluster 0.4~dfsg-1
has caused the Debian Bug report #733116,
regarding libjs-leaflet-markercluster: Does not work with current libjs-leaflet
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.)


-- 
733116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjs-leaflet-markercluster
Version: 0.2~dfsg-1
Severity: grave
Justification: renders package unusable

While trying to debug why my map was not working, I first realised that the
MarkerClusterGroup.getBounds() method was not working. Then I discovered that
the cause was that the MarkerClusterGroup.eachLayer() method didn't ever call
the callback.

I didn't find the reason for that, but then when trying to report a bug, I
realised that nothing works at all: the examples shipped with the package only
work because they are using Leaflet 0.4.4 from the CDN. As soon as I made them
use the Debian version of Leaflet, they stop working. Hence the grave severity
for this bug.

The easiest solution I see for this, is to update Leaflet and MarkerCluster to
the current versions, which seem to work OK.

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

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

libjs-leaflet-markercluster depends on no packages.

Versions of packages libjs-leaflet-markercluster recommends:
pn  javascript-common  
ii  libjs-leaflet  0.6.4-1

libjs-leaflet-markercluster suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: leaflet-markercluster
Source-Version: 0.4~dfsg-1

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated leaflet-markercluster 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 Jan 2014 18:41:34 +0100
Source: leaflet-markercluster
Binary: libjs-leaflet-markercluster
Architecture: source all
Version: 0.4~dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Description: 
 libjs-leaflet-markercluster - Provides Marker Clustering functionality for 
Leaflet
Closes: 733116
Changes: 
 leaflet-markercluster (0.4~dfsg-1) unstable; urgency=medium
 .
   [ upstream ]
   * new release.
 + Works with leaflet 0.7.1+.
   Closes: bug#733116. Thanks to Martín Ferrari.
 .
   [ Jonas Smedegaard ]
   * Move packaging to pkg-javascript team.
   * Depend on (not recommend) leaflet, and tighten to recent versions.
   * Improve example files path fixing (i.e. Debian relative paths
 instead of CDN) to be version-agnostic.
   * Update copyright file: Cover newly included convenience code copies.
   * Unfuzz and update patch 2001.
   * Add patch 2002 to adapt build script to support Uglifyjs 1.x.
Checksums-Sha1: 
 56a8a0b0ad723690cf525f5404bfd4574b7eb741 2177 
leaflet-markercluster_0.4~dfsg-1.dsc
 e5ec5a2e1c794725d41c432d7643f9ecf4684fbb 73855 
leaflet-markercluster_0.4~dfsg.orig.tar.gz
 30573735bfcc6707a9b652780f22a3f02e9e4552 6296 
leaflet-markercluster_0.4~dfsg-1.debian.tar.xz
 dfae790f396f59ab3e10965a1c64139d979c1626 38954 
libjs-leaflet-markercluster_0.4~dfsg-1_all.deb
Checksums-Sha256: 
 c7d18b917528b8ebaef536e71a3d1be781275b9ba091c731571b8d266edb4496 2177 
leaflet-markercluster_0.4~dfsg-1.dsc
 a8471a1f99fb1a443ac69842604a0061051e7dc89cc0c3b97c3db8506b2c7eb1 73855 
leaflet-markercluster_0.4~dfsg.orig.tar.gz
 3cbc5a70537e60406b1cf9fc8ae68c47b2dc51561325b05110c5c14b96add7d9 6296 
leaflet-markercluster_0.4~dfsg-1.debian.tar.xz
 2f86f72e60238eafa6b7416c1f501e12b8d68cc60ede8bb7e832a63a647f929c 38954 
libjs-leaflet-markercluster_0.4~dfsg-1_all.

Bug#736079: gajim doesn't start

[Andrey Gusev]

On 24.01.2014 02:16, Tanguy Ortolo wrote:

Andrey Gusev, 2014-01-19 18:55+0400:

Dear Maintainer,
I try to start gajim and it doesn't start. The oputput to console is
Traceback (most recent call last):
 File "gajim.py", line 217, in 
from ctypes import CDLL


Can you try that alone in a plain Python interpreter?


from ctypes import CDLL


If it yields the same result, then it is likely a Python bug only.

I can not repeat this. Now gajim works without problem. May be it was 
some issue with configuration of packages after update.



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

Bug#735361: [request-tracker-maintainers] Bug#735361: Bug#735361: request-tracker4: FTBFS: GPG test failures

[Kevin Falcone]

On Wed, Jan 15, 2014 at 12:35:44AM +, Dominic Hargreaves wrote:
> On Wed, Jan 15, 2014 at 12:25:23AM +, Dominic Hargreaves wrote:
> > This appears to break the RT tests, which use this parameter:
> 
> Just to be clear: since trust-model=always is only used in the test
> suite, I don't believe this issue affects running installations.

It's also a really common configuration to run in production,
especially if you tell RT to auto-download keys and want it to encrypt
back to randoms who email in, process of:
New ticket from b...@example.com, signed, encrypted to queue key.
RT downloads b...@example.com's key because you have
'auto-key-locate' => 'keyserver',
'keyserver-options' => 'auto-key-retrieve',
set in %GnuPGOptions

When you reply back to the user, you pick the Reply option, if there's
no trust path in the database gpg can kick back a warning/error about
not wanting to encrypt to an untrusted key.
Recipient 'b...@example.com' is unusable, the reason is 'Key not trusted'

For sites that manually keep a tightly controlled keyring, this isn't an
issue. I don't have statistics on how many users run with trust-model =
always but I definitely run into it with clients.

-kevin


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

Bug#736656: libdbi-drivers: drivers not found anymore, due to multi-arch

[GCS]

On Tue, Jan 28, 2014 at 2:33 PM, Prach Pongpanich  wrote:
> On Tue, Jan 28, 2014 at 1:30 PM, László Böszörményi (GCS)
>  wrote:
> I've discussed with Markus Hoenicka and he told me about a atoll()
> call which the sqlite3 driver uses to convert raw data into a long
> long number causes problems, he will work on this problem.
>
> drivers/sqlite3/dbd_sqlite3.c:
> 1719:data->d_longlong = (long long) atoll(raw); break; /* hah,
> wonder if that'll work */
 No wonder, as GNU libc manual[1] on parsing integers states:
Function: long long int atoll (const char *string)
"This function is similar to atol, except it returns a long long int.
The atoll function was introduced in ISO C99. It too is obsolete
(despite having just been added); use strtoll instead."
Thus atoll is deprecated in favour of stroll. Hope if it this change
will be made, then the compilation issue will be solved. Prach, if you
have connection with Markus Hoenicka then may you send him the URL
I've mentioned?

Algernon, if I code a small converter, can you test it on Sparc (if
you have any nearby at your workplace)?

Regards,
Laszlo/GCS
[1] http://www.gnu.org/software/libc/manual/html_node/Parsing-of-Integers.html


--
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#736498: src:libgringotts: FTBFS on s390x

[Debian Bug Tracking System]

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

> reopen 736498
Bug #736498 {Done: Vincent Cheng } [src:libgringotts] 
src:libgringotts: FTBFS on s390x
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1:1.2.1-14.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
736498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736498
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#736628: procps: FTBFS [amd64]: FAIL: vmstat partition (using sda1)

[Daniel Schepler]

On Tuesday, January 28, 2014 09:37:36 PM Craig Small wrote:
> tags 736628 help
> tags 736628 upstream
> 
> On Mon, Jan 27, 2014 at 09:08:56AM -0800, Daniel Schepler wrote:
> > (gdb) p disks
> > $1 = (struct disk_stat **) 0x7fffeb08
> > (gdb) p *disks
> > $2 = (struct disk_stat *) 0x0
> > (gdb) p cDisk
> 
> The problem seems to be that a partition is found before the disk
> appears. More specifically, the partition needs to be before *any*
> disk. (A different but related bug is that the library assumes
> all partitions appear immediately after the disk line).
> 
> So: sda, sda1, sda2 = ok
> sda1,sda2,sda = crash
> sr0, sda1, sda2 = ok, but sda1 is "linked" to sr0
> 
> The problem now is, under what conditions do these odd
> /proc/diskstats occur and what interpretation should
> vmstat make of the situation? Ignore the partitions?
> Raise an error? re-map the disk->partition links
> after reading the file?

I just did a bit more debugging using strace, and found that this happens just 
before the crash:

access("/sys/block/sda", F_OK)  = -1 ENOENT (No such file or directory)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Segmentation fault

In fact, it looks like pbuilder doesn't mount /sys, and I can get vmstat to 
work by hand mounting it:

root@frobozz:/# vmstat -p sda1
Segmentation fault
root@frobozz:/# mount -t sysfs sysfs /sys
root@frobozz:/# vmstat -p sda1
sda1  reads   read sectors  writesrequested writes
  727293   24757690 278900   32422536
root@frobozz:/# umount /sys
root@frobozz:/# vmstat -p sda1
Segmentation fault
-- 
Daniel Schepler


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

Bug#736498: src:libgringotts: FTBFS on s390x

[Aurelien Jarno]

reopen 736498
thanks

On Sun, Jan 26, 2014 at 09:37:36PM +0100, Markus Koschany wrote:
> Hi Jose!
> 
> (I'm not subscribed to this bug report, please CC me or use
> 736498-submit...@bugs.debian.org)
> 
> > Before
> > split and conversion to format version 3 the source didn't build the
> > simple test suite (dh_auto_test) as it does now. Moreover, it never
> > built successfully on s390x and hurd-i386[0].
> 
> The reason why Osmo can't migrate to testing is that libgringotts2 built
> successfully in src:gringotts for all architectures before the package
> split. Now the system assumes that the new package introduces a
> regression and blocks all reverse dependencies from reentering testing.
> 
> In my opinion the best way forward is to contact the developers of
> libgringotts and fix the test suite upstream.
> 
> You can also choose to revert your change to enable the test suite or
> you can choose to disable it only on s390x.
> 
> Something like that in debian/rules:
> 
> DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
> 
> override_dh_auto_test:
> ifneq (s390x,$(DEB_HOST_ARCH))
>   dh_auto_test
> endif
> 
> You might possibly want to contact your sponsor and ask him, if he can
> test your patch/fixes on a s390x porter box.
> 
> I would probably disable the test suite on s390x, if that's the only
> reason for the current FTBFS, upload a new and fixed revision and close
> this bug report. Then I would open a new bug report with a lower
> severity and look into the issue again and try to fix it permanently.
> 
> As far as we know there were never complains about libgringotts on s390x
> thus I think just disabling the suite on s390x should suffice for the
> moment.

The problem reported by the testsuite is real, and ignoring it means
that bzip2 compression support is broken on s390x (and other 64-bit 
big-endian architectures).

The problem is that some pointers are casted from long to unsigned int,
while they do not have the same size. The patch below fixes that using
a temporary variable as the pointer. There might be better solutions
like changing the variable type, but I leave that for the upstream.

--- libgringotts-1.2.1.orig/src/libgrg_crypt.c
+++ libgringotts-1.2.1/src/libgrg_crypt.c
@@ -347,10 +347,14 @@ decrypt_mem (const GRG_CTX gctx, const G
}

if (gctx->comp_algo)//bz2
+   {
+   unsigned int uint_oDim = oDim;
err = BZ2_bzBuffToBuffDecompress ((unsigned char *)
- tmpData, (unsigned 
int *) &oDim,
+ tmpData, &uint_oDim,
  (unsigned char *) 
curdata, curlen,
  USE_BZ2_SMALL_MEM, 0);
+   oDim = uint_oDim;
+   }
else//zlib
err = uncompress (tmpData, &oDim, curdata, curlen);
 
@@ -411,13 +415,16 @@ grg_encrypt_mem (const GRG_CTX gctx, con
 
//compress the data
if (gctx->comp_algo)//bz2
+   {
+   unsigned int uint_compDim = &compDim;
err = BZ2_bzBuffToBuffCompress (compData,
-   (unsigned int *)
-   &compDim,
+   &uint_compDim,
(unsigned char *)
origData, uncDim,
gctx->comp_lvl * 3, 0,
0);
+   compDim = uint_compDim;
+   }
else
err = compress2 (compData, &compDim, origData, uncDim,
 gctx->comp_lvl * 3);

-- 
Aurelien Jarno  GPG: 1024D/F1BCDB73
aurel...@aurel32.net http://www.aurel32.net


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

Bug#736938: src:libgringotts: FTBFS on powerpc

[Markus Koschany]

Source: libgringotts
Version: 1:1.2.1-14
Severity: serious

Hello Jose,

Now libgringotts FTBFS on powerpc but it built succesfully in the past.
It seems it's an issue with the test suite again. You could disable
the test suite for powerpc too or maybe it's just a "temporary"
problem and a "give-back" will resolve it.

Cheers,

Markus


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

Bug#733423: marked as done (ruby-activesupport-3.2 should depend on ruby-minitest or drop port-to-minitest.patch)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jan 2014 15:37:07 +
with message-id 
and subject line Bug#733423: fixed in ruby-activesupport-3.2 3.2.16-2
has caused the Debian Bug report #733423,
regarding ruby-activesupport-3.2 should depend on ruby-minitest or drop 
port-to-minitest.patch
to be marked as done.

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

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


-- 
733423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-fixture-builder
Version: 0.3.6-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131226 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):
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- minitest (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from /usr/lib/ruby/vendor_ruby/active_support/test_case.rb:1:in ` (required)>'
>   from /usr/lib/ruby/vendor_ruby/active_record/test_case.rb:5:in 
> `'
>   from /usr/lib/ruby/vendor_ruby/active_record/test_case.rb:1:in ` (required)>'
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from /«PKGBUILDDIR»/test/test_helper.rb:17:in `'
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from /«PKGBUILDDIR»/test/fixture_builder_test.rb:1:in `'
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:15:in `block in 
> '
>   from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `select'
>   from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `'
> rake aborted!
> Command failed with status (1): [ruby -I"lib:test" 
> -I"/usr/lib/ruby/vendor_ruby" 
> "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
> "test/fixture_builder_test.rb" 
> "test/legacy_fixture_mode_fixture_generation_test.rb" 
> "test/legacy_fixture_mode_test.rb" "test/namer_test.rb" ]
> -e:1:in `'
> Tasks: TOP => default => test
> (See full trace by running task with --trace)
> ERROR: Test "ruby1.9.1" failed: 

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/12/26/ruby-fixture-builder_0.3.6-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: ruby-activesupport-3.2
Source-Version: 3.2.16-2

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated ruby-activesupport-3.2 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 28 Jan 2014 15:59:26 +0100
Source: ruby-activesupport-3.2
Binary: ruby-activesupport-3.2
Architecture: source all
Version: 3.2.16-2
Distribution: unstable
Urgency: high
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Ondřej Surý 
Description: 
 ruby-activesupport-3.2 - Support and utility classes used by the Rails 3.2 
framework
Closes: 733423
Changes: 
 ruby-activesupport-3.2 (3.2.16-2) unstable; urgency=low
 .
   * Depend on ruby-minitest (Closes: #733423)
Checksums-Sha1: 
 abf35c97aeea0293eef299eb29a211959b28aefe 1614 
ruby-activesupport-3.2_3.2.16-2.dsc
 cff9853efa63a57c097532eaaa89bcb6c3c16d6a 3348 
ruby-activesupport-3.2_3.2.16-2.debian.tar.xz
 f88b1af22236478be3848c9aab2f73e2f892462a 181480 
ruby-activesupport-3.2_3.2.16-2

Processed: python-wstools: diff for NMU version 0.4.3-1.1

[Debian Bug Tracking System]

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

> tags 735827 + patch
Bug #735827 [src:python-wstools] python-wstools: FTBFS: ImportError: No module 
named setuptools
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
735827: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735827
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#735827: python-wstools: diff for NMU version 0.4.3-1.1

[Andrey Rahmatullin]

tags 735827 + patch
thanks

Dear maintainer,

I've prepared an NMU for python-wstools (versioned as 0.4.3-1.1). The diff
is attached to this message.

Regards.

-- 
WBR, wRAR
diff -Nru python-wstools-0.4.3/debian/changelog python-wstools-0.4.3/debian/changelog
--- python-wstools-0.4.3/debian/changelog	2013-09-16 21:17:42.0 +0600
+++ python-wstools-0.4.3/debian/changelog	2014-01-28 21:18:06.0 +0600
@@ -1,3 +1,10 @@
+python-wstools (0.4.3-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add Build-Depends: python-setuptools (Closes: #735827)
+
+ -- Andrey Rahmatullin   Tue, 28 Jan 2014 21:14:11 +0600
+
 python-wstools (0.4.3-1) unstable; urgency=low
 
   * Initial release (closes: #723102).
diff -Nru python-wstools-0.4.3/debian/control python-wstools-0.4.3/debian/control
--- python-wstools-0.4.3/debian/control	2013-09-16 21:12:51.0 +0600
+++ python-wstools-0.4.3/debian/control	2014-01-28 21:17:42.0 +0600
@@ -4,7 +4,8 @@
 Section: python
 Priority: optional
 Build-Depends: python-all (>= 2.6.6-3),
-debhelper (>= 7)
+debhelper (>= 7),
+python-setuptools
 Standards-Version: 3.9.4
 
 Package: python-wstools

Processed: bug 735861 is forwarded to https://github.com/headius/thread_safe/issues/32

[Debian Bug Tracking System]

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

> forwarded 735861 https://github.com/headius/thread_safe/issues/32
Bug #735861 [src:ruby-thread-safe] ruby-thread-safe: FTBFS: Segfault on test 
"ruby2.0"
Set Bug forwarded-to-address to 
'https://github.com/headius/thread_safe/issues/32'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
735861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735861
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#567210: doc-available always returns false without network

[Michael Kay]

Saxon-B 9.1 does not include copies of these resources. 

You can always write a URIResolver and direct the request to copies held at 
application level, but it can't be done "behind the scenes".

My recommendation would be to move forward to a later Saxon release that fixes 
the problem. The current release is 9.5. We have no plans to issue further 
maintenance releases for 9.1, although we do appreciate that some users have 
been sticking with that release because of the discontinuities introduced 
between 9.1 and 9.2.

Michael Kay
Saxonica



On 28 Jan 2014, at 13:28, Eugene Zhukov  wrote:

> Hi Michael,
> 
> Thanks for your previous replay.
> I checked with tcpdump and Wireshark that requests are made to
> www.w3.org [0]. Hence the failure without network.
> Could you please elaborate how to patch Saxonb 9.1.0.8 to redirect
> those requests to a local copy held within Saxon itself?
> 
> You can find previous discussion here:
> http://bugs.debian.org/567210
> 
> [0] http://paste.debian.net/78819/
> 
> Thanks & Regards,
> Eugene


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

Bug#736925: Does not apply to current kernel versions (3.2.y, 3.12.y, 3.13)

[Ben Hutchings]

Package: linux-patch-grsecurity2
Version: 2.9.1+3.2.21-201206221855-1
Severity: grave
Tags: security

The patch for 3.2.y has not been updated for a very long time, and now
conflicts with later updates so in effect it is incompatible with
security fixes.

No patches are included for current kernel versions.

It should be be updated or removed from both wheezy and jessie.

Ben.

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

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


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

Bug#736656: libdbi-drivers: drivers not found anymore, due to multi-arch

[Prach Pongpanich]

On Tue, Jan 28, 2014 at 1:30 PM, László Böszörményi (GCS)
 wrote:
> Hi Prach,
>
> On Mon, Jan 27, 2014 at 12:37 PM, Prach Pongpanich  wrote:
>> On Mon, Jan 27, 2014 at 5:08 PM, László Böszörményi (GCS)
>>  wrote:
>> I've removed debian/*.dir files, which created an empty directory
>> (usr/lib/dbd ).
>> We don't want to run sqlite and sqlite3 tests[1] when cross-building,
>> I attached a patch for both issues.
>> [1] https://buildd.debian.org/status/package.php?p=libdbi-drivers&suite=sid
>  You made the diff in the wrong, backward way. As such, it tries to
> add the mentioned dir files. Btw thanks, those files indeed need to be
> removed.
> The mentioned page shows only the architectures that officially part
> of Debian. They are _not_ cross-builds but native to those
> architectures. I suppose you meant that don't run any tests when
> DEB_BUILD_OPTIONS instructs so.
> This is not the case for buildds. Those should run self-tests to early
> reveal platform specific bugs.

Sorry for my mistake.
I've discussed with Markus Hoenicka and he told me about a atoll()
call which the sqlite3 driver uses to convert raw data into a long
long number causes problems, he will work on this problem.

drivers/sqlite3/dbd_sqlite3.c:
1719:data->d_longlong = (long long) atoll(raw); break; /* hah,
wonder if that'll work */

>
>> P.S. please you set me as Maintainer to avoid missing an e-mail from the BTS.
>  Only one person can be the maintainer. You should get bugreports as
> uploader or you may subscribe to the source packages of your
> choice[2].

Thanks for the explanation.


Cheers,
 Prach


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

Bug#733110: wordnet: Please migrate to Ruby 2.0/1.9

[Andreas Tille]

Hi,

Dmitry E. Oboukhov has injected some Ruby 1.8 code into the wordnet
packaging.  I personally do not speak Ruby and thus can not fix the
problem in an other way than simply droping the goldendict-wordnet
binary package (its data package is created in this way).

Since Dmitry has not (yet) respondet to this bug report I would like
to ask the Ruby team to find a patch for the problem in the build
system that fixes the following:


WARNING: sentidx.vrb format error: ["pet%2:35:00::"]
debian/wn-for-goldendict.rb:300:in `initialize': undefined method `times' for 
"\x01":String (NoMethodError)
from debian/wn-for-goldendict.rb:158:in `new'
from debian/wn-for-goldendict.rb:158:in `get_data'
from debian/wn-for-goldendict.rb:648:in `block (2 levels) in '
from debian/wn-for-goldendict.rb:647:in `each'
from debian/wn-for-goldendict.rb:647:in `block in '
from debian/wn-for-goldendict.rb:644:in `foreach'
from debian/wn-for-goldendict.rb:644:in `'


If I do not get any help I need to go the unfortunate route to kick
goldendict support again.

Kind regards

 Andreas.


On Wed, Dec 25, 2013 at 05:57:33PM +0100, Christian Hofstaedtler wrote:
> Package: wordnet
> Severity: normal
> 
> Dear Maintainer,
> 
> Your package "wordnet" uses Ruby 1.8 during it's build process.
> Ruby 1.8 is no longer maintained upstream, and the Ruby team wishes to
> remove it from the archive soon. Please migrate your build scripts to
> use Ruby 1.9 or 2.0.
> 
> For your convienence a "ruby" package is provided which always depends
> on the current default version of the ruby interpreter (at time of this
> writing, the default is 1.9.1).
> 
> Thank you,
> Christian
> 
> -- 
>  ,''`.  Christian Hofstaedtler 
> : :' :  Debian Developer
> `. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
>   `-
> 
> -- 
> debian-science-maintainers mailing list
> debian-science-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
> 

-- 
http://fam-tille.de


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

Bug#567210: doc-available always returns false without network

[Eugene Zhukov]

Hi Michael,

Thanks for your previous replay.
I checked with tcpdump and Wireshark that requests are made to
www.w3.org [0]. Hence the failure without network.
Could you please elaborate how to patch Saxonb 9.1.0.8 to redirect
those requests to a local copy held within Saxon itself?

You can find previous discussion here:
http://bugs.debian.org/567210

[0] http://paste.debian.net/78819/

Thanks & Regards,
Eugene


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

Bug#736923: schleuder should bump the required version of actionmailer to rails 4.0

[Ondřej Surý]

Package: schleuder
Version: 2.2.1-3
Severity: grave
Tags: upstream
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

The schleuder currently depends either on ruby-tmail (for ruby1.8) or
ruby-actionmailer =2.3.14 (for ! ruby1.8).

Either schleuder needs to fix that, or we would need to remove
schleuder from the archive, since tmail is obsolete and
ruby-actionmailer-2.3 has been removed from Debian unstable (finally)
because it's unmaintained upstream (for a long time now).

Ondrej

- -- System Information:
Debian Release: 7.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

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

iEYEARECAAYFAlLnq3oACgkQ9OZqfMIN8nNCHgCgrXEg0nNC3vwWpZQx8Tr4eknC
n/cAoKmjgBUcoZwo4z/iUvS7417UrgVd
=mdSR
-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#733409: marked as done (ttf2ufm: FTBFS: ft.c:15:38: fatal error: freetype/config/ftheader.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jan 2014 13:04:28 +
with message-id 
and subject line Bug#733409: fixed in ttf2ufm 3.4.4~r2+gbp-1
has caused the Debian Bug report #733409,
regarding ttf2ufm: FTBFS: ft.c:15:38: fatal error: freetype/config/ftheader.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.)


-- 
733409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ttf2ufm
Version: 3.4.4~r2-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131226 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

On the new 2.5 version the headers are located at
'/usr/include/freetype2/ftglyph.h' instead of
'/usr/include/freetype2/freetype/ftglyph.h' like in previous versions.

Relevant part (hopefully):
> cc -O2 -D_GNU_SOURCE -DUSE_FREETYPE -I/usr/include/freetype2 -I/usr/include   
> -c ft.c
> ft.c:15:38: fatal error: freetype/config/ftheader.h: No such file or directory
>  #include 
>   ^
> compilation terminated.
> make[1]: *** [ft.o] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/12/26/ttf2ufm_3.4.4~r2-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: ttf2ufm
Source-Version: 3.4.4~r2+gbp-1

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated ttf2ufm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 28 Jan 2014 13:45:44 +0100
Source: ttf2ufm
Binary: ttf2ufm
Architecture: source amd64
Version: 3.4.4~r2+gbp-1
Distribution: unstable
Urgency: low
Maintainer: Ondřej Surý 
Changed-By: Ondřej Surý 
Description: 
 ttf2ufm- True Type to PostScript Type 1 Font Converter
Closes: 733409
Changes: 
 ttf2ufm (3.4.4~r2+gbp-1) unstable; urgency=low
 .
   * New upstream version 3.4.4~r2+gbp without upstream binary mess
   * Include fix for freetype transition mess (Closes: #733409)
Checksums-Sha1: 
 8034f45a7d59712d12dccec0c07306050bfe9d94 1256 ttf2ufm_3.4.4~r2+gbp-1.dsc
 57816593f669801aa26a6872206b7ffc8ef21876 515592 
ttf2ufm_3.4.4~r2+gbp.orig.tar.gz
 501817e006d952bfe404eee25dc56c011839cd33 12100 
ttf2ufm_3.4.4~r2+gbp-1.debian.tar.xz
 d125643b03fcf400ab6a31248372e5487c9845d1 254128 
ttf2ufm_3.4.4~r2+gbp-1_amd64.deb
Checksums-Sha256: 
 651e6f19228ebffc71394a1b17d736861bf2f127535aa2f5046ea5619b20a0f4 1256 
ttf2ufm_3.4.4~r2+gbp-1.dsc
 fdab0b76ffe84cd9db2d53a81d26aeb3f64fbd273372817891809625c46e0b9f 515592 
ttf2ufm_3.4.4~r2+gbp.orig.tar.gz
 96a6d7f7058e3df2652812f605db7ad0ad0ba666cf685c4327ca38d67102ea1a 12100 
ttf2ufm_3.4.4~r2+gbp-1.debian.tar.xz
 5b872271841108e94238952b6a630c5bd6632ebdb06f37e45538d64020dcb630 254128 
ttf2ufm_3.4.4~r2+gbp-1_amd64.deb
Files: 
 d37a51826192b0eb2de3ba8c96a06f98 1256 utils extra ttf2ufm_3.4.4~r2+gbp-1.dsc
 9407222fd271d76d3296b5502b2f3765 515592 utils extra 
ttf2ufm_3.4.4~r2+gbp.orig.tar.gz
 58de4171f0bc3fe3bd08b038c4691d66 12100 utils extra 
ttf2ufm_3.4.4~r2+gbp-1.debian.tar.xz
 08b308ad7d48d309e0a7315e0eb4966b 254128 utils extra 
ttf2ufm_3.4.4~r2+gbp-1_amd64.deb

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

iEYEARECAAYFAlLnp+8ACgkQ9OZqfMIN8nN0AQCgitWKqboHibGEx9NuusRHeXq+
oqIAnjHfSQ4edAOmuED0IZjLilxj67yB
=TmGL
-END PGP SIGNATURE End Message ---

Bug#699647: proftpd-mod-geoip: /usr/lib/proftpd/mod_geoip.so missing after upgrade from sid

[Francesco P. Lovergine]

On Mon, Jan 27, 2014 at 08:35:02PM +0100, Andreas Beckmann wrote:
> Won't work. Even if you ensure via Conflicts/Pre-Depends that the buggy 
> package gets removed, the postrm script will stay around. You cannot force a 
> package to be purged.
> (Changing the module filename would work.)

which seems to me much better than a ugly hack such as the proposed one.

-- 
Francesco P. Lovergine


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

Bug#734344: marked as done (opendnssec-auditor: Please migrate to Ruby 1.9/2.0)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jan 2014 12:49:51 +
with message-id 
and subject line Bug#734344: fixed in opendnssec 1:1.4.3-3
has caused the Debian Bug report #734344,
regarding opendnssec-auditor: Please migrate to Ruby 1.9/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.)


-- 
734344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734344
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: opendnssec-auditor
Version: 1:1.3.16-2
Severity: important

Dear Maintainer,

your package "opendnssec-auditor" depends on Ruby 1.8, an obsolete
version of the Ruby interpreter.

As you are likely aware, the Debian Ruby team is willing to remove this
version soon.

Please migrate to Ruby 1.9 / 2.0 to ensure your package continues to be
installable.

Thank you,
Christian
--- End Message ---
--- Begin Message ---
Source: opendnssec
Source-Version: 1:1.4.3-3

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated opendnssec package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 28 Jan 2014 13:17:29 +0100
Source: opendnssec
Binary: opendnssec-common opendnssec opendnssec-doc opendnssec-enforcer 
opendnssec-enforcer-mysql opendnssec-enforcer-sqlite3 opendnssec-signer 
libhsm-bin opendnssec-dbg-mysql opendnssec-dbg-sqlite3
Architecture: source all amd64
Version: 1:1.4.3-3
Distribution: unstable
Urgency: medium
Maintainer: Ondřej Surý 
Changed-By: Ondřej Surý 
Description: 
 libhsm-bin - library for interfacing PKCS#11 Hardware Security Modules
 opendnssec - dependency package to install full OpenDNSSEC suite
 opendnssec-common - common configuration files for OpenDNSSEC suite
 opendnssec-dbg-mysql - Debug symbols for OpenDNSSEC (Enforcer with MySQL 
support)
 opendnssec-dbg-sqlite3 - Debug symbols for OpenDNSSEC (Enforcer with SQLite3 
support)
 opendnssec-doc - documentation for OpenDNSSEC suite
 opendnssec-enforcer - tool to prepare DNSSEC keys (common package)
 opendnssec-enforcer-mysql - tool to prepare DNSSEC keys (mysql backend)
 opendnssec-enforcer-sqlite3 - tool to prepare DNSSEC keys (sqlite3 backend)
 opendnssec-signer - daemon to sign DNS zone files periodically
Closes: 717980 734344 735587
Changes: 
 opendnssec (1:1.4.3-3) unstable; urgency=medium
 .
   * Add epoch to conflicts/breaks with opendnssec-auditor (Closes: #717980)
   * opendnssec-auditor has been removed (Closes: #734344, #735587)
Checksums-Sha1: 
 5d96d857713c2e73207ae689f5aba21dfdfccf69 1962 opendnssec_1.4.3-3.dsc
 f2b1978d6226caa3647edddbd67c3830300c453e 16312 opendnssec_1.4.3-3.debian.tar.xz
 9769d3fc1178d8d702408b9af1f9b855393449d5 46822 
opendnssec-common_1.4.3-3_all.deb
 fbffd62f16d4a3f39c1ef53653d8a6f0818e5933 25854 opendnssec_1.4.3-3_all.deb
 894d701f187fa4e2c08988cbc557d56979690b9a 57442378 
opendnssec-doc_1.4.3-3_all.deb
 28ec3d130067a9bb99f85b0e356bf2a3fc129b47 41266 
opendnssec-enforcer_1.4.3-3_all.deb
 be64d7ec1701606dbb943bb354ee528735912fba 122862 
opendnssec-enforcer-mysql_1.4.3-3_amd64.deb
 5380f95b9315fc149bb617cfd1a99818b4e5706e 122042 
opendnssec-enforcer-sqlite3_1.4.3-3_amd64.deb
 ecc54906bf504ebf6da62577da9307f3168eac53 162184 
opendnssec-signer_1.4.3-3_amd64.deb
 21bba0da42cf75ab5d7351963c5da40a1499b8ee 54492 libhsm-bin_1.4.3-3_amd64.deb
 151973ed34e4e021102ade12dc2d7bfb6d9d3532 643556 
opendnssec-dbg-mysql_1.4.3-3_amd64.deb
 f54ea1d42da7601bef8e55184aaf391ee6552c5d 632298 
opendnssec-dbg-sqlite3_1.4.3-3_amd64.deb
Checksums-Sha256: 
 71990941f2eaa38cfb6592c1d8459d3cc25b8da30806505fa054146170c33c1e 1962 
opendnssec_1.4.3-3.dsc
 3c5f48e581cda03745897f41e15b0f97a4dfb6f4e3a43972ae123cfc7b26d9b1 16312 
opendnssec_1.4.3-3.debian.tar.xz
 a50bc0de31082e71dc70ddd3eb5c0691364f4c24d30a25a21cf288b99d60a312 46822 
opendnssec-common_1.4.3-3_all.deb
 bcbb7f4f5c2ad78e3697b28f47fcfb0874bfd0bacecad23a3247e99936bdf722 25854 
opendnssec_1.4.3-3_all.deb
 df55bab9eb9f98c059c50da057dc4fc532b36962b795f421285ed8c83be42908 57442378 
opendnssec-doc_1.4.3-3_all.deb
 71875bedebb6c

Bug#717980: marked as done (opendnssec-enforcer-mysql: fails to upgrade from 'sid' - trying to overwrite /usr/bin/ods-kaspcheck)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jan 2014 12:49:51 +
with message-id 
and subject line Bug#717980: fixed in opendnssec 1:1.4.3-3
has caused the Debian Bug report #717980,
regarding opendnssec-enforcer-mysql: fails to upgrade from 'sid' - trying to 
overwrite /usr/bin/ods-kaspcheck
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.)


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

Hi,

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

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

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

  Selecting previously unselected package opendnssec-enforcer-mysql.
  Unpacking opendnssec-enforcer-mysql (from 
.../opendnssec-enforcer-mysql_1%3a1.4.1-1_amd64.deb) ...
  dpkg: error processing 
/var/cache/apt/archives/opendnssec-enforcer-mysql_1%3a1.4.1-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/ods-kaspcheck', which is also in package 
opendnssec-auditor 1:1.3.14-2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/opendnssec-enforcer-mysql_1%3a1.4.1-1_amd64.deb


cheers,

Andreas


opendnssec-auditor=1:1.3.14-2_opendnssec-enforcer-mysql=1:1.4.1-1.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Source: opendnssec
Source-Version: 1:1.4.3-3

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated opendnssec package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 28 Jan 2014 13:17:29 +0100
Source: opendnssec
Binary: opendnssec-common opendnssec opendnssec-doc opendnssec-enforcer 
opendnssec-enforcer-mysql opendnssec-enforcer-sqlite3 opendnssec-signer 
libhsm-bin opendnssec-dbg-mysql opendnssec-dbg-sqlite3
Architecture: source all amd64
Version: 1:1.4.3-3
Distribution: unstable
Urgency: medium
Maintainer: Ondřej Surý 
Changed-By: Ondřej Surý 
Description: 
 libhsm-bin - library for interfacing PKCS#11 Hardware Security Modules
 opendnssec - dependency package to install full OpenDNSSEC suite
 opendnssec-common - common configuration files for OpenDNSSEC suite
 opendnssec-dbg-mysql - Debug symbols for OpenDNSSEC (Enforcer with MySQL 
support)
 opendnssec-dbg-sqlite3 - Debug symbols for OpenDNSSEC (Enforcer with SQLite3 
support)
 opendnssec-doc - documentation for OpenDNSSEC suite
 opendnssec-enforcer - tool to prepare DNSSEC keys (common package)
 opendnssec-enforcer-mysql - tool to prepare DNSSEC keys (mysql backend)
 opendnssec-enforcer-sqlite3 - tool to prepare DNSSEC keys (sqlite3 backend)
 opendnssec-signer - daemon to sign DNS zone files periodically
Closes: 717980 734344 735587
Changes: 
 opendnssec (1:1.4.3-3) unstable; urgency=medium
 .
   * Add epoch to conflicts/breaks with opendnssec-auditor (Closes: #717980)
   * opendnssec-auditor has been removed (Closes: #734344, #735587)
Checksums-Sha1: 
 5d96d857713c2e73207ae689f5aba21dfdfccf69 1962 opendnssec_1.4.3-3.dsc
 f2b1978d6226caa3647edddbd67c3830300c453e 16312 opendnssec_1.4.3-3.debian.tar.xz
 9769d3fc1178d8d702408b9af1f9b855393449d5 46822 
opendnssec-common_1.4.3-3_all.deb
 fbffd62f16d4a3f39c1ef53653d8a6f0818e5933 25854 opendnssec_1.4.3-3_all.deb
 894d701f187fa4e2c08988cbc557d56979690b9a 57442378 
opendnssec-doc_1.4.3-3_all.deb
 28ec3d130067a9bb99f85b0e356bf2a3fc129b47 41266 
opendnssec-enforcer_1.4.3-3_all.deb
 be64d7ec1701606dbb943bb354ee528735912fba 122862 
opendnssec-enforcer-mysql_1.4.3-3_amd64.deb
 5380f95b9315fc149bb617cfd1a99818b4e5706e 122042 
opendnssec-enforcer-sql

Bug#735587: marked as done (opendnssec: please do not build-depend on rubygems anymore)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jan 2014 12:49:51 +
with message-id 
and subject line Bug#735587: fixed in opendnssec 1:1.4.3-3
has caused the Debian Bug report #735587,
regarding opendnssec: please do not build-depend on rubygems anymore
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.)


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

Dear Ondrej,
Could you please remove rubygems from the build dependencies?
The rubygems package would like to go away from the archive, together
with ruby1.8.

Thanks in advance.

Cédric
--- End Message ---
--- Begin Message ---
Source: opendnssec
Source-Version: 1:1.4.3-3

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated opendnssec package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 28 Jan 2014 13:17:29 +0100
Source: opendnssec
Binary: opendnssec-common opendnssec opendnssec-doc opendnssec-enforcer 
opendnssec-enforcer-mysql opendnssec-enforcer-sqlite3 opendnssec-signer 
libhsm-bin opendnssec-dbg-mysql opendnssec-dbg-sqlite3
Architecture: source all amd64
Version: 1:1.4.3-3
Distribution: unstable
Urgency: medium
Maintainer: Ondřej Surý 
Changed-By: Ondřej Surý 
Description: 
 libhsm-bin - library for interfacing PKCS#11 Hardware Security Modules
 opendnssec - dependency package to install full OpenDNSSEC suite
 opendnssec-common - common configuration files for OpenDNSSEC suite
 opendnssec-dbg-mysql - Debug symbols for OpenDNSSEC (Enforcer with MySQL 
support)
 opendnssec-dbg-sqlite3 - Debug symbols for OpenDNSSEC (Enforcer with SQLite3 
support)
 opendnssec-doc - documentation for OpenDNSSEC suite
 opendnssec-enforcer - tool to prepare DNSSEC keys (common package)
 opendnssec-enforcer-mysql - tool to prepare DNSSEC keys (mysql backend)
 opendnssec-enforcer-sqlite3 - tool to prepare DNSSEC keys (sqlite3 backend)
 opendnssec-signer - daemon to sign DNS zone files periodically
Closes: 717980 734344 735587
Changes: 
 opendnssec (1:1.4.3-3) unstable; urgency=medium
 .
   * Add epoch to conflicts/breaks with opendnssec-auditor (Closes: #717980)
   * opendnssec-auditor has been removed (Closes: #734344, #735587)
Checksums-Sha1: 
 5d96d857713c2e73207ae689f5aba21dfdfccf69 1962 opendnssec_1.4.3-3.dsc
 f2b1978d6226caa3647edddbd67c3830300c453e 16312 opendnssec_1.4.3-3.debian.tar.xz
 9769d3fc1178d8d702408b9af1f9b855393449d5 46822 
opendnssec-common_1.4.3-3_all.deb
 fbffd62f16d4a3f39c1ef53653d8a6f0818e5933 25854 opendnssec_1.4.3-3_all.deb
 894d701f187fa4e2c08988cbc557d56979690b9a 57442378 
opendnssec-doc_1.4.3-3_all.deb
 28ec3d130067a9bb99f85b0e356bf2a3fc129b47 41266 
opendnssec-enforcer_1.4.3-3_all.deb
 be64d7ec1701606dbb943bb354ee528735912fba 122862 
opendnssec-enforcer-mysql_1.4.3-3_amd64.deb
 5380f95b9315fc149bb617cfd1a99818b4e5706e 122042 
opendnssec-enforcer-sqlite3_1.4.3-3_amd64.deb
 ecc54906bf504ebf6da62577da9307f3168eac53 162184 
opendnssec-signer_1.4.3-3_amd64.deb
 21bba0da42cf75ab5d7351963c5da40a1499b8ee 54492 libhsm-bin_1.4.3-3_amd64.deb
 151973ed34e4e021102ade12dc2d7bfb6d9d3532 643556 
opendnssec-dbg-mysql_1.4.3-3_amd64.deb
 f54ea1d42da7601bef8e55184aaf391ee6552c5d 632298 
opendnssec-dbg-sqlite3_1.4.3-3_amd64.deb
Checksums-Sha256: 
 71990941f2eaa38cfb6592c1d8459d3cc25b8da30806505fa054146170c33c1e 1962 
opendnssec_1.4.3-3.dsc
 3c5f48e581cda03745897f41e15b0f97a4dfb6f4e3a43972ae123cfc7b26d9b1 16312 
opendnssec_1.4.3-3.debian.tar.xz
 a50bc0de31082e71dc70ddd3eb5c0691364f4c24d30a25a21cf288b99d60a312 46822 
opendnssec-common_1.4.3-3_all.deb
 bcbb7f4f5c2ad78e3697b28f47fcfb0874bfd0bacecad23a3247e99936bdf722 25854 
opendnssec_1.4.3-3_all.deb
 df55bab9eb9f98c059c50da057dc4fc532b36962b795f421285ed8c83be42908 57442378 
opendnssec-doc_1.4.3-3_all.deb
 71875bedebb6cb82ef090d7a2ad74a8467eef2b06dfc7233d1463cbb8e52c545 41266 
opendnssec-enforcer_1.4.3-3_all.deb
 15fb0118f777b4445b86ec3c87e4c874a24c245eefa3ca4684

Bug#731074: [pkg-lighttpd] Bug#731074: lighttpd: indeterminate test on kfreebsd buildds

[Arno Töll]

Hi Steven.

On 27.01.2014 21:22, Steven Chamberlain wrote:
> I could reproduce it 8 times out of 100 here on kfreebsd-amd64.
> 
> The race happens after getting Connection Refused trying to contact the
> fcgi-responder which has just exit (intentionally).
> 
> The parent does a wait4() syscall, and if this returns the pid of the
> process that just exit, a new listen is set up on 1/tcp and lighttpd
> forks a new fcgi-responder.  The parent waits with select() for it to be
> ready, then sends the FCGI request which is successful:

is this a libc portability issue then? All in all this does not really
sound like a problem in the lighttpd code base, does it?


-- 
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D



signature.asc
Description: OpenPGP digital signature

Bug#736628: marked as forwarded (procps: FTBFS [amd64]: FAIL: vmstat partition (using sda1))

[Debian Bug Tracking System]

Your message dated Tue, 28 Jan 2014 21:46:06 +1100
with message-id <20140128104606.gb24...@enc.com.au>
has caused the   report #736628,
regarding procps: FTBFS [amd64]: FAIL: vmstat partition (using sda1)
to be marked as having been forwarded to the upstream software
author(s) Procps-ng Mail list 

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


-- 
736628: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
I've had some bug reports reporting that vmstat crashes under certain
circumstances. Usually it gets reported when the pbuilders gag on the
test scripts.

The symptoms are that "vmstat -p " such as vmstat -p sda1
will make vmstat crash.  I can confirm that if any partition appears
before any disk then vmstat -p or vmstat -D (basically anything that
uses getdiskstat() ) will crash. The code also assumes that all
partitions appear immediately after the relevant disk, which may or
may not be true.

The problem is, I'm trying to work out when this does occur and what
vmstat should do about it.

References: http://bugs.debian.org/736628

 - Craig
-- 
Craig Small (@smallsees)   http://enc.com.au/   csmall at : enc.com.au
Debian GNU/Linux   http://www.debian.org/   csmall at : debian.org
GPG fingerprint:5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5--- End Message ---

Bug#736872: marked as done (busybox: zcat does not decompress file which do not have a .gz suffix)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jan 2014 10:48:33 +
with message-id 
and subject line Bug#736872: fixed in busybox 1:1.22.0-3
has caused the Debian Bug report #736872,
regarding busybox: zcat does not decompress file which do not have a .gz suffix
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.)


-- 
736872: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736872
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: busybox
Version: 1:1.22.0-2
Severity: critical
Justification: breaks the whole system

The zcat applet seems to behave like cat unless the input file has a .gz
suffix:

Given two identical files (compressed string "Hello World"), one with a .gz
suffix and one without:

$ file test test.gz
test:gzip compressed data, was "test", from Unix, last modified: Mon Jan 27 
20:31:45 2014
test.gz: gzip compressed data, was "test", from Unix, last modified: Mon Jan 27 
20:31:45 2014
$ md5sum test test.gz
9001811fcfd18c9479e98f78ebfd364b  test
9001811fcfd18c9479e98f78ebfd364b  test.gz

Regular zcat behaves as expected:
$ zcat test | file -
/dev/stdin: ASCII text
$ zcat test.gz | file -
/dev/stdin: ASCII text

But busybox zcat does not:
$ busybox zcat test | file -
/dev/stdin: gzip compressed data, was "test", from Unix, last modified: Mon Jan 
27 20:31:45 2014
$ busybox zcat test.gz | file -
/dev/stdin: ASCII text

If the input file does not have a .gz suffix then zcat is behaving
like plain cat:
$ cat test | md5sum
9001811fcfd18c9479e98f78ebfd364b  -
$ busybox zcat test | md5sum
9001811fcfd18c9479e98f78ebfd364b  -

It works correctly when operating on stdin:
$ cat test | busybox zcat | file -
/dev/stdin: ASCII text

I've given this severity critical since it break the installer by breaking at
least net-retriever.

The version currently in Jessie (1:1.21.0-1) seems to be OK:
$ busybox zcat test | file -
/dev/stdin: ASCII text

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

Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages busybox depends on:
ii  libc6  2.17-92+b1

busybox recommends no packages.

busybox suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: busybox
Source-Version: 1:1.22.0-3

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

Debian distribution maintenance software
pp.
Michael Tokarev  (supplier of updated busybox package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 28 Jan 2014 14:27:50 +0400
Source: busybox
Binary: busybox busybox-static busybox-udeb busybox-syslogd udhcpc udhcpd
Architecture: source amd64 all
Version: 1:1.22.0-3
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team 
Changed-By: Michael Tokarev 
Description: 
 busybox- Tiny utilities for small and embedded systems
 busybox-static - Standalone rescue shell with tons of builtin utilities
 busybox-syslogd - Provides syslogd and klogd using busybox
 busybox-udeb - Tiny utilities for the debian-installer (udeb)
 udhcpc - Provides the busybox DHCP client implementation
 udhcpd - Provides the busybox DHCP server implementation
Closes: 375568 484799 696704 704815 736872
Changes: 
 busybox (1:1.22.0-3) unstable; urgency=low
 .
   * mention closing of #685361 by 1.22
   * enable devmem applet for regular and static builds (Closes: #696704)
   * enable acpid applet for regular and static builds (Closes: #704815)
   * enable mount -f (MOUNT_FAKE) for all builds (Closes: #484799)
   * let busybox-static to provide busybox (Closes: #375568)
   * added two fixes from upstream (Closes: #736872)
 libarchive-open_zipped-does-not-need-to-check-extensions.diff
 libbb-open_zipped-should-not-fail-on-non-compressed-files.diff
Checksums-Sha1: 
 c42a5955658429b09600c3289833491c0dca1560 1630 busybox_1.22.0-3.dsc
 111d7fc

Bug#736628: procps: FTBFS [amd64]: FAIL: vmstat partition (using sda1)

[Craig Small]

tags 736628 help
tags 736628 upstream
On Mon, Jan 27, 2014 at 09:08:56AM -0800, Daniel Schepler wrote:
> (gdb) p disks
> $1 = (struct disk_stat **) 0x7fffeb08
> (gdb) p *disks
> $2 = (struct disk_stat *) 0x0
> (gdb) p cDisk
The problem seems to be that a partition is found before the disk
appears. More specifically, the partition needs to be before *any*
disk. (A different but related bug is that the library assumes
all partitions appear immediately after the disk line).

So: sda, sda1, sda2 = ok
sda1,sda2,sda = crash
sr0, sda1, sda2 = ok, but sda1 is "linked" to sr0

The problem now is, under what conditions do these odd
/proc/diskstats occur and what interpretation should
vmstat make of the situation? Ignore the partitions?
Raise an error? re-map the disk->partition links
after reading the file?

 - Craig

-- 
Craig Small (@smallsees)   http://enc.com.au/   csmall at : enc.com.au
Debian GNU/Linux   http://www.debian.org/   csmall at : debian.org
GPG fingerprint:5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5


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

Bug#736914: missing licenses in debian/copyright

[Thorsten Alteholz]

Package: efl
Severity: serious
User: alteh...@debian.org
Usertags: ftp
X-Debbugs-CC: ftpmas...@ftp-master.debian.org
thanks

Dear Maintainer,

please add the MIT license of at least:
  src/modules/evas/engines/psl1ght/rsxutil.c
  src/modules/evas/engines/psl1ght/rsxutil.h
  src/benchmarks/eina/city.cc
  src/benchmarks/eina/city.h
  src/lib/ecore_con/dns.c
  src/lib/ecore_con/dns.h
  parts of src/lib/eina/*
to debian/copyright.

Thanks!
  Thorsten


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

Bug#724143: marked as done (ion: FTBFS: POD errors)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jan 2014 10:03:26 +
with message-id 
and subject line Bug#724143: fixed in ion 3.2.0~dfsg1-1
has caused the Debian Bug report #724143,
regarding ion: FTBFS: POD errors
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.)


-- 
724143: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ion
Version: 3.1.3~dfsg1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130922 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):
> mkdir -p ./ici/doc
> mkdir -p ./ltp/doc
> mkdir -p ./dgr/doc
> mkdir -p ./bp/doc
> mkdir -p ./bss/doc
> mkdir -p ./cfdp/doc
> pod2man -s 1 -c "ICI executables" ici/doc/pod1/ionadmin.pod ici/doc/ionadmin.1
> pod2man -s 1 -c "ICI executables" ici/doc/pod1/ionsecadmin.pod 
> ici/doc/ionsecadmin.1
> pod2man -s 1 -c "ICI executables" ici/doc/pod1/rfxclock.pod ici/doc/rfxclock.1
> ici/doc/pod1/rfxclock.pod around line 47: Expected text after =item, not a 
> number
> POD document had syntax errors at /usr/bin/pod2man line 71.
> make[3]: *** [ici/doc/rfxclock.1] Error 255

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/09/22/ion_3.1.3~dfsg1-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: ion
Source-Version: 3.2.0~dfsg1-1

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

Debian distribution maintenance software
pp.
Leo Iannacone  (supplier of updated ion package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 09 Jul 2013 16:22:20 +0200
Source: ion
Binary: ion libion0 libion-dev ion-doc
Architecture: source amd64 all
Version: 3.2.0~dfsg1-1
Distribution: unstable
Urgency: low
Maintainer: Leo Iannacone 
Changed-By: Leo Iannacone 
Description: 
 ion- NASA implementation of Delay-Tolerant Networking (DTN)
 ion-doc- Interplanetary Overlay Network - examples and documentation
 libion-dev - NASA implementation of Delay-Tolerant Networking (DTN) - developm
 libion0- NASA implementation of Delay-Tolerant Networking (DTN) - main lib
Closes: 724143
Changes: 
 ion (3.2.0~dfsg1-1) unstable; urgency=low
 .
   * New upstream release.
   * Updated debian/ion-tools.pod and debian/ion.links
 with new binaries.
   * Updated fix-manpages-errors.patch (closes: #724143).
   * Refreshed old patches.
   * Removed fix-gcc4.8-errors.patch. Applied to upstream.
Checksums-Sha1: 
 bdf657bedcb275dc4f1f6c4a38f429ef6d3df1a7 1992 ion_3.2.0~dfsg1-1.dsc
 ff90bb169ad3444eb4c333449492d45a785439fc 4093562 ion_3.2.0~dfsg1.orig.tar.gz
 774582f91d7d2ed4559c850f8ee8ec4e016d2d66 9613 ion_3.2.0~dfsg1-1.debian.tar.gz
 17a98a5527625ea09e03eac1dd49f75a48af3ef9 781626 ion_3.2.0~dfsg1-1_amd64.deb
 a3343396c10c634b08c90b388ef27d00648074ac 330542 libion0_3.2.0~dfsg1-1_amd64.deb
 4b01e0a96b477929e40f723ef8ab468dda7b7923 56494 
libion-dev_3.2.0~dfsg1-1_amd64.deb
 4bc40b38004bc37c791739e66647ba2ade0f175a 210138 ion-doc_3.2.0~dfsg1-1_all.deb
Checksums-Sha256: 
 0301198fec9a625950193d95a26187f12d2c098272885cc4d3474ee85acc03c2 1992 
ion_3.2.0~dfsg1-1.dsc
 2a5edadd2ea87b32c8997180e88a29a186ef3cfdd4fb3af79fe66babe460dae9 4093562 
ion_3.2.0~dfsg1.orig.tar.gz
 091a31c51223ef4a97377aa0093f70eb33061b337540ae2d2f11a97077c37541 9613 
ion_3.2.0~dfsg1-1.debian.tar.gz
 bd96cba11a2446c6ce7a7a188d2cb935a8729d0b0629451cdb753d494b7359d5 781626 
ion_3.2.0~dfsg1-1_amd64.deb
 73cfb73838235193ff68eb5d352bcdc34dc137abd47f0e5b6dfa7cc72df3a9b0 330542 
libion0_3.2.0~dfsg1-1_amd64.deb
 cc80ddbb5f70d33203ee0d7f1daa1ae9defeda44bf4acfbc75cdca021323eb8

Bug#736872: busybox: zcat does not decompress file which do not have a .gz suffix

[Ian Campbell]

On Tue, 2014-01-28 at 13:07 +0400, Michael Tokarev wrote:
> Uncortunately, this whole mess around compression introduces another issue.
> After the 2 fixes for this bug, busybox zcat happily accepts uncompressed
> input and behaves like regular cat, while original zcat refuses to accept
> uncpmpressed input.  I reported this upstream.

Ugh, nasty. (It seems to me that the code is simply trying to be too
clever...)

> But I think it is better
> to accept and use uncompressed data than to fail to decompress compressed
> data, and the current bug is indeed serious enough to have a quick fix.

I agree.

> Thank you!

Thanks for the speedy upload!

Ian.


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