Processed: retitle 904215 to civicrm: CVE-2018-1999022: CIVI-SA-2018-07: Remote code execution in QuickForm

[Debian Bug Tracking System]

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

> retitle 904215 civicrm: CVE-2018-1999022: CIVI-SA-2018-07: Remote code 
> execution in QuickForm
Bug #904215 [src:civicrm] civicrm: CIVI-SA-2018-07: Remote Code Execution in 
Quickform
Changed Bug title to 'civicrm: CVE-2018-1999022: CIVI-SA-2018-07: Remote code 
execution in QuickForm' from 'civicrm: CIVI-SA-2018-07: Remote Code Execution 
in Quickform'.
> thanks
Stopping processing here.

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

Processed: Re: python3-taskflow: incompatibility between python3-taskflow 3.1.0-3 and python3-networkx 2.1-1

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #902985 [python3-taskflow] python3-taskflow: incompatibility between 
python3-taskflow 3.1.0-3 and python3-networkx 2.1-1
Severity set to 'serious' from 'important'

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

Processed: Re: Bug#904405: routino-www: fails to install: chown: cannot access '/var/lib/routino/results/*': No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #904405 [routino-www] routino-www: fails to install: chown: cannot access 
'/var/lib/routino/results/*': No such file or directory
Added tag(s) confirmed.

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

Bug#904405: routino-www: fails to install: chown: cannot access '/var/lib/routino/results/*': No such file or directory

[Sebastiaan Couwenberg]

Control: tags -1 confirmed

