Bug#891057: marked as done (gcc-defaults: gcc-* cross-toolchains uninstallable.)

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2018 05:58:07 +0100
with message-id <8f3f8b3b-3b0d-ff21-f70b-e7ecdd9fa...@debian.org>
and subject line Re: gcc-defaults: gcc-* cross-toolchains uninstallable.
has caused the Debian Bug report #891057,
regarding gcc-defaults: gcc-* cross-toolchains uninstallable.
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.)


-- 
891057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-defaults
Severity: serious
Version: 1.173d1

Thanks for all your work on keeping cross-toolchains up to date!

Currently, gcc-defaults has gcc-aarch64-linux-gnu depend on
gcc-7-aarch64-linux-gnu, which is no longer available in sid, presumably
replaced by gcc-8-aarch64-linux-gnu.

Similar for the other cross-toolchains such as gcc-arm-linux-gnueabi and
gcc-arm-linux-gnueabihf, which makes crossbuild-essential-*
uninstallable, which makes cross-building packages difficult.


live well,
  vagrant


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
now fixed with the recent gcc-7-cross* uploads.--- End Message ---

Bug#893049: marked as done (libfiu FTBFS: recipe for target 'run-test-basic_ctrl.py' failed)

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2018 04:08:38 +
with message-id 
and subject line Bug#893049: fixed in libfiu 0.95-6
has caused the Debian Bug report #893049,
regarding libfiu FTBFS: recipe for target 'run-test-basic_ctrl.py' failed
to be marked as done.

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

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


-- 
893049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libfiu
Version: 0.95-5
Severity: serious

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

...
./generate-test -c tests/malloc.conf -o tests/malloc.c
make[4]: Leaving directory '/<>/tests/generated'
make[4]: Entering directory '/<>/tests/utils'
LD_LIBRARY_PATH=../../libfiu/ ./test-basic_ctrl.py > 
output-test-basic_ctrl.py.txt 2>&1
Makefile:38: recipe for target 'run-test-basic_ctrl.py' failed
make[4]: *** [run-test-basic_ctrl.py] Error 1
--- End Message ---
--- Begin Message ---
Source: libfiu
Source-Version: 0.95-6

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

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

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated libfiu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Mar 2018 19:05:21 -0700
Source: libfiu
Binary: libfiu0 fiu-utils libfiu-dev python-fiu python3-fiu
Architecture: source amd64
Version: 0.95-6
Distribution: unstable
Urgency: medium
Maintainer: Chris Lamb 
Changed-By: Chris Lamb 
Description:
 fiu-utils  - userspace fault injection framework (utilities)
 libfiu-dev - userspace fault injection framework (development libraries)
 libfiu0- userspace fault injection framework
 python-fiu - userspace fault injection framework (Python bindings)
 python3-fiu - userspace fault injection framework (Python 3 bindings)
Closes: 893049
Changes:
 libfiu (0.95-6) unstable; urgency=medium
 .
   * LD_PRELOAD libfiu.so explicitly to avoid test failure. (Closes: #893049)
Checksums-Sha1:
 3df178e50126051dbc09d7babfa9d6b3c952a76f 2114 libfiu_0.95-6.dsc
 0ae1523f48edde9de1af323b1c9506cfa7d6787f 5976 libfiu_0.95-6.debian.tar.xz
 119a93a4829ccb59bdcaa2d8f777cd4a25ee07cb 11704 fiu-utils_0.95-6_amd64.deb
 5fb8e58f041d9646daf6630f07264f836aad9cc8 28016 libfiu-dev_0.95-6_amd64.deb
 69b820dce76dbb2af1f7dd37c87ba5f42c664934 66076 libfiu0-dbgsym_0.95-6_amd64.deb
 208028fe5543cdf0960f87724c74196819ed8c42 25836 libfiu0_0.95-6_amd64.deb
 f30898482b5840c21bf768ff206def219c339061 8433 libfiu_0.95-6_amd64.buildinfo
 bfa2f6a109ed4b3a93ea34169d4fd6374bac7fee 12408 
python-fiu-dbgsym_0.95-6_amd64.deb
 cf503227f0a9ff862c86883ac7a54975832bcc0d 11248 python-fiu_0.95-6_amd64.deb
 3ec31dc344bdcad9e0eec5ca1b509e167675f6a0 13792 
python3-fiu-dbgsym_0.95-6_amd64.deb
 f68bfa72410c179e7920bb7b98b20ddacc190dc0 11356 python3-fiu_0.95-6_amd64.deb
Checksums-Sha256:
 bf526fedaa4a3a312a626365759bd85a685aa96a5a38ff065bb7c7ac136116b6 2114 
libfiu_0.95-6.dsc
 fe91867f861d983d5736daf60f9f361fc50f1707a7c6604675db8e8b803eb026 5976 
libfiu_0.95-6.debian.tar.xz
 936a8c79d77636b7c3c74f8b37ad51d9621e5b50568dcbfff458c539faf344c8 11704 
fiu-utils_0.95-6_amd64.deb
 951f69fae7d1053bbd6868022c1a0c94584ec5d14072f3662d9be80ddfe69bbb 28016 
libfiu-dev_0.95-6_amd64.deb
 eb2983914cef34690f9fec268b5c749fb1ca33e25613f02f55996e4231db1ce6 66076 
libfiu0-dbgsym_0.95-6_amd64.deb
 bf27ea25785d9dfb424b1ee3c6e4b276a4284708c90543c0ba26e00c502ed675 25836 
libfiu0_0.95-6_amd64.deb
 96e65304e9791e84f414b0d636aa42ecabf08ca008f09db2cc1be60f6899e39b 8433 
libfiu_0.95-6_amd64.buildinfo
 f7cffc93ee8757de8f1e7e344a4bf24edb513b9d50f02cb9c4a906c65ec548f3 12408 
python-fiu-dbgsym_0.95-6_amd64.deb
 3f29a0283244a5056d55f5e7a495d0b1e8d9c9780636cd903752dd6a76730b6a 11248 
python-fiu_0.95-6_amd64.deb
 f264e26478f3a870f5fe4852933a07270f11ced464d48a28b14546db6f511944 13792 
python3-fiu-dbgsym_0.95-6_amd64.deb
 15695bc245983b760531254b138a0d4af24f8d281a889f48abca973c0907fae6 11356 
python3-fiu_0.95-6_amd64.deb
Files:
 c9fc14b2ff5523c1e84fa38892fc9653 2114 libs 

Bug#760660: marked as done (bindgraph, don't startup.)

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2018 04:06:13 +
with message-id 
and subject line Bug#760660: fixed in bindgraph 0.2a-6
has caused the Debian Bug report #760660,
regarding bindgraph, don't startup.
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.)


-- 
760660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bindgraph
Version: 0.2a-5.1
Severity: important

Dear Maintainer,

I have installed the bindgraph, but it does not start a message similar to the 
following is displayed.

# /etc/init.d/bindgraph start
[] Starting DNS Statistics: /usr/sbin/bindgraph.plPrototype mismatch: sub 
Parse::Syslog::str2time ($$$) vs () at 
/usr/share/perl5/Parse/Syslog.pm line 121.
Subroutine str2time redefined at /usr/share/perl5/Parse/Syslog.pm line 66.
Subroutine new redefined at /usr/share/perl5/Parse/Syslog.pm line 138.
Subroutine _next_line redefined at /usr/share/perl5/Parse/Syslog.pm line 206.
Subroutine next redefined at /usr/share/perl5/Parse/Syslog.pm line 388.
Not enough arguments for Parse::Syslog::str2time at /usr/sbin/bindgraph.pl line 
264, near "})"
BEGIN not safe after errors--compilation aborted at /usr/sbin/bindgraph.pl line 
282.
 (warning).



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

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages bindgraph depends on:
ii  debconf [debconf-2.0]  1.5.53
ii  libfile-tail-perl  0.99.3-5
ii  librrds-perl   1.4.8-1.1+b1

Versions of packages bindgraph recommends:
ii  apache2-bin [httpd]  2.4.10-1
ii  apache2-mpm-itk [httpd]  2.4.10-1
ii  apache2-mpm-prefork [httpd]  2.4.10-1
ii  apache2-mpm-worker [httpd]   2.4.10-1
ii  bind91:9.9.5.dfsg-4

bindgraph suggests no packages.

-- debconf information:
  bindgraph/stay_on_purge: true
  bindgraph/start_on_boot: true
  bindgraph/logfile: /var/log/bind9-query.log
--- End Message ---
--- Begin Message ---
Source: bindgraph
Source-Version: 0.2a-6

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated bindgraph 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: Fri, 16 Mar 2018 04:19:06 +0100
Source: bindgraph
Binary: bindgraph
Architecture: source
Version: 0.2a-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Description:
 bindgraph  - DNS statistics RRDtool frontend for BIND9
