Bug#892494: marked as done (diceware: "diceware" name violates trademark)

[Debian Bug Tracking System]

Your message dated Mon, 9 Apr 2018 01:20:51 -0400
with message-id <20180409052051.l2fglguq6hr3k...@curie.anarc.at>
and subject line Re: Bug#892494: diceware: "diceware" name violates trademark
has caused the Debian Bug report #892494,
regarding diceware: "diceware" name violates trademark
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.)


-- 
892494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: diceware
Severity: serious
Tags: upstream
Justification: Policy 2.1

As stated in the footer of http://world.std.com/%7Ereinhold/diceware.html the 
original creator of diceware claims a trademark on the name. I've filed a bug 
with upstream here: https://github.com/ulif/diceware/issues/48

Upstream does not have permission from Arnold Reinhold to use the trademark, 
but is aware of the issue and has reached out to Reinhold with no response. 
This package should probably be removed or renamed if upstream does not get a 
response soon.
--- End Message ---
--- Begin Message ---
Control: forwarded 892494 https://github.com/ulif/diceware/issues/48

On Fri, Mar 09, 2018 at 12:27:19PM -0500, Simon Fondrie-Teitler wrote:
> As stated in the footer of http://world.std.com/%7Ereinhold/diceware.html the 
> original creator of diceware claims a trademark on the name. I've filed a bug 
> with upstream here: https://github.com/ulif/diceware/issues/48
> 
> Upstream does not have permission from Arnold Reinhold to use the trademark, 
> but is aware of the issue and has reached out to Reinhold with no response. 
> This package should probably be removed or renamed if upstream does not get a 
> response soon.

On Thu, Mar 22, 2018 at 02:17:48PM +0100, Uli Fouquet wrote:
> this issue can be closed. I got a message from Mr. Reinhold granting me
> use of "diceware" explicitly, given that I keep the Python system as
> default source of randomness.

After reviewing the above issue, I agree this should be resolved, and
have (hopefully) done so in this message.

This should let the package trickle back down into testing from here on.

A.


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

Bug#873086: marked as done (ifupdown script disables IPv6 on parent of VLAN interface)

[Debian Bug Tracking System]

Your message dated Mon, 09 Apr 2018 02:55:08 +
with message-id 
and subject line Bug#873086: fixed in bridge-utils 1.5-16
has caused the Debian Bug report #873086,
regarding ifupdown script disables IPv6 on parent of VLAN interface
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.)


-- 
873086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bridge-utils
Version: 1.5-14

Well, what the subject says, this just killed my IPv6 connectivity on a
machine that's untagged on the same interface on which a VLAN is supposed
to be attached to a bridge. I guess at the very least, bride-utils should
avoid touching the configuration of interfaces that are managed by
ifupdown and that aren't even supposed to be attached to a bridge?
--- End Message ---
--- Begin Message ---
Source: bridge-utils
Source-Version: 1.5-16

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

Debian distribution maintenance software
pp.
Santiago Garcia Mantinan  (supplier of updated bridge-utils 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 08 Apr 2018 23:06:30 +0200
Source: bridge-utils
Binary: bridge-utils
Architecture: source amd64
Version: 1.5-16
Distribution: unstable
Urgency: medium
Maintainer: Santiago Garcia Mantinan 
Changed-By: Santiago Garcia Mantinan 
Description:
 bridge-utils - Utilities for configuring the Linux Ethernet bridge
Closes: 873086
Changes:
 bridge-utils (1.5-16) unstable; urgency=medium
 .
   * Don't set dev globally at bridge-utils.sh. Closes: #873086.
Checksums-Sha1:
 0299724f5ba93d55de72e4036c393aefff2d42e6 1718 bridge-utils_1.5-16.dsc
 a68b85285800d2fdf96e8634d944c0fbaffb0a90 17039 bridge-utils_1.5-16.diff.gz
 63e1e6a74c61ddb633433c77f3b7754f8fa0ea62 36012 
bridge-utils-dbgsym_1.5-16_amd64.deb
 9e8ae1344a103fe1b1b3063f1a3f9e7421105c9b 5981 
bridge-utils_1.5-16_amd64.buildinfo
 0d78b32a97af44549bc862fcf8d124e5ee579c9a 34236 bridge-utils_1.5-16_amd64.deb
Checksums-Sha256:
 48b481b3deb4e71dbbc62aa4ccd8f426512b88f39ca6bfa12b2a42f1c66e16cd 1718 
bridge-utils_1.5-16.dsc
 e841aae4c7feccc4fb719a0a93397c3182dba5e9d20b4a2eae7c3b80dbd0cdf5 17039 
bridge-utils_1.5-16.diff.gz
 336d8a6ff2a285582d111c87b28cdeb96c34325187409e7dd6ea34956acc7ac2 36012 
bridge-utils-dbgsym_1.5-16_amd64.deb
 fcef9e28c352d4ee040e587cb2233a43f7f25e7462d60f8c7d509695ca41695e 5981 
bridge-utils_1.5-16_amd64.buildinfo
 a6d57a9b057e50ec7fa186f6b58562b92e8b85618d87743902446cbda57ee974 34236 
bridge-utils_1.5-16_amd64.deb
Files:
 50c163bbb4bec2a4472c8ec3076b180e 1718 net optional bridge-utils_1.5-16.dsc
 57c8c7e04a984d743d1972a02c8e869b 17039 net optional bridge-utils_1.5-16.diff.gz
 d8dd6a91ada6597cc788df64452c792a 36012 debug optional 
bridge-utils-dbgsym_1.5-16_amd64.deb
 7d0628b171f717bed8b18e49f3c82b74 5981 net optional 
bridge-utils_1.5-16_amd64.buildinfo
 7cc08bba4f4f3badc298e9ea337ba74b 34236 net optional 
bridge-utils_1.5-16_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEBqPldg9hG0uxqQ5ouGiMo9h21aMFAlrKj7MACgkQuGiMo9h2
1aNDkhAAjlIrWJoDsxJ9EqgacQHMKZV+nYu4fOWTlJgi9794QGstZYGlcrxbVDCS
OB2z3N7vY5XKgID5fa2w7zu939CxXuxSjsG0p8ELm5LShhqN57/qJ3bI3qwJ0OZm
G6kvKad9fm+mJsY5xDCbtTZ0IFuV21ZFX8dGW4fkG1KDiKPG8yOfuBIRfkh+hRCH
+vS7Pj/qIpLjJaVicod6wBiY7s0OoVwuNzLmUllPndBf5ZCP7+mewukBzBTRDPKn
b37P4/TVZbtTxYq2qhXy+j3tF2Trw2640HKNDHltcJPS/ujeIV/VAHntWajIck/Q
B5zCYkGVNGSuIjZgZwCSbtP+4mOnKxE/zAkDjYKqNVaEcl1SsORN46wgr+7D/vrB
8vFKXHYvhuH2Z9XzlCX3ZktZ8RvMlXkuvJjfe35zG8Z3w/mmAn9za6zMB9QvhgJd
m5AY6ArYh5ZRTNPmJuJEWi0iur/1FpOAxJYAWKmIKVtt8JEMT7OEmRtg51FVqLoX
XazllrMmUdb7tYRFjoLEYKeUqZtmSo77MdT75pzU6c2Z2noGEB+rHUdrgYJLA9Oq
UqjpVLZB9c+BgEmq8RfF4i2ZYNGPfSo6iISm/XP8Ai+f3BV0IGx2pALl1wC3lKGf
CKktqiZFWzUVRiqNcFqidZQKSiy5lnUw3V7LO9/o2r6OfAfEmnU=
=0Cad
-END PGP SIGNATURE End Message ---

Bug#893515: digikam: FTBFS with kdepim 17.12.2

[Steve Robbins]

On Sunday, April 8, 2018 1:25:42 PM CDT Simon Frei wrote:
> I totally understand that, I am just trying to get infos to you as
> debian maintainer from my (at the moment admittedly almost non-existing)
> involvement upstream. Exiv2 0.26 will likely not get into testing.
> Upstream does backport a lot of security fixes to 0.26, but negated
> creating a dot release on request, and is focussing on 0.27. It was
> planned to release an rc in early 2018, but from what I read in the
> issue tracker, that's not going to happen asap.

Yes, fair enough.   I'm not entirely opposed to patching digikam to accept the 
older exiv2.  That was going to be my Plan B in any case, but you make a good 
case to do it immediately and work on updating exiv2 in parallel.

-S
 


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

Bug#892458: Fwd: [Debian-astro-maintainers] ftools update

[Sam Fowler]

On Wed, 14 Mar 2018 16:22:19 +0100 Ole Streicher  wrote:
> FYI
> 
> 
>  Forwarded Message 
> Subject: [Debian-astro-maintainers] ftools update
> Date: Wed, 14 Mar 2018 10:42:25 -0400
> From: Michael Arida 
> To: debian-astro-maintain...@lists.alioth.debian.org
> 
> 
> Dear Debian Astro Maintainers,
> 
> As you may have noticed CFITSIO was updated Friday (March 2) for a
> major bug fix.  Since you have a software bundle that uses what we
> assume is CFITSIO somewhere under the hood, we wanted to let you know
> that you should update that code.  We are also expecting another
> update in April.
> 
> If you have any questions or concerns, feel free to contact me.
> 
> Regards,
>  Mike Arida
> 
> Michael Arida (ADNET) ASD/HEASARC
> 301.286.2291/1215 (voice/fax)  Code 660, NASA/GSFC
> michael.ar...@nasa.gov Greenbelt, MD 20771
> 
> ___
> Debian-astro-maintainers mailing list
> debian-astro-maintain...@lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/debian-astro-maintainers

This has been assigned has been assigned CVE-2018-1000166.

Regards,
-- 
Sam Fowler, Red Hat Product Security

Bug#894917: procps: pgrep -u UID segfaults

[Craig Small]

The bug is actually worse than this. Any time pgrep is run without a
process name and it matches nothing it segfaults.

The fix is a one liner already applied upstream.

 - Craig

-- 
Craig Small https://dropbear.xyz/ csmall at : dropbear.xyz
Debian GNU/Linuxhttps://www.debian.org/   csmall at : debian.org
Mastodon: @smalls...@social.dropbear.xyz Twitter: @smallsees
GPG fingerprint:  5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5

Bug#892950: marked as done (apcupsd FTBFS: python-imaging removed from pillow/5.0.0-1)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 21:20:22 +
with message-id 
and subject line Bug#892950: fixed in apcupsd 3.14.14-2
has caused the Debian Bug report #892950,
regarding apcupsd FTBFS: python-imaging removed from pillow/5.0.0-1
to be marked as done.

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

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


-- 
892950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apcupsd
Version: 3.14.14-1
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

apcupsd fails to build from source in unstable. Its Build-Depends are no
longer satisfiable, because python-imaging was removed from
pillow/5.0.0-1.

Helmut
--- End Message ---
--- Begin Message ---
Source: apcupsd
Source-Version: 3.14.14-2

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated apcupsd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 25 Mar 2018 19:14:07 +0100
Source: apcupsd
Binary: apcupsd apcupsd-cgi apcupsd-doc
Architecture: source amd64 all
Version: 3.14.14-2
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 apcupsd- APC UPS Power Management (daemon)
 apcupsd-cgi - APC UPS Power Management (web interface)
 apcupsd-doc - APC UPS Power Management (documentation/examples)
Closes: 541660 572727 576703 878209 885820 889670 892950
Changes:
 apcupsd (3.14.14-2) unstable; urgency=medium
 .
   * debian/control: bump standard to 4.1.4 (no changes)
   * debian/control: use dh11 (mostly)
   * debian/control: add salsa VCS URLs
   * debian/control: remove dependency for dh-systemd
   * debian/control: use prio optional
   * debian/control: remove dependency for python-imaging (Closes: #892950)
 (dependency does not seem to be needed anymore)
   * debian/local/*: replace /etc/apcupsd/powerfail by file created
 with PWRFAILDIR from config
 (Closes: #541660, #572727, #576703)
   * debian/copyright: use https in URL
   * debian/control: drop dependency on libgconf2-dev (Closes: #885820)
   * debian/control: drop dependency on libgtk2.0-dev again
   * debian/rules: do not build with --enable-gapcmon
   Unfortunately gconf2 shall be removed from Debian.
   Upstream needs to move from gconf to gsettings.
   As long as this did not happen, we can not build
   the frontend any longer. (Closes: #889670, #878209)
Checksums-Sha1:
 82d5109360483c7c75e6172f63a5efe2849f8919 2270 apcupsd_3.14.14-2.dsc
 ba3afa49d9f14c584b5a14417dbf60a500c1462a 1816338 apcupsd_3.14.14.orig.tar.gz
 424b09f9db3395bee576b7007eb44777dd4203e3 20480 apcupsd_3.14.14-2.debian.tar.xz
 98c828eed3c918df0fd8ceed0e7c7272f9ae4ee8 243928 
apcupsd-cgi-dbgsym_3.14.14-2_amd64.deb
 b361662acaf3d7b4d2758791d7951cdd9af01d8f 94260 apcupsd-cgi_3.14.14-2_amd64.deb
 d792e4ad19465e591a5cf5c5db187489c7d16593 964504 
apcupsd-dbgsym_3.14.14-2_amd64.deb
 39e4f542b5634fec9850fd9237a07e1b7e2ab642 650876 apcupsd-doc_3.14.14-2_all.deb
 7b2ed3cd75282a28cc7533f326d5fab7be0059a0 9667 apcupsd_3.14.14-2_amd64.buildinfo
 3763c0fe27c6e8b6f557eb06a6af324c7e351afd 264372 apcupsd_3.14.14-2_amd64.deb
Checksums-Sha256:
 ab9895e1291d9e270969c3c48dc106dccb1f4c057b2229b6c992be5b33316993 2270 
apcupsd_3.14.14-2.dsc
 37a266d5dc3240227ff2f8d02fdf608a48d82f90665931ea315558b96f23b1ec 1816338 
apcupsd_3.14.14.orig.tar.gz
 ca44d511103ac8c0c26f5a10e54547474fe24a7112fc76166f05c2e395a9d67e 20480 
apcupsd_3.14.14-2.debian.tar.xz
 acf4f141c2a92ee9b37097c9c667cc55044ee82429afc82aae49c0cfc24a76c6 243928 
apcupsd-cgi-dbgsym_3.14.14-2_amd64.deb
 2729f1db121568fa88565b874ee1e0e589552fe1c1a3d2fdc0c08eecce7d08be 94260 
apcupsd-cgi_3.14.14-2_amd64.deb
 462819bc2101a001e9f2a2d22282cbe49caab60382817377703253ff1b5325da 964504 

Bug#885820: marked as done (apcupsd: Depends on gconf)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 21:20:21 +
with message-id 
and subject line Bug#885820: fixed in apcupsd 3.14.14-2
has caused the Debian Bug report #885820,
regarding apcupsd: Depends on gconf
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.)


-- 
885820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apcupsd
Version: 3.14.14-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf
Tags: sid buster

Your package depends or build-depends on gconf, but gconf will be
removed from Debian soon.

gconf's last release was about 5 years ago. It has been replaced by
gsettings (provided in Debian by source glib2.0 )

References
--
https://developer.gnome.org/gio/stable/ch34.html
https://developer.gnome.org/gio/stable/GSettings.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: apcupsd
Source-Version: 3.14.14-2

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated apcupsd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 25 Mar 2018 19:14:07 +0100
Source: apcupsd
Binary: apcupsd apcupsd-cgi apcupsd-doc
Architecture: source amd64 all
Version: 3.14.14-2
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 apcupsd- APC UPS Power Management (daemon)
 apcupsd-cgi - APC UPS Power Management (web interface)
 apcupsd-doc - APC UPS Power Management (documentation/examples)
Closes: 541660 572727 576703 878209 885820 889670 892950
Changes:
 apcupsd (3.14.14-2) unstable; urgency=medium
 .
   * debian/control: bump standard to 4.1.4 (no changes)
   * debian/control: use dh11 (mostly)
   * debian/control: add salsa VCS URLs
   * debian/control: remove dependency for dh-systemd
   * debian/control: use prio optional
   * debian/control: remove dependency for python-imaging (Closes: #892950)
 (dependency does not seem to be needed anymore)
   * debian/local/*: replace /etc/apcupsd/powerfail by file created
 with PWRFAILDIR from config
 (Closes: #541660, #572727, #576703)
   * debian/copyright: use https in URL
   * debian/control: drop dependency on libgconf2-dev (Closes: #885820)
   * debian/control: drop dependency on libgtk2.0-dev again
   * debian/rules: do not build with --enable-gapcmon
   Unfortunately gconf2 shall be removed from Debian.
   Upstream needs to move from gconf to gsettings.
   As long as this did not happen, we can not build
   the frontend any longer. (Closes: #889670, #878209)
Checksums-Sha1:
 82d5109360483c7c75e6172f63a5efe2849f8919 2270 apcupsd_3.14.14-2.dsc
 ba3afa49d9f14c584b5a14417dbf60a500c1462a 1816338 apcupsd_3.14.14.orig.tar.gz
 424b09f9db3395bee576b7007eb44777dd4203e3 20480 apcupsd_3.14.14-2.debian.tar.xz
 98c828eed3c918df0fd8ceed0e7c7272f9ae4ee8 243928 
apcupsd-cgi-dbgsym_3.14.14-2_amd64.deb
 b361662acaf3d7b4d2758791d7951cdd9af01d8f 94260 apcupsd-cgi_3.14.14-2_amd64.deb
 d792e4ad19465e591a5cf5c5db187489c7d16593 964504 
apcupsd-dbgsym_3.14.14-2_amd64.deb
 39e4f542b5634fec9850fd9237a07e1b7e2ab642 650876 apcupsd-doc_3.14.14-2_all.deb
 7b2ed3cd75282a28cc7533f326d5fab7be0059a0 9667 apcupsd_3.14.14-2_amd64.buildinfo
 3763c0fe27c6e8b6f557eb06a6af324c7e351afd 264372 apcupsd_3.14.14-2_amd64.deb
Checksums-Sha256:
 ab9895e1291d9e270969c3c48dc106dccb1f4c057b2229b6c992be5b33316993 2270 
apcupsd_3.14.14-2.dsc
 37a266d5dc3240227ff2f8d02fdf608a48d82f90665931ea315558b96f23b1ec 1816338 
apcupsd_3.14.14.orig.tar.gz
 ca44d511103ac8c0c26f5a10e54547474fe24a7112fc76166f05c2e395a9d67e 20480 
apcupsd_3.14.14-2.debian.tar.xz
 acf4f141c2a92ee9b37097c9c667cc55044ee82429afc82aae49c0cfc24a76c6 

Bug#894770: [becker...@gmail.com: Bug#894769: Java error message and permission on serial port]

[Geert Stappers]

now in this bugreport

- Forwarded message from becker...@gmail.com -

Date: Sun, 08 Apr 2018 19:12:56 +0200
From: becker...@gmail.com
To: 894...@bugs.debian.org
Subject: Bug#894769: Java error message and permission on serial port

Hi,

I have the same issue, this is what I've found so far:

- after plugging in the Arduino and starting the IDE, the status line reports 
the correct 
settings (board type and serial device selected in a previous session)

- just klicking on the 'Tools' menu throws the error message:
java.lang.NullPointerException thrown while loading gnu.io.RXTXCommDriver

- the user running the Arduino IDE is in the dialout group, I tried if chmod 
666 on the serial 
device would help but it didn't

- tried to send a sketch to the Arduino, this produced the following two lines  
repeatedly:

java.lang.NullPointerException thrown while loading gnu.io.RXTXCommDriver
PORTS {} / {} => {}

then followed by:

processing.app.debug.RunnerException: Couldn???t find a Leonardo on the 
selected port. 
Check that you have the correct port selected.  If it is correct, try pressing 
the board's reset 
button after initiating the upload.
at 
processing.app.debug.AvrdudeUploader.uploadViaBootloader(AvrdudeUploader.java:154)
at 
processing.app.debug.AvrdudeUploader.uploadUsingPreferences(AvrdudeUploader.java:67)
at processing.app.Sketch.upload(Sketch.java:1671)
at processing.app.Sketch.exportApplet(Sketch.java:1627)
at processing.app.Sketch.exportApplet(Sketch.java:1599)
at processing.app.Editor$DefaultExportHandler.run(Editor.java:2380)
at java.base/java.lang.Thread.run(Thread.java:844)


-- System Information: 


- End forwarded message -


Groeten
Geert Stappers
-- 
Leven en laten leven

Bug#894769: marked as done (arduino: serial communication/uploader not working)

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 22:27:13 +0200
with message-id <20180408202713.gb30...@gpm.stappers.nl>
and subject line closing the oldest of the duplicates
has caused the Debian Bug report #894769,
regarding arduino: serial communication/uploader not working
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.)


-- 
894769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894769
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: arduino
Version: 2:1.0.5+dfsg2-4.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

normal use of arduino program
however at the moment the serial connection selection is greyed out

connect to arduino via serial port not working, cannot upload code to arduino

get the following error
java.lang.NullPointerException thrown while loading gnu.io.RXTXCommDriver

this is the same on two different machines running buster
where serial upload was previously working without a problem

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

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

Versions of packages arduino depends on:
ii  arduino-core   2:1.0.5+dfsg2-4.1
ii  default-jre [java6-runtime]2:1.9-62
ii  libjna-java4.5.1-1
ii  librxtx-java   2.2pre2+dfsg1-1
ii  openjdk-8-jre [java6-runtime]  8u162-b12-1
ii  openjdk-9-jre [java6-runtime]  9.0.4+12-3

Versions of packages arduino recommends:
ii  extra-xdg-menus  1.0-4
ii  policykit-1  0.105-20

arduino suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, Apr 08, 2018 at 08:18:03PM +, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> 
> > unmerge 894769
> Bug #894769 [arduino] arduino: serial communication/uploader not working
> Bug #894770 [arduino] arduino: serial communication/uploader not working
> Disconnected #894769 from all other report(s).
> > stop
> Stopping processing here.
> 
> 894769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894769

Closing that one


> 894770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894770

Using that one for further discussion.



Groeten
Geert Stappers
-- 
Leven en laten leven--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> unmerge 894769
Bug #894769 [arduino] arduino: serial communication/uploader not working
Bug #894770 [arduino] arduino: serial communication/uploader not working
Disconnected #894769 from all other report(s).
> stop
Stopping processing here.

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

Processed: affects 891557

[Debian Bug Tracking System]

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

> affects 891557 src:gocryptfs
Bug #891557 {Done: Felix Lechner } 
[golang-github-jacobsa-crypto-dev] gocryptfs FTBFS: 
src/github.com/jacobsa/crypto/cmac/hash.go:97:3: undefined: xorBlock
Added indication that 891557 affects src:gocryptfs
> thanks
Stopping processing here.

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

Bug#892641: marked as done (python-xarray: FTBFS and Debci failure with pandas 0.22.0)

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 22:48:57 +0300
with message-id <20180408194857.GI9516@localhost>
and subject line Seems to be fixed in 0.10.2-1
has caused the Debian Bug report #892641,
regarding python-xarray: FTBFS and Debci failure with pandas 0.22.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.)


-- 
892641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892641
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-xarray
Version: 0.9.6-1
Severity: serious

https://ci.debian.net/packages/p/python-xarray/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-xarray.html

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: cd 
/build/1st/python-xarray-0.9.6/.pybuild/pythonX.Y_3.6/build; python3.6 -m 
pytest 
= test session starts ==
platform linux -- Python 3.6.4+, pytest-3.3.2, py-1.5.2, pluggy-0.6.0
rootdir: /build/1st/python-xarray-0.9.6, inifile: setup.cfg
collected 2460 items / 1 skipped

xarray/tests/test_accessors.py s...  [  0%]
xarray/tests/test_backends.py .ss.ss [  1%]
s.ss [  4%]
sss. [  7%]
.ss..... [ 10%]
s.s...s. [ 13%]
 [ 16%]
ss.s..ss.ss.s..ss.ss [ 19%]
 [ 22%]
 [ 25%]
s.s..[ 27%]
xarray/tests/test_combine.py s   [ 28%]
xarray/tests/test_computation.py ..s [ 29%]
xarray/tests/test_conventions.py .ss [ 30%]
ss.s.sss [ 31%]
xarray/tests/test_dask.py ss [ 33%]
xarray/tests/test_dataarray.py .s... [ 35%]
sFF. [ 38%]
...s...F [ 41%]
..s. [ 43%]
 [ 46%]
 [ 49%]
 [ 52%]
...  [ 53%]
xarray/tests/test_dataset.py ..s.s.. [ 54%]
F... [ 57%]
.F.F.s..s..s [ 60%]
...s..s..s.s [ 63%]
 [ 66%]
 [ 69%]
 [ 72%]
 [ 75%]
 [ 78%]
 [ 81%]
 [ 82%]
xarray/tests/test_duck_array_ops.py .[ 83%]
xarray/tests/test_extensions.py  [ 83%]
xarray/tests/test_formatting.py  [ 84%]
xarray/tests/test_groupby.py .   [ 84%]
xarray/tests/test_indexing.py .F..   [ 84%]
xarray/tests/test_merge.py . [ 85%]
xarray/tests/test_options.py ..  [ 85%]
xarray/tests/test_plot.py .. [ 87%]
 [ 90%]

Processed: Move to the package where it was fixed

[Debian Bug Tracking System]

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

> reassign 891557 golang-github-jacobsa-crypto-dev 
> 0.0~git2016.0.293ce0c+dfsg1-8
Bug #891557 {Done: Felix Lechner } [src:gocryptfs] 
gocryptfs FTBFS: src/github.com/jacobsa/crypto/cmac/hash.go:97:3: undefined: 
xorBlock
Bug reassigned from package 'src:gocryptfs' to 
'golang-github-jacobsa-crypto-dev'.
No longer marked as found in versions gocryptfs/1.4.3-5.
No longer marked as fixed in versions 
golang-github-jacobsa-crypto/0.0~git20171018.0.c73681c+dfsg1-2.
Bug #891557 {Done: Felix Lechner } 
[golang-github-jacobsa-crypto-dev] gocryptfs FTBFS: 
src/github.com/jacobsa/crypto/cmac/hash.go:97:3: undefined: xorBlock
Marked as found in versions 
golang-github-jacobsa-crypto/0.0~git2016.0.293ce0c+dfsg1-8.
> fixed 891557 0.0~git20171018.0.c73681c+dfsg1-2
Bug #891557 {Done: Felix Lechner } 
[golang-github-jacobsa-crypto-dev] gocryptfs FTBFS: 
src/github.com/jacobsa/crypto/cmac/hash.go:97:3: undefined: xorBlock
Marked as fixed in versions 
golang-github-jacobsa-crypto/0.0~git20171018.0.c73681c+dfsg1-2.
> thanks
Stopping processing here.

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

Bug#893238: marked as done (libgoogle-gson-java FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 19:34:22 +
with message-id 
and subject line Bug#893238: fixed in libgoogle-gson-java 2.8.2-1
has caused the Debian Bug report #893238,
regarding libgoogle-gson-java FTBFS with openjdk-9
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.)


-- 
893238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgoogle-gson-java
Version: 2.4-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libgoogle-gson-java.html

...
[ERROR] Failures: 
[ERROR]   
DefaultDateTypeAdapterTest.testFormatUsesDefaultTimezone:119->assertFormatted:155
 expected: but was:
[ERROR]   
DefaultDateTypeAdapterTest.testFormattingInEnUs:34->assertFormattingAlwaysEmitsUsLocale:47->assertFormatted:155
 expected: but was:
[ERROR]   
DefaultDateTypeAdapterTest.testFormattingInFr:38->assertFormattingAlwaysEmitsUsLocale:47->assertFormatted:155
 expected: but was:
[ERROR]   DefaultTypeAdaptersTest.testDefaultDateSerialization:332 
expected:<"Sep 11, 2011[] 10:55:03 PM"> but was:<"Sep 11, 2011[,] 10:55:03 PM">
[ERROR]   DefaultTypeAdaptersTest.testDefaultDateSerializationUsingBuilder:399 
expected:<"Sep 11, 2011[] 10:55:03 PM"> but was:<"Sep 11, 2011[,] 10:55:03 PM">
[ERROR]   DefaultTypeAdaptersTest.testDefaultJavaSqlTimestampSerialization:373 
expected:<"Dec 3, 2009[] 1:18:02 PM"> but was:<"Dec 3, 2009[,] 1:18:02 PM">
[ERROR]   ObjectTest.testDateAsMapObjectField:485 expected:<..."date":"Dec 31, 
1969[] 4:00:00 PM"}}> but was:<..."date":"Dec 31, 1969[,] 4:00:00 PM"}}>
[ERROR] Errors: 
[ERROR]   
DefaultDateTypeAdapterTest.testParsingDatesFormattedWithSystemLocale:71->assertParsed:159
 ? JsonSyntax
[ERROR]   
DefaultDateTypeAdapterTest.testParsingDatesFormattedWithUsLocale:95->assertParsed:159
 ? JsonSyntax
[ERROR]   DefaultTypeAdaptersTest.testDefaultDateDeserialization:337 ? 
JsonSyntax Dec 13...
[ERROR]   
DefaultTypeAdaptersTest.testDefaultJavaSqlTimestampDeserialization:378 ? 
JsonSyntax
[INFO] 
[ERROR] Tests run: 966, Failures: 7, Errors: 4, Skipped: 0
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 13.058 s
[INFO] Finished at: 2018-03-17T01:41:55-12:00
[INFO] Final Memory: 17M/56M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
project gson: There are test failures.
[ERROR] 
[ERROR] Please refer to 
/build/1st/libgoogle-gson-java-2.4/gson/target/surefire-reports for the 
individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
[date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/libgoogle-gson-java-2.4 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/libgoogle-gson-java-2.4/debian 
-Dmaven.repo.local=/build/1st/libgoogle-gson-java-2.4/debian/maven-repo 
--batch-mode --file gson/pom.xml returned exit code 1
make[1]: *** [debian/rules:11: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: libgoogle-gson-java
Source-Version: 2.8.2-1

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

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

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated libgoogle-gson-java 
package)

(This message was generated 

Processed: libart-lgpl: Intent to Adopt

[Debian Bug Tracking System]

Processing control commands:

> block 895247 by -1
Bug #895247 [src:libgnomecanvas] libgnomecanvas: Intent to Adopt
895247 was not blocked by any bugs.
895247 was not blocking any bugs.
Added blocking bug(s) of 895247: 895249

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

Bug#895249: libart-lgpl: Intent to Adopt

[Adrian Bunk]

Source: libart-lgpl
Version: 2.3.21-3
Severity: serious
Control: block 895247 by -1

I hereby declare my intent to adopt pygtk.

libart-lgpl is a dependency of libgnomecanvas.

This is about keeping software that is long dead upstream but
has reverse dependencies longer on life support.

The goal is that the package works in buster not worse than
it did in stretch, it is clear that spending much effort on
maintainance upstream or in Debian would be a waste of time.

Bug#894091: marked as done (bind-dyndb-ldap FTBFS with bind9 9.11.3)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 19:19:09 +
with message-id 
and subject line Bug#894091: fixed in bind-dyndb-ldap 11.1-2
has caused the Debian Bug report #894091,
regarding bind-dyndb-ldap FTBFS with bind9 9.11.3
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.)


-- 
894091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bind-dyndb-ldap
Version: 11.1-1
Severity: serious

https://buildd.debian.org/status/package.php?p=bind-dyndb-ldap=sid

...
../../src/bindcfg.c: In function 'get_type_from_tuplefield':
../../src/bindcfg.c:27:2: error: implicit declaration of function 'REQUIRE'; 
did you mean 'ISC_REQUIRE'? [-Werror=implicit-function-declaration]
  REQUIRE(cfg_type != NULL && cfg_type->of != NULL);
  ^~~
--- End Message ---
--- Begin Message ---
Source: bind-dyndb-ldap
Source-Version: 11.1-2

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated bind-dyndb-ldap 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 08 Apr 2018 21:59:56 +0300
Source: bind-dyndb-ldap
Binary: bind9-dyndb-ldap
Architecture: source
Version: 11.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Description:
 bind9-dyndb-ldap - LDAP back-end plug-in for BIND
Closes: 894091
Changes:
 bind-dyndb-ldap (11.1-2) unstable; urgency=medium
 .
   * Fix build with bind 9.11.3. (Closes: #894091)
Checksums-Sha1:
 5c6b2f699af641018e8bbf127aed04baa466e40c 2082 bind-dyndb-ldap_11.1-2.dsc
 6f39f8ece22c7859d5005c8aac03d47ca63d4b5d 5420 
bind-dyndb-ldap_11.1-2.debian.tar.xz
 a4f290aac23c951e2c6d06286c91da0868d0b1c3 5942 
bind-dyndb-ldap_11.1-2_source.buildinfo
Checksums-Sha256:
 84747360a62c663d4c35e0a54f8787e9cb2b8ede9af53e5bae112718923fdf0b 2082 
bind-dyndb-ldap_11.1-2.dsc
 0542a652a4786be0c771d692d5f5fb5be24da8a480ed774040a05f9b0e3c05ef 5420 
bind-dyndb-ldap_11.1-2.debian.tar.xz
 23d7e88ebd6eca661784a70044ff4fc720f48546831428af6edbef1cb61b7536 5942 
bind-dyndb-ldap_11.1-2_source.buildinfo
Files:
 f6753aabbf0d2d5769205980762e0309 2082 net optional bind-dyndb-ldap_11.1-2.dsc
 00d49609933b16d3d312999af2466a1c 5420 net optional 
bind-dyndb-ldap_11.1-2.debian.tar.xz
 a346d06b6763ef09afe35d89233291dd 5942 net optional 
bind-dyndb-ldap_11.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAlrKZroACgkQy3AxZaiJ
hNwdcRAAms5yK25lKW5JtTWckUBaZHSIpzPH7RYX7nDty0+LFsvtWIb53rjEpd8d
+R15NlmAeEafIqaxKBlN0/sv1evroBQIriQ2pP6WMQ4uD2wTxxMQgOD2lLJNRMbw
+64gYlaJwrn3ZJzssKs6K5EupLFJb5Z+tdvEq7bn7A2OJd4US2e6LtPmsXGwbrzK
o7qzoGcUYa9pgNd7MzuF0A4ZsNc17eR8yByCjPeukFOCQCqxZoEzpXHQ/jqP2x0/
oQb/FN4zMW6ZpYEb76kMua5KPV3GqbziQzlTQdX4ZP+2GJoZaLGBWgvihPoOnmvI
IzxHgpO2+m3yipXQWgwrku6DGPAgLOn60W6bOtB5jzErQTkLP1/zDMxLEFU79rf0
7DNHhtcDyw5yI1d6qY9Tly3vqJEo+l4WWymGd77VEORdD5v2YKoDPt1XqvI2hJrX
byx8f/hYNnbBaVCuvhQE65CowUXnDocEgmTNn0SGDqrQd4Dt08fgQgzNn7D0Ckr+
1alKUjAh2MNkx1XhJ0ZOS8Fq56ECOPFT/Qt24MhzAf4cYVplPHBFknMZMDUWsVmA
qO3HWzhI9MAkaBAEPE6ahd+99MYZFnCNY0MiGjbfpP0ahhgytvfggO7UX4+beknc
NWlXLCNmhCaFeoYTmOtNUgiqPs9OKLc+1U7t011qNkWRQLIsvhg=
=lSb8
-END PGP SIGNATURE End Message ---

Bug#895247: libgnomecanvas: Intent to Adopt

[Adrian Bunk]

Source: libgnomecanvas
Version: 2.30.3-3
Severity: serious
Tags: buster sid

17:37 < jbicha> how about this for a next step: someone who wants to maintain 
libgnomecanvas can file a severity: serious bug against Debian's 
libgnomecanvas with the title Intent to Adopt
17:37 < jbicha> we can discuss things more on that bug

I hereby declare my intent to adopt libgnomecanvas,
mostly triggered by #893770 (amide).

This is about keeping software that is long dead upstream but
has reverse dependencies longer on life support.

The goal is that the package works in buster not worse than
it did in stretch, it is clear that spending much effort on
maintainance upstream or in Debian would be a waste of time.

Bug#895248: pygtk: Intent to Adopt

[Adrian Bunk]

Source: pygtk
Version: 2.24.0-5.1
Severity: serious
Tags: buster sid

I hereby declare my intent to adopt pygtk.

pygtk still has many (including popular) reverse dependencies.
Python 2 will be removed in bullseye, and there is no clear
reason why pygtk has to be removed one release earlier.

This is about keeping software that is long dead upstream but
has reverse dependencies longer on life support.

The goal is that the package works in buster not worse than
it did in stretch, it is clear that spending much effort on
maintainance upstream or in Debian would be a waste of time.

Bug#895246: gconf: Intent to Adopt

[Adrian Bunk]

Source: gconf
Version: 3.2.6-4.1
Severity: serious

I hereby declare my intent to adopt gconf.

It is not a good service to our users to rip gconf support
out of many packages for buster.

This is about keeping software that is long dead upstream but
has reverse dependencies longer on life support.

The goal is that the package works in buster not worse than
it did in stretch, it is clear that spending much effort on
maintainance upstream or in Debian would be a waste of time.

Processed: libxml2: CVE-2017-18258: Set memory limit for LZMA decompression

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2.9.7+dfsg-1
Bug #895245 [src:libxml2] libxml2: CVE-2017-18258: Set memory limit for LZMA 
decompression
Marked as fixed in versions libxml2/2.9.7+dfsg-1.
> block -1 by 895195
Bug #895245 [src:libxml2] libxml2: CVE-2017-18258: Set memory limit for LZMA 
decompression
895245 was not blocked by any bugs.
895245 was not blocking any bugs.
Added blocking bug(s) of 895245: 895195

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

Bug#887666: jh_linkjars: Invalid option: N

[Niels Thykier]

Emmanuel Bourg:
> Le 08/04/2018 à 12:57, Niels Thykier a écrit :
> 
>> I had a go and it failed (presumably because I do not have write access)
> 
> You have to join back the team then ;)
> 

Ok, requested access. :)

Let me know once it has been progressed.

Thanks,
~Niels

Processed: Re: Bug#895195: libxml2: CVE-2018-9251

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #895195 [src:libxml2] libxml2: CVE-2018-9251
Severity set to 'serious' from 'important'

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

Processed: Re: Bug#895154: ffmpeg: FTBFS - make[2]: write error: stdout

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #895154 [src:ffmpeg] ffmpeg: FTBFS - make[2]: write error: stdout
Added tag(s) pending.

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

Bug#895154: ffmpeg: FTBFS - make[2]: write error: stdout

[James Cowgill]

Control: tags -1 pending

Hi,

On 08/04/18 11:18, Niels Thykier wrote:
> On Sat, 7 Apr 2018 21:38:53 +0100 James Cowgill  wrote:
>> Source: ffmpeg
>> Version: 7:3.4.1-1
>> Severity: serious
>> Tags: sid buster
>>
>> For some reason ffmpeg has started FTBFS with this error:
>>> TESTvsynth2-zlib
>>> /<>/tests/fate-run.sh fate-vsynth2-zlib "" "" 
>>> "/<>/debian/standard" 'enc_dec "rawvideo -s 352x288 -pix_fmt 
>>> yuv420p " tests/data/vsynth2.yuv avi "-c zlib " rawvideo "-s 352x288 
>>> -pix_fmt yuv420p -vsync 0 " -keep ""' '' 
>>> '/<>/tests/ref/vsynth/vsynth2-zlib' '' '1' '' '' '' '' '' '1' 
>>> '' '' ''
>>>  /<>/debian/standard/ffmpeg -nostdin -nostats -cpuflags all -f 
>>> rawvideo -s 352x288 -pix_fmt yuv420p -threads 1 -idct simple -flags 
>>> +bitexact -sws_flags +accurate_rnd+bitexact -fflags +bitexact -hwaccel none 
>>> -threads 1 -thread_type frame+slice -i 
>>> /<>/debian/standard/tests/data/vsynth2.yuv -threads 1 -idct 
>>> simple -dct fastint -c zlib -flags +bitexact -sws_flags 
>>> +accurate_rnd+bitexact -fflags +bitexact -f avi -y 
>>> /<>/debian/standard/tests/data/fate/vsynth2-zlib.avi
>>>  /<>/debian/standard/ffmpeg -nostdin -nostats -cpuflags all 
>>> -threads 1 -idct simple -flags +bitexact -sws_flags +accurate_rnd+bitexact 
>>> -fflags +bitexact -hwaccel none -threads 1 -thread_type frame+slice -i 
>>> /<>/debian/standard/tests/data/fate/vsynth2-zlib.avi -threads 
>>> 1 -idct simple -dct fastint -s 352x288 -pix_fmt yuv420p -vsync 0 -flags 
>>> +bitexact -sws_flags +accurate_rnd+bitexact -fflags +bitexact -f rawvideo 
>>> -y 
>>> /<>/debian/standard/tests/data/fate/vsynth2-zlib.out.rawvideo
>>> make[2]: Leaving directory '/<>/debian/standard'
>>> make[2]: write error: stdout
>>> dh_auto_test: cd debian/standard && make -j4 -O check -k returned exit code 
>>> 1
>>> make[1]: *** [debian/rules:231: override_dh_auto_test-arch] Error 25
>>> make[1]: Leaving directory '/<>'
>>> make: *** [debian/rules:192: binary] Error 2
>>> dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
>>> status 2
>>
>> This can be seen on the reproducible builds first seen 2018-03-15
>> affecting 3.4 and 3.5 in experimental.
>>
>> I'm guessing this has something to do with "make -O" which was enabled
>> recently in debhelper, but I haven't checked.
>>
>> James
> 
> Hi James,
> 
> In a recent upload, debhelper started using -Oline instead of -O.  Does
> that solve this problem for you?  (It was done unrelated to this bug,
> but looking at the documentation for -O, I suspect it might help here as
> well)

As me and Adrian said on IRC, it does not. The problem was nodejs
leaving stderr in non-blocking mode and I've committed this to fix it.
So no bugs in debhelper here.

https://salsa.debian.org/multimedia-team/ffmpeg/commit/71b483f31e5a411a02717278e0a30323965c2c88

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#893515: digikam: FTBFS with kdepim 17.12.2

[Simon Frei]

I totally understand that, I am just trying to get infos to you as
debian maintainer from my (at the moment admittedly almost non-existing)
involvement upstream. Exiv2 0.26 will likely not get into testing.
Upstream does backport a lot of security fixes to 0.26, but negated
creating a dot release on request, and is focussing on 0.27. It was
planned to release an rc in early 2018, but from what I read in the
issue tracker, that's not going to happen asap.



signature.asc
Description: OpenPGP digital signature

Bug#895103: why3 server broken on multiple architectures

[Ralf Treinen]

Hi Steve,

On Fri, Apr 06, 2018 at 09:00:44PM -0700, Steve Langasek wrote:

> The attached patch fixes the trivial portability issue in why3, and as seen
> at http://autopkgtest.ubuntu.com/packages/w/why3 the tests are now passing
> for 0.88.3 on all architectures where they previously passed.

Thanks a lot for the patch. Applied and forwarded to upstream -Ralf.

Bug#895103: marked as done (why3 server broken on multiple architectures)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 18:23:27 +
with message-id 
and subject line Bug#895103: fixed in why3 0.88.3-2
has caused the Debian Bug report #895103,
regarding why3 server broken on multiple architectures
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.)


-- 
895103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: why3
Version: 0.88.3-1
Severity: grave
Tags: patch
Justification: renders package unusable
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch autopkgtest

Dear Ralf,

The 0.88.3 version of why3 has been blocked for a while from being included
in the upcoming Ubuntu 18.04 release due to failing autopkgtests on multiple
architectures, e.g.:

autopkgtest [08:58:21]: test why3+alt-ergo: [---
client_connect: connection failed: Connection refused (connect,) 
(socket_name=/tmp/why3server3f8c61sock)
autopkgtest [08:58:57]: test why3+alt-ergo: ---]
why3+alt-ergoFAIL non-zero exit status 1

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/w/why3/20180405_094212_aa650@/log.gz

I finally had a chance to track this down, and it turns out why3 0.88.3 is
completely broken upstream on various architectures (arm64, armhf, ppc64el,
and s390x, at least) due to wrong handling of return values from
getopt_long() that prevents why3-server from ever starting.

This issue was not seen in Debian's automated test runs because Debian only
runs autopkgtests for amd64: https://ci.debian.net/packages/w/why3/ but in
any case this would not have prevented the why3 package from being broken in
Debian testing because Debian unfortunately does not gate testing on
autopkgtest failures.

The attached patch fixes the trivial portability issue in why3, and as seen
at http://autopkgtest.ubuntu.com/packages/w/why3 the tests are now passing
for 0.88.3 on all architectures where they previously passed.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru why3-0.88.3/debian/patches/portable-getopt.patch 
why3-0.88.3/debian/patches/portable-getopt.patch
--- why3-0.88.3/debian/patches/portable-getopt.patch1969-12-31 
16:00:00.0 -0800
+++ why3-0.88.3/debian/patches/portable-getopt.patch2018-04-06 
17:22:54.0 -0700
@@ -0,0 +1,19 @@
+Description: fix unportable assumptions in getopt_long() handling
+ Don't store an int in a char and expect comparison to -1 to work across
+ architectures.
+Author: Steve Langasek 
+Last-Modified: 2018-04-06
+
+Index: why3-0.88.3/src/server/options.c
+===
+--- why3-0.88.3.orig/src/server/options.c
 why3-0.88.3/src/server/options.c
+@@ -30,7 +30,7 @@ void parse_options(int argc, char **argv
+   };
+   while (1) {
+  int option_index = 0;
+- char c = 0;
++ int c = 0;
+  c = getopt_long (argc, argv, "j:s:",
+   long_options, _index);
+  /* Detect the end of the options. */
diff -Nru why3-0.88.3/debian/patches/series why3-0.88.3/debian/patches/series
--- why3-0.88.3/debian/patches/series   2018-01-14 14:46:38.0 -0800
+++ why3-0.88.3/debian/patches/series   2018-04-06 17:20:54.0 -0700
@@ -0,0 +1 @@
+portable-getopt.patch
--- End Message ---
--- Begin Message ---
Source: why3
Source-Version: 0.88.3-2

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

Debian distribution maintenance software
pp.
Ralf Treinen  (supplier of updated why3 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 07 Apr 2018 11:54:01 

Bug#893515: digikam: FTBFS with kdepim 17.12.2

[Steve Robbins]

On Sunday, April 8, 2018 1:03:29 PM CDT Simon Frei wrote:
> Digikam still works with exiv2 0.25. It's just that a lot of fixes have
> gone into 0.26 that prevent crashs in digikam, that's why its cmake file
> has a >=0.26 dependency.

Well, the digikam build with 0.25 just stops with an error -- as you say, its 
from the cmake file.  It's possible this is just to "prevent crashes", but I 
hate to second-guess upstream.  Moreover, preventing crashes is good.  So I'd 
prefer to focus on getting exiv2 0.26 into Debian.

-Steve


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

Bug#893515: digikam: FTBFS with kdepim 17.12.2

[Simon Frei]

Digikam still works with exiv2 0.25. It's just that a lot of fixes have
gone into 0.26 that prevent crashs in digikam, that's why its cmake file
has a >=0.26 dependency.



signature.asc
Description: OpenPGP digital signature

Bug#894769: Java error message and permission on serial port

[beckert . j]

Hi,

I have the same issue, this is what I've found so far:

- after plugging in the Arduino and starting the IDE, the status line reports 
the correct 
settings (board type and serial device selected in a previous session)

- just klicking on the 'Tools' menu throws the error message:
java.lang.NullPointerException thrown while loading gnu.io.RXTXCommDriver

- the user running the Arduino IDE is in the dialout group, I tried if chmod 
666 on the serial 
device would help but it didn't

- tried to send a sketch to the Arduino, this produced the following two lines  
repeatedly:

java.lang.NullPointerException thrown while loading gnu.io.RXTXCommDriver
PORTS {} / {} => {}

then followed by:

processing.app.debug.RunnerException: Couldn’t find a Leonardo on the selected 
port. 
Check that you have the correct port selected.  If it is correct, try pressing 
the board's reset 
button after initiating the upload.
at 
processing.app.debug.AvrdudeUploader.uploadViaBootloader(AvrdudeUploader.java:154)
at 
processing.app.debug.AvrdudeUploader.uploadUsingPreferences(AvrdudeUploader.java:67)
at processing.app.Sketch.upload(Sketch.java:1671)
at processing.app.Sketch.exportApplet(Sketch.java:1627)
at processing.app.Sketch.exportApplet(Sketch.java:1599)
at processing.app.Editor$DefaultExportHandler.run(Editor.java:2380)
at java.base/java.lang.Thread.run(Thread.java:844)


-- System Information: 

Bug#895235: sugar-toolkit-gtk3 FTBFS: devlibs error: There is no package matching [libfribidi0-dev] and noone provides it

[Adrian Bunk]

Source: sugar-toolkit-gtk3
Version: 0.112-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sugar-toolkit-gtk3.html

...
d-shlibmove --commit \
--multiarch \
--exclude-la --exclude-a \
--devunversioned --ignorelibdep \
--movedev debian/tmp/usr/share/gir-1.0 usr/share/ \
--extralib 
debian/tmp/usr/lib/x86_64-linux-gnu/libsugar-eventcontroller.so \
debian/tmp/usr/lib/x86_64-linux-gnu/libsugarext.so
Library package automatic movement utility
 --> libasound2-dev package exists.
 --> libatk1.0-dev package exists.
 --> libcairo-dev is provided by a package.
 --> libcairo2-dev package exists.
devlibs error: There is no package matching [libfribidi0-dev] and noone 
provides it, please report bug to d-shlibs maintainer
 --> libglib2.0-dev package exists.
 --> libgtk-3-dev package exists.
 --> libgtk2.0-dev package exists.
 --> libice-dev package exists.
 --> libpango1.0-dev package exists.
 --> librsvg2-dev package exists.
 --> libsm-dev package exists.
 --> libx11-dev package exists.
 --> libxfixes-dev package exists.
 --> libxi-dev package exists.
make: *** [debian/rules:118: debian/stamp-local-shlibs-libsugarext] Error 1

Processed: tagging 893515

[Debian Bug Tracking System]

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

> tags 893515 + pending
Bug #893515 [src:digikam] digikam: FTBFS with kdepim 17.12.2
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#895213: marked as done (libbpp-popgen ftbfs on all architectures except on amd64)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 17:04:45 +
with message-id 
and subject line Bug#895213: fixed in libbpp-popgen 2.4.0-2
has caused the Debian Bug report #895213,
regarding libbpp-popgen ftbfs on all architectures except on amd64
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.)


-- 
895213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libbpp-popgen
Version: 2.4.0-1
Severity: serious
Tags: sid buster

libbpp-popgen ftbfs on all architectures except on amd64, please update the
symbols file
--- End Message ---
--- Begin Message ---
Source: libbpp-popgen
Source-Version: 2.4.0-2

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

Debian distribution maintenance software
pp.
Julien Dutheil  (supplier of updated 
libbpp-popgen package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 08 Apr 2018 18:40:50 +0200
Source: libbpp-popgen
Binary: libbpp-popgen-dev libbpp-popgen8
Architecture: source
Version: 2.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Julien Dutheil 
Description:
 libbpp-popgen-dev - Bio++ Population Genetics library development files
 libbpp-popgen8 - Bio++ Population Genetics library
Closes: 895213
Changes:
 libbpp-popgen (2.4.0-2) unstable; urgency=medium
 .
   [ Julien Dutheil ]
   * Provide symbols file only for amd64
 Closes: #895213
 .
   [ Andreas Tille ]
   * Provide full license text of CeCILL license
   * Point Vcs fields to salsa.debian.org
Checksums-Sha1:
 59efd2fd78f2329ecfae0f8148507a6248963723 2201 libbpp-popgen_2.4.0-2.dsc
 f2b3c72ef591819cc28be8908e7f0adf71642b63 18340 
libbpp-popgen_2.4.0-2.debian.tar.xz
 a106f288fd365ddd94baaf05218fbf1ba29c9332 13720 
libbpp-popgen_2.4.0-2_source.buildinfo
Checksums-Sha256:
 970d3c73c43b76db4343d33781e2fcbe8a4e93d02485bdee52f0486339dc22c8 2201 
libbpp-popgen_2.4.0-2.dsc
 4b0600a40f9568d5f54360dfa40b42925c29fc4e39573730d97d36a4f112e64d 18340 
libbpp-popgen_2.4.0-2.debian.tar.xz
 76797d071b15f4ed5369fc369a4149b7a6bedac13008656befdb6b123d7042dc 13720 
libbpp-popgen_2.4.0-2_source.buildinfo
Files:
 63f5eee0c6aac89f09e3eed95520e0b8 2201 science optional 
libbpp-popgen_2.4.0-2.dsc
 43c50b0070e5319dd341c854e4e3c30d 18340 science optional 
libbpp-popgen_2.4.0-2.debian.tar.xz
 9171df8695aaba9d105fb4fde6029d26 13720 science optional 
libbpp-popgen_2.4.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlrKRnMOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtEVcg//VSFByGDcJvwWP8klOUWCKT6rU98ogNiWKYFS
+y3e8My6tKC38eWXUe4hC/0iXVgY7XNdD2FLJeQraVuUyGS1CXKDd64GnEjkYAlf
bYkBdxr4Q7OxqxdEBDLjerH+tvvFJr9cKsHDVOXzggP6YaTDDGDKbX6ow7HC18j4
vuaPpX4D03sq9acz+pmQ6sX827DjQmDGgfDRnCetxe00j99+rpSxES7zlo5jRbke
A8c9UYjCyTui8jrf+2vhwGoKDhSKFfaRqtHU6lKhQRulGYZM+TygfMg1BR0ONgm9
4oJxK1bvWBqz3NPSbzUFPDSj2j5ptHko3ymd0DBQI/vOZ7bAVn8vHAHS/ebA5C7b
D5HgHGHs//HtXn64wOmkXqFO78TcUv+5xih0uhHrbXqCQeeO4W1ZhPuqyxO9CBqw
nZbSaDYgWa8YPhSB98l61WzDuwAoFHponX/BwnEUwVVqA+xR/H72ORpgVvcrYlFX
HhrBXykfKhAsuo5bjNb5/BECg0E3bYCL1oAdc6gBJ18CU0W786K9NHgWDcS46LCS
hXRd0RV7dME5djO8S3uuN89/TQX9bW/TY5XpiYUmNahE+xfG86ko3p2H2uLn4Toq
q8SZtyWbnVWgDwezYldtlgDuPACbpUZiyKedMmPjbZbr9ethlUWRBr65X74Pncvd
JRtYGnc=
=hbOP
-END PGP SIGNATURE End Message ---

Bug#893515: digikam: FTBFS with kdepim 17.12.2

[Steve Robbins]

On Monday, March 19, 2018 10:48:38 AM CDT you wrote:

> digikam 5.6.0-4 can't be compiled with KDE Pim 17.12.2, it failes
> because kcalcore was been refactored to use QDateTime instead of
> KDateTime. 

I have DigiKam 5.9.0 compiled locally and it works.  Unfortunately, it depends 
on exiv2 0.26 that only exists in experimental.  So the digikam upload will 
also be to experimental.

-Steve


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

Bug#895212: marked as done (libbpp-seq-omics ftbfs on all archs except amd64)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 16:49:33 +
with message-id 
and subject line Bug#895212: fixed in libbpp-seq-omics 2.4.0-2
has caused the Debian Bug report #895212,
regarding libbpp-seq-omics ftbfs on all archs except amd64
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.)


-- 
895212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libbpp-seq-omics
Version: 2.4.0-1
Severity: serious
Tags: sid buster

libbpp-seq-omics ftbfs on all archs except amd64. an update of the symbols file
is in order.
--- End Message ---
--- Begin Message ---
Source: libbpp-seq-omics
Source-Version: 2.4.0-2

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

Debian distribution maintenance software
pp.
Julien Dutheil  (supplier of updated 
libbpp-seq-omics package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 08 Apr 2018 18:29:27 +0200
Source: libbpp-seq-omics
Binary: libbpp-seq-omics-dev libbpp-seq-omics3
Architecture: source
Version: 2.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Julien Dutheil 
Description:
 libbpp-seq-omics-dev - Bio++ Sequence library: genomics components 
(development files)
 libbpp-seq-omics3 - Bio++ Sequence library: genomics components
Closes: 895212
Changes:
 libbpp-seq-omics (2.4.0-2) unstable; urgency=medium
 .
   [ Julien Dutheil ]
   * Provide symbols file only for amd64
 Closes: #895212
   * Versioned Build-Depends: d-shlibs (>= 0.82)
 .
   [ Andreas Tille ]
   * Provide full license text of CeCILL license
   * Point Vcs fields to salsa.debian.org
Checksums-Sha1:
 9a7710575a33af0720787d4a9bb35282d07dced1 2212 libbpp-seq-omics_2.4.0-2.dsc
 40aa361faaa82eb47820ef0dde4258a2fe518789 16836 
libbpp-seq-omics_2.4.0-2.debian.tar.xz
 7c6e8d5307295bbb2bd35808075f0fe1fa826ad8 13738 
libbpp-seq-omics_2.4.0-2_source.buildinfo
Checksums-Sha256:
 bfe032c93fc87dda8b011732fcb775623fe803f6fac80e8c774dee77b401f865 2212 
libbpp-seq-omics_2.4.0-2.dsc
 7c1a765402ea9893b618365a4625a4384e244f8bf8181f9bd92cd015c4ecd48e 16836 
libbpp-seq-omics_2.4.0-2.debian.tar.xz
 07eca4a1b54f16797080e0dc7d0e0330b326f48d9c4b9a2c4835df7aa4cb0ed2 13738 
libbpp-seq-omics_2.4.0-2_source.buildinfo
Files:
 6bebaa48be781b3901c85662ce121389 2212 science optional 
libbpp-seq-omics_2.4.0-2.dsc
 c3492ec3d93bc9f95f9e8257a174dad1 16836 science optional 
libbpp-seq-omics_2.4.0-2.debian.tar.xz
 5726dc7365c45bd6806b931745e3a09c 13738 science optional 
libbpp-seq-omics_2.4.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlrKQ6UOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtHx0g//WvZV9opGUVYOu0BY0jhLRGa4N5yWKEf74F4Y
28vmix3ovN6cpffH1RmdToGODJKWaDiM3L2lQiwTxYYMlPZ+Qrcd9pXbT8UQRNlz
xUbxYpAeDh9WdlKCmMXYtJZX4Y0QvP1eN/IQywI6kojje989LnN2MeeCeGihacXE
odSOInaqLS1q5IGnRjFTadDjjn0GC1z82inQWAntN9fcb2lGhSVXNUZH20716I6z
j/rYc2X3pm2dsTgZ1t/lztKfqbmtDD1683kIAz8U/rcrV7dphmWznnJfOe3gpkvW
LjlRtTLfEGe66cCcjb1L6LLX/vDAfygP7bkA93KFgEJ03YCo1bD4OI1GME9wXBpn
pBEXJqMB7EvYBdqL2X59yTCr9Y54wLBvQ0CZoAqzMzNpUlu8uI+7cFlxssqmR9r5
FKgxv9g4ppB0LteVSRCfzUHLkKJoDudDvwaDWjDpQ8pI6H6dwNhY84RPx+7EQ5xM
WgJkyRKa9Nf9F7O8qtLGtSyCTmHfGbgBBhO7my84gTU/B/ssFnD/ZiyB4YxXQU/Y
1laPmE6T9dYEnOrMdWJRZw2h630jPJwnT4jYdOojFgx+m3a7ueaq2zZLuWzVWR96
FhAfvQwEQgD6MBG7dJQYVX+DLhW2sEKZd5mzndttoO3PI517fHPjEFZjmosLbQQi
wJkny18=
=0hfd
-END PGP SIGNATURE End Message ---

Bug#895149: marked as done (cinnamon-screensaver: Fails to lock the screen if a menu is selected)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 17:47:11 +0200
with message-id <6340e52e12a36d88d0a65ff83cc94...@debian.org>
and subject line Bug#895149: cinnamon-screensaver: Fails to lock the screen if 
a menu  is selected
has caused the Debian Bug report #895149,
regarding cinnamon-screensaver: Fails to lock the screen if a menu is selected
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.)


-- 
895149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cinnamon-screensaver
Version: 3.6.1-2
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

I found that cinnamon-screensaver does not start if a window menu is clicked.
This can be a security problem as users unaware of this can leave their
computer unlocked unwillingly if they clicked a menu before abandoning or
trusting that their computer will be locked.

To reproduce this, just click the "File" menu in a window. For example, gnome-
terminal's "File" menu.

Starting cinnamon-screensaver in a terminal and looking at its log, I see the
following when the screensaver tries to start:



couldn't grab keyboard
couldn't grab keyboard
couldn't grab keyboard
couldn't grab keyboard
couldn't grab keyboard
couldn't grab keyboard
couldn't grab keyboard
couldn't grab keyboard
couldn't grab mouse
couldn't grab mouse
couldn't grab mouse
couldn't grab mouse
Can't fade in screensaver, unable to grab the keyboard

.

If I unselect the "File" menu and wait for the screensaver to trigger again, it
is then able to do it.

I'm reporting this as a security issue but I understand having this exploited
is somewhat unlikely: it would require the attacker to somehow make (or wait
for) the victim to click a menu and ensuring that he leaves his computer
unlocked and unattended without noticing the screen lock was not triggered.

Thanks and best regards,
Luís Picciochi Oliveira



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

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

Versions of packages cinnamon-screensaver depends on:
ii  cinnamon-desktop-data   3.6.2-2
ii  gir1.2-accountsservice-1.0  0.6.45-1
ii  gir1.2-cinnamondesktop-3.0  3.6.2-2
ii  gir1.2-gkbd-3.0 3.26.0-3
ii  gir1.2-glib-2.0 1.56.0-2
ii  gir1.2-gtk-3.0  3.22.29-2
ii  gir1.2-xapp-1.0 1.0.4-2
ii  iso-flags-png-320x240   1.0.1-1
ii  libc6   2.27-3
ii  libcscreensaver03.6.1-2
ii  libglib2.0-02.56.0-4
ii  libgtk-3-0  3.22.29-2
ii  python3 3.6.4-1
ii  python3-gi  3.28.1-1
ii  python3-gi-cairo3.28.1-1
ii  python3-setproctitle1.1.10-1+b1
ii  python3-xapp1.0.1-1
ii  python3-xlib0.20-3

Versions of packages cinnamon-screensaver recommends:
pn  cinnamon-screensaver-x-plugin  

Versions of packages cinnamon-screensaver suggests:
pn  cinnamon-screensaver-webkit-plugin  

-- no debconf information
--- End Message ---
--- Begin Message ---

Hi!

I found that cinnamon-screensaver does not start if a window menu is 
clicked.


This is a known issue with X11.  All screensavers running under X are 
affected.  The only solution is to move to Wayland (cinnamon does not 
yet support Wayland, but I hope it will happen in the not so distant 
future).


See for example this very old gnome-screensaver bug, where there is some 
discussion of the issue:

https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/49579

This is the existing bug of the X11 package:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514036

The issue is that the screensaver should grab the keyboard and mouse 
before starting, and when there's an X11 popup, the popup holds keyboard 
and mouse, not allowing the screensaver to do it.



This can be a security problem as users unaware of this can leave their
computer unlocked unwillingly if they clicked a menu before abandoning 
or

trusting that their computer will be locked.


There are plenty of things that could cause your screensaver not to 
start (on top of this one, the key combination that triggers it can 
sometimes be received by a different program, you could have a video 
playing on one screen, preventing the 

Bug#895178: marked as done (libosmocore-dev: missing dependency on libtalloc-dev)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 15:50:07 +
with message-id 
and subject line Bug#895178: fixed in libosmocore 0.10.2-6
has caused the Debian Bug report #895178,
regarding libosmocore-dev: missing dependency on libtalloc-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.)


-- 
895178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libosmocore-dev
Version: 0.10.2-5
Severity: serious
Control: affects -1 src:libosmo-netif src:libosmo-abis src:openggsn

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/libosmo-netif.html

...
make[5]: Entering directory '/build/1st/libosmo-netif-0.0.6/src/channel/abis'
/bin/bash ../../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../..  -I../../../include -I../../.. -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-Wall -I/usr/include/ -I/usr/include/   -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -c -o ipa_stream_server.lo ipa_stream_server.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../include 
-I../../.. -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wall -I/usr/include/ 
-I/usr/include/ -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -c ipa_stream_server.c  -fPIC -DPIC -o 
.libs/ipa_stream_server.o
In file included from ipa_stream_server.c:8:0:
/usr/include/osmocom/core/talloc.h:5:10: fatal error: talloc.h: No such file or 
directory
 #include 
  ^~
compilation terminated.
Makefile:392: recipe for target 'ipa_stream_server.lo' failed
make[5]: *** [ipa_stream_server.lo] Error 1
--- End Message ---
--- Begin Message ---
Source: libosmocore
Source-Version: 0.10.2-6

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated libosmocore package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 08 Apr 2018 12:05:14 +0100
Source: libosmocore
Binary: libosmocore libosmocodec0 libosmocodec-doc libosmocore9 libosmocore-doc 
libosmogb5 libosmogsm8 libosmogsm-doc libosmovty4 libosmovty-doc libosmoctrl0 
libosmosim0 libosmocore-dev libosmocore-utils
Architecture: source all amd64
Version: 0.10.2-6
Distribution: sid
Urgency: medium
Maintainer: Debian Mobcom Maintainers 

Changed-By: Thorsten Alteholz 
Description:
 libosmocodec-doc - Documentation for the osmo codec library
 libosmocodec0 - Osmo codec library
 libosmocore - Open Source MObile COMmunications CORE library (metapackage)
 libosmocore-dev - Development headers for Open Source MObile COMmunications 
CORE li
 libosmocore-doc - Documentation for the Osmo Core library
 libosmocore-utils - Utilities for gsm
 libosmocore9 - Osmo Core library
 libosmoctrl0 - Osmo control library
 libosmogb5 - Osmo GPRS GB library
 libosmogsm-doc - Documentation for the Osmo GSM utility library
 libosmogsm8 - Osmo GSM utility library
 libosmosim0 - Osmo SIM library
 libosmovty-doc - Documentation for the Osmo VTY library
 libosmovty4 - Osmo VTY library
Closes: 895178
Changes:
 libosmocore (0.10.2-6) unstable; urgency=medium
 .
   * add dependency of libtalloc-dev to libsomocore-dev (Closes: #895178)
Checksums-Sha1:
 3277d8643d88a4f0134aadd4c221939c81d8fc33 3010 libosmocore_0.10.2-6.dsc
 d838ff0e6566289918b25a7abc90c1a1c370e0a8 543196 libosmocore_0.10.2.orig.tar.xz
 46939750b8537e1e7d115ab937a1cdb50f8b6f3a 17784 
libosmocore_0.10.2-6.debian.tar.xz
 a6a5c196196f8bf53956c1ebb5a96adf385e8235 102276 
libosmocodec-doc_0.10.2-6_all.deb
 044d14f5bb244af4a02a3d82c9d978e996d66f20 6612 
libosmocodec0-dbgsym_0.10.2-6_amd64.deb
 b2e271d548ec36af8e06174fad9da105e2f1e21b 9956 libosmocodec0_0.10.2-6_amd64.deb
 6588e53b3af133ef5432710bd968d8202734b0b6 106692 
libosmocore-dev_0.10.2-6_amd64.deb
 a5454496fbcc94b2fc110e893934a086b2e22928 429888 
libosmocore-doc_0.10.2-6_all.deb
 

Bug#887666: jh_linkjars: Invalid option: N

[Emmanuel Bourg]

Le 08/04/2018 à 12:57, Niels Thykier a écrit :

> I had a go and it failed (presumably because I do not have write access)

You have to join back the team then ;)

Bug#894526: marked as done (scikit-learn build depends on the removed python-imaging)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 15:30:50 +
with message-id 
and subject line Bug#894526: fixed in scikit-learn 0.19.1-4
has caused the Debian Bug report #894526,
regarding scikit-learn build depends on the removed python-imaging
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.)


-- 
894526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scikit-learn
Version: 0.19.1-3
Severity: serious

The following packages have unmet dependencies:
 builddeps:scikit-learn : Depends: python-imaging but it is not installable

python-pil should be used instead of python-imaging.
--- End Message ---
--- Begin Message ---
Source: scikit-learn
Source-Version: 0.19.1-4

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

Debian distribution maintenance software
pp.
Yaroslav Halchenko  (supplier of updated scikit-learn 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 08 Apr 2018 10:02:12 -0400
Source: scikit-learn
Binary: python-sklearn python-sklearn-lib python3-sklearn python3-sklearn-lib 
python-sklearn-doc python-scikits-learn
Architecture: source all amd64
Version: 0.19.1-4
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: Yaroslav Halchenko 
Description:
 python-scikits-learn - transitional compatibility package for scikits.learn -> 
sklearn m
 python-sklearn - Python modules for machine learning and data mining
 python-sklearn-doc - documentation and examples for scikit-learn
 python-sklearn-lib - low-level implementations and bindings for scikit-learn
 python3-sklearn - Python modules for machine learning and data mining
 python3-sklearn-lib - low-level implementations and bindings for scikit-learn 
- Python
Closes: 894526
Changes:
 scikit-learn (0.19.1-4) unstable; urgency=medium
 .
   * debian/control
 - build-depends on python-pil not deprecating -imaging (Closes: #894526)
Checksums-Sha1:
 a62b475093b5036de635dff7527aa7aa992d4aab 2804 scikit-learn_0.19.1-4.dsc
 1d447f64613248007cbdd720d419d69ab099c1f3 1294852 
scikit-learn_0.19.1-4.debian.tar.xz
 47a712bfa7493e27d0a41e055901aee29bb863f5 85464 
python-scikits-learn_0.19.1-4_all.deb
 c64e210b997ce5e776ad756df18685a6eec765d6 5098876 
python-sklearn-doc_0.19.1-4_all.deb
 06c50a9bd8fc4fa4c2778b25e30beb0616eb7a09 6103932 
python-sklearn-lib-dbgsym_0.19.1-4_amd64.deb
 41f9fcaf6616cda8533affedfb26ff9309abef6a 1599380 
python-sklearn-lib_0.19.1-4_amd64.deb
 94cb6702eaa80ed55c0eaf8f35a151ef79278ff3 1455120 
python-sklearn_0.19.1-4_all.deb
 2d04be25cbc2d7d0e0747aa2b5d1ba6c80e38965 6469588 
python3-sklearn-lib-dbgsym_0.19.1-4_amd64.deb
 5d82b73007f916ca427352c56378fc28d1032633 1508112 
python3-sklearn-lib_0.19.1-4_amd64.deb
 df8f3b170d9c7b474d813618509f579a1bc1751f 1454884 
python3-sklearn_0.19.1-4_all.deb
 dcc08c1239d79277e002f2fb438f832cc585833c 12614 
scikit-learn_0.19.1-4_amd64.buildinfo
Checksums-Sha256:
 abf03cf5a91a8865736a3f83fa9b2bb00f3cdba28936dea759f7d891d85069c8 2804 
scikit-learn_0.19.1-4.dsc
 3ee7af5c1efe435399ca35a2fcae72955d5d5af6219d146968c374b4a3ec7330 1294852 
scikit-learn_0.19.1-4.debian.tar.xz
 0ed905d6940b4582b1d84a189281aedb2fe2e3a889ef6278ed4eb2b893b2587d 85464 
python-scikits-learn_0.19.1-4_all.deb
 ab54b327af6aa2a51c068e53a9e0d11df812616f8e2d94b3ad620cc1c102975c 5098876 
python-sklearn-doc_0.19.1-4_all.deb
 78fd30eee11400851e3c881825dd7d35bee19941d27d973b64c9a1c142b50ae0 6103932 
python-sklearn-lib-dbgsym_0.19.1-4_amd64.deb
 67dee1afec4c9357ab9bd1d752c7c4df3960f841db643064e67e6717671d3514 1599380 
python-sklearn-lib_0.19.1-4_amd64.deb
 cadbfcee2307b681ed720637faf0f0240579a5094909202e7aff2e04bd7fc6a3 1455120 
python-sklearn_0.19.1-4_all.deb
 761f3ab8a3c71beb55d8d7b7ddd3eb48de429023fc5e67b7d2b475b7a4b4d73b 6469588 
python3-sklearn-lib-dbgsym_0.19.1-4_amd64.deb
 a062c56219779bcecb1e956d66146e5f31b329819578b50fcdb6a92c4024a773 1508112 

Bug#895226: FTBFS on amd64 in testing/unstable - a number of tests failures

[Yaroslav Halchenko]

Package: python-cffi
Version: 1.11.5-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

testing/cffi0/test_verify.py ..s [ 35%]
 [ 39%]
.s...s..F.   [ 41%]
testing/cffi0/test_verify2.py ..s... [ 43%]
 [ 47%]
..s...s..F.  [ 50%]
...
and so on
here you could find the full build log:
http://neuro.debian.net/_files/_buildlogs/python-cffi/1.9.1/python-cffi_1.9.1-2~nd+1_amd64.build


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

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

Versions of packages python-cffi depends on:
ii  python   2.7.14-4
ii  python-cffi-backend  1.11.5-1
ii  python-pycparser 2.18-2

python-cffi recommends no packages.

Versions of packages python-cffi suggests:
ii  python-dev  2.7.14-4

-- no debconf information

Bug#895223: debhelper: Many packages using cmake failed to build from source since upgrade to 11.2

[Jean-Luc]

Le 08/04/2018 à 16:02, Mattia Rizzolo a écrit :

Control: notfound -1 11.1.6
Control: forcemerge 895181 -1

On Sun, Apr 08, 2018 at 03:36:03PM +0200, Jean-Luc Coulon (f5ibh) wrote:

Version: 11.1.6
I've upgraded debhelper from 11.1-6 to 11.2.

Then please use a correct Version there…

Sorry for that... Very sorry.



Since then, many packages dont build from source.
I've attached the build log of rawtherapee as an example.
The same applies to hugin, lensfun,...

Already fixed by 11.2.1

Ok, fine, thanks. Was not available yet when I've reported the bug. Sorry.

Jean-Luc

Processed: Re: Bug#895223: debhelper: Many packages using cmake failed to build from source since upgrade to 11.2

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 11.1.6
Bug #895223 [debhelper] debhelper: Many packages using cmake failed to build 
from source since upgrade to 11.2
No longer marked as found in versions debhelper/11.1.6.
> forcemerge 895181 -1
Bug #895181 {Done: Niels Thykier } [debhelper] debhelper: 
cmake-based projects broken
Bug #895223 [debhelper] debhelper: Many packages using cmake failed to build 
from source since upgrade to 11.2
Severity set to 'serious' from 'important'
Marked Bug as done
Marked as fixed in versions debhelper/11.2.1.
Marked as found in versions debhelper/11.2.
Merged 895181 895223

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

Bug#894526: Taking over scikit-learn into Debian Science team maintenance

[Yaroslav Halchenko]

meanwhile may be let me just take care about this tiny issue myself

On Sun, 08 Apr 2018, Yaroslav Halchenko wrote:

> Ok. Go ahead. Thanks.
>  But indeed please keep it in a shape so it could be easily backported.

> On April 8, 2018 1:59:53 AM EDT, Andreas Tille  wrote:
> >Hi Yaroslav and Michael,

> >as I did in the past with other scientific packages I would like to
> >take
> >over scikit-learn into Debian Science team maintenance to fix bug
> >#894526.  As I understood you in those cases you are OK with this as
> >long as backportability is given.

> >Please let me know until tomorrow if you do not like it.

> >Kind regards

> >   Andreas.



-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik


signature.asc
Description: PGP signature

Bug#895162: update etl, synfig and synfigstudio to 1.2.1

[Matthias Klose]

Control: tags -1 + patch

fyi, I updated etl, synfig and synfigstudio to 1.2.1, please find the packaging 
at

https://launchpad.net/ubuntu/+source/etl/1.2.1-0ubuntu1
https://launchpad.net/ubuntu/+source/synfig/1.2.1-0ubuntu1
https://launchpad.net/ubuntu/+source/synfigstudio/1.2.1-0ubuntu1

Processed: update etl, synfig and synfigstudio to 1.2.1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #895162 [src:synfigstudio] synfigstudio: Update fonts-freefont build-depends
Added tag(s) patch.

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

Bug#894526: Taking over scikit-learn into Debian Science team maintenance

[Yaroslav Halchenko]

Ok. Go ahead. Thanks.
 But indeed please keep it in a shape so it could be easily backported.

On April 8, 2018 1:59:53 AM EDT, Andreas Tille  wrote:
>Hi Yaroslav and Michael,
>
>as I did in the past with other scientific packages I would like to
>take
>over scikit-learn into Debian Science team maintenance to fix bug
>#894526.  As I understood you in those cases you are OK with this as
>long as backportability is given.
>
>Please let me know until tomorrow if you do not like it.
>
>Kind regards
>
>   Andreas.

Processed: Re: Bug#895218: astroml-addons: autopkgtest fails since python3.6 dropped depends on python3-distutils

[Debian Bug Tracking System]

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

> reassign 895218 python3-matplotlib 2.1.1-2
Bug #895218 [matplotlib] astroml-addons: autopkgtest fails since python3.6 
dropped depends on python3-distutils
Bug reassigned from package 'matplotlib' to 'python3-matplotlib'.
No longer marked as found in versions 2.1.1-2.
Ignoring request to alter fixed versions of bug #895218 to the same values 
previously set
Bug #895218 [python3-matplotlib] astroml-addons: autopkgtest fails since 
python3.6 dropped depends on python3-distutils
Marked as found in versions matplotlib/2.1.1-2.
> reassign 895220 python3-matplotlib 2.1.1-2
Bug #895220 [matplotlib] astroml: autopkgtest fails since python3.6 dropped 
depends on python3-distutils
Bug reassigned from package 'matplotlib' to 'python3-matplotlib'.
No longer marked as found in versions 2.1.1-2.
Ignoring request to alter fixed versions of bug #895220 to the same values 
previously set
Bug #895220 [python3-matplotlib] astroml: autopkgtest fails since python3.6 
dropped depends on python3-distutils
Marked as found in versions matplotlib/2.1.1-2.
> forcemerge 894502 895218 895220
Bug #894502 [python3-matplotlib] python3-matplotlib: Missing distutils 
dependency
Bug #895218 [python3-matplotlib] astroml-addons: autopkgtest fails since 
python3.6 dropped depends on python3-distutils
Severity set to 'serious' from 'normal'
894903 was blocked by: 894502
894903 was not blocking any bugs.
Added blocking bug(s) of 894903: 895218
Added tag(s) patch.
Bug #895220 [python3-matplotlib] astroml: autopkgtest fails since python3.6 
dropped depends on python3-distutils
Severity set to 'serious' from 'normal'
894903 was blocked by: 895218 894502
894903 was not blocking any bugs.
Added blocking bug(s) of 894903: 895220
Added tag(s) patch.
Merged 894502 895218 895220
>
End of message, stopping processing here.

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

Processed (with 2 errors): Re: Bug#895218: astroml-addons: autopkgtest fails since python3.6 dropped depends on python3-distutils

[Debian Bug Tracking System]

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

> reassign 895218 matplotlib 2.1.1-2
Bug #895218 [src:astroml-addons] astroml-addons: autopkgtest fails since 
python3.6 dropped depends on python3-distutils
Bug reassigned from package 'src:astroml-addons' to 'matplotlib'.
No longer marked as found in versions astroml-addons/0.2.2-4.
Ignoring request to alter fixed versions of bug #895218 to the same values 
previously set
Bug #895218 [matplotlib] astroml-addons: autopkgtest fails since python3.6 
dropped depends on python3-distutils
There is no source info for the package 'matplotlib' at version '2.1.1-2' with 
architecture ''
Unable to make a source version for version '2.1.1-2'
Marked as found in versions 2.1.1-2.
> reassign 895220 matplotlib 2.1.1-2
Bug #895220 [src:astroml] astroml: autopkgtest fails since python3.6 dropped 
depends on python3-distutils
Bug reassigned from package 'src:astroml' to 'matplotlib'.
No longer marked as found in versions astroml/0.3-7.
Ignoring request to alter fixed versions of bug #895220 to the same values 
previously set
Bug #895220 [matplotlib] astroml: autopkgtest fails since python3.6 dropped 
depends on python3-distutils
There is no source info for the package 'matplotlib' at version '2.1.1-2' with 
architecture ''
Unable to make a source version for version '2.1.1-2'
Marked as found in versions 2.1.1-2.
> forcemerge 894502 895218 895220
Bug #894502 [python3-matplotlib] python3-matplotlib: Missing distutils 
dependency
Unable to merge bugs because:
package of #895218 is 'matplotlib' not 'python3-matplotlib'
package of #895220 is 'matplotlib' not 'python3-matplotlib'
Failed to forcibly merge 894502: Did not alter merged bugs.

> affects 894502 python3-astroml python3-astroml-addons python3-aplpy 
> python3-imexam
Failed to mark 894502 as affecting package(s): failed to get lock on 
/org/bugs.debian.org/spool/lock/894502 -- Unable to lock 
/org/bugs.debian.org/spool/lock/894502 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/894502 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/894502 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/894502 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/894502 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/894502 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/894502 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/894502 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/894502 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/894502 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.

>
End of message, stopping processing here.

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

Processed: mugshot: diff for NMU version 0.3.1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 855157 + patch
Bug #855157 [mugshot] mugshot: missing dependency on accountsservice
Bug #785102 [mugshot] mugshot: missing dependency on accountsservice
Added tag(s) patch.
Added tag(s) patch.

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

Bug#855157: mugshot: diff for NMU version 0.3.1-1.1

[Adrian Bunk]

Control: tags 855157 + patch

Dear maintainer,

I've prepared an NMU for mugshot (versioned as 0.3.1-1.1) and uploaded 
it to DELAYED/2. Please feel free to tell me if I should cancel it.

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 -Nru mugshot-0.3.1/debian/changelog mugshot-0.3.1/debian/changelog
--- mugshot-0.3.1/debian/changelog	2016-08-26 23:48:02.0 +0300
+++ mugshot-0.3.1/debian/changelog	2018-04-08 15:46:42.0 +0300
@@ -1,3 +1,10 @@
+mugshot (0.3.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add the missing dependency on accountsservice. (Closes: #855157)
+
+ -- Adrian Bunk   Sun, 08 Apr 2018 15:46:42 +0300
+
 mugshot (0.3.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru mugshot-0.3.1/debian/control mugshot-0.3.1/debian/control
--- mugshot-0.3.1/debian/control	2016-08-26 23:48:02.0 +0300
+++ mugshot-0.3.1/debian/control	2018-04-08 15:46:42.0 +0300
@@ -15,6 +15,7 @@
 Package: mugshot
 Architecture: all
 Depends:
+ accountsservice,
  gir1.2-gdkpixbuf-2.0,
  gir1.2-glib-2.0,
  gir1.2-gst-plugins-base-1.0,

Processed: Bug title fix

[Debian Bug Tracking System]

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

> retitle 895214 slic3r-prusa FTBFS on mips/mipsel: virtual memory exhausted
Bug #895214 [src:slic3r-prusa] slic3r-prusa FTBFS on mips/mipsel:
Changed Bug title to 'slic3r-prusa FTBFS on mips/mipsel: virtual memory 
exhausted' from 'slic3r-prusa FTBFS on mips/mipsel:'.
> thanks
Stopping processing here.

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

Bug#895215: cypari2 FTBFS with dh-python >= 3.20180313

[Adrian Bunk]

Source: cypari2
Version: 1.1.4-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cypari2.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/cypari2-1.1.4'
python2 tests/rundoctest.py
Traceback (most recent call last):
  File "tests/rundoctest.py", line 16, in 
import cypari2
  File "/build/1st/cypari2-1.1.4/cypari2/__init__.py", line 1, in 
from .pari_instance import Pari
ImportError: No module named pari_instance
make[1]: *** [debian/rules:16: override_dh_auto_test] Error 1

Bug#895214: slic3r-prusa FTBFS on mips/mipsel:

[Adrian Bunk]

Source: slic3r-prusa
Version: 1.39.1+dfsg-2
Severity: serious
Tags: patch

https://buildd.debian.org/status/package.php?p=slic3r-prusa=sid

...
[ 76%] Building CXX object 
xs/CMakeFiles/libslic3r.dir/src/libslic3r/PlaceholderParser.cpp.o
cd /<>/slic3r-prusa-1.39.1+dfsg/obj-mipsel-linux-gnu/xs && 
/usr/bin/c++  -DBOOST_LOG_DYN_LINK -DSLIC3R_GUI -DSLIC3R_PRUS 
-DTBB_USE_CAPTURED_EXCEPTION=0 -DUNICODE -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 
-D_UNICODE -D__WXGTK__ -DwxUSE_UNICODE 
-I/<>/slic3r-prusa-1.39.1+dfsg/xs/src 
-I/<>/slic3r-prusa-1.39.1+dfsg/xs/src/libslic3r 
-I/usr/lib/mipsel-linux-gnu/wx/include/gtk2-unicode-3.0 -I/usr/include/wx-3.0 
-I/usr/include/eigen3  -g -O2 
-fdebug-prefix-map=/<>/slic3r-prusa-1.39.1+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -O3 -DNDEBUG   -fPIC -std=c++11 -Wall 
-fext-numeric-literals -std=gnu++11 -o 
CMakeFiles/libslic3r.dir/src/libslic3r/PlaceholderParser.cpp.o -c 
/<>/slic3r-prusa-1.39.1+dfsg/xs/src/libslic3r/PlaceholderParser.cpp
/<>/slic3r-prusa-1.39.1+dfsg/xs/src/libslic3r/PlaceholderParser.cpp: 
In function 'std::__cxx11::string Slic3r::process_macro(const string&, 
Slic3r::client::MyContext&)':
/<>/slic3r-prusa-1.39.1+dfsg/xs/src/libslic3r/PlaceholderParser.cpp:1145:10:
 warning: unused variable 'res' [-Wunused-variable]
 bool res = phrase_parse(iter, end, macro_processor_instance(), 
space, output);
  ^~~
/<>/slic3r-prusa-1.39.1+dfsg/xs/src/libslic3r/PlaceholderParser.cpp: 
In instantiation of 
'Slic3r::client::macro_processor::macro_processor() [with Iterator = 
__gnu_cxx::__normal_iterator >]':
/<>/slic3r-prusa-1.39.1+dfsg/xs/src/libslic3r/PlaceholderParser.cpp:1139:33:
   required from here
/<>/slic3r-prusa-1.39.1+dfsg/xs/src/libslic3r/PlaceholderParser.cpp:881:39:
 warning: suggest parentheses around comparison in operand of '|' 
[-Wparentheses]
 (   eps(_a==true) > text_block(_r1) [_val=_1]
 ~~^~~
/<>/slic3r-prusa-1.39.1+dfsg/xs/src/libslic3r/PlaceholderParser.cpp: 
In instantiation of 'static void 
Slic3r::client::expr::ternary_op(Slic3r::client::expr&, 
Slic3r::client::expr&, Slic3r::client::expr&) [with 
Iterator = __gnu_cxx::__normal_iterator >]':
/<>/slic3r-prusa-1.39.1+dfsg/xs/src/libslic3r/PlaceholderParser.cpp:947:103:
   required from 'Slic3r::client::macro_processor::macro_processor() 
[with Iterator = __gnu_cxx::__normal_iterator >]'
/<>/slic3r-prusa-1.39.1+dfsg/xs/src/libslic3r/PlaceholderParser.cpp:1139:33:
   required from here
/<>/slic3r-prusa-1.39.1+dfsg/xs/src/libslic3r/PlaceholderParser.cpp:469:18:
 warning: unused variable 'value' [-Wunused-variable]
 bool value = false;
  ^
/<>/slic3r-prusa-1.39.1+dfsg/xs/src/libslic3r/PlaceholderParser.cpp: 
In instantiation of 'static void 
Slic3r::client::expr::regex_op(Slic3r::client::expr&, 
boost::iterator_range&, char) [with Iterator = 
__gnu_cxx::__normal_iterator >]':
/<>/slic3r-prusa-1.39.1+dfsg/xs/src/libslic3r/PlaceholderParser.cpp:449:106:
   required from 'static void 
Slic3r::client::expr::regex_matches(Slic3r::client::expr&, 
boost::iterator_range&) [with Iterator = 
__gnu_cxx::__normal_iterator >]'
/<>/slic3r-prusa-1.39.1+dfsg/xs/src/libslic3r/PlaceholderParser.cpp:965:72:
   required from 'Slic3r::client::macro_processor::macro_processor() 
[with Iterator = __gnu_cxx::__normal_iterator >]'
/<>/slic3r-prusa-1.39.1+dfsg/xs/src/libslic3r/PlaceholderParser.cpp:1139:33:
   required from here
/<>/slic3r-prusa-1.39.1+dfsg/xs/src/libslic3r/PlaceholderParser.cpp:427:32:
 warning: unused variable 'mask' [-Wunused-variable]
 const std::string *mask = nullptr;
^~~~
virtual memory exhausted: Cannot allocate memory
xs/CMakeFiles/libslic3r.dir/build.make:1169: recipe for target 
'xs/CMakeFiles/libslic3r.dir/src/libslic3r/PlaceholderParser.cpp.o' failed
make[3]: *** 
[xs/CMakeFiles/libslic3r.dir/src/libslic3r/PlaceholderParser.cpp.o] Error 1


Fix:

--- debian/rules.old2018-04-03 05:39:30.057140450 +
+++ debian/rules2018-04-03 05:40:48.460469366 +
@@ -2,6 +2,12 @@
 
 include /usr/share/dpkg/default.mk
 
+# less debug info to avoid running
+# out of address space
+ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel))
+  export DEB_CXXFLAGS_MAINT_APPEND += -g1
+endif
+
 %:
dh $@ --buildsystem=cmake --parallel
 

Bug#895213: libbpp-popgen ftbfs on all architectures except on amd64

[Matthias Klose]

Package: src:libbpp-popgen
Version: 2.4.0-1
Severity: serious
Tags: sid buster

libbpp-popgen ftbfs on all architectures except on amd64, please update the
symbols file

Bug#895212: libbpp-seq-omics ftbfs on all archs except amd64

[Matthias Klose]

Package: src:libbpp-seq-omics
Version: 2.4.0-1
Severity: serious
Tags: sid buster

libbpp-seq-omics ftbfs on all archs except amd64. an update of the symbols file
is in order.

Bug#895174: glib2.0 FTBFS: fails to execute ninja

[Simon McVittie]

On Sun, 08 Apr 2018 at 09:49:14 +0200, Sven Joachim wrote:
> Current glib2.0 source can be built with either meson or autotools, and
> debian/rules should probably specify which one to use.  Feel free
> reassign a clone of this bug back to glib2.0 for that, but "debian/rules
> clean" even fails when meson is installed, which looks like a serious
> problem in debhelper.

meson is like cmake, or a mixture of Autotools and configure: it
implements the dh_auto_configure step. ninja is like make: it implements
the dh_auto_build step.

smcv

Bug#895208: gnumeric: missing build dependency on libxml2-utils

[Adrian Bunk]

Source: gnumeric
Version: 1.12.35-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnumeric.html

...
checking for perl... perl
checking
 for perl ExtUtils::Embed module... yes
checking Checking for perl compiler, linker, libraries and headers... yes
checking for python... /usr/bin/python
checking
 for python = 2.x... yes
checking
 Look for /usr/include/python2.7/Python.h... yes
checking for PYGOBJECT... yes
checking for itstool... itstool
checking for xmllint... no
configure: error: xmllint not found

Bug#895207: golang-github-appc-docker2aci: FTBFS and Debci failure

[Adrian Bunk]

Source: golang-github-appc-docker2aci
Version: 0.14.0+dfsg-2
Severity: serious

https://ci.debian.net/packages/g/golang-github-appc-docker2aci/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-appc-docker2aci.html

...
   dh_auto_build -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/build/1st/golang-github-appc-docker2aci-0.14.0\+dfsg/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/build/1st/golang-github-appc-docker2aci-0.14.0\+dfsg/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/appc/docker2aci github.com/appc/docker2aci/lib 
github.com/appc/docker2aci/lib/common github.com/appc/docker2aci/lib/internal 
github.com/appc/docker2aci/lib/internal/backend/file 
github.com/appc/docker2aci/lib/internal/backend/repository 
github.com/appc/docker2aci/lib/internal/docker 
github.com/appc/docker2aci/lib/internal/tarball 
github.com/appc/docker2aci/lib/internal/types 
github.com/appc/docker2aci/lib/internal/typesV2 
github.com/appc/docker2aci/lib/internal/util 
github.com/appc/docker2aci/lib/tests github.com/appc/docker2aci/pkg/log
github.com/appc/docker2aci/lib/internal/types
github.com/appc/docker2aci/lib/internal/docker
github.com/docker/distribution/digest
github.com/docker/distribution/reference
github.com/appc/docker2aci/lib/common
github.com/appc/docker2aci/lib/internal/tarball
github.com/opencontainers/go-digest
github.com/opencontainers/image-spec/specs-go
github.com/opencontainers/image-spec/specs-go/v1
github.com/appc/docker2aci/lib/internal/typesV2
# github.com/appc/docker2aci/lib/internal/typesV2
src/github.com/appc/docker2aci/lib/internal/typesV2/docker_types.go:35:29: 
undefined: v1.MediaTypeImageManifestList
github.com/appc/spec/schema/common
github.com/coreos/go-semver/semver
github.com/gogo/protobuf/proto
github.com/spf13/pflag
gopkg.in/inf.v0
github.com/appc/spec/vendor/k8s.io/kubernetes/pkg/api/resource
github.com/appc/spec/schema/types
go4.org/errorutil
github.com/appc/spec/schema
github.com/appc/spec/pkg/acirenderer
github.com/appc/docker2aci/lib/internal/util
github.com/appc/docker2aci/pkg/log
github.com/appc/spec/pkg/device
github.com/appc/spec/pkg/tarheader
github.com/appc/spec/aci
github.com/klauspost/cpuid
github.com/klauspost/compress/flate
github.com/klauspost/crc32
github.com/klauspost/pgzip
golang.org/x/sys/unix
golang.org/x/crypto/ssh/terminal
github.com/coreos/ioprogress
github.com/coreos/pkg/progressutil
dh_auto_build: cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/build/1st/golang-github-appc-docker2aci-0.14.0\+dfsg/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/build/1st/golang-github-appc-docker2aci-0.14.0\+dfsg/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/appc/docker2aci github.com/appc/docker2aci/lib 
github.com/appc/docker2aci/lib/common github.com/appc/docker2aci/lib/internal 
github.com/appc/docker2aci/lib/internal/backend/file 
github.com/appc/docker2aci/lib/internal/backend/repository 
github.com/appc/docker2aci/lib/internal/docker 
github.com/appc/docker2aci/lib/internal/tarball 
github.com/appc/docker2aci/lib/internal/types 
github.com/appc/docker2aci/lib/internal/typesV2 
github.com/appc/docker2aci/lib/internal/util 
github.com/appc/docker2aci/lib/tests github.com/appc/docker2aci/pkg/log 
returned exit code 2
make: *** [debian/rules:4: build] Error 2

Bug#895205: dislocker FTBFS with ruby2.5-dev 2.5.1-1

[Adrian Bunk]

Source: dislocker
Version: 0.7.1-3
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dislocker.html

...
cd /build/1st/dislocker-0.7.1/src && /usr/bin/cc -DAUTHOR="\"Romain Coltel\"" 
-DPROGNAME=\"dislocker\" -DVERSION=\"0.7.1\" -D_FILE_OFFSET_BITS=64 
-D_HAVE_RUBY=2.5.1 -D__ARCH=\"x86_64\" -D__ARCH_X86_64 -D__LINUX 
-D__OS=\"Linux\" -Ddislocker_EXPORTS -isystem /usr/local/include 
-I/build/1st/dislocker-0.7.1/include -I/usr/include/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/x86_64-linux-gnu 
-I/usr/include/x86_64-linux-gnu/ruby-2.5.1  -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wall 
-Wextra -fstack-protector -fstrict-aliasing -D_FORTIFY_SOURCE=2 -O1 
-Wconversion -Wl,-z,now -Wl,-z,relro -fPIC   -o 
CMakeFiles/dislocker.dir/config.c.o   -c /build/1st/dislocker-0.7.1/src/config.c
In file included from /usr/include/ruby-2.5.0/ruby.h:33:0,
 from /build/1st/dislocker-0.7.1/include/dislocker/ruby.h:35,
 from /build/1st/dislocker-0.7.1/include/dislocker/common.h:83,
 from /build/1st/dislocker-0.7.1/src/config.c:28:
/usr/include/ruby-2.5.0/ruby/ruby.h:24:10: fatal error: ruby/config.h: No such 
file or directory
 #include "ruby/config.h"
  ^~~
compilation terminated.
make[3]: *** [src/CMakeFiles/dislocker.dir/build.make:114: 
src/CMakeFiles/dislocker.dir/config.c.o] Error 1


The version differs between -I/usr/include/x86_64-linux-gnu/ruby-2.5.1
and /usr/include/x86_64-linux-gnu/ruby-2.5.0/ruby/config.h

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 894432 https://github.com/ncclient/ncclient/issues/227
Bug #894432 [src:python-ncclient] python-ncclient FTBFS: AttributeError: 
'NoneType' object has no attribute 'settimeout'
Changed Bug forwarded-to-address to 
'https://github.com/ncclient/ncclient/issues/227' from 
'https://github.com/ncclient/ncclient/issues/218'.
> owner 894432 !
Bug #894432 [src:python-ncclient] python-ncclient FTBFS: AttributeError: 
'NoneType' object has no attribute 'settimeout'
Owner recorded as Sebastien Badia .
> tags 894432 + pending
Bug #894432 [src:python-ncclient] python-ncclient FTBFS: AttributeError: 
'NoneType' object has no attribute 'settimeout'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#887666: jh_linkjars: Invalid option: N

[Niels Thykier]

Emmanuel Bourg:
> Le 07/04/2018 à 19:55, Niels Thykier a écrit :
> 
>> I have written some patches to rewrite most of the javatools helpers
>> into perl using Debhelper's Dh_Lib[1].  This would fix this problem and
>> avoid future instances of it.
> 
> Thank you Niels! Feel free to commit the changes directly into the Git
> repository (still on Alioth).
> 
> Emmanuel Bourg
> 

Thanks. :)

I had a go and it failed (presumably because I do not have write access):

"""
$ git push origin master
Counting objects: 44, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (44/44), done.
Writing objects: 100% (44/44), 10.89 KiB | 1.82 MiB/s, done.
Total 44 (delta 34), reused 0 (delta 0)
remote: error: insufficient permission for adding an object to
repository database ./objects
remote: fatal: failed to write object
error: remote unpack failed: unpack-objects abnormal exit
To ssh://git.debian.org/git/pkg-java/javatools.git
 ! [remote rejected] master -> master (unpacker error)
error: failed to push some refs to
'ssh://git.debian.org/git/pkg-java/javatools.git'
"""

(As I recall, I am no longer a member of the java team on alioth)

Thanks,
~Niels

Processed: affects 895178

[Debian Bug Tracking System]

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

> affects 895178 src:osmo-bts
Bug #895178 [libosmocore-dev] libosmocore-dev: missing dependency on 
libtalloc-dev
Added indication that 895178 affects src:osmo-bts
> thanks
Stopping processing here.

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

Processed: affects 895178

[Debian Bug Tracking System]

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

> affects 895178 src:openggsn src:openbsc src:libosmo-abis
Bug #895178 [libosmocore-dev] libosmocore-dev: missing dependency on 
libtalloc-dev
Added indication that 895178 affects src:openbsc
> thanks
Stopping processing here.

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

Bug#895154: ffmpeg: FTBFS - make[2]: write error: stdout

[Niels Thykier]

On Sat, 7 Apr 2018 21:38:53 +0100 James Cowgill  wrote:
> Source: ffmpeg
> Version: 7:3.4.1-1
> Severity: serious
> Tags: sid buster
> 
> For some reason ffmpeg has started FTBFS with this error:
> > TESTvsynth2-zlib
> > /<>/tests/fate-run.sh fate-vsynth2-zlib "" "" 
> > "/<>/debian/standard" 'enc_dec "rawvideo -s 352x288 -pix_fmt 
> > yuv420p " tests/data/vsynth2.yuv avi "-c zlib " rawvideo "-s 352x288 
> > -pix_fmt yuv420p -vsync 0 " -keep ""' '' 
> > '/<>/tests/ref/vsynth/vsynth2-zlib' '' '1' '' '' '' '' '' '1' 
> > '' '' ''
> >  /<>/debian/standard/ffmpeg -nostdin -nostats -cpuflags all -f 
> > rawvideo -s 352x288 -pix_fmt yuv420p -threads 1 -idct simple -flags 
> > +bitexact -sws_flags +accurate_rnd+bitexact -fflags +bitexact -hwaccel none 
> > -threads 1 -thread_type frame+slice -i 
> > /<>/debian/standard/tests/data/vsynth2.yuv -threads 1 -idct 
> > simple -dct fastint -c zlib -flags +bitexact -sws_flags 
> > +accurate_rnd+bitexact -fflags +bitexact -f avi -y 
> > /<>/debian/standard/tests/data/fate/vsynth2-zlib.avi
> >  /<>/debian/standard/ffmpeg -nostdin -nostats -cpuflags all 
> > -threads 1 -idct simple -flags +bitexact -sws_flags +accurate_rnd+bitexact 
> > -fflags +bitexact -hwaccel none -threads 1 -thread_type frame+slice -i 
> > /<>/debian/standard/tests/data/fate/vsynth2-zlib.avi -threads 
> > 1 -idct simple -dct fastint -s 352x288 -pix_fmt yuv420p -vsync 0 -flags 
> > +bitexact -sws_flags +accurate_rnd+bitexact -fflags +bitexact -f rawvideo 
> > -y 
> > /<>/debian/standard/tests/data/fate/vsynth2-zlib.out.rawvideo
> > make[2]: Leaving directory '/<>/debian/standard'
> > make[2]: write error: stdout
> > dh_auto_test: cd debian/standard && make -j4 -O check -k returned exit code 
> > 1
> > make[1]: *** [debian/rules:231: override_dh_auto_test-arch] Error 25
> > make[1]: Leaving directory '/<>'
> > make: *** [debian/rules:192: binary] Error 2
> > dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
> > status 2
> 
> This can be seen on the reproducible builds first seen 2018-03-15
> affecting 3.4 and 3.5 in experimental.
> 
> I'm guessing this has something to do with "make -O" which was enabled
> recently in debhelper, but I haven't checked.
> 
> James
> 

Hi James,

In a recent upload, debhelper started using -Oline instead of -O.  Does
that solve this problem for you?  (It was done unrelated to this bug,
but looking at the documentation for -O, I suspect it might help here as
well)

Thanks,
~Niels

Processed: found 858250 in 0.1.1+dfsg1-2

[Debian Bug Tracking System]

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

> found 858250 0.1.1+dfsg1-2
Bug #858250 {Done: Balint Reczey } [runc] Fails to build 
for unstable, build-depends not strict enough
Bug #861966 {Done: Balint Reczey } [runc] Fails to build 
for unstable, build-depends not strict enough
Marked as found in versions runc/0.1.1+dfsg1-2.
Marked as found in versions runc/0.1.1+dfsg1-2.
> thanks
Stopping processing here.

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

Bug#894473: closed by Andreas Tille <ti...@debian.org> (Bug#894473: fixed in prodigal 1:2.6.3-3)

[Adrian Bunk]

Control: reopen -1

On Thu, Apr 05, 2018 at 09:27:06AM +, Debian Bug Tracking System wrote:
>...
>  prodigal (1:2.6.3-3) unstable; urgency=medium
>  .
>[ Adrian Bunk ]
>* Stop overwriting the optimization with -O3
>  Closes: #894473
>...

I didn't write clearly enough that *both* this patch and the
debian/rules change from the bug are required to fix the FTBFS.

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: Re: Bug#894473 closed by Andreas Tille <ti...@debian.org> (Bug#894473: fixed in prodigal 1:2.6.3-3)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #894473 {Done: Andreas Tille } [src:prodigal] prodigal 
FTBFS on armel/armhf: Build killed with signal TERM after 150 minutes of 
inactivity
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions prodigal/1:2.6.3-3.

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

Bug#894816: marked as done ([ruby-gtk2] mikutter doesn't start with error)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 09:50:16 +
with message-id 
and subject line Bug#894816: fixed in ruby-gnome2 3.2.3-2
has caused the Debian Bug report #894816,
regarding [ruby-gtk2] mikutter doesn't start with error
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.)


-- 
894816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mikutter
Version: 3.6.5+dfsg-1
Severity: important

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

mikutter doesn't start.

Followings are console message.

$ mikutter 
Traceback (most recent call last):
54: from /usr/share/mikutter/mikutter.rb:42:in `'
53: from /usr/share/mikutter/core/miquire.rb:18:in `miquire'
52: from /usr/share/mikutter/core/miquire.rb:75:in `miquire'
51: from /usr/share/mikutter/core/miquire.rb:75:in `each'
50: from /usr/share/mikutter/core/miquire.rb:76:in `block in miquire'
49: from /usr/share/mikutter/core/miquire.rb:95:in 
`file_or_directory_require'
48: from /usr/share/mikutter/core/miquire.rb:98:in 
`miquire_original_require'
47: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
46: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
45: from /usr/share/mikutter/core/boot/load_plugin.rb:10:in `'
44: from /usr/share/mikutter/core/miquire_plugin.rb:96:in `load_all'
43: from /usr/share/mikutter/core/miquire_plugin.rb:36:in `each_spec'
42: from /usr/share/mikutter/core/miquire_plugin.rb:33:in `each'
41: from /usr/share/mikutter/core/miquire_plugin.rb:33:in `each'
40: from /usr/share/mikutter/core/miquire_plugin.rb:38:in `block in 
each_spec'
39: from /usr/share/mikutter/core/miquire_plugin.rb:98:in `block in 
load_all'
38: from /usr/share/mikutter/core/miquire_plugin.rb:146:in `load'
37: from /usr/share/mikutter/core/utils.rb:278:in `atomic'
36: from /usr/lib/ruby/2.5.0/monitor.rb:226:in `mon_synchronize'
35: from /usr/share/mikutter/core/utils.rb:278:in `block in atomic'
34: from /usr/share/mikutter/core/miquire_plugin.rb:147:in `block in 
load'
33: from /usr/share/mikutter/core/miquire_plugin.rb:147:in `each'
32: from /usr/share/mikutter/core/miquire_plugin.rb:149:in `block (2 
levels) in load'
31: from /usr/share/mikutter/core/miquire_plugin.rb:146:in `load'
30: from /usr/share/mikutter/core/utils.rb:278:in `atomic'
29: from /usr/lib/ruby/2.5.0/monitor.rb:226:in `mon_synchronize'
28: from /usr/share/mikutter/core/utils.rb:278:in `block in atomic'
27: from /usr/share/mikutter/core/miquire_plugin.rb:147:in `block in 
load'
26: from /usr/share/mikutter/core/miquire_plugin.rb:147:in `each'
25: from /usr/share/mikutter/core/miquire_plugin.rb:149:in `block (2 
levels) in load'
24: from /usr/share/mikutter/core/miquire_plugin.rb:146:in `load'
23: from /usr/share/mikutter/core/utils.rb:278:in `atomic'
22: from /usr/lib/ruby/2.5.0/monitor.rb:226:in `mon_synchronize'
21: from /usr/share/mikutter/core/utils.rb:278:in `block in atomic'
20: from /usr/share/mikutter/core/miquire_plugin.rb:158:in `block in 
load'
19: from /usr/share/mikutter/core/miquire_plugin.rb:158:in `load'
18: from /usr/share/mikutter/core/plugin/gtk/gtk.rb:7:in `'
17: from /usr/share/mikutter/core/miquire.rb:18:in `miquire'
16: from /usr/share/mikutter/core/miquire.rb:75:in `miquire'
15: from /usr/share/mikutter/core/miquire.rb:75:in `each'
14: from /usr/share/mikutter/core/miquire.rb:76:in `block in miquire'
13: from /usr/share/mikutter/core/miquire.rb:95:in 
`file_or_directory_require'
12: from /usr/share/mikutter/core/miquire.rb:98:in 
`miquire_original_require'
11: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
10: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
 9: from 
/usr/share/mikutter/core/mui/cairo_cell_renderer_message.rb:3:in `'
 8: from /usr/share/mikutter/core/miquire.rb:18:in `miquire'
 7: from /usr/share/mikutter/core/miquire.rb:75:in `miquire'
 6: from /usr/share/mikutter/core/miquire.rb:75:in `each'
 5: from /usr/share/mikutter/core/miquire.rb:76:in `block in miquire'
 4: from /usr/share/mikutter/core/miquire.rb:95:in 

Bug#895174: marked as done (glib2.0 FTBFS: fails to execute ninja)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 09:05:17 +
with message-id 
and subject line Bug#895174: fixed in debhelper 11.2.1
has caused the Debian Bug report #895174,
regarding glib2.0 FTBFS: fails to execute ninja
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.)


-- 
895174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glib2.0
Version: 2.56.0-6
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

glib2.0 FTBFS during dh_auto_clean. Including the full build log:

| dpkg-buildpackage: info: source package glib2.0
| dpkg-buildpackage: info: source version 2.56.0-6
| dpkg-buildpackage: info: source distribution unstable
| dpkg-buildpackage: info: source changed by Simon McVittie 
|  dpkg-source --before-build glib2.0-2.56.0
| dpkg-buildpackage: info: host architecture amd64
|  debian/rules clean
| dh clean --with gnome,python3
|dh_auto_clean
|   LC_ALL=C.UTF-8 ninja clean
| Can't exec "ninja": No such file or directory at 
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 356.
| dh_auto_clean: LC_ALL=C.UTF-8 ninja clean failed to execute: No child 
processes
| dh_auto_clean: LC_ALL=C.UTF-8 ninja clean returned exit code 10
| make: *** [debian/rules:24: clean] Error 2
| dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2

I guess this is connected to debhelper 11.2 (as the failure surfaced
close to the upload). Since I'm unsure whether this is a debhelper or
glib2.0 problem, I'm filing it with glib2.0 and trust that you know how
to reassign.

Helmut
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 11.2.1

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 08 Apr 2018 08:47:35 +
Source: debhelper
Binary: debhelper dh-systemd
Architecture: source
Version: 11.2.1
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Description:
 debhelper  - helper programs for debian/rules
 dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
Closes: 895174 895181
Changes:
 debhelper (11.2.1) unstable; urgency=medium
 .
   * Buildsystem.pm: Correctly pass build directory values to
 target buildsystems.  Thanks to Helmut Grohne, Adrian Bunk
 and Tobias Frost for the reports and debugging.
 (Closes: #895174, #895181)
   * Buildsystems: Avoid choosing a build system for the clean
 step if it is not necessary.  Previously, debhelper could
 choose a "random" build system that would prefer building
 in a separate build directory on the basis that the build
 directory should be removed.  With this, change we only
 choose such a build system if there is a build directory
 to remove.
Checksums-Sha1:
 ddf845168510585021d9299e618f63b0b0d4eaab 1689 debhelper_11.2.1.dsc
 e1626da376d6e594e262cdbde3914a9c2e103777 456036 debhelper_11.2.1.tar.xz
 2d58c4211d38e4198f41638727657115664f8c46 4554 debhelper_11.2.1_source.buildinfo
Checksums-Sha256:
 2380aee11355a444da3e9f17bcefcd8c4063c65a7df6a6176742b3911310cec7 1689 
debhelper_11.2.1.dsc
 d969476a748f024381fa985813ac444eddd73995700109c3f304de711251010b 456036 
debhelper_11.2.1.tar.xz
 5a862896d758a8f26b8b2ac9b3ce83971ef4aef2da9c0743686385fdd24dc4d1 4554 
debhelper_11.2.1_source.buildinfo
Files:
 f958818ca0108a2b038f2d766d218e45 1689 devel optional debhelper_11.2.1.dsc
 34eb8e89f848e2bc39b9c4072938b036 456036 devel optional debhelper_11.2.1.tar.xz
 727b2c114df3d57747b7a2bc8be3233a 4554 devel optional 
debhelper_11.2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEsxMaRR2/33ygW0GXBUu7n32AZEIFAlrJ12cACgkQBUu7n32A
ZEISURAAsaLrgp4F28ct/an0rwWzXhWOiIYN4e4YSUTdMLp5r4b5CsxymluesU9+

Bug#895181: marked as done (debhelper: cmake-based projects broken)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 09:05:17 +
with message-id 
and subject line Bug#895181: fixed in debhelper 11.2.1
has caused the Debian Bug report #895181,
regarding debhelper: cmake-based projects broken
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.)


-- 
895181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895181
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 11.2
Severity: serious

Dear Maintainer,

since yesterday evening all cmake-based projects fails to compile.
Symptom is that it looks like that debhelper skips the build step.

Example buildlogs are for my expermential builds of cppds:
https://buildd.debian.org/status/package.php?p=cppdb=experimental

Locally, I can reproduce this behaviour also on my other packages
employing cmake (e.g dhewm3, rbfdoom3): it works with 11.1.6, it breaks
with 11.2.

--
tobi

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

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

Versions of packages debhelper depends on:
ii  autotools-dev20180224.1
ii  dh-autoreconf17
ii  dh-strip-nondeterminism  0.040-1
ii  dpkg 1.19.0.5
ii  dpkg-dev 1.19.0.5
ii  file 1:5.32-2
ii  libdpkg-perl 1.19.0.5
ii  man-db   2.8.3-1
ii  perl 5.26.1-5
ii  po-debconf   1.0.20

debhelper recommends no packages.

Versions of packages debhelper suggests:
pn  dh-make  
pn  dwz  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 11.2.1

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 08 Apr 2018 08:47:35 +
Source: debhelper
Binary: debhelper dh-systemd
Architecture: source
Version: 11.2.1
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Description:
 debhelper  - helper programs for debian/rules
 dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
Closes: 895174 895181
Changes:
 debhelper (11.2.1) unstable; urgency=medium
 .
   * Buildsystem.pm: Correctly pass build directory values to
 target buildsystems.  Thanks to Helmut Grohne, Adrian Bunk
 and Tobias Frost for the reports and debugging.
 (Closes: #895174, #895181)
   * Buildsystems: Avoid choosing a build system for the clean
 step if it is not necessary.  Previously, debhelper could
 choose a "random" build system that would prefer building
 in a separate build directory on the basis that the build
 directory should be removed.  With this, change we only
 choose such a build system if there is a build directory
 to remove.
Checksums-Sha1:
 ddf845168510585021d9299e618f63b0b0d4eaab 1689 debhelper_11.2.1.dsc
 e1626da376d6e594e262cdbde3914a9c2e103777 456036 debhelper_11.2.1.tar.xz
 2d58c4211d38e4198f41638727657115664f8c46 4554 debhelper_11.2.1_source.buildinfo
Checksums-Sha256:
 2380aee11355a444da3e9f17bcefcd8c4063c65a7df6a6176742b3911310cec7 1689 
debhelper_11.2.1.dsc
 d969476a748f024381fa985813ac444eddd73995700109c3f304de711251010b 456036 
debhelper_11.2.1.tar.xz
 5a862896d758a8f26b8b2ac9b3ce83971ef4aef2da9c0743686385fdd24dc4d1 4554 
debhelper_11.2.1_source.buildinfo
Files:
 f958818ca0108a2b038f2d766d218e45 1689 devel optional debhelper_11.2.1.dsc
 34eb8e89f848e2bc39b9c4072938b036 456036 devel optional debhelper_11.2.1.tar.xz
 727b2c114df3d57747b7a2bc8be3233a 4554 devel 

Bug#895192: breezy FTBFS on i386: ERROR: breezy.tests.commands.test_commit.TestCommitWithBoundBranch.test_commit_mine_modified

[Adrian Bunk]

Source: breezy
Version: 3.0.0~bzr6940-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=breezy=i386=3.0.0~bzr6940-1=1523075761=0

...
breezy.plugins.email.tests.testemail.TestGetTo.test_url_unset   OK   40ms
commands.test_commit.TestCommitWithBoundBranch.test_commit_mine_modifiedERROR   
 0ms
lost connection during test 
'breezy.tests.commands.test_commit.TestCommitWithBoundBranch.test_commit_mine_modified'
==
ERROR: 
breezy.tests.commands.test_commit.TestCommitWithBoundBranch.test_commit_mine_modified
--
Traceback (most recent call last):
testtools.testresult.real._StringException: lost connection during test 
'breezy.tests.commands.test_commit.TestCommitWithBoundBranch.test_commit_mine_modified'
--
Ran 21812 tests in 640.751s

FAILED (errors=1, known_failure_count=49)
2298 tests skipped
debian/rules:21: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Processed: affects 895178

[Debian Bug Tracking System]

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

> affects 895178 src:gr-gsm
Bug #895178 [libosmocore-dev] libosmocore-dev: missing dependency on 
libtalloc-dev
Added indication that 895178 affects src:gr-gsm
> thanks
Stopping processing here.

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

Bug#895134: libwx-scintilla-perl: needs tighter dependency on Wx build?

[Niko Tyni]

On Sat, Apr 07, 2018 at 09:57:15PM +0100, Olly Betts wrote:
> On Sat, Apr 07, 2018 at 04:20:48PM +0300, Niko Tyni wrote:
> > So to do this properly it looks like we need something to make
> > sure the Perl Wx related packages are upgraded in sync. The
> > virtual package provided by libalien-wxwidgets-perl (currently
> > wxperl-gtk-3-0-4-uni-gcc-3-4) seems like a candidate, but I don't have
> > a ready recipe for injecting that.
> 
> I'd guess that makes sense, but I don't entirely understand how the
> libalien-wxwidgets-perl <-> libwx-perl connection works, or why we need
> a chain of binNMUs after each new upstream wxwidgets3.0 release.

AIUI Alien::wxWidgets provides information about a wxwidgets installation,
and libwx-perl uses that to offer machinery for building wxwidgets
related Perl packages (the Wx::build namespace.)  This build machinery
embeds the exact wxwidgets version/configuration from Alien::wxWidgets,
and breaks if those get out of sync. Hence the binNMU requirement. See
#757855 for the full story.

So the tight coupling is only for the Wx::build machinery. As we see in
this bug, no such extra provisions currently exist for keeping Wx based
binary Perl code (lke libwx-scintilla-perl) in sync with the Wx bindings
(libwx-perl).

> Presumably just copying libwx-perl's dependencies related to this
> across would work?

Yeah, if we accept the burden of rebuilding libwx-scintilla-perl and
libwx-glcanvas-perl too on every wxwidgets3.0 upstream release.

Alternatively I guess either libwx-perl or libalien-wxwidgets-perl
could Provide another less finely grained virtual package that
only encodes those parts that are expected to be incompatible at
run time, like wxperl-gtk3 or something like that. But that feels
overkill.

Another approach would be to consider this a one time glitch (how often
are we going to change toolkits anyway?), make libwx-perl Break older
(gtk2 based) libwx-scintilla-perl and libwx-glcanvas-perl versions,
and have those packages in turn depend on newer (gtk3 based) libwx-perl
versions. That should handle it afaics.

> > It seems probable that other packages (libwx-glcanvas-perl?) are
> > similarly affected, but I haven't looked into that.
> 
> I'd expect so.  There don't seem to be any others - at least I don't see
> any other -perl packages in the transition tracker:

I think those are the only two Wx perl packages we have with compiled
C extensions ("XS").

> I didn't try to handle preventing combinations of new libwx-perl with
> older libwx-scintilla-perl or libwx-glcanvas-perl though since there was
> no evidence that such handling was attempted for previous transitions.

Either they haven't broken partial upgrades earlier, or we just haven't
noticed that.

> > Setting severity to RC initially and marking as a transition blocker,
> > but others should feel free to adjust as appropriate.
> 
> It would certainly be good to address this somehow, but mostly because
> it will ease future transitions.  I'm not sure this really deserves to
> block this one as the libwx*-perl collection is now back in step across
> all release archs:
> 
> https://buildd.debian.org/status/package.php?p=libalien-wxwidgets-perl+libwx-perl+libwx-scintilla-perl+libwx-glcanvas-perl
> 
> Also blocking the transition really just means that the wx gtk2 packages
> can't be removed, yet doing that if anything improves the situation.
> 
> But that's mostly a theoretical point right now as the full transition
> is going to take months.

Yeah. FWIW I don't think the transition blocker metadata technically
affects testing migration or wx gtk2 binary removal. I intended it just
as a note for humans that these issues are linked. Naturally I'm fine
with removing it if it gets in the way for anybody.

As for whether this needs to be fixed or not: I think the minimum
requirement in the release criticality sense is that partial upgrades
between stable releases stay working.  I expect we'll be rebuilding
libwx-scintilla-perl and libwx-glcanvas-perl for at least Perl 5.28
before the buster release anyway, so that will probably take care of it
(because both libwx-perl and libwx-scintilla-perl will then be necessarily
upgraded in lockstep with Perl itself.)

Of course, keeping partial upgrades working for users of testing and
Debian derivatives is a worthy goal too.
-- 
Niko

Bug#894832: marked as done (CVE-2018-1002150)

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 10:34:59 +0200
with message-id <20180408083459.GA23589@eldamar.local>
and subject line Re: Bug#894832: CVE-2018-1002150
has caused the Debian Bug report #894832,
regarding CVE-2018-1002150
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.)


-- 
894832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894832
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: koji
Severity: grave
Tags: security

http://www.openwall.com/lists/oss-security/2018/04/04/1

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Control: forwarded -1 https://pagure.io/koji/issue/850

Hi

There is some further information on that issue in the upstrema bug at
https://pagure.io/koji/issue/850 and the
https://docs.pagure.org/koji/CVE-2018-1002150/ . Versions prior to
1.12.0 are not vulnerable because they do not have the dist-repo
feature.

Regards,
Salvatore--- End Message ---

Bug#894832: CVE-2018-1002150

[Salvatore Bonaccorso]

Control: forwarded -1 https://pagure.io/koji/issue/850

Hi

There is some further information on that issue in the upstrema bug at
https://pagure.io/koji/issue/850 and the
https://docs.pagure.org/koji/CVE-2018-1002150/ . Versions prior to
1.12.0 are not vulnerable because they do not have the dist-repo
feature.

Regards,
Salvatore

Processed: Re: Bug#894832: CVE-2018-1002150

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://pagure.io/koji/issue/850
Bug #894832 [src:koji] CVE-2018-1002150
Set Bug forwarded-to-address to 'https://pagure.io/koji/issue/850'.

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

Processed: Re: Bug#857970 closed by b...@debian.org (Barak A. Pearlmutter) (Bug#857970: fixed in mldemos 0.5.1+git.1.ee5d11f-2)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #857970 {Done: b...@debian.org (Barak A. Pearlmutter)} [src:mldemos] 
mldemos FTBFS on armel/armhf: error: 'glColor3f' was not declared in this scope
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions mldemos/0.5.1+git.1.ee5d11f-2.

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

Bug#857970: closed by b...@debian.org (Barak A. Pearlmutter) (Bug#857970: fixed in mldemos 0.5.1+git.1.ee5d11f-2)

[Adrian Bunk]

Control: reopen -1

On Thu, Apr 05, 2018 at 05:30:07PM +, Debian Bug Tracking System wrote:
>...
>  mldemos (0.5.1+git.1.ee5d11f-2) unstable; urgency=medium
>...
>* surely arm is updated to have glColor3f by now (closes: #857970)
>...

This has nothing to do with arm, the problem is:

> This is likely related to Qt in Debian using OpenGL ES instead of OpenGL
> on armel and armhf.


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: limit source to debhelper, tagging 895181, tagging 895174

[Debian Bug Tracking System]

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

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

> tags 895181 + pending
Bug #895181 [debhelper] debhelper: cmake-based projects broken
Added tag(s) pending.
> tags 895174 + pending
Bug #895174 [debhelper] glib2.0 FTBFS: fails to execute ninja
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: closing 893436

[Debian Bug Tracking System]

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

> close 893436 5.4.1-1
Bug #893436 [src:jupyter-notebook] jupyter-notebook: CVE-2018-8768
Marked as fixed in versions jupyter-notebook/5.4.1-1.
Bug #893436 [src:jupyter-notebook] jupyter-notebook: CVE-2018-8768
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#893436: closing 893436

[Salvatore Bonaccorso]

close 893436 5.4.1-1
thanks

Processed: bug 894577 is forwarded to https://issues.apache.org/jira/browse/THRIFT-3893

[Debian Bug Tracking System]

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

> forwarded 894577 https://issues.apache.org/jira/browse/THRIFT-3893
Bug #894577 [thrift-compiler] CVE-2016-5397
Set Bug forwarded-to-address to 
'https://issues.apache.org/jira/browse/THRIFT-3893'.
> thanks
Stopping processing here.

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

Bug#895181: debhelper: cmake-based projects broken

[Tobias Frost]

Package: debhelper
Version: 11.2
Severity: serious

Dear Maintainer,

since yesterday evening all cmake-based projects fails to compile.
Symptom is that it looks like that debhelper skips the build step.

Example buildlogs are for my expermential builds of cppds:
https://buildd.debian.org/status/package.php?p=cppdb=experimental

Locally, I can reproduce this behaviour also on my other packages
employing cmake (e.g dhewm3, rbfdoom3): it works with 11.1.6, it breaks
with 11.2.

--
tobi

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

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

Versions of packages debhelper depends on:
ii  autotools-dev20180224.1
ii  dh-autoreconf17
ii  dh-strip-nondeterminism  0.040-1
ii  dpkg 1.19.0.5
ii  dpkg-dev 1.19.0.5
ii  file 1:5.32-2
ii  libdpkg-perl 1.19.0.5
ii  man-db   2.8.3-1
ii  perl 5.26.1-5
ii  po-debconf   1.0.20

debhelper recommends no packages.

Versions of packages debhelper suggests:
pn  dh-make  
pn  dwz  

-- no debconf information

Bug#895180: rakudo: dependency on nqp is too strict

[Adrian Bunk]

Package: rakudo
Version: 2018.03-1
Severity: serious


Package: rakudo
Version: 2018.03-1
Depends: ..., nqp (= 2018.03+dfsg-1), ...

This would break even on a binNMU of nqp,
or like right now in unstable after a -2
bugfix release of nqp.

Please relax the nqp dependency to require only
the upstream version of nqp (similar to the
moarvm dependency).

Processed: Re: Bug#895174: glib2.0 FTBFS: fails to execute ninja

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 debhelper 11.2
Bug #895174 [src:glib2.0] glib2.0 FTBFS: fails to execute ninja
Bug reassigned from package 'src:glib2.0' to 'debhelper'.
No longer marked as found in versions glib2.0/2.56.0-6.
Ignoring request to alter fixed versions of bug #895174 to the same values 
previously set
Bug #895174 [debhelper] glib2.0 FTBFS: fails to execute ninja
Marked as found in versions debhelper/11.2.

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

Processed: tagging 894858

[Debian Bug Tracking System]

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

> tags 894858 - newcomer
Bug #894858 [gui-apt-key] gui-apt-key: Missing package relation with menu
Removed tag(s) newcomer.
> thanks
Stopping processing here.

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

Bug#895174: glib2.0 FTBFS: fails to execute ninja

[Sven Joachim]

Control: reassign -1 debhelper 11.2

Am 08.04.2018 um 08:44 schrieb Helmut Grohne:

> Source: glib2.0
> Version: 2.56.0-6
> Severity: serious
> User: helm...@debian.org
> Usertags: rebootstrap
>
> glib2.0 FTBFS during dh_auto_clean. Including the full build log:
>
> | dpkg-buildpackage: info: source package glib2.0
> | dpkg-buildpackage: info: source version 2.56.0-6
> | dpkg-buildpackage: info: source distribution unstable
> | dpkg-buildpackage: info: source changed by Simon McVittie 
> |  dpkg-source --before-build glib2.0-2.56.0
> | dpkg-buildpackage: info: host architecture amd64
> |  debian/rules clean
> | dh clean --with gnome,python3
> |dh_auto_clean
> | LC_ALL=C.UTF-8 ninja clean
> | Can't exec "ninja": No such file or directory at 
> /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 356.
> | dh_auto_clean: LC_ALL=C.UTF-8 ninja clean failed to execute: No child 
> processes
> | dh_auto_clean: LC_ALL=C.UTF-8 ninja clean returned exit code 10
> | make: *** [debian/rules:24: clean] Error 2
> | dpkg-buildpackage: error: debian/rules clean subprocess returned exit 
> status 2
>
> I guess this is connected to debhelper 11.2 (as the failure surfaced
> close to the upload). Since I'm unsure whether this is a debhelper or
> glib2.0 problem, I'm filing it with glib2.0 and trust that you know how
> to reassign.

This has been caused by the build system rewrite in debhelper 11.2, I
bisected it to commit d3bc4c31453a (Rewrite build system to support a
"target build system").

Current glib2.0 source can be built with either meson or autotools, and
debian/rules should probably specify which one to use.  Feel free
reassign a clone of this bug back to glib2.0 for that, but "debian/rules
clean" even fails when meson is installed, which looks like a serious
problem in debhelper.

,
| $ debian/rules clean
| dh clean --with gnome,python3
|dh_auto_clean
| LC_ALL=C.UTF-8 ninja clean
| ninja: error: loading 'build.ninja': No such file or directory
`

Cheers,
   Sven

Bug#887666: jh_linkjars: Invalid option: N

[Emmanuel Bourg]

Le 07/04/2018 à 19:55, Niels Thykier a écrit :

> I have written some patches to rewrite most of the javatools helpers
> into perl using Debhelper's Dh_Lib[1].  This would fix this problem and
> avoid future instances of it.

Thank you Niels! Feel free to commit the changes directly into the Git
repository (still on Alioth).

Emmanuel Bourg

Bug#895178: libosmocore-dev: missing dependency on libtalloc-dev

[Adrian Bunk]

Package: libosmocore-dev
Version: 0.10.2-5
Severity: serious
Control: affects -1 src:libosmo-netif src:libosmo-abis src:openggsn

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/libosmo-netif.html

...
make[5]: Entering directory '/build/1st/libosmo-netif-0.0.6/src/channel/abis'
/bin/bash ../../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../..  -I../../../include -I../../.. -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-Wall -I/usr/include/ -I/usr/include/   -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -c -o ipa_stream_server.lo ipa_stream_server.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../include 
-I../../.. -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wall -I/usr/include/ 
-I/usr/include/ -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -c ipa_stream_server.c  -fPIC -DPIC -o 
.libs/ipa_stream_server.o
In file included from ipa_stream_server.c:8:0:
/usr/include/osmocom/core/talloc.h:5:10: fatal error: talloc.h: No such file or 
directory
 #include 
  ^~
compilation terminated.
Makefile:392: recipe for target 'ipa_stream_server.lo' failed
make[5]: *** [ipa_stream_server.lo] Error 1

Processed: libosmocore-dev: missing dependency on libtalloc-dev

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:libosmo-netif src:libosmo-abis src:openggsn
Bug #895178 [libosmocore-dev] libosmocore-dev: missing dependency on 
libtalloc-dev
Added indication that 895178 affects src:libosmo-netif, src:libosmo-abis, and 
src:openggsn

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

Bug#895174: glib2.0 FTBFS: fails to execute ninja

[Helmut Grohne]

Source: glib2.0
Version: 2.56.0-6
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

glib2.0 FTBFS during dh_auto_clean. Including the full build log:

| dpkg-buildpackage: info: source package glib2.0
| dpkg-buildpackage: info: source version 2.56.0-6
| dpkg-buildpackage: info: source distribution unstable
| dpkg-buildpackage: info: source changed by Simon McVittie 
|  dpkg-source --before-build glib2.0-2.56.0
| dpkg-buildpackage: info: host architecture amd64
|  debian/rules clean
| dh clean --with gnome,python3
|dh_auto_clean
|   LC_ALL=C.UTF-8 ninja clean
| Can't exec "ninja": No such file or directory at 
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 356.
| dh_auto_clean: LC_ALL=C.UTF-8 ninja clean failed to execute: No child 
processes
| dh_auto_clean: LC_ALL=C.UTF-8 ninja clean returned exit code 10
| make: *** [debian/rules:24: clean] Error 2
| dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2

I guess this is connected to debhelper 11.2 (as the failure surfaced
close to the upload). Since I'm unsure whether this is a debhelper or
glib2.0 problem, I'm filing it with glib2.0 and trust that you know how
to reassign.

Helmut

Bug#894526: Taking over scikit-learn into Debian Science team maintenance

[Andreas Tille]

Hi Yaroslav and Michael,

as I did in the past with other scientific packages I would like to take
over scikit-learn into Debian Science team maintenance to fix bug
#894526.  As I understood you in those cases you are OK with this as
long as backportability is given.

Please let me know until tomorrow if you do not like it.

Kind regards

   Andreas.

-- 
http://fam-tille.de