Bug#823005: pepperflashplugin-nonfree: Missing PGP key

[Trent W. Buck]

Andreas Ferber wrote:
> Package: pepperflashplugin-nonfree
> Version: 1.8.1
> Severity: grave
> Justification: renders package unusable
>
> Google apparently started using a new PGP key, which leads to: [...]
> Appending the new key to /usr/lib/pepperflashplugin-nonfree/pubkey-google.txt
> solves the problem for me. The old key seems to still be needed, since
> with only the new key ih pubkey-google.txt I'm getting the same error
> with a different key id.

FYI there was an email from Google about this on another ticket:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818540#34

Bug#781501: marked as done (gnote segfaults when it can't find a .note file)

[Debian Bug Tracking System]

Your message dated Mon, 02 May 2016 04:19:52 +
with message-id 
and subject line Bug#781501: fixed in gnote 3.20.0-2
has caused the Debian Bug report #781501,
regarding gnote segfaults when it can't find a .note file
to be marked as done.

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

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


-- 
781501: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: gnote
version: 3.14.2-1
severity: grave
reason: gnote is unusable with this

When I manually created this file, I could start gnote and use it normally.

I had just installed it and using it for the first time.

pravi@savannah:~/forge/diaspora$ gnote
Segmentation fault (core dumped)
pravi@savannah:~/forge/diaspora$ gdb gnote
GNU gdb (Debian 7.7.1-2) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gnote...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/gnote
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffea870700 (LWP 5454)]
[New Thread 0x7fffe9e62700 (LWP 5455)]

(gnote:5450): glibmm-CRITICAL **:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 1
what  : Error opening file
'/home/pravi/.local/share/gnote/33c7ece0-72fa-4c6a-b27f-84cf78f04e84.note':
No such file or directory

[New Thread 0x7fffe9661700 (LWP 5456)]
[Thread 0x7fffea870700 (LWP 5454) exited]
[Thread 0x7fffe9e62700 (LWP 5455) exited]
[Thread 0x77fa9a00 (LWP 5450) exited]
[Inferior 1 (process 5450) exited with code 01]
(gdb)



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: gnote
Source-Version: 3.20.0-2

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

Debian distribution maintenance software
pp.
Vincent Cheng  (supplier of updated gnote 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, 01 May 2016 19:23:19 -0700
Source: gnote
Binary: gnote
Architecture: source
Version: 3.20.0-2
Distribution: unstable
Urgency: medium
Maintainer: Vincent Cheng 
Changed-By: Vincent Cheng 
Description:
 gnote  - desktop note taking program using Wiki style links
Closes: 781501
Changes:
 gnote (3.20.0-2) unstable; urgency=medium
 .
   * Add debian/patches/fix-data-migration-crash.patch to fix crash on first
 run when data migration is required. (Closes: #781501)
   * Update Standards version to 3.9.8, no changes required.
   * Update debian/copyright.
Checksums-Sha1:
 92f76441e3f2bb79b82ba13b10b6d876aae293de 2187 gnote_3.20.0-2.dsc
 a8d8aa1d347577d3139a6f89c40cc1ee68af4d66 7484 gnote_3.20.0-2.debian.tar.xz
Checksums-Sha256:
 153296aeb199e8169011caa0021312a427f7987ca2911a6c61d42c62af480ea8 2187 
gnote_3.20.0-2.dsc
 41da41af5ee0b8c3a115f0074d2d9e019c5d6b8049467db96bee73feb7d9bbdf 7484 
gnote_3.20.0-2.debian.tar.xz
Files:
 cbd73566e93db28f4313e618896e637b 2187 gnome optional gnote_3.20.0-2.dsc
 477a0983662efe79d5dcc960fbbb497f 7484 gnome optional 
gnote_3.20.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXJr81AAoJEI7tzBuqHzL/rF0QAJj+6ui0Qp6LldQkIQxM6BpE
xGxkqBFN5DrHa6L6qrmEykCoFgwWEJYGMDpA2KVE1NCALNule2R1mYPItN3h7HvS

Bug#818709: marked as done (RM: php-mail-mimedecode -- ROM; PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Mon, 02 May 2016 01:46:10 +
with message-id 
and subject line Bug#818709: Removed package(s) from unstable
has caused the Debian Bug report #818709,
regarding RM: php-mail-mimedecode -- ROM; PHP 7.0 Transition
to be marked as done.

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

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


-- 
818709: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-mail-mimedecode
Version: 1.5.5-3
Severity: serious

[Filled as RC by a team member to see it autoremoved from testing if
 nobody disagrees. Please, do downgrade it with an explanation if you
 disagree.]

This package has no reverse dependencies anymore in Stretch, and hasn’t
seen any activity upstream in over five years. There is a priori little
point in shipping php-mail-mimedecode with the next Debian stable
release.

I don’t intend to follow up with an RM request since Thomas said he’d
wish to see extplorer in Debian again at some point.

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.5.5-3+rm

Dear submitter,

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

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

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

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

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

Bug#818709: marked as done (RM: php-mail-mimedecode -- ROM; PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Mon, 02 May 2016 01:46:05 +
with message-id 
and subject line Bug#818709: Removed package(s) from unstable
has caused the Debian Bug report #818709,
regarding RM: php-mail-mimedecode -- ROM; PHP 7.0 Transition
to be marked as done.

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

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


-- 
818709: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-mail-mimedecode
Version: 1.5.5-3
Severity: serious

[Filled as RC by a team member to see it autoremoved from testing if
 nobody disagrees. Please, do downgrade it with an explanation if you
 disagree.]

This package has no reverse dependencies anymore in Stretch, and hasn’t
seen any activity upstream in over five years. There is a priori little
point in shipping php-mail-mimedecode with the next Debian stable
release.

I don’t intend to follow up with an RM request since Thomas said he’d
wish to see extplorer in Debian again at some point.

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

php-mail-mimedecode |1.5.5-3 | source, all

--- Reason ---
ROM; PHP 7.0 transition
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 818...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/818709

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

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

Bug#759972: marked as done (php-xml-serializer: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Mon, 02 May 2016 01:47:43 +
with message-id 
and subject line Bug#819322: Removed package(s) from unstable
has caused the Debian Bug report #759972,
regarding php-xml-serializer: FTBFS: tests 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.)


-- 
759972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-xml-serializer
Version: 0.20.2-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140830 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/«PKGBUILDDIR»'
> dh_link -O--buildsystem=phppear
> chmod +x ./debian/tests_run
> ./debian/tests_run
> PHPUnit 3.7.28 by Sebastian Bergmann.
> 
> . 65 / 73 ( 
> 89%)
> F...
> 
> Time: 297 ms, Memory: 7.50Mb
> 
> There was 1 failure:
> 
> 1) /«PKGBUILDDIR»/XML_Serializer-0.20.2/tests/bug-15602.phpt
> --- Expected
> +++ Actual
> @@ @@
>  
> -
> -  
> +
> +  
>  I say: A, B  C, d!
>
>I say: 
> A, B  C, d!
>  
> 
> 
> FAILURES!
> Tests: 73, Assertions: 81, Failures: 1.
> make[1]: *** [override_dh_link] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/08/30/php-xml-serializer_0.20.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. The build
was done with DEB_BUILD_OPTIONS="parallel=4", so if your packaging tries
to support this, it might be a good idea to explore whether this might
be the cause of the failure.
--- End Message ---
--- Begin Message ---
Version: 0.20.2-3+rm

Dear submitter,

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

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

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

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

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

Bug#818060: FTBFS: pep8 module is now in python-pep8 package

[Brian May]

Hello,

As per documentation at https://wiki.debian.org/NmuDep, I am about to upload
the following change to delayed/2 in order to fix this RC bug.

Regards