Closes: 668730 760660
Changes:
 bindgraph (0.2a-6) unstable; urgency=medium
 .
   * QA upload.
   * Set Maintainer to Debian QA Group.  (See #838074)
   * Switch to debhelper compat level 11 with minimal dh rules.
   * Switch to Priority: optional.
   * Add bindgraph_startup.patch, thanks to Joseph Nahmias.  (Closes: #760660)
   * Remove /var/log/bind9-query.log on purge.  (Closes: #668730)
   * Fix some Lintian issues.
Checksums-Sha1:
 13343031ba7720fd3fe50a27176d6c1781581f17 1741 bindgraph_0.2a-6.dsc
 43e3a42f4662dc21e49f570c5f6eeb2ef7270280 20488 bindgraph_0.2a-6.debian.tar.xz
 4c9e1098cd30ae30dcb7e74dee6e9f93a19e8170 5257 bindgraph_0.2a-6_source.buildinfo
Checksums-Sha256:
 bfcb3f67a0884e1ef53ff87023a9d17b94bea7280f53eb2e495fe052a21d154f 1741 
bindgraph_0.2a-6.dsc
 4308e01c1a1fa89d492a26430a62970eb3b8096690b375efdd88a6e03ac34d77 20488 
bindgraph_0.2a-6.debian.tar.xz
 cd0fa84c9b5c3971c64a6454cc4c2ea55941cda44daa443fe0e315116c88e98a 5257 
bindgraph_0.2a-6_source.buildinfo
Files:
 85a090802af4b05ab705615f6cfab8c5 1741 admin optional bindgraph_0.2a-6.dsc
 406189e4e1c406532d4d6730414a599b 20488 admin optional 
bindgraph_0.2a-6.debian.tar.xz
 5bcb9aacd6ffb4c7fa7eee8af5c770f6 5257 admin optional 

Bug#784302: marked as done (/usr/sbin/bindgraph.pl: Prototype mismatch: sub Parse::Syslog::str2time)

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2018 04:06:13 +
with message-id 
and subject line Bug#760660: fixed in bindgraph 0.2a-6
has caused the Debian Bug report #760660,
regarding /usr/sbin/bindgraph.pl: Prototype mismatch: sub 
Parse::Syslog::str2time
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.)


-- 
760660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bindgraph
Version: 0.2a-5.1
Severity: normal

Hello,

It seems that bindgraph has an issue with the perl routine 
Parse::Syslog::str2time.  Here's the output when I try to start bindgraph:

# /etc/init.d/bindgraph start
[] Starting DNS Statistics: /usr/sbin/bindgraph.plPrototype mismatch: sub 
Parse::Syslog::str2time ($$$) vs () at 
/usr/share/perl5/Parse/Syslog.pm line 121.
Subroutine str2time redefined at /usr/share/perl5/Parse/Syslog.pm line 66.
Subroutine new redefined at /usr/share/perl5/Parse/Syslog.pm line 138.
Subroutine _next_line redefined at /usr/share/perl5/Parse/Syslog.pm line 206.
Subroutine next redefined at /usr/share/perl5/Parse/Syslog.pm line 388.
Not enough arguments for Parse::Syslog::str2time at /usr/sbin/bindgraph.pl line 
264, near "})"
BEGIN not safe after errors--compilation aborted at /usr/sbin/bindgraph.pl line 
282.
 (warning).


Thanks,
--Joe

-- System Information:
Debian Release: 8.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

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

Versions of packages bindgraph depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  libfile-tail-perl  0.99.3-5
ii  librrds-perl   1.4.8-1.2

Versions of packages bindgraph recommends:
ii  bind9 1:9.9.5.dfsg-9
ii  lighttpd [httpd]  1.4.35-4

bindgraph suggests no packages.

-- debconf information:
  bindgraph/logfile: /var/log/bind9-query.log
  bindgraph/stay_on_purge: true
  bindgraph/start_on_boot: true
--- End Message ---
--- Begin Message ---
Source: bindgraph
Source-Version: 0.2a-6

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated bindgraph 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: Fri, 16 Mar 2018 04:19:06 +0100
Source: bindgraph
Binary: bindgraph
Architecture: source
Version: 0.2a-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Description:
 bindgraph  - DNS statistics RRDtool frontend for BIND9
Closes: 668730 760660
Changes:
 bindgraph (0.2a-6) unstable; urgency=medium
 .
   * QA upload.
   * Set Maintainer to Debian QA Group.  (See #838074)
   * Switch to debhelper compat level 11 with minimal dh rules.
   * Switch to Priority: optional.
   * Add bindgraph_startup.patch, thanks to Joseph Nahmias.  (Closes: #760660)
   * Remove /var/log/bind9-query.log on purge.  (Closes: #668730)
   * Fix some Lintian issues.
Checksums-Sha1:
 13343031ba7720fd3fe50a27176d6c1781581f17 1741 bindgraph_0.2a-6.dsc
 43e3a42f4662dc21e49f570c5f6eeb2ef7270280 20488 bindgraph_0.2a-6.debian.tar.xz
 4c9e1098cd30ae30dcb7e74dee6e9f93a19e8170 5257 bindgraph_0.2a-6_source.buildinfo
Checksums-Sha256:
 bfcb3f67a0884e1ef53ff87023a9d17b94bea7280f53eb2e495fe052a21d154f 1741 
bindgraph_0.2a-6.dsc
 4308e01c1a1fa89d492a26430a62970eb3b8096690b375efdd88a6e03ac34d77 20488 
bindgraph_0.2a-6.debian.tar.xz
 cd0fa84c9b5c3971c64a6454cc4c2ea55941cda44daa443fe0e315116c88e98a 5257 
bindgraph_0.2a-6_source.buildinfo
Files:
 85a090802af4b05ab705615f6cfab8c5 1741 admin optional bindgraph_0.2a-6.dsc
 406189e4e1c406532d4d6730414a599b 20488 admin optional 
bindgraph_0.2a-6.debian.tar.xz
 5bcb9aacd6ffb4c7fa7eee8af5c770f6 5257 admin optional 
bindgraph_0.2a-6_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#893066: python3-zaqar-ui: fails to upgrade from 'testing' - trying to overwrite /usr/share/openstack-dashboard/openstack_dashboard/enabled/_1510_project_messaging_group.py

[Andreas Beckmann]

Package: python3-zaqar-ui
Version: 4.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' 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...):

  Selecting previously unselected package python3-zaqar-ui.
  Preparing to unpack .../16-python3-zaqar-ui_4.0.0-1_all.deb ...
  Unpacking python3-zaqar-ui (4.0.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-RfrGCs/16-python3-zaqar-ui_4.0.0-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/openstack-dashboard/openstack_dashboard/enabled/_1510_project_messaging_group.py',
 which is also in package python-zaqar-ui 1.0.0~rc1-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-RfrGCs/16-python3-zaqar-ui_4.0.0-1_all.deb


cheers,

Andreas


python-zaqar-ui=1.0.0~rc1-2_python3-zaqar-ui=4.0.0-1.log.gz
Description: application/gzip

Processed: Re: libfiu FTBFS: recipe for target 'run-test-basic_ctrl.py' failed

[Debian Bug Tracking System]

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

> tags 893049 + pending
Bug #893049 [src:libfiu] libfiu FTBFS: recipe for target 
'run-test-basic_ctrl.py' failed
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#893049: libfiu FTBFS: recipe for target 'run-test-basic_ctrl.py' failed

[Chris Lamb]

tags 893049 + pending
thanks

[Adding albert...@blitiri.com.ar to CC]

> https://buildd.debian.org/status/package.php?p=libfiu=sid
> 
> ...
> ./generate-test -c tests/malloc.conf -o tests/malloc.c
> make[4]: Leaving directory '/<>/tests/generated'
> make[4]: Entering directory '/<>/tests/utils'
> LD_LIBRARY_PATH=../../libfiu/ ./test-basic_ctrl.py > 
> output-test-basic_ctrl.py.txt 2>&1
> Makefile:38: recipe for target 'run-test-basic_ctrl.py' failed
> make[4]: *** [run-test-basic_ctrl.py] Error 1

Adrian, I've fixed this in Git, pending upload:

  
https://github.com/lamby/pkg-libfiu/commit/55bcc37af0b142ddd4e121802df8ebb45e723d9e

Alberto, do you know why this is now required? (Feel free to take
the patch upstream, naturally...)


Regards,

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

Processed: stardict: Raising severity of libgnome rdepends bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886045 [src:stardict] stardict: Depends on gconf
Severity set to 'serious' from 'important'

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

Processed: stardict: Raising severity of libgnome rdepends bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #868405 [src:stardict] stardict: Please drop the (build-)dependency against 
gnome-vfs
Severity set to 'serious' from 'important'

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

Bug#893065: ironic-inspector: fails to install: ironic-inspector-dbsync: not found

[Andreas Beckmann]

Package: ironic-inspector
Version: 7.2.0-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...):

  Selecting previously unselected package ironic-inspector.
  (Reading database ... 
(Reading database ... 16191 files and directories currently installed.)
  Preparing to unpack .../ironic-inspector_7.2.0-2_all.deb ...
  Unpacking ironic-inspector (7.2.0-2) ...
  Setting up ironic-inspector (7.2.0-2) ...
  sh: 1: ironic-inspector-dbsync: not found
  dpkg: error processing package ironic-inspector (--configure):
   installed ironic-inspector package post-installation script subprocess 
returned error exit status 127
  Errors were encountered while processing:


cheers,

Andreas


ironic-inspector_7.2.0-2.log.gz
Description: application/gzip

Bug#892956: libinput-dev: Requires.private without package dependencies breaks pkg-config users

[Jeremy Bicha]

By the way, meson's error message for this situation was very unhelpful.

See https://bugzilla.gnome.org/794313 where gnome-bluetooth was
affected. (I simply added the extra dependencies to the Debian package
once I figured out what happened.)

Thanks,
Jeremy Bicha

Bug#890954: closed by Michael Gilbert <mgilb...@debian.org> (Bug#890954: fixed in chromium-browser 65.0.3325.146-2)

[Georg Faerber]

Hi,

I can confirm this works now. Thanks for the work, Michael!

Cheers,
Georg


signature.asc
Description: Digital signature

Bug#892884: Bug #892884 in neutron-taas marked as pending

[thomas]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/services/neutron-taas/commit/54013f2dba61c3becca03c6e39bc86da132d4803


changelog  (Closes: #892884)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/892884

Processed: Bug #892884 in neutron-taas marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #892884 [python-neutron-taas] python-neutron-taas build-depends on cruft 
package python-neutron
Added tag(s) pending.

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

Processed: Bug #892884 in neutron-taas marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #892884 [python-neutron-taas] python-neutron-taas build-depends on cruft 
package python-neutron
Ignoring request to alter tags of bug #892884 to the same tags previously set

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

Bug#892884: Bug #892884 in neutron-taas marked as pending

[thomas]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/services/neutron-taas/commit/54013f2dba61c3becca03c6e39bc86da132d4803


changelog  (Closes: #892884)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/892884

Bug#884563: Bug #884563 in networking-sfc marked as pending

[thomas]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/services/networking-sfc/commit/6b2ebcbc7d27d624c4164db9c1a7c1fa08afae11


New version fixes:
- Fixes FTBFS (Closes: #884563).
- Works with SQLA 1.1 (Closes: #852800).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/884563

Processed: Bug #852800 in networking-sfc marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #852800 [python-networking-sfc] python-networking-sfc: uninstallable, needs 
to support python-sqlalchemy 1.1
Ignoring request to alter tags of bug #852800 to the same tags previously set

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

Processed: Bug #884563 in networking-sfc marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #884563 [src:networking-sfc] networking-sfc: FTBFS: tests fail with 
AttributeError: 'module' object has no attribute 'NAME_MAX_LEN'
Ignoring request to alter tags of bug #884563 to the same tags previously set

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

Bug#884563: Bug #884563 in networking-sfc marked as pending

[thomas]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/services/networking-sfc/commit/6b2ebcbc7d27d624c4164db9c1a7c1fa08afae11


New version fixes:
- Fixes FTBFS (Closes: #884563).
- Works with SQLA 1.1 (Closes: #852800).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/884563

Processed: Bug #852800 in networking-sfc marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #852800 [python-networking-sfc] python-networking-sfc: uninstallable, needs 
to support python-sqlalchemy 1.1
Added tag(s) pending.

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

Bug#852800: Bug #852800 in networking-sfc marked as pending

[thomas]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/services/networking-sfc/commit/6b2ebcbc7d27d624c4164db9c1a7c1fa08afae11


New version fixes:
- Fixes FTBFS (Closes: #884563).
- Works with SQLA 1.1 (Closes: #852800).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/852800

Bug#852800: Bug #852800 in networking-sfc marked as pending

[thomas]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/services/networking-sfc/commit/6b2ebcbc7d27d624c4164db9c1a7c1fa08afae11


New version fixes:
- Fixes FTBFS (Closes: #884563).
- Works with SQLA 1.1 (Closes: #852800).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/852800

Processed: Bug #884563 in networking-sfc marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #884563 [src:networking-sfc] networking-sfc: FTBFS: tests fail with 
AttributeError: 'module' object has no attribute 'NAME_MAX_LEN'
Added tag(s) pending.

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

Bug#892108: marked as done (nim FTBFS on arm64/ppc64el: Nim_and_C_compiler_disagree_on_target_architecture)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 22:35:18 +
with message-id 
and subject line Bug#892108: fixed in nim 0.18.0-2
has caused the Debian Bug report #892108,
regarding nim FTBFS on arm64/ppc64el: 
Nim_and_C_compiler_disagree_on_target_architecture
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.)


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

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

...
PATH=./bin/:$PATH  ./build.sh --os linux --cpu arm64
# OS: linux
# CPU: arm
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -w -O3 -fno-strict-aliasing -Ic_code -c 
c_code/2_1/compiler_nim.c -o c_code/2_1/compiler_nim.o
In file included from c_code/2_1/compiler_nim.c:7:0:
c_code/nimbase.h:477:13: error: size of array 
'Nim_and_C_compiler_disagree_on_target_architecture' is negative
 typedef int Nim_and_C_compiler_disagree_on_target_architecture[sizeof(NI) == 
sizeof(void*) && NIM_INTBITS == sizeof(NI)*8 ? 1 : -1];
 ^~
debian/rules:18: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---
Source: nim
Source-Version: 0.18.0-2

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

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

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

Debian distribution maintenance software
pp.
Federico Ceratto  (supplier of updated nim package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Mar 2018 21:57:32 +
Source: nim
Binary: nim nim-doc
Architecture: source
Version: 0.18.0-2
Distribution: unstable
Urgency: medium
Maintainer: Federico Ceratto 
Changed-By: Federico Ceratto 
Description:
 nim- Nim programming language - compiler
 nim-doc- Nim programming language - documentation
Closes: 892108
Changes:
 nim (0.18.0-2) unstable; urgency=medium
 .
   * Install txt files
   [ Frédéric Bonnard ]
   * Fix FTBFS on ppc64, ppc64el, arm64 and re-enable mips64el (Closes: #892108)
Checksums-Sha1:
 17028f36be1f76bbffd9223e3fe0cf535b789139 1997 nim_0.18.0-2.dsc
 4cf316458f3de5a2d158c3b4e0dd50b1e2c4987e 10312 nim_0.18.0-2.debian.tar.xz
 0b458e8015b9f8c43f6f8aaf200906057e6bf107 5932 nim_0.18.0-2_amd64.buildinfo
Checksums-Sha256:
 58edbb41e41bfc17bc7a9e3e397e06580f06df5b0a18fbf888c6d31d45823526 1997 
nim_0.18.0-2.dsc
 49fc2d3a4c15e254b632a5b8e702948814e51dce0612ae4fb3b1621f615c4a49 10312 
nim_0.18.0-2.debian.tar.xz
 c364f498df392921426035b30ce91922b912d44e3ef3d7b49d1fb510327b191e 5932 
nim_0.18.0-2_amd64.buildinfo
Files:
 25298956acffbd36078bf42bed685a3b 1997 devel optional nim_0.18.0-2.dsc
 fa7d14d08d8440a38dfe639ca0b14218 10312 devel optional 
nim_0.18.0-2.debian.tar.xz
 e186646b0d1631233ab055c1b815bf75 5932 devel optional 
nim_0.18.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfKfd+zM5IUCMbyuWbzG8RPUXfaoFAlqq7/AACgkQbzG8RPUX
faquaxAAkxPQaRT3SQKGvpnVbch8ICOSURHHPVx16XRP3ze0PS6jbsCoHU2tpkHG
KfLvcEIhpbbnvRkvfSxN7KHPX1C/H3FivFssneUnLJrUgiyF1R/FTIFWJ0W1izqq
fKIOSZjIXPF5ew6MbT5n4yAc6xyOWDxhub4P0TVoiW1bMJ1asMFrFJN3QaybEdZ1
dDnqVQQIkFNGfojbpmGVYI9BjnUzgBY2DAwoWBn7XG3DhNkMrvmdjqFqZiYjmwys
eBkT9ZTh2dqDd1+XuWsjzDAoT6Q8p+AORgFN7F1Nj89kLC8vivelJWBr4loPcIaY
XByW/PzPgR112975nFk1ib6Sw/lBl+tdh1N0JKbcQq5+HfF51gn+rw+z+paN9Wqc
3fwWI56xMg4/Tk5z4N2yQ61uQhakM04mjeXGLBEKFG/TbrDbG1vBgK2hzMZqFooT
WJfxv2yKNOz26cLz7Cgo8eDPn0C9UTz3YnlTH42+eHpCDlG01eEZm4B4FBN/7oT6
lLfKjl/h51JulZLI3I6tn8fR3/YyArKFZC5LzEKMDftJi6+oXorjFqCMP+Afsxmw
ACeXaPKdnNSiq6LS2HYWvE4uvt75UluypsRHTJ8fggjwwQCH9fKdw5D7jEVl4eMc
T2I5nYL1ESMTltRA4xvcsLWpCwYaVuzLCmitZt5X/OFndeZGU+0=
=D8sc
-END PGP SIGNATURE End Message ---

Bug#891656: marked as done (Adblockers fail to start)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 18:21:50 -0400
with message-id 

Bug#890954: marked as done (With this version all extensions crash)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 18:21:50 -0400
with message-id 

Bug#892509: marked as done ([chromium] uBlock Origin extension do not work anymore)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 18:21:50 -0400
with message-id 

Bug#892956: Additional info

[Jussi Pakkanen]

Hi

The -llibfoo thing is obviously wrong, we'll need to get that fixed.

The private one is a bit trickier. We generate private requires
because they are needed for static linkin. This is where pkg-config
behaves a bit strangely:

For --libs, private depends are not listed unless you use --static.

For --cflags, private depends are always listed.

The problem here is that an arguable case can be made for listing the
headers without --static and also for not doing that. I would have
expected the latter behaviour but apparently based on pkg-config's Git
repo they have explicitly made it do the former.

Bug#893051: prometheus-mysqld-exporter FTBFS on 32bit: global_variables_test.go:79:67: constant 2147483648 overflows int

[Adrian Bunk]

Source: prometheus-mysqld-exporter
Version: 0.10.0+git20180201.a71f4bb+ds-1
Severity: serious

https://buildd.debian.org/status/package.php?p=prometheus-mysqld-exporter=sid

...
   dh_auto_test -a -O--buildsystem=golang
cd obj-i686-linux-gnu && go test -vet=off -v -p 4 
github.com/prometheus/mysqld_exporter 
github.com/prometheus/mysqld_exporter/collector
# github.com/prometheus/mysqld_exporter/collector
src/github.com/prometheus/mysqld_exporter/collector/global_variables_test.go:79:67:
 constant 2147483648 overflows int
=== RUN   TestParseMycnf

  Various .my.cnf configurations 
Local tcp connection ✔
Local tcp connection on non-default port ✔
Socket connection ✔
Socket connection ignoring defined host ✔
Remote connection ✔
Missed user ✔
Missed password ✔
No [client] section ✔
Invalid config ✔


9 total assertions

--- PASS: TestParseMycnf (0.00s)
=== RUN   TestBin
=== RUN   TestBin/mysqld_exporter
=== RUN   
TestBin/mysqld_exporter/github.com/prometheus/mysqld_exporter.testLandingPage
=== PAUSE 
TestBin/mysqld_exporter/github.com/prometheus/mysqld_exporter.testLandingPage
=== CONT  
TestBin/mysqld_exporter/github.com/prometheus/mysqld_exporter.testLandingPage
--- PASS: TestBin (4.19s)
--- PASS: TestBin/mysqld_exporter (0.00s)
--- PASS: 
TestBin/mysqld_exporter/github.com/prometheus/mysqld_exporter.testLandingPage 
(1.00s)
PASS
ok  github.com/prometheus/mysqld_exporter   4.204s
FAILgithub.com/prometheus/mysqld_exporter/collector [build failed]
dh_auto_test: cd obj-i686-linux-gnu && go test -vet=off -v -p 4 
github.com/prometheus/mysqld_exporter 
github.com/prometheus/mysqld_exporter/collector returned exit code 2
debian/rules:22: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2

Bug#893049: libfiu FTBFS: recipe for target 'run-test-basic_ctrl.py' failed

[Adrian Bunk]

Source: libfiu
Version: 0.95-5
Severity: serious

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

...
./generate-test -c tests/malloc.conf -o tests/malloc.c
make[4]: Leaving directory '/<>/tests/generated'
make[4]: Entering directory '/<>/tests/utils'
LD_LIBRARY_PATH=../../libfiu/ ./test-basic_ctrl.py > 
output-test-basic_ctrl.py.txt 2>&1
Makefile:38: recipe for target 'run-test-basic_ctrl.py' failed
make[4]: *** [run-test-basic_ctrl.py] Error 1

Bug#893050: pyopencl FTBFS: ModuleNotFoundError: No module named 'pyopencl'

[Adrian Bunk]

Source: pyopencl
Version: 2018.1.1-1
Severity: serious

Some recent change in unstable makes pyopencl FTBFS:

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

...
I: pybuild base:215: make -C /build/1st/pyopencl-2018.1.1/doc html
make[2]: Entering directory '/build/1st/pyopencl-2018.1.1/doc'
python3 make_constants.py > constants.inc
Traceback (most recent call last):
  File "make_constants.py", line 25, in 
import pyopencl as cl
ModuleNotFoundError: No module named 'pyopencl'
make[2]: *** [Makefile:38: constants] Error 1

Bug#892529: marked as done (java-common: Depends on GCJ which is going away)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 21:39:51 +
with message-id 
and subject line Bug#892529: fixed in java-common 0.61
has caused the Debian Bug report #892529,
regarding java-common: Depends on GCJ which is going away
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.)


-- 
892529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: java-common
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcj-rm

Hi,

java-common depends or build-depends on GCJ. GCJ has been dropped
upstream since GCC 7, so we are dropping it from Debian. Thus please
either drop support for GCJ if you are just building an alternative
package with GCJ support (e.g. ant-gcj, ecj-gcj) or switch to
default-jdk / default-jre as appropriate.

Cheers, Emilio 
--- End Message ---
--- Begin Message ---
Source: java-common
Source-Version: 0.61

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated java-common package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Mar 2018 19:59:44 +0100
Source: java-common
Binary: java-common default-jre default-jre-headless default-jdk 
default-jdk-headless default-jdk-doc default-java-plugin gcj-native-helper
Architecture: source
Version: 0.61
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Matthias Klose 
Description:
 default-java-plugin - Default Java Plugin for running applets and Java Web 
Start applic
 default-jdk - Standard Java or Java compatible Development Kit
 default-jdk-doc - Standard Java or Java compatible Development Kit 
(documentation)
 default-jdk-headless - Standard Java or Java compatible Development Kit 
(headless)
 default-jre - Standard Java or Java compatible Runtime
 default-jre-headless - Standard Java or Java compatible Runtime (headless)
 gcj-native-helper - Standard helper tools for creating gcj native packages
 java-common - Base package for Java runtimes
Closes: 892529
Changes:
 java-common (0.61) unstable; urgency=medium
 .
   * Don't build jre/jdk defaults packages on platforms still relying
 on java 5 (provided by gcj). Closes: #892529.
   * Remove kfreebsd-amd64 kfreebsd-i386 from java9_architectures.
   * Prepare the default values for Java 11
   * Stop building gcj-native-helper.
   * java_defaults.mk: Add two new macros:
 - java_default_architectures
 - java_dependency, call as $(call java_dependency, default-jdk)
   -> default-jdk [!hppa !ia64 !s390 !sparc !hurd-i386]
Checksums-Sha1:
 5a52504510d4b7fdc4838ebebc2943fd53407275 2134 java-common_0.61.dsc
 c012967b38133fed839211b58e09f62f07c5888e 13332 java-common_0.61.tar.xz
 bf54a92b9b4b8d9675bdcaf436ae66944a4b4254 5652 java-common_0.61_source.buildinfo
Checksums-Sha256:
 47dbcb15ebe0482323ed3b75be078fc91a0e9c66dc01a4a39de574b7f027d4d7 2134 
java-common_0.61.dsc
 f6882255bfd9f9580f49cdc584fff533d89d4adb234f01cb161986b380c7faae 13332 
java-common_0.61.tar.xz
 aec0680e7011e349ffb5ae82c3b329575393012218f6298a05e6b01127414eff 5652 
java-common_0.61_source.buildinfo
Files:
 f47f2512e5147d2de6a5361203b582b3 2134 java optional java-common_0.61.dsc
 6804c0855ca66691cefa5baceee1ece9 13332 java optional java-common_0.61.tar.xz
 7f98a7f0c189d288c47dcb30a3f29cac 5652 java optional 
java-common_0.61_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlqq4dEQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9cGFEACWePBHNboQPY+XCdjRT2AjTNSNhgeqA5SP
09rxf/gfu11TzN1NTQ1vZeQHcb/ch826X1I606nZ3H/zEYN532a+QKDh2fqsan/y
fGYxkAic+Idgb8I8Pip/6Ogppr+IeqvOtXFJRmuR/ELkdSzaESSPSm35lq4sIUf2
IPcx4VelfM9HQc4tM5IUSiKptMXIJj1+NJpX7SpsDnwEOANAU0E9tm0y3YgkDe2t
5Ogn3gL/tLpjrGOWr+Vv+03H1Eqk9aPSiELelB0CgqBjv0YE8kzyIvHXgNjui2gd
Mvrx28xw0FGXjAqYs+tDmXMqhbVFj72esvDzbaT80D/fOsiwjSsgNDBXTqjMlgyo

Bug#888127: Fix available in 0.7.1

[Nish Aravamudan]

Specifically, 
https://github.com/ruby-grape/grape-entity/commit/03d3b928ee7d1c48fdfa9bf55b150eee46d5e572

which I believe is in 0.7.0 and 0.7.1. uscan/uupdate finds it, but
patches need refreshing, and there is a new build-dependency on
ruby-simplecov.

-- 
Nishanth Aravamudan
Ubuntu Server
Canonical Ltd

Bug#893047: maxima FTBFS: INTERNAL-SIMPLE-PACKAGE-ERROR: Package error on #<"MAXIMA" package>: Cannot import symbol as it will produce a name conflict

[Adrian Bunk]

Source: maxima
Version: 5.41.0-2
Severity: serious

Some recent change in unstable makes maxima FTBFS:

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

...
Compiling /build/1st/maxima-5.41.0/src/mhayat.lisp.
End of Pass 1.  
End of Pass 2.  
OPTIMIZE levels: Safety=0 (No runtime error checking), Space=0, Speed=3
Finished compiling binary-gcl/mhayat.o.

;  - Loading binary file "binary-gcl/mhayat.o" 
;- Compiling source file "/build/1st/maxima-5.41.0/src/optimize.lisp" 
Compiling /build/1st/maxima-5.41.0/src/optimize.lisp.
End of Pass 1.  
End of Pass 2.  
OPTIMIZE levels: Safety=0 (No runtime error checking), Space=0, Speed=3
Finished compiling binary-gcl/optimize.o.

;- Loading binary file "binary-gcl/optimize.o" 
Error: 
Fast links are on: do (si::use-fast-links nil) for debugging
Signalled by IMPORT.
Condition in IMPORT [or a callee]: INTERNAL-SIMPLE-PACKAGE-ERROR: Package error 
on #<"MAXIMA" package>: Cannot import symbol as it will produce a name conflict

Broken at IMPORT.  Type :H for Help.
1  Return to top level. 
MAXIMA>>make[2]: *** [Makefile:1305: sys-proclaim.lisp] Error 255

Bug#893044: slurm-llnl: CVE-2018-7033: Issue in accounting_storage/mysql plugin by always escaping strings within the slurmdbd

[Salvatore Bonaccorso]

Source: slurm-llnl
Version: 14.03.9-5
Severity: grave
Tags: patch security upstream
Forwarded: https://bugs.schedmd.com/show_bug.cgi?id=4792

Hi,

the following vulnerability was published for slurm-llnl, filling as
grave to be on safe side, but details are yet not disclosed in the
upstream report.

CVE-2018-7033[0]:
|Issue in accounting_storage/mysql plugin by always escaping strings
|within the slurmdbd

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-7033
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7033
[1] https://bugs.schedmd.com/show_bug.cgi?id=4792

Regards,
Salvatore

Bug#893040: libseafile0: contains a python module

[Helmut Grohne]

Package: libseafile0
Version: 6.1.5-1
Severity: serious
Justification: policy 8.2

libseafile0 contains a python module "ccnet". The Debian policy section
8.2 prohibits shipping soname-independent files with the shared library
package:

| If your package contains files whose names do not change with each
| change in the library shared object version, you must not put them in
| the shared library package.

Please package it separately in a properly named python-seafile package.

Helmut

Bug#893039: libccnet0: contains a python module

[Helmut Grohne]

Package: libccnet0
Version: 6.1.5-1
Severity: serious
Justification: policy 8.2

libccnet0 contains a python module "ccnet". The Debian policy section
8.2 prohibits shipping soname-independent files with the shared library
package:

| If your package contains files whose names do not change with each
| change in the library shared object version, you must not put them in
| the shared library package.

Please package it separately in a properly named python-ccnet package
(that already exists somewhat in debian/control).

Helmut

Bug#853480: marked as done (libaqbanking: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 21:13:53 +0100
with message-id <20180315201353.ahwv3c4qftzal...@fuzzy.home.lenk.info>
and subject line Re: Bug#853480: libaqbanking: ftbfs with GCC-7
has caused the Debian Bug report #853480,
regarding libaqbanking: ftbfs with GCC-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.)


-- 
853480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libaqbanking
Version: 5.6.12-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/libaqbanking_5.6.12-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 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-7/porting_to.html

[...]
make[4]: Entering directory '/<>/doc'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/<>/doc'
Making all in m4
make[4]: Entering directory '/<>/m4'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/<>/m4'
Making all in src
make[4]: Entering directory '/<>/src'
Making all in libs
make[5]: Entering directory '/<>/src/libs'
Making all in aqbanking
make[6]: Entering directory '/<>/src/libs/aqbanking'
Making all in types
make[7]: Entering directory '/<>/src/libs/aqbanking/types'
/bin/bash ../../../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H 
-I. -I../../../.. -I../../../../aqbanking5   -Wdate-time -D_FORTIFY_SOURCE=2 
-DBUILDING_AQBANKING -fvisibility=hidden -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -g -Wall -Wdeclaration-after-statement -c -o 
accstatus.lo accstatus.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../.. 
-I../../../../aqbanking5 -Wdate-time -D_FORTIFY_SOURCE=2 -DBUILDING_AQBANKING 
-fvisibility=hidden -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -g -Wall 
-Wdeclaration-after-statement -c accstatus.c  -fPIC -DPIC -o .libs/accstatus.o
In file included from ../../../../aqbanking5/aqbanking/accstatus.h:18:0,
 from accstatus_l.h:18,
 from accstatus_p.h:18,
 from accstatus.c:19:
../../../../aqbanking5/aqbanking/value.h:18:10: fatal error: 
gwenhywfar/buffer.h: No such file or directory
 #include 
  ^
compilation terminated.
Makefile:645: recipe for target 'accstatus.lo' failed
make[7]: *** [accstatus.lo] Error 1
make[7]: Leaving directory '/<>/src/libs/aqbanking/types'
Makefile:971: recipe for target 'all-recursive' failed
make[6]: *** [all-recursive] Error 1
make[6]: Leaving directory '/<>/src/libs/aqbanking'
Makefile:500: recipe for target 'all-recursive' failed
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory '/<>/src/libs'
Makefile:500: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory '/<>/src'
Makefile:821: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/<>'
Makefile:593: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
debian/rules:31: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Hi Matthias,

according to the [build logs] GCC-7 seems to be the default compiler
now.  And 

Processed: affects 892956

[Debian Bug Tracking System]

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

> affects 892956 libappstream-glib-dev src:flatpak
Bug #892956 [meson] meson creates bogus pkgconfig files
Added indication that 892956 affects libappstream-glib-dev and src:flatpak
> thanks
Stopping processing here.

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

Bug#892275: [redshift]

[gregor herrmann]

Control: tag -1 unreproducible
Control: severity -1 important

On Wed, 07 Mar 2018 14:45:29 +0100, Wild Turtles wrote:

> Package: redshift
> Version: 1.11-1
> Severity: grave
> 
> Redshift (and -gtk) crash at startup.
> 
> Error message is the next : 
> 
> Failed to run Redshift
> Trying location provider 'geoclue2' …
> Unable to connect to GeoClue.
> Unable to get location from provider.

redshift still works for me (haven't tried redshift-gtk), both with
the manual and the geoclue2 location provider.
I'm adjusting the bug metadata is this doesn't seem to be a general
problem.
 
> A bug is open upstream with some (geo)clues.
> https://github.com/jonls/redshift/issues/158

... where bigon argues that /usr/share/applications/redshift.desktop
should be enough, and this file is indeed installed by the Debian
package.
 

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: Bob Dylan: Early Roman Kings


signature.asc
Description: Digital Signature

Processed: Re: Bug#892275: [redshift]

[Debian Bug Tracking System]

Processing control commands:

> tag -1 unreproducible
Bug #892275 [redshift] redshift: Unable to connect to GeoClue.
Added tag(s) unreproducible.
> severity -1 important
Bug #892275 [redshift] redshift: Unable to connect to GeoClue.
Severity set to 'important' from 'grave'

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

Bug#893031: vowpal-wabbit: Baseline violation on i386 and FTBFS on !x86

[Adrian Bunk]

Source: vowpal-wabbit
Version: 8.5.0.dfsg1-2
Severity: serious

https://buildd.debian.org/status/package.php?p=vowpal-wabbit=sid

MMX and SSE are not part of the i386 port baseline
and must not be used there.

Trying to use -msse on !x86 results in FTBFS.

Bug#892529: marked as done (java-common: Depends on GCJ which is going away)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 19:19:33 +
with message-id 
and subject line Bug#892529: fixed in java-common 0.60
has caused the Debian Bug report #892529,
regarding java-common: Depends on GCJ which is going away
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.)


-- 
892529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: java-common
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcj-rm

Hi,

java-common depends or build-depends on GCJ. GCJ has been dropped
upstream since GCC 7, so we are dropping it from Debian. Thus please
either drop support for GCJ if you are just building an alternative
package with GCJ support (e.g. ant-gcj, ecj-gcj) or switch to
default-jdk / default-jre as appropriate.

Cheers, Emilio 
--- End Message ---
--- Begin Message ---
Source: java-common
Source-Version: 0.60

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated java-common package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Mar 2018 19:59:44 +0100
Source: java-common
Binary: java-common default-jre default-jre-headless default-jdk 
default-jdk-headless default-jdk-doc default-java-plugin gcj-native-helper
Architecture: source
Version: 0.60
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Matthias Klose 
Description:
 default-java-plugin - Default Java Plugin for running applets and Java Web 
Start applic
 default-jdk - Standard Java or Java compatible Development Kit
 default-jdk-doc - Standard Java or Java compatible Development Kit 
(documentation)
 default-jdk-headless - Standard Java or Java compatible Development Kit 
(headless)
 default-jre - Standard Java or Java compatible Runtime
 default-jre-headless - Standard Java or Java compatible Runtime (headless)
 gcj-native-helper - Standard helper tools for creating gcj native packages
 java-common - Base package for Java runtimes
Closes: 892529
Changes:
 java-common (0.60) unstable; urgency=medium
 .
   * Don't build jre/jdk defaults packages on platforms still relying
 on java 5 (provided by gcj). Closes: #892529.
   * Remove kfreebsd-amd64 kfreebsd-i386 from java9_architectures.
   * Prepare the default values for Java 11
   * Stop building gcj-native-helper.
   * java_defaults.mk: Add two new macros:
 - java_default_architectures
 - java_dependency, call as $(call java_dependency, default-jdk)
   -> default-jdk [!hppa !ia64 !s390 !sparc !hurd-i386]
Checksums-Sha1:
 4f39d35b4c4736285d6aacc1d7a690af6efab7bb 2134 java-common_0.60.dsc
 385b6b054e5e9abcde59f5712fe32ff951532218 13336 java-common_0.60.tar.xz
 657b0bba5e29a17e4f5b919feeffef501efa075d 5652 java-common_0.60_source.buildinfo
Checksums-Sha256:
 087f3047899da1dd3c68b87a7408ee783be4ab806e9e7bc8d4d94524eb1ae793 2134 
java-common_0.60.dsc
 f22e115d18e65d1c9f70f293d03d5f5e0f349b1f77d60b35a0c90f36395d1d5e 13336 
java-common_0.60.tar.xz
 c88a1b03a6989f0b48c0089282b3a4ea9cd9f8b6e6e8bc96abe45ce0d25c68aa 5652 
java-common_0.60_source.buildinfo
Files:
 bab728cb63880b76d4c399c6591ad507 2134 java optional java-common_0.60.dsc
 766710cb36399af42858487cb583c8e3 13336 java optional java-common_0.60.tar.xz
 3c03d2a5ca9afce6ad30b1249dfbf544 5652 java optional 
java-common_0.60_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlqqw3IQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9eTaD/91laTsDEs1lMIIbIHbxl5Dqigsq1Qdzj3u
Wuw0ZHQoSUBItHJQ1bKIHN0vKZNsYL8hrqH2uRoBk8BAL5IEG90YKRfux/2LhcYF
oA2Wyw3PsGBl50suwvT9RPkoCfx6c4VObsruieIsYlyPxN71oBiCRlLMg06P2fWR
5+uSpRLbU5LTNrB6ju4OVGW52EkDbA9IncIiGJmNO7sqeanN/kO4lPgNHoBYMDCk
sVS3VZAp36P1dZSiobk8jqQVTz+JzFXdthdKBiDelLq2rFRwbXgz77+Xu2u1kk1Z
03A+IHIKNd4ZIKrOa3UMCntVg3Q8qy8oS+Vy7yIuRbx2oebY+j3zT6hN6VFMWQ61

Bug#891188: blends-dev: created d/control recommends packages not in main

[Andreas Tille]

Hi Ole,

On Thu, Mar 15, 2018 at 05:14:36PM +0100, Andreas Tille wrote:
> > Feel free to lower the severity.
> 
> I think there is no need to since I found the part of the code where the
> issue occures.  If I would only understand Perl a bit better I would be
> ready with a fix. :-(

I've commited a fix to Git which for me creates now sensible Debian
Astro metapackages.  I'd love some review / enhancement of my beginners
Perl code before uploading.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#891188: blends-dev: created d/control recommends packages not in main

[Andreas Tille]

Hi Ole,

On Thu, Mar 15, 2018 at 04:55:24PM +0100, Ole Streicher wrote:
> > 
> >GENCONTROL_DEPENDS = true
> > 
> 
> Feel free to lower the severity.

I think there is no need to since I found the part of the code where the
issue occures.  If I would only understand Perl a bit better I would be
ready with a fix. :-(

> However, that was a change of the
> default behaviour that we discussed a year ago: we wanted to remove the
> translation
> 
> "Depends:" (tasks) -> "Recommends:" (d/control)
> "Recommends:" (tasks) -> "Suggests:" (d/control)
> 
> in favour of a direct copy.

Its true that we agreed upon this and the code **seemed** to do this.
However, if there is no Depends -> Recommends the check whether the
missings need to be removed is simply not done.

> I am wondering why debian-astro is the only
> blend which finally used this, and I think we wanted to convert all.

I have not seen any reason to switch any behaviour since there are no
strict Depends in Debian Med.  Thus I just substituted
s/Depends/Recommends/ inside the watch file "to be prepared" and be more
expclicit what we mean.  But I had no reason to force any switch.  Most
probably all other Blends did the same as I in Debian Med and thus you
were simply the only one who was stumbling upon this issue.
 
> > But I do not want to play severity ping-pong and will have a look
> > why GENCONTROL_DEPENDS is obviously breaking this.
> 
> That is probably the code that was introduced for this purpose (August
> 2017).

It is

a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 267) my $pkglist;
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 268) my $missinglist;
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 269) if (defined $taskinfo{$task}{Depends})
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 270) {
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 271) ($pkglist, $missinglist) = 
process_pkglist(join(",",@{$taskinfo{$task}{Depends}}));
36791f91 cdd/devtools/cdd-gen-control  (Andreas Tille   2007-08-27 
17:48:49 + 272) }
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 273) 
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 274) my (@depends, @recommends, @suggests);
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 275) 
0fc23d84 devtools/blend-gen-control(Mike Gabriel2017-08-21 
13:51:30 -0400 276) push @depends, $tasksname.' (= 
${source:Version})';
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 277) push @depends, '${misc:Depends}';
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 278) push @depends, @{$pkglist}
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 279) if defined $pkglist;
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 280) 
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 281) push @recommends, 
@{$taskinfo{$task}{Recommends}}
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 282) if defined $taskinfo{$task}{Recommends};
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 283) 
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 284) push @suggests, @{$missinglist}
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 285) if defined $missinglist;
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 286) push @suggests, 
@{$taskinfo{$task}{Suggests}}
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 287) if defined $taskinfo{$task}{Suggests};
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 288) 
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 289) my @depends_sorted = sort_uniq(\%seenlist, 
@depends);
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 290) my @recommends_sorted = 
sort_uniq(\%seenlist, @recommends);
a452586c devtools/blend-gen-control(Mike Gabriel2017-08-11 
23:39:29 -0400 291) my @suggests_sorted = sort_uniq(\%seenlist, 
@suggests);

