Bug#728074: petsc: FTBFS on several architectures but built there in the past

[Niels Thykier]

Package: petsc
Version: 3.4.2.dfsg1-4
Severity: serious

Hi,

Your package FTBFS on s390x and mipsel (maybe also mips, still waiting
for built there), but has built there in the past.  This is a
regression on a release architecture and therefore an RC bug.

~Niels


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

Bug#692606: marked as done (network-manager-strongswan: charon dump on vpn start)

[Debian Bug Tracking System]

Your message dated Mon, 28 Oct 2013 08:53:59 +0100
with message-id <1382946839.2105.6.camel@scapa>
and subject line Marking as done in recent versions
has caused the Debian Bug report #692606,
regarding network-manager-strongswan: charon dump on vpn 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.)


-- 
692606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager-strongswan
Version: 1.3.0-1
Severity: important

Dear Maintainer,

start of a nm - strongswan vpn fail without connecting the vpn server.(die
immedetly after start)
Same with new kernel.
Starting /usr/lib/ipsec/charon in consol  than start vpn give me that in
console see attached file





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

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

Versions of packages network-manager-strongswan depends on:
ii  gconf-service   3.2.5-1+build1
ii  libart-2.0-22.3.21-2
ii  libatk1.0-0 2.4.0-2
ii  libbonobo2-02.24.3-1
ii  libbonoboui2-0  2.24.3-1
ii  libc6   2.13-35
ii  libcairo2   1.12.2-2
ii  libdbus-1-3 1.6.8-1
ii  libdbus-glib-1-20.100-1
ii  libfontconfig1  2.9.0-7
ii  libfreetype62.4.9-1
ii  libgconf-2-43.2.5-1+build1
ii  libgdk-pixbuf2.0-0  2.26.1-1
ii  libglib2.0-02.33.12+really2.32.4-3
ii  libgnome-keyring0   3.4.1-1
ii  libgnome2-0 2.32.1-2
ii  libgnomecanvas2-0   2.30.3-1.2
ii  libgnomeui-02.24.5-2
ii  libgnomevfs2-0  1:2.24.4-1
ii  libgtk2.0-0 2.24.10-2
ii  libice6 2:1.0.8-2
ii  libnm-glib-vpn1 0.9.4.0-6
ii  libnm-glib4 0.9.4.0-6
ii  libnm-util2 0.9.4.0-6
ii  liborbit2   1:2.14.19-0.1
ii  libpango1.0-0   1.30.0-1
ii  libpopt01.16-7
ii  libsm6  2:1.2.1-2
ii  network-manager 0.9.4.0-6
ii  strongswan-nm   4.5.2-1.5

network-manager-strongswan recommends no packages.

network-manager-strongswan suggests no packages.
# /usr/lib/ipsec/charon
00[DMN] Starting IKEv2 charon daemon (strongSwan 4.5.2)
00[LIB] Padlock not found, CPU is GenuineIntel
00[LIB] plugin 'padlock': failed to load - padlock_plugin_create returned NULL
00[CFG] loaded PKCS#11 v2.20 library 'opensc' (/usr/lib/i386-linux-gnu/opensc-
pkcs11.so)
00[CFG]   OpenSC (www.opensc-project.org): Smart card PKCS#11 API v0.0
00[KNL] listening on interfaces:
00[KNL]   eth0
00[KNL]   eth1
00[KNL] 172.31.0.80
00[KNL] fe80::212:f0ff:fef0:66f9
00[LIB] plugin 'stroke' failed to load: /usr/lib/ipsec/plugins/libstrongswan-
stroke.so: cannot open shared object file: No such file or directory
00[CFG] sql plugin: database URI not set
00[LIB] plugin 'sql': failed to load - sql_plugin_create returned NULL
00[LIB] plugin 'updown' failed to load: /usr/lib/ipsec/plugins/libstrongswan-
updown.so: cannot open shared object file: No such file or directory
00[CFG] loaded 0 RADIUS server configurations
00[LIB] plugin 'medsrv' failed to load: /usr/lib/ipsec/plugins/libstrongswan-
medsrv.so: cannot open shared object file: No such file or directory
00[CFG] mediation client database URI not defined, skipped
00[LIB] plugin 'medcli': failed to load - medcli_plugin_create returned NULL
00[CFG] HA config misses local/remote address
00[LIB] plugin 'ha': failed to load - ha_plugin_create returned NULL
00[DMN] loaded plugins: test-vectors curl ldap aes des sha1 sha2 md5 random
x509 revocation constraints pubkey pkcs1 pgp pem openssl fips-prf gmp agent
pkcs11 xcbc hmac ctr ccm gcm attr kernel-netlink resolve socket-raw farp eap-
identity eap-aka eap-md5 eap-gtc eap-mschapv2 eap-radius eap-tls eap-ttls eap-
tnc nm dhcp led addrblock
00[DMN] removing pidfile '/var/run/charon.pid', process not running
00[JOB] spawning 16 worker threads
05[CFG] module 'opensc' does not support hot-plugging, cancelled
08[CFG] received initiate for NetworkManager connection Test.Monster
08[DMN] thread 8 received 11
 dumping 17 stack frame addresses:
   @ 0xb771f000 (__kernel_sigreturn+0x0) [0xb771f400]
-> addr2line: '0xb771f400': No such file

  /usr/lib/ipsec/plugins/libstrongswan-nm.so @ 0xb6b75000 [0xb6b778c9]
-> ??:0
  /usr/lib/libnm-glib-vpn.so.1 @ 0xb6ac7000 [0xb6aca680]
-> ??:0
  /usr/lib/libnm-glib-vpn.so.1 @ 0xb6ac7000 [0xb6ac9699]
-> ??:0
  /usr/lib/i386-linux-gnu/libdbus-glib-1.so.2 @ 0xb6aa1000 [0xb6aac4e0]
-> 

Processed: fixed 692606 in 4.6.4-1

[Debian Bug Tracking System]

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

> # oops, actually providing the fixed version
> fixed 692606 4.6.4-1
Bug #692606 [strongswan-nm] network-manager-strongswan: charon dump on vpn start
Marked as fixed in versions strongswan/4.6.4-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
692606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692606
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#692606: Marking as done in recent versions

[Yves-Alexis Perez]

Hi,

it seems we never actually received the mail for the reassign, please
always copy the destination package people so they're actually aware of
it.

I'm closing the bug with version information so it's correctly tracked
as fixed in later versions. I'll coordinate with SRM for uploading a fix
to stable. Are you available to test a tentatively fixed package before
upload?

Regards,
-- 
Yves-Alexis


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

Processed: your mail

[Debian Bug Tracking System]

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

> tag 721779 + pending
Bug #721779 [src:billiard] billiard: FTBFS: dh: unable to load addon sphinxdoc
Added tag(s) pending.
> thanks
Stopping processing here.

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

[Debian Bug Tracking System]

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

> tags 727628 + pending
Bug #727628 [xfce4-weather-plugin] broken by weather.com URI change
Added tag(s) pending.
> thanks
Stopping processing here.

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

[fulvio ciriaco]

Package: cmucl
Version: 20c-2
Followup-For: Bug #723679

Hallo,
here cmucl segfaults too, at the same point.
cmucl-20c from upstream segfaults too,
more recent versions, e.g. 20e run fine.
Fulvio

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


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

Kernel: Linux 3.10-3-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 cmucl depends on:
ii  debconf [debconf-2.0]  1.5.51
ii  libc6  2.17-93

Versions of packages cmucl recommends:
ii  binfmt-support  2.0.15

Versions of packages cmucl suggests:
pn  cmucl-docs
pn  cmucl-source  
pn  ilisp 

-- Configuration Files:
/etc/common-lisp/cmucl/site-init.lisp changed [not included]

-- debconf information excluded


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

Bug#728078: ceph: fails to build, assumes all 64-bit architectures are x86-64

[Aurelien Jarno]

Package: ceph
Version: 0.67.3-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

ceph fails to build on 64-bit architectures that are not x86-64 ones. It
tries to build x86 specific assembly code on all 64-bit architectures:

| common/crc32c-intel.c: In function 'crc32c_intel_le_hw_byte':
| common/crc32c-intel.c:41:17: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c: In function 'ceph_crc32c_le_intel':
| common/crc32c-intel.c:63:17: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:59:17: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c: In function 'crc32c_intel_le_hw_byte':
| common/crc32c-intel.c:37:17: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c: In function 'ceph_crc32c_le_intel':
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:68:46: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:68:46: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:68:46: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:68:46: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:68:46: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:99:1: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:48:10: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:48:10: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:48:10: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:48:10: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:48:10: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:48:10: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:48:10: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:48:10: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:48:10: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:48:10: warning: matching constraint does not allow a 
register [enabled by default]
| common/crc32c-intel.c:48:10: warning: matching cons

Bug#728079: stk: FTFBS on kfreebsd but built there in the past

[Niels Thykier]

Package: stk
Version: 4.4.4-3
Severity: serious

Hi,

Your package FTBFS on kfreebsd, but built there in the past.

~Niels


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

Bug#692606: Marking as done in recent versions

[Raphael Geissert]

Hi,

On 28 October 2013 08:53, Yves-Alexis Perez  wrote:
> Hi,
>
> it seems we never actually received the mail for the reassign, please
> always copy the destination package people so they're actually aware of
> it.

Gah, right.

> I'm closing the bug with version information so it's correctly tracked
> as fixed in later versions. I'll coordinate with SRM for uploading a fix
> to stable. Are you available to test a tentatively fixed package before
> upload?

The change is trivial, but sure.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net


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

Bug#692606: Marking as done in recent versions

[Yves-Alexis Perez]

On Mon, 2013-10-28 at 09:46 +0100, Raphael Geissert wrote:
> The change is trivial, but sure.

Yeah, but are you positively certain it fixes your bug?
-- 
Yves-Alexis


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

Bug#728017: marked as done (FTBFS: missing build dependencies)

[Debian Bug Tracking System]

Your message dated Mon, 28 Oct 2013 09:07:15 +
with message-id 
and subject line Bug#728017: fixed in genometools 1.5.1-2
has caused the Debian Bug report #728017,
regarding FTBFS: missing build dependencies
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.)


-- 
728017: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: genometools
Version: 1.5.1-1
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch

A snippet from trying to rebuild in a clean sid chroot:
The following packages have unmet dependencies:
 sbuild-build-depends-genometools-dummy : Depends: liblua5.1-md5-dev but it is 
not installable
E: Unable to correct problems, you have held broken packages.

All these binary renames have occured in unstable.

Thanks!

*** /tmp/tmp8yZKNl/bug_body

In Ubuntu, the attached patch was applied to achieve the following:


  * Change some lua build dependencies to the reflect the renaming of lua
binaries due to lua policy
- update debian/control


Thanks for considering the patch.


-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise-proposed'), (500, 'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.8.0-28-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru genometools-1.5.1/debian/changelog genometools-1.5.1/debian/changelog
diff -Nru genometools-1.5.1/debian/control genometools-1.5.1/debian/control
--- genometools-1.5.1/debian/control	2013-03-07 07:07:56.0 -0600
+++ genometools-1.5.1/debian/control	2013-10-27 11:48:39.0 -0500
@@ -4,8 +4,8 @@
 Maintainer: Debian Med Packaging Team 
 Uploaders: Sascha Steinbiss 
 Build-Depends: debhelper (>= 9),
- liblua5.1-0-dev, liblua5.1-md5-dev, liblua5.1-filesystem-dev,
- liblua5.1-lpeg-dev, libcairo2-dev, zlib1g-dev, libbz2-dev, libexpat1-dev,
+ liblua5.1-0-dev, lua-md5-dev, lua-filesystem-dev,
+ lua-lpeg-dev, libcairo2-dev, zlib1g-dev, libbz2-dev, libexpat1-dev,
  libncurses5-dev, libsqlite3-dev, libbam-dev, libpango1.0-dev,
  texlive-latex-base, texlive-latex-extra, texlive-fonts-extra, latex-xcolor,
  texlive-fonts-recommended, python
--- End Message ---
--- Begin Message ---
Source: genometools
Source-Version: 1.5.1-2

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 28 Oct 2013 08:17:04 +0100
Source: genometools
Binary: genometools genometools-common libgenometools0 libgenometools0-dev 
genometools-doc genometools-dbg python-genometools
Architecture: source amd64 all
Version: 1.5.1-2
Distribution: unstable
Urgency: low
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description: 
 genometools - versatile genome analysis toolkit
 genometools-common - shared data files for GenomeTools
 genometools-dbg - versatile genome analysis toolkit, with debug symbols
 genometools-doc - documentation for GenomeTools
 libgenometools0 - versatile genome analysis library
 libgenometools0-dev - development files for GenomeTools
 python-genometools - Python bindings for genometools
Closes: 728017
Changes: 
 genometools (1.5.1-2) unstable; urgency=low
 .
   * debian/control
  - Add myself to Uploaders
  - cme fix dpkg-control
  - Follow liblua package name transition
Closes: #728017
  - Remove depends from virtual package python-ctypes which is provided
by python
   * provide symbols file
Checksums-Sha1: 
 117f72b98da80399a6cf4acf4675d3f836299923 2029 genometools_1.5.1-2.dsc
 cdbc9a162b94af79e2de5ab558c4741168ac6767 70005 
genometools_1.5.1-2.debian.t

Bug#728084: eztrace gets broken after every new binutils update

[Antonio Ospite]

Package: eztrace
Version: 0.9.1-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

after each new binutils update the eztrace package become uninstallable
because it depends on a previous binutils version.

Maybe this is due to the src dependency on binutils-dev which pulls in
a versioned dependency (with =) on binutils for the binary package, but I ma not
an expert on these matters.

Could you please check the situation?

Thanks,
   Antonio Ospite
   http://ao2.it


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

Kernel: Linux 3.12.0-rc5-ao2 (SMP w/1 CPU core)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages eztrace depends on:
ii  binutils 2.23.90.20130927-1
ii  libc62.17-93
ii  libeztrace0  0.9.1-3
ii  libfxt0  0.2.14-2
ii  libgtg0  0.2+dfsg-1+b1
ii  opari2   1.0.7+dfsg-2

eztrace recommends no packages.

eztrace suggests no packages.

-- no debconf information


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

Bug#725027: marked as done (namazu2: FTBFS after removing alternatives for /usr/bin/wish)

[Debian Bug Tracking System]

Your message dated Mon, 28 Oct 2013 09:34:15 +
with message-id 
and subject line Bug#725027: fixed in namazu2 2.0.21-8.1
has caused the Debian Bug report #725027,
regarding namazu2: FTBFS after removing alternatives for /usr/bin/wish
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.)


-- 
725027: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: namazu2
Version: 2.0.21-8
Severity: normal
Tags: patch

Dear Maintainer,

We plan to drop alternatives for /usr/bin/wish from all tk8.* packages and
provide one fixed symlink shipping in the tk package soon (before jessie
release). Unfortunately this causes namazu2 to FTBFS (see [1] for details).

I'd like to propose a patch which switches build dependency from tk8.4 to tk.

[1] 
http://sgolovan.nes.ru/debian-tcltk/build-failures/namazu2_2.0.21-8.dsc.log.gz

