Processed: limit source to uw-imap, tagging 828589

[Debian Bug Tracking System]

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

> limit source uw-imap
Limiting to bugs with field 'source' containing at least one of 'uw-imap'
Limit currently set to 'source':'uw-imap'

> tags 828589 + pending
Bug #828589 [src:uw-imap] uw-imap: FTBFS with openssl 1.1.0
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: limit source to pike8.0, tagging 845146

[Debian Bug Tracking System]

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

> limit source pike8.0
Limiting to bugs with field 'source' containing at least one of 'pike8.0'
Limit currently set to 'source':'pike8.0'

> tags 845146 + pending
Bug #845146 [src:pike8.0] pike8.0: build-depends on heimdal-dev, which is to be 
removed from testing
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: limit source to uw-imap, tagging 828589

[Debian Bug Tracking System]

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

> limit source uw-imap
Limiting to bugs with field 'source' containing at least one of 'uw-imap'
Limit currently set to 'source':'uw-imap'

> tags 828589 + pending
Bug #828589 [src:uw-imap] uw-imap: FTBFS with openssl 1.1.0
Ignoring request to alter tags of bug #828589 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#844803: 844803 FTBFS: build-dependency not installable: libssl-dev

[Lucas Nussbaum]

On 21/11/16 at 16:25 +0100, Christoph Martin wrote:
> Hi Lucas,
> 
> please retry the build. Why should libssl-dev be not installable?
> 
> I can't see the problem in libapache2-mod-auth-openidc

As written in the bug report, builds are retried automatically once to
exclude random errors. Did you try to build it? Because it still fails,
so I'm surprised that you can't see the problem.
dose reports the following:

(I)Distcheck: Cudf Universe: 53096 packages
(I)Distcheck: --checkonly specified, consider all packages as background 
packages
(I)Distcheck: Solving...
output-version: 1.2
native-architecture: amd64
report:
 -
  package: sbuild-build-depends-libapache2-mod-auth-openidc-dummy
  version: 0.invalid.0
  architecture: amd64
  status: broken
  reasons:
   -
conflict:
 pkg1:
  package: libssl1.0-dev
  version: 1.0.2j-4
  architecture: amd64
  unsat-conflict: libssl-dev:amd64
 pkg2:
  package: libssl-dev
  version: 1.1.0c-2
  architecture: amd64
 depchain1:
  -
   depchain:
-
 package: sbuild-build-depends-libapache2-mod-auth-openidc-dummy
 version: 0.invalid.0
 architecture: amd64
 depends: apache2-dev:amd64
-
 package: apache2-dev
 version: 2.4.23-7
 architecture: amd64
 depends: libssl1.0-dev:amd64 | libssl-dev:amd64 (< 1.1)
 depchain2:
  -
   depchain:
-
 package: sbuild-build-depends-libapache2-mod-auth-openidc-dummy
 version: 0.invalid.0
 architecture: amd64
 depends: libssl-dev:amd64
 
background-packages: 53095
foreground-packages: 1
total-packages: 53096

Lucas

Processed: raise the bug level to RC for #836395

[Debian Bug Tracking System]

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

> severity 836395 grave
Bug #836395 [libopencc2] libopencc2: missing files cause librime fail to work
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Bug#845278:

[Adrian Bunk]

On Tue, Nov 22, 2016 at 12:01:16AM -0500, Paul R. Tagliamonte wrote:
> Yeah, same here on a sid system:
> 
> Preparing to unpack .../libxtables12_1.6.0+snapshot20161117-2_amd64.deb ...
> Unpacking libxtables12:amd64 (1.6.0+snapshot20161117-2) ...
> dpkg: error processing archive
> /var/cache/apt/archives/libxtables12_1.6.0+snapshot20161117-2_amd64.deb
> (--unpack):
>  trying to overwrite '/usr/lib/x86_64-linux-gnu/libxtables.so.12.0.0',
> which is also in package libxtables11:amd64 1.6.0+snapshot20161117-1
> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
> Errors were encountered while processing:
>  /var/cache/apt/archives/libxtables12_1.6.0+snapshot20161117-2_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> However, the old package wasn't used anymore, so a dpkg --purge
> libxtables11:amd64, and an apt-get install -f did the trick.
> 
> Seems like a Conflicts/Breaks might be best here, apt can just get rid
> of the other package.

Breaks+Replaces is the proper solution.

>   Paul

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: bug 845082 forwarded ito https://github.com/pydata/numexpr/issues/224

[Debian Bug Tracking System]

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

> forwarded 845082 https://github.com/pydata/numexpr/issues/224
Bug #845082 [src:numexpr] numexpr FTBFS on ppc64el: test failures
Set Bug forwarded-to-address to 'https://github.com/pydata/numexpr/issues/224'.
> thanks
Stopping processing here.

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

Processed: Version tracking fix

[Debian Bug Tracking System]

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

> found 828461 1:4.2.8p7+dfsg-4
Bug #828461 {Done: Kurt Roeckx } [src:ntp] ntp: FTBFS with 
openssl 1.1.0
Marked as found in versions ntp/1:4.2.8p7+dfsg-4.
> thanks
Stopping processing here.

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

Bug#845278:

[Paul R. Tagliamonte]

Yeah, same here on a sid system:

Preparing to unpack .../libxtables12_1.6.0+snapshot20161117-2_amd64.deb ...
Unpacking libxtables12:amd64 (1.6.0+snapshot20161117-2) ...
dpkg: error processing archive
/var/cache/apt/archives/libxtables12_1.6.0+snapshot20161117-2_amd64.deb
(--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libxtables.so.12.0.0',
which is also in package libxtables11:amd64 1.6.0+snapshot20161117-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libxtables12_1.6.0+snapshot20161117-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

However, the old package wasn't used anymore, so a dpkg --purge
libxtables11:amd64, and an apt-get install -f did the trick.

Seems like a Conflicts/Breaks might be best here, apt can just get rid
of the other package.

  Paul

Bug#845278: libxtables12: can't be installed

[Gabriel Filion]

Gabriel Filion:
> I've just exerienced the same during an upgrade of sid packages.
> 
> The only way to break out of this mess is to force the upgrade of the
> package with:
> 
> dpkg --force-overwrite -i
> /var/cache/apt/archives/libxtables12_1.6.0+snapshot20161117-2_amd64.deb
> 
> then it becomes possible to continue with the rest of the upgrade.
> 
> libxtables12 seems like it should have a "breaks: libxtables11", or
> replaces: (I'm not sure if the latter is actually appropriate in this
> situation)

Seems like this is not the only thing missing.

nftables is still depending on libxtables11. if I try to apt remove
libxtables11 after running the dpkg command above, I get:

The following packages will be REMOVED:
  libxtables11 nftables

so the upgrade to libxtables12 would be breaking nftables with the
correct dependency to break libxtables11



signature.asc
Description: OpenPGP digital signature

Bug#845278: libxtables12: can't be installed

[Gabriel Filion]

Hello,

I've just exerienced the same during an upgrade of sid packages.

The only way to break out of this mess is to force the upgrade of the
package with:

dpkg --force-overwrite -i
/var/cache/apt/archives/libxtables12_1.6.0+snapshot20161117-2_amd64.deb

then it becomes possible to continue with the rest of the upgrade.

libxtables12 seems like it should have a "breaks: libxtables11", or
replaces: (I'm not sure if the latter is actually appropriate in this
situation)



signature.asc
Description: OpenPGP digital signature

Bug#845278: libxtables12: can't be installed

[Christoph Anton Mitterer]

Package: libxtables12
Version: 1.6.0+snapshot20161117-2
Severity: grave
Justification: renders package unusable


Hi.

Unpacking libxtables12:amd64 (1.6.0+snapshot20161117-2) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-DBLJsg/0-libxtables12_1.6.0+snapshot20161117-2_amd64.deb 
(--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libxtables.so.12.0.0', which is 
also in package libxtables11:amd64 1.6.0+snapshot20161117-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


Cheers,
Chris.


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

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

Bug#844755: marked as done (iptables: bumped library version without soname change, breaking reverse dependencies)

[Debian Bug Tracking System]

Your message dated Tue, 22 Nov 2016 02:00:47 +
with message-id 
and subject line Bug#844755: fixed in iptables 1.6.0+snapshot20161117-2
has caused the Debian Bug report #844755,
regarding iptables: bumped library version without soname change, breaking 
reverse dependencies
to be marked as done.

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

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


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

Dear Maintainer,

with the latest libxtables11 in Debian stretch/sid connmand does not start any 
longer:

/usr/sbin/connmand -n
/usr/sbin/connmand: error while loading shared libraries: libxtables.so.11: 
cannot open shared object file: 1

This is since libxtables11 1.6.0+snapshot20161117-1, which installs 
libxtables.so.12:

/usr/lib/x86_64-linux-gnu# ls -la libxtables*
lrwxrwxrwx 1 root root20 Nov 18 17:55 libxtables.so.12 -> 
libxtables.so.12.0.0
-rw-r--r-- 1 root root 52088 Nov 17 11:46 libxtables.so.12.0.0

I would expect libxtables.so.11 in that path.

Thank you.


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

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

Versions of packages connman depends on:
ii  dbus 1.10.12-1
ii  init-system-helpers  1.46
ii  libc62.24-5
ii  libdbus-1-3  1.10.12-1
ii  libglib2.0-0 2.50.2-1
ii  libgnutls30  3.5.6-4
ii  libreadline7 7.0-1
ii  libxtables11 1.6.0+snapshot20161117-1
ii  lsb-base 9.20161101

Versions of packages connman recommends:
pn  bluez  
pn  ofono  
ii  wpasupplicant  2.5-2+v2.4-3+b1

Versions of packages connman suggests:
pn  indicator-network  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: iptables
Source-Version: 1.6.0+snapshot20161117-2

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

Debian distribution maintenance software
pp.
Arturo Borrero Gonzalez  (supplier of updated iptables 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Nov 2016 09:25:51 +0100
Source: iptables
Binary: iptables iptables-dev libxtables12 libxtables-dev libiptc0 libiptc-dev 
libip4tc0 libip4tc-dev libip6tc0 libip6tc-dev iptables-nftables-compat
Architecture: source amd64 all
Version: 1.6.0+snapshot20161117-2
Distribution: unstable
Urgency: medium
Maintainer: Arturo Borrero Gonzalez 
Changed-By: Arturo Borrero Gonzalez 
Description:
 iptables   - administration tools for packet filtering and NAT
 iptables-dev - transitional dummy package
 iptables-nftables-compat - iptables compat tools for nftables
 libip4tc-dev - Development files for libip4tc
 libip4tc0  - netfilter libip4tc library
 libip6tc-dev - Development files for libip6tc
 libip6tc0  - netfilter libip6tc library
 libiptc-dev - Development files for libiptc
 libiptc0   - netfilter libiptc library
 libxtables-dev - netfilter xtables library
 libxtables12 - netfilter xtables library
Closes: 844755
Changes:
 iptables (1.6.0+snapshot20161117-2) unstable; urgency=medium
 .
   * [146c602] libxtables: bump from libxtables11 to libxtables12 (Closes:
 #844755)
Checksums-Sha1:
 e945f1dc04b7f5235cc34d15572b46c1b7c7c61b 2897 
iptables_1.6.0+snapshot20161117-2.dsc
 0c183bdfbae539fe10a2503a9ab42e2b2763cb29 59780 
iptables_1.6.0+snapshot20161117-2.debian.tar.xz
 dfc9b61a538f6a6ff626e4bde583efa1615e0420 944614 
iptables-dbgsym_1.6.0+snapshot20161117-2_amd64.deb
 8c3f64d07ae082280ebbe6b6e9beecf1c38966a1 55432 
iptables-dev_1.6.0+snapshot20161117-2_all.deb
 a900278ed00bbc158881e6b0adae9c2b6af9eead 306800 
iptables-nftables-compat-dbgsym_1.6.0+snapshot20161117-2_amd64.deb
 

Bug#845171: wine-development: FTBFS: ld aborts or segfaults

[Jens Reyer]

On 21.11.2016 22:07, Michael Gilbert wrote:
> On Sun, Nov 20, 2016 at 9:16 PM, Jens Reyer wrote:
>> wine-development 1.9.22-1 (in stretch) built successfully on all
>> architectures when it was uploaded to unstable, but fails to
>> build in a stretch environment on i386 now (amd64 is still fine).
>> Exactly the same for 1.9.23-1 on i386 in a sid environment:
> 
> Hi Jens,
> 
> 1.9.23-1 built for me ok in a sid i386 chroot.  Can you clarify the
> setup where it fails?  Did you mean kfreebsd-i386?

Hi Mike

first off, it just built fine on debomatic-i386:
http://debomatic-i386.debian.net/distribution#unstable/wine-development/1.9.23-1/buildlog

And if I understood you correctly it also built fine for you *today*?

So it seems i386 is a local problem, for whatever reasons. If the
upcoming 1.9.24 will still build on the official buildd and noone else
can reproduce this, I'd say the i386 issue may be ignored (especially
for the stretch release). I'll update the bug metadata then.

But of course I need to figure this out here anyway.


I built with git-buildpackage for i386 (not kfreebsd-i386), on my usual
amd64 stretch/sid machine.

The failures began while using my old chroot (minimal base-sid-i386.cow
with only wine build-deps installed). But I now created a new one and
deleted the ccache. It still fails with the same error message when I do
this:

$ DIST=sid ARCH=i386 git pbuilder create
$ DIST=sid ARCH=amd64 git pbuilder update --override-config
$ gbp buildpackage -B \
--git-pbuilder \
--git-arch=i386 \
--git-dist=sid \
--git-upstream-tag="wine-%(version)s"


Similarly 1.9.22-1 failed with a fresh minimal base-stretch-i386.cow,
and ccache deleted.

Both 1.9.22-1 and 1.9.23-1 built fine here with gbp in the past, but
fail now (with an updated chroot).



> A recent change to binutils adds -Wl,--enable-new-dtags by default.
> That may be the cause of the problem on arm.

Unfortunately no, see the buildlogs at
https://buildd.debian.org/status/package.php?p=wine-development:

1.9.23-1 failed to build on Nov 13 (armel), and Nov 14 (armhf).
The binutils change "ld: enable new dtags by default for linux/gnu
targets.  Closes: #835859." was only uploaded on Nov 17.

1.9.23-1 failed with binutils_2.27.51.20161108-1 (armel and armhf)
1.9.22-1 built  with binutils_2.27-9+b1 (armel and armhf)


> The i386 and arm failures are probably different issues.

Ok, I'll try to look into the arm problem separately then. If I don't
find a solution soon, I'll file a separate bug for that.

btw, debomatic-...debian.net works like a charm for testing this.

Greets
jre

Bug#844300: nvidia-driver-libs:amd64: upgrade failure due to dependency issue

[Luca Boccassi]

Control: severity -1 normal

On Mon, 2016-11-14 at 16:20 +0100, Vincent Lefevre wrote:
> On 2016-11-14 15:52:28 +0100, Diederik de Haas wrote:
> > On maandag 14 november 2016 15:12:14 CET Vincent Lefevre wrote:
> > > aptitude often ignores Recommends. So, you should not rely on it.
> > 
> > That's an incorrect statement.
> > Aptitude, and I think apt too, doesn't automatically install _new_ 
> > recommended 
> > packages for an already installed package. 
> > It does report "The following recommended packages will not be installed" 
> > (or 
> > sth along those lines). But that's far from ignoring it.
> 
> No, I do not always get these reports. Here I didn't even have any
> report that a recommended package would be removed: aptitude just
> said that  would be removed because they are
> no longer used.

I can't manage to reproduce this.

In the end, you shouldn't have let aptitude remove the packages. It can
happen from time to time on unstable to have temporary inconsistent
state in the apt tree (that's why it's called unstable), for example in
this case it was probably because the new amd64 version was up in the
repo but the i386 was still being built/published.

The solution is simply to reinstall what was removed, so there's nothing
that justifies holding he migration of 367.57-2 to stretch, which just
adds a patch to make it compatible with newer kernels which are about to
be uploaded and nothing else, so severity downgraded.

Kind regards,
Luca Boccassi


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

Processed: Re: Bug#844300: nvidia-driver-libs:amd64: upgrade failure due to dependency issue

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #844300 [nvidia-driver-libs] nvidia-driver-libs:amd64: upgrade failure due 
to dependency issue
Severity set to 'normal' from 'grave'

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

Bug#842806: docker.io: Can't connect to the daemon

[Tianon Gravi]

severity 842806 important
thanks

On 21 November 2016 at 00:18, Kurt Roeckx  wrote:
> It's not installed.

So, does installing "cgroupfs-mount" (and making sure the "service" is
started from its init script) fix the issue with Docker? :)

>> Any objections to lowering the severity of this bug?  This sounds like
>> a system configuration issue, not necessarily a package-level issue,
>> so the most we could do is maybe fuddle Depends or add a blurb in
>> README.Debian. :(
>
> Yes, sounds fine for me.

Thanks! <3


♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Processed: Re: Bug#842806: docker.io: Can't connect to the daemon

[Debian Bug Tracking System]

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

> severity 842806 important
Bug #842806 [docker.io] docker.io: Can't connect to the daemon
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: Re: dmg2img: FTBFS with openssl 1.1.0

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #828282 [src:dmg2img] dmg2img: FTBFS with openssl 1.1.0
Added tag(s) patch.

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

Bug#828282: dmg2img: FTBFS with openssl 1.1.0

[Reiner Herrmann]

Control: tags -1 + patch

Hi,

attached is a patch which allows building dmg2img with OpenSSL 1.1.

Regards,
  Reiner
diff --git a/debian/patches/openssl1.1.patch b/debian/patches/openssl1.1.patch
new file mode 100644
index 000..1207664
--- /dev/null
+++ b/debian/patches/openssl1.1.patch
@@ -0,0 +1,142 @@
+Author: Reiner Herrmann 
+Description: Fix building with OpenSSL 1.1
+
+--- a/vfdecrypt.c
 b/vfdecrypt.c
+@@ -183,7 +183,7 @@
+   pwhdr->encrypted_keyblob_size = htonl(pwhdr->encrypted_keyblob_size);
+ }
+ 
+-HMAC_CTX hmacsha1_ctx;
++HMAC_CTX *hmacsha1_ctx = NULL;
+ AES_KEY aes_decrypt_key;
+ int CHUNK_SIZE=4096;  // default
+ 
+@@ -196,9 +196,9 @@
+   unsigned int mdLen;
+   
+   chunk_no = OSSwapHostToBigInt32(chunk_no);
+-  HMAC_Init_ex(_ctx, NULL, 0, NULL, NULL);
+-  HMAC_Update(_ctx, (void *) _no, sizeof(uint32_t));
+-  HMAC_Final(_ctx, mdResult, );
++  HMAC_Init_ex(hmacsha1_ctx, NULL, 0, NULL, NULL);
++  HMAC_Update(hmacsha1_ctx, (void *) _no, sizeof(uint32_t));
++  HMAC_Final(hmacsha1_ctx, mdResult, );
+   memcpy(iv, mdResult, CIPHER_BLOCKSIZE);
+ }
+ 
+@@ -212,47 +212,47 @@
+ /* DES3-EDE unwrap operation loosely based on to RFC 2630, section 12.6 
+  *wrapped_key has to be 40 bytes in length.  */
+ int apple_des3_ede_unwrap_key(uint8_t *wrapped_key, int wrapped_key_len, uint8_t *decryptKey, uint8_t *unwrapped_key) {
+-  EVP_CIPHER_CTX ctx;
++  EVP_CIPHER_CTX *ctx;
+   uint8_t *TEMP1, *TEMP2, *CEKICV;
+   uint8_t IV[8] = { 0x4a, 0xdd, 0xa2, 0x2c, 0x79, 0xe8, 0x21, 0x05 };
+   int outlen, tmplen, i;
+ 
+-  EVP_CIPHER_CTX_init();
++  ctx = EVP_CIPHER_CTX_new();
+   /* result of the decryption operation shouldn't be bigger than ciphertext */
+   TEMP1 = malloc(wrapped_key_len);
+   TEMP2 = malloc(wrapped_key_len);
+   CEKICV = malloc(wrapped_key_len);
+   /* uses PKCS#7 padding for symmetric key operations by default */
+-  EVP_DecryptInit_ex(, EVP_des_ede3_cbc(), NULL, decryptKey, IV);
++  EVP_DecryptInit_ex(ctx, EVP_des_ede3_cbc(), NULL, decryptKey, IV);
+ 
+-  if(!EVP_DecryptUpdate(, TEMP1, , wrapped_key, wrapped_key_len)) {
++  if(!EVP_DecryptUpdate(ctx, TEMP1, , wrapped_key, wrapped_key_len)) {
+ fprintf(stderr, "internal error (1) during key unwrap operation!\n");
+ return(-1);
+   }
+-  if(!EVP_DecryptFinal_ex(, TEMP1 + outlen, )) {
++  if(!EVP_DecryptFinal_ex(ctx, TEMP1 + outlen, )) {
+ fprintf(stderr, "internal error (2) during key unwrap operation!\n");
+ return(-1);
+   }
+   outlen += tmplen;
+-  EVP_CIPHER_CTX_cleanup();
++  EVP_CIPHER_CTX_free(ctx);
+ 
+   /* reverse order of TEMP3 */
+   for(i = 0; i < outlen; i++) TEMP2[i] = TEMP1[outlen - i - 1];
+ 
+-  EVP_CIPHER_CTX_init();
++  ctx = EVP_CIPHER_CTX_new();
+   /* uses PKCS#7 padding for symmetric key operations by default */
+-  EVP_DecryptInit_ex(, EVP_des_ede3_cbc(), NULL, decryptKey, TEMP2);
+-  if(!EVP_DecryptUpdate(, CEKICV, , TEMP2+8, outlen-8)) {
++  EVP_DecryptInit_ex(ctx, EVP_des_ede3_cbc(), NULL, decryptKey, TEMP2);
++  if(!EVP_DecryptUpdate(ctx, CEKICV, , TEMP2+8, outlen-8)) {
+ fprintf(stderr, "internal error (3) during key unwrap operation!\n");
+ return(-1);
+   }
+-  if(!EVP_DecryptFinal_ex(, CEKICV + outlen, )) {
++  if(!EVP_DecryptFinal_ex(ctx, CEKICV + outlen, )) {
+ fprintf(stderr, "internal error (4) during key unwrap operation!\n");
+ return(-1);
+   }
+ 
+   outlen += tmplen;
+-  EVP_CIPHER_CTX_cleanup();
++  EVP_CIPHER_CTX_free(ctx);
+ 
+   memcpy(unwrapped_key, CEKICV+4, outlen-4);
+   free(TEMP1);
+@@ -279,7 +279,7 @@
+ int unwrap_v2_header(char *passphrase, cencrypted_v2_pwheader *header, uint8_t *aes_key, uint8_t *hmacsha1_key) {
+   /* derived key is a 3DES-EDE key */
+   uint8_t derived_key[192/8];
+-  EVP_CIPHER_CTX ctx;
++  EVP_CIPHER_CTX *ctx;
+   uint8_t *TEMP1;
+   int outlen, tmplen;
+ 
+@@ -288,22 +288,22 @@
+ 
+   print_hex(derived_key, 192/8);
+ 
+-  EVP_CIPHER_CTX_init();
++  ctx = EVP_CIPHER_CTX_new();
+   /* result of the decryption operation shouldn't be bigger than ciphertext */
+   TEMP1 = malloc(header->encrypted_keyblob_size);
+   /* uses PKCS#7 padding for symmetric key operations by default */
+-  EVP_DecryptInit_ex(, EVP_des_ede3_cbc(), NULL, derived_key, header->blob_enc_iv);
++  EVP_DecryptInit_ex(ctx, EVP_des_ede3_cbc(), NULL, derived_key, header->blob_enc_iv);
+ 
+-  if(!EVP_DecryptUpdate(, TEMP1, , header->encrypted_keyblob, header->encrypted_keyblob_size)) {
++  if(!EVP_DecryptUpdate(ctx, TEMP1, , header->encrypted_keyblob, header->encrypted_keyblob_size)) {
+ fprintf(stderr, "internal error (1) during key unwrap operation!\n");
+ return(-1);
+   }
+-  if(!EVP_DecryptFinal_ex(, TEMP1 + outlen, )) {
++  if(!EVP_DecryptFinal_ex(ctx, TEMP1 + outlen, )) {
+ fprintf(stderr, "internal error (2) during key unwrap operation!\n");
+ return(-1);
+   }
+   outlen += tmplen;
+-  EVP_CIPHER_CTX_cleanup();
++  EVP_CIPHER_CTX_free(ctx);
+   memcpy(aes_key, TEMP1, 16);
+   memcpy(hmacsha1_key, TEMP1, 20);
+ 
+@@ 

Processed: Re: Bug#817236: schroot: no access to pseudo-terminals in new chroots

[Debian Bug Tracking System]

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

> reassign 817236 debootstrap 1.0.85
Bug #817236 [schroot] schroot: no access to pseudo-terminals in new chroots
Bug reassigned from package 'schroot' to 'debootstrap'.
No longer marked as found in versions schroot/1.6.10-2.
Ignoring request to alter fixed versions of bug #817236 to the same values 
previously set
Bug #817236 [debootstrap] schroot: no access to pseudo-terminals in new chroots
Marked as found in versions debootstrap/1.0.85.
> reassign 841935 debootstrap
Bug #841935 [pbuilder] pbuilder: incorrect permissions on /dev/ptmx breaks 
openpty()
Bug reassigned from package 'pbuilder' to 'debootstrap'.
No longer marked as found in versions pbuilder/0.226.1.
Ignoring request to alter fixed versions of bug #841935 to the same values 
previously set
> forcemerge 817236 841935
Bug #817236 [debootstrap] schroot: no access to pseudo-terminals in new chroots
Bug #841935 [debootstrap] pbuilder: incorrect permissions on /dev/ptmx breaks 
openpty()
Severity set to 'important' from 'normal'
829299 was blocked by: 817236
829299 was not blocking any bugs.
Added blocking bug(s) of 829299: 841935
Marked as found in versions debootstrap/1.0.85.
Bug #817236 [debootstrap] schroot: no access to pseudo-terminals in new chroots
Added tag(s) patch.
Merged 817236 841935
> affects 817236 pbuilder sbuild schroot
Bug #817236 [debootstrap] schroot: no access to pseudo-terminals in new chroots
Bug #841935 [debootstrap] pbuilder: incorrect permissions on /dev/ptmx breaks 
openpty()
Added indication that 817236 affects pbuilder, sbuild, and schroot
Added indication that 841935 affects pbuilder, sbuild, and schroot
> stop
Stopping processing here.

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

Bug#845037: libschroedinger-1.0-0: is this package fit for stretch?

[Andreas Cadhalpun]

Hi Sebastian,

On 21.11.2016 08:22, Sebastian Dröge wrote:
> On Sun, 2016-11-20 at 11:57 +0100, Moritz Muehlenhoff wrote:
> 
>>> Thus I think stretch would be better of without this library.
>>>
>>> As replacement, ffmpeg has a decent dirac decoder and also a
>>> vc2 encoder, which is the intra-only subset of dirac that
>>> got standardized by the SMPTE.
>>
>> Andreas, thanks for filing this bug. Fully agreed from my side.
> 
> I tend to agree here.

OK, then it's agreed to remove libschroedinger.

> Note however that VC2 is only a subset of Dirac,
> so we'll definitely lose some (probably unimportant) functionality
> here.

That's true, but I also think that the functionality going to be lost
is rather unimportant.

> Current reverse dependencies are
>  ffmpeg
>  gmerlin-avdecoder
>  gst-plugins-bad1.0
>  libquicktime
>  liquidsoap
>  lives
>  ocaml-schroedinger
>  vlc

There is also mplayer, which has a build-dependency on libschroedinger-dev,
however no run-time dependency due to:
Checking for libschroedinger ... no (ffmpeg (static) is required by 
libschroedinger, sorry)

> Except for the ocaml bindings, this should all be a matter of simply
> disabling the functionality.

Yes. The ocaml bindings have a very low popcon (14), so I think it's
OK to just remove them together with libschroedinger.

I will take care of ffmpeg myself and I assume you will take care of
gst-plugins-bad1.0.
I intend to file bugs for the other packages and block this bug by
them.

Best regards,
Andreas

Processed: forwarded 844303 https://github.com/nmap/ncrack/issues/15

[Debian Bug Tracking System]

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

> forwarded 844303 https://github.com/nmap/ncrack/issues/15
Bug #844303 [src:ncrack] ncrack: FTBFS: configure:6846: error: ./configure 
failed for opensshlib
Set Bug forwarded-to-address to 'https://github.com/nmap/ncrack/issues/15'.
>
End of message, stopping processing here.

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

Bug#725768: And now with the patch, sorry

[Martin Quinson]

Index: j/tkcvs-8.2.3/debian/control
===
--- j.orig/tkcvs-8.2.3/debian/control
+++ j/tkcvs-8.2.3/debian/control
@@ -8,7 +8,7 @@ Build-Depends: debhelper (>= 7.0.0)
 
 Package: tkcvs
 Architecture: all
-Depends: cvs | subversion, tk8.4 | tk8.5, ttf-dejavu, ${misc:Depends}
+Depends: cvs | subversion, tk (>=8.4), ttf-dejavu, ${misc:Depends}
 Replaces: tkdiff
 Provides: tkdiff
 Recommends: xterm | x-terminal-emulator, dirdiff
Index: j/tkcvs-8.2.3/debian/control
===
--- j.orig/tkcvs-8.2.3/debian/control
+++ j/tkcvs-8.2.3/debian/control
@@ -8,7 +8,7 @@ Build-Depends: debhelper (>= 7.0.0)
 
 Package: tkcvs
 Architecture: all
-Depends: cvs | subversion, tk8.4 | tk8.5, ttf-dejavu, ${misc:Depends}
+Depends: cvs | subversion, tk (>=8.4), ttf-dejavu, ${misc:Depends}
 Replaces: tkdiff
 Provides: tkdiff
 Recommends: xterm | x-terminal-emulator, dirdiff


signature.asc
Description: PGP signature

Processed (with 1 error): Moving ipython bug to python-backports-shutil-get-terminal-size and reducing severity

[Debian Bug Tracking System]

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

> reassign 843898 python-backports-shutil-get-terminal-size
Bug #843898 [ipython] IPython 2 launch fails with "No module named 
shutil_get_terminal_size"
Bug reassigned from package 'ipython' to 
'python-backports-shutil-get-terminal-size'.
No longer marked as found in versions ipython/5.1.0-2.
Ignoring request to alter fixed versions of bug #843898 to the same values 
previously set
> severity 843898 wishlist
Bug #843898 [python-backports-shutil-get-terminal-size] IPython 2 launch fails 
with "No module named shutil_get_terminal_size"
Severity set to 'wishlist' from 'grave'
> affects 843898 ipython
Bug #843898 [python-backports-shutil-get-terminal-size] IPython 2 launch fails 
with "No module named shutil_get_terminal_size"
Added indication that 843898 affects ipython
> found 843898 1.0.0-3
Bug #843898 [python-backports-shutil-get-terminal-size] IPython 2 launch fails 
with "No module named shutil_get_terminal_size"
Marked as found in versions python-backports-shutil-get-terminal-size/1.0.0-3.
> retitle 843898 python-backports-shutil-get-terminal-size: could be more
Bug #843898 [python-backports-shutil-get-terminal-size] IPython 2 launch fails 
with "No module named shutil_get_terminal_size"
Changed Bug title to 'python-backports-shutil-get-terminal-size: could be more' 
from 'IPython 2 launch fails with "No module named shutil_get_terminal_size"'.
> robust against user-installed packages hijacking the backports module
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#812280: Fix/Workaround for the newmat FTBFS

[Robert Davies]

I have made a fix to the code but haven't tested it yet on all compilers.
There is one other problem that gives a lot of warnings with
some compilers that I am still trying to understand.

One wants to switch to C++14 if one possibly can.

What do I need to do when I am satisfied with the updated version?

Robert



At 10:07 AM 22/11/2016, Adrian Bunk wrote:


Control: tags -1 patch

What broke the build is that gcc 6 changed the default C++ standard
from C++98 to C++14.

Not all valid C++98 code is also valid C++11 and C++14 code.

Note that this just changed the default, when told to process C++98 code
gcc 6 does not differ in any significant way from gcc 5.

Making the code compatible with C++14 would be the best possible
solution, but as a workaround it is possible to fix the build with
this change to tell gcc that this is C++98 code.

CXXFLAGS set in debian/rules were not used at all, this is also fixed.

--- debian/rules.old2016-11-21 21:00:13.0 +
+++ debian/rules2016-11-21 21:02:13.0 +
@@ -15,6 +15,8 @@
CXXFLAGS += -O2
 endif

+CXXFLAGS += -std=gnu++98
+
 # shared library versions,
 version=`ls src/.libs/lib*.so.* | \
 awk '{if (match($$0,/[0-9]+\.[0-9]+\.[0-9]+$$/)) print substr($$0,RSTART)}'`
@@ -33,7 +35,7 @@

 configure-stamp: config-stamp
dh_testdir
-   CFLAGS="$(CFLAGS) -Wl,-z,defs" \
+   CXXFLAGS="$(CXXFLAGS)" CFLAGS="$(CFLAGS) -Wl,-z,defs" \
./configure --host=$(DEB_HOST_GNU_TYPE) \
--build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr \
--mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info


cu
Adrian

--

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#844909: marked as done (python-trollius: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 21:50:11 +
with message-id 
and subject line Bug#844234: fixed in openssl 1.1.0c-2
has caused the Debian Bug report #844234,
regarding python-trollius: FTBFS: Tests failures
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.)


-- 
844234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-trollius
Version: 2.1~b1-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> data = self.loop.run_until_complete(f)
>   File "/<>/trollius/base_events.py", line 350, in 
> run_until_complete
> return future.result()
>   File "/<>/trollius/futures.py", line 285, in result
> compat.reraise(type(self._exception), self._exception, exc_tb)
>   File "/<>/trollius/tasks.py", line 259, in _step
> result = coro.send(value)
>   File "/<>/trollius/streams.py", line 464, in read
> raise self._exception
> socket.error: [Errno 0] Error
> 
> --
> Ran 905 tests in 9.564s
> 
> FAILED (errors=2, skipped=1)
> debian/rules:24: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/python-trollius_2.1~b1-4_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: openssl
Source-Version: 1.1.0c-2

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

Debian distribution maintenance software
pp.
Kurt Roeckx  (supplier of updated openssl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Nov 2016 22:20:00 +0100
Source: openssl
Binary: openssl libssl1.1 libcrypto1.1-udeb libssl1.1-udeb libssl-dev 
libssl-doc libssl1.1-dbg
Architecture: source
Version: 1.1.0c-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenSSL Team 
Changed-By: Kurt Roeckx 
Description:
 libcrypto1.1-udeb - Secure Sockets Layer toolkit - libcrypto udeb (udeb)
 libssl-dev - Secure Sockets Layer toolkit - development files
 libssl-doc - Secure Sockets Layer toolkit - development documentation
 libssl1.1  - Secure Sockets Layer toolkit - shared libraries
 libssl1.1-dbg - Secure Sockets Layer toolkit - debug information
 libssl1.1-udeb - ssl shared library - udeb (udeb)
 openssl- Secure Sockets Layer toolkit - cryptographic utility
Closes: 844234 844715
Changes:
 openssl (1.1.0c-2) unstable; urgency=medium
 .
   * Revert behaviour of SSL_read() and SSL_write(), and update documentation.
 (Closes: #844234)
   * Add missing -zdelete on x32 (Closes: #844715)
   * Add a Breaks on salt-common. Addresses #844706
Checksums-Sha1:
 7e26a7d98166e6c8d0d0d50ca2dc989942de14af 2552 openssl_1.1.0c-2.dsc
 5b0556f53c427e14e660151b56b82d40dba65967 55392 openssl_1.1.0c-2.debian.tar.xz
Checksums-Sha256:
 a6ca664b8443ad1ed01cc90a9c8d8af8a079efa471536ec971a1bf2f5b8253a0 2552 
openssl_1.1.0c-2.dsc
 c47b1d2df11b061243bf91ecd95130840ebe7e6a84a6bf1b063d1953e9fddda5 55392 
openssl_1.1.0c-2.debian.tar.xz
Files:
 5a5f07499eb6dda464b325bda91f6a89 2552 utils optional openssl_1.1.0c-2.dsc
 60826b6aa69cd73a00c810f29a37bfe8 55392 utils optional 
openssl_1.1.0c-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYM2qCAAoJEOPE3c0eTBJEMpgP/itd/WDBSUqFLrjcYNXqwxNy
5eOhMC3o3Qmr63/vWjTM/vC284IgpHW3rfv5fJ1oZ8t07DtDdbVeqP3MzsZGsVcM

Bug#844234: marked as done (libssl1.1: 1.1.0c broke Python)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 21:50:11 +
with message-id 
and subject line Bug#844234: fixed in openssl 1.1.0c-2
has caused the Debian Bug report #844234,
regarding libssl1.1: 1.1.0c broke Python
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.)


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

python-eventlet fails to build from source in unstable/amd64:

  […]

  verify_hub_empty()
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 244, in verify_hub_empty
  ', '.join(map(format_listener, writers)), num_writers,
  AssertionError: Readers: Listener FdListener('read', 19, , ) for greenlet  with run callback None (1) Writers:  (0)
  
  ==
  ERROR: test_count (tests.zmq_test.TestQueueLock)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 189, in tearDown
  verify_hub_empty()
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 244, in verify_hub_empty
  ', '.join(map(format_listener, writers)), num_writers,
  AssertionError: Readers: Listener FdListener('read', 19, , ) for greenlet  with run callback None (1) Writers:  (0)
  
  ==
  ERROR: test_errors (tests.zmq_test.TestQueueLock)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 189, in tearDown
  verify_hub_empty()
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 244, in verify_hub_empty
  ', '.join(map(format_listener, writers)), num_writers,
  AssertionError: Readers: Listener FdListener('read', 19, , ) for greenlet  with run callback None (1) Writers:  (0)
  
  ==
  ERROR: test_nested_acquire (tests.zmq_test.TestQueueLock)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 189, in tearDown
  verify_hub_empty()
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 244, in verify_hub_empty
  ', '.join(map(format_listener, writers)), num_writers,
  AssertionError: Readers: Listener FdListener('read', 19, , ) for greenlet  with run callback None (1) Writers:  (0)
  
  ==
  ERROR: test_queue_lock_order (tests.zmq_test.TestQueueLock)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 189, in tearDown
  verify_hub_empty()
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 244, in verify_hub_empty
  ', '.join(map(format_listener, writers)), num_writers,
  AssertionError: Readers: Listener FdListener('read', 19, , ) for greenlet  with run callback None (1) Writers:  (0)
  
  ==
  ERROR: test_change_subscription (tests.zmq_test.TestUpstreamDownStream)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 95, in wrapped
  return func(*a, **kw)
File 

Bug#844907: marked as done (libssl1.1: 1.1.0c broke Python)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 21:50:11 +
with message-id 
and subject line Bug#844234: fixed in openssl 1.1.0c-2
has caused the Debian Bug report #844234,
regarding libssl1.1: 1.1.0c broke Python
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.)


-- 
844234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-tornado
Version: 4.4.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> 
> --
> Ran 1463 tests in 10.780s
> 
> FAILED (failures=1, errors=7, skipped=57)
> Some tests were skipped because: PEP 380 (yield from) not available,
> PEP 492 (async/await) not available, Prevent internet access during
> build, asyncio module not present, curl client accepts invalid
> headers, localhost does not resolve to ipv6, needs fix, non-windows
> platform, pycares module not present, timing tests unreliable on
> travis, tornado.speedups module not present
> [E 161118 23:29:11 testing:735] FAIL
> [E 161118 23:29:11 runtests:182] logged 17 warnings and 2 errors
> E: pybuild pybuild:276: test: plugin custom failed with: exit code=1: 
> python2.7 ./tornado/test/runtests.py --verbose
> dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
> debian/rules:14: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/python-tornado_4.4.2-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: openssl
Source-Version: 1.1.0c-2

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

Debian distribution maintenance software
pp.
Kurt Roeckx  (supplier of updated openssl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Nov 2016 22:20:00 +0100
Source: openssl
Binary: openssl libssl1.1 libcrypto1.1-udeb libssl1.1-udeb libssl-dev 
libssl-doc libssl1.1-dbg
Architecture: source
Version: 1.1.0c-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenSSL Team 
Changed-By: Kurt Roeckx 
Description:
 libcrypto1.1-udeb - Secure Sockets Layer toolkit - libcrypto udeb (udeb)
 libssl-dev - Secure Sockets Layer toolkit - development files
 libssl-doc - Secure Sockets Layer toolkit - development documentation
 libssl1.1  - Secure Sockets Layer toolkit - shared libraries
 libssl1.1-dbg - Secure Sockets Layer toolkit - debug information
 libssl1.1-udeb - ssl shared library - udeb (udeb)
 openssl- Secure Sockets Layer toolkit - cryptographic utility
Closes: 844234 844715
Changes:
 openssl (1.1.0c-2) unstable; urgency=medium
 .
   * Revert behaviour of SSL_read() and SSL_write(), and update documentation.
 (Closes: #844234)
   * Add missing -zdelete on x32 (Closes: #844715)
   * Add a Breaks on salt-common. Addresses #844706
Checksums-Sha1:
 7e26a7d98166e6c8d0d0d50ca2dc989942de14af 2552 openssl_1.1.0c-2.dsc
 5b0556f53c427e14e660151b56b82d40dba65967 55392 openssl_1.1.0c-2.debian.tar.xz
Checksums-Sha256:
 a6ca664b8443ad1ed01cc90a9c8d8af8a079efa471536ec971a1bf2f5b8253a0 2552 
openssl_1.1.0c-2.dsc
 c47b1d2df11b061243bf91ecd95130840ebe7e6a84a6bf1b063d1953e9fddda5 55392 
openssl_1.1.0c-2.debian.tar.xz
Files:
 5a5f07499eb6dda464b325bda91f6a89 2552 utils optional openssl_1.1.0c-2.dsc
 60826b6aa69cd73a00c810f29a37bfe8 55392 utils optional 

Bug#844366: marked as done (libssl1.1: 1.1.0c broke Python)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 21:50:11 +
with message-id 
and subject line Bug#844234: fixed in openssl 1.1.0c-2
has caused the Debian Bug report #844234,
regarding libssl1.1: 1.1.0c broke Python
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.)


-- 
844234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libssl1.1
Version: 1.1.0c-1
Severity: critical
Tags: upstream
Justification: breaks unrelated software

Hi,

update to 1.1.0c broke Python ssl wrapper. I have first faced the issue
with offlineimap, which would crash with the [Errno 0] Error and the
following stack-trace when trying to refresh OAuth2 token from google:

Traceback:
  File "/usr/share/offlineimap/offlineimap/accounts.py", line 271, in syncrunner
self.__sync()
  File "/usr/share/offlineimap/offlineimap/accounts.py", line 334, in __sync
remoterepos.getfolders()
  File "/usr/share/offlineimap/offlineimap/repository/IMAP.py", line 452, in 
getfolders
imapobj = self.imapserver.acquireconnection()
  File "/usr/share/offlineimap/offlineimap/imapserver.py", line 540, in 
acquireconnection
self.__authn_helper(imapobj)
  File "/usr/share/offlineimap/offlineimap/imapserver.py", line 406, in 
__authn_helper
if func(imapobj):
  File "/usr/share/offlineimap/offlineimap/imapserver.py", line 340, in 
__authn_xoauth2
imapobj.authenticate('XOAUTH2', self.__xoauth2handler)
  File "/usr/lib/python2.7/dist-packages/imaplib2.py", line 705, in authenticate
typ, dat = self._simple_command('AUTHENTICATE', mechanism.upper())
  File "/usr/lib/python2.7/dist-packages/imaplib2.py", line 1692, in 
_simple_command
return self._command_complete(self._command(name, *args), kw)
  File "/usr/lib/python2.7/dist-packages/imaplib2.py", line 1418, in _command
literal = literator(data, rqb)
  File "/usr/lib/python2.7/dist-packages/imaplib2.py", line 2283, in process
ret = self.mech(self.decode(data))
  File "/usr/share/offlineimap/offlineimap/imapserver.py", line 239, in 
__xoauth2handler
six.reraise(type(e), type(e)(msg), exc_info()[2])
  File "/usr/share/offlineimap/offlineimap/imapserver.py", line 233, in 
__xoauth2handler
self.oauth2_request_url, urllib.urlencode(params)).read()
  File "/usr/lib/python2.7/socket.py", line 355, in read
data = self._sock.recv(rbufsize)
  File "/usr/lib/python2.7/ssl.py", line 766, in recv
return self.read(buflen)
  File "/usr/lib/python2.7/ssl.py", line 653, in read
v = self._sslobj.read(len)

These seem to be relevant upstream bugs:

  * https://github.com/openssl/openssl/issues/1919 (which was merged to 1903)
  * https://github.com/openssl/openssl/issues/1903

Downgrading to 1.1.0b (by installing libssl1.1_1.1.0b-2_amd64.deb from
snapshots) resolves the issue (and introduces back the vulnerability).

Best,

  Antonin

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

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

Versions of packages libssl1.1 depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  libc6  2.24-5

libssl1.1 recommends no packages.

libssl1.1 suggests no packages.

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: openssl
Source-Version: 1.1.0c-2

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

Debian distribution maintenance software
pp.
Kurt Roeckx  (supplier of updated openssl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Nov 2016 22:20:00 +0100
Source: openssl
Binary: openssl libssl1.1 libcrypto1.1-udeb libssl1.1-udeb libssl-dev 
libssl-doc libssl1.1-dbg
Architecture: source
Version: 1.1.0c-2
Distribution: unstable
Urgency: 

Bug#844931: marked as done (python-dugong: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.5 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 21:50:11 +
with message-id 
and subject line Bug#844234: fixed in openssl 1.1.0c-2
has caused the Debian Bug report #844234,
regarding python-dugong: FTBFS: dh_auto_test: pybuild --test -i python{version} 
-p 3.5 returned exit code 13
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.)


-- 
844234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-dugong
Version: 3.7+dfsg-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 '/<>/python-dugong-3.7+dfsg'
> dh_auto_build
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/python-dugong-3.7+dfsg/.pybuild/pythonX.Y_3.5/build/dugong
> copying ./dugong/__init__.py -> 
> /<>/python-dugong-3.7+dfsg/.pybuild/pythonX.Y_3.5/build/dugong
> # Build docs
> python3 setup.py build_sphinx
> running build_sphinx
> creating /<>/python-dugong-3.7+dfsg/doc/doctrees
> creating /<>/python-dugong-3.7+dfsg/doc/html
> Running Sphinx v1.4.8
> loading pickled environment... not yet created
> loading intersphinx inventory from ../debian/python.inv...
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 7 source files that are out of date
> updating environment: 7 added, 0 changed, 0 removed
> reading sources... [ 14%] api
> reading sources... [ 28%] coroutines
> reading sources... [ 42%] index
> reading sources... [ 57%] intro
> reading sources... [ 71%] issues
> reading sources... [ 85%] tutorial
> reading sources... [100%] whatsnew
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 14%] api
> writing output... [ 28%] coroutines
> writing output... [ 42%] index
> writing output... [ 57%] intro
> writing output... [ 71%] issues
> writing output... [ 85%] tutorial
> writing output... [100%] whatsnew
> 
> /<>/python-dugong-3.7+dfsg/rst/api.rst:35: WARNING: py:obj 
> reference target not found: ssl.SSLSocket
> generating indices... genindex
> writing additional pages... search
> copying static files... done
> copying extra files... done
> dumping search index in English (code: en) ... done
> dumping object inventory... done
> build succeeded, 1 warning.
> make[1]: Leaving directory '/<>/python-dugong-3.7+dfsg'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:184: cd 
> /<>/python-dugong-3.7+dfsg/.pybuild/pythonX.Y_3.5/build; python3.5 
> -m pytest --installed "/<>/python-dugong-3.7+dfsg/test/"
> = test session starts 
> ==
> platform linux -- Python 3.5.2+, pytest-3.0.3, py-1.4.31, pluggy-0.4.0 -- 
> /usr/bin/python3.5
> cachedir: ../../../test/.cache
> rootdir: /<>/python-dugong-3.7+dfsg/test, inifile: pytest.ini
> plugins: catchlog-1.2.2
> collecting ... collected 118 items
> 
> ../../../test/test_aio.py::test_aio_future PASSED
> ../../../test/test_dugong.py::test_connect_ssl SKIPPED
> ../../../test/test_dugong.py::test_invalid_ssl SKIPPED
> ../../../test/test_dugong.py::test_dns_one PASSED
> ../../../test/test_dugong.py::test_dns_two PASSED
> ../../../test/test_dugong.py::test_http_proxy[plain-None] PASSED
> ../../../test/test_dugong.py::test_http_proxy[plain-8080] PASSED
> ../../../test/test_dugong.py::test_connect_proxy[plain-None] PASSED
> ../../../test/test_dugong.py::test_connect_proxy[plain-8080] PASSED
> ../../../test/test_dugong.py::test_get_pipeline[plain] PASSED
> ../../../test/test_dugong.py::test_ssl_info[plain] PASSED
> ../../../test/test_dugong.py::test_blocking_send[plain] PASSED
> ../../../test/test_dugong.py::test_blocking_read[plain] PASSED
> ../../../test/test_dugong.py::test_discard[plain] PASSED
> ../../../test/test_dugong.py::test_discard_chunked[plain] PASSED
> ../../../test/test_dugong.py::test_read_text[plain] PASSED
> ../../../test/test_dugong.py::test_read_text2[plain] PASSED
> ../../../test/test_dugong.py::test_read_text3[plain] PASSED
> ../../../test/test_dugong.py::test_read_identity[plain] PASSED
> ../../../test/test_dugong.py::test_conn_close_1[plain] PASSED
> ../../../test/test_dugong.py::test_conn_close_2[plain] PASSED
> ../../../test/test_dugong.py::test_conn_close_3[plain] PASSED
> 

Processed: severity of 844706 is important

[Debian Bug Tracking System]

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

> severity 844706 important
Bug #844706 [libssl1.1] libssl1.1 needs Breaks on salt-common
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#843024: marked as done (libqpid-proton8-dev: missing Breaks+Replaces: libqpid-proton2-dev)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 21:18:08 +
with message-id 
and subject line Bug#843024: fixed in qpid-proton 0.14.0-3
has caused the Debian Bug report #843024,
regarding libqpid-proton8-dev: missing Breaks+Replaces: libqpid-proton2-dev
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.)


-- 
843024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqpid-proton8-dev
Version: 0.14.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Selecting previously unselected package libqpid-proton8-dev.
  Preparing to unpack .../1-libqpid-proton8-dev_0.14.0-2_amd64.deb ...
  Unpacking libqpid-proton8-dev (0.14.0-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-jJYeCl/1-libqpid-proton8-dev_0.14.0-2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/include/proton/cid.h', which is also in package 
libqpid-proton2-dev 0.10-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-jJYeCl/1-libqpid-proton8-dev_0.14.0-2_amd64.deb


cheers,

Andreas


libqpid-proton2-dev=0.10-2_libqpid-proton8-dev=0.14.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: qpid-proton
Source-Version: 0.14.0-3

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

Debian distribution maintenance software
pp.
Daniel Pocock  (supplier of updated qpid-proton 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, 03 Nov 2016 10:24:19 +0100
Source: qpid-proton
Binary: libqpid-proton8 libqpid-proton-cpp8 libqpid-proton8-dev 
libqpid-proton-cpp8-dev libqpid-proton8-dev-examples libqpid-proton8-dev-doc 
libqpid-proton-cpp8-dev-doc python-qpid-proton python3-qpid-proton 
python-qpid-proton-doc
Architecture: source
Version: 0.14.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Middleware Maintainers 

Changed-By: Daniel Pocock 
Description:
 libqpid-proton-cpp8 - C++ libraries for Qpid Proton
 libqpid-proton-cpp8-dev - C++ Development libraries for writing messaging apps 
with Qpid Pr
 libqpid-proton-cpp8-dev-doc - C++ developer documentation for Qpid Proton
 libqpid-proton8 - C libraries for Qpid Proton
 libqpid-proton8-dev - C Development libraries for writing messaging apps with 
Qpid Prot
 libqpid-proton8-dev-doc - Developer documentation for Qpid Proton
 libqpid-proton8-dev-examples - Example applications for writign messaging apps 
with Qpid Proton
 python-qpid-proton - language bindings for Qpid Proton messaging framework - 
Python 2.
 python-qpid-proton-doc - Documentation for the Python language bindings for 
Qpid Proton
 python3-qpid-proton - language bindings for Qpid Proton messaging framework - 
Python 3.
Closes: 828521 843024
Changes:
 qpid-proton (0.14.0-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Daniel Pocock ]
   * Replace legacy packages. (Closes: #843024)
 .
   [ Ondřej Nový ]
   * Use OpenSSL 1.0, because OpenSSL 1.1 is not supported (Closes: #828521)
   * Bumped debhelper compat version to 10
   * d/control:
 - Use https protocol for Vcs-Git
 - Minor fixies in short descriptions
   * d/copyright: Fixed copyright for moved file
   * Added symbols file
   * Added simple autopkgtests for Python bindings
Checksums-Sha1:
 3883d86414cdb43dcd601b9641fed4cfcbfaedec 2967 qpid-proton_0.14.0-3.dsc
 1aa21f4c46eab901ebec72d1f09346db85c72796 12280 
qpid-proton_0.14.0-3.debian.tar.xz
Checksums-Sha256:
 e41ec9bfb1dcca2a3a34d1fb62314072e637b2e03103634ff0f770a4db2b4f35 2967 
qpid-proton_0.14.0-3.dsc
 

Bug#828521: marked as done (qpid-proton: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 21:18:08 +
with message-id 
and subject line Bug#828521: fixed in qpid-proton 0.14.0-3
has caused the Debian Bug report #828521,
regarding qpid-proton: FTBFS with openssl 1.1.0
to be marked as done.

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

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


-- 
828521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qpid-proton
Version: 0.10-2
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/qpid-proton_0.10-2_amd64-20160529-1518

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: qpid-proton
Source-Version: 0.14.0-3

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

Debian distribution maintenance software
pp.
Daniel Pocock  (supplier of updated qpid-proton 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, 03 Nov 2016 10:24:19 +0100
Source: qpid-proton
Binary: libqpid-proton8 libqpid-proton-cpp8 libqpid-proton8-dev 
libqpid-proton-cpp8-dev libqpid-proton8-dev-examples libqpid-proton8-dev-doc 
libqpid-proton-cpp8-dev-doc python-qpid-proton python3-qpid-proton 
python-qpid-proton-doc
Architecture: source
Version: 0.14.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Middleware Maintainers 

Changed-By: Daniel Pocock 
Description:
 libqpid-proton-cpp8 - C++ libraries for Qpid Proton
 libqpid-proton-cpp8-dev - C++ Development libraries for writing messaging apps 
with Qpid Pr
 libqpid-proton-cpp8-dev-doc - C++ developer documentation for Qpid Proton
 libqpid-proton8 - C libraries for Qpid Proton
 libqpid-proton8-dev - C Development libraries for writing messaging apps with 
Qpid Prot
 libqpid-proton8-dev-doc - Developer documentation for Qpid Proton
 libqpid-proton8-dev-examples - Example applications for writign messaging apps 
with Qpid Proton
 python-qpid-proton - language bindings for Qpid Proton messaging framework - 
Python 2.
 python-qpid-proton-doc - Documentation for the Python language bindings for 
Qpid Proton
 python3-qpid-proton - language bindings for Qpid Proton messaging framework - 
Python 3.
Closes: 828521 843024
Changes:
 qpid-proton (0.14.0-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Daniel Pocock ]
   * Replace legacy packages. (Closes: #843024)
 .
   [ Ondřej Nový ]
   * Use OpenSSL 1.0, because OpenSSL 1.1 is not supported (Closes: #828521)
   * Bumped debhelper compat version to 10
   * d/control:
 - Use https protocol for Vcs-Git
 - Minor fixies in short descriptions
   * d/copyright: Fixed copyright for moved file
   * Added symbols file
   * Added simple autopkgtests for Python bindings
Checksums-Sha1:
 3883d86414cdb43dcd601b9641fed4cfcbfaedec 2967 qpid-proton_0.14.0-3.dsc
 1aa21f4c46eab901ebec72d1f09346db85c72796 12280 
qpid-proton_0.14.0-3.debian.tar.xz
Checksums-Sha256:
 e41ec9bfb1dcca2a3a34d1fb62314072e637b2e03103634ff0f770a4db2b4f35 2967 
qpid-proton_0.14.0-3.dsc
 9e9422a0f6f10f35866b6fd1d0f3dc48b5a0f59b18f48217a1cf7a31c18c37db 12280 
qpid-proton_0.14.0-3.debian.tar.xz
Files:
 9f6d8fe0f8da9955d3ccb1fec38d6c29 2967 libs optional qpid-proton_0.14.0-3.dsc
 8525f5bf82bb2a72f1cea5fec97767ee 12280 libs optional 
qpid-proton_0.14.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

Bug#841662: marked as done (libserver-starter-perl: test suite sometimes times out)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 21:16:34 +
with message-id 
and subject line Bug#841662: fixed in libserver-starter-perl 0.32-2
has caused the Debian Bug report #841662,
regarding libserver-starter-perl: test suite sometimes times out
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.)


-- 
841662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libserver-starter-perl
Version: 0.32-1
Severity: normal
User: debian-p...@lists.debian.org
Usertags: autopkgtest

This package occasionally fails its autopkgtest checks on ci.debian.net.

  https://ci.debian.net/packages/libs/libserver-starter-perl/unstable/amd64/

It's not clear to me which test is hanging; it looks like t/04-starter-dir.t
finishes properly but I guess it could also be its cleanup or something.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libserver-starter-perl
Source-Version: 0.32-2

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

Debian distribution maintenance software
pp.
Niko Tyni  (supplier of updated libserver-starter-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: Mon, 21 Nov 2016 22:26:02 +0200
Source: libserver-starter-perl
Binary: libserver-starter-perl
Architecture: source
Version: 0.32-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Niko Tyni 
Description:
 libserver-starter-perl - superdaemon for hot-deploying Perl server programs
Closes: 841662
Changes:
 libserver-starter-perl (0.32-2) unstable; urgency=medium
 .
   * Team upload.
   [ Salvatore Bonaccorso ]
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
   * debian/upstream/metadata: use HTTPS for GitHub URLs.
 .
   [ Niko Tyni ]
   * Skip most of the test suite, it's racy and sometimes hangs altogether.
 (Closes: #841662)
 + drop most of the build dependencies, not needed any longer
   * Declare Standards-Version 3.9.8.
Checksums-Sha1:
 43111d104c3db418e253e56b2196c8c5aeba0979 2185 libserver-starter-perl_0.32-2.dsc
 392514bc798fa0ab94ba0c39fbca06ddee3d42ff 2936 
libserver-starter-perl_0.32-2.debian.tar.xz
Checksums-Sha256:
 207540621b5e822c14853d63d2049f2e09284ed0820f4fb2c743c142f91c09db 2185 
libserver-starter-perl_0.32-2.dsc
 5eb706848152746012d34679f00e5cb953abe02f0e6b6cf23f9652bbe57f2d71 2936 
libserver-starter-perl_0.32-2.debian.tar.xz
Files:
 dd84e8b46689107d02d7c7f48f99454b 2185 perl optional 
libserver-starter-perl_0.32-2.dsc
 d8ab70e9c36367f62fc90f98f3a22e84 2936 perl optional 
libserver-starter-perl_0.32-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdqKOQsmBHZHoj7peLsD/s7cwGx8FAlgzWX4ACgkQLsD/s7cw
Gx9lnA/8D+06qV/A3z7V41hgqWpHlThDSm3NYuEe/mSCtTe0CMW1YijIk3ZB3Skn
di9dd2rLVVK4KLVbA8QYsNROlA+W22ObjwcAyoQ9I7Sgx5z+xi4KBbjoqYWC5sQJ
9nUPqz+R3dSHTQsVjPF3nue7lGhsEa3lZejUzGlzBDehCpu7Ax696RiZAhu2DmQd
a5S7aCqe5FmtIsOmtEOkQP0C/YkgjU7sQiYwlSqE/YXHYzkvL+C6fIGcU5yiVwwp
dFtJrWOqEA3ntL9tuney7IDNvNssSnSJz5eL7zh12XQrwBqyUN8EFeTp9HdHKRx0
8PQDS2JZY1HEq6ks3Azn1W2MmfLLN09MahWqNHl/IKUbFlO9+3HPwVaPd3h2XdeF
rkFo4xgrXYm7gHsCEurbrKj9Q/WdUOc+x7ur8/w7pWA0FHRWx1rWQUPZlj0/cuZ0
Xh7eTIp3Fz5pJTMCeOawKnGM4MJVXOPBRAptnGVEJ8HoeOwgh8Wtf1PHdgNAVXsz
oXtUmGpF12Yt0227HvgR1KSYZs+KSi1VOHCsc47fuBG20//e5O1J9QJbpZtlelBQ
V7e49hHEbQkBc+Gmyqh8by7/94eouM+vgOlZPVNHSwmVEqpxpcqxa8i8Jcgh/tuC
8kdo0ipe4BIYFw4V4IBCI0FL2txvbCzqIEJt9facGvqbljHfC84=
=prKP
-END PGP SIGNATURE End Message ---

Bug#812280: Fix/Workaround for the newmat FTBFS

[Adrian Bunk]

Control: tags -1 patch

What broke the build is that gcc 6 changed the default C++ standard
from C++98 to C++14.

Not all valid C++98 code is also valid C++11 and C++14 code.

Note that this just changed the default, when told to process C++98 code 
gcc 6 does not differ in any significant way from gcc 5.

Making the code compatible with C++14 would be the best possible 
solution, but as a workaround it is possible to fix the build with
this change to tell gcc that this is C++98 code.

CXXFLAGS set in debian/rules were not used at all, this is also fixed.

--- debian/rules.old2016-11-21 21:00:13.0 +
+++ debian/rules2016-11-21 21:02:13.0 +
@@ -15,6 +15,8 @@
CXXFLAGS += -O2
 endif
 
+CXXFLAGS += -std=gnu++98
+
 # shared library versions,
 version=`ls src/.libs/lib*.so.* | \
 awk '{if (match($$0,/[0-9]+\.[0-9]+\.[0-9]+$$/)) print substr($$0,RSTART)}'`
@@ -33,7 +35,7 @@
 
 configure-stamp: config-stamp
dh_testdir
-   CFLAGS="$(CFLAGS) -Wl,-z,defs" \
+   CXXFLAGS="$(CXXFLAGS)" CFLAGS="$(CFLAGS) -Wl,-z,defs" \
 ./configure --host=$(DEB_HOST_GNU_TYPE) \
 --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr \
 --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info


cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: Fix/Workaround for the newmat FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #812280 [newmat] newmat: FTBFS with GCC 6: terminate called
Added tag(s) patch.

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

Bug#845171: [pkg-wine-party] Bug#845171: wine-development: FTBFS: ld aborts or segfaults

[Michael Gilbert]

On Sun, Nov 20, 2016 at 9:16 PM, Jens Reyer wrote:
> wine-development 1.9.22-1 (in stretch) built successfully on all
> architectures when it was uploaded to unstable, but fails to
> build in a stretch environment on i386 now (amd64 is still fine).
> Exactly the same for 1.9.23-1 on i386 in a sid environment:

Hi Jens,

1.9.23-1 built for me ok in a sid i386 chroot.  Can you clarify the
setup where it fails?  Did you mean kfreebsd-i386?

A recent change to binutils adds -Wl,--enable-new-dtags by default.
That may be the cause of the problem on arm.

The i386 and arm failures are probably different issues.

Best wishes,
Mike

Processed: limit source to imagemagick, tagging 845242, tagging 845206, tagging 845195, tagging 845244 ...

[Debian Bug Tracking System]

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

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

> tags 845242 + pending
Bug #845242 [src:imagemagick] Heap buffer overflow in heap-buffer-overflow in 
IsPixelGray
Added tag(s) pending.
> tags 845206 + pending
Bug #845206 [src:imagemagick] CVE-2016-8677: memory allocate failure in 
AcquireQuantumPixels
Added tag(s) pending.
> tags 845195 + pending
Bug #845195 [src:imagemagick] Imagemagick (jessie and older) buffer overflow
Added tag(s) pending.
> tags 845244 + pending
Bug #845244 [src:imagemagick] Add check for invalid mat file
Added tag(s) pending.
> tags 845212 + pending
Bug #845212 [src:imagemagick] Fix out of bound read in viff file handling
Added tag(s) pending.
> tags 845202 + pending
Bug #845202 [src:imagemagick] Better check for bufferoverflow for TIFF handling
Added tag(s) pending.
> tags 845213 + pending
Bug #845213 [src:imagemagick] Suspend exception processing if there are too 
many exceptions
Added tag(s) pending.
> tags 845198 + pending
Bug #845198 [src:imagemagick] Check validity of extend during TIFF file reading
Added tag(s) pending.
> tags 845196 + pending
Bug #845196 [src:imagemagick] Check return of write function
Added tag(s) pending.
> tags 845246 + pending
Bug #845246 [src:imagemagick] mat file out of bound
Added tag(s) pending.
> tags 845243 + pending
Bug #845243 [src:imagemagick] null pointer passed as argument 2, which is 
declared to never be null
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
845195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845195
845196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845196
845198: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845198
845202: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845202
845206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845206
845212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845212
845213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845213
845242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845242
845243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845243
845244: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845244
845246: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#845260: kernel-common: hard lockup with Call Trace after upgrading from 4.2 to 4.8 kernel

[Galen Thurber]

Package: kernel-common
Version: kernel
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   * What led up to the situation?
upgraded Sparky Linux 4, kernel 4.2 to 4.8 via safe upgrade method
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
was able to only boot to single recovery mode.
Managed to boot once with 4.2 kernel to report this
   * What was the outcome of this action?
boots to 4.8 result in hard lockup after Call Trace
   * What outcome did you expect instead?
normal boot, then xserver



-- System Information:
Distributor ID: Sparky
Description:SparkyLinux
Release:4
Codename:   Tyche
Architecture: i686

Kernel: Linux 4.2.0-1-586
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#813970: marked as done (dbus: purge fails: invoke-rc.d: initscript dbus, action "stop" failed.)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 21:02:09 +
with message-id 
and subject line Bug#813970: fixed in dbus 1.8.22-0+deb8u1
has caused the Debian Bug report #813970,
regarding dbus: purge fails: invoke-rc.d: initscript dbus, action "stop" failed.
to be marked as done.

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

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


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I cannot purge dbus package on my server:

(Læser database ... 104307 filer og kataloger installeret i øjeblikket.)
Afinstallerer dbus (1.8.20-0+deb8u1) ...
Job for dbus.service canceled.
invoke-rc.d: initscript dbus, action "stop" failed.
dpkg: fejl under behandling af pakken dbus (--purge):
 underproces installerede pre-removal-script returnerede afslutningsstatus 1
Der opstod fejl under behandlingen:
 dbus


 - Jonas

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWtvPYAAoJECx8MUbBoAEhx9QP/AppsKAuduB3uUQumOWKsDy6
HfiY2OupLX7RNyY+1eI60z4Lrqkh0DmO4wmO3InGgW6yJ32mYuTDgv4PcFlXxuNq
8CQuwIv+L46iy+6s0xoZN1Fs5hpaG9/wv7F6FgOLb1c/AE4LlPd2O5OWgDNHZJSy
XNEHzlfAJwcO78cnXG6VzzJiokn+oStQLVqvKLxMCLirHFvK28+coyfHaW6rxsf7
ke1X1NbqhuVjvhBa4nygZqwHv3q9KEUpMklzuYobPXJ0f2pAr7O+j9gPBsIg3bvT
zQJKZTHYBIqOWyoJ5ZDPkQBpXpzxC4g9FDGdfK4bmvVAK+ORRI4MVzmWZ4C0tLGQ
pyEQm9CSBBuEYKYl3hbVfoBmGMfEx7oI8XNhgL1y0ojcF9y2boBFvS+j79UKP6TG
s87171B+c5RLtTLa/ul3gU6lDqU5xMPuWtLt0d1pH5yPOC887YduHnBeSIgdBWEM
B+R+zqoxN1lX7NOjdX8pK6eXjqLXSi3aStz7t51K7DqMMNGZAXXX+bTkFcLVUHs8
Gu2opmxcf4VcVyaJ7odJ3Ev0ZUT7NUUCnz2MkeWQfrqWUgzIt12nRS4TgAQ/k6Dj
+E7LTsKRulMjPDjL4+LDXtL/+BPbHttoWxMA0KDPJyYluJUawdeu4/L0h/dPYyR1
XHm082GrYyU7b4pWR9Db
=pTWg
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: dbus
Source-Version: 1.8.22-0+deb8u1

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

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated dbus package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 10 Oct 2016 11:42:50 +0100
Source: dbus
Binary: dbus dbus-udeb dbus-x11 libdbus-1-3 libdbus-1-3-udeb dbus-1-doc 
libdbus-1-dev dbus-1-dbg
Architecture: all source
Version: 1.8.22-0+deb8u1
Distribution: jessie
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Simon McVittie 
Closes: 813970
Description: 
 dbus-1-dbg - simple interprocess messaging system (debug symbols)
 dbus-1-doc - simple interprocess messaging system (documentation)
 dbus   - simple interprocess messaging system (daemon and utilities)
 dbus-udeb  - simple interprocess messaging system (minimal runtime) (udeb)
 dbus-x11   - simple interprocess messaging system (X11 deps)
 libdbus-1-3 - simple interprocess messaging system (library)
 libdbus-1-3-udeb - simple interprocess messaging system (minimal library) 
(udeb)
 libdbus-1-dev - simple interprocess messaging system (development headers)
Changes:
 dbus (1.8.22-0+deb8u1) jessie; urgency=medium
 .
   * New upstream bugfix release
 - fix a potential format string vulnerability, which is not believed
   to be exploitable in practice
   * dbus.prerm: ensure that dbus.socket is stopped before removal,
 so that a new connection to the bus won't cause dbus.service to be
 restarted (Closes: #813970)
Checksums-Sha1: 
 e515376ad0bcba52ebd0d34812558c7ef78fb9a1 2889 dbus_1.8.22-0+deb8u1.dsc
 6e71490083037ce2d78067eb8856cfcca3be5d1f 1894768 dbus_1.8.22.orig.tar.gz
 346ed566f48feb5c8910cf622ac8731bb30f26ac 38168 
dbus_1.8.22-0+deb8u1.debian.tar.xz
 a4cb535664dbbb66a3d918f3a3ed019a0d289453 1324650 
dbus-1-doc_1.8.22-0+deb8u1_all.deb
Checksums-Sha256: 
 13cf18c13043baccf6fb26d18ea4e0fcb4b6859942175b3b735a1f63608c75c1 2889 
dbus_1.8.22-0+deb8u1.dsc
 19a52e5a42b2a2faf15a54745a098bb8cf55a76598fa4a0b8b6d886adcbe1d53 1894768 
dbus_1.8.22.orig.tar.gz
 

Processed: limit source to imagemagick, tagging 845202, tagging 845242, tagging 845244, tagging 845213 ...

[Debian Bug Tracking System]

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

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

> tags 845202 + pending
Bug #845202 [src:imagemagick] Better check for bufferoverflow for TIFF handling
Ignoring request to alter tags of bug #845202 to the same tags previously set
> tags 845242 + pending
Bug #845242 [src:imagemagick] Heap buffer overflow in heap-buffer-overflow in 
IsPixelGray
Ignoring request to alter tags of bug #845242 to the same tags previously set
> tags 845244 + pending
Bug #845244 [src:imagemagick] Add check for invalid mat file
Ignoring request to alter tags of bug #845244 to the same tags previously set
> tags 845213 + pending
Bug #845213 [src:imagemagick] Suspend exception processing if there are too 
many exceptions
Ignoring request to alter tags of bug #845213 to the same tags previously set
> tags 845212 + pending
Bug #845212 [src:imagemagick] Fix out of bound read in viff file handling
Ignoring request to alter tags of bug #845212 to the same tags previously set
> tags 845198 + pending
Bug #845198 [src:imagemagick] Check validity of extend during TIFF file reading
Ignoring request to alter tags of bug #845198 to the same tags previously set
> tags 845243 + pending
Bug #845243 [src:imagemagick] null pointer passed as argument 2, which is 
declared to never be null
Ignoring request to alter tags of bug #845243 to the same tags previously set
> tags 845195 + pending
Bug #845195 [src:imagemagick] Imagemagick (jessie and older) buffer overflow
Ignoring request to alter tags of bug #845195 to the same tags previously set
> tags 845206 + pending
Bug #845206 [src:imagemagick] CVE-2016-8677: memory allocate failure in 
AcquireQuantumPixels
Ignoring request to alter tags of bug #845206 to the same tags previously set
> tags 845196 + pending
Bug #845196 [src:imagemagick] Check return of write function
Ignoring request to alter tags of bug #845196 to the same tags previously set
> tags 845246 + pending
Bug #845246 [src:imagemagick] mat file out of bound
Ignoring request to alter tags of bug #845246 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
845195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845195
845196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845196
845198: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845198
845202: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845202
845206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845206
845212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845212
845213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845213
845242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845242
845243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845243
845244: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845244
845246: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Fix from Ubuntu for netmrg

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #790454 [netmrg] FTBFS in unstable due to build-depends on 
libmysqlclient15-dev
Added tag(s) patch.

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

Processed: Fix from Ubuntu for netmrg

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #821537 [netmrg] netmrg: PHP 7.0 Transition
Added tag(s) patch.

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

Bug#790454: Fix from Ubuntu for netmrg

[Adrian Bunk]

Control: tags -1 patch

The fix I found in Ubuntu for these bugs is attached.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

diff -pruN 0.20-7/debian/control 0.20-7ubuntu2/debian/control
--- 0.20-7/debian/control	2016-04-07 08:18:26.0 +
+++ 0.20-7ubuntu2/debian/control	2016-04-07 08:18:26.0 +
@@ -1,8 +1,8 @@
 Maintainer: Uwe Steinmann 
-Build-Depends: rrdtool (>= 1.3.1-4), debhelper (>= 5), debconf, libxml2-dev, libmysqlclient15-dev, libsnmp-dev, xsltproc, docbook-xsl, docbook-xml
+Build-Depends: rrdtool (>= 1.3.1-4), debhelper (>= 5), debconf, libxml2-dev, libmysqlclient-dev, libsnmp-dev, xsltproc, docbook-xsl, docbook-xml
 Standards-Version: 3.7.2
 
 Package: netmrg
 Architecture: any
-Depends: adduser, rrdtool, apache2 | httpd, php5 | php4 | php5-cgi | php4-cgi, php5-cli | php4-cli, php5-mysql | php4-mysql, mysql-client, debconf, wwwconfig-common, ${shlibs:Depends}, ${misc:Depends}
+Depends: adduser, rrdtool, apache2 | httpd, php | php-cgi, php-cli, php-mysql, mysql-client, debconf, wwwconfig-common, ${shlibs:Depends}, ${misc:Depends}
 Suggests: mysql-server

Bug#803713: Elasticsearch should not be part of a Debian release

[Hilko Bengen]

* Emmanuel Bourg:

> Do you think elasticsearch should be removed from unstable?

Not necessarily. It should just not become part of stretch because there
is no sensible way to support it.

BTW: Apparently I was wrong about the 1.7.x branch no longer being
supported by the upstream project: A tag for v1.7.6 recently appeared in
the Github repo a few days ago. Their policy about security issues is
still Oracle-grade stupid and user-hostile.

Cheers,
-Hilko

Bug#841662: Pending fixes for bugs in the libserver-starter-perl package

[pkg-perl-maintainers]

tag 841662 + pending
thanks

Some bugs in the libserver-starter-perl package are closed in
revision 2be7fe08952ce2eae66b29d1af9a9f283be83e5a in branch 'master'
by Niko Tyni

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libserver-starter-perl.git/commit/?id=2be7fe0

Commit message:

Skip most of the test suite, it's racy and sometimes hangs altogether

Closes: #841662

Processed: Pending fixes for bugs in the libserver-starter-perl package

[Debian Bug Tracking System]

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

> tag 841662 + pending
Bug #841662 [libserver-starter-perl] libserver-starter-perl: test suite 
sometimes times out
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#844869: isatapd: FTBFS: ip.h:85:8: error: redefinition of 'struct iphdr'

[Bernhard Schmidt]

Hi Adrian,

On Mon, Nov 21, 2016 at 04:58:34PM +0200, Adrian Bunk wrote:
> On Sun, Nov 20, 2016 at 08:54:06PM +0100, Bernhard Schmidt wrote:
> >...
> > On Sat, Nov 19, 2016 at 07:43:42AM +0100, Lucas Nussbaum wrote:
> >...
> > > Relevant part (hopefully):
> > > > gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g 
> > > > -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> > > > -Wformat -Werror=format-security -c -o tunnel.o tunnel.c
> > > > In file included from /usr/include/linux/if_tunnel.h:6:0,
> > > >  from tunnel.c:23:
> > > > /usr/include/linux/ip.h:85:8: error: redefinition of 'struct iphdr'
> > > >  struct iphdr {
> > > > ^
> > > > In file included from tunnel.c:21:0:
> > > > /usr/include/netinet/ip.h:44:8: note: originally defined here
> > > >  struct iphdr
> > > > ^
> > > > Makefile:353: recipe for target 'tunnel.o' failed
> > > > make[3]: *** [tunnel.o] Error 1
> >...
> > Odd. I can reproduce this FTBFS. The package has not been touched for a
> > long time, does not have any uncommon builddeps and (according to the
> > reproducible builds at
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/isatapd.html)
> > built fine in sid until a month ago.
> >...
> 
> This is caused by a recent change to the kernel userspace headers:
>   
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1fe8e0f074c77aa41aaa579345a9e675acbebfa9

Thanks!

I'm far away from being a C programmer, so maybe the solution is easy.
But I could not find any.

I need netinet/ip.h for the definition of IP_DF, it is not defined
anywhere else.

I obviously need linux/if_tunnel.h for all the tunnel stuff, which
includes linux/ip.h with the conflicting definition of the iphdr struct.

This works, but I don't think this is the right solution

-#include 
 #include 
 #include 
+#define   IP_DF 0x4000/* dont fragment flag */

Bernhard


signature.asc
Description: Digital signature

Processed: found 845246 in 8:6.7.7.10-4

[Debian Bug Tracking System]

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

> found 845246 8:6.7.7.10-4
Bug #845246 [src:imagemagick] mat file out of bound
Marked as found in versions imagemagick/8:6.7.7.10-4.
> thanks
Stopping processing here.

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

Processed: found 845244 in 8:6.7.7.10-4

[Debian Bug Tracking System]

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

> found 845244 8:6.7.7.10-4
Bug #845244 [src:imagemagick] Add check for invalid mat file
Marked as found in versions imagemagick/8:6.7.7.10-4.
> thanks
Stopping processing here.

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

Processed: bug 845243 is forwarded to https://github.com/ImageMagick/ImageMagick/issues/298 ...

[Debian Bug Tracking System]

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

> forwarded 845243 https://github.com/ImageMagick/ImageMagick/issues/298
Bug #845243 [src:imagemagick] null pointer passed as argument 2, which is 
declared to never be null
Set Bug forwarded-to-address to 
'https://github.com/ImageMagick/ImageMagick/issues/298'.
> found 845243 8:6.7.7.10-4
Bug #845243 [src:imagemagick] null pointer passed as argument 2, which is 
declared to never be null
Marked as found in versions imagemagick/8:6.7.7.10-4.
> thanks
Stopping processing here.

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

Processed: found 845242 in 8:6.7.7.10-4

[Debian Bug Tracking System]

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

> found 845242 8:6.7.7.10-4
Bug #845242 [src:imagemagick] Heap buffer overflow in heap-buffer-overflow in 
IsPixelGray
Marked as found in versions imagemagick/8:6.7.7.10-4.
> thanks
Stopping processing here.

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

Bug#844293: Possible fix for the criu FTBFS

[Salvatore Bonaccorso]

Hi Adrian,

On Mon, Nov 21, 2016 at 05:29:10PM +0200, Adrian Bunk wrote:
> Control: tags -1 -help
> 
> This is a result of the recent PIE changes in dpkg.
> 
> Did you really intend hardening=-all?

This was a decision by the previous maintainer. Will look. I think we
actually would like to have the oposite for now, but do not find for
now a trace about the reasiong. Let me check that.

Regards,
Salvatore

Processed: Fix from Ubuntu for nagvis

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #821536 [nagvis] nagvis: PHP 7.0 Transition
Added tag(s) patch.

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

Bug#821536: Fix from Ubuntu for nagvis

[Adrian Bunk]

Control: tags -1 patch

The fix I found in Ubuntu for this bug is attached.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

diff -pruN 1:1.7.10+dfsg1-3/debian/control 1:1.7.10+dfsg1-3ubuntu1/debian/control
--- 1:1.7.10+dfsg1-3/debian/control	2014-03-30 18:42:10.0 +
+++ 1:1.7.10+dfsg1-3ubuntu1/debian/control	2016-03-26 03:43:02.0 +
@@ -16,12 +17,12 @@ Vcs-Browser: http://anonscm.debian.org/g
 Package: nagvis
 Architecture: all
 Depends: ${misc:Depends},
- php5-common (>= 5.3.0),
- php5,
- php5-gd,
+ php-common,
+ php,
+ php-gd,
  ucf,
  graphviz,
- php5-sqlite,
+ php-sqlite3,
  php-net-socket,
  php-gettext
 Suggests: check-mk-livestatus, nagvis-demos

Processed: found 845213 in 8:6.7.7.10-4

[Debian Bug Tracking System]

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

> found 845213 8:6.7.7.10-4
Bug #845213 [src:imagemagick] Suspend exception processing if there are too 
many exceptions
Marked as found in versions imagemagick/8:6.7.7.10-4.
> thanks
Stopping processing here.

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

Bug#843327: Not solved

[Scott Kitterman]

It's done completely differently now.  Please file a new bug with specifics of 
what exactly is wrong, with a copy of the generated files attached.

Scott K

Processed: found 845195 in 8:6.7.7.10-4

[Debian Bug Tracking System]

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

> # mark as found in common anchestor for wheezy and jessie
> found 845195 8:6.7.7.10-4
Bug #845195 [src:imagemagick] Imagemagick (jessie and older) buffer overflow
Marked as found in versions imagemagick/8:6.7.7.10-4.
> thanks
Stopping processing here.

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

Bug#828506: pkcs11-helper: FTBFS with openssl 1.1.0

[Clint Adams]

On Tue, Nov 01, 2016 at 12:03:40AM +0100, Sebastian Andrzej Siewior wrote:
> There is an pull request from fedora. The fedora bug ist at
>   https://bugzilla.redhat.com/show_bug.cgi?id=1388463

Better to switch to libssl1.0-dev to avoid breaking openvpn.

Bug#844132: marked as done (glibc: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 18:48:47 +
with message-id 
and subject line Bug#844132: fixed in glibc 2.24-6
has caused the Debian Bug report #844132,
regarding glibc: FTBFS: tests failed
to be marked as done.

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

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


-- 
844132: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.24-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-2016 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

> UNRESOLVED: argp/argp-test
> UNRESOLVED: argp/bug-argp1
> UNRESOLVED: argp/bug-argp2
> UNRESOLVED: argp/tst-argp1
> UNRESOLVED: argp/tst-argp2
> UNRESOLVED: assert/test-assert
> UNRESOLVED: assert/test-assert-perr
> UNRESOLVED: catgets/tst-catgets
> FAIL: conform/ISO/assert.h/linknamespace
> FAIL: conform/ISO/ctype.h/linknamespace
> FAIL: conform/ISO/errno.h/linknamespace
> FAIL: conform/ISO/locale.h/linknamespace
> FAIL: conform/ISO/math.h/linknamespace
> FAIL: conform/ISO/setjmp.h/linknamespace
> FAIL: conform/ISO/signal.h/linknamespace
> FAIL: conform/ISO/stdio.h/linknamespace
> FAIL: conform/ISO/stdlib.h/linknamespace
> FAIL: conform/ISO/string.h/linknamespace
> FAIL: conform/ISO/time.h/linknamespace
> FAIL: conform/ISO11/assert.h/linknamespace
> FAIL: conform/ISO11/complex.h/linknamespace
> FAIL: conform/ISO11/ctype.h/linknamespace
> FAIL: conform/ISO11/errno.h/linknamespace
> FAIL: conform/ISO11/fenv.h/linknamespace
> FAIL: conform/ISO11/inttypes.h/linknamespace
> FAIL: conform/ISO11/locale.h/linknamespace
> FAIL: conform/ISO11/math.h/linknamespace
> FAIL: conform/ISO11/setjmp.h/linknamespace
> FAIL: conform/ISO11/signal.h/linknamespace
> FAIL: conform/ISO11/stdio.h/linknamespace
> FAIL: conform/ISO11/stdlib.h/linknamespace
> FAIL: conform/ISO11/string.h/linknamespace
> FAIL: conform/ISO11/tgmath.h/linknamespace
> FAIL: conform/ISO11/time.h/linknamespace
> FAIL: conform/ISO11/uchar.h/linknamespace
> FAIL: conform/ISO11/wchar.h/linknamespace
> FAIL: conform/ISO11/wctype.h/linknamespace
> FAIL: conform/ISO99/assert.h/linknamespace
> FAIL: conform/ISO99/complex.h/linknamespace
> FAIL: conform/ISO99/ctype.h/linknamespace
> FAIL: conform/ISO99/errno.h/linknamespace
> FAIL: conform/ISO99/fenv.h/linknamespace
> FAIL: conform/ISO99/inttypes.h/linknamespace
> FAIL: conform/ISO99/locale.h/linknamespace
> FAIL: conform/ISO99/math.h/linknamespace
> FAIL: conform/ISO99/setjmp.h/linknamespace
> FAIL: conform/ISO99/signal.h/linknamespace
> FAIL: conform/ISO99/stdio.h/linknamespace
> FAIL: conform/ISO99/stdlib.h/linknamespace
> FAIL: conform/ISO99/string.h/linknamespace
> FAIL: conform/ISO99/tgmath.h/linknamespace
> FAIL: conform/ISO99/time.h/linknamespace
> FAIL: conform/ISO99/wchar.h/linknamespace
> FAIL: conform/ISO99/wctype.h/linknamespace
> FAIL: conform/POSIX/aio.h/linknamespace
> FAIL: conform/POSIX/assert.h/linknamespace
> FAIL: conform/POSIX/ctype.h/linknamespace
> FAIL: conform/POSIX/dirent.h/linknamespace
> FAIL: conform/POSIX/errno.h/linknamespace
> FAIL: conform/POSIX/fcntl.h/linknamespace
> FAIL: conform/POSIX/fnmatch.h/linknamespace
> FAIL: conform/POSIX/glob.h/linknamespace
> FAIL: conform/POSIX/grp.h/linknamespace
> FAIL: conform/POSIX/locale.h/linknamespace
> FAIL: conform/POSIX/math.h/linknamespace
> FAIL: conform/POSIX/mqueue.h/linknamespace
> FAIL: conform/POSIX/pthread.h/linknamespace
> FAIL: conform/POSIX/pwd.h/linknamespace
> FAIL: conform/POSIX/regex.h/linknamespace
> FAIL: conform/POSIX/sched.h/linknamespace
> FAIL: conform/POSIX/semaphore.h/linknamespace
> FAIL: conform/POSIX/setjmp.h/linknamespace
> FAIL: conform/POSIX/signal.h/linknamespace
> FAIL: conform/POSIX/stdio.h/linknamespace
> FAIL: conform/POSIX/stdlib.h/linknamespace
> FAIL: conform/POSIX/string.h/linknamespace
> FAIL: conform/POSIX/sys/mman.h/linknamespace
> FAIL: conform/POSIX/sys/stat.h/linknamespace
> FAIL: conform/POSIX/sys/times.h/linknamespace
> FAIL: conform/POSIX/sys/utsname.h/linknamespace
> FAIL: conform/POSIX/sys/wait.h/linknamespace
> FAIL: conform/POSIX/termios.h/linknamespace
> FAIL: conform/POSIX/time.h/linknamespace
> FAIL: conform/POSIX/unistd.h/linknamespace
> FAIL: conform/POSIX/utime.h/linknamespace
> FAIL: conform/POSIX/wordexp.h/linknamespace
> FAIL: conform/UNIX98/assert.h/linknamespace
> FAIL: conform/UNIX98/ctype.h/linknamespace
> FAIL: conform/UNIX98/errno.h/linknamespace
> FAIL: conform/UNIX98/locale.h/linknamespace
> FAIL: 

Bug#843691: marked as done (glibc: FTBFS on ppc64el: Error: operand out of range)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 18:48:47 +
with message-id 
and subject line Bug#843691: fixed in glibc 2.24-6
has caused the Debian Bug report #843691,
regarding glibc: FTBFS on ppc64el: Error: operand out of range
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.)


-- 
843691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843691
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.24-5
Severity: serious

Hello,

glibc is failing to build on ppc64el, on sid with the following:

.../sysdeps/powerpc/powerpc64/power6/memset.S: Assembler messages:
.../sysdeps/powerpc/powerpc64/power6/memset.S:254: Error: operand out of range 
(5 is not between 0 and 1)
.../sysdeps/powerpc/powerpc64/power6/memset.S:254: Error: operand out of range 
(128 is not between 0 and 31)
.../sysdeps/powerpc/powerpc64/power6/memset.S:254: Error: missing operand

This was an attempt with sbuild with sid.
It initially built on the same version on buildd, 20 days ago or so,
but the failure was also observed on cross-compilation.

Thanks.

Fernando
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.24-6

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Nov 2016 19:22:48 +0100
Source: glibc
Binary: libc-bin libc-dev-bin libc-l10n glibc-doc glibc-source locales 
locales-all nscd multiarch-support libc6 libc6-dev libc6-dbg libc6-pic 
libc6-udeb libc6.1 libc6.1-dev libc6.1-dbg libc6.1-pic libc6.1-udeb libc0.3 
libc0.3-dev libc0.3-dbg libc0.3-pic libc0.3-udeb libc0.1 libc0.1-dev 
libc0.1-dbg libc0.1-pic libc0.1-udeb libc6-i386 libc6-dev-i386 libc6-sparc 
libc6-dev-sparc libc6-sparc64 libc6-dev-sparc64 libc6-s390 libc6-dev-s390 
libc6-amd64 libc6-dev-amd64 libc6-powerpc libc6-dev-powerpc libc6-ppc64 
libc6-dev-ppc64 libc6-mips32 libc6-dev-mips32 libc6-mipsn32 libc6-dev-mipsn32 
libc6-mips64 libc6-dev-mips64 libc0.1-i386 libc0.1-dev-i386 libc6-x32 
libc6-dev-x32 libc6-xen libc0.3-xen libc6.1-alphaev67 libc0.1-i686 libc0.3-i686 
libc6-i686
Architecture: source
Version: 2.24-6
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Description:
 glibc-doc  - GNU C Library: Documentation
 glibc-source - GNU C Library: sources
 libc-bin   - GNU C Library: Binaries
 libc-dev-bin - GNU C Library: Development binaries
 libc-l10n  - GNU C Library: localization files
 libc0.1- GNU C Library: Shared libraries
 libc0.1-dbg - GNU C Library: detached debugging symbols
 libc0.1-dev - GNU C Library: Development Libraries and Header Files
 libc0.1-dev-i386 - GNU C Library: 32bit development libraries for AMD64
 libc0.1-i386 - GNU C Library: 32bit shared libraries for AMD64
 libc0.1-i686 - transitional dummy package
 libc0.1-pic - GNU C Library: PIC archive library
 libc0.1-udeb - GNU C Library: Shared libraries - udeb (udeb)
 libc0.3- GNU C Library: Shared libraries
 libc0.3-dbg - GNU C Library: detached debugging symbols
 libc0.3-dev - GNU C Library: Development Libraries and Header Files
 libc0.3-i686 - transitional dummy package
 libc0.3-pic - GNU C Library: PIC archive library
 libc0.3-udeb - GNU C Library: Shared libraries - udeb (udeb)
 libc0.3-xen - GNU C Library: Shared libraries [Xen version]
 libc6  - GNU C Library: Shared libraries
 libc6-amd64 - GNU C Library: 64bit Shared libraries for AMD64
 libc6-dbg  - GNU C Library: detached debugging symbols
 libc6-dev  - GNU C Library: Development Libraries and Header Files
 libc6-dev-amd64 - GNU C Library: 64bit Development Libraries for AMD64
 libc6-dev-i386 - GNU C Library: 32-bit development libraries for AMD64
 libc6-dev-mips32 - GNU C Library: o32 Development Libraries for MIPS
 libc6-dev-mips64 - GNU C Library: 64bit Development Libraries for MIPS64
 

Bug#828461: marked as done (ntp: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 18:49:20 +
with message-id 
and subject line Bug#828461: fixed in ntp 1:4.2.8p9+dfsg-1
has caused the Debian Bug report #828461,
regarding ntp: FTBFS with openssl 1.1.0
to be marked as done.

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

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


-- 
828461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ntp
Version: 4.2.8p7+dfsg-4
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/ntp_4.2.8p7+dfsg-4_amd64-20160529-1457

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: ntp
Source-Version: 1:4.2.8p9+dfsg-1

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

Debian distribution maintenance software
pp.
Kurt Roeckx  (supplier of updated ntp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Nov 2016 19:30:02 +0100
Source: ntp
Binary: ntp ntpdate ntp-doc
Architecture: source
Version: 1:4.2.8p9+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NTP Team 
Changed-By: Kurt Roeckx 
Description:
 ntp- Network Time Protocol daemon and utility programs
 ntp-doc- Network Time Protocol documentation
 ntpdate- client for setting system time from NTP servers
Closes: 600661 617965 802040 823269 828461
Changes:
 ntp (1:4.2.8p9+dfsg-1) unstable; urgency=medium
 .
   * New usptream version
 - Adds OpenSSL 1.1.0 support (Closes: #828461)
 - Fix CVE-2016-9311
 - Fix CVE-2016-9310
 - Fix CVE-2016-7427
 - Fix CVE-2016-7428
 - Fix CVE-2016-9312
 - Fix CVE-2016-7431
 - Fix CVE-2016-7434
 - Fix CVE-2016-7429
 - Fix CVE-2016-7426
 - Fix CVE-2016-7433
   * Update watch for new version specific URL. Patch from
 Nicholas Luedtke  (Closes: #823269)
   * Make ntpdate-debian use the DHCP servers. Patch from
 Christian Ehrhardt  (Closes: #617965)
   * Move dhcp temporary files from /var/lib to /run. (Closes: #600661)
   * Wait for ntp to die in the stop target. Patch from Christoph Biedl
  (Closes: #802040)
Checksums-Sha1:
 4b7546d868bdefad1594d01684ea2d007abb6b6a 2227 ntp_4.2.8p9+dfsg-1.dsc
 45ec58a4b9ec1e814763305233e6f68f17b3ef71 4231056 ntp_4.2.8p9+dfsg.orig.tar.xz
 b0724578faa77a13b3caaad232e12194f5d84e10 53716 ntp_4.2.8p9+dfsg-1.debian.tar.xz
Checksums-Sha256:
 7204663c7485f98bec34a78068a37c444036925533b73359e0c1fe0fe7832a77 2227 
ntp_4.2.8p9+dfsg-1.dsc
 be24e8fa447366b9fbe4b51ff72a5da2deb5c48eddd59a97d395aebd52c1372c 4231056 
ntp_4.2.8p9+dfsg.orig.tar.xz
 50ab9d6fd08177efa41debe5ce8db7e721440625e9c5d4ab807371387159e43f 53716 
ntp_4.2.8p9+dfsg-1.debian.tar.xz
Files:
 b178a7d76e0326ea8c0ee4fa794949bb 2227 net optional ntp_4.2.8p9+dfsg-1.dsc
 979d47b6f0ad3e43ad481523930fc1c6 4231056 net optional 
ntp_4.2.8p9+dfsg.orig.tar.xz
 650025143c0ee77be86aab8da5361919 53716 net optional 
ntp_4.2.8p9+dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYMz49AAoJEOPE3c0eTBJEHbsQAJXKNDmsv+iiiM9laoh1+iJ/
wQWH7x9uz/u2PYLosu534nWjzZ7YXiQ+Nm1ghzriQ7xgaQ0wLsue0r0VWGJ0zEzx
ggRdpc6F1NGoNzK58k1zD9H9yU/kucZExMe7yZdM0wZA7xlsInNFgbJWzPI1NdpP
8kp2MmUhQF1PB5vWxf8uhyVUlF7Dh4+TQjg1V47P8W17YhH4+5JPGr1NEhSd2sEY

Processed: fixed 845122 in 0.3.7.beta-16.1+deb7u1

[Debian Bug Tracking System]

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

> fixed 845122 0.3.7.beta-16.1+deb7u1
Bug #845122 {Done: Salvatore Bonaccorso } [sniffit] 
CVE-2014-5439: Root shell on Sniffit
There is no source info for the package 'sniffit' at version 
'0.3.7.beta-16.1+deb7u1' with architecture ''
Unable to make a source version for version '0.3.7.beta-16.1+deb7u1'
Marked as fixed in versions 0.3.7.beta-16.1+deb7u1.
> thanks
Stopping processing here.

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

Processed: forcibly merging 843691 845096

[Debian Bug Tracking System]

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

> forcemerge 843691 845096
Bug #843691 [src:glibc] glibc: FTBFS on ppc64el: Error: operand out of range
Bug #845096 [src:glibc] glibc: FTBFS: 
../sysdeps/powerpc/powerpc64/power6/memset.S:254:
Marked as found in versions glibc/2.24-5.
Added tag(s) pending.
Bug #843691 [src:glibc] glibc: FTBFS on ppc64el: Error: operand out of range
Added tag(s) stretch and sid.
Merged 843691 845096
> thanks
Stopping processing here.

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

Bug#844549: network-console broken: no screen to be resumed matching sh

[Roger Shimizu]

Seems I'm late for the d-i/screen party, but ..

On Thu, Nov 17, 2016 at 6:39 AM, Martin Michlmayr  wrote:
>
> Oh, good point.
>
> I think that's what we want but I'm not sure.  Maybe Roger can
> comment.  In his old code, there was also a $NETBOOT_SCREEN variable
> which afaict wasn't set set anywhere.

Originally I add screen support to D-I for my orion5x-based
Linkstation NAS, which supports both serial / network console to start
D-I.

I want to support screen in both way (serial / network console), because
 - for serial console, no other option to access command line as free
as anytime.
 - for network console, no way to resume if the network cable gets
unplugged accidentally, or SSH connection disconnects for whatever
reason.

Because I'm new to D-I code base, I want to test the code I injected
in works alright, so I add $NETBOOT_SCREEN variable so that I can test
screen support for "one D-I image" in either serial console way (=1)
or network console way (=0).

The "one D-I image" I chose to test was netboot/network, so the
default of $NETBOOT_SCREEN is 0.
The "one D-I image" is just literally in D-I image filename, built by
same source code except with different $NETBOOT_SCREEN setting.

Maybe it's more clear to remove $NETBOOT_SCREEN after I submit my
patch, but I thought it might need to debug again some time later, so
it was kept as it was until Samuel's "Move" change.

On Sun, Nov 20, 2016 at 8:20 PM, Philip Hands  wrote:
>
> I'd think that the advantage is that one could start a serial install up
> to the point that the network comes up, and then hijack it onto the ssh
> session so that one gets to see the same install (as well as any other
> shells you might have started).
>
> That way, if you think you've preseeded all the pre-network stuff, there
> would be a session to look at via serial if it never gets to the
> network.
>
> Perhaps this is not a real scenario though (I've not played with SSH
> connections to d-i, so I don't know what happens when you log in and
> debconf is already active on the console)

This spec will be fantastic if it's able to be implemented.

On Mon, Nov 21, 2016 at 1:22 AM, Samuel Thibault  wrote:
>
> Mmm, that's a nice idea indeed.  I've eventually uploaded the -x fix,
> which gives us that behavior, and also allowing several people to follow
> the installation, interact, etc.

Thanks for your fixes!
I see another TERMCAP fix related to screen support. So you're really
appreciated!

I'll test the daily image on my Linkstation NAS.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#845246: mat file out of bound

[Bastien ROUCARIES]

Package: src:imagemagick
version: 8:6.8.9.9-5+deb8u5
Severity: grave
Tags: patch security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org
control: found -1 8:6.7.7.10-5+deb7u7
control: notfound -1 8:6.9.6.2+dfsg-2

moreinfo
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1545366

https://github.com/ImageMagick/ImageMagick/issues/131
Fixed by;

https://github.com/ImageMagick/ImageMagick/commit/b173a35239785c51c9a0e9d59eb6ce24c455
https://github.com/ImageMagick/ImageMagick/commit/f3b483e8b054c50149912523b4773687e18afe25

Bug#811790: Patch for the mp3blaster FTBFS

[Adrian Bunk]

Control: tags -1 patch

What broke the build is that gcc 6 changed the default C++ standard
from C++98 to C++14.

Not all valid C++98 code is also valid C++11 and C++14 code.

Note that this just changed the default, when told to process C++98 code 
gcc 6 does not differ in any significant way from gcc 5.

Making the code compatible with C++14 would be the best possible 
solution, but as a workaround it is possible to fix the build with
this change to tell gcc that this is C++98 code.

--- debian/rules.old2016-11-21 17:59:48.0 +
+++ debian/rules2016-11-21 18:00:07.0 +
@@ -12,7 +12,7 @@
autoheader
automake --add-missing
autoconf
-   dh_auto_configure -- --datadir=/usr/share/doc
+   dh_auto_configure -- --datadir=/usr/share/doc CXXFLAGS="-O2 -Wall 
-std=gnu++98"
 
 .PHONY: override_dh_installdocs
 override_dh_installdocs:


cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#843465: fixed upstream

[Bastian Blank]

This problem is actually fixed upstream.  I have no idea how this upload
survived.

Bastian

-- 
What kind of love is that?  Not to be loved; never to have shown love.
-- Commissioner Nancy Hedford, "Metamorphosis",
   stardate 3219.8

Processed: Patch for the mp3blaster FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #811790 [mp3blaster] mp3blaster: FTBFS with GCC 6: narrowing conversion
Added tag(s) patch.

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

Processed: mat file out of bound

[Debian Bug Tracking System]

Processing control commands:

> found -1 8:6.7.7.10-5+deb7u7
Bug #845246 [src:imagemagick] mat file out of bound
The source 'imagemagick' and version '8:6.7.7.10-5+deb7u7' do not appear to 
match any binary packages
Marked as found in versions imagemagick/8:6.7.7.10-5+deb7u7.
> notfound -1 8:6.9.6.2+dfsg-2
Bug #845246 [src:imagemagick] mat file out of bound
Ignoring request to alter found versions of bug #845246 to the same values 
previously set

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

Processed: Add check for invalid mat file

[Debian Bug Tracking System]

Processing control commands:

> found -1 8:6.7.7.10-5+deb7u7
Bug #845244 [src:imagemagick] Add check for invalid mat file
The source 'imagemagick' and version '8:6.7.7.10-5+deb7u7' do not appear to 
match any binary packages
Marked as found in versions imagemagick/8:6.7.7.10-5+deb7u7.
> notfound -1 8:6.9.6.2+dfsg-2
Bug #845244 [src:imagemagick] Add check for invalid mat file
Ignoring request to alter found versions of bug #845244 to the same values 
previously set

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

Bug#845243: null pointer passed as argument 2, which is declared to never be null

[Bastien ROUCARIES]

Package: src:imagemagick
version: 8:6.8.9.9-5+deb8u5
Severity: grave
Tags: patch security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org
control: found -1 8:6.7.7.10-5+deb7u7
control: found -1 8:6.9.6.2+dfsg-2


API abuse lead to sigv

fixed in 
https://github.com/ImageMagick/ImageMagick/commit/1c795ce9fe1d6feac8bc36c2e6c5ba7110b671b1

moreinformation https://github.com/ImageMagick/ImageMagick/issues/298

Processed: null pointer passed as argument 2, which is declared to never be null

[Debian Bug Tracking System]

Processing control commands:

> found -1 8:6.7.7.10-5+deb7u7
Bug #845243 [src:imagemagick] null pointer passed as argument 2, which is 
declared to never be null
The source 'imagemagick' and version '8:6.7.7.10-5+deb7u7' do not appear to 
match any binary packages
Marked as found in versions imagemagick/8:6.7.7.10-5+deb7u7.
> found -1 8:6.9.6.2+dfsg-2
Bug #845243 [src:imagemagick] null pointer passed as argument 2, which is 
declared to never be null
Marked as found in versions imagemagick/8:6.9.6.2+dfsg-2.

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

Bug#845244: Add check for invalid mat file

[Bastien ROUCARIES]

Package: src:imagemagick
version: 8:6.8.9.9-5+deb8u5
Severity: grave
Tags: patch security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org
control: found -1 8:6.7.7.10-5+deb7u7
control: notfound -1 8:6.9.6.2+dfsg-2

Found by code review of changleog

https://github.com/ImageMagick/ImageMagick/commit/8a370f9ab120faf182aa160900ba692ba8e2bcf0

Processed: This makes the package pretty useless (even for stable)

[Debian Bug Tracking System]

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

> severity 749557 serious
Bug #749557 [martian-modem-source] fixes to build martian-modem-source with 3.x 
kernels - at least to 3.13
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: Heap buffer overflow in heap-buffer-overflow in IsPixelGray

[Debian Bug Tracking System]

Processing control commands:

> found -1 8:6.7.7.10-5+deb7u7
Bug #845242 [src:imagemagick] Heap buffer overflow in heap-buffer-overflow in 
IsPixelGray
The source 'imagemagick' and version '8:6.7.7.10-5+deb7u7' do not appear to 
match any binary packages
Marked as found in versions imagemagick/8:6.7.7.10-5+deb7u7.
> found -1 8:6.9.6.2+dfsg-2
Bug #845242 [src:imagemagick] Heap buffer overflow in heap-buffer-overflow in 
IsPixelGray
Marked as found in versions imagemagick/8:6.9.6.2+dfsg-2.

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

Bug#845242: Heap buffer overflow in heap-buffer-overflow in IsPixelGray

[Bastien ROUCARIES]

Package: src:imagemagick
version: 8:6.8.9.9-5+deb8u5
Severity: grave
Tags: patch security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org
control: found -1 8:6.7.7.10-5+deb7u7
control: found -1 8:6.9.6.2+dfsg-2


Moreinformation https://github.com/ImageMagick/ImageMagick/issues/301

Fixed in 
https://github.com/ImageMagick/ImageMagick/commit/174de08d7c81ce147689f3b1c73fadd6bf1c023c

Processed: Prevent fault in MSL interpreter

[Debian Bug Tracking System]

Processing control commands:

> found -1 8:6.7.7.10-5+deb7u7
Bug #845241 [src:imagemagick] Prevent fault in MSL interpreter
The source 'imagemagick' and version '8:6.7.7.10-5+deb7u7' do not appear to 
match any binary packages
Marked as found in versions imagemagick/8:6.7.7.10-5+deb7u7.
> found -1 8:6.9.6.2+dfsg-2
Bug #845241 [src:imagemagick] Prevent fault in MSL interpreter
Marked as found in versions imagemagick/8:6.9.6.2+dfsg-2.

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

Bug#845241: Prevent fault in MSL interpreter

[Bastien ROUCARIES]

Package: src:imagemagick
version: 8:6.8.9.9-5+deb8u5
Severity: grave
Tags: patch security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org
control: found -1 8:6.7.7.10-5+deb7u7
control: found -1 8:6.9.6.2+dfsg-2

Lead to segfault

https://www.imagemagick.org/discourse-server/viewtopic.php?f=3=30797

 
https://github.com/ImageMagick/ImageMagick/commit/56d6e20de489113617cbbddaf41e92600a34db22

Bug#845179: marked as done (FTBFS with super-fresh cython -- seems to carry pre-cythoned sources which get rebuilt during clean)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 17:34:18 +
with message-id 
and subject line Bug#845179: fixed in slixmpp 1.2.1-3
has caused the Debian Bug report #845179,
regarding FTBFS with super-fresh cython -- seems to carry pre-cythoned sources 
which get rebuilt during clean
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.)


-- 
845179: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slixmpp
Version: 1.2.1-2
Severity: serious
Justification: fails to build from source

While preparing for upload of fresh cython (0.25.2~b0-1) and running build of
rdepends python-aiohttp failed to build with

 fakeroot debian/rules clean
dh clean --with python3,sphinxdoc --buildsystem=pybuild
   dh_testdir -O--buildsystem=pybuild
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/build/slixmpp-1.2.1'
dh_auto_clean
I: pybuild base:184: python3.5 setup.py clean 
Compiling slixmpp/stringprep.pyx because it depends on 
/usr/lib/python3/dist-packages/Cython/Includes/libc/string.pxd.
[1/1] Cythonizing slixmpp/stringprep.pyx
running clean
removing '/build/slixmpp-1.2.1/.pybuild/pythonX.Y_3.5/build' (and everything 
under it)
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-3.5' does not exist -- can't clean it
make -C docs clean
make[2]: Entering directory '/build/slixmpp-1.2.1/docs'
rm -rf _build/*
make[2]: Leaving directory '/build/slixmpp-1.2.1/docs'
make[1]: Leaving directory '/build/slixmpp-1.2.1'
   dh_clean -O--buildsystem=pybuild
 dpkg-source -b slixmpp-1.2.1
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building slixmpp using existing ./slixmpp_1.2.1.orig.tar.gz
dpkg-source: warning: ignoring deletion of directory slixmpp.egg-info
dpkg-source: warning: ignoring deletion of file slixmpp.egg-info/top_level.txt, 
use --include-removal to override
dpkg-source: warning: ignoring deletion of file slixmpp.egg-info/SOURCES.txt, 
use --include-removal to override
dpkg-source: warning: ignoring deletion of file slixmpp.egg-info/requires.txt, 
use --include-removal to override
dpkg-source: warning: ignoring deletion of file 
slixmpp.egg-info/dependency_links.txt, use --include-removal to override
dpkg-source: warning: ignoring deletion of file slixmpp.egg-info/PKG-INFO, use 
--include-removal to override
dpkg-source: info: local changes detected, the modified files are:
 slixmpp-1.2.1/slixmpp/stringprep.c
dpkg-source: error: aborting due to unexpected upstream changes, see 
/tmp/slixmpp_1.2.1-2.diff.hICiN3
dpkg-source: info: you can integrate the local changes with dpkg-source --commit


so you can see that clean does recythonizing, which modifies shipped with
upstream tarball slixmpp-1.2.1/slixmpp/stringprep.c

as a quick solution (besides cleansing the sources pkg) I think you
could make use of  dh_autoreconf so it memorizes changed files



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

Kernel: Linux 4.6.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)
--- End Message ---
--- Begin Message ---
Source: slixmpp
Source-Version: 1.2.1-3

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

Debian distribution maintenance software
pp.
Tanguy Ortolo  (supplier of updated slixmpp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Nov 2016 17:39:36 +0100
Source: slixmpp
Binary: python3-slixmpp python3-slixmpp-lib python-slixmpp-doc
Architecture: source all amd64
Version: 1.2.1-3
Distribution: unstable
Urgency: medium
Maintainer: Tanguy Ortolo 
Changed-By: Tanguy Ortolo 
Description:
 python-slixmpp-doc - 

Processed: [bts-link] source package src:heat

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:heat
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #843232 (http://bugs.debian.org/843232)
> # Bug title: heat: CVE-2016-9185: template source URL allows network port scan
> #  * https://bugs.launchpad.net/bugs/1606500
> #  * remote status changed: In-Progress -> Fix-Released
> #  * closed upstream
> tags 843232 + fixed-upstream
Bug #843232 [src:heat] heat: CVE-2016-9185: template source URL allows network 
port scan
Added tag(s) fixed-upstream.
> usertags 843232 - status-In-Progress
Usertags were: status-In-Progress.
Usertags are now: .
> usertags 843232 + status-Fix-Released
There were no usertags set.
Usertags are now: status-Fix-Released.
> thanks
Stopping processing here.

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

Bug#843327: Not solved

[Robert Garcon]

Bug still present in 1.3.2~Beta0+dfsg-3

Bug#841588: marked as done (acoustid-fingerprinter: FTBFS: CheckSymbolExists.cxx:8:19: error: 'Q_WS_WIN' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 16:48:23 +
with message-id 
and subject line Bug#841588: fixed in acoustid-fingerprinter 0.6-6
has caused the Debian Bug report #841588,
regarding acoustid-fingerprinter: FTBFS: CheckSymbolExists.cxx:8:19: error: 
'Q_WS_WIN' was not declared in this scope
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.)


-- 
841588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: acoustid-fingerprinter
Version: 0.6-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /usr/bin/c++-I/usr/include/qt4  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o 
> CMakeFiles/cmTC_7d7bd.dir/CheckSymbolExists.cxx.o -c 
> /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx
> /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:
>  In function 'int main(int, char**)':
> /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:8:19:
>  error: 'Q_WS_WIN' was not declared in this scope
>return ((int*)(_WS_WIN))[argc];
>^~~~
> CMakeFiles/cmTC_7d7bd.dir/build.make:65: recipe for target 
> 'CMakeFiles/cmTC_7d7bd.dir/CheckSymbolExists.cxx.o' failed
> make[3]: *** [CMakeFiles/cmTC_7d7bd.dir/CheckSymbolExists.cxx.o] Error 1

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   
http://aws-logs.debian.net/2016/10/21/acoustid-fingerprinter_0.6-5_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: acoustid-fingerprinter
Source-Version: 0.6-6

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
acoustid-fingerprinter package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 21 Nov 2016 17:05:08 +0100
Source: acoustid-fingerprinter
Binary: acoustid-fingerprinter
Architecture: source
Version: 0.6-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Gianfranco Costamagna 
Description:
 acoustid-fingerprinter - Acoustid fingerprinter
Closes: 841588
Changes:
 acoustid-fingerprinter (0.6-6) unstable; urgency=medium
 .
   * Upload to zesty
   * QA upload.
   * d/p/06-taglib.patch
 - cherry-pick upstream FTBFSfix with new taglib (Closes: #841588)
Checksums-Sha1:
 9c1137a22c8b40e4abfba610e836681c77dfaeed 2068 acoustid-fingerprinter_0.6-6.dsc
 cd863a6c959ba367fb170e74b469524791254d52 47208 
acoustid-fingerprinter_0.6-6.debian.tar.xz
Checksums-Sha256:
 5fab8afe0e37a60db3865d65cb8d334318f3062206bbe807b633c190a9152780 2068 
acoustid-fingerprinter_0.6-6.dsc
 41c4ab1c2476254078aeb2e4dcf17287e52d894d4c635a5283ad98ba9e8614eb 47208 
acoustid-fingerprinter_0.6-6.debian.tar.xz
Files:
 96759ff0aee0272481fd60d310eab512 2068 sound optional 

Bug#816588: marked as done (siproxd: FTBFS: LaTeX Error: File `ulem.sty' not found.)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 18:42:02 +0200
with message-id <20161121164202.aj4q4yjgryyt2...@bunk.spdns.de>
and subject line siproxd seems to build fine now
has caused the Debian Bug report #816588,
regarding siproxd: FTBFS: LaTeX Error: File `ulem.sty' 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.)


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

siproxd fails to build from source in unstable/amd64:

  [..]

  (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/infwarerr.sty)
  (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ltxcmds.sty)))
  (/usr/share/texlive/texmf-dist/tex/latex/colortbl/colortbl.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/marvosym/marvosym.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/graphics.cfg)))
  (/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty)
  
  ! LaTeX Error: File `ulem.sty' not found.
  
  Type X to quit or  to proceed,
  or enter new name. (Default extension: sty)
  
  Enter file name: 
  ! Emergency stop.
   
   
  l.27 \RequirePackage
  {fancyhdr}^^M
  !  ==> Fatal error occurred, no output PDF file produced!
  Transcript written on pdfjadetex.log.
  mktexfmt [ERROR]: running `pdftex -ini   -jobname=pdfjadetex 
-progname=pdfjadetex *pdfjadetex.ini >&2 &2 

siproxd.1:0.8.1-4.1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
siproxd seems to build fine now.

This looks as if there was a dependency problem in jadetex earlier this 
year, but now texlive-generic-recommended is properly pulled in.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Bug#843073: Debian Installer Stretch Alpha 8 release

[Raphael Hertzog]

On Mon, 21 Nov 2016, Guillem Jover wrote:
> Oh, and forgot to mention, this issue has been known for over 8
> months, and now there's this need to be pushy and rush things, etc.
> I certainly do not appreciate that.

I have not been involved in this project so I don't know its history
but #843073 is not 8 months old and I only discovered the problem
when I read about in on debian-devel and yet I have followed former
discussions on debian-devel about merged-/usr.

I can understand that this project was of no interest to you and that
while you were aware of the problem for 8 months, you did not want to fix
it by yourself. But then I'm also sympathetic to people who want
to get their project moving forward and I'm always happy to assist them
when it touches code that I wrote in dpkg. Feel free to direct such people
towards me when you are not interested yourself.

In this specific case, the merged-/usr was mostly done and ready before
the freeze but then this problem (which was possibly underrated by Marco
or whoever else was aware of it) came into light. I would not like that we
end up with this feature reverted at freeze time because you did not find
the time to merge the patch. Hence my query.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Bug#843073: Debian Installer Stretch Alpha 8 release

[Marco d'Itri]

On Nov 21, Guillem Jover  wrote:

> Oh, and forgot to mention, this issue has been known for over 8
> months, and now there's this need to be pushy and rush things, etc.
> I certainly do not appreciate that.
No, not really: it was not clear (e.g. I could never reproduce it) until 
very recently.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#843073: Debian Installer Stretch Alpha 8 release

[Guillem Jover]

On Mon, 2016-11-21 at 17:09:50 +0100, Guillem Jover wrote:
> On Mon, 2016-11-21 at 16:38:07 +0100, Raphael Hertzog wrote:
> > I can offer to upload dpkg 1.18.15.1 to sid with just those patches if
> > it relieves you from handling an intermediary upload until you
> > release 1.18.16 on your usual schedule.
> 
> No, thanks. That's not the blocker. Also the release intervals will be
> shorter for a while, at least until deeper freeze stages.

Oh, and forgot to mention, this issue has been known for over 8
months, and now there's this need to be pushy and rush things, etc.
I certainly do not appreciate that.

Regards,
Guillem

Bug#844848: marked as done (mgba: FTBFS: ld: cannot find -lncurses)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 16:03:26 +
with message-id 
and subject line Bug#844573: fixed in libedit 3.1-20160903-2
has caused the Debian Bug report #844573,
regarding mgba: FTBFS: ld: cannot find -lncurses
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.)


-- 
844573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mgba
Version: 0.4.1+dfsg1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /usr/bin/cc  -fPIC -g -O2 -fdebug-prefix-map=/<>/mgba-0.4.1+dfsg1=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wextra -std=c99 -pthread -Wl,-z,relro -Wl,-z,now 
> -Wl,--as-needed -shared -Wl,-soname,libmgba.so.0.4 -o libmgba.so.0.4.1 
> CMakeFiles/mgba.dir/src/arm/arm.c.o 
> CMakeFiles/mgba.dir/src/arm/decoder-arm.c.o 
> CMakeFiles/mgba.dir/src/arm/decoder-thumb.c.o 
> CMakeFiles/mgba.dir/src/arm/decoder.c.o 
> CMakeFiles/mgba.dir/src/arm/isa-arm.c.o 
> CMakeFiles/mgba.dir/src/arm/isa-thumb.c.o 
> CMakeFiles/mgba.dir/src/gba/audio.c.o CMakeFiles/mgba.dir/src/gba/bios.c.o 
> CMakeFiles/mgba.dir/src/gba/cheats.c.o CMakeFiles/mgba.dir/src/gba/gba.c.o 
> CMakeFiles/mgba.dir/src/gba/hardware.c.o 
> CMakeFiles/mgba.dir/src/gba/hle-bios.c.o 
> CMakeFiles/mgba.dir/src/gba/input.c.o CMakeFiles/mgba.dir/src/gba/io.c.o 
> CMakeFiles/mgba.dir/src/gba/memory.c.o 
> CMakeFiles/mgba.dir/src/gba/savedata.c.o 
> CMakeFiles/mgba.dir/src/gba/serialize.c.o 
> CMakeFiles/mgba.dir/src/gba/sharkport.c.o CMakeFiles/mgba.dir/src/gba/sio.c.o 
> CMakeFiles/mgba.dir/src/gba/video.c.o 
> CMakeFiles/mgba.dir/src/gba/cheats/codebreaker.c.o 
> CMakeFiles/mgba.dir/src/gba/cheats/gameshark.c.o 
> CMakeFiles/mgba.dir/src/gba/cheats/parv3.c.o 
> CMakeFiles/mgba.dir/src/gba/context/config.c.o 
> CMakeFiles/mgba.dir/src/gba/context/context.c.o 
> CMakeFiles/mgba.dir/src/gba/context/directories.c.o 
> CMakeFiles/mgba.dir/src/gba/context/overrides.c.o 
> CMakeFiles/mgba.dir/src/gba/context/sync.c.o 
> CMakeFiles/mgba.dir/src/debugger/debugger.c.o 
> CMakeFiles/mgba.dir/src/debugger/memory-debugger.c.o 
> CMakeFiles/mgba.dir/src/debugger/gdb-stub.c.o 
> CMakeFiles/mgba.dir/src/gba/renderers/software-bg.c.o 
> CMakeFiles/mgba.dir/src/gba/renderers/software-mode0.c.o 
> CMakeFiles/mgba.dir/src/gba/renderers/software-obj.c.o 
> CMakeFiles/mgba.dir/src/gba/renderers/video-software.c.o 
> CMakeFiles/mgba.dir/src/util/circle-buffer.c.o 
> CMakeFiles/mgba.dir/src/util/configuration.c.o 
> CMakeFiles/mgba.dir/src/util/crc32.c.o 
> CMakeFiles/mgba.dir/src/util/formatting.c.o 
> CMakeFiles/mgba.dir/src/util/gui.c.o CMakeFiles/mgba.dir/src/util/hash.c.o 
> CMakeFiles/mgba.dir/src/util/nointro.c.o 
> CMakeFiles/mgba.dir/src/util/patch-ips.c.o 
> CMakeFiles/mgba.dir/src/util/patch-ups.c.o 
> CMakeFiles/mgba.dir/src/util/patch.c.o 
> CMakeFiles/mgba.dir/src/util/png-io.c.o 
> CMakeFiles/mgba.dir/src/util/string.c.o 
> CMakeFiles/mgba.dir/src/util/table.c.o CMakeFiles/mgba.dir/src/util/vfs.c.o 
> CMakeFiles/mgba.dir/version.c.o CMakeFiles/mgba.dir/src/util/vfs/vfs-mem.c.o 
> CMakeFiles/mgba.dir/src/util/vfs/vfs-fd.c.o 
> CMakeFiles/mgba.dir/src/util/vfs/vfs-dirent.c.o 
> CMakeFiles/mgba.dir/src/platform/posix/memory.c.o 
> CMakeFiles/mgba.dir/src/third-party/inih/ini.c.o 
> CMakeFiles/mgba.dir/src/third-party/blip_buf/blip_buf.c.o 
> CMakeFiles/mgba.dir/src/gba/rr/mgm.c.o CMakeFiles/mgba.dir/src/gba/rr/rr.c.o 
> CMakeFiles/mgba.dir/src/gba/rr/vbm.c.o 
> CMakeFiles/mgba.dir/src/gba/supervisor/cli.c.o 
> CMakeFiles/mgba.dir/src/gba/supervisor/export.c.o 
> CMakeFiles/mgba.dir/src/gba/supervisor/thread.c.o 
> CMakeFiles/mgba.dir/src/platform/commandline.c.o 
> CMakeFiles/mgba.dir/src/gba/sio/lockstep.c.o 
> CMakeFiles/mgba.dir/src/debugger/cli-debugger.c.o 
> CMakeFiles/mgba.dir/src/debugger/parser.c.o 
> CMakeFiles/mgba.dir/src/platform/ffmpeg/ffmpeg-encoder.c.o 
> CMakeFiles/mgba.dir/src/platform/imagemagick/imagemagick-gif-encoder.c.o 
> CMakeFiles/mgba.dir/src/util/vfs/vfs-zip.c.o 
> CMakeFiles/mgba.dir/src/util/vfs/vfs-lzma.c.o 
> CMakeFiles/mgba.dir/src/third-party/lzma/7zAlloc.c.o 
> CMakeFiles/mgba.dir/src/third-party/lzma/7zArcIn.c.o 
> CMakeFiles/mgba.dir/src/third-party/lzma/7zBuf.c.o 
> CMakeFiles/mgba.dir/src/third-party/lzma/7zBuf2.c.o 
> 

Bug#843073: Debian Installer Stretch Alpha 8 release

[Guillem Jover]

Just a brief reply.

On Mon, 2016-11-21 at 16:38:07 +0100, Raphael Hertzog wrote:
> On Mon, 14 Nov 2016, Michael Biebl wrote:
> > Just for the record: I can confirm it fixes the problem in dpkg-shlibdeps.
> [...]
> > Guillem, it would be great if you can upload a fixed dpkg soon.
> 
> A full week went by already. What's your plan?

First I have to go over a list of queued pending items and then I'll
get to this during this week. I have not yet reviewed the patches (in
part because I didn't do much Debian stuff last week due to lack of
motivation after an unpleasant interaction precisely due to this
issue, and TBH it has become one of those energey drainers), there's
a pending run in rebootstrap by Helmut (which is now waiting for a
gixed gcc), and then I need to write a mail summary of the current
situation and implications.

> I can offer to upload dpkg 1.18.15.1 to sid with just those patches if
> it relieves you from handling an intermediary upload until you
> release 1.18.16 on your usual schedule.

No, thanks. That's not the blocker. Also the release intervals will be
shorter for a while, at least until deeper freeze stages.

Regards,
Guillem

Bug#844857: marked as done (libneo4j-client: FTBFS: ld: cannot find -lncurses)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 16:03:26 +
with message-id 
and subject line Bug#844573: fixed in libedit 3.1-20160903-2
has caused the Debian Bug report #844573,
regarding libneo4j-client: FTBFS: ld: cannot find -lncurses
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.)


-- 
844573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libneo4j-client
Version: 1.2.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> /bin/bash ../../libtool  --tag=CC   --mode=link gcc  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -std=gnu11 -fvisibility=hidden -pipe -Wall -W -Werror 
> -Wno-unused-parameter -Wno-missing-field-initializers -Wpointer-arith 
> -Wstrict-prototypes -Wcast-qual -Wcast-align -Wno-error=unused-function 
> -Wno-error=unused-variable -Wno-error=deprecated-declarations  -Wl,-z,relro 
> -Wl,-z,now -o neo4j-client neo4j_client-neo4j-client.o 
> neo4j_client-authentication.o neo4j_client-batch.o 
> neo4j_client-colorization.o neo4j_client-commands.o neo4j_client-connect.o 
> neo4j_client-evaluate.o neo4j_client-interactive.o neo4j_client-options.o 
> neo4j_client-readpass.o neo4j_client-render.o neo4j_client-state.o 
> neo4j_client-util.o neo4j_client-verification.o 
> ../../src/lib/libneo4j-client.la -ledit -lncurses -lbsd -lcypher-parser -lbsd 
> libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -std=gnu11 
> -fvisibility=hidden -pipe -Wall -W -Werror -Wno-unused-parameter 
> -Wno-missing-field-initializers -Wpointer-arith -Wstrict-prototypes 
> -Wcast-qual -Wcast-align -Wno-error=unused-function 
> -Wno-error=unused-variable -Wno-error=deprecated-declarations -Wl,-z 
> -Wl,relro -Wl,-z -Wl,now -o .libs/neo4j-client neo4j_client-neo4j-client.o 
> neo4j_client-authentication.o neo4j_client-batch.o 
> neo4j_client-colorization.o neo4j_client-commands.o neo4j_client-connect.o 
> neo4j_client-evaluate.o neo4j_client-interactive.o neo4j_client-options.o 
> neo4j_client-readpass.o neo4j_client-render.o neo4j_client-state.o 
> neo4j_client-util.o neo4j_client-verification.o  
> ../../src/lib/.libs/libneo4j-client.so -ledit -lncurses -lcypher-parser -lbsd 
> -pthread
> /usr/bin/ld: cannot find -lncurses
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/libneo4j-client_1.2.1-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated libedit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 21 nov 2016 16:20:15 +0100
Source: libedit
Binary: libedit2 libedit-dev libedit2-dbg
Architecture: source amd64
Version: 3.1-20160903-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 libedit-dev - BSD editline and history libraries (development files)
 libedit2   - BSD editline and history libraries
 libedit2-dbg - BSD editline and history libraries (debug package)
Closes: 844573
Changes:
 libedit (3.1-20160903-2) unstable; urgency=medium
 .
   * Add 

Bug#844705: marked as done (libedit-dev: Missing build dependency - ncurses)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 16:03:26 +
with message-id 
and subject line Bug#844573: fixed in libedit 3.1-20160903-2
has caused the Debian Bug report #844573,
regarding libedit-dev: Missing build dependency - ncurses
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.)


-- 
844573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libedit-dev
Version: 3.1-20160903-1
Severity: normal

Dear Maintainer,

An application makes use of the libedit-dev library. In a recent updated
from Debian8 to Debian9 the (previously working) build failed. The
reason for the failure was a missing library - ncurses:

[   68s] cc -g -fdebug-prefix-map=/usr/src/packages/BUILD=.
-fstack-protector-strong -Wformat -Werror=format-security -O3 -g -Wall
-Wextra -Werror -I/usr/include/json-c -I/usr/include/editline
-Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I ../ctrldb -Wl,-z,relro
-o vplsh \
[   68s]   vplsh.o ../ctrldb/ctrldb.o -lczmq -lzmq -ljson-c -ledit
-lncurses -lbsd
[   68s] /usr/bin/ld: cannot find -lncurses
[   68s] collect2: error: ld returned 1 exit status
[   68s] Makefile:21: recipe for target 'vplsh' failed
[   68s] make[2]: *** [vplsh] Error 1

The line in the makefile is simply:

   VPLSH_LIBS  = $(LIBS) $(shell pkg-config --libs libedit)

The fix was to modify the application control file so as to add
libncurses5-dev as an explicit dependency.

Ultimately the libedit-dev package file should have called out the
dependency and pulled in the necessary support library. Either that or
eliminate ncurses if its not actually required.

Thanks,

Mark

--- End Message ---
--- Begin Message ---
Source: libedit
Source-Version: 3.1-20160903-2

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated libedit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 21 nov 2016 16:20:15 +0100
Source: libedit
Binary: libedit2 libedit-dev libedit2-dbg
Architecture: source amd64
Version: 3.1-20160903-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 libedit-dev - BSD editline and history libraries (development files)
 libedit2   - BSD editline and history libraries
 libedit2-dbg - BSD editline and history libraries (debug package)
Closes: 844573
Changes:
 libedit (3.1-20160903-2) unstable; urgency=medium
 .
   * Add libncurses5-dev as a dependency of libedit-dev (Closes: #844573)
 Now officially required by upstream
   * Fix the vcs fields
Checksums-Sha1:
 b8f42eb448fe8c3cc52665fe3ad60bbf47d86d27 2208 libedit_3.1-20160903-2.dsc
 447d408fd7b6a67a251f462e20bb7694816d5f87 11176 
libedit_3.1-20160903-2.debian.tar.bz2
 4389ded73b361296f604d904bfb97bd1aef0160c 107612 
libedit-dev_3.1-20160903-2_amd64.deb
 b66dcbee19f182c6a8ed3e88c443721b8f5cb739 202426 
libedit2-dbg_3.1-20160903-2_amd64.deb
 27c23962a154feb4eb3605d070ff3cb66c318926 84720 
libedit2_3.1-20160903-2_amd64.deb
 b80bbae67dcc351e1281c1a78f0873f66f0e2a9b 5052 
libedit_3.1-20160903-2_20161121T152600z-2bd97474.buildinfo
Checksums-Sha256:
 9c954a038f6f55c26eba1b1163a68ad4c484a02802b320dc7811b6d13cc19363 2208 
libedit_3.1-20160903-2.dsc
 d885014ef46374c877f0c494fe0640349ee2aaec10bd74a04b6aece92a521273 11176 
libedit_3.1-20160903-2.debian.tar.bz2
 1017a8cf77d413c34260073d87e89dab1c1a67ba174a8ccc090dfdbc0636bbe3 107612 
libedit-dev_3.1-20160903-2_amd64.deb
 f305638d27738465651089be6ace81fd2126066820837f0f3c245ecb4d01d471 202426 
libedit2-dbg_3.1-20160903-2_amd64.deb
 8168be5f1d86ba641e8fd1793fac365548767204ea5a8f381eb2e21c9300b17e 84720 
libedit2_3.1-20160903-2_amd64.deb
 252991aba4e5a52f8fbe77cccef22b3a088a74fb559a21a293ce39ab7f6a 5052 
libedit_3.1-20160903-2_20161121T152600z-2bd97474.buildinfo
Files:
 06bedd8dcaa011f8b71990a67e058fc3 2208 libs standard 

Bug#844867: marked as done (knot: FTBFS: ld: cannot find -lncurses)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 16:03:26 +
with message-id 
and subject line Bug#844573: fixed in libedit 3.1-20160903-2
has caused the Debian Bug report #844573,
regarding knot: FTBFS: ld: cannot find -lncurses
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.)


-- 
844573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: knot
Version: 2.3.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> /bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -DNDEBUG -Wall -Werror=format-security 
> -Werror=implicit -Wstrict-prototypes  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
> -o knotd utils/knotd/knotd-main.o libknotd.la -lurcu -ldl -lpthread -lm 
> libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -DNDEBUG 
> -Wall -Werror=format-security -Werror=implicit -Wstrict-prototypes -Wl,-z 
> -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/knotd 
> utils/knotd/knotd-main.o  ./.libs/libknotd.a -lsystemd 
> /<>/src/.libs/libknot.so -llmdb 
> /<>/src/dnssec/.libs/libdnssec.so -lgnutls -lnettle -ljansson 
> /<>/src/zscanner/.libs/libzscanner.so -lurcu -ldl -lpthread -lm
> libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -DNDEBUG 
> -Wall -Werror=format-security -Werror=implicit -Wstrict-prototypes -Wl,-z 
> -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/kzonecheck 
> utils/kzonecheck/main.o utils/kzonecheck/zone_check.o  ./.libs/libknotd.a 
> -lsystemd /<>/src/.libs/libknot.so -llmdb 
> /<>/src/dnssec/.libs/libdnssec.so -lgnutls -lnettle -ljansson 
> /<>/src/zscanner/.libs/libzscanner.so -lurcu -ldl -lpthread -lm
> libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -DNDEBUG 
> -Wall -Werror=format-security -Werror=implicit -Wstrict-prototypes -Wl,-z 
> -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/knotc 
> utils/knotc/knotc-commands.o utils/knotc/knotc-estimator.o 
> utils/knotc/knotc-interactive.o utils/knotc/knotc-process.o 
> utils/knotc/knotc-main.o  ./.libs/libknotd.a -lsystemd 
> /<>/src/zscanner/.libs/libzscanner.so -lurcu ./.libs/libknotus.a 
> -lidn /<>/src/.libs/libknot.so -llmdb 
> /<>/src/dnssec/.libs/libdnssec.so -lgnutls -lnettle -ljansson 
> -ledit -lncurses -lbsd -ldl -lpthread -lm
> /usr/bin/ld: cannot find -lncurses
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/knot_2.3.2-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: libedit
Source-Version: 3.1-20160903-2

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated libedit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 21 nov 2016 16:20:15 +0100
Source: libedit
Binary: libedit2 libedit-dev libedit2-dbg
Architecture: source amd64
Version: 3.1-20160903-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 libedit-dev - BSD editline and history libraries (development files)
 libedit2   - BSD 

Bug#845211: marked as done (link-grammar: FTBFS: /usr/bin/ld: cannot find -lncurses)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 16:03:26 +
with message-id 
and subject line Bug#844573: fixed in libedit 3.1-20160903-2
has caused the Debian Bug report #844573,
regarding link-grammar: FTBFS: /usr/bin/ld: cannot find -lncurses
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.)


-- 
844573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: link-grammar
Version: 5.3.11-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

link-grammar fails to build from source in unstable/amd64:

  […]

  gcc -DPACKAGE_NAME=\"link-grammar\" -DPACKAGE_TARNAME=\"link-grammar\" 
-DPACKAGE_VERSION=\"5.3.11\" -DPACKAGE_STRING=\"link-grammar\ 5.3.11\" 
-DPACKAGE_BUGREPORT=\"link-gram...@googlegroups.com\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"link-grammar\" -DVERSION=\"5.3.11\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DSTDC_HEADERS=1 
-DHAVE_STRNDUP=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE_FORK=1 -DHAVE_VFORK=1 
-DHAVE_WORKING_VFORK=1 -DHAVE_WORKING_FORK=1 -DHAVE_PRCTL=1 
-DHAVE_LOCALE_T_IN_LOCALE_H=1 -DHAVE_MKLIT=1 -DHAVE_LIBSTDC__=1 
-DHAVE_HUNSPELL=1 -DHUNSPELL_DICT_DIR=\"/usr/share/myspell/dicts\" 
-DHAVE_EDITLINE=1 -DHAVE_WIDECHAR_EDITLINE=1 -DHAVE_REGEXEC=1 
-DHAVE_PYTHON=\"2.7\" -DHAVE_MAYBE_UNINITIALIZED=1 -DVERSION=\"5.3.11\" 
-DDICTIONARY_DIR=\"/usr/share/link-grammar\" -I.  -I.. -I.. -Wstrict-prototypes 
-Wmissing-prototypes -Wnested-externs -Wold-style-definition  -Wall -Wextra 
-Wsign-compare -Werror-implicit-function-declaration -Wpointer-arith 
-Wwrite-strings -Wmissing-declarations -Wpacked -Wswitch-enum 
-Wmissing-format-attribute -Wstrict-aliasing -Winit-self 
-Wno-missing-field-initializers -Wno-unused-parameter -Wno-attributes 
-Wno-long-long -Winline -I/usr/include/hunspell -I/usr/include/editline 
-Wdate-time -D_FORTIFY_SOURCE=2 -DUSE_PTHREADS=1 -DUSE_SAT_SOLVER=1  -g -O2 
-fdebug-prefix-map=«BUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -O3 -std=c11 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE 
-D_DEFAULT_SOURCE -c -o parser-utilities.o parser-utilities.c
  /bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 
-fdebug-prefix-map=«BUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -O3 -std=c11 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE 
-D_DEFAULT_SOURCE -fno-strict-aliasing -Wl,-z,relro -Wl,-z,now -Wl,-O1 
-Wl,--as-needed -o link-parser link-parser.o command-line.o lg_readline.o 
parser-utilities.o ../link-grammar/liblink-grammar.la -ledit -lncurses -lbsd   
-lminisat  -lstdc++ 
  libtool: link: gcc -g -O2 -fdebug-prefix-map=«BUILDDIR»=. 
-fstack-protector-strong -Wformat -Werror=format-security -O3 -std=c11 
-D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -D_DEFAULT_SOURCE 
-fno-strict-aliasing -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-O1 -o 
.libs/link-parser link-parser.o command-line.o lg_readline.o parser-utilities.o 
 -Wl,--as-needed ../link-grammar/.libs/liblink-grammar.so -ledit -lncurses 
-lbsd -lminisat -lstdc++
  /usr/bin/ld: cannot find -lncurses
  collect2: error: ld returned 1 exit status
  Makefile:469: recipe for target 'link-parser' failed
  make[2]: *** [link-parser] Error 1
  make[2]: Leaving directory '«BUILDDIR»/link-parser'
  Makefile:539: recipe for target 'all-recursive' failed
  make[1]: *** [all-recursive] Error 1
  make[1]: Leaving directory '«BUILDDIR»'
  dh_auto_build: make -j9 returned exit code 2
  debian/rules:7: 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
   `-


link-grammar.5.3.11-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: libedit
Source-Version: 3.1-20160903-2

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

Bug#844885: marked as done (dnsdist: FTBFS: ld: cannot find -lncurses)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 16:03:26 +
with message-id 
and subject line Bug#844573: fixed in libedit 3.1-20160903-2
has caused the Debian Bug report #844573,
regarding dnsdist: FTBFS: ld: cannot find -lncurses
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.)


-- 
844573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dnsdist
Version: 1.0.0-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> /bin/bash ./libtool  --tag=CXX   --mode=link x86_64-linux-gnu-g++  -fPIE 
> -DPIE -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 --param ssp-buffer-size=4 
> -fstack-protector -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security  -pie  -pthread  
> -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-z,relro -Wl,-z,now -o dnsdist dns.o 
> dnscrypt.o dnsdist.o dnsdist-cache.o dnsdist-carbon.o dnsdist-console.o 
> dnsdist-dnscrypt.o dnsdist-ecs.o dnsdist-lua.o dnsdist-lua2.o 
> dnsdist-protobuf.o dnsdist-rings.o dnsdist-tcp.o dnsdist-web.o dnslabeltext.o 
> dnsname.o dnsparser.o dnswriter.o ednsoptions.o ednscookies.o ednssubnet.o 
> iputils.o misc.o qtype.o remote_logger.o sodcrypto.o ext/json11/json11.o  
> -llua5.2 -ledit -lncurses -lbsd  ./ext/yahttp/yahttp/libyahttp.la -lsodium
>  
> libtool: link: x86_64-linux-gnu-g++ -fPIE -DPIE -U_FORTIFY_SOURCE 
> -D_FORTIFY_SOURCE=2 --param ssp-buffer-size=4 -fstack-protector -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -pie -pthread -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-z 
> -Wl,relro -Wl,-z -Wl,now -o dnsdist dns.o dnscrypt.o dnsdist.o 
> dnsdist-cache.o dnsdist-carbon.o dnsdist-console.o dnsdist-dnscrypt.o 
> dnsdist-ecs.o dnsdist-lua.o dnsdist-lua2.o dnsdist-protobuf.o dnsdist-rings.o 
> dnsdist-tcp.o dnsdist-web.o dnslabeltext.o dnsname.o dnsparser.o dnswriter.o 
> ednsoptions.o ednscookies.o ednssubnet.o iputils.o misc.o qtype.o 
> remote_logger.o sodcrypto.o ext/json11/json11.o  -llua5.2 -ledit -lncurses 
> -lbsd ./ext/yahttp/yahttp/.libs/libyahttp.a -lsodium -pthread
> /usr/bin/ld: cannot find -lncurses
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/dnsdist_1.0.0-2_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated libedit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 21 nov 2016 16:20:15 +0100
Source: libedit
Binary: libedit2 libedit-dev libedit2-dbg
Architecture: source amd64
Version: 3.1-20160903-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 libedit-dev - BSD editline and history libraries (development files)
 libedit2   - BSD editline and history libraries
 libedit2-dbg - BSD editline and history libraries (debug package)
Closes: 844573
Changes:
 libedit (3.1-20160903-2) unstable; urgency=medium
 .
   * Add libncurses5-dev as a dependency of libedit-dev (Closes: #844573)
 Now officially required by upstream
   * Fix the vcs fields
Checksums-Sha1:
 b8f42eb448fe8c3cc52665fe3ad60bbf47d86d27 2208 libedit_3.1-20160903-2.dsc
 

Bug#844901: marked as done (openssh: FTBFS: configure: error: libedit not found)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 16:03:26 +
with message-id 
and subject line Bug#844573: fixed in libedit 3.1-20160903-2
has caused the Debian Bug report #844573,
regarding openssh: FTBFS: configure: error: libedit 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.)


-- 
844573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openssh
Version: 1:7.3p1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> checking for /proc/pid/fd directory... yes
> checking for libwrap... yes
> checking for pkg-config... /usr/bin/pkg-config
> checking if /usr/bin/pkg-config knows about libedit... yes
> checking for el_init in -ledit... no
> configure: error: libedit not found
>   "tail -v -n +0 config.log"

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/openssh_7.3p1-3_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated libedit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 21 nov 2016 16:20:15 +0100
Source: libedit
Binary: libedit2 libedit-dev libedit2-dbg
Architecture: source amd64
Version: 3.1-20160903-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 libedit-dev - BSD editline and history libraries (development files)
 libedit2   - BSD editline and history libraries
 libedit2-dbg - BSD editline and history libraries (debug package)
Closes: 844573
Changes:
 libedit (3.1-20160903-2) unstable; urgency=medium
 .
   * Add libncurses5-dev as a dependency of libedit-dev (Closes: #844573)
 Now officially required by upstream
   * Fix the vcs fields
Checksums-Sha1:
 b8f42eb448fe8c3cc52665fe3ad60bbf47d86d27 2208 libedit_3.1-20160903-2.dsc
 447d408fd7b6a67a251f462e20bb7694816d5f87 11176 
libedit_3.1-20160903-2.debian.tar.bz2
 4389ded73b361296f604d904bfb97bd1aef0160c 107612 
libedit-dev_3.1-20160903-2_amd64.deb
 b66dcbee19f182c6a8ed3e88c443721b8f5cb739 202426 
libedit2-dbg_3.1-20160903-2_amd64.deb
 27c23962a154feb4eb3605d070ff3cb66c318926 84720 
libedit2_3.1-20160903-2_amd64.deb
 b80bbae67dcc351e1281c1a78f0873f66f0e2a9b 5052 
libedit_3.1-20160903-2_20161121T152600z-2bd97474.buildinfo
Checksums-Sha256:
 9c954a038f6f55c26eba1b1163a68ad4c484a02802b320dc7811b6d13cc19363 2208 
libedit_3.1-20160903-2.dsc
 d885014ef46374c877f0c494fe0640349ee2aaec10bd74a04b6aece92a521273 11176 
libedit_3.1-20160903-2.debian.tar.bz2
 1017a8cf77d413c34260073d87e89dab1c1a67ba174a8ccc090dfdbc0636bbe3 107612 
libedit-dev_3.1-20160903-2_amd64.deb
 f305638d27738465651089be6ace81fd2126066820837f0f3c245ecb4d01d471 202426 
libedit2-dbg_3.1-20160903-2_amd64.deb
 8168be5f1d86ba641e8fd1793fac365548767204ea5a8f381eb2e21c9300b17e 84720 
libedit2_3.1-20160903-2_amd64.deb
 252991aba4e5a52f8fbe77cccef22b3a088a74fb559a21a293ce39ab7f6a 5052 
libedit_3.1-20160903-2_20161121T152600z-2bd97474.buildinfo
Files:
 06bedd8dcaa011f8b71990a67e058fc3 2208 libs standard libedit_3.1-20160903-2.dsc
 8cc652602763eb2d6be63bbf365a7771 11176 libs standard 
libedit_3.1-20160903-2.debian.tar.bz2
 e339f5a7f44169977ec3e794b8161288 107612 libdevel optional 

Bug#844573: marked as done (link-grammar: FTBFS (cannot find -lncurses))

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 16:03:26 +
with message-id 
and subject line Bug#844573: fixed in libedit 3.1-20160903-2
has caused the Debian Bug report #844573,
regarding link-grammar: FTBFS (cannot find -lncurses)
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.)


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

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2
   dh_testdir -i
   dh_update_autotools_config -i
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf --as-needed
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'

[... snipped ...]

build:

BUILD SUCCESSFUL
Total time: 1 second
make[3]: Leaving directory '/<>/bindings/java'
Making all in ocaml
make[3]: Entering directory '/<>/bindings/ocaml'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<>/bindings/ocaml'
Making all in python
make[3]: Entering directory '/<>/bindings/python'
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ 
-DPACKAGE_NAME=\"link-grammar\" -DPACKAGE_TARNAME=\"link-grammar\" 
-DPACKAGE_VERSION=\"5.3.11\" -DPACKAGE_STRING=\"link-grammar\ 5.3.11\" 
-DPACKAGE_BUGREPORT=\"link-gram...@googlegroups.com\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"link-grammar\" -DVERSION=\"5.3.11\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DSTDC_HEADERS=1 
-DHAVE_STRNDUP=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE_FORK=1 -DHAVE_VFORK=1 
-DHAVE_WORKING_VFORK=1 -DHAVE_WORKING_FORK=1 -DHAVE_PRCTL=1 
-DHAVE_LOCALE_T_IN_LOCALE_H=1 -DHAVE_MKLIT=1 -DHAVE_LIBSTDC__=1 
-DHAVE_HUNSPELL=1 -DHUNSPELL_DICT_DIR=\"/usr/share/myspell/dicts\" 
-DHAVE_EDITLINE=1 -DHAVE_WIDECHAR_EDITLINE=1 -DHAVE_REGEXEC=1 
-DHAVE_PYTHON=\"2.7\" -DHAVE_MAYBE_UNINITIALIZED=1 -I.   
-I/usr/include/python2.7 -I../.. -I../.. -Wdate-t
 ime -D_FORTIFY_SOURCE=2 -DUSE_PTHREADS=1 -DUSE_SAT_SOLVER=1  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -O3 -Wall -std=c++11 -c -o 
../../bindings/python/_clinkgrammar_la-lg_python_wrap.lo `test -f 
'../../bindings/python/lg_python_wrap.cc' || echo 
'./'`../../bindings/python/lg_python_wrap.cc
libtool: compile:  g++ -DPACKAGE_NAME=\"link-grammar\" 
-DPACKAGE_TARNAME=\"link-grammar\" -DPACKAGE_VERSION=\"5.3.11\" 
"-DPACKAGE_STRING=\"link-grammar 5.3.11\"" 
-DPACKAGE_BUGREPORT=\"link-gram...@googlegroups.com\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"link-grammar\" -DVERSION=\"5.3.11\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DSTDC_HEADERS=1 
-DHAVE_STRNDUP=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE_FORK=1 -DHAVE_VFORK=1 
-DHAVE_WORKING_VFORK=1 -DHAVE_WORKING_FORK=1 -DHAVE_PRCTL=1 
-DHAVE_LOCALE_T_IN_LOCALE_H=1 -DHAVE_MKLIT=1 -DHAVE_LIBSTDC__=1 
-DHAVE_HUNSPELL=1 -DHUNSPELL_DICT_DIR=\"/usr/share/myspell/dicts\" 
-DHAVE_EDITLINE=1 -DHAVE_WIDECHAR_EDITLINE=1 -DHAVE_REGEXEC=1 
-DHAVE_PYTHON=\"2.7\" -DHAVE_MAYBE_UNINITIALIZED=1 -I. -I/usr/include/python2.7 
-I../.. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -DUSE_PTHR
 EADS=1 -DUSE_SAT_SOLVER=1 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O3 -Wall -std=c++11 
-c ../../bindings/python/lg_python_wrap.cc  -fPIC -DPIC -o 
../../bindings/python/.libs/_clinkgrammar_la-lg_python_wrap.o
/bin/bash ../../libtool  --tag=CXX   --mode=link g++  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -O3 -Wall -std=c++11 -version-info 8:11:3   -module 
-no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--as-needed -o 
_clinkgrammar.la -rpath /usr/lib/python2.7/dist-packages/linkgrammar 

Bug#844853: marked as done (link-grammar: FTBFS: ld: cannot find -lncurses)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 16:03:26 +
with message-id 
and subject line Bug#844573: fixed in libedit 3.1-20160903-2
has caused the Debian Bug report #844573,
regarding link-grammar: FTBFS: ld: cannot find -lncurses
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.)


-- 
844573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: link-grammar
Version: 5.3.11-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> /bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -O3 -std=c11 -D_BSD_SOURCE -D_SVID_SOURCE 
> -D_GNU_SOURCE -D_DEFAULT_SOURCE -fno-strict-aliasing -Wl,-z,relro -Wl,-z,now 
> -Wl,-O1 -Wl,--as-needed -o link-parser link-parser.o command-line.o 
> lg_readline.o parser-utilities.o ../link-grammar/liblink-grammar.la -ledit 
> -lncurses -lbsd   -lminisat  -lstdc++ 
> libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -O3 -std=c11 
> -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -D_DEFAULT_SOURCE 
> -fno-strict-aliasing -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-O1 -o 
> .libs/link-parser link-parser.o command-line.o lg_readline.o 
> parser-utilities.o  -Wl,--as-needed ../link-grammar/.libs/liblink-grammar.so 
> -ledit -lncurses -lbsd -lminisat -lstdc++
> /usr/bin/ld: cannot find -lncurses
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/link-grammar_5.3.11-2_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated libedit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 21 nov 2016 16:20:15 +0100
Source: libedit
Binary: libedit2 libedit-dev libedit2-dbg
Architecture: source amd64
Version: 3.1-20160903-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 libedit-dev - BSD editline and history libraries (development files)
 libedit2   - BSD editline and history libraries
 libedit2-dbg - BSD editline and history libraries (debug package)
Closes: 844573
Changes:
 libedit (3.1-20160903-2) unstable; urgency=medium
 .
   * Add libncurses5-dev as a dependency of libedit-dev (Closes: #844573)
 Now officially required by upstream
   * Fix the vcs fields
Checksums-Sha1:
 b8f42eb448fe8c3cc52665fe3ad60bbf47d86d27 2208 libedit_3.1-20160903-2.dsc
 447d408fd7b6a67a251f462e20bb7694816d5f87 11176 
libedit_3.1-20160903-2.debian.tar.bz2
 4389ded73b361296f604d904bfb97bd1aef0160c 107612 
libedit-dev_3.1-20160903-2_amd64.deb
 b66dcbee19f182c6a8ed3e88c443721b8f5cb739 202426 
libedit2-dbg_3.1-20160903-2_amd64.deb
 27c23962a154feb4eb3605d070ff3cb66c318926 84720 
libedit2_3.1-20160903-2_amd64.deb
 b80bbae67dcc351e1281c1a78f0873f66f0e2a9b 5052 
libedit_3.1-20160903-2_20161121T152600z-2bd97474.buildinfo
Checksums-Sha256:
 9c954a038f6f55c26eba1b1163a68ad4c484a02802b320dc7811b6d13cc19363 2208 
libedit_3.1-20160903-2.dsc
 d885014ef46374c877f0c494fe0640349ee2aaec10bd74a04b6aece92a521273 11176 
libedit_3.1-20160903-2.debian.tar.bz2
 

Bug#844807: marked as done (ceph: FTBFS: ld: cannot find -lncurses)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 16:03:26 +
with message-id 
and subject line Bug#844573: fixed in libedit 3.1-20160903-2
has caused the Debian Bug report #844573,
regarding ceph: FTBFS: ld: cannot find -lncurses
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.)


-- 
844573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ceph
Version: 0.80.11-1.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> /bin/bash ../libtool  --tag=CXX   --mode=link g++ -I/usr/include/nss 
> -I/usr/include/nspr  -Wall -Wtype-limits -Wignored-qualifiers -Winit-self 
> -Wpointer-arith -Werror=format-security -fno-strict-aliasing -fsigned-char 
> -rdynamic -ftemplate-depth-1024 -Wnon-virtual-dtor -Wno-invalid-offsetof   
> -fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc 
> -fno-builtin-free -Wstrict-null-sentinel -std=gnu++98 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wl,--as-needed -latomic_ops -Wl,-z,relro -Wl,-z,now 
> -Wl,--as-needed -o libclient_fuse.la  client/fuse_ll.lo libclient.la -lfuse 
> -lboost_thread -lboost_system 
> libtool: link: (cd .libs/libclient_fuse.lax/libclient.a && ar x 
> "/<>/src/./.libs/libclient.a")
> libtool: link: /usr/bin/nm -B  .libs/libcephfs.o   ./.libs/libclient.a 
> ./.libs/libcommon.a | sed -n -e 's/^.*[ 
> ]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][  
> ]*\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2 \2/p' | sed '/ __gnu_lto/d' | /bin/sed 
> 's/.* //' | sort | uniq > .libs/libcephfs.exp
> libtool: link: ar cru .libs/libclient_fuse.a client/.libs/fuse_ll.o   
> .libs/libclient_fuse.lax/libclient.a/Client.o 
> .libs/libclient_fuse.lax/libclient.a/ClientSnapRealm.o 
> .libs/libclient_fuse.lax/libclient.a/Dentry.o 
> .libs/libclient_fuse.lax/libclient.a/Filer.o 
> .libs/libclient_fuse.lax/libclient.a/Inode.o 
> .libs/libclient_fuse.lax/libclient.a/Journaler.o 
> .libs/libclient_fuse.lax/libclient.a/MetaRequest.o 
> .libs/libclient_fuse.lax/libclient.a/MetaSession.o 
> .libs/libclient_fuse.lax/libclient.a/ObjectCacher.o 
> .libs/libclient_fuse.lax/libclient.a/Objecter.o 
> .libs/libclient_fuse.lax/libclient.a/Striper.o 
> .libs/libclient_fuse.lax/libclient.a/Trace.o 
> ar: `u' modifier ignored since `D' is the default (see `U')
> libtool: link: /bin/grep -E -e "^ceph_.*" ".libs/libcephfs.exp" > 
> ".libs/libcephfs.expT"
> libtool: link: mv -f ".libs/libcephfs.expT" ".libs/libcephfs.exp"
> libtool: link: g++  -fPIC -DPIC -shared -nostdlib 
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/crti.o 
> /usr/lib/gcc/x86_64-linux-gnu/6/crtbeginS.o  .libs/libcephfs.o  
> -Wl,--whole-archive ./.libs/libclient.a ./.libs/libcommon.a 
> -Wl,--no-whole-archive  /usr/lib/x86_64-linux-gnu/libatomic_ops.a 
> -Wl,--as-needed -ledit -lncurses -lbsd -ldl -lpthread -lnss3 -lnssutil3 
> -lsmime3 -lssl3 -lplds4 -lplc4 -lnspr4 -luuid -lrt -lboost_thread 
> -lboost_system -L/usr/lib/gcc/x86_64-linux-gnu/6 
> -L/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu 
> -L/usr/lib/gcc/x86_64-linux-gnu/6/../../../../lib -L/lib/x86_64-linux-gnu 
> -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib 
> -L/usr/lib/gcc/x86_64-linux-gnu/6/../../.. -lstdc++ -lm -lc -lgcc_s 
> /usr/lib/gcc/x86_64-linux-gnu/6/crtendS.o 
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/crtn.o  -g -O2 
> -fstack-protector-strong -Wl,-z -Wl,relro -Wl,-z -Wl,now   -Wl,-soname 
> -Wl,libcephfs.so.1 -Wl,-retain-symbols-file -Wl,.libs/libcephfs.exp -o 
> .libs/libcephfs.so.1.0.0
> /usr/bin/ld: cannot find -lncurses
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/ceph_0.80.11-1.1_unstable.log

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

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

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

A 

Bug#844898: marked as done (cross-toolchain-base-ports: FTBFS: gcc: error: unrecognized command line option '-mno-space-regs'; did you mean '-fno-make-deps'?)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 16:00:20 +
with message-id 
and subject line Bug#844898: fixed in cross-toolchain-base-ports 7
has caused the Debian Bug report #844898,
regarding cross-toolchain-base-ports: FTBFS: gcc: error: unrecognized command 
line option '-mno-space-regs'; did you mean '-fno-make-deps'?
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.)


-- 
844898: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cross-toolchain-base-ports
Version: 6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> powerpc-linux-gnu-gcc-6 -m64 argz-extract.c -c -std=gnu11 -fgnu89-inline  -O2 
> -Wall -Werror -Wundef -Wwrite-strings -fmerge-all-constants -frounding-math 
> -g -pipe -Wstrict-prototypes -Wold-style-definition -mlong-double-128
> -ftls-model=initial-exec-isystem 
> /<>/glibc-2.24/debian/include  -I../include 
> -I/<>/glibc-2.24/build-tree/powerpc-ppc64/string  
> -I/<>/glibc-2.24/build-tree/powerpc-ppc64  
> -I../sysdeps/unix/sysv/linux/powerpc/powerpc64/fpu  
> -I../sysdeps/unix/sysv/linux/powerpc/powerpc64  
> -I../sysdeps/unix/sysv/linux/wordsize-64  
> -I../sysdeps/unix/sysv/linux/powerpc  -I../sysdeps/powerpc/nptl  
> -I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux  
> -I../sysdeps/nptl  -I../sysdeps/pthread  -I../sysdeps/gnu  
> -I../sysdeps/unix/inet  -I../sysdeps/unix/sysv  -I../sysdeps/unix/powerpc  
> -I../sysdeps/unix  -I../sysdeps/posix  
> -I../sysdeps/powerpc/powerpc64/fpu/multiarch  
> -I../sysdeps/powerpc/powerpc64/fpu  -I../sysdeps/powerpc/powerpc64/multiarch  
> -I../sysdeps/powerpc/powerpc64  -I../sysdeps/wordsize-64  
> -I../sysdeps/powerpc/fpu  -I../sysdeps/powerpc  
> -I../sysdeps/ieee754/ldbl-128ibm  -I../sysdeps/ieee754/ldbl-opt  
> -I../sysdeps/ieee754/dbl-64  -I../sysdeps/ieee754/flt-32  
> -I../sysdeps/ieee754  -I../sysdeps/generic  -I.. -I../libio -I. -nostdinc 
> -isystem 
> /<>/debian/tmp.powerpc/usr/bin/../lib/gcc-cross/powerpc-linux-gnu/6/include
>  -isystem 
> /<>/debian/tmp.powerpc/usr/bin/../lib/gcc-cross/powerpc-linux-gnu/6/include-fixed
>  -isystem /<>/glibc-2.24/debian/include  -D_LIBC_REENTRANT 
> -include /<>/glibc-2.24/build-tree/powerpc-ppc64/libc-modules.h 
> -DMODULE_NAME=libc -include ../include/libc-symbols.h   -o 
> /<>/glibc-2.24/build-tree/powerpc-ppc64/string/argz-extract.o 
> -MD -MP -MF 
> /<>/glibc-2.24/build-tree/powerpc-ppc64/string/argz-extract.o.dt 
> -MT /<>/glibc-2.24/build-tree/powerpc-ppc64/string/argz-extract.o
> powerpc-linux-gnu-gcc-6 -m64 argz-insert.c -c -std=gnu11 -fgnu89-inline  -O2 
> -Wall -Werror -Wundef -Wwrite-strings -fmerge-all-constants -frounding-math 
> -g -pipe -Wstrict-prototypes -Wold-style-definition -mlong-double-128
> -ftls-model=initial-exec-isystem 
> /<>/glibc-2.24/debian/include  -I../include 
> -I/<>/glibc-2.24/build-tree/powerpc-ppc64/string  
> -I/<>/glibc-2.24/build-tree/powerpc-ppc64  
> -I../sysdeps/unix/sysv/linux/powerpc/powerpc64/fpu  
> -I../sysdeps/unix/sysv/linux/powerpc/powerpc64  
> -I../sysdeps/unix/sysv/linux/wordsize-64  
> -I../sysdeps/unix/sysv/linux/powerpc  -I../sysdeps/powerpc/nptl  
> -I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux  
> -I../sysdeps/nptl  -I../sysdeps/pthread  -I../sysdeps/gnu  
> -I../sysdeps/unix/inet  -I../sysdeps/unix/sysv  -I../sysdeps/unix/powerpc  
> -I../sysdeps/unix  -I../sysdeps/posix  
> -I../sysdeps/powerpc/powerpc64/fpu/multiarch  
> -I../sysdeps/powerpc/powerpc64/fpu  -I../sysdeps/powerpc/powerpc64/multiarch  
> -I../sysdeps/powerpc/powerpc64  -I../sysdeps/wordsize-64  
> -I../sysdeps/powerpc/fpu  -I../sysdeps/powerpc  
> -I../sysdeps/ieee754/ldbl-128ibm  -I../sysdeps/ieee754/ldbl-opt  
> -I../sysdeps/ieee754/dbl-64  -I../sysdeps/ieee754/flt-32  
> -I../sysdeps/ieee754  -I../sysdeps/generic  -I.. -I../libio -I. -nostdinc 
> -isystem 
> /<>/debian/tmp.powerpc/usr/bin/../lib/gcc-cross/powerpc-linux-gnu/6/include
>  -isystem 
> /<>/debian/tmp.powerpc/usr/bin/../lib/gcc-cross/powerpc-linux-gnu/6/include-fixed
>  -isystem /<>/glibc-2.24/debian/include  -D_LIBC_REENTRANT 
> -include /<>/glibc-2.24/build-tree/powerpc-ppc64/libc-modules.h 
> -DMODULE_NAME=libc -include ../include/libc-symbols.h   -o 
> /<>/glibc-2.24/build-tree/powerpc-ppc64/string/argz-insert.o -MD 
> -MP -MF 
>