dpkg-source: warning: extracting unsigned source package 
(/home/brian/tree/debian/nmu/python-shortuuid/shortuuid_0.4.3-1.1.dsc)
diff -Nru shortuuid-0.4.3/debian/changelog shortuuid-0.4.3/debian/changelog
--- shortuuid-0.4.3/debian/changelog2016-02-13 17:11:21.0 +1100
+++ shortuuid-0.4.3/debian/changelog2016-05-02 11:13:08.0 +1000
@@ -1,3 +1,10 @@
+shortuuid (0.4.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS. Add python-pep8 to build-depends. Closes: #818060.
+
+ -- Brian May   Mon, 02 May 2016 11:12:25 +1000
+
 shortuuid (0.4.3-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru shortuuid-0.4.3/debian/control shortuuid-0.4.3/debian/control
--- shortuuid-0.4.3/debian/control  2015-10-08 10:13:39.0 +1100
+++ shortuuid-0.4.3/debian/control  2016-05-02 07:49:34.0 +1000
@@ -6,7 +6,7 @@
dh-python,
python-all (>= 2.6),
python-setuptools,
-   pep8,
+   python-pep8,
python3-all (>= 3.2),
python3-setuptools,
python3-pep8,
-- 
Brian May 

Bug#785054: marked as done (harden-doc: Please remove dependency on dpsyco)

[Debian Bug Tracking System]

Your message dated Sun, 01 May 2016 23:20:16 +
with message-id 
and subject line Bug#785054: fixed in harden-doc 3.18.1
has caused the Debian Bug report #785054,
regarding harden-doc: Please remove dependency on dpsyco
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.)


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

Hi harden-doc maintainers.

I would like you to kindly remove the dependency on dpsyco-devel. I have
attached a patch for that. The reason is that I have requested the removal
of psyco source and this reverse dependency prevents that from happening.
See bug #784869.

I know it is my own fault that we have this dependency as I have added it
myself sometime many years ago. I do not see the point of having it anymore.

Please let me know if you want me to NMU the change.

Thanks in advance!

// Ola

-- 
 --- Inguza Technology AB --- MSc in Information Technology 
/  o...@inguza.comAnnebergsslingan 37\
|  o...@debian.org   654 65 KARLSTAD|
|  http://inguza.com/Mobile: +46 (0)70-332 1551 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
 ---
diff -ur harden-doc-3.18.old/debian/control harden-doc-3.18/debian/control
--- harden-doc-3.18.old/debian/control	2015-01-17 15:27:21.0 +0100
+++ harden-doc-3.18/debian/control	2015-05-11 23:17:33.384718877 +0200
@@ -5,7 +5,6 @@
 Uploaders: Thijs Kinkhorst 
 Build-Depends: debhelper (>= 9)
 Build-Depends-Indep: debiandoc-sgml,
- dpsyco-devel,
  ghostscript,
  perl,
  po4a,
diff -ur harden-doc-3.18.old/debian/rules harden-doc-3.18/debian/rules
--- harden-doc-3.18.old/debian/rules	2015-01-17 15:27:21.0 +0100
+++ harden-doc-3.18/debian/rules	2015-05-11 23:17:25.132949065 +0200
@@ -25,7 +25,6 @@
 	dh_installdirs
 
 	$(MAKE) install
-	dpsch-cvsclean
 
 
 # Build architecture-independent files here.
--- End Message ---
--- Begin Message ---
Source: harden-doc
Source-Version: 3.18.1

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

Debian distribution maintenance software
pp.
Javier Fernández-Sanguino Peña  (supplier of updated 
harden-doc 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, 02 May 2016 00:35:17 +0200
Source: harden-doc
Binary: harden-doc
Architecture: source all
Version: 3.18.1
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernández-Sanguino Peña 
Changed-By: Javier Fernández-Sanguino Peña 
Description:
 harden-doc - useful documentation to secure a Debian system
Closes: 785054
Changes:
 harden-doc (3.18.1) unstable; urgency=medium
 .
   * Remove psyco-devel dependency (Closes: #785054)
   * Update to latest sources in DDP SVN
   * debian/rules: Move to use debhelper utilities instead of having manual
 targets
   * debian/control:
   - Use UTF-8 for maintainer name, use the proper email address
Checksums-Sha1:
 09a46b62dad51da02a01224a72273d49febcf9fa 1832 harden-doc_3.18.1.dsc
 e5b6ac4592dea51d3c990509ec546e638d33e394 1122100 harden-doc_3.18.1.tar.xz
 6b49faade61336f7190b4b6c94ada61b453e99fc 5729548 harden-doc_3.18.1_all.deb
Checksums-Sha256:
 dcc24688c8556786bfa0c08b32a11ed218dc993c36db8ba58c095088587b6a8b 1832 
harden-doc_3.18.1.dsc
 9b8b9136eba729a9f8a940f5feb19cd3cc2b79280d2c821a2aded92f222dc8e0 1122100 
harden-doc_3.18.1.tar.xz
 12ffbf16d304eecfe05be223913b82674a19db26f1d19c20d8a1537925c5a8eb 5729548 
harden-doc_3.18.1_all.deb
Files:
 b84893c40c9d77b725e7c2b51e87d98f 1832 doc extra harden-doc_3.18.1.dsc
 aeb26e3fe8c16e94aba4b75cda09c4de 1122100 doc extra harden-doc_3.18.1.tar.xz
 30184109bf8aff63a05e8883eb6a5722 5729548 doc extra harden-doc_3.18.1_all.deb

-BEGIN 

Processed: severity of 821337 is important

[Debian Bug Tracking System]

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

> severity 821337 important
Bug #821337 [src:gtk+3.0] FTBFS on mipsel(64), 
gtk+3.0-3.20.3/testsuite/reftests/button-wrapping.ui: FAIL
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#822660: marked as done (seelablet-common: fails to remove in chroot: postinst chokes on udevadm call)

[Debian Bug Tracking System]

Your message dated Sun, 01 May 2016 22:27:58 +
with message-id 
and subject line Bug#822660: fixed in seelablet 1.0-1
has caused the Debian Bug report #822660,
regarding seelablet-common: fails to remove in chroot: postinst chokes on 
udevadm call
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.)


-- 
822660: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: seelablet-common
Version: 0.1.9-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to remove.

udevadm in postrm probably needs similar handling as in postinst.

I also noticed your package failed to purge due
to a command not found. According to policy 7.2 you cannot rely on the
depends being available during purge, only the essential packages are
available for sure. So you need to check udevadm for existence first.

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

'apt-get', 'remove', ... 'seelablet-common'
...
  Removing seelablet-common (0.1.9-4) ...
  dpkg: error processing package seelablet-common (--remove):
   subprocess installed post-removal script returned error exit status 2

0m34.6s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpagKyJA', 'dpkg', 
'--purge', 'seelablet-common']
0m34.7s DUMP: 
  (Reading database ... 7358 files and directories currently installed.)
  Removing seelablet-common (0.1.9-4) ...
  /var/lib/dpkg/info/seelablet-common.postrm: 24: 
/var/lib/dpkg/info/seelablet-common.postrm: udevadm: not found
  dpkg: error processing package seelablet-common (--purge):
   subprocess installed post-removal script returned error exit status 127
  Errors were encountered while processing:
   seelablet-common
0m34.7s DEBUG: Command failed (status=1), but ignoring error: ['chroot', 
'/tmp/piupartss/tmpagKyJA', 'dpkg', '--purge', 'seelablet-common']



cheers,

Andreas


seelablet-common_0.1.9-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: seelablet
Source-Version: 1.0-1

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated seelablet 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, 01 May 2016 18:04:27 +0200
Source: seelablet
Binary: seelablet python-seelablet python3-seelablet seelablet-common 
seelablet-doc
Architecture: source all
Version: 1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 python-seelablet - python library for SEELablet
 python3-seelablet - python3 library for SEELablet
 seelablet  - python library and scripts for SEELablet experiment box
 seelablet-common - common files for SEELablet
 seelablet-doc - end-user and programmer documentation for SEELablet
Closes: 822660
Changes:
 seelablet (1.0-1) unstable; urgency=medium
 .
   * New upstream release
   * rewritten the script to get the newest upstream package; now applications
 are downloaded from a sister repository in addition to the library.
   * upraded Standards-Version to 3.9.8
   * fixed postinst and postrm scripts. Closes: #822660
Checksums-Sha1:
 fa12d4540e40b1b00b7f289936f46d5c6d4fcaad 2064 seelablet_1.0-1.dsc
 055357a5060a4342131e4c6760da7b5fb32da5e8 577820 seelablet_1.0.orig.tar.xz
 04f1fa76c3cc949a74fc17093cd697bb2c8d376b 22296 seelablet_1.0-1.debian.tar.xz
 4b9c75478522a337e9bab19cd81a17b9d597f3cc 164722 python-seelablet_1.0-1_all.deb
 a0de62a1fc8fa4b95036851dde492038e4343e92 164830 python3-seelablet_1.0-1_all.deb
 2984303ee4689c01efb454e1e62d29a9e173cc97 381352 seelablet-common_1.0-1_all.deb
 33deaa1171eb692154f285c5db6800848d56c5ff 117138 seelablet-doc_1.0-1_all.deb
 37f1c1bc999d2a0767a0b9d31544572e7eccd973 7022 seelablet_1.0-1_all.deb
Checksums-Sha256:
 

Bug#819079: marked as done (ruby-powerpack ships without a gemspec file)

[Debian Bug Tracking System]

Your message dated Sun, 01 May 2016 22:27:44 +
with message-id 
and subject line Bug#819079: fixed in ruby-powerpack 0.1.1-3
has caused the Debian Bug report #819079,
regarding ruby-powerpack ships without a gemspec file
to be marked as done.

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

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


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

Package: ruby-powerpack
Version: 0.1.1-2
Severity: serious
Tags: sid stretch

ruby-powerpack ships without a gemspec file, making it useless to fulfil 
dependencies.
--- End Message ---
--- Begin Message ---
Source: ruby-powerpack
Source-Version: 0.1.1-3

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

Debian distribution maintenance software
pp.
Sebastien Badia  (supplier of updated ruby-powerpack package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 29 Mar 2016 00:35:22 +0200
Source: ruby-powerpack
Binary: ruby-powerpack
Architecture: source
Version: 0.1.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Sebastien Badia 
Description:
 ruby-powerpack - Useful extensions to core Ruby classes
Closes: 819079
Changes:
 ruby-powerpack (0.1.1-3) unstable; urgency=medium
 .
   * Rebuild, using a newer version of gem2deb (Closes: #819079)
Checksums-Sha1:
 42a3ca749fe0a205f88e249a06e3736261fb2766 2084 ruby-powerpack_0.1.1-3.dsc
 b479544cb34216a3090b7ba1bf172598e8655af1 2308 
ruby-powerpack_0.1.1-3.debian.tar.xz
Checksums-Sha256:
 eb885fa7db27114ec3c14bb91ae7716385c0f60e0803c53a7da6e26bad690cd5 2084 
ruby-powerpack_0.1.1-3.dsc
 63e1120fc491b01f8046257671b2d30dc64815aabf33499481abde6b84a0f8e3 2308 
ruby-powerpack_0.1.1-3.debian.tar.xz
Files:
 7295b0762b52b589a0db2640a7324735 2084 ruby optional ruby-powerpack_0.1.1-3.dsc
 ea6293ae89f6723da70bfa6bde84b3a4 2308 ruby optional 
ruby-powerpack_0.1.1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXJnjoAAoJEFwT1tuTBS4D/4cP/3We5ES3OZAdiNVuCKXUBaFd
mNBJnLQ6Xc0zs21G8a8Ty/Pf8kqyQCiaIZmVe7qcUPljmDtcWvjogCo2c3MCmduA
v6O9MrLjOGU//XC6PzAwJq90lSq/+SUW6AR1zN2FC4GNdfywxL4RXKwuFJYHnjq6
Yi0eURL0C2VobN5lbRl2f98GQsnyejty6uCopWYAHBMdnFUSjoMT8xJpH8urTOhf
QHAxkrXGAtRb/Uzf0QGTgNQdR8PXes9j7SHUrLeBFjc0j1W3tpDIhls8rQJAJNBx
1AblABzX0BvegzXRohT4ouYNqKD2mIGiK/n+eGy/YwfOMIKRWpkIl9yA26D94M+z
Yo0ps6IBgtVj0IuiJl/SQFsNZjIxT7ZU3+8+GBLOajeOPat+q5aOj3mGwzWmpmYa
ZVmfxGlhOUSI+StyckVehdCy/TMVvioKNce59+5+Usk8vB4ZjCUgtliXYwAAOl33
FvBczcl4LOcr+bv7qsJL5hZGurP4vvqUAzJjAFQ5ZG2pLUSJ/7iahU70yqwNo9aM
GCT6AgVhtPYfTUteDhlrN8fIR6PiT4eiebLWP8iqIzoEr4ULsZU7ZU+W0vrDdqZc
atVfU5TXQ77I8oHgfQ08tko3FAGu6ztXmcQwuKJRgO/lE7Icg2sfTSGM10+Tp4vm
YcVQEMvmXIw9sNRg1ouj
=VxLR
-END PGP SIGNATURE End Message ---

Bug#815802: marked as done (ruby-gir-ffi: Requiring 'gir_ffi' fails)

[Debian Bug Tracking System]

Your message dated Sun, 01 May 2016 22:27:26 +
with message-id 
and subject line Bug#815802: fixed in ruby-gir-ffi 0.9.0-3
has caused the Debian Bug report #815802,
regarding ruby-gir-ffi: Requiring 'gir_ffi' 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.)


-- 
815802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-gir-ffi
Version: 0.9.0-1
Severity: important

Dear Maintainer,

requiring 'gir_ffi' fails when using just the Debian packages, I have
a file with just this line:

require 'gir_ffi'

and when I execute it I get this error:

$ ruby test.rb 
/usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot 
load such file -- ffi/bit_masks (LoadError)
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/vendor_ruby/gir_ffi/core.rb:2:in `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/vendor_ruby/gir_ffi.rb:1:in `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from test.rb:1:in `'

It looks like this happens because the ffi-bit_masks[1] plugin is
missing and it's not available in Debian so it can't be pulled in
automatically as a dependency of ruby-gir-ffi.

[1] https://github.com/postmodern/ffi-bit_masks

by installing the plugin via gem the error is gone:

$ sudo gem install ffi-bit_masks
[sudo] password for user: 
Fetching: ffi-bit_masks-0.1.0.gem (100%)
Successfully installed ffi-bit_masks-0.1.0
Parsing documentation for ffi-bit_masks-0.1.0
Installing ri documentation for ffi-bit_masks-0.1.0
Done installing documentation for ffi-bit_masks after 0 seconds
1 gem installed
$ ruby test.rb 
$

However if I install the ruby-gir-ffi as a Debian package I would like
not to have to pull stuff in using gem.

I guess ffi-bit_masks would need to be packaged to make ruby-gir-ffi
work as expected when installed as a Debian package.

Thanks,
   Antonio


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

Kernel: Linux 4.5.0-rc4-ao2 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages ruby-gir-ffi depends on:
ii  libgirepository-1.0-1   1.46.0-4
ii  libglib2.0-dev  2.46.2-3
ii  ruby1:2.2.4
ii  ruby-ffi1.9.10debian-1
ii  ruby-indentation0.1.1-1
ii  ruby2.1 [ruby-interpreter]  2.1.5-4
ii  ruby2.2 [ruby-interpreter]  2.2.4-1

ruby-gir-ffi recommends no packages.

Versions of packages ruby-gir-ffi suggests:
ii  gir1.2-glib-2.01.46.0-4
ii  gir1.2-gtk-3.0 3.18.7-1
pn  gir1.2-webkit-1.0  

-- no debconf information
-- 
Antonio Ospite
http://ao2.it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
--- End Message ---
--- Begin Message ---
Source: ruby-gir-ffi
Source-Version: 0.9.0-3

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

Debian distribution maintenance software
pp.
Christian Hofstaedtler  (supplier of updated ruby-gir-ffi 
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, 01 May 2016 21:40:40 +
Source: ruby-gir-ffi
Binary: ruby-gir-ffi
Architecture: source
Version: 0.9.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Christian Hofstaedtler 
Description:
 ruby-gir-ffi - 

Bug#822973: marked as done (idjc displays "something bad happened" and doesn't start (undefined symbol: avcodec_alloc_frame))

[Debian Bug Tracking System]

Your message dated Sun, 01 May 2016 22:21:17 +
with message-id 
and subject line Bug#822973: fixed in idjc 0.8.15-2
has caused the Debian Bug report #822973,
regarding idjc displays "something bad happened" and doesn't start (undefined 
symbol: avcodec_alloc_frame)
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.)


-- 
822973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: idjc
Version: 0.8.15-1+b1
Severity: important

Hi,

 $ idjc
jack client ID: idjc_default
something bad happened

I altered part of main.py to get a proper trace and got this:

Traceback (most recent call last):
  File "/usr/bin/idjc", line 32, in 
exit(idjc.main())
  File "/usr/lib/idjc/site-packages/idjc/__init__.py", line 119, in main
return maingui.main()
  File "/usr/lib/idjc/site-packages/idjc/maingui.py", line 3995, in main
run_instance = MainWindow()
  File "/usr/lib/idjc/site-packages/idjc/maingui.py", line 3047, in __init__
self.backend = ctypes.CDLL(FGlobs.backend)
  File "/usr/lib/python2.7/ctypes/__init__.py", line 365, in __init__
self._handle = _dlopen(self._name, mode)
OSError: /usr/lib/idjc/idjc.so: undefined symbol: avcodec_alloc_frame

The symbol was apparently marked avcodec_alloc_frame, I guess if finally
got removed in a recent ffmpeg upload.


thanks,
Fred

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

Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages idjc depends on:
ii  jackd 5
ii  libavcodec57  7:3.0.1-3
ii  libavformat57 7:3.0.1-3
ii  libavutil55   7:3.0.1-3
ii  libc6 2.22-7
ii  libflac8  1.3.1-4
ii  libglib2.0-0  2.48.0-1
ii  libjack-jackd2-0 [libjack-0.116]  1.9.10+20150825git1ed50c92~dfsg-1
ii  libmp3lame0   3.99.5+repack1-9+b1
ii  libmpg123-0   1.22.4-1
ii  libogg0   1.3.2-1
ii  libopus0  1.1.2-1
ii  libsamplerate00.1.8-8
ii  libshout-idjc32.3.1-2
ii  libsndfile1   1.0.25-10
ii  libspeex1 1.2~rc1.2-1
ii  libswresample27:3.0.1-3
ii  libvorbis0a   1.3.5-3
ii  libvorbisenc2 1.3.5-3
ii  python2.7.11-1
ii  python-dbus   1.2.4-1
ii  python-gobject3.20.0-2
ii  python-gtk2   2.24.0-4
ii  python-irc8.5.3+dfsg-2
ii  python-mutagen1.31-1
ii  python2.7 2.7.11-8
pn  python:any

Versions of packages idjc recommends:
ii  python-eyed3  0.6.18-1

idjc suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: idjc
Source-Version: 0.8.15-2

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated idjc 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, 01 May 2016 23:10:29 +0200
Source: idjc
Binary: idjc
Architecture: source
Version: 0.8.15-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Sebastian Ramacher 
Description:
 idjc   - graphical shoutcast/icecast client
Closes: 822973
Changes:
 idjc (0.8.15-2) unstable; urgency=medium
 .
   * Team upload.
   * debian/patches: Apply upstream 

Processed: Re: Bug#823186: bump severity

[Debian Bug Tracking System]

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

> severity 823186 grave
Bug #823186 [chromium] chromium: crashes on many websites
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#807735: NMU for gmpc-plugins

[Antoine Beaupré]

On 2016-05-01 11:56:38, Étienne Millon wrote:
> Thanks, I just pushed the diff to the git repository.
> I actually do not use this package very often, so if you would like to
> adopt it I'm all for it :) (same applies to gmpc).
> Let me know what you think.

I'd be glad to. Next time I need to make an update, I'll adopt it if
it's okay with you. :)

Do you have special communications with upstream to get notified of
releases (if there's upstream still?)

a.
-- 
Being cynical is the only way to deal with modern civilization — you
can't just swallow it whole.
- Frank Zappa

Bug#822973: marked as pending

[Sebastian Ramacher]

tag 822973 pending
thanks

Hello,

Bug #822973 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=pkg-multimedia/idjc.git;a=commitdiff;h=9cb23cb

---
commit 9cb23cbd1fd980eb7e3e77635962617abbc143af
Author: Sebastian Ramacher 
Date:   Sun May 1 23:07:17 2016 +0200

Finalize changelog

diff --git a/debian/changelog b/debian/changelog
index 3863f98..70cb26e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+idjc (0.8.15-2) unstable; urgency=medium
+
+  * Team upload.
+  * debian/patches: Apply upstream patches to fix issues with ffmpeg 3.0.
+(Closes: #822973)
+
+ -- Sebastian Ramacher   Sun, 01 May 2016 23:07:08 +0200
+
 idjc (0.8.15-1) unstable; urgency=medium
 
   * Team upload.

Processed: Bug#822973 marked as pending

[Debian Bug Tracking System]

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

> tag 822973 pending
Bug #822973 [idjc] idjc displays "something bad happened" and doesn't start 
(undefined symbol: avcodec_alloc_frame)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: reassign 822315 to src:ruby-gnome2, forcibly merging 805804 822315

[Debian Bug Tracking System]

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

> reassign 822315 src:ruby-gnome2
Bug #822315 [ruby-clutter-gstreamer] ruby-clutter-gstreamer: depends on 
clutter-gst-2.0 which is going to be removed
Bug reassigned from package 'ruby-clutter-gstreamer' to 'src:ruby-gnome2'.
No longer marked as found in versions ruby-gnome2/2.2.5-4.
Ignoring request to alter fixed versions of bug #822315 to the same values 
previously set
> forcemerge 805804 822315
Bug #805804 [src:ruby-gnome2] please remove ruby-clutter-gstreamer package
Bug #822315 [src:ruby-gnome2] ruby-clutter-gstreamer: depends on 
clutter-gst-2.0 which is going to be removed
Severity set to 'normal' from 'important'
805640 was blocked by: 808512 805804 808518
805640 was not blocking any bugs.
Added blocking bug(s) of 805640: 822315
Merged 805804 822315
> thanks
Stopping processing here.

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

Processed: reassign 821821 to src:ruby-gollum-lib, forcibly merging 823046 821821, affects 823046

[Debian Bug Tracking System]

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

> reassign 821821 src:ruby-gollum-lib
Bug #821821 [ruby-gollum-lib] gitlab: fails to install in sid: Bundler could 
not find compatible versions for gem "github-markup"
Bug reassigned from package 'ruby-gollum-lib' to 'src:ruby-gollum-lib'.
Ignoring request to alter found versions of bug #821821 to the same values 
previously set
Ignoring request to alter fixed versions of bug #821821 to the same values 
previously set
> forcemerge 823046 821821
Bug #823046 [src:ruby-gollum-lib] ruby-gollum-lib: FTBFS:  Could not find 
'github-markup' (~> 1.3.3) - did find: [github-markup-1.4.0] (Gem::LoadError)
Bug #821821 [src:ruby-gollum-lib] gitlab: fails to install in sid: Bundler 
could not find compatible versions for gem "github-markup"
Marked as found in versions ruby-gollum-lib/4.1.0-3.
Merged 821821 823046
> affects 823046 gitlab
Bug #823046 [src:ruby-gollum-lib] ruby-gollum-lib: FTBFS:  Could not find 
'github-markup' (~> 1.3.3) - did find: [github-markup-1.4.0] (Gem::LoadError)
Bug #821821 [src:ruby-gollum-lib] gitlab: fails to install in sid: Bundler 
could not find compatible versions for gem "github-markup"
Added indication that 823046 affects gitlab
Added indication that 821821 affects gitlab
> thanks
Stopping processing here.

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

Processed (with 2 errors): reassign 821821 to ruby-gollum-lib, forcibly merging 823046 821821, affects 823046

[Debian Bug Tracking System]

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

> reassign 821821 ruby-gollum-lib
Bug #821821 [gitlab] gitlab: fails to install in sid: Bundler could not find 
compatible versions for gem "github-markup"
Bug reassigned from package 'gitlab' to 'ruby-gollum-lib'.
No longer marked as found in versions gitlab/8.5.8+dfsg-5.
Ignoring request to alter fixed versions of bug #821821 to the same values 
previously set
> forcemerge 823046 821821
Bug #823046 [src:ruby-gollum-lib] ruby-gollum-lib: FTBFS:  Could not find 
'github-markup' (~> 1.3.3) - did find: [github-markup-1.4.0] (Gem::LoadError)
Unable to merge bugs because:
package of #821821 is 'ruby-gollum-lib' not 'src:ruby-gollum-lib'
Failed to forcibly merge 823046: Did not alter merged bugs.

> affects 823046 gitlab
Failed to mark 823046 as affecting package(s): failed to get lock on 
/org/bugs.debian.org/spool/lock/823046 -- Unable to lock 
/org/bugs.debian.org/spool/lock/823046 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/823046 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/823046 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/823046 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/823046 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/823046 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/823046 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/823046 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/823046 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/823046 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.

> thanks
Stopping processing here.

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

Processed (with 2 errors): forcibly merging 823046 821821, affects 823046

[Debian Bug Tracking System]

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

> forcemerge 823046 821821
Bug #823046 [src:ruby-gollum-lib] ruby-gollum-lib: FTBFS:  Could not find 
'github-markup' (~> 1.3.3) - did find: [github-markup-1.4.0] (Gem::LoadError)
Unable to merge bugs because:
package of #821821 is 'gitlab' not 'src:ruby-gollum-lib'
Failed to forcibly merge 823046: Did not alter merged bugs.

> affects 823046 gitlab
Failed to mark 823046 as affecting package(s): failed to get lock on 
/org/bugs.debian.org/spool/lock/823046 -- Unable to lock 
/org/bugs.debian.org/spool/lock/823046 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/823046 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/823046 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/823046 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/823046 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/823046 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/823046 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/823046 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/823046 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/823046 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.

> thanks
Stopping processing here.

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

Bug#823170: marked as done (golang-testify: Vendors code without attribution)

[Debian Bug Tracking System]

Your message dated Sun, 01 May 2016 19:49:02 +
with message-id 
and subject line Bug#823170: fixed in golang-testify 
1.1.3+git20160418.12.c5d7a69+ds-1
has caused the Debian Bug report #823170,
regarding golang-testify: Vendors code without attribution
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.)


-- 
823170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-testify
Severity: serious
Justification: Policy 12.5

This package is embedding source code for three other distributions without
attribution in debian/copyright:

vendor/github.com/davecgh/go-spew
vendor/github.com/pmezard/go-difflib
vendor/github.com/stretchr/objx


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

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Source: golang-testify
Source-Version: 1.1.3+git20160418.12.c5d7a69+ds-1

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

Debian distribution maintenance software
pp.
Martín Ferrari  (supplier of updated golang-testify 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, 01 May 2016 19:28:18 +
Source: golang-testify
Binary: golang-github-stretchr-testify-dev
Architecture: source all
Version: 1.1.3+git20160418.12.c5d7a69+ds-1
Distribution: unstable
Urgency: high
Maintainer: pkg-go 
Changed-By: Martín Ferrari 
Description:
 golang-github-stretchr-testify-dev - sacred extension to the standard Go 
testing package
Closes: 823170
Changes:
 golang-testify (1.1.3+git20160418.12.c5d7a69+ds-1) unstable; urgency=high
 .
   * Repackage the source, removing third-party code. Closes: #823170.
   * Add these dependencies to debian/control.
   * debian/rules: Add gen-orig-tgz target.
   * debian/watch: Mangle version for repackaging.
Checksums-Sha1:
 21cc2c991397e137e2b2d96b86c0915c65df28ad 2424 
golang-testify_1.1.3+git20160418.12.c5d7a69+ds-1.dsc
 af193ece9679f408a65b54b0d8703bc28242d021 43521 
golang-testify_1.1.3+git20160418.12.c5d7a69+ds.orig.tar.gz
 07a363ee146ed4725ece508f15f36f52bc2a08c5 3192 
golang-testify_1.1.3+git20160418.12.c5d7a69+ds-1.debian.tar.xz
 afa90f14b526a6ff3d57bd55afd433949b6274e4 35394 
golang-github-stretchr-testify-dev_1.1.3+git20160418.12.c5d7a69+ds-1_all.deb
Checksums-Sha256:
 b0fc584f8f0515c92acac6ac39017dd11ecfd8ba9ba3d2a718cf61748c793137 2424 
golang-testify_1.1.3+git20160418.12.c5d7a69+ds-1.dsc
 b838466f3b59cb8d927a30031bdbecc2570c0b10444b502cfb53239d4ae0539e 43521 
golang-testify_1.1.3+git20160418.12.c5d7a69+ds.orig.tar.gz
 5247c6d9c1017a46507dfe7a2b3907edfbfc96a07df7ca7932b89ad687a436b3 3192 
golang-testify_1.1.3+git20160418.12.c5d7a69+ds-1.debian.tar.xz
 41bf40962845b13546a934f20e21826dbfd5f58a9a892b2899bdeb6835c56d26 35394 
golang-github-stretchr-testify-dev_1.1.3+git20160418.12.c5d7a69+ds-1_all.deb
Files:
 cb615aee1ecd25cb35ada60e17669734 2424 devel extra 
golang-testify_1.1.3+git20160418.12.c5d7a69+ds-1.dsc
 910df6b5c530b8dc76b4d1f94f5a3f00 43521 devel extra 
golang-testify_1.1.3+git20160418.12.c5d7a69+ds.orig.tar.gz
 b310494139b41d830099b5131487e40e 3192 devel extra 
golang-testify_1.1.3+git20160418.12.c5d7a69+ds-1.debian.tar.xz
 21d9eae50c3a3e768c5c2070831a46b1 35394 devel extra 
golang-github-stretchr-testify-dev_1.1.3+git20160418.12.c5d7a69+ds-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXJlmgAAoJEF3Y4L+Ro9PaUvkP/0fuC7adRuE4xwZDJQs9DO1u
EWrKTlqnkgRHRrFuWyTBigJCArJGn4O+noCrJH+FSUqKboyVnaYFQ+JFRyXbwniE
6LHB1mlChkzrTIzd6HmBu+PPvXPcL2F7oG82OuUWgpbYlaL+usGtt0KBgwldKUYZ

Processed: Re: #819080: ruby-augeas ships without a gemspec file

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #819080 [ruby-augeas] ruby-augeas ships without a gemspec file
Severity set to 'normal' from 'serious'

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

Bug#819080: #819080: ruby-augeas ships without a gemspec file

[Christian Hofstaedtler]

Control: severity -1 normal

> ruby-augeas ships without a gemspec file,

While this is true, no r-dep in Debian currently loads augeas using
rubygems. Downgrading this bug for now.

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

Processed: Pending fixes for bugs in the golang-testify package

[Debian Bug Tracking System]

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

> tag 823170 + pending
Bug #823170 [src:golang-testify] golang-testify: Vendors code without 
attribution
Added tag(s) pending.
> tag 823170 + pending
Bug #823170 [src:golang-testify] golang-testify: Vendors code without 
attribution
Ignoring request to alter tags of bug #823170 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#818719: marked as done (ruby-rails-deprecated-sanitizer: FTBFS: action_view/helpers/sanitize_helper (LoadError))

[Debian Bug Tracking System]

Your message dated Sun, 01 May 2016 19:34:21 +
with message-id 
and subject line Bug#818719: fixed in ruby-rails-deprecated-sanitizer 1.0.3-2
has caused the Debian Bug report #818719,
regarding ruby-rails-deprecated-sanitizer: FTBFS: 
action_view/helpers/sanitize_helper (LoadError)
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.)


-- 
818719: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818719
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rails-deprecated-sanitizer
Version: 1.0.3-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ruby-rails-deprecated-sanitizer fails to build from source in unstable/amd64:

  [..]
  
  
RUBYLIB=/home/lamby/temp/cdt.20160320085914.YMSdAoy2ta/ruby-rails-deprecated-sanitizer-1.0.3/debian/ruby-rails-deprecated-sanitizer/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-rails-deprecated-sanitizer/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -S rake -f debian/ruby-tests.rake
  /usr/bin/ruby2.3 -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/cdata_node_test.rb" 
"test/deprecated_sanitizer_test.rb" "test/document_test.rb" "test/node_test.rb" 
"test/tag_node_test.rb" "test/text_node_test.rb" "test/tokenizer_test.rb" -v
  /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': 
cannot load such file -- action_view/helpers/sanitize_helper (LoadError)
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from 
/home/lamby/temp/cdt.20160320085914.YMSdAoy2ta/ruby-rails-deprecated-sanitizer-1.0.3/test/test_helper.rb:6:in
 `'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from 
/home/lamby/temp/cdt.20160320085914.YMSdAoy2ta/ruby-rails-deprecated-sanitizer-1.0.3/test/cdata_node_test.rb:1:in
 `'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:15:in `block in 
'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `select'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `'
  rake aborted!
  Command failed with status (1): [ruby -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/cdata_node_test.rb" 
"test/deprecated_sanitizer_test.rb" "test/document_test.rb" "test/node_test.rb" 
"test/tag_node_test.rb" "test/text_node_test.rb" "test/tokenizer_test.rb" -v]
  
  Tasks: TOP => default
  (See full trace by running task with --trace)
  ERROR: Test "ruby2.3" failed. Exiting.
  dh_auto_install: dh_ruby --install 
/home/lamby/temp/cdt.20160320085914.YMSdAoy2ta/ruby-rails-deprecated-sanitizer-1.0.3/debian/ruby-rails-deprecated-sanitizer
 returned exit code 1
  debian/rules:6: recipe for target 'binary' failed
  make: *** [binary] Error 1

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


ruby-rails-deprecated-sanitizer.1.0.3-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: ruby-rails-deprecated-sanitizer
Source-Version: 1.0.3-2

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

Debian distribution maintenance software
pp.
Lucas Albuquerque Medeiros de Moura  (supplier of 
updated ruby-rails-deprecated-sanitizer 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, 31 

Bug#823170: Pending fixes for bugs in the golang-testify package

[pkg-go-maintainers]

tag 823170 + pending
tag 823170 + pending
thanks

Some bugs in the golang-testify package are closed in revision
5eb3d6fcfd1219ded43363c9a37a5778de96a8f1 in branch 'master' by
Martín Ferrari

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-testify.git/commit/?id=5eb3d6f

Commit message:

Repackage the source, removing third-party code. Closes: #823170.

* Repackage the source, removing third-party code. Closes: #823170.
* Add these dependencies to debian/control.

Bug#821436: libtasn1-6: missing build-dep dblatex

[William Bonnet]

Hello
> The error message is red herring, the build will fail on up-to-date sid
> no matter whether dblatex is installed. The issue is in gtk-doc-tools,
> reassiging.
I experienced several weird compilation issues when rebuilding packages
from sid on ppc64 arch. This bug was one of them (mostly issues when
building packages with -j4 flag and reusing an environnement for several
builds).

This issue no longer happen with package currently in sid and a fresh
environnement. Thus i propose to close this bug. No need to keep it open
since i can now build. I will reopen it or recreate another if it
happens again.

Kind regards,

-- 
William BONNET

CTO & Founder / The IT Makers

william.bon...@theitmakers.com
GSM +33 689 376 977 
twitter @theitmakers




signature.asc
Description: OpenPGP digital signature

Bug#823162: pseudo: wrong update-alternatives call in postinst

[Andrew Shadura]

On 1 May 2016 at 18:40, Gian Piero Carrubba  wrote:
> This bug is presumably related to #805937, but I'm reporting it alone as
> it prevents a smooth installation of the package.

> The pseudo package does not contain the fakeroot-pseudo wrapper (as a
> fix for #805937 ?):

Oops, that was a mistake. I'll upload a fixed version tomorrow.

-- 
Cheers,
  Andrew

Bug#823170: golang-testify: Vendors code without attribution

[Martín Ferrari]

Source: golang-testify
Severity: serious
Justification: Policy 12.5

This package is embedding source code for three other distributions without
attribution in debian/copyright:

vendor/github.com/davecgh/go-spew
vendor/github.com/pmezard/go-difflib
vendor/github.com/stretchr/objx


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

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

Bug#823166: swift: FTBFS: AssertionError: Items in the first set but not the second:

[Chris Lamb]

Source: swift
Version: 2.7.0-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

swift fails to build from source in unstable/amd64:

  [..]

  test_OPTIONS (test.unit.proxy.test_server.TestContainerController) ... ok
  test_OPTIONS_get_info_drops_origin 
(test.unit.proxy.test_server.TestContainerController) ... ok
  test_POST (test.unit.proxy.test_server.TestContainerController) ... ok
  test_POST_bad_metadata (test.unit.proxy.test_server.TestContainerController) 
... ok
  test_POST_calls_clean_acl 
(test.unit.proxy.test_server.TestContainerController) ... ok
  test_POST_metadata (test.unit.proxy.test_server.TestContainerController) ... 
ok
  test_PUT (test.unit.proxy.test_server.TestContainerController) ... ok
  test_PUT_autocreate_account_with_sysmeta 
(test.unit.proxy.test_server.TestContainerController) ... ok
  test_PUT_backed_x_timestamp_header 
(test.unit.proxy.test_server.TestContainerController) ... ok
  test_PUT_bad_metadata (test.unit.proxy.test_server.TestContainerController) 
... ok
  test_PUT_calls_clean_acl 
(test.unit.proxy.test_server.TestContainerController) ... ok
  test_PUT_connect_exceptions 
(test.unit.proxy.test_server.TestContainerController) ... ok
  test_PUT_max_container_name_length 
(test.unit.proxy.test_server.TestContainerController) ... ok
  test_PUT_max_containers_per_account 
(test.unit.proxy.test_server.TestContainerController) ... ok
  test_PUT_metadata (test.unit.proxy.test_server.TestContainerController) ... ok
  test_PUT_policy_headers (test.unit.proxy.test_server.TestContainerController) 
... ok
  test_PUT_x_account_headers_with_fewer_account_replicas 
(test.unit.proxy.test_server.TestContainerController) ... ok
  test_PUT_x_account_headers_with_more_account_replicas 
(test.unit.proxy.test_server.TestContainerController) ... ok
  test_acc_missing_returns_404 
(test.unit.proxy.test_server.TestContainerController) ... ok
  test_authorized_requests_when_account_not_found 
(test.unit.proxy.test_server.TestContainerController) ... ok
  test_convert_index_to_name 
(test.unit.proxy.test_server.TestContainerController) ... ok
  test_convert_policy_to_index 
(test.unit.proxy.test_server.TestContainerController) ... ok
  test_error_convert_index_to_name 
(test.unit.proxy.test_server.TestContainerController) ... ok
  test_error_limiting (test.unit.proxy.test_server.TestContainerController) ... 
ok
  test_no_convert_index_to_name_when_container_not_found 
(test.unit.proxy.test_server.TestContainerController) ... ok
  test_node_read_timeout_retry_to_container 
(test.unit.proxy.test_server.TestContainerController) ... ok
  test_put_locking (test.unit.proxy.test_server.TestContainerController) ... ok
  test_response_get_accept_ranges_header 
(test.unit.proxy.test_server.TestContainerController) ... ok
  test_response_head_accept_ranges_header 
(test.unit.proxy.test_server.TestContainerController) ... ok
  test_transfer_headers (test.unit.proxy.test_server.TestContainerController) 
... ok
  test_unauthorized_requests_when_account_not_found 
(test.unit.proxy.test_server.TestContainerController) ... ok
  test_account_info_200 (test.unit.proxy.test_server.TestController) ... ok
  test_account_info_404 (test.unit.proxy.test_server.TestController) ... ok
  test_account_info_container_count 
(test.unit.proxy.test_server.TestController) ... ok
  test_account_info_no_account (test.unit.proxy.test_server.TestController) ... 
ok
  test_account_info_no_cache (test.unit.proxy.test_server.TestController) ... ok
  test_container_info_200 (test.unit.proxy.test_server.TestController) ... ok
  test_container_info_404 (test.unit.proxy.test_server.TestController) ... ok
  test_container_info_invalid_account 
(test.unit.proxy.test_server.TestController) ... ok
  test_container_info_no_cache (test.unit.proxy.test_server.TestController) ... 
ok
  test_get_info_cache_returns_values_as_strings 
(test.unit.proxy.test_server.TestController) ... ok
  test_make_requests (test.unit.proxy.test_server.TestController) ... ok
  test_transfer_headers (test.unit.proxy.test_server.TestController) ... ok
  test_mixing_different_objects_fragment_archives 
(test.unit.proxy.test_server.TestECMismatchedFA) ... ok
  test_COPY_account_delete_at 
(test.unit.proxy.test_server.TestObjectController) ... ok
  test_COPY_account_destination_leading_slash 
(test.unit.proxy.test_server.TestObjectController) ... ok
  test_COPY_account_newest (test.unit.proxy.test_server.TestObjectController) 
... ok
  test_COPY_account_no_object_in_destination 
(test.unit.proxy.test_server.TestObjectController) ... ok
  test_COPY_account_not_found_reading_source 
(test.unit.proxy.test_server.TestObjectController) ... ok
  test_COPY_account_server_error_reading_source 
(test.unit.proxy.test_server.TestObjectController) ... ok
  test_COPY_account_source_larger_than_max_file_size 

Bug#818072: warzone2100: FTBFS in stretch (new flex)

[Markus Koschany]

Am 01.05.2016 um 18:24 schrieb Graham Inggs:
> Control: tags -1 patch
> 
> Hi Maintainer
> 
> Please see attached patch which fixes the FTBFS with recent versions of flex.
> 
> Regards
> Graham

Hi Graham,

that was really bad timing. I had uploaded a new revision with a fix one
hour before you sent your e-mail. Nevertheless thanks for the patch!

Regards,

Markus





signature.asc
Description: OpenPGP digital signature

Bug#823164: lua-lgi: FTBFS: Segmentation fault (core dumped)

[Chris Lamb]

Source: lua-lgi
Version: 0.9.0.20151101.git.885af4-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

lua-lgi fails to build from source in unstable/amd64:

  [..]

  7fd9c54bc000-7fd9c54bd000 r--p 00021000 08:01 2885775 
/lib/x86_64-linux-gnu/liblzma.so.5.0.0
  7fd9c54bd000-7fd9c54be000 rw-p 00022000 08:01 2885775 
/lib/x86_64-linux-gnu/liblzma.so.5.0.0
  7fd9c54be000-7fd9c553f000 r-xp  08:01 4335805 
/lib/x86_64-linux-gnu/libsystemd.so.0.14.0
  7fd9c553f000-7fd9c5542000 r--p 0008 08:01 4335805 
/lib/x86_64-linux-gnu/libsystemd.so.0.14.0
  7fd9c5542000-7fd9c5543000 rw-p 00083000 08:01 4335805 
/lib/x86_64-linux-gnu/libsystemd.so.0.14.0
  7fd9c5543000-7fd9c5544000 rw-p  00:00 0
  7fd9c5544000-7fd9c5591000 r-xp  08:01 1445155 
/lib/x86_64-linux-gnu/libdbus-1.so.3.14.6
  7fd9c5591000-7fd9c579 ---p 0004d000 08:01 1445155 
/lib/x86_64-linux-gnu/libdbus-1.so.3.14.6
  7fd9c579-7fd9c5792000 r--p 0004c000 08:01 1445155 
/lib/x86_64-linux-gnu/libdbus-1.so.3.14.6
  7fd9c5792000-7fd9c5793000 rw-p 0004e000 08:01 1445155 
/lib/x86_64-linux-gnu/libdbus-1.so.3.14.6
  7fd9c5793000-7fd9c57c3000 r-xp  08:01 1445157 
/usr/lib/x86_64-linux-gnu/libatspi.so.0.0.1
  7fd9c57c3000-7fd9c59c3000 ---p 0003 08:01 1445157 
/usr/lib/x86_64-linux-gnu/libatspi.so.0.0.1
  7fd9c59c3000-7fd9c59c6000 r--p 0003 08:01 1445157 
/usr/lib/x86_64-linux-gnu/libatspi.so.0.0.1
  7fd9c59c6000-7fd9c59c7000 rw-p 00033000 08:01 1445157 
/usr/lib/x86_64-linux-gnu/libatspi.so.0.0.1
  7fd9c59c7000-7fd9c59fa000 r-xp  08:01 1445162 
/usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0.0.0
  7fd9c59fa000-7fd9c5bf9000 ---p 00033000 08:01 1445162 
/usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0.0.0
  7fd9c5bf9000-7fd9c5bfa000 r--p 00032000 08:01 1445162 
/usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0.0.0
  7fd9c5bfa000-7fd9c5bfc000 rw-p 00033000 08:01 1445162 
/usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0.0.0
  7fd9c5bfc000-7fd9c5c1f000 r-xp  08:01 1445138 
/usr/lib/x86_64-linux-gnu/libatk-1.0.so.0.22009.1
  7fd9c5c1f000-7fd9c5e1e000 ---p 00023000 08:01 1445138 
/usr/lib/x86_64-linux-gnu/libatk-1.0.so.0.22009.1
  7fd9c5e1e000-7fd9c5e21000 r--p 00022000 08:01 1445138 
/usr/lib/x86_64-linux-gnu/libatk-1.0.so.0.22009.1
  7fd9c5e21000-7fd9c5e22000 rw-p 00025000 08:01 1445138 
/usr/lib/x86_64-linux-gnu/libatk-1.0.so.0.22009.1
  7fd9c5e22000-7fd9c64f2000 r-xp  08:01 1449067 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2000.3
  7fd9c64f2000-7fd9c66f1000 ---p 006d 08:01 1449067 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2000.3
  7fd9c66f1000-7fd9c66fc000 r--p 006cf000 08:01 1449067 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2000.3
  7fd9c66fc000-7fd9c6703000 rw-p 006da000 08:01 1449067 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2000.3
  7fd9c6703000-7fd9c6708000 rw-p  00:00 0
  7fd9c6708000-7fd9c672b000 r-xp  08:01 1445584 
/usr/lib/x86_64-linux-gnu/libgraphite2.so.3.0.1
  7fd9c672b000-7fd9c692b000 ---p 00023000 08:01 1445584 
/usr/lib/x86_64-linux-gnu/libgraphite2.so.3.0.1
  7fd9c692b000-7fd9c692d000 r--p 00023000 08:01 1445584 
/usr/lib/x86_64-linux-gnu/libgraphite2.so.3.0.1
  7fd9c692d000-7fd9c692e000 rw-p 00025000 08:01 1445584 
/usr/lib/x86_64-linux-gnu/libgraphite2.so.3.0.1
  7fd9c692e000-7fd9c69ac000 r-xp  08:01 1445592 
/usr/lib/x86_64-linux-gnu/libharfbuzz.so.0.10200.6
  7fd9c69ac000-7fd9c6bac000 ---p 0007e000 08:01 1445592 
/usr/lib/x86_64-linux-gnu/libharfbuzz.so.0.10200.6
  7fd9c6bac000-7fd9c6bad000 r--p 0007e000 08:01 1445592 
/usr/lib/x86_64-linux-gnu/libharfbuzz.so.0.10200.6
  7fd9c6bad000-7fd9c6bae000 rw-p 0007f000 08:01 1445592 
/usr/lib/x86_64-linux-gnu/libharfbuzz.so.0.10200.6
  7fd9c6bae000-7fd9c6bc2000 r-xp  08:01 1445594 
/usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.4000.1
  7fd9c6bc2000-7fd9c6dc2000 ---p 00014000 08:01 1445594 
/usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.4000.1
  7fd9c6dc2000-7fd9c6dc3000 r--p 00014000 08:01 1445594 
/usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.4000.1
  7fd9c6dc3000-7fd9c6dc4000 rw-p 00015000 08:01 1445594 
/usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.4000.1
  7fd9c6dc4000-7fd9c6eaa000 r-xp  08:01 1445171 
/usr/lib/x86_64-linux-gnu/libepoxy.so.0.0.0
  7fd9c6eaa000-7fd9c70aa000 ---p 000e6000 08:01 1445171 
/usr/lib/x86_64-linux-gnu/libepoxy.so.0.0.0
  7fd9c70aa000-7fd9c70b1000 r--p 000e6000 08:01 1445171 
/usr/lib/x86_64-linux-gnu/libepoxy.so.0.0.0
  7fd9c70b1000-7fd9c70b8000 rw-p 000ed000 08:01 1445171 
/usr/lib/x86_64-linux-gnu/libepoxy.so.0.0.0
  7fd9c70b8000-7fd9c70c4000 r-xp  08:01 1448579 
/usr/lib/x86_64-linux-gnu/libwayland-client.so.0.3.0
  7fd9c70c4000-7fd9c72c4000 ---p c000 08:01 1448579 
/usr/lib/x86_64-linux-gnu/libwayland-client.so.0.3.0
  7fd9c72c4000-7fd9c72c6000 r--p c000 08:01 1448579 

Bug#822650: marked as done (openmsx: FTBFS: error: no matching function for call to 'begin...)

[Debian Bug Tracking System]

Your message dated Sun, 01 May 2016 16:53:15 +
with message-id 
and subject line Bug#822650: fixed in openmsx 0.12.0-2
has caused the Debian Bug report #822650,
regarding openmsx: FTBFS: error: no matching function for call to 'begin...
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.)


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

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> Compiling RTScheduler.cc...
> g++ \
>-MP -MMD -MF derived/x86_64-linux-debian/dep/RTScheduler.d \
>   -o derived/x86_64-linux-debian/obj/RTScheduler.o  -g 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -O3   -m64 -pipe -std=c++11 -Wall -Wextra -Wundef 
> -Wno-invalid-offsetof -Wunused-macros -Wdouble-promotion 
> -Wmissing-declarations -Wno-missing-field-initializers -Isrc -Isrc/cassette 
> -Isrc/commands -Isrc/config -Isrc/console -Isrc/cpu -Isrc/debugger 
> -Isrc/events -Isrc/fdc -Isrc/file -Isrc/ide -Isrc/input -Isrc/laserdisc 
> -Isrc/memory -Isrc/resource -Isrc/security -Isrc/serial -Isrc/settings 
> -Isrc/sound -Isrc/thread -Isrc/utils -Isrc/video -Isrc/video/ld 
> -Isrc/video/scalers -Isrc/video/v9990 -Iderived/x86_64-linux-debian/config 
> -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL 
> -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/tcl8.5-c src/RTScheduler.cc
> src/RTScheduler.cc: In member function 'bool 
> openmsx::RTScheduler::isPending(const openmsx::RTSchedulable&) const':
> src/RTScheduler.cc:33:38: error: no matching function for call to 
> 'begin(const openmsx::SchedulerQueue&)'
>   return std::find_if(std::begin(queue), std::end(queue),
>   ^
> In file included from /usr/include/c++/5/utility:75:0,
>  from /usr/include/c++/5/algorithm:60,
>  from src/utils/MemBuffer.hh:7,
>  from src/SchedulerQueue.hh:4,
>  from src/RTScheduler.hh:4,
>  from src/RTScheduler.cc:1:
> /usr/include/c++/5/initializer_list:89:5: note: candidate: template _Tp> constexpr const _Tp* std::begin(std::initializer_list<_Tp>)
>  begin(initializer_list<_Tp> __ils) noexcept
>  ^
> /usr/include/c++/5/initializer_list:89:5: note:   template argument 
> deduction/substitution failed:
> src/RTScheduler.cc:33:38: note:   
> 'openmsx::SchedulerQueue' is not derived from 
> 'std::initializer_list<_Tp>'
>   return std::find_if(std::begin(queue), std::end(queue),
>   ^
> src/RTScheduler.cc:33:55: error: no matching function for call to 'end(const 
> openmsx::SchedulerQueue&)'
>   return std::find_if(std::begin(queue), std::end(queue),
>^
> In file included from /usr/include/c++/5/utility:75:0,
>  from /usr/include/c++/5/algorithm:60,
>  from src/utils/MemBuffer.hh:7,
>  from src/SchedulerQueue.hh:4,
>  from src/RTScheduler.hh:4,
>  from src/RTScheduler.cc:1:
> /usr/include/c++/5/initializer_list:99:5: note: candidate: template _Tp> constexpr const _Tp* std::end(std::initializer_list<_Tp>)
>  end(initializer_list<_Tp> __ils) noexcept
>  ^
> /usr/include/c++/5/initializer_list:99:5: note:   template argument 
> deduction/substitution failed:
> src/RTScheduler.cc:33:55: note:   
> 'openmsx::SchedulerQueue' is not derived from 
> 'std::initializer_list<_Tp>'
>   return std::find_if(std::begin(queue), std::end(queue),
>^
> src/RTScheduler.cc:34:72: error: no matching function for call to 'end(const 
> openmsx::SchedulerQueue&)'
>   EqualRTSchedulable(schedulable)) != std::end(queue);
> ^
> In file included from /usr/include/c++/5/utility:75:0,
>  from /usr/include/c++/5/algorithm:60,
>  from src/utils/MemBuffer.hh:7,
>  from src/SchedulerQueue.hh:4,
>  from src/RTScheduler.hh:4,
>  from src/RTScheduler.cc:1:
> /usr/include/c++/5/initializer_list:99:5: note: candidate: template _Tp> constexpr const _Tp* std::end(std::initializer_list<_Tp>)
>  

Bug#823162: pseudo: wrong update-alternatives call in postinst

[Gian Piero Carrubba]

Package: pseudo
Version: 1.7.5-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

thank for your work on pseudo.

This bug is presumably related to #805937, but I'm reporting it alone as
it prevents a smooth installation of the package.

During upgrade:

  Setting up pseudo (1.7.5-4) ...
  update-alternatives: error: alternative path /usr/bin/fakeroot-pseudo
  doesn't exist
  dpkg: error processing package pseudo (--configure):
   subprocess installed post-installation script returned error exit
  status 2

This is because of the update-alternatives invocation in postinst:

  configure)
  # continue below
  update-alternatives --install /usr/bin/fakeroot fakeroot \
  /usr/bin/fakeroot-pseudo 5 \
  --slave /usr/share/man/man1/fakeroot.1.gz \
  fakeroot.1.gz /usr/share/man/man1/fakeroot-pseudo.1.gz
  ;;

The pseudo package does not contain the fakeroot-pseudo wrapper (as a
fix for #805937 ?):

  $ fgrep bin /var/lib/dpkg/info/pseudo.list 
  /usr/bin
  /usr/bin/pseudolog
  /usr/bin/pseudodb
  /usr/bin/pseudo 

Thanks,
Gian Piero.

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

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

Versions of packages pseudo depends on:
ii  libc6 2.22-7
ii  libpseudo 1.7.5-4
ii  libsqlite3-0  3.12.2-1

pseudo recommends no packages.

pseudo suggests no packages.

-- no debconf information

Processed: Re: Bug#821435: patchelf: FTBFS on mips*: tests fail: set-rpath.sh no-rpath.sh big-dynstr.sh set-rpath-library.sh

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #821435 [src:patchelf] patchelf: --set-rpath breaks binaries on mips*
Severity set to 'important' from 'serious'

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

Bug#821435: patchelf: FTBFS on mips*: tests fail: set-rpath.sh no-rpath.sh big-dynstr.sh set-rpath-library.sh

[Felipe Sateler]

Control: severity -1 important

On 18 April 2016 at 21:21, Felipe Sateler  wrote:
> Control: tags -1 upstream confirmed
> Control: forwarded -1 https://github.com/NixOS/patchelf/issues/82
> Control: retitle -1 patchelf: --set-rpath breaks binaries on mips*
>
> Hi,
>
> On 18 April 2016 at 14:40, Andreas Beckmann  wrote:
>> Hi,
>>
>> patchelf FTBFS on mips* with some testsuite failures:
>
> Thanks for the bug report. It appears patchelf never worked on mips.
> I'm pondering asking for a removal there until this issue is fixed.

I have done this now (#822211). Therefore lowering severity to important.

-- 

Saludos,
Felipe Sateler

Bug#818072: marked as done (warzone2100: FTBFS in stretch (new flex))

[Debian Bug Tracking System]

Your message dated Sun, 01 May 2016 16:26:13 +
with message-id 
and subject line Bug#818072: fixed in warzone2100 3.1.1-3
has caused the Debian Bug report #818072,
regarding warzone2100: FTBFS in stretch (new flex)
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.)


-- 
818072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:warzone2100
Version: 3.1.1-2
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch:

resource_lexer.lpp: In function 'int res_lex_destroy()':
resource_lexer.lpp:154:5: error: redefinition of 'int res_lex_destroy()'
resource_lexer.cpp:1928:5: note: 'int res_lex_destroy()' previously defined here
 int res_lex_destroy  (void)
  ^
Makefile:475: recipe for target 'resource_lexer.o' failed

I suspect that the new flex is the reason.

The full build log is attached.

Thanks.

warzone2100_3.1.1-2_amd64-20160313-1047.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: warzone2100
Source-Version: 3.1.1-3

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated warzone2100 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: Sun, 01 May 2016 16:31:18 +0200
Source: warzone2100
Binary: warzone2100 warzone2100-data warzone2100-music
Architecture: source
Version: 3.1.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 warzone2100 - 3D real time strategy game
 warzone2100-data - data files for warzone2100
 warzone2100-music - official music for warzone2100
Closes: 818072
Changes:
 warzone2100 (3.1.1-3) unstable; urgency=medium
 .
   * Team upload.
   * Rebase fix-yacc patch.
   * Add redefinition-FTBFS.patch
 Adjust lexer files to prevent a FTBFS with newer flex versions.
 (Closes: #818072)
   * Declare compliance with Debian Policy 3.9.8.
   * Vcs-Browser: Use https.
   * debian/control: Change Recommends: warzone2100 to Suggests.
   * Drop debug package and use the automatically provided -dbgsym package
 instead.
   * Fix Lintian warnings space-in-std-shortname-in-dep5-copyright,
 unused-file-paragraph-in-dep5-copyright and
 wildcard-matches-nothing-in-dep5-copyright in debian/copyright.
Checksums-Sha1:
 792ab31c69660170e04c77b9d76cf393bfb0b2b0 2710 warzone2100_3.1.1-3.dsc
 ddd1cec2b1beacaf0ee40dc5ff5c2cafc8ea3a71 63720 
warzone2100_3.1.1-3.debian.tar.xz
Checksums-Sha256:
 161fb34c03b1d531ffaa375bed0ab1d872daa0e2f47ec5153d71c3f0084293d7 2710 
warzone2100_3.1.1-3.dsc
 bd242249de0aab58f601cc091698fbb24bd629f4883742e82c9e78173d4e7103 63720 
warzone2100_3.1.1-3.debian.tar.xz
Files:
 bebc3436557a6a60341eb417ecb4cfc5 2710 games optional warzone2100_3.1.1-3.dsc
 a004f871baf2e2307ca63670fdd7040d 63720 games optional 
warzone2100_3.1.1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJXJhn3XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE
OUFEMTRCOTUxM0I1MUU0AAoJENmtFLlRO1HkweEQAKFEkavUljkvQsu54ajY0nJ/
/3mzI3lR5VsO1Nk+LZZLVAcQnC33T0j4a0bcV8KKnnUvwdpkntNak44W+lXEQ1m4
AnV7sR4U4OLhq8MuW/w/CMVsJ80hYWDEldo5IB4x0ZdQSiuTCQPhIhBwyQjzGgSe
bUTIrkdbVpLLWCQnzOe9oc6FevszINd6yo84YoJc9CaZuKTqbfHE9x+prYaDh1Aj
7pa4hNcQ5bYQVgGGXPN8rizSRZTIwZOCXl0HsPTha4ng/ifleHoMiiHqFUeDuJh8
1Z2LTwhks5wkIMhG2Ecgl/koCwdi5or14zZ7B+IwQf0AtqQECd3eg2zmeOM2QLUe
29PRtylUVjII++gmWW/IEasyy6tZ2LTnZ+ipDRCrbtcdmAFsUABvZGKoX+A41Bem
P1olCImbia7A2Wbj3YETOvxlGhqB+XpOL4LAGeduB/7dM7WYYGimH22TlBxQZ4yB
NEABOXT0464TzN79r9KpKqEP5lHecVWcliVStPU1bAIG/VYCSnJnPI+RPPziQh7f
A5dyWHjasHhz5M10hEiSOmi8jayaNZkGSt+APCzCyH5/L6Ekyy7Z1J85XvrybymI
KilikqeO1XMSozpkO1r2ayvPeWMyO5G/XeWqwNt1er53dNXiDvrZzP01OnPba1a+
JVXvQDO/hf2i9o/EH3A6
=lxHV
-END PGP SIGNATURE End Message 

Bug#818072: warzone2100: FTBFS in stretch (new flex)

[Graham Inggs]

Control: tags -1 patch

Hi Maintainer

Please see attached patch which fixes the FTBFS with recent versions of flex.

Regards
Graham
Description: Fix FTBFS with recent versions of flex
Bug-Debian: https://bugs.debian.org/818072
Forwarded: No
Author: Graham Inggs 
Last-Update: 2016-05-01
--- a/lib/framework/resource_lexer.lpp
+++ b/lib/framework/resource_lexer.lpp
@@ -49,7 +49,7 @@
  * yyget_text() and yyget_lineno().
  * (and neither define a subminor version)
  */
-#if !defined(YY_FLEX_SUBMINOR_VERSION) || (YY_FLEX_SUBMINOR_VERSION < 9)
+#if !defined(YY_FLEX_SUBMINOR_VERSION) || ((YY_FLEX_SUBMAJOR_VERSION == 5) && (YY_FLEX_SUBMINOR_VERSION < 9))
 # define yyget_extra  res_get_extra
 # define yyset_extra  res_set_extra
 # define yyget_lineno res_get_lineno
@@ -67,7 +67,7 @@
 {
 	return yytext;
 }
-#elif defined(YY_FLEX_SUBMINOR_VERSION) && YY_FLEX_SUBMINOR_VERSION == 33
+#elif defined(YY_FLEX_SUBMINOR_VERSION) && ((YY_FLEX_MAJOR_VERSION > 2) || (YY_FLEX_SUBMAJOR_VERSION > 5) || (YY_FLEX_SUBMINOR_VERSION >= 33))
 extern YY_EXTRA_TYPE yyget_extra(void);
 extern int res_get_lineno(void);
 extern FILE *res_get_in(void);
@@ -149,7 +149,7 @@
 /* Older GNU Flex versions don't define yylex_destroy()
  * (and neither define a subminor version)
  */
-#if !defined(YY_FLEX_SUBMINOR_VERSION) || (YY_FLEX_SUBMINOR_VERSION < 9)
+#if !defined(YY_FLEX_SUBMINOR_VERSION) || ((YY_FLEX_SUBMAJOR_VERSION == 5) && (YY_FLEX_SUBMINOR_VERSION < 9))
 int res_lex_destroy(void)
 {
 	/* For non-reentrant C scanner only. */
--- a/lib/framework/strres_lexer.lpp
+++ b/lib/framework/strres_lexer.lpp
@@ -53,7 +53,7 @@
  * yyget_text() and yyget_lineno().
  * (and neither define a subminor version)
  */
-#if !defined(YY_FLEX_SUBMINOR_VERSION) || (YY_FLEX_SUBMINOR_VERSION < 9)
+#if !defined(YY_FLEX_SUBMINOR_VERSION) || ((YY_FLEX_SUBMAJOR_VERSION == 5) && (YY_FLEX_SUBMINOR_VERSION < 9))
 # define yyget_extra  strres_get_extra
 # define yyset_extra  strres_set_extra
 # define yyget_lineno strres_get_lineno
@@ -71,7 +71,7 @@
 {
 	return yytext;
 }
-#elif defined(YY_FLEX_SUBMINOR_VERSION) && YY_FLEX_SUBMINOR_VERSION == 33
+#elif defined(YY_FLEX_SUBMINOR_VERSION) && ((YY_FLEX_MAJOR_VERSION > 2) || (YY_FLEX_SUBMAJOR_VERSION > 5) || (YY_FLEX_SUBMINOR_VERSION >= 33))
 extern YY_EXTRA_TYPE yyget_extra(void);
 extern int strres_get_lineno(void);
 extern FILE *strres_get_in(void);
@@ -146,7 +146,7 @@
 /* Older GNU Flex versions don't define yylex_destroy()
  * (and neither define a subminor version)
  */
-#if !defined(YY_FLEX_SUBMINOR_VERSION) || (YY_FLEX_SUBMINOR_VERSION < 9)
+#if !defined(YY_FLEX_SUBMINOR_VERSION) || ((YY_FLEX_SUBMAJOR_VERSION == 5) && (YY_FLEX_SUBMINOR_VERSION < 9))
 int strres_lex_destroy(void)
 {
 	/* For non-reentrant C scanner only. */
--- a/lib/script/chat_lexer.lpp
+++ b/lib/script/chat_lexer.lpp
@@ -47,7 +47,7 @@
 #define YYLMAX	255
 #endif
 
-#if defined(YY_FLEX_SUBMINOR_VERSION) && YY_FLEX_SUBMINOR_VERSION == 33
+#if defined(YY_FLEX_SUBMINOR_VERSION) && ((YY_FLEX_MAJOR_VERSION > 2) || (YY_FLEX_SUBMAJOR_VERSION > 5) || (YY_FLEX_SUBMINOR_VERSION >= 33))
 extern int chat_get_lineno(void);
 extern FILE *chat_get_in(void);
 extern FILE *chat_get_out(void);
@@ -227,7 +227,7 @@
 /* Older GNU Flex versions don't define yylex_destroy()
  * (and neither define a subminor version)
  */
-#if !defined(YY_FLEX_SUBMINOR_VERSION) || (YY_FLEX_SUBMINOR_VERSION < 9)
+#if !defined(YY_FLEX_SUBMINOR_VERSION) || ((YY_FLEX_SUBMAJOR_VERSION == 5) && (YY_FLEX_SUBMINOR_VERSION < 9))
 int chat_lex_destroy(void)
 {
 	/* For non-reentrant C scanner only. */
--- a/lib/script/script_lexer.lpp
+++ b/lib/script/script_lexer.lpp
@@ -45,7 +45,7 @@
 #define YYLMAX	255
 #endif
 
-#if defined(YY_FLEX_SUBMINOR_VERSION) && YY_FLEX_SUBMINOR_VERSION == 33
+#if defined(YY_FLEX_SUBMINOR_VERSION) && ((YY_FLEX_MAJOR_VERSION > 2) || (YY_FLEX_SUBMAJOR_VERSION > 5) || (YY_FLEX_SUBMINOR_VERSION >= 33))
 extern int scr_get_lineno(void);
 extern FILE *scr_get_in(void);
 extern FILE *scr_get_out(void);
@@ -857,7 +857,7 @@
 /* Older GNU Flex versions don't define yylex_destroy()
  * (and neither define a subminor version)
  */
-#if !defined(YY_FLEX_SUBMINOR_VERSION) || (YY_FLEX_SUBMINOR_VERSION < 9)
+#if !defined(YY_FLEX_SUBMINOR_VERSION) || ((YY_FLEX_SUBMAJOR_VERSION == 5) && (YY_FLEX_SUBMINOR_VERSION < 9))
 int scr_lex_destroy(void)
 {
 	/* For non-reentrant C scanner only. */
--- a/lib/gamelib/audp_lexer.lpp
+++ b/lib/gamelib/audp_lexer.lpp
@@ -52,7 +52,7 @@
  * yyget_text() and yyget_lineno().
  * (and neither define a subminor version)
  */
-#if !defined(YY_FLEX_SUBMINOR_VERSION) || (YY_FLEX_SUBMINOR_VERSION < 9)
+#if !defined(YY_FLEX_SUBMINOR_VERSION) || ((YY_FLEX_SUBMAJOR_VERSION == 5) && (YY_FLEX_SUBMINOR_VERSION < 9))
 # define yyget_extra  audp_get_extra
 # define yyset_extra  audp_set_extra
 # define yyget_lineno audp_get_lineno
@@ -70,7 +70,7 @@
 {
 	return yytext;
 }
-#elif defined(YY_FLEX_SUBMINOR_VERSION) && YY_FLEX_SUBMINOR_VERSION == 33
+#elif 

Processed: warzone2100: FTBFS in stretch (new flex)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #818072 [src:warzone2100] warzone2100: FTBFS in stretch (new flex)
Added tag(s) patch.

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

Bug#823156: marked as done (linux-headers-4.5.0-0.bpo.1-all-amd64: breaks kwin (abort with fatal error) on Thinkpad T560)

[Debian Bug Tracking System]

Your message dated Sun, 01 May 2016 18:17:12 +0200
with message-id <1462119432.17662.50.ca...@decadent.org.uk>
and subject line Re: Bug#823156: linux-headers-4.5.0-0.bpo.1-all-amd64: breaks 
kwin (abort with fatal error) on Thinkpad T560
has caused the Debian Bug report #823156,
regarding linux-headers-4.5.0-0.bpo.1-all-amd64: breaks kwin (abort with fatal 
error) on Thinkpad T560
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.)


-- 
823156: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-headers-4.5.0-0.bpo.1-all-amd64
Version: 4.5.1-1~bpo8+1
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

after a fresh Netinstall of Debian Jessie (stable) I installed the backport
Kernel as much Hardware of Thinkpad T560 is not supported (mainly Sound and
WLAN as I noticed this far). It actually reaches the commandline but is unable
to start kwin. Whenever I try to start it with his kernel it aborts with fatal
error. Linux Mint KDE is actually able to use WLAN even within the Live Iso
Environment (although I don't like their closed source policy). Did not find
/var/log/boot nor /etc/init.d/bootlogd and /etc/init.d/bootlogs points Kernel
messages to /var/log/dmesg which is empty. /var is on a separate partition.
This is just to inform you. Thanks for your work, but I am afraid I have to
change Distro as it has to many issues on my platform. Maybe I'll try again in
half a year.

Oh and in my previous install from the same netinst iso I dist-upgraded to
testing which resulted in quite similar results of a broken system.
Thanks and Bye, Maria.



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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-headers-4.5.0-0.bpo.1-all-amd64 depends on:
ii  linux-headers-4.5.0-0.bpo.1-amd64  4.5.1-1~bpo8+1

linux-headers-4.5.0-0.bpo.1-all-amd64 recommends no packages.

linux-headers-4.5.0-0.bpo.1-all-amd64 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, 2016-05-01 at 17:50 +0200, Maria wrote:
[...]
> This is just to inform you. Thanks for your work, but I am afraid I
> have to
> change Distro as it has to many issues on my platform. Maybe I'll try again in
> half a year.

You haven't provided enough information to begin debugging this and it
seems you don't intend to do so, so I'm closing the report.  If you
wish to send another bug report the next time you try Debian, please
start by running 'reportbug kernel' as this will automatically gather
some useful information about your system.

As Debian now uses systemd by default, /etc/init.d/bootlogs does not
run and so /var/log/dmesg is not created.  The kernel log is available
by running 'dmesg' (recent messages only) or 'grep kernel:
/var/log/messages.1 /var/log/messages' (last 1-2 weeks).

Ben.

-- 
Ben Hutchings
73.46% of all statistics are made up.


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

Bug#823106: marked as done (fretsonfire: Depends on fonts-mgopen which has been requested to be removed)

[Debian Bug Tracking System]

Your message dated Sun, 01 May 2016 16:19:57 +
with message-id 
and subject line Bug#823106: fixed in fretsonfire 1.3.110.dfsg2-3
has caused the Debian Bug report #823106,
regarding fretsonfire: Depends on fonts-mgopen which has been requested to be 
removed
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.)


-- 
823106: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fretsonfire
Version: 1.3.110.dfsg2-2
Severity: serious
Control: block 819026 with -1

Hi,

fretsonfire depends on the fonts-mgopen font which has been requested to
eb removed. (#819026). Please switch to a different font.


Andreas
--- End Message ---
--- Begin Message ---
Source: fretsonfire
Source-Version: 1.3.110.dfsg2-3

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated fretsonfire 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: Sun, 01 May 2016 17:10:08 +0200
Source: fretsonfire
Binary: fretsonfire fretsonfire-game
Architecture: source
Version: 1.3.110.dfsg2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 fretsonfire - game of musical skill and fast fingers
 fretsonfire-game - game of musical skill and fast fingers - Game files
Closes: 823106
Changes:
 fretsonfire (1.3.110.dfsg2-3) unstable; urgency=medium
 .
   * Team upload.
   * Declare compliance with Debian Policy 3.9.8.
   * Replace fonts-mgopen dependency with fonts-dejavu. (Closes: #823106)
Checksums-Sha1:
 a2f59770030b4a8b0d10f956fb7a13c2156361a8 2287 fretsonfire_1.3.110.dfsg2-3.dsc
 889b758998c534b2b36d613e3040e06bce2b3045 22064 
fretsonfire_1.3.110.dfsg2-3.debian.tar.xz
Checksums-Sha256:
 e2836793b14490ddc06a15ef06deb4b526c18b0624039af72e0d371b3e1a7cce 2287 
fretsonfire_1.3.110.dfsg2-3.dsc
 808422748bcf5e8768501b1075db34e4ed9777e0ef2afbc6e2435511edc83234 22064 
fretsonfire_1.3.110.dfsg2-3.debian.tar.xz
Files:
 f68a1d64b274a77bbc7c1c862afc1d6d 2287 games optional 
fretsonfire_1.3.110.dfsg2-3.dsc
 21f98a809bab65110c3c5191cface4fe 22064 games optional 
fretsonfire_1.3.110.dfsg2-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJXJh6bXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE
OUFEMTRCOTUxM0I1MUU0AAoJENmtFLlRO1HkyOYQAJisJNUAg5iZQyXWWz00kJZc
Ap5HCEOm8yqVliyzygLdEHnazDboTpiB3vWJ9bcxqEN8/KIaFYj6YM6etRquUGvC
PXFKqu9YqT++3vdOaVaaU59qVIRufhQC6AQS3qbpzr9fvv/bTsNx1c7QLKjO30sc
Y1Rp2eASfMCxmeICotGMhk9TaHyuZlYvFmFlsTFz7JsLH5V/ZtM2EscpfM5GMLG3
J/mSnz8wNpwD5VpyfXS0m1SI8vr28E/Lto2WAdZpYKAkzhPwpZQqOLii3cgQ41Da
mM3dUq6vA+5wPhiyfr4CATOe6hT4kWkcnKGxzAuaQP+HUEMr7tZuBgXFhEOwfFVx
2KcNUiwTLg27mXY5Hxmq5V5fKYj6Bu7TSeEqUo1hpje3EcARmzBRbeI+zKdSNmDF
B8UqJxeMlJ5gizpX686xP8QX8tXFi4n204zEU/T+2F47KzmhoTXp9m6SbaZVKw5Z
zl+9YLAj612th7qaokEixCjCW1nj1y8P2f3Nu0SsUt15QfByTZNTHG1O/M0mXahg
5OTV3matfQMT/qSrZCVEAXGc9O3qKtWT3z95PVSeNvYt7DNmJsfcWEiILE2urZJu
TBi6bp1nJl+56MWLKJyZZL7MlYfSHPvOQJb7UwzzbF49Ze5U6jsm9MMfid//Gkcr
7TQOvaZFBEE/SjOWUpCv
=way5
-END PGP SIGNATURE End Message ---

Bug#815369: texi2pdf output filename bug?

[Gavin Smith]

On 1 May 2016 at 12:14, Gavin Smith  wrote:
> I haven't researched why --tidy makes a difference. I plan to stop
> this error by making @value non-expandable when writing to auxiliary
> files. This would have the effect that the value used would be the
> value at the time when the auxiliary file was read in, instead of when
> it was written to, that's when @value worked at all. I think this
> change would be okay, because this is already the case for @macro and
> I doubt that many documents would rely on changing a @value in the
> middle of the document.

I have found another problem: the --tidy and --command options appear
to be incompatible. In the "insert_commands" function, the "in_input"
variable is changed to be the file that is the result of inserting the
extra commands, but in the "run_tex" function, this is discarded if
--tidy was given.

Bug#807735: NMU for gmpc-plugins

[Étienne Millon]

Thanks, I just pushed the diff to the git repository.
I actually do not use this package very often, so if you would like to
adopt it I'm all for it :) (same applies to gmpc).
Let me know what you think.

Bug#823156: linux-headers-4.5.0-0.bpo.1-all-amd64: breaks kwin (abort with fatal error) on Thinkpad T560

[Maria]

Package: linux-headers-4.5.0-0.bpo.1-all-amd64
Version: 4.5.1-1~bpo8+1
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

after a fresh Netinstall of Debian Jessie (stable) I installed the backport
Kernel as much Hardware of Thinkpad T560 is not supported (mainly Sound and
WLAN as I noticed this far). It actually reaches the commandline but is unable
to start kwin. Whenever I try to start it with his kernel it aborts with fatal
error. Linux Mint KDE is actually able to use WLAN even within the Live Iso
Environment (although I don't like their closed source policy). Did not find
/var/log/boot nor /etc/init.d/bootlogd and /etc/init.d/bootlogs points Kernel
messages to /var/log/dmesg which is empty. /var is on a separate partition.
This is just to inform you. Thanks for your work, but I am afraid I have to
change Distro as it has to many issues on my platform. Maybe I'll try again in
half a year.

Oh and in my previous install from the same netinst iso I dist-upgraded to
testing which resulted in quite similar results of a broken system.
Thanks and Bye, Maria.



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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-headers-4.5.0-0.bpo.1-all-amd64 depends on:
ii  linux-headers-4.5.0-0.bpo.1-amd64  4.5.1-1~bpo8+1

linux-headers-4.5.0-0.bpo.1-all-amd64 recommends no packages.

linux-headers-4.5.0-0.bpo.1-all-amd64 suggests no packages.

-- no debconf information

Bug#823106: fretsonfire: Depends on fonts-mgopen which has been requested to be removed

[Faidon Liambotis]

Markus,

On Sat, Apr 30, 2016 at 11:28:53PM +0200, Markus Koschany wrote:
> > fretsonfire depends on the fonts-mgopen font which has been requested to
> > eb removed. (#819026). Please switch to a different font.
> 
> providing patches or filing bug reports before requesting package
> removals are always appreciated. Thanks for your consideration next time.

You're absolutely right. I didn't think anyone would be using
fonts-mgopen but it was sloppy of me to not check beforehand. My
apologies.

Best,
Faidon

Bug#816085: marked as done (elkcode: FTBFS on mips)

[Debian Bug Tracking System]

Your message dated Sun, 1 May 2016 16:16:44 +0200
with message-id <20160501141644.ga9...@aurel32.net>
and subject line Bug#816085: elkcode: FTBFS on mips
has caused the Debian Bug report #816085,
regarding elkcode: FTBFS on mips
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.)


-- 
816085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816085
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: elkcode
Version: 2.3.22-1
Severity: serious

Your package failed to build on mips. See logs at:

https://buildd.debian.org/status/logs.php?pkg=elkcode=2.3.22-1%2Bb1=mips

Emilio
--- End Message ---
--- Begin Message ---
On 2016-02-27 11:31, Emilio Pozuelo Monfort wrote:
> Source: elkcode
> Version: 2.3.22-1
> Severity: serious
> 
> Your package failed to build on mips. See logs at:
> 
> https://buildd.debian.org/status/logs.php?pkg=elkcode=2.3.22-1%2Bb1=mips

The problem was actually due to the lack of FPU of certain build
daemons. It built successfully on mips-aql-06. I am therefore closing
the bug.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net--- End Message ---

Bug#823149: libjs-jquery-fancybox doesn't work with current libjs-jquery

[Colomban Wendling]

Package: libjs-jquery-fancybox
Version: 11-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The version of libjs-jquery-fancybox packaged (1.3.4 (11/11/2010) [1])
is not compatible with current version of libjs-jquery (1.12.3), and
doesn't work at all with it:

TypeError: $.browser is undefined
(at jquery.fancybox.min.js:1:418)

According to 
https://stackoverflow.com/questions/14344289/fancybox-doesnt-work-with-jquery-v1-9-0-f-browser-is-undefined-cannot-read
it's simply that this old version of FancyBox isn't compatible with
API changes in newer jQuery.

I see three possible fixes for the package, in order of preference:

* Update the plugin to its latest version (or at least, newer) which
  should be compatible.
* Patch the packaged version of the plugin to work with current jQuery.
* Make the libjs-jquery-fancybox package depend on libjs-jquery < 1.9,
  but that would effectively make the package uninstallable on testing
  and newer.

Thanks,
Colomban

[1] $ grep Version: /usr/share/javascript/jquery-fancybox/jquery.fancybox.js


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

Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libjs-jquery-fancybox depends on:
ii  libjs-jquery 1.12.3-1
ii  libjs-jquery-easing  11-1
ii  libjs-jquery-mousewheel  11-1

Versions of packages libjs-jquery-fancybox recommends:
ii  javascript-common  11

libjs-jquery-fancybox suggests no packages.

-- no debconf information

Bug#809671: should openmeeg be removed from Debian?

[Yaroslav Halchenko]

Yeah, sorry about that... If nothing comes out in a week, RM it
Thanks

On May 1, 2016 4:46:57 AM EDT, Gianfranco Costamagna  
wrote:
>Hi,
>
>lets put a deadline.
>
>is it ok for you to upload something before one month or two starting
>from today?
>
>we are working hard in removing vtk5 from the archive and also
>libpng12, and this bug is
>one of the last unsolved blockers for now.
>
>sorry for being pushy, but it missed jessie, it will probably miss
>stretch too if we don't act
>in a timely manner.
>
>cheers!
>
>Gianfranco
>
>On Sat, 23 Apr 2016 11:42:23 + Mattia Rizzolo 
>wrote:
>> On Sat, Jan 02, 2016 at 05:12:12PM +, Mattia Rizzolo wrote:
>> > On Sat, Jan 02, 2016 at 12:04:07PM -0500, Yaroslav Halchenko wrote:
>> > > On Sat, 02 Jan 2016, Mattia Rizzolo wrote:
>> > > I would not call it dead upstream.  It is a research project
>after all -
>> > > so people develop it whenever there is need.
>> > 
>> > ok, sorry, I must have looked to either the wrong place, or in the
>wrong
>> > way.
>> > 
>> > > I will look into fixing packaging up one way or another within a
>> > > week or two, ok?  and if I upload new release, I will close this
>one
>> > 
>> > that's cool, thanks for fixing it!
>> 
>> months later, any news on this?
>> This package just gained another RC bug (dunno how it missed it
>before),
>> and still can't see any active work going on.
>> 
>> 
>> -- 
>> regards,
>> Mattia Rizzolo
>> 
>> GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540 
>.''`.
>> more about me:  https://mapreri.org : :' 
>:
>> Launchpad user: https://launchpad.net/~mapreri  `.
>`'`
>> Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

-- 
Sent from a phone which beats iPhone.

Bug#823143: context: non-free files (CC-BY-NC-SA-3.0)

[Norbert Preining]

On So, 01 Mai 2016, Dmitry Smirnov wrote:
> are licensed as CC-BY-NC-SA-3.0;

Good point. The should neither be in TeX Live or relicensed.

I have already contact the ConTeXt devs and will fix that in
upstream TeX Live before 2016 is released, when this will be
fixed in Debian, too.

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Processed: severity of 823146 is important

[Debian Bug Tracking System]

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

> severity 823146 important
Bug #823146 [src:linux] linux-image-4.5.0-0.bpo.1-amd64: Kernel 4.5 fails to 
boot on AMD A6 APU
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#823146: linux-image-4.5.0-0.bpo.1-amd64: Kernel 4.5 fails to boot on AMD A6 APU

[CJP]

Package: src:linux
Version: 4.5.1-1~bpo8+1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

After installing the recent linux-image update from jessie-backports, my laptop
failed to boot. With the newly installed 4.5 kernel, the system still asked me
for the password of my encrypted hard drive (LUKS), but after confirming that
my password was OK, the screen became black. The system was unresponsive to
Ctrl+Alt+Del, and had to be shut down by keeping the power button pressed.

The system still boots successfully with the previous version 4.4. I could not
find output from the 4.5 booting attempt in /var/log.

I tried booting with the 4.5 kernel in recovery mode, and that showed me more
output on the screen. The system hanged, while repeatedly (very quickly)
printing lines of the following form:

ACPI Error: No handler or method for GPE xx, disabling event
(20160108/evgpe-790)
(xx was various different numbers; it went too fast to read actual numbers.)

Apart from repeatedly printing this line, the system was unresponsive again,
and had to be powered off by keeping the power button pressed.

I searched for the error message on the internet, and found the following
discussion:
https://bugzilla.kernel.org/show_bug.cgi?id=114201

I followed the advice of adding the following kernel boot argument to the 4.5
boot command line:

modprobe.blacklist=sp5100_tco

With that argument added, booting 4.5 was successful. I am writing this while
booted with version 4.5. I seem to have no regressions running the system
without the sp5100_tco module; in version 4.4, the system didn't load
sp5100_tco either, so I don't see why this module would be needed.

While the boot argument solves the problem for me, I think there should be a
solution that lets this package work "out of the box", without requiring such
tweaks by the system maintainer. Black-listing sp5100_tco *by default* could be
such a solution, but I leave it up to you to decide what is the best solution.
I just want to make you aware of this critical bug.



-- Package-specific info:
** Version:
Linux version 4.5.0-0.bpo.1-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.5.1-1~bpo8+1 (2016-04-20)

** Command line:
BOOT_IMAGE=/vmlinuz-4.5.0-0.bpo.1-amd64 
root=UUID=cab2c5d5-4664-4105-bcbd-fcb860cc035d modprobe.blacklist=sp5100_tco ro 
quiet

** Tainted: OE (12288)
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[   36.667372] uvcvideo 1-3:1.0: Entity type for entity Processing 3 was not 
initialized!
[   36.667380] uvcvideo 1-3:1.0: Entity type for entity Camera 1 was not 
initialized!
[   36.667869] input: HP Webcam-101 as 
/devices/pci:00/:00:12.2/usb1/1-3/1-3:1.0/input/input16
[   36.668322] usbcore: registered new interface driver uvcvideo
[   36.668330] USB Video Class driver (1.1.1)
[   36.704666] [drm] fb mappable at 0xD0478000
[   36.704673] [drm] vram apper at 0xD000
[   36.704676] [drm] size 4325376
[   36.704678] [drm] fb depth is 24
[   36.704680] [drm]pitch is 5632
[   36.705096] fbcon: radeondrmfb (fb0) is primary device
[   37.056317] Console: switching to colour frame buffer device 170x48
[   37.066706] radeon :00:01.0: fb0: radeondrmfb frame buffer device
[   37.136351] [drm] Initialized radeon 2.43.0 20080528 for :00:01.0 on 
minor 0
[   37.136636] radeon :01:00.0: enabling device ( -> 0003)
[   37.137346] [drm] initializing kernel modesetting (CAICOS 0x1002:0x6760 
0x103C:0x1663).
[   37.137382] [drm] register mmio base: 0xF030
[   37.137386] [drm] register mmio size: 131072
[   37.137392] vga_switcheroo: enabled
[   37.138242] ATPX version 1, functions 0x0182
[   37.238057] ATOM BIOS: HP
[   37.238559] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
[   37.238562] radeon :01:00.0: GTT: 1024M 0x4000 - 
0x7FFF
[   37.238564] [drm] Detected VRAM RAM=1024M, BAR=256M
[   37.238565] [drm] RAM width 64bits DDR
[   37.238585] [drm] radeon: 1024M of VRAM memory ready
[   37.238586] [drm] radeon: 1024M of GTT memory ready.
[   37.238602] [drm] Loading CAICOS Microcode
[   37.247887] radeon :01:00.0: firmware: direct-loading firmware 
radeon/CAICOS_pfp.bin
[   37.311842] radeon :01:00.0: firmware: direct-loading firmware 
radeon/CAICOS_me.bin
[   37.319540] radeon :01:00.0: firmware: direct-loading firmware 
radeon/BTC_rlc.bin
[   37.354083] radeon :01:00.0: firmware: direct-loading firmware 
radeon/CAICOS_mc.bin
[   37.355918] radeon :01:00.0: firmware: direct-loading firmware 
radeon/CAICOS_smc.bin
[   37.355943] [drm] Internal thermal controller with fan control
[   37.360507] [drm] radeon: dpm initialized
[   37.360600] [drm] GART: num cpu pages 262144, num gpu pages 262144
[   37.367497] [drm] PCIE GART of 1024M enabled (table at 0x00274000).
[   37.367707] radeon :01:00.0: WB 

Bug#822398: marked as done (gnumeric: FTBFS: error: implicit declaration of function 'PX_open_gsf')

[Debian Bug Tracking System]

Your message dated Sun, 01 May 2016 12:34:20 +
with message-id 
and subject line Bug#822398: fixed in gnumeric 1.12.28-2
has caused the Debian Bug report #822398,
regarding gnumeric: FTBFS: error: implicit declaration of function 'PX_open_gsf'
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.)


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

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> LC_ALL=C /usr/bin/intltool-merge  -x -u -c ../../po/.intltool-merge-cache 
> ../../po plugin.xml.in plugin.xml
> libtool: compile:  cc -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--as-needed 
> -DHAVE_CONFIG_H -I. -I../.. -DGNOMELOCALEDIR=\"/usr/share/locale\" 
> -I../../src -I../../src -pthread -I/usr/include/librsvg-2.0 
> -I/usr/include/libgsf-1 -I/usr/include/libxml2 -I/usr/include/gtk-3.0 
> -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
> -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
> -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libgoffice-0.10 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -g -Wsign-compare -Wpointer-arith 
> -Wchar-subscripts -Wwrite-strings -Wdeclar
> ation-after-statement -Wnested-externs -Wmissing-noreturn 
> -Werror=missing-prototypes -Werror=implicit-function-declaration 
> -Wmissing-declarations -Wno-pointer-sign -Werror=format-security 
> -Wstrict-prototypes -Wno-error=format-nonliteral -c paradox.c  -fPIC -DPIC -o 
> .libs/paradox.o
> Found cached translation database
> Merging translations into plugin.xml.
> CREATED plugin.xml
> paradox.c: In function 'paradox_file_open':
> paradox.c:65:6: error: implicit declaration of function 'PX_open_gsf' 
> [-Werror=implicit-function-declaration]
>   if (PX_open_gsf (pxdoc, input) < 0) {
>   ^
> paradox.c:65:2: warning: nested extern declaration of 'PX_open_gsf' 
> [-Wnested-externs]
>   if (PX_open_gsf (pxdoc, input) < 0) {
>   ^
> paradox.c: In function 'paradox_file_probe':
> paradox.c:273:12: warning: variable 'pxh' set but not used 
> [-Wunused-but-set-variable]
>   pxhead_t *pxh;
> ^
> cc1: some warnings being treated as errors
> Makefile:546: recipe for target 'paradox.lo' failed
> make[4]: *** [paradox.lo] Error 1
> make[4]: Leaving directory '/<>/plugins/paradox'

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: gnumeric
Source-Version: 1.12.28-2

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated gnumeric 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, 01 May 2016 22:03:22 +1000
Source: gnumeric
Binary: gnumeric gnumeric-common gnumeric-doc gnumeric-plugins-extra 
gir1.2-gnumeric
Architecture: source amd64 all
Version: 1.12.28-2
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 gir1.2-gnumeric - GObject introspection data for the Gnumeric spreadsheet
 gnumeric   - spreadsheet application for GNOME - main program
 gnumeric-common - spreadsheet application for GNOME - common files
 gnumeric-doc - spreadsheet application for GNOME - documentation
 gnumeric-plugins-extra - spreadsheet application for GNOME - additional plugins
Closes: 819876 822398
Changes:
 gnumeric (1.12.28-2) 

Bug#823144: contextfree: non-free files (CC-BY-NC-1.0)

[Dmitry Smirnov]

Source: contextfree
Version: 3.0.5+dfsg1-2.2
Severity: serious
Usertags: dfsg

The following files are licensed under CC-BY-NC-1.0:

src-osx/KFSplitView.h
src-osx/KFSplitView.m

Please investigate.

-- 
Best wishes,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B

---

If you focus your mind on the freedom and community that you can build
by staying firm, you will find the strength to do it. "Stand for
something, or you will fall for nothing."
-- Richard Stallman


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

Processed: tag #771755 and #749745

[Debian Bug Tracking System]

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

> tags 771755 + pending
Bug #771755 [gnustep-dl2-postgresql-adaptor] gnustep-dl2-postgresql-adaptor: 
unhandled symlink to directory conversion: 
/usr/lib/GNUstep/Frameworks/PostgreSQLEOAdaptor.framework/Resources
Added tag(s) pending.
> tags 749745 + pending
Bug #749745 [src:gnustep-dl2] gnustep-dl2: GCC warnings that may lead to 
runtime issues with new GNUstep libraries
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#822398: tagged as pending

[Dmitry Smirnov]

tag 822398 pending
--

We believe that the bug #822398 you reported has been fixed in the Git
repository. You can see the commit message below and/or inspect the
commit contents at:

http://anonscm.debian.org/cgit/collab-maint/gnumeric.git/diff/?id=a92b802

(This message was generated automatically by
 'git-post-receive-tag-pending-commitmsg' hook).
---
commit a92b802
Author: Dmitry Smirnov 
Date:   Sun May 1 12:08:34 2016

New patch to fix FTBFS with pxlib-dev_0.6.6-1 (Closes: #822398)

 Thanks, Jean Brefort.

  * plugins-extra: don't install paradox plugin.

Processed: tag #754838

[Debian Bug Tracking System]

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

> tags 754838 + pending
Bug #754838 [grr.app] grr.app: Cannot add new feeds
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Bug#822398 tagged as pending

[Debian Bug Tracking System]

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

> tag 822398 pending
Bug #822398 [gnumeric] gnumeric: FTBFS: error: implicit declaration of function 
'PX_open_gsf'
Added tag(s) pending.
> --
Stopping processing here.

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

Bug#823143: context: non-free files (CC-BY-NC-SA-3.0)

[Dmitry Smirnov]

Source: context
Version: 2015.05.18.20150601-2
Severity: serious
Usertags: dfsg

Files in
texmf-dist/doc/context/sources/general/manuals/swiglib
texmf-dist/doc/context/sources/general/manuals/tools
texmf-dist/doc/context/sources/general/manuals/xtables

are licensed as CC-BY-NC-SA-3.0;

Files
texmf-dist/doc/context/sources/general/manuals/readme/mreadme.tex
texmf-dist/doc/context/documents/general/manuals/mreadme.pdf

contain:


The documentation is provided under another Creative Commons licence

   Attribution NonCommercial ShareAlike


(Arguably "mreadme.pdf" is a documentation hence it describes its own 
license.)

Please investigate.

-- 
Cheers,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B

---

You have to start with the truth. The truth is the only way that we can
get anywhere. Because any decision-making that is based upon lies or
ignorance can't lead to a good conclusion.
-- Julian Assange, 2010


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

Processed: found 823043 in 3.07.01-1, notfound 823043 in 10.5.0-1, affects 823043

[Debian Bug Tracking System]

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

> found 823043 3.07.01-1
Bug #823043 [yodl] c++-annotations: FTBFS: `APATH' (symbol) multiply defined
Marked as found in versions yodl/3.07.01-1.
> notfound 823043 10.5.0-1
Bug #823043 [yodl] c++-annotations: FTBFS: `APATH' (symbol) multiply defined
There is no source info for the package 'yodl' at version '10.5.0-1' with 
architecture ''
Unable to make a source version for version '10.5.0-1'
No longer marked as found in versions 10.5.0-1.
> affects 823043 + c++-annotations
Bug #823043 [yodl] c++-annotations: FTBFS: `APATH' (symbol) multiply defined
Added indication that 823043 affects c++-annotations
> thanks
Stopping processing here.

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

Bug#823101: python-geoclue: geoclue is scheduled for removal - switch to geoclue2

[Laurent Bigonville]

On Sat, 30 Apr 2016 21:37:03 +0200 Andreas Beckmann  wrote:
>
> geoclue has been superseded by geoclue2 and therefore was requested
> to be removed (#788279). python-geoclue is the last dependency blocking
> this. Please switch to geoclue2 (or get the python-geoclue package 
removed, too).


The switch to geoclue2 will probably never happen. The design is 
completely different and geoclue2 ships gobject introspection anyway.


So I guess the package can be removed.

Cheers,

Laurent Bigonville

Bug#815369: texi2pdf output filename bug?

[Gavin Smith]

On 30 April 2016 at 22:57, Guo Yixuan  wrote:

> The mwe.texi file by Norbert:
>
> $ cat mwe.texi
> \input texinfo   @c -*-texinfo-*-
> @setfilename min2.info
>
> What ever
> @anchor{@value{cmd1} doc}@anchor{0}
> Here we go
> @bye
>


> ./mwe.aux:1: TeX capacity exceeded, sorry [input stack size=18000].
> @value ->@begingroup @makevalueexpandable
>   @valuexxx
> @makevalueexpandable ->@let @value
>= @expandablevalue @catcode `@-=@other 
> @c...
>
> @value ->@begingroup @makevalueexpandable
>   @valuexxx
> @makevalueexpandable ->@let @value
>= @expandablevalue @catcode `@-=@other 
> @c...
>
> @value ->@begingroup @makevalueexpandable
>   @valuexxx
> @makevalueexpandable ->@let @value
>= @expandablevalue @catcode `@-=@other 
> @c...
> ...
> l.1 ..., used in @value, is not set.} doc-title}{}

Appears to be a bug with --tidy. The filename appears to be irrelevant.

I haven't researched why --tidy makes a difference. I plan to stop
this error by making @value non-expandable when writing to auxiliary
files. This would have the effect that the value used would be the
value at the time when the auxiliary file was read in, instead of when
it was written to, that's when @value worked at all. I think this
change would be okay, because this is already the case for @macro and
I doubt that many documents would rely on changing a @value in the
middle of the document.

$ texi2pdf --command="@set cmd1 HELLO" --tidy  mwe.texi
This is pdfeTeXk, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
 file:line:error style messages enabled.
entering extended mode
(/home/g/src/texinfo/PROJ_SVN/util/mwe.texi
(/home/g/src/texinfo/PROJ_SVN/util/texinfo.tex
Loading texinfo [version 2016-02-20.23]: pdf, fonts, markup, glyphs,
page headings, tables, conditionals, indexing, sectioning, toc, environments,
defuns, macros, cross references, insertions,
(/usr/share/texmf/tex/generic/epsf/epsf.tex
This is `epsf.tex' v2.7.4 <14 February 2011>
) localization, formatting, and turning on texinfo input format.) [1{/usr/share
/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] )
Output written on mwe.pdf (1 page, 8835 bytes).
Transcript written on mwe.log.
This is pdfeTeXk, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
 file:line:error style messages enabled.
entering extended mode
(/home/g/src/texinfo/PROJ_SVN/util/mwe.texi
(/home/g/src/texinfo/PROJ_SVN/util/texinfo.tex
Loading texinfo [version 2016-02-20.23]: pdf, fonts, markup, glyphs,
page headings, tables, conditionals, indexing, sectioning, toc, environments,
defuns, macros, cross references, insertions,
(/usr/share/texmf/tex/generic/epsf/epsf.tex
This is `epsf.tex' v2.7.4 <14 February 2011>
) localization, formatting, and turning on texinfo input format.) (./mwe.aux
./mwe.aux:1: TeX capacity exceeded, sorry [input stack size=1500].
@value ->@begingroup @makevalueexpandable
  @valuexxx
@makevalueexpandable ->@let @value
   = @expandablevalue @catcode `@-=@other @c...

@value ->@begingroup @makevalueexpandable
  @valuexxx
@makevalueexpandable ->@let @value
   = @expandablevalue @catcode `@-=@other @c...

@value ->@begingroup @makevalueexpandable
  @valuexxx
@makevalueexpandable ->@let @value
   = @expandablevalue @catcode `@-=@other @c...
...
l.1 ..., used in @value, is not set.} doc-title}{}

No pages of output.
Transcript written on mwe.log.
/usr/local/bin/texi2dvi: pdfetex exited with bad status, quitting.
$ rm mwe.t2d/ mwe.aux -r
rm: cannot remove 'mwe.aux': No such file or directory
$ texi2pdf --command="@set cmd1 HELLO" mwe.texi
tar: mwe.aux: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
This is pdfeTeXk, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
 file:line:error style messages enabled.
entering extended mode
(/home/g/src/texinfo/PROJ_SVN/util/mwe.t2d/pdf/xtr/mwe.texi
(/home/g/src/texinfo/PROJ_SVN/util/texinfo.tex
Loading texinfo [version 2016-02-20.23]: pdf, fonts, markup, glyphs,
page headings, tables, conditionals, indexing, sectioning, toc, environments,
defuns, macros, cross references, insertions,
(/usr/share/texmf/tex/generic/epsf/epsf.tex
This is `epsf.tex' v2.7.4 <14 February 2011>
) localization, formatting, and turning on texinfo input format.) [1{/usr/share
/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] )
Output written on mwe.pdf (1 page, 8685 bytes).
Transcript written on mwe.log.
This is pdfeTeXk, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
 file:line:error style messages enabled.
entering extended mode
(/home/g/src/texinfo/PROJ_SVN/util/mwe.t2d/pdf/xtr/mwe.texi

Processed: Re: Bug#823135: atop doesn't log anything on some days: trap divide error

[Debian Bug Tracking System]

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

> Severity #823135 normal
Bug #823135 [atop] atop doesn't log anything on some days: trap divide error
Severity set to 'normal' from 'grave'
> tags #823135 upstream help
Bug #823135 [atop] atop doesn't log anything on some days: trap divide error
Added tag(s) upstream and help.
> thanks
Stopping processing here.

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

Bug#823135: atop doesn't log anything on some days: trap divide error

[Marc Haber]

Severity #823135 normal
tags #823135 upstream help
thanks

Please note that filing bugs with severly inflated severity doesn't
help to motivate the maintainer. Additionally, this is an upstream
bug, please kindly take it upstream yourself.

Do you want to help in packaging? There is a new upstream version
available that needs packaging.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#823135: atop doesn't log anything on some days: trap divide error

[Vincent Lefevre]

Package: atop
Version: 1.26-2+b1
Severity: grave
Justification: renders package unusable

Since midnight, I don't get any atop logs, which is really annoying to
know what happened a few hours ago. The last file in /var/log/atop is:

-rw-r--r-- 1 root root 3258933 2016-05-01 00:00:01 atop_20160430

and there is no atop_20160501 in particular. According to the atop(1),

   View the contents of today's standard logfile interactively:

 atop -r

but:

zira:~> atop -r
/var/log/atop//atop_20160501 - open raw file: No such file or directory

So, the file should have been there.

With journalctl, I can see concerning atop:

[...]
Apr 27 00:00:01 zira CRON[28037]: (root) CMD (invoke-rc.d atop _cron)
Apr 28 00:00:01 zira CRON[24816]: (root) CMD (invoke-rc.d atop _cron)
Apr 29 00:00:01 zira CRON[14896]: (root) CMD (invoke-rc.d atop _cron)
Apr 30 00:00:01 zira CRON[15535]: (root) CMD (invoke-rc.d atop _cron)
May 01 00:00:01 zira CRON[30335]: (root) CMD (invoke-rc.d atop _cron)
May 01 00:00:01 zira kernel: traps: atop[30371] trap divide error ip:4073c2 
sp:7ffc215d2860 error:0 in atop[40+26000]

I can see that this is not the first time I get a "trap divide error"
for atop:

Oct 01 00:00:01 zira kernel: traps: atop[11095] trap divide error ip:40780a 
sp:7ffd6285ef08 error:0 in atop[40+26000]
Oct 30 00:00:01 zira kernel: traps: atop[28965] trap divide error ip:40780a 
sp:7ffea61350f8 error:0 in atop[40+26000]
Dec 27 15:13:02 zira kernel: traps: atop[788] trap divide error ip:4073c2 
sp:7ffef102f9d0 error:0 in atop[40+26000]
Jan 18 17:43:00 zira kernel: traps: atop[758] trap divide error ip:4073c2 
sp:7fffe0ce3320 error:0 in atop[40+26000]
Feb 08 00:00:01 zira kernel: traps: atop[7906] trap divide error ip:4073c2 
sp:7ffd23cd0e00 error:0 in atop[40+26000]
Feb 22 00:00:01 zira kernel: traps: atop[29804] trap divide error ip:4073c2 
sp:7fff36a32cb0 error:0 in atop[40+26000]
Mar 08 00:00:01 zira kernel: traps: atop[21994] trap divide error ip:4073c2 
sp:7ffca552f5a0 error:0 in atop[40+26000]
Mar 15 00:00:01 zira kernel: traps: atop[8938] trap divide error ip:4073c2 
sp:7ffc48db6880 error:0 in atop[40+26000]
Apr 01 00:00:01 zira kernel: traps: atop[27738] trap divide error ip:4073c2 
sp:7ffd11c5cdb0 error:0 in atop[40+26000]
Apr 05 00:00:01 zira kernel: traps: atop[9025] trap divide error ip:4073c2 
sp:7ffe9e337e00 error:0 in atop[40+26000]
May 01 00:00:01 zira kernel: traps: atop[30371] trap divide error ip:4073c2 
sp:7ffc215d2860 error:0 in atop[40+26000]

The atop_20160405 is also missing. So, the missing files seem to
correspond to these "trap divide error" errors (a division by 0?).

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages atop depends on:
ii  libc62.22-7
ii  libncurses5  6.0+20160319-1
ii  libtinfo56.0+20160319-1
ii  lsb-base 9.20160110
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages atop recommends:
ii  cron  3.0pl1-128

atop suggests no packages.

-- no debconf information

Bug#746005: guile-2.0 migration

[Emilio Pozuelo Monfort]

On 29/04/16 22:33, Don Armstrong wrote:
> On Fri, 29 Apr 2016, Emilio Pozuelo Monfort wrote:
>> We talked about this on the RT meeting yesterday and agreed to bump
>> this to RC again. We wouldn't like to release Stretch with guile-1.8
>> just for lilypond's sake, and it is better to act now that there's
>> plenty of time before the freeze so that a new version can be uploaded
>> (possibly to experimental for the time being) and fixes can be
>> applied.
> 
> OK. Basically, there's no way that 2.18 will be fixed to work with Guile
> 2.0, but assuming that 2.20 gets released before stretch, this will be
> workable.
> 
>> We can discuss this again later in the cycle if necessary, though
>> hopefully lilypond can get in shape and we won't need to do that :)
> 
> Well, the shape that will be required is the release of a stable
> lilypond release which supports guile. Hopefully soon.
> 
>> There have been plenty of 'unstable' releases (last one was 2.19.40
>> just a few days ago) and those have a --with-guile2 configure switch.
>> It may be a good idea to upload that to experimental with guile 2.0
>> support?
> 
> Sure, but this won't fix the version of lilypond in unstable. [I at
> least do not have the time to support a development release of lilypond
> through the lifetime of a stable release.]

Yeah, but at least people can try it and report bugs. Uploading to experimental
means we don't release with a development version.

> Are auto-removals from testing currently off? [Basically, I'd like to
> avoid having lilypond removed from testing until we're closer to the
> release if that's at all possible.]

No, they are enabled.

Cheers,
Emilio

Bug#809671: should openmeeg be removed from Debian?

[Gianfranco Costamagna]

Hi,

lets put a deadline.

is it ok for you to upload something before one month or two starting from 
today?

we are working hard in removing vtk5 from the archive and also libpng12, and 
this bug is
one of the last unsolved blockers for now.

sorry for being pushy, but it missed jessie, it will probably miss stretch too 
if we don't act
in a timely manner.

cheers!

Gianfranco

On Sat, 23 Apr 2016 11:42:23 + Mattia Rizzolo  wrote:
> On Sat, Jan 02, 2016 at 05:12:12PM +, Mattia Rizzolo wrote:
> > On Sat, Jan 02, 2016 at 12:04:07PM -0500, Yaroslav Halchenko wrote:
> > > On Sat, 02 Jan 2016, Mattia Rizzolo wrote:
> > > I would not call it dead upstream.  It is a research project after all -
> > > so people develop it whenever there is need.
> > 
> > ok, sorry, I must have looked to either the wrong place, or in the wrong
> > way.
> > 
> > > I will look into fixing packaging up one way or another within a
> > > week or two, ok?  and if I upload new release, I will close this one
> > 
> > that's cool, thanks for fixing it!
> 
> months later, any news on this?
> This package just gained another RC bug (dunno how it missed it before),
> and still can't see any active work going on.
> 
> 
> -- 
> regards,
> Mattia Rizzolo
> 
> GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
> more about me:  https://mapreri.org : :'  :
> Launchpad user: https://launchpad.net/~mapreri  `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-



signature.asc
Description: OpenPGP digital signature

Bug#822322: openmeeg: please switch to vtk5

[Gianfranco Costamagna]

control: retitle -1 openmeeg: please switch to vtk6
On Sat, 23 Apr 2016 11:40:13 + Mattia Rizzolo  wrote:
> Source: openmeeg
> Version: 2.0.0.dfsg-5.2
> Severity: serious
> Control: block 822321 by -1
> 
> We're kicking vtk5 out of Debian, but your package still build-depend on
> it.  Funnily, the binary doesn't depend on vtk, so I wonder if the
> build-dep is just needed at all.
> 
> -- 
> regards,
> Mattia Rizzolo
> 
> GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
> more about me:  https://mapreri.org : :'  :
> Launchpad user: https://launchpad.net/~mapreri  `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-



signature.asc
Description: OpenPGP digital signature

Processed: Re: openmeeg: please switch to vtk5

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 openmeeg: please switch to vtk6
Bug #822322 [src:openmeeg] openmeeg: please switch to vtk5
Changed Bug title to 'openmeeg: please switch to vtk6' from 'openmeeg: please 
switch to vtk5'.

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

Bug#821876: marked as done (libfeel++-dev: Depends on libvtk5-dev, which will be removed)

[Debian Bug Tracking System]

Your message dated Sun, 1 May 2016 08:35:04 +
with message-id <20160501083504.gc6...@chase.mapreri.org>
and subject line Fixed in 1:0.101.1-1
has caused the Debian Bug report #821876,
regarding libfeel++-dev: Depends on libvtk5-dev, which will be removed
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.)


-- 
821876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821876
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libfeel++-dev
Severity: serious
Justification: Depends on vtk5
Control: block 798164 with -1

Dear Maintainer,

Your package depends on vtk 5.x, which should not be in stretch.
Please switch to vtk 6.x or drop the dependency.

--
tobi

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 1:0.101.1-1

I managed to forget to include the bugs in the changelog, so closing
them manually.

The bug you have reported has been fixed in the last update, about to be
installed in the archive.


The updated changelog:

feel++ (1:0.101.1-1) unstable; urgency=medium

  * Team upload.

  [ Mattia Rizzolo ]
  * New upstream version.
+ Fix building with gcc5.  Closes: #777848, #811714
+ Use vtk6.  Closes: #821876
+ Use boost1.58.  Closes: #822120
  * debian/control:
+ Run wrap-and-sort.
+ Build-depend on slepc-dev instead of the versioned libslepc3.4.2-dev.
+ Move packaging to git.
+ Add new build-deps: libopenturns, libreadline, libscotch, libtrilinos-ml,
  libvtk6, paraview, petsc.
+ Remove build-depends on cdbs.
+ Stop building the -dbg package.  There are automatic debug packages now.
+ Stop building for ia64 and sparc, those architectures are gone now.
+ Bump Standards-Version to 3.9.8, no changes needed.
+ Make the descriptions policy compliant.
+ Disable building on powerpc: probably it won't be able anymore.
  * debian/watch: update for the move to github.
  * debian/rules:
+ Rewrite using the dh sequencer. (also bump compat level to 9).
+ Don't do parallel building.  The build really requires a lot of ram.

  [ Gianfranco Costamagna ]
  * debian/control:
+ Use default clang version.
+ Add astyle dependency.
  * debian/rules:
+ Remove PETSC hack on rules file.
+ Build with debug symbols.
+ Disable doxygen documentation, upstream didn't provide the api directory.
  * debian/patches/fix-scotch.patch: fix scotch include cmake script.

 -- Mattia Rizzolo   Sat, 30 Apr 2016 22:24:42 +


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


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

Bug#822120: marked as done (Boost 1.55 to be removed; your attention required)

[Debian Bug Tracking System]

Your message dated Sun, 1 May 2016 08:35:04 +
with message-id <20160501083504.gc6...@chase.mapreri.org>
and subject line Fixed in 1:0.101.1-1
has caused the Debian Bug report #822120,
regarding Boost 1.55 to be removed; your attention required
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.)


-- 
822120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: feel++
Severity: normal

Boost 1.55 has not built correctly since the GCC 5 introduction in July 2015 
and I plan
to ask for its removal from unstable very shortly.  It has already been removed 
from
testing.

The package feel++ appeared on a list of reverse dependencies generated 
using 'dak rm -Rn boost1.55' (see below).  This bug is to request an
upload with updated boost dependencies.

If your package build-depends on the default boost, then a simple rebuild will 
suffice.
If your package uses 1.55-versioned build-deps, then please check whether you 
can
move to default boost.  Or if not, at least move to 1.58.

Output from ssh mirror.ftp-master.debian.org "dak rm -Rn boost1.55" follows.

Checking reverse dependencies...
# Broken Depends:
ball: ballview [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  libball1.4 [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  libballview1.4 [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  python-ball [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  python-ballview [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
cufflinks/non-free: cufflinks [amd64]
diet: diet-agent [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  libdiet-admin2.8 [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  libdiet-client2.8 [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  libdiet-dagda2.8 [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  libdiet-sed2.8 [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
feel++: feel++-apps [amd64 i386 powerpc]
libfeel++1 [amd64 i386 powerpc]
gqrx-sdr: gqrx-sdr [kfreebsd-amd64 kfreebsd-i386]
gr-air-modes: gr-air-modes [kfreebsd-amd64 kfreebsd-i386]
  libair-modes0 [kfreebsd-amd64 kfreebsd-i386]
gr-osmosdr: gr-osmosdr [kfreebsd-amd64 kfreebsd-i386]
libgnuradio-osmosdr0.1.3 [kfreebsd-amd64 kfreebsd-i386]
kig: kig [hurd-i386]
librime: librime-bin [hurd-i386]
 librime1 [hurd-i386]
limereg: limereg [mips mipsel]
mongodb: mongodb-clients [hurd-i386 kfreebsd-i386]
 mongodb-server [hurd-i386 kfreebsd-i386]
openvrml: libopenvrml9 [amd64 armel armhf i386 mips mipsel powerpc ppc64el 
s390x]
  openvrml-lookat [amd64 armel armhf i386 mips mipsel powerpc ppc64el 
s390x]
pcb2gcode: pcb2gcode [kfreebsd-amd64 kfreebsd-i386]
qbittorrent: qbittorrent [kfreebsd-amd64 kfreebsd-i386]
 qbittorrent-nox [kfreebsd-amd64 kfreebsd-i386]
qpid-cpp: libqpidcommon2 [amd64 arm64 i386 mipsel powerpc ppc64el]
  qpidd [amd64 arm64 i386 mipsel powerpc ppc64el]
smc: smc [amd64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel 
powerpc s390x]
swift-im: libswiften-dev [amd64 arm64 armel armhf i386 mips mipsel powerpc 
ppc64el s390x]
  libswiften2 [amd64 arm64 armel armhf i386 mips mipsel powerpc ppc64el 
s390x]
  swift-im [amd64 arm64 armel armhf i386 mips mipsel powerpc ppc64el 
s390x]
--- End Message ---
--- Begin Message ---
Version: 1:0.101.1-1

I managed to forget to include the bugs in the changelog, so closing
them manually.

The bug you have reported has been fixed in the last update, about to be
installed in the archive.


The updated changelog:

feel++ (1:0.101.1-1) unstable; urgency=medium

  * Team upload.

  [ Mattia Rizzolo ]
  * New upstream version.
+ Fix building with gcc5.  Closes: #777848, #811714
+ Use vtk6.  Closes: #821876
+ Use boost1.58.  Closes: #822120
  * debian/control:
+ Run wrap-and-sort.
+ Build-depend on slepc-dev instead of the versioned libslepc3.4.2-dev.
+ Move packaging to git.
+ Add new build-deps: libopenturns, 

Bug#811714: marked as done (FTBFS: unknown type name 'matrix'; did you mean 'Feel::tag::matrix')

[Debian Bug Tracking System]

Your message dated Sun, 1 May 2016 08:35:04 +
with message-id <20160501083504.gc6...@chase.mapreri.org>
and subject line Fixed in 1:0.101.1-1
has caused the Debian Bug report #811714,
regarding FTBFS: unknown type name 'matrix'; did you mean 'Feel::tag::matrix'
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.)


-- 
811714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: feel++
Version: 1:0.99.0-final.1-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-unknown-type-name

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> cd /build/feel++-aBi8dr/feel++-0.99.0-final.1/obj-x86_64-linux-gnu/feel && 
> /usr/bin/clang++-3.5   -DBOOST_FILESYSTEM_VERSION=3 
> -DBOOST_NO_CXX11_SCOPED_ENUMS -DBOOST_NO_CXX11_VARIADIC_TEMPLATES 
> -DBOOST_NO_SCOPED_ENUMS -DBOOST_PARAMETER_MAX_ARITY=24 
> -DBOOST_RESULT_OF_USE_TR1 -DBOOST_TEST_DYN_LINK -DBOOST_UBLAS_MOVE_SEMANTICS 
> -DFEELPP_HAS_DLFCN_H -DFEELPP_HAS_DLOPEN -DFEELPP_HAS_GMSH=1 
> -DFEELPP_HAS_MPI=1 -DFEELPP_HAS_MPI_H=1 -DFEELPP_HAS_PETSC 
> -DFEELPP_HAS_PETSC_H -DGMSH_EXECUTABLE=/usr/bin/gmsh -DHAVE_LIBDL -DIN_GINAC 
> -D_FEELPP_HAS_GMSH_ -Dfeelpp_EXPORTS 
> -I/build/feel++-aBi8dr/feel++-0.99.0-final.1/contrib 
> -I/usr/lib/openmpi/include -I/usr/lib/openmpi/include/openmpi 
> -I/usr/include/hdf5/openmpi 
> -I/build/feel++-aBi8dr/feel++-0.99.0-final.1/obj-x86_64-linux-gnu/contrib/cln/include
>  -I/build/feel++-aBi8dr/feel++-0.99.0-final.1/contrib/ginac 
> -I/build/feel++-aBi8dr/feel++-0.99.0-final.1/obj-x86_64-linux-gnu/contrib/ginac
>  -I/build/feel++-aBi8dr/feel++-0.99.0-final.1/contrib/ginac/gina
> c 
> -I/build/feel++-aBi8dr/feel++-0.99.0-final.1/obj-x86_64-linux-gnu/contrib/ginac/ginac
>  -I/build/feel++-aBi8dr/feel++-0.99.0-final.1/contrib/nlopt/api 
> -I/build/feel++-aBi8dr/feel++-0.99.0-final.1/contrib/eigen -I/usr/include/ANN 
> -I/build/feel++-aBi8dr/feel++-0.99.0-final.1/obj-x86_64-linux-gnu/contrib/gflags/include
>  
> -I/build/feel++-aBi8dr/feel++-0.99.0-final.1/obj-x86_64-linux-gnu/contrib/glog/include
>  -I/usr/include/python2.7 -I/usr/lib/petscdir/3.4.2/include 
> -I/usr/lib/petscdir/3.4.2/linux-gnu-c-opt/include -I/usr/include/suitesparse 
> -I/usr/include/scotch -I/usr/lib/x86_64-linux-gnu/hdf5/openmpi/include 
> -I/usr/lib/petsc/include -I/usr/lib/petsc/linux-gnu-c-opt/include 
> -I/usr/lib/slepc/linux-gnu-c-opt/include -I/usr/lib/slepc/include 
> -I/usr/include/gmsh -I/build/feel++-aBi8dr/feel++-0.99.0-final.1/contrib/gmsh 
> -I/build/feel++-aBi8dr/feel++-0.99.0-final.1/obj-x86_64-linux-gnu 
> -I/build/feel++-aBi8dr/feel++-0.99.0-final.1 
> -I/build/feel++-aBi8dr/feel++-0.99.0-final.1/contrib/gmm/include  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wdate-time 
> -D_FORTIFY_SOURCE=2 -std=c++0x -std=c++11 -ftemplate-depth=1024 
> -stdlib=libstdc++ -O2 -DNDEBUG -g0 -fPIC-Wall -Wno-unused 
> -Wno-sign-compare  -Wno-deprecated-register -fmacro-backtrace-limit=0 
> -ftemplate-backtrace-limit=0 -UBOOST_UBLAS_TYPE_CHECK -o 
> CMakeFiles/feelpp.dir/feelalg/preconditioner.cpp.o -c 
> /build/feel++-aBi8dr/feel++-0.99.0-final.1/feel/feelalg/preconditioner.cpp
> In file included from 
> /build/feel++-aBi8dr/feel++-0.99.0-final.1/feel/feelalg/preconditioner.cpp:29:
> In file included from 
> /build/feel++-aBi8dr/feel++-0.99.0-final.1/feel/feelalg/preconditioner.hpp:35:
> In file included from 
> /build/feel++-aBi8dr/feel++-0.99.0-final.1/feel/feelalg/matrixsparse.hpp:56:
> /usr/include/boost/numeric/ublas/matrix.hpp:1387:35: error: unknown type name 
> 'matrix'; did you mean 'Feel::tag::matrix'?
> fixed_matrix  = (matrix m) {
>   ^
> /build/feel++-aBi8dr/feel++-0.99.0-final.1/feel/feelcore/parameter.hpp:69:27: 
> note: 'Feel::tag::matrix' declared here
> BOOST_PARAMETER_NAME( matrix )
>   ^
> /usr/include/boost/parameter/name.hpp:140:7: note: expanded from macro 
> 'BOOST_PARAMETER_NAME'
> )(name) \
>   ^
> 

Bug#777848: marked as done (feel++: ftbfs with GCC-5)

[Debian Bug Tracking System]

Your message dated Sun, 1 May 2016 08:35:04 +
with message-id <20160501083504.gc6...@chase.mapreri.org>
and subject line Fixed in 1:0.101.1-1
has caused the Debian Bug report #777848,
regarding feel++: ftbfs with GCC-5
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.)


-- 
777848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:feel++
Version: 1:0.99.0-final.1-1
Severity: normal
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The
severity of this report may be raised before the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc5-20150205/feel++_0.99.0-final.1-1_unstable_gcc5.log
The last lines of the build log are at the end of this report.

To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ 

Common build failures are C11 as the default C mode, new warnings
resulting in build failures with -Werror turned on, or new/dropped
symbols in Debian symbols files.  For other C/C++ related build failures
see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html

[...]
-- set direct/DIRserial.c as c++
-- set direct/DIRsubrout.c as c++
-- set cdirect/cdirect.c as c++
-- set cdirect/hybrid.c as c++
-- set praxis/praxis.c as c++
-- set luksan/plis.c as c++
-- set luksan/plip.c as c++
-- set luksan/pnet.c as c++
-- set luksan/mssubs.c as c++
-- set luksan/pssubs.c as c++
-- set crs/crs.c as c++
-- set mlsl/mlsl.c as c++
-- set mma/mma.c as c++
-- set mma/ccsa_quadratic.c as c++
-- set cobyla/cobyla.c as c++
-- set newuoa/newuoa.c as c++
-- set neldermead/nldrmd.c as c++
-- set neldermead/sbplx.c as c++
-- set auglag/auglag.c as c++
-- set bobyqa/bobyqa.c as c++
-- set isres/isres.c as c++
-- set slsqp/slsqp.c as c++
-- set esch/esch.c as c++
-- set api/general.c as c++
-- set api/options.c as c++
-- set api/optimize.c as c++
-- set api/deprecated.c as c++
-- set api/f77api.c as c++
-- set util/mt19937ar.c as c++
-- set util/sobolseq.c as c++
-- set util/timer.c as c++
-- set util/stop.c as c++
-- set util/redblack.c as c++
-- set util/qsort_r.c as c++
-- set util/rescale.c as c++
-- Performing Test standard_math_library_linked_to_automatically
-- Performing Test standard_math_library_linked_to_automatically - Failed
-- Performing Test standard_math_library_linked_to_as_m
-- Performing Test standard_math_library_linked_to_as_m - Failed
CMake Error at contrib/eigen/CMakeLists.txt:76 (message):
  Can't link to the standard math library.  Please report to the Eigen
  developers, telling them about your platform.


-- Configuring incomplete, errors occurred!
See also 
"/build/feel++-LZ7j46/feel++-0.99.0-final.1/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
See also 
"/build/feel++-LZ7j46/feel++-0.99.0-final.1/obj-x86_64-linux-gnu/CMakeFiles/CMakeError.log".
make: *** [obj-x86_64-linux-gnu/CMakeCache.txt] Error 1
/usr/share/cdbs/1/class/cmake.mk:55: recipe for target 
'obj-x86_64-linux-gnu/CMakeCache.txt' failed
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
--- End Message ---
--- Begin Message ---
Version: 1:0.101.1-1

I managed to forget to include the bugs in the changelog, so closing
them manually.

The bug you have reported has been fixed in the last update, about to be
installed in the archive.


The updated changelog:

feel++ (1:0.101.1-1) unstable; urgency=medium

  * Team upload.

  [ Mattia Rizzolo ]
  * New upstream version.
+ Fix building with gcc5.  Closes: #777848, #811714
+ Use vtk6.  Closes: #821876
+ Use boost1.58.  Closes: #822120
  * debian/control:
+ Run wrap-and-sort.
+ Build-depend on slepc-dev instead of the versioned libslepc3.4.2-dev.
+ Move packaging to git.
+ Add new build-deps: libopenturns, libreadline, libscotch, libtrilinos-ml,
  libvtk6, paraview, petsc.
+ Remove build-depends on cdbs.
+ Stop building the -dbg package.  There are automatic debug packages now.
+ Stop building for ia64 and sparc, those architectures are gone now.

Bug#822383: marked as done (gringo: FTBFS: error: 'pow' is not a member of 'std')

[Debian Bug Tracking System]

Your message dated Sun, 01 May 2016 07:20:48 +
with message-id 
and subject line Bug#822383: fixed in gringo 4.5.4-2
has caused the Debian Bug report #822383,
regarding gringo: FTBFS: error: 'pow' is not a member of 'std'
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.)


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

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> g++ -o build/release/libgringo/src/term.o -c -g -O2 -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -O3 
> -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DNDEBUG=1 -DWITH_LUA=1 
> -DWITH_PYTHON=1 -I/usr/include/lua5.2 -I/usr/include/python2.7 -Ilibgringo 
> -Ibuild/release/libgringo/src -Ilibgringo/src -Ilibprogram_opts 
> -Ilibprogram_opts/src libgringo/src/term.cc
> libgringo/src/term.cc: In member function 'virtual double 
> Gringo::FunctionTerm::estimate(double, const VarSet&) const':
> libgringo/src/term.cc:1848:37: error: 'pow' is not a member of 'std'
>  double root = std::max(1.0, std::pow(((*name).empty() ? size : 
> size/2.0), 1.0/args.size()));
>  ^
> scons: *** [build/release/libgringo/src/term.o] Error 1
> scons: building terminated because of errors.
> debian/rules:49: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 2

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: gringo
Source-Version: 4.5.4-2

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

Debian distribution maintenance software
pp.
Thomas Krennwallner  (supplier of updated gringo 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, 01 May 2016 08:47:29 +0200
Source: gringo
Binary: gringo
Architecture: source amd64
Version: 4.5.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Thomas Krennwallner 
Description:
 gringo - grounding tools for (disjunctive) logic programs
Closes: 822383
Changes:
 gringo (4.5.4-2) unstable; urgency=medium
 .
   * Bug fix: "FTBFS: error: 'pow' is not a member of 'std'", thanks to
 Martin Michlmayr (Closes: #822383).
   * Add patch to fix random python multithreading segfaults (upstream bug 117)
   * Add patch to fix #min/#max translation bug (upstream bug 119)
   * Build with liblua5.3
   * Bump Standards-Version to 3.9.8
Checksums-Sha1:
 c43b7ba91692a2c3878abf728c593ff2227e69fd 2056 gringo_4.5.4-2.dsc
 daac6e09a795711ec9637a21b102b055dc586dc2 10464 gringo_4.5.4-2.debian.tar.xz
 ed66e65af4942fa3c857420187ad43fee35d13ce 28247694 
gringo-dbgsym_4.5.4-2_amd64.deb
 448bbd605964a478657c17df862738c80042e811 1839910 gringo_4.5.4-2_amd64.deb
Checksums-Sha256:
 ff554b448edb20a4dab4ff0762bb09ea8c684418ef5b5a71a120687c9839b8d7 2056 
gringo_4.5.4-2.dsc
 52d8da8870d9a2f398c0e6030e8e7b656545ea42462149c9542e2a445dfdb95a 10464 
gringo_4.5.4-2.debian.tar.xz
 ecfd7a5e7093a2f5ea13c95b4ff80ec580ca36640a4f2b0e57387928422f5dca 28247694 
gringo-dbgsym_4.5.4-2_amd64.deb
 7bbd157d2ba8fb452b78e945f4f77fd5f5062deda677bc02fb68c95bece127bd 1839910 
gringo_4.5.4-2_amd64.deb
Files:
 c606da6e48a4e077b7954197cb4a47d6 2056 interpreters extra gringo_4.5.4-2.dsc
 a7ed5e2a5602015d35e3e92086eaaab8 10464 interpreters extra 
gringo_4.5.4-2.debian.tar.xz
 606cfa5391a88920f0d4db612c155ea4 28247694 debug extra 
gringo-dbgsym_4.5.4-2_amd64.deb
 92c6a12d01dfe35ec69c8d6cc0fac23c 1839910 interpreters extra 
gringo_4.5.4-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXJahnAAoJECeX33SmZpqpHzgP/13UExUqxkUkEGZdufF1CDLT
zHiv80Rb0UedPLHNgmCCLU5enBxf+I5knaGOF0hhusDdILpDJd6FlXyNroUHANV8

Bug#813065: marked as done (mgltools-gle: FTBFS in sid: Error: Unknown SWIG preprocessor directive: typemaps)

[Debian Bug Tracking System]

Your message dated Sun, 01 May 2016 07:06:52 +
with message-id 
and subject line Bug#813065: fixed in mgltools-gle 1.5.7~rc1+cvs.20140424-2
has caused the Debian Bug report #813065,
regarding mgltools-gle: FTBFS in sid: Error: Unknown SWIG preprocessor 
directive: typemaps
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.)


-- 
813065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mgltools-gle
Version: 1.5.7~rc1+cvs.20140424-1
Severity: serious
Tags: sid stretch
Justification: fails to build from source (but built successfully in the past)

Hi,

mgltools-gle FTBFS in sid and stretch (but builds fine in jessie):

[...]
 debian/rules build
dh build --with python2
   dh_testdir
   dh_update_autotools_config
   dh_auto_configure
   dh_auto_build
python setup.py build --force
running build
running build_ext
building '_gle' extension
swigging gle/gle.i to gle/gle_wrap.c
swig -python -o gle/gle_wrap.c gle/gle.i
gle/gle.i:152: Error: Unknown SWIG preprocessor directive: typemaps (if this is 
a block of target language code, delimit it with %{ and %})
gle/gle.i:175: Error: Unknown SWIG preprocessor directive: typemaps (if this is 
a block of target language code, delimit it with %{ and %})
gle/gle.i:198: Error: Unknown SWIG preprocessor directive: typemaps (if this is 
a block of target language code, delimit it with %{ and %})
gle/gle.i:221: Error: Unknown SWIG preprocessor directive: typemaps (if this is 
a block of target language code, delimit it with %{ and %})
error: command 'swig' failed with exit status 1
dh_auto_build: python setup.py build --force returned exit code 1
debian/rules:15: recipe for target 'build' failed
make: *** [build] Error 1


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: mgltools-gle
Source-Version: 1.5.7~rc1+cvs.20140424-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated mgltools-gle 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, 01 May 2016 08:50:14 +0200
Source: mgltools-gle
Binary: mgltools-gle
Architecture: source
Version: 1.5.7~rc1+cvs.20140424-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 mgltools-gle - GLE library Python extension
Closes: 813065
Changes:
 mgltools-gle (1.5.7~rc1+cvs.20140424-2) unstable; urgency=medium
 .
   * Fix FTBFS with stricter new swig (Thanks for the patch to Adam Conrad)
 Closes: #813065 (LP: #1562470)
   * cme fix dpkg-control
   * debhelper 9
   * DEP5
   * remove obsolete debian/pycompat
Checksums-Sha1:
 5a9d318b47f1a6611249cd7f77bc68a32a738810 2306 
mgltools-gle_1.5.7~rc1+cvs.20140424-2.dsc
 3730fbbd80259bcbd8ca8b33dce419b64eca9e48 8248 
mgltools-gle_1.5.7~rc1+cvs.20140424-2.debian.tar.xz
Checksums-Sha256:
 6f44e411f4414ca5933fc4cc1cb7589a6a738ec2f75c02cf4c6bcf8401f8a39a 2306 
mgltools-gle_1.5.7~rc1+cvs.20140424-2.dsc
 ebd00af705880ff5543b545f058f6a6a6d276d658e1fc37b50113802d81f848a 8248 
mgltools-gle_1.5.7~rc1+cvs.20140424-2.debian.tar.xz
Files:
 02a88b970e0eff19bd25031287b5fd84 2306 non-free/libs optional 
mgltools-gle_1.5.7~rc1+cvs.20140424-2.dsc
 e9be036d38310463609a81334e036934 8248 non-free/libs optional 
mgltools-gle_1.5.7~rc1+cvs.20140424-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXJaigAAoJEFeKBJTRxkbRwi8P/2VSBiw6+91j7Mz1srrTruSa
Bdb17osoWPHnSf+++Gp2wAZBgiszSXNbHbkkbp7qHckT2IeFFcQcG2reM8OkrVr6
9JC9sTVu7uP7n0YZDZ42D7fbyKapFr0hsFW7s7P1qa1oRd55jouViDVIkT03MaZz
TLfgNiVfIPIXCxK4TIXNWb72X0Lj/R5Jpz6w+kXw57JZFTQMgBUaxq56QLWvnCkn
prunO88CLJe6UDl2MQnDMDyx1WPEGgE0EBD+NB7scv77vxPY3KOhUqZPf+LfYqRW
FgQjcc4t/LK6SNzoQGNj0twkThiZeUbScu82pwAlpt8Qrxm8m/ifub5GsZi7z0Fx
knEQQD0Hp7AYFA0iQKFw9e+xnAaOe2vlnAXfdCS6r31Ow+nbhTYBdenLHJL7QNjU

Bug#822409: marked as done (pkg-config: FTBFS: error: m4_copy: won't overwrite defined macro: glib_DEFUN)

[Debian Bug Tracking System]

Your message dated Sun, 01 May 2016 06:49:05 +
with message-id 
and subject line Bug#822409: fixed in pkg-config 0.29-4
has caused the Debian Bug report #822409,
regarding pkg-config: FTBFS: error: m4_copy: won't overwrite defined macro: 
glib_DEFUN
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.)


-- 
822409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pkg-config
Version: 0.29-3
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
>dh_testdir
>dh_update_autotools_config
>dh_autoreconf
> m4macros/glib-gettext.m4:39: error: m4_copy: won't overwrite defined macro: 
> glib_DEFUN
> m4macros/glib-gettext.m4:39: the top level
> autom4te: /usr/bin/m4 failed with exit status: 1
> aclocal: error: echo failed with exit status: 1
> autoreconf: aclocal failed with exit status: 1
> dh_autoreconf: autoreconf -f -i returned exit code 1
> debian/rules:22: recipe for target 'build' failed
> make: *** [build] Error 2

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: pkg-config
Source-Version: 0.29-4

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

Debian distribution maintenance software
pp.
Tollef Fog Heen  (supplier of updated pkg-config 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, 01 May 2016 08:26:59 +0200
Source: pkg-config
Binary: pkg-config
Architecture: source amd64
Version: 0.29-4
Distribution: unstable
Urgency: medium
Maintainer: Tollef Fog Heen 
Changed-By: Tollef Fog Heen 
Description:
 pkg-config - manage compile and link flags for libraries
Closes: 809221 822409
Changes:
 pkg-config (0.29-4) unstable; urgency=medium
 .
   * Update glib/m4macros/glib-gettext.m4 from newer upstream version to
 avoid m4 redefinition/overwrite.  Closes: #822409
   * Add Conflicts and Replaces on pkg-config-bin. This was a suggested
 change earlier which some users have picked up, even if it never made
 it into Debian.  Closes: #809221
Checksums-Sha1:
 df2fdbfa1829f6f54b93c6efedd8429fae8864d7 1718 pkg-config_0.29-4.dsc
 fbe8a7c6738f151ee09a3e8eb62acbf6f73f85e3 7560 pkg-config_0.29-4.diff.gz
 5be4a1b4ae5821b8f35c342e2e4858565264e4fc 38632 
pkg-config-dbgsym_0.29-4_amd64.deb
 6c87c8ddba02e630c83450d46535228b4ce89f42 62472 pkg-config_0.29-4_amd64.deb
Checksums-Sha256:
 6a00ca4f4813c9d531b7f99072e1b6b443a8eea045c97e7d2b9d34f9a960deb5 1718 
pkg-config_0.29-4.dsc
 0c1253e3755942d3bf407d5c6465568e97ee960c8d9829c53cbae8ff26dc3762 7560 
pkg-config_0.29-4.diff.gz
 0d417a1761c5ec2334d3f1f5ec449da07260231f00e97b85c50a14342133eb93 38632 
pkg-config-dbgsym_0.29-4_amd64.deb
 ca3e1d050bcc789a4f9854e4568184d4caeaba27505890f37b68e08cdb753364 62472 
pkg-config_0.29-4_amd64.deb
Files:
 9701931d34b79f941ee35c67d567a7bc 1718 devel optional pkg-config_0.29-4.dsc
 9b9e2f7a9e7df78294b45780c52fdce1 7560 devel optional pkg-config_0.29-4.diff.gz
 200ebd111c928d41718b2fbfa4b512c3 38632 debug extra 
pkg-config-dbgsym_0.29-4_amd64.deb
 d8f16a9765990635dac8e150ecb1728e 62472 devel optional 
pkg-config_0.29-4_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXJaTpAAoJELZaSHHKGdcXm4YP/3SmfPcLu94i62+8ElzEE31K
tiw0QQg3oKk9SevB1x0EM8pLWZM3IzzGRALUGy0ND4pbVpi7ZzeQxBAd4rC8x4fy
nnpcg2YiGYONOf7phQC143mei9CDr6ylSY9RgWigtUvuR0yZDR5Nr9uohOwvdrhA
h4lTi86XAR/rpE9wTCbTXVJEKc3Wg3bvtShxWZA/vbNnDUNF/tdaIudSeHKmmAFK
vfJRHJzQ3jPP1QemoNtcUjsmSCod70mpAB0krDSGfCAWtCSAThskLYt31Kckgcyo
q/J1JXI1zvosay94uhD/PefeWdt1PpvUykjJsfLqGAyKQKSrAcozWfr8kngB4yF9
EokTa/GUUbPG/97F61XadmrkK15S/jdNYqi0cfu4qfV6dT20qJsuy3lP79qCf2BM
t4cCF8QfJMD42UC5FZBWRZdYzi1rIrgoxjBPlmKmZXs8WkYNBCOe8Hyv4zE/6H/9
+W5ZXxx97iJQqNswUeMPQUJiH7rqd+/SwIZlTIUrbbMX17hspH74PvlHxq7W4Hbx
uxSMeV+FslsUljhPBGNzVuQPjHXIeL5deA9Sac4Q/p58wA0F3mGcwKg/8mt0ggAh

Bug#815319: After update dhcpd server don't start

[Adrian Immanuel Kiess]

Package: isc-dhcp-server
Version: 4.3.4-1
Followup-For: Bug #815319

Dear Maintainer,

   * What led up to the situation?
 Upgrading isc-dhcp-server
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 apt -u dist-upgrade
   * What was the outcome of this action?
 dhcpd won't be started after boot process or using service isc-dhcp-server
restart
   * What outcome did you expect instead?
 Running dhcpd service

I can confirm this bug.

After upgrading isc-dhcp-server it won't be executed after boot process or
using $ service isc-dhcp-server restart.

The solution to make it work again, I found from another bug report, is the
following:

In /etc/default/isc-dhcp-server

Change

INTERFACES=""

to

INTERFACESv4="eth0 virbr0"

Now $ service isc-dhcp-server restart works again.

But I guess this is just a workaround and thus it is not possible to let dhcpd
listen automatically to all interfaces by leaving INTERFACES variable with "".

Thank you very much for your time and reading this!

With many greetings,

Adrian Immanuel Kieß
http://www.immanuelK.net



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

Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages isc-dhcp-server depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  debianutils4.7
ii  libc6  2.22-7
ii  libdns-export162   1:9.10.3.dfsg.P4-8
ii  libirs-export141   1:9.10.3.dfsg.P4-8
ii  libisc-export160   1:9.10.3.dfsg.P4-8
ii  lsb-base   9.20160110

Versions of packages isc-dhcp-server recommends:
ii  isc-dhcp-common  4.3.4-1
ii  policycoreutils  2.4-4

Versions of packages isc-dhcp-server suggests:
pn  isc-dhcp-server-ldap  

-- Configuration Files:
/etc/dhcp/dhcpd.conf changed:
allow booting;
allow bootp;
authoritative;
option domain-name-servers 192.168.0.3;
option domain-name "lan.dac";
option routers 192.168.0.2;
option subnet-mask 255.255.0.0;
option broadcast-address 192.168.255.255;
option ntp-servers 192.168.0.3;  
option time-servers 192.168.0.3;
option www-server 192.168.0.3;
option x-display-manager 192.168.0.3;
default-lease-time 6000;
max-lease-time 72000;
server-name "g6.lan.dac";
option wpad code 252 = text;
option wpad "http://wpad.lan.dac/proxy.pac\n;;
subnet 192.168.0.0 netmask 255.255.0.0 {
  range 192.168.0.20 192.168.0.30;
 #class "pxeclients" {
 #  match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
 #  option vendor-class-identifier "PXEClient";
 #  vendor-option-space PXE;
 #  option PXE.mtftp-ip 0.0.0.0;
 #  filename "pxeboot_ia32.bin";
 #  next-server 192.168.0.3;
 #  }
}
  #hardware ethernet 00:0E:0C:2C:7B:8A;
  #hardware ethernet 00:02:B3:9C:31:5C;
host g6 {
  hardware ethernet 64:31:50:d3:c0:f8;
  fixed-address 192.168.0.3;
  option host-name "g6";
  next-server 192.168.0.3;
  always-reply-rfc1048 true;
}
host tdz2000 {
  #hardware ethernet 00:90:27:6f:43:2b; 
  #hardware ethernet 00:02:b3:9c:31:5c; 
  #hardware ethernet 00:0E:0C:2C:7B:8A;
  hardware ethernet 00:0E:0C:2C:75:10;
  fixed-address 192.168.0.2;
  option host-name "tdz2000";
  #server-name "g6.lan.dac";
  next-server 192.168.0.3;
  filename "pxeboot_ia32.bin";
  #always-reply-rfc1048 true;
  option root-path "/client/tdz2000/root";

}
host m2n {
  hardware ethernet 00:0C:6E:81:35:E8;
  fixed-address 192.168.0.7;
  option host-name "m2n";
  #filename "pxelinux.0";
  next-server 192.168.0.3;
}


-- debconf information:
  isc-dhcp-server/interfaces:
  isc-dhcp-server/config_warn: