Bug#807800: heimdall-flash: heimdall fails on files larger than 2GB

[Tomka Gergely]

Package: heimdall-flash
Version: 1.4.1-1
Severity: grave
Tags: lfs
Justification: renders package unusable

Dear Maintainer,

I was running heimdall for a Note 4, and got this:

open("system.img", O_RDONLY)= -1 EOVERFLOW (Value too large for 
defined data type)
write(2, "ERROR: ", 7ERROR: )  = 7
write(2, "Failed to open file \"system.img\""..., 33Failed to open file 
"system.img"

This was the command:

heimdall flash --BOOTLOADER sboot.bin --BOOT boot.img --RADIO modem.bin 
--RECOVERY recovery.img --HIDDEN hidden.img --SYSTEM system.img --CACHE 
cache.img

And here are the files:

-rw-rw-r-- 1 tudor tudor  62M márc  12  2015 modem.bin
-rw-rw-r-- 1 tudor tudor 1,6M márc  13  2015 sboot.bin
-rw-rw-r-- 1 tudor tudor  11M márc  13  2015 boot.img
-rw-rw-r-- 1 tudor tudor  12M márc  13  2015 recovery.img
-rw-rw-r-- 1 tudor tudor 3,1G márc  13  2015 system.img ==> Ooops!
-rw-r--r-- 1 tudor tudor  27M márc  18  2015 hidden.img
-rw-r--r-- 1 tudor tudor  42M márc  18  2015 cache.img

Regards,

tg

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

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

Versions of packages heimdall-flash depends on:
ii  libc6 2.21-4
ii  libgcc1   1:5.3.1-3
ii  libstdc++65.3.1-3
ii  libusb-1.0-0  2:1.0.20-1

heimdall-flash recommends no packages.

heimdall-flash suggests no packages.

-- no debconf information

Bug#807673: 807673 patch

[Dave Schaefer]

Hi, thanks for the bug report. I have a potential patch in development -
https://github.com/daveschaefer/Perspectives/commit/031d27659f5896d518eef20ba30e42761b2605eb

I'm having trouble reproducing this break on my current machine, but as
soon as I can get to a full dev environment I will reproduce, test the
patch, and push the patch through. If anyone wants to test the patch in the
meantime feel free to let me know how it goes.

Bug#807795: childsplay: non-free font: arial.ttf

[Dmitry Smirnov]

Source: childsplay
Version: 2.6.5-1
Severity: serious

File "lib/SPData/base/arial.ttf" is non-free:

"This software is a valuable asset of Monotype. Unless you have entered
into a specific license agreement granting you additional rights, your
use of this software is limited to your workstation for your own
publishing use. You may not copy or distribute this software."

-- 
All the best,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B

---

The belief in a supernatural source of evil is not necessary; men alone
are quite capable of every wickedness.
-- Joseph Conrad


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

Bug#807734: bobcat: FTBFS: Error: double quote at end of string not found

[Chris Lamb]

Source: bobcat
Version: 4.01.03-2
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,

bobcat fails to build from source in unstable/amd64:

  [..]

   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: source package bobcat
  dpkg-buildpackage: source version 4.01.03-2
  dpkg-buildpackage: source distribution unstable
  dpkg-buildpackage: source changed by tony mancill 
   dpkg-source --before-build bobcat-4.01.03
  dpkg-buildpackage: host architecture amd64
   fakeroot debian/rules clean
  dh_testdir
  dh_testroot
  rm -f build-stamp
  ./build clean
  [./build, line 38] Error: double quote at end of string not found
  [./build, line 38] Error: Syntax error at `#include'
  debian/rules:34: recipe for target 'clean' failed
  make: *** [clean] Error 1

  [..]

The full build log is attached.


Regards,

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


bobcat.4.01.03-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#730908: marked as done (libio-event-perl: FTBFS: Failed tests)

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2015 10:22:48 +
with message-id 
and subject line Bug#730908: fixed in libio-event-perl 0.813-2
has caused the Debian Bug report #730908,
regarding libio-event-perl: FTBFS: Failed tests
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.)


-- 
730908: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libio-event-perl
Version: 0.813-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131128 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»'
> PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" 
> "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
> t/callbacks1.t .. ok
> t/callbacks2.t .. ok
> t/callbacks3.t .. ok
> t/forked1.t . ok
> # Looks like you planned 115 tests but ran 111.
> print 26175: Connection reset by peer
> Compilation failed in require at t/forked2.t line 5.
> t/forked2.t . 
> Dubious, test returned 255 (wstat 65280, 0xff00)
> Failed 4/115 subtests 
> t/forked3.t . ok
> t/getline1.t  ok
> t/getline2.t  ok
> t/getline3.t  ok
> t/multifork1.t .. ok
> t/multifork2.t .. ok
> t/multifork3.t .. ok
> 
> Test Summary Report
> ---
> t/forked2.t   (Wstat: 65280 Tests: 111 Failed: 0)
>   Non-zero exit status: 255
>   Parse errors: Bad plan.  You planned 115 tests but ran 111.
> Files=12, Tests=920, 129 wallclock secs ( 0.23 usr  0.09 sys +  1.82 cusr  
> 0.58 csys =  2.72 CPU)
> Result: FAIL
> Failed 1/12 test programs. 0/920 subtests failed.
> make[1]: *** [test_dynamic] Error 255
> make[1]: Leaving directory `/«PKGBUILDDIR»'
> dh_auto_test: make -j1 test returned exit code 2

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/11/28/libio-event-perl_0.813-1_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Niko Tyni  (supplier of updated libio-event-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 12 Dec 2015 11:52:34 +0200
Source: libio-event-perl
Binary: libio-event-perl
Architecture: source
Version: 0.813-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Niko Tyni 
Description:
 libio-event-perl - Perl module that ties filehandles for nonblocking IO with 
object
Closes: 730908
Changes:
 libio-event-perl (0.813-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-Browser URL to cgit web frontend
 .
   [ Niko Tyni ]
   * Patch the test suite to fix undeterministic test failures in t/forked2.t.
 (Closes: #730908)
   * Declare the package autopkgtestable.
Checksums-Sha1:
 adf2e01c07ab64d18e5083b8bbabbc9bc08303a1 2113 libio-event-perl_0.813-2.dsc
 2f29bfc32a3a17a13aae641232fa7e660c592316 2560 
libio-event-perl_0.813-2.debian.tar.xz
Checksums-Sha256:
 de86b332812882ebacf5294ba260a1ea1c12d12a4facb29eaf57959d5632b2fa 2113 
libio-event-perl_0.813-2.dsc
 d348bcbb714e89292f7f3834ccc42934cbb75be0f2bbc514b1d771e98284363b 2560 
libio-event-perl_0.813-2.debian.tar.xz
Files:
 88509bab23cfefa0f8dacd125a1cfa72 2113 perl optional 
libio-event-perl_0.813-2.dsc
 67b2f40dfd6301ca3638a3a04bc18e56 2560 perl optional 
libio-event-perl_0.813-2.debian.tar.xz

Bug#807745: command-not-found: Does not work with apt-file 3.0

[Julian Andres Klode]

Package: command-not-found
Version: 0.2.38-1.1
Severity: grave
Tag: experimental

update-command-not-found directly uses the apt-file
cache which no longer exists with apt-file 3.0.

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

Kernel: Linux 4.3.0-trunk-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 /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages command-not-found depends on:
ii  apt-file 3.0~exp
ii  lsb-release  9.20150917
ii  python   2.7.11-1
ii  python-gdbm  2.7.11-2
pn  python:any   

command-not-found recommends no packages.

command-not-found suggests no packages.

-- no debconf information

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

Bug#807728: marked as done (Could not create directory: /home/jff/.cache)

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2015 13:10:20 +
with message-id <20151212131020.ga26...@chase.mapreri.org>
and subject line Re: Bug#807728: Could not create directory: /home/jff/.cache
has caused the Debian Bug report #807728,
regarding Could not create directory: /home/jff/.cache
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

since the last update I get allways:

[...]
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
E: Could not create directory: /home/jff/.cache:
boost::filesystem::create_directory: No such file or directory:
"/home/jff/.cache"
E: pbuilder-satisfydepends failed.
[...]

The directory /home/jff/.cache exists:

ls -al
insgesamt 38248
drwxr-xr-x 71 jff  jff   4096 Dez 12 07:30 .
drwxr-xr-x  4 root root  4096 Okt  9  2014 ..
[...]
- -rw-r--r--  1 jff  jff  39261 Jan 26  2015 .bzr.log
drwx-- 55 jff  jff   4096 Dez 12 07:19 .cache
drwx-- 10 jff  jff   4096 Jul 26 20:16 .claws-mail
drwx-- 53 jff  jff   4096 Dez  8 06:14 .config
drwx--  2 jff  jff   4096 Jul 19 13:01 .cups
drwx--  3 jff  jff   4096 Okt  9  2014 .dbus






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

Kernel: Linux 4.2.0-1-amd64 (SMP w/6 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 pbuilder depends on:
ii  debconf [debconf-2.0]  1.5.58
ii  debootstrap1.0.75
ii  dpkg-dev   1.18.3
ii  wget   1.17-1

Versions of packages pbuilder recommends:
ii  devscripts  2.15.9
ii  fakeroot1.20.2-1
ii  iproute24.3.0-1
ii  net-tools   1.60+git20150829.73cef8a-2
ii  sudo1.8.12-1

Versions of packages pbuilder suggests:
ii  cowdancer 0.75
ii  gdebi-core0.9.5.7
pn  pbuilder-uml  

- -- debconf information:
  pbuilder/rewrite: false
  pbuilder/mirrorsite: http://mirror.1und1.de/debian/
  pbuilder/nomirror:

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWa8JzAAoJEAn4nzyModJdKJcQAIg7rf7JdR+OIldpLDOkBigN
GzRmai0waB3Wbvsl4H5dekxBNjAfW5UV6gS+ujX3c3uwgvXf29YS8BBn9V5a0gb/
r39txzdkJNXHA1UwNviH8N7MllsUoN+YAZ9/oOLak7uKYxggUYwncxBDWkZhJTGL
y2pamYf+ywbZ5bcqv/FuMP4hQq8ARO9DWxp0ehhjYXy+PX5rYu7OhOFJg3xKUch+
YECMo6Icf5qvcQieYO0M3QluU63NThBspYlKLo4349/MXvK3lh7MadRFSOFzgYh8
w8pcEQaL0Nsyg+P7Vk5QmtjhE1plR9tUzQP+q2WBYW7V4A/7PRqoKLgh+HOLAVrx
qDJU/MQ2rcNR07DgsSGdoU4KS+KfRNxWsiHAYkd3phGotLW8NUyw5dymcX2kujBv
df5B8nh82Ctcl+u7ShlZkHW0mBAi3XccpvXFMQ+mLP9vix/vFIKtXmIkOiUP5Zx9
WMRyEDLRZogQPNycKQ2X2XrkzZ/ZgiM6eAviGb+hJoRwOGSsvoKAA8xxadj362pi
zK2PRHxbhU39fpeeVqjBvL2ESQKDGyqGq6Z6pTF+4tfk1ptPJ5XGwzQZe6NW3lYA
VSk2h9+GQCY5TJAJHktWw2KEYlzNHHGUhjLYdXG4fZc/Hgg7vw64c6Z6l9rkLI2q
7SeBLo9n03DwK2LpqFSS
=1R+Y
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 0.221.3

On Sat, Dec 12, 2015 at 07:45:07AM +0100, Jörg Frings-Fürst wrote:
> since the last update I get allways:
> 
> [...]
> Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Initializing package states...
> Writing extended state information...
> Building tag database...
> E: Could not create directory: /home/jff/.cache:
> boost::filesystem::create_directory: No such file or directory:
> "/home/jff/.cache"
> E: pbuilder-satisfydepends failed.
> [...]

This is due to yet another change in aptitude, but the kinda of
workaround I did in 0.221.3 should be sufficient for this too.

> The directory /home/jff/.cache exists:
> 
> ls -al
> insgesamt 38248
> drwxr-xr-x 71 jff  jff   4096 Dez 12 07:30 .
> drwxr-xr-x  4 root root  4096 Okt  9  2014 ..
> [...]
> - -rw-r--r--  1 jff  jff  39261 Jan 26  2015 .bzr.log
> drwx-- 55 jff  jff   4096 Dez 12 07:19 .cache
> drwx-- 10 jff  jff   4096 Jul 26 20:16 .claws-mail
> drwx-- 53 jff  jff   4096 Dez  8 06:14 .config
> drwx--  2 jff  jff   4096 Jul 19 13:01 .cups
> drwx--  

Bug#807756: gnubg: fails to start. hangs using 100% of one cpu core

[Julian Hughes]

Package: gnubg
Version: 1.05.000-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

when starting gnubg it uses 100% of one cpu core and then apparently
hangs with no output and without starting the gui.

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

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

Versions of packages gnubg depends on:
ii  debconf [debconf-2.0] 1.5.58
ii  gnubg-data1.05.000-2
ii  libc6 2.19-22
ii  libcairo2 1.14.4-1
ii  libcanberra-gtk0  0.30-2.1
ii  libcanberra0  0.30-2.1
ii  libcurl3  7.45.0-1+b1
ii  libfreetype-infinality6   2.4.9-3
ii  libgdk-pixbuf2.0-02.32.2-1
ii  libgl1-mesa-glx [libgl1]  11.0.6-1
ii  libglib2.0-0  2.46.2-1
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgmp10  2:6.1.0+dfsg-2
ii  libgtk2.0-0   2.24.28-1
ii  libgtkglext1  1.2.0-3.2
ii  libpango-1.0-01.38.1-1
ii  libpangocairo-1.0-0   1.38.1-1
ii  libpng12-01.2.54-1
ii  libpython2.7  2.7.10-5+b1
ii  libreadline6  6.3-8+b4
ii  libsqlite3-0  3.9.2-1

gnubg recommends no packages.

Versions of packages gnubg suggests:
pn  kbackgammon  

-- debconf information:
  gnubg/build-bearoffs: false

Bug#807730: incorrect bsd/unistd.h header

[Guillem Jover]

Hi!

On Sat, 2015-12-12 at 08:55:33 +0100, Vincent Bernat wrote:
> Package: libbsd-dev
> Version: 0.8.0-2
> Severity: grave

> After a recent update of libbsd, programs using it now fail at compile
> time with:
> 
> /usr/include/bsd/unistd.h: In function 'setproctitle':
> /usr/include/bsd/unistd.h:64:2: error: expected declaration specifiers before 
> '__printflike'
>   __printflike(1, 2);
>   ^

Indeed! :(

> It seems there is a missing backslash at the end of the previous line.

This is due to the overlays, some headers now expect declarations from
the overlayed headers, bu they are not requsting them and just use the
system ones. I've added a unit test to catch this in the future, and
will be fixing it for an upload targetted for later today.

Thanks,
Guillem

Bug#730908: libio-event-perl: FTBFS: Failed tests

[Niko Tyni]

Control: tag -1 patch

On Sat, Nov 30, 2013 at 09:17:11PM +0100, gregor herrmann wrote:
> On Sat, 30 Nov 2013 17:33:15 +0100, David Suárez wrote:
> 
> > > t/forked1.t . ok
> > > # Looks like you planned 115 tests but ran 111.
> > > print 26175: Connection reset by peer
> > > Compilation failed in require at t/forked2.t line 5.
> > > t/forked2.t . 
> > > Dubious, test returned 255 (wstat 65280, 0xff00)
> > > Failed 4/115 subtests 
> 
> Now that's an intereting bug.
> The tests still pass for me but take quite some long. So maybe we're
> running into a timeout here, or some other fork problem on the amazon
> build machine ...

What happens here is that

- the test script forks, the parent sets up a TCP server and starts an
  event loop for clients
- child connects there, sends test data and synchronizes on event
  indications from the parent
- for every test data group, client disconnects when it has sent
  all the data and then makes a new connection for the next group
- when the parent gets a new connection, it decrements its counter
  of tests left (in ie_connection())
- when the parent gets an EOF from a client connection, it exits
  if the test counter is zero (in ie_eof())

Now, it can happen that the client disconnect and the next connect both
happen before the parent gets CPU time. In this case, the parent may get
the 'new connection' event before the 'eof' event. This wouldn't matter
otherwise, but if it's the last test group starting, ie_connection()
decrements the counter to zero first, and ie_eof() thinks it's all done
even though a new connection has just been accepted.

The parent then does an exit(0) in ie_eof(), the child gets a connection
reset, and an END block in the test libraries notices that there were
too few tests and dies.

The attached patch should fix it by making the client synchronize on the
eof event from the parent before making a new connection. Will send
it properly upstream once rt.cpan.org is up again.
-- 
Niko Tyni   nt...@debian.org
>From e11dc91080151bb59d73e72c3c0a3409c1b999ef Mon Sep 17 00:00:00 2001
From: Niko Tyni 
Date: Sat, 12 Dec 2015 11:33:34 +0200
Subject: [PATCH] Fix undeterministic test failures in t/forked2.t

The parent process may get both the eof event from an old connection
and the connect event from a new connection at the same time, and in an
unpredictable order. If the connect event comes first, the handler may
decrement the test counter to zero and make the eof handler think the
testing is already over.

Having the child synchronize on the eof event before making a new
connection fixes this race.

Bug-Debian: https://bugs.debian.org/730908
Bug: https://rt.cpan.org/Ticket/Display.html?id=92200
---
 t/forked.tt | 1 +
 1 file changed, 1 insertion(+)

diff --git a/t/forked.tt b/t/forked.tt
index e56c7fa..0d9ce18 100755
--- a/t/forked.tt
+++ b/t/forked.tt
@@ -265,6 +265,7 @@ if ($child = fork()) {
 		}
 		print "# CHILD closing\n";
 		close($s);
+		syncto("e");
 	}
 } else {
 	die "fork: $!";
-- 
2.6.2

Processed: Re: Bug#730908: libio-event-perl: FTBFS: Failed tests

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #730908 [src:libio-event-perl] libio-event-perl: FTBFS: Failed tests
Added tag(s) patch.

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

Bug#807746: guncat: FTBFS: "CXX multiply defined"

[Chris Lamb]

Source: guncat
Version: 0.92.00-5
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,

guncat fails to build from source in unstable/amd64:

  [..]

   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: source package guncat
  dpkg-buildpackage: source version 0.92.00-5
  dpkg-buildpackage: source distribution unstable
  dpkg-buildpackage: source changed by tony mancill 
   dpkg-source --before-build guncat-0.92.00
  dpkg-buildpackage: host architecture amd64
   fakeroot debian/rules clean
  dh_testdir
  dh_testroot
  rm -f build-stamp configure-stamp
  # Add here commands to clean up after the build process.
  ./build clean
  [icmconf, line 21] Error: CXX multiply defined
  [icmconf, line 30] Error: LDFLAGS multiply defined
  debian/rules:49: recipe for target 'clean' failed
  make: *** [clean] Error 1

  [..]

The full build log is attached.


Regards,

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


guncat.0.92.00-5.unstable.amd64.log.txt.gz
Description: Binary data

Bug#807747: meep-mpich2: FTBFS: debian/rules:29: recipe for target 'override_dh_auto_configure' failed

[Chris Lamb]

Source: meep-mpich2
Version: 1.3-2
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,

meep-mpich2 fails to build from source in unstable/amd64:

  [..]

  host='x86_64-linux-gnu'
  host_alias='x86_64-linux-gnu'
  host_cpu=''
  host_os=''
  host_vendor=''
  htmldir='${docdir}'
  includedir='${prefix}/include'
  infodir='${prefix}/share/info'
  install_sh='${SHELL} 
/home/lamby/temp/cdt.20151212125120.3RgWNIsu0S/meep-mpich2-1.3/install-sh'
  libdir='${prefix}/lib/x86_64-linux-gnu'
  libexecdir='${prefix}/lib/x86_64-linux-gnu'
  localedir='${datarootdir}/locale'
  localstatedir='/var'
  mandir='${prefix}/share/man'
  mkdir_p='$(MKDIR_P)'
  oldincludedir='/usr/include'
  pdfdir='${docdir}'
  prefix='/usr'
  program_transform_name='s,x,x,'
  psdir='${docdir}'
  runstatedir='${localstatedir}/run'
  sbindir='${exec_prefix}/sbin'
  sharedstatedir='${prefix}/com'
  sysconfdir='/etc'
  target_alias=''
  
  ## --- ##
  ## confdefs.h. ##
  ## --- ##
  
  /* confdefs.h */
  #define PACKAGE_NAME "meep-mpich2"
  #define PACKAGE_TARNAME "meep"
  #define PACKAGE_VERSION "1.3"
  #define PACKAGE_STRING "meep 1.3"
  #define PACKAGE_BUGREPORT "m...@ab-initio.mit.edu"
  #define PACKAGE_URL ""
  #define PACKAGE "meep-mpich2"
  #define VERSION "1.3"
  
  configure: exit 1
  dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=${prefix}/include --mandir=${prefix}/share/man 
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu 
--libexecdir=${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --host=x86_64-linux-gnu --build=x86_64-linux-gnu 
--prefix=/usr --mandir=${prefix}/share/man --infodir=${prefix}/share/info 
--with-libctl=/usr/share/libctl3 --with-gcc-arch=no --enable-shared --with-pic 
--enable-cxx --with-mpi=yes returned exit code 1
  debian/rules:29: recipe for target 'override_dh_auto_configure' failed
  make[1]: *** [override_dh_auto_configure] Error 255
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151212125120.3RgWNIsu0S/meep-mpich2-1.3'
  debian/rules:26: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


meep-mpich2.1.3-2.unstable.amd64.log.txt.gz
Description: Binary data

Processed: tagging 807745

[Debian Bug Tracking System]

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

> tags 807745 + experimental
Bug #807745 [command-not-found] command-not-found: Does not work with apt-file 
3.0
Added tag(s) experimental.
> thanks
Stopping processing here.

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

Bug#807734: bobcat: FTBFS: Error: double quote at end of string not found

[Frank B. Brokken]

Dear Chris Lamb, you wrote:

> bobcat fails to build from source in unstable/amd64:

>   ./build clean
>   [./build, line 38] Error: double quote at end of string not found
>   [./build, line 38] Error: Syntax error at `#include'
>   debian/rules:34: recipe for target 'clean' failed

Thanks! That's a plain old typo. But an update also including the required
changes for the icmake 8.00.04 upgrade is being prepared right now.

-- 
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281 
Public PGP key: http://pgp.surfnet.nl
Key Fingerprint: DF32 13DE B156 7732 E65E  3B4D 7DB2 A8BE EAE4 D8AA

Bug#807733: antlr3: FTBFS: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode

[Chris Lamb]

Source: antlr3
Version: 3.5.2-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,

antlr3 fails to build from source in unstable/amd64:

  [..]

  cd antlr3-maven-plugin && cd . && /usr/lib/jvm/default-java/bin/java 
-noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 
-Dproperties.file.manual=/home/lamby/temp/cdt.20151212101545.Zh9YPF8EtD/antlr3-3.5.2/debian/maven.properties
 -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/lamby/temp/cdt.20151212101545.Zh9YPF8EtD/antlr3-3.5.2
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Dmaven.repo.local=/home/lamby/temp/cdt.20151212101545.Zh9YPF8EtD/antlr3-3.5.2/debian/maven-repo
 -DbuildNumber="debian-3" 
-Ddebian.dir=/home/lamby/temp/cdt.20151212101545.Zh9YPF8EtD/antlr3-3.5.2/debian 
-Ddebian.package=antlr3 
-Dmaven.repo.local=/home/lamby/temp/cdt.20151212101545.Zh9YPF8EtD/antlr3-3.5.2/debian/maven-repo
 -Dinstall.to.usj=false -Dmaven.test.skip=true -Duse.maven.repo.local=true 
package install org.debian.maven:debian-maven-plugin:2.0:install
  [INFO] Scanning for projects...
  [INFO]
 
  [INFO] 

  [INFO] Building ANTLR 3 Maven plugin 3.5.2
  [INFO] 

  [WARNING] The POM for org.codehaus.plexus:plexus-compiler-api:jar:debian is 
missing, no dependency information available
  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

  [INFO] Total time: 0.818 s
  [INFO] Finished at: 2015-12-12T10:20:09+02:00
  [INFO] Final Memory: 8M/236M
  [INFO] 

  [ERROR] Failed to execute goal on project antlr3-maven-plugin: Could not 
resolve dependencies for project 
org.antlr:antlr3-maven-plugin:maven-plugin:3.5.2: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.codehaus.plexus:plexus-compiler-api:jar:debian has not been downloaded from 
it before. -> [Help 1]
  [ERROR] 
  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
  [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  [ERROR] 
  [ERROR] For more information about the errors and possible solutions, please 
read the following articles:
  [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
  debian/rules:21: recipe for target 'before-mvn-build' failed
  make: *** [before-mvn-build] Error 1

  [..]

The full build log is attached.


Regards,

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


antlr3.3.5.2-3.unstable.amd64.log.txt.gz
Description: Binary data

Bug#807737: sqwebmail-de: FTBFS: debian/rules:14: recipe for target 'override_dh_auto_build' failed

[Chris Lamb]

Source: sqwebmail-de
Version: 5.5.1-2
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,

sqwebmail-de fails to build from source in unstable/amd64:

  [..]

  patching file abooklist.html
  patching file acl.html
  patching file attachments.html
  patching file autoresponder.html
  patching file calendarlogin.inc.html
  patching file empty.html
  patching file eventacl.html
  patching file eventdaily.html
  patching file eventdelete.html
  patching file eventmonthly.html
  patching file eventnotifydelete.txt
  patching file eventnotifynew.txt
  patching file eventnotifysubject.txt
  patching file eventshow.html
  patching file eventweekly.html
  patching file expired.html
  patching file filter.html
  patching file folder.html
  patching file folders.html
  patching file gpg.html
  patching file gpgcreate.html
  patching file gpgerr.html
  patching file index.html
  patching file invalid.html
  patching file keyimport.html
  patching file ldaplist.html
  patching file ldapsearch.html
  patching file login.html
  patching file loginform.inc.html
  patching file navbar.inc.html
  patching file navbar2.inc.html
  patching file navbar3.inc.html
  patching file newevent.html
  patching file newmsg.html
  patching file preferences.html
  patching file print.html
  patching file printnocookie.html
  patching file printredirect.html
  patching file quickadd.html
  patching file readmsg.html
  patching file redirect.html
  patching file spellchk.html
  debian/rules:14: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151212101648.Xqd70LIgHI/sqwebmail-de-5.5.1'
  debian/rules:11: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


sqwebmail-de.5.5.1-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#807738: ttt: FTBFS: net_names.c:529:1: error: conflicting types for 'inet6_ntoa'

[Chris Lamb]

Source: ttt
Version: 1.7-3.5
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,

ttt fails to build from source in unstable/amd64:

  [..]

  In file included from /usr/include/stdlib.h:314:0,
   from net_names.c:18:
  /usr/include/x86_64-linux-gnu/sys/types.h:202:1: note: previous declaration 
of 'u_int32_t' was here
   __u_intN_t (32, __SI__);
   ^
  net_names.c:529:1: error: conflicting types for 'inet6_ntoa'
   inet6_ntoa(u_int32_t *addr)
   ^
  net_names.c:161:14: note: previous declaration of 'inet6_ntoa' was here
   static char *inet6_ntoa(uint32_t *addr);  /* should be replaced
^
  net_names.c:161:14: warning: 'inet6_ntoa' used but never defined
  Makefile:87: recipe for target 'net_names.o' failed
  make[1]: *** [net_names.o] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151212101456.mbD2Ik1Vew/ttt-1.7'
  debian/rules:44: recipe for target 'build-arch-stamp' failed
  make: *** [build-arch-stamp] Error 2

  [..]

The full build log is attached.


Regards,

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


ttt.1.7-3.5.unstable.amd64.log.txt.gz
Description: Binary data

Bug#807735: gmpc-plugins: FTBFS: libmpd-internal.h:210:10: error: expected identifier or '(' before '__extension__'

[Chris Lamb]

Source: gmpc-plugins
Version: 11.8.16-2
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,

gmpc-plugins fails to build from source in unstable/amd64:

  [..]

  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -pthread 
-I/usr/include/gmpc -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 
-I/usr/include/libxml2 -I/usr/include/libmpd-1.0/ -I./ 
-DDATA_DIR=\"/usr/share/gmpc/plugins/jamendo/\" -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -c jamendo.c  -fPIC -DPIC -o 
.libs/jamendoplugin_la-jamendo.o
  In file included from /usr/include/string.h:634:0,
   from jamendo.c:21:
  /usr/include/libmpd-1.0/libmpd/libmpd-internal.h:210:10: error: expected 
identifier or '(' before '__extension__'
   char *   strndup (const char *s, size_t n);
^
  jamendo.c: In function 'jamendo_db_load_data':
  jamendo.c:326:46: warning: pointer type mismatch in conditional expression
   (image != NULL)?image:""); 
^
  Makefile:479: recipe for target 'jamendoplugin_la-jamendo.lo' failed
  make[4]: *** [jamendoplugin_la-jamendo.lo] Error 1
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20151212101533.VCTTVWszV2/gmpc-plugins-11.8.16/gmpc-jamendo/src'
  Makefile:428: recipe for target 'all-recursive' failed
  make[3]: *** [all-recursive] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20151212101533.VCTTVWszV2/gmpc-plugins-11.8.16/gmpc-jamendo'
  Makefile:360: recipe for target 'all' failed
  make[2]: *** [all] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20151212101533.VCTTVWszV2/gmpc-plugins-11.8.16/gmpc-jamendo'
  Makefile:416: recipe for target 'all-recursive' failed
  make[1]: *** [all-recursive] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151212101533.VCTTVWszV2/gmpc-plugins-11.8.16'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:9: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


gmpc-plugins.11.8.16-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#807736: gparted: FTBFS: Win_GParted.h:28:31: fatal error: sigc++/class_slot.h: No such file or directory

[Chris Lamb]

Source: gparted
Version: 0.19.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,

gparted fails to build from source in unstable/amd64:

  [..]

  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -pthread 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -std=c++11 
-pthread -I/usr/include/gtkmm-2.4 -I/usr/lib/x86_64-linux-gnu/gtkmm-2.4/include 
-I/usr/include/atkmm-1.6 -I/usr/include/gtk-unix-print-2.0 
-I/usr/include/gtk-2.0 -I/usr/include/gdkmm-2.4 
-I/usr/lib/x86_64-linux-gnu/gdkmm-2.4/include -I/usr/include/giomm-2.4 
-I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/pangomm-1.4 
-I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include -I/usr/include/glibmm-2.4 
-I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/cairomm-1.0 
-I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/sigc++-2.0 
-I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 
-DGPARTED_DATADIR=\""/usr/share"\" -DGNOME_ICONDIR=\""/usr/share/pixmaps"\" 
-DGNOMELOCALEDIR=\""/usr/share/locale"\"  -D_FORTIFY_SOURCE=2 -Wall -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security -MT 
GParted_Core.o -MD -MP -MF .deps/GParted_Core.Tpo -c -o GParted_Core.o 
GParted_Core.cc
  In file included from GParted_Core.cc:18:0:
  ../include/Win_GParted.h:28:31: fatal error: sigc++/class_slot.h: No such 
file or directory
  compilation terminated.
  Makefile:479: recipe for target 'GParted_Core.o' failed
  make[3]: *** [GParted_Core.o] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20151212101705.AM2zXKViRt/gparted-0.19.0/src'
  Makefile:484: recipe for target 'all-recursive' failed
  make[2]: *** [all-recursive] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20151212101705.AM2zXKViRt/gparted-0.19.0'
  Makefile:347: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151212101705.AM2zXKViRt/gparted-0.19.0'
  debian/rules:28: recipe for target 'build-stamp' failed
  make: *** [build-stamp] Error 2

  [..]

The full build log is attached.


Regards,

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


gparted.0.19.0-3.unstable.amd64.log.txt.gz
Description: Binary data

Bug#807741: [package:salt-master] salt-master.service start times out

[Dirk Heinrichs]

Package: package:salt-master
Version: 2015.8.3+ds-1
Severity: serious

--- Please enter the report below this line. ---
After upgrade from version 2015.8.1+ds-2 to 2015.8.3+ds-1 the salt-
master.service times out upon start. This already happens during apt-get. If I 
try to start it afterwards, I get:

# systemctl start salt-master
Job for salt-master.service failed because a timeout was exceeded. See 
"systemctl status salt-master.service" and "journalctl -xe" for details.

However, the process runs for some time, I can see logging output using 
journactl -f in a 2nd shell, but once systemctl returns the salt-master 
process is also gone.

If I start it from the shell directly, it runs just fine.

Since the package is not usable in this state, I've set the severity to 
"serious"...
--- System information. ---
Architecture: amd64
Kernel:   Linux 4.2.0-1-amd64

Debian Release: stretch/sid
  990 testing www.deb-multimedia.org 
  990 testing security.debian.org 
  990 testing ftp.de.debian.org 
  500 utopic  ppa.launchpad.net 
  500 unstabledownload.jitsi.org 
  500 stable  update.devolo.com 
  500 nightly pkg.tox.chat 

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

Package's Recommends field is empty.

Package's Suggests field is empty.
-- 
Dirk Heinrichs 
GPG Public Key CB614542 | Jabber: dirk.heinri...@altum.de
Tox: he...@toxme.se
Sichere Internetkommunikation: http://www.retroshare.org
Privacy Handbuch: https://www.privacy-handbuch.de


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

Bug#807746: guncat: FTBFS: "CXX multiply defined"

[Frank B. Brokken]

Dear Chris Lamb, you wrote:

> guncat fails to build from source in unstable/amd64:

>   ./build clean
>   [icmconf, line 21] Error: CXX multiply defined
>   [icmconf, line 30] Error: LDFLAGS multiply defined
>   debian/rules:49: recipe for target 'clean' failed
>   make: *** [clean] Error 1

Thanks! The update adapting the icmake 8.00.04 will arrive shortly

-- 
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281 
Public PGP key: http://pgp.surfnet.nl
Key Fingerprint: DF32 13DE B156 7732 E65E  3B4D 7DB2 A8BE EAE4 D8AA

Bug#807730: incorrect bsd/unistd.h header

[Vincent Bernat]

 ❦ 12 décembre 2015 14:23 +0100, Guillem Jover  :

>> After a recent update of libbsd, programs using it now fail at compile
>> time with:
>> 
>> /usr/include/bsd/unistd.h: In function 'setproctitle':
>> /usr/include/bsd/unistd.h:64:2: error: expected declaration specifiers 
>> before '__printflike'
>>   __printflike(1, 2);
>>   ^
>
> Indeed! :(
>
>> It seems there is a missing backslash at the end of the previous line.
>
> This is due to the overlays, some headers now expect declarations from
> the overlayed headers, bu they are not requsting them and just use the
> system ones. I've added a unit test to catch this in the future, and
> will be fixing it for an upload targetted for later today.

Do you mean that if we hit this bug, we are doing something wrong?

I am including bsd/unistd.h, shouldn't I?
-- 
Don't stop with your first draft.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Bug#805193: aster: FTBFS: Fatal Error: finclude/petscsys.h: No such file or directory

[peter green]

On 12/12/15 17:32, peter green wrote:
I was able to get aster to build for raspbian stretch (in which I have 
imported the updated petsc from debian sid) with the changes in the 
attatched debdiff.
Sorry I must learn to read the screen more carefully and actually check 
that something has succeeded. The build in fact seems to have failed 
with an "unrepresentable changes to source" error. Further the debdiff I 
sent you doesn't represent the state of my source tree at the time I 
sent it due to said error.


There was another fix to the clean target needed. I am now testing the 
build again and will report back later with whether it suceeded or not.

Bug#807760: cfflib: maintainer address bounces

[Ansgar Burchardt]

Source: cfflib
Tags: sid
Severity: serious

The maintainer address for cfflib bounces, see below.

Ansgar

Mail Delivery System writes:
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   deb...@unidesign.ch
> SMTP error from remote mail server after RCPT TO::
> host unidesign.ch [194.126.200.43]: 550 No Such User Here"
>
> -- This is a copy of the message, including all the headers. --
>
[...]
> To: Stephan Gerhard , Mattia Rizzolo 
[...]
> Subject: cfflib_2.0.5-1.1_source.changes ACCEPTED into unstable
> Message-Id: 
> Date: Sat, 12 Dec 2015 00:18:58 +

Bug#800298: apt-show-source: Please migrate a supported debhelper compat level

[Giovani Ferreira]

Hi,

I did make a NMU to 10-day/delay queue. Feel free to cancel this
upload if needed.

The debian/changelog is:

apt-show-source (0.10+nmu3) unstable; urgency=medium

  * Non-maintainer upload.
  * Update DH level to 9. (Closes: #800298)
  * debian/compat: created.
  * debian/control:
 - Added the ${misc:Depends} variable to provide the right install
   dependencies.
 - Bumped Standards-Version to 3.9.6.
  * debian/rules: disabled the DH_COMPAT line.

I attached a debdiff.

cheers,


-- 
Giovani Ferreira
http://softwarelivre.org/jova2
GNU/Linux user: 337388  GPG ID: 2375A66C
diff -Nru apt-show-source-0.10+nmu2/debian/changelog 
apt-show-source-0.10+nmu3/debian/changelog
--- apt-show-source-0.10+nmu2/debian/changelog  2015-09-02 04:40:50.0 
-0300
+++ apt-show-source-0.10+nmu3/debian/changelog  2015-12-11 21:01:21.0 
-0200
@@ -1,3 +1,16 @@
+apt-show-source (0.10+nmu3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update DH level to 9. (Closes: #800298)
+  * debian/compat: created.
+  * debian/control:
+ - Added the ${misc:Depends} variable to provide the right install
+   dependencies.
+ - Bumped Standards-Version to 3.9.6.
+  * debian/rules: desabled the DH_COMPAT line.
+
+ -- Giovani Augusto Ferreira   Fri, 11 Dec 2015 18:31:28 
-0200
+
 apt-show-source (0.10+nmu2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru apt-show-source-0.10+nmu2/debian/compat 
apt-show-source-0.10+nmu3/debian/compat
--- apt-show-source-0.10+nmu2/debian/compat 1969-12-31 21:00:00.0 
-0300
+++ apt-show-source-0.10+nmu3/debian/compat 2015-12-11 18:32:18.0 
-0200
@@ -0,0 +1 @@
+9
diff -Nru apt-show-source-0.10+nmu2/debian/control 
apt-show-source-0.10+nmu3/debian/control
--- apt-show-source-0.10+nmu2/debian/control2015-08-20 17:09:41.0 
-0300
+++ apt-show-source-0.10+nmu3/debian/control2015-12-11 18:58:20.0 
-0200
@@ -2,13 +2,13 @@
 Section: admin
 Priority: optional
 Maintainer: OHURA Makoto 
-Standards-Version: 3.5.9
+Standards-Version: 3.9.6
 Build-Depends-Indep: perl
-Build-Depends: debhelper
+Build-Depends: debhelper (>=9)
 
 Package: apt-show-source
 Architecture: all
-Depends: ${perl:Depends}, apt
+Depends: ${misc:Depends}, ${perl:Depends}, apt
 Description: Shows source-package information
  This program parses the APT lists for source packages and the
  dpkg status file and then lists every package with a different
diff -Nru apt-show-source-0.10+nmu2/debian/rules 
apt-show-source-0.10+nmu3/debian/rules
--- apt-show-source-0.10+nmu2/debian/rules  2015-08-20 17:08:39.0 
-0300
+++ apt-show-source-0.10+nmu3/debian/rules  2015-12-11 19:21:55.0 
-0200
@@ -6,7 +6,7 @@
 #export DH_VERBOSE=1
 
 # This is the debhelper compatability version to use.
-export DH_COMPAT=1
+#export DH_COMPAT=1
 
 ifndef PERL
PERL = /usr/bin/perl

Bug#807736: Debian Bug report logs - #807736,gparted: FTBFS: Win_GParted.h:28:31: fatal error: sigc++/class_slot.h: No such file or directory

[Curtis Gedak]

Hi Chris,

The sigc++/class_slot.h include was removed from upstream GParted with
the following bug report and commit:

Bug 756035 - GParted does not compile with newer gtkmm libraries in
 Fedora 23
https://bugzilla.gnome.org/show_bug.cgi?id=756035

Stop including removed  header (#756035)
https://git.gnome.org/browse/gparted/commit/?id=d925bd2bb592160bd9b760c200fbeb7c9d24b2a1

Thanks goes to Mike Fleetwood for identifying and fixing this problem.


The enhancement was included in the upstream GParted 0.24.0 release on
October 27, 2015.

Phillip Susi has begun the process of packaging GParted 0.24.0.  See:

https://packages.qa.debian.org/g/gparted.html

Hence I believe that this problem will be resolved when the new version
of GParted is accepted into Debian.

Regards,
Curtis

Bug#807741: [package:salt-master] salt-master.service start times out

[Andrei POPESCU]

Control: reassign -1 salt-master 2015.8.3+ds-1

On Sb, 12 dec 15, 10:34:36, Dirk Heinrichs wrote:
> Package: package:salt-master
> Version: 2015.8.3+ds-1
> Severity: serious
> 
> --- Please enter the report below this line. ---
> After upgrade from version 2015.8.1+ds-2 to 2015.8.3+ds-1 the salt-
> master.service times out upon start. This already happens during apt-get. If 
> I 
> try to start it afterwards, I get:
> 
> # systemctl start salt-master
> Job for salt-master.service failed because a timeout was exceeded. See 
> "systemctl status salt-master.service" and "journalctl -xe" for details.
> 
> However, the process runs for some time, I can see logging output using 
> journactl -f in a 2nd shell, but once systemctl returns the salt-master 
> process is also gone.
> 
> If I start it from the shell directly, it runs just fine.
> 
> Since the package is not usable in this state, I've set the severity to 
> "serious"...
> --- System information. ---
> Architecture: amd64
> Kernel:   Linux 4.2.0-1-amd64
> 
> Debian Release: stretch/sid
>   990 testing www.deb-multimedia.org 
>   990 testing security.debian.org 
>   990 testing ftp.de.debian.org 
>   500 utopic  ppa.launchpad.net 
>   500 unstabledownload.jitsi.org 
>   500 stable  update.devolo.com 
>   500 nightly pkg.tox.chat 
> 
> --- Package information. ---
> Package's Depends field is empty.
> 
> Package's Recommends field is empty.
> 
> Package's Suggests field is empty.
> -- 
> Dirk Heinrichs 
> GPG Public Key CB614542 | Jabber: dirk.heinri...@altum.de
> Tox: he...@toxme.se
> Sichere Internetkommunikation: http://www.retroshare.org
> Privacy Handbuch: https://www.privacy-handbuch.de



-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Bug#807773: python-pkg-resources: UnicodeDecodeError: 'utf8' codec can't decode byte 0xb6 in position 147: invalid start byte

[Axel Beckert]

Package: python-pkg-resources
Version: 18.7.1-1
Severity: grave
Control: affects -1 git-buildpackage whatmaps
Justification: renders package unusable

Since the recent upgrade of packages built from the python2.7 source
package, multiple unrelated programs bail out with the following
backtraces, at least "gbp pull" and "whatmaps".

It always boils down to this line of code and backtrace:

→ python
Python 2.7.11 (default, Dec  9 2015, 00:29:25) 
[GCC 5.3.1 20151205] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from pkg_resources import load_entry_point
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3138, 
in 
@_call_aside
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3124, 
in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3151, 
in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 652, 
in _build_master
ws = cls()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 645, 
in __init__
self.add_entry(entry)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 701, 
in add_entry
for dist in find_distributions(entry, True):
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2139, 
in find_on_path
path_item, entry, metadata, precedence=DEVELOP_DIST
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2521, 
in from_location
py_version=py_version, platform=platform, **kw
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2835, 
in _reload_version
md_version = _version_from_file(self._get_metadata(self.PKG_INFO))
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2486, 
in _version_from_file
line = next(iter(version_lines), '')
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2654, 
in _get_metadata
for line in self.get_metadata_lines(name):
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2030, 
in get_metadata_lines
return yield_lines(self.get_metadata(name))
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2025, 
in get_metadata
metadata = f.read()
  File "/usr/lib/python2.7/codecs.py", line 314, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xb6 in position 147: 
invalid start byte
>>> 

Even only sourcing
/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py causes that
backtrace:

→ python /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 91, 
in 
import pkg_resources._vendor.packaging.version
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3138, 
in 
@_call_aside
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3124, 
in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3151, 
in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 652, 
in _build_master
ws = cls()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 645, 
in __init__
self.add_entry(entry)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 701, 
in add_entry
for dist in find_distributions(entry, True):
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2139, 
in find_on_path
path_item, entry, metadata, precedence=DEVELOP_DIST
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2521, 
in from_location
py_version=py_version, platform=platform, **kw
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2835, 
in _reload_version
md_version = _version_from_file(self._get_metadata(self.PKG_INFO))
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2486, 
in _version_from_file
line = next(iter(version_lines), '')
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2654, 
in _get_metadata
for line in self.get_metadata_lines(name):
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2030, 
in get_metadata_lines
return yield_lines(self.get_metadata(name))
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2025, 
in get_metadata
metadata = f.read()
  File "/usr/lib/python2.7/codecs.py", line 314, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xb6 in position 

Processed: python-pkg-resources: UnicodeDecodeError: 'utf8' codec can't decode byte 0xb6 in position 147: invalid start byte

[Debian Bug Tracking System]

Processing control commands:

> affects -1 git-buildpackage whatmaps
Bug #807773 [python-pkg-resources] python-pkg-resources: UnicodeDecodeError: 
'utf8' codec can't decode byte 0xb6 in position 147: invalid start byte
Added indication that 807773 affects git-buildpackage and whatmaps

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

Processed: Debian bug: #807427

[Debian Bug Tracking System]

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

> reassign 807427 hplip
Bug #807427 [sane-utils] sane-utils: Can not provide access to hplip scanner 
over network
Bug reassigned from package 'sane-utils' to 'hplip'.
No longer marked as found in versions sane-backends/1.0.24-8.
Ignoring request to alter fixed versions of bug #807427 to the same values 
previously set
> severity 807427 grave
Bug #807427 [hplip] sane-utils: Can not provide access to hplip scanner over 
network
Severity set to 'grave' from 'normal'
> --
Stopping processing here.

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

Bug#807672: marked as done (natlog: FTBFS: [/usr/bin/icmbuild, line 166] Error: idx undefined)

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2015 17:51:08 +
with message-id 
and subject line Bug#807672: fixed in natlog 1.02.03-1
has caused the Debian Bug report #807672,
regarding natlog: FTBFS: [/usr/bin/icmbuild, line 166] Error: idx undefined
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.)


-- 
807672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: natlog
Version: 1.02.00-4
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,

natlog fails to build from source in unstable/amd64:

  [..]

  # Add here commands to configure the package.
  touch configure-stamp
  dh_testdir
  # compile the package.
  ./build program
  [icmake/md, line 15] Warning: `sizeof' is deprecated. Use `listlen'
  
  touch version.cc
  gcc -E VERSION.h | grep -v '#' | sed 's/\"//g' > release.yo
  icmbuild program 
  [/usr/bin/icmbuild, line 166] Error: idx undefined
  [/usr/bin/icmbuild, line 166] Error: Incorrect returntype for function 
'find()'
  
  2 error(s) detected
  Fatal: system - failure of system call (status 256)
  debian/rules:33: recipe for target 'build-stamp' failed
  make: *** [build-stamp] Error 1

  [..]

The full build log is attached.


Regards,

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


natlog.1.02.00-4.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: natlog
Source-Version: 1.02.03-1

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

Debian distribution maintenance software
pp.
Frank B. Brokken  (supplier of updated natlog 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: Fri, 11 Dec 2015 17:33:15 +0100
Source: natlog
Binary: natlog
Architecture: source amd64
Version: 1.02.03-1
Distribution: unstable
Urgency: medium
Maintainer: Frank B. Brokken 
Changed-By: Frank B. Brokken 
Description:
 natlog - Source-natting firewall logging utility
Closes: 807672
Changes:
 natlog (1.02.03-1) unstable; urgency=medium
 .
   [ Frank B. Brokken ]
   * New upstream release (Closes: #807672).
   * Updated required versions of icmake and yodl in 'control'
 .
   [ tony mancill ]
   * Add patch for typo in usage.cc.
Checksums-Sha1:
 33af796f27dcec1b01510bd85b7cd729938b4bf4 1992 natlog_1.02.03-1.dsc
 35a901cbd019742abda60e047d7c8079112a0626 302974 natlog_1.02.03.orig.tar.gz
 92226272d60155b17606cb1a724734d6618fce12 7772 natlog_1.02.03-1.debian.tar.xz
 3d8def629674bcf7279eb3a3d98249d95f0893b1 48484 natlog_1.02.03-1_amd64.deb
Checksums-Sha256:
 80834aa6df73daddd23c9bb8512b4010e89332d9c44fa5e1d8e23b4147d83586 1992 
natlog_1.02.03-1.dsc
 38d9d159be2ae7c1f8de670498d1ed396577037ac557f1f0d9ab80b2d52bdcab 302974 
natlog_1.02.03.orig.tar.gz
 db92a3bb74a46eee33533051fab96dbb9ef2ab7bc61a066deb8912537635b807 7772 
natlog_1.02.03-1.debian.tar.xz
 05ec200828fc41e2e86d101fb6b942eeeb2627299a08bc4cc6e2bd350aafc7ef 48484 
natlog_1.02.03-1_amd64.deb
Files:
 30f94ce17562379a1803a426f8dff906 1992 devel optional natlog_1.02.03-1.dsc
 32ce47b37e0478b62f78927c47c41e42 302974 devel optional 
natlog_1.02.03.orig.tar.gz
 b9a43dd6d5d5e74c30f00ac0f3713e74 7772 devel optional 
natlog_1.02.03-1.debian.tar.xz
 f04ef809b67ebfe1ea33b6890447c5b7 48484 devel optional 
natlog_1.02.03-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWbFzEAAoJECHSBYmXSz6WCEEQALNsDLNWX/Ac2LmxzJg8HRiq
uIgU07ocCIJeddap04lpAx+W/b9ny/AOyBh/7VehocFNEJufDh5Bvj5Eux5C6MUe
IQZFnb+ws0GPoUa1tdVehCi7uz7sowgMHYlCfMfc9Sn5HypUxCGwqa4Ftsi+7+8v
3kIKhz736NwzufStEPFlpr0ff3lG5EK0KX+8ouy7MmBRZ3fVMXv6eKB8pnzHKPOn
LNkyRaCUXGlbyArCJjcdH5wUFTpKEpNPcgxY9LcvSa5Bp2VmN4gmTQHM+3hP6mgx
JR56+G60VOFXX4kokPT2I/JM6LP2T0ob8rAX4LLMKf+rAKr/10rh9j1ZEnrsFoCf

Bug#792548: [DRE-maint] Bug#792548: ruby-hashie, ruby-rash: error when trying to install together

[Antonio Terceiro]

On Wed, Sep 09, 2015 at 10:54:55AM +0200, Matthias Klose wrote:
> > Since ruby-rash has no reverse dependencies, I propose we remove it and
> > add a Conflicts: to ruby-hashie.
> 
> $ reverse-depends -b src:ruby-rash
> Reverse-Build-Depends
> =
> * ruby-faraday-middleware   (for ruby-rash)

Right, thanks for the heads up. This dependency has since been removed,
so I will proceed with the removal request.

-- 
Antonio Terceiro 


signature.asc
Description: PGP signature

Bug#807660: marked as done (jenkins-winstone: FTBFS: jenkins-winstone-2.8/target/test-classes does not exist)

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2015 15:52:56 +
with message-id 
and subject line Bug#807660: fixed in jenkins-winstone 2.9-1
has caused the Debian Bug report #807660,
regarding jenkins-winstone: FTBFS: jenkins-winstone-2.8/target/test-classes 
does not exist
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.)


-- 
807660: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jenkins-winstone
Version: 2.8-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,

jenkins-winstone fails to build from source in unstable/amd64:

  [..]

  main:
   [copy] Copying 3 files to 
/home/lamby/temp/cdt.20151211131603.5ByL2e24N7/jenkins-winstone-2.8/target
  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

  [INFO] Total time: 2.550 s
  [INFO] Finished at: 2015-12-11T13:18:59+02:00
  [INFO] Final Memory: 19M/298M
  [INFO] 

  [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-antrun-plugin:1.7:run (prepare-testwebapp) on 
project winstone: An Ant BuildException has occured: 
/home/lamby/temp/cdt.20151211131603.5ByL2e24N7/jenkins-winstone-2.8/target/test-classes
 does not exist.
  [ERROR] around Ant part .. @ 7:136 in 
/home/lamby/temp/cdt.20151211131603.5ByL2e24N7/jenkins-winstone-2.8/target/antrun/build-main.xml
  [ERROR] -> [Help 1]
  [ERROR] 
  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
  [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  [ERROR] 
  [ERROR] For more information about the errors and possible solutions, please 
read the following articles:
  [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
  /usr/share/cdbs/1/class/maven.mk:92: recipe for target 'mvn-build' failed
  make: *** [mvn-build] Error 1

  [..]

The full build log is attached.


Regards,

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


jenkins-winstone.2.8-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: jenkins-winstone
Source-Version: 2.9-1

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated jenkins-winstone 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 12 Dec 2015 12:25:35 +0100
Source: jenkins-winstone
Binary: libjenkins-winstone-java libjenkins-winstone-java-doc
Architecture: source all
Version: 2.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libjenkins-winstone-java - Jenkins branch of Winstone servlet container
 libjenkins-winstone-java-doc - Documentation for libjenkins-winstone-java
Closes: 807660
Changes:
 jenkins-winstone (2.9-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release
   * Removed the unused dependency on maven-antrun-plugin to fix a build
 failure with Maven 3 (Closes: #807660)
Checksums-Sha1:
 caf9d0c6ce2dca47a9e15e6b2806fa7aaa57bab1 2356 jenkins-winstone_2.9-1.dsc
 e1272e90fe224ebedeb5f70e10940b343f5d9ea7 54952 jenkins-winstone_2.9.orig.tar.xz
 9f54df39c02585073e0eb523f5c12dec9c56a21f 11148 
jenkins-winstone_2.9-1.debian.tar.xz
 93f6859ea3b00829373a520abbbdf84ba3a40c37 59494 
libjenkins-winstone-java-doc_2.9-1_all.deb
 a8044a236f7fd103aa2415a4033312e405d0ad02 1393268 
libjenkins-winstone-java_2.9-1_all.deb
Checksums-Sha256:
 

Processed: re: aster: FTBFS: Fatal Error: finclude/petscsys.h: No such file or directory

[Debian Bug Tracking System]

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

> Tags 805193 +patch
Bug #805193 [src:aster] aster: FTBFS: Fatal Error: finclude/petscsys.h: No such 
file or directory
Added tag(s) patch.
> Thanks
Stopping processing here.

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

Bug#807730: incorrect bsd/unistd.h header

[Guillem Jover]

[ BTW I got a JIRA mail for this bug report. ]

Hi!

On Sat, 2015-12-12 at 15:10:59 +0100, Vincent Bernat wrote:
>  ❦ 12 décembre 2015 14:23 +0100, Guillem Jover  :
> > This is due to the overlays, some headers now expect declarations from
> > the overlayed headers, bu they are not requsting them and just use the
> > system ones. I've added a unit test to catch this in the future, and
> > will be fixing it for an upload targetted for later today.
> 
> Do you mean that if we hit this bug, we are doing something wrong?

Not at all, sorry for the possible confusing wording.

> I am including bsd/unistd.h, shouldn't I?

That's fine, and it is supported, although it makes portability harder.

The problem is that bsd/unistd.h now requires internally bsd/sys/cdefs.h,
and it only includes sys/cdefs.h, which in your case is the system
sys/cdefs.h not the overlaid bsd/sys/cdefs.h, which would get transparently
used if using «pkg-config --cflags libbsd-overlay» for example.

The overlay is intended to be used to make portability easier, so that the
code can work out-of-the-box on BSD and non-BSD systems.

Thanks,
Guillem

Bug#807706: marked as done (uima-addons: FTBFS: Unresolveable build extension: Plugin org.apache.uima:PearPackagingMavenPlugin:2.3.1 )

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2015 16:23:02 +
with message-id 
and subject line Bug#807706: fixed in uima-addons 2.3.1-4
has caused the Debian Bug report #807706,
regarding uima-addons: FTBFS: Unresolveable build extension: Plugin 
org.apache.uima:PearPackagingMavenPlugin:2.3.1 
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.)


-- 
807706: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uima-addons
Version: 2.3.1-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,

uima-addons fails to build from source in unstable/amd64:

  [..]

  [INFO] Scanning for projects...
  [WARNING] The POM for org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1 is 
missing, no dependency information available
  [ERROR] [ERROR] Some problems were encountered while processing the POMs:
  [WARNING] 'build.plugins.plugin.version' for 
org.codehaus.mojo:build-helper-maven-plugin is missing. @ 
org.apache.uima:uima-addons-parent:2.3.1, 
/home/lamby/temp/cdt.20151211222410.4qLUOq6sqn/uima-addons-2.3.1/uima-addons-parent/pom.xml,
 line 571, column 14
  [ERROR] Unresolveable build extension: Plugin 
org.apache.uima:PearPackagingMavenPlugin:2.3.1 or one of its dependencies could 
not be resolved: The following artifacts could not be resolved: 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1, 
org.codehaus.plexus:plexus-utils:jar:1.1: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1 has not been downloaded from 
it before. @ 
  [WARNING] 'build.plugins.plugin.version' for 
org.codehaus.mojo:build-helper-maven-plugin is missing. @ 
org.apache.uima:uima-addons-parent:2.3.1, 
/home/lamby/temp/cdt.20151211222410.4qLUOq6sqn/uima-addons-2.3.1/uima-addons-parent/pom.xml,
 line 571, column 14
  [ERROR] Unresolveable build extension: Plugin 
org.apache.uima:PearPackagingMavenPlugin:2.3.1 or one of its dependencies could 
not be resolved: The following artifacts could not be resolved: 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1, 
org.codehaus.plexus:plexus-utils:jar:1.1: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1 has not been downloaded from 
it before. @ 
  [WARNING] 'build.plugins.plugin.version' for 
org.codehaus.mojo:build-helper-maven-plugin is missing. @ 
org.apache.uima:uima-addons-parent:2.3.1, 
/home/lamby/temp/cdt.20151211222410.4qLUOq6sqn/uima-addons-2.3.1/uima-addons-parent/pom.xml,
 line 571, column 14
  [ERROR] Unresolveable build extension: Plugin 
org.apache.uima:PearPackagingMavenPlugin:2.3.1 or one of its dependencies could 
not be resolved: The following artifacts could not be resolved: 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1, 
org.codehaus.plexus:plexus-utils:jar:1.1: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1 has not been downloaded from 
it before. @ 
  [WARNING] 'build.plugins.plugin.version' for 
org.codehaus.mojo:build-helper-maven-plugin is missing. @ 
org.apache.uima:uima-addons-parent:2.3.1, 
/home/lamby/temp/cdt.20151211222410.4qLUOq6sqn/uima-addons-2.3.1/uima-addons-parent/pom.xml,
 line 571, column 14
  [ERROR] Unresolveable build extension: Plugin 
org.apache.uima:PearPackagingMavenPlugin:2.3.1 or one of its dependencies could 
not be resolved: The following artifacts could not be resolved: 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1, 
org.codehaus.plexus:plexus-utils:jar:1.1: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1 has not been downloaded from 
it before. @ 
  [WARNING] 'build.plugins.plugin.version' for 
org.codehaus.mojo:build-helper-maven-plugin is missing. @ 
org.apache.uima:uima-addons-parent:2.3.1, 
/home/lamby/temp/cdt.20151211222410.4qLUOq6sqn/uima-addons-2.3.1/uima-addons-parent/pom.xml,
 line 571, column 14
  [ERROR] Unresolveable build extension: Plugin 
org.apache.uima:PearPackagingMavenPlugin:2.3.1 or one of its dependencies could 
not be resolved: The following artifacts could not be resolved: 
org.apache.uima:PearPackagingMavenPlugin:jar:2.3.1, 
org.codehaus.plexus:plexus-utils:jar:1.1: Cannot 

Bug#805193: aster: FTBFS: Fatal Error: finclude/petscsys.h: No such file or directory

[peter green]

Tags 805193 +patch
Thanks

I was able to get aster to build for raspbian stretch (in which I have 
imported the updated petsc from debian sid) with the changes in the 
attatched debdiff. I have not tried it on any other system. I have not 
tested if the resulting packages actually work. I will be uploading this 
to raspbian shortly. No intent to NMU in Debian.


The failure in the bug report was fixed by adding an include path. I 
added the include path to three different variables. I'm not sure which 
of them the build is actually using.


I then ran into another failure, PETSC_DEFAULT_DOUBLE_PRECISION seems to 
have dissapeared. I did some googling and found 
http://lists.mcs.anl.gov/pipermail/petsc-users/2014-February/020567.html 
which seemed to indicate that it should be replaced with 
PETSC_DEFAULT_REAL. I did so and got a successful build.


I also ran into and fixed a broken clean target while working on the 
package. I forgot to document this in the changelog.


P.S. Trying to build this package as root will break your system's 
python-numpy and then fail because of said breakage.
diff -Nru aster-11.5.0+dfsg2/debian/changelog 
aster-11.5.0+dfsg2/debian/changelog
--- aster-11.5.0+dfsg2/debian/changelog 2014-08-04 10:18:27.0 +
+++ aster-11.5.0+dfsg2/debian/changelog 2015-12-11 03:19:31.0 +
@@ -1,3 +1,10 @@
+aster (11.5.0+dfsg2-3+rpi1) stretch-staging; urgency=medium
+
+  * Force new include path for petsc fortran stuff.
+  * Change PETSC_DEFAULT_DOUBLE_PRECISION to PETSC_DEFAULT_REAL as hinted at 
by http://lists.mcs.anl.gov/pipermail/petsc-users/2014-February/020567.html
+
+ -- Peter Michael Green   Fri, 11 Dec 2015 00:53:43 
+
+
 aster (11.5.0+dfsg2-3) unstable; urgency=medium
 
   * Team upload.
diff -Nru aster-11.5.0+dfsg2/debian/patches/0011-petsc-default.patch 
aster-11.5.0+dfsg2/debian/patches/0011-petsc-default.patch
--- aster-11.5.0+dfsg2/debian/patches/0011-petsc-default.patch  1970-01-01 
00:00:00.0 +
+++ aster-11.5.0+dfsg2/debian/patches/0011-petsc-default.patch  2015-12-11 
03:35:46.0 +
@@ -0,0 +1,16 @@
+Description:  Change PETSC_DEFAULT_DOUBLE_PRECISION to PETSC_DEFAULT_REAL as 
hinted at by 
http://lists.mcs.anl.gov/pipermail/petsc-users/2014-February/020567.html
+Author: Peter Michael Green 
+
+--- aster-11.5.0+dfsg2.orig/bibfor/petsc/apksp.F90
 aster-11.5.0+dfsg2/bibfor/petsc/apksp.F90
+@@ -103,8 +103,8 @@ subroutine apksp(kptsc)
+ endif
+ !
+ rtol = resire
+-atol = PETSC_DEFAULT_DOUBLE_PRECISION
+-dtol = PETSC_DEFAULT_DOUBLE_PRECISION
++atol = PETSC_DEFAULT_REAL
++dtol = PETSC_DEFAULT_REAL
+ !
+ call KSPSetTolerances(ksp, rtol, atol, dtol, maxits,&
+   ierr)
diff -Nru aster-11.5.0+dfsg2/debian/patches/series 
aster-11.5.0+dfsg2/debian/patches/series
--- aster-11.5.0+dfsg2/debian/patches/series2014-08-04 10:07:55.0 
+
+++ aster-11.5.0+dfsg2/debian/patches/series2015-12-11 03:35:26.0 
+
@@ -8,3 +8,4 @@
 0008-Disable-BLACS-checks.patch
 0009-Fix-NumPy-version-comparison.patch
 0010-Check-that-DEST_CPU-exists-before-reading-it.patch
+0011-petsc-default.patch
diff -Nru aster-11.5.0+dfsg2/debian/rules aster-11.5.0+dfsg2/debian/rules
--- aster-11.5.0+dfsg2/debian/rules 2014-08-04 10:13:49.0 +
+++ aster-11.5.0+dfsg2/debian/rules 2015-12-11 03:01:43.0 +
@@ -11,6 +11,9 @@
 
 ifneq ($(wildcard 
/usr/lib/$(DEB_HOST_MULTIARCH)/hdf5/$(ARCH_DEFAULT_MPI_IMPL)/libhdf5.so),)
   export DEB_CPPFLAGS_MAINT_APPEND := 
-I/usr/include/hdf5/$(ARCH_DEFAULT_MPI_IMPL)
+  export DEB_FCFLAGS_MAINT_APPEND :=  
-I/usr/lib/petscdir/3.6.2/$(DEB_HOST_MULTIARCH)-real/include/petsc/
+  export DEB_FFLAGS_MAINT_APPEND :=  
-I/usr/lib/petscdir/3.6.2/$(DEB_HOST_MULTIARCH)-real/include/petsc/
+  export DEB_CFLAGS_MAINT_APPEND :=  
-I/usr/lib/petscdir/3.6.2/$(DEB_HOST_MULTIARCH)-real/include/petsc/
   export DEB_LDFLAGS_MAINT_APPEND := 
-Wl,-L/usr/lib/$(DEB_HOST_MULTIARCH)/hdf5/$(ARCH_DEFAULT_MPI_IMPL)
 endif
 

Bug#807474: marked as done (libfile-rsyncp-perl: FTBFS with perl 5.22 in experimental (MakeMaker changes))

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2015 19:34:39 +
with message-id 
and subject line Bug#807474: fixed in libfile-rsyncp-perl 0.74-2.1
has caused the Debian Bug report #807474,
regarding libfile-rsyncp-perl: FTBFS with perl 5.22 in experimental (MakeMaker 
changes)
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.)


-- 
807474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libfile-rsyncp-perl
Version: 0.74-2
Severity: serious
Justification: transition imminent
User: debian-p...@lists.debian.org
Usertags: perl-5.22-transition makemaker-prefix
Tags: sid stretch

This package FTBFS with perl 5.22.0-2, which removed support for a long-
obsolete way of overriding PREFIX when calling 'make install' with
ExtUtils::MakeMaker, as described in the lintian tag
debian-rules-makemaker-prefix-is-deprecated[1] and the Debian Perl
policy[2]:


ERROR: Can't create '/usr/lib/x86_64-linux-gnu/perl5/5.22/File'
mkdir /usr/lib/x86_64-linux-gnu/perl5/5.22/File: Permission denied at 
/usr/share/perl/5.22/ExtUtils/Install.pm line 477.


 at -e line 1.
make[1]: *** [pure_vendor_install] Error 13

The fix is to use DESTDIR instead of PREFIX; please see the lintian
`description for examples. Alternatively, newer versions of debhelper
can automatically call make install with the correct arguments when
using the dh7 style rules files.

The perl 5.22 is due to start this week, so apologies for the late
submission of this bug; for some reason my previous testing of this
issue overlooked this package.

Cheers,
Dominic.

[1] 

[2] 

--- End Message ---
--- Begin Message ---
Source: libfile-rsyncp-perl
Source-Version: 0.74-2.1

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libfile-rsyncp-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Dec 2015 20:08:12 +0100
Source: libfile-rsyncp-perl
Binary: libfile-rsyncp-perl
Architecture: source amd64
Version: 0.74-2.1
Distribution: unstable
Urgency: medium
Maintainer: Ludovic Drolez 
Changed-By: gregor herrmann 
Description:
 libfile-rsyncp-perl - Perl based implementation of an Rsync client
Closes: 807474
Changes:
 libfile-rsyncp-perl (0.74-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "FTBFS with perl 5.22 in experimental (MakeMaker changes)":
 use DESTDIR instead of PREFIX in debian/rules.
 (Closes: #807474)
Checksums-Sha1:
 956858204d8ebf85da3db194977db094b0b4561e 1872 libfile-rsyncp-perl_0.74-2.1.dsc
 9ed077a083ebcd2eb3928d8d7ad120e9e65dc279 2716 
libfile-rsyncp-perl_0.74-2.1.diff.gz
 a909d305fb7819ff705e026d84af3cfbafc43b77 85804 
libfile-rsyncp-perl_0.74-2.1_amd64.deb
Checksums-Sha256:
 e10cde770abea12e8146e0c176c91874de2b789e0bee1ec0ab44874a8e91f32e 1872 
libfile-rsyncp-perl_0.74-2.1.dsc
 0de23ad9be31391d074250a9d40a6e87ffd8a4f7766cf570e406870d9c3126fe 2716 
libfile-rsyncp-perl_0.74-2.1.diff.gz
 2453ba86b323c8baa91bcccd5972ac620324ac6467ae757a276751f6589f3d65 85804 
libfile-rsyncp-perl_0.74-2.1_amd64.deb
Files:
 5db6dd8da1ab10c5891d1497529ef1b4 1872 perl optional 
libfile-rsyncp-perl_0.74-2.1.dsc
 da2c7e50925cfa173517840192376f86 2716 perl optional 
libfile-rsyncp-perl_0.74-2.1.diff.gz
 98a770914e1a34dc364ca473f5538c0d 85804 perl optional 
libfile-rsyncp-perl_0.74-2.1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJWac3EXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC

Bug#806882: libc-bin: unable to set pts permissions (and open a terminal...)

[Jakub Wilk]

* Aurelien Jarno , 2015-12-04, 18:11:
In that case given the issue is due to a user misconfiguration, I 
guess we should just try to detect it, display a note and fail the 
installation.


Warning the user would be certainly a good idea. But of course that 
would only help if the devpts filesystem was misconfigured at 
installation time. For me, this wasn't the case.


What was the issue on your case?


I had schroot configured to mount /dev/pts with default permissions. 
(This should not be the problem for most schroot users. By default 
schroot bind-mounts /dev/pts from the host.) So my /dev/pts permissions 
were fine on upgrade; they only broke later, when I tried to build a 
package.


In another mail Aurelien wrote:


usertags 806882 + serious
thanks


tag 806882 + serious
thanks

Due to a typo, this bug didn't get upgraded to serious.


FWIW, it wasn't a typo. :) It's an actual usertag of mine:
https://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=serious=jwilk%40debian.org

--
Jakub Wilk

Bug#807546: [alfred] Fails to build on non-linux systems

[Petter Reinholdtsen]

[Franz Schrober]
> Package fails to build on non-linux systems systems because libcap-dev
> is missing on them. On these systems the make calls have to use the
> parameter CONFIG_ALFRED_CAPABILITIES=n and the control file has to
> reduce the Build-Depends for libcap-dev no linux-any only

If the package never built on these systems, I would expect the severity of
the bug to be important, not grave.  Why do you believe not building
on a platform where it never has been built before in Debian is a grave
bug?

It is defintely a issue that should be fixed, but I do not believe it should 
block
it from entering testing (and eventually stable) if it isn't fixed.

-- 
Happy hacking
Petter Reinholdtsen

Bug#801541: marked as done (tg.devtools: unsatisfiable Depends: python-sqlalchemy (<< 0.10))

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2015 19:00:02 +
with message-id 
and subject line Bug#805800: Removed package(s) from unstable
has caused the Debian Bug report #801541,
regarding tg.devtools: unsatisfiable Depends: python-sqlalchemy (<< 0.10)
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.)


-- 
801541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tg.devtools
Version: 2.0.2-5
Severity: serious
Tags: sid
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

0m23.7s ERROR: Command failed (status=100): ['chroot', 
'/tmp/piupartss/tmpf6HdAf', 'apt-get', '-y', 'install', 
'python-tg.devtools=2.0.2-5']
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   python-tg.devtools : Depends: python-sqlalchemy (< 0.10) but 1.0.8+ds1-1 is 
to be installed
  E: Unable to correct problems, you have held broken packages.


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Version: 2.0.2-5+rm

Dear submitter,

as the package tg.devtools 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/805800

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#807730: incorrect bsd/unistd.h header

[Vincent Bernat]

 ❦ 12 décembre 2015 18:35 +0100, Guillem Jover  :

>>  ❦ 12 décembre 2015 14:23 +0100, Guillem Jover  :
>> > This is due to the overlays, some headers now expect declarations from
>> > the overlayed headers, bu they are not requsting them and just use the
>> > system ones. I've added a unit test to catch this in the future, and
>> > will be fixing it for an upload targetted for later today.
>> 
>> Do you mean that if we hit this bug, we are doing something wrong?
>
> Not at all, sorry for the possible confusing wording.
>
>> I am including bsd/unistd.h, shouldn't I?
>
> That's fine, and it is supported, although it makes portability harder.
>
> The problem is that bsd/unistd.h now requires internally bsd/sys/cdefs.h,
> and it only includes sys/cdefs.h, which in your case is the system
> sys/cdefs.h not the overlaid bsd/sys/cdefs.h, which would get transparently
> used if using «pkg-config --cflags libbsd-overlay» for example.
>
> The overlay is intended to be used to make portability easier, so that the
> code can work out-of-the-box on BSD and non-BSD systems.

OK. I am using this:

# setproctitle (maybe through libbsd [until 0.5, it is only a stub function])
AC_SEARCH_LIBS([setproctitle], [util bsd])
AC_REPLACE_FUNCS([setproctitle])
AC_CHECK_FUNCS([setproctitle_init])

case " $LIBS " in
 *\ -lbsd\ *)
AC_DEFINE(HAVE_LIBBSD, 1, [Define if libbsd is used])
;;
esac

Then:

#ifdef HAVE_LIBBSD
# include 
# include 
# include 
#endif

#if !HAVE_SETPROCTITLE
void setproctitle(const char *fmt, ...) __attribute__ ((format (printf, 1, 2)));
#endif

My own setproctitle is just an empty stub. So, now, the best way seems
to be able to just use PKG_CHECK_MODULES([BSD], [libbsd-overlay]),
right? Is there something special to do to know if I can use
setproctitle_init or should I test for its presence?
-- 
Use self-identifying input.  Allow defaults.  Echo both on output.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Bug#807746: marked as done (guncat: FTBFS: "CXX multiply defined")

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2015 18:49:20 +
with message-id 
and subject line Bug#807746: fixed in guncat 1.01.02-1
has caused the Debian Bug report #807746,
regarding guncat: FTBFS: "CXX multiply defined"
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.)


-- 
807746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: guncat
Version: 0.92.00-5
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,

guncat fails to build from source in unstable/amd64:

  [..]

   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: source package guncat
  dpkg-buildpackage: source version 0.92.00-5
  dpkg-buildpackage: source distribution unstable
  dpkg-buildpackage: source changed by tony mancill 
   dpkg-source --before-build guncat-0.92.00
  dpkg-buildpackage: host architecture amd64
   fakeroot debian/rules clean
  dh_testdir
  dh_testroot
  rm -f build-stamp configure-stamp
  # Add here commands to clean up after the build process.
  ./build clean
  [icmconf, line 21] Error: CXX multiply defined
  [icmconf, line 30] Error: LDFLAGS multiply defined
  debian/rules:49: recipe for target 'clean' failed
  make: *** [clean] Error 1

  [..]

The full build log is attached.


Regards,

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


guncat.0.92.00-5.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: guncat
Source-Version: 1.01.02-1

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

Debian distribution maintenance software
pp.
Frank B. Brokken  (supplier of updated guncat 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: Sat, 12 Dec 2015 15:24:33 +0100
Source: guncat
Binary: guncat
Architecture: source amd64
Version: 1.01.02-1
Distribution: unstable
Urgency: medium
Maintainer: Frank B. Brokken 
Changed-By: Frank B. Brokken 
Description:
 guncat - Catenates files while decrypting PGP-encrypted sections
Closes: 807746
Changes:
 guncat (1.01.02-1) unstable; urgency=medium
 .
   * New upstream release adapts build scripts to icmake >= 8.00.04, and
 applies the patch to suppresses calling 'tput clear' by /usr/bin/icmbuild
 (Closes: #807746).
 .
   * debian/control adapted accordingly.
Checksums-Sha1:
 bd4d304ad02ba54d680a775b8598bae729fa4829 1968 guncat_1.01.02-1.dsc
 1f31c14d41c9216064d0ed55c95edb07ca573305 15824 guncat_1.01.02.orig.tar.gz
 7c11599a2b97457fa480ed03ebf93520308a6083 3272 guncat_1.01.02-1.debian.tar.xz
 7b7711f9dcf46ac3eb6bb80b647b3c0d0fb97603 22660 guncat_1.01.02-1_amd64.deb
Checksums-Sha256:
 6ad44495f72fe1a1fdfaafea47cfb488f74823a74c4620146eb6257937a0e349 1968 
guncat_1.01.02-1.dsc
 eb984a83f33d8be55e0efdf94a805aa4f676d51bbf7ef482020656fb02253658 15824 
guncat_1.01.02.orig.tar.gz
 a35161df288f933d56c10e39cf0b8db6941d4403152f5990bdcbb1e091fc2107 3272 
guncat_1.01.02-1.debian.tar.xz
 724e30043791b634f4eda2ba2876da97cd35a10bb9e2b594a57646409647b9dd 22660 
guncat_1.01.02-1_amd64.deb
Files:
 a7ee200ece03fa72322875c1cbcbce7c 1968 devel optional guncat_1.01.02-1.dsc
 0e086a89568ed65560bdcf5afe1c410b 15824 devel optional 
guncat_1.01.02.orig.tar.gz
 132016b9c1dfc89192beefa354e6a66b 3272 devel optional 
guncat_1.01.02-1.debian.tar.xz
 80241da122d39febfcf1ae6da321c234 22660 devel optional 
guncat_1.01.02-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWbGhaAAoJECHSBYmXSz6Wwm4QAM7ZkupIaB0oyv3FJrowoR/k
OVjYTy2q34Q2P3Ttea1rAWwdlJA3NN2uUU/W+pOLDErMXke7dNRe6Xa2cljfh6qm
XpSH+S1Klowgu41hiX0AnE+7gKYt8YDsBmv04F00dD1r0eyJpgQEXiu4g8xE5rp1
MoEWcknWDuZHqp9Hr47TYrTjdneZ7026Erc5PIOu8utoTbjbqui3p+DlEyREj5pj

Bug#805193: aster: FTBFS: Fatal Error: finclude/petscsys.h: No such file or directory

[peter green]

On 12/12/15 17:47, peter green wrote:

On 12/12/15 17:32, peter green wrote:
I was able to get aster to build for raspbian stretch (in which I 
have imported the updated petsc from debian sid) with the changes in 
the attatched debdiff.
Sorry I must learn to read the screen more carefully and actually 
check that something has succeeded. The build in fact seems to have 
failed with an "unrepresentable changes to source" error. Further the 
debdiff I sent you doesn't represent the state of my source tree at 
the time I sent it due to said error.


There was another fix to the clean target needed. I am now testing the 
build again and will report back later with whether it suceeded or not.
Another gotcha I ran into, for some reason even after I su'd to nobody 
it still wanted to use the same temp directory (with root in it's name) 
which already existed and was owned by root causing the build to fail.


So I removed that directory from /tmp and tried the build again and 
FINALLY got a successful build.


New debdiff attatched, still no intent to NMU.

Bug#807422: marked as done (libsys-cpuload-perl: FTBFS with perl 5.22 in experimental (MakeMaker changes))

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2015 19:19:59 +
with message-id 
and subject line Bug#807422: fixed in libsys-cpuload-perl 0.03-7.1
has caused the Debian Bug report #807422,
regarding libsys-cpuload-perl: FTBFS with perl 5.22 in experimental (MakeMaker 
changes)
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.)


-- 
807422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsys-cpuload-perl
Version: 0.03
Severity: serious
Justification: transition imminent
User: debian-p...@lists.debian.org
Usertags: perl-5.22-transition makemaker-prefix
Tags: sid stretch

This package FTBFS with perl 5.22.0-2, which removed support for a long-
obsolete way of overriding PREFIX when calling 'make install' with
ExtUtils::MakeMaker, as described in the lintian tag
debian-rules-makemaker-prefix-is-deprecated[1] and the Debian Perl
policy[2]:


ERROR: Can't create '/usr/lib/x86_64-linux-gnu/perl5/5.22/Sys'
mkdir /usr/lib/x86_64-linux-gnu/perl5/5.22/Sys: Permission denied at /usr/share/
perl/5.22/ExtUtils/Install.pm line 477.


 at -e line 1.
Makefile:802: recipe for target 'pure_vendor_install' failed

The fix is to use DESTDIR instead of PREFIX; please see the lintian
`description for examples. Alternatively, newer versions of debhelper
can automatically call make install with the correct arguments when
using the dh7 style rules files.

The perl 5.22 is due to start this week, so apologies for the late
submission of this bug; for some reason my previous testing of this
issue overlooked this package.

Cheers,
Dominic.

[1] 

[2] 

--- End Message ---
--- Begin Message ---
Source: libsys-cpuload-perl
Source-Version: 0.03-7.1

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libsys-cpuload-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Dec 2015 20:03:24 +0100
Source: libsys-cpuload-perl
Binary: libsys-cpuload-perl
Architecture: source amd64
Version: 0.03-7.1
Distribution: unstable
Urgency: medium
Maintainer: Noël Köthe 
Changed-By: gregor herrmann 
Description:
 libsys-cpuload-perl - module which retrieves load average of a machine
Closes: 807422
Changes:
 libsys-cpuload-perl (0.03-7.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "FTBFS with perl 5.22 in experimental (MakeMaker changes)":
 use DESTDIR instead of PREFIX in debian/rules.
 (Closes: #807422)
Checksums-Sha1:
 7e94ed69dba7490df11c202fab41e25fd2a779f6 1918 libsys-cpuload-perl_0.03-7.1.dsc
 9b7a25297ab036e9168227f4c0ffa153decd79ed 2393 
libsys-cpuload-perl_0.03-7.1.diff.gz
 cea990970ca440ceb72f4167f20f59f39055c967 8686 
libsys-cpuload-perl_0.03-7.1_amd64.deb
Checksums-Sha256:
 ebf9fe2c45716e2d9e39213113911d94340368dfcdeff2bc29c0110a8767fe5e 1918 
libsys-cpuload-perl_0.03-7.1.dsc
 0d86b3e2e0ecef0b2bb2c308a208120dc05d4dbf01b534914c4f1b9e964a0561 2393 
libsys-cpuload-perl_0.03-7.1.diff.gz
 6b3e95ab974112afb9ae8d6cd8cef82000ff130dfa5221434900b226aefd6e07 8686 
libsys-cpuload-perl_0.03-7.1_amd64.deb
Files:
 5b89d622d9e43c093775ad092a03b2f7 1918 perl optional 
libsys-cpuload-perl_0.03-7.1.dsc
 ba7cfa2c9555e0356de6596e2fe161cd 2393 perl optional 
libsys-cpuload-perl_0.03-7.1.diff.gz
 252c1d9cf649ca61b7467def9e13d504 8686 perl optional 
libsys-cpuload-perl_0.03-7.1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJWacygXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC

Bug#807401: marked as done (libtext-unaccent-perl: FTBFS with perl 5.22 in experimental (MakeMaker changes))

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2015 19:20:10 +
with message-id 
and subject line Bug#807401: fixed in libtext-unaccent-perl 1.08-1.1
has caused the Debian Bug report #807401,
regarding libtext-unaccent-perl: FTBFS with perl 5.22 in experimental 
(MakeMaker changes)
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.)


-- 
807401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807401
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtext-unaccent-perl
Version: 1.08-1
Severity: serious
Justification: transition imminent
User: debian-p...@lists.debian.org
Usertags: perl-5.22-transition makemaker-prefix
Tags: sid stretch

This package FTBFS with perl 5.22.0-2, which removed support for a long-
obsolete way of overriding PREFIX when calling 'make install' with
ExtUtils::MakeMaker, as described in the lintian tag
debian-rules-makemaker-prefix-is-deprecated[1] and the Debian Perl
policy[2]:


ERROR: Can't create '/usr/lib/x86_64-linux-gnu/perl5/5.22/Text'
mkdir /usr/lib/x86_64-linux-gnu/perl5/5.22/Text: Permission denied at /usr/share
/perl/5.22/ExtUtils/Install.pm line 477.


 at -e line 1.
Makefile:808: recipe for target 'pure_vendor_install' failed

The fix is to use DESTDIR instead of PREFIX; please see the lintian
`description for examples. Alternatively, newer versions of debhelper
can automatically call make install with the correct arguments when
using the dh7 style rules files.

The perl 5.22 is due to start this week, so apologies for the late
submission of this bug; for some reason my previous testing of this
issue overlooked this package.

Cheers,
Dominic.

[1] 

[2] 

--- End Message ---
--- Begin Message ---
Source: libtext-unaccent-perl
Source-Version: 1.08-1.1

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libtext-unaccent-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Dec 2015 19:52:06 +0100
Source: libtext-unaccent-perl
Binary: libtext-unaccent-perl
Architecture: source amd64
Version: 1.08-1.1
Distribution: unstable
Urgency: medium
Maintainer: Loic Dachary (OuoU) 
Changed-By: gregor herrmann 
Description:
 libtext-unaccent-perl - provides functions to remove accents using UTF16 as a 
pivot
Closes: 807401
Changes:
 libtext-unaccent-perl (1.08-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "FTBFS with perl 5.22 in experimental (MakeMaker changes)":
 use DESTDIR instead of PREFIX in debian/rules.
 (Closes: #807401)
Checksums-Sha1:
 a29715282c5fd2418473edae82ff7de6d24d87bc 1901 
libtext-unaccent-perl_1.08-1.1.dsc
 842a9848c802a516080b3da37060e4deee4f5064 2394 
libtext-unaccent-perl_1.08-1.1.diff.gz
 7d5024ee07cfa61dae945947fd9937402f3106db 21308 
libtext-unaccent-perl_1.08-1.1_amd64.deb
Checksums-Sha256:
 39dacaf410390d2e493e158427f07143d0719d304ee98244903a7902a49d549a 1901 
libtext-unaccent-perl_1.08-1.1.dsc
 f7ba6bfa3132a3f4dd21d419d789dceb28fe668784e49450f6f7053c969e8b47 2394 
libtext-unaccent-perl_1.08-1.1.diff.gz
 bae11db5ec2f76346f40b6c5b41e78c8b91ea778f553b4a420eeb3b85791bf52 21308 
libtext-unaccent-perl_1.08-1.1_amd64.deb
Files:
 de1f93df83245d27ef331f8d618d6495 1901 interpreters optional 
libtext-unaccent-perl_1.08-1.1.dsc
 37ed4c7b8374aa067950485db6788b17 2394 interpreters optional 
libtext-unaccent-perl_1.08-1.1.diff.gz
 8769b24cc2e8ab7da62ef81f595730dc 21308 interpreters optional 
libtext-unaccent-perl_1.08-1.1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Bug#807400: marked as done (libtext-aspell-perl: FTBFS with perl 5.22 in experimental (MakeMaker changes))

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2015 19:20:05 +
with message-id 
and subject line Bug#807400: fixed in libtext-aspell-perl 0.09-1.1
has caused the Debian Bug report #807400,
regarding libtext-aspell-perl: FTBFS with perl 5.22 in experimental (MakeMaker 
changes)
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.)


-- 
807400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtext-aspell-perl
Version: 0.09-1
Severity: serious
Justification: transition imminent
User: debian-p...@lists.debian.org
Usertags: perl-5.22-transition makemaker-prefix
Tags: sid stretch

This package FTBFS with perl 5.22.0-2, which removed support for a long-
obsolete way of overriding PREFIX when calling 'make install' with
ExtUtils::MakeMaker, as described in the lintian tag
debian-rules-makemaker-prefix-is-deprecated[1] and the Debian Perl
policy[2]:


ERROR: Can't create '/usr/lib/x86_64-linux-gnu/perl5/5.22/Text'
mkdir /usr/lib/x86_64-linux-gnu/perl5/5.22/Text: Permission denied at /usr/share
/perl/5.22/ExtUtils/Install.pm line 477.


 at -e line 1.

The fix is to use DESTDIR instead of PREFIX; please see the lintian
`description for examples. Alternatively, newer versions of debhelper
can automatically call make install with the correct arguments when
using the dh7 style rules files.

The perl 5.22 is due to start this week, so apologies for the late
submission of this bug; for some reason my previous testing of this
issue overlooked this package.

Cheers,
Dominic.

[1] 

[2] 

--- End Message ---
--- Begin Message ---
Source: libtext-aspell-perl
Source-Version: 0.09-1.1

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libtext-aspell-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Dec 2015 19:42:26 +0100
Source: libtext-aspell-perl
Binary: libtext-aspell-perl
Architecture: source amd64
Version: 0.09-1.1
Distribution: unstable
Urgency: medium
Maintainer: Brian Nelson 
Changed-By: gregor herrmann 
Description:
 libtext-aspell-perl - Perl interface to the GNU Aspell library
Closes: 807400
Changes:
 libtext-aspell-perl (0.09-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "FTBFS with perl 5.22 in experimental (MakeMaker changes)":
 use DESTDIR instead of PREFIX in debian/rules.
 (Closes: #807400)
Checksums-Sha1:
 85a63766260f47f35c6e38f3fe9c85b4d5b5d51d 1955 libtext-aspell-perl_0.09-1.1.dsc
 4b37b645fdbaab2d1e7ad6d9e102a1c1f25b6eb2 2408 
libtext-aspell-perl_0.09-1.1.diff.gz
 4d2cf6b8114e73afc8e2f1fde5c042f7106feb54 27152 
libtext-aspell-perl_0.09-1.1_amd64.deb
Checksums-Sha256:
 95eff80183989276885b3dba6eb784d6d8b8452fb07f3ea26ca4580771fa3cbc 1955 
libtext-aspell-perl_0.09-1.1.dsc
 5b9b8f325e03a38012ef73d69a5d5ca40205208c4ab9774a624aeeec957090b6 2408 
libtext-aspell-perl_0.09-1.1.diff.gz
 9ff9f523e4c09eed53fba186537f5da9347b6e94933188300ef98d1deb74f9b3 27152 
libtext-aspell-perl_0.09-1.1_amd64.deb
Files:
 d0d960d006b4a783c3a31a1f665315c8 1955 perl optional 
libtext-aspell-perl_0.09-1.1.dsc
 68274527211d79d4bdc423bd76c2df3c 2408 perl optional 
libtext-aspell-perl_0.09-1.1.diff.gz
 eb9d163681a73131b7116acfaa02692c 27152 perl optional 
libtext-aspell-perl_0.09-1.1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJWacheXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoG6DsP/iQ5hoZ8ZT2OwfrXscLDjpdr

Processed (with 1 error): Re: Bug#807773: python-pkg-resources: UnicodeDecodeError: 'utf8' codec can't decode byte 0xb6 in position 147: invalid start byte

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #807773 [python-pkg-resources] python-pkg-resources: UnicodeDecodeError: 
'utf8' codec can't decode byte 0xb6 in position 147: invalid start byte
Severity set to 'important' from 'grave'
> forcemerge 807681 -1
Bug #807681 [python3-pkg-resources] python3-pkg-resources: UnicodeDecodeError 
when parsing egg-info files with non-ASCII content
Unable to merge bugs because:
package of #807773 is 'python-pkg-resources' not 'python3-pkg-resources'
Failed to forcibly merge 807681: Did not alter merged bugs.


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

Bug#807773: python-pkg-resources: UnicodeDecodeError: 'utf8' codec can't decode byte 0xb6 in position 147: invalid start byte

[Matthias Klose]

Control: severity -1 important
Control: forcemerge 807681 -1

I always appreciate your sensibility for checking the BTS before filing bug 
reports.

Bug#807734: marked as done (bobcat: FTBFS: Error: double quote at end of string not found)

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2015 19:48:57 +
with message-id 
and subject line Bug#807734: fixed in bobcat 4.01.04-1
has caused the Debian Bug report #807734,
regarding bobcat: FTBFS: Error: double quote at end of string not found
to be marked as done.

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

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


-- 
807734: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807734
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bobcat
Version: 4.01.03-2
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,

bobcat fails to build from source in unstable/amd64:

  [..]

   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: source package bobcat
  dpkg-buildpackage: source version 4.01.03-2
  dpkg-buildpackage: source distribution unstable
  dpkg-buildpackage: source changed by tony mancill 
   dpkg-source --before-build bobcat-4.01.03
  dpkg-buildpackage: host architecture amd64
   fakeroot debian/rules clean
  dh_testdir
  dh_testroot
  rm -f build-stamp
  ./build clean
  [./build, line 38] Error: double quote at end of string not found
  [./build, line 38] Error: Syntax error at `#include'
  debian/rules:34: recipe for target 'clean' failed
  make: *** [clean] Error 1

  [..]

The full build log is attached.


Regards,

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


bobcat.4.01.03-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: bobcat
Source-Version: 4.01.04-1

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

Debian distribution maintenance software
pp.
Frank B. Brokken  (supplier of updated bobcat 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: Sat, 12 Dec 2015 13:44:20 +0100
Source: bobcat
Binary: libbobcat4 libbobcat-dev
Architecture: source amd64
Version: 4.01.04-1
Distribution: unstable
Urgency: medium
Maintainer: Frank B. Brokken 
Changed-By: Frank B. Brokken 
Description:
 libbobcat-dev - headers and documentation for the Bobcat library
 libbobcat4 - run-time (shared) Bobcat library
Closes: 807734
Changes:
 bobcat (4.01.04-1) unstable; urgency=medium
 .
   * New upstream release, updates build scripts to icmake >= 8.00.04, and
 applies Tony's 4.01.03-2 patches. (Closes: #807734).
Checksums-Sha1:
 0d73e918ce943cc0cd20437e383d318b58004196 2099 bobcat_4.01.04-1.dsc
 03550e0af55c375d89a3f386678002392ae10c42 1095225 bobcat_4.01.04.orig.tar.gz
 63f01ef46385d5ad810308517940c5d6e757a7e1 12632 bobcat_4.01.04-1.debian.tar.xz
 5daa190b62818d48b8b250a9310cb5b5d2d98d76 1388662 
libbobcat-dev_4.01.04-1_amd64.deb
 349e52ac049827bf12b07f017f263455d64ad7c7 252126 libbobcat4_4.01.04-1_amd64.deb
Checksums-Sha256:
 82a31eb8d55290597a0166fe9d464a29a2c4154a9daef9502e9e4599ecd9eafd 2099 
bobcat_4.01.04-1.dsc
 a4199fb0c281f95a758e3fffa7cf1fd342e89003455fe47af46948e6db9b439b 1095225 
bobcat_4.01.04.orig.tar.gz
 d817144dfc7d5d4b8021f5e96604cb3bd274604989278432c2e12344519bc9a2 12632 
bobcat_4.01.04-1.debian.tar.xz
 7fecca1715680222a9106786ba3284eef797934d55ea8ad64fdef88a6e427ba2 1388662 
libbobcat-dev_4.01.04-1_amd64.deb
 affb083fb6743faf9e0a24a3e344002cfbe01fe4242e4ba7253b0e47be0a19ec 252126 
libbobcat4_4.01.04-1_amd64.deb
Files:
 e344d953deb0a9eb3a07b9e142aecd68 2099 libs optional bobcat_4.01.04-1.dsc
 06974f87ef4650e6f42c1115efed5f9c 1095225 libs optional 
bobcat_4.01.04.orig.tar.gz
 da832b3e5eee3f7a229763eb704225b3 12632 libs optional 
bobcat_4.01.04-1.debian.tar.xz
 47deca5aa937fbb24995e7d0d6ebb981 1388662 libdevel optional 
libbobcat-dev_4.01.04-1_amd64.deb
 913175961635ae62965c68d1d1889adc 252126 libs optional 
libbobcat4_4.01.04-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Processed: giflib 5 now in unstable; raising the issues needed for the transition (#805012)

[Debian Bug Tracking System]

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

> severity 803273 serious
Bug #803273 [src:fontforge] prepare for giflib5
Severity set to 'serious' from 'normal'
> severity 803274 serious
Bug #803274 [src:libgdiplus] prepare for giflib5
Severity set to 'serious' from 'normal'
> severity 803276 serious
Bug #803276 [src:aseprite] prepare for giflib5
Severity set to 'serious' from 'normal'
> severity 803277 serious
Bug #803277 [src:driftnet] prepare for giflib5
Severity set to 'serious' from 'normal'
> severity 803278 serious
Bug #803278 [src:efl] prepare for giflib5
Severity set to 'serious' from 'normal'
> severity 803279 serious
Bug #803279 [src:fenix] prepare for giflib5
Severity set to 'serious' from 'normal'
> severity 803281 serious
Bug #803281 [src:gladtex] prepare for giflib5
Severity set to 'serious' from 'normal'
> severity 803283 serious
Bug #803283 [src:gnustep-gui] prepare for giflib5
Severity set to 'serious' from 'normal'
> severity 803285 serious
Bug #803285 [src:metapixel] prepare for giflib5
Severity set to 'serious' from 'normal'
> severity 803286 serious
Bug #803286 [src:mtpaint] prepare for giflib5
Severity set to 'serious' from 'normal'
> severity 803287 serious
Bug #803287 [src:ming] prepare for giflib5
Severity set to 'serious' from 'normal'
> severity 803289 serious
Bug #803289 [src:prima] prepare for giflib5
Severity set to 'serious' from 'normal'
> severity 803290 serious
Bug #803290 [src:qutemol] prepare for giflib5
Severity set to 'serious' from 'normal'
> severity 803291 serious
Bug #803291 [src:swftools] prepare for giflib5
Severity set to 'serious' from 'normal'
> severity 803292 serious
Bug #803292 [src:wmaker] prepare for giflib5
Severity set to 'serious' from 'normal'
> severity 803293 serious
Bug #803293 [src:xplanet] prepare for giflib5
Severity set to 'serious' from 'normal'
> severity 803295 serious
Bug #803295 [src:spamprobe] prepare for giflib5
Severity set to 'serious' from 'normal'
> severity 803297 serious
Bug #803297 [src:kmess] prepare for giflib5
Severity set to 'serious' from 'normal'
> severity 803298 serious
Bug #803298 [src:boats] prepare for giflib5
Severity set to 'serious' from 'normal'
> severity 803300 serious
Bug #803300 [src:openscenegraph] prepare for giflib5
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
803273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803273
803274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803274
803276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803276
803277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803277
803278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803278
803279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803279
803281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803281
803283: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803283
803285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803285
803286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803286
803287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803287
803289: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803289
803290: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803290
803291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803291
803292: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803292
803293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803293
803295: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803295
803297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803297
803298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803298
803300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#807756: gnubg: fails to start. hangs using 100% of one cpu core

[Russ Allbery]

Julian Hughes  writes:

> when starting gnubg it uses 100% of one cpu core and then apparently
> hangs with no output and without starting the gui.

Hm, that sounds like it somehow got built with PIE.  I was experimenting
with that and it definitely doesn't work, but I could have sworn the
version I uploaded wasn't built with PIE.

I can reproduce this, trying to figure out what's going on right now.

-- 
Russ Allbery (r...@debian.org)   

Bug#803281: Update of GladTeX

[Sebastian Humenda]

Hi,

I'll try to provide an update in the upcoming month. However the next upload
will not require the gif library anymore. Still, thanks fo reporting.

Cheers
Sebastian


signature.asc
Description: PGP signature

Bug#796514: marked as done (ruby-hashie: FTBFS: Expected pending 'Bug in MRI 2.2.x means this behavior is broken in those versions' to fail)

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2015 18:22:06 +
with message-id 
and subject line Bug#796514: fixed in ruby-hashie 3.4.2-3
has caused the Debian Bug report #796514,
regarding ruby-hashie: FTBFS: Expected pending 'Bug in MRI 2.2.x means this 
behavior is broken in those versions' to fail
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.)


-- 
796514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-hashie
Version: 3.4.2-2
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-hashie fails to build from source in unstable/amd64:

  [..]

  
┌──┐
  │ Run tests for ruby2.2 from debian/ruby-tests.rake   
  │
  
└──┘
  
  
RUBYLIB=/tmp/buildd/ruby-hashie-3.4.2/debian/ruby-hashie/usr/lib/ruby/vendor_ruby:.
  rake2.2 -f debian/ruby-tests.rake
  /usr/bin/ruby2.2 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
  
...F.
  
  Failures:
  
1) Hashie::Mash#respond_to? is able to access an unknown suffixed
key as a method FIXED
   Expected pending 'Bug in MRI 2.2.x means this behavior is broken
   in those versions' to fail. No Error was raised.
   # ./spec/hashie/mash_spec.rb:365
  
  Finished in 0.49762 seconds (files took 0.99926 seconds to load)
  545 examples, 1 failure
  
  Failed examples:
  
  rspec ./spec/hashie/mash_spec.rb:365 # Hashie::Mash#respond_to? is
  able to access an unknown suffixed key as a method
  
  /usr/bin/ruby2.2 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
  failed
  ERROR: Test "ruby2.2" failed. Exiting.
  dh_auto_install: dh_ruby --install
  /tmp/buildd/ruby-hashie-3.4.2/debian/ruby-hashie returned exit code 1
  debian/rules:6: recipe for target 'binary' failed
  make: *** [binary] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
  status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/ruby-hashie_3.4.2-2.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Fri Aug 21 08:23:13 GMT+12 2015
I: pbuilder-time-stamp: 1440188593
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 7.0.50~), gem2deb, rake, ruby-rspec, pry, 
ruby-activesupport
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20247 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 

Bug#732300: logkeys: logfile is gibberish

[Paulo]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

I could reproduce bug here.

My default locale is pt_BR.UTF-8, so I did:

logkeys --export-keymap=my-keymap.txt
logkeys: Success writing keymap to file 'my-keymap.txt'

logkeys --start --keymap=my-keymap.txt --output=output.txt
echo abcdefghijklmnopqrstuv

with the same results:

cat output.txt
e]fo ȁx]aesdfighjvcopqr܂tuz܀y'

BUT,

upstream made commit: [1] ...b0fbffb
including some keymaps

When I use pt_BR.map provided by Kluts at the commit,
everything works nice.

[1] 
https://github.com/kernc/logkeys/commit/2c70d1743516bf8597832164f1eec4bc4b0fbffb

Regards,
[]'s
kretcheu
:x
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWbGs1AAoJEDnxel9a775zhMkP/1AbAKWvH4sCKGSfXrABjen2
dlXaqQ3UzFBpqtgCijUedesIftAPz3dlbnh1IEYscf6FZJUWWbpGOr9fTaZhHxZt
V1Cc37mwijTIYoNtt6si5JfzVeQXoEXBj4vm6Som+Rvo2kDlUL47O5veG1fdQsGy
o31Uo7lPCJ7Gj5jrgdH+GyWcOeZO25nPYp+Ktsyno3j9u1oouv2Ugk/mI+gQQ94k
zO6dts3LZNWlADvzTTdGAAb/kQpp0TojQwFitdv5DJzuJ1Q/RlpjmpNs0n06OAxW
g8cAmM8pG300SNPtQOwkeJhOlEUUPitZwuSd6TS9wKhsxvyH/T7ein2Rt9mFWLPM
uK38JLre/w4cm+5ZtNsO0Kbinx5kJvp2xBHguQ3hC+79+bmoEojsqyEIXkuSsAFM
2p10K84p1jpXgseLlpM77Gc8mb8PZooOByxTrvD90ENPmI69uIEJ1t3OkiVsevil
mp1d3AFD4QAERFGdsvZ5VxebkJCI5+VSdfN2+bVyhlyIyo7pU5HpaIHCcNuoz2gn
UllJIjxbhGbBcbwkbtlBmWAUDqq3f3qdozE71RPL0hYgv+xL66LeMkmF08bY8kro
dAGhzPxHEaMdgDhM2ipW4YO451Z2FX1IqqaikF6fIUCb4dlYdIyz8yRFEOoFT7Jm
xOdfWgLxIZyxAh/nl1qr
=alnU
-END PGP SIGNATURE-

Bug#807736: marked as done (gparted: FTBFS: Win_GParted.h:28:31: fatal error: sigc++/class_slot.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2015 20:43:28 -0500
with message-id <566ccd40.8060...@ubuntu.com>
and subject line gparted: FTBFS: Win_GParted.h:28:31: fatal error: 
sigc++/class_slot.h: No such file or directory
has caused the Debian Bug report #807736,
regarding gparted: FTBFS: Win_GParted.h:28:31: fatal error: 
sigc++/class_slot.h: No such file or directory
to be marked as done.

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

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


-- 
807736: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gparted
Version: 0.19.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,

gparted fails to build from source in unstable/amd64:

  [..]

  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -pthread 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -std=c++11 
-pthread -I/usr/include/gtkmm-2.4 -I/usr/lib/x86_64-linux-gnu/gtkmm-2.4/include 
-I/usr/include/atkmm-1.6 -I/usr/include/gtk-unix-print-2.0 
-I/usr/include/gtk-2.0 -I/usr/include/gdkmm-2.4 
-I/usr/lib/x86_64-linux-gnu/gdkmm-2.4/include -I/usr/include/giomm-2.4 
-I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/pangomm-1.4 
-I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include -I/usr/include/glibmm-2.4 
-I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/cairomm-1.0 
-I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/sigc++-2.0 
-I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 
-DGPARTED_DATADIR=\""/usr/share"\" -DGNOME_ICONDIR=\""/usr/share/pixmaps"\" 
-DGNOMELOCALEDIR=\""/usr/share/locale"\"  -D_FORTIFY_SOURCE=2 -Wall -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security -MT 
GParted_Core.o -MD -MP -MF .deps/GParted_Core.Tpo -c -o GParted_Core.o 
GParted_Core.cc
  In file included from GParted_Core.cc:18:0:
  ../include/Win_GParted.h:28:31: fatal error: sigc++/class_slot.h: No such 
file or directory
  compilation terminated.
  Makefile:479: recipe for target 'GParted_Core.o' failed
  make[3]: *** [GParted_Core.o] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20151212101705.AM2zXKViRt/gparted-0.19.0/src'
  Makefile:484: recipe for target 'all-recursive' failed
  make[2]: *** [all-recursive] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20151212101705.AM2zXKViRt/gparted-0.19.0'
  Makefile:347: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151212101705.AM2zXKViRt/gparted-0.19.0'
  debian/rules:28: recipe for target 'build-stamp' failed
  make: *** [build-stamp] Error 2

  [..]

The full build log is attached.


Regards,

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


gparted.0.19.0-3.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Version: 0.24.0-1

Fixed in new upstream release.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCgAGBQJWbM06AAoJEBB5UWFcu6UWTBcH/ilLPbLVL9Q2HbPLUOD6OF33
i7FikD/R4r76+bWLRu2vNyXikF1++RF6t7/GTeEqK7LmjM5HLfYA2iFVh9vDdF1a
WPUHnDINWFnbQY9rasHWWCFaTZAkV+wFDq775oT5EzyXy9l2iqcTprhMkrNKkn3m
/ZvznShDQbSHNlgkR169Sft66H3zE623hAwYHkYvZ1H+ubSgBlZn+UHDXdXQprYi
iUgS+nkLe9AJh1S6VacP/tzK1W6KoAcg2lhz3Fay4bwOiWnZAg58sKPNl0cpoPdK
0ybypoeNeorcjcgzuvLnBgsWut2uAVv3gvYyOpGcGEFS/RWNqJV30Yt8J4mlz3M=
=QJaW
-END PGP SIGNATURE End Message ---

Bug#765062: libapache-mod-auth-radius: FTBFS - missing build dependency on libssl-dev

[Paulo]

Hi,

I uploaded a NMU to 10-day/delay queue. Feel free to cancel this upload if 
needed.

The debian/changelog is:


libapache-mod-auth-radius (1.5.8-1.3) unstable; urgency=medium

  * Non-maintainer upload.
  * Added patch to fix FTBFS (Closes: #765062) thanks to
Josip Rodin  and Michael Tautschnig 
.
  * debian/control: Standards-Version to 3.9.6.
  * debian/watch: Included.

I attached a debdiff.

Thanks.

[]'s
kretcheu
:x


diff -u libapache-mod-auth-radius-1.5.8/mod_auth_radius-2.0.la 
libapache-mod-auth-radius-1.5.8/mod_auth_radius-2.0.la
--- libapache-mod-auth-radius-1.5.8/mod_auth_radius-2.0.la
+++ libapache-mod-auth-radius-1.5.8/mod_auth_radius-2.0.la
@@ -1,5 +1,5 @@
 # mod_auth_radius-2.0.la - a libtool library file
-# Generated by ltmain.sh (GNU libtool) 2.2.6b Debian-2.2.6b-2
+# Generated by libtool (GNU libtool) 2.4.2 Debian-2.4.2-1.11
 #
 # Please DO NOT delete this file!
 # It is necessary for linking the library.
diff -u libapache-mod-auth-radius-1.5.8/mod_auth_radius-2.0.lo 
libapache-mod-auth-radius-1.5.8/mod_auth_radius-2.0.lo
--- libapache-mod-auth-radius-1.5.8/mod_auth_radius-2.0.lo
+++ libapache-mod-auth-radius-1.5.8/mod_auth_radius-2.0.lo
@@ -1,5 +1,5 @@
 # mod_auth_radius-2.0.lo - a libtool object file
-# Generated by ltmain.sh (GNU libtool) 2.2.6b Debian-2.2.6b-2
+# Generated by libtool (GNU libtool) 2.4.2 Debian-2.4.2-1.11
 #
 # Please DO NOT delete this file!
 # It is necessary for linking the library.
diff -u libapache-mod-auth-radius-1.5.8/mod_auth_radius-2.0.c 
libapache-mod-auth-radius-1.5.8/mod_auth_radius-2.0.c
--- libapache-mod-auth-radius-1.5.8/mod_auth_radius-2.0.c
+++ libapache-mod-auth-radius-1.5.8/mod_auth_radius-2.0.c
@@ -288,7 +288,6 @@
  */
 
 #include 
-#include 
 #include 
 #include 
 #include 
diff -u libapache-mod-auth-radius-1.5.8/debian/control 
libapache-mod-auth-radius-1.5.8/debian/control
--- libapache-mod-auth-radius-1.5.8/debian/control
+++ libapache-mod-auth-radius-1.5.8/debian/control
@@ -3,7 +3,7 @@
 Uploaders: Fabio M. Di Nitto 
 Section: web
 Priority: optional
-Standards-Version: 3.6.1
+Standards-Version: 3.9.6
 Build-Depends: debhelper (>= 5), dh-apache2, apache2-dev
 
 Package: libapache2-mod-auth-radius
diff -u libapache-mod-auth-radius-1.5.8/debian/changelog 
libapache-mod-auth-radius-1.5.8/debian/changelog
--- libapache-mod-auth-radius-1.5.8/debian/changelog
+++ libapache-mod-auth-radius-1.5.8/debian/changelog
@@ -1,3 +1,13 @@
+libapache-mod-auth-radius (1.5.8-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Added patch to fix FTBFS (Closes: #765062) thanks to
+Josip Rodin  and Michael Tautschnig 
.
+  * debian/control: Standards-Version to 3.9.6.
+  * debian/watch: Included.
+
+ -- Paulo Roberto Alves de Oliveira (aka kretcheu)   Sat, 
12 Dec 2015 17:44:00 -0200
+
 libapache-mod-auth-radius (1.5.8-1.2) unstable; urgency=low
 
   * Non-maintainer upload.
only in patch2:
unchanged:
--- libapache-mod-auth-radius-1.5.8.orig/debian/watch
+++ libapache-mod-auth-radius-1.5.8/debian/watch
@@ -0,0 +1,2 @@
+version=3
+http://freeradius.org/mod_auth_radius/ 
.*/mod_auth_radius-(\d.*)\.(?:tgz|tbz2|txz|tar)


signature.asc
Description: OpenPGP digital signature

Processed: found 806909 in 2.4.40+dfsg-1

[Debian Bug Tracking System]

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

> found 806909 2.4.40+dfsg-1
Bug #806909 [slapd] slapd: crashes on big jpegPhoto with auditlog enabled
Marked as found in versions openldap/2.4.40+dfsg-1.
> thanks
Stopping processing here.

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

Processed: re: krfb build-depends on cruft package

[Debian Bug Tracking System]

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

> tags 807277 +patch
Bug #807277 [krfb] krfb build-depends on cruft package
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#807277: krfb build-depends on cruft package

[Peter Green]

tags 807277 +patch
thanks

In a raspbian stretch-staging environment (which has sid's 
ktp-common-internals) I was able to build this package after changing 
the build-dependency from libktpcommoninternalsprivate-dev to libktp-dev

Bug#807784: octave-optim suggests `lyx`

[Hormet Yiltiz]

Package: octave-optim
Version: 1.4.1-1+b1
Severity: serious
Justification: Policy 7.2

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   octave-optim suggests lyx, which is a office suite that makes working
   with LaTeX easy, and implements a way for reproducable research.
   However, `lyx` then depends on `texlive`, which is a heavy
   dependency. Octave-optim is a package of GNU Octave, which is used
   for scientific computation. octave-optim, being a package for a
   octave that does the computation, should NOT depend or suggest a 3rd
   party software that is not very related to its usage.

   * What exactly did you do (or not do) that was effective (or
   Looked at `apt-cache info octave-optim`
 ineffective)?
   * What was the outcome of this action?
   suggests `lyx`
   * What outcome did you expect instead?
   does NOT suggests `lyx` or any texlive package.

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


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

Kernel: Linux 4.2.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 octave-optim depends on:
ii  libblas3 [libblas.so.3]1.2.20110419-11
ii  libc6  2.19-22
ii  libgcc11:5.2.1-23
ii  liblapack3 [liblapack.so.3]3.5.0-5
ii  liboctave3v5   4.0.0-5
ii  libopenblas-base [liblapack.so.3]  0.2.15-1
ii  libstdc++6 5.2.1-23
ii  octave 4.0.0-5
ii  octave-struct  1.0.11-1+b2

octave-optim recommends no packages.

Versions of packages octave-optim suggests:
ii  lyx  2.1.4-2

-- no debconf information

Processed: re: kst: Fails to build with GSL 2

[Debian Bug Tracking System]

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

> severity 805799 serious
Bug #805799 [src:kst] kst: Fails to build with GSL 2
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#807756: gnubg: fails to start. hangs using 100% of one cpu core

[Russ Allbery]

Control: reassign -1 libtasn1-6
Control: affects -1 gnubg

Julian Hughes  writes:

> Package: gnubg
> Version: 1.05.000-2
> Severity: grave
> Justification: renders package unusable

> when starting gnubg it uses 100% of one cpu core and then apparently
> hangs with no output and without starting the gui.

So, I'm not sure what's going on here, but it seems to be some sort of
weird bug in libgnutls/libtasn1.  gnubg is going into an infinite loop
before any gnubg code actually runs at all, during shared library
initialization.  This is the backtrace of the infinite loop:

#0  memcpy (__dest=0x83e070, __src=0x7fffea09a46e, __len=6)
at /usr/include/x86_64-linux-gnu/bits/string3.h:53
#1  0x7fffe838eee2 in strcpy (__src=0x7fffea09a46e "PKIX1", 
__dest=0x83e070 "") at /usr/include/x86_64-linux-gnu/bits/string3.h:104
#2  _asn1_str_cpy (dest=dest@entry=0x83e070 "", 
dest_tot_size=dest_tot_size@entry=65, src=0x7fffea09a46e "PKIX1")
at gstr.c:59
#3  0x7fffe838f43b in _asn1_set_name (node=node@entry=0x83e070, 
name=) at parser_aux.c:379
#4  0x7fffe8390489 in asn1_array2tree (array=, 
definitions=definitions@entry=0x7fffea2d0f20 <_gnutls_pkix1_asn>, 
errorDescription=errorDescription@entry=0x0) at structure.c:199
#5  0x7fffe9ff4edd in gnutls_global_init () at gnutls_global.c:257
#6  0x7fffe9fd6ed9 in lib_init () at gnutls_global.c:434
#7  0x77dea26a in call_init (l=, argc=argc@entry=1, 
argv=argv@entry=0x7fffe098, env=env@entry=0x7fffe0a8)
at dl-init.c:72
#8  0x77dea37b in call_init (env=0x7fffe0a8, argv=0x7fffe098, 
argc=1, l=) at dl-init.c:30
#9  _dl_init (main_map=0x77ffe188, argc=1, argv=0x7fffe098, 
env=0x7fffe0a8) at dl-init.c:120
#10 0x77ddbcca in _dl_start_user () from /lib64/ld-linux-x86-64.so.2
#11 0x0001 in ?? ()
#12 0x7fffe42a in ?? ()
#13 0x in ?? ()

So for some reason it's going into an infinite loop inside a memcpy of
only six bytes?  I'm really boggled by this behavior, but I'm not seeing
the mechanism where gnubg could cause this.

Reassigning to the libtasn1-6 package for help.  Maybe they have some idea
what's going on here.

libtasn1-6 maintainers, this is 100% reproducible by just installing gnubg
from unstable and running gnubg.  To get the above backtrace, I just
grabbed the source package, did apt-get build-dep gnubg, debian/rules
build, and installed the debugging packages for libgnutls and libtasn1.

-- 
Russ Allbery (r...@debian.org)   

Processed: Re: Bug#807756: gnubg: fails to start. hangs using 100% of one cpu core

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libtasn1-6
Bug #807756 [gnubg] gnubg: fails to start. hangs using 100% of one cpu core
Bug reassigned from package 'gnubg' to 'libtasn1-6'.
No longer marked as found in versions gnubg/1.05.000-2.
Ignoring request to alter fixed versions of bug #807756 to the same values 
previously set
> affects -1 gnubg
Bug #807756 [libtasn1-6] gnubg: fails to start. hangs using 100% of one cpu core
Added indication that 807756 affects gnubg

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

Bug#806588: Should conduit be removed?

[Mattia Rizzolo]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: conduit -- RoQA; depends on old libs, dead upstream, 
low popcon, unmaintainer
Control: severity -1 normal

> Should conduit be removed?

yes.

> - It depends on gstreamer 0.10, which is scheduled for removal
> - It's dead upstream
> - Popcon is marginal
> - Unmaintained (last maintainer upload in 2010)

Also:
 - It build-depends on pythons-support, scheduled for removal too
 - the build is unreproducible

It's a leaf packages, shouldn't be any problem:

mattia@coccia ~ % dak rm -Rn conduit
Will remove the following packages from unstable:

   conduit | 0.3.17-1.1 | source, all

   Maintainer: Jose Carlos Garcia Sogo 

   --- Reason ---

   --

   Checking reverse dependencies...
   No dependency problem found.

dak rm -Rn conduit  19.80s user 1.48s system 37% cpu 57.447 total
mattia@coccia ~ % 


-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#803281: Update of GladTeX

[Matthias Klose]

On 12.12.2015 21:50, Sebastian Humenda wrote:

Hi,

I'll try to provide an update in the upcoming month. However the next upload
will not require the gif library anymore. Still, thanks fo reporting.


I don't think it's ok to delay the transition for a month. So please upload the 
fix now.

Bug#807733: marked as done (antlr3: FTBFS: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode )

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2015 21:49:51 +
with message-id 
and subject line Bug#807733: fixed in antlr3 3.5.2-4
has caused the Debian Bug report #807733,
regarding antlr3: FTBFS: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode 
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.)


-- 
807733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: antlr3
Version: 3.5.2-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,

antlr3 fails to build from source in unstable/amd64:

  [..]

  cd antlr3-maven-plugin && cd . && /usr/lib/jvm/default-java/bin/java 
-noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 
-Dproperties.file.manual=/home/lamby/temp/cdt.20151212101545.Zh9YPF8EtD/antlr3-3.5.2/debian/maven.properties
 -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/lamby/temp/cdt.20151212101545.Zh9YPF8EtD/antlr3-3.5.2
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Dmaven.repo.local=/home/lamby/temp/cdt.20151212101545.Zh9YPF8EtD/antlr3-3.5.2/debian/maven-repo
 -DbuildNumber="debian-3" 
-Ddebian.dir=/home/lamby/temp/cdt.20151212101545.Zh9YPF8EtD/antlr3-3.5.2/debian 
-Ddebian.package=antlr3 
-Dmaven.repo.local=/home/lamby/temp/cdt.20151212101545.Zh9YPF8EtD/antlr3-3.5.2/debian/maven-repo
 -Dinstall.to.usj=false -Dmaven.test.skip=true -Duse.maven.repo.local=true 
package install org.debian.maven:debian-maven-plugin:2.0:install
  [INFO] Scanning for projects...
  [INFO]
 
  [INFO] 

  [INFO] Building ANTLR 3 Maven plugin 3.5.2
  [INFO] 

  [WARNING] The POM for org.codehaus.plexus:plexus-compiler-api:jar:debian is 
missing, no dependency information available
  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

  [INFO] Total time: 0.818 s
  [INFO] Finished at: 2015-12-12T10:20:09+02:00
  [INFO] Final Memory: 8M/236M
  [INFO] 

  [ERROR] Failed to execute goal on project antlr3-maven-plugin: Could not 
resolve dependencies for project 
org.antlr:antlr3-maven-plugin:maven-plugin:3.5.2: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.codehaus.plexus:plexus-compiler-api:jar:debian has not been downloaded from 
it before. -> [Help 1]
  [ERROR] 
  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
  [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  [ERROR] 
  [ERROR] For more information about the errors and possible solutions, please 
read the following articles:
  [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
  debian/rules:21: recipe for target 'before-mvn-build' failed
  make: *** [before-mvn-build] Error 1

  [..]

The full build log is attached.


Regards,

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


antlr3.3.5.2-3.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: antlr3
Source-Version: 3.5.2-4

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated antlr3 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 

Bug#807478: marked as done (razor: FTBFS with perl 5.22 in experimental (MakeMaker changes))

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2015 21:55:02 +
with message-id 
and subject line Bug#807478: fixed in razor 1:2.85-4.2
has caused the Debian Bug report #807478,
regarding razor: FTBFS with perl 5.22 in experimental (MakeMaker changes)
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.)


-- 
807478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: razor
Version: 1:2.85-4.1
Severity: serious
Justification: transition imminent
User: debian-p...@lists.debian.org
Usertags: perl-5.22-transition makemaker-prefix
Tags: sid stretch

This package FTBFS with perl 5.22.0-2, which removed support for a long-
obsolete way of overriding PREFIX when calling 'make install' with
ExtUtils::MakeMaker, as described in the lintian tag
debian-rules-makemaker-prefix-is-deprecated[1] and the Debian Perl
policy[2]:


ERROR: Can't create '/usr/bin'
Do not have write permissions on '/usr/bin'

 at -e line 1.
Makefile:945: recipe for target 'pure_vendor_install' failed

The fix is to use DESTDIR instead of PREFIX; please see the lintian
`description for examples. Alternatively, newer versions of debhelper
can automatically call make install with the correct arguments when
using the dh7 style rules files.

The perl 5.22 is due to start this week, so apologies for the late
submission of this bug; for some reason my previous testing of this
issue overlooked this package.

Cheers,
Dominic.

[1] 

[2] 

--- End Message ---
--- Begin Message ---
Source: razor
Source-Version: 1:2.85-4.2

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Dec 2015 21:13:53 +0100
Source: razor
Binary: razor
Architecture: source amd64
Version: 1:2.85-4.2
Distribution: unstable
Urgency: medium
Maintainer: Giuseppe Iuculano 
Changed-By: gregor herrmann 
Description:
 razor  - spam-catcher using a collaborative filtering network
Closes: 807478
Changes:
 razor (1:2.85-4.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "FTBFS with perl 5.22 in experimental (MakeMaker changes)":
 replace PREFIX with DESTDIR in debian/rules.
 (Closes: #807478)
   * Additional change for perl 5.22: fix handling of section 5 manpages:
 - drop unneeded handling from debian/rules
 - add patch to adjust regexp for inserting man5 targets in Makefile.PL:
   ExtUtils::MakeMaker now adds quotation marks.
Checksums-Sha1:
 eddda7996e6c65508e301f762a8e57759618f635 1988 razor_2.85-4.2.dsc
 625c19f5f894a840d6cc5bf494cab3c7c8a3cfee 15150 razor_2.85-4.2.diff.gz
 c075f8ec7a209f9e5dbd3bebfb8eb97f45c55598 112768 razor_2.85-4.2_amd64.deb
Checksums-Sha256:
 2623d8546ad89e8bad0213ee1b41920d9532a9638ccd0c3b35efea2a80a9b7ca 1988 
razor_2.85-4.2.dsc
 49d516741f0d7c84899832c15e98d2ae2a67940691bdfa152605c88681e60703 15150 
razor_2.85-4.2.diff.gz
 c69c873034e41f6f6da0eb8913d03a3bbe7b1f3f3a4bc88f1fb3571701498cdd 112768 
razor_2.85-4.2_amd64.deb
Files:
 605922a71ddb2d4fe674c8c5ccd96b6c 1988 mail optional razor_2.85-4.2.dsc
 719a323c352e61d8a624a1c23bccf7e6 15150 mail optional razor_2.85-4.2.diff.gz
 cd0c2ca6ae59ece2712415cb8d5a1882 112768 mail optional razor_2.85-4.2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJWad3tXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGCWEP/0S5KwD0cM6rsiuzNKrz+KCC

Bug#805193: aster: FTBFS: Fatal Error: finclude/petscsys.h: No such file or directory

[peter green]

On 12/12/15 19:01, peter green wrote:


New debdiff attatched, still no intent to NMU.
Sorry, debdiff at 
http://debdiffs.raspbian.org/main/a/aster/aster_11.5.0%2bdfsg2-3%2brpi1.debdiff

Processed: your mail

[Debian Bug Tracking System]

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

> tags 807662 + fixed-upstream
Bug #807662 [mrpt-common] mrpt-common: fails to upgrade from 'jessie' - trying 
to overwrite 
/usr/share/mrpt/config_files/simul-beacons/example_simul-beacons.ini
Added tag(s) fixed-upstream.
>
End of message, stopping processing here.

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

Bug#807659: marked as done (libgettext-commons-java: FTBFS: Error resolving version for plugin 'org.apache.maven.plugins:maven-eclipse-plugin' )

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2015 22:34:05 +
with message-id 
and subject line Bug#807659: fixed in libgettext-commons-java 0.9.6-3
has caused the Debian Bug report #807659,
regarding libgettext-commons-java: FTBFS:  Error resolving version for plugin 
'org.apache.maven.plugins:maven-eclipse-plugin' 
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.)


-- 
807659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgettext-commons-java
Version: 0.9.6-2
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,

libgettext-commons-java fails to build from source in unstable/amd64:

  [..]

  cd . && /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 
-Dproperties.file.manual=/home/lamby/temp/cdt.20151211131618.ZBtWBvMQgk/libgettext-commons-java-0.9.6/debian/maven.properties
 -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/lamby/temp/cdt.20151211131618.ZBtWBvMQgk/libgettext-commons-java-0.9.6
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Dmaven.repo.local=/home/lamby/temp/cdt.20151211131618.ZBtWBvMQgk/libgettext-commons-java-0.9.6/debian/maven-repo
  package -DskipTests
  [INFO] Scanning for projects...
  [INFO]
 
  [INFO] 

  [INFO] Building Gettext Commons 0.9.6
  [INFO] 

  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

  [INFO] Total time: 0.163 s
  [INFO] Finished at: 2015-12-11T13:18:58+02:00
  [INFO] Final Memory: 6M/236M
  [INFO] 

  [ERROR] Error resolving version for plugin 
'org.apache.maven.plugins:maven-eclipse-plugin' from the repositories [local 
(/home/lamby/temp/cdt.20151211131618.ZBtWBvMQgk/libgettext-commons-java-0.9.6/debian/maven-repo),
 central (https://repo.maven.apache.org/maven2)]: Plugin not found in any 
plugin repository -> [Help 1]
  [ERROR] 
  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
  [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  [ERROR] 
  [ERROR] For more information about the errors and possible solutions, please 
read the following articles:
  [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginVersionResolutionException
  /usr/share/cdbs/1/class/maven.mk:92: recipe for target 'mvn-build' failed
  make: *** [mvn-build] Error 1

  [..]

The full build log is attached.


Regards,

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


libgettext-commons-java.0.9.6-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: libgettext-commons-java
Source-Version: 0.9.6-3

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated libgettext-commons-java 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 12 Dec 2015 23:26:03 +0100
Source: libgettext-commons-java
Binary: libgettext-commons-java
Architecture: source all
Version: 0.9.6-3
Distribution: unstable
Urgency: low
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 

Processed: Re: Bug#806588: Should conduit be removed?

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #806588 [conduit] Should conduit be removed?
Bug reassigned from package 'conduit' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #806588 to the same values 
previously set
Ignoring request to alter fixed versions of bug #806588 to the same values 
previously set
> retitle -1 RM: conduit -- RoQA; depends on old libs, dead upstream, low 
> popcon, unmaintainer
Bug #806588 [ftp.debian.org] Should conduit be removed?
Changed Bug title to 'RM: conduit -- RoQA; depends on old libs, dead upstream, 
low popcon, unmaintainer' from 'Should conduit be removed?'
> severity -1 normal
Bug #806588 [ftp.debian.org] RM: conduit -- RoQA; depends on old libs, dead 
upstream, low popcon, unmaintainer
Severity set to 'normal' from 'serious'

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

Bug#807323: gparted needs policykit-1 but its neither in depends or recommends

[Phillip Susi]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 12/08/2015 04:49 AM, shirish शिरीष wrote:
> You would have to share the whole command, because I'm not so
> familiar with udisks2-inhibit. I tried to see if there was a
> manpage or something but came up nada :(

/usr/lib/udisks2/udisks2-inhibit true

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCgAGBQJWbLXMAAoJEBB5UWFcu6UWbsAH/ikeM8MRBYcdyW1uo9/mDVbH
lOzpAibZpxJt3TvsXhcVWVeH2X3Q2yzr6ksJkMAxqJLz/NMPAiKk97Y6/TpioZxc
HzfGTfZMsP3ScLmHNELNwzV0/7OCBd4zt9ZGWHDC+oI6li140tp7riCteoRe2DGl
iZ+q1S0f4oTmHX656oh2lTSJLbR8qnvxnndwp44vbWlxwJvlTKYhWmhQTomnpYO7
ZPcTDuZU3xwg+7hTvytkBY3uABJ/sx+RDraDORkULtkYj97tfPFzX/ffMpHLWDlN
w/HfZQeW8YHxEtu7g1ikzmhB3dv6NQKDvVgcaDG3nh+SEJ4O4xGO9cUp/gGD5mo=
=BWih
-END PGP SIGNATURE-