On 07/24/2018 05:26 AM, Andreas Beckmann wrote:
>   + chown www-data:www-data /var/lib/routino/results/*
>   chown: cannot access '/var/lib/routino/results/*': No such file or directory

If only we could keep using `chown -R`, but that had security issues.

I'll need to look into a different solution.

Kind Regards,

Bas

Bug#832127: Test::Aggregate: pending removal from Debian

[intrigeri]

Hi,

The Debian perl group is reviewing packages with bugs which make them
un-releasable; in particular when they are not heavily used by Debian
users. We would like to remove such modules from Debian if we don't
think they are likely to be fixed.

Test::Aggregate is one such module, owing to
https://rt.cpan.org/Public/Bug/Display.html?id=100035 (aka.
https://github.com/rwstauner/test-aggregate/issues/2 and
https://bugs.debian.org/832127), and we would like to know whether you
have any plans to look at the bug in the foreseeable future before we
remove the package from Debian.

If we don't hear anything we will remove the package from Debian
around the end of August. This of course does not affect the standing
of your module on CPAN.

Thank you for maintaining this module so far!
-- 
intrigeri

Bug#868253: POE::Component::Client::MPD: pending removal from Debian

[intrigeri]

Hi Jérôme,

The Debian perl group is reviewing packages with bugs which make them
un-releasable; in particular when they are not heavily used by Debian
users. We would like to remove such modules from Debian if we don't
think they are likely to be fixed.

POE::Component::Client::MPD is one such module, owing to
https://rt.cpan.org/Public/Bug/Display.html?id=122469 (aka.
https://bugs.debian.org/868253), and we would like to know whether you
have any plans to look at the bug in the foreseeable future before we
remove the package from Debian.

If we don't hear anything we will remove the package from Debian
around the end of August. This of course does not affect the standing
of your module on CPAN.

Thank you for maintaining this module so far!
-- 
intrigeri

Bug#864800: Mail::DeliveryStatus::BounceParser contains a live virus and some real spam/phishing mails

[intrigeri]

Hi Ricardo,

Paul Wise:
> The Mail::DeliveryStatus::BounceParser source contains a live virus and
> some real spam/phishing mails. This is leading to Netcraft and other
> virus detection systems on the Internet reporting Debian mirrors as
> malicious, which potentially reduces the reputation of debian.org on
> various anti-spam and anti-malware services.

The Debian perl group is reviewing packages with bugs which make them
un-releasable; in particular when they are not heavily used by Debian
users. We would like to remove such modules from Debian if we don't
think they are likely to be fixed.

Mail::DeliveryStatus::BounceParser is one such module, owing to
https://rt.cpan.org/Public/Bug/Display.html?id=122559, and we would
like to know whether you have any plans to look at the bug in the
foreseeable future before we remove the package from Debian.

If we don't hear anything we will remove the package from Debian
around the end of August. This of course does not affect the standing
of your module on CPAN.

Thank you for maintaining this module so far!
-- 
intrigeri

Bug#904405: routino-www: fails to install: chown: cannot access '/var/lib/routino/results/*': No such file or directory

[Andreas Beckmann]

Package: routino-www
Version: 3.2-3
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 routino-www.
  (Reading database ... 
(Reading database ... 7563 files and directories currently installed.)
  Preparing to unpack .../routino-www_3.2-3_all.deb ...
  Unpacking routino-www (3.2-3) ...
  Setting up routino-www (3.2-3) ...
  + set -e
  + [  = developer ]
  + [ ! -d /var/lib/routino/data ]
  + mkdir -p /var/lib/routino/data
  + [ ! -d /var/lib/routino/results ]
  + mkdir -p /var/lib/routino/results
  + chown www-data:www-data /var/lib/routino/results
  + chown www-data:www-data /var/lib/routino/results/*
  chown: cannot access '/var/lib/routino/results/*': No such file or directory
  dpkg: error processing package routino-www (--configure):
   installed routino-www package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   routino-www


cheers,

Andreas


routino-www_3.2-3.log.gz
Description: application/gzip

Bug#904404: liece-dcc: fails to install with emacs25

[Andreas Beckmann]

Package: liece-dcc
Version: 2.0+0.20030527cvs-11.2
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...):

  Setting up emacs25 (25.2+1-6+b3) ...
  update-alternatives: using /usr/bin/emacs25-x to provide /usr/bin/emacs 
(emacs) in auto mode
  update-alternatives: using /usr/bin/emacs25 to provide /usr/bin/editor 
(editor) in auto mode
  Install emacsen-common for emacs25
  emacsen-common: Handling install of emacsen flavor emacs25
  Install liece for emacs25
  install/liece: Handling emacs25, logged in /tmp/elc_Mb8V4E.log
  ERROR: install script from liece package failed
  dpkg: error processing package emacs25 (--configure):
   installed emacs25 package post-installation script subprocess returned error 
exit status 1

The logfile contains:

emacs25 -q -no-site-file --no-site-file -batch -l liece-make.el -f 
autoload-liece
Loading /usr/share/emacs25/site-lisp/liece/liece-config.el (source)...
Cannot open load file: No such file or directory, install


cheers,

Andreas


liece-dcc_2.0+0.20030527cvs-11.2+b1.log.gz
Description: application/gzip

Bug#825231: Devel-BeginLift: pending removal from Debian

[intrigeri]

Dear Maintainer,

The Debian perl group is reviewing packages with bugs which make them
un-releasable; in particular when they are not heavily used by Debian
users. We would like to remove such modules from Debian if we don't
think they are likely to be fixed.

Devel::BeginLift is one such module, due to:

  https://rt.cpan.org/Ticket/Display.html?id=114663
  https://rt.cpan.org/Ticket/Display.html?id=115272

We would like to know whether you have any plans to look at the bug in
the foreseeable future before we remove the package from Debian.

If we don't hear anything we will remove the package from Debian in ~1
month. This of course does not affect the standing of your module
on CPAN.

Thank you for maintaining this module so far!
-- 
intrigeri

Bug#904403: goiardi: fails to install: chown: cannot access '/var/lib/goiardi/lfs/*': No such file or directory

[Andreas Beckmann]

Package: goiardi
Version: 0.11.8-1
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 goiardi.
  (Reading database ... 
(Reading database ... 4469 files and directories currently installed.)
  Preparing to unpack .../goiardi_0.11.8-1_amd64.deb ...
  Unpacking goiardi (0.11.8-1) ...
  Setting up goiardi (0.11.8-1) ...
  adduser: Warning: The home directory `/var/lib/goiardi' does not belong to 
the user you are currently creating.
  chown: cannot access '/var/lib/goiardi/lfs/*': No such file or directory
  dpkg: error processing package goiardi (--configure):
   installed goiardi package post-installation script subprocess returned error 
exit status 1
  Errors were encountered while processing:
   goiardi

cheers,

Andreas


goiardi_0.11.8-1.log.gz
Description: application/gzip

Processed: tag

[Debian Bug Tracking System]

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

> tags 904402 + ftbfs
Bug #904402 [libdevel-beginlift-perl] libdevel-beginlift-perl: FTBFS with perl 
5.25+: 'OP' {aka 'struct op'} has no member named 'op_sibling'
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: bug 904402 is forwarded to https://rt.cpan.org/Public/Bug/Display.html?id=115272

[Debian Bug Tracking System]

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

> forwarded 904402 https://rt.cpan.org/Public/Bug/Display.html?id=115272
Bug #904402 [libdevel-beginlift-perl] libdevel-beginlift-perl: FTBFS with perl 
5.25+: 'OP' {aka 'struct op'} has no member named 'op_sibling'
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Public/Bug/Display.html?id=115272'.
> thanks
Stopping processing here.

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

Bug#904402: libdevel-beginlift-perl: FTBFS with perl 5.25+: 'OP' {aka 'struct op'} has no member named 'op_sibling'

[intrigeri]

Package: libdevel-beginlift-perl
Severity: serious
Version:  0.001003-1

Running Mkbootstrap for BeginLift ()
chmod 644 "BeginLift.bs"
"/usr/bin/perl" "-Iinc" -MExtUtils::Command::MM -e 'cp_nonempty' -- 
BeginLift.bs blib/arch/auto/Devel/BeginLift/BeginLift.bs 644
"/usr/bin/perl" "-Iinc" "/usr/share/perl/5.26/ExtUtils/xsubpp"  -typemap 
'/usr/share/perl/5.26/ExtUtils/typemap' -typemap 
'/usr/lib/x86_64-linux-gnu/perl5/5.26/B/Utils/Install/typemap'  BeginLift.xs > 
BeginLift.xsc
mv BeginLift.xsc BeginLift.c
x86_64-linux-gnu-gcc -c  
-I/usr/lib/x86_64-linux-gnu/perl5/5.26/B/Hooks/OP/Check/Install 
-I/usr/lib/x86_64-linux-gnu/perl5/5.26/B/Hooks/OP/Check/EntersubForCV/Install 
-I/usr/lib/x86_64-linux-gnu/perl5/5.26/B/Utils/Install -D_REENTRANT 
-D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   
-DVERSION=\"0.001003\" -DXS_VERSION=\"0.001003\" -fPIC 
"-I/usr/lib/x86_64-linux-gnu/perl/5.26/CORE"   BeginLift.c
BeginLift.xs:13: warning: "LINKLIST" redefined
 #define LINKLIST(o) ((o)->op_next ? (o)->op_next : linklist((OP*)o))
 
In file included from /usr/lib/x86_64-linux-gnu/perl/5.26/CORE/perl.h:3921,
 from BeginLift.xs:4:
/usr/lib/x86_64-linux-gnu/perl/5.26/CORE/op.h:641: note: this is the location 
of the previous definition
 #define LINKLIST(o) ((o)->op_next ? (o)->op_next : op_linklist((OP*)o))
 
BeginLift.xs: In function 'THX_linklist':
BeginLift.xs:27:16: error: 'OP' {aka 'struct op'} has no member named 
'op_sibling'; did you mean 'op_sibparent'?
   if (kid->op_sibling) {
^~
op_sibparent
BeginLift.xs:28:33: error: 'OP' {aka 'struct op'} has no member named 
'op_sibling'; did you mean 'op_sibparent'?
kid->op_next = LINKLIST(kid->op_sibling);
 ^~
BeginLift.xs:13:23: note: in definition of macro 'LINKLIST'
 #define LINKLIST(o) ((o)->op_next ? (o)->op_next : linklist((OP*)o))
   ^
BeginLift.xs:28:33: error: 'OP' {aka 'struct op'} has no member named 
'op_sibling'; did you mean 'op_sibparent'?
kid->op_next = LINKLIST(kid->op_sibling);
 ^~
BeginLift.xs:13:38: note: in definition of macro 'LINKLIST'
 #define LINKLIST(o) ((o)->op_next ? (o)->op_next : linklist((OP*)o))
  ^
BeginLift.xs:28:33: error: 'OP' {aka 'struct op'} has no member named 
'op_sibling'; did you mean 'op_sibparent'?
kid->op_next = LINKLIST(kid->op_sibling);
 ^~
BeginLift.xs:16:41: note: in definition of macro 'linklist'
 # define linklist(o) THX_linklist(aTHX_ o)
 ^
BeginLift.xs:28:19: note: in expansion of macro 'LINKLIST'
kid->op_next = LINKLIST(kid->op_sibling);
   ^~~~
BeginLift.xs:29:15: error: 'OP' {aka 'struct op'} has no member named 
'op_sibling'; did you mean 'op_sibparent'?
kid = kid->op_sibling;
   ^~
   op_sibparent
BeginLift.xs: In function 'lift_cb':
BeginLift.xs:64:24: error: 'OP' {aka 'struct op'} has no member named 
'op_sibling'; did you mean 'op_sibparent'?
 for ( arg = curop->op_sibling; arg->op_sibling; arg = arg->op_sibling ) {
^~
op_sibparent
BeginLift.xs:64:41: error: 'OP' {aka 'struct op'} has no member named 
'op_sibling'; did you mean 'op_sibparent'?
 for ( arg = curop->op_sibling; arg->op_sibling; arg = arg->op_sibling ) {
 ^~
 op_sibparent
BeginLift.xs:64:64: error: 'OP' {aka 'struct op'} has no member named 
'op_sibling'; did you mean 'op_sibparent'?
 for ( arg = curop->op_sibling; arg->op_sibling; arg = arg->op_sibling ) {
^~
op_sibparent
BeginLift.xs:99:12: error: 'OP' {aka 'struct op'} has no member named 
'op_sibling'; did you mean 'op_sibparent'?
   new->op_sibling = NULL;
^~
op_sibparent
make[1]: *** [Makefile:340: BeginLift.o] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2

Bug#870418: How much longer should Shutter remain in sid?

[intrigeri]

Hi,

(status update on top, specific questions for Jeremy and Dominique at
the bottom)

Jeremy Bicha:
> As announced [1], we do not intend to release Debian 10 "Buster" with
> the old libgnome (and related) libraries. As part of this process, I
> am now raising the severity of these bugs.

Almost a year has now passed since I've filed this bug report during
DebCamp17. Shutter is now the only blocker that currently prevents us
from removing 7 obsolete lib*-perl packages from the archive, which in
turns blocks removing obsolete GNOME 2 libraries. Since then, calls
for help were sent to the gtk-perl list (9 months ago) and to
debian-{devel,user}@ (6.5 months ago).

My understanding of the upstream situation [1] is:

 - A patch was proposed by Dominique Dumont 4 months ago, that ports
   file handling from VFS to GIO. Thanks Dominique!

 - As a follow-up to this patch submission, on March 11 the only
   active upstream maintainer of Shutter wrote "I'm not a developer
   and in particular I never learnt Pearl and never worked with GTK
   libraries", cannot review patches, and proposed to give Dominique
   access to the upstream BZR repo so he can fix stuff directly there
   (and de facto become the only person active upstream with
   development skills). Dominique did not reply to this offer.

 - I'm not aware of any WIP to port Shutter away from its other
   lib{gtk,gnome}2-*-perl dependencies (see the list of RC bugs
   blocked by this one for details).

[1] https://bugs.launchpad.net/shutter/+bug/1006290

At this point, it looks quite clear that nobody has the skills,
motivation and time to take over Shutter development upstream and port
its codebase to non-obsolete libraries during the Buster development
cycle. shutter and lib*-perl packages were removed from testing a few
months ago and it's unlikely they'll be part of the Buster release.

What I'm now wondering is how long we want to keep them in sid.

With my pkg-perl team member hat on, I'm not very comfortable with
keeping, under the team umbrella, 7 obsolete lib{gtk,gnome}2-*-perl
packages in the archive, themselves depending on libraries that have
been declared unmaintained upstream for years. I'm fine with keeping
them in sid a little longer (say, until the end of 2018) if Dominique
thinks that waiting some more has any chance to bring a new Shutter
version that does not depend on these obsolete libraries. Dominique,
what do you think?

Jeremy, what's the plan wrt. obsolete GNOME libraries in sid?

Cheers,
-- 
intrigeri

Bug#902658: apache2: apachectl graceful/restart results in segfault

[Kai-Martin Knaak]

Similar problem here. My apache2 server goes into a reload loop every
time /etc/logrotate.d/apache2 is called. That is, daily a few minutes
after midnight. The loop is triggered by the reload statement in the
logrotate script. 
As a band-aid I just replaced "reload" by "restart" in the logrotate script.

In my case kern.log attributes the segfault to libglib-2.0:

# tail -n 1 /var/log/kern.log
Jul 24 02:22:39 bibo kernel: [175623.347801] /usr/sbin/apach[8662]: segfault at 
7fb516473660 ip 7fb516473660 sp 7ffe8b10e508 error 14 in 
libglib-2.0.so.0.5600.1[7fb516dac000+113000]

If I apply the /proc/$pid/maps|sort search with ldd I get:

# pid=770; for i in $(awk '{ print $6 }' < /proc/$pid/maps|sort -u|grep /) ; do 
ldd -d  $i|grep libglib && echo $i ; done
ldd: /dev/zero: not regular file
ldd: /SYSV6405bf18: No such file or directory
libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7fcfb3308000)
/usr/lib/php/20170718/imagick.so
libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7f0a395be000)
/usr/lib/x86_64-linux-gnu/liblqr-1.so.0.3.2
libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7f2b15ea5000)
/usr/lib/x86_64-linux-gnu/libMagickCore-6.Q16.so.5.0.0
libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7fa7bdb1c000)
/usr/lib/x86_64-linux-gnu/libMagickWand-6.Q16.so.5.0.0

---<)kaimartin(>---

-- 
Kai-Martin Knaak
Email: k...@familieknaak.de
Öffentlicher PGP-Schlüssel:
https://keyserver.ubuntu.com/pks/lookup?op=index=0x7B0F9882


pgpR5EKBEFbcG.pgp
Description: OpenPGP digital signature

Processed: bug 903611 is forwarded to https://github.com/syncthing/syncthing/issues/4990

[Debian Bug Tracking System]

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

> forwarded 903611 https://github.com/syncthing/syncthing/issues/4990
Bug #903611 [src:syncthing] syncthing FTBFS on 32bit: FAIL: TestBlockSize 
Set Bug forwarded-to-address to 
'https://github.com/syncthing/syncthing/issues/4990'.
> thanks
Stopping processing here.

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

Bug#904396: foma: fails to upgrade from 'sid' - trying to overwrite /usr/bin/cgflookup

[Andreas Beckmann]

Package: foma
Version: 1:0.9.18~r248-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../foma_1%3a0.9.18~r248-1_amd64.deb ...
  Unpacking foma (1:0.9.18~r248-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/foma_1%3a0.9.18~r248-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/cgflookup', which is also in package foma-bin 
0.9.18+r243-1+b3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/foma_1%3a0.9.18~r248-1_amd64.deb


cheers,

Andreas


foma-bin=0.9.18+r243-1+b3_foma=1%0.9.18~r248-1.log.gz
Description: application/gzip

Processed: fixed 897568 in 0.7.9-1, fixed 897568 in 0.7.9-2, notfixed 670798 in 1.2.7, fixed 670798 in 1.2.7-1 ...

[Debian Bug Tracking System]

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

> fixed 897568 0.7.9-1
Bug #897568 {Done: Felix Geyer } [zfs-dkms] zfs-dkms 0.7.6 
fails to build on 4.16.0-1-amd64
Marked as fixed in versions zfs-linux/0.7.9-1.
> fixed 897568 0.7.9-2
Bug #897568 {Done: Felix Geyer } [zfs-dkms] zfs-dkms 0.7.6 
fails to build on 4.16.0-1-amd64
Marked as fixed in versions zfs-linux/0.7.9-2.
> notfixed 670798 1.2.7
Bug #670798 {Done: Innocent De Marchi } [connectagram] 
connectagram: sometimes twisty words touch inpropriately
There is no source info for the package 'connectagram' at version '1.2.7' with 
architecture ''
Unable to make a source version for version '1.2.7'
No longer marked as fixed in versions connectagram/1.2.7.
> fixed 670798 1.2.7-1
Bug #670798 {Done: Innocent De Marchi } [connectagram] 
connectagram: sometimes twisty words touch inpropriately
Marked as fixed in versions connectagram/1.2.7-1.
> reassign 897528 python3-zzzeeksphinx 1.0.20-1
Bug #897528 {Done: Piotr Ożarowski } [src:sqlalchemy] 
sqlalchemy: FTBFS: ImportError: cannot import name 'Directive'
Bug reassigned from package 'src:sqlalchemy' to 'python3-zzzeeksphinx'.
No longer marked as found in versions sqlalchemy/1.2.5+ds1-1.
No longer marked as fixed in versions zzzeeksphinx/1.0.20-2.
Bug #897528 {Done: Piotr Ożarowski } [python3-zzzeeksphinx] 
sqlalchemy: FTBFS: ImportError: cannot import name 'Directive'
Marked as found in versions zzzeeksphinx/1.0.20-1.
> fixed 897528 1.0.20-2
Bug #897528 {Done: Piotr Ożarowski } [python3-zzzeeksphinx] 
sqlalchemy: FTBFS: ImportError: cannot import name 'Directive'
Marked as fixed in versions zzzeeksphinx/1.0.20-2.
> reassign 805753 lynx 2.8.9dev6-4
Bug #805753 {Done: Elimar Riesebieter } [lynx-cur] no colon 
sometimes
Bug reassigned from package 'lynx-cur' to 'lynx'.
No longer marked as found in versions lynx/2.8.9dev8-4 and lynx-cur/2.8.9dev6-4.
No longer marked as fixed in versions lynx/2.8.9pre.1-1.
Bug #805753 {Done: Elimar Riesebieter } [lynx] no colon 
sometimes
Marked as found in versions lynx-cur/2.8.9dev6-4.
> fixed 805753 2.8.9pre.1-1
Bug #805753 {Done: Elimar Riesebieter } [lynx] no colon 
sometimes
Marked as fixed in versions lynx/2.8.9pre.1-1.
> thanks
Stopping processing here.

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

Bug#904390: python3-exabgp: fails to install with Python 3.7

[Andreas Beckmann]

Package: python3-exabgp
Version: 4.0.6-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up python3-exabgp (4.0.6-2) ...
  update-alternatives: using /usr/sbin/python3-exabgp to provide 
/usr/sbin/exabgp (exabgp) in auto mode
File 
"/usr/lib/python3/dist-packages/exabgp/reactor/api/command/announce.py", line 63
  reactor.async.schedule(service,line,callback())
  ^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/exabgp/reactor/api/command/neighbor.py", line 
165
  reactor.async.schedule(service,command,callback_summary())
  ^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/exabgp/reactor/api/command/reactor.py", line 84
  reactor.async.clear(service)
  ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/exabgp/reactor/api/command/rib.py", 
line 89
  reactor.async.schedule(service,line,callback())
  ^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/exabgp/reactor/api/command/watchdog.py", line 34
  reactor.async.schedule(service,line,callback(name))
  ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/exabgp/reactor/listener.py", line 195
  reactor.async.schedule(str(uuid.uuid1()),'sending notification 
(6,5)',connection.notification(6,5,'could not accept the connection (more than 
one neighbor match)'))
  ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/exabgp/reactor/loop.py", line 24
  from exabgp.reactor.async import ASYNC
  ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/exabgp/reactor/network/incoming.py", 
line 5
  from .tcp import async
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/exabgp/reactor/network/outgoing.py", 
line 11
  from .tcp import async
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/exabgp/reactor/network/tcp.py", line 
222
  def async (io, ip):
  ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-exabgp (--configure):
   installed python3-exabgp package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   python3-exabgp


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-exabgp=4.0.6-2.log.gz
Description: application/gzip

Processed: python3-exabgp: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 903526 904363 904373 903145 902900 902761 903525 904388 
904371 903016 904351 902766 903528 904383 904368 903218 902650 904361 903457 
904367 902817 903388 903031 904389 903423 902989 904381 904298 902631 904364 
903522 904358 903529 904369 904365 903030 903784 904357 902646 904343 902715 
902757 903558 903826 904370 902794 904350 903527 904382
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904390

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

Bug#904389: python3-glance: fails to install with Python 3.7

[Andreas Beckmann]

Package: python3-glance
Version: 2:16.0.1-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up python3-glance (2:16.0.1-6) ...
File 
"/usr/lib/python3/dist-packages/glance/async/flows/api_image_import.py", line 26
  import glance.async.flows._internal_plugins as internal_plugins
^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/glance/async/flows/base_import.py", 
line 33
  from glance.async import utils
  ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/glance/async/flows/introspect.py", 
line 24
  from glance.async import utils
  ^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/glance/async/flows/plugins/plugin_opts.py", 
line 17
  import glance.async.flows.plugins.inject_image_metadata
^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/glance/async/taskflow_executor.py", 
line 26
  import glance.async
^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/glance/opts.py", line 31
  import glance.async.flows._internal_plugins
^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/glance/tests/unit/async/flows/plugins/test_inject_image_metadata.py",
 line 22
  import glance.async.flows.plugins.inject_image_metadata as inject_metadata
^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/glance/tests/unit/async/flows/test_api_image_import.py",
 line 20
  import glance.async.flows.api_image_import as import_flow
^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/glance/tests/unit/async/flows/test_convert.py", 
line 25
  from glance.async.flows import convert
  ^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/glance/tests/unit/async/flows/test_import.py", 
line 28
  import glance.async.flows.base_import as import_flow
^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/glance/tests/unit/async/flows/test_introspect.py",
 line 23
  from glance.async.flows import introspect
  ^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/glance/tests/unit/async/flows/test_ovf_process.py",
 line 27
  from glance.async.flows import ovf_process
  ^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/glance/tests/unit/async/test_async.py", line 19
  import glance.async
^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/glance/tests/unit/async/test_taskflow_executor.py",
 line 22
  from glance.async import taskflow_executor
  ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/glance/tests/unit/test_domain.py", 
line 24
  import glance.async
^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/glance/tests/unit/test_notifier.py", 
line 25
  import glance.async
^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-glance (--configure):
   installed python3-glance package post-installation script subprocess 
returned error exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-glance=2%16.0.1-6.log.gz
Description: application/gzip

Processed: python3-glance: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 904358 903457 903526 904357 903388 903525 903031 904361 
903784 904368 904343 904382 904351 904363 903218 902989 904369 902631 903527 
902900 904364 904383 904298 904388 904365 904370 903558 904373 904371 902757 
904381 903016 903522 902817 902761 903826 904367 903145 903528 902794 903529 
904350 903423 902650 903030 902766 902715 902646
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904389

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

Bug#904388: python3-gbulb: fails to install with Python 3.7

[Andreas Beckmann]

Package: python3-gbulb
Version: 0.5.3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up python3-gbulb (0.5.3-2) ...
File "/usr/lib/python3/dist-packages/gbulb/glib_events.py", line 126
  future = tasks.async(future, loop=self)
 ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-gbulb (--configure):
   installed python3-gbulb package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   python3-gbulb


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-gbulb=0.5.3-2.log.gz
Description: application/gzip

Processed: python3-gbulb: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 902766 902650 904357 902646 904363 904351 902989 904370 
904350 904358 902900 902757 903145 902761 904371 904298 903529 903528 904368 
904381 904365 903527 903016 903522 904382 904361 903030 903218 902794 902631 
904367 904369 902817 903526 903423 904343 904364 903784 902715 903457 903388 
903525 904383 903826 903031 903558 904373
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904388

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

Bug#902784: marked as done (cython-dbg: StringIOTree debug module missing)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jul 2018 21:03:49 +
with message-id 
and subject line Bug#902784: fixed in cython 0.28.4-1
has caused the Debian Bug report #902784,
regarding cython-dbg: StringIOTree debug module missing
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.)


-- 
902784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cython-dbg
Version: 0.28.2-4
Severity: important

cython ships a StringIOTree extension module:

/usr/lib/python2.7/dist-packages/Cython/StringIOTree.x86_64-linux-gnu.so

However, cython-dbg is missing the debug version of this module. This results
in import errors when using the debug interpreter:

mithrandi@lorien ~> python-dbg -c 'import Cython.Compiler.Main'
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/Main.py", line 30, in 

from .Symtab import ModuleScope
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/Symtab.py", line 19, 
in 
from . import PyrexTypes
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/PyrexTypes.py", line 
17, in 
from .Code import UtilityCode, LazyUtilityCode, TempitaUtilityCode
  File "Cython/Compiler/Code.py", line 38, in init Cython.Compiler.Code
ImportError: 
/usr/lib/python2.7/dist-packages/Cython/StringIOTree.x86_64-linux-gnu.so: 
undefined symbol: Py_InitModule4_64

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

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

Versions of packages cython-dbg depends on:
ii  cython  0.28.2-4
ii  libc6   2.27-3

cython-dbg recommends no packages.

cython-dbg suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: cython
Source-Version: 0.28.4-1

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

Debian distribution maintenance software
pp.
Julian Taylor  (supplier of updated cython 
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, 23 Jul 2018 17:58:49 +
Source: cython
Binary: cython cython-dbg cython3 cython3-dbg cython-doc
Architecture: source
Version: 0.28.4-1
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Julian Taylor 
Description:
 cython - C-Extensions for Python
 cython-dbg - C-Extensions for Python - debug build
 cython-doc - C-Extensions for Python - documentation
 cython3- C-Extensions for Python 3
 cython3-dbg - C-Extensions for Python 3 - debug build
Closes: 902551 902784 903024
Changes:
 cython (0.28.4-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #902551)
   * Fix missing installation of some debug libraries. (Closes: #902784)
   * debian/patches/fix-fused-test.patch:
 fix invalid testcase crashing with gcc-8
   * debian/patches/drop-test.patch:
 drop test of behaviour changed in python3.7
 Closes: #903024
   * bump standards version
   * switch to python3-sphinx
Checksums-Sha1:
 089a209b1314f87a636ba9f9fbe85a4257019856 2517 cython_0.28.4-1.dsc
 b965c1efa2236fb57470d749438f22fbe1a23b53 1880943 cython_0.28.4.orig.tar.gz
 36d50481fce83f4404bc945d203bac67eeda2d52 25944 cython_0.28.4-1.debian.tar.xz
Checksums-Sha256:
 f7c35503da94d09584987374a72aeff570fe82975caa93a26f32f374c25c5e9e 2517 
cython_0.28.4-1.dsc
 76ac2b08d3d956d77b574bb43cbf1d37bd58b9d50c04ba281303e695854ebc46 1880943 
cython_0.28.4.orig.tar.gz
 e8b3067e5a62a4d5407d3cfd5f6c6cb9ee51958f4dac1ddd95d10e010639a094 25944 
cython_0.28.4-1.debian.tar.xz
Files:
 73b37fce8c6442865a86475452b6bd83 2517 python optional cython_0.28.4-1.dsc
 fa01ba71b1e3136b0f12e3ed8958ea02 1880943 python 

Bug#903024: marked as done (cython: FTBFS with python3.7: Doctest: pure_doctest__generators_py.with_outer_raising ... FAIL)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jul 2018 21:03:49 +
with message-id 
and subject line Bug#903024: fixed in cython 0.28.4-1
has caused the Debian Bug report #903024,
regarding cython: FTBFS with python3.7: Doctest: 
pure_doctest__generators_py.with_outer_raising ... FAIL
to be marked as done.

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

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


-- 
903024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cython
Version: 0.28.2-4
Severity: serious

Hi,

Your package failed to build on a rebuild with python3.7 as a supported python3 
interpreter:

Doctest: pure_doctest__generators_py.with_outer_raising ... FAIL
[...]
FAIL: with_outer_raising (pure_doctest__generators_py)
Doctest: pure_doctest__generators_py.with_outer_raising
--
Traceback (most recent call last):
  File "/usr/lib/python3.7/doctest.py", line 2198, in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for 
pure_doctest__generators_py.with_outer_raising
  File "/<>/tests/run/generators_py.py", line 84, in 
with_outer_raising

--
File "/<>/tests/run/generators_py.py", line 87, in 
pure_doctest__generators_py.with_outer_raising
Failed example:
list(x())
Exception raised:
Traceback (most recent call last):
  File "/<>/tests/run/generators_py.py", line 93, in generator
raise StopIteration
StopIteration

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/lib/python3.7/doctest.py", line 1329, in __run
compileflags, 1), test.globs)
  File "", line 
1, in 
list(x())
RuntimeError: generator raised StopIteration


It'd be good to fix this soon as this is blocking many packages for the 
python3.7 transition.

Cheers,
Emilio

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), 
LANGUAGE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: cython
Source-Version: 0.28.4-1

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

Debian distribution maintenance software
pp.
Julian Taylor  (supplier of updated cython 
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, 23 Jul 2018 17:58:49 +
Source: cython
Binary: cython cython-dbg cython3 cython3-dbg cython-doc
Architecture: source
Version: 0.28.4-1
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Julian Taylor 
Description:
 cython - C-Extensions for Python
 cython-dbg - C-Extensions for Python - debug build
 cython-doc - C-Extensions for Python - documentation
 cython3- C-Extensions for Python 3
 cython3-dbg - C-Extensions for Python 3 - debug build
Closes: 902551 902784 903024
Changes:
 cython (0.28.4-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #902551)
   * Fix missing installation of some debug libraries. (Closes: #902784)
   * debian/patches/fix-fused-test.patch:
 fix invalid testcase crashing with gcc-8
   * debian/patches/drop-test.patch:
 drop test of behaviour changed in python3.7
 Closes: #903024
   * bump standards version
   * switch to python3-sphinx
Checksums-Sha1:
 089a209b1314f87a636ba9f9fbe85a4257019856 2517 cython_0.28.4-1.dsc
 b965c1efa2236fb57470d749438f22fbe1a23b53 1880943 cython_0.28.4.orig.tar.gz
 36d50481fce83f4404bc945d203bac67eeda2d52 25944 cython_0.28.4-1.debian.tar.xz
Checksums-Sha256:
 

Bug#904194: marked as done (cython-dbg is broken, incomplete installation)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jul 2018 21:03:49 +
with message-id 
and subject line Bug#902784: fixed in cython 0.28.4-1
has caused the Debian Bug report #902784,
regarding cython-dbg is broken, incomplete installation
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.)


-- 
902784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cython-dbg
Version: 0.28.2-4
Severity: serious
Tags: sid buster

$ python -c 'import Cython.StringIOTree'


$ python-dbg -c 'import Cython.StringIOTree'
Traceback (most recent call last):
  File "", line 1, in 
ImportError:
/usr/lib/python2.7/dist-packages/Cython/StringIOTree.x86_64-linux-gnu.so:
undefined symbol: Py_InitModule4_64
--- End Message ---
--- Begin Message ---
Source: cython
Source-Version: 0.28.4-1

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

Debian distribution maintenance software
pp.
Julian Taylor  (supplier of updated cython 
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, 23 Jul 2018 17:58:49 +
Source: cython
Binary: cython cython-dbg cython3 cython3-dbg cython-doc
Architecture: source
Version: 0.28.4-1
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Julian Taylor 
Description:
 cython - C-Extensions for Python
 cython-dbg - C-Extensions for Python - debug build
 cython-doc - C-Extensions for Python - documentation
 cython3- C-Extensions for Python 3
 cython3-dbg - C-Extensions for Python 3 - debug build
Closes: 902551 902784 903024
Changes:
 cython (0.28.4-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #902551)
   * Fix missing installation of some debug libraries. (Closes: #902784)
   * debian/patches/fix-fused-test.patch:
 fix invalid testcase crashing with gcc-8
   * debian/patches/drop-test.patch:
 drop test of behaviour changed in python3.7
 Closes: #903024
   * bump standards version
   * switch to python3-sphinx
Checksums-Sha1:
 089a209b1314f87a636ba9f9fbe85a4257019856 2517 cython_0.28.4-1.dsc
 b965c1efa2236fb57470d749438f22fbe1a23b53 1880943 cython_0.28.4.orig.tar.gz
 36d50481fce83f4404bc945d203bac67eeda2d52 25944 cython_0.28.4-1.debian.tar.xz
Checksums-Sha256:
 f7c35503da94d09584987374a72aeff570fe82975caa93a26f32f374c25c5e9e 2517 
cython_0.28.4-1.dsc
 76ac2b08d3d956d77b574bb43cbf1d37bd58b9d50c04ba281303e695854ebc46 1880943 
cython_0.28.4.orig.tar.gz
 e8b3067e5a62a4d5407d3cfd5f6c6cb9ee51958f4dac1ddd95d10e010639a094 25944 
cython_0.28.4-1.debian.tar.xz
Files:
 73b37fce8c6442865a86475452b6bd83 2517 python optional cython_0.28.4-1.dsc
 fa01ba71b1e3136b0f12e3ed8958ea02 1880943 python optional 
cython_0.28.4.orig.tar.gz
 4fdb83767130ea75eda39a9eec13f3b4 25944 python optional 
cython_0.28.4-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAltWJpYACgkQr8/sjmac
4cKBKA/+M46c6Sb41RQOwbJBCo5L+RgJqxGoyXrGf+kq8M2uagRWAannvzEDdnKe
vQu296gwJsZQrFkPPOhEZFk75wtTxn8nubAHTrgwgFeIFZcZ8v9QNfVnDdJKwdZZ
GGdvDhG7PuTa9NaRpZgwtCcxjkCeNSxXZ3DJccKDfZpD37g74jyyrZlfV3su+sPs
ufPHYFCqrWoGfFOOxZ7rVACcd067W+1ZtXqCBNx4GFYcMo+8uIrU7OoINMQb6TX+
c8Ep23/cHvEdbYTulQ6+v33dTR7U9WOzE/NKtuVftLu/mTx+D6WPXabKe1MkiO74
AOAH8hwT1vu1VWEJ6OIUImrtM7WOvusJo1hn+m1Jq4Eq1GErAqNYMUocj64BntLq
8ygY4kKzHp0FGzXN6g3uOM9kRgssRp/QXf5YWvh7vYh8O/P8iKrxY0LDHIY1+bVt
XwRBknQhrBAYz2IVFQgkByQeErv0xAp323zv02Jya2nxI5fPR/go+9Od+/RLHUpl
eGytej3wXO2BwzvkyEZSTopJP/E5Cgob2bA39MZgjQBqrsX2dMCdIj3k7CcGK0TL
nYPYglEAjQnHdo9x92MIxvhzZHkUBEdo2dM4DgV/21YRnjdsTRb0+EOzre0J0+h/
6F5Nm6ZsPZdfjZHI/rpE3yw2dhKi83jAhYnXKKxUTXKPFZOY4nY=
=Chv3
-END PGP SIGNATURE End Message ---

Processed: severity of 904381 is normal

[Debian Bug Tracking System]

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

> severity 904381 normal
Bug #904381 [python3-dns] python3-dns: fails to install with Python 3.7
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#867451: python-pysolr/python3-pysolr: missing dependencies

[Dererk]

I don't mind at all, on the other hand. Thanks!


Cheers,

Dererk


On 23/07/18 16:10, Andreas Beckmann wrote:

On 2018-07-23 20:41, Dererk wrote:

Hi Andreas.

Just for me to understand, should I re-build, upload to proposed-updates
&& request d-release@ ?

It has been some time since the last I did that, that why I wanted to
avoid any mistakes from my end.

Let's wait for an ACK from the release team on the PU request. If you
don't mind, I'll upload it since I've already prepared it some time ago.


Andreas


--
BOFH excuse #154:

You can tune a file system, but you can't tune a fish (from most tunefs man 
pages)

Processed: upstream tracks the issue

[Debian Bug Tracking System]

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

> forwarded 897758 https://github.com/ggcov/ggcov/issues/4
Bug #897758 [src:ggcov] ggcov: ftbfs with GCC-8
Set Bug forwarded-to-address to 'https://github.com/ggcov/ggcov/issues/4'.
> stop
Stopping processing here.

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

Bug#867451: python-pysolr/python3-pysolr: missing dependencies

[Andreas Beckmann]

On 2018-07-23 20:41, Dererk wrote:
> Hi Andreas.
> 
> Just for me to understand, should I re-build, upload to proposed-updates
> && request d-release@ ?
> 
> It has been some time since the last I did that, that why I wanted to
> avoid any mistakes from my end.

Let's wait for an ACK from the release team on the PU request. If you
don't mind, I'll upload it since I've already prepared it some time ago.


Andreas

Bug#897792: [Pkg-kde-extras] Bug#897792: Bug#897792: libqaccessibilityclient: ftbfs with GCC-8

[Pino Toscano]

In data lunedì 23 luglio 2018 15:38:47 CEST, Maximiliano Curia ha scritto:
> ¡Hola!
> 
> El 2018-05-04 a las 12:22 +, Matthias Klose escribió:
> > Package: src:libqaccessibilityclient
> > Version: 0.1.1-5
> > 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/libqaccessibilityclient_0.1.1-5_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
> 
> It seems to me that src:libqaccessibilityclient currently has not reverse 
> dependencies, and since it's still qt4 based, we might want to get rid of it. 

We actually do want to use it.

> Although, there is an "unstable" qt5 release
> (https://download.kde.org/unstable/libqaccessibilityclient/), and recent 
> versions of kmag seem to be trying to use that.

It seems misnamed, and actually the latest release in a while.

> Sandro, if you plan to upload libqaccessibilityclient 0.2 please close this 
> issue with it.

You could have checked this bug, see that I marked it as "pending",
and possibly imagined the issue was taken care already.

You could have checked its VCS:
https://salsa.debian.org/qt-kde-team/extras/libqaccessibilityclient
and noticing work on it, including this bug, and the Qt4 bug mentioned
above.

You could have also checked the kde-extras ML for possible uploads:
https://alioth-lists.debian.net/pipermail/pkg-kde-extras/2018-July/029275.html
... and its NEW entry:
https://ftp-master.debian.org/new/libqaccessibilityclient_0.2.0-1.html

But you did not, as usual, check for things. Sad.

-- 
Pino Toscano

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

Bug#867451: python-pysolr/python3-pysolr: missing dependencies

[Dererk]

Hi Andreas.

Just for me to understand, should I re-build, upload to proposed-updates 
&& request d-release@ ?


It has been some time since the last I did that, that why I wanted to 
avoid any mistakes from my end.



Thanks in advance.


\d


On 14/01/18 19:10, Andreas Beckmann wrote:

Followup-For: Bug #867451

stretch-pu request: https://bugs.debian.org/887321


Andreas


--
BOFH excuse #154:

You can tune a file system, but you can't tune a fish (from most tunefs man 
pages)

Bug#904365: marked as done (python3-cs: fails to install with Python 3.7)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jul 2018 18:50:12 +
with message-id 
and subject line Bug#904365: fixed in python-cs 2.3.1-1
has caused the Debian Bug report #904365,
regarding python3-cs: fails to install with Python 3.7
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.)


-- 
904365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-cs
Version: 2.1.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up python3-cs (2.1.6-1) ...
File "/usr/lib/python3/dist-packages/cs/__init__.py", line 101
  if 'Async' not in command and 'jobid' in response and not options.async:
^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/cs/client.py", line 36
  from cs.async import AIOCloudStack  # noqa
  ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-cs (--configure):
   installed python3-cs package post-installation script subprocess returned 
error exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-cs=2.1.6-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-cs
Source-Version: 2.3.1-1

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

Debian distribution maintenance software
pp.
Vincent Bernat  (supplier of updated python-cs 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, 23 Jul 2018 20:31:27 +0200
Source: python-cs
Binary: cs python-cs python3-cs
Architecture: source
Version: 2.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Vincent Bernat 
Changed-By: Vincent Bernat 
Description:
 cs - simple, yet powerful CloudStack API client
 python-cs  - simple, yet powerful CloudStack API client (Python module)
 python3-cs - simple, yet powerful CloudStack API client (Python 3 module)
Closes: 904365
Changes:
 python-cs (2.3.1-1) unstable; urgency=medium
 .
   * New upstream release.
  + Don't use async keyword anymore. Closes: #904365.
Checksums-Sha1:
 178b1801eefd321fe2867e52e4fc19935f7f7bf5 2202 python-cs_2.3.1-1.dsc
 4f79cc335168e0dc8e0d519d4a45aeae698eb54d 10786 python-cs_2.3.1.orig.tar.gz
 dce12e9159fb3394e3e21a23de1484b4df07bee2 3320 python-cs_2.3.1-1.debian.tar.xz
 e0f73b12155dd1e1a22c5a6fd07e6956c66559c5 8159 python-cs_2.3.1-1_amd64.buildinfo
Checksums-Sha256:
 41142e3749ff844352b65b56ab41f325a6e1eeda324d0050ee58a3e676161ce8 2202 
python-cs_2.3.1-1.dsc
 0fe4431a2abcc67921fda606ff5d26770cfda8889c31287db476fb0503ab342f 10786 
python-cs_2.3.1.orig.tar.gz
 4a00c8789ad23bbdb1946605f31fac799a5a8e5b279333a210427921037e73b7 3320 
python-cs_2.3.1-1.debian.tar.xz
 8e2ccead9d494a78c8f55ca27d14dac62a69c691d43af030ae6009fc0c8cfd2d 8159 
python-cs_2.3.1-1_amd64.buildinfo
Files:
 c530bf3db743c835af11daa81814a43b 2202 python optional python-cs_2.3.1-1.dsc
 2e9ef1a1c443a0d3f9d362f3e5e1caeb 10786 python optional 
python-cs_2.3.1.orig.tar.gz
 cc150d2eb3ef6839e596e2200df7a635 3320 python optional 
python-cs_2.3.1-1.debian.tar.xz
 c9b970c1fc44c54bc53744f95e0fa51e 8159 python optional 
python-cs_2.3.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAltWH9wSHGJlcm5hdEBk
ZWJpYW4ub3JnAAoJEJWkL+g1NSX5mHsP/326tpiDAFlS1BWutdGfd/aLYaoJHEVi
CtBhYo6EFHSrkB8a6acnpk2Q7PEA1o+Wo4Lc8RvzlSV2EaFed6hRGvH/HeGe8XDO
+/OvKeWXd0kiYPUOx4ZyuXvBpjW2vCrkbJloE7ma21jSZ6vqJLjVGlWIvyVNMsUt
Q4QBw221ACBO/4jFnvvuPMaZA8lV3r7BYe8BdhcPI5Pd9GO4DMSKgDnQeAqKbybV
22LOY2/hwLcuF2y8xY4r3K7/RALBhSe9g2aLHpjFjxfChSidAI+ujjn9wnbchy9i
4XzYRmWrp8nIeygbT2dcihPU1siyp7gFJG9ScwKx6rzHpIwjYpbeuzmu++hVa27b

Processed: python3-engineio: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 904350 904361 903457 902631 904371 902900 904370 902715 
904343 904298 903145 902817 902989 904368 903558 904357 904369 903218 904364 
903527 904363 903826 902766 902650 903031 903030 903526 904365 902761 904373 
902757 902646 903522 904382 904381 903525 904358 904351 903388 903529 904367 
903784 903423 902794 903528 903016
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904383

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

Bug#904383: python3-engineio: fails to install with Python 3.7

[Andreas Beckmann]

Package: python3-engineio
Version: 1.6.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up python3-engineio (1.6.1-1) ...
File "/usr/lib/python3/dist-packages/engineio/server.py", line 357
  ret = self._trigger_event('connect', sid, environ, async=False)
 ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/engineio/socket.py", line 56
  async=self.server.async_handlers)
  ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-engineio (--configure):
   installed python3-engineio package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   python3-engineio


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-engineio=1.6.1-1.log.gz
Description: application/gzip

Bug#904382: python3-doublex: fails to install with Python 3.7

[Andreas Beckmann]

Package: python3-doublex
Version: 1.8.2-1
Severity: serious
Tags: sid buster
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up python3-doublex (1.8.2-1) ...
File "/usr/lib/python3/dist-packages/doublex/matchers.py", line 129
  def async(self, timeout):
  ^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/doublex/test/async_race_condition_test.py", 
line 39
  assert_that(spy.write, called().async(1))
  ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/doublex/test/unit_tests.py", line 1333
  assert_that(spy.write, called().async(timeout=1))
  ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-doublex (--configure):
   installed python3-doublex package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   python3-doublex


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-doublex=1.8.2-1.log.gz
Description: application/gzip

Processed: python3-dns: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 903525 903030 902989 903558 902794 902715 904343 903528 
903423 903388 902646 904298 904364 904357 903784 904368 903522 902761 904369 
904350 902631 902817 903016 904371 904367 903218 903031 903145 904363 904365 
903527 902766 904373 904358 903526 904370 902900 902650 903826 904351 904361 
903457 902757 903529
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904381

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

Bug#904381: python3-dns: fails to install with Python 3.7

[Andreas Beckmann]

Package: python3-dns
Version: 3.1.1-1
Severity: serious
Tags: sid buster
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up python3-dns (3.1.1-1) ...
File "/usr/lib/python3/dist-packages/DNS/Base.py", line 96
  self.async=None
   ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-dns (--configure):
   installed python3-dns package post-installation script subprocess returned 
error exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-dns=3.1.1-1.log.gz
Description: application/gzip

Processed: python3-doublex: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 902757 902646 903526 903030 902650 902900 903826 904365 
904370 904373 903423 904369 903527 903522 903558 902761 902631 903145 903784 
902715 903529 904357 904361 904351 904364 903031 904363 903525 902794 904358 
902989 902766 904298 904343 903016 904350 903528 904368 904371 903388 902817 
903218 904367 904381 903457
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904382

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

Bug#904369: Bug #904369 in patroni marked as pending

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #904369 in patroni 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/postgresql/patroni/commit/21872714586ca7cf16282295cdf8e038ce2ee3de


Avoid using "async" which is a keyword in python3.7. Closes: #904369.



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/904369

Processed: Bug #904369 in patroni marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #904369 [patroni] patroni: fails to install with Python 3.7
Added tag(s) pending.

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

Processed: bug 904369 is forwarded to https://github.com/zalando/patroni/issues/750

[Debian Bug Tracking System]

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

> forwarded 904369 https://github.com/zalando/patroni/issues/750
Bug #904369 [patroni] patroni: fails to install with Python 3.7
Set Bug forwarded-to-address to 'https://github.com/zalando/patroni/issues/750'.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:ruby-doorkeeper

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:ruby-doorkeeper
> # 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 #903980 (http://bugs.debian.org/903980)
> # Bug title: ruby-doorkeeper: CVE-2018-1000211: Public apps can't revoke 
> OAuth access & refresh tokens in Doorkeeper
> #  * https://github.com/doorkeeper-gem/doorkeeper/issues/891
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 903980 + fixed-upstream
Bug #903980 [src:ruby-doorkeeper] ruby-doorkeeper: CVE-2018-1000211: Public 
apps can't revoke OAuth access & refresh tokens in Doorkeeper
Added tag(s) fixed-upstream.
> usertags 903980 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:snapd
> # 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 #897865 (http://bugs.debian.org/897865)
> # Bug title: snapd: ftbfs with GCC-8
> #  * https://github.com/snapcore/snapd/pull/5138
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 897865 + fixed-upstream
Bug #897865 [src:snapd] snapd: ftbfs with GCC-8
Added tag(s) fixed-upstream.
> usertags 897865 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:freefem++

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:freefem++
> # 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 #897751 (http://bugs.debian.org/897751)
> # Bug title: freefem++: ftbfs with GCC-8
> #  * https://github.com/FreeFem/FreeFem-sources/issues/18
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 897751 + fixed-upstream
Bug #897751 [src:freefem++] freefem++: ftbfs with GCC-8
Added tag(s) fixed-upstream.
> usertags 897751 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:php-db

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:php-db
> # 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 #889532 (http://bugs.debian.org/889532)
> # Bug title: php-db FTBFS with PHP 7.2
> #  * https://github.com/pear/DB/pull/5
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 889532 + fixed-upstream
Bug #889532 [src:php-db] php-db FTBFS with PHP 7.2
Added tag(s) fixed-upstream.
> usertags 889532 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 889532 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#904111: clamav-daemon causing deadlocks/blocking I/O.

[Richard Lucassen]

Same here (6 Postfix front-end servers), non-systemd, non-GUI system
running Debian Stretch. Downgrading to 0.99 is a workaround.
ScanOnAccess is set to false.

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
+--+

Bug#902470: Relates to numpy

[Alexandre Viau]

On 2018-07-23 11:47 AM, olivier sallou wrote:
> Looked at your pull request, but latest code update is still failing.

Yeah, my pull requests makes no attempt to fix the bug, only show it.

Previous Travis builds would pass because it used an older version of numpy.

> If issue is really only related to a str/repr problem, then I suppose
> that we could skip the failing test in the meanwhile to close the bug
> or lower its severity waiting for an upstream fix.

I'd be open to that, or maybe we can just ping xginn8 again.

Cheers <3

-- 
Alexandre Viau
av...@debian.org




signature.asc
Description: OpenPGP digital signature

Bug#904319: FTBFS when building binary-packages only

[Graham Inggs]

Control: severity -1 normal
Control: tags -1 + moreinfo unreproducible

Hi Daniel

On 23/07/2018 11:54, Daniel Baumann wrote:

However, when locally rebuilding the package I saw that it wants to
check the md5sum of the upstream tarball. This fails when building
binary packages only, which should be possible.


dpkg-buildpackage -b works fine for me.
How did you obtain the source package and what error message did you see?

Regards
Graham

Processed: Re: Bug#904319: FTBFS when building binary-packages only

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #904319 [src:intel-mkl] FTBFS when building binary-packages only
Warning: Unknown package 'src:intel-mkl'
Severity set to 'normal' from 'serious'
Warning: Unknown package 'src:intel-mkl'
> tags -1 + moreinfo unreproducible
Bug #904319 [src:intel-mkl] FTBFS when building binary-packages only
Warning: Unknown package 'src:intel-mkl'
Added tag(s) moreinfo and unreproducible.
Warning: Unknown package 'src:intel-mkl'

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

Bug#902470: Relates to numpy

[olivier sallou]

Le lun. 23 juil. 2018 à 17:38, Alexandre Viau  a écrit :

> On 2018-07-23 11:23 AM, olivier sallou wrote:
> > Maybe a bug should be filled upstream
>
> Hello,
>
> Thank you for caring and putting time into this.
>
> The bug is in influxdb-python due to a breaking change in numpy.
>
> I already marked the bug as forwarded with a link to the upstream bug,
> maybe you missed it?
>  - https://github.com/influxdata/influxdb-python/pull/596



>
>
> Forwarded tags don't appear in the discussion thread of the bug but they
> appear on the top of the page:
>  - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902470
>
>
I just saw it on bug page some minutes ago :-)


> The reason that tests pass with tox is that tox will download specific
> versions of packages so it will not test with Debian's packages.
>

yes, this is what I saw.
one of my packages depends on python-influxdb, this is why I care so much ,
my package will be removed if python-influxdb is removed.


Looked at your pull request, but latest code update is still failing.
If issue is really only related to a str/repr problem, then I suppose that
we could skip the failing test in the meanwhile to close the bug or lower
its severity waiting for an upstream fix.




>
> Cheers,
>
> --
> Alexandre Viau
> av...@debian.org
>
>

Bug#902470: Relates to numpy

[Alexandre Viau]

On 2018-07-23 11:23 AM, olivier sallou wrote:
> Maybe a bug should be filled upstream

Hello,

Thank you for caring and putting time into this.

The bug is in influxdb-python due to a breaking change in numpy.

I already marked the bug as forwarded with a link to the upstream bug,
maybe you missed it?
 - https://github.com/influxdata/influxdb-python/pull/596

Forwarded tags don't appear in the discussion thread of the bug but they
appear on the top of the page:
 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902470

The reason that tests pass with tox is that tox will download specific
versions of packages so it will not test with Debian's packages.

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#902470: created upstream issue

[olivier sallou]

I created an issue on upstream repo [0]

A temporary workaround could be to skip this test waiting for an upstream
resolution or explanation.
Indeed, problem may have no real incidence on usage but only on tests.
Bug could remain opened but lowered as it does not prevent its usage or
build.


[0] https://github.com/influxdata/influxdb-python/issues/622

Bug#904373: python3-opcua: fails to install with Python 3.7

[Andreas Beckmann]

Package: python3-opcua
Version: 0.95.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up python3-opcua (0.95.1-1) ...
File "/usr/lib/python3/dist-packages/opcua/common/utils.py", line 171
  task = asyncio.async(coro, loop=self.loop)
 ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-opcua (--configure):
   installed python3-opcua package post-installation script subprocess returned 
error exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python-opcua-tools=0.95.1-1.log.gz
Description: application/gzip

Bug#902470: Relates to numpy

[olivier sallou]

Installing numpy 1.13.3 (from pypi) which is used version in tox.ini makes
tests OK.
Fails with numpy 1.14.5 (debian default)

Maybe a bug should be filled upstream

Processed: python3-opcua: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 902989 904357 903145 904365 904298 903423 904371 904364 
903388 902766 902631 902761 902646 903016 903784 904343 904367 902650 904350 
903526 903527 904370 902794 903528 903030 904361 903218 903457 903529 902817 
903826 903525 903031 904351 902900 904368 902715 903558 904363 904358 903522 
904369 902757
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904373

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

Bug#902470: Works with tox, fails to nose

[olivier sallou]

I made a quick test and could reproduce the error using nose for testing.
However, using tox, all tests are ok (which is the tool described in readme
of repo)

Processed: openscap-daemon: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 904363 903527 902631 903784 903826 903016 903218 902650 
902761 904370 903145 904361 904298 902900 904369 904357 904343 902817 904350 
904368 902757 903457 902766 904365 902715 904351 904358 903031 903423 903529 
903526 903030 904364 903558 902646 904367 902794 903528 903522 903525 902989 
903388
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904371

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

Bug#904371: openscap-daemon: fails to install with Python 3.7

[Andreas Beckmann]

Package: openscap-daemon
Version: 0.1.10-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up openscap-daemon (0.1.10-2) ...
File "/usr/lib/python3/dist-packages/openscap_daemon/dbus_daemon.py", line 
84
  return self.system.async.get_status()
 ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/openscap_daemon/system.py", line 29
  from openscap_daemon import async
  ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package openscap-daemon (--configure):
   installed openscap-daemon package post-installation script subprocess 
returned error exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


openscap-daemon=0.1.10-2.log.gz
Description: application/gzip

Bug#904370: oca-core: fails to install with Python 3.7

[Andreas Beckmann]

Package: oca-core
Version: 11.0.20180420-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up oca-core (11.0.20180420-1) ...
File 
"/usr/lib/python3/dist-packages/odoo/addons/base/ir/ir_qweb/assetsbundle.py", 
line 103
  def to_html(self, sep=None, css=True, js=True, debug=False, async=False, 
url_for=(lambda url: url)):
  ^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/odoo/addons/base/ir/ir_qweb/ir_qweb.py", line 
194
  def _get_asset(self, xmlid, options, css=True, js=True, debug=False, 
async=False, values=None):
   ^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/odoo/addons/website/models/ir_qweb.py", line 26
  def _get_asset(self, xmlid, options, css=True, js=True, debug=False, 
async=False, values=None):
   ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package oca-core (--configure):
   installed oca-core package post-installation script subprocess returned 
error exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


oca-core=11.0.20180420-1.log.gz
Description: application/gzip

Processed: oca-core: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 904364 903527 903528 902631 903826 903218 904358 902650 
903526 902757 903388 903423 903016 903031 904351 903525 904357 902900 902989 
904363 902794 902817 902646 904361 903529 904368 903457 902715 902761 904369 
904367 903030 902766 903558 904298 903145 903784 904350 904365 904343 903522
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904370

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

Bug#904369: patroni: fails to install with Python 3.7

[Andreas Beckmann]

Package: patroni
Version: 1.4.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up patroni (1.4.4-1) ...
File "/usr/lib/python3/dist-packages/patroni/ha.py", line 610
  'offline':  dict(stop='fast', checkpoint=False, release=False, 
offline=True, async=False),

   ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package patroni (--configure):
   installed patroni package post-installation script subprocess returned error 
exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


patroni=1.4.4-1.log.gz
Description: application/gzip

Processed: patroni: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 903525 904363 903784 904361 903527 904298 903031 903522 
903528 903457 904367 903145 904365 904368 903529 904350 902631 904364 902715 
902817 902989 903526 902757 904358 902900 903030 903016 902646 904343 904351 
903826 903558 902650 903388 902761 902766 903423 902794 904357 903218
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904369

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

Bug#904368: python3-panoramisk: fails to install with Python 3.7

[Andreas Beckmann]

Package: python3-panoramisk
Version: 1.0-1
Severity: serious
Tags: sid buster
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up python3-panoramisk (1.0-1) ...
File "/usr/lib/python3/dist-packages/panoramisk/actions.py", line 64
  elif msg.endswith('successfully queued') and self.async != 'false':
^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/panoramisk/manager.py", line 212
  asyncio.async(ret, loop=self.loop)
  ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-panoramisk (--configure):
   installed python3-panoramisk package post-installation script subprocess 
returned error exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


panoramisk=1.0-1.log.gz
Description: application/gzip

Processed: python3-panoramisk: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 904363 903218 902631 902715 902794 902650 902766 903526 
903826 903784 904298 903016 904367 904343 902757 904361 903423 903558 902817 
904364 904351 903528 903527 904358 902900 903525 902646 904357 904350 903030 
902989 903031 903457 903388 903145 904365 903522 903529 902761
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904368

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

Processed: linux-show-player: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 902650 902794 903526 904351 902757 904298 904363 902715 
903016 903457 903558 902766 903528 902646 903030 903031 903218 904357 904350 
902989 903529 902761 903527 902631 903784 903145 904361 904358 902900 903388 
903826 904364 904365 903423 902817 903525 903522 904343
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904367

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

Bug#904367: linux-show-player: fails to install with Python 3.7

[Andreas Beckmann]

Package: linux-show-player
Version: 0.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up linux-show-player (0.5-1) ...
File "/usr/lib/python3/dist-packages/lisp/core/decorators.py", line 26
  def async(target):
  ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/lisp/core/signal.py", line 31
  from lisp.core.decorators import async
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/lisp/cues/cue.py", line 24
  from lisp.core.decorators import async
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/lisp/cues/media_cue.py", line 25
  from lisp.core.decorators import async
   ^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/lisp/modules/action_cues/command_cue.py", line 
25
  from lisp.core.decorators import async
   ^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/lisp/modules/action_cues/volume_control.py", 
line 28
  from lisp.core.decorators import async
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/lisp/modules/remote/controller.py", 
line 26
  from lisp.core.decorators import async
   ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package linux-show-player (--configure):
   installed linux-show-player package post-installation script subprocess 
returned error exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


linux-show-player=0.5-1.log.gz
Description: application/gzip

Bug#904366: mailutils-config and the mailutils tool are unusable in 1:3.4-1

[Sergey Poznyakoff]

Package: libmailutils-dev
Version: 1:3.4-1
Severity: serious

Hello,

Invoking mailutils-config with any argument results in:

$ mailutils-config --info
/usr/bin/mailutils-config: 115: /usr/bin/mailutils-config: mailutils: not found

This script is in fact a wrapper around the 'mailutils' tool, but the
tool itself is included in another packet, mailutils. Now, installing
mailutils doesn't make the situation any better:

$ mailutils-config --info
mailutils: don't know what info is

This is because the mailutils tool is a dispatcher command that calls
one of the specific standalone binaries from the pkglibexecdir to
perform the requested action (see the commit 444d20f3,
http://git.savannah.gnu.org/cgit/mailutils.git/commit/?id=444d20f3c).
Now, none of these binaries is included in the package (nor in any other
sub-package of mailutils, for that matter).

The script mailutils-config is used by the AM_MAILUTILS macro, defined in
/usr/share/aclocal/mailutils.m4. This means that this bug makes it
impossible to build any projects that depend on Mailutils and use this
macro in configure.ac to detect its presence. Therefore I qualified it
as serious.

To fix this, I would suggest to move usr/bin/mailutils from package
'mailutils' to 'libmailutils-dev' and to add all mailutils-*
binaries from the pkglibexecdir directory. The proposed patch is
attached.

The patch fixes the reported bug, yet reveals another (minor)
one. Please note the 'usr/lib/mailutils/mailutils/' path in the resulting
libmailutils-dev.install file. This is because
/usr/share/cdbs/1/class/autotools-vars.mk from cdbs sets the
DEB_CONFIGURE_LIBEXECDIR variable to "\$${prefix}/lib/$(DEB_SOURCE_PACKAGE)",
thereby defeating the purpose of libexecdir, for which GNU standards say
that this is

  [t]he directory for installing executable programs to be run by other
  programs rather than by users. 
  [...]
  The definition of 'libexecdir' is the same for all packages

This looks like yet another instance of the bug fixed long ago in debhelper:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541458. Perhaps it's
worth reporting to cdbs hackers. Anyway, adding

   DEB_CONFIGURE_LIBEXECDIR = \$${prefix}/lib

to the debian/rules will fix this as well (obviously the paths in the
attached file should be changed accordingly).

Best regards,
Sergey

diff -pur debian-orig/libmailutils-dev.install debian/libmailutils-dev.install
--- debian-orig/libmailutils-dev.install	2018-07-23 13:54:47.755922366 +
+++ debian/libmailutils-dev.install	2018-07-23 13:58:06.908660263 +
@@ -1,4 +1,6 @@
 usr/bin/mailutils-config
+usr/bin/mailutils
+usr/lib/mailutils/mailutils/mailutils-*
 usr/include/mailutils/*
 usr/lib/*/lib*.so
 usr/share/aclocal/mailutils.m4