Bug#892194: marked as done (ruby-sshkit FTBFS with Ruby 2.5: test failure)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 18:23:15 +
with message-id 
and subject line Bug#892194: fixed in ruby-sshkit 1.16.0-1
has caused the Debian Bug report #892194,
regarding ruby-sshkit FTBFS with Ruby 2.5: test failure
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.)


-- 
892194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-sshkit
Version: 1.9.0-1
Severity: serious
Tags: buster sid

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

...
┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/1st/ruby-sshkit-1.9.0/debian/ruby-sshkit/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-sshkit/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 -w -I"lib:test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/unit/backends/test_abstract.rb" 
"test/unit/backends/test_connection_pool.rb" "test/unit/backends/test_local.rb" 
"test/unit/backends/test_netssh.rb" "test/unit/backends/test_printer.rb" 
"test/unit/core_ext/test_string.rb" "test/unit/formatters/test_custom.rb" 
"test/unit/formatters/test_dot.rb" "test/unit/formatters/test_pretty.rb" 
"test/unit/formatters/test_simple_text.rb" "test/unit/test_color.rb" 
"test/unit/test_command.rb" "test/unit/test_command_map.rb" 
"test/unit/test_configuration.rb" "test/unit/test_coordinator.rb" 
"test/unit/test_deprecation_logger.rb" "test/unit/test_dsl.rb" 
"test/unit/test_host.rb" "test/unit/test_logger.rb" 
"test/unit/test_mapping_interaction_handler.rb" 
/build/1st/ruby-sshkit-1.9.0/lib/sshkit.rb:14: warning: method redefined; 
discarding old config
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/host.rb:130: warning: character class 
has duplicated range: /[@|\[|\]]/
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/configuration.rb:33: warning: method 
redefined; discarding old output_verbosity
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/configuration.rb:37: warning: method 
redefined; discarding old output_verbosity=
/usr/lib/ruby/vendor_ruby/net/scp.rb:365: warning: shadowing outer local 
variable - ch
/usr/lib/ruby/vendor_ruby/net/scp.rb:366: warning: shadowing outer local 
variable - ch
/usr/lib/ruby/vendor_ruby/net/scp.rb:367: warning: shadowing outer local 
variable - ch
/usr/lib/ruby/vendor_ruby/net/scp.rb:368: warning: shadowing outer local 
variable - ch
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/netssh.rb:8: warning: method 
redefined; discarding old default_files
/usr/lib/ruby/vendor_ruby/net/ssh/config.rb:51: warning: previous definition of 
default_files was here
/build/1st/ruby-sshkit-1.9.0/test/helper.rb:20: warning: method redefined; 
discarding old flush_connections
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/connection_pool.rb:68: 
warning: previous definition of flush_connections was here
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/host.rb:59: warning: instance variable 
@local not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:141: warning: 
instance variable @pwd not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:149: warning: 
instance variable @env not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:149: warning: 
instance variable @user not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:149: warning: 
instance variable @group not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/host.rb:59: warning: instance variable 
@local not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:141: warning: 
instance variable @pwd not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:149: warning: 
instance variable @env not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:149: warning: 
instance variable @user not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:149: warning: 
instance variable @group not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/host.rb:59: warning: instance variable 
@local not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:141: warning: 
instance variable @pwd not 

Bug#892956: libinput-dev: Requires.private without package dependencies breaks pkg-config users

[Adrian Bunk]