-- System Information:
Debian Release: 7.1
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'stable'), (100, 'unstable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -u namazu2-2.0.21/debian/control namazu2-2.0.21/debian/control
--- namazu2-2.0.21/debian/control
+++ namazu2-2.0.21/debian/control
@@ -2,13 +2,13 @@
 Section: text
 Priority: optional
 Maintainer: NOKUBI Takatsugu 
-Build-Depends: debhelper (>= 4.1.16), perl, kakasi, chasen, libnkf-perl, libfile-mmagic-perl, libtext-kakasi-perl, tk8.4 | wish, lynx, file
+Build-Depends: debhelper (>= 4.1.16), perl, kakasi, chasen, libnkf-perl, libfile-mmagic-perl, libtext-kakasi-perl, tk, lynx, file
 Standards-Version: 3.6.1
 
 Package: namazu2
 Architecture: any
 Depends: ${shlibs:Depends}, namazu2-common, ${misc:Depends}
-Suggests: www-browser, apache, namazu2-index-tools, emacsen-common, wish
+Suggests: www-browser, apache, namazu2-index-tools, emacsen-common, tk
 Conflicts: namazu (<< 2.0), namazu-el, tknamazu
 Provides: namazu
 Replaces: namazu (<< 2.0)
diff -u namazu2-2.0.21/debian/changelog namazu2-2.0.21/debian/changelog
--- namazu2-2.0.21/debian/changelog
+++ namazu2-2.0.21/debian/changelog
@@ -1,3 +1,11 @@
+namazu2 (2.0.21-8.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Switched to tk build-dependency instead of tk8.4 because the package
+needs /usr/bin/wish which soon will be provided only by tk.
+
+ -- Sergei Golovan   Mon, 30 Sep 2013 19:53:52 +0400
+
 namazu2 (2.0.21-8) unstable; urgency=low
 
   * Add pt_BR.po , Closes: #693379
--- End Message ---
--- Begin Message ---
Source: namazu2
Source-Version: 2.0.21-8.1

We believe that the bug you reported is fixed in the latest version of
namazu2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 725...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sergei Golovan  (supplier of updated namazu2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 28 Oct 2013 13:04:26 +0400
Source: namazu2
Binary: namazu2 namazu2-index-tools namazu2-common libnmz7 libnmz7-dev
Architecture: source all amd64
Version: 2.0.21-8.1
Distribution: unstable
Urgency: low
Maintainer: NOKUBI Takatsugu 
Changed-By: Sergei Golovan 
Description: 
 libnmz7- full text search engine - shared library
 libnmz7-dev - full text search engine - header files and static libraries
 namazu2- full text search engine - binary and CGI script
 namazu2-common - full text search engine - documentation
 namazu2-index-tools - full text search engine - index handling tools
Closes: 725027
Changes: 
 namazu2 (2.0.21-8.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Switched to tk build-dependency instead of tk8.4 because the package
 needs /usr/bin/wish which soon will be provided only by tk,
 Closes: #725027
Checksums-Sha1: 
 9ef61e0729ab583d9c52e9feff39cc607f4c0686 1300 namazu2_2.0.21-8.1.dsc
 c06cd30b2565e08760ebbb0669fb9618025c648c 532988 namazu2_2.0.21-8.1.diff.gz
 0cdc73ef266c7e320b645c2b98241bc7e1598682 91590 
namazu2-index-tools_2

Bug#725526: marked as done (getdata: FTBFS: dpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision)

[Debian Bug Tracking System]

Your message dated Mon, 28 Oct 2013 10:04:06 +
with message-id 
and subject line Bug#725526: fixed in getdata 0.2-1
has caused the Debian Bug report #725526,
regarding getdata: FTBFS: dpkg-source: error: can't build with source format 
'3.0 (native)': native package version may not have a revision
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.)


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

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> test -x debian/rules
> rm -f debian/stamp-makefile-build debian/stamp-makefile-install
> /usr/bin/make  -C . CFLAGS="-g -O2 -fstack-protector 
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall" 
> CXXFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
> -Werror=format-security -Wall" CPPFLAGS="-D_FORTIFY_SOURCE=2" 
> LDFLAGS="-Wl,-z,relro"  -k clean
> make[1]: Entering directory `/«PKGBUILDDIR»'
> rm --force getData.1 getData.txt
> make[1]: Leaving directory `/«PKGBUILDDIR»'
> dh_clean 
>  dpkg-source -b getdata-0.1
> dpkg-source: warning: unknown information field 'Dm-Upload-Allowed' in input 
> data in general section of control info file
> dpkg-source: error: can't build with source format '3.0 (native)': native 
> package version may not have a revision
> dpkg-buildpackage: error: dpkg-source -b getdata-0.1 gave error exit status 
> 255
> 
> Build finished at 20131005-1255

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/10/06/getdata_0.1-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: getdata
Source-Version: 0.2-1

We believe that the bug you reported is fixed in the latest version of
getdata, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 725...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Charles Plessy  (supplier of updated getdata package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 28 Oct 2013 18:57:31 +0900
Source: getdata
Binary: getdata
Architecture: source all
Version: 0.2-1
Distribution: unstable
Urgency: low
Maintainer: Steffen Moeller 
Changed-By: Charles Plessy 
Description: 
 getdata- management of external databases
Closes: 725526
Changes: 
 getdata (0.2-1) unstable; urgency=low
 .
   [ Steffen Moeller ]
   * Update of DE405 (URL changed)
 .
   [ Andreas Tille ]
   * debian/control
 - Fixed VCS fields
 .
   [ Charles Plessy ]
   * Normalised with config-model-edit.
   * Conforms with Policy 3.9.5.
   * Using Debhelper 9.
   * Switch back to source format 1.0.  (Closes: #725526).
   * Machine-readable Debian copyright file.
   * Use canonical VCS URLs.
Checksums-Sha1: 
 301782c11f99441e4cfb15d4c182b50c8c2b1785 1892 getdata_0.2-1.dsc
 18bebea7dce482f981ddda143b2a58da18530d01 18559 getdata_0.2.orig.tar.gz
 37cc2f864dcdfaf2f4978acff25a914629eed95e 2523 getdata_0.2-1.diff.gz
 4abc08a07b9b2af75fff77c7dbe51202a57c806f 20162 getdata_0.2-1_all.deb
Checksums-Sha256: 
 d7bd32431343a614284a264f12928912e53ae9865f87a453eba26c0b6c636efd 1892 
getdata_0.2-1.dsc
 888af9d4efce71756b30fdbf3f02ad90f0c253664c7980fc40027604bcf9d4cb 18559 
getdata_0.2.orig.tar.gz
 60e2a45098e3cdd2a09404f18c8a68bea24245f1dbd14bebff64ab6716b32ac1 2523 
getdata_0.2-1.diff.gz
 a0f8168b02a0daf71d56a1aa83541a97f1ab73265d5761e8ceab2117a5e59be0 20162 
getdata_0.2-1_all.deb
Files: 
 47680bf7ef9394c0d6af74ac9543c39a 1892 science optional

Bug#725385: marked as done (spek: FTBFS on s390x: test suite causes segfault)

[Debian Bug Tracking System]

Your message dated Mon, 28 Oct 2013 11:15:20 +0100
with message-id <526e3938.3020...@thykier.net>
and subject line Re: Bug#725385: retry with new libav?
has caused the Debian Bug report #725385,
regarding spek: FTBFS on s390x: test suite causes segfault
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.)


-- 
725385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: spek
Version: 0.8.2-3
X-Debbugs-Cc: debian-s...@lists.debian.org
Severity: serious
Justification: fails to build from source (but built successfully in the
past)

Hi,

The spek test suite crashes, apparently only on s390x, and reproduced on
two different buildds:

> make  check-TESTS
> make[3]: Entering directory 
> `/build/buildd-spek_0.8.2-3-s390x-A7JkU3/spek-0.8.2/tests'
> -
> audio info: 1ch-96000Hz-24bps.flac
> /bin/bash: line 5: 31724 Segmentation fault  ${dir}$tst
> FAIL: test
> ==
> 1 of 1 test failed
> ==
> make[3]: *** [check-TESTS] Error 1

On 04/10/13 22:41, Aurelien Jarno wrote:
> [...] a quick look seems to show the problem is in libav, though I haven't
> looked in details yet.
> 
> #0  0x03ff80002388 in ?? ()
> #1  0x03fffc982312 in ?? () from 
> /usr/lib/s390x-linux-gnu/libavformat.so.54
> #2  0x03fffc987a82 in avformat_open_input () from 
> /usr/lib/s390x-linux-gnu/libavformat.so.54
> #3  0x800057ca in Audio::open (this=this@entry=0x3e7900f, 
> file_name=...) at spek-audio.cc:90
> #4  0x800027e8 in test_file (info=..., name=...) at 
> test-audio-info.cc:38
> #5  operator() (__closure=) at test-audio-info.cc:55
> #6  std::_Function_handler test_audio_info()::__lambda0>::_M_invoke(const std::_Any_data &) 
> (__functor=...) at /usr/include/c++/4.8/functional:2071
> #7  0x80003252 in test_audio_info () at test-audio-info.cc:55
> #8  0x800024e0 in main () at test.cc:28

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org
--- End Message ---
--- Begin Message ---
Alexander Kojevnikov wrote:
> Spek has been removed from s390x (see bug 726149). I guess this bug
> can be closed now.

Yes, taking the liberty of doing so now.

~Niels--- End Message ---

Bug#724166: marked as done (mythtv-status: FTBFS: POD errors)

[Debian Bug Tracking System]

Your message dated Mon, 28 Oct 2013 10:19:23 +
with message-id 
and subject line Bug#724166: fixed in mythtv-status 0.10.4-1
has caused the Debian Bug report #724166,
regarding mythtv-status: 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.)


-- 
724166: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mythtv-status
Version: 0.10.2-3
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):
>  debian/rules build
> pod2man bin/mythtv-status > debian/mythtv-status.1
> bin/mythtv-status around line 1363: Expected text after =item, not a number
> POD document had syntax errors at /usr/bin/pod2man line 71.
> make: *** [build-stamp] Error 255

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/09/22/mythtv-status_0.10.2-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: mythtv-status
Source-Version: 0.10.4-1

We believe that the bug you reported is fixed in the latest version of
mythtv-status, 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.
Andrew Ruthven  (supplier of updated mythtv-status package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 28 Oct 2013 23:03:44 +1300
Source: mythtv-status
Binary: mythtv-status
Architecture: source all
Version: 0.10.4-1
Distribution: unstable
Urgency: low
Maintainer: Andrew Ruthven 
Changed-By: Andrew Ruthven 
Description: 
 mythtv-status - Show the status of a MythTV backend
Closes: 709377 709449 724166
Changes: 
 mythtv-status (0.10.4-1) unstable; urgency=low
 .
   * New upstream release (Closes: #724166, #709377, #709449).
   * Remove an extraneous hypen in our postinst (Cloases: #704436)
 Thank you Francois Marier for the patch.
   * Update standards version to 3.9.4, remove obsolete control field
Checksums-Sha1: 
 80377840b7301ed0299521e982b08924fa4169ab 1273 mythtv-status_0.10.4-1.dsc
 b8aac7c3b41dd5f3b051f0cb1353240fe5123769 37640 mythtv-status_0.10.4.orig.tar.gz
 d0988f6c6e77286a748ab36d714bda35afeae6ee 20052 
mythtv-status_0.10.4-1.debian.tar.gz
 c38d4acd8b6530fca5fb7cd724403146de8051dd 36394 mythtv-status_0.10.4-1_all.deb
Checksums-Sha256: 
 37915807b4237eb48521de63dc137053422f740f07aec75e1480a7f8d1134566 1273 
mythtv-status_0.10.4-1.dsc
 01ace567c9462d42901e86afa78d75bf8c64b94073bf26cb0acf22e2c6e75e98 37640 
mythtv-status_0.10.4.orig.tar.gz
 7c6895a26f34554bd174bd9412c97083855520036e78875943bb1b4ee1b1633c 20052 
mythtv-status_0.10.4-1.debian.tar.gz
 366430f8b34d459cf890a7351c938c499f0421a02a013befed7fd0cb7597d56f 36394 
mythtv-status_0.10.4-1_all.deb
Files: 
 b614b9260af0b68cf999b8fcc56bf933 1273 misc extra mythtv-status_0.10.4-1.dsc
 e53666a10a050e47dd371d0083d81b99 37640 misc extra 
mythtv-status_0.10.4.orig.tar.gz
 e30444cc5d70f6a8225f3c82fdb72c13 20052 misc extra 
mythtv-status_0.10.4-1.debian.tar.gz
 83791d8994e32d71ac14fed9ccdeba7a 36394 misc extra 
mythtv-status_0.10.4-1_all.deb

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

iD8DBQFSbjcQ0obODAxit5ERAjCgAJ4r+eOlDggUy3l+3dxhVFQrq3umogCfbgAE
KjCsuHOPgbVMDRWeIX5y4t4=
=QSC1
-END PGP SIGNATURE End Message ---

Bug#725040: marked as done (timidity: FTBFS after alternatives for /usr/bin/tclsh will be dropped)

[Debian Bug Tracking System]

Your message dated Mon, 28 Oct 2013 10:33:39 +
with message-id 
and subject line Bug#725040: fixed in timidity 2.13.2-40.2
has caused the Debian Bug report #725040,
regarding timidity: FTBFS after alternatives for /usr/bin/tclsh will be dropped
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.)


-- 
725040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: timidity
Version: 2.13.2-40.1
Severity: normal
Tags: patch

Dear Maintainer,

We plan to drop alternatives for /usr/bin/tclsh which means that for example
tcl8.4 will contain only /usr/bin/tclsh8.4 binary and /usr/bin/tclsh will be a
symlink pointing to the current stable tclsh8.* binary.

Unfortunately, this change will cause timidity to FTBFS (see [1] for a build
log). To fix it (and also to get rid of tcl8.4/tk8.4 dependencies as these
packages are to be removed from Debian before jessie release) I'd propose an
attached patch. The nontrivial part of it defined USE_INTERP_RESULT macro
which helps to use deprecated and hidden in 8.6 Tcl_Interp.result field.

[1] 
http://sgolovan.nes.ru/debian-tcltk/build-failures/timidity_2.13.2-40.1.dsc.log.gz

-- System Information:
Debian Release: 7.1
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'stable'), (100, 'unstable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru timidity-2.13.2/debian/changelog timidity-2.13.2/debian/changelog
--- timidity-2.13.2/debian/changelog	2012-10-11 22:11:33.0 +0400
+++ timidity-2.13.2/debian/changelog	2013-09-30 23:16:07.0 +0400
@@ -1,3 +1,11 @@
+timidity (2.13.2-40.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fixed FTBFS caused by dropping /usr/bin/tclsh alternatives.
+  * Build Tcl/Tk interface with Tcl/Tk 8.6.
+
+ -- Sergei Golovan   Mon, 30 Sep 2013 23:13:58 +0400
+
 timidity (2.13.2-40.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru timidity-2.13.2/debian/control timidity-2.13.2/debian/control
--- timidity-2.13.2/debian/control	2011-11-21 20:14:10.0 +0400
+++ timidity-2.13.2/debian/control	2013-09-30 23:12:49.0 +0400
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Geoffrey Thomas 
 Uploaders: Karl Ramm 
-Build-Depends: debhelper (>= 7), libasound2-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386], libaudiofile-dev, libesd0-dev, libjack-dev, libaudio-dev, libvorbis-dev (>= 1.0.0-3), libspeex-dev (>= 1.0), libflac-dev (>= 1.1.4), libncurses-dev, libslang2-dev, libx11-dev, libxext-dev, libxmu-dev, libxpm-dev, libxt-dev, libxaw7-dev, tcl8.4-dev, tk8.4-dev, libgtk2.0-dev, autotools-dev, dpkg-dev (>= 1.16.0)
+Build-Depends: debhelper (>= 7), libasound2-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386], libaudiofile-dev, libesd0-dev, libjack-dev, libaudio-dev, libvorbis-dev (>= 1.0.0-3), libspeex-dev (>= 1.0), libflac-dev (>= 1.1.4), libncurses-dev, libslang2-dev, libx11-dev, libxext-dev, libxmu-dev, libxpm-dev, libxt-dev, libxaw7-dev, tcl-dev, tk-dev, libgtk2.0-dev, autotools-dev, dpkg-dev (>= 1.16.0)
 Standards-Version: 3.9.2
 Homepage: http://timidity.sourceforge.net/
 
diff -Nru timidity-2.13.2/debian/rules timidity-2.13.2/debian/rules
--- timidity-2.13.2/debian/rules	2011-11-21 20:14:10.0 +0400
+++ timidity-2.13.2/debian/rules	2013-09-30 23:21:32.0 +0400
@@ -32,7 +32,7 @@
 DEBUGFLAGS += -O2
 endif
 
-EXTRAFLAGS:=-D_FORTIFY_SOURCE=2 -Wformat -Wformat-security
+EXTRAFLAGS:=-DUSE_INTERP_RESULT -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security
 
 ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS)))
 	CONFFLAGS += --enable-debug
@@ -72,8 +72,8 @@
 	 --sysconfdir=/etc --with-default-path=/etc/timidity \
 	 --with-lispdir=/usr/share/emacs/site-lisp/timidity-el \
 	 --with-x \
-	 --with-tcl-includes=/usr/include/tcl8.4 \
-	 --with-tk-includes=/usr/include/tcl8.4 \
+	 --with-tcl-includes=/usr/include/tcl \
+	 --with-tk-includes=/usr/include/tcl \
 	 --enable-audio=$(audio) \
 	 --with-default-output=default \
 	 --enable-interface=$(interface) \
--- End Message ---
--- Begin Message ---
Source: timidity
Source-Version: 2.13.2-40.2

We believe that the bug you reported is fixed in the latest version of
timidity, 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
hav

Bug#728092: ifupdown: ifup -v displays wpa-password in cleartext

[Thorsten Glaser]

Package: ifupdown
Version: 0.7.45
Severity: grave
Tags: security
Justification: user security hole

I’ve got a configuration snippet in /etc/network/interfaces (chmod 0600,
root-owned) on my work laptop like the following one:

iface tarent-lan inet dhcp
wireless-mode Managed
wireless-essid tarent-lan
wpa-ssid tarent-lan
wpa-key-mgmt WPA-EAP
wpa-identity tglase
wpa-password xxx

This is for “enterprise” WPA, which was introduced here last week.

Now I normally run “sudo ifup -v wlan0=tarent-lan” to activate it,
but ifupdown then displays the wpa-password in cleartext.

This does *not* happen for “regular” WPA, like this (from FOSDEM):

iface bruxelles inet dhcp
wireless-mode Managed
wireless-essid "HOTEL-BEVERLY-HILLS 3"
wpa-ssid "HOTEL-BEVERLY-HILLS 3"
wpa-psk xxx

Please hide this information.

Additionally, it would be very nice if I could write the passwords
(both wpa-psk and wpa-password) into a *separate* file, so access
to /e/n/i needs not to be restricted that much. I’ve not got a good
feeling having my LDAP password be written there in the plaintext…

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

Kernel: Linux 3.11-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh

Versions of packages ifupdown depends on:
ii  file-rc  0.8.16
ii  initscripts  2.88dsf-43
ii  iproute2 3.11.0-1
ii  libc62.17-93
ii  lsb-base 4.1+Debian12

Versions of packages ifupdown recommends:
ii  isc-dhcp-client [dhcp-client]  4.2.4-7

Versions of packages ifupdown suggests:
ii  net-tools  1.60-25
ii  ppp2.4.5-5.2
pn  rdnssd 

-- no debconf information


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

Processed: This is nota non-severe issue

[Debian Bug Tracking System]

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

> severity 714279 serious
Bug #714279 [fontconfig-config] fontconfig-config: Not correct view 
anti-aliasing fonts and incorrect visualization.
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
714279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714279
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#728094: stimfit: FTBFS on kfreebsd but built there in the past

[Niels Thykier]

Package: stimfit
Version: 0.13.2-1
Severity: serious

Hi,

Your package FTBFS on kfreebsd but built there in the past.

~Niels


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

Bug#728092: ifupdown: ifup -v displays wpa-password in cleartext

[Andrew Shadura]

Control: reassign -1 wpasupplicant

Hi, this is a bug in wpa-supplicant's scripts.

Bug#728092: Fwd: Re: Bug#728092: ifupdown: ifup -v displays wpa-password in cleartext

[Andrew Shadura]

Control: reassign -1 wpasupplicant

Hi, this is a bug in wpa-supplicant's scripts.

Processed: Re: Bug#728092: ifupdown: ifup -v displays wpa-password in cleartext

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 wpasupplicant
Bug #728092 [ifupdown] ifupdown: ifup -v displays wpa-password in cleartext
Bug reassigned from package 'ifupdown' to 'wpasupplicant'.
No longer marked as found in versions ifupdown/0.7.45.
Ignoring request to alter fixed versions of bug #728092 to the same values 
previously set

-- 
728092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728092
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: Fwd: Re: Bug#728092: ifupdown: ifup -v displays wpa-password in cleartext

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 wpasupplicant
Bug #728092 [wpasupplicant] ifupdown: ifup -v displays wpa-password in cleartext
Ignoring request to reassign bug #728092 to the same package

-- 
728092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728092
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#728092: ifupdown: ifup -v displays wpa-password in cleartext

[Andrew Shadura]

Hi,

One more thought: wpasupplicant.conf may be what you want.

Bug#725080: marked as done (scsitools: FTBFS with upcoming changes in Tcl/Tk)

[Debian Bug Tracking System]

Your message dated Mon, 28 Oct 2013 11:49:36 +
with message-id 
and subject line Bug#725080: fixed in scsitools 0.12-2.2
has caused the Debian Bug report #725080,
regarding scsitools: FTBFS with upcoming changes in Tcl/Tk
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.)


-- 
725080: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: scsitools
Version: 0.12-2.1
Severity: normal
Tags: patch

Dear Maintainer,

We plan to drop alternatives for /usr/bin/wish from tcl8.* packages, and this
makes scscitools FTBFS (as /usr/bin/wish will be in tk package only, see [1]
for build log). Another goal for jessie is to remove Tcl/Tk 8.4 from Debian.

I'd like to propose a patch which just replaces tk8.4 by tk in dependencies.
Yhe package builds fine, though I didn't have time to test it yet.

[1] 
http://sgolovan.nes.ru/debian-tcltk/build-failures/scsitools_0.12-2.1.dsc.log.gz

-- System Information:
Debian Release: 7.1
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'stable'), (100, 'unstable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru scsitools-0.12/debian/changelog scsitools-0.12/debian/changelog
--- scsitools-0.12/debian/changelog	2011-12-07 20:26:55.0 +0400
+++ scsitools-0.12/debian/changelog	2013-10-01 12:57:57.0 +0400
@@ -1,3 +1,10 @@
+scsitools (0.12-2.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Replaced tk8.4 by tk in dependencies to get rid of Tcl/Tk 8.4.
+
+ -- Sergei Golovan   Tue, 01 Oct 2013 12:57:22 +0400
+
 scsitools (0.12-2.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru scsitools-0.12/debian/control scsitools-0.12/debian/control
--- scsitools-0.12/debian/control	2011-01-11 00:53:41.0 +0300
+++ scsitools-0.12/debian/control	2013-10-01 12:56:07.0 +0400
@@ -3,13 +3,13 @@
 Priority: optional
 Maintainer: Eric Delaunay 
 Standards-Version: 3.9.1
-Build-Depends: tk8.4, debhelper (>= 7), quilt (>= 0.46-7~)
+Build-Depends: tk, debhelper (>= 7), quilt (>= 0.46-7~)
 
 Package: scsitools
 Architecture: any
 Depends: ${shlibs:Depends}, util-linux (>= 2.11b-3), sg3-utils (>= 1.24), ${misc:Depends}
 Conflicts: hwtools (<< 0.6)
-Recommends: tk8.4 | wish
+Recommends: tk
 Description: Collection of tools for SCSI hardware management
  This package is a collection of tools for manipulating SCSI hardware:
  .
--- End Message ---
--- Begin Message ---
Source: scsitools
Source-Version: 0.12-2.2

We believe that the bug you reported is fixed in the latest version of
scsitools, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 725...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sergei Golovan  (supplier of updated scsitools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 28 Oct 2013 15:29:51 +0400
Source: scsitools
Binary: scsitools
Architecture: source amd64
Version: 0.12-2.2
Distribution: unstable
Urgency: low
Maintainer: Eric Delaunay 
Changed-By: Sergei Golovan 
Description: 
 scsitools  - Collection of tools for SCSI hardware management
Closes: 725080
Changes: 
 scsitools (0.12-2.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Replaced tk8.4 by tk in dependencies to get rid of Tcl/Tk 8.4.
 (Closes: #725080)
Checksums-Sha1: 
 a6e41b7b34afae10b61e97b70bf94ef26e60464d 1054 scsitools_0.12-2.2.dsc
 5f0a55b4d69bd39a2daf63f3d514a90bd9547df5 6 scsitools_0.12-2.2.debian.tar.gz
 f27a845fc45597f038c5e05261e26460b1908b31 115882 scsitools_0.12-2.2_amd64.deb
Checksums-Sha256: 
 adb14c61a5eb8c2e50dab25b5f63170e36ef19958ff06eec053d3ce1bdd75063 1054 
scsitools_0.12-2.2.dsc
 5257fa67765e520883dbd780328a16a3683dc97a3fd1842cd12379afa4bb3f3a 6 
scsitools_0.12-2.2.debian.tar.gz
 8e3408343ba8bf912329bb9c277e68a2b30b426bd6adebdd44c0aa7323c47c98 115882 
scsitools_0.12-2.2_amd64.deb
Files: 
 90ef685fdfa1a89fb0a47bec8658a778 1054 utils optional scsitools_0.12-2.2

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

[Ferenc Wagner]

Ferenc Wagner  writes:

> Bernd Zeimetz  writes:
>
>>> I'm preparing a new upload of sblim-wbemcli.  Shall I rename the
>>> contained wbemcli binary, or do you still plan letting me use that
>>> name?
>>
>> given the low popcon and pywebem not being devleoped by upstream
>> anymore, I think it would be okay for you to take the name, if we find
>> a proper way to let people know about it. I guess pywbem could ship
>> wbemcli.py instead, then it would be obvious.
>
> I agree.
>
>> What would you think about a debconf notice which is displayed only to
>> those who have python-wbem installed? or something like that?
>> Do you have better ideas?
>
> I could most certainly add a notice like that.  However, this is
> actually a change in pywbem, thus I feel like it should be documented
> there.  I also think a NEWS entry would be more than enough, as the
> current wbemcli binary in pywbem looks more like an example than a
> readily usable utility, so I don't expect a wide affected user base.

Hi Bernd,

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


-- 
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#727758: cups segfaults in libdbus

[Debian Bug Tracking System]

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

> reassign 727758 cups
Bug #727758 [libdbus-1-3] cups segfaults in libdbus
Bug reassigned from package 'libdbus-1-3' to 'cups'.
No longer marked as found in versions dbus/1.6.16-1.
Ignoring request to alter fixed versions of bug #727758 to the same values 
previously set
> affects 727758 + libdbus-1-3
Bug #727758 [cups] cups segfaults in libdbus
Added indication that 727758 affects libdbus-1-3
> thanks
Stopping processing here.

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

[Simon McVittie]

reassign 727758 cups
affects 727758 + libdbus-1-3
thanks

On Sat, 26 Oct 2013 at 11:37:44 +0200, Michael Meskes wrote:
> Most of the times cups comes up I get this:
> 
> Oct 25 20:27:57 aragorn kernel: [  389.581166] cupsd[2937]: segfault at 8 ip 
> 7faeb7c98cd0 sp 7fff18af7148 error 4 in 
> libdbus-1.so.3.7.5[7faeb7c72000+45000]

Having thought about this some more, I'm going to reassign this to cups.
I'm quite prepared for it to be reassigned back if it turns out to be a
dbus bug, but we can't know that - or how to fix it - without more
information, and the cups maintainers are likely to know much more about
how to get that information than I do.

Please reply to this bug with the result of "reportbug --template cups"
so the cups package's full dependencies, and any other useful info
from reportbug scripts, are visible.

If an executable is crashing in a way that might implicate a library, it's
likely to be best to report it initially as a bug in the executable (ideally
with a cc to the library's @packages.debian.org address), unless you have a
minimal test-case demonstrating that it is in fact a bug in the library.
That way, the bug report already contains the executable's full dependencies
and other relevant information from its bug scripts, and it'll be triaged
by someone who knows how to get debug information from that particular
executable.

The proposed HOWTO_BUGREPORT documents in

might explain how you can provide enough information for this crash
to be diagnosed and fixed.

>From a quick look at the cups bug list, your crash might be related to one
of these, for instance:


(crash in libdbus possibly caused by cups passing a dangling string pointer
to libdbus functions, which also has some notes about how to get a
backtrace or core dump)


(segfault in libavahi-common (which uses libdbus), closed because
unreproducible)

Regards,
S


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

Bug#727758: cups segfaults in libdbus

[Michael Meskes]

On Sat, Oct 26, 2013 at 11:40:20PM +0100, Simon McVittie wrote:
> "thread apply all bt" backtrace from cupsd, please? Sorry, I don't know

Will send as soon as I'm on the system again. 

> Why is this RC severity? If cupsd links libdbus, then almost by
> definition it isn't "breaks unrelated software"...

Well, you're right, kind of. I think this bug "makes the package in question
unusable". However, the package is cups that you moved the bug to anyway. 

Michael

-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
Jabber: michael.meskes at gmail dot com
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL


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

Bug#727805: rjava: Depends on openjdk-6 which is going away

[Niels Thykier]

On 2013-10-27 22:22, Dirk Eddelbuettel wrote:
> 
> On 27 October 2013 at 08:10, Niels Thykier wrote:
> | Package: rjava
> | Version: 0.9-4-1
> | Severity: serious
> | 
> | Hi,
> | 
> | rjava Depends on openjdk-6-jre, but openjdk-6 is going away.  Please
> | adjust your dependency to either use default-jre, openjdk-7-jre or
> | some other java implementation.
> 
> rjava (or "rJava" upstream) is an interface package which uses what R
> itself got compiled with.  So I need the relevant jdk for R.
> 
> jdk-7 should work as that has been working on Ubuntu for a while.
> 

Okay.  :)

> | NB: openjdk-7 is not available on mipsel, but rjava has been built
> | there.  If you change your dependency to openjdk-7-jre, you probably
> | have to get rjava/mipsel removed from unstable.  In that case, please
> | ensure the package is not built on mipsel and then request the ftp
> | masters to remove it from unstable.
> 
> What do we do with R there?  Build without Java support?  Could do...
> 
> Dirk
> 

I would assume so; it wouldn't be any different than mips AFAICT.

~Niels


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

Bug#728106: libreoffice-writer: The "Save" dialog doesn't appear when quitting with two windows open on different desktops

[Vincent Lefevre]

Package: libreoffice-writer
Version: 1:4.1.2-1
Severity: grave
Justification: causes non-serious data loss

To reproduce the problem:

0. Make sure you have a configuration with different desktops.
   With my window manager fvwm, I use:
 DeskTopSize 2x2
   and the FvwmPager module. Just in case, I've attached my fvwm
   configuration, where fvwm is run with:
 fvwm2 -cmd "ModuleSynchronous FvwmM4 -lock $HOME/etc/fvwm2rc.m4"
1. Open a first file with "libreoffice file1.odt".
2. From a different desktop (this is important to reproduce the bug!),
   open a second file with: "libreoffice file2.odt".
3. Modify the first file (file1.odt), but do not save it.
4. In the file2.odt window, type Ctrl-Q.

The effect is that LibreOffice switches to the first desktop, where
the file1.odt window is, but I can't do anything with this window.
In the list of windows, I can see a "Save docum[...]" window, but
this window doesn't appear. Even if I iconify it and reopen it from
the list of windows, it still doesn't appear (just in case it was
below some other window).

The only thing I can do is to destroy both windows via fvwm. Then,
if I reopen file1.odt, LibreOffice proposes me to start recovery,
which I accept. It says "Successfully recovered", but the changes
have been lost!

As described, this bug is always reproducible here.

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

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

Versions of packages libreoffice-writer depends on:
ii  libc6  2.17-93
ii  libgcc11:4.8.2-1
ii  libicu48   4.8.1.1-13+nmu1
ii  libmwaw-0.1-1  0.1.11-1
ii  libodfgen-0.0-00.0.2-1
ii  libreoffice-base-core  1:4.1.2-1
ii  libreoffice-core   1:4.1.2-1
ii  libstdc++6 4.8.2-1
ii  libwpd-0.9-9   0.9.9-1
ii  libwpg-0.2-2   0.2.1-1
ii  libwps-0.2-2   0.2.9-2
ii  libxml22.9.1+dfsg1-3
ii  uno-libs3  4.1.2-1
ii  ure4.1.2-1
ii  zlib1g 1:1.2.8.dfsg-1

Versions of packages libreoffice-writer recommends:
ii  default-jre [java5-runtime]1:1.7-49
ii  gcj-4.6-jre [java5-runtime]4.6.4-2
ii  gcj-4.7-jre [java5-runtime]4.7.3-2
ii  gcj-4.8-jre [java5-runtime]4.8.2-1
ii  gcj-jre [java5-runtime]4:4.8.1-3
ii  libreoffice-java-common1:4.1.2-1
ii  libreoffice-math   1:4.1.2-1
ii  openjdk-7-jre [java5-runtime]  7u25-2.3.12-4

Versions of packages libreoffice-writer suggests:
ii  libreoffice-base  1:4.1.2-1
pn  libreoffice-gcj   

Versions of packages libreoffice-core depends on:
ii  fontconfig  2.10.2-2
ii  fonts-opensymbol2:102.3+LibO4.1.2-1
ii  libatk1.0-0 2.10.0-2
ii  libboost-date-time1.54.01.54.0-3
ii  libc6   2.17-93
ii  libcairo2   1.12.16-2
ii  libclucene-contribs12.3.3.4-4
ii  libclucene-core12.3.3.4-4
ii  libcmis-0.3-3   0.3.1-3
ii  libcups21.6.3-1
ii  libcurl3-gnutls 7.33.0-1
ii  libdbus-1-3 1.6.16-1
ii  libdbus-glib-1-20.100.2-1
ii  libexpat1   2.1.0-4
ii  libexttextcat-2.0-0 3.4.0-4
ii  libfontconfig1  2.10.2-2
ii  libfreetype62.4.9-1.1
ii  libgcc1 1:4.8.2-1
ii  libgdk-pixbuf2.0-0  2.28.2-1
ii  libglib2.0-02.36.4-1
ii  libgraphite2-3  1.2.3-1
ii  libgstreamer-plugins-base1.0-0  1.2.0-1
ii  libgstreamer1.0-0   1.2.0-1
ii  libgtk2.0-0 2.24.21-1
ii  libharfbuzz-icu00.9.19-1
ii  libharfbuzz0a   0.9.19-1
ii  libhunspell-1.3-0   1.3.2-4
ii  libhyphen0  2.8.6-3
ii  libice6 2:1.0.8-2
ii  libicu484.8.1.1-13+nmu1
ii  libjpeg88d-1
ii  liblangtag1 0.5.1-2
ii  liblcms2-2  2.2+git20110628-2.3
ii  libldap-2.4-2   2.4.31-1+nmu2+b1
ii  libmythes-1.2-0 2:1.2.2-1
ii  libneon27-gnutls0.30.0-1
ii  libnspr42:4.10.1-1
ii  libnss3 2:3.15.2-1
ii  libnss3-1d  2:3.15.2-1
ii  libpango-1.0-0  1.32.5-5+b1
ii  libpangocairo-1.0-0 1.32.5-5+b1
ii  libpangoft2-1.0-0   1.32.5-5+b1
ii  libpng12-0  1.2.49-5
ii  librdf0 1.0.16-1
ii  libreoffice-common  1:4.1.2-1
ii  libsm6  2:1.2.1-2
ii  libs

Bug#727805: rjava: Depends on openjdk-6 which is going away

[Dirk Eddelbuettel]

Hi Niels,

On 28 October 2013 at 14:32, Niels Thykier wrote:
| On 2013-10-27 22:22, Dirk Eddelbuettel wrote:
| > jdk-7 should work as that has been working on Ubuntu for a while.
| > 
| 
| Okay.  :)
| 
| > | NB: openjdk-7 is not available on mipsel, but rjava has been built
| > | there.  If you change your dependency to openjdk-7-jre, you probably
| > | have to get rjava/mipsel removed from unstable.  In that case, please
| > | ensure the package is not built on mipsel and then request the ftp
| > | masters to remove it from unstable.
| > 
| > What do we do with R there?  Build without Java support?  Could do...
| > 
| > Dirk
| > 
| 
| I would assume so; it wouldn't be any different than mips AFAICT.

And R itself already has (and had for ages) this in
debian/control::Build-Depends

default-jdk [!arm !hppa !kfreebsd-i386 !kfreebsd-amd64 !hurd-i386 !mips]

SO I guess we really only need to trigger a rebuild for rJava -- and possibly
tell the mips builders to ignore this package as it also has

default-jdk [!arm !hppa !kfreebsd-i386 !kfreebsd-amd64 !hurd-i386 !mips]

but it should really be skipped on all of these/

Can you remind how I do that again?

Dirk

-- 
Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com


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

Bug#728106: libreoffice-writer: The "Save" dialog doesn't appear when quitting with two windows open on different desktops

[Rene Engelhard]

reassign 728106 libreoffice
severity 728106 important
tag 728106 + moreinfo
thanks

Hi,

On Mon, Oct 28, 2013 at 02:46:55PM +0100, Vincent Lefevre wrote:
> Package: libreoffice-writer

Nah, Save is shared between all of them..

> Version: 1:4.1.2-1
> Severity: grave
> Justification: causes non-serious data loss

I assume this is not new in 4.1.2 and affects testing, too?
I don't think this should block transition of this to testing.

> To reproduce the problem:
> 
> 1. Open a first file with "libreoffice file1.odt".
> 2. From a different desktop (this is important to reproduce the bug!),
>open a second file with: "libreoffice file2.odt".
> 3. Modify the first file (file1.odt), but do not save it.
> 4. In the file2.odt window, type Ctrl-Q.
> 
> The effect is that LibreOffice switches to the first desktop, where
> the file1.odt window is, but I can't do anything with this window.
> In the list of windows, I can see a "Save docum[...]" window, but
> this window doesn't appear. Even if I iconify it and reopen it from
> the list of windows, it still doesn't appear (just in case it was
> below some other window).

And you are *sure* this isn't fvwm only? (And/or a fvwm bug?)

If this only happens in fvwm (only knowledged people will use it)
I wouldn't count this as grave (i.e. if it doesn't work in GNOME/KDE/XFCE/...)
-> not grave as it doesn't affect majority of people.

Regards,

Rene


-- 
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#728106: libreoffice-writer: The "Save" dialog doesn't appear when quitting with two windows open on different desktops

[Debian Bug Tracking System]

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

> reassign 728106 libreoffice
Bug #728106 [libreoffice-writer] libreoffice-writer: The "Save" dialog doesn't 
appear when quitting with two windows open on different desktops
Bug reassigned from package 'libreoffice-writer' to 'libreoffice'.
No longer marked as found in versions libreoffice/1:4.1.2-1.
Ignoring request to alter fixed versions of bug #728106 to the same values 
previously set
> severity 728106 important
Bug #728106 [libreoffice] libreoffice-writer: The "Save" dialog doesn't appear 
when quitting with two windows open on different desktops
Severity set to 'important' from 'grave'
> tag 728106 + moreinfo
Bug #728106 [libreoffice] libreoffice-writer: The "Save" dialog doesn't appear 
when quitting with two windows open on different desktops
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
728106: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728106
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#727819: [icedove] found workaround

[Lorenz Wenner]

Package: icedove
Version: 17.0.9-2

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

i just found this simple work around, which i would liketo share with
you. In case icedoce is going mad, just tell it to work offline and you
are done. Until next time it goes mad...

--- System information. ---
Architecture: i386
Kernel: Linux 3.11-rc7-486

Debian Release: jessie/sid
800 testing www.deb-multimedia.org
800 testing security.debian.org
800 testing ftp.de.debian.org
750 unstable ftp.de.debian.org
250 experimental ftp.de.debian.org

--- Package information. ---
Depends (Version) | Installed
===-+-===
fontconfig | 2.10.2-2
psmisc | 22.20-1
debianutils (>= 1.16) | 4.4
libasound2 (>= 1.0.16) | 1.0.27.2-3
libatk1.0-0 (>= 1.12.4) | 2.10.0-2
libc6 (>= 2.15) | 2.17-93
libcairo2 (>= 1.10.2-2~) | 1.12.16-2
libdbus-1-3 (>= 1.0.2) | 1.6.16-1
libdbus-glib-1-2 (>= 0.78) | 0.100.2-1
libevent-2.0-5 (>= 2.0.10-stable) | 2.0.21-stable-1
libffi6 (>= 3.0.4) | 3.0.13-4
libfontconfig1 (>= 2.10.0) | 2.10.2-2
libfreetype6 (>= 2.3.9) | 2.4.9-1.1
libgcc1 (>= 1:4.1.1) | 1:4.8.1-10
libgdk-pixbuf2.0-0 (>= 2.22.0) | 2.28.2-1
libglib2.0-0 (>= 2.22.0) | 2.36.4-1
libgtk2.0-0 (>= 2.24.0) | 2.24.21-1
libhunspell-1.3-0 | 1.3.2-4
libjpeg8 (>= 8c) | 8d-1
libnspr4 (>= 2:4.9.2) | 2:4.10-1
libnss3 (>= 2:3.13.4-2~) | 2:3.15.2-1
OR libnss3-1d (>= 3.13.2) | 2:3.15.2-1
libpango-1.0-0 (>= 1.14.0) | 1.32.5-5+b1
libpangocairo-1.0-0 (>= 1.14.0) | 1.32.5-5+b1
libpangoft2-1.0-0 (>= 1.14.0) | 1.32.5-5+b1
libpixman-1-0 (>= 0.18.0) | 0.30.2-1
libsqlite3-0 (>= 3.7.4) | 3.8.0.2-1
libstartup-notification0 (>= 0.8) | 0.12-3
libstdc++6 (>= 4.6) | 4.8.1-10
libvpx1 (>= 1.0.0) | 1.2.0-2
libx11-6 | 2:1.6.2-1
libxext6 | 2:1.3.2-1
libxrender1 | 1:0.9.8-1
libxt6 | 1:1.1.4-1
zlib1g (>= 1:1.2.0) | 1:1.2.8.dfsg-1


Recommends (Version) | Installed
==-+-===
myspell-en-us |
OR hunspell-dictionary |
OR myspell-dictionary |


Suggests (Version) | Installed
===-+-===
fonts-lyx | 2.0.6-1
libgssapi-krb5-2 | 1.11.3+dfsg-3


0x0C8DE883.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Bug#727805: rjava: Depends on openjdk-6 which is going away

[Niels Thykier]

On 2013-10-28 15:01, Dirk Eddelbuettel wrote:
> 
> Hi Niels,
> 
> On 28 October 2013 at 14:32, Niels Thykier wrote:
> | On 2013-10-27 22:22, Dirk Eddelbuettel wrote:
> | > jdk-7 should work as that has been working on Ubuntu for a while.
> | > 
> | 
> | Okay.  :)
> | 
> | > | NB: openjdk-7 is not available on mipsel, but rjava has been built
> | > | there.  If you change your dependency to openjdk-7-jre, you probably
> | > | have to get rjava/mipsel removed from unstable.  In that case, please
> | > | ensure the package is not built on mipsel and then request the ftp
> | > | masters to remove it from unstable.
> | > 
> | > What do we do with R there?  Build without Java support?  Could do...
> | > 
> | > Dirk
> | > 
> | 
> | I would assume so; it wouldn't be any different than mips AFAICT.
> 
> And R itself already has (and had for ages) this in
> debian/control::Build-Depends
> 
> default-jdk [!arm !hppa !kfreebsd-i386 !kfreebsd-amd64 !hurd-i386 !mips]
> 

You would be missing mipsel then. :)

> SO I guess we really only need to trigger a rebuild for rJava -- and possibly
> tell the mips builders to ignore this package as it also has
> 

s/mips/mipsel/

> default-jdk [!arm !hppa !kfreebsd-i386 !kfreebsd-amd64 !hurd-i386 !mips]
> 
> but it should really be skipped on all of these/
> 
> Can you remind how I do that again?
> 
> Dirk
> 

Set the Architecture field to list only acceptable architectures should
do.  From there, the buildds should mark it as "Auto-Not-For-Us" and
ignore it.  Mind you, you still have to file a removal bug for binaries
on architectures that (as a consequence) will no longer be built.
  An alternative is to Build-Depend on a package that is available on
exactly the architectures your package supports[1].  Again, it would
still need the removal bug, but that is another possibility.

~Niels

[1] This makes for e.g. Build-Depends on an -dev package only available
on certain architectures.  I am not certain that it makes sense in this
particular case.


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

Bug#727009: FTBFS on kfreebsd-i386: FAIL: test-pangocairo-threads

[Emilio Pozuelo Monfort]

On 21/10/13 15:54, Michael Biebl wrote:
> Source: pango1.0
> Version: 1.36.0-1
> Severity: serious
> User: debian-...@lists.debian.org
> 
> pango1.0 FTBFS on kfreebsd-i386 when executing the test-suite:
> 
> /«PKGBUILDDIR»/./test-driver: line 95: 41714 Trace/breakpoint trap   "$@" > 
> $log_file 2>&1
> FAIL: test-pangocairo-threads

The test is failing with

(process:7450): GLib-ERROR **: creating thread '37': Error creating thread:
Resource temporarily unavailable

The test is trying to create 100 threads, but pthread_create returns EAGAIN
because it hits some limit, which makes g_thread_new() abort (as stated in the
docs, g_thread_try_new() wouldn't abort but return NULL).

The question is, why are we hitting the limit so soon here?

ulimit on fischer (where I'm debugging this) reports:

max user processes  (-u) 5547

so I doubt we're hitting the maximum number of threads here. Perhaps the test
should use g_thread_try_new() and retry a limited number of times on EAGAIN.

Regards,
Emilio


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

Processed: notfound 724713 in jython/2.5.2-2

[Debian Bug Tracking System]

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

> # The BTS is confused, best solution I got for this case it to remove the 
> found version
> notfound 724713 jython/2.5.2-2
Bug #724713 {Done: Emmanuel Bourg } [jython] jython: Can not 
install
No longer marked as found in versions jython/2.5.2-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
724713: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724713
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#725244: marked as done (cableswig: Package build-depends on deprecated Tcl 8.4)

[Debian Bug Tracking System]

Your message dated Mon, 28 Oct 2013 15:19:06 +
with message-id 
and subject line Bug#725244: fixed in cableswig 0.1.0+cvs20111009-1.1
has caused the Debian Bug report #725244,
regarding cableswig: Package build-depends on deprecated Tcl 8.4
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.)


-- 
725244: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725244
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cableswig
Version: 0.1.0+cvs20111009-1
Severity: normal
Tags: patch

Dear Maintainer,

We plan to drop Tcl/Tk 8.4 from Debian archive before jessie release. The
cableswig package currecntly build-depend on tcl8.4-dev, though just replacing
it by tcl-dev is fine. It Builds fine and I can't find any difference between
binary packages with tcl8.4-dev and tcl-dev dependencies.

I've prepared a small patch which addresses this bug.

-- System Information:
Debian Release: 7.1
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'stable'), (100, 'unstable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -u cableswig-0.1.0+cvs20111009/debian/changelog cableswig-0.1.0+cvs20111009/debian/changelog
--- cableswig-0.1.0+cvs20111009/debian/changelog
+++ cableswig-0.1.0+cvs20111009/debian/changelog
@@ -1,3 +1,10 @@
+cableswig (0.1.0+cvs20111009-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Replaced tcl8.4-dev by tcl-dev in build-dependencies.
+
+ -- Sergei Golovan   Thu, 03 Oct 2013 09:25:11 +0400
+
 cableswig (0.1.0+cvs20111009-1) unstable; urgency=low
 
   * New upstream, pulled from CVS HEAD.
diff -u cableswig-0.1.0+cvs20111009/debian/control cableswig-0.1.0+cvs20111009/debian/control
--- cableswig-0.1.0+cvs20111009/debian/control
+++ cableswig-0.1.0+cvs20111009/debian/control
@@ -3,7 +3,7 @@
 Section: devel
 Priority: optional
 Maintainer: Steve M. Robbins 
-Build-Depends: debhelper (>= 8), cmake (>= 2.6.3), gccxml, python-dev (>= 2.3), tcl8.4-dev (>= 8.4.11)
+Build-Depends: debhelper (>= 8), cmake (>= 2.6.3), gccxml, python-dev (>= 2.3), tcl-dev
 Standards-Version: 3.9.2
 
 Package: cableswig
--- End Message ---
--- Begin Message ---
Source: cableswig
Source-Version: 0.1.0+cvs20111009-1.1

We believe that the bug you reported is fixed in the latest version of
cableswig, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 725...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sergei Golovan  (supplier of updated cableswig package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 28 Oct 2013 17:41:43 +0400
Source: cableswig
Binary: cableswig libcableswig-dev
Architecture: source amd64
Version: 0.1.0+cvs20111009-1.1
Distribution: unstable
Urgency: low
Maintainer: Steve M. Robbins 
Changed-By: Sergei Golovan 
Description: 
 cableswig  - Generate wrappers for Python and Tcl from C++ code
 libcableswig-dev - Libraries for writing a C++ wrapper generator
Closes: 725244
Changes: 
 cableswig (0.1.0+cvs20111009-1.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Replaced tcl8.4-dev by tcl-dev in build-dependencies. Closes: #725244.
Checksums-Sha1: 
 051184730f3268416feb7747403464da9a37200d 1253 
cableswig_0.1.0+cvs20111009-1.1.dsc
 ad351f8a1ee35daa92b6b1118b3d2e85a268dfe2 7172 
cableswig_0.1.0+cvs20111009-1.1.diff.gz
 e51a6eeea9515a0d4178f633bb41d6b68df6631b 561856 
cableswig_0.1.0+cvs20111009-1.1_amd64.deb
 ff574a169d8858727e6c38544041f151dcdffaf3 139468 
libcableswig-dev_0.1.0+cvs20111009-1.1_amd64.deb
Checksums-Sha256: 
 dfd840f0d41f60d3265b7148567a47e6ab4f6ed92eb3eba1c35cc568b84e63f5 1253 
cableswig_0.1.0+cvs20111009-1.1.dsc
 50995398d13da8c36aebe94b3436e44e1b4402672e6f242a1b2dc99e11ebf2ec 7172 
cableswig_0.1.0+cvs20111009-1.1.diff.gz
 2a5c4d5294feb04a63e4082d44fdca242e8083d7404ae5f7053a5f0df1835f77 561856 
cableswig_0.1.0+cvs20111009-1.1_amd64.deb
 14d3691bf3e7b58999b47d82755e15c0ef83b3cbfb523165aac87b0c1a91d4de 139468 
libcableswig-dev_0.1.0+cvs20111009-1.1_amd64.deb
Files: 
 ca6

Bug#727779: libspandsp2: asterisk segfaults because of libspandsp

[Thomas Rechberger]

its working now, asterisk was probably not correct compiled or it 
affects only anonymous calls. Bug can be closed.



--
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#725057: vlc plugin linking issue (seems to affect only live systems)

[Debian Bug Tracking System]

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

> tags 725057 - patch
Bug #725057 [vlc] vlc plugin linking issue (seems to affect only live systems)
Removed tag(s) patch.
> tags 725057 + moreinfo
Bug #725057 [vlc] vlc plugin linking issue (seems to affect only live systems)
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
725057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725057
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#725057: vlc plugin linking issue (seems to affect only live systems)

[Rémi Denis-Courmont]

tags 725057 - patch
tags 725057 + moreinfo
thanks

Le lundi 30 septembre 2013 22:17:11 boacs a écrit :
> Package: vlc
> Version: 2.0.8-1
> Severity: serious
> Tags: patch
> Justification: Policy 2.5
> 
> Dear Maintainer,
> 
> In vlc versions before 2.0.3-5 , there was a linking issue which immediately
> crashed vlc on a live system, saying, "[0x220e108] main libvlc error: No
> plugins found! Check your VLC installation."
> 
> One workaround I've found out is linking:
> "VLC_PLUGIN_PATH=/usr/lib/vlc/plugins/ vlc"

Meh? That is the default value for VLC_PLUGIN_PATH... And I cannot reproduce 
the problem. Can you please post the verbose log (vlc -vv) ?

-- 
Rémi Denis-Courmont
http://www.remlab.net/


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

Bug#719736: marked as done (openvswitch: build FTBFS "make check" failures on most archs)

[Debian Bug Tracking System]

Your message dated Mon, 28 Oct 2013 16:03:51 +
with message-id 
and subject line Bug#719736: fixed in openvswitch 1.9.3+git20131028-1
has caused the Debian Bug report #719736,
regarding openvswitch: build FTBFS "make check" failures on most archs
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.)


-- 
719736: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openvswitch
Version: 1.9.2+git20130813
Severity: grave

I'm filing this bug to track the various "make check" failures that
caused the 1.9.2+git20130813 build to fail on most archs.  I need to
spend some time tracking down the exact causes, and this bug report
seems to be a reasonable place to put some of that.

There seem to be a couple of classes of problems, see sections below.

--

 Most of the amd64 test failures, at
https://buildd.debian.org/status/fetch.php?pkg=openvswitch&arch=amd64&ver=1.9.2%2Bgit20130813-1&stamp=1376461705
exemplify one of those.  These amd64 failures involve Python and most
of them involve the unixctl client or server:

 288: unixctl-py.at:6unixctl ovs-vswitchd exit - Python
 289: unixctl-py.at:17   unixctl ovs-vswitchd help - Python
 290: unixctl-py.at:32   unixctl ovs-vswitchd arguments - Python
 292: unixctl-py.at:91   unixctl server - Python
 1152: ovs-monitor-ipsec.at:3 ovs-monitor-ipsec
 1153: ovs-xapi-sync.at:3 ovs-xapi-sync
 1172: vlog.at:106vlog - vlog/reopen - Python
 1173: vlog.at:135vlog - vlog/reopen without log file - Python
 1174: vlog.at:153vlog - vlog/reopen can't reopen log file - Python
 1175: vlog.at:185vlog - vlog/set and vlog/list - Python

Here's an example failure detail, for test 288:

../../tests/unixctl-py.at:8: ovs-vsctl -- add-br br0 -- set bridge br0 
datapath-type=dummy other-config:datapath-id=fedcba9876543210 
other-config:hwaddr=aa:55:aa:55:00:00 fail-mode=secure --  
../../tests/unixctl-py.at:10: $PYTHON $srcdir/appctl.py --timeout 20 -t 
ovs-vswitchd exit
--- /dev/null   2013-04-04 14:58:34.0 +
+++ 
/??BUILDDIR??/openvswitch-1.9.2+git20130813/_debian/tests/testsuite.dir/at-groups/288/stderr
2013-08-14 06:27:32.094459992 +
@@ -0,0 +1,15 @@
+2013-08-14T06:27:32Z|0|unixctl_client|WARN|failed to connect to 
/??BUILDDIR??/openvswitch-1.9.2+git20130813/_debian/tests/testsuite.dir/0288/ovs-vswitchd.11263.ctl
+Traceback (most recent call last):
+  File "../../../../tests/appctl.py", line 75, in 
+main()
+  File "../../../../tests/appctl.py", line 59, in main
+client = connect_to_target(target)
+  File "../../../../tests/appctl.py", line 35, in connect_to_target
+ovs.util.ovs_fatal(error, "cannot connect to \"%s\"" % socket_name)
+  File "/??BUILDDIR??/openvswitch-1.9.2+git20130813/python/ovs/util.py", 
line 92, in ovs_fatal
+ovs_error(*args, **kwargs)
+  File "/??BUILDDIR??/openvswitch-1.9.2+git20130813/python/ovs/util.py", 
line 76, in ovs_error
+err_msg += " (%s)" % ovs_retval_to_string(err_no)
+  File "/??BUILDDIR??/openvswitch-1.9.2+git20130813/python/ovs/util.py", 
line 60, in ovs_retval_to_string
+return os.strerror(retval)
+TypeError: an integer is required
../../tests/unixctl-py.at:10: exit code was 1, expected 0

--

sparc has these failures but others too, see
https://buildd.debian.org/status/fetch.php?pkg=openvswitch&arch=sparc&ver=1.9.2%2Bgit20130813-1&stamp=1376471499:

216: learning action - learn refreshes hard_age  FAILED (learn.at:138)
217: learning action - TCPv4 port learning   FAILED (learn.at:199)
509: ofproto-dpif - dec_ttl  FAILED (ofproto-dpif.at:80)
514: ofproto-dpif - controller   FAILED 
(ofproto-dpif.at:263)
526: ofproto-dpif - NetFlow flow expiration  FAILED 
(ofproto-dpif.at:969)
527: ofproto-dpif - NetFlow active expirationFAILED 
(ofproto-dpif.at:1019)
528: idle_age and hard_age increase over timeFAILED 
(ofproto-dpif.at:1082)

plus others, such as 501, that hang and cause the build to time out.

A little work with gdb shows that 501 failed due to misaligned data
access in a "packet out" OpenFlow command in packet_set_ipv4().  It
looks like handle_packet_out() in ofproto.c needs to properly align
the L3 header.  It seems likely that the other failures are for the
same or related reasons.
--- End Message ---
---

Bug#728117: php5-apcu: breaks Mediawiki DB upgrade script

[Thorsten Glaser]

Package: php5-apcu
Version: 4.0.2-2
Severity: serious
Justification: breaks other software

When running Mediawiki with the APC user cache enabled,
and trying to run the Mediawiki DB upgrade script, which
previously worked, it fails with:

CACHE_ACCEL requested but no suitable object cache is present. You may want to 
install APC.

The reason for this appears to be:

php5_invoke apcu: no action - module was disabled by maintainer for cli SAPI


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

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

Versions of packages php5-apcu depends on:
ii  libc6  2.17-93
ii  php5-common [phpapi-20121212]  5.5.5+dfsg-1

php5-apcu recommends no packages.

Versions of packages php5-apcu suggests:
ii  php5-gd  5.5.5+dfsg-1

-- no debconf information


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

Bug#728117: php5-apcu: breaks Mediawiki DB upgrade script

[Thorsten Glaser]

On Mon, 28 Oct 2013, Thorsten Glaser wrote:

> The reason for this appears to be:
> 
> php5_invoke apcu: no action - module was disabled by maintainer for cli SAPI

Manually running sudo php5enmod apcu seems to fix this.
I don’t understand.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-314
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Boris Esser, Sebastian Mancke


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

Bug#727805: rjava: Depends on openjdk-6 which is going away

[Dirk Eddelbuettel]

On 28 October 2013 at 15:17, Niels Thykier wrote:
| > And R itself already has (and had for ages) this in
| > debian/control::Build-Depends
| > 
| > default-jdk [!arm !hppa !kfreebsd-i386 !kfreebsd-amd64 !hurd-i386 !mips]
| > 
| 
| You would be missing mipsel then. :)

Oops.  We had mips at one point though.  Should I subst or add !mipsel ?
 
| > SO I guess we really only need to trigger a rebuild for rJava -- and 
possibly
| > tell the mips builders to ignore this package as it also has
| > 
| 
| s/mips/mipsel/
| 
| > default-jdk [!arm !hppa !kfreebsd-i386 !kfreebsd-amd64 !hurd-i386 !mips]

Will do.

| > but it should really be skipped on all of these/
| > 
| > Can you remind how I do that again?
| > 
| > Dirk
| > 
| 
| Set the Architecture field to list only acceptable architectures should
| do.  From there, the buildds should mark it as "Auto-Not-For-Us" and
| ignore it.  Mind you, you still have to file a removal bug for binaries
| on architectures that (as a consequence) will no longer be built.

I never liked that as I would miss 'new' Architectures that are added.  But I
can of course respond quickly to bug reports suggesting to add these.

Maybe I should try this...

|   An alternative is to Build-Depend on a package that is available on
| exactly the architectures your package supports[1].  Again, it would
| still need the removal bug, but that is another possibility.
| 
| ~Niels
| 
| [1] This makes for e.g. Build-Depends on an -dev package only available
| on certain architectures.  I am not certain that it makes sense in this
| particular case.

Right.

Thanks!

Dirk
 

-- 
Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com


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

Bug#716759: marked as done (openshot: mlt 0.9.0-1 renames python-mlt5 => python-mlt)

[Debian Bug Tracking System]

Your message dated Mon, 28 Oct 2013 17:33:56 +
with message-id 
and subject line Bug#716759: fixed in openshot 1.4.3-1.1
has caused the Debian Bug report #716759,
regarding openshot: mlt 0.9.0-1 renames python-mlt5 => python-mlt
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.)


-- 
716759: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openshot
Version: 1.4.3-1
Severity: normal

Hi,

I have just uploaded mlt=0.9.0-1 and it renames the python-mlt5 package to
python-mlt. Currently it is in NEW, after it is accepted openshot should
depend on it.

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

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: openshot
Source-Version: 1.4.3-1.1

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated openshot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Oct 2013 19:11:58 +0200
Source: openshot
Binary: openshot openshot-doc
Architecture: source all
Version: 1.4.3-1.1
Distribution: unstable
Urgency: low
Maintainer: Jonathan Thomas 
Changed-By: gregor herrmann 
Description: 
 openshot   - Create and edit videos and movies
 openshot-doc - Help manual for OpenShot Video Editor
Closes: 716759
Changes: 
 openshot (1.4.3-1.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix "mlt 0.9.0-1 renames python-mlt5 => python-mlt":
 debian/rules: update Depends.
 (Closes: #716759)
Checksums-Sha1: 
 67f29100b4c27051c0e5e6e4f1cd10494faed96d 1927 openshot_1.4.3-1.1.dsc
 6c41bc6b707ba29c0bf294731f9fdfab96be7d4e 4256 openshot_1.4.3-1.1.debian.tar.gz
 2b1f923df206e9ae253ff40f988351b9409ff120 20292932 openshot_1.4.3-1.1_all.deb
 d3002289c4b0969dafdb168e09b2c556d01b613c 7033998 openshot-doc_1.4.3-1.1_all.deb
Checksums-Sha256: 
 d1bfa06e588f643e9245c27530174aba11cc7a01eae9207ed1789e298f406b3d 1927 
openshot_1.4.3-1.1.dsc
 eb25e88da2205bece6df1a7a6a52c852c962b5f51d3b22bee75895b7f97116a2 4256 
openshot_1.4.3-1.1.debian.tar.gz
 148754f82c2437fa53ffca02a2c75b0b60ed236ccf3217a24d429d12fd0d0699 20292932 
openshot_1.4.3-1.1_all.deb
 1726149ba68ee7ef18898760b659d6e860bbae050f0f1985ca961734d526be1b 7033998 
openshot-doc_1.4.3-1.1_all.deb
Files: 
 948e5a5161314cb8c81c383f126f03df 1927 video optional openshot_1.4.3-1.1.dsc
 246e5cbb84dbbd29609599293503a906 4256 video optional 
openshot_1.4.3-1.1.debian.tar.gz
 e1f658409e67928503c91d30496ddd3d 20292932 video optional 
openshot_1.4.3-1.1_all.deb
 60dcd46f6de1c61c38be6b15579a3b0b 7033998 doc optional 
openshot-doc_1.4.3-1.1_all.deb

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

iQIcBAEBCAAGBQJSa/hUAAoJELs6aAGGSaoGewMQALK1Xr9HihNty5PyPl0Lv4d6
biNviljjn/Hs0KcW/W7FUHgyrzfGo85PV5G3e7YfR7EAV4b9uMnI8Z9HbxyfWi+B
NYh+PZF2k7Nt1rQEYaVovmLEf0kVY2GXSdfMpDQCAA1df8gqtpfY6AmGd2iiYcsm
9IsG9fBN2RVTWvOlWoiQgveZpvooFIjLW/iI+1FhDWturktQKvoVTkCNQv4glMW+
MFY3ADCvYbNnVbRSdlBF/sjfr1i9vid4d4LqXSLzeABKpxKAHq4f8xrbX7Ii5Icc
f1wN42zxaOuBqDzhVQtShi6hHNYkgA+1z1u2vCDkmmH8Zf/023noz9AQWaO+JkNT
rYeMTM4IxzGuved76e78NVWvA821XxI6V3Fs2Fl/4PxBj7GTtJbiP+2wKcvGiSqO
A7T+/g0MYkXKPSYOyf+6M6vDUlSOpkZtZtbhOnKD8PRv7bDBwozabTY192/8gMRY
dr0ocb9ib3jncUkFPKv0wChZfU6G9DzxTI6EjMb1C7fQsu/hwX5+vJVYUpVXjZBV
UhPDsWxS2DxDWk2I63eCWzUHHh8GwJ54nbo4AcmfZrnzqjoX4v5vATKnb4QTZhF+
Kyzl+SErShIWYsAH7TmOyzh4LmxtRgb3e8dqiUb5MpbHi9UmKbgFSBhT5rDmABvB
MsHs9hAROnkXHU7dgSCs
=XXKs
-END PGP SIGNATURE End Message ---

Bug#713628: marked as done (prelink: FTBFS: (.text+0x1d8): undefined reference to `pthread_atfork')

[Debian Bug Tracking System]

Your message dated Mon, 28 Oct 2013 17:34:04 +
with message-id 
and subject line Bug#713628: fixed in prelink 0.0.20090925-8
has caused the Debian Bug report #713628,
regarding prelink: FTBFS: (.text+0x1d8): undefined reference to `pthread_atfork'
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.)


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

Hi,

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

Relevant part:
> gcc -D_GNU_SOURCE -DHAVE_CONFIG_H -Wall -Wno-pointer-sign -I. -I../../src 
> -I.. -I../../gelfx -DSBINDIR='"//sbin"'  -Wall -Wno-pointer-sign -g -O2 -c 
> ../../src/sha.c
> ../../src/sha.c: In function 'sha_finish_ctx':
> ../../src/sha.c:92:3: warning: dereferencing type-punned pointer will break 
> strict-aliasing rules [-Wstrict-aliasing]
>*(md5_uint32 *) &ctx->buffer[bytes + pad + 4] = NOTSWAP (ctx->total[0] << 
> 3);
>^
> ../../src/sha.c:93:3: warning: dereferencing type-punned pointer will break 
> strict-aliasing rules [-Wstrict-aliasing]
>*(md5_uint32 *) &ctx->buffer[bytes + pad] = NOTSWAP ((ctx->total[1] << 3) |
>^
> /bin/bash ../libtool  --tag=CC   --mode=link gcc -Wall -Wno-pointer-sign -g 
> -O2 -all-static  -o prelink cache.o conflict.o cxx.o doit.o exec.o 
> execle_open.o get.o gather.o layout.o main.o prelink.o reloc.o space.o undo.o 
> undoall.o verify.o canonicalize.o md5.o sha.o checksum.o data.o dso.o 
> dwarf2.o fptr.o hashtab.o mdebug.o stabs.o crc32.o arch-i386.o arch-alpha.o 
> arch-ppc.o arch-ppc64.o arch-sparc.o arch-sparc64.o arch-x86_64.o arch-mips.o 
> arch-s390.o arch-s390x.o arch-arm.o arch-sh.o arch-ia64.o  -lselinux -lelf 
> libtool: link: gcc -Wall -Wno-pointer-sign -g -O2 -static -o prelink cache.o 
> conflict.o cxx.o doit.o exec.o execle_open.o get.o gather.o layout.o main.o 
> prelink.o reloc.o space.o undo.o undoall.o verify.o canonicalize.o md5.o 
> sha.o checksum.o data.o dso.o dwarf2.o fptr.o hashtab.o mdebug.o stabs.o 
> crc32.o arch-i386.o arch-alpha.o arch-ppc.o arch-ppc64.o arch-sparc.o 
> arch-sparc64.o arch-x86_64.o arch-mips.o arch-s390.o arch-s390x.o arch-arm.o 
> arch-sh.o arch-ia64.o  -lselinux -lelf
> /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libselinux.a(procattr.o):
>  In function `init_procattr':
> (.text+0x1d8): undefined reference to `pthread_atfork'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/prelink_0.0.20090925-7_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: prelink
Source-Version: 0.0.20090925-8

We believe that the bug you reported is fixed in the latest version of
prelink, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 713...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Moog  (supplier of updated prelink package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 10 Aug 2013 23:22:16 +0200
Source: prelink
Binary: prelink execstack
Architecture: source amd64
Version: 0.0.20090925-8
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group 
Changed-By: Andreas Moog 
Description: 
 execstack  - ELF GNU_STACK program header editing utility
 prelink- ELF prelinking utility to speed up dynamic linking
Closes: 713628
Changes: 
 prelink (0.0.20090925-8) unstable; urgency=low
 .
   * QA upload.
   * Add debian/patches/ftbfs-no-copy-dt-needed.patch: (Closes: #713628)
 - Fixes a FTBFS with The --no-copy-dt-needed linker flag which requires
   that all 

Bug#728092: [pkg-wpa-devel] Bug#728092: ifupdown: ifup -v displays wpa-password in cleartext

[Stefan Lippers-Hollmann]

Control: severity -1 minor

Hi

On Monday 28 October 2013, Andrew Shadura wrote:
> Hi,
> 
> One more thought: wpasupplicant.conf may be what you want.

Using a wpasupplicant.conf should indeed avoid this, e.g.:

allow-hotplug wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf

iface xyz-work inet dhcp

See /usr/share/doc/wpa_supplicant/README.Debian.gz and the examples
under that directory for details.

While I currently don't have access to wpa-enterprise encrypted 
networks, all you should end up seeing via "ifup -v" is something 
like:

Configuring interface wlan0=wlan0 (inet)
[…]
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wait for wpa_cli to attach
wpa_supplicant: wpa-driver nl80211,wext (default)
wpa_supplicant: /sbin/wpa_supplicant -s -B -P /var/run/wpa_supplicant.wlan0.pid 
-i wlan0 -W -D nl80211,wext -c /etc/wpa_supplicant/wpa_supplicant.conf
Starting /sbin/wpa_supplicant...
wpa_supplicant: creating sendsigs omission pidfile: 
/run/sendsigs.omit.d/wpasupplicant.wpa_supplicant.wlan0.pid
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
[…]
run-parts: executing /etc/network/if-up.d/wpasupplicant
wpa_supplicant: /sbin/wpa_cli -B -P /var/run/wpa_action.wlan0.pid -i wlan0 -p 
/var/run/wpa_supplicant -a /sbin/wpa_action
Starting /sbin/wpa_cli...

I'm adjusting the severity of this bug to minor, as an ordinary user 
can't query this information. Actually I'm not quite sure if it 
qualifies for a security tag either, but I'll keep that for the time
being.

$ /sbin/ifup -v wlan0
/sbin/ifup: failed to open lockfile /run/network/.ifstate.lock: Permission 
denied

You have to elevate its capabilities to root (via sudo) - at this point
the user has been granted unresticted access to ifup and its options 
anyways, including access to the wireless credentials.

While I will audit the wpa_supplicant hooks into ifupdown again (as
there are several changes planned anyways[1]), it would help me if you
could provide the full, obfuscated(!) (replace your password and other 
private information with X), results of ifup -v for a 
wpa-enterprise network.

As an, unrelated, remark, it's usually best not to mix the wireless-* 
and wpa-* namespace for the same interface stanza, although doing so
shouldn't be harmful -as long as the settings agree-, doing so might
create subtile race conditions between wireless-tools and 
wpa_supplicant trying to configure the interface (you only get away
with this, because wireless-tools is more or less state-less and not
a dæmon).

Regards
Stefan Lippers-Hollmann

[1] better DBus coexistence and #728092


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

Processed: Re: [pkg-wpa-devel] Bug#728092: ifupdown: ifup -v displays wpa-password in cleartext

[Debian Bug Tracking System]

Processing control commands:

> severity -1 minor
Bug #728092 [wpasupplicant] ifupdown: ifup -v displays wpa-password in cleartext
Severity set to 'minor' from 'grave'

-- 
728092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728092
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#725361: marked as done (openshot is not installable)

[Debian Bug Tracking System]

Your message dated Mon, 28 Oct 2013 17:33:56 +
with message-id 
and subject line Bug#716759: fixed in openshot 1.4.3-1.1
has caused the Debian Bug report #716759,
regarding openshot is not installable
to be marked as done.

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

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


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

I get the following when trying to install openshot.

  # aptitude install openshot
  The following NEW packages will be installed:
libmlt-data{a} libmlt6{a} libquicktime2{a} melt{a} openshot{b} 
  The following packages are RECOMMENDED but will NOT be installed:
openshot-doc 
  0 packages upgraded, 5 newly installed, 0 to remove and 250 not upgraded.
  Need to get 26.9 MB of archives. After unpacking 93.7 MB will be used.
  The following packages have unmet dependencies:
   openshot : Depends: python-mlt5 which is a virtual package. or
   python-mlt3 which is a virtual package. or
   python-mlt2 which is a virtual package.
  The following actions will resolve these dependencies:

   Keep the following packages at their current version:
  1) openshot [Not Installed]   



  Accept this solution? [Y/n/q/?] n

  *** No more solutions available ***


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

Kernel: Linux 3.10-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages openshot depends on:
ii  librsvg2-common 2.36.4-2
pn  melt
ii  python  2.7.5-4
ii  python-glade2   2.24.0-3+b1
ii  python-gtk2 2.24.0-3+b1
pn  python-mlt2 
ii  python-pygoocanvas  0.14.1-1+b3
ii  python-support  1.0.15
ii  python-xdg  0.25-3

Versions of packages openshot recommends:
pn  openshot-doc  

openshot suggests no packages.
--- End Message ---
--- Begin Message ---
Source: openshot
Source-Version: 1.4.3-1.1

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated openshot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Oct 2013 19:11:58 +0200
Source: openshot
Binary: openshot openshot-doc
Architecture: source all
Version: 1.4.3-1.1
Distribution: unstable
Urgency: low
Maintainer: Jonathan Thomas 
Changed-By: gregor herrmann 
Description: 
 openshot   - Create and edit videos and movies
 openshot-doc - Help manual for OpenShot Video Editor
Closes: 716759
Changes: 
 openshot (1.4.3-1.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix "mlt 0.9.0-1 renames python-mlt5 => python-mlt":
 debian/rules: update Depends.
 (Closes: #716759)
Checksums-Sha1: 
 67f29100b4c27051c0e5e6e4f1cd10494faed96d 1927 openshot_1.4.3-1.1.dsc
 6c41bc6b707ba29c0bf294731f9fdfab96be7d4e 4256 openshot_1.4.3-1.1.debian.tar.gz
 2b1f923df206e9ae253ff40f988351b9409ff120 20292932 openshot_1.4.3-1.1_all.deb
 d3002289c4b0969dafdb168e09b2c556d01b613c 7033998 openshot-doc_1.4.3-1.1_all.deb
Checksums-Sha256: 
 d1bfa06e588f643e9245c27530174aba11cc7a01eae9207ed1789e298f406b3d 1927 
openshot_1.4.3-1.1.dsc
 eb25e88da2205bece6df1a7a6a52c852c962b5f51d3b22bee75895b7f97116a2 4256 
openshot_1.4.3-1.1.debian.tar.gz
 148754f82c2437fa53ffca02a2c75b0b60ed236ccf3217a24d429d12fd0d0699 20292932 
openshot_1.4.3-1.1_all.deb
 1726149ba68ee7ef18898760b659d6e860bbae050f0f1985ca961734d526be1b 7033998 
openshot-doc_1.4.3-1.1_all.deb
Files: 
 948e5a5161314cb8c81c383f126f03df 1927 video optional openshot_1.4.3-1.1.dsc
 246e5cbb84dbbd29609599293503a906 4256 video optional 
openshot_1.4.3-1.1.debian.tar.gz
 e1f658409e67928503c91d30496ddd3d 20292932 video optional 
openshot_1.4.3-1.1_all.deb
 60dcd46f6de1c61c38be6b15579a3b0b 7

Processed: severity of 728117 is important

[Debian Bug Tracking System]

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

> severity 728117 important
Bug #728117 [php5-apcu] php5-apcu: breaks Mediawiki DB upgrade script
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
728117: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728117
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#727751: enblend-enfuse: FTBFS on mipsel but built there in the past

[Andreas Metzler]

On 2013-10-26 Niels Thykier  wrote:
> Package: enblend-enfuse
> Version: 4.0+dfsg-6
> Severity: serious

> Hi,

> Your package FTBFS on mipsel but built there in the past.  It looks
> like it is an ICE, so you may have to reassign the bug to the relevant
> compiler/part of the toolchain.

Hello,

is it possible that the mipsel *buildd* machines are hosed? e.g.
4.1.2+dfsg-1 in experimental) failed to build on mayer [buildd]
yesterday but worked on eder [porterbox]. Afaict both were using the
same up to date toolchain.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'


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

Bug#728128: flexpart: FTBFS on *amd64: relocation overflows

[Aaron M. Ucko]

Source: flexpart
Version: 9.02-2
Severity: serious
Justification: fails to build from source

Builds of flexpart on amd64 and kfreebsd-amd64 have been failing:

  gfortran *.o -o flexpart.gfs -Wl,-z,relro -O2 -fdefault-real-8 
-fconvert=little-endian -frecord-marker=4 -I/usr/include  -L/usr/lib 
-Wl,--as-needed  -lgrib_api_f90 -lgrib_api -lm -ljasper
  FLEXPART.o: In function `MAIN__':
  FLEXPART.f90:(.text+0x2c): relocation truncated to fit: R_X86_64_32S against 
symbol `__com_mod_MOD_rannumb' defined in .bss section in com_mod.o
  FLEXPART.f90:(.text+0x10d): relocation truncated to fit: R_X86_64_PC32 
against symbol `__com_mod_MOD_nested_output' defined in .bss section in 
com_mod.o
  [...]

Searching for these messages brings me to
http://stackoverflow.com/questions/12916176/gfortran-for-dummies-what-does-mcmodel-medium-do-exactly
which indicates that they stem from having too many large static
arrays and recommends either making some of them dynamic (allocatable)
or, if that's not feasible, building with -mcmodel=medium.  It's not
clear whether code built with that flag will safely be able to use
libraries built without it, though.

At any rate, could you please take a look?

Thanks!


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

Bug#728129: ballerburg: FTBFS: ERROR: You need the 'cmake' program

[Aaron M. Ucko]

Source: ballerburg
Version: 1.0.1-1
Severity: serious
Justification: fails to build from source

Builds of ballerburg in minimal environments (as on the autobuilders)
have been failing:

  ./configure --prefix=/usr
  ERROR: You need the 'cmake' program to configure the build process.
  Please install 'cmake' first, then try again.
  make[1]: *** [override_dh_auto_configure] Error 1

Please declare a build dependency on cmake, and confirm with pbuilder
or the like that you haven't missed any others.

Thanks!


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

Bug#728130: vlc: FTBFS on kfreebsd-*

[Sebastian Ramacher]

Source: vlc
Version: 2.1.0-1
Severity: serious
Justification: fails to build (but built successfully in the past)

vlc fails to build on kfreebsd-*:
| /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -std=gnu99 
-DHAVE_CONFIG_H -I. -I../..  -DMODULE_NAME=$(p="libv4l2_plugin_la-video.lo"; 
p="${p##*/}"; p="${p#lib}"; echo "${p%_plugin*}") 
-DMODULE_NAME_IS_$(p="libv4l2_plugin_la-video.lo"; p="${p##*/}"; p="${p#lib}"; 
echo "${p%_plugin*}") -DMODULE_STRING=\"$(p="libv4l2_plugin_la-video.lo"; 
p="${p##*/}"; p="${p#lib}"; echo "${p%_plugin*}")\" -D__PLUGIN__ -I./v4l2 
-I../../include -I../../include -D_FORTIFY_SOURCE=2   -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wextra 
-Wsign-compare -Wundef -Wpointer-arith -Wbad-function-cast -Wwrite-strings 
-Wmissing-prototypes -Wvolatile-register-var 
-Werror-implicit-function-declaration -pipe -fvisibility=hidden -ffast-math 
-funroll-loops -fomit-frame-pointer -c -o libv4l2_plugin_la-video.lo `test -f 
'v4l2/video.c' || echo './'`v4l2/video.c
| libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. 
-DMODULE_NAME=v4l2 -DMODULE_NAME_IS_v4l2 -DMODULE_STRING=\"v4l2\" -D__PLUGIN__ 
-I./v4l2 -I../../include -I../../include -D_FORTIFY_SOURCE=2 -g -O2 
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
-Wall -Wextra -Wsign-compare -Wundef -Wpointer-arith -Wbad-function-cast 
-Wwrite-strings -Wmissing-prototypes -Wvolatile-register-var 
-Werror-implicit-function-declaration -pipe -fvisibility=hidden -ffast-math 
-funroll-loops -fomit-frame-pointer -c v4l2/video.c  -fPIC -DPIC -o 
.libs/libv4l2_plugin_la-video.o
| In file included from v4l2/v4l2.h:21:0,
|  from v4l2/video.c:39:
| ./v4l2/linux/videodev2.h:60:25: fatal error: linux/ioctl.h: No such file or 
directory
|  #include 
|  ^
| compilation terminated.
| make[6]: *** [libv4l2_plugin_la-v4l2.lo] Error 1

For a full build log see
https://buildd.debian.org/status/fetch.php?pkg=vlc&arch=kfreebsd-i386&ver=2.1.0-1&stamp=1382855238.

Regards
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#728131: avw.lv2: FTBFS on architectures where gcc-4.6 is still the default

[Sebastian Ramacher]

Source: avw.lv2
Version: 0.1.4~dfsg0-1
Severity: serious
Justification: fails to build (but built successfully in the past)

avw.lv2 FTBFS on architectures that still have gcc-4.6 as default
compiler (ia64, powerpc, s390x, sparc):
| cc1plus: error: unrecognized command line option '-std=c++11'

Fuill build log:
https://buildd.debian.org/status/fetch.php?pkg=avw.lv2&arch=s390x&ver=0.1.6~dfsg0-1&stamp=1382861312

This can be fixed by explicitely dependening on g++-4.8 and setting CXX
accordingly.

Regards
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#728134: python-markdown: Copyright file incomplete

[Luke Faraone]

Package: python-markdown
Version: 2.1.1-3
Severity: serious
Justification: Policy 12.5

Dear maintainer,

debian/copyright for this package states that the package is
dual-licensed under the GPL 2 and the BSD licenses, however I cannot
find any indication that it is under GPL 2.

In addition, copyright statements are omitted:

markdown/searializers.py:
# Copyright (c) 1999-2007 by Fredrik Lundh
#
# By obtaining, using, and/or copying this software and/or its
# associated documentation, you agree that you have read, understood,
# and will comply with the following terms and conditions:
#
# Permission to use, copy, modify, and distribute this software and
# its associated documentation for any purpose and without fee is
# hereby granted, provided that the above copyright notice appears in
# all copies, and that both that copyright notice and this permission
# notice appear in supporting documentation, and that the name of
# Secret Labs AB or the author not be used in advertising or publicity
# pertaining to distribution of the software without specific, written
# prior permission.
#
# SECRET LABS AB AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD
# TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANT-
# ABILITY AND FITNESS.  IN NO EVENT SHALL SECRET LABS AB OR THE AUTHOR
# BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY
# DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
# WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
# ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE
# OF THIS SOFTWARE.


__init__.py lists:
Copyright 2007-2012 The Python Markdown Project (v. 1.7 and later)
Copyright 200? Django Software Foundation (OrderedDict implementation)
Copyright 2004, 2005, 2006 Yuri Takhteyev (v. 0.2-1.6b)
Copyright 2004 Manfred Stienstra (the original version)

extensions/abbr.py:
Copyright 2007-2008
* [Waylan Limberg](http://achinghead.com/)
* [Seemant Kulleen](http://www.kulleen.org/)

extensions/attr_list.py:
Copyright 2011 [Waylan Limberg](http://achinghead.com/).
extensions/codehilite.py:
Copyright 2006-2008 [Waylan Limberg](http://achinghead.com/).
extensions/def_list.py:
Copyright 2008 - [Waylan Limberg](http://achinghead.com)
extensions/fenced_code.py:
Copyright 2007-2008 [Waylan Limberg](http://achinghead.com/).
extensions/headerid.py:
Copyright 2007-2011 [Waylan Limberg](http://achinghead.com/).
extensions/html_tidy.py:
Copyright (c)2008 [Waylan Limberg](http://achinghead.com)
extensions/meta.py:
Copyright 2007-2008 [Waylan Limberg](http://achinghead.com).
extensions/nl2br.py:
Copyright 2011 [Brian Neal](http://deathofagremmie.com/)
extensions/smart_strong.py:
Copyright 2011 [Waylan Limberg](http://achinghead.com)
extensions/tables.py:
Copyright 2009 - [Waylan Limberg](http://achinghead.com)
extensions/toc.py:
(c) 2008 [Jack Miller](http://codezen.org)

I have not looked through every file in the package, so I am sure it is
possible I missed some entries.

When updating debian/copyright also consider updating the upstream URL
listed therein.

Cheers,

Luke Faraone





-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

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


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

Bug#711236: ruby-rack1.4 in NEW

[Christian Hofstaedtler]

ruby-rack1.4 is now in NEW.

Once it's through, packages that can't use rack 1.5 should switch
their Depends: line to ruby-rack1.4.

Packages that can use either version should drop any versioned
Depends they have on ruby-rack.

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-



signature.asc
Description: Digital signature

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

[Sebastian Ramacher]

Source: brutefir
Version: 1.0l-1
Severity: serious
Justifcation: fails to built (but built successfully in the past)

brutefir fails to build on kfreebsd-i386:
| gcc -L/usr/lib -Xlinker --allow-multiple-definition -o brutefir brutefir.o 
fftw_convolver.o bfconf.o bfrun.o firwindow.o emalloc.o shmalloc.o dai.o 
bfconf_lexical.o inout.o dither.o delay.o -lfftw3 -lfftw3f -lm -ldl
| fftw_convolver.o: In function `convolver_convolve_add':
| fftw_convolver.c:(.text+0x5288): undefined reference to 
`convolver_sse_convolve_add'
| collect2: error: ld returned 1 exit status
| make[2]: *** [brutefir] Error 1

Full build log is available at
https://buildd.debian.org/status/fetch.php?pkg=brutefir&arch=kfreebsd-i386&ver=1.0l-1&stamp=1381845349

Regards
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#727786: follow-up for: removal of libc6-amd64 makes system unusable

[Paul Gevers]

Just an important note for anybody ending up at this bug and wanting to
remove libc6-amd64. As long as you have root access to the system and
have not powered off yet, I believe you can fix this issue without
rescue CD/USB.

With root access (sudo does not work anymore, because the setguid fails)
you can do:
apt-get remove libc6-amd64
cd lib64
/lib/x86_64-linux-gnu/ld-2.13.so /bin/rm ld-linux-x86-64.so.2
/lib/x86_64-linux-gnu/ld-2.13.so /bin/ln -s
/lib/x86_64-linux-gnu/ld-2.13.so ld-linux-x86-64.so.2

Done.

I haven't tested this sequence (as I did not have a root login
available) but I am pretty sure this would work.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#724102: [Pkg-haskell-maintainers] Bug#724102: #724102: pandoc misses recommends on pandoc-data

[intrigeri]

Hi Jonas,

Jonas Smedegaard wrote (28 Sep 2013 13:29:59 GMT) :
> I have now changed package "pandoc" to depend on "pandoc-data",
> in git.

Thanks. Any ETA for an upload with this change?

I've just had one package auto-removed from testing due to a FTBFS
caused by #724102.

Cheers,
--
  intrigeri
  | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc


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

Processed: found 726478 in 2012.2.1-1

[Debian Bug Tracking System]

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

> found 726478 2012.2.1-1
Bug #726478 [glance] glance: CVE-2013-4428: image_download policy not enforced 
for cached images
Marked as found in versions glance/2012.2.1-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
726478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726478
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#727831: vlc: FTBFS on architectures built with --disable-mmx

[Benjamin Drung]

On So, 2013-10-27 at 15:28 +0100, Sebastian Ramacher wrote:
> Source: vlc
> Version: 2.1.0-1
> Severity: serious
> Justification: fails to build (but built successfully in the past)
> 
> vlc fails to build on armhf, ia64, mips{,el}, s390x and sparc with:
> | # Install stuff
> | dh_install --fail-missing
> | cp: cannot stat 
> 'debian/tmp/usr/lib/vlc/plugins/mmx/libi420_rgb_mmx_plugin.so': No such file 
> or directory
> | dh_install: cp -a 
> debian/tmp/usr/lib/vlc/plugins/mmx/libi420_rgb_mmx_plugin.so 
> debian/vlc-nox//usr/lib/vlc/plugins/mmx/ returned exit code 1
> 
> (I presume it will FTBFS on armel for the same reason, but it has not
> been tried there yet.)
> 
> vlc is built with --disable-mmx on these architectures which would
> explain the absence of this plugin.
> 
> Build logs are available at
> https://buildd.debian.org/status/package.php?p=vlc.

I fixed this kind of build failure four days ago in our git repository:
http://anonscm.debian.org/gitweb/?p=pkg-multimedia/vlc.git;a=commitdiff;h=d8ff1171
http://anonscm.debian.org/gitweb/?p=pkg-multimedia/vlc.git;a=commitdiff;h=799db4f9

kfreebsd-{amd64,i386} and powerpc seem to have a different reason to
fail to build.

-- 
Benjamin Drung
Debian & Ubuntu Developer


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

Bug#726472: share passwords not working after upgrade from samba3

[Ivo De Decker]

Hi,

On Mon, Oct 21, 2013 at 10:37:49PM +1300, Andrew Bartlett wrote:
> > Ok.  I think we need to undo this /var/lib/samba/private nonsense.  It is a
> > pointless and imperfect migration (as shown by this bug report), and the
> > only rationale upstream ever gave for keeping these files in a separate
> > "private" directory is some stupid and ancient target OS that couldn't
> > properly set per-file permissions.  Debian users have been using
> > /var/lib/samba exclusively for the better part of a decade; migrating to
> > this private/ directory adds no value for our users.
> 
> In the alternate, the only reason this happened now is because we are
> finally having the Debian packages follow where upstream has decided to
> put the files.  Having different packages moving files around to
> different places only increases user confusion, and creates 'only on
> Debian' bugs.  
> 
> For example, a significant number of issues came about as folks tried to
> divine if a particular TDB was short, medium or long-term, when no such
> separation existed in the code. 
> 
> We (upstream) have gone to significant effort to integrate the FHS
> changes that have been proposed via Debian, I can only ask that having
> got to a mutually agreed state, that Debian not change it again, having
> once more Debian packages special and different. 

I had a long talk with Jelmer yesterday about this bug. Here are a number of
considerations from that discussion:


First of all, it certainly isn't clear that the issue is caused by a mistake
in unstable some time ago. I haven't been able to find any indication for that
(yet) in any of the samba versions available on snapshot.debian.org. We've
been using /etc/samba as private dir from the first 3.2 upload to the last 3.6
upload and there is no apparent usage of /var/lib/samba/private anywhere in
the code of any of these versions.

It is quite possible that the issue is triggered by a race condition in the
tdb-handling (especially for passdb.tdb), which can result in the creation of
the wrong tdb file during the upgrade, which messes up our move. This could be
caused by the usage of the 'smbpasswd' command or the pam-smbpass pam module.
I haven't had the time yet to create a situation where I can trigger the race
condition.

There are a number of ways to work around these possible race conditions
during at the time of the move. An incomplete list of ideas (some of these
would have to be combined to get to a complete fix):

- Patch the passdb tdb module to do the move, instead of having it in
  samba.postinst. This isn't completely unprecedented, as the move of
  MACHINE.SID was supported by the samba code.

- Track the fact that the move was done, by adding some field to the new tdb
  file. This might cause issues in tools that don't handle unknown fields. The
  samba4 upgrade script might be one of those.

- Track the fact that the move was done, by making sure the old tdb can't be
  used anymore. This could be done by changing the version number of the old
  tdb to something non-existent.

- Do some kind of merge of both tdb files, if they both exist.

- When both tdb files exist, have a debconf question that gives some
  information about both (eg number of users), and ask the user to choose
  between them.

Any decent implementation will require some careful planning and probably
quite some discussion as well. It is clear that the new samba 4.x packages
provide a nice step forward compared to the samba 3.6 packages, and these
changes shouldn't be blocked by this problem. Therefore we are proposing to
postpone this move for now.

Moving the private dir to /var/lib/samba would cause an issue with the files
kept by samba4 in /var/lib/samba/private. So the only obvious way forward
would be to have a new version of our previous patch, which moves the 4
affected files back to /var/lib/samba. I really regret having to propose this,
as I very much would like to avoid reintroducing a patch like that, but at
this point, I don't really see any other short term options.

So the proposal is to reintroduce something like the old patch, and try to get
that version into shape for testing/jessie. After that, we can figure out how
to get this move done the right way.

Any thoughts, comments?

> Or in the alternate, propose such changes upstream. 

Moving the files upstream would inflict all this pain on other distributions,
so someone would still have to sort this all out.


Cheers,

Ivo


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

Bug#728145: amsynth: FTBFS on kfreebsd-*: ALSAmmapAudioDriver.cc:26:28: error: 'ESTRPIPE' was not declared in this scope

[Sebastian Ramacher]

Source: amsynth
Version: 1.3.2-1
Severity: serious
Justification: fails to build (but built successfully in the past)

amsynth fails to build on kfreebsd-* with:
| g++ -DHAVE_CONFIG_H -I. -I../..  -I/usr/include/alsa-g -O2 -c -o 
libdrivers_a-ALSAmmapAudioDriver.o `test -f 'ALSAmmapAudioDriver.cc' || echo 
'./'`ALSAmmapAudioDriver.cc
| ALSAmmapAudioDriver.cc: In member function 'int 
ALSAmmapAudioDriver::xrun_recovery()':
| ALSAmmapAudioDriver.cc:26:28: error: 'ESTRPIPE' was not declared in this scope
| make[4]: *** [libdrivers_a-ALSAmmapAudioDriver.o] Error 1

Full build log is available at
https://buildd.debian.org/status/fetch.php?pkg=amsynth&arch=kfreebsd-amd64&ver=1.3.2-2&stamp=1367836646

Regards
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#728146: pd-iemambi: FTBFS on kfreebsd-*: #error No byte order defined

[Sebastian Ramacher]

Source: pd-iemambi
Version: 0.2-1
Severity: serious
Justification: fails to build (but built successfully in the past)

pd-iemambi fails to build on kfreebsd-* with:
| /usr/bin/make  -C src CFLAGS="-g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall" CXXFLAGS="-g 
-O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
-Werror=format-security -Wall" CPPFLAGS="-D_FORTIFY_SOURCE=2" 
LDFLAGS="-Wl,-z,relro"
| make[1]: Entering directory `/«PKGBUILDDIR»/src'
| cc -DPD -DUNIX -W -Wno-unused -Wno-parentheses -Wno-switch -funroll-loops 
-fomit-frame-pointer -fno-strict-aliasing -DDL_OPEN -fPIC -g -O2 
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
-Wall -I. -I/usr/local/src/pd/src  -c -o ambi_decode.o ambi_decode.c
| In file included from ambi_decode.c:7:0:
| iemlib.h:69:2: error: #error No byte order defined
|  #error No byte order defined
|   ^
| make[1]: *** [ambi_decode.o] Error 1


Full build log is available at
https://buildd.debian.org/status/fetch.php?pkg=pd-iemambi&arch=kfreebsd-amd64&ver=0.2-1&stamp=1373234505.

Regards
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#726472: share passwords not working after upgrade from samba3

[Andrew Bartlett]

On Mon, 2013-10-28 at 22:00 +0100, Ivo De Decker wrote:
> Hi,
> 
> On Mon, Oct 21, 2013 at 10:37:49PM +1300, Andrew Bartlett wrote:
> > > Ok.  I think we need to undo this /var/lib/samba/private nonsense.  It is 
> > > a
> > > pointless and imperfect migration (as shown by this bug report), and the
> > > only rationale upstream ever gave for keeping these files in a separate
> > > "private" directory is some stupid and ancient target OS that couldn't
> > > properly set per-file permissions.  Debian users have been using
> > > /var/lib/samba exclusively for the better part of a decade; migrating to
> > > this private/ directory adds no value for our users.
> > 
> > In the alternate, the only reason this happened now is because we are
> > finally having the Debian packages follow where upstream has decided to
> > put the files.  Having different packages moving files around to
> > different places only increases user confusion, and creates 'only on
> > Debian' bugs.  
> > 
> > For example, a significant number of issues came about as folks tried to
> > divine if a particular TDB was short, medium or long-term, when no such
> > separation existed in the code. 
> > 
> > We (upstream) have gone to significant effort to integrate the FHS
> > changes that have been proposed via Debian, I can only ask that having
> > got to a mutually agreed state, that Debian not change it again, having
> > once more Debian packages special and different. 
> 
> I had a long talk with Jelmer yesterday about this bug. Here are a number of
> considerations from that discussion:
> 
> 
> First of all, it certainly isn't clear that the issue is caused by a mistake
> in unstable some time ago. I haven't been able to find any indication for that
> (yet) in any of the samba versions available on snapshot.debian.org. We've
> been using /etc/samba as private dir from the first 3.2 upload to the last 3.6
> upload and there is no apparent usage of /var/lib/samba/private anywhere in
> the code of any of these versions.
> 
> It is quite possible that the issue is triggered by a race condition in the
> tdb-handling (especially for passdb.tdb), which can result in the creation of
> the wrong tdb file during the upgrade, which messes up our move. This could be
> caused by the usage of the 'smbpasswd' command or the pam-smbpass pam module.
> I haven't had the time yet to create a situation where I can trigger the race
> condition.
> 
> There are a number of ways to work around these possible race conditions
> during at the time of the move. An incomplete list of ideas (some of these
> would have to be combined to get to a complete fix):
> 
> - Patch the passdb tdb module to do the move, instead of having it in
>   samba.postinst. This isn't completely unprecedented, as the move of
>   MACHINE.SID was supported by the samba code.
> 
> - Track the fact that the move was done, by adding some field to the new tdb
>   file. This might cause issues in tools that don't handle unknown fields. The
>   samba4 upgrade script might be one of those.
> 
> - Track the fact that the move was done, by making sure the old tdb can't be
>   used anymore. This could be done by changing the version number of the old
>   tdb to something non-existent.
> 
> - Do some kind of merge of both tdb files, if they both exist.
> 
> - When both tdb files exist, have a debconf question that gives some
>   information about both (eg number of users), and ask the user to choose
>   between them.
> 
> Any decent implementation will require some careful planning and probably
> quite some discussion as well. It is clear that the new samba 4.x packages
> provide a nice step forward compared to the samba 3.6 packages, and these
> changes shouldn't be blocked by this problem. Therefore we are proposing to
> postpone this move for now.
> 
> Moving the private dir to /var/lib/samba would cause an issue with the files
> kept by samba4 in /var/lib/samba/private. So the only obvious way forward
> would be to have a new version of our previous patch, which moves the 4
> affected files back to /var/lib/samba. I really regret having to propose this,
> as I very much would like to avoid reintroducing a patch like that, but at
> this point, I don't really see any other short term options.
> 
> So the proposal is to reintroduce something like the old patch, and try to get
> that version into shape for testing/jessie. After that, we can figure out how
> to get this move done the right way.
> 
> Any thoughts, comments?
> 
> > Or in the alternate, propose such changes upstream. 
> 
> Moving the files upstream would inflict all this pain on other distributions,
> so someone would still have to sort this all out.

I strongly oppose both proposals.  The upgrade to Samba 4.0 is the time
to correct this silly business of having files in different paths to
what upstream has, rightly or wrongly, chosen.  

Andrew Bartlett

-- 
Andrew Bartlett
http://samba.org/~abartlet/
Authentication Developer, Samba Team

Bug#728148: mixxx: FTBFS in arm*: /usr/include/qt4/QtGui/qcolor.h:138:10: note: no known conversion for argument 1 from 'double*' to 'qreal* {aka float*}'

[Sebastian Ramacher]

Source: mixxx
Version: 1.11.0~dfsg-1
Severity: serious

mixxx fails to build on arm*:
| g++ -o lin32_build/waveform/renderers/waveformrendererhsv.o -c -g -O2 
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
-D_FORTIFY_SOURCE=2 -pipe -Wall -Wextra -g -O3 -fomit-frame-pointer -ffast-math 
-funroll-loops -DQT_GUI_LIB -Darmel -D__LINUX__ -D__UNIX__ 
-DSETTINGS_PATH=\".mixxx/\" -DBPMSCHEME_FILE=\"mixxxbpmscheme.xml\" 
-DSETTINGS_FILE=\"mixxx.cfg\" -DTRACK_FILE=\"mixxxtrack.xml\" 
-DUNIX_SHARE_PATH=\"/usr/share/mixxx\" -DUNIX_LIB_PATH=\"/usr/lib/mixxx\" 
-D__PORTAUDIO__ -DQT_TABLET_SUPPORT -DQT_SHARED -D__SNDFILE__ -D__MAD__ 
-D__HID__ -D__BULK__ -D__VINYLCONTROL__ -D__SHOUTCAST__ -D__VAMP__ -DHAVE_FFTW3 
-I/usr/share/qt4/include -Ilin32_build -Isrc -I/usr/include/soundtouch 
-Ilib/replaygain -I/usr/include/qt4 -I/usr/include/qt4/QtCore 
-I/usr/include/qt4/QtGui -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtXml 
-I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtScript 
-I/usr/include/qt4/QtXmlPatterns -I/usr/include/qt4/QtNetwork 
-I/usr/share/qt4/include/QtCore -I/usr/share/qt4/include/QtGui 
-I/usr/share/qt4/include/QtOpenGL -I/usr/share/qt4/include/QtXml 
-I/usr/share/qt4/include/QtNetwork -I/usr/share/qt4/include/QtSql 
-I/usr/share/qt4/include/QtScript -I/usr/share/qt4/include/Qt 
-Ilib/fidlib-0.9.10 -I/usr/include/taglib -Ilib/hidapi-0.8.0-pre/hidapi 
-I/usr/include/libusb-1.0 -Ilib/xwax -Ilib/scratchlib 
src/waveform/renderers/waveformrendererhsv.cpp
| src/waveform/renderers/waveformrendererhsv.cpp: In member function 'virtual 
void WaveformRendererHSV::draw(QPainter*, QPaintEvent*)':
| src/waveform/renderers/waveformrendererhsv.cpp:75:46: error: no matching 
function for call to 'QColor::getHsvF(double*, double*, double*) const'
|  m_pColors->getLowColor().getHsvF(&h,&s,&v);
|   ^
| src/waveform/renderers/waveformrendererhsv.cpp:75:46: note: candidate is:
| In file included from /usr/include/qt4/QtGui/QColor:1:0,
|  from src/waveform/renderers/waveformsignalcolors.h:4,
|  from src/waveform/renderers/waveformrenderersignalbase.h:5,
|  from src/waveform/renderers/waveformrendererhsv.h:4,
|  from src/waveform/renderers/waveformrendererhsv.cpp:1:
| /usr/include/qt4/QtGui/qcolor.h:138:10: note: void QColor::getHsvF(qreal*, 
qreal*, qreal*, qreal*) const
|  void getHsvF(qreal *h, qreal *s, qreal *v, qreal *a = 0) const;
|   ^
| /usr/include/qt4/QtGui/qcolor.h:138:10: note:   no known conversion for 
argument 1 from 'double*' to 'qreal* {aka float*}'
| scons: *** [lin32_build/waveform/renderers/waveformrendererhsv.o] Error 1

Full build log is available at
https://buildd.debian.org/status/fetch.php?pkg=mixxx&arch=armel&ver=1.11.0~dfsg-2&stamp=1380909221.

Regards
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#727122: [gitolite3] Patch

[bastien ROUCARIES]

Package: gitolite3
control: tags -1 + patch

Ok now the patch please apply

--- Setup.pm.old	2013-07-10 08:17:36.0 +0200
+++ Setup.pm	2013-10-28 22:25:05.976114145 +0100
@@ -165,5 +165,5 @@
 repo gitolite-admin
 RW+ =   %ADMIN
 
-repo testing
-RW+ =   @all
+# repo testing
+#RW+ =   @all

Processed: [gitolite3] Patch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #727122 [gitolite3] [gitolite3] Do not create a test-repo with @all RW
Added tag(s) patch.

-- 
727122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727122
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#720296: marked as done (apt-cacher-ng: modifies conffiles (policy 10.7.3): /etc/apt-cacher-ng/backends_debian)

[Debian Bug Tracking System]

Your message dated Mon, 28 Oct 2013 21:48:53 +
with message-id 
and subject line Bug#720296: fixed in apt-cacher-ng 0.7.19-1
has caused the Debian Bug report #720296,
regarding apt-cacher-ng: modifies conffiles (policy 10.7.3): 
/etc/apt-cacher-ng/backends_debian
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.)


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

Hi,

during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files

10.7.3: "[...] The easy way to achieve this behavior is to make the
configuration file a conffile. [...] This implies that the default
version will be part of the package distribution, and must not be
modified by the maintainer scripts during installation (or at any
other time)."

Note that once a package ships a modified version of that conffile,
dpkg will prompt the user for an action how to handle the upgrade of
this modified conffile (that was not modified by the user).

Further in 10.7.3: "[...] must not ask unnecessary questions
(particularly during upgrades) [...]"

If a configuration file is customized by a maintainer script after
having asked some debconf questions, it may not be marked as a
conffile. Instead a template could be installed in /usr/share and used
by the postinst script to fill in the custom values and create (or
update) the configuration file (preserving any user modifications!).
This file must be removed during postrm purge.
ucf(1) may help with these tasks.
See also http://wiki.debian.org/DpkgConffileHandling

In https://lists.debian.org/debian-devel/2012/09/msg00412.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

debsums reports modification of the following files,
from the attached log (scroll to the bottom...):

0m19.0s ERROR: FAIL: debsums reports modifications inside the chroot:
  /etc/apt-cacher-ng/backends_debian


cheers,

Andreas


apt-cacher-ng_0.7.17-1.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Source: apt-cacher-ng
Source-Version: 0.7.19-1

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

Debian distribution maintenance software
pp.
Eduard Bloch  (supplier of updated apt-cacher-ng package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 28 Oct 2013 22:20:09 +0100
Source: apt-cacher-ng
Binary: apt-cacher-ng
Architecture: source amd64
Version: 0.7.19-1
Distribution: unstable
Urgency: low
Maintainer: Eduard Bloch 
Changed-By: Eduard Bloch 
Description: 
 apt-cacher-ng - caching proxy server for software repositories
Closes: 720296 720954 722600 722712 722907 726925
Changes: 
 apt-cacher-ng (0.7.19-1) unstable; urgency=low
 .
   [ Eduard Bloch ]
   * New upstream version
 + prints errno message from a failed daemon() call (closes: #726925)
 + suppresses output from the red utility leaked to stderr (closes: #722600)
   * Attempting to use a http proxy from apt settings for the mirror lookup in
 postinst (closes: #720954)
   * no longer delivering empty conffiles (backends_*, closes: #720296)
   [ Julian Andres Klode ]
   * Included IPv6 in the avahi config (closes: #722907)
   [ Lukas Anzinger  ]
   * Converted apt-cacher-ng to debhelper 9 (closes: #722712)
Checksums-Sha1: 
 9f86d65156045229c5266f33084a265b25c6c1f8 1264 apt-cacher-ng_0.7.19-1.dsc
 80187536c792fc945c61c101b10dbc5ff4fec35c 265140 
apt-cacher-ng_0.7.19.orig.tar.xz
 3db08be7e2245a8bd21c799e080e65a0c9475ad2 26552 
apt-cacher-ng_0.7.19-1.debian.tar.xz
 09c3ca84a8a08596053476ca4228575d05726906 532120 
apt-cacher-ng_0.7.19-1_amd64.deb
Checksums-Sha256: 
 4c4a68b88c0ca8cd2e0ba4547ae1709c4cf30233174e81c143b12d3f9ff95bc6 1264 
apt-cacher-ng_0.7.19-1.dsc
 73df667ad5a742f603df7a0d9c3bb9600b6d7b9bc448553fd73fa41

Bug#727751: enblend-enfuse: FTBFS on mipsel but built there in the past

[Andreas Barth]

* Andreas Metzler (ametz...@bebt.de) [131028 19:24]:
> On 2013-10-26 Niels Thykier  wrote:

> > Your package FTBFS on mipsel but built there in the past.  It looks
> > like it is an ICE, so you may have to reassign the bug to the relevant
> > compiler/part of the toolchain.

> is it possible that the mipsel *buildd* machines are hosed? e.g.
> 4.1.2+dfsg-1 in experimental) failed to build on mayer [buildd]
> yesterday but worked on eder [porterbox]. Afaict both were using the
> same up to date toolchain.

I dist-upgraded the chroots this morning. For this reason I just
rescheduled a build, we will see if it works or not.



Andi


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

Bug#728151: libimobiledevice4: fails upgrade

[Andreas Henriksson]

Package: libimobiledevice4
Version: 1.1.5-1
Severity: serious
Justification: fails upgrade

Dear Maintainer,
When upgrading my system I ran into a problem in libimobiledevice4 (1.1.5-1)
which seems to try to replace file(s) in libimobiledevice2 without declaring
a Replaces (and Breaks) directive.



(Reading database ... 323856 files and directories currently installed.)
Unpacking libimobiledevice4:amd64 (from 
.../libimobiledevice4_1.1.5-1_amd64.deb) ...
dpkg: error processing 
/var/cache/apt/archives/libimobiledevice4_1.1.5-1_amd64.deb (--unpack):
 trying to overwrite 
'/usr/share/hal/fdi/information/20thirdparty/31-apple-mobile-device.fdi', which 
is also in package libimobiledevice2 1.1.1-4
Errors were encountered while processing:
 /var/cache/apt/archives/libimobiledevice4_1.1.5-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
dpkg: dependency problems prevent configuration of libimobiledevice-dev:
 libimobiledevice-dev depends on libimobiledevice4 (= 1.1.5-1); however:
  Package libimobiledevice4:amd64 is not installed.

dpkg: error processing libimobiledevice-dev (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 libimobiledevice-dev



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

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

Versions of packages libimobiledevice4 depends on:
ii  libc6  2.17-93
ii  libgcrypt111.5.3-2
ii  libgnutls262.12.23-8
ii  libplist1  1.10-1
ii  libtasn1-3 2.14-3
ii  libusbmuxd21.0.8-2
ii  multiarch-support  2.17-93
ii  usbmuxd1.0.8-2

libimobiledevice4 recommends no packages.

libimobiledevice4 suggests no packages.


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

Bug#720519: marked as done (xen-tools: FTBFS with perl 5.18: POD failure)

[Debian Bug Tracking System]

Your message dated Mon, 28 Oct 2013 22:34:31 +
with message-id 
and subject line Bug#720519: fixed in xen-tools 4.4~rc1-1
has caused the Debian Bug report #720519,
regarding xen-tools: FTBFS with perl 5.18: POD failure
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.)


-- 
720519: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xen-tools
Version: 4.3.1-1
Severity: serious
Justification: transition imminent
User: debian-p...@lists.debian.org
Usertags: perl-5.18-transition
Tags: sid jessie

This package FTBFS with perl 5.18:

cd bin; for i in *-*[!y]; do pod2man --release=4.3.1 --official --section=8 $i 
../man/$i.8; done
xen-create-image around line 758: Non-ASCII character seen before =encoding in 
'Stphane'. Assuming UTF-8
POD document had syntax errors at /usr/bin/pod2man line 71.
xen-create-nfs around line 90: Non-ASCII character seen before =encoding in 'St
phane'. Assuming UTF-8
POD document had syntax errors at /usr/bin/pod2man line 71.
xen-delete-image around line 137: Non-ASCII character seen before =encoding in 
'Stphane'. Assuming UTF-8
POD document had syntax errors at /usr/bin/pod2man line 71.
xen-list-images around line 64: Non-ASCII character seen before =encoding in 
'Stphane'. Assuming UTF-8
POD document had syntax errors at /usr/bin/pod2man line 71.
xen-update-image around line 87: Non-ASCII character seen before =encoding in 
'Stphane'. Assuming UTF-8
POD document had syntax errors at /usr/bin/pod2man line 71.
xt-create-xen-config around line 111: Non-ASCII character seen before =encoding 
in 'Stphane'. Assuming UTF-8
POD document had syntax errors at /usr/bin/pod2man line 71.
xt-customize-image around line 67: Non-ASCII character seen before =encoding in 
'Stphane'. Assuming UTF-8
POD document had syntax errors at /usr/bin/pod2man line 71.
xt-guess-suite-and-mirror around line 36: Non-ASCII character seen before 
=encoding in 'Stphane'. Assuming UTF-8
POD document had syntax errors at /usr/bin/pod2man line 71.
xt-install-image around line 89: Non-ASCII character seen before =encoding in 
'Stphane'. Assuming UTF-8
POD document had syntax errors at /usr/bin/pod2man line 71.
make[1]: *** [manpages] Error 255
make[1]: Leaving directory 
`/build/dom-xen-tools_4.3.1-1-i386-ICpQI7/xen-tools-4.3.1'
make: *** [install] Error 2


Please ask debian-p...@lists.debian.org if you need help with preparing
or testing a change; if you have a suitable test i386 system you can
install perl 5.18 by adding experimental to your sources as well as the
repository at 

You can also find more about the perl 5.18 transition, which we hope
to start this week[1], at .

Thanks for your work!

Cheers,
Dominic.

[1] apologies for the late appearance of this bug report; earlier
test coverage did not cover this package
--- End Message ---
--- Begin Message ---
Source: xen-tools
Source-Version: 4.4~rc1-1

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated xen-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 28 Oct 2013 22:31:03 +0100
Source: xen-tools
Binary: xen-tools
Architecture: source all
Version: 4.4~rc1-1
Distribution: unstable
Urgency: low
Maintainer: Axel Beckert 
Changed-By: Axel Beckert 
Description: 
 xen-tools  - Tools to manage Xen virtual servers
Closes: 703159 704878 720519 725192
Changes: 
 xen-tools (4.4~rc1-1) unstable; urgency=low
 .
   * New upstream release candidate
 - Also switch from cdn.debian.net to http.debian.net in xen-tools.conf
 - Do not run "passwd" via runCommand as that one captures STDOUT for
   logging. Makes --passwd usable again. Thanks to Christian Herzog for
   the bug report.
 - Loop around calling "passwd" to get a second chance to change the
   password. (Closes: #703159) Thanks to Joan  for a
   bug fix in this new code

Bug#727666: marked as done (FTBFS: mipsel-linux-gnu-gcc: internal compiler error: Killed (program cc1plus))

[Debian Bug Tracking System]

Your message dated Mon, 28 Oct 2013 23:16:30 +0100
with message-id <20131028221630.ga12...@volta.rr44.fr>
and subject line Re: FTBFS: mipsel-linux-gnu-gcc: internal compiler error: 
Killed (program cc1plus)
has caused the Debian Bug report #727666,
regarding FTBFS: mipsel-linux-gnu-gcc: internal compiler error: Killed (program 
cc1plus)
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.)


-- 
727666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pytango
Version: 8.0.3-3
Severity: critical
File: pytango


Here the log message during the build on mayer.

/«PKGBUILDDIR»/src/boost/cpp/server/attribute.cpp: In function 'void 
PyAttribute::__set_value_date_quality_array(Tango::Attribute&, 
boost::python::api::object&, double, Tango::AttrQuality*, long int*, long int*, 
const string&, bool)':
/«PKGBUILDDIR»/src/boost/cpp/server/attribute.cpp:267:64: warning: typedef 
'TangoArrayType' locally defined but not used [-Wunused-local-typedefs]
 typedef typename TANGO_const2arraytype(tangoTypeConst) TangoArrayType;
^
mipsel-linux-gnu-gcc: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.
error: command 'mipsel-linux-gnu-gcc' failed with exit status 4


I rebuilt it on eder (porter box), (attached the non-FTBFS build log).


what is wrong with mayer ?

cheers

Frederic

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

Kernel: Linux 3.11-1-486
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-pytango depends on:
ii  ipython   0.13.2-2
ii  libboost-python1.54.0 1.54.0-3
ii  libc6 2.17-93
ii  libcos4-1 4.1.6-2
ii  libgcc1   1:4.8.2-1
ii  liblog4tango5 8.1.2c+dfsg-1
ii  libomniorb4-1 4.1.6-2
ii  libomnithread3c2  4.1.6-2
ii  libstdc++64.8.2-1
ii  libtango8 8.1.2c+dfsg-1
ii  libzmq3   3.2.4+dfsg-1
ii  python2.7.5-5
ii  python-numpy [python-numpy-abi9]  1:1.7.1-3

python-pytango recommends no packages.

python-pytango suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, Oct 25, 2013 at 08:37:44AM +0200, Picca Frédéric-Emmanuel wrote:
> Package: python-pytango
> Version: 8.0.3-3
> Severity: critical
> File: pytango
> 
> 
> Here the log message during the build on mayer.
> 
> /«PKGBUILDDIR»/src/boost/cpp/server/attribute.cpp: In function 'void 
> PyAttribute::__set_value_date_quality_array(Tango::Attribute&, 
> boost::python::api::object&, double, Tango::AttrQuality*, long int*, long 
> int*, const string&, bool)':
> /«PKGBUILDDIR»/src/boost/cpp/server/attribute.cpp:267:64: warning: typedef 
> 'TangoArrayType' locally defined but not used [-Wunused-local-typedefs]
>  typedef typename TANGO_const2arraytype(tangoTypeConst) 
> TangoArrayType;
> ^
> mipsel-linux-gnu-gcc: internal compiler error: Killed (program cc1plus)
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See  for instructions.
> error: command 'mipsel-linux-gnu-gcc' failed with exit status 4
> 
> 
> I rebuilt it on eder (porter box), (attached the non-FTBFS build log).
> 
> 
> what is wrong with mayer ?
> 

The problem here is that cc1plus is killed due to OOM. mayer only has
512MB of swap for historical reasons. Until a solution is found to add
more swap, pytango is blacklisted on this build daemon.

It has been built fine after a requeue, I am therefore closing the bug.

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

Bug#727009: FTBFS on kfreebsd-i386: FAIL: test-pangocairo-threads

[Steven Chamberlain]

On 28/10/13 14:33, Emilio Pozuelo Monfort wrote:
> The test is trying to create 100 threads, but pthread_create returns EAGAIN
> because it hits some limit, which makes g_thread_new() abort (as stated in the
> docs, g_thread_try_new() wouldn't abort but return NULL).
> 
> The question is, why are we hitting the limit so soon here?

Not sure yet but this reminds me of bug #725516:
>> lbzip2: unable to create a POSIX thread: Resource temporarily unavailable

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: tagging 727774

[Debian Bug Tracking System]

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

> # udeb_configure_flags re-added to the debian/rules
> tags 727774 + pending
Bug #727774 [dbus-udeb] dbus-udeb/experimental: depends on non-udeb packages
Added tag(s) pending.
> thanks
Stopping processing here.

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

[Debian Bug Tracking System]

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

> tags 722136 + fixed-upstream
Bug #722136 [postgrey] postgrey fails to start with perl-base 5.18.1-3
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
722136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722136
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#725532: marked as done (ruby-augeas: FTBFS: ERROR: Test "ruby1.9.1" failed.)

[Debian Bug Tracking System]

Your message dated Mon, 28 Oct 2013 23:33:31 +
with message-id 
and subject line Bug#725532: fixed in ruby-augeas 0.5.0-2
has caused the Debian Bug report #725532,
regarding ruby-augeas: FTBFS: ERROR: Test "ruby1.9.1" failed.
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.)


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

Hi,

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

Relevant part (hopefully):
>  76: 
>  77: def test_transform
>   => 78: aug = aug_open(Augeas::NO_LOAD)
>  79: aug.clear_transforms
>  80: aug.transform(:lens => "Hosts.lns",
>  81:   :incl => "/etc/hosts")
> ===
> 
> 
> Finished in 0.084067617 seconds.
> 
> 21 tests, 1 assertions, 0 failures, 20 errors, 0 pendings, 0 omissions, 0 
> notifications
> 4.7619% passed
> 
> 249.80 tests/s, 11.90 assertions/s
> ERROR: Test "ruby1.9.1" failed.

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/10/06/ruby-augeas_0.5.0-1_unstable.log

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

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

We believe that the bug you reported is fixed in the latest version of
ruby-augeas, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 725...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-augeas 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, 28 Oct 2013 23:52:49 +0100
Source: ruby-augeas
Binary: ruby-augeas libaugeas-ruby libaugeas-ruby1.8 libaugeas-ruby1.9.1
Architecture: source amd64 all
Version: 0.5.0-2
Distribution: unstable
Urgency: low
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Description: 
 libaugeas-ruby - Transitional package for ruby-augeas
 libaugeas-ruby1.8 - Transitional package for ruby-augeas
 libaugeas-ruby1.9.1 - Transitional package for ruby-augeas
 ruby-augeas - Augeas bindings for the Ruby language
Closes: 725532
Changes: 
 ruby-augeas (0.5.0-2) unstable; urgency=low
 .
   * Team upload
   * Add do_not_modify_loadpath_in_tests.patch, in order to
 use the correct extension in tests (Closes: #725532)
   * Build against gem2deb >= 0.5 to add support for Ruby 2.0 and drop support
 for Ruby 1.8
   * debian/rules:
 + no need to ignore test failures with Ruby1.8 since this version is no
   longer supported by gem2deb >= 0.5
 + install NEWS as upstream changelog
 + delete build/ when cleaning
   * Add lintian overrides for duplicate description of transitional packages
   * Convert copyright file to copyright-format/1.0
   * Bump Standards-Version to 3.9.5 (no changes needed)
Checksums-Sha1: 
 6706a841ff565c7b4b369b570f450bffe08970f1 2256 ruby-augeas_0.5.0-2.dsc
 9bcee2b5547101b08dee92298b254acb58661254 3112 ruby-augeas_0.5.0-2.debian.tar.gz
 8a38e5b856b0b8e39855d2042ddaccb47217770c 11554 ruby-augeas_0.5.0-2_amd64.deb
 93c9e1b8fefbea3940ec260d974899012f346fd5 3464 libaugeas-ruby_0.5.0-2_all.deb
 cd70173e538aab7c19d94e755d7e7c206325a7f2 3468 libaugeas-ruby1.8_0.5.0-2_all.deb
 c1540e5b0f131e82f9647085310211cd6b28cb03 3468 
libaugeas-ruby1.9.1_0.5.0-2_all.deb
Checksums-Sha256: 
 11238c8665e0da444840e1e16e7e164f0c7c29b26973606379be9f1d514a5370 2256 
ruby-augeas_0.5.0-2.dsc
 ef8edbda1a30ca4b88fe172dae3633f89ba007207b15310f19c609bb27687786 3112 
ruby-augeas_0.5.0-2.debian.tar.gz
 4aa8063263f1c22f07d8e750c1d2b4b2e2

Bug#713240: marked as done (ebview: FTBFS: configure: error: Package requirements (pangox) were not met:)

[Debian Bug Tracking System]

Your message dated Mon, 28 Oct 2013 23:33:19 +
with message-id 
and subject line Bug#713240: fixed in ebview 0.3.6.2-1.3
has caused the Debian Bug report #713240,
regarding ebview: FTBFS: configure: error: Package requirements (pangox) were 
not met:
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.)


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

Hi,

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

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> if test -e /usr/share/misc/config.guess ; then \
>   for i in ./config.guess ; do \
>   if ! test -e $i.cdbs-orig ; then \
>   mv $i $i.cdbs-orig ; \
>   cp --remove-destination 
> /usr/share/misc/config.guess $i ; \
>   fi ; \
>   done ; \
>   fi
> if test -e /usr/share/misc/config.sub ; then \
>   for i in ./config.sub ; do \
>   if ! test -e $i.cdbs-orig ; then \
>   mv $i $i.cdbs-orig ; \
>   cp --remove-destination 
> /usr/share/misc/config.sub $i ; \
>   fi ; \
>   done ; \
>   fi
> make[1]: Leaving directory `/«PKGBUILDDIR»'
> if test -e /usr/share/misc/config.guess ; then \
>   for i in ./config.guess ; do \
>   if ! test -e $i.cdbs-orig ; then \
>   mv $i $i.cdbs-orig ; \
>   cp --remove-destination 
> /usr/share/misc/config.guess $i ; \
>   fi ; \
>   done ; \
>   fi
> if test -e /usr/share/misc/config.sub ; then \
>   for i in ./config.sub ; do \
>   if ! test -e $i.cdbs-orig ; then \
>   mv $i $i.cdbs-orig ; \
>   cp --remove-destination 
> /usr/share/misc/config.sub $i ; \
>   fi ; \
>   done ; \
>   fi
> touch debian/stamp-autotools-files
> chmod a+x /«PKGBUILDDIR»/./configure
> mkdir -p .
> cd . &&   CFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
> -Werror=format-security -Wall" CXXFLAGS="-g -O2 -fstack-protector 
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall" 
> CPPFLAGS="-D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro" 
> /«PKGBUILDDIR»/./configure --build=x86_64-linux-gnu  --prefix=/usr 
> --includedir="\${prefix}/include" --mandir="\${prefix}/share/man" 
> --infodir="\${prefix}/share/info" --sysconfdir=/etc --localstatedir=/var 
> --libexecdir="\${prefix}/lib/ebview" --srcdir=. --disable-maintainer-mode 
> --disable-dependency-tracking --disable-silent-rules   --sysconfdir=/etc 
> configure: WARNING: unrecognized options: --disable-maintainer-mode, 
> --disable-silent-rules
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking for style of include used by make... GNU
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables... 
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking dependency style of gcc... none
> checking how to run the C preprocessor... gcc -E
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking locale.h usability... yes
> checking locale.h presence... yes
> checking for locale.h... yes
> checking for LC_MESSAGES... yes
> checking libintl.h usability... yes
> checking libintl.h presence...

Bug#726472: [Pkg-samba-maint] Bug#726472: share passwords not working after upgrade from samba3

[Jelmer Vernooij]

On Mon, Oct 28, 2013 at 10:00:12PM +0100, Ivo De Decker wrote:
> Hi,
> 
> On Mon, Oct 21, 2013 at 10:37:49PM +1300, Andrew Bartlett wrote:
> > > Ok.  I think we need to undo this /var/lib/samba/private nonsense.  It is 
> > > a
> > > pointless and imperfect migration (as shown by this bug report), and the
> > > only rationale upstream ever gave for keeping these files in a separate
> > > "private" directory is some stupid and ancient target OS that couldn't
> > > properly set per-file permissions.  Debian users have been using
> > > /var/lib/samba exclusively for the better part of a decade; migrating to
> > > this private/ directory adds no value for our users.
> > 
> > In the alternate, the only reason this happened now is because we are
> > finally having the Debian packages follow where upstream has decided to
> > put the files.  Having different packages moving files around to
> > different places only increases user confusion, and creates 'only on
> > Debian' bugs.  
> > 
> > For example, a significant number of issues came about as folks tried to
> > divine if a particular TDB was short, medium or long-term, when no such
> > separation existed in the code. 
> > 
> > We (upstream) have gone to significant effort to integrate the FHS
> > changes that have been proposed via Debian, I can only ask that having
> > got to a mutually agreed state, that Debian not change it again, having
> > once more Debian packages special and different. 
> 
> I had a long talk with Jelmer yesterday about this bug. Here are a number of
> considerations from that discussion:
> 
> 
> First of all, it certainly isn't clear that the issue is caused by a mistake
> in unstable some time ago. I haven't been able to find any indication for that
> (yet) in any of the samba versions available on snapshot.debian.org. We've
> been using /etc/samba as private dir from the first 3.2 upload to the last 3.6
> upload and there is no apparent usage of /var/lib/samba/private anywhere in
> the code of any of these versions.
> 
> It is quite possible that the issue is triggered by a race condition in the
> tdb-handling (especially for passdb.tdb), which can result in the creation of
> the wrong tdb file during the upgrade, which messes up our move. This could be
> caused by the usage of the 'smbpasswd' command or the pam-smbpass pam module.
> I haven't had the time yet to create a situation where I can trigger the race
> condition.
> 
> There are a number of ways to work around these possible race conditions
> during at the time of the move. An incomplete list of ideas (some of these
> would have to be combined to get to a complete fix):
> 
> - Patch the passdb tdb module to do the move, instead of having it in
>   samba.postinst. This isn't completely unprecedented, as the move of
>   MACHINE.SID was supported by the samba code.
> 
> - Track the fact that the move was done, by adding some field to the new tdb
>   file. This might cause issues in tools that don't handle unknown fields. The
>   samba4 upgrade script might be one of those.
> 
> - Track the fact that the move was done, by making sure the old tdb can't be
>   used anymore. This could be done by changing the version number of the old
>   tdb to something non-existent.
> 
> - Do some kind of merge of both tdb files, if they both exist.
> 
> - When both tdb files exist, have a debconf question that gives some
>   information about both (eg number of users), and ask the user to choose
>   between them.
> 
> Any decent implementation will require some careful planning and probably
> quite some discussion as well. It is clear that the new samba 4.x packages
> provide a nice step forward compared to the samba 3.6 packages, and these
> changes shouldn't be blocked by this problem. Therefore we are proposing to
> postpone this move for now.
> 
> Moving the private dir to /var/lib/samba would cause an issue with the files
> kept by samba4 in /var/lib/samba/private. So the only obvious way forward
> would be to have a new version of our previous patch, which moves the 4
> affected files back to /var/lib/samba. I really regret having to propose this,
> as I very much would like to avoid reintroducing a patch like that, but at
> this point, I don't really see any other short term options.

> So the proposal is to reintroduce something like the old patch, and try to get
> that version into shape for testing/jessie. After that, we can figure out how
> to get this move done the right way.

An alternative solution might be to just move those four files that
already existed back in 3.x back from privatedir to sysstatedir and
to not revert the entire move to privatedir.

That'll also cause some confusion though, as those files will be in
sysstatedir on debian but in privatedir on other systems...

Cheers,

Jelmer


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

Bug#726472: share passwords not working after upgrade from samba3

[Jelmer Vernooij]

On Tue, Oct 29, 2013 at 10:10:58AM +1300, Andrew Bartlett wrote:
> On Mon, 2013-10-28 at 22:00 +0100, Ivo De Decker wrote:
> > Hi,
> > 
> > On Mon, Oct 21, 2013 at 10:37:49PM +1300, Andrew Bartlett wrote:
> > > > Ok.  I think we need to undo this /var/lib/samba/private nonsense.  It 
> > > > is a
> > > > pointless and imperfect migration (as shown by this bug report), and the
> > > > only rationale upstream ever gave for keeping these files in a separate
> > > > "private" directory is some stupid and ancient target OS that couldn't
> > > > properly set per-file permissions.  Debian users have been using
> > > > /var/lib/samba exclusively for the better part of a decade; migrating to
> > > > this private/ directory adds no value for our users.
> > > 
> > > In the alternate, the only reason this happened now is because we are
> > > finally having the Debian packages follow where upstream has decided to
> > > put the files.  Having different packages moving files around to
> > > different places only increases user confusion, and creates 'only on
> > > Debian' bugs.  
> > > 
> > > For example, a significant number of issues came about as folks tried to
> > > divine if a particular TDB was short, medium or long-term, when no such
> > > separation existed in the code. 
> > > 
> > > We (upstream) have gone to significant effort to integrate the FHS
> > > changes that have been proposed via Debian, I can only ask that having
> > > got to a mutually agreed state, that Debian not change it again, having
> > > once more Debian packages special and different. 
> > 
> > I had a long talk with Jelmer yesterday about this bug. Here are a number of
> > considerations from that discussion:
> > 
> > 
> > First of all, it certainly isn't clear that the issue is caused by a mistake
> > in unstable some time ago. I haven't been able to find any indication for 
> > that
> > (yet) in any of the samba versions available on snapshot.debian.org. We've
> > been using /etc/samba as private dir from the first 3.2 upload to the last 
> > 3.6
> > upload and there is no apparent usage of /var/lib/samba/private anywhere in
> > the code of any of these versions.
> > 
> > It is quite possible that the issue is triggered by a race condition in the
> > tdb-handling (especially for passdb.tdb), which can result in the creation 
> > of
> > the wrong tdb file during the upgrade, which messes up our move. This could 
> > be
> > caused by the usage of the 'smbpasswd' command or the pam-smbpass pam 
> > module.
> > I haven't had the time yet to create a situation where I can trigger the 
> > race
> > condition.
> > 
> > There are a number of ways to work around these possible race conditions
> > during at the time of the move. An incomplete list of ideas (some of these
> > would have to be combined to get to a complete fix):
> > 
> > - Patch the passdb tdb module to do the move, instead of having it in
> >   samba.postinst. This isn't completely unprecedented, as the move of
> >   MACHINE.SID was supported by the samba code.
> > 
> > - Track the fact that the move was done, by adding some field to the new tdb
> >   file. This might cause issues in tools that don't handle unknown fields. 
> > The
> >   samba4 upgrade script might be one of those.
> > 
> > - Track the fact that the move was done, by making sure the old tdb can't be
> >   used anymore. This could be done by changing the version number of the old
> >   tdb to something non-existent.
> > 
> > - Do some kind of merge of both tdb files, if they both exist.
> > 
> > - When both tdb files exist, have a debconf question that gives some
> >   information about both (eg number of users), and ask the user to choose
> >   between them.
> > 
> > Any decent implementation will require some careful planning and probably
> > quite some discussion as well. It is clear that the new samba 4.x packages
> > provide a nice step forward compared to the samba 3.6 packages, and these
> > changes shouldn't be blocked by this problem. Therefore we are proposing to
> > postpone this move for now.
> > 
> > Moving the private dir to /var/lib/samba would cause an issue with the files
> > kept by samba4 in /var/lib/samba/private. So the only obvious way forward
> > would be to have a new version of our previous patch, which moves the 4
> > affected files back to /var/lib/samba. I really regret having to propose 
> > this,
> > as I very much would like to avoid reintroducing a patch like that, but at
> > this point, I don't really see any other short term options.
> > 
> > So the proposal is to reintroduce something like the old patch, and try to 
> > get
> > that version into shape for testing/jessie. After that, we can figure out 
> > how
> > to get this move done the right way.
> > 
> > Any thoughts, comments?
> > 
> > > Or in the alternate, propose such changes upstream. 
> > 
> > Moving the files upstream would inflict all this pain on other 
> > distributions,
> > so someone would still have to sort this all 

Bug#728155: php5-svn: install, remove, install makes /etc/php5/mods-available/svn.ini disappear

[Andreas Beckmann]

Package: php5-svn
Version: 1.0.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install,
remove (but not purge), and install again.
Before the second installation the package is in config-files-remaining
state. The configuration is remaining from the last version that was
successfully configured - which is the same version that is going to be
installed again.

There is no error during the second installation, but one of the
package's conffiles disappears: /etc/php5/mods-available/svn.ini

Like a plain failure on initial install this makes the package too buggy
for a release, thus the severity.

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

0m24.1s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /etc/php5/mods-available/svn.ini (from php5-svn package)


cheers,

Andreas


php5-svn_1.0.2-1.log.gz
Description: GNU Zip compressed data

Bug#726530: fvwm: random segfault

[Steve Cotton]

On Thu, Oct 17, 2013 at 10:23 +0100, Luke Kenneth Casson Leighton wrote:
> On Thu, Oct 17, 2013 at 2:26 AM, Vincent W. Chen  wrote:
> > I tried grepping for munmap_chunk() in the fvwm source but found nothing.
> 
>  yehh i have this suspicion it's in the x11 libraries somewhere - feel
> free to move this bug around if more appropriate.

munmap_chunk() is part of libc's free()/realloc()/malloc().

That error message seems mean memory corruption, but AFAICS in
bookkeeping data stored just before the start of the memory being
free()'d.

> fvwm when run continuously 24x7 for
> more than 2 months doesn't interact well with screensavers, so i don't
> use them.

Screensavers not locking sounds like a bug that should be fixed,
and it might be easier than this bug.

Steve


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

Bug#727009: FTBFS on kfreebsd-i386: FAIL: test-pangocairo-threads

[Emilio Pozuelo Monfort]

On 28/10/13 23:49, Steven Chamberlain wrote:
> On 28/10/13 14:33, Emilio Pozuelo Monfort wrote:
>> The test is trying to create 100 threads, but pthread_create returns EAGAIN
>> because it hits some limit, which makes g_thread_new() abort (as stated in 
>> the
>> docs, g_thread_try_new() wouldn't abort but return NULL).
>>
>> The question is, why are we hitting the limit so soon here?
> 
> Not sure yet but this reminds me of bug #725516:
>>> lbzip2: unable to create a POSIX thread: Resource temporarily unavailable

Indeed, looks very similar. It's also failing consistently when ran as `make
check' but works most of the time when invoked directly.

FWIW we run autoreconf at the beginning of the build so we're using latest
automake as available in Debian (1.14 in this case).


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

Bug#728157: trove-guestagent: fails to install: chown: invalid user: 'trove-guestagent.conf:trove-guestagent.conf'

[Andreas Beckmann]

Package: trove-guestagent
Version: 2013.2~rc1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package trove-guestagent.
  (Reading database ... 15406 files and directories currently installed.)
  Unpacking trove-guestagent (from .../trove-guestagent_2013.2~rc1-1_all.deb) 
...
  Setting up trove-guestagent (2013.2~rc1-1) ...
  chown: invalid user: 'trove-guestagent.conf:trove-guestagent.conf'
  dpkg: error processing trove-guestagent (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   trove-guestagent


cheers,

Andreas


trove-guestagent_2013.2~rc1-1.log.gz
Description: GNU Zip compressed data

Processed: spacefm-common: fails to upgrade from 'testing' - trying to overwrite /usr/share/spacefm/ui/prefdlg2.ui

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + spacefm-gtk3
Bug #728158 [spacefm-common] spacefm-common: fails to upgrade from 'testing' - 
trying to overwrite /usr/share/spacefm/ui/prefdlg2.ui
Added indication that 728158 affects spacefm-gtk3

-- 
728158: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728158
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#728158: spacefm-common: fails to upgrade from 'testing' - trying to overwrite /usr/share/spacefm/ui/prefdlg2.ui

[Andreas Beckmann]

Package: spacefm-common
Version: 0.9.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + spacefm-gtk3

Hi,

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

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

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

  Preparing to replace spacefm-common 0.8.7-3 (using 
.../spacefm-common_0.9.0-1_all.deb) ...
  Unpacking replacement spacefm-common ...
  dpkg: error processing /var/cache/apt/archives/spacefm-common_0.9.0-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/spacefm/ui/prefdlg2.ui', which is also in 
package spacefm-gtk3 0.8.7-3
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Preparing to replace spacefm-gtk3 0.8.7-3 (using 
.../spacefm-gtk3_0.9.0-1_amd64.deb) ...
  Unpacking replacement spacefm-gtk3 ...
  Processing triggers for desktop-file-utils ...
  Errors were encountered while processing:
   /var/cache/apt/archives/spacefm-common_0.9.0-1_all.deb

cheers,

Andreas


spacefm-gtk3_0.9.0-1.log.gz
Description: GNU Zip compressed data

Bug#728163: python-txlibravatar: fails to upgrade from 'testing' - trying to overwrite /usr/lib/python2.7/dist-packages/txLibravatar-1.1.egg-info

[Andreas Beckmann]

Package: python-txlibravatar
Version: 1.1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Unpacking python-txlibravatar (from .../python-txlibravatar_1.1-5_all.deb) ...
  dpkg: error processing 
/var/cache/apt/archives/python-txlibravatar_1.1-5_all.deb (--unpack):
   trying to overwrite 
'/usr/lib/python2.7/dist-packages/txLibravatar-1.1.egg-info', which is also in 
package python-twisted-libravatar 1.1-3
  Errors were encountered while processing:
   /var/cache/apt/archives/python-txlibravatar_1.1-5_all.deb

cheers,

Andreas


python-twisted-libravatar=1.1-3_python-txlibravatar=1.1-5.log.gz
Description: GNU Zip compressed data

Bug#728164: ceph-fs-common, ceph-mds: fails to upgrade from 'testing' - trying to overwrite /sbin/mount.ceph, /usr/bin/ceph-mds

[Andreas Beckmann]

Package: ceph-fs-common,ceph-mds
Version: 0.67.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package ceph-fs-common.
  (Reading database ... 6954 files and directories currently installed.)
  Unpacking ceph-fs-common (from .../ceph-fs-common_0.67.3-1_amd64.deb) ...
  dpkg: error processing 
/var/cache/apt/archives/ceph-fs-common_0.67.3-1_amd64.deb (--unpack):
   trying to overwrite '/sbin/mount.ceph', which is also in package ceph-common 
0.48-2
  Errors were encountered while processing:
   /var/cache/apt/archives/ceph-fs-common_0.67.3-1_amd64.deb

  Selecting previously unselected package ceph-mds.
  Unpacking ceph-mds (from .../ceph-mds_0.67.3-1_amd64.deb) ...
  dpkg: error processing /var/cache/apt/archives/ceph-mds_0.67.3-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/ceph-mds', which is also in package ceph 0.48-2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Selecting previously unselected package sdparm.
  Unpacking sdparm (from .../sdparm_1.07-1_amd64.deb) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/ceph-mds_0.67.3-1_amd64.deb


cheers,

Andreas


ceph-common=0.48-2_ceph-fs-common=0.67.3-1.log.gz
Description: GNU Zip compressed data

Bug#725091: [Pkg-openldap-devel] Bug#725091: Bug#725091: slapd with memory leak in active sync

[Quanah Gibson-Mount]

--On Friday, October 18, 2013 1:39 PM +0200 Thomas Sesselmann 
 wrote:




This would be the best option for us. Did you know when a new
upstream version in unstable or experimental would be released?

Until this we have to try to build our own package at 2.4.36
(the first trial is failed).


2.4.37 was released on Sunday.

I would note that other people have had success building on ubuntu12 with:

18:05]  i use checkinstall > ./configure . ; make depend ; make 
; sudo checkinstall -D --showinstall --pkgname=openldap --maintainer= 
--pkgversion=2.4.37 --pkgrelease=1 --pkglicense=GPL --pkggroup=checkinstall 
--requires=make,automake,gcc,libtool,libperl-dev,libdb5.1-dev,libssl-dev,libsasl2-dev

[18:06]  it's easy to use
[18:09]  and i modified 2 files from slapd debian package: 
/etc/default/slapd & /etc/init.d/slapd to have "/usr/local". and then " 
update-rc.d slapd defaults"

[18:09]  and nothing else

You would of course need to use the configure options most relevant to you.


--Quanah

--

Quanah Gibson-Mount
Architect - Server
Zimbra, Inc.

Zimbra ::  the leader in open source messaging and collaboration


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

Bug#728165: lmdb-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man3/mdb_node.3.gz

[Andreas Beckmann]

Package: lmdb-doc
Version: 0.9.9-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package lmdb-doc.
  Unpacking lmdb-doc (from .../lmdb-doc_0.9.9-1_all.deb) ...
  dpkg: error processing /var/cache/apt/archives/lmdb-doc_0.9.9-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/man/man3/mdb_node.3.gz', which is also in 
package liblmdb-dev:amd64 0.9.7-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/lmdb-doc_0.9.9-1_all.deb


cheers,

Andreas


liblmdb-dev=0.9.7-1_lmdb-doc=0.9.9-1.log.gz
Description: GNU Zip compressed data

Bug#728170: contains undocumented licenses

[Paul Tagliamonte]

Package: liblttng-ust2
Severity: serious
User: paul...@debian.org
Usertags: ftp
X-Debbugs-CC: ftpmas...@ftp-master.debian.org
thanks

From an ftp-team trainee::

lttng-ust-2.3.0\liblttng-ust-ctl\ustctl.c  is GPL2 and not mentioned in
debian/copyright
lttng-ust-2.3.0\doc\examples\demo\tp*.c is not LGPL2.1+
lttng-ust-2.3.0\doc\examples\demo\ust* is not LGPL2.1+
  as well as most of the files in doc/examples

lttng-ust-2.3.0\include\lttng\* has the same problem


Thanks for your work!
  Paul


-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Processed: reassign 728170 to ust

[Debian Bug Tracking System]

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

> reassign 728170 ust
Bug #728170 [liblttng-ust2] contains undocumented licenses
Warning: Unknown package 'liblttng-ust2'
Bug reassigned from package 'liblttng-ust2' to 'ust'.
Ignoring request to alter found versions of bug #728170 to the same values 
previously set
Ignoring request to alter fixed versions of bug #728170 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
728170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728170
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#728171: plexus-containers1.5: FTBFS: Compilation errors (incompatible types)

[Daniel Schepler]

Source: plexus-containers1.5
Version: 1.5.5-5
Severity: serious

>From my pbuilder build log:

...
mvn-generate:

mvn-generate2:

compile:
[mkdir] Created dir: 
/tmp/buildd/plexus-containers1.5-1.5.5/plexus-container-default/target/generated-sources
[javac] /usr/share/maven-ant-helper/maven-build.xml:337: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Compiling 179 source files to 
/tmp/buildd/plexus-containers1.5-1.5.5/plexus-container-default/target/classes
[javac] 
/tmp/buildd/plexus-containers1.5-1.5.5/plexus-container-default/src/main/java/org/codehaus/plexus/component/repository/ComponentDescriptor.java:192:
 error: incompatible types
[javac] roleClass = getRealm().loadClass( getRole() );
[javac] ^
[javac]   required: Class
[javac]   found:Class
[javac]   where T is a type-variable:
[javac] T extends Object declared in class ComponentDescriptor
[javac]   where CAP#1 is a fresh type-variable:
[javac] CAP#1 extends Object from capture of ?
[javac] 
/tmp/buildd/plexus-containers1.5-1.5.5/plexus-container-default/src/main/java/org/codehaus/plexus/component/repository/ComponentDescriptor.java:302:
 error: incompatible types
[javac] implementationClass = getRealm().loadClass( 
getImplementation() );
[javac]   ^
[javac]   required: Class
[javac]   found:Class
[javac]   where T is a type-variable:
[javac] T extends Object declared in class ComponentDescriptor
[javac]   where CAP#1 is a fresh type-variable:
[javac] CAP#1 extends Object from capture of ?
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 2 errors

BUILD FAILED
/tmp/buildd/plexus-containers1.5-1.5.5/debian/build.xml:47: The following error 
occurred while executing this line:
/tmp/buildd/plexus-containers1.5-1.5.5/debian/build.xml:22: The following error 
occurred while executing this line:
/usr/share/maven-ant-helper/maven-build.xml:337: Compile failed; see the 
compiler error output for details.

Total time: 3 seconds
make: *** [debian/stamp-ant-build] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2


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

Bug#728172: ploop: FTBFS: libxml/parser.h: No such file or directory

[Aaron M. Ucko]

Source: ploop
Version: 1.9-2
Severity: serious
Justification: fails to build from source

Builds of ploop in minimal environments have been failing even when not
affected by architecture-specific issues (which I'll report separately):

xml.c:23:27: fatal error: libxml/parser.h: No such file or directory

Please declare a build dependency on libxml2-dev and confirm with pbuilder
or the like that no others are missing.

Thanks!


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

Bug#728173: ploop: FTBFS on non-x86: misses fallocate, syncfs syscall numbers

[Aaron M. Ucko]

Source: ploop
Version: 1.9-2
Severity: serious
Justification: fails to build from source

Builds of ploop on Linux architectures other than amd64 and i386 have
been failing:

  ploop.h:21:2: error: #error "No fallocate syscall known for this arch"
  ploop.h:31:2: error: #error "No syncfs syscall known for this arch"

Please try having ploop.h #include  to pick up system
definitions rather than relying on its fallbacks, defined only for x86.

Thanks!


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