Bug#898969: dnssec-trigger: fails with OpenSSL 1.1.1 due to too-small key

[Diane Trout]

On Mon, 2018-09-17 at 09:55 +0800, Paul Wise wrote:
> Package: dnssec-trigger
> Version: 0.15+repack-1
> Followup-For: Bug #898969
> Control: retitle -1 dnssec-trigger: fails with OpenSSL 1.1.1 due to
> too-small key and unknown ca
> Control: severity -1 serious 
> 
> If I delete the existing keys and recreate them with dnssec-trigger-
> control-setup (since dnssec-triggerd-keygen is broken) and restart
> dnssec-triggerd, I get an error repeating over and over again:

Could you go into a bit more detail about how dnssec-triggerd-keygen
isn't working for you?

Because currently the easiest answer I can think of for this is to
delete the keys and restart the daemons on upgrade.

Also I'm a bit surprised the panel is working. I guess this means
you're using something that is not gnome.


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

Processed: severity of 910056 is serious

[Debian Bug Tracking System]

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

> severity 910056 serious
Bug #910056 [src:twisted] twisted: Missing version constraint on python-attr 
dependencies
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#891098: NMU sugegstion

[Sergei Golovan]

Hi Onur,

I've prepared a NMU with the Stefano's patch. If you don't mind, I'd
like to upload it. The diff is attached.

Cheers!
-- 
Sergei Golovan


gumbo-parser_0.10.1+dfsg-2.3.debdiff
Description: Binary data

Bug#906609: marked as done (gnucash: FTBFS on mips/sid: Segmentation fault)

[Debian Bug Tracking System]

Your message dated Tue, 02 Oct 2018 04:50:40 +
with message-id 
and subject line Bug#906609: fixed in gnucash 1:3.3-1
has caused the Debian Bug report #906609,
regarding gnucash: FTBFS on mips/sid: Segmentation fault
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.)


-- 
906609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnucash
Version: 1:3.2-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Tags: fbtfs

Dear Maintainer,

gnucash fails to build from source in sid/mips:

  […]

[ 45%] Generating 
../../lib/mips-linux-gnu/gnucash/gnucash/scm/ccache/2.2/gnucash/unittest-support.go
cd /<>/.build/common/test-core && /usr/bin/cmake -E env 
LD_LIBRARY_PATH=/<>/.build//lib/mips-linux-gnu/gnucash:/<>/.build//lib/mips-linux-gnu/gnucash/gnucash:
 GNC_UNINSTALLED=YES GNC_BUILDDIR=/<>/.build 
GUILE_LOAD_PATH=/<>/common/test-core 
GUILE_LOAD_COMPILED_PATH=/<>/.build//lib/mips-linux-gnu/gnucash/gnucash/scm/ccache/2.2
 
GNC_MODULE_PATH=/<>/.build//lib/mips-linux-gnu/gnucash:/<>/.build//lib/mips-linux-gnu/gnucash/gnucash:
 /usr/bin/guile -e '(@@ (guild) main)' -s /usr/bin/guild compile -o 
/<>/.build//lib/mips-linux-gnu/gnucash/gnucash/scm/ccache/2.2/gnucash/unittest-support.go
 /<>/common/test-core/unittest-support.scm
Segmentation fault
make[3]: *** [common/test-core/CMakeFiles/scm-test-core.dir/build.make:65: 
lib/mips-linux-gnu/gnucash/gnucash/scm/ccache/2.2/gnucash/unittest-support.go] 
Error 1
  […]

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

  
https://buildd.debian.org/status/fetch.php?pkg=gnucash=mips=1%3A3.2-1=1530801120=1

This also appears to affect x390x:

  
https://buildd.debian.org/status/fetch.php?pkg=gnucash=s390x=1%3A3.2-1=1530791265=0


Regards,

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


gnucash.1:3.2-1.sid.mips.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: gnucash
Source-Version: 1:3.3-1

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated gnucash package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 02 Oct 2018 11:37:03 +1000
Source: gnucash
Binary: gnucash gnucash-common python3-gnucash
Architecture: source all amd64
Version: 1:3.3-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 gnucash- personal and small-business financial-accounting software
 gnucash-common - common files for the financial-accounting software Gnucash
 python3-gnucash - Gnucash interface for Python
