Bug#732023: marked as done (libtk-img: undefined symbol TIFFReassignTagToIgnore in libtifftcl3.8.2.so)

[Debian Bug Tracking System]

Your message dated Sat, 14 Dec 2013 06:18:42 +
with message-id 
and subject line Bug#732023: fixed in libtk-img 1:1.4.2-1
has caused the Debian Bug report #732023,
regarding libtk-img: undefined symbol TIFFReassignTagToIgnore in 
libtifftcl3.8.2.so
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.)


-- 
732023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732023
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtk-img
Version: 1:1.3-release-12+b1
Severity: grave
Justification: renders package unusable

Hi,

The saods9 programme fails to start with:

Error in startup script: couldn't load file 
"/usr/lib/tcltk/Img1.3/libtifftcl3.8.2.so": 
/usr/lib/tcltk/Img1.3/libtifftcl3.8.2.so: undefined symbol: 
TIFFReassignTagToIgnore
while executing
"load /usr/lib/tcltk/Img1.3/libtifftcl3.8.2.so"
("package ifneeded tifftcl 3.8.2" script)
invoked from within
"load /usr/lib/tcltk/Img1.3/libtkimgtiff1.3.so"
("package ifneeded img::tiff 1.3" script)
invoked from within
"package require img::tiff"
("x11" arm line 28)
invoked from within
"switch $ds9(wm) {
x11 {
# set to absolute path so that if -cd command is used,
# so we can still find our files
set ds9(root) "/usr/share/saods..."
(file "/usr/share/saods9/src/ds9.tcl" line 177)

This problem can also be seen using tclsh

% package require img::tiff
couldn't load file "/usr/lib/tcltk/Img1.3/libtifftcl3.8.2.so": 
/usr/lib/tcltk/Img1.3/libtifftcl3.8.2.so: undefined symbol: 
TIFFReassignTagToIgnore

Maybe it is related to the libtiff5 transition.

Regards,

Yannick

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

Kernel: Linux 3.12.4 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libtk-img depends on:
ii  libc6   2.17-97
ii  libfontconfig1  2.11.0-2
ii  libjpeg88d-2
ii  libpng12-0  1.2.49-5
ii  libtiff54.0.3-6
ii  libx11-62:1.6.2-1
ii  libxext62:1.3.2-1
ii  libxft2 2.3.1-1
ii  libxss1 1:1.2.2-1
ii  tk [wish]   8.6.0+6
ii  zlib1g  1:1.2.8.dfsg-1

libtk-img recommends no packages.

Versions of packages libtk-img suggests:
pn  libtk-img-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libtk-img
Source-Version: 1:1.4.2-1

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

Debian distribution maintenance software
pp.
Sergei Golovan  (supplier of updated libtk-img 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: Sat, 14 Dec 2013 09:56:27 +0400
Source: libtk-img
Binary: libtk-img libtk-img-dev libtk-img-doc
Architecture: source all amd64
Version: 1:1.4.2-1
Distribution: unstable
Urgency: low
Maintainer: Sergei Golovan 
Changed-By: Sergei Golovan 
Description: 
 libtk-img  - Extended image format support for Tcl/Tk (runtime)
 libtk-img-dev - Extended image format support for Tcl/Tk (development files)
 libtk-img-doc - Extended image format support for Tcl/Tk (manual pages)
Closes: 732023
Changes: 
 libtk-img (1:1.4.2-1) unstable; urgency=low
 .
   * New upstream release.
   * Refreshed patches, removed obsolete ones.
   * Use internal copy of the libtiff library because libtk-img doesn't work
 with the newer version which is currently in unstable (closes: #732023).
   * Use internal copy of the libpng library because upstream switched to 1.4
 while Debian have only 1.2 yet.
   * Don't install doc-base file because libtk-img doesn't come with HTML docs
 now.
   * Switched to 3.0 (quilt) source format and bumped debhelper compatibility
 level to 8.
   * Bumped standards version to 3.9.4.
Checksums-Sha1: 
 c5b99a3437508dab99e43bbc8a2eb243496ce2dd 1275 libtk-img_1.4.2-1.dsc
 9cbfa76dbd8eaaf20d6f99deb26841cc747bcb74 7257064 libtk-img_1.4.2.orig.tar.gz
 31ab67c0a13b

Bug#718272: Bitcoin still not ready for stable release in Debian

[Luke-Jr]

I agree with Scott's assessment, although I would note that Debian *does* have 
a suite that addresses the needs of Bitcoin: stable-updates. Mandatory 
protocol rule changes would seem to fall within the "broken by the flow of 
time" category. Thoughts?


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

Bug#732105: tor: Crash on startup: Error in `tor': free(): invalid pointer: 0x00007f0ad9db532b

[Linus Lüssing]

Package: tor
Version: 0.2.3.25-1
Severity: grave
Justification: renders package unusable

Hi,

When trying to start Tor with this command, so starting it with the
Debian default torrc:

$ tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc

... then I'm getting the following error message:

"Error in `tor': free(): invalid pointer: 0x7f0ad9db532b"

For the complete command line output, including a backtrace (the debug
symbols seem to be missing even though I've installed tor-dbg?), see the
attached log.

Cheers, Linus


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

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

Versions of packages tor depends on:
ii  adduser 3.113+nmu3
ii  libc6   2.17-95
ii  libevent-2.0-5  2.0.21-stable-1
ii  libssl1.0.0 1.0.1e-4
ii  lsb-base4.1+Debian12
ii  zlib1g  1:1.2.8.dfsg-1

Versions of packages tor recommends:
ii  logrotate3.8.6-1
ii  tor-geoipdb  0.2.3.25-1
ii  torsocks 1.3-3

Versions of packages tor suggests:
pn  apparmor-utils 
pn  mixmaster  
ii  privoxy3.0.21-1
ii  socat  1.7.2.2-1
pn  tor-arm
pn  xul-ext-torbutton  

-- Configuration Files:
/etc/default/tor changed [not included]
/etc/tor/torrc changed [not included]

-- debconf-show failed
$ tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc
Dec 14 04:28:30.938 [notice] Tor v0.2.3.25 (git-3fed5eb096d2d187) running on 
Linux.
Dec 14 04:28:30.938 [notice] Tor can't help you if you use it wrong! Learn how 
to be safe at https://www.torproject.org/download/download#warning
Dec 14 04:28:30.938 [notice] Read configuration file 
"/usr/share/tor/tor-service-defaults-torrc".
Dec 14 04:28:30.938 [notice] Read configuration file "/etc/tor/torrc".
Dec 14 04:28:30.960 [notice] We were compiled with headers from version 
2.0.19-stable of Libevent, but we're using a Libevent library that says it's 
version 2.0.21-stable.
Dec 14 04:28:30.960 [notice] Initialized libevent version 2.0.21-stable using 
method epoll (with changelist). Good.
Dec 14 04:28:30.960 [notice] Opening Socks listener on 127.0.0.1:9050
Dec 14 04:28:30.961 [notice] Opening DNS listener on 127.0.0.1:53535
Dec 14 04:28:30.961 [notice] Opening Transparent pf/netfilter listener on 
127.0.0.1:9040
Dec 14 04:28:30.962 [notice] Opening Control listener on /var/run/tor/control
*** Error in `tor': free(): invalid pointer: 0x7f0ad9db532b ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x7aa16)[0x7f0adaf26a16]
/lib/x86_64-linux-gnu/libc.so.6(+0x7b793)[0x7f0adaf27793]
tor(+0x178d2)[0x7f0adc64e8d2]
tor(+0x5ff7c)[0x7f0adc696f7c]
tor(+0x188c5)[0x7f0adc64f8c5]
tor(+0x18b11)[0x7f0adc64fb11]
tor(+0x18c8f)[0x7f0adc64fc8f]
tor(+0x19082)[0x7f0adc650082]
tor(+0x1e9ae)[0x7f0adc6559ae]
tor(+0x15809)[0x7f0adc64c809]
tor(+0x1706e)[0x7f0adc64e06e]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f0adaecd995]
tor(+0x119fd)[0x7f0adc6489fd]
=== Memory map: 
7f0ad9a92000-7f0ad9aa7000 r-xp  fe:18 647880 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f0ad9aa7000-7f0ad9ca7000 ---p 00015000 fe:18 647880 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f0ad9ca7000-7f0ad9ca8000 rw-p 00015000 fe:18 647880 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f0ad9ca8000-7f0ada156000 r--p  fe:16 921098 
/var/lib/tor/cached-microdescs
7f0ada156000-7f0ada357000 rw-p  00:00 0
7f0ada458000-7f0ada464000 r-xp  fe:18 647974 
/lib/x86_64-linux-gnu/libnss_files-2.17.so
7f0ada464000-7f0ada663000 ---p c000 fe:18 647974 
/lib/x86_64-linux-gnu/libnss_files-2.17.so
7f0ada663000-7f0ada664000 r--p b000 fe:18 647974 
/lib/x86_64-linux-gnu/libnss_files-2.17.so
7f0ada664000-7f0ada665000 rw-p c000 fe:18 647974 
/lib/x86_64-linux-gnu/libnss_files-2.17.so
7f0ada665000-7f0ada66f000 r-xp  fe:18 647976 
/lib/x86_64-linux-gnu/libnss_nis-2.17.so
7f0ada66f000-7f0ada86e000 ---p a000 fe:18 647976 
/lib/x86_64-linux-gnu/libnss_nis-2.17.so
7f0ada86e000-7f0ada86f000 r--p 9000 fe:18 647976 
/lib/x86_64-linux-gnu/libnss_nis-2.17.so
7f0ada86f000-7f0ada87 rw-p a000 fe:18 647976 
/lib/x86_64-linux-gnu/libnss_nis-2.17.so
7f0ada87-7f0ada885000 r-xp  fe:18 647970 
/lib/x86_64-linux-gnu/libnsl-2.17.so
7f0ada885000-7f0adaa84000 ---p 00015000 fe:18 647970 
/lib/x86_64-linux-gnu/libnsl-2.17.so
7f0adaa84000-7f0adaa85000 r--p 00014000 fe:18 647970 
/lib/x86_64-linux-gnu/libnsl-2.17.so
7f0adaa85000-7f0adaa86000 rw-p 00015000 fe:18 647970   

Processed: severity

[Debian Bug Tracking System]

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

> severity 707641 normal
Bug #707641 [cryptsetup] overriding root device on TS-419 non-working
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
707641: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707641
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#726799: qgo: deletes a shipped file during upgrades: /usr/share/mime/text/x-sgf.xml

[Yann Dirson]

On Fri, Dec 13, 2013 at 01:58:31AM +0100, Andreas Beckmann wrote:
> On 2013-12-03 22:30, Yann Dirson wrote:
> > I'm wondering if that could not be caused by a bug in the mime
> > trigger, that would have been fixed already.
> 
> That would be easier to test - what package is it?

I was thinking about the mime-support trigger, but that package has
not been changed for 6 months, so the problem must be somewhere else.

> > Can you please retry the test,
> 
> reproducible in jessie-> sid and wheezy->sid updates to version
> 2.0~git-20131123-1
> 
> > and if it still fails, run it while the
> > following stap script is running:
> 
> That may take some time ... I'll need to rerun the piuparts test
> manually in a chroot ... and on a different machine ...

OK


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

Bug#732095: webkitgtk contains a JSON do-no-evil licensed file.

[Paul Tagliamonte]

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

Howdy maintainers,

http://sources.debian.net/src/webkitgtk/2.3.2-1/Source/WebCore/inspector/Scripts/jsmin.py

I believe this file to be a derived work, and subject to Crockford's terms,
and thus isn't distributable in main.

For some reason this is in the lintian overrides(!?), please remove it
from the overrides, and strip this file (or move this package to
non-free).

Cheers,
  Paul

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


signature.asc
Description: Digital signature

Bug#729629: marked as done (mediawiki: CVE-2013-4567, CVE-2013-4568 and CVE-2013-4572)

[Debian Bug Tracking System]

Your message dated Fri, 13 Dec 2013 21:20:48 +
with message-id 
and subject line Bug#729629: fixed in mediawiki 1:1.19.8+dfsg-2.2
has caused the Debian Bug report #729629,
regarding mediawiki: CVE-2013-4567, CVE-2013-4568 and CVE-2013-4572
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.)


-- 
729629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mediawiki
Severity: grave
Tags: security upstream patch fixed-upstream

Hi

To have this issues tracked: Upstream announced new security releases
for mediawiki:

http://lists.wikimedia.org/pipermail/wikitech-l/2013-November/073115.html

for mediawiki these are:

* Kevin Israel (Wikipedia user PleaseStand) identified and reported two
vectors for injecting Javascript in CSS that bypassed MediaWiki's blacklist
(CVE-2013-4567, CVE-2013-4568).


* Internal review while debugging a site issue discovered that MediaWiki
and the CentralNotice extension were incorrectly setting cache headers when
a user was autocreated, causing the user's session cookies to be cached,
and returned to other users (CVE-2013-4572).


Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: mediawiki
Source-Version: 1:1.19.8+dfsg-2.2

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

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated mediawiki package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 08 Dec 2013 16:13:40 -0400
Source: mediawiki
Binary: mediawiki mediawiki-classes
Architecture: source all
Version: 1:1.19.8+dfsg-2.2
Distribution: unstable
Urgency: high
Maintainer: Mediawiki Maintenance Team 

Changed-By: David Prévot 
Description: 
 mediawiki  - website engine for collaborative work
 mediawiki-classes - website engine for collaborative work - standalone classes
Closes: 729629 731381
Changes: 
 mediawiki (1:1.19.8+dfsg-2.2) unstable; urgency=high
 .
   * Non-maintainer upload
   * Security fixes (Closes: #729629):
 - Kevin Israel (Wikipedia user PleaseStand) identified and reported two
   vectors for injecting Javascript in CSS that bypassed MediaWiki's
   blacklist [CVE-2013-4567, CVE-2013-4568]
 - Internal review while debugging a site issue discovered that MediaWiki
   and the CentralNotice extension were incorrectly setting cache headers
   when a user was autocreated, causing the user's session cookies to be
   cached, and returned to other users [CVE-2013-4572]
   * New Polish debconf translation, thanks to Magdalena Z. Kubot
 (Closes: #731381)
Checksums-Sha1: 
 c48906798a9b1496d636660b46754f7adbb263ed 1853 mediawiki_1.19.8+dfsg-2.2.dsc
 098bf5fb07ef0e5d7955a0328dc3af3a1ca7ed2c 53660 
mediawiki_1.19.8+dfsg-2.2.debian.tar.gz
 b76ddf5c1024aa98125aae5b8f921532dca20998 11726608 
mediawiki_1.19.8+dfsg-2.2_all.deb
 23979f747a6d714ad258cbf08c9f665d3a17d5e7 236188 
mediawiki-classes_1.19.8+dfsg-2.2_all.deb
Checksums-Sha256: 
 835e60b6adaa7309750a03e3bb7c2f98f37558700c7c2a40d31ea0972488c95a 1853 
mediawiki_1.19.8+dfsg-2.2.dsc
 f04460c72b51d5833a799a19fafc6187eded20f4f1ab519b5e9ae486f4601771 53660 
mediawiki_1.19.8+dfsg-2.2.debian.tar.gz
 a5aedeb151b6a829ab529bd2785368df95c388975a9b82b6be841fb97dc957a1 11726608 
mediawiki_1.19.8+dfsg-2.2_all.deb
 73a3f5fd66bbd5211b2035593005e1be78cfd14a0d577e7c7e8e4575a3f8a198 236188 
mediawiki-classes_1.19.8+dfsg-2.2_all.deb
Files: 
 764e12343537c8c0257698ae6a2a8808 1853 web optional 
mediawiki_1.19.8+dfsg-2.2.dsc
 cd6ee552dc1d740542a9b55665547d8d 53660 web optional 
mediawiki_1.19.8+dfsg-2.2.debian.tar.gz
 de750724e828a2db803c77e24c67 11726608 web optional 
mediawiki_1.19.8+dfsg-2.2_all.deb
 32c7cd5864cb4479dfa8b71d5d7cabd7 236188 web optional 
mediawiki-classes_1.19.8+dfsg-2.2_all.deb

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

iQEcBAEBCAAGBQJSpNToAAoJEAWMHPlE9r08wjcH/2NZDbXaa+00vaBZ3

Bug#731606: marked as done (git-annex: git annex lock ignores modifications and replaces from latest annexed version)

[Debian Bug Tracking System]

Your message dated Fri, 13 Dec 2013 19:03:46 +
with message-id 
and subject line Bug#731606: fixed in git-annex 5.20131213
has caused the Debian Bug report #731606,
regarding git-annex: git annex lock ignores modifications and replaces from 
latest annexed version
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.)


-- 
731606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: git-annex
Version: 4.20131106
Severity: grave
Tags: upstream
Justification: causes non-serious data loss

Hi.

I hope I'm not overreacting.

Consider the following situation, where :

1. a file is annexed, with git annex add.
2. make the file modifiable : git annex unlock
3. modify the contents of the file.
3. git annex lock the file

The lock command doesn't complain that the file was modified, and silently 
removes it to replace it by the link to the previous version.

File changes are lost :-(

It seems this is on purpose, reading the manpage :
  Use this to undo an unlock command if you don't want to modify the files, or 
have made modifications you want  to  dis‐
  card.

IMHO, this is really undesirable, as one should be warned/prompted that a 
commit is necessary, by default. Only with an explicit force option would lock 
ever erase pending changes (there's git reset for reverting changes, and having 
lock duplicate the behaviour is confusing for git users, IMHO). Lock should 
just be the inverse of unlock, i.e. no longer allowing modifications, but not 
*erasing* modifications, if it happens there were some.

Hope this makes sense.

Best regards,

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

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

Versions of packages git-annex depends on:
ii  curl7.33.0-1
ii  git 1:1.8.4.3-1
ii  libc6   2.17-97
ii  libffi6 3.0.13-4
ii  libgmp102:5.1.2+dfsg-3
ii  libgnutls26 2.12.23-8
ii  libgsasl7   1.8.0-2
ii  libicu484.8.1.1-14
ii  libidn111.28-1
ii  libxml2 2.9.1+dfsg1-3
ii  libyaml-0-2 0.1.4-2
ii  openssh-client  1:6.4p1-1
ii  rsync   3.1.0-2
ii  wget1.14-5
ii  zlib1g  1:1.2.8.dfsg-1

Versions of packages git-annex recommends:
ii  bind9-host 1:9.8.4.dfsg.P1-6+nmu3
ii  git-remote-gcrypt  0.20130908-5
ii  gnupg  1.4.15-1.1
ii  lsof   4.86+dfsg-1
ii  quvi   0.4.2-1
ii  ssh-askpass1:1.2.4.1-9

Versions of packages git-annex suggests:
pn  bup  
ii  graphviz 2.26.3-15+b1
ii  libnss-mdns  0.10-3.2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: git-annex
Source-Version: 5.20131213

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

Debian distribution maintenance software
pp.
Joey Hess  (supplier of updated git-annex package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 13 Dec 2013 14:20:32 -0400
Source: git-annex
Binary: git-annex
Architecture: source amd64
Version: 5.20131213
Distribution: unstable
Urgency: low
Maintainer: Joey Hess 
Changed-By: Joey Hess 
Description: 
 git-annex  - manage files with git, without checking their contents into git
Closes: 731142 731606
Changes: 
 git-annex (5.20131213) unstable; urgency=low
 .
   * Avoid using git commit in direct mode, since in some situations
 it will read the full contents of files in the tree.
   * assistant: Batch jobs are now run with ionice and nocache, when
 those commands are available.
   * assistant: Run transferkeys as batch jobs.
   * Automatically fix up bad bare repositories created by
 versions 5.20131118 through 5.20131127.
   * rsync special remote: Fix fallback mode for rsync remotes that
 use hashDirMixed. Closes: #731142
   * copy --from, get --from:

Processed: your mail

[Debian Bug Tracking System]

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

> unarchive 726009
Bug #726009 {Done: Anton Gladky } [src:yade] Yade requires 
too much RAM for building
Unarchived Bug 726009
> forcemerge 726009 731878
Bug #726009 {Done: Anton Gladky } [src:yade] Yade requires 
too much RAM for building
Bug #731878 [src:yade] yade: FTBFS, insane memory requirements
708401 was blocked by: 728094 730739 730738 708379 707872 707315 707962 731878 
718153
708401 was not blocking any bugs.
Removed blocking bug(s) of 708401: 731878
Marked Bug as done
Marked as fixed in versions yade/1.05.0-2 and yade/1.00.0-5.
Marked as found in versions yade/1.05.0-1, yade/1.00.0-2, yade/1.00.0-3, and 
yade/1.00.0-4.
Bug #726009 {Done: Anton Gladky } [src:yade] Yade requires 
too much RAM for building
Marked as found in versions yade/1.05.0-2.
Merged 726009 731878
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
708401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708401
726009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726009
731878: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731878
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#731878: yade: FTBFS, insane memory requirements

[Anton Gladky]

forcemerge 726009 731878
thanks

This is the same bug like #731878. I have implemented all
possible procedures, which were advised to reduce RAM
consumption including splitting some large .cpp-files.

I do not see any other possibilities to reduce it more, sorry.
Thus we can just blacklist yade on buildds, with RAM <4Gb.
But it is not RC.

Please, give yade_1.05.0-2+b1 back. Or wait a little bit as a new
source-uploads will be done soon.

Thanks,

Anton


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

Bug#725631: marked as done (getfem++: FTBFS due to: /usr/bin/install: cannot stat 'jar/*.jar': No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 13 Dec 2013 18:58:06 +0100
with message-id 

and subject line 
has caused the Debian Bug report #725631,
regarding getfem++: FTBFS due to: /usr/bin/install: cannot stat 'jar/*.jar': No 
such file or directory
to be marked as done.

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

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


-- 
725631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: getfem++
Version: 4.2.1~beta1~svn4422~dfsg-1
Severity: serious
Justification: FTBFS

Hi,

your package FTBFS on a bunch of archs with:
| /usr/bin/install -c -D -m 644 -t 
/build/getfem++-rS5QtJ/getfem++-4.2.1~beta1~svn4422~dfsg/debian/tmp/usr/lib/arm-linux-gnueabi/scilab-getfem++//jar
 jar/*.jar
| /usr/bin/install: cannot stat 'jar/*.jar': No such file or directory
| make[5]: *** [install] Error 1

Full build logs:
  https://buildd.debian.org/status/package.php?p=getfem%2B%2B&suite=sid

Mraw,
KiBi.
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 32672--- End Message ---

Processed: Closing bug

[Debian Bug Tracking System]

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

> fixed 725631 4.2.1~beta1~svn4482~dfsg-2
Bug #725631 [src:getfem++] getfem++: FTBFS due to: /usr/bin/install: cannot 
stat 'jar/*.jar': No such file or directory
Marked as fixed in versions getfem++/4.2.1~beta1~svn4482~dfsg-2.
> thanks
Stopping processing here.

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

[Anton Gladky]

fixed 725631 4.2.1~beta1~svn4482~dfsg-2
thanks


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

Bug#732070: marked as done (openvswitch-switch: installation fails)

[Debian Bug Tracking System]

Your message dated Fri, 13 Dec 2013 17:48:48 +
with message-id 
and subject line Bug#732070: fixed in openvswitch 1.9.3+git20131029-1.1
has caused the Debian Bug report #732070,
regarding openvswitch-switch: installation fails
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.)


-- 
732070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openvswitch-switch
Version: 1.9.3+git20131029-1
Severity: important

Dear Maintainer,

root@t430gone:/home/goneri# apt-get install openvswitch-switch
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libamd2.2.0 libboost-thread1.49.0 libcolamd2.7.1 libgsm1:i386 libodbc1:i386 
libtiff4:i386 libumfpack5.4.0 libv4l-0:i386 libv4lconvert0:i386 libwine-bin:i386
  libwine-gl:i386 libxcomposite1:i386 libxinerama1:i386 libxrandr2:i386 
libxslt1.1:i386 openjdk-7-jre-lib wine-bin:i386
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  openvswitch-common
Suggested packages:
  openvswitch-datapath-module
The following NEW packages will be installed:
  openvswitch-common openvswitch-switch
0 upgraded, 2 newly installed, 0 to remove and 75 not upgraded.
Need to get 1,188 kB of archives.
After this operation, 5,384 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.fr.debian.org/debian/ sid/main openvswitch-common amd64 
1.9.3+git20131029-1 [423 kB]
Get:2 http://ftp.fr.debian.org/debian/ sid/main openvswitch-switch amd64 
1.9.3+git20131029-1 [765 kB]
Fetched 1,188 kB in 2s (413 kB/s)   
Selecting previously unselected package openvswitch-common. 

   
(Reading database ... 213732 files and directories currently installed.)

   
Preparing to unpack .../openvswitch-common_1.9.3+git20131029-1_amd64.deb ...

   
Unpacking openvswitch-common (1.9.3+git20131029-1) ...  

   
Selecting previously unselected package openvswitch-switch. 

   
Preparing to unpack .../openvswitch-switch_1.9.3+git20131029-1_amd64.deb ...

   
Unpacking openvswitch-switch (1.9.3+git20131029-1) ...  

   
Processing triggers for man-db (2.6.5-2) ...

   
Setting up openvswitch-common (1.9.3+git20131029-1) ...
Setting up openvswitch-switch (1.9.3+git20131029-1) ...
[ ok ] Inserting openvswitch module.
/usr/share/openvswitch/scripts/ovs-ctl: 186: ulimit: error setting limit 
(Invalid argument)
[warn] /etc/openvswitch/conf.db does not exist ... (warning).
ovsdb-tool: I/O error: /etc/openvswitch/conf.db: failed to lock lockfile (No 
such file or directory)
[FAIL] Creating empty database /etc/openvswitch/conf.db ... failed!
/usr/share/openvswitch/scripts/ovs-ctl: 186: ulimit: error setting limit 
(Invalid argument)

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

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

Versions of packages openvswitch-switch depends on:
ii  libc6   2.17-97
ii  libssl1.0.0 1.0.1e-4
ii  module-init-tools   9-3
ii  netbase 5.1
iu  openvswitch-common  1.9.3+git20131029-1
ii  procps  1:3.3.8-2
pn  python:any  
ii  uuid-runtime2.20.1-5.5

openvswitch-switch recommends no packages.

Versions of packages openvswitch-switch suggests:
pn  openvswitch-datapath-module  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: openvswitch

Bug#718272: Bitcoin still not ready for stable release in Debian

[Scott Howard]

Below is my opinion, and is open for debate:

Although there are mechanisms for supporting security updates in
stable debian releases, and luke-jr's work of porting fixes is great
and exactly what is needed, updates to network protocols would not
classify as a security update and would only be available via
backports.d.o.

"Mandatory" network updates from upstream don't have a propagation
system through stable Debian releases, therefore it should not be in a
stable release.

Ubuntu has just removed the bitcoin package in favor of the upstream
"official" PPA. This package, as it is an unstable-only package, has a
similar function as a PPA at this point. Users can apt-pin to it and
stay up-to-date via regular updates.

As bitcoin evolves, and network protocols becomes standardized, we can
revisit whether this would be viable for stable release.


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

Bug#732070: Will NMU soon

[Thomas Goirand]

Hi Ben,

it's always a pleasure to see that you are ok with help. I will NMU shortly.

Thomas


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

Bug#732070: Switched severity to grave

[Ben Pfaff]

On Sat, Dec 14, 2013 at 12:22:46AM +0800, Thomas Goirand wrote:
> Since this completely blocks the apt-get install process, and makes it
> impossible to install openvswitch-switch without manual intervention, I
> have set this bug severity to "grave", because it fits this definition:
> 
> "makes the package in question unusable by most or all users."
> 
> By the way, it seems that a simple:
> 
> mkdir -p /var/lib/openvswitch
> 
> on top of the debian/openvswitch-switch.postinst (just right after the
> "configure)" line) is enough to fix the problem.
> 
> If you cannot fix this package in a timely manner (for example, next
> week or something...), please write about it in this bug report: both
> Goneri or myself would be very happy to help and NMU the fix, if we are
> right that a simple mkdir is enough.

Assistance is always welcome, especially in the case of a severe bug.
Please feel free to NMU.


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

Bug#732070: Switched severity to grave

[Thomas Goirand]

Hi,

Since this completely blocks the apt-get install process, and makes it
impossible to install openvswitch-switch without manual intervention, I
have set this bug severity to "grave", because it fits this definition:

"makes the package in question unusable by most or all users."

By the way, it seems that a simple:

mkdir -p /var/lib/openvswitch

on top of the debian/openvswitch-switch.postinst (just right after the
"configure)" line) is enough to fix the problem.

If you cannot fix this package in a timely manner (for example, next
week or something...), please write about it in this bug report: both
Goneri or myself would be very happy to help and NMU the fix, if we are
right that a simple mkdir is enough.

Thomas Goirand (zigo)


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

Processed: Switch to RC bug

[Debian Bug Tracking System]

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

> severity 732070 grave
Bug #732070 [openvswitch-switch] openvswitch-switch: installation fails
Severity set to 'grave' from 'important'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
732070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732070
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#727750: marked as done (boost1.54: macro for int128 detection)

[Debian Bug Tracking System]

Your message dated Fri, 13 Dec 2013 16:00:13 +
with message-id 
and subject line Bug#727750: fixed in boost1.54 1.54.0-4
has caused the Debian Bug report #727750,
regarding boost1.54: macro for int128 detection
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.)


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

Hi,

mongodb/1:2.4.6-1 FTBFS on i386 but built there in the past.

~Niels
--- End Message ---
--- Begin Message ---
Source: boost1.54
Source-Version: 1.54.0-4

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

Debian distribution maintenance software
pp.
Steve M. Robbins  (supplier of updated boost1.54 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 04 Dec 2013 00:50:47 -0600
Source: boost1.54
Binary: libboost1.54-dbg libboost1.54-dev libboost1.54-tools-dev 
libboost1.54-all-dev libboost1.54-doc libboost-atomic1.54.0 
libboost-atomic1.54-dev libboost-chrono1.54.0 libboost-chrono1.54-dev 
libboost-context1.54.0 libboost-context1.54-dev libboost-coroutine1.54-dev 
libboost-date-time1.54.0 libboost-date-time1.54-dev libboost-exception1.54-dev 
libboost-filesystem1.54.0 libboost-filesystem1.54-dev libboost-graph1.54.0 
libboost-graph1.54-dev libboost-graph-parallel1.54.0 
libboost-graph-parallel1.54-dev libboost-iostreams1.54.0 
libboost-iostreams1.54-dev libboost-locale1.54.0 libboost-locale1.54-dev 
libboost-log1.54.0 libboost-log1.54-dev libboost-math1.54.0 
libboost-math1.54-dev libboost-mpi1.54.0 libboost-mpi1.54-dev 
libboost-mpi-python1.54.0 libboost-mpi-python1.54-dev 
libboost-program-options1.54.0 libboost-program-options1.54-dev 
libboost-python1.54.0 libboost-python1.54-dev libboost-random1.54.0 
libboost-random1.54-dev libboost-regex1.54.0 libboost-regex1.54-dev
 libboost-serialization1.54.0 libboost-serialization1.54-dev 
libboost-signals1.54.0 libboost-signals1.54-dev libboost-system1.54.0 
libboost-system1.54-dev libboost-test1.54.0 libboost-test1.54-dev 
libboost-thread1.54.0 libboost-thread1.54-dev libboost-timer1.54.0 
libboost-timer1.54-dev libboost-wave1.54.0
 libboost-wave1.54-dev
Architecture: source amd64 all
Version: 1.54.0-4
Distribution: unstable
Urgency: low
Maintainer: Debian Boost Team 
Changed-By: Steve M. Robbins 
Description: 
 libboost-atomic1.54-dev - atomic data types, operations, and memory ordering 
constraints
 libboost-atomic1.54.0 - atomic data types, operations, and memory ordering 
constraints
 libboost-chrono1.54-dev - C++ representation of time duration, time point, and 
clocks
 libboost-chrono1.54.0 - C++ representation of time duration, time point, and 
clocks
 libboost-context1.54-dev - provides a sort of cooperative multitasking on a 
single thread
 libboost-context1.54.0 - provides a sort of cooperative multitasking on a 
single thread
 libboost-coroutine1.54-dev - provides a sort of cooperative multitasking on a 
single thread
 libboost-date-time1.54-dev - set of date-time libraries based on generic 
programming concepts
 libboost-date-time1.54.0 - set of date-time libraries based on generic 
programming concepts
 libboost-exception1.54-dev - library to help write exceptions and handlers
 libboost-filesystem1.54-dev - filesystem operations (portable paths, iteration 
over directories
 libboost-filesystem1.54.0 - filesystem operations (portable paths, iteration 
over directories
 libboost-graph-parallel1.54-dev - generic graph components and algorithms in 
C++
 libboost-graph-parallel1.54.0 - generic graph components and algorithms in C++
 libboost-graph1.54-dev - generic graph components and algorithms in C++
 libboost-graph1.54.0 - generic graph components and algorithms in C++
 libboost-iostreams1.54-dev - Boost.Iostreams Library development files
 libboost-iostreams1.54.0 - Boost.Iostreams Library
 libboost-locale1.54-dev - C++ facilities for localization
 libboost-locale1.54.0 - C++ facilities for localization
 libboost-log1.54-d

Bug#732044: [Debichem-devel] Bug#732044: psi4: FTBFS when not building -data package

[Michael Banck]

Hi,

On Thu, Dec 12, 2013 at 10:45:30PM -0500, Aaron M. Ucko wrote:
> Source: psi4
> Version: 4.0~beta5+dfsg-1
> Severity: serious
> Justification: fails to build from source
> 
> Builds of psi4 covering only its architecture-dependent psi4 binary
> package (as on the autobuilders, or with debuild -B) have been failing:

Thanks for the heads-up, I thought I tested that case.  Will look into
it.


Michael


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

Bug#720681: [Debian-med-packaging] Bug#720681: Help with cmake needed (Was: Bug#720681: (Further) help with C++ needed)

[Gert Wollny]

Bad news is now compiling fails with: 

/home/wollny/Debian/ball/build/source/PYTHON/EXTENSIONS/VIEWmodule/sipVIEWpart0.cpp:
 In member function 'virtual void sipDatasetControl::destroy()':
/home/wollny/Debian/ball/build/source/PYTHON/EXTENSIONS/VIEWmodule/sipVIEWpart0.cpp:2981:9:
 error: reference to 'destroy' is ambiguous
 DatasetControl::destroy();
 ^
In file included
from /home/wollny/Debian/ball/include/BALL/VIEW/KERNEL/mainControl.h:17:0,

from /home/wollny/Debian/ball/source/PYTHON/EXTENSIONS/VIEW/mainControl.sip:13:
/home/wollny/Debian/ball/include/BALL/VIEW/KERNEL/connectionObject.h:73:17: 
note: candidates are: virtual void BALL::VIEW::ConnectionObject::destroy()
virtual void destroy();
 ^
In file included
from 
/home/wollny/Debian/ball/source/PYTHON/EXTENSIONS/VIEW/modularWidget.sip:12:0:
/home/wollny/Debian/ball/include/BALL/VIEW/KERNEL/modularWidget.h:91:17:
note: virtual void BALL::VIEW::ModularWidget::destroy()
virtual void destroy()
 ^
In file included from /usr/include/qt4/QtGui/qdialog.h:45:0,
 from /usr/include/qt4/QtGui/qcolordialog.h:45,
 from /usr/include/qt4/QtGui/QColorDialog:1,

from /home/wollny/Debian/ball/include/BALL/VIEW/KERNEL/common.h:27,

from /home/wollny/Debian/ball/source/PYTHON/EXTENSIONS/VIEW/view-common.sip:7,

from 
/home/wollny/Debian/ball/build/source/PYTHON/EXTENSIONS/VIEWmodule/sipVIEWpart0.cpp:7:
/usr/include/qt4/QtGui/qwidget.h:726:10: note: void
QWidget::destroy(bool, bool)
 void destroy(bool destroyWindow = true,
  ^


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

Bug#720681: [Debian-med-packaging] Bug#720681: Help with cmake needed (Was: Bug#720681: (Further) help with C++ needed)

[Gert Wollny]

Hello, 

it seems the attached patch solves the problem (Building at 95% way
beyond where it failed before). 

Actually, it is commit 1e76c9 in the ball git repro
https://bitbucket.org/ball/ball


Cheers, 
Gert



>From 1e76c9cb1920e9176b725269985c7eb43126d188 Mon Sep 17 00:00:00 2001
From: Luis de la Garza 
Date: Fri, 22 Nov 2013 15:18:55 +0100
Subject: [PATCH] QT4_EXTRACT_OPTIONS CMake macro changed in CMake 2.8.12;
 fixed BALLMacros.cmake

---
 cmake/BALLMacros.cmake | 14 ++
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/cmake/BALLMacros.cmake b/cmake/BALLMacros.cmake
index f81ab89..0ac1b87 100644
--- a/cmake/BALLMacros.cmake
+++ b/cmake/BALLMacros.cmake
@@ -6,16 +6,22 @@
 ### minor modifications (marked with ## BALL ###)
 ###
 MACRO(QT4_WRAP_UI_BALL outfiles )
-  QT4_EXTRACT_OPTIONS(ui_files ui_options ${ARGN})
-
-	### BALL ###
+  # since 2.8.12 qt4_extract_options has an additional argument
+  # copied fix from OpenMS
+  IF(${CMAKE_VERSION} VERSION_LESS "2.8.12")
+  QT4_EXTRACT_OPTIONS(ui_files ui_options ${ARGN})
+  ELSE()
+  QT4_EXTRACT_OPTIONS(ui_files ui_options ui_target ${ARGN})
+  ENDIF()
+
+  ### BALL ###
   # create output directory (will not exist for out-of-source builds)
   FILE(MAKE_DIRECTORY ${PROJECT_BINARY_DIR}/include/BALL/VIEW/UIC/)
 
   FOREACH (it ${ui_files})
 GET_FILENAME_COMPONENT(outfile ${it} NAME_WE)
 GET_FILENAME_COMPONENT(infile ${it} ABSOLUTE)
-		### BALL ###
+### BALL ###
 SET(outfile ${PROJECT_BINARY_DIR}/include/BALL/VIEW/UIC/ui_${outfile}.h)
 ADD_CUSTOM_COMMAND(OUTPUT ${outfile}
   COMMAND ${QT_UIC_EXECUTABLE}
-- 
1.8.5.1

Bug#728094: marked as done (stimfit: FTBFS on kfreebsd but built there in the past)

[Debian Bug Tracking System]

Your message dated Fri, 13 Dec 2013 15:20:58 +
with message-id 
and subject line Bug#728094: fixed in stimfit 0.13.6-1
has caused the Debian Bug report #728094,
regarding stimfit: FTBFS on kfreebsd but built there in the past
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.)


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

Hi,

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

~Niels
--- End Message ---
--- Begin Message ---
Source: stimfit
Source-Version: 0.13.6-1

We believe that the bug you reported is fixed in the latest version of
stimfit, 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.
Christoph Schmidt-Hieber  (supplier of updated stimfit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 11 Dec 2013 21:42:13 +
Source: stimfit
Binary: stimfit stimfit-dbg python-stfio
Architecture: source amd64
Version: 0.13.6-1
Distribution: unstable
Urgency: low
Maintainer: Christoph Schmidt-Hieber 
Changed-By: Christoph Schmidt-Hieber 
Description: 
 python-stfio - Python module to read common electrophysiology file formats.
 stimfit- Program for viewing and analyzing electrophysiological data
 stimfit-dbg - Debug symbols for stimfit
Closes: 728094
Changes: 
 stimfit (0.13.6-1) unstable; urgency=low
 .
   * Export stfio recordings to pandas
   * Improved support for accessing date and time of recordings
 .
 stimfit (0.13.5-1) unstable; urgency=low
 .
   * New upstream release
 - Don't write test results to disk
 - Fall back to gcc/Unix for unknown platforms/compilers
   in axodefn.h (Closes: #728094)
   * Improved batch analysis
   * Multi-channel concatenation
   * Less disruptive warnings and error messages
Checksums-Sha1: 
 1c269ae520da2541a1158cb4ff05d58afb861e10 1450 stimfit_0.13.6-1.dsc
 ef869717aac333ea793fe9dfc63428745f62cd6e 2268515 stimfit_0.13.6.orig.tar.gz
 7587878d80306252350158663437b790f36ff345 7412 stimfit_0.13.6-1.debian.tar.gz
 b0019e28dc637d1eb58db37958865e07b81f9cbd 634322 stimfit_0.13.6-1_amd64.deb
 f54b25e3442bd77498cf441770bd7825b7be3d79 3671940 stimfit-dbg_0.13.6-1_amd64.deb
 79c47fba8f19398d8bfbe8cd46583cfef790e5c8 207304 python-stfio_0.13.6-1_amd64.deb
Checksums-Sha256: 
 eec89432f80a7b0f2bcbfb2c1cb6c3bf7a149b6d541bb1001ed769c93ef96dd9 1450 
stimfit_0.13.6-1.dsc
 b1830e594a6b3e5f5edb7705f555973baaa9420ac3c53d27d7b4dd9ad771bab4 2268515 
stimfit_0.13.6.orig.tar.gz
 5a958ff9ebed1707f1e23240f453d29fa1cfd1668acc2e92cda0456098b1ade0 7412 
stimfit_0.13.6-1.debian.tar.gz
 8e0968a07ae06e029cc9e1dadf3bc163ab8beee4449fe767a8942c50a7d7b0a9 634322 
stimfit_0.13.6-1_amd64.deb
 1e84ec95e6d7e6720b8b5897e8961f7f2bb7e9a99280145f38d592420bc47285 3671940 
stimfit-dbg_0.13.6-1_amd64.deb
 1c77a65d663ba6a00464f292c5d52aa65f79b681e2c80ded50524fcaf442f880 207304 
python-stfio_0.13.6-1_amd64.deb
Files: 
 e1c1eac263a0c1456ccff7cf1a31f595 1450 science optional stimfit_0.13.6-1.dsc
 307e372fbb663bb2866d4580eb525f89 2268515 science optional 
stimfit_0.13.6.orig.tar.gz
 290aa7aa58116c57dca3f76532612930 7412 science optional 
stimfit_0.13.6-1.debian.tar.gz
 fd72cebeb195c572dcd7a45b28a94726 634322 science optional 
stimfit_0.13.6-1_amd64.deb
 6d7a2ac7b9edee57c2db3f60d65058e6 3671940 debug extra 
stimfit-dbg_0.13.6-1_amd64.deb
 7ddcb21b74ce1f90d15d63d5bbf1c424 207304 python optional 
python-stfio_0.13.6-1_amd64.deb

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

iEYEARECAAYFAlKrH6gACgkQjRFFY3XAJMgSCwCfR+X+VWXHHzTklBGEqFrLttiP
qJQAn0iXFDFlHeFWKsClHXloX7lb5zZl
=qkek
-END PGP SIGNATURE End Message ---

Bug#720681: Help with cmake needed (Was: Bug#720681: (Further) help with C++ needed)

[Andreas Tille]

Hi,

On Fri, Dec 13, 2013 at 01:11:10PM +0100, Gert Wollny wrote:
> The build system is quite complex, which makes it difficult to fix it
> without digging too much into it. As far as I can see there is some
> mixup between creating the files in VIEW/DIALOG and VIEW/UIC and then
> things go wrong, but how and why, I don't really understand. 
> 
> > 
> > I'm now trying to implement the hint of the issue reporter to run
> > uic-qt4 on the .ui files.
> A quick and dirty fix would be to create the files manually and add them
> as patch

Since about more than 50 ui_*.h files seem to be needed in this process
I dived again into the build system.  I dropped some comment into d/rules
(in Git git://git.debian.org/git/debian-med/ball.git)

## Uhmmm, seems we need to do this for all UI files mentioned in
##   source/VIEW/DIALOGS/sources.cmake
## but I really hope some cmake expert might be able to find a clue
## how to trigger cmake to do it as intended by upstream.
## Somehow the code
##   ADD_BALL_UIFILES("VIEW/DIALOGS" "${UI_LIST}")
## needs to be called before the build code below can be started

which basically tries to describe what needs to happen but my cmake
knowledge is to rudimentary to know how to approach this.  If nobody has
any idea I'd try some script hacking around the cmake input file and try
to do what needs to be done to create the missing files.

Kind regards

   Andreas.

-- 
http://fam-tille.de


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

Bug#732010: gimp: FTBFS (fails to find freetype headers)

[Ari Pollak]

If you're doing an NMU anyway, want to apply the patches for the recent
CVEs? I was waiting for a new release, but not sure when one will be out.

Thanks,
Ari
On Dec 12, 2013 12:39 PM, "Cyril Brulebois"  wrote:

> Control: tag -1 upstream patch
>
> Julien Cristau  (2013-12-12):
> > Source: gimp
> > Version: 2.8.6-1
> > Severity: serious
> > Justification: fails to build from source (but built successfully in the
> past)
> > Control: block 717923 with -1
> >
> > Hi,
> >
> > gimp fails to build from source against freetype 2.5.1:
> > > gcc -DHAVE_CONFIG_H -I. -I/«PKGBUILDDIR»/./app/text -I../.. -I../..
> -I/«PKGBUILDDIR»/. -I../../app -I/«PKGBUILDDIR»/./app -pthread
> -I/usr/include/gegl-0.2 -I/usr/include/babl-0.1 -I/usr/include/glib-2.0
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include   -pthread
> -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/glib-2.0
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
> -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm
> -I/usr/include/harfbuzz   -pthread -I/usr/include/gdk-pixbuf-2.0
> -I/usr/include/libpng12 -I/usr/include/glib-2.0
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include   -I/usr/include
> -DG_LOG_DOMAIN=\"Gimp-Text\" -D_FORTIFY_SOURCE=2 -DGIMP_DISABLE_DEPRECATED
> -DBABL_DISABLE_DEPRECATED -DGSEAL_ENABLE -DGDK_DISABLE_DEPRECATED
> -DGTK_DISABLE_DEPRECATED -DGDK_MULTIHEAD_SAFE -DGTK_MULTIHEAD_SAFE  -g -O2
> -fstack-protector --param=ssp-buffer-size=4 -Wformat
> -Werror=format-security -Wall -Wdeclaration-after-statement
> -Wmissing-prototypes -Werror=missing-prototypes -Wstrict-prototypes
> -Wmissing-declarations -Winit-self -Wpointer-arith -Wold-style-definition
> -Wmissing-format-attribute -Wformat-security  -fno-common
> -fdiagnostics-show-option   -c /«PKGBUILDDIR»/./app/text/gimpfont.c
> > > /«PKGBUILDDIR»/./app/text/gimpfont.c:30:31: fatal error:
> freetype/tttables.h: No such file or directory
> > >  #include 
> > >^
> > > compilation terminated.
> > > make[5]: *** [gimpfont.o] Error 1
> >
> > freetype changed its header location, you should include
> > FT_TRUETYPE_TABLES_H instead of .
>
> Commit available upstream:
>
> https://git.gnome.org/browse/gimp/commit/?id=6c73f28b6d87a2afd11974552a075bffec52347f
>
> And attached to this mail.
>
> Confirmed locally in a devel chroot, can NMU if that helps.
>
> Mraw,
> KiBi.
>

Bug#732010: gimp: FTBFS (fails to find freetype headers)

[Cyril Brulebois]

Ari Pollak  (2013-12-13):
> If you're doing an NMU anyway, want to apply the patches for the recent
> CVEs? I was waiting for a new release, but not sure when one will be out.

Julien doesn't seem to be in a hurry for this transition, so I'll
probably skip NMUing. Was just trying to send patches for
FTBFS/transition blockers.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#705023: New fix to #705023

[Arturo Borrero Gonzalez]

Hi there,

I've updated the copy of corosync I was working with.

The patch is now here:
https://github.com/aborrero/pkg-corosync

Commit: 3343dd2 [Fix Debian bug #705023]

Please let me know any issue.

Regards.

-- 
Arturo Borrero González


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

Bug#725714: the kernel should write missing firmware to a file

[Andreas Cadhalpun]

Hi,

Thanks, Kay, for the very fast response and the detailed reasoning.

Your arguments convinced me, that it is technically a very good idea to 
keep userspace out of the firmware loading. This should definitely not 
be reintroduced upstream or in the Debian version of udev.  (Originally 
I thought the problem was caused by the kernel, since it is not obvious, 
why the kernel would need another program to load a firmware-kernel-module.)


It seems that the kernel now handles the actual loading of the firmware, 
but does not write missing drivers to a file.


In fact, I'm inclined to reassign this to linux again, because I think 
this could be easily fixed in the kernel:
In the 3. step Ben described, the kernel should, instead of calling 
udev, write the missing firmware to some file. The kernel just has to 
find out, which file a specific firmware request is referring to. (The 
4. and 5. steps are already removed from udev.)
Then the installer would just need to update the path, where it is 
looking for this file, and it would work again as before. (Also 
gnome-settings-daemon should just update the 
GSD_UPDATES_FIRMWARE_MISSING_DIR.)


The next step would be to update the kernel handling of the firmware 
requests, to only write them to the file, when the firmware is actually 
needed. But I'm not sure how that could be done. (Note that this is not 
required for the Debian installer to work again.)


So I think isenkram is not needed. Looking at the commit, it would 
probably not be helpful as well, because it would try to download the 
WLAN driver!?!


Best regards,
Andreas


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

Bug#714984:

[Mathieu Malaterre]

On Fri, Dec 13, 2013 at 12:48 PM, Mathieu Malaterre  wrote:
> Control: forwarded -1 https://github.com/jcupitt/libvips/issues/88
>
> On Fri, Dec 13, 2013 at 11:20 AM, Jay Berkenbilt  wrote:
>> Mathieu Malaterre  wrote:
>>
>>> This bug is hard to debug, since libjpeg / libtiff / imagemagick are
>>> all linked together so this is not just a matter of recompiling vips
>>> with libjpeg62-dev unfortunately.
>>
>> The vips in wheezy does seem to have gotten caught up in libjpeg
>> transition issues.  The cases you describe work fine with the current
>> vips in sid and jessie.  I'm not sure what to do about the version in
>> wheezy.  I think the best approach there would probably be to do a
>> backport.  As you noted, vips has a huge list of dependencies, so
>> straightening out this kind of issue can be somewhat problematic.  I
>> don't really have much time or inclination to put a lot of effort into
>> it given that the current versions of the packages work correctly and
>> vips has a relatively small user base, especially in stable.  It's not
>> that I don't think having things work in stable is important -- clearly
>> it is.  I just have very limited time to work on this.
>
> I have forwarded the issue upstream. If this really cannot easily
> fixed with a simple one-liner patch, then yes I'll request a backport.

FYI:

[Please only upload package with a noteable userbase. User request for
the package may be an indicator.]

ref: http://backports.debian.org/Contribute/#index5h3


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

Bug#727758: marked as done (cups segfaults in libdbus)

[Debian Bug Tracking System]

Your message dated Fri, 13 Dec 2013 13:26:21 +0100
with message-id <1423124.pZfXh09XV4@gyllingar>
and subject line Re: Bug #727758: cups segfaults in libdbus - Fixed in 1.6.4-2 ?
has caused the Debian Bug report #727758,
regarding cups segfaults in libdbus
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.)


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

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]

Sometimes actually this only happens when the printer is switched on or a job 
is send to cups. 

Today for the first time I got this instead:

Oct 26 11:26:22 aragorn kernel: [   53.133630] traps: cupsd[2992] general 
protection ip:7f4c61ba5c7e sp:7fff4b69f108 error:0 in 
libdbus-1.so.3.7.5[7f4c61b88000+45000]

I'm not sure who's the culprit, libdbus or cups, so feel free to reassign. 
However, the effect is that my cups server simply disappears. Interestingly 
enough more often than not it works after a restart.

Any idea?

Michael

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

Kernel: Linux 3.10-3-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 ---
Version: 1.6.4-2

Le jeudi, 28 novembre 2013, 20.41:34 Michael Meskes a écrit :
> On Thu, Nov 28, 2013 at 02:32:45PM +0100, Didier 'OdyX' Raboud wrote:
> > It would be nice if you could attempt reproducing this bug with
> > 1.6.4-2 and report back to the bugreport.
> 
> New version is installed and running. With the server not segfaulting
> all the time for me I cannot say much yet, it did start correctly
> though. I will keep you guys posted.

Hi Michael, hi all,

This statement of yours was two weeks ago and none of you reported a new 
failure; so I'll assume that this is fixed and hereby close this bug as 
fixed in 1.6.4-2.

Please don't hesitate to re-open if the bug reappears!

Cheers,
OdyX

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

Processed: your mail

[Debian Bug Tracking System]

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

> retitle 732059 VTK_USE_SYSTEM_FREETYPE is ON, but FREETYPE_LIBRARY is 
> NOTFOUND.
Bug #732059 [vtk] https://github.com/jcupitt/libvips/issues/88
Changed Bug title to 'VTK_USE_SYSTEM_FREETYPE is ON, but FREETYPE_LIBRARY is 
NOTFOUND.' from 'https://github.com/jcupitt/libvips/issues/88'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
732059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732059
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#732059: https://github.com/jcupitt/libvips/issues/88

[Mathieu Malaterre]

Package: vtk
Severity: serious

Looks like vtk cannot be build using latest freetype (2.5.1-1), it
keeps failing with:

-- Found EXPAT: expat (found version "2.1.0")
CMake Error at CMake/vtkThirdParty.cmake:19 (MESSAGE):
  VTK_USE_SYSTEM_FREETYPE is ON, but FREETYPE_LIBRARY is NOTFOUND.
Call Stack (most recent call first):
  CMakeLists.txt:791 (VTK_THIRD_PARTY_OPTION)

As can be seen on recent rebuilds:

http://buildd.debian-ports.org/status/fetch.php?pkg=vtk&arch=ppc64&ver=5.8.0-14.1%2Bb2&stamp=1386595412


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

Bug#714984:

[Mathieu Malaterre]

Control: forwarded -1 https://github.com/jcupitt/libvips/issues/88

On Fri, Dec 13, 2013 at 11:20 AM, Jay Berkenbilt  wrote:
> Mathieu Malaterre  wrote:
>
>> This bug is hard to debug, since libjpeg / libtiff / imagemagick are
>> all linked together so this is not just a matter of recompiling vips
>> with libjpeg62-dev unfortunately.
>
> The vips in wheezy does seem to have gotten caught up in libjpeg
> transition issues.  The cases you describe work fine with the current
> vips in sid and jessie.  I'm not sure what to do about the version in
> wheezy.  I think the best approach there would probably be to do a
> backport.  As you noted, vips has a huge list of dependencies, so
> straightening out this kind of issue can be somewhat problematic.  I
> don't really have much time or inclination to put a lot of effort into
> it given that the current versions of the packages work correctly and
> vips has a relatively small user base, especially in stable.  It's not
> that I don't think having things work in stable is important -- clearly
> it is.  I just have very limited time to work on this.

I have forwarded the issue upstream. If this really cannot easily
fixed with a simple one-liner patch, then yes I'll request a backport.

Thanks


-- 
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#714984:

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/jcupitt/libvips/issues/88
Bug #714984 [libvips-tools] libvips-tools: Segmentation Fault: vips 7.28.5-1 
with jpeg compression
Set Bug forwarded-to-address to 'https://github.com/jcupitt/libvips/issues/88'.

-- 
714984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714984
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: only affects old version

[Debian Bug Tracking System]

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

> fixed 714984 7.36.3-2
Bug #714984 [libvips-tools] libvips-tools: Segmentation Fault: vips 7.28.5-1 
with jpeg compression
Marked as fixed in versions vips/7.36.3-2.
> thanks
Stopping processing here.

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

[Debian Bug Tracking System]

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

> forwarded 721622 https://issues.asterisk.org/jira/browse/ASTERISK-22980
Bug #721622 {Done: Jeremy Lainé } [asterisk-modules] 
dependency change s/libradiusclient-ng2/libfreeradius-client2
Set Bug forwarded-to-address to 
'https://issues.asterisk.org/jira/browse/ASTERISK-22980'.
> thanks
Stopping processing here.

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

[Jay Berkenbilt]

Mathieu Malaterre  wrote:

> This bug is hard to debug, since libjpeg / libtiff / imagemagick are
> all linked together so this is not just a matter of recompiling vips
> with libjpeg62-dev unfortunately.

The vips in wheezy does seem to have gotten caught up in libjpeg
transition issues.  The cases you describe work fine with the current
vips in sid and jessie.  I'm not sure what to do about the version in
wheezy.  I think the best approach there would probably be to do a
backport.  As you noted, vips has a huge list of dependencies, so
straightening out this kind of issue can be somewhat problematic.  I
don't really have much time or inclination to put a lot of effort into
it given that the current versions of the packages work correctly and
vips has a relatively small user base, especially in stable.  It's not
that I don't think having things work in stable is important -- clearly
it is.  I just have very limited time to work on this.

-- 
Jay Berkenbilt 


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

Processed: only affects old version

[Debian Bug Tracking System]

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

> notfound 714984 7.36.3-1
Bug #714984 [libvips-tools] libvips-tools: Segmentation Fault: vips 7.28.5-1 
with jpeg compression
Ignoring request to alter found versions of bug #714984 to the same values 
previously set
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
714984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714984
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#730978: marked as done (blender: FTBFS on armel: error: implicit declaration of function 'atomic_add_uint32')

[Debian Bug Tracking System]

Your message dated Fri, 13 Dec 2013 10:04:23 +
with message-id 
and subject line Bug#730978: fixed in blender 2.69-3
has caused the Debian Bug report #730978,
regarding blender: FTBFS on armel: error: implicit declaration of function 
'atomic_add_uint32'
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.)


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

blender fails to build on armel:
| /«PKGBUILDDIR»/intern/atomic/atomic_ops.h:248:4: error: #error "Missing 
implementation for 32-bit atomic operations"
|  #  error "Missing implementation for 32-bit atomic operations"
| ^
| /«PKGBUILDDIR»/intern/atomic/atomic_ops.h: In function 'atomic_add_z':
| /«PKGBUILDDIR»/intern/atomic/atomic_ops.h:261:2: error: implicit declaration 
of function 'atomic_add_uint32' [-Werror=implicit-function-declaration]
|   return ((size_t)atomic_add_uint32((uint32_t *)p, (uint32_t)x));
|   ^
| /«PKGBUILDDIR»/intern/guardedalloc/intern/mallocn.c: In function 
'make_memhead_header':
| /«PKGBUILDDIR»/intern/guardedalloc/intern/mallocn.c:509:9: warning: cast 
increases required alignment of target type [-Wcast-align]
|   memt = (MemTail *)(((char *) memh) + sizeof(MemHead) + len);
|  ^
| /«PKGBUILDDIR»/intern/guardedalloc/intern/mallocn.c: In function 'MEM_freeN':
| /«PKGBUILDDIR»/intern/guardedalloc/intern/mallocn.c:878:10: warning: cast 
increases required alignment of target type [-Wcast-align]
|memt = (MemTail *)(((char *) memh) + sizeof(MemHead) + memh->len);
|   ^
| cc1: some warnings being treated as errors
| make[3]: *** 
[source/blender/makesdna/intern/CMakeFiles/makesdna.dir/__/__/__/__/intern/guardedalloc/intern/mallocn.c.o]
 Error 1

Full build log is available at
https://buildd.debian.org/status/fetch.php?pkg=blender&arch=armel&ver=2.69-1&stamp=1383747502

Regards
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: blender
Source-Version: 2.69-3

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

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

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

Debian distribution maintenance software
pp.
Matteo F. Vescovi  (supplier of updated blender package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 13 Dec 2013 08:54:15 +0100
Source: blender
Binary: blender blender-data blender-dbg
Architecture: source amd64 all
Version: 2.69-3
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers 

Changed-By: Matteo F. Vescovi 
Description: 
 blender- Very fast and versatile 3D modeller/renderer
 blender-data - Very fast and versatile 3D modeller/renderer - data package
 blender-dbg - debug symbols for Blender
Closes: 730978
Changes: 
 blender (2.69-3) unstable; urgency=low
 .
   * debian/patches/: patchset updated
 - 0011-fix_FTBFS_on_armel.patch added (Closes: #730978)
   Thanks to Sergey Sharybin (upstream devel) for the hint.
Checksums-Sha1: 
 745b8ebcf562da2bd63141dff9380f87a57c0e62 2691 blender_2.69-3.dsc
 55f267a9d6759bbbe351975499725569d8ca2a08 46217 blender_2.69-3.debian.tar.gz
 caba491df5e7002f8d2c3aca681105bbc59cf5a1 18216860 blender_2.69-3_amd64.deb
 76c737bbbc9451c8f4862445a5df667b1d7f31c1 7050982 blender-data_2.69-3_all.deb
 fb50603af9db799a4c046dcd7014b2dfdfd8aea3 170360502 blender-dbg_2.69-3_amd64.deb
Checksums-Sha256: 
 13b7995a4d31314c2cefd120f05568e1a06f4e23a58678aa4c40d58bdc798cf5 2691 
blender_2.69-3.dsc
 17774a7f22c448a194bb4e691b4e159989cac8ed705c3b5569652bf756464d8a 46217 
blender_2.69-3.debian.tar.gz
 2d449ab8ed142c18f6f6dd77355c19af3134705d6b78ba9a1c58fd9b3f248bad 18216860 
blender_2.69-3_amd64.deb
 9455ddee02ffa10a82fe54f7282f7154f38c88096960414e1885c5f1a333d8d0 7050982 
blender-data_2.69-3_all.deb
 f137883dbca0920f6acc1ac31efa19338f816682056b4c5057bd9a92776d4d07 170360502 
blender-dbg_2.69-3_amd64.deb
Files: 
 bebac291a68a402c7d84ad21adf48c8b 2691 graphics 

Bug#706155: marked as done (python3-evemu: fails to install: SyntaxError: invalid syntax in evemu/base.py, line 22)

[Debian Bug Tracking System]

Your message dated Fri, 13 Dec 2013 09:19:19 +
with message-id 
and subject line Bug#706155: fixed in evemu 1.2.0-1
has caused the Debian Bug report #706155,
regarding python3-evemu: fails to install: SyntaxError: invalid syntax in 
evemu/base.py, line 22
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.)


-- 
706155: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-evemu
Version: 1.0.10-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 python3-evemu.
  (Reading database ... 8237 files and directories currently installed.)
  Unpacking python3-evemu (from .../python3-evemu_1.0.10-1_amd64.deb) ...
  Setting up python3-evemu (1.0.10-1) ...
File "/usr/lib/python3/dist-packages/evemu/base.py", line 22
  raise exception.ExecutionError, "%s: %s" % (
^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/evemu/base.py", line 22
  raise exception.ExecutionError, "%s: %s" % (
^
  SyntaxError: invalid syntax
  
  dpkg: error processing python3-evemu (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   python3-evemu


cheers,

Andreas


python3-evemu_1.0.10-1.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Source: evemu
Source-Version: 1.2.0-1

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

Debian distribution maintenance software
pp.
Stephen M. Webb  (supplier of updated evemu 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: Thu, 12 Dec 2013 19:12:23 -0500
Source: evemu
Binary: libevemu1 python-evemu python3-evemu libevemu-dev evemu-tools
Architecture: source amd64
Version: 1.2.0-1
Distribution: unstable
Urgency: low
Maintainer: Stephen M. Webb 
Changed-By: Stephen M. Webb 
Description: 
 evemu-tools - Linux Input Event Device Emulation Library - test tools
 libevemu-dev - Linux Input Event Device Emulation Library - development files
 libevemu1  - Linux Input Event Device Emulation Library
 python-evemu - Linux Input Event Device Emulation Library - Python bindings
 python3-evemu - Linux Input Event Device Emulation Library - Python3 bindings
Closes: 706155
Changes: 
 evemu (1.2.0-1) unstable; urgency=low
 .
   * New upstream release.
   * debian/patches/0001-add-evemu-event-manpage.patch: removed
   * debian/control: un-forced Python3 version
 - updated to Standards-Version 3.9.5 (no changes)
   * debian/python3-evemu: fixed paths
   * debian/patches/0005-python3-raise-syntax.patch:
 - fix exception raise syntax for Python3 (closes: #706155)
   * debian/libevemu1.symbols: added new symbols
   * debian/copyright: added new maintainers
Checksums-Sha1: 
 6cbe7a49c297414369d0508f6c8f60d7bb111dd0 2023 evemu_1.2.0-1.dsc
 d05151822e7175fbb92409b7a669b70502e30ea9 498400 evemu_1.2.0.orig.tar.xz
 f48995049884a045f7dc5418c0d5affcafeb0d15 4969 evemu_1.2.0-1.debian.tar.gz
 f1f1886aaccde2a016a0775feec355e31c5d1950 30744 libevemu1_1.2.0-1_amd64.deb
 41caecc71d00cfd0d9fa71abb9abc4928cc1cfaf 22716 python-evemu_1.2.0-1_amd64.deb
 9df505656b95d0a9bd6e8dcc0d714fbf6d59388d 22698 python3-evemu_1.2.0-1_amd64.deb
 49a275ccf2978193201cd907f2012968ff4fd5c4 31124 libevemu-dev_1.2.0-1_amd64.deb
 44695b833f44d76d47ad9fbefbf2a5adf1826f1d 27376 evemu-tools_1.2.0-1_amd64.deb
Checksums-Sha256: 
 6243e570ec441ffada241c3ea56b1f27d4b265c105a2ebc8172ad9bdc413a4a3 2023 
evemu_1.2.0-1.dsc
 bcc2a97a8e10048ff6b9122180d27ccada63d4f8ca89e61e962201a13551f475 498400 
evemu_1.2.0.orig.tar.xz
 510cd408bba5da364094efa30af06da6934731b4622f8029dd7436e3856db152 4969 
evemu_

Bug#721622: More changes needed for libfreeradius-client2

[Jeremy Lainé]

It seems just linking against libfreeradius-client2 is not sufficient, we also 
need to
change the default RADIUS configuration path in the asterisk code. If
libfreeradius-client2 tries to load the old configuration file
(/etc/radiusclient-ng/radiusclient.conf) it bombs with a segfault:

#0  0x7fffab126f38 in rc_conf_int () from
/usr/lib/x86_64-linux-gnu/libfreeradius-client.so.2
#1  0x7fffab127108 in test_config () from
/usr/lib/x86_64-linux-gnu/libfreeradius-client.so.2
#2  0x7fffab127605 in rc_read_config () from
/usr/lib/x86_64-linux-gnu/libfreeradius-client.so.2
#3  0x7fff9fb011d1 in load_module () at cdr_radius.c:268
#4  0x004cf590 in start_resource (mod=0xefa870) at loader.c:845
#5  0x004d0300 in start_resource (mod=) at loader.c:1037
#6  load_resource_list (load_order=load_order@entry=0x7fffc480,
global_symbols=global_symbols@entry=0, 
mod_count=mod_count@entry=0x7fffc47c) at
loader.c:1047
#7  0x004d0605 in load_modules (preload_only=preload_only@entry=0) at 
loader.c:1200
#8  0x00426ded in main (argc=, argv=) at 
asterisk.c:4239

Jeremy


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

Bug#732034: bison: FTBFS: mv: cannot stat 'examples/extracted.stamp.tmp': No such file or directory

[Chuan-kai Lin]

On Thu, Dec 12, 2013 at 10:42 AM, Sven Joachim  wrote:
> It seems there is a problem with parallel builds, I could reproduce it
> with "dpkg-buildpackage -j2", but not in a non-parallel build.

The race condition seems to be triggered by the inability to extract
program examples from the info file (because bison.info in the bison
Debian package is empty - the actual file had been moved to bison-doc
due to DFSG non-compliance).

I created a patch to disable example code extraction in the makefile,
which seem to have fixed parallel builds.  The patch still needs some
work, and I will try to upload a fixed package over the weekend.

Thanks,

-- 
Chuan-kai Lin


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

Bug#732015: marked as done (has_binary_operator.hp:50: Parse error at "BOOST_JOIN")

[Debian Bug Tracking System]

Your message dated Fri, 13 Dec 2013 09:18:18 +0100
with message-id 

and subject line 
has caused the Debian Bug report #732015,
regarding has_binary_operator.hp:50: Parse error at "BOOST_JOIN"
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.)


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

For some reason I am not able to compile gofigure2 anymore, it fails with:

[ 27%] Generating moc_QGoCreateMeshDialog.cxx
cd 
/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/build/Code/GUI/lib
&& /usr/bin/moc-qt4
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/build/Main
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/Main
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/build/Code/ExternalCode/ctk
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/Code/ExternalCode/ctk
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/build/Code/ExternalCode/PoissonReconstruction
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/Code/ExternalCode/PoissonReconstruction
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/Code/ExternalCode/itkQt
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/build/Code/ExternalCode/itkQt
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/build/Code/ExternalCode/vtkLSM
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/Code/ExternalCode/vtkLSM
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/build/Code/ExternalCode/MegaVTK/vtkRenderingAddOn
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/Code/ExternalCode/MegaVTK/vtkRenderingAddOn
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/build/Code/ExternalCode/MegaVTK/vtkItk
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/Code/ExternalCode/MegaVTK/vtkItk
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/build/Code/ExternalCode/MegaVTK
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/Code/ExternalCode/MegaVTK
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/build/Code/GUI/src
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/Code/GUI/src
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/build/Interfaces
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/Interfaces
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/build/Code/GUI/lib/LineageViewer
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/Code/GUI/lib/LineageViewer
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/build/Code/GUI/lib/TransferFunctionEditor
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/Code/GUI/lib/TransferFunctionEditor
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/build/Code/GUI/lib/TraceEditing
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/Code/GUI/lib/TraceEditing
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/build/Code/GUI/lib/Wizard
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/Code/GUI/lib/Wizard
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/build/Code/GUI/lib/Video
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/Code/GUI/lib/Video
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/build/Code/GUI/lib/VisualizationTraceContainers
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/Code/GUI/lib/VisualizationTraceContainers
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/build/Code/GUI/lib/SynchronizedViews
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/build/Code/GUI/lib/SynchronizedViews
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0/Code/GUI/lib/DBManager
-I/home/mathieu/debian/debian-med/trunk/packages/gofigure2/trunk/gofigure2-0.9.0

Bug#732047: Purging inn2 destroys /var/lib/news even if inn2-lfs is installed

[Richard Kettlewell]

Package: inn2
Severity: critical

As subject.  Having done the following, over a period of time:

   install inn2
   discover it doesn't work at all (bug 655748)
   remove inn2
   install inn2
   purge inn2

The result is that the active, history and newsgroups files are deleted 
without warning.


ttfn/rjk


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

Bug#724215: marked as done (eliom: FTBFS: make[1]: *** No rule to make target `Makefile.config'. Stop.)

[Debian Bug Tracking System]

Your message dated Fri, 13 Dec 2013 09:13:28 +0100
with message-id <52aac1a8.3060...@debian.org>
and subject line Re: Bug#724215: eliom: FTBFS: make[1]: *** No rule to make 
target `Makefile.config'.  Stop.
has caused the Debian Bug report #724215,
regarding eliom: FTBFS: make[1]: *** No rule to make target `Makefile.config'.  
Stop.
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.)


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

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with ocaml
>dh_testdir
>dh_auto_clean
> make[1]: Entering directory `/«PKGBUILDDIR»'
> Makefile:1: Makefile.config: No such file or directory
> make[1]: *** No rule to make target `Makefile.config'.  Stop.
> make[1]: Leaving directory `/«PKGBUILDDIR»'
> dh_auto_clean: make -j1 distclean returned exit code 2
> make: *** [clean] Error 2

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/09/22/eliom_3.0.3-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 ---
Version: 3.0.3-2

Le 22/09/2013 19:58, David Suárez a écrit :
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> [...]

This is obviously fixed...

-- 
Stéphane--- End Message ---

Processed:

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #729515 {Done: Mathieu Malaterre } [gdcm] java 
compilation should target 1.5
Severity set to 'grave' from 'normal'

-- 
729515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729515
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:

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #729748 {Done: Mathieu Malaterre } [gdcm] Fwd: Comments 
regarding gdcm_2.4.0-1_amd64.changes
Severity set to 'serious' from 'important'

-- 
729748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729748
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#705023: Fix to #705023

[Arturo Borrero Gonzalez]

On 12 December 2013 21:29, Arturo Borrero Gonzalez
 wrote:
>
> I am triying to fix #705023. I forked the main corosync packaging git
> repo and pushed a commit to mine.
>

I'm sorry,

I miss that the source package version you had in the git repo was
1.4.2-3, instead of the latest 2.3.0-1.
My patch was for 1.4.2-3 and should be for 2.3.0-1. I will fix this
situation and let you know.

Are you packaging somewhere other than [0] ?

Regards.

[0] http://anonscm.debian.org/gitweb/?p=debian-ha/corosync.git;a=summary

-- 
Arturo Borrero González


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