Control: reassign -1 meson 0.45.0-1
Control: retitle -1 meson creates bogus pkgconfig files
Control: affects -1 libinput-dev

On Thu, Mar 15, 2018 at 06:38:30PM +0100, Andreas Metzler wrote:
> On 2018-03-15 Timo Aaltonen  wrote:
> > On 14.03.2018 22:25, Adrian Bunk wrote:
> > > Package: libinput-dev
> [...] 
> > > Root cause are the new dependencies in Requires.private
> > > without package dependencies:
> 
> > > $ pkg-config --cflags libinput
> > > Package libwacom was not found in the pkg-config search path.
> > > Perhaps you should add the directory containing `libwacom.pc'
> > > to the PKG_CONFIG_PATH environment variable
> > > Package 'libwacom', required by 'libinput', not found
> 
> > 1.10.2-1 didn't have them, and nothing changed in 1.10.3 that would
> > result in this, so the culprit is elsewhere. Where did that
> > "Requires.private" come from?
> 
> Hello,
> 
> Meson changed:

Thanks.

> --- 
> ./libinput-1.10.3-builtwithmeson0.44.1-1/debian/libinput-dev/usr/lib/x86_64-linux-gnu/pkgconfig/libinput.pc
> 2018-03-15 18:24:08.366925927 +0100
> +++ 
> ./libinput-1.10.3-builtwithmeson0.45.0-1/debian/libinput-dev/usr/lib/x86_64-linux-gnu/pkgconfig/libinput.pc
>2018-03-15 18:15:49.059380110 +0100
> @@ -5,5 +5,7 @@ includedir=${prefix}/include
>  Name: Libinput
>  Description: Input device library
>  Version: 1.10.3
> +Requires.private: libwacom libudev mtdev libevdev

This is wrong.

Whether or not libinput internally uses other libraries like libwacom is 
an implementation detail, not something that should leak through the cflags.

It bloats the command line with tons of unnecessary -I flags.

And in some cases it also leaks whatever other flags are in the cflags 
of the libraries used by libinput.

>  Libs: -L${libdir} -linput
> +Libs.private: -lm -lrt -L${libdir} -llibinput-util

-llibinput-util would be liblibinput-util.a, that's clearly bogus.

>  Cflags: -I${includedir}
> 
> I guess the source was merging of 
> https://github.com/mesonbuild/meson/pull/3131 
> 
> cu Andreas

cu
Adrian

-- 

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

Processed: Re: Bug#892956: libinput-dev: Requires.private without package dependencies breaks pkg-config users

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 meson 0.45.0-1
Bug #892956 [libinput-dev] libinput-dev: Requires.private without package 
dependencies breaks pkg-config users
Bug reassigned from package 'libinput-dev' to 'meson'.
No longer marked as found in versions libinput/1.10.3-1.
Ignoring request to alter fixed versions of bug #892956 to the same values 
previously set
Bug #892956 [meson] libinput-dev: Requires.private without package dependencies 
breaks pkg-config users
Marked as found in versions meson/0.45.0-1.
> retitle -1 meson creates bogus pkgconfig files
Bug #892956 [meson] libinput-dev: Requires.private without package dependencies 
breaks pkg-config users
Changed Bug title to 'meson creates bogus pkgconfig files' from 'libinput-dev: 
Requires.private without package dependencies breaks pkg-config users'.
> affects -1 libinput-dev
Bug #892956 [meson] meson creates bogus pkgconfig files
Added indication that 892956 affects libinput-dev

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

Bug#892956: libinput-dev: Requires.private without package dependencies breaks pkg-config users

[Andreas Metzler]

On 2018-03-15 Andreas Metzler  wrote:
> On 2018-03-15 Timo Aaltonen  wrote:
>> On 14.03.2018 22:25, Adrian Bunk wrote:
> > > Package: libinput-dev
[...] 
> > > Root cause are the new dependencies in Requires.private
> > > without package dependencies:
[...] 

>> 1.10.2-1 didn't have them, and nothing changed in 1.10.3 that would
>> result in this, so the culprit is elsewhere. Where did that
>> "Requires.private" come from?

> Hello,

> Meson changed:
[...]
> I guess the source was merging of 
> https://github.com/mesonbuild/meson/pull/3131 

I am not very familiar with meson but afaict from reading the docs
https://github.com/mesonbuild/meson/blob/master/docs/markdown/Pkgconfig-module.md
this behavior cannot be overriden. - Setting requires_private to ''
does not work since the autodeps are appended.

So it looks like the possibilties of fixing this are
1. Use a kludge (sed in debian/rules)
2. Add package dependencies
3. Stop using pkg.generate().

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#893023: librsl FTBFS with flex 2.6.4-6

[Adrian Bunk]

Source: librsl
Version: 1.43-1.2
Severity: serious

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

...
/bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -static -Wl,-z,relro 
-o any_to_gif any_to_gif.o -L/usr/lib -lmfhdf -ldf -ljpeg -lz -lm -lfl 
../.libs/librsl.a  -L/usr/lib -lmfhdf -ldf -ljpeg -lz -lm -lfl
libtool: link: gcc -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z -Wl,relro -o any_to_gif any_to_gif.o  -L/usr/lib 
../.libs/librsl.a /usr/lib/libmfhdf.so /usr/lib/libdf.so -ljpeg -lz -lm -lfl
/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libfl.so: undefined 
reference to `yylex'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:487: any_to_gif] Error 1

Processed: Closing issue reported for backport version, no information in the report

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #877853 [openjdk-8-jdk] openjdk-8-jdk: java programs run with openjdk 1.8 
gives issue - javax.servlet.ServletException: java.lang.NoClassDefFoundError: 
Could not initialize class 
org.apache.jasper.el.ELContextImpljavax.servlet.ServletException
Added tag(s) moreinfo.
> severity -1 important
Bug #877853 [openjdk-8-jdk] openjdk-8-jdk: java programs run with openjdk 1.8 
gives issue - javax.servlet.ServletException: java.lang.NoClassDefFoundError: 
Could not initialize class 
org.apache.jasper.el.ELContextImpljavax.servlet.ServletException
Severity set to 'important' from 'critical'

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

Bug#877853: Closing issue reported for backport version, no information in the report

[Matthias Klose]

Control: tags -1 + moreinfo
Control: severity -1 important

Closing issue reported for backport version, no information at all in the 
report.

Bug#892956: libinput-dev: Requires.private without package dependencies breaks pkg-config users

[Andreas Metzler]

On 2018-03-15 Timo Aaltonen  wrote:
> On 14.03.2018 22:25, Adrian Bunk wrote:
> > Package: libinput-dev
[...] 
> > Root cause are the new dependencies in Requires.private
> > without package dependencies:

> > $ pkg-config --cflags  libinput
> > Package libwacom was not found in the pkg-config search path.
> > Perhaps you should add the directory containing `libwacom.pc'
> > to the PKG_CONFIG_PATH environment variable
> > Package 'libwacom', required by 'libinput', not found

> 1.10.2-1 didn't have them, and nothing changed in 1.10.3 that would
> result in this, so the culprit is elsewhere. Where did that
> "Requires.private" come from?

Hello,

Meson changed:

--- 
./libinput-1.10.3-builtwithmeson0.44.1-1/debian/libinput-dev/usr/lib/x86_64-linux-gnu/pkgconfig/libinput.pc
2018-03-15 18:24:08.366925927 +0100
+++ 
./libinput-1.10.3-builtwithmeson0.45.0-1/debian/libinput-dev/usr/lib/x86_64-linux-gnu/pkgconfig/libinput.pc
   2018-03-15 18:15:49.059380110 +0100
@@ -5,5 +5,7 @@ includedir=${prefix}/include
 Name: Libinput
 Description: Input device library
 Version: 1.10.3
+Requires.private: libwacom libudev mtdev libevdev
 Libs: -L${libdir} -linput
+Libs.private: -lm -lrt -L${libdir} -llibinput-util
 Cflags: -I${includedir}

I guess the source was merging of 
https://github.com/mesonbuild/meson/pull/3131 

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#822019: marked as done (python-osd: Build arch:all+arch:any but is missing build-{arch,indep} targets)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 17:37:58 +
with message-id 
and subject line Bug#822019: fixed in python-osd 0.2.14-6.1
has caused the Debian Bug report #822019,
regarding python-osd: Build arch:all+arch:any but is missing build-{arch,indep} 
targets
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.)


-- 
822019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-osd
Severity: normal
Usertags: arch-all-and-any-missing-targets

Hi,

The package python-osd builds an architecture independent *and* an
architecture dependent package, but does not have the (now mandatory)
"build-arch" and "build-indep" targets in debian/rules.

We would like to phase out the hacks in dpkg, which are currently
needed to ensure that python-osd builds despite its lack of these
targets.

 * Please add build-arch and build-indep targets to python-osd at
   your earliest convenience.
   - This can also be solved by using e.g. the "dh"-style rules.

 * The work around will be removed in the first dpkg upload after
   the 1st of June.  After that upload, python-osd will FTBFS if
   this bug has not been fixed before then.

Thanks,

See also: https://lists.debian.org/debian-devel/2016/04/msg00023.html
--- End Message ---
--- Begin Message ---
Source: python-osd
Source-Version: 0.2.14-6.1

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated python-osd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Mar 2018 17:08:13 +
Source: python-osd
Binary: python-pyosd python-osd
Architecture: source
Version: 0.2.14-6.1
Distribution: unstable
Urgency: medium
Maintainer: Mauro Lizaur 
Changed-By: James Cowgill 
Description:
 python-osd - Transitional dummy package
 python-pyosd - Python bindings for X On-Screen Display library
Closes: 822019
Changes:
 python-osd (0.2.14-6.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Santiago Vila ]
   * Add build-{arch,indep} targets. (Closes: #822019)
Checksums-Sha1:
 e91fdd4043309126496f575c90c47a4227ea276d 2060 python-osd_0.2.14-6.1.dsc
 91713cc9b1f8adfd63726640a7080e2994bbccb1 3437 python-osd_0.2.14-6.1.diff.gz
 1756da3be34ce86ae8f8dbeda7119ed90b393851 6266 
python-osd_0.2.14-6.1_source.buildinfo
Checksums-Sha256:
 c487935090214e6647b53539f71a987bd5c2a419ef0df22e363345d7d356c0f9 2060 
python-osd_0.2.14-6.1.dsc
 b3571d023782c91a407d8d0225aa9af862a3c63a81602144cf2c7ace41e6ce26 3437 
python-osd_0.2.14-6.1.diff.gz
 2b2fa56b4cac4aa29f38958164b33811dc6190621973d232111b1a60bacf050b 6266 
python-osd_0.2.14-6.1_source.buildinfo
Files:
 8ff38d57f36c4a590c76d321798ae7a0 2060 python optional python-osd_0.2.14-6.1.dsc
 6d23d8be449ff804716d2e664348bad4 3437 python optional 
python-osd_0.2.14-6.1.diff.gz
 0e8f04b2a62dafef24d16a9814ee5139 6266 python optional 
python-osd_0.2.14-6.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE+Ixt5DaZ6POztUwQx/FnbeotAe8FAlqqqJgUHGpjb3dnaWxs
QGRlYmlhbi5vcmcACgkQx/FnbeotAe85jA//XFR1iluxzM3Jso6T88K0Xq0Djqve
/pQrHse+173Hheyv9h2UC9becGP4ZQve/vVA9ZNGFqiA6aPdpsSgo6rBxCkb3Zk0
HU6iUIXCRLu8n5Cd5o/WKieEBJQ/yCvX9GW51JkUJYsOr080f4AGBO8OaJnMkdzG
XUy1Vl36+owyJ7F1sy1CswjM0DQIIsr2t6KpyhsLdNbxwIiu13seaosDsxt5tLbY
R6J501jVJWlSSJ1jk/pCNXM4WlvBl1ZQ1Qasf+4/BwNOic7JhDcmAgQyNCCnEaJZ
4TGBjPueBj1eYVdREsIwFt7YNax8UmA6yJ2NZAxHUhmfDwk785LCdSCpOJ35PH6p
Q7MOZ4ohZlABDBYQBvHniiA0i82EesITSEZDmIoiYp8u+CgSiARLaWXfxvIwAbWs
1q93Kgnlv+zgw6ABwO2KX+7GHRP3sex12kme7Hxdx4NQUi2elyxg/RRPAGloaKpZ
0Z+Go8BO7HnRZ0Ds85WrCvDC5/z5JcAEJMDbhu4QSy6NfaWUEHL0Dq6dNqu4Qlws
kxWTG1w7lChQ2t8Q4ycV66wtwtxcWBYTdqKULOAKCpV+eWvSXIP6Y3VFFdZtrg9N
CtsZQ0RbQKXw3hpk5R9Q2uKxm3SKTtGmSulB3m6CX/IENbdqlXkxh8ePpcdM2Dp1
cfsJB6VOH1Nersg=
=va3/
-END PGP SIGNATURE End Message ---

Processed: [bts-link] source package openssl

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package openssl
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #891570 (http://bugs.debian.org/891570)
> # Bug title: SSL connect attempt failed error:141A90B5:SSL 
> routines:ssl_cipher_list_to_bytes:no ciphers available
> #  * https://github.com/openssl/openssl/issues/5359
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 891570 + fixed-upstream
Bug #891570 [libssl1.1] SSL connect attempt failed error:141A90B5:SSL 
routines:ssl_cipher_list_to_bytes:no ciphers available
Added tag(s) fixed-upstream.
> usertags 891570 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 891570 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#893019: flask-restful FTBFS with python3-aniso8601 3.0.0-1

[Adrian Bunk]

Source: flask-restful
Version: 0.3.6-1
Severity: serious

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

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:215: cd 
/build/1st/flask-restful-0.3.6/.pybuild/cpython3_3.6_flask-restful/build; 
python3.6 -m nose tests
...[2019-04-16 18:13:58,776] ERROR in app: Exception on / [GET]
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/flask/app.py", line 1612, in 
full_dispatch_request
rv = self.dispatch_request()
  File "/usr/lib/python3/dist-packages/flask/app.py", line 1598, in 
dispatch_request
return self.view_functions[rule.endpoint](**req.view_args)
  File 
"/build/1st/flask-restful-0.3.6/.pybuild/cpython3_3.6_flask-restful/build/flask_restful/__init__.py",
 line 484, in wrapper
return self.make_response(data, code, headers=headers)
  File 
"/build/1st/flask-restful-0.3.6/.pybuild/cpython3_3.6_flask-restful/build/flask_restful/__init__.py",
 line 521, in make_response
raise InternalServerError()
werkzeug.exceptions.InternalServerError: 500 Internal Server Error: The server 
encountered an internal error and was unable to complete your request.  Either 
the server is overloaded or there is an error in the application.
.[2019-04-16 18:13:58,929] ERROR in app: Exception on 
/foo [GET]
[2019-04-16 18:13:59,024] ERROR in app: Exception on /foo [GET]
..[2019-04-16 18:13:59,032] ERROR in app: Exception on /foo [GET]
...E.
==
ERROR: tests.test_inputs.test_bad_isointervals(, , '')
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/usr/lib/python3.6/unittest/case.py", line 733, in assertRaises
return context.handle('assertRaises', args, kwargs)
  File "/usr/lib/python3.6/unittest/case.py", line 178, in handle
callable_obj(*args, **kwargs)
  File 
"/build/1st/flask-restful-0.3.6/.pybuild/cpython3_3.6_flask-restful/build/flask_restful/inputs.py",
 line 171, in iso8601interval
start, end = _parse_interval(value)
  File 
"/build/1st/flask-restful-0.3.6/.pybuild/cpython3_3.6_flask-restful/build/flask_restful/inputs.py",
 line 134, in _parse_interval
return sorted(aniso8601.parse_interval(value))
  File "/usr/lib/python3/dist-packages/aniso8601/interval.py", line 34, in 
parse_interval
if isointervalstr[0] == 'R':
IndexError: string index out of range

--
Ran 395 tests in 1.483s

FAILED (errors=1)
E: pybuild pybuild:323: test: plugin distutils failed with: exit code=1: cd 
/build/1st/flask-restful-0.3.6/.pybuild/cpython3_3.6_flask-restful/build; 
python3.6 -m nose tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.6 returned 
exit code 13
make: *** [debian/rules:6: build] Error 25

Bug#739251: iptables: Situation resolved

[g.smyli]

Package: iptables
Version: 1.6.0+snapshot20161117-6
Followup-For: Bug #739251

Dear Maintainer,

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

   Using synaptic, I removed all debian-edu packages. Iptables immediately 
functioned as expected.
Rules loading up at boot and maintained seamlessly throughout runtime. I would 
guess this bug is with 
the skole-linux, debian-edu package. Iptables working fine with simple xfce 
desktop.


-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable')
Architecture: amd64 (x86_64)

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

Versions of packages iptables depends on:
ii  libc62.24-11+deb9u3
ii  libip4tc01.6.0+snapshot20161117-6
ii  libip6tc01.6.0+snapshot20161117-6
ii  libiptc0 1.6.0+snapshot20161117-6
ii  libnetfilter-conntrack3  1.0.6-2
ii  libnfnetlink01.0.1-3
ii  libxtables12 1.6.0+snapshot20161117-6

iptables recommends no packages.

Versions of packages iptables suggests:
ii  kmod  23-2

-- no debconf information

Processed: Re: python-osd: Build arch:all+arch:any but is missing build-{arch,indep} targets

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #822019 [src:python-osd] python-osd: Build arch:all+arch:any but is missing 
build-{arch,indep} targets
Added tag(s) pending.

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

Bug#822019: python-osd: Build arch:all+arch:any but is missing build-{arch,indep} targets

[James Cowgill]

Control: tags -1 pending

Hi,

On Wed, 20 Apr 2016 23:05:56 +0200 ni...@thykier.net wrote:
> Package: python-osd
> Severity: normal
> Usertags: arch-all-and-any-missing-targets
> 
> Hi,
> 
> The package python-osd builds an architecture independent *and* an
> architecture dependent package, but does not have the (now mandatory)
> "build-arch" and "build-indep" targets in debian/rules.

I've uploaded the attached NMU which fixes this. It simply applies the
patch which was already in this bug report since a year and a half ago.

Thanks,
James
diff -u python-osd-0.2.14/debian/changelog python-osd-0.2.14/debian/changelog
--- python-osd-0.2.14/debian/changelog
+++ python-osd-0.2.14/debian/changelog
@@ -1,3 +1,12 @@
+python-osd (0.2.14-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Santiago Vila ]
+  * Add build-{arch,indep} targets. (Closes: #822019)
+
+ -- James Cowgill   Thu, 15 Mar 2018 17:08:13 +
+
 python-osd (0.2.14-6) unstable; urgency=medium
 
   [ Jakub Wilk ]
diff -u python-osd-0.2.14/debian/rules python-osd-0.2.14/debian/rules
--- python-osd-0.2.14/debian/rules
+++ python-osd-0.2.14/debian/rules
@@ -4,6 +4,8 @@
 
 #-l$(CURDIR)/$p/usr/lib/
 
+build-arch: build
+build-indep: build
 build: build-stamp
 build-stamp:
dh_testdir
@@ -56 +58 @@
-.PHONY: build clean binary-indep binary-arch binary install
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary 
install


signature.asc
Description: OpenPGP digital signature

Bug#880842: marked as done (gnome-twitch FTBFS with meson 0.43.0: Invalid kwargs for option "use-deprecated-webkit": "descritpion")

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 16:52:41 +
with message-id 
and subject line Bug#880842: fixed in gnome-twitch 0.4.1-2
has caused the Debian Bug report #880842,
regarding gnome-twitch FTBFS with meson 0.43.0: Invalid kwargs for option 
"use-deprecated-webkit": "descritpion"
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.)


-- 
880842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-twitch
Version: 0.3.1-1
Severity: serious
Tags: buster sid

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

...
Meson encountered an error in file meson_options.txt, line 2, column 0:
Invalid kwargs for option "use-deprecated-webkit": "descritpion"

A full log can be found at 
/build/1st/gnome-twitch-0.3.1/build/meson-logs/meson-log.txt
debian/rules:13: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 1
--- End Message ---
--- Begin Message ---
Source: gnome-twitch
Source-Version: 0.4.1-2

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

Debian distribution maintenance software
pp.
Tim Dengel  (supplier of updated gnome-twitch 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 05 Nov 2017 19:23:48 +0100
Source: gnome-twitch
Binary: gnome-twitch gnome-twitch-player-backend-gstreamer-cairo 
gnome-twitch-player-backend-gstreamer-opengl 
gnome-twitch-player-backend-gstreamer-clutter 
gnome-twitch-player-backend-mpv-opengl
Architecture: source
Version: 0.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Tim Dengel 
Changed-By: Tim Dengel 
Description:
 gnome-twitch - GNOME Twitch app for watching Twitch.tv streams without a 
browser
 gnome-twitch-player-backend-gstreamer-cairo - Player backend for GNOME Twitch 
based on gstreamer+cairo
 gnome-twitch-player-backend-gstreamer-clutter - Player backend for GNOME 
Twitch based on gstreamer+clutter
 gnome-twitch-player-backend-gstreamer-opengl - Player backend for GNOME Twitch 
based on gstreamer+opengl
 gnome-twitch-player-backend-mpv-opengl - Player backend for GNOME Twitch based 
on mpv
Closes: 880842
Changes:
 gnome-twitch (0.4.1-2) unstable; urgency=medium
 .
   * Set priority to optional because extra has been deprecated
   * Bump standards version from 3.9.8 to 4.1.1
   * Fix typo in meson build file (Closes: 880842)
Checksums-Sha1:
 a40e51f23da245785b2cce058868ebbbcf15f783 2525 gnome-twitch_0.4.1-2.dsc
 a9246d7f668570653b129ec731a1fa7855738a57 4640 
gnome-twitch_0.4.1-2.debian.tar.xz
 42bb3873f6c708a35b4a148f1b74f05c461bfae4 6580 
gnome-twitch_0.4.1-2_source.buildinfo
Checksums-Sha256:
 e251ea7198fa31bd8a232668bc0090a40f6939994fa730834512649183c924db 2525 
gnome-twitch_0.4.1-2.dsc
 232b79d627f40c19b6e2e95848f6e73494ab1865b438562ad8b4e7717ec89451 4640 
gnome-twitch_0.4.1-2.debian.tar.xz
 7185e7e4d71a1a47de1a0a09d04c28b0acb685216d06114925b8e70496b2c708 6580 
gnome-twitch_0.4.1-2_source.buildinfo
Files:
 5dbf2723d0671613d2811a8c941896d0 2525 video optional gnome-twitch_0.4.1-2.dsc
 438fec96a156c3c5655d57010467c0dc 4640 video optional 
gnome-twitch_0.4.1-2.debian.tar.xz
 1f351a528d7d3c669ffe97e173ee5f1c 6580 video optional 
gnome-twitch_0.4.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJaqp9RAAoJEPNPCXROn13ZiN0QANXE54j3W+DLL4r2eNPLYOpE
dGd5cRfu3zFR1C1qGrS+dUBCGydNm2IaS7Wn8VZLmOJ8UXSg5dPoG5dpEpgp8qQj
ogEVk5vXx/kDU3kQ/B3rNm74WkSiE28NSwjIYfqyTCr5ygAevewBXbjEDI8ImTg8
5FvA1cPQSscxRSgu6QvAnjTWAQpcieUI83RWU5psj4YS+mVdX5ted0DbraMNW/Ut
OXKnwpKrzGVtzra5aP31lpCHBhW46DIJ5KFHhFSTfja637y3C7F9SWTkQugmxzFA
gNCTMiOKYD4NZCTROBzYjb09muS10PPKr8m+dVDwfE7JB9UNP1yngvy/LkLExFN5
e3DWdO1wDd05R2TTmbAHUDubyGM9nZ98J09pTi20BKmGsvMZFE1iNJi7fIZC6lSn
omlAmvx6GZcy+3Qz44+F5Pj0hnN/4JlVW7qrdx1oHDCPkxYLZcEOPqF0eg8BnMsP
NVWKYvGu8WCKhPu1otlW1MLGFCVPyBZEuiFHBCNuxsy3tr2aEJc7wiV6Bfn99zG5

Bug#821970: marked as done (chise-base: Build arch:all+arch:any but is missing build-{arch,indep} targets)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 16:51:09 +
with message-id 
and subject line Bug#821970: fixed in chise-base 0.3.0-2.1
has caused the Debian Bug report #821970,
regarding chise-base: Build arch:all+arch:any but is missing build-{arch,indep} 
targets
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.)


-- 
821970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chise-base
Severity: normal
Usertags: arch-all-and-any-missing-targets

Hi,

The package chise-base builds an architecture independent *and* an
architecture dependent package, but does not have the (now mandatory)
"build-arch" and "build-indep" targets in debian/rules.

We would like to phase out the hacks in dpkg, which are currently
needed to ensure that chise-base builds despite its lack of these
targets.

 * Please add build-arch and build-indep targets to chise-base at
   your earliest convenience.
   - This can also be solved by using e.g. the "dh"-style rules.

 * The work around will be removed in the first dpkg upload after
   the 1st of June.  After that upload, chise-base will FTBFS if
   this bug has not been fixed before then.

Thanks,

See also: https://lists.debian.org/debian-devel/2016/04/msg00023.html
--- End Message ---
--- Begin Message ---
Source: chise-base
Source-Version: 0.3.0-2.1

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated chise-base package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Mar 2018 14:57:51 +
Source: chise-base
Binary: chise-db libchise1 libchise-dev
Architecture: source
Version: 0.3.0-2.1
Distribution: unstable
Urgency: medium
Maintainer: NIIBE Yutaka 
Changed-By: James Cowgill 
Description:
 chise-db   - CHISE db, the character information database
 libchise-dev - C language binding of CHISE, the character information database
 libchise1  - C language binding of CHISE, the character information database
Closes: 821970
Changes:
 chise-base (0.3.0-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Santiago Vila ]
   * Add build-{arch,indep} targets. (Closes: #821970)
Checksums-Sha1:
 8ff3ba5e7552cd80ff7dfef9e1aff1643c5758a8 1832 chise-base_0.3.0-2.1.dsc
 2f8b4592a5c867d2488f8ca994c16aaff1083742 493645 chise-base_0.3.0-2.1.diff.gz
 700a68dc1cba7911ad0fdcb2d00c8259034b4472 5879 
chise-base_0.3.0-2.1_source.buildinfo
Checksums-Sha256:
 3cdbf81ad27776e7fcbfea9e24eaa2369feec9aaf99d059f905d3214f52f3925 1832 
chise-base_0.3.0-2.1.dsc
 15b77d8aa7ec6b45c46e2ff5304a7eef87dccaac4827ec0bc93b7a065ef60e96 493645 
chise-base_0.3.0-2.1.diff.gz
 e3af8a8384123d52d4d9f72e293abfafa33b05a5ebfe34edf8d5fa425ddd8856 5879 
chise-base_0.3.0-2.1_source.buildinfo
Files:
 d731829cafa16fec3a40a0db66792d52 1832 devel optional chise-base_0.3.0-2.1.dsc
 b62cd67f44c563c6b1d02b51e5a5a669 493645 devel optional 
chise-base_0.3.0-2.1.diff.gz
 54e5b4ace1ed1d29cb90f946101e8af7 5879 devel optional 
chise-base_0.3.0-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE+Ixt5DaZ6POztUwQx/FnbeotAe8FAlqqjmYUHGpjb3dnaWxs
QGRlYmlhbi5vcmcACgkQx/FnbeotAe/sLBAAuDHyC5xOsZEr7POrS6VMZ5KykZIH
EhGtXnZQUdecLtNurdS0lU4kh23eS0M44pmPZOZj7CNc1Cbgu1shXFt4LlimnMtZ
5zzWswLCtXIBaN6LQ1SNQHK7Z/aB/NgMwRKYMkVCwTHQDwJ9VaheASM86i/QZgOt
u1twK5lWUMOXGv7ciJSbMLgWM/OpNtSDNCYylAuRZRomYLTm3CrcR35uTN7+oQPJ
gpZ9+UiACT9jYqe47NlmUxLMXXh4VapLKQc6+7vf+t+vKuQnkIYEc6iFZSxrZml2
h52VSLhxxVjE4a/0lOnniuP4Ui5ebjejafGYj3sd1WtMOuKfitcoeEKxhToHoeUx
7mrsVg3Xuu0Vg2EGumOSLmuqBboXyZtCA/eTNKExXk+kG36o2B6bzsslH4bfDRW9
diKmBYiCE99l69B5L0p82qlznKp4WauHZifOth6iAEWoITLLE31GVH7syzIAjkA/
1LZdtjweb903utQkMeuUEnqq8X8lPiXsUWLnr6uXvgSwNJRB+dvhsN7PounVtFop
ywTENexYHNnL+TY8yL1tejLH3a/3pLPJXJ9eqUmv6zi5BQj6A4vrCpdMC5oU8EBG
3/0d92OjVIYHhxYLCTJCW5I2HDns0+mOxxrI7sB7HIhsR0MLvZOGR5mQbJnMyy7e
Xi5ALMB+jmfilvM=
=athq
-END PGP 

Processed: Re: chise-base: Build arch:all+arch:any but is missing build-{arch,indep} targets

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #821970 [src:chise-base] chise-base: Build arch:all+arch:any but is missing 
build-{arch,indep} targets
Added tag(s) pending.

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

Bug#821970: chise-base: Build arch:all+arch:any but is missing build-{arch,indep} targets

[James Cowgill]

Control: tags -1 pending

Hi,

On Wed, 20 Apr 2016 22:48:40 +0200 ni...@thykier.net wrote:
> Package: chise-base
> Severity: normal
> Usertags: arch-all-and-any-missing-targets
> 
> Hi,
> 
> The package chise-base builds an architecture independent *and* an
> architecture dependent package, but does not have the (now mandatory)
> "build-arch" and "build-indep" targets in debian/rules.

I've uploaded the attached NMU to fix this. It simply applies the patch
which was added to this bug a year and a half ago.

James
diff -u chise-base-0.3.0/debian/rules chise-base-0.3.0/debian/rules
--- chise-base-0.3.0/debian/rules
+++ chise-base-0.3.0/debian/rules
@@ -38,6 +38,8 @@
cd libchise && CFLAGS="$(CFLAGS)" ./configure 
--host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr 
--mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info
 
 
+build-arch: build
+build-indep: build
 build: build-stamp
 build-stamp: libchise/config.status
dh_testdir
@@ -117 +119 @@
-.PHONY: build clean binary-indep binary-arch binary install 
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary 
install
diff -u chise-base-0.3.0/debian/changelog chise-base-0.3.0/debian/changelog
--- chise-base-0.3.0/debian/changelog
+++ chise-base-0.3.0/debian/changelog
@@ -1,3 +1,12 @@
+chise-base (0.3.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Santiago Vila ]
+  * Add build-{arch,indep} targets. (Closes: #821970)
+
+ -- James Cowgill   Thu, 15 Mar 2018 14:57:51 +
+
 chise-base (0.3.0-2) unstable; urgency=low
 
   * libchise/Makefile.in (CFLAGS): Added -DHAVE_CONFIG_H


signature.asc
Description: OpenPGP digital signature

Bug#891188: blends-dev: created d/control recommends packages not in main

[Ole Streicher]

Hi Andreas,

On 15.03.2018 16:16, Andreas Tille wrote:
> I tend to set the issue from serious to important since I now found out
> why the problem seems to occure only in the case of Debian Astro (or may
> be any other Blend that is using
> 
>GENCONTROL_DEPENDS = true
> 

Feel free to lower the severity. However, that was a change of the
default behaviour that we discussed a year ago: we wanted to remove the
translation

"Depends:" (tasks) -> "Recommends:" (d/control)
"Recommends:" (tasks) -> "Suggests:" (d/control)

in favour of a direct copy. I am wondering why debian-astro is the only
blend which finally used this, and I think we wanted to convert all.

> But I do not want to play severity ping-pong and will have a look
> why GENCONTROL_DEPENDS is obviously breaking this.

That is probably the code that was introduced for this purpose (August
2017).

Best

Ole

Bug#893016: oclgrind FTBFS on big endian: test failures

[Adrian Bunk]

Source: oclgrind
Version: 18.3-1
Severity: serious

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

32bit big endian:
...
The following tests FAILED:
 54 - interactive/struct_member (Failed)
 70 - misc/printf (Failed)
Errors while running CTest


64bit big endian:
...
The following tests FAILED:
 54 - interactive/struct_member (Failed)
 96 - rt_sampler (Failed)
Errors while running CTest

Processed: affects 892956

[Debian Bug Tracking System]

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

> affects 892956 src:gnome-control-center src:budgie-desktop src:cinnamon 
> src:totem
Bug #892956 [libinput-dev] libinput-dev: Requires.private without package 
dependencies breaks pkg-config users
Added indication that 892956 affects src:gnome-control-center, 
src:budgie-desktop, src:cinnamon, and src:totem
> thanks
Stopping processing here.

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

Bug#891188: blends-dev: created d/control recommends packages not in main

[Andreas Tille]

Hi Ole,

On Fri, Feb 23, 2018 at 10:43:01AM +0100, Ole Streicher wrote:
> Package: blends-dev
> Version: 0.6.100
> Severity: serious

I tend to set the issue from serious to important since I now found out
why the problem seems to occure only in the case of Debian Astro (or may
be any other Blend that is using

   GENCONTROL_DEPENDS = true

I've found out that with the following change

diff --git a/Makefile b/Makefile
index 7734c93..3be1b00 100755
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
 #!/usr/bin/make -f
 
 BLENDMAKEFILE=/usr/share/blends-dev/Makefile
-GENCONTROL_DEPENDS = true
+# GENCONTROL_DEPENDS = true
 
 CheckBLENDMakefile := $(shell if [ -e $(BLENDMAKEFILE) ] ; then echo 1 ; else 
echo 0 ; fi)
 ifeq ($(CheckBLENDMakefile),1)


the intended behaviour to have packages in contrib/non-free will be
Suggests only.

But I do not want to play severity ping-pong and will have a look
why GENCONTROL_DEPENDS is obviously breaking this.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#891331: marked as done (Beta from SQLA are *not* to upload, and full of bugs)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 15:58:56 +0100
with message-id <20180315145856.wonm7fblafm7y...@sar0.p1otr.com>
and subject line 1.2.5 uploaded to unstable
has caused the Debian Bug report #891331,
regarding Beta from SQLA are *not* to upload, and full of bugs
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.)


-- 
891331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sqlalchemy
Version: 1.2.0~b2+ds1-1
Severity: grave

Dear maintainer,

According to Mike Bayer, upstream for SQLAlchemy, you should *not* upload any
beta release of SQLAlchemy. Indeed, the version in Experimental has bugs,
for example this one:

http://docs.sqlalchemy.org/en/latest/changelog/changelog_12.html#change-dff3a469788c81a46440584406cb22be

This issue causes more than 600 unit test failures in Nova, about 32 in Manila,
and so on. This makes it impossible for me to run unit tests of OpenStack
Queens using sbuild and experimental, as this bad version of SQLAlchemy in
Experimental render unit tests as broken, when they are not (SQLA 1.2.0~b2 is).

Please upload a working version of SQLA in Experimental, for example 1.2.1,
which is accepted by OpenStack, as per this document:

https://github.com/openstack/requirements/blob/stable/queens/upper-constraints.txt#L136

Thanks for your work on SQLA,
Cheers,

Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 87334--- End Message ---

Bug#876521: FTBFS with CGAL 4.11

[Bas Couwenberg]

On 2018-03-15 14:35, Vincas Dargis wrote:

There is new PR, does this fix the issue?

https://github.com/Oslandia/SFCGAL/pull/157


No, see: 
https://github.com/Oslandia/SFCGAL/pull/157#issuecomment-373383973


Kind Regards,

Bas

Bug#893008: wide-dhcpv6 FTBFS with flex 2.6.4-6

[Adrian Bunk]

Source: wide-dhcpv6
Version: 20080615-19
Severity: serious
Tags: buster sid patch

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

...
gcc -Wl,-z,relro -Wl,-z,now -o dhcp6ctl dhcp6_ctlclient.o base64.o auth.o 
strlcpy.o strlcat.o arc4random.o -lfl
/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libfl.so: undefined 
reference to `yylex'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:74: dhcp6ctl] Error 1


Fix is attached.
Description: Remove unused linking with libfl
 Due to the yylex requirement this caused FTBFS
 when a shared libfl is provided.
Author: Adrian Bunk 

--- wide-dhcpv6-20080615.orig/Makefile.in
+++ wide-dhcpv6-20080615/Makefile.in
@@ -40,7 +40,7 @@ CFLAGS=   @CFLAGS@ @CPPFLAGS@ @DEFS@ -DSYS
-DLOCALDBDIR=\"${localdbdir}\"
 LDFLAGS=@LDFLAGS@
 LIBOBJS=@LIBOBJS@
-LIBS=  @LIBS@ @LEXLIB@
+LIBS=  @LIBS@
 CC=@CC@
 TARGET=dhcp6c dhcp6s dhcp6relay dhcp6ctl
 
@@ -63,11 +63,14 @@ RELAYOBJS = dhcp6relay.o dhcp6relay_scri
 CTLOBJS= dhcp6_ctlclient.o base64.o auth.o
 CLEANFILES+=   y.tab.h
 
+CLIENTLIBS=@LEXLIB@
+SERVLIBS=  @LEXLIB@
+
 all:   $(TARGET)
 dhcp6c:$(CLIENTOBJS) $(LIBOBJS)
-   $(CC) $(LDFLAGS) -o dhcp6c $(CLIENTOBJS) $(LIBOBJS) $(LIBS)
+   $(CC) $(LDFLAGS) -o dhcp6c $(CLIENTOBJS) $(LIBOBJS) $(LIBS) 
$(CLIENTLIBS)
 dhcp6s:$(SERVOBJS) $(LIBOBJS)
-   $(CC) $(LDFLAGS) -o dhcp6s $(SERVOBJS) $(LIBOBJS) $(LIBS)
+   $(CC) $(LDFLAGS) -o dhcp6s $(SERVOBJS) $(LIBOBJS) $(LIBS) $(SERVLIBS)
 dhcp6relay: $(RELAYOBJS) $(LIBOBJS)
$(CC) $(LDFLAGS) -o $@ $(RELAYOBJS) $(LIBOBJS) $(LIBS)
 dhcp6ctl: $(CTLOBJS)

Bug#893007: keep openjdk-11 in unstable for now, early snapshot package

[Matthias Klose]

Package: src:openjdk-11
Severity: serious

keep openjdk-11 in unstable for now, it's an early snapshot package, with the
release targeted for the end of 2018.

Bug#891331: SQLAlchemy 1.2.5

[Sandro Tosi]

Hello,
SQLA 1.2.5 has been released 10 days ago, any chance you can get it
uploaded in unstable?

thanks

Bug#876521: FTBFS with CGAL 4.11

[Vincas Dargis]

There is new PR, does this fix the issue?

https://github.com/Oslandia/SFCGAL/pull/157

Bug#892785: marked as done (zaqar-ui FTBFS: ImportError: No module named openstack_dashboard.test.settings)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 13:00:22 +
with message-id 
and subject line Bug#892785: fixed in zaqar-ui 4.0.0-1
has caused the Debian Bug report #892785,
regarding zaqar-ui FTBFS: ImportError: No module named 
openstack_dashboard.test.settings
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.)


-- 
892785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zaqar-ui
Version: 1.0.0~rc1-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes zaqar-ui FTBFS:

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/zaqar-ui-1.0.0~rc1'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
bash run_tests.sh -N --no-pep8
Running Zaqar UI tests
Traceback (most recent call last):
  File "/build/1st/zaqar-ui-1.0.0~rc1/manage.py", line 23, in 
execute_from_command_line(sys.argv)
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 364, in execute_from_command_line
utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 308, in execute
settings.INSTALLED_APPS
  File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 56, in 
__getattr__
self._setup(name)
  File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 41, in 
_setup
self._wrapped = Settings(settings_module)
  File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 110, in 
__init__
mod = importlib.import_module(self.SETTINGS_MODULE)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
ImportError: No module named openstack_dashboard.test.settings
Tests failed.
make[1]: *** [debian/rules:10: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: zaqar-ui
Source-Version: 4.0.0-1

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated zaqar-ui package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 13 Mar 2018 08:59:30 +0100
Source: zaqar-ui
Binary: python3-zaqar-ui
Architecture: source all
Version: 4.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 python3-zaqar-ui - OpenStack Queueing as a Service - Dashboard plugin
Closes: 892785
Changes:
 zaqar-ui (4.0.0-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Bumped debhelper compat version to 10
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Daniel Baumann ]
   * Updating copyright format url.
   * Updating maintainer field.
   * Running wrap-and-sort -bast.
   * Removing gbp.conf, not used anymore or should be specified in the
 developers dotfiles.
   * Deprecating priority extra as per policy 4.0.1.
 .
   [ Ondřej Nový ]
 .
   [ Thomas Goirand ]
   * New upstream release:
 - Fixed FTBFS (Closes: #892785).
   * Fixed (build-)depends for this release.
   * Switched to Python 3.
   * Revised debian/copyright holder list and years.
   * Standards-Version is now 4.1.3.
Checksums-Sha1:
 4dad5c54e8234878b2542e8be380f45e452c96fc 2558 zaqar-ui_4.0.0-1.dsc
 0f09b43a74b977b64463d2cda2f7bd0db5b79760 59740 zaqar-ui_4.0.0.orig.tar.xz
 35c1649b370216918328c5fe72ed3b3ad89c76c8 2972 zaqar-ui_4.0.0-1.debian.tar.xz
 72e5512a522263c402927e6d492ba17092850964 27800 python3-zaqar-ui_4.0.0-1_all.deb
 78f4f16c1d6a52a0b4e0b836e8f3ebd4b757d71a 17360 zaqar-ui_4.0.0-1_amd64.buildinfo
Checksums-Sha256:
 

Bug#884029: library package with conffile and SONAME?

[Philipp Hahn]

Hello,

some library packages like "libtirpc1" (just my example here) contain a
conffile like "/etc/netconfig". Naturally they must conflict with their
successor "libtirpc3" as they contain the same file name. Currently it
does not: 

1. Either I could add the "Conflicts: libtirpc1" but that would render
the rename of the package following the SONAME change useless as they
will never be co-installed anyway then.

2. Or I could add a "Replaces: libtirpc1 (<< 0.2.5-1.2)" to silence dpkg
and allow libtirpc3 to overwrite that with which still has the same
format and content. This has the drawback that anyone later on
installing 1 after 3 will get the error from dpkg as 1 is not allowed to
replace the file from 3.

3. And/or I can create an additional package "libtirpc-common" to just
contain that single conffile and make "libtirpc[13]" both depend on it.
This last option is AFAIK frowned upon as it creates yet another package
for a single file.

So whats the current best practice?

Philipp

Bug#873422: marked as done (oclgrind: Please update to llvm-toolchain 4.0 or, better, 5.0)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 13:00:19 +
with message-id 
and subject line Bug#873422: fixed in oclgrind 18.3-1
has caused the Debian Bug report #873422,
regarding oclgrind: Please update to llvm-toolchain 4.0 or, better, 5.0
to be marked as done.

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

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


-- 
873422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: oclgrind
Severity: normal

Hello,

Currently, we have 6 versions of the llvm toolchain in the archive.
I would like to move to 3 versions (4.0, 5.0 and snapshot, aka 6.0)

Could you please update your package to use 4.0 (or, better, 5.0 which will be 
released very 
soon)?

I will update the severity of this bug at the end of September

Thanks
Sylvestre
--- End Message ---
--- Begin Message ---
Source: oclgrind
Source-Version: 18.3-1

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

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

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

Debian distribution maintenance software
pp.
James Price  (supplier of updated oclgrind package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 Mar 2018 09:31:39 +
Source: oclgrind
Binary: liboclgrind-18.3 liboclgrind-dev oclgrind
Architecture: source i386
Version: 18.3-1
Distribution: unstable
Urgency: low
Maintainer: Debian OpenCL Maintainers 
Changed-By: James Price 
Description:
 liboclgrind-18.3 - core library for Oclgrind
 liboclgrind-dev - development files for Oclgrind
 oclgrind   - OpenCL device simulator
Closes: 873422
Changes:
 oclgrind (18.3-1) unstable; urgency=low
 .
   [ James Price ]
   * New upstream release
   * Refresh patches, drop those applied upstream
   * Update to LLVM/Clang 6.0 (Closes: #873422)
   * Bump Standards-Version to 4.1.3
   * Add debian/upstream/metadata file
 .
   [ Andreas Beckmann ]
   * Switch Vcs-* URLs to salsa.debian.org.
   * Install NEWS as upstream changelog.
Checksums-Sha1:
 f67f8931b68bce12f3a28a15fefc1fb5d2bdcbae 2213 oclgrind_18.3-1.dsc
 6e35ccd7f7f9e2c2f8c7c421f1866dcd98be3991 196160 oclgrind_18.3.orig.tar.gz
 1a2844d5c18a8b6bef458274c633d1141e20ac74 6784 oclgrind_18.3-1.debian.tar.xz
 1be113fdcaf04f631f0ebd5a16772051af747af7 5873964 
liboclgrind-18.3-dbgsym_18.3-1_i386.deb
 c48ced21b3946c906ea5038e824c6978d5235d29 16576988 
liboclgrind-18.3_18.3-1_i386.deb
 926584b26ae95245df7b1fafd73856f8246e6ff8 13540 liboclgrind-dev_18.3-1_i386.deb
 3c6412cec21adecd6ad1e2dd3d4bd72115366b8a 630860 oclgrind-dbgsym_18.3-1_i386.deb
 2a668ad2f7bdd866aeef3dc6a305e45e7ccf9634 8504 oclgrind_18.3-1_i386.buildinfo
 8150434fafb786a44045de17a0d3de411df4cb3a 91844 oclgrind_18.3-1_i386.deb
Checksums-Sha256:
 68f694833f7e5cce11183f447cd80dc8a600d660beb749b126ac7b5c458d3bfc 2213 
oclgrind_18.3-1.dsc
 90518d47573e64c6c28e173dc6f10c4e0ca53a99543ef2f1afaac1cbf725fe90 196160 
oclgrind_18.3.orig.tar.gz
 62bf94e7e00d6313e500ce2053492e161a60904ba96b84476f5baf46fd56 6784 
oclgrind_18.3-1.debian.tar.xz
 05c68791cf551b5bc3655f0bbeaa1b999c754790ffd5d720f40ccfac27e67af6 5873964 
liboclgrind-18.3-dbgsym_18.3-1_i386.deb
 a5f63cf2da74500fa60af18be70bc6dea6157afa1398d7d91f3511c412a3fa90 16576988 
liboclgrind-18.3_18.3-1_i386.deb
 00ecbb7ca4e743933f81ff1404886500dd9059fe233e77afcf49141ab85c886b 13540 
liboclgrind-dev_18.3-1_i386.deb
 090dea8b535e8afb7c360555e727e45de05b4152157e79bd58e777a7da575656 630860 
oclgrind-dbgsym_18.3-1_i386.deb
 11f42d5ba95926f72b85256c273119ef91e8e0c3c0f64927597a27caa37304e5 8504 
oclgrind_18.3-1_i386.buildinfo
 08bd2525a683134cf399843b7fb7781a5f3860227f8b4ba8684d85221c48 91844 
oclgrind_18.3-1_i386.deb
Files:
 e0df29c6a0ba5981ed3346923a93211b 2213 devel optional oclgrind_18.3-1.dsc
 7598e719b28d303f8d32f1e17730de9a 196160 devel optional 
oclgrind_18.3.orig.tar.gz
 fef1c7f29c99a4c6a02de330878a9fe8 6784 devel optional 
oclgrind_18.3-1.debian.tar.xz
 32667310ed3bda11c3b5416dc92257ed 5873964 debug optional 
liboclgrind-18.3-dbgsym_18.3-1_i386.deb
 

Bug#892995: systemtap: failes to compile scripts, implicit declaration of some functions

[Timo Lindfors]

Hi,

this is probably https://sourceware.org/bugzilla/show_bug.cgi?id=22158 
which suggests that 0643ca2b7 fixes this.


-Timo

Bug#891752: marked as done (cwltool FTBFS: error running tests)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 12:00:11 +
with message-id 
and subject line Bug#891752: fixed in cwltool 1.0.20180302231433-1
has caused the Debian Bug report #891752,
regarding cwltool FTBFS: error running tests
to be marked as done.

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

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


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

https://buildd.debian.org/status/fetch.php?pkg=cwltool=all=1.0.20180225105849-1=1519823880=0

...
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild pybuild:219: python2.7 /<>/setup.py develop
running develop
error: can't create or remove files in install directory

The following error occurred while trying to add or remove files in the
installation directory:

[Errno 13] Permission denied: 
'/usr/local/lib/python2.7/dist-packages/test-easy-install-6769.write-test'

The installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:

/usr/local/lib/python2.7/dist-packages/

Perhaps your account does not have write access to this directory?  If the
installation directory is a system-owned directory, you may need to sign in
as the administrator or "root" account.  If you do not have administrative
access to this machine, you may wish to choose a different installation
directory, preferably one that is listed in your PYTHONPATH environment
variable.

For information on other options, you may wish to consult the
documentation at:

  https://setuptools.readthedocs.io/en/latest/easy_install.html

Please make the appropriate changes for your system and try again.

E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: 
python2.7 /<>/setup.py develop
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
make: *** [debian/rules:11: build-indep] Error 25
--- End Message ---
--- Begin Message ---
Source: cwltool
Source-Version: 1.0.20180302231433-1

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated cwltool 
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, 05 Mar 2018 06:44:41 -0800
Source: cwltool
Binary: cwltool
Architecture: source all
Version: 1.0.20180302231433-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Description:
 cwltool- Common Workflow Language reference implementation
Closes: 891752
Changes:
 cwltool (1.0.20180302231433-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #891752)
Checksums-Sha1:
 0f52e7bfc11b2c4bd1fdae5d15a80d99117c3327 2487 cwltool_1.0.20180302231433-1.dsc
 498e3426c74180eeca23831c2f8e02dd492378ef 284687 
cwltool_1.0.20180302231433.orig.tar.gz
 a5083766c746ef8948046fa2cd6daf89f5fc0ecb 4496 
cwltool_1.0.20180302231433-1.debian.tar.xz
 04752dd4008431430d3f90bd95347b93d6c576b6 143886 
cwltool_1.0.20180302231433-1_all.deb
 cc524f22cbec5f88fe38834b7573068c421e42b3 7512 
cwltool_1.0.20180302231433-1_amd64.buildinfo
Checksums-Sha256:
 12d226cc20f7ea587b429454343bce5bbcc745ab763ae2d375510530fdf6b04f 2487 
cwltool_1.0.20180302231433-1.dsc
 a8b3b9391ef1b9045aec8f18b8bc0003a9328c2b15c8727ae8891a687f89d2a3 284687 
cwltool_1.0.20180302231433.orig.tar.gz
 72c94fc2e5de4549f6704194cc52529eded06e0a6525d47c331377dd936d53a1 4496 
cwltool_1.0.20180302231433-1.debian.tar.xz
 255eac28ec6f3aee0f036bdc8453dc89c4a1220fe6f70e8bed93d7f658a921d4 143886 
cwltool_1.0.20180302231433-1_all.deb
 16c8b0fb4a41d6de148b8e5cf6b4a26f264cb3d4ffe9aef794689df533d629bf 7512 
cwltool_1.0.20180302231433-1_amd64.buildinfo
Files:
 6cac0ba3dd486c8be3a1fd00dc85c557 2487 science optional 
cwltool_1.0.20180302231433-1.dsc
 fdbb8fc9c1c0c8db4d829f5db9d2b8af 284687 science optional 

Bug#892995: systemtap: failes to compile scripts, implicit declaration of some functions

[Frank Ch. Eigler]

Hi -

> Package: systemtap
> Version: 3.1-3
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
> [...]

Due to the absence of a fixed kernel API, newer systemtap versions are
required to deal with newer kernels.  The particular errors listed
here have been dealt with in upstream systemtap at

https://sourceware.org/bugzilla/show_bug.cgi?id=22551

- FChE

Bug#892372: marked as done (proftpd-mod-msg FTBFS with proftpd 1.3.6-1)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 11:37:14 +
with message-id 
and subject line Bug#892372: fixed in proftpd-mod-msg 0.4.1-2
has caused the Debian Bug report #892372,
regarding proftpd-mod-msg FTBFS with proftpd 1.3.6-1
to be marked as done.

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

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


-- 
892372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: proftpd-mod-msg
Version: 0.4.1-1.1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/proftpd-mod-msg.html

...
mod_msg.c:56:3: error: #error "mod_msg requires Controls support 
(--enable-ctrls)"
 # error "mod_msg requires Controls support (--enable-ctrls)"
   ^
--- End Message ---
--- Begin Message ---
Source: proftpd-mod-msg
Source-Version: 0.4.1-2

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

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

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

Debian distribution maintenance software
pp.
Francesco Paolo Lovergine  (supplier of updated 
proftpd-mod-msg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Mar 2018 12:10:44 +0100
Source: proftpd-mod-msg
Binary: proftpd-mod-msg
Architecture: source amd64
Version: 0.4.1-2
Distribution: unstable
Urgency: low
Maintainer: ProFTPD Maintainance Team 

Changed-By: Francesco Paolo Lovergine 
Description:
 proftpd-mod-msg - ProFTPD module mod_msg
Closes: 892372
Changes:
 proftpd-mod-msg (0.4.1-2) unstable; urgency=low
 .
   [ Fabrizio Regalli ]
   * Removing libacl1-dev as BD and increasing proftpd-dev to (>= 1.3.4~rc3-2~)
 .
   [Hilmar Preuße]
   * Patch from Gentoo[1] to make module work w/ ProFTP 1.3.6:
 proftpd-1.3.6_rc4-msg-refresh-api.patch
 (Closes: #892372)
 .
   * Remove Fabrizio Regalli from uploaders list
   * d/control: Remove "DM-Upload-Allowed" field
   * d/rules: add --without python-support to dh call
   * d/rules: overhaul clean target to make it work
   * raise dh compat level to 9, adapt bd version accordingly
   * tighten BD version of proftp-dev to 1.3.6
   * Standards Version 4.1.3, no changes needed.
 .
   [1] 
https://gitweb.gentoo.org/repo/gentoo.git/commit/net-ftp/proftpd/files/proftpd-1.3.6_rc4-msg-refresh-api.patch?id=fba48bedb74f80376bb3a6761a052244350f4fd8
Checksums-Sha1:
 97e2a5acf7be9ae39189fc4020f5c5a7e684630c 2077 proftpd-mod-msg_0.4.1-2.dsc
 c8d6c037464452d0239cc4365efce78862f932ea 4340 
proftpd-mod-msg_0.4.1-2.debian.tar.xz
 e9a0cdf54a2540c6b97568366af9b49dbfd90d66 20056 
proftpd-mod-msg-dbgsym_0.4.1-2_amd64.deb
 cf65440a205a563f448bdff4917f11e59c98d0ad 6892 
proftpd-mod-msg_0.4.1-2_amd64.buildinfo
 b869ca9908ef19183c3bbe6a1cd9cc9091e3f0fe 31880 
proftpd-mod-msg_0.4.1-2_amd64.deb
Checksums-Sha256:
 42b15606401d2c86d70fa3be199d612ad97370ada93170912d28153b4b966591 2077 
proftpd-mod-msg_0.4.1-2.dsc
 e687c7b6bd61c8b17a741434a67b6c3016f4c6ce80469fcc28d8a25cdfc658d7 4340 
proftpd-mod-msg_0.4.1-2.debian.tar.xz
 2d9b3a5be64705c0a90755ecd2bba7b0df08509495c1c01c97e2212cecd67af3 20056 
proftpd-mod-msg-dbgsym_0.4.1-2_amd64.deb
 6110eed62dbd146b81a441e25b70648c088fce2b59d25edc6dda7a9727dabd88 6892 
proftpd-mod-msg_0.4.1-2_amd64.buildinfo
 598673c20941d4eaab160196bbece3a446238c5a74939e22facd010d0e6266fb 31880 
proftpd-mod-msg_0.4.1-2_amd64.deb
Files:
 93149f2704a1bac863618365b12789cd 2077 net optional proftpd-mod-msg_0.4.1-2.dsc
 9cff4e371fa31d9527a92f89d890f6f4 4340 net optional 
proftpd-mod-msg_0.4.1-2.debian.tar.xz
 902c369d09843a85d3ffce0b21b5317b 20056 debug optional 
proftpd-mod-msg-dbgsym_0.4.1-2_amd64.deb
 48912f70c84e387a3ca69b7d6c295a45 6892 net optional 
proftpd-mod-msg_0.4.1-2_amd64.buildinfo
 ef32eaab8ce14cbc8b079f456dd79140 31880 net optional 
proftpd-mod-msg_0.4.1-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEBXmpeiI46/m+Ye0CDwKl4RY2hqQFAlqqVVgTHGZyYW5raWVA
ZGViaWFuLm9yZwAKCRAPAqXhFjaGpMr5EACn3qfo0SC5qP+25QhqeupyinnCFFVV

Bug#892700: marked as done (metview: FTBFS, probably missing B-D: libfftw3-dev)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 11:20:41 +
with message-id 
and subject line Bug#892700: fixed in metview 5.0.1-2
has caused the Debian Bug report #892700,
regarding metview: FTBFS, probably missing B-D: libfftw3-dev
to be marked as done.

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

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


-- 
892700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: metview
Version: 5.0.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

metview/experimental FTFBS:
https://buildd.debian.org/status/package.php?p=metview=experimental

make[3]: *** No rule to make target '/usr/lib/aarch64-linux-gnu/libfftw3.so', 
needed by 'lib/libMvMars.so.0.0.0'.  Stop.

This is probably a missing Build-Depends: libfftw3-dev


Andreas
--- End Message ---
--- Begin Message ---
Source: metview
Source-Version: 5.0.1-2

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

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

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated metview package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 13 Mar 2018 04:06:36 +
Source: metview
Binary: metview metview-data libmetview0d libmetview-dev
Architecture: source amd64 all
Version: 5.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libmetview-dev - Development files for MetView
 libmetview0d - Shared libraries  for MetView
 metview- Interactive data visualization and analysis environment,
 metview-data - Data needed for the Metview data analysis environment
Closes: 892700
Changes:
 metview (5.0.1-2) unstable; urgency=medium
 .
   * Add libfftw-dev build-dep. Closes: 892700,
Checksums-Sha1:
 7540dc91c6823bb8a8718c3db189bceca6d707ef 2622 metview_5.0.1-2.dsc
 251f1e1b373e534de26f0ff89239bdcc556ab2b9 43196 metview_5.0.1-2.debian.tar.xz
 0c849fdf978466f8bece931acdfeb1c080725599 257608 
libmetview-dev_5.0.1-2_amd64.deb
 5bff7bf2f0654e263c56a9bfb4fcd78323cf9e66 7238104 
libmetview0d-dbgsym_5.0.1-2_amd64.deb
 f9d3a599a75fff8e61a5a31a095014fcee179946 1401456 libmetview0d_5.0.1-2_amd64.deb
 be76eef7a97d9e8e6f7b2892668fb135a60be283 1499312 metview-data_5.0.1-2_all.deb
 b88f3b670415b1b6b0f636c2f2da3b87b42fca3e 98354584 
metview-dbgsym_5.0.1-2_amd64.deb
 7fdeacbec90790347495f16efc0a37b45748f9db 18176 metview_5.0.1-2_amd64.buildinfo
 ef669cd2c1333fc9bf462fffdfef9afd29402ca8 5574752 metview_5.0.1-2_amd64.deb
Checksums-Sha256:
 0c0435db03c1916cce8d9d1e3e53f9bd840e20ad19b6681b891823de1ad31914 2622 
metview_5.0.1-2.dsc
 85698db92e69d5649259d6570eb75d8279bcdc44a4985436cd9b80ce01db532e 43196 
metview_5.0.1-2.debian.tar.xz
 3d3aa22b77736130e8e1e54e6878e27067fca911d97741d9499970a9aed226ea 257608 
libmetview-dev_5.0.1-2_amd64.deb
 ff57f60b750db52d968b400f2d7ac42b100b1d47483375e54fa7a84124b3d8dd 7238104 
libmetview0d-dbgsym_5.0.1-2_amd64.deb
 5f7906436b4dccd58ad214e7b56293421343c5cef9a9e6db4f593a04979154a0 1401456 
libmetview0d_5.0.1-2_amd64.deb
 54627c3386a0d15012bb1ca0f53a6292da176590b6149ff7f14b26257efe9e4d 1499312 
metview-data_5.0.1-2_all.deb
 7284eecec38d4522921f4dc0d9ceb7d6bec1ef30b779c1b36a83b9dcbb4f99dd 98354584 
metview-dbgsym_5.0.1-2_amd64.deb
 d7a525baa364a3599fa62d2fc6e38272eaa1b9b3488bd93012ece9622bc08869 18176 
metview_5.0.1-2_amd64.buildinfo
 64eb3ad39b684aecb5223292e6048187c04759a340578ca3b9ea6779756bfc2c 5574752 
metview_5.0.1-2_amd64.deb
Files:
 3259c360ff5966d4ca31314a4c3d43ca 2622 science optional metview_5.0.1-2.dsc
 ad0a9d3e7740001eca1aec8b58e7cbbf 43196 science optional 
metview_5.0.1-2.debian.tar.xz
 4256432780aca6a156fa6886efb5cd6b 257608 libdevel optional 
libmetview-dev_5.0.1-2_amd64.deb
 ad12e727af7011c567f4b2a5a40b78de 7238104 debug optional 
libmetview0d-dbgsym_5.0.1-2_amd64.deb
 c7be1a00c2ed42b032fe89dcc790c122 1401456 libs optional 
libmetview0d_5.0.1-2_amd64.deb
 

Bug#892997: mailfilter FTBFS with flex 2.6.4-6

[Adrian Bunk]

Source: mailfilter
Version: 0.8.6-2
Severity: serious
Tags: buster sid patch

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

...
g++ -Wall -g -O2 -fstack-protector-strong -Wformat -Werror=format-security  
-Wl,-z,relro -Wl,-z,now -o mailfilter md5c.o rcfile.o rcparser.o rfc822.o 
rfc822parser.o mailfilter.o header.o weeder.o preferences.o feedback.o filter.o 
score.o account.o protocol.o socket.o pop3.o apop.o imap.o   -lfl -lnsl -lssl 
-lcrypto 
/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libfl.so: undefined 
reference to `yylex'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:415: mailfilter] Error 1


For fixing this FTBFS, required are both the attached patch
and running automake (e.g. dh compat 10).
Description: Remove unused linking with libfl
 Due to the yylex requirement this caused FTBFS
 when a shared libfl is provided.
 .
 libfl is not required due to noyywrap.
Author: Adrian Bunk 

--- mailfilter-0.8.6.orig/src/Makefile.am
+++ mailfilter-0.8.6/src/Makefile.am
@@ -79,5 +79,3 @@ AM_CPPFLAGS = -I$(includedir)
  -DLOCALEDIR=\"$(datadir)/locale\"   \
  -I$(top_srcdir)/intl\
  -I$(top_builddir) -I$(top_builddir)/include -I.
-
-LIBS = @LEXLIB@ @LIBS@

Bug#892995: systemtap: failes to compile scripts, implicit declaration of some functions

[choury]

Package: systemtap
Version: 3.1-3
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

The error log of "stap -v -e 'probe vfs.read {printf("read performed\n"); 
exit()}'":


Pass 1: parsed user script and 466 library scripts using 
114224virt/47336res/6424shr/41108data kb, in 60usr/80sys/198real ms.
Pass 2: analyzed script: 1 probe, 1 function, 7 embeds, 0 globals using 
290116virt/224684res/7844shr/217000data kb, in 1310usr/120sys/1442real ms.
Pass 3: translated to C into 
"/tmp/stapmbSbnD/stap_93c22f4dd82758d8a2c6248ef9859b2a_2556_src.c" using 
290116virt/224876res/8036shr/217000data kb, in 0usr/0sys/5real ms.
In file included from /usr/share/systemtap/runtime/stp_utrace.c:30:0,
 from /usr/share/systemtap/runtime/linux/task_finder2.c:4,
 from /usr/share/systemtap/runtime/linux/task_finder.c:17,
 from /usr/share/systemtap/runtime/linux/runtime.h:222,
 from /usr/share/systemtap/runtime/runtime.h:26,
 from 
/tmp/stapmbSbnD/stap_93c22f4dd82758d8a2c6248ef9859b2a_2556_src.c:25:
/usr/share/systemtap/runtime/stp_helper_lock.h: In function 
‘stp_spin_unlock_wait’:
/usr/share/systemtap/runtime/stp_helper_lock.h:60:61: error: implicit 
declaration of function ‘spin_unlock_wait’; did you mean 
‘stp_spin_unlock_wait’? [-Werror=implicit-function-declaration]
 static inline void stp_spin_unlock_wait(spinlock_t *lock) { 
spin_unlock_wait(lock); }
 ^~~~
 
stp_spin_unlock_wait
In file included from /usr/share/systemtap/runtime/transport/transport.c:65:0,
 from /usr/share/systemtap/runtime/linux/print.c:17,
 from /usr/share/systemtap/runtime/print.c:17,
 from /usr/share/systemtap/runtime/runtime_context.h:22,
 from 
/tmp/stapmbSbnD/stap_93c22f4dd82758d8a2c6248ef9859b2a_2556_src.c:121:
/usr/share/systemtap/runtime/transport/relay_v2.c: In function 
‘__stp_relay_timer_init’:
/usr/share/systemtap/runtime/transport/relay_v2.c:154:2: error: implicit 
declaration of function ‘init_timer’; did you mean ‘init_timers’? 
[-Werror=implicit-function-declaration]
  init_timer(&_stp_relay_data.timer);
  ^~
  init_timers
/usr/share/systemtap/runtime/transport/relay_v2.c:156:33: error: assignment 
from incompatible pointer type [-Werror=incompatible-pointer-types]
  _stp_relay_data.timer.function = __stp_relay_wakeup_timer;
 ^
/usr/share/systemtap/runtime/transport/relay_v2.c:157:23: error: ‘struct 
timer_list’ has no member named ‘data’
  _stp_relay_data.timer.data = 0;
   ^
In file included from /usr/share/systemtap/runtime/linux/print.c:17:0,
 from /usr/share/systemtap/runtime/print.c:17,
 from /usr/share/systemtap/runtime/runtime_context.h:22,
 from 
/tmp/stapmbSbnD/stap_93c22f4dd82758d8a2c6248ef9859b2a_2556_src.c:121:
/usr/share/systemtap/runtime/transport/transport.c: In function ‘_stp_attach’:
/usr/share/systemtap/runtime/transport/transport.c:328:31: error: assignment 
from incompatible pointer type [-Werror=incompatible-pointer-types]
  _stp_ctl_work_timer.function = _stp_ctl_work_callback;
   ^
/usr/share/systemtap/runtime/transport/transport.c:329:21: error: ‘struct 
timer_list’ has no member named ‘data’
  _stp_ctl_work_timer.data= 0;
 ^
cc1: all warnings being treated as errors
make[3]: *** 
[/usr/src/linux-headers-4.15.0-1-common/scripts/Makefile.build:321: 
/tmp/stapmbSbnD/stap_93c22f4dd82758d8a2c6248ef9859b2a_2556_src.o] Error 1
make[2]: *** [/usr/src/linux-headers-4.15.0-1-common/Makefile:1523: 
_module_/tmp/stapmbSbnD] Error 2
make[1]: *** [Makefile:146: sub-make] Error 2
make: *** [Makefile:8: all] Error 2
WARNING: kbuild exited with status: 2
Pass 4: compiled C into "stap_93c22f4dd82758d8a2c6248ef9859b2a_2556.ko" in 
7750usr/1280sys/9054real ms.
Pass 4: compilation failed.  [man error::pass4]
Tip: /usr/share/doc/systemtap/README.Debian should help you get started.

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

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

Versions of packages systemtap depends on:
ii  libavahi-client3   0.7-3.1
ii  libavahi-common3   0.7-3.1
ii  libc6  2.27-2
ii  libdw1 0.170-0.3
ii  libelf10.170-0.3
ii  libgcc11:8-20180312-2
ii  libnspr4   2:4.18-1
ii  libnss32:3.35-2
ii  libsqlite3-0   3.22.0-1
ii  libstdc++6 

Bug#892511: marked as done (ruby-grape-route-helpers: FTBFS and Debci failure with ruby-grape 0.19.2-3)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 10:20:29 +
with message-id 
and subject line Bug#892511: fixed in ruby-grape-route-helpers 2.1.0-2
has caused the Debian Bug report #892511,
regarding ruby-grape-route-helpers: FTBFS and Debci failure with ruby-grape 
0.19.2-3
to be marked as done.

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

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


-- 
892511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-grape-route-helpers
Version: 2.1.0-1
Severity: serious

https://ci.debian.net/packages/r/ruby-grape-route-helpers/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-grape-route-helpers.html

...
Failures:

  1) GrapeRouteHelpers::DecoratedRoute#helper_names when an API has multiple 
versions returns the route's helper name for each version
 Failure/Error: route_version.scan(version_pattern)

 NoMethodError:
   undefined method `scan' for ["beta", "alpha", "v1"]:Array
 # ./lib/grape-route-helpers/decorated_route.rb:69:in `route_versions'
 # ./lib/grape-route-helpers/decorated_route.rb:33:in `define_path_helpers'
 # ./lib/grape-route-helpers/decorated_route.rb:17:in `initialize'
 # ./spec/grape_route_helpers/decorated_route_spec.rb:8:in `new'
 # ./spec/grape_route_helpers/decorated_route_spec.rb:8:in `block (3 
levels) in '
 # ./spec/grape_route_helpers/decorated_route_spec.rb:7:in `map'
 # ./spec/grape_route_helpers/decorated_route_spec.rb:7:in `block (2 
levels) in '
 # ./spec/grape_route_helpers/decorated_route_spec.rb:29:in `block (2 
levels) in '
 # ./spec/grape_route_helpers/decorated_route_spec.rb:75:in `block (4 
levels) in '

  2) GrapeRouteHelpers::DecoratedRoute#path_helper_name when the path is a 
catch-all path returns a name without the glob star
 Failure/Error: expect(result).to eq('api_v1_path_path')

   expected: "api_v1_path_path"
got: "api_v1___path_path"

   (compared using ==)
 # ./spec/grape_route_helpers/decorated_route_spec.rb:147:in `block (4 
levels) in '

  3) GrapeRouteHelpers::DecoratedRoute path helper method when a route's API 
has multiple versions returns a path for each version
 Failure/Error: route_version.scan(version_pattern)

 NoMethodError:
   undefined method `scan' for ["beta", "alpha", "v1"]:Array
 # ./lib/grape-route-helpers/decorated_route.rb:69:in `route_versions'
 # ./lib/grape-route-helpers/decorated_route.rb:33:in `define_path_helpers'
 # ./lib/grape-route-helpers/decorated_route.rb:17:in `initialize'
 # ./spec/grape_route_helpers/decorated_route_spec.rb:8:in `new'
 # ./spec/grape_route_helpers/decorated_route_spec.rb:8:in `block (3 
levels) in '
 # ./spec/grape_route_helpers/decorated_route_spec.rb:7:in `map'
 # ./spec/grape_route_helpers/decorated_route_spec.rb:7:in `block (2 
levels) in '
 # ./spec/grape_route_helpers/decorated_route_spec.rb:29:in `block (2 
levels) in '
 # ./spec/grape_route_helpers/decorated_route_spec.rb:222:in `block (4 
levels) in '

  4) GrapeRouteHelpers::NamedRouteMatcher#route_match? when route responds to a 
method name returns true
 Failure/Error: route_version.scan(version_pattern)

 NoMethodError:
   undefined method `scan' for ["beta", "alpha", "v1"]:Array
 # ./lib/grape-route-helpers/decorated_route.rb:69:in `route_versions'
 # ./lib/grape-route-helpers/decorated_route.rb:33:in `define_path_helpers'
 # ./lib/grape-route-helpers/decorated_route.rb:17:in `initialize'
 # ./lib/grape-route-helpers/all_routes.rb:8:in `new'
 # ./lib/grape-route-helpers/all_routes.rb:8:in `block in decorated_routes'
 # ./lib/grape-route-helpers/all_routes.rb:8:in `map'
 # ./lib/grape-route-helpers/all_routes.rb:8:in `decorated_routes'
 # ./spec/grape_route_helpers/named_route_matcher_spec.rb:7:in `block (2 