Closes: 906609 909834
Changes:
 gnucash (1:3.3-1) unstable; urgency=medium
 .
   [ Dmitry Smirnov ]
   * New upstream release.
 + Fixed FTBFS with glib 2.58 (Closes: #909834).
 .
   [ Bernhard Übelacker ]
   * Fix FTBFS on mips* (Closes: #906609).
 .
   [ Ondřej Nový ]
   * d/watch: Use https protocol
Checksums-Sha1:
 c5ecd16cab5ce3772dc4446c7e4fd953f76a 2398 gnucash_3.3-1.dsc
 c03b62d1cd09e2350098b15df18d1d9266fad68e 9293968 gnucash_3.3.orig.tar.xz
 60fffcdd8f3c2eb1b604477fc690d4646638ca54 36228 gnucash_3.3-1.debian.tar.xz
 ca304bd2ffdd49b2b0abc26941280d2b3ff5233b 4996892 gnucash-common_3.3-1_all.deb
 e79edfea37ef6a19debc09c2b5aef4ed986336eb 20532668 
gnucash-dbgsym_3.3-1_amd64.deb
 9ebcc6a1335630dfb86de81d9988fc70a2e8b4f3 18959 gnucash_3.3-1_amd64.buildinfo
 f56b8748232abe83ee1aef558be1ade3960ebdc5 4463544 gnucash_3.3-1_amd64.deb
 0a6cd1287ecd36a8593736d9005c446897dc7597 763880 
python3-gnucash-dbgsym_3.3-1_amd64.deb
 2873e040b1eb6a7c94d4a83af51cbc42929da742 301064 python3-gnucash_3.3-1_amd64.deb
Checksums-Sha256:
 b5cedbfac8c0dd3ad6664beeb7977db4889e6fc606ab7eb9d50b8a09cf8f1e18 2398 
gnucash_3.3-1.dsc
 751ebd08bb8b2d6172d8bba93fad434551280415eb00b2797e58e5c00be1c89f 

Bug#909834: marked as done (gnucash FTBFS with glib 2.58)

[Debian Bug Tracking System]

Your message dated Tue, 02 Oct 2018 04:50:40 +
with message-id 
and subject line Bug#909834: fixed in gnucash 1:3.3-1
has caused the Debian Bug report #909834,
regarding gnucash FTBFS with glib 2.58
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.)


-- 
909834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnucash
Version: 1:3.2-1
Severity: serious
Tags: ftbfs

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

...
/build/1st/gnucash-3.2/libgnucash/engine/Account.cpp: In function 'void 
gnc_account_class_init(AccountClass*)':
/build/1st/gnucash-3.2/libgnucash/engine/Account.cpp:575:59: error: 'void 
g_type_class_add_private(gpointer, gsize)' is deprecated 
[-Werror=deprecated-declarations]
 g_type_class_add_private(klass, sizeof(AccountPrivate));
   ^
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /build/1st/gnucash-3.2/libgnucash/engine/guid.h:34,
 from /build/1st/gnucash-3.2/libgnucash/engine/qofid.h:82,
 from /build/1st/gnucash-3.2/libgnucash/engine/qof.h:72,
 from /build/1st/gnucash-3.2/libgnucash/engine/Account.h:47,
 from /build/1st/gnucash-3.2/libgnucash/engine/AccountP.h:42,
 from /build/1st/gnucash-3.2/libgnucash/engine/Account.cpp:34:
/usr/include/glib-2.0/gobject/gtype.h:1303:10: note: declared here
 void g_type_class_add_private   (gpointerg_class,
  ^~~~
--- End Message ---
--- Begin Message ---
Source: gnucash
Source-Version: 1:3.3-1

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated gnucash package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 02 Oct 2018 11:37:03 +1000
Source: gnucash
Binary: gnucash gnucash-common python3-gnucash
Architecture: source all amd64
Version: 1:3.3-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 gnucash- personal and small-business financial-accounting software
 gnucash-common - common files for the financial-accounting software Gnucash
 python3-gnucash - Gnucash interface for Python
Closes: 906609 909834
Changes:
 gnucash (1:3.3-1) unstable; urgency=medium
 .
   [ Dmitry Smirnov ]
   * New upstream release.
 + Fixed FTBFS with glib 2.58 (Closes: #909834).
 .
   [ Bernhard Übelacker ]
   * Fix FTBFS on mips* (Closes: #906609).
 .
   [ Ondřej Nový ]
   * d/watch: Use https protocol
Checksums-Sha1:
 c5ecd16cab5ce3772dc4446c7e4fd953f76a 2398 gnucash_3.3-1.dsc
 c03b62d1cd09e2350098b15df18d1d9266fad68e 9293968 gnucash_3.3.orig.tar.xz
 60fffcdd8f3c2eb1b604477fc690d4646638ca54 36228 gnucash_3.3-1.debian.tar.xz
 ca304bd2ffdd49b2b0abc26941280d2b3ff5233b 4996892 gnucash-common_3.3-1_all.deb
 e79edfea37ef6a19debc09c2b5aef4ed986336eb 20532668 
gnucash-dbgsym_3.3-1_amd64.deb
 9ebcc6a1335630dfb86de81d9988fc70a2e8b4f3 18959 gnucash_3.3-1_amd64.buildinfo
 f56b8748232abe83ee1aef558be1ade3960ebdc5 4463544 gnucash_3.3-1_amd64.deb
 0a6cd1287ecd36a8593736d9005c446897dc7597 763880 
python3-gnucash-dbgsym_3.3-1_amd64.deb
 2873e040b1eb6a7c94d4a83af51cbc42929da742 301064 python3-gnucash_3.3-1_amd64.deb
Checksums-Sha256:
 b5cedbfac8c0dd3ad6664beeb7977db4889e6fc606ab7eb9d50b8a09cf8f1e18 2398 
gnucash_3.3-1.dsc
 751ebd08bb8b2d6172d8bba93fad434551280415eb00b2797e58e5c00be1c89f 9293968 
gnucash_3.3.orig.tar.xz
 396bd4fbd71c272b0d5f87bae9499c4a8e17421a65d203525787715b16dd3455 36228 
gnucash_3.3-1.debian.tar.xz
 59e70bb2e4e7dcfe9881ba9db817ea6828869a9487a665d07b33cec334e053db 4996892 
gnucash-common_3.3-1_all.deb
 79c5b0e40c2644bb62c5ee8427f66d0c460316028f8804bd924c3ce71efcb2bd 20532668 

Bug#898969: dnssec-trigger: fails with OpenSSL in experimental due to too-small key

[Diane Trout]

On Mon, 2018-10-01 at 20:23 +0200, Lee Garrett wrote:
> Hi,
> 
> Any update on this bug? dnssec-trigger will be autoremoved due to
> this bug
> tomorrow. I'd like to see it in buster, though.



Ooops I forgot, Also does this bug impact unbound? I tried checking the
unbound maintainer scripts and they're not doing anything to handle
this case

What's 
sudo -s openssl x509 \
  -in /etc/dnssec-trigger/dnssec_trigger_control.pem  -text | \
  grep 'Public-Key'

Look like on an effected system?

On mine is 3072, and I don't seem to be impacted.

I'm guessing I can use that to determine if I need to regenerate the
key

The other option is to just delete the key and regenerate it on the
specific version upgrade.

What do others think
Diane


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

Bug#906609: gnucash: FTBFS on mips/sid: Segmentation fault

[Dmitry Smirnov]

On Tuesday, 2 October 2018 12:22:18 AM AEST Chris Lamb wrote:
> Gentle ping on this? gnucash is not currently in testing (!).

Thanks for reminder. It's the lack of time, not lack of attention is the 
problem...

I've taken care of that problem and I'm planing to upload the updated package 
in about an hour or so...

-- 
Regards,
 Dmitry Smirnov.

---

No person, no idea, and no religion deserves to be illegal to insult,
not even the Church of Emacs.
-- Richard Stallman


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

Bug#906609: gnucash: FTBFS on mips/sid: Segmentation fault

[Dmitry Smirnov]

On Tuesday, 4 September 2018 3:08:03 AM AEST Bernhard Übelacker wrote:
> This macro WORDS_BIGENDIAN was maybe set by autotools in the past.
> But after the switch to cmake it looks like it has to
> to given to cmake at "configure" time.
> 
> Attached patch tries to append based on DEB_TARGET_ARCH_ENDIAN
> a cmake parameter to have that macro defined.

Thank you very much for your help and excellent analysis. 


> Unfortunately my mips VM is terrible slow and a mips qemu-user chroot
> is not reliable enough. Therefore I could not finish (yet) any build with
> this patch included.

Despite trying for many hours I could not make a bootable mips qemu image at 
all...

-- 
Best wishes,
 Dmitry Smirnov.

---

Criticism may not be agreeable, but it is necessary. It fulfils the same
function as pain in the human body. It calls attention to an unhealthy
state of things.
-- Winston Churchill


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

Processed: Re: Bug#910009: exim4-config: upgrade fails when trying to execute conffile difference visualizer

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #910009 [dpkg] dpkg execs $PAGER with execvp instead of sh -c, yielding 
upgrade failure
Severity set to 'serious' from 'grave'

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

Bug#910009: exim4-config: upgrade fails when trying to execute conffile difference visualizer

[Guillem Jover]

Control: severity -1 serious

Hi!

On Mon, 2018-10-01 at 14:47:09 +0200, Vincent Lefevre wrote:
> Control: reassign -1 dpkg 1.19.1
> Control: retitle -1 dpkg execs $PAGER with execvp instead of sh -c, yielding 
> upgrade failure

> As a summary, when a pager needs to be invoked (e.g. for the
> conffile difference visualizer), one gets an upgrade failure
> if $PAGER contains the program name + options, as specified
> by POSIX.

Nice catch! Thanks for the analysis.

> On 2018-10-01 14:12:20 +0200, Vincent Lefevre wrote:
> > On 2018-10-01 14:08:17 +0200, Vincent Lefevre wrote:
> > > A possible bug might be that $PAGER is run as a program name,
> > > instead of something like system(), which allows options.
> > 
> > Hmm... I can see in /usr/share/doc/dpkg/changelog.Debian.gz that
> > there have been pager-related changes in dpkg 1.19.1 (26 Sep 2018).
> > The bug might actually be there.
> 
> Indeed, after a quick look at the code (pager_spawn in lib/dpkg/pager.c
> and lib/dpkg/command.c code), this seems to be the case.

I've queued a patch fixing this, which I'll be uploding around
Wednesday with dpkg 1.19.2. Although this will temporarily get in
the way of making the pager presence detection harder, but I'll
improve that later on.

Thanks,
Guillem

Bug#910051: uwgi: fails to build with shellcheck 0.5.0

[Jeremy Bicha]

Source: uwsgi
Version: 2.0.17.1-7
Severity: serious
Tags: ftbfs

uwsgi fails to build from source with shellcheck 0.5.0. That version
hasn't built in Debian yet; I believe it's caught up in the ongoing
haskell transition.

You can see the build failure at
https://launchpad.net/ubuntu/+source/uwsgi/2.0.17.1-7/+build/15501460

A friend is working on a patch

Thanks,
Jeremy Bicha

Bug#908681: marked as done (libsane1: pointless package rename)

[Debian Bug Tracking System]

Your message dated Mon, 01 Oct 2018 23:48:42 +
with message-id 
and subject line Bug#908681: fixed in sane-backends 1.0.27-2
has caused the Debian Bug report #908681,
regarding libsane1: pointless package rename
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.)


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

Hi,

libsane was renamed to libsane1 for apparently no good reason.  Renames
for library packages should be tied to ABI breakage (and associated
SONAME changes).

Either there was ABI breakage and the SONAME should be bumped (and
Provides: libsane would be wrong), or there wasn't and the package name
change ought to be reverted.

I don't know which it is, and when I asked I didn't get a clear answer,
so I'll ask again here.

Cheers,
Julien
--- End Message ---
--- Begin Message ---
Source: sane-backends
Source-Version: 1.0.27-2

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

Debian distribution maintenance software
pp.
Jörg Frings-Fürst  (supplier of updated sane-backends package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 27 Sep 2018 08:30:18 +0200
Source: sane-backends
Binary: sane-utils libsane-common libsane1 libsane-dev
Architecture: source
Version: 1.0.27-2
Distribution: sid
Urgency: medium
Maintainer: John Paul Adrian Glaubitz 
Changed-By: Jörg Frings-Fürst 
Description:
 libsane-common - API library for scanners -- documentation and support files
 libsane-dev - API development library for scanners [development files]
 libsane1   - API library for scanners
 sane-utils - API library for scanners -- utilities
Closes: 908681
Changes:
 sane-backends (1.0.27-2) unstable; urgency=medium
 .
   * debian/control:
 - Remove obsolete section about sane-backends-extras.
 - Revert change from Breaks to Conflicts for binary package libsane1
   (Closes: #908681).
Checksums-Sha1:
 a17d8ddb594730365810bbb839f5bb943c7d0e6e 2348 sane-backends_1.0.27-2.dsc
 623abe8ab0ff6adc1fd22c3e4d65d52c7b1fa9eb 113448 
sane-backends_1.0.27-2.debian.tar.xz
 cf8b5715d98ca213289eaa47b2475594bba56757 9178 
sane-backends_1.0.27-2_amd64.buildinfo
Checksums-Sha256:
 1d56c7f3415ba2ad2d826d21a57947738a6de8a34926100268a04b58874c03a1 2348 
sane-backends_1.0.27-2.dsc
 4e290ba27e31315d503b8b64ab0e482266af13fb50e36e63d2a0dd2575dfbf89 113448 
sane-backends_1.0.27-2.debian.tar.xz
 1f7de2110f90891b637151bfdd21067734600ec2e675ef6091b1f6b42cc0626c 9178 
sane-backends_1.0.27-2_amd64.buildinfo
Files:
 c6131d897373e549690ad6f492759f3d 2348 graphics optional 
sane-backends_1.0.27-2.dsc
 6593c3fd56cd7bd2f7a4e35342913fac 113448 graphics optional 
sane-backends_1.0.27-2.debian.tar.xz
 ace23f21f9690a72bc4b581acc1121e1 9178 graphics optional 
sane-backends_1.0.27-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAluyqiEACgkQdCY7N/W1
+RN5yA//Wv+8TDtyy5A4Ve2n1BkGAR3lglbDgQGVoQofpjW+JD+4eyGzGAqLFCll
1pSs/SQGEZ7tMDtHJTZBhwYP71yQKUHo/49j/so2bpdUhT5NIFtTzNW+9yaZ6C0+
iOMd+8kpQvxIordS9J93LQ+e8OxbkuenrOTFZx/3wHiIfnH0e8Z01o4LoChZ5L5v
VYJm9mP3uIySpuKE/mtu2q6QdUADHYWvw6VEEGUjjneOHuC9OsyjEJ5TDKsGMkKT
yJ2nEZwbrZV+BnQ9Cq2Rejj1Dw5o1tvxIKRq3U9NDyZZ63psW/IY4RC/baXTSBas
YDZwc6k9tKJ9buseHcsndFoeGFPblL9ch+Xb1sKUBp2Krjj6S9Z1LN0l7cAZZv4t
1jk9baDfdN5nAq12OYW5YRrEveksUpCKwrkMDP2oWW66UZC8IWLZ/cbvJEU4O+/8
D6+ZJVmKJDXRAS/UL23exalC5QtpnrnNpg4OMvGkZIuni90VCPYf4Hlh8LokneKH
plnHAAlQClcVQXHuP7Bvyy8T829vZHfAUqx3nYN3qkIjDvuDiiKB0eA/X6Or3UFB
QkMI1iPW/Wn9u4vKqga6QtUB86qY7HwGfccMgibwWs+TbpubbtmJdZXJl9Zf9ggp
b+TDSfUuojy12nyA4wnxE1bbzJvRNnFq0WC3B+ySsQQ9S4279Fs=
=HobL
-END PGP SIGNATURE End Message ---

Bug#891096: marked as done (planet-venus: python-beautifulsoup is replaced with python-bs4)

[Debian Bug Tracking System]

Your message dated Tue, 02 Oct 2018 00:57:59 +0200
with message-id <153843467945.1793.1721246443055878...@auryn.jones.dk>
and subject line Re: planet-venus: python-beautifulsoup is replaced with 
python-bs4
has caused the Debian Bug report #891096,
regarding planet-venus: python-beautifulsoup is replaced with python-bs4
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.)


-- 
891096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: planet-venus
Version: 0~git9de2109-4
Severity: important
Control: block 891087 by -1

beautifulsoup version 4 was replaced as a new package, bs4, which has
been in Debian for over 5 years now. beautfiulsoup (3.x) hasn't seen any
maintenance since then. It's high time to remove it from the archive.

Most code written against Beautiful Soup 3 will work against Beautiful
Soup 4 with one simple change. All you should have to do is change the
package name from BeautifulSoup to bs4, and depend on python-bs4 instead
of python-beautifulsoup.

There is some documentation on the migration here:
https://www.crummy.com/software/BeautifulSoup/bs4/doc/#porting-code-to-bs4

Thanks,

SR
--- End Message ---
--- Begin Message ---
planet-venus only reference SeautifulSoup in a vendor dir which is fully 
patched out and therefore irrelevant.

Therefore closing this as a non-bug.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


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

Bug#910015: message wrong

[積丹尼 Dan Jacobson]

It turns out this message is totally wrong.

It should just say "check your device for a permissions confirmation
screen."

(And no the user is not always online to be able to access web explanations.)

Bug#909851: meson fails: AttributeError: 'list' object has no attribute 'absolute_path'

[Jussi Pakkanen]

On Sat, Sep 29, 2018 at 6:36 PM Adrian Bunk  wrote:

> Package: meson
> Version: 0.48.0-1
> Severity: serious
> Control: affects -1 src:gnome-initial-setup src:file-roller

The fix for this is pending review upstream and will be in the next
point release:

https://github.com/mesonbuild/meson/pull/4308

Bug#909327: marked as done (unattended-upgrades FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Mon, 01 Oct 2018 21:44:18 +
with message-id 
and subject line Bug#909327: fixed in unattended-upgrades 1.6
has caused the Debian Bug report #909327,
regarding unattended-upgrades FTBFS: test failures
to be marked as done.

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

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


-- 
909327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unattended-upgrades
Version: 1.5
Severity: serious
Tags: ftbfs

Some recent change in unstable makes unattended-upgrades FTBFS:

https://tests.reproducible-builds.org/debian/history/unattended-upgrades.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/unattended-upgrades.html

...
==
FAIL: test_remove_unused_dependencies (__main__.TestRemoveUnused)
--
Traceback (most recent call last):
  File "./test_remove_unused.py", line 111, in test_remove_unused_dependencies
"Can not find '%s' in '%s'" % (needle, haystack))
AssertionError: False is not true : Can not find 'Packages that were 
successfully auto-removed: old-unused-dependency test-package-dependency' in 
'2018-09-20 20:38:43,234 INFO Initial blacklisted packages: 
2018-09-20 20:38:43,235 INFO Initial whitelisted packages: 
2018-09-20 20:38:43,235 INFO Starting unattended upgrades script
2018-09-20 20:38:43,236 INFO Allowed origins are: o=Ubuntu,a=lucid-security
2018-09-20 20:38:43,464 DEBUG APT::VersionedKernelPackages is not set
2018-09-20 20:38:43,466 DEBUG Checking: test-package ([])
2018-09-20 20:38:43,470 DEBUG pkgs that look like they should be upgraded: 
test-package
2018-09-20 20:38:43,478 DEBUG fetch.run() result: 0
2018-09-20 20:38:43,479 DEBUG http://archive.ubuntu.com/ubuntu/test-package_2.0_all.deb' ID:0 
ErrorText: ''>
2018-09-20 20:38:43,480 DEBUG 
check_conffile_prompt(/build/1st/unattended-upgrades-1.5/test/root.unused-deps/var/cache/apt/archives/test-package_2.0_all.deb)
2018-09-20 20:38:43,481 DEBUG found pkg: test-package
2018-09-20 20:38:43,481 DEBUG blacklist: []
2018-09-20 20:38:43,481 DEBUG whitelist: []
2018-09-20 20:38:43,481 INFO Packages that will be upgraded: test-package
2018-09-20 20:38:43,482 INFO Writing dpkg log to 
./root.unused-deps/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
2018-09-20 20:38:43,490 DEBUG applying set ['test-package']
2018-09-20 20:38:43,951 DEBUG left to upgrade set()
2018-09-20 20:38:43,951 INFO All upgrades installed
2018-09-20 20:38:43,960 DEBUG InstCount=1 DelCount=0 BrokenCount=0
2018-09-20 20:38:43,968 DEBUG Extracting content from 
./root.unused-deps/var/log/unattended-upgrades/unattended-upgrades-dpkg.log 
since 2018-09-20 20:38:43
'

==
FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
--
Traceback (most recent call last):
  File "./test_remove_unused.py", line 138, in 
test_remove_unused_dependencies_new_unused_only
"Can not find '%s' in '%s'" % (needle, haystack))
AssertionError: False is not true : Can not find 'Packages that were 
successfully auto-removed: test-package-dependency' in '2018-09-20 20:38:43,984 
INFO Initial blacklisted packages: 
2018-09-20 20:38:43,985 INFO Initial whitelisted packages: 
2018-09-20 20:38:43,985 INFO Starting unattended upgrades script
2018-09-20 20:38:43,985 INFO Allowed origins are: o=Ubuntu,a=lucid-security
2018-09-20 20:38:44,278 DEBUG Using (^linux-image|^.*-modules|^linux-headers) 
regexp to find kernel packages
2018-09-20 20:38:44,284 DEBUG Using 
(^linux-image.*4.9.0-8-amd64|4.9.0-8-amd64.*-modules|^linux-headers.*4.9.0-8-amd64)
 regexp to find running kernel packages
2018-09-20 20:38:44,286 DEBUG Checking: test-package ([])
2018-09-20 20:38:44,288 DEBUG pkgs that look like they should be upgraded: 
test-package
2018-09-20 20:38:44,298 DEBUG fetch.run() result: 0
2018-09-20 20:38:44,299 DEBUG http://archive.ubuntu.com/ubuntu/test-package_2.0_all.deb' ID:0 
ErrorText: ''>
2018-09-20 20:38:44,299 DEBUG 
check_conffile_prompt(/build/1st/unattended-upgrades-1.5/test/root.unused-deps/var/cache/apt/archives/test-package_2.0_all.deb)
2018-09-20 20:38:44,299 DEBUG found pkg: test-package
2018-09-20 20:38:44,300 DEBUG blacklist: []
2018-09-20 20:38:44,300 DEBUG whitelist: []
2018-09-20 20:38:44,301 INFO Packages that will be upgraded: test-package
2018-09-20 20:38:44,301 INFO Writing dpkg log to 

Bug#909975: marked as done (remove unneeded dependency on backports.ssl-match-hostname)

[Debian Bug Tracking System]

Your message dated Mon, 01 Oct 2018 21:43:34 +
with message-id 
and subject line Bug#909975: fixed in sagemath 8.3-2
has caused the Debian Bug report #909975,
regarding remove unneeded dependency on backports.ssl-match-hostname
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.)


-- 
909975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:backports.ssl-match-hostname
Version: 3.5.0.1-1
Severity: important
Tags: sid buster

The python3 and python2 versions already have that fix (and had it in stretch
too).  This package should  be removed for the buster release.
--- End Message ---
--- Begin Message ---
Source: sagemath
Source-Version: 8.3-2

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

Debian distribution maintenance software
pp.
Tobias Hansen  (supplier of updated sagemath package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 01 Oct 2018 20:16:30 +0200
Source: sagemath
Binary: sagemath sagemath-common sagemath-jupyter sagemath-doc-ca 
sagemath-doc-de sagemath-doc-en sagemath-doc-es sagemath-doc-fr sagemath-doc-hu 
sagemath-doc-it sagemath-doc-ja sagemath-doc-pt sagemath-doc-ru sagemath-doc-tr
Architecture: source
Version: 8.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Tobias Hansen 
Description:
 sagemath   - Open Source Mathematical Software
 sagemath-common - Open Source Mathematical Software - architecture-independent 
file
 sagemath-doc-ca - Open Source Mathematical Software - documentation (Catalan; 
Valen
 sagemath-doc-de - Open Source Mathematical Software - documentation (German)
 sagemath-doc-en - Open Source Mathematical Software - documentation (English)
 sagemath-doc-es - Open Source Mathematical Software - documentation (Spanish; 
Casti
 sagemath-doc-fr - Open Source Mathematical Software - documentation (French)
 sagemath-doc-hu - Open Source Mathematical Software - documentation (Hungarian)
 sagemath-doc-it - Open Source Mathematical Software - documentation (Italian)
 sagemath-doc-ja - Open Source Mathematical Software - documentation (Japanese)
 sagemath-doc-pt - Open Source Mathematical Software - documentation 
(Portuguese)
 sagemath-doc-ru - Open Source Mathematical Software - documentation (Russian)
 sagemath-doc-tr - Open Source Mathematical Software - documentation (Turkish)
 sagemath-jupyter - Open Source Mathematical Software - Jupyter kernel
Closes: 909975
Changes:
 sagemath (8.3-2) unstable; urgency=medium
 .
   * Remove dependency on backports.ssl-match-hostname. (Closes: #909975)
   * Remove patches:
 - d1-test-optional.patch
Checksums-Sha1:
 fb33c7b0414ed6baa2d1de0c4905868fd2c76aa5 6855 sagemath_8.3-2.dsc
 5eeb8de2243127639cb29856e2c0e8bb75700aac 91768 sagemath_8.3-2.debian.tar.xz
 d15fd54b6cde6dd892de82bcbb116d3db35c5157 29441 sagemath_8.3-2_source.buildinfo
Checksums-Sha256:
 11a87644f6b2fa1c766df9f6efb62a92f1f14d61730cd85f6b4e602c49c20b1f 6855 
sagemath_8.3-2.dsc
 42aa7ee3beaf8193128ed4f6a29249dfe58d9b5129e3fb8c8dd8fd2aaceb2947 91768 
sagemath_8.3-2.debian.tar.xz
 06733e97fe6bf1c22ed66afa241f26607919ec8c19b2393d502ee1d7633f0ed1 29441 
sagemath_8.3-2_source.buildinfo
Files:
 941adadc8f237768a358df5d703878e5 6855 math optional sagemath_8.3-2.dsc
 85e73f1ff98129eb604d17dea1e6e70e 91768 math optional 
sagemath_8.3-2.debian.tar.xz
 574e73a2a2a070c9c8563ede052b5939 29441 math optional 
sagemath_8.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoH46ol3M2u2mYo0kjIIWnY7OzSoFAluydsYACgkQjIIWnY7O
zSpYRA//Rim/ECiCB+dxRY37xrJsfy/vrb/ctex3AyVU9efWBXeF4AjksZJzVm1i
xOoIHxjVDJ1T0ogaTYr1IgwTiIoS5LFzEOFuuD57raCBwAQzEApQrkBtYa7E64z9
RH//tFXVMCciwZ9UtGG2ndlY7xCZr/+Ym88xbsLDwAX8uVMpN/F4wTM53abtV4gW
dcsCx4uONZKMIoc/CW3wiSuU+hQRV2yGHkboQdkPwe/vYsGocLwLyU78b107v5GC
TW+yLO5ucdVAGktA3EN1VPFoG4CGQssjwC929H2yhN9c6Z0OEvXBjLUM5MLYvIk7
668870fZImWrxNE19TLITtw19rVpIeVczt5lWmdYp+Asj04KluqZCn5jsgAPh5pU
wOedD3huFQrFMlRZ39Gjps7CcSm6KI/AeC8Nw1uQA/GjhvFFIJuVsTGDqQP5MbNd

Bug#909942: mmdebstrap: breaks system it runs on, power cycle needed.

[Johannes Schauer]

Hi again,

On Mon, 01 Oct 2018 17:20:17 +0200 Johannes Schauer  wrote:
> I now added a commit that mounts a completely new sysfs when not running in
> unshare mode and doesn't use the --recursive when unmounting:
> 
> https://gitlab.mister-muffin.de/josch/mmdebstrap/commit/640d854c2e0f139fdfbd60ddaffc5dfe72063fc0
> 
> If you are okay with that, I'd be happy if you could verify that after adding
> this patch, the problem indeed disappears.

and this commit should fix the unintended renaming of the source of the bind
mounts:

https://gitlab.mister-muffin.de/josch/mmdebstrap/commit/6da8791c118b132feff51503182b7e8ce5dda48d


signature.asc
Description: signature

Bug#909218: nvidia-xconfig: Files section missing ModulePath entries break GLX upon installing libgl1-nvidia-glx (required by Steam)

[Miguel Angel Vilela]

Please find logs attached.

It appears only an empty or missing xorg.conf will cause the issue with
xflock4.
I tried before a file with only the Files section, and today I tried also
with both sections (with-files) as well as without Files, and again and
empty xorg.conf

Thanks to you!
Miguel


On Sun, Sep 30, 2018 at 3:14 PM Andreas Beckmann  wrote:

> PS: can you repeat the xflock4 test with the working minimal xorg.conf,
> too? Including the sleep+stop trick, to produce a well matching logfile?
>
> Thanks,
>
> Andreas
>


-- 
There are 10 types of geeks: 1s and 0s.

X.Org X Server 1.20.1
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.9.0-7-amd64 x86_64 Debian
Current Operating System: Linux rapture 4.18.0-1-amd64 #1 SMP Debian 4.18.6-1 
(2018-09-06) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1-amd64 
root=UUID=7e47da94-60c7-43de-aa1b-8f2e4bf73be8 ro nomodeset net.ifnames=0 
biosdevname=0
Build Date: 17 August 2018  08:05:00PM
xorg-server 2:1.20.1-1 (https://www.debian.org/support) 
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct  1 22:54:18 2018
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(==) No Layout section.  Using the first Screen section.
(==) No screen section available. Using defaults.
(**) |-->Screen "Default Screen Section" (0)
(**) |   |-->Monitor ""
(==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(==) Automatically adding GPU devices
(==) Max clients allowed: 256, resource mask: 0x1f
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
Entry deleted from font path.
(==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
(**) ModulePath set to "/usr/lib/xorg/modules/linux,/usr/lib/xorg/modules"
(II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
(II) Loader magic: 0x557345da3de0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 24.0
X.Org XInput driver : 24.1
X.Org Server Extension : 10.0
(++) using VT number 7

(II) systemd-logind: logind integration requires -keeptty and -keeptty was not 
provided, disabling logind integration
(II) xfree86: Adding drm device (/dev/dri/card0)
(--) PCI:*(9@0:0:0) 10de:1b81:1043:8598 rev 161, Mem @ 0xf600/16777216, 
0xe000/268435456, 0xf000/33554432, I/O @ 0xd000/128, BIOS @ 
0x/131072
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/linux/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module  390.87  Tue Aug 21 16:10:56 PDT 2018
(II) Applying OutputClass "nvidia" to /dev/dri/card0
loading driver: nvidia
(==) Matched nvidia as autoconfigured driver 0
(==) Matched nouveau as autoconfigured driver 1
(==) Matched nv as autoconfigured driver 2
(==) Matched modesetting as autoconfigured driver 3
(==) Matched fbdev as autoconfigured driver 4
(==) Matched vesa as autoconfigured driver 5
(==) Assigned the driver to the xf86ConfigLayout
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) LoadModule: "nouveau"
(II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
(II) Module nouveau: vendor="X.Org Foundation"
compiled for 1.20.0, module version = 1.0.15
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 24.0
(II) LoadModule: "nv"
(WW) Warning, couldn't open module nv
(EE) Failed to load module "nv" (module does not exist, 0)
(II) LoadModule: "modesetting"
(II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
(II) Module modesetting: vendor="X.Org Foundation"
compiled for 1.20.1, module version = 1.20.1
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 24.0
(II) LoadModule: "fbdev"
(II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
(II) Module fbdev: vendor="X.Org Foundation"
compiled for 1.20.0, module version = 0.5.0
Module class: X.Org Video 

Bug#910045: apertium-hbs-mkd parallel FTBFS

[Helmut Grohne]

Source: apertium-hbs-mkd
Version: 0.1.0~r76450-2
Severity: serious
Tags: ftbfs

apertium-hbs-mkd fails to build from source with sbuild on
unstable/amd64 when DEB_BUILD_OPTIONS is sufficiently parallel. A build
log ends with:

|dh_auto_build -O--fail-missing
| make -j8
| make[1]: Entering directory '/<>'
| make  all-am
| make[2]: Entering directory '/<>'
| xsltproc --stringparam alt hbs --stringparam var ijek alt.xsl 
apertium-hbs-mkd.hbs.metadix >apertium-hbs-mkd.hbs.dix 
| apertium-validate-dictionary apertium-hbs-mkd.mkd.dix
| xsltproc --stringparam alt hbs_BS --stringparam var ijek alt.xsl 
apertium-hbs-mkd.hbs.metadix >apertium-hbs-mkd.hbs_BS.dix
| xsltproc --stringparam alt hbs_HR --stringparam var ijek alt.xsl 
apertium-hbs-mkd.hbs.metadix >apertium-hbs-mkd.hbs_HR.dix
| xsltproc --stringparam alt hbs_SR --stringparam var ek alt.xsl 
apertium-hbs-mkd.hbs.metadix >apertium-hbs-mkd.hbs_SR.dix
| if [ ! -d .deps ]; then mkdir .deps; fi
| if [ ! -d .deps ]; then mkdir .deps; fi
| apertium-validate-dictionary apertium-hbs-mkd.mkd.dix
| mkdir: apertium-validate-dictionary apertium-hbs-mkd.hbs-mkd.dix
| cannot create directory ‘.deps’: File exists
| make[2]: *** [Makefile:829: mkd-hbs.autobil.bin] Error 1
| make[2]: *** Waiting for unfinished jobs
| apertium-hbs-mkd.mkd.dix:2484: element pardef: Schemas validity error : 
Element 'pardef': Duplicate key-sequence ['зн/ае__vblex'] in unique 
identity-constraint 'pardef-unique'.
| lt-comp lr apertium-hbs-mkd.mkd.dix mkd-hbs.automorf.bin
| apertium-hbs-mkd.mkd.dix:2484: element pardef: Schemas validity error : 
Element 'pardef': Duplicate key-sequence ['зн/ае__vblex'] in unique 
identity-constraint 'pardef-unique'.
| lt-comp lr apertium-hbs-mkd.hbs-mkd.dix hbs-mkd.autobil.bin
| lt-comp rl apertium-hbs-mkd.mkd.dix hbs-mkd.autogen.bin
| main@standard 14580 22636
| final@inconditional 161 815
| main@standard 12693 26012
| final@inconditional 161 792
| main@standard 12630 25786
| prefixes@standard 9 9
| make[2]: Leaving directory '/<>'
| make[1]: *** [Makefile:333: all] Error 2
| make[1]: Leaving directory '/<>'
| dh_auto_build: make -j8 returned exit code 2
| make: *** [debian/rules:9: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

This is a race condition between the "if [ ! -d .deps ]; then mkdir
.deps; fi" commands. When both are executed simultaneously, both see
.deps as absent and try to create it.

Helmut

Bug#908490: marked as done (py3status FTBFS: ImportError: cannot import name '_to_ascii' from 'setuptools.command.easy_install')

[Debian Bug Tracking System]

Your message dated Mon, 01 Oct 2018 20:13:26 +
with message-id 
and subject line Bug#908490: fixed in py3status 3.13-1
has caused the Debian Bug report #908490,
regarding py3status FTBFS: ImportError: cannot import name '_to_ascii' from 
'setuptools.command.easy_install'
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.)


-- 
908490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: py3status
Version: 3.12-1
Severity: serious
Tags: ftbfs

Some recent change in unstable makes py3status FTBFS:

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

...
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 10, in 
from setuptools.command.easy_install import _to_ascii, ScriptWriter
ImportError: cannot import name '_to_ascii' from 
'setuptools.command.easy_install' 
(/usr/lib/python3/dist-packages/setuptools/command/easy_install.py)
E: pybuild pybuild:338: clean: plugin distutils failed with: exit code=1: 
python3.7 setup.py clean 
dh_auto_clean: pybuild --clean -i python{version} -p "3.7 3.6" returned exit 
code 13
make: *** [debian/rules:6: clean] Error 25
--- End Message ---
--- Begin Message ---
Source: py3status
Source-Version: 3.13-1

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

Debian distribution maintenance software
pp.
Sebastien Delafond  (supplier of updated py3status package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Oct 2018 12:01:17 -0700
Source: py3status
Binary: py3status
Architecture: source
Version: 3.13-1
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Delafond 
Changed-By: Sebastien Delafond 
Description:
 py3status  - extensible i3status wrapper written in Python (Python3 package)
Closes: 908490
Changes:
 py3status (3.13-1) unstable; urgency=medium
 .
   * New upstream version 3.13 (Closes: #908490)
   * Bump up Standards-Version
Checksums-Sha1:
 9bfe24b2ead38dace8cd01ab1caa559ccdd40988 1543 py3status_3.13-1.dsc
 03c5871cd816447916f4321b7643a08ce00e0c2f 230620 py3status_3.13.orig.tar.xz
 a5920ecbd15360473202d094b463487949237231 2488 py3status_3.13-1.debian.tar.xz
 e3d8d115011413c8e8377cc1df4cd2a11408251d 6109 py3status_3.13-1_amd64.buildinfo
Checksums-Sha256:
 c5e9fa077440633d85cc342e2787589fa9ce4e6b792e3fc7e0aef80ae646bc9e 1543 
py3status_3.13-1.dsc
 d1ba909a072cd21d3b7864c14aa644f4c68c293b800d33814c71a0e13d0ce54b 230620 
py3status_3.13.orig.tar.xz
 1b8a8bd5b00307869ccdb11fe2381c5c572d0a86659429a71dfb0bf804ebdaa4 2488 
py3status_3.13-1.debian.tar.xz
 8355dabca2e6126fabab764cc620259bad4503b818b7f58dc3b130dd7caab953 6109 
py3status_3.13-1_amd64.buildinfo
Files:
 f38c845b736147b5c97e4c004ef2e06e 1543 utils optional py3status_3.13-1.dsc
 91fd33318e197d686372e3a103d15ea8 230620 utils optional 
py3status_3.13.orig.tar.xz
 df3d733180264289c2b36bfcab6d9b76 2488 utils optional 
py3status_3.13-1.debian.tar.xz
 69c0da200879adefca161a6d6a79533a 6109 utils optional 
py3status_3.13-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFDBAEBCgAtFiEEAqSkbVtrXP4xJMh3EL6Jg/PVnWQFAluyc5APHHNlYkBkZWJp
YW4ub3JnAAoJEBC+iYPz1Z1ktRMH/1UFGYl4fqWd5nAg3PVMrOiR6cC3ewWjT9Nm
iS7Z78RNe00XpkTG/GQwdHGaX9a8ancSMd5jZp8/RhPQTqCopLSQ9eRTNlg4tWWI
zBhRxupKv/0hUA6klG8zlb+Ri/w0lJuE/o+nJYSEy+Ilayl/TZ8F04ozZSZMdcTV
iKSj4YVmcrvUqxifhu9L39srWSadnMCHQUbaobTfq3T2rAVbDC+kFlLXaYQlINyF
VdS+D0ET113rMo26OlRoMtHoJBUPOwEFHWTKHiC7csOBD7zwcc46G2KB5Bqt4vKr
kDx40calvRXFIK7GkjqJFUePFtDE5tw7+ohsZOxwxGOyXkEUM6I=
=+r8+
-END PGP SIGNATURE End Message ---

Bug#910042: afterburnr.fx FTBFS: compilation error

[Helmut Grohne]

Source: afterburner.fx
Version: 1.7.0-1
Severity: serious
Tags: ftbfs

afterburner.fx fails to build in sbuild for unstable/amd64. A build log
ends with:

|dh_auto_build
|   /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=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
| WARNING: An illegal reflective access operation has occurred
| WARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$1 
(file:/usr/share/maven/lib/guice.jar) to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
| WARNING: Please consider reporting this to the maintainers of 
com.google.inject.internal.cglib.core.$ReflectUtils$1
| WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
| WARNING: All illegal access operations will be denied in a future release
| [INFO] Scanning for projects...
| [WARNING] The POM for 
org.apache.maven.plugins:maven-install-plugin:jar:2.4 is missing, no dependency 
information available
| [WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-install-plugin:2.4: Plugin 
org.apache.maven.plugins:maven-install-plugin:2.4 or one of its dependencies 
could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.maven.plugins:maven-install-plugin:jar:2.4 has not been downloaded 
from it before.
| [WARNING] The POM for 
org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is missing, no dependency 
information available
| [WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-deploy-plugin:2.7: Plugin 
org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies 
could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 has not been downloaded 
from it before.
| [WARNING] The POM for 
org.apache.maven.plugins:maven-site-plugin:jar:3.3 is missing, no dependency 
information available
| [WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-site-plugin:3.3: Plugin 
org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies could 
not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) 
in offline mode and the artifact 
org.apache.maven.plugins:maven-site-plugin:jar:3.3 has not been downloaded from 
it before.
| [WARNING] The POM for 
org.apache.maven.plugins:maven-antrun-plugin:jar:1.3 is missing, no dependency 
information available
| [WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-antrun-plugin:1.3: Plugin 
org.apache.maven.plugins:maven-antrun-plugin:1.3 or one of its dependencies 
could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.maven.plugins:maven-antrun-plugin:jar:1.3 has not been downloaded 
from it before.
| [WARNING] The POM for 
org.apache.maven.plugins:maven-assembly-plugin:jar:2.2-beta-5 is missing, no 
dependency information available
| [WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5: Plugin 
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5 or one of its 
dependencies could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.maven.plugins:maven-assembly-plugin:jar:2.2-beta-5 has not been 
downloaded from it before.
| [WARNING] The POM for 
org.apache.maven.plugins:maven-dependency-plugin:jar:2.8 is missing, no 
dependency information available
| [WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-dependency-plugin:2.8: Plugin 
org.apache.maven.plugins:maven-dependency-plugin:2.8 or one of its dependencies 
could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.maven.plugins:maven-dependency-plugin:jar:2.8 has not been 
downloaded from it before.
| [WARNING] The POM for 
org.apache.maven.plugins:maven-release-plugin:jar:2.5.3 is missing, no 
dependency information available
| [WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-release-plugin:2.5.3: Plugin 
org.apache.maven.plugins:maven-release-plugin:2.5.3 

Bug#895765: How to announce commons.io in gradle build

[Andreas Tille]

Hi,

igv upstream has switched the build system to gradle and provides
specific java9 gradle input file.  I probably did not found the most
elegant way to choose this[1] but it should at least work.  I wonder
how I should announce common classes that are not found in

...
Compiling with JDK Java compiler API.
/build/igv-2.4.14+dfsg/src/main/java9/module-info.java:96: error: module not 
found: com.google.common
requires com.google.common;
   ^
/build/igv-2.4.14+dfsg/src/main/java9/module-info.java:97: error: module not 
found: commons.io
requires commons.io;
^
/build/igv-2.4.14+dfsg/src/main/java9/module-info.java:98: error: module not 
found: commons.math
requires commons.math;
^
/build/igv-2.4.14+dfsg/src/main/java9/module-info.java:100: error: module not 
found: gson
requires gson;
 ^
/build/igv-2.4.14+dfsg/src/main/java9/module-info.java:110: error: module not 
found: javafx.base
requires javafx.base;
   ^
/build/igv-2.4.14+dfsg/src/main/java9/module-info.java:111: error: module not 
found: javafx.controls
requires javafx.controls;
   ^
...

since I can not find these in the said *.gradle files and thus have no
idea how to replace the upstream delivered jar file by the Debian
packaged file.  The according Build-Depends are (hopefully) properly
set.

Kind regards

Andreas.

[1] 
https://salsa.debian.org/med-team/igv/commit/1fd85b5d63a43613ee39f7915278e35787438aa2

-- 
http://fam-tille.de

Bug#910041: aether-ant-tasks FTBFS: error: Can't rename /usr/share/java/commons-lang3.jar as /usr/share/java/commons-lang3.zbk Permission denied

[Helmut Grohne]

Source: aether-ant-tasks
Version: 1.0.1-2
Severity: serious
Tags: ftbfs

A native build of aether-ant-tasks with sbuild in unstable on amd64 ends
with:

|jh_classpath -O--buildsystem=maven
| error: Can't rename /usr/share/java/commons-lang3.jar as 
/usr/share/java/commons-lang3.zbk Permission denied 
|  at /usr/share/perl5/Archive/Zip/Archive.pm line 471.
| 
Archive::Zip::Archive::overwriteAs(Archive::Zip::Archive=HASH(0x55ba51fd0bf8), 
"/usr/share/java/commons-lang3.jar") called at 
/usr/share/perl5/Archive/Zip/Archive.pm line 439
| 
Archive::Zip::Archive::overwrite(Archive::Zip::Archive=HASH(0x55ba51fd0bf8)) 
called at /usr/bin/jh_manifest line 342
| main::update_jar("/usr/share/java/commons-lang3.jar", undef) called 
at /usr/bin/jh_manifest line 147
| jh_manifest: Writing modified jar (/usr/share/java/commons-lang3.jar) failed: 
Permission denied
| jh_classpath: jh_manifest -plibaether-ant-tasks-java --classpath=\\ 
/usr/share/java/commons-lang3.jar returned exit code 13
| make: *** [debian/rules:4: binary] Error 2
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

Helmut

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 910038 src:rpyc
Bug #910038 [python3-rpyc] python3-rpyc: did not build
Bug reassigned from package 'python3-rpyc' to 'src:rpyc'.
No longer marked as found in versions 4.0.2-2.
Ignoring request to alter fixed versions of bug #910038 to the same values 
previously set
> forcemerge 908941 910038
Bug #908941 [src:rpyc] rpyc FTBFS: test_registry.TestUdpRegistry failures
Bug #910038 [src:rpyc] python3-rpyc: did not build
Severity set to 'serious' from 'important'
The source rpyc and version 4.0.2-2 do not appear to match any binary packages
Marked as found in versions rpyc/4.0.2-2.
Added tag(s) ftbfs.
Merged 908941 910038
> affects 908941 python3-rpyc
Bug #908941 [src:rpyc] rpyc FTBFS: test_registry.TestUdpRegistry failures
Bug #910038 [src:rpyc] python3-rpyc: did not build
Added indication that 908941 affects python3-rpyc
Added indication that 910038 affects python3-rpyc
> thanks
Stopping processing here.

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

Bug#908472: Bug #908472 in gdcm marked as pending

[Gert Wollny]

Control: tag -1 pending

Hello,

Bug #908472 in gdcm reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/med-team/gdcm/commit/21ebea9089756135bd9f9b77c07d81d9d020ff16


d/control: Add conflict with python2 packages, Closes: #908472



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/908472

Processed: Bug #908472 in gdcm marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #908472 [python3-vtkgdcm] python3-vtkgdcm: missing Breaks+Replaces: 
python-vtkgdcm
Added tag(s) pending.

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

Processed: tagging 844861

[Debian Bug Tracking System]

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

> tags 844861 + patch
Bug #844861 [src:wsjtx] wsjtx: FTBFS: ld: final link failed: Nonrepresentable 
section on output
Added tag(s) patch.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:pyfai
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #908615 (http://bugs.debian.org/908615)
> # Bug title: pyfai: FTBFS and autopkgtest fails with python3.7 in supported 
> versions
> #  * https://github.com/silx-kit/pyFAI/issues/888
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 908615 + fixed-upstream
Bug #908615 [src:pyfai] pyfai: FTBFS and autopkgtest fails with python3.7 in 
supported versions
Added tag(s) fixed-upstream.
> usertags 908615 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 908615 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package python2.7

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package python2.7
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #909673 (http://bugs.debian.org/909673)
> # Bug title: python2.7: CVE-2018-1000802
> #  * https://bugs.python.org/issue34540
> #  * remote status changed: (?) -> closed
> #  * remote resolution changed: (?) -> fixed
> #  * closed upstream
> tags 909673 + fixed-upstream
Bug #909673 [python2.7] python2.7: CVE-2018-1000802
Added tag(s) fixed-upstream.
> usertags 909673 + status-closed resolution-fixed
There were no usertags set.
Usertags are now: status-closed resolution-fixed.
> thanks
Stopping processing here.

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

Bug#898969: dnssec-trigger: fails with OpenSSL in experimental due to too-small key

[Lee Garrett]

Hi,

Any update on this bug? dnssec-trigger will be autoremoved due to this bug
tomorrow. I'd like to see it in buster, though.

Regards,
Lee

Bug#907491: closed by Paul Gevers (Re: goobook fails to authenticate)

[Sergio Mendoza]

Hi Ilias,

  Today I performed a dist-upgrade and things are back to normal.  goobook
runs fine as it should.  Hope it doesn't go wrong again.

Cheers,

Sergio.

-- 
Sergio Mendoza  
Instituto de Astronomia, UNAM
http://www.mendozza.org/sergio
On Mon, Sep 24, 2018 at 09:19:49AM -0500, Sergio Mendoza wrote:
> Hi Ilias,
> 
>   Nope.  It's not python-httplib2.  Can't find what can it be:
> 
> 
> root@izta:~# pip uninstall python-httplib2
> Cannot uninstall requirement python-httplib2, not installed
> root@izta:~# dpkg -l python-httplib2
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name   Version  Architecture Description
> +++-==---==
> ii  python-httplib 0.11.3-1 all  comprehensive HTTP client library
> root@izta:~# ls -l /usr/lib/python2.7/dist-packages/httplib2/
> total 180
> -rw-r--r-- 1 root root 73431 Sep  5 01:45 __init__.py
> -rw-r--r-- 1 root root 59427 Sep  9 13:05 __init__.pyc
> -rw-r--r-- 1 root root  3828 Mar 29 20:28 iri2uri.py
> -rw-r--r-- 1 root root  3786 Sep  9 13:05 iri2uri.pyc
> -rw-r--r-- 1 root root 18999 Mar 29 20:28 socks.py
> -rw-r--r-- 1 root root 17500 Sep  9 13:05 socks.pyc
> 
> 
> Cheers,
> 
> Sergio.
> 
> --
> Sergio Mendoza  
> Instituto de Astronomia, UNAM
> http://www.mendozza.org/sergio
> 
> 
> 
> 
> On Sat, Sep 22, 2018 at 02:36:45PM +0300, Ilias Tsitsimpis wrote:
> > Hi again,
> > 
> > On Fri, Sep 21, 2018 at 01:46PM, Sergio Mendoza wrote:
> > >   Unfortunately, no matter how hard I look for to spot the problem, I have
> > > not find the culprit package.  I tried and tried, but couldn't.  This is
> > > the reason I reported the bug to goobook.  Sorry for not being more
> > > helpful.
> > > 
> > > > > sergio@izta:~$ goobook query sergio
> > > > > Traceback (most recent call last):
> > > > >   File "/usr/bin/goobook", line 11, in 
> > > > > load_entry_point('goobook==1.9', 'console_scripts', 'goobook')()
> > > > >   File "/usr/share/goobook/goobook/application.py", line 94, in main
> > > > > args.func(config, args)
> > > > >   File "/usr/share/goobook/goobook/application.py", line 125, in 
> > > > > do_query
> > > > > goobk = GooBook(config)
> > > > >   File "/usr/share/goobook/goobook/goobook.py", line 59, in __init__
> > > > > self.cache.load()
> > > > >   File "/usr/share/goobook/goobook/goobook.py", line 257, in load
> > > > > self.update()
> > > > >   File "/usr/share/goobook/goobook/goobook.py", line 264, in update
> > > > > self.contacts = list(self._parse_contacts(gc.fetch_contacts()))
> > > > >   File "/usr/share/goobook/goobook/goobook.py", line 395, in 
> > > > > fetch_contacts
> > > > > res = self._get(query)
> > > > >   File "/usr/share/goobook/goobook/goobook.py", line 371, in _get
> > > > > connection_type=httplib2.HTTPSConnectionWithTimeout)
> > > > >   File 
> > > > > "/usr/local/lib/python2.7/dist-packages/oauth2client/client.py", line 
> > > > > 562, in new_request
> > > > > redirections, connection_type)
> > > > >   File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py", 
> > > > > line 1608, in request
> > > > > (response, content) = self._request(conn, authority, uri, 
> > > > > request_uri, method, body, headers, redirections, cachekey)
> > > > >   File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py", 
> > > > > line 1350, in _request
> > > > > (response, content) = self._conn_request(conn, request_uri, 
> > > > > method, body, headers)
> > > > >   File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py", 
> > > > > line 1272, in _conn_request
> > > > > conn.connect()
> > > > >   File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py", 
> > > > > line 1059, in connect
> > > > > raise SSLHandshakeError(e)
> > > > > httplib2.SSLHandshakeError: [SSL: CERTIFICATE_VERIFY_FAILED] 
> > > > > certificate verify failed (_ssl.c:726)
> > > > 
> > > > The above traceback mentions 
> > > > "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py".
> > > > This is not the canonical location where Debian Python packages get
> > > > installed. I believe you have installed a different version of the
> > > > httplib2 module using pip. Could you please test using the Python module
> > > > provided by the python-httplib2 package?
> > 
> > Please take a look at the comment above. It looks like you are not using
> > the official Debian package for python-httplib2, which is installed
> > under /usr/lib/python2.7/dist-packages/httplib2/ [1]. My guess is that
> > you have `pip install`-ed that package, so I would start by uninstalling
> > it and revert back to the Debian one.
> > 
> > [1] https://packages.debian.org/sid/all/python-httplib2/filelist
> > 
> > Cheers,
> > 
> > -- 
> > Ilias

Bug#909986: marked as done (cloudpickle: FTBFS (TypeError: can't pickle _abc_data objects))

[Debian Bug Tracking System]

Your message dated Mon, 01 Oct 2018 18:19:23 +
with message-id 
and subject line Bug#909986: fixed in cloudpickle 0.5.6-1
has caused the Debian Bug report #909986,
regarding cloudpickle: FTBFS (TypeError: can't pickle _abc_data objects)
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.)


-- 
909986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cloudpickle
Version: 0.5.2-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build

[... snipped ...]

self.framer.commit_frame()

# Check for persistent id (defined by a subclass)
pid = self.persistent_id(obj)
if pid is not None and save_persistent_id:
self.save_pers(pid)
return

# Check the memo
x = self.memo.get(id(obj))
if x is not None:
self.write(self.get(x[0]))
return

# Check the type dispatch table
t = type(obj)
f = self.dispatch.get(t)
if f is not None:
f(self, obj) # Call unbound method with explicit self
return

# Check private dispatch table if any, or else copyreg.dispatch_table
reduce = getattr(self, 'dispatch_table', dispatch_table).get(t)
if reduce is not None:
rv = reduce(obj)
else:
# Check for a class with a custom metaclass; treat as regular class
try:
issc = issubclass(t, type)
except TypeError: # t is not a class (old Boost; see SF #502085)
issc = False
if issc:
self.save_global(obj)
return

# Check for a __reduce_ex__ method, fall back to __reduce__
reduce = getattr(obj, "__reduce_ex__", None)
if reduce is not None:
>   rv = reduce(self.proto)
E   TypeError: can't pickle _abc_data objects

/usr/lib/python3.7/pickle.py:524: TypeError
=== 2 failed, 101 passed, 7 skipped in 12.76 seconds ===
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.7_cloudpickle/build; python3.7 -m pytest -s
dh_auto_test: pybuild --test -i python{version} -p "3.7 3.6" returned exit code 
13
make: *** [debian/rules:8: build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: cloudpickle
Source-Version: 0.5.6-1

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

Debian distribution maintenance software
pp.
Diane Trout  (supplier of updated cloudpickle 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: Tue, 03 Jul 2018 21:54:43 -0700
Source: cloudpickle
Binary: python3-cloudpickle python-cloudpickle
Architecture: source

Processed: [bts-link] source package pypi2deb

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package pypi2deb
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #909549 (http://bugs.debian.org/909549)
> # Bug title: cannot download... None details from PyPI: ContentTypeError
> #  * https://github.com/p1otr/pypi2deb/pull/19
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 909549 + fixed-upstream
Bug #909549 [pypi2deb] cannot download... None details from PyPI: 
ContentTypeError
Added tag(s) fixed-upstream.
> usertags 909549 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#909986: cloudpickle: FTBFS (TypeError: can't pickle _abc_data objects)

[Diane Trout]

On Sun, 2018-09-30 at 23:03 +, Santiago Vila wrote:
> Package: src:cloudpickle
> Version: 0.5.2-2
> Severity: serious
> Tags: ftbfs
> 
> Dear maintainer:
> 
> I tried to build this package in buster but it failed:

Looks like a python 3.7 incompatibility

I updated to cloudpickle 0.5.6 and it seems to work.

(The internal unittests pass, though though autopkgtests are having
trouble because of a debian mirror consistency problem)

I pushed a new source release and will see how the autobuilders handle
it.

Diane


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

Bug#909785: python-pcl: Incomplete debian/copyright and/or "freeware" source code?

[Jochen Sprickerhof]

Hi Chris,

* Chris Lamb  [2018-09-30 20:27]:

Great stuff; thanks! The only thing I would add would be something that
explicitly addresses the the "freeware" term - it is a bit of a
"trigger word" for people looking for DFSG violations.


Now I get why you where asking for this, thanks for the explanation :). 
I updated the comment here:


https://salsa.debian.org/science-team/pcl/commit/a99ca3f9916a6a5e9d66cc2e7e4eb4adc7d3ade9

Cheers Jochen


signature.asc
Description: PGP signature

Bug#906183: marked as done (libopenhpi-dev: broken symlink: /usr/lib/libopenhpi_snmp.so -> libopenhpi_snmp.so.3.8.0)

[Debian Bug Tracking System]

Your message dated Mon, 01 Oct 2018 16:51:35 +
with message-id 
and subject line Bug#906183: fixed in openhpi 3.8.0-2
has caused the Debian Bug report #906183,
regarding libopenhpi-dev: broken symlink: /usr/lib/libopenhpi_snmp.so -> 
libopenhpi_snmp.so.3.8.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.)


-- 
906183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libopenhpi-dev
Version: 3.8.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m34.1s ERROR: FAIL: Broken symlinks:
  /usr/lib/libopenhpi_snmp.so -> libopenhpi_snmp.so.3.8.0


You are probably missing a dependency on the corresponding
library package.


cheers,

Andreas


libopenhpi-dev_3.8.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: openhpi
Source-Version: 3.8.0-2

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

Debian distribution maintenance software
pp.
Mohan Devarajulu  (supplier of updated openhpi 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 13 Sep 2018 11:50:16 -0500
Source: openhpi
Binary: libopenhpi3 libopenhpi-dev openhpid openhpi-clients 
openhpi-plugin-ilo2-ribcl openhpi-plugin-ipmi openhpi-plugin-ipmidirect 
openhpi-plugin-oa-soap openhpi-plugin-ov-rest openhpi-plugin-slave 
openhpi-plugin-test-agent openhpi-plugin-snmp-bc openhpi-plugin-sysfs 
openhpi-plugin-watchdog openhpi-plugin-simulator 
openhpi-plugin-dynamic-simulator openhpi
Architecture: source amd64 all
Version: 3.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Mohan Devarajulu 
Changed-By: Mohan Devarajulu 
Description:
 libopenhpi-dev - OpenHPI libraries (development files)
 libopenhpi3 - OpenHPI libraries (runtime and support files)
 openhpi- SAF's HPI: Abstracted interface for managing computer hardware
 openhpi-clients - OpenHPI example client programs
 openhpi-plugin-dynamic-simulator - OpenHPI plugin module for a dynamic 
simulator
 openhpi-plugin-ilo2-ribcl - OpenHPI plugin module for HP's ProLiant rackmount 
servers
 openhpi-plugin-ipmi - OpenHPI plugin module for OpenIPMI
 openhpi-plugin-ipmidirect - OpenHPI plugin module for direct IPMI over LAN 
(RMCP) or SMI
 openhpi-plugin-oa-soap - OpenHPI plugin module for HPE's BladeSystem c-Class
 openhpi-plugin-ov-rest - OpenHPI plugin module for HPE's Synergy enclosures
 openhpi-plugin-simulator - OpenHPI plugin module for a simulator that works 
without hardware
 openhpi-plugin-slave - OpenHPI plugin module for slave plugin
 openhpi-plugin-snmp-bc - OpenHPI plugin module for IBM's BladeCenter or RSA 
over SNMP
 openhpi-plugin-sysfs - OpenHPI plugin module for the sysfs filesystem
 openhpi-plugin-test-agent - OpenHPI plugin module for test agent plugin
 openhpi-plugin-watchdog - OpenHPI plugin module for the Linux watchdog 
interface
 openhpid   - OpenHPI daemon, supports gathering of manageability information
Closes: 906183
Changes:
 openhpi (3.8.0-2) unstable; urgency=medium
 .
   * Fixed libopenhpi-dev: broken symlink: /usr/lib/libopenhpi_snmp.so ->
 libopenhpi_snmp.so.3.8.0 (Closes: #906183)
Checksums-Sha1:
 aba0b6551248da548ea99b55278845c02de258b8 3215 openhpi_3.8.0-2.dsc
 84c3e359aaa199fd4e3389289d353328e7ea8093 16124 openhpi_3.8.0-2.debian.tar.xz
 127714f769a09a366b815afb74f8f539113b5c8f 1028364 
libopenhpi-dev_3.8.0-2_amd64.deb
 23d58bc3816eca7cdbc8aad12a7cf82763418023 498532 
libopenhpi3-dbgsym_3.8.0-2_amd64.deb
 13daff623b2a57db65bd09ee1f5367c6f476d1b1 153632 libopenhpi3_3.8.0-2_amd64.deb
 1b4514b91ecd73f7682fc24564e242f10a8c87c0 1103708 
openhpi-clients-dbgsym_3.8.0-2_amd64.deb
 642228d8bc46a9a343c6667de1276a829a5c45e2 242240 
openhpi-clients_3.8.0-2_amd64.deb
 7f663787b47b0fdeebf459d2f995f0f68626814d 506196 
openhpi-plugin-dynamic-simulator-dbgsym_3.8.0-2_amd64.deb
 

Bug#910027: marked as done (python-hacking has python3-eventlet (= 0.20.0-4) build dependency)

[Debian Bug Tracking System]

Your message dated Mon, 01 Oct 2018 16:51:49 +
with message-id 
and subject line Bug#910027: fixed in python-hacking 1.1.0-2
has caused the Debian Bug report #910027,
regarding python-hacking has python3-eventlet (= 0.20.0-4) build dependency
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.)


-- 
910027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-hacking
Version: 1.1.0-1
Severity: serious
Tags: ftbfs

Was this supposed to be a >= ?
--- End Message ---
--- Begin Message ---
Source: python-hacking
Source-Version: 1.1.0-2

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-hacking package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Oct 2018 18:28:05 +0200
Source: python-hacking
Binary: python-hacking python-hacking-doc python3-hacking
Architecture: source all
Version: 1.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Ondřej Nový 
Description:
 python-hacking - Flake8 OpenStack Hacking Guidelines Enforcement plugins - 
Python
 python-hacking-doc - Flake8 OpenStack Hacking Guidelines Enforcement plugins - 
doc
 python3-hacking - Flake8 OpenStack Hacking Guidelines Enforcement plugins - 
Python
Closes: 910027
Changes:
 python-hacking (1.1.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Use 'python3 -m sphinx' instead of sphinx-build for building docs
   * Allow newer python-eventlet (Closes: #910027)
   * Bump standards version to 4.2.1 (no changes)
   * Bump debhelper compat level to 11
Checksums-Sha1:
 2a50f96a055564d9de159e6d3222b317f6142abe 3000 python-hacking_1.1.0-2.dsc
 33abb0bdeb9a3455f0db45d81f10c5db60a01f6f 4584 
python-hacking_1.1.0-2.debian.tar.xz
 a59a76b255d3f0b60f9e8ee01a309004541f4503 921848 
python-hacking-doc_1.1.0-2_all.deb
 1e5d1c97f433809db44a71bb7af02c3a9066b9ad 21176 python-hacking_1.1.0-2_all.deb
 22af8e1124f8b92c445500a39d68509699b1208a 11394 
python-hacking_1.1.0-2_amd64.buildinfo
 211e32345489a6d66c6118c7904b870f43d1a1ca 21268 python3-hacking_1.1.0-2_all.deb
Checksums-Sha256:
 0696ae82a2010369dd7d99ef767ff853be8e0f6d58c17ab8bb9d3200e50c8284 3000 
python-hacking_1.1.0-2.dsc
 5138c4c63ebdf8138b200b1c0fa73334c705af9170a365b1298d911bf79acadb 4584 
python-hacking_1.1.0-2.debian.tar.xz
 6f67ad84ca6607204ecf80e07b245d1400eef89441ea101f1d0ca291499663ac 921848 
python-hacking-doc_1.1.0-2_all.deb
 bcbd4512f44545a4c751b134a51f174db96227fc7cf9b9c8e250b147f2575c17 21176 
python-hacking_1.1.0-2_all.deb
 3bc5dee3740eca9baf9e3f4d238cd4fb3d1a4b432f651b81fed93fa52bcbf100 11394 
python-hacking_1.1.0-2_amd64.buildinfo
 c58e553091223f8c8ba0e5658733cd795477b0d343c6cbd2409f57619762c61d 21268 
python3-hacking_1.1.0-2_all.deb
Files:
 5c31594c64d3dc9f0fcce71f4587e715 3000 python optional 
python-hacking_1.1.0-2.dsc
 5357cf95863f3bbbd547dd3ff4e37783 4584 python optional 
python-hacking_1.1.0-2.debian.tar.xz
 a2b9e9946e018b2f34ab77de9bdf0566 921848 doc optional 
python-hacking-doc_1.1.0-2_all.deb
 a700e9c5ef00ec71b0b260d84723f743 21176 python optional 
python-hacking_1.1.0-2_all.deb
 ad7646f8e05a7ef9d9070af0d0ec0c50 11394 python optional 
python-hacking_1.1.0-2_amd64.buildinfo
 785e3f96fbf8afa26a032e223ec541f4 21268 python optional 
python3-hacking_1.1.0-2_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAluyTPQACgkQNXMSVZ0e
Bkuq2g/+I67djzg1YoA6kmkix6hhqtU6tKbVHOjOrwKzzDI+P8i/t5jlYyyWounw
3Qawc795n4qVtlmN6rmhAFXKrexwLpcec0Q8dVrj6vTz+kzc9lunSamlly89as40
I1PC2Y5ZB7iKxEYDL+uuQcXKO94IzC5/Y5uF+Se9+PP6EdS4SmWZPcu3JrgMdAZ1
T5LyeDEnZG8f/fz7vtntcWhXRcrjK7N5m+PEhOprk361JBapTskV7OEh3fDl7fNw
ieThUiW+rEcvSb4cDWUvlAx68bBxVwGV7Ly1tV+5TcusrOiFWM2MBWfROsAgbutp
4fbt4Nw8m0d3tQ0dbKpZJlxcRfqjc+cr8TNeEtXeFaAMxIuv8eNJ6YIMV0Af9Upu
8fkh9teZnn8hQtKBReh6SDeP3tuEZzO/9C2SYRAWWl2f7Yic7xPKhynCC6ehKJ3t
AcjYERS6VOC0JhuGSWrscp08NMNbs507+oEKshI8HRqODX9ZmYvf33Kym+ToBvn+

Processed: affects 910009

[Debian Bug Tracking System]

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

> affects 910009 exim4-config
Bug #910009 [dpkg] dpkg execs $PAGER with execvp instead of sh -c, yielding 
upgrade failure
Added indication that 910009 affects exim4-config
> thanks
Stopping processing here.

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

Bug#910031: fuse3: Incomplete debian/copyright?

[Chris Lamb]

Source: fuse3
Version: 3.2.4-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Laszlo Boszormenyi (GCS) , 
ftpmas...@debian.org

Hi,

I just ACCEPTed fuse3 from NEW but noticed it was missing attribution 
in debian/copyright for at least Sebastian Pipping, SUSE Linux, Tejun
Heo, etc.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

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

Bug#910027: Bug #910027 in python-hacking marked as pending

[Ondřej Nový]

Control: tag -1 pending

Hello,

Bug #910027 in python-hacking reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/openstack-team/libs/python-hacking/commit/37e88644bffdac36a1ec3a0c041092ba251bd787


Allow never python-eventlet (Closes: #910027)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/910027

Processed: Bug #910027 in python-hacking marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #910027 [src:python-hacking] python-hacking has python3-eventlet (= 
0.20.0-4) build dependency
Added tag(s) pending.

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

Bug#910027: python-hacking has python3-eventlet (= 0.20.0-4) build dependency

[Adrian Bunk]

Source: python-hacking
Version: 1.1.0-1
Severity: serious
Tags: ftbfs

Was this supposed to be a >= ?

Bug#909377: [Pkg-emacsen-addons] Bug#909377: xemacs

[David Bremner]

"Barak A. Pearlmutter"  writes:

> It appears that xemacs support has bit-rotted away, while plain
> emacs25 installs fine. So I'm inclined to just mark this as
> conflicting with xemacs25 and mark this as a wishlist bug, in case
> anyone wants to figure out and fix the problem.
>
> Objections?

I would think it would be better to ignore xemacs21 (e.g. as the elpa-*
emacsen scripts do), rather than conflicting.

David

Bug#897747: marked as done (faketime: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Mon, 01 Oct 2018 15:21:32 +
with message-id 
and subject line Bug#897747: fixed in faketime 0.9.7-2.1
has caused the Debian Bug report #897747,
regarding faketime: ftbfs with GCC-8
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.)


-- 
897747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:faketime
Version: 0.9.7-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

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

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

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/faketime_0.9.7-2_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
make[2]: Entering directory '/<>/src'

make[2]: Leaving directory '/<>/src'
make  -C test distclean
make[2]: Entering directory '/<>/test'

make[2]: Leaving directory '/<>/test'
   dh_clean
 debian/rules binary-arch
PREFIX=/usr dh binary-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
   dh_auto_build -a
make -j8 -Oline "INSTALL=install --strip-program=true"
make  -C src all
make[2]: Entering directory '/<>/src'
cc -o faketime -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DMULTI_ARCH 
-Wno-nonnull-compare -std=gnu99 -Wall -Wextra -Werror -Wno-nonnull-compare 
-DFAKE_STAT -DFAKE_SLEEP -DFAKE_TIMERS -DFAKE_INTERNAL_CALLS -fPIC 
-DPREFIX='"'/usr'"' -DLIBDIRNAME='"'/lib/faketime'"' -Wdate-time 
-D_FORTIFY_SOURCE=2  faketime.c -Wl,-z,relro -Wl,-z,now -lpthread 
-Wl,--version-script=libfaketime.map -lrt
faketime.c: In function 'main':
faketime.c:289:45: error: '%s' directive output may be truncated writing up to 
4095 bytes into a region of size between 0 and 4095 [-Werror=format-truncation=]
 snprintf(shared_objs, PATH_BUFSIZE, "%s %s", sem_name, shm_name);
 ^~ 
In file included from /usr/include/stdio.h:862,
 from faketime.c:35:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: 
'__builtin___snprintf_chk' output between 2 and 8192 bytes into a destination 
of size 4096
   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  ^~~~
__bos (__s), __fmt, __va_arg_pack ());
~
cc1: all warnings being treated as errors
make[2]: *** [Makefile:98: faketime] Error 1
make[2]: Leaving directory '/<>/src'
make[2]: *** Waiting for unfinished jobs
make[2]: Entering directory '/<>/src'
cc -o libfaketimeMT.o -c -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DMULTI_ARCH 
-Wno-nonnull-compare -std=gnu99 -Wall -Wextra -Werror -Wno-nonnull-compare 
-DFAKE_STAT -DFAKE_SLEEP -DFAKE_TIMERS -DFAKE_INTERNAL_CALLS -fPIC 
-DPREFIX='"'/usr'"' -DLIBDIRNAME='"'/lib/faketime'"' -Wdate-time 
-D_FORTIFY_SOURCE=2 -DPTHREAD -DPTHREAD_SINGLETHREADED_TIME libfaketime.c
In file included from libfaketime.c:49:
libfaketime.c: In function 'fake_clock_gettime':
libfaketime.c:1994:24: error: cast between incompatible function types from 
'int (*)(pthread_mutex_t *)' {aka 'int (*)(union  *)'} to 'void 
(*)(void *)' [-Werror=cast-function-type]
   pthread_cleanup_push((void (*)(void *))pthread_mutex_unlock, (void 
*)_mutex);
^
cc1: all warnings being treated as errors
make[2]: *** [Makefile:92: libfaketimeMT.o] Error 1
make[2]: Leaving directory '/<>/src'
make[2]: Entering directory '/<>/src'
cc -o libfaketime.o -c -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat 

Bug#891551: marked as done (faketime: FTBFS with GCC 8 - error: 'strncpy' specified bound 256 equals destination size)

[Debian Bug Tracking System]

Your message dated Mon, 01 Oct 2018 15:21:32 +
with message-id 
and subject line Bug#897747: fixed in faketime 0.9.7-2.1
has caused the Debian Bug report #897747,
regarding faketime: FTBFS with GCC 8 - error: 'strncpy' specified bound 256 
equals destination size
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.)


-- 
897747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: faketime
Version: 0.9.7-1
Severity: important
User: debian-...@lists.debian.org
Usertag: ftbfs-gcc-8

Hi,

I recently performed an (unofficial) archive rebuild with GCC 8 on
mips64el. The main purpose of the rebuild was to discover mips toolchain
regressions, however I noticed this error in the logs which might be
interesting to you:

> faketime.c: In function 'main':
> faketime.c:289:45: error: '%s' directive output may be truncated writing up 
> to 4095 bytes into a region of size between 0 and 4095 
> [-Werror=format-truncation=]
>  snprintf(shared_objs, PATH_BUFSIZE, "%s %s", sem_name, shm_name);
>  ^~ 
> faketime.c:289:5: note: 'snprintf' output between 2 and 8192 bytes into a 
> destination of size 4096
>  snprintf(shared_objs, PATH_BUFSIZE, "%s %s", sem_name, shm_name);
>  ^~~~
> In file included from libfaketime.c:49:
> libfaketime.c: In function 'fake_clock_gettime':
> libfaketime.c:1986:24: error: cast between incompatible function types from 
> 'int (*)(pthread_mutex_t *)' {aka 'int (*)(union  *)'} to 'void 
> (*)(void *)' [-Werror=cast-function-type]
>pthread_cleanup_push((void (*)(void *))pthread_mutex_unlock, (void 
> *)_mutex);
> ^
> cc1: all warnings being treated as errors
> Makefile:98: recipe for target 'faketime' failed
> make[2]: *** [faketime] Error 1
> make[2]: *** Waiting for unfinished jobs
> libfaketime.c: In function 'fake_clock_gettime.part.4':
> libfaketime.c:2081:7: error: 'strncpy' specified bound 256 equals destination 
> size [-Werror=stringop-truncation]
>strncpy(user_faked_time, tmp_env, BUFFERLEN);
>^~~~
> libfaketime.c:2081:7: error: 'strncpy' specified bound 256 equals destination 
> size [-Werror=stringop-truncation]
>strncpy(user_faked_time, tmp_env, BUFFERLEN);
>^~~~
> libfaketime.c: In function 'ftpl_init':
> libfaketime.c:1831:12: error: 'strncpy' specified bound 1024 equals 
> destination size [-Werror=stringop-truncation]
>  (void) strncpy(ft_spawn_target, getenv("FAKETIME_SPAWN_TARGET"), 1024);
> ^~~
> libfaketime.c:1892:5: error: 'strncpy' specified bound 8192 equals 
> destination size [-Werror=stringop-truncation]
>  strncpy(user_faked_time_fmt, tmp_env, BUFSIZ);
>  ^
> libfaketime.c: In function 'ftpl_init':
> libfaketime.c:1831:12: error: 'strncpy' specified bound 1024 equals 
> destination size [-Werror=stringop-truncation]
>  (void) strncpy(ft_spawn_target, getenv("FAKETIME_SPAWN_TARGET"), 1024);
> ^~~
> libfaketime.c:1892:5: error: 'strncpy' specified bound 8192 equals 
> destination size [-Werror=stringop-truncation]
>  strncpy(user_faked_time_fmt, tmp_env, BUFSIZ);
>  ^
> cc1: all warnings being treated as errors
> Makefile:92: recipe for target 'libfaketime.o' failed
> make[2]: *** [libfaketime.o] Error 1
> cc1: all warnings being treated as errors
> Makefile:92: recipe for target 'libfaketimeMT.o' failed
> make[2]: *** [libfaketimeMT.o] Error 1
> make[2]: Leaving directory '/<>/src'
> Makefile:7: recipe for target 'all' failed
> make[1]: *** [all] Error 2
> make[1]: Leaving directory '/<>'
> dh_auto_build: make -j3 "INSTALL=install --strip-program=true" returned exit 
> code 2
> debian/rules:22: recipe for target 'build-arch' failed
> make: *** [build-arch] Error 2
> dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
> status 2

As you probably know, you need to be careful using strncpy.

Instead of:
 char out[SIZE];
 strncpy(out, in, SIZE);

You need to do:
 char out[SIZE]
 strncpy(out, in, SIZE - 1);
 out[SIZE - 1] = '\0';

See strcpy(3)

James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---

Bug#909942: mmdebstrap: breaks system it runs on, power cycle needed.

[Johannes Schauer]

Hi,

I'm sorry for the trouble that running mmdebstrap as superuser caused. I'm glad
that no data got lost!

On Sun, 30 Sep 2018 17:18:38 +0200 Andreas Henriksson  wrote:
> On Sun, Sep 30, 2018 at 04:49:07PM +0200, Andreas Henriksson wrote:
> [...]
> > > - cgroup mounts dissapearing
> [...]
> 
> So a simple test like this (similar as what can be seen used in the
> code) reveals the problem with all /sys sub-mounts dissapearing:
> 
> mount | grep /sys
> 
> mkdir /tmp/test
> mount --rbind /sys /tmp/test
> 
> mount | grep /sys
> 
> umount --lazy --recursive /tmp/test
> 
> mount | grep /sys
> 
> 
> (The same problem doesn't seem to occur without the --lazy flag, but
> then mount errors out after doing most of the job.)

I now added a commit that mounts a completely new sysfs when not running in
unshare mode and doesn't use the --recursive when unmounting:

https://gitlab.mister-muffin.de/josch/mmdebstrap/commit/640d854c2e0f139fdfbd60ddaffc5dfe72063fc0

If you are okay with that, I'd be happy if you could verify that after adding
this patch, the problem indeed disappears.

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#909377: marked as done (ilisp: fails to install with xemacs21)

[Debian Bug Tracking System]

Your message dated Mon, 01 Oct 2018 14:50:21 +
with message-id 
and subject line Bug#909377: fixed in ilisp 5.12.0+cvs.2004.12.26-27
has caused the Debian Bug report #909377,
regarding ilisp: fails to install with xemacs21
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.)


-- 
909377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909377
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ilisp
Version: 5.12.0+cvs.2004.12.26-26
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package ilisp.
  Preparing to unpack .../ilisp_5.12.0+cvs.2004.12.26-26_all.deb ...
  Unpacking ilisp (5.12.0+cvs.2004.12.26-26) ...
  Setting up ilisp (5.12.0+cvs.2004.12.26-26) ...
  Install emacsen-common for xemacs21
  emacsen-common: Handling install of emacsen flavor xemacs21
  Loading /usr/share/emacsen-common/debian-startup...
  Loading 00debian...
  Loading site-start...
  Loading /usr/share/emacsen-common/debian-startup...
  Loading 00debian...
  Loading site-start...
  Loading /usr/share/emacsen-common/debian-startup...
  Loading 00debian...
  Loading site-start...
[...]
  Loading site-start...
  Loading /usr/share/emacsen-common/debian-startup...
  Loading 00debian...
  Loading site-start...
  Loading /usr/share/emacsen-common/debian-startup...
  Loading 00debian...
  Loading site-start...
  Loading /usr/share/emacsen-common/debian-startup...
  Loading 00debian...
  Error while loading 00debian: Variable binding depth exceeds max-specpdl-size
  Compiling /usr/share/xemacs21/site-lisp/debian-startup.el...
  Wrote /usr/share/xemacs21/site-lisp/debian-startup.elc
  Done
  Install ilisp for xemacs21
  install/ilisp: Handling install for emacsen flavor xemacs21
  ERROR: install script from ilisp package failed
  dpkg: error processing package ilisp (--configure):
   installed ilisp package post-installation script subprocess returned error 
exit status 1
  Errors were encountered while processing:
   ilisp


cheers,

Andreas


ilisp=5.12.0+cvs.2004.12.26-26_xemacs21.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ilisp
Source-Version: 5.12.0+cvs.2004.12.26-27

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

Debian distribution maintenance software
pp.
Barak A. Pearlmutter  (supplier of updated ilisp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Oct 2018 15:13:36 +0100
Source: ilisp
Binary: ilisp ilisp-doc
Architecture: source all
Version: 5.12.0+cvs.2004.12.26-27
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacs addons team 

Changed-By: Barak A. Pearlmutter 
Description:
 ilisp  - Emacs interface to LISP implementations
 ilisp-doc  - Documentation for ILISP package
Closes: 909377
Changes:
 ilisp (5.12.0+cvs.2004.12.26-27) unstable; urgency=medium
 .
   * does not seem compatible with xemacs21 (closes: #909377)
   * bump policy
Checksums-Sha1:
 9283b5064378e3e3ca33d91feec3162894dee744 2088 
ilisp_5.12.0+cvs.2004.12.26-27.dsc
 a7975f84a03a85b06e3071c1f896f3689ec2ef43 86512 
ilisp_5.12.0+cvs.2004.12.26-27.debian.tar.xz
 a3c508d71b17588c44d18f36ff1a4410792a2f57 347336 
ilisp-doc_5.12.0+cvs.2004.12.26-27_all.deb
 31d5fac5298418365119d4134fef819aa7dea81e 226500 
ilisp_5.12.0+cvs.2004.12.26-27_all.deb
 8621a62c61a05a3a56f39a8a90375abb700b9a79 8378 
ilisp_5.12.0+cvs.2004.12.26-27_amd64.buildinfo
Checksums-Sha256:
 e9761948732705496e6cdfee12a80a36e505a53d91f9388e8cade08fc9cfec05 2088 
ilisp_5.12.0+cvs.2004.12.26-27.dsc
 05abff2a28c4cf13ebd04ed5f4026852e86a979bb62c9eabf062365d96c655a4 86512 
ilisp_5.12.0+cvs.2004.12.26-27.debian.tar.xz
 300e33affcdd9fcc57873db694f0ac3ba61894028ec74ed870476dd4f12d66cc 347336 
ilisp-doc_5.12.0+cvs.2004.12.26-27_all.deb
 

Bug#906609: gnucash: FTBFS on mips/sid: Segmentation fault

[Chris Lamb]

Hi,

> gnucash: FTBFS on mips/sid: Segmentation fault

Gentle ping on this? gnucash is not currently in testing (!).


Regards,

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

Bug#909377: xemacs

[Barak A. Pearlmutter]

It appears that xemacs support has bit-rotted away, while plain
emacs25 installs fine. So I'm inclined to just mark this as
conflicting with xemacs25 and mark this as a wishlist bug, in case
anyone wants to figure out and fix the problem.

Objections?

--Barak.

Bug#910016: marked as done (python-django: CVE-2018-16984)

[Debian Bug Tracking System]

Your message dated Mon, 01 Oct 2018 13:50:29 +
with message-id 
and subject line Bug#910016: fixed in python-django 2:2.1.2-1
has caused the Debian Bug report #910016,
regarding python-django: CVE-2018-16984
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.)


-- 
910016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-django
Version: 2:2.1.1-1
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for python-django.

CVE-2018-16984[0]:
Password hash disclosure to "view only" admin users

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16984
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16984


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: python-django
Source-Version: 2:2.1.2-1

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated python-django package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 01 Oct 2018 14:23:27 +0100
Source: python-django
Binary: python3-django python-django-doc
Built-For-Profiles: nocheck
Architecture: source all
Version: 2:2.1.2-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Chris Lamb 
Description:
 python-django-doc - High-level Python web development framework (documentation)
 python3-django - High-level Python web development framework (Python 3 version)
Closes: 910016
Changes:
 python-django (2:2.1.2-1) experimental; urgency=medium
 .
   * New upstream security release.
 .
 CVE-2018-16984: Password hash disclosure to "view only" admin users. If an
 admin user has the change permission to the user model, only part of the
 password hash is displayed in the change form. Admin users with the view
 (but not change) permission to the user model were displayed the entire
 hash.  While it's typically infeasible to reverse a strong password hash,
 if a site uses weaker password hashing algorithms such as MD5 or SHA1,
 it could be a problem. (Closes: #910016)
 .
   * Move all documentation to /usr/share/doc.
   * Really remove all license files (eg. LICENSE-SELECT2.md).
   * debian/tests/control: Drop deprecated needs-recommends test restriction.
Checksums-Sha1:
 0b58bccf144252c5f54847c6809562ff5d9f20ed 2666 python-django_2.1.2-1.dsc
 1be0feba9cb817f422a116f6b3bddbe1bd353ca7 8611286 
python-django_2.1.2.orig.tar.gz
 9f3ef08feb6322ffe862a36106afb29608636822 23812 
python-django_2.1.2-1.debian.tar.xz
 6a0d88e9d46a2cea08193cd5a368168f76cf3496 3040096 
python-django-doc_2.1.2-1_all.deb
 6d130f2ae839e280414462137af587b6c19fcd1b 7392 
python-django_2.1.2-1_amd64.buildinfo
 5b93566e7fb22a5cd61448b7c4dc063056bc4d70 2588460 python3-django_2.1.2-1_all.deb
Checksums-Sha256:
 b798bc6dde6d3522ba1bd4695d21cf96560849326927359438b3ca7e1a9cd764 2666 
python-django_2.1.2-1.dsc
 efbcad7ebb47daafbcead109b38a5bd519a3c3cd92c6ed0f691ff97fcdd16b45 8611286 
python-django_2.1.2.orig.tar.gz
 43d9571a097a37a5b22282fae120caacab90b542fd3024d89357f68fd207515c 23812 
python-django_2.1.2-1.debian.tar.xz
 afdd476cff7db79d2686b93f298a22986185149c30e49549599f74b4b6bcbdc6 3040096 
python-django-doc_2.1.2-1_all.deb
 b9561abdc5c1a2e51540f95ee8b8f92d8c96dcfe2041e9582e1e1d84717254a7 7392 
python-django_2.1.2-1_amd64.buildinfo
 1ce9f330e165144746a8822c79f27b664643c6b3824bd7091ec52c9434dde06c 2588460 
python3-django_2.1.2-1_all.deb
Files:
 699966b1ca33e44ba0fb8483fd3353d6 2666 python optional python-django_2.1.2-1.dsc
 383ca4e98ad5d0aa9d71378fe743bdef 8611286 python optional 
python-django_2.1.2.orig.tar.gz
 

Bug#749991: Wrong kernel in debian-installer package

[Wolfgang Schweer]

On Thu, Apr 06, 2017 at 09:46:55AM +0200, Cyril Brulebois wrote:
> Alexander Sosedkin  (2017-04-06):
> > That's one way to think about it. Got it, keeping old modules is hard.
> > But I wasn't asking about keeping old modules, I see no point in this.
> > I was asking about generating and publishing a matching
> > dists/testing/main/installer-/current on kernel upload.
> > Why is _that_ hard?
> 
> Because what's below testing/ was copied over from unstable/, and what's
> below unstable/ is being copied from the results of the debian-installer
> upload, which fetches its components from testing (that's our release
> cycle works: we hammer testing into shape until it gets released as a
> new stable). So a new kernel in unstable isn't sufficient to have all
> the pieces together, that's why we have daily builds, and that's why you
> keep being pointed at them.

Maybe people could be pointed to stable instead.

As the debian-installer netboot packages are updated with each point 
release, kernel module mismatch/missing issues should be avoidable.

Besides installing dist=stable by default, also testing and sid are 
supported.

Just adding 'mirror/suite=testing' as additional param to the kernel 
command line is enough.

(Someone wanting unstable would replace 'testing' with 'sid'.)

Wolfgang


signature.asc
Description: PGP signature

Processed: severity of 909957 is serious

[Debian Bug Tracking System]

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

> severity 909957 serious
Bug #909957 [ghostscript] Regression in ghostscript when using pstoedit 
(/undefined in --setpagedevice--)
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#909375: Bug #909375: Re: nautilus: Trace/breakpoint trap

[Michael Biebl]

Am 01.10.2018 um 14:56 schrieb Jeremy Bicha:
> On Sun, Sep 30, 2018 at 2:45 PM Michael Biebl  wrote:
>> Raising this issue of handling a missing ontologies file more gracefully
>> with the tracker upstream developers seems like a reasonable idea and I
>> would prefer this solution.
> 
> Tim & I were just going to create a tracker-common package and have
> libtracker-sparql-2.0-0 depend on it. See our packaging at
> https://salsa.debian.org/gnome-team/tracker and comment 30 at
> https://bugs.debian.org/908800
> 
> Michael, if that sounds fine to you, I can upload that.

I would prefer if the upstream route is tried first.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#909818: firefox: Web Content is eating nearly 100% CPU, several of them

[Simon Budig]

Package: firefox
Version: 62.0.2-1
Followup-For: Bug #909818

Dear Maintainer,

I can confirm the CPU-eating problem with firefox.

It might be related to the desktop environment. In my case I use XFCE and
the CPU eating problem goes away if I kill xfsettingsd.

stracing the "Web Conntent"-Process I see that firefox seems to do lots of
sendmsg() with references to font related files, not sure if this maybe is
related to fontconfig.

--- SIGSYS {si_signo=SIGSYS, si_code=SYS_SECCOMP, si_errno=ENOTDIR, 
si_call_addr=0x7fc4874a1dbe, si_syscall=__NR_openat, si_arch=AUDIT_ARCH_X86_64} 
---
socketpair(AF_UNIX, SOCK_SEQPACKET, 0, [35, 37]) = 0
sendmsg(30, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", iov_len=16}, 
{iov_base="/usr/share/fonts/cmap/adobe-cns1"..., iov_len=51}, {iov_base=NULL, 
iov_len=0}], msg_iovlen=3, msg_control=[{cmsg_len=20, cmsg_level=SOL_SOCKET, 
cmsg_type=SCM_RIGHTS, cmsg_data=[37]}], msg_controllen=24, msg_flags=0}, 
MSG_NOSIGNAL) = 67
close(37)   = 0
recvmsg(35, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="\354\377\377\377", iov_len=4}], msg_iovlen=1, 
msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 4
close(35)   = 0
rt_sigreturn({mask=[]}) = -1 ENOTDIR (Not a directory)
openat(AT_FDCWD, "/usr/share/fonts/cmap/adobe-cns1/resource.frk/Adobe-CNS1-6", 
O_RDONLY) = 257
--- SIGSYS {si_signo=SIGSYS, si_code=SYS_SECCOMP, si_errno=ENOTDIR, 
si_call_addr=0x7fc4874a1dbe, si_syscall=__NR_openat, si_arch=AUDIT_ARCH_X86_64} 
---
socketpair(AF_UNIX, SOCK_SEQPACKET, 0, [35, 37]) = 0
sendmsg(30, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", iov_len=16}, 
{iov_base="/usr/share/fonts/cmap/adobe-cns1"..., iov_len=59}, {iov_base=NULL, 
iov_len=0}], msg_iovlen=3, msg_control=[{cmsg_len=20, cmsg_level=SOL_SOCKET, 
cmsg_type=SCM_RIGHTS, cmsg_data=[37]}], msg_controllen=24, msg_flags=0}, 
MSG_NOSIGNAL) = 75
close(37)   = 0
recvmsg(35, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="\376\377\377\377", iov_len=4}], msg_iovlen=1, 
msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 4
close(35)   = 0
rt_sigreturn({mask=[]}) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/fonts/cmap/adobe-cns1/.resource/Adobe-CNS1-6", 
O_RDONLY) = 257


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

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

Versions of packages firefox depends on:
ii  debianutils   4.8.6
ii  fontconfig2.13.1-1
ii  libatk1.0-0   2.30.0-1
ii  libc6 2.27-6
ii  libcairo-gobject2 1.15.12-1
ii  libcairo2 1.15.12-1
ii  libdbus-1-3   1.12.10-1
ii  libdbus-glib-1-2  0.110-3
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-8
ii  libfontconfig12.13.1-1
ii  libfreetype6  2.8.1-2
ii  libgcc1   1:8.2.0-7
ii  libgdk-pixbuf2.0-02.38.0+dfsg-6
ii  libglib2.0-0  2.58.1-2
ii  libgtk-3-03.24.1-2
ii  libjsoncpp1   1.7.4-3
ii  libnspr4  2:4.20-1
ii  libnss3   2:3.39-1
ii  libpango-1.0-01.42.4-3
ii  libsqlite3-0  3.25.2-1
ii  libstartup-notification0  0.12-5
ii  libstdc++68.2.0-7
ii  libvpx5   1.7.0-3
ii  libx11-6  2:1.6.6-1
ii  libx11-xcb1   2:1.6.6-1
ii  libxcb-shm0   1.13-3
ii  libxcb1   1.13-3
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  procps2:3.3.15-2
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages firefox recommends:
ii  libavcodec57  7:3.4.3-1
ii  libavcodec58  7:4.0.2-2+b1

Versions of packages firefox suggests:
ii  fonts-lmodern  2.004.5-5
ii  fonts-stix [otf-stix]  1.1.1-4
ii  libcanberra0   0.30-6
ii  libgssapi-krb5-2   1.16-2
ii  libgtk2.0-02.24.32-3
ii  pulseaudio 12.2-2

-- debconf-show failed

Processed: fixed 909999 in 9.06~dfsg-2+deb8u10

[Debian Bug Tracking System]

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

> fixed 90 9.06~dfsg-2+deb8u10
Bug #90 [ghostscript] ghostscript (via pdf2ps) crashes on most inputs 
following upgrade to 9.06~dfsg-2+deb8u9
There is no source info for the package 'ghostscript' at version 
'9.06~dfsg-2+deb8u10' with architecture ''
Unable to make a source version for version '9.06~dfsg-2+deb8u10'
Marked as fixed in versions 9.06~dfsg-2+deb8u10.
> thanks
Stopping processing here.

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

Bug#907806: How to disable tests for Python2 only?

[Yaroslav Halchenko]

On Mon, 01 Oct 2018, Andreas Tille wrote:

> Hi Yaroslav,

> was this helpful for you?

sorry -- didn't look into scikit-learn yet. BTW - 0.20 release was
posted, so we should update and try again.  Will you have time or should
I ?

-- 
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

Bug#909375: Bug #909375: Re: nautilus: Trace/breakpoint trap

[Jeremy Bicha]

On Sun, Sep 30, 2018 at 2:45 PM Michael Biebl  wrote:
> Raising this issue of handling a missing ontologies file more gracefully
> with the tracker upstream developers seems like a reasonable idea and I
> would prefer this solution.

Tim & I were just going to create a tracker-common package and have
libtracker-sparql-2.0-0 depend on it. See our packaging at
https://salsa.debian.org/gnome-team/tracker and comment 30 at
https://bugs.debian.org/908800

Michael, if that sounds fine to you, I can upload that.

Thanks,
Jeremy Bicha

Processed: Re: Bug#910009: exim4-config: upgrade fails when trying to execute conffile difference visualizer

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 dpkg 1.19.1
Bug #910009 [exim4-config] exim4-config: upgrade fails when trying to execute 
conffile difference visualizer
Bug reassigned from package 'exim4-config' to 'dpkg'.
No longer marked as found in versions exim4/4.91-8.
Ignoring request to alter fixed versions of bug #910009 to the same values 
previously set
Bug #910009 [dpkg] exim4-config: upgrade fails when trying to execute conffile 
difference visualizer
Marked as found in versions dpkg/1.19.1.
> retitle -1 dpkg execs $PAGER with execvp instead of sh -c, yielding upgrade 
> failure
Bug #910009 [dpkg] exim4-config: upgrade fails when trying to execute conffile 
difference visualizer
Changed Bug title to 'dpkg execs $PAGER with execvp instead of sh -c, yielding 
upgrade failure' from 'exim4-config: upgrade fails when trying to execute 
conffile difference visualizer'.

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

Processed: Re: Bug#910009: exim4-config: upgrade fails when trying to execute conffile difference visualizer

[Debian Bug Tracking System]

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

> tags 910009 - moreinfo unreproducible
Bug #910009 [dpkg] dpkg execs $PAGER with execvp instead of sh -c, yielding 
upgrade failure
Removed tag(s) unreproducible and moreinfo.
>
End of message, stopping processing here.

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

Bug#910009: exim4-config: upgrade fails when trying to execute conffile difference visualizer

[Vincent Lefevre]

Control: reassign -1 dpkg 1.19.1
Control: retitle -1 dpkg execs $PAGER with execvp instead of sh -c, yielding 
upgrade failure

As a summary, when a pager needs to be invoked (e.g. for the
conffile difference visualizer), one gets an upgrade failure
if $PAGER contains the program name + options, as specified
by POSIX.

On 2018-10-01 14:12:20 +0200, Vincent Lefevre wrote:
> On 2018-10-01 14:08:17 +0200, Vincent Lefevre wrote:
> > A possible bug might be that $PAGER is run as a program name,
> > instead of something like system(), which allows options.
> 
> Hmm... I can see in /usr/share/doc/dpkg/changelog.Debian.gz that
> there have been pager-related changes in dpkg 1.19.1 (26 Sep 2018).
> The bug might actually be there.

Indeed, after a quick look at the code (pager_spawn in lib/dpkg/pager.c
and lib/dpkg/command.c code), this seems to be the case.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: tagging 910016

[Debian Bug Tracking System]

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

> tags 910016 + upstream fixed-upstream
Bug #910016 [python-django] python-django: CVE-2018-16984
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#910009: exim4-config: upgrade fails when trying to execute conffile difference visualizer

[Vincent Lefevre]

On 2018-10-01 14:08:17 +0200, Vincent Lefevre wrote:
> A possible bug might be that $PAGER is run as a program name,
> instead of something like system(), which allows options.

Hmm... I can see in /usr/share/doc/dpkg/changelog.Debian.gz that
there have been pager-related changes in dpkg 1.19.1 (26 Sep 2018).
The bug might actually be there.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#910009: exim4-config: upgrade fails when trying to execute conffile difference visualizer

[Vincent Lefevre]

On 2018-10-01 12:12:21 +0100, Adam D. Barratt wrote:
> On 2018-10-01 10:19, Vincent Lefevre wrote:
> > Package: exim4-config
> > Version: 4.91-8
> > Severity: grave
> > Justification: renders package unusable
> [...]
> > *** exim4.conf.template (Y/I/N/O/D/Z) [default=N] ? D
> > dpkg (subprocess): unable to execute conffile difference visualizer
> > (less -Lis): No such file or directory
> > dpkg: error processing package exim4-config (--configure):
> >  conffile difference visualizer subprocess returned error exit status 2
> 
> How is this possibly a bug in exim4-config? That package does not specify
> what command dpkg should use in order to page diffs.
> 
> Looking at the dpkg source code, it first checks $PAGER and if that's not
> set falls back to running the "pager" executable. That suggests one of two
> things:
> 
> - you have $PAGER set to "less -Lis" and for some reason don't have less
> available

It is set to "less -Lis", and I could check that it still works fine.
Note that I've used this value since December 2012 and had never had
any problem with it, including with the conffile difference visualizer:
the last time on this machine was on 2018-08-31, according to
/var/log/apt/term.log* files:

Log started: 2018-08-31  15:21:38
[...]
Installing new version of config file /etc/apparmor.d/abstractions/lightdm ...

Configuration file '/etc/lightdm/lightdm.conf'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** lightdm.conf (Y/I/N/O/D/Z) [default=N] ? D
[blank lines]
--- /etc/lightdm/lightdm.conf   2016-07-01 13:06:09.139950327 +0200
+++ /etc/lightdm/lightdm.conf.dpkg-new  2018-08-28 11:29:22.0 +0200
[...]

So, there doesn't seem to be anything wrong with my config.

> - your /usr/bin/pager alternative points to something that's not installed
> on your system.

Just in case, /usr/bin/pager works fine too (but since $PAGER is set,
this does not matter).

> 1) What is $PAGER set to in the environment in which you performed the
> upgrade?

less -Lis

> 2) What does /usr/bin/pager point to? (Please chase any symlinks to the
> ultmate endpoint)

/usr/bin/pager -> /etc/alternatives/pager
/etc/alternatives/pager -> /bin/less

> 3) How precisely did you invoke dpkg?

I used aptitude with its curses UI.

A possible bug might be that $PAGER is run as a program name,
instead of something like system(), which allows options.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#910016: python-django: CVE-2018-16984

[Chris Lamb]

Package: python-django
Version: 2:2.1.1-1
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for python-django.

CVE-2018-16984[0]:
Password hash disclosure to "view only" admin users

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16984
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16984


Regards,

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

Processed: Re: Bug#910009: exim4-config: upgrade fails when trying to execute conffile difference visualizer

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo unreproducible
Bug #910009 [exim4-config] exim4-config: upgrade fails when trying to execute 
conffile difference visualizer
Added tag(s) unreproducible and moreinfo.

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

Bug#910009: exim4-config: upgrade fails when trying to execute conffile difference visualizer

[Adam D. Barratt]

Control: tags -1 + moreinfo unreproducible

On 2018-10-01 10:19, Vincent Lefevre wrote:

Package: exim4-config
Version: 4.91-8
Severity: grave
Justification: renders package unusable

[...]

*** exim4.conf.template (Y/I/N/O/D/Z) [default=N] ? D
dpkg (subprocess): unable to execute conffile difference visualizer
(less -Lis): No such file or directory
dpkg: error processing package exim4-config (--configure):
 conffile difference visualizer subprocess returned error exit status 2


How is this possibly a bug in exim4-config? That package does not 
specify what command dpkg should use in order to page diffs.


Looking at the dpkg source code, it first checks $PAGER and if that's 
not set falls back to running the "pager" executable. That suggests one 
of two things:


- you have $PAGER set to "less -Lis" and for some reason don't have less 
available
- your /usr/bin/pager alternative points to something that's not 
installed on your system.


1) What is $PAGER set to in the environment in which you performed the 
upgrade?
2) What does /usr/bin/pager point to? (Please chase any symlinks to the 
ultmate endpoint)

3) How precisely did you invoke dpkg?

Regards,

Adam

Bug#910015: User is in the plugdev group

[積丹尼 Dan Jacobson]

Package: adb
Version: 1:8.1.0+r23-1~stage1.2
Severity: grave

$ id
uid=1000(jidanni) gid=1000(jidanni) 
groups=1000(jidanni),20(dialout),29(audio),46(plugdev),121(netdev),130(adb)
$ adb shell
error: insufficient permissions for device: user jidanni is not in the plugdev 
group
See [http://developer.android.com/tools/device.html] for more information

Bug#907806: How to disable tests for Python2 only?

[Andreas Tille]

Hi Yaroslav,

was this helpful for you?

Kind regards

  Andreas.

On Wed, Sep 26, 2018 at 01:06:38PM +0200, Andreas Tille wrote:
> 
> On Mon, Sep 24, 2018 at 11:32:03AM -0400, Yaroslav Halchenko wrote:
> > 
> > > I confirm that there are cases where this workflow makes sense.  We need
> > > to outweight pros and cons.
> > 
> > To say the truth, I am no longer sure since it is possible to still have
> > regular upstream repo as a remote and dedicated branches for them in the
> > same git repo (locally), so I could still cherry pick etc.  Pretty much
> > what I do eg for cython etc.
> > 
> > That is why I am agreeing to go "standard" so to make life easier for
> > others as well.
> 
> Sounds good. :-)
>  
> > My only concern with the "standard" workflow ATM is that pristine-tar is
> > not as reliable as needed to be. # of open issues manifests to that
> > https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=pristine-tar;dist=unstable
> > and Joey himself moved from using it to dgit AFAIK.  But anyways it is
> > unrelated to this discussion, sorry for bringing it up ;(
> 
> I admit that I'm a bit concerned about some kind of increasing orphanage
> of pristine-tar.  Luckily I personally had not faced any serious problem
> with it.  I simply hope that if we follow a standard that many people
> are using somebody will either take over and solve the problems if they
> become really hard or someone will develop some tool to switch to some
> new standard easily. ;-)
> 
> > > I hope I will find the time tomorrow or the day after tomorrow.
> > 
> > thanks
> 
> I have pushed scikit-learn 0.20~rc1+dfsg-1 to Git[1].  I tried to adapt
> all patches to the new upstream version (several were applied upstream).
> The one which excluded some tests accessing remote locations did not
> applied.  I added a comment and a FIXME string in case some other means
> might be needed as replacement.  I hope I did not messed up things.
> 
> The build starts but fails later with
> 
> ...
> x86_64-linux-gnu-gcc-ar: adding 40 object files to 
> build/temp.linux-x86_64-2.7/libcblas.a
> running build_ext
> customize UnixCCompiler
> customize UnixCCompiler using build_ext
> customize UnixCCompiler
> customize UnixCCompiler using build_ext
> building 'sklearn.__check_build._check_build' extension
> compiling C sources
> C compiler: x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -g -O2 
> -fdebug-prefix-map=/build/scikit-learn-0.20~rc1+dfsg=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC
> 
> creating build/temp.linux-x86_64-2.7/sklearn/__check_build
> compile options: '-I/usr/lib/python2.7/dist-packages/numpy/core/include 
> -I/usr/lib/python2.7/dist-packages/numpy/core/include 
> -I/usr/include/python2.7 -c'
> x86_64-linux-gnu-gcc: sklearn/__check_build/_check_build.c
> x86_64-linux-gnu-gcc: error: sklearn/__check_build/_check_build.c: No such 
> file or directory
> x86_64-linux-gnu-gcc: fatal error: no input files
> compilation terminated.
> x86_64-linux-gnu-gcc: error: sklearn/__check_build/_check_build.c: No such 
> file or directory
> x86_64-linux-gnu-gcc: fatal error: no input files
> compilation terminated.
> 
> 
> I admit I need to give up here and trust your insight that you will be
> able to deal with this.
> 
> BTW, I'm wondering whether the code copy of atlas/lapack in
> sklearn/src/cblas will be really needed - but for the moment I think
> we should concentrate to get the package out at all before we care
> about code copies.
>  
> > > I'll check what might be the easier solution and will come back once I
> > > did so.  Hopefully you will have solved the ssh issue meanwhile. 
> > 
> > I will try again later today, and when home (different network/provider)
> 
> Hope this works now
> 
>Andreas.
> 
> 
> [1] https://salsa.debian.org/science-team/scikit-learn 
> 
> -- 
> http://fam-tille.de
> 
> 

-- 
http://fam-tille.de

Bug#885657: rarian: Don't release with Buster

[Ivo De Decker]

Hi,

On Sun, Sep 30, 2018 at 09:44:39AM -0400, Jeremy Bicha wrote:
> On Sun, Sep 30, 2018 at 2:54 AM Niels Thykier  wrote:
> > FYI: There are still ~15-16 open bugs on the bts tagged rarian (I have
> > made them blockers via a separate update).  If the plan is still to
> > remove rarian for Buster, these bugs should be resolved before the
> > transition freeze (2019-01-12).
> 
> Thanks for the reminder. We basically just need someone to write the
> patches for this packages (several of the remaining packages need
> their buildsystem modified a bit).
> 
> I don't think anyone has worked on this recently so it might not get
> done in time for Buster, but it's still an achievable goal now.

Most of the blocking bugs are currently 'important'. If you want to get this
done for buster, it's probably a good idea to upgrade them to serious.

Looking at the rdeps, the main blocker is synaptic. If you can get a fix for
that one, the rest can probably be (auto-) removed if really necessary. 

Ivo

Bug#909999: ghostscript (via pdf2ps) crashes on most inputs following upgrade to 9.06~dfsg-2+deb8u9

[Markus Koschany]

Am 01.10.18 um 06:13 schrieb Berkeley Roshan Churchill:
> Package: ghostscript
> Version: 9.06~dfsg-2+deb8u9
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> 
> Ghostscript was upgraded to 9.06~dfsg-2+deb8u9
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> I tried running 'pdf2ps ' on several PDF files, and in
> several cases it failed. Attached is a file, bug.pdf, that illustrates
> this problem. However, pdf2ps generally worked before the ghostscript
> upgrade.

[...]

Thank you for reporting this issue. I believe I have identified the
problem and I will release an update that fixes it shortly. This bug was
caused by an incomplete fix for CVE-2018-16543. In CVE-2018-16543.patch
the line

0 mark /PageSize currentdevice /PageSize //.gsgetdeviceprop .dicttomark

had to be changed to

0 mark /PageSize currentdevice /PageSize //.gsgetdeviceprop exec .dicttomark

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#908277: marked as done (wtforms: FTBFS (failing tests))

[Debian Bug Tracking System]

Your message dated Mon, 01 Oct 2018 10:20:51 +
with message-id 
and subject line Bug#908277: fixed in wtforms 2.2.1-1
has caused the Debian Bug report #908277,
regarding wtforms: FTBFS (failing tests)
to be marked as done.

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

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


-- 
908277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:wtforms
Version: 2.1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with sphinxdoc,python2,python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_py

[... snipped ...]

make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
python-coverage run tests/runtests.py
### Disabled test 'ext_django.tests', dependency not found
..FF.
==
FAIL: test_formatting (locale_babel.TestLocaleDecimal)
--
Traceback (most recent call last):
  File "/<>/tests/locale_babel.py", line 49, in test_formatting
self._format_test("-12'345.2", '-12345.2', ['de_CH'])
  File "/<>/tests/locale_babel.py", line 23, in _format_test
self.assertEqual(form.a._value(), expected)
AssertionError: u'-12\u2019345.2' != u"-12'345.2"
- -12\u2019345.2
?^
+ -12'345.2
?^


==
FAIL: test_parsing (locale_babel.TestLocaleDecimal)
--
Traceback (most recent call last):
  File "/<>/tests/locale_babel.py", line 77, in test_parsing
self._parse_test("1'23'456.789", expected, ['de_CH'])
  File "/<>/tests/locale_babel.py", line 59, in _parse_test
raw_val, form.a.errors,
AssertionError: Expected value u"1'23'456.789" to parse as a decimal, instead 
got [u'Keine g\xfcltige Dezimalzahl']

--
Ran 177 tests in 0.379s

FAILED (failures=2)
make[1]: *** [debian/rules:12: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:9: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


That's from my autobuilder, but it also fails here:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: wtforms
Source-Version: 2.2.1-1

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated wtforms 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 01 Oct 2018 12:03:57 +0200
Source: wtforms
Binary: python-wtforms python3-wtforms python-wtforms-doc
Architecture: source
Version: 2.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Christoph Berg 
Description:
 python-wtforms - flexible forms validation and rendering 

Bug#909988: marked as done (ironic: FTBFS (Failures during discovery))

[Debian Bug Tracking System]

Your message dated Mon, 01 Oct 2018 10:05:33 +
with message-id 
and subject line Bug#909988: fixed in ironic 1:11.1.0-4
has caused the Debian Bug report #909988,
regarding ironic: FTBFS (Failures during discovery)
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.)


-- 
909988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ironic
Version: 1:11.1.0-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python3,sphinxdoc,systemd
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_autoreconf -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
dh_auto_configure: Please use the third-party "pybuild" build system instead of 
python-distutils
dh_auto_configure: This feature will be removed in compat 12.
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions

[... snipped ...]

+ PKGOS_USE_PY3=yes
+ PKGOS_TEST_PARALLEL=yes
+ PYTHONS=disabled
+ PYTHON3S=disabled
+ TEST_PARALLEL_OPT=--parallel
+ PKGOS_USE_PY2=no
+ shift
+ [ no = yes ]
+ [ yes = yes ]
+ py3versions -vr
+ PYTHON3S=3.7 3.6
+ [ yes = no ]
+ [ disabled = disabled ]
+ continue
+ [ 3.7 = disabled ]
+ cut -d. -f1
+ echo 3.7
+ PYMAJOR=3
+ echo ===> Testing with python (python3)
===> Testing with python (python3)
+ [ 3 = 3 ]
+ pwd
+ [ -d /<>/debian/tmp/usr/lib/python3/dist-packages ]
+ [ -z  ]
+ pwd
+ export PYTHONPATH=/<>/debian/tmp/usr/lib/python3/dist-packages
+ [ -e .stestr.conf ]
+ rm -rf .stestr
+ subunit2pyunit
+ PYTHON=python3.7 python3-stestr run --subunit 
ironic\.tests\.unit\.(?!(.*api\.controllers\.v1\.test_chassis\.TestPost\.test_create_chassis_unicode_description.*))

=
Failures during discovery
=
b'--- stdout ---\n2018-09-27 16:06:32.223 18596 INFO keyring.backend [-] 
Loading KWallet\x1b[00m\n2018-09-27 16:06:32.239 18596 INFO keyring.backend [-] 
Loading SecretService\x1b[00m\n2018-09-27 16:06:32.245 18596 INFO 
keyring.backend [-] Loading Windows\x1b[00m\n2018-09-27 16:06:32.247 18596 INFO 
keyring.backend [-] Loading macOS\x1b[00m\n--- import errors ---\nFailed to 
import test module: ironic.tests.unit.drivers.modules.irmc.test_bios\nTraceback 
(most recent call last):\n  File 
"/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path\nmodule = self._get_module_from_name(name)\n  File 
"/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name\n__import__(name)\n  File 
"/<>/ironic/tests/unit/drivers/modules/irmc/test_bios.py", line 
29, in \nclass IRMCBIOSTestCase(test_common.BaseIRMCTest):\n  File 
"/<>/ironic/tests/unit/drivers/modules/irmc/test_bios.py", line 
41, in IRMCBIOSTestC
 ase\n@mock.patch.object(irmc_bios.irmc.elcm, 
\'set_bios_configuration\',\nAttributeError: \'NoneType\' object has no 
attribute \'elcm\'\n'

The above traceback was encountered during test discovery which imports all the 
found test modules in the specified test_path.

--
Ran 0 tests in 9.345s

OK
+ python3-stestr slowest
make[1]: *** [debian/rules:31: override_dh_install] Error 3
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- 

Processed: Bug #909988 in ironic marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #909988 [src:ironic] ironic: FTBFS (Failures during discovery)
Added tag(s) pending.

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

Bug#909988: Bug #909988 in ironic marked as pending

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #909988 in ironic reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/openstack-team/services/ironic/commit/d86561f185e43a4f1afb7c5a4671545c07d8b173


Remove Fujitsu BIOS test file (Closes: #909988).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/909988

Bug#909999: ghostscript (via pdf2ps) crashes on most inputs following upgrade to 9.06~dfsg-2+deb8u9

[Samuel Wolf]

This issue is much bigger than i guess, most of our printes stop working:
[...]
D [01/Oct/2018:10:19:47 +0200] [Job 58179] Started filter gs (PID 32513)
D [01/Oct/2018:10:19:47 +0200] [Job 58179] Started filter pstops (PID 32514)
D [01/Oct/2018:10:19:47 +0200] [Job 58179] GPL Ghostscript 9.06:
Unrecoverable error, exit code 1
[...]

We downgrade now to:
ghostscript_9.06~dfsg-2+deb8u8_amd64.deb
libgs9_9.06~dfsg-2+deb8u8_amd64.deb
libgs9-common_9.06~dfsg-2+deb8u8_all.deb

Bug#910009: exim4-config: upgrade fails when trying to execute conffile difference visualizer

[Vincent Lefevre]

Package: exim4-config
Version: 4.91-8
Severity: grave
Justification: renders package unusable

I got the following error:

Setting up exim4-config (4.91-8) ...
Installing new version of config file 
/etc/exim4/conf.d/acl/30_exim4-config_check_rcpt ...
Installing new version of config file 
/etc/exim4/conf.d/main/01_exim4-config_listmacrosdefs ...

Configuration file '/etc/exim4/exim4.conf.template'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** exim4.conf.template (Y/I/N/O/D/Z) [default=N] ? D
dpkg (subprocess): unable to execute conffile difference visualizer (less 
-Lis): No such file or directory
dpkg: error processing package exim4-config (--configure):
 conffile difference visualizer subprocess returned error exit status 2

This ended with:

Errors were encountered while processing:
 exim4-config
 exim4-base
 exim4
 exim4-daemon-light
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- Package-specific info:
Exim version 4.91 #4 built 29-Sep-2018 17:08:52
Copyright (c) University of Cambridge, 1995 - 2018
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2018
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DANE DKIM DNSSEC 
Event OCSP PRDR SOCKS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Configuration file is /var/lib/exim4/config.autogenerated
# /etc/exim4/update-exim4.conf.conf
#
# Edit this file and /etc/mailname by hand and execute update-exim4.conf
# yourself or use 'dpkg-reconfigure exim4-config'
#
# Please note that this is _not_ a dpkg-conffile and that automatic changes
# to this file might happen. The code handling this will honor your local
# changes, so this is usually fine, but will break local schemes that mess
# around with multiple versions of the file.
#
# update-exim4.conf uses this file to determine variable values to generate
# exim configuration macros for the configuration file.
#
# Most settings found in here do have corresponding questions in the
# Debconf configuration, but not all of them.
#
# This is a Debian specific file

dc_eximconfig_configtype='internet'
dc_other_hostnames='cventin.lip.ens-lyon.fr'
dc_local_interfaces='127.0.0.1 ; ::1'
dc_readhost=''
dc_relay_domains=''
dc_minimaldns='false'
dc_relay_nets=''
dc_smarthost=''
CFILEMODE='644'
dc_use_split_config='false'
dc_hide_mailname=''
dc_mailname_in_oh='true'
dc_localdelivery='maildir_home'
mailname:cventin.lip.ens-lyon.fr
# /etc/default/exim4
EX4DEF_VERSION=''

# 'combined' -   one daemon running queue and listening on SMTP port
# 'no'   -   no daemon running the queue
# 'separate' -   two separate daemons
# 'ppp'  -   only run queue with /etc/ppp/ip-up.d/exim4.
# 'nodaemon' - no daemon is started at all.
# 'queueonly' - only a queue running daemon is started, no SMTP listener.
# setting this to 'no' will also disable queueruns from /etc/ppp/ip-up.d/exim4
QUEUERUNNER='combined'
# how often should we run the queue
QUEUEINTERVAL='5m'
# options common to quez-runner and listening daemon
COMMONOPTIONS=''
# more options for the daemon/process running the queue (applies to the one
# started in /etc/ppp/ip-up.d/exim4, too.
QUEUERUNNEROPTIONS=''
# special flags given to exim directly after the -q. See exim(8)
QFLAGS=''
# Options for the SMTP listener daemon. By default, it is listening on
# port 25 only. To listen on more ports, it is recommended to use
# -oX 25:587:10025 -oP /var/run/exim4/exim.pid
SMTPLISTENEROPTIONS=''

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

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

Versions of packages exim4-config depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.69

exim4-config recommends no packages.

exim4-config suggests no packages.

-- Configuration Files:
/etc/exim4/exim4.conf.template changed:
exim_path = /usr/sbin/exim4
.ifndef 

Bug#909973: marked as done (remove unneeded dependency on backports.ssl-match-hostname)

[Debian Bug Tracking System]

Your message dated Mon, 01 Oct 2018 09:20:21 +
with message-id 
and subject line Bug#909973: fixed in websocket-client 0.53.0-1
has caused the Debian Bug report #909973,
regarding remove unneeded dependency on backports.ssl-match-hostname
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.)


-- 
909973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:backports.ssl-match-hostname
Version: 3.5.0.1-1
Severity: important
Tags: sid buster

The python3 and python2 versions already have that fix (and had it in stretch
too).  This package should  be removed for the buster release.
--- End Message ---
--- Begin Message ---
Source: websocket-client
Source-Version: 0.53.0-1

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated 
websocket-client package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 01 Oct 2018 10:54:13 +0200
Source: websocket-client
Binary: python-websocket python3-websocket
Architecture: source
Version: 0.53.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Christoph Berg 
Description:
 python-websocket - WebSocket client library - Python 2.7
 python3-websocket - WebSocket client library - Python 3.x
Closes: 909973
Changes:
 websocket-client (0.53.0-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * Convert git repository from git-dpm to gbp layout
 .
   [ Christoph Berg ]
   * New upstream version.
   * Remove python-backports.ssl-match-hostname dependency. (Closes: #909973)
Checksums-Sha1:
 47d631c732853c2d51f15c01cf97c524bafc6a2c 2231 websocket-client_0.53.0-1.dsc
 09bd8914944646fde9d2672392579a982ea0f031 43276 
websocket-client_0.53.0.orig.tar.gz
 18be8c34b3ae334ef6ad4ffde10cff99483a60c3 8116 
websocket-client_0.53.0-1.debian.tar.xz
Checksums-Sha256:
 00b02e18a9f37f0a07a4ee84fede399182bea686cc626084283cf9d8b2498187 2231 
websocket-client_0.53.0-1.dsc
 c42b71b68f9ef151433d6dcc6a7cb98ac72d2ad1e3a74981ca22bc5d9134f166 43276 
websocket-client_0.53.0.orig.tar.gz
 18c9b25dc95656c052dee38ecbac86d8a50f3119b77ad9c905aee27b93f7770a 8116 
websocket-client_0.53.0-1.debian.tar.xz
Files:
 bfcf6b5d470dc0216c55bec57b5893c4 2231 python optional 
websocket-client_0.53.0-1.dsc
 e1700953d5daef5706c527dbb4b5edef 43276 python optional 
websocket-client_0.53.0.orig.tar.gz
 044a3049e5c821c0b6322da97faa9bf0 8116 python optional 
websocket-client_0.53.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlux4R4ACgkQTFprqxLS
p65qzA//XkwzGaLoI8rxTjhkg6VXkzUMyupgfURzy1OlrKxuMGi5iSqTWQAgHU7t
wDITYltdNvkhey8NofdhuxB5z+74rmuXibcbjqR8rQnX2V0K/V5tb4QTsHzm2Rxd
6lyYoo6ey7fHHB6bTuHO9U/rA3M30pBXE8QwUxRNZIdFslV9ztVJq9w8MAurdzUv
Qg6sZPTZWTfRyXr+IWYF7vKPffQmMVjZYtCq6PCOgW83g5gv/4d3xFrkT4HHjv44
dW+hBu1Lc3chxwoqgGGQ9kU74mFNYi0Tj3IcxZ3673RzJ0mSTaqRMzZKh87kcCt0
lS+DpJ+Yed9On7+Sp/cegaJXwRt/VTyJs8BHiQzsKJxBuJqWACXaY4buSALHbLpU
j2fPcAGRBJHFKAXiPC8LpIE43qm+9AjTrtL3XAdRo1ueU5nULNEjJt55hc1U0FTM
0VE2tFdOgelkR+qCYJxcWNenEg46TJoN4zXk8KOQ1FTH8aL2pef00gIYYSVrZcH8
Khf6I5eWJ8wdmr8eHANv1XLip0OaUiqE7Ryo383BSM5GvuTvYlF/wS+1y+OcbhXO
UNiEYmWogzUrkNMsM+WQUcgG1OHmHuOGF3zQBtajNgeIyiDciJn1MamWxfVwLxuq
fn9j1aKWrsMm2P5fBHqjuecvuREi90u9bSQl98S4vynqeqwK7KI=
=pNDd
-END PGP SIGNATURE End Message ---

Bug#909999: ghostscript (via pdf2ps) crashes on most inputs following upgrade to 9.06~dfsg-2+deb8u9

[Samuel Wolf]

Unfortunately same issue here with convert and 9.06~dfsg-2+deb8u9, any
chance to fix this?

convert -density 300 ws.pdf -depth 8 scan.jpeg
[...]
GPL Ghostscript 9.06: Unrecoverable error, exit code 1
convert: no images defined `scan.jpeg' @
error/convert.c/ConvertImageCommand/3210.

Samuel

Bug#909973: Bug #909973 in websocket-client marked as pending

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #909973 in websocket-client reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/websocket-client/commit/f1e737a762c8d9472bd3c57187bc75954490a9a0


Remove python-backports.ssl-match-hostname dependency. (Closes: #909973)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/909973

Bug#910008: haskell-mtl: Package libghc-mtl-dev not co-installable with ghc due to file conflicts

[John Paul Adrian Glaubitz]

Source: haskell-mtl
Version: 2.2.2-2
Severity: serious
Justification: renders package unusable

Hello!

The the libghc-mtl-dev package is currently not co-installable with the
ghc package due to file conflicts:

root@epyc:~> apt update && apt  install libghc-mtl-dev ghc
Get:1 http://ftp.de.debian.org/debian unstable InRelease [233 kB]
Get:2 http://incoming.ports.debian.org/buildd unstable InRelease [49.1 kB]
Get:3 http://ftp.de.debian.org/debian experimental InRelease [101 kB]
Get:4 http://ftp.de.debian.org/debian-ports unstable InRelease [47.1 kB]
   
Get:5 http://ftp.de.debian.org/debian-ports unreleased InRelease [52.4 kB]
Get:6 http://ftp.de.debian.org/debian unstable/main Sources.diff/Index [27.9 kB]
Get:7 http://ftp.de.debian.org/debian unstable/non-free Sources.diff/Index 
[27.8 kB]
Get:8 http://ftp.de.debian.org/debian unstable/main i386 Packages.diff/Index 
[27.9 kB]
Get:9 http://ftp.de.debian.org/debian unstable/main amd64 Packages.diff/Index 
[27.9 kB]
Get:10 http://ftp.de.debian.org/debian unstable/main i386 Contents 
(deb).diff/Index [28.0 kB]
Get:11 http://ftp.de.debian.org/debian unstable/main amd64 Contents 
(deb).diff/Index [28.0 kB]
Get:12 http://ftp.de.debian.org/debian unstable/main Sources 
2018-10-01-0215.35.pdiff [224 kB]
Get:13 http://ftp.de.debian.org/debian unstable/main Sources 
2018-10-01-0815.09.pdiff [3,947 B]
Get:13 http://ftp.de.debian.org/debian unstable/main Sources 
2018-10-01-0815.09.pdiff [3,947 B]
Get:14 http://ftp.de.debian.org/debian unstable/non-free Sources 
2018-10-01-0215.35.pdiff [764 B]
Get:14 http://ftp.de.debian.org/debian unstable/non-free Sources 
2018-10-01-0215.35.pdiff [764 B]
Get:15 http://ftp.de.debian.org/debian unstable/main i386 Packages 
2018-10-01-0215.35.pdiff [4,227 B]
Get:16 http://ftp.de.debian.org/debian unstable/main i386 Packages 
2018-10-01-0815.09.pdiff [36.3 kB]  
Get:16 http://ftp.de.debian.org/debian unstable/main i386 Packages 
2018-10-01-0815.09.pdiff [36.3 kB]
Get:17 http://ftp.de.debian.org/debian unstable/main amd64 Packages 
2018-10-01-0215.35.pdiff [42.9 kB]
Get:18 http://ftp.de.debian.org/debian unstable/main amd64 Packages 
2018-10-01-0815.09.pdiff [33.4 kB]  
Get:18 http://ftp.de.debian.org/debian unstable/main amd64 Packages 
2018-10-01-0815.09.pdiff [33.4 kB]
Get:19 http://ftp.de.debian.org/debian unstable/main i386 Contents (deb) 
2018-10-01-0215.35.pdiff [12.5 kB]  
Get:20 http://ftp.de.debian.org/debian unstable/main i386 Contents (deb) 
2018-10-01-0815.09.pdiff [23.7 kB]
Get:20 http://ftp.de.debian.org/debian unstable/main i386 Contents (deb) 
2018-10-01-0815.09.pdiff [23.7 kB]  
Get:21 http://ftp.de.debian.org/debian unstable/main amd64 Contents (deb) 
2018-10-01-0215.35.pdiff [27.3 kB]  

Get:22 http://ftp.de.debian.org/debian unstable/main amd64 Contents (deb) 
2018-10-01-0815.09.pdiff [21.0 kB]  
 
Get:22 http://ftp.de.debian.org/debian unstable/main amd64 Contents (deb) 
2018-10-01-0815.09.pdiff [21.0 kB]  
 
Get:23 http://ftp.de.debian.org/debian experimental/main amd64 
Packages.diff/Index [27.8 kB]   

Get:24 http://ftp.de.debian.org/debian experimental/main amd64 Contents 
(deb).diff/Index [27.9 kB]  
   
Get:25 http://ftp.de.debian.org/debian experimental/main amd64 Packages 
2018-10-01-0215.35.pdiff [704 B]
   
Get:25 http://ftp.de.debian.org/debian experimental/main amd64 Packages 
2018-10-01-0215.35.pdiff [704 B]
   
Get:26 http://ftp.de.debian.org/debian experimental/main amd64 Contents (deb) 
2018-10-01-0215.35.pdiff [317 B]
 
Get:26 http://ftp.de.debian.org/debian experimental/main amd64 Contents (deb) 
2018-10-01-0215.35.pdiff [317 B]
 
Get:27 http://ftp.de.debian.org/debian unstable/main all Packages [4,320 kB]

   
Get:28 http://incoming.ports.debian.org/buildd unstable/main m68k Packages [175 
kB] 
   
Get:29 http://incoming.ports.debian.org/buildd unstable/main sh4 Packages [175 
kB] 

Get:30 http://incoming.ports.debian.org/buildd unstable/main x32 Packages [241 
kB]

Processed: Bug #909973 in websocket-client marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #909973 [websocket-client] remove unneeded dependency on 
backports.ssl-match-hostname
Added tag(s) pending.

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

Processed: Bug #908800 in tracker marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #908800 [libtracker-sparql-2.0-0] nautilus: can't use nautilus without 
tracker
Bug #909375 [libtracker-sparql-2.0-0] nautilus: Trace/breakpoint trap
Added tag(s) pending.
Added tag(s) pending.

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

Bug#908800: Bug #908800 in tracker marked as pending

[Tim Lunn]

Control: tag -1 pending

Hello,

Bug #908800 in tracker reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/tracker/commit/a9f531033ec05a4c0cc883754f727fe1513e5cc8


Split out common files into tracker-common (Closes: #908800)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/908800

Bug#909989: marked as done (keystone: FTBFS (failing tests))

[Debian Bug Tracking System]

Your message dated Mon, 01 Oct 2018 07:51:27 +
with message-id 
and subject line Bug#909989: fixed in keystone 2:14.0.0-2
has caused the Debian Bug report #909989,
regarding keystone: FTBFS (failing tests)
to be marked as done.

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

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


-- 
909989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:keystone
Version: 2:14.0.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python3,sphinxdoc,systemd
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_autoreconf -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
dh_auto_configure: Please use the third-party "pybuild" build system instead of 
python-distutils
dh_auto_configure: This feature will be removed in compat 12.
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions

[... snipped ...]

  File "/<>/keystone/common/sql/upgrades.py", line 62, in upgrade
self.schema_.runchange(ver, change, changeset.step)
  File "/usr/lib/python3/dist-packages/migrate/versioning/schema.py", line 93, 
in runchange
change.run(self.engine, step)
  File "/usr/lib/python3/dist-packages/migrate/versioning/script/py.py", line 
148, in run
script_func(engine)
  File 
"/<>/keystone/common/sql/contract_repo/versions/013_contract_protocol_cascade_delete_for_federated_user.py",
 line 26, in upgrade
refcolumns=[protocol_table.c.id, protocol_table.c.idp_id]).drop()
  File "/usr/lib/python3/dist-packages/migrate/changeset/constraint.py", line 
59, in drop
self.__do_imports('constraintdropper', *a, **kw)
  File "/usr/lib/python3/dist-packages/migrate/changeset/constraint.py", line 
32, in __do_imports
run_single_visitor(engine, visitorcallable, self, *a, **kw)
  File "/usr/lib/python3/dist-packages/migrate/changeset/databases/visitor.py", 
line 85, in run_single_visitor
fn(element, **kwargs)
  File "/usr/lib/python3/dist-packages/migrate/changeset/databases/sqlite.py", 
line 204, in visit_migrate_foreign_key_constraint
self.recreate_table(p[0].table, omit_constraints=[p[0].name])
  File "/usr/lib/python3/dist-packages/migrate/changeset/databases/sqlite.py", 
line 100, in recreate_table
self.execute()
  File "/usr/lib/python3/dist-packages/migrate/changeset/ansisql.py", line 44, 
in execute
return self.connection.execute(self.buffer.getvalue())
  File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 942, in 
execute
return self._execute_text(object, multiparams, params)
  File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1104, 
in _execute_text
statement, parameters
  File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1200, 
in _execute_context
context)
  File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1409, 
in _handle_dbapi_exception
util.raise_from_cause(newraise, exc_info)
  File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 203, in 
raise_from_cause
reraise(type(exception), exception, tb=exc_tb, cause=cause)
  File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 186, in 
reraise
raise value.with_traceback(tb)
  File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1193, 
in _execute_context
context)
  File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 508, 
in do_execute
cursor.execute(statement, parameters)
oslo_db.exception.DBNonExistentTable: (sqlite3.OperationalError) error in 
trigger federated_user_insert_trigger: no such table: main.migration_tmp [SQL: 
'ALTER TABLE federated_user RENAME TO migration_tmp'] (Background on this error 
at: http://sqlalche.me/e/e3q8)


--
Ran 5575 tests in 3360.083s

FAILED (failures=17, skipped=831)
make[1]: *** [debian/rules:55: override_dh_install] Error 1

Bug#909989: Bug #909989 in keystone marked as pending

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #909989 in keystone reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/openstack-team/services/keystone/commit/ab1b6e76af2604579a9b2eea667ac400f335b940


  * Do not run keystone.tests.unit.test_sql_upgrade tests, as it looks like
broken if using SQLite (Closes: #909989).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/909989

Processed: Bug #909989 in keystone marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #909989 [src:keystone] keystone: FTBFS (failing tests)
Added tag(s) pending.

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

Bug#909938: marked as done (spdlog FTBFS on armel/mips/mipsel: undefined reference to __atomic_load_8)

[Debian Bug Tracking System]

Your message dated Mon, 01 Oct 2018 07:05:44 +
with message-id 
and subject line Bug#909938: fixed in spdlog 1:1.1.0-2
has caused the Debian Bug report #909938,
regarding spdlog FTBFS on armel/mips/mipsel: undefined reference to 
__atomic_load_8
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.)


-- 
909938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spdlog
Version: 1:1.1.0-1
Severity: serious
Tags: patch ftbfs

https://buildd.debian.org/status/package.php?p=spdlog=sid

...
[ 68%] Linking CXX executable latency
cd /<>/obj-arm-linux-gnueabi/bench && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/latency.dir/link.txt --verbose=1
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wl,-z,relro -rdynamic 
CMakeFiles/latency.dir/latency.cpp.o  -o latency -lpthread 
/usr/bin/ld: CMakeFiles/latency.dir/latency.cpp.o: in function `bench_mt(int, 
std::shared_ptr, int)':
/usr/include/c++/8/bits/atomic_base.h:396: undefined reference to 
`__atomic_load_8'
/usr/bin/ld: CMakeFiles/latency.dir/latency.cpp.o: in function 
`std::thread::_State_impl, int)::{lambda()#1}> > >::_M_run()':
/usr/include/c++/8/bits/atomic_base.h:312: undefined reference to 
`__atomic_fetch_add_8'
collect2: error: ld returned 1 exit status
make[3]: *** [bench/CMakeFiles/latency.dir/build.make:87: bench/latency] Error 1


Fix:

--- debian/rules.old2018-09-30 09:29:49.388250919 +
+++ debian/rules2018-09-30 09:36:01.654652659 +
@@ -1,5 +1,9 @@
 #!/usr/bin/make -f
 
+ifneq (,$(filter $(DEB_HOST_ARCH), armel m68k mips mipsel powerpc powerpcspe 
sh4))
+  export DEB_LDFLAGS_MAINT_APPEND=-latomic
+endif
+
 %:
dh $@
 
--- End Message ---
--- Begin Message ---
Source: spdlog
Source-Version: 1:1.1.0-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated spdlog package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 01 Oct 2018 08:31:40 +0200
Source: spdlog
Binary: libspdlog-dev
Architecture: source
Version: 1:1.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libspdlog-dev - Very fast, header only, C++ logging library
Closes: 909938
Changes:
 spdlog (1:1.1.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Drop debian/gdb.conf (specifying only defaults)
   * Fix build on several architectures (Thanks for the patch to
 Adrian Bunk )
 Closes: #909938
Checksums-Sha1:
 3569ec50f94d9e757d6c59f378e9c8941c96 1966 spdlog_1.1.0-2.dsc
 043e41e0255f1f799ba1c22553ba98e834c9ba8c 3608 spdlog_1.1.0-2.debian.tar.xz
Checksums-Sha256:
 f7ddb84a6d48227afeadc0146a4fde449fe00cc7cb85c239fe6ba65cf3709e51 1966 
spdlog_1.1.0-2.dsc
 e1f944b6e3ab280074fe289db4f6b26e92c353b4cdecd3e1325b4c6ba3a0bbb0 3608 
spdlog_1.1.0-2.debian.tar.xz
Files:
 697eaf48b69917c8f912649cbfc81913 1966 libdevel optional spdlog_1.1.0-2.dsc
 635506717a2d24a7d8c4971783e03e55 3608 libdevel optional 
spdlog_1.1.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAluxwzYRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGbIA//Sn7GhbwHm0oXQaLA4ywDRw/0sO8aFkh9
ZC+F3fz+mmwIDicejf7wUgunO97Fw/w3MgqOGg3k7yC8SpSEWcFsz7FkDVlgOrkb
VRp5k+ctxvckd8JjN2vWPBIZ5/m0MC4UW739CKgx2/TnN44ebgwD4yA0v0aUUhRm
1pQSYpvO33IpCYYyB52ZfL9WBIhAW1dpLa2L3ASxvq1r45thNLpQ+uDeETbcod6c
0Dl/q8KPlS1cJNkE1UxvcMkFfivd7wdKPhvwBwGiYpvkFRyX82qIcEQrW7fQvlcQ
4DT/6LX9c9wpaF08xixQAhIiR3TGB2c78bbVDxgLPsfdwxDRa3p7r3Wh8/UkIlFW
9smrmjjfYSAVFs0Fhb7cFtZc1EIDsOD9LhmbOm4TxhbbTw/QFbTLtushQnOe7wVm
/g64BsbiJgyhJU74nyRaewbDjq1saKOhYaONb51pMcQTZiYsq5nSppYDfs6Jxv0d
N2W/Q3dP34fDqwX3+z4QMIecrjs4li+KEYMkE/AkKblUWFQsRepM6A4kGhHYgghK
pl6hTNJlF0pyjxeLGTXF3mchDYfMFal+oap9+pjqVlsjLyvANAIu6yX/27Mmx/mN
jtGBCcnS3hT0MkTkuYHYBR4HMB9Or4iIhLaXim7yuZxo9JFW3UNOzjr7MN26YjEB
+8dhcYvnldg=
=rIex
-END PGP 

Bug#908970: marked as done (spamassassin: CVE-2018-11780: potential remote code execution bug with the PDFInfo plugin)

[Debian Bug Tracking System]

Your message dated Mon, 01 Oct 2018 07:05:38 +
with message-id 
and subject line Bug#908970: fixed in spamassassin 3.4.2-1
has caused the Debian Bug report #908970,
regarding spamassassin: CVE-2018-11780: potential remote code execution bug 
with the PDFInfo plugin
to be marked as done.

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

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


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

Hi,

The following vulnerability was published for spamassassin.

CVE-2018-11780[0]:
potential remote code execution bug with the PDFInfo plugin

It is fixed in new upstream version 3.4.2.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-11780
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11780
[1] https://www.openwall.com/lists/oss-security/2018/09/16/1

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: spamassassin
Source-Version: 3.4.2-1

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

Debian distribution maintenance software
pp.
Noah Meyerhans  (supplier of updated spamassassin 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, 30 Sep 2018 23:44:58 -0700
Source: spamassassin
Binary: spamassassin spamc sa-compile
Architecture: source all amd64
Version: 3.4.2-1
Distribution: unstable
Urgency: medium
Maintainer: Noah Meyerhans 
Changed-By: Noah Meyerhans 
Description:
 sa-compile - Tools for compiling SpamAssassin rules into C
 spamassassin - Perl-based spam filter using text analysis
 spamc  - Client for SpamAssassin spam filtering daemon
Closes: 858457 865924 883775 884163 889501 890650 891041 891833 908969 908970 
908971
Changes:
 spamassassin (3.4.2-1) unstable; urgency=medium
 .
   * New upstream release fixes multiple security vulnerabilities
 - CVE-2017-15705: Denial of service issue in which certain unclosed
   tags in emails cause markup to be handled incorrectly leading to
   scan timeouts. (Closes: 908969)
 - CVE-2016-1238: Unsafe usage of "." in @INC in a configuration
   script.
 - CVE-2018-11780: potential Remote Code Execution bug with the
   PDFInfo plugin. (Closes: 908970)
 - CVE-2018-11781: local user code injection in the meta rule syntax.
   (Closes: 908971)
 - BayesStore: bayes_expire table grows, remove_running_expire_tok not
   called (Closes: 883775)
 - Fix use of uninitialized variable warning in PDFInfo.pm
   (Closes: 865924)
 - Fix "failed to parse plugin" error in
   Mail::SpamAssassin::Plugin::URILocalBL (Closes: 891041)
   * Don't recursively chown /var/lib/spamassassin during postinst.
 (Closes: 889501)
   * Reload spamd after compiling rules in sa-compile.postinst.
   * Preserve locally set ENABLED=1 setting from /etc/default/spamassassin
 when installing on systemd-based systems. (Closes: 884163, 858457)
   * Update SysV init script to cope with upstream's change to $0.
   * Remove compiled rules upon removal of the sa-compile package.
   * Ensure that /var/lib/spamassassin/compiled doesn't change modes with
 the cron job's execution. (Closes: 890650)
   * Update standards version to 4.2.1
   * Create /var/lib/spamassassin via dpkg, rather than the postinst.
 (Closes: 891833)
Checksums-Sha1:
 4682b1ae4582df205cb676ed6fa0c1c5fea5dc2f 2437 spamassassin_3.4.2-1.dsc
 a7c72a47e9aa88276aeefc926a159c27dc4a74ab 234232 
spamassassin_3.4.2.orig-pkgrules.tar.xz
 f295571631e4163225ee3eab04d5c0cce3a69fbc 1873396 spamassassin_3.4.2.orig.tar.xz
 9e99ec3e223bc4c0e184e217319ca57c98e72d7a 38612 
spamassassin_3.4.2-1.debian.tar.xz
 c16c099174bb14f2f54bca19ab6b54296a14aa10 47904 sa-compile_3.4.2-1_all.deb
 b4e85ee7bd6c0dc29464e4b3280f90d626044cf7 

Bug#908969: marked as done (spamassassin: CVE-2017-15705: denial of service vulnerability)

[Debian Bug Tracking System]

Your message dated Mon, 01 Oct 2018 07:05:38 +
with message-id 
and subject line Bug#908969: fixed in spamassassin 3.4.2-1
has caused the Debian Bug report #908969,
regarding spamassassin: CVE-2017-15705: denial of service vulnerability
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.)


-- 
908969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spamassassin
Version: 3.4.1-1
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for spamassassin.

CVE-2017-15705[0]:
denial of service vulnerability

It is fixed upstream in new 3.4.2 release.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-15705
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15705
[1] https://www.openwall.com/lists/oss-security/2018/09/16/1

Please adjust the affected versions in the BTS as needed.



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

Kernel: Linux 4.18.0-1-amd64 (SMP w/4 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
--- End Message ---
--- Begin Message ---
Source: spamassassin
Source-Version: 3.4.2-1

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

Debian distribution maintenance software
pp.
Noah Meyerhans  (supplier of updated spamassassin 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, 30 Sep 2018 23:44:58 -0700
Source: spamassassin
Binary: spamassassin spamc sa-compile
Architecture: source all amd64
Version: 3.4.2-1
Distribution: unstable
Urgency: medium
Maintainer: Noah Meyerhans 
Changed-By: Noah Meyerhans 
Description:
 sa-compile - Tools for compiling SpamAssassin rules into C
 spamassassin - Perl-based spam filter using text analysis
 spamc  - Client for SpamAssassin spam filtering daemon
Closes: 858457 865924 883775 884163 889501 890650 891041 891833 908969 908970 
908971
Changes:
 spamassassin (3.4.2-1) unstable; urgency=medium
 .
   * New upstream release fixes multiple security vulnerabilities
 - CVE-2017-15705: Denial of service issue in which certain unclosed
   tags in emails cause markup to be handled incorrectly leading to
   scan timeouts. (Closes: 908969)
 - CVE-2016-1238: Unsafe usage of "." in @INC in a configuration
   script.
 - CVE-2018-11780: potential Remote Code Execution bug with the
   PDFInfo plugin. (Closes: 908970)
 - CVE-2018-11781: local user code injection in the meta rule syntax.
   (Closes: 908971)
 - BayesStore: bayes_expire table grows, remove_running_expire_tok not
   called (Closes: 883775)
 - Fix use of uninitialized variable warning in PDFInfo.pm
   (Closes: 865924)
 - Fix "failed to parse plugin" error in
   Mail::SpamAssassin::Plugin::URILocalBL (Closes: 891041)
   * Don't recursively chown /var/lib/spamassassin during postinst.
 (Closes: 889501)
   * Reload spamd after compiling rules in sa-compile.postinst.
   * Preserve locally set ENABLED=1 setting from /etc/default/spamassassin
 when installing on systemd-based systems. (Closes: 884163, 858457)
   * Update SysV init script to cope with upstream's change to $0.
   * Remove compiled rules upon removal of the sa-compile package.
   * Ensure that /var/lib/spamassassin/compiled doesn't change modes with
 the cron job's execution. (Closes: 890650)
   * Update standards version to 4.2.1
   * Create /var/lib/spamassassin via dpkg, rather than the postinst.
 (Closes: 891833)
Checksums-Sha1:
 4682b1ae4582df205cb676ed6fa0c1c5fea5dc2f 2437 spamassassin_3.4.2-1.dsc
 

Bug#908971: marked as done (spamassassin: CVE-2018-11781: local user code injection in the meta rule syntax)

[Debian Bug Tracking System]

Your message dated Mon, 01 Oct 2018 07:05:38 +
with message-id 
and subject line Bug#908971: fixed in spamassassin 3.4.2-1
has caused the Debian Bug report #908971,
regarding spamassassin: CVE-2018-11781: local user code injection in the meta 
rule syntax
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.)


-- 
908971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908971
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spamassassin
Version: 3.4.1-1
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for spamassassin.

CVE-2018-11781[0]:
local user code injection in the meta rule syntax

It is fixed in new upstream version 3.4.2.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-11781
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11781
[1] https://www.openwall.com/lists/oss-security/2018/09/16/1

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: spamassassin
Source-Version: 3.4.2-1

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

Debian distribution maintenance software
pp.
Noah Meyerhans  (supplier of updated spamassassin 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, 30 Sep 2018 23:44:58 -0700
Source: spamassassin
Binary: spamassassin spamc sa-compile
Architecture: source all amd64
Version: 3.4.2-1
Distribution: unstable
Urgency: medium
Maintainer: Noah Meyerhans 
Changed-By: Noah Meyerhans 
Description:
 sa-compile - Tools for compiling SpamAssassin rules into C
 spamassassin - Perl-based spam filter using text analysis
 spamc  - Client for SpamAssassin spam filtering daemon
Closes: 858457 865924 883775 884163 889501 890650 891041 891833 908969 908970 
908971
Changes:
 spamassassin (3.4.2-1) unstable; urgency=medium
 .
   * New upstream release fixes multiple security vulnerabilities
 - CVE-2017-15705: Denial of service issue in which certain unclosed
   tags in emails cause markup to be handled incorrectly leading to
   scan timeouts. (Closes: 908969)
 - CVE-2016-1238: Unsafe usage of "." in @INC in a configuration
   script.
 - CVE-2018-11780: potential Remote Code Execution bug with the
   PDFInfo plugin. (Closes: 908970)
 - CVE-2018-11781: local user code injection in the meta rule syntax.
   (Closes: 908971)
 - BayesStore: bayes_expire table grows, remove_running_expire_tok not
   called (Closes: 883775)
 - Fix use of uninitialized variable warning in PDFInfo.pm
   (Closes: 865924)
 - Fix "failed to parse plugin" error in
   Mail::SpamAssassin::Plugin::URILocalBL (Closes: 891041)
   * Don't recursively chown /var/lib/spamassassin during postinst.
 (Closes: 889501)
   * Reload spamd after compiling rules in sa-compile.postinst.
   * Preserve locally set ENABLED=1 setting from /etc/default/spamassassin
 when installing on systemd-based systems. (Closes: 884163, 858457)
   * Update SysV init script to cope with upstream's change to $0.
   * Remove compiled rules upon removal of the sa-compile package.
   * Ensure that /var/lib/spamassassin/compiled doesn't change modes with
 the cron job's execution. (Closes: 890650)
   * Update standards version to 4.2.1
   * Create /var/lib/spamassassin via dpkg, rather than the postinst.
 (Closes: 891833)
Checksums-Sha1:
 4682b1ae4582df205cb676ed6fa0c1c5fea5dc2f 2437 spamassassin_3.4.2-1.dsc
 a7c72a47e9aa88276aeefc926a159c27dc4a74ab 234232 
spamassassin_3.4.2.orig-pkgrules.tar.xz
 f295571631e4163225ee3eab04d5c0cce3a69fbc 1873396 spamassassin_3.4.2.orig.tar.xz
 9e99ec3e223bc4c0e184e217319ca57c98e72d7a 38612 
spamassassin_3.4.2-1.debian.tar.xz
 c16c099174bb14f2f54bca19ab6b54296a14aa10 47904 sa-compile_3.4.2-1_all.deb
 b4e85ee7bd6c0dc29464e4b3280f90d626044cf7 1121628 

Processed: tagging 879471

[Debian Bug Tracking System]

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

> tags 879471 + pending
Bug #879471 [src:varnish] src:varnish: 5.2 needs a SONAME version bump
Added tag(s) pending.
> thanks
Stopping processing here.

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