diff -pur debian-orig/mailutils.install debian/mailutils.install
--- debian-orig/mailutils.install	2018-07-23 13:54:47.758922443 +
+++ debian/mailutils.install	2018-07-23 13:58:44.483808011 +
@@ -1,7 +1,6 @@
 usr/bin/dotlock.mailutils
 usr/bin/frm.mailutils
 usr/bin/from.mailutils
-usr/bin/mailutils
 usr/bin/mail.mailutils
 usr/bin/messages.mailutils
 usr/bin/mimeview

Bug#904365: python3-cs: fails to install with Python 3.7

[Andreas Beckmann]

Package: python3-cs
Version: 2.1.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up python3-cs (2.1.6-1) ...
File "/usr/lib/python3/dist-packages/cs/__init__.py", line 101
  if 'Async' not in command and 'jobid' in response and not options.async:
^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/cs/client.py", line 36
  from cs.async import AIOCloudStack  # noqa
  ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-cs (--configure):
   installed python3-cs package post-installation script subprocess returned 
error exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-cs=2.1.6-1.log.gz
Description: application/gzip

Processed: python3-cs: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 904343 903529 903522 903218 902715 903031 904357 902794 
902900 903826 902757 902989 904350 903525 903016 903558 904298 903423 902650 
902761 902646 903784 903528 904364 903526 904358 904351 903388 902817 903030 
904363 903527 902631 903457 903145 902766 904361
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904365

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