levels) in '
 # ./spec/grape_route_helpers/named_route_matcher_spec.rb:11:in `block (2 
levels) in '
 # ./spec/grape_route_helpers/named_route_matcher_spec.rb:30:in `block (4 
levels) in '
 # ./spec/grape_route_helpers/named_route_matcher_spec.rb:43:in `block (4 
levels) in '

  5) GrapeRouteHelpers::NamedRouteMatcher#route_match? when route responds to a 
method name when segments is not a hash raises an ArgumentError
 Failure/Error:
   expect do
 route_match?(route, method_name, 1234)
   end.to raise_error(ArgumentError)

   expected ArgumentError, got # with backtrace:
 # 

Bug#891209: ruby-github-api: Depends: ruby-faraday (< 0.10) but 0.13.1-2 is to be installed

[Pirate Praveen]

On Fri, 23 Feb 2018 14:05:36 +0200 Adrian Bunk  wrote:>
The following packages have unmet dependencies:
>  ruby-github-api : Depends: ruby-faraday (< 0.10) but 0.13.1-2 is to be 
> installed

This is blocking testing migration of ruby-faraday. There is a new
upstream release which declares a compatible dependency on faraday.



signature.asc
Description: OpenPGP digital signature

Bug#892991: ruby-bundler is no longer installable

[Adrian Bunk]

Package: ruby-bundler
Version: 1.15.1-1
Severity: serious

ruby-bundler depends on ruby-molinillo.

ruby-molinillo 0.6.4-1 breaks ruby-bundler (<< 1.16.1-1~).

Bug#890137: marked as done (jellyfish FTBFS on arm64/ppc64el: FAIL: tests/generate_sequence)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 09:49:59 +
with message-id 
and subject line Bug#890137: fixed in jellyfish 2.2.8-2
has caused the Debian Bug report #890137,
regarding jellyfish FTBFS on arm64/ppc64el: FAIL: tests/generate_sequence
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.)


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

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

...
FAIL: tests/generate_sequence
=

Seed: 3141592653
Creating fasta file 'seq10m.fa'
Seed: 1040104553
Creating fasta file 'seq1m_0.fa'
Creating fasta file 'seq1m_1.fa'
Creating fasta file 'seq1m_2.fa'
Creating fasta file 'seq1m_3.fa'
Creating fasta file 'seq1m_4.fa'
Seed: 1473540700
Creating fastq file 'seq10m.fq'
Usage: fastq2sam [options] fastq:string+
Use --help for more information
FAIL tests/generate_sequence.sh (exit status: 1)

SKIP: tests/big
===

Skip big test
SKIP tests/big.sh (exit status: 77)

SKIP: tests/sam
===

Skip SAM/BAM/CRAM file format test
SKIP tests/sam.sh (exit status: 77)

SKIP: tests/swig_python
===

SKIP tests/swig_python.sh (exit status: 77)

SKIP: tests/swig_ruby
=

SKIP tests/swig_ruby.sh (exit status: 77)


Testsuite summary for jellyfish 2.2.7

# TOTAL: 14
# PASS:  9
# SKIP:  4
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to gmarc...@umd.edu

Makefile:2280: recipe for target 'test-suite.log' failed
make[4]: *** [test-suite.log] Error 1


There are also FTBFS on other architectures, but the arm64/ppc64el
ones are RC since 2.2.6-6 built there.
--- End Message ---
--- Begin Message ---
Source: jellyfish
Source-Version: 2.2.8-2

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated jellyfish 
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, 12 Mar 2018 05:31:00 -0700
Source: jellyfish
Binary: jellyfish libjellyfish-2.0-2 libjellyfish-2.0-dev python3-dna-jellyfish 
libjellyfish-perl jellyfish-examples
Architecture: source
Version: 2.2.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Description:
 jellyfish  - count k-mers in DNA sequences
 jellyfish-examples - count k-mers in DNA sequences (examples for testing)
 libjellyfish-2.0-2 - count k-mers in DNA sequences (dynamic library of 
jellyfish)
 libjellyfish-2.0-dev - count k-mers in DNA sequences (development files of 
jellyfish)
 libjellyfish-perl - count k-mers in DNA sequences (Perl bindings of jellyfish)
 python3-dna-jellyfish - count k-mers in DNA sequences (Python bindings of 
jellyfish)
Closes: 890137
Changes:
 jellyfish (2.2.8-2) unstable; urgency=medium
 .
   * Add the missing small_mers.sh file, courtesy upstream.
   * Fix arm/powerpc build, patch courtesy upstream (Closes: #890137)
Checksums-Sha1:
 b3a1c0e8a7cd2a2181de8884636aaab52d24c699 2514 jellyfish_2.2.8-2.dsc
 61d050d5da9c5e4c38e6757909afc3c00e5e69bf 12028 jellyfish_2.2.8-2.debian.tar.xz
 a51129bdd26378e0ff177a0b04c5d2c957046536 7952 
jellyfish_2.2.8-2_source.buildinfo
Checksums-Sha256:
 dd36d315956eb97c8239726db26690f19f76b7f2b1ef5f2984a38d427898f10a 2514 
jellyfish_2.2.8-2.dsc
 ac4a33f2676f94ba506ea1d59f19ec05b4f0566df6f1261683d755239adf084c 12028 
jellyfish_2.2.8-2.debian.tar.xz
 12132f55a104c244c67f6bb43b2f2561f709eb9ff50f4a8f87ec89a95a4c94d6 7952 

Bug#892988: autokey-gtk: does not start

[Francesco Marchesi]

Package: autokey-gtk
Version: 0.90.4-1.1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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

the applet is not shown.
Trying to start it from the terminal, leads to the following error:

/usr/lib/python2.7/dist-packages/autokey/gtkapp.py:24: PyGIWarning: Gtk was
imported without specifying a version first. Use gi.require_version('Gtk',
'3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk, Gdk, GObject, GLib
Traceback (most recent call last):
  File "/usr/bin/autokey-gtk", line 20, in 
from autokey.gtkapp import Application
  File "/usr/lib/python2.7/dist-packages/autokey/gtkapp.py", line 28, in

import service, monitor
  File "/usr/lib/python2.7/dist-packages/autokey/service.py", line 21, in

from iomediator import Key, IoMediator
  File "/usr/lib/python2.7/dist-packages/autokey/iomediator.py", line 107, in

from interface import *
  File "/usr/lib/python2.7/dist-packages/autokey/interface.py", line 29, in

from Xlib import X, XK, display, error
  File "/usr/lib/python2.7/dist-packages/Xlib/display.py", line 26, in 
from six import create_unbound_method
ImportError: cannot import name create_unbound_method

I'm using Cinnamon DE
Thanks,
Francesco



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

Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages autokey-gtk depends on:
ii  autokey-common0.90.4-1.1
ii  gir1.2-glib-2.0   1.54.1-4
ii  gir1.2-gtk-3.03.22.28-1
ii  gir1.2-gtksource-3.0  3.24.6-1
ii  gir1.2-notify-0.7 0.7.7-3
ii  python2.7.14-4
ii  python-dbus   1.2.6-1
ii  python-gi 3.26.1-2
ii  zenity3.27.90-1

autokey-gtk recommends no packages.

autokey-gtk suggests no packages.

-- no debconf information

Bug#892710: marked as done ({tcl,tk}-i{tcl,tk}4-{dev,doc}: missing Conflicts: i{tcl,tk}-{dev,doc})

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 08:52:27 +
with message-id 
and subject line Bug#892710: fixed in itk4 4.1.0-3
has caused the Debian Bug report #892710,
regarding {tcl,tk}-i{tcl,tk}4-{dev,doc}: missing Conflicts: i{tcl,tk}-{dev,doc}
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.)


-- 
892710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tcl-itcl4-dev,tcl-itcl4-doc,tk-itk4-doc,tk-itk4-dev
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 4.1.0-1
Control: found -1 4.1.1-1

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' 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...):

  Selecting previously unselected package tcl-itcl4-dev:amd64.
  Preparing to unpack .../tcl-itcl4-dev_4.1.1-1_amd64.deb ...
  Unpacking tcl-itcl4-dev:amd64 (4.1.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tcl-itcl4-dev_4.1.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/itclConfig.sh', which is also 
in package itcl3-dev:amd64 3.4.3-2
  Errors were encountered while processing:
   /var/cache/apt/archives/tcl-itcl4-dev_4.1.1-1_amd64.deb

  Selecting previously unselected package tcl-itcl4-doc.
  Preparing to unpack .../tcl-itcl4-doc_4.1.1-1_all.deb ...
  Unpacking tcl-itcl4-doc (4.1.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tcl-itcl4-doc_4.1.1-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/body.3itcl.gz', which is also in 
package itcl3-doc 3.4.3-2
  Errors were encountered while processing:
   /var/cache/apt/archives/tcl-itcl4-doc_4.1.1-1_all.deb

  Selecting previously unselected package tcl-itcl4-dev:amd64.
  Preparing to unpack .../3-tcl-itcl4-dev_4.1.1-1_amd64.deb ...
  Unpacking tcl-itcl4-dev:amd64 (4.1.1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-u8Krl5/3-tcl-itcl4-dev_4.1.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/itclConfig.sh', which is also 
in package itcl3-dev:amd64 3.4.3-2
  Selecting previously unselected package tk-itk4:amd64.
  Preparing to unpack .../4-tk-itk4_4.1.0-1_amd64.deb ...
  Unpacking tk-itk4:amd64 (4.1.0-1) ...
  Selecting previously unselected package tk-itk4-dev:amd64.
  Preparing to unpack .../5-tk-itk4-dev_4.1.0-1_amd64.deb ...
  Unpacking tk-itk4-dev:amd64 (4.1.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-u8Krl5/5-tk-itk4-dev_4.1.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/itkConfig.sh', which is also 
in package itk3-dev:amd64 3.4.2-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-u8Krl5/3-tcl-itcl4-dev_4.1.1-1_amd64.deb
   /tmp/apt-dpkg-install-u8Krl5/5-tk-itk4-dev_4.1.0-1_amd64.deb

  Selecting previously unselected package tk-itk4-doc.
  Preparing to unpack .../tk-itk4-doc_4.1.0-1_all.deb ...
  Unpacking tk-itk4-doc (4.1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tk-itk4-doc_4.1.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/Archetype.3itk.gz', which is also 
in package itk3-doc 3.4.2-2
  Errors were encountered while processing:
   /var/cache/apt/archives/tk-itk4-doc_4.1.0-1_all.deb

The new packages also need a Conflicts against the old virtual package
names (i{tcl,tk}-*) used in stretch and buster to ensure clean upgrade paths.


cheers,

Andreas


itcl3-dev=3.4.3-2_tcl-itcl4-dev=4.1.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: itk4
Source-Version: 4.1.0-3

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

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

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

Debian distribution maintenance software
pp.
Sergei Golovan  (supplier of updated itk4 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive

Bug#892710: marked as done ({tcl,tk}-i{tcl,tk}4-{dev,doc}: missing Conflicts: i{tcl,tk}-{dev,doc})

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 08:52:14 +
with message-id 
and subject line Bug#892710: fixed in itcl4 4.1.1-3
has caused the Debian Bug report #892710,
regarding {tcl,tk}-i{tcl,tk}4-{dev,doc}: missing Conflicts: i{tcl,tk}-{dev,doc}
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.)


-- 
892710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tcl-itcl4-dev,tcl-itcl4-doc,tk-itk4-doc,tk-itk4-dev
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 4.1.0-1
Control: found -1 4.1.1-1

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' 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...):

  Selecting previously unselected package tcl-itcl4-dev:amd64.
  Preparing to unpack .../tcl-itcl4-dev_4.1.1-1_amd64.deb ...
  Unpacking tcl-itcl4-dev:amd64 (4.1.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tcl-itcl4-dev_4.1.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/itclConfig.sh', which is also 
in package itcl3-dev:amd64 3.4.3-2
  Errors were encountered while processing:
   /var/cache/apt/archives/tcl-itcl4-dev_4.1.1-1_amd64.deb

  Selecting previously unselected package tcl-itcl4-doc.
  Preparing to unpack .../tcl-itcl4-doc_4.1.1-1_all.deb ...
  Unpacking tcl-itcl4-doc (4.1.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tcl-itcl4-doc_4.1.1-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/body.3itcl.gz', which is also in 
package itcl3-doc 3.4.3-2
  Errors were encountered while processing:
   /var/cache/apt/archives/tcl-itcl4-doc_4.1.1-1_all.deb

  Selecting previously unselected package tcl-itcl4-dev:amd64.
  Preparing to unpack .../3-tcl-itcl4-dev_4.1.1-1_amd64.deb ...
  Unpacking tcl-itcl4-dev:amd64 (4.1.1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-u8Krl5/3-tcl-itcl4-dev_4.1.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/itclConfig.sh', which is also 
in package itcl3-dev:amd64 3.4.3-2
  Selecting previously unselected package tk-itk4:amd64.
  Preparing to unpack .../4-tk-itk4_4.1.0-1_amd64.deb ...
  Unpacking tk-itk4:amd64 (4.1.0-1) ...
  Selecting previously unselected package tk-itk4-dev:amd64.
  Preparing to unpack .../5-tk-itk4-dev_4.1.0-1_amd64.deb ...
  Unpacking tk-itk4-dev:amd64 (4.1.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-u8Krl5/5-tk-itk4-dev_4.1.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/itkConfig.sh', which is also 
in package itk3-dev:amd64 3.4.2-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-u8Krl5/3-tcl-itcl4-dev_4.1.1-1_amd64.deb
   /tmp/apt-dpkg-install-u8Krl5/5-tk-itk4-dev_4.1.0-1_amd64.deb

  Selecting previously unselected package tk-itk4-doc.
  Preparing to unpack .../tk-itk4-doc_4.1.0-1_all.deb ...
  Unpacking tk-itk4-doc (4.1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tk-itk4-doc_4.1.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/Archetype.3itk.gz', which is also 
in package itk3-doc 3.4.2-2
  Errors were encountered while processing:
   /var/cache/apt/archives/tk-itk4-doc_4.1.0-1_all.deb

The new packages also need a Conflicts against the old virtual package
names (i{tcl,tk}-*) used in stretch and buster to ensure clean upgrade paths.


cheers,

Andreas


itcl3-dev=3.4.3-2_tcl-itcl4-dev=4.1.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: itcl4
Source-Version: 4.1.1-3

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

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

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

Debian distribution maintenance software
pp.
Sergei Golovan  (supplier of updated itcl4 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive

Processed: bug 892511 is forwarded to https://github.com/reprah/grape-route-helpers/pull/19

[Debian Bug Tracking System]

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

> forwarded 892511 https://github.com/reprah/grape-route-helpers/pull/19
Bug #892511 [src:ruby-grape-route-helpers] ruby-grape-route-helpers: FTBFS and 
Debci failure with ruby-grape 0.19.2-3
Set Bug forwarded-to-address to 
'https://github.com/reprah/grape-route-helpers/pull/19'.
> thanks
Stopping processing here.

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

Bug#892468: proftp: Prevent migration to testing

[Hilmar Preuße]

Am 09.03.2018 um 16:37 teilte Francesco P. Lovergine mit:

On Fri, Mar 09, 2018 at 12:13:55PM +0100, Hilmar Preuße wrote:


Hi Francesco,


- Bug#892371: proftpd-mod-vroot FTBFS with proftpd 1.3.6-1
- Bug#892372: proftpd-mod-msg FTBFS with proftpd 1.3.6-1
- Bug#892373: proftpd-mod-fsync FTBFS with proftpd 1.3.6-1



Hilmar, I just followed up error reports with hints for fixing. Do you 
mind to work on them?



Last patch is in, feel free to upload.

Hilmar
--
#206401 http://counter.li.org

Bug#892849: [3dprinter-general] Bug#892849: Bug#892849: cura: Exception while launching cura

[Jean-Luc]

Hi,


It was my fault.

I've installed rapid-photo-downloader (https://www.damonlynch.net/rapid/).

And the install process uses pip and crates some files in .local/lib

.local/lib/python3.5
└── site-packages
    ├── arrow
    │   ├── api.py
    │   ├── arrow.py
    │   ├── factory.py
    │   ├── formatter.py
    │   ├── __init__.py
    │   ├── locales.py
    │   ├── parser.py
[etc.]

.local/lib/python3.6
└── site-packages
    ├── arrow
    │   ├── api.py
    │   ├── arrow.py
    │   ├── factory.py
[etc.]

and there is a whole bunch of libs there.

sip.so is there also.

I've (re)moved it and then I managed to have cura running.


Regards


Jean-Luc


Le 14/03/2018 à 22:07, Gregor Riepl a écrit :

ii  libarcus3  3.1.0-1  amd64    message queue for Cura based on p
ii  python3-arcus  3.1.0-1  amd64    message queue for Cura based on p
ii  python3-sip    4.19.8+dfsg- amd64    Python 3/C++ bindings generator r

Thank you.

Unfortunately, I cannot reproduce the problem on my machine, even with these
exact versions from sid installed.
But I'm using a sid/stretch mix, not pure sid, so it may be related to that.

On the other hand, I will submit Cura 3.2.1 soon, so perhaps a new build will
help. I'll keep the bug open until then.
If it still happens with 3.2.1, we'll need to debug this further.

Bug#892710: [Pkg-tcltk-devel] Bug#892710: {tcl, tk}-i{tcl, tk}4-{dev, doc}: missing Conflicts: i{tcl, tk}-{dev, doc}

[Sergei Golovan]

Hi Andreas,

On Wed, Mar 14, 2018 at 4:58 AM, Andreas Beckmann  wrote:
>
> Hi,
>
> unfortunately i{tcl,tk}3-dev in stretch did not provide a virtual
> package, so you'll need Breaks+Replaces or Conflicts against the real
> packages. (Sorry, didn't check the -dev packages in detail, just assumed
> they worked similarily to the -doc packages.)

Sorry, I missed this too. I'll add the necessary conflicts shortly.

Cheers!
-- 
Sergei Golovan