Processed: python3-azure: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 903218 904350 904343 903031 902631 902766 904358 903388 
903457 902817 903016 904361 903558 903526 902650 904363 902646 903528 903525 
902761 902900 903784 903522 902757 902989 903030 903527 903145 904351 903529 
904298 903423 902715 903826 902794 904357
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904364

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

Bug#862678: Switch from network-manager-dev to libnm-dev

[gregor herrmann]

On Sun, 22 Jul 2018 19:04:01 -0400, Ari Pollak wrote:

> Thanks Gregor. I'll upload a new version with this patch.

Great, thank you!


Cheers,
gregor
 
-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Stan Getz & Astrud Gilberto: Desafinado


signature.asc
Description: Digital Signature

Bug#904364: python3-azure: fails to install with Python 3.7

[Andreas Beckmann]

Package: python3-azure
Version: 20170915+git-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up python3-azure (20170915+git-1) ...
File 
"/usr/lib/python3/dist-packages/azure/servicemanagement/schedulermanagementservice.py",
 line 113
  return self._perform_put(path, body, async=True)
   ^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/azure/servicemanagement/servicemanagementclient.py",
 line 372
  def _perform_put(self, path, body, async=False, x_ms_version=None):
 ^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/azure/servicemanagement/servicemanagementservice.py",
 line 235
  async=True)
  ^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/azure/servicemanagement/websitemanagementservice.py",
 line 195
  xml, async=True)
   ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-azure (--configure):
   installed python3-azure package post-installation script subprocess returned 
error exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-azure=20170915+git-1.log.gz
Description: application/gzip

Processed: python3-applicationinsights: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 903529 903030 902989 904357 903218 902761 902650 902900 
903526 904350 902817 904358 904343 903145 903826 902757 904361 903558 903016 
903525 902631 903528 903527 903522 904351 902794 903031 902766 902715 904298 
903388 903457 903784 903423 902646
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904363

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

Bug#904363: python3-applicationinsights: fails to install with Python 3.7

[Andreas Beckmann]

Package: python3-applicationinsights
Version: 0.11.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up python3-applicationinsights (0.11.0-1) ...
File 
"/usr/lib/python3/dist-packages/applicationinsights/channel/contracts/RemoteDependencyData.py",
 line 256
  def async(self):
  ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-applicationinsights (--configure):
   installed python3-applicationinsights package post-installation script 
subprocess returned error exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-applicationinsights=0.11.0-1.log.gz
Description: application/gzip

Processed: python3-aiopg: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 903218 903016 903525 902900 903784 904357 903457 903522 
903528 903145 902757 904351 902766 902631 903529 902817 904358 903030 902646 
902761 903527 903031 902794 903423 902989 902715 904343 903558 903526 904350 
903388 903826 904298 902650
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904361

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

Bug#904361: python3-aiopg: fails to install with Python 3.7

[Andreas Beckmann]

Package: python3-aiopg
Version: 0.14.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up python3-aiopg (0.14.0-1) ...
File "/usr/lib/python3/dist-packages/aiopg/connection.py", line 109
  self._conn = psycopg2.connect(dsn, async=True, **kwargs)
 ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/aiopg/utils.py", line 18
  ensure_future = asyncio.async
  ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-aiopg (--configure):
   installed python3-aiopg package post-installation script subprocess returned 
error exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-aiopg=0.14.0-1.log.gz
Description: application/gzip

Processed: python3-aiozmq: fails to install with python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 904343 902631 904351 903030 902757 903784 902900 902794 
903528 902715 903388 903525 903527 904350 904298 902817 903031 903558 903529 
902650 902766 902989 902646 903016 903218 903457 903522 903423 903145 902761 
903526 904357 903826
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904358

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

Bug#904359: pandas 0.23.3 update needed for Python 3.7 compatibility

[Matthias Klose]

Package: src:pandas
Version: 0.22.0-8
Severity: serious
Tags: sid buster

an update to pandas 0.23.3 is needed for Python 3.7 compatibility.  Please
package the new upstream version.

Bug#904358: python3-aiozmq: fails to install with python 3.7

[Andreas Beckmann]

Package: python3-aiozmq
Version: 0.7.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up python3-aiozmq (0.7.1-2) ...
File "/usr/lib/python3/dist-packages/aiozmq/rpc/base.py", line 251
  fut = asyncio.async(coro, loop=self.loop)
^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-aiozmq (--configure):
   installed python3-aiozmq package post-installation script subprocess 
returned error exit status 1


"async" has become a reserved keyword in python 3.7


cheers,

Andreas


python3-aiozmq=0.7.1-2.log.gz
Description: application/gzip

Processed: python3-pysnmp4: fails to install with python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 904343 902715 903145 903388 903526 903826 904298 902900 
904351 902794 902761 903525 903457 903016 903558 902766 902646 902989 902817 
903528 903522 903527 903784 902631 903031 904350 903218 902757 902650 903423 
903529 903030
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904357

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

Processed: upstream tickets

[Debian Bug Tracking System]

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

> forwarded 897808 https://github.com/measurement-kit/measurement-kit/pull/1614
Bug #897808 [src:measurement-kit] measurement-kit: ftbfs with GCC-8
Set Bug forwarded-to-address to 
'https://github.com/measurement-kit/measurement-kit/pull/1614'.
> forwarded 897817 https://bugzilla.nasm.us/show_bug.cgi?id=3392461
Bug #897817 [src:nasm] nasm: ftbfs with GCC-8
Set Bug forwarded-to-address to 
'https://bugzilla.nasm.us/show_bug.cgi?id=3392461'.
> stop
Stopping processing here.

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

Bug#904357: python3-pysnmp4: fails to install with python 3.7

[Andreas Beckmann]

Package: python3-pysnmp4
Version: 4.4.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up python3-pysnmp4 (4.4.3-1) ...
File "/usr/lib/python3/dist-packages/pysnmp/carrier/asyncio/dgram/base.py", 
line 86
  self._lport = asyncio.async(c)
^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/pysnmp/carrier/asyncio/dispatch.py", 
line 72
  self.loopingcall = asyncio.async(self.handle_timeout())
 ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-pysnmp4 (--configure):
   installed python3-pysnmp4 package post-installation script subprocess 
returned error exit status 1


"async" has become a reserved keyword in python 3.7


cheers,

Andreas


ceilometer-common=1%10.0.0-5.log.gz
Description: application/gzip

Bug#903860: marked as done (python3-stem: File "/usr/lib/python3/dist-packages/stem/util/test/test_tools.py", line 151 / self.method.async = self

[Debian Bug Tracking System]

Your message dated Mon, 23 Jul 2018 13:51:23 +
with message-id 
and subject line Bug#903860: fixed in python-stem 1.6.0-2
has caused the Debian Bug report #903860,
regarding python3-stem: File 
"/usr/lib/python3/dist-packages/stem/util/test/test_tools.py", line 151 / 
self.method.async = self
/  ^
   /SyntaxError: invalid 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.)


-- 
903860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-stem
Version: 1.6.0-1
Severity: serious
Tags: a11y
Justification: fails to build from source

Dear Maintainer,



   * What led up to the situation?
Package was pulled in as a dependency for nyx which is a dependency for tor-arm 
and onionshare
   * What exactly did you do (or not do) that was effective (or
 ineffective)?  Have tried purging and building from source.  Have dpkg 
--purge to reinstall the package but was also not effective. 
   * What was the outcome of this action?
Package still will not install
   * What outcome did you expect instead?
Hoping a rebuild would have helped



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

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

Versions of packages python3-stem depends on:
ii  python3  3.6.6-1

python3-stem recommends no packages.

python3-stem suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python-stem
Source-Version: 1.6.0-2

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

Debian distribution maintenance software
pp.
Ulises Vitulli  (supplier of updated python-stem 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, 23 Jul 2018 10:25:51 -0300
Source: python-stem
Binary: python-stem python3-stem
Architecture: source all
Version: 1.6.0-2
Distribution: unstable
Urgency: high
Maintainer: Ulises Vitulli 
Changed-By: Ulises Vitulli 
Description:
 python-stem - Tor control library for Python
 python3-stem - Tor control library for Python 3 series
Closes: 903860
Changes:
 python-stem (1.6.0-2) unstable; urgency=high
 .
   * Patch for py3.7 compat issues on reserved words (Closes: #903860).
Checksums-Sha1:
 3b9fe6a0d44305586401285c32c949998f042a1a 1989 python-stem_1.6.0-2.dsc
 dba9413ea52f6f6c011c556481816b7be18449dc 4248 python-stem_1.6.0-2.debian.tar.xz
 004e810433ee44345df79185a2c22bdee77dfc77 256716 python-stem_1.6.0-2_all.deb
 130cdfe8b1d20b09ded7e31618aeac6278912aba 7430 
python-stem_1.6.0-2_amd64.buildinfo
 accd177badb2bc6414f244c8b4b716a9c79dc1a3 256812 python3-stem_1.6.0-2_all.deb
Checksums-Sha256:
 e2a8316462b3157c89082f1ae1e00673c00f47835efa892ef8f00b31012d77ed 1989 
python-stem_1.6.0-2.dsc
 c2e96ea80a47eae9b4a2e93358ded42899240f82483424b9387d9c980800b774 4248 
python-stem_1.6.0-2.debian.tar.xz
 3404080e3370ac7cf25748d2714a0962c8a0c3f28455d35f9d06f417c02b0ca4 256716 
python-stem_1.6.0-2_all.deb
 61e9bc395600172dba2d545b2ce48d6f374d84866162770f8ece813863e3ad09 7430 
python-stem_1.6.0-2_amd64.buildinfo
 dfdb804372a2c40996b840fd976677760d49a6e1e6e96250d456327f6e32726f 256812 
python3-stem_1.6.0-2_all.deb
Files:
 990c5fe47f0e0a300ee5403bd19e6301 1989 python optional python-stem_1.6.0-2.dsc
 c23f2793fa9b099b5205292384c0a7a1 4248 python optional 
python-stem_1.6.0-2.debian.tar.xz
 1eede75c75a040dbad58c8bb6b2dc0fc 256716 python optional 
python-stem_1.6.0-2_all.deb
 f85115aa890af4f8af11080de3eab449 7430 python optional 
python-stem_1.6.0-2_amd64.buildinfo
 13aac80a6c7eb77f1ef07c5fc42df1aa 256812 python optional 
python3-stem_1.6.0-2_all.deb

-BEGIN PGP SIGNATURE-

Bug#897792: [Pkg-kde-extras] Bug#897792: libqaccessibilityclient: ftbfs with GCC-8

[Maximiliano Curia]

¡Hola!

El 2018-05-04 a las 12:22 +, Matthias Klose escribió:

Package: src:libqaccessibilityclient
Version: 0.1.1-5
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/libqaccessibilityclient_0.1.1-5_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


It seems to me that src:libqaccessibilityclient currently has not reverse 
dependencies, and since it's still qt4 based, we might want to get rid of it. 
Although, there is an "unstable" qt5 release
(https://download.kde.org/unstable/libqaccessibilityclient/), and recent 
versions of kmag seem to be trying to use that.


I'm ccing Sandro, as he might be working in kmag and adding the support of 
libqaccessibilityclient to our packages [1].


[1]: 
https://salsa.debian.org/qt-kde-team/kde/kmag/commit/6fd9637477b4eb9da465e3c5fe782352a20f607a

Sandro, if you plan to upload libqaccessibilityclient 0.2 please close this 
issue with it.


Happy hacking,
--
"Executive ability is deciding quickly and getting somebody else to do the
work."
-- Pollard's Postulate
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#902631: devscripts: CI fails in unstable due to Python 3.7

[Pierre-Elliott Bécue]

Le dimanche 22 juillet 2018 à 20:43:02-0400, Sandro Tosi a écrit :
> On Sun, Jul 22, 2018 at 8:31 PM Mattia Rizzolo  wrote:
> >
> > On Sun, Jul 22, 2018 at 03:52:04PM -0400, Sandro Tosi wrote:
> > > thanks for ignoring the next paragraph in that email, so let me re-add it 
> > > here:
> >
> > I didn't ignore it, I explicitly picked on your first, fairly taunting,
> > and inappropriately passive-aggressive sentence (like this one).
> 
> good good

Mmh, I tend to admit that Sandro's answers can be blunt. I assume it may be
connected with a busy life, but sometimes it's a little awkward.

That said, I'd rather all of us to act/behave accordingly to [1], please.
Because we're all smart people, with good intentions, who share common
values (the ones that made us join Debian). :)

> > > since astroid/pylint only support python 3.4+, it is not as simple as
> > > package the new version and upload it; i'm not even (yet) sure buster
> > > should have 2.0 but maybe it should to 1.9
> >
> > This is a fairly common situation for distributors.
> >
> > Did you also evaluate the feasibility and practicality of working on a
> > patch to introduce py3.7 compatibility to the current 1.6.5?
> 
> no, i didnt look into it myself: upstream dismissed the forwarded bug
> saying to upgrade to 2.0 to get 3.7 support.
> 
> if someone wants to try and dedicate time to that effort, that'd be
> welcome and please attach a patch here when ready.

Would you consider repackaging 1.6.5 without py3 support and provide another
package with exclusive py3 support? That'd ease the drop of py2 in a few
years, and, also, avoid big horrible patches. If you agree with this kind of
idea I'd be pleased to provide the new package work and a team patch for the
current package.

If you really wish to go by a patch for 1.6.5, I'll try to do it after the
end of my PhD thesis manuscript writing.

Sincerely

[1] https://www.debian.org/code_of_conduct.en.html

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#904351: python3-astroquery: fails to install with python 3.7

[Andreas Beckmann]

Package: python3-astroquery
Version: 0.3.8+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up python3-astroquery (0.3.8+dfsg-2) ...
File 
"/usr/lib/python3/dist-packages/astroquery/vo_conesearch/conesearch.py", line 26
  from .async import AsyncBase
^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-astroquery (--configure):
   installed python3-astroquery package post-installation script subprocess 
returned error exit status 1


"async" has become a reserved keyword in python 3.7


cheers,

Andreas


python3-astroquery=0.3.8+dfsg-2.log.gz
Description: application/gzip

Processed: python3-astroquery: fails to install with python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 903527 902794 903522 904298 903826 902650 904350 903529 
902646 902761 903145 903423 903218 902757 902715 904343 903526 903457 902766 
903525 903558 903030 902900 903016 903388 903784 903528 902631 902989 903031 
902817
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904351

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

Bug#897780: many packages automremoval due to GCC 8

[Andreas Tille]

On Mon, Jul 23, 2018 at 02:41:29PM +0200, Mattia Rizzolo wrote:
> > [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897780
> 
> Looking at that bug, the 7 new symbols that appeared are of that
> category I was talking about (looking at the unmangled naming that
> c++filt reports they are things like:
> 
> + std::_Rb_tree_iterator std::vector, 
> std::allocator >, std::allocator std::char_traits, std::allocator > > > > > std::_Rb_tree std::pair std::char_traits, std::allocator >, 
> std::allocator, 
> std::allocator > > > >, std::_Select1st std::vector, 
> std::allocator >, std::allocator std::char_traits, std::allocator > > > > >, std::greater, 
> std::allocator std::vector, 
> std::allocator >, std::allocator std::char_traits, std::allocator > > > > > 
> >::_M_emplace_hint_unique std::tuple, std::tuple<> >(std::_Rb_tree_const_iterator const, std::vector, 
> std::allocator >, std::allocator std::char_traits, std::allocator > > > > >, 
> std::piecewise_construct_t const&, std::tuple&&, std::tuple<>&&)@Base 
> 2.4.0-3
> 
> which is ... not something people should usually care about…), and if
> added they should have the '(optional)' tag (incidentally, it feels to me
> that also all the surrounding symbols should).  However, that's not the
> error, dpkg-gensymbols wouldn't fail for new symbols by default, but
> only if some disappear: you should check the ones that disappeared.

OK, maintainer in CC.
 
> Also, I noticed the rules file is doing some funky renaming to have the
> symbols file apply only on amd64.  I recommend you go read
> dpkg-gensymbols(1) and discover architecture-specific symbols file.

This was actually my recommendation following an "the perfect is the
enemy of the good" principle.  We checked the possibility of having
architecture-specific symbols files for all libbpp* libs.  However, it
turned out that the effort to maintain this would be at least one order
of magnitude higher than every other maintenance work for these
packages.  Since having symbols files on amd64 in principle serves the
purpose of detecting ABI changes and the software is in practice used
only here I suggested this solution to the maintainer (who is also
upstream).  (This should be somewhere recorded on one Debian Med list -
I'm to offline-ish currently to seek for this.)

Kind regards

 Andreas.
-- 
http://fam-tille.de

Processed: snakemake: fails to install with python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 903031 902761 903526 902757 903527 902817 903218 902631 
903558 902715 903826 904298 904343 902794 903388 902650 903423 903457 903525 
903016 903529 903784 903030 902989 903522 902900 902766 902646 903145 903528
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904350

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

Bug#904350: snakemake: fails to install with python 3.7

[Andreas Beckmann]

Package: snakemake
Version: 5.1.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up snakemake (5.1.5-1) ...
File "/usr/lib/python3/dist-packages/snakemake/shell.py", line 69
  async=False,
  ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package snakemake (--configure):
   installed snakemake package post-installation script subprocess returned 
error exit status 1


"async" has become a reserved keyword in python 3.7


cheers,

Andreas


snakemake=5.1.5-1.log.gz
Description: application/gzip

Bug#903698: marked as done (sphinxbase: build appears broken for multiple python3 versions)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jul 2018 13:34:11 +
with message-id 
and subject line Bug#903698: fixed in dh-python 3.20180723
has caused the Debian Bug report #903698,
regarding sphinxbase: build appears broken for multiple python3 versions
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.)


-- 
903698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinxbase
Version: 0.8+5prealpha+1-2
Severity: serious

Hi all,

sphinxbase is currently involved in the python3.7 "transition"¹. I
noticed that sphinxbase was rebuild, but that is was still listed in the
"bad" category. I took a look at the amd64 build log² and spotted the
following some oddities in python3-sphinxbase.

1) it has only has the 3.6 dependencies (hence listed as bad)
2) it only has 3.7 site-packages files
3) _sphinxbase.cpython-37m-x86_64-linux-gnu.so points to a non-exitent
file. The file is in the 3.7 site-packages directory.
4) python3 versions in the build are first 3.7 and then 3.6, they seem
to be using the same build directory.

I think this is caused by the fact that we loop over $pyver in the
d/rules file, but apparently that is broken for multiple python3 versions.

I think the package is probably not working currently hence I file this
bug. (I don't know how to fix it properly yet, maybe Samuel has ideas?).

Paul

¹ https://release.debian.org/transitions/html/python3.7.html
²
https://buildd.debian.org/status/fetch.php?pkg=sphinxbase=amd64=0.8%2B5prealpha%2B1-2%2Bb1=1530298945=0



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: dh-python
Source-Version: 3.20180723

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

Debian distribution maintenance software
pp.
Piotr Ożarowski  (supplier of updated dh-python 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, 23 Jul 2018 14:39:41 +0200
Source: dh-python
Binary: dh-python
Architecture: source all
Version: 3.20180723
Distribution: unstable
Urgency: medium
Maintainer: Piotr Ożarowski 
Changed-By: Piotr Ożarowski 
Description:
 dh-python  - Debian helper tools for packaging Python libraries and applicatio
Closes: 739500 801710 894203 903698
Changes:
 dh-python (3.20180723) unstable; urgency=medium
 .
   * dh-python depends on python3-distutils (as most package that use dh-python
 would have to depend on it anyway, closes: 894203)
   * dh_python{2,3}:
 - fix \.so.* symlink renaming for non-default Python versions
   (closes: 739500, 903698)
 - when files cannot be shared between Python versions because of
   differences, print (in --verbose mode) a unified diff for diagnostic
   purposes (closes: 801710, thanks to Barry Warsaw for the original patch)
Checksums-Sha1:
 f794b3f8da70ad54c22b31de2620debca5f70f36 1874 dh-python_3.20180723.dsc
 707b59e4688ffd6a960f3733341314a02d589940 96212 dh-python_3.20180723.tar.xz
 122e4f6f5c65bc26fc6c10962185774127b33d88 94204 dh-python_3.20180723_all.deb
 7ed6cec750945864a2dfd27e1033cd0f7eab3c52 6556 
dh-python_3.20180723_amd64.buildinfo
Checksums-Sha256:
 10e07cc33c7085d663b9ee8d201b3ae2d6f6db76b5429b2a8db6a846f12eecd4 1874 
dh-python_3.20180723.dsc
 4faf130d654eba94e2551c3e180a75893df0773448d492fea32f15a4eea4bcfa 96212 
dh-python_3.20180723.tar.xz
 b71ce8ba73b89257963bb043605123a7146f810097846437d4a2b74aab0cd8ec 94204 
dh-python_3.20180723_all.deb
 14d1cc2427817037994b24ea173b135e2ba07199be8851892434fe0aba6695e8 6556 
dh-python_3.20180723_amd64.buildinfo
Files:
 a934f3f0dc4794649970aa4fd6d6e1d7 1874 python optional dh-python_3.20180723.dsc
 a4c1f1650959b6981b91aa9981c02f32 96212 python optional 
dh-python_3.20180723.tar.xz
 8df1c817a035acf478f5e03d9e00fd14 94204 python optional 
dh-python_3.20180723_all.deb
 3410b3fb467701849f6b38bb2eed454a 6556 python optional 
dh-python_3.20180723_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEHS+omFjar2IXhi33rvbxoqdFdkUFAltV0xsACgkQrvbxoqdF

Bug#904347: prewikka: /bin/prewikka-crontab fails with SyntaxError

[Andreas Beckmann]

Package: prewikka
Version: 4.1.5-2
Severity: serious

Hi,

/bin/prewikka-crontab fails with a SyntaxError:

$ /bin/prewikka-crontab
  File "/bin/prewikka-crontab", line 74
os.umask(027)
   ^
SyntaxError: invalid token


Andreas

Bug#897816: marked as done (mwrap: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jul 2018 13:21:24 +
with message-id 
and subject line Bug#897816: fixed in mwrap 0.33-7
has caused the Debian Bug report #897816,
regarding mwrap: 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.)


-- 
897816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mwrap
Version: 0.33-4
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/mwrap_0.33-4_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

[...]
 fprintf(fp, "const mxArray*", v->name);
 ^~~~
mwrap-cgen.cc:300:21: warning: too many arguments for format 
[-Wformat-extra-args]
 fprintf(fp, "%s*", v->basetype, v->name);
 ^
mwrap-cgen.cc: In function 'void mex_unpack_input_array(FILE*, Var*)':
mwrap-cgen.cc:683:13: warning: too many arguments for format 
[-Wformat-extra-args]
 "} else\n"
 ^~
 "in%d_ = NULL;\n",
 ~
g++ -Wl,-z,relro -o ../mwrap mwrap.o lex.yy.o mwrap-ast.o mwrap-typecheck.o 
mwrap-mgen.o mwrap-cgen.o
make[2]: Leaving directory '/<>/src'
make[1]: Leaving directory '/<>'
   dh_auto_test -a
make -j8 -Oline test
make[1]: Entering directory '/<>'
(cd testing; make)
make[2]: Entering directory '/<>/testing'
make[2]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
make[2]: Leaving directory '/<>/testing'
make[2]: Entering directory '/<>/testing'
../mwrap -mex test_transfersmex \
-c test_transfersmex.cc \
-m test_transfers.m test_transfers.mw
mkoctfile --mex test_transfersmex.cc
../mwrap -cppcomplex \
-mex test_cpp_complexmex \
-c test_cpp_complexmex.cc \
-m test_cpp_complex.m test_cpp_complex.mw
mkoctfile --mex test_cpp_complexmex.cc
../mwrap -c99complex \
-mex test_c99_complexmex \
-c test_c99_complexmex.c \
-m test_c99_complex.m test_c99_complex.mw
mkoctfile --mex test_c99_complexmex.c
../mwrap -cppcomplex test_syntax.mw 2> test_syntax.log
make[2]: [Makefile:28: test_syntax] Error 139 (ignored)
diff test_syntax.log test_syntax.ref
2c2
< Segmentation fault
---
> Parse error (test_syntax.mw:8): syntax error, unexpected $end, expecting ';'
make[2]: *** [Makefile:29: test_syntax] Error 1
make[2]: Leaving directory '/<>/testing'
make[1]: *** [Makefile:9: test] Error 2
make[1]: Leaving directory '/<>'
dh_auto_test: make -j8 -Oline test returned exit code 2
make: *** [debian/rules:5: build-arch] Error 25
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2
--- End Message ---
--- Begin Message ---
Source: mwrap
Source-Version: 0.33-7

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

Debian distribution maintenance software
pp.
Rafael Laboissiere  (supplier of updated mwrap 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

Processed: block 902788 with 902817

[Debian Bug Tracking System]

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

> block 902788 with 902817
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 903528 902631 903388 902757 903784 903031 903558 903522 
902766 903030 903016 902761 902646 902900 903826 902989 902794 903525 903529 
904298 903457 903423 903218 902715 904343 903527 903526 902650 903145
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 902817
> thanks
Stopping processing here.

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

Processed: python3-morse-simulator: fails to install with python 3.7 as a supported python version

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 902646 903423 903016 903527 902715 903031 903218 903528 
902794 903522 902766 904298 903457 903558 902757 903826 902650 903145 903784 
902900 903525 903526 902761 903529 903030 902989 902631 903388
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904343

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

Bug#904343: python3-morse-simulator: fails to install with python 3.7 as a supported python version

[Andreas Beckmann]

Package: python3-morse-simulator
Version: 1.4-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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...):

  Setting up python3-morse-simulator (1.4-3) ...
File "/usr/lib/python3/dist-packages/morse/core/request_manager.py", line 
140
  def register_service(self, component_name, callback, service_name = None, 
async = False):

^
  SyntaxError: invalid syntax

File "/usr/lib/python3/dist-packages/morse/core/services.py", line 110
  def do_service_registration(fn, component_name = None, service_name = 
None, async = False, request_managers = None):

  ^
  SyntaxError: invalid syntax

File 
"/usr/lib/python3/dist-packages/morse/middleware/ros_request_manager.py", line 
396
  return services.service(fn, component = None, name = name, async = True)
 ^
  SyntaxError: invalid syntax

  dpkg: error processing package python3-morse-simulator (--configure):
   installed python3-morse-simulator package post-installation script 
subprocess returned error exit status 1


"async" has become a reserved keyword in python 3.7


cheers,

Andreas


morse-simulator=1.4-3.log.gz
Description: application/gzip

Bug#902117: [Debian-ha-maintainers] Bug#902117: corosync-qdevice will not daemonize/run

[Valentin Vidic]

On Fri, Jul 06, 2018 at 12:50:42PM +0200, Ferenc Wágner wrote:
> Thanks for the report.  I've been pretty busy with other tasks, but I'll
> check this out as soon as possible, your report isn't forgotten.  I ask
> for you patience till then.

Feri, you still want to check this or should we close this issue?

-- 
Valentin