date:20180404

Processing control commands:

> clone -1 -2 -3
Bug #894867 [src:gitlab] gitlab: GitLab Security Release: 10.6.3, 10.5.7, and 
10.4.7
Bug 894867 cloned as bugs 894868-894869
> retitle -1 gitlab: Confidential issue comments in Slack, Mattermost, and 
> webhook integrations
Bug #894867 [src:gitlab] gitlab: GitLab Security Release: 10.6.3, 10.5.7, and 
10.4.7
Changed Bug title to 'gitlab: Confidential issue comments in Slack, Mattermost, 
and webhook integrations' from 'gitlab: GitLab Security Release: 10.6.3, 
10.5.7, and 10.4.7'.
> retitle -2 gitlab: Persistent XSS in milestones data-milestone-id
Bug #894868 [src:gitlab] gitlab: GitLab Security Release: 10.6.3, 10.5.7, and 
10.4.7
Changed Bug title to 'gitlab: Persistent XSS in milestones data-milestone-id' 
from 'gitlab: GitLab Security Release: 10.6.3, 10.5.7, and 10.4.7'.
> retitle -3 gitlab: Persistent XSS in filename of merge request
Bug #894869 [src:gitlab] gitlab: GitLab Security Release: 10.6.3, 10.5.7, and 
10.4.7
Changed Bug title to 'gitlab: Persistent XSS in filename of merge request' from 
'gitlab: GitLab Security Release: 10.6.3, 10.5.7, and 10.4.7'.
> found -1 8.13.11+dfsg1-8
Bug #894867 [src:gitlab] gitlab: Confidential issue comments in Slack, 
Mattermost, and webhook integrations
Marked as found in versions gitlab/8.13.11+dfsg1-8.
> found -3 8.13.11+dfsg1-8
Bug #894869 [src:gitlab] gitlab: Persistent XSS in filename of merge request
Marked as found in versions gitlab/8.13.11+dfsg1-8.

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

Bug#894867: gitlab: GitLab Security Release: 10.6.3, 10.5.7, and 10.4.7

2018-04-04 Thread Salvatore Bonaccorso

Source: gitlab
Version: 10.6.2+dfsg-1
Severity: grave
Tags: security upstream
Justification: user security hole
Control: clone -1 -2 -3
Control: retitle -1 gitlab: Confidential issue comments in Slack, Mattermost, 
and webhook integrations
Control: retitle -2 gitlab: Persistent XSS in milestones data-milestone-id
Control: retitle -3 gitlab: Persistent XSS in filename of merge request
Control: found -1 8.13.11+dfsg1-8
Control: found -3 8.13.11+dfsg1-8


Hi

New gitlab release fixing three issues. Will fill three bugs for it
since no CVEs are assigned (yet) to clearly identify the issues
(cloning this bug report to three bugs).

See: 
https://about.gitlab.com/2018/04/04/security-release-gitlab-10-dot-6-dot-3-released/

Regards,
Salvatore

Bug#894816: [mikutter] mikutter doesn't start with error

2018-04-04 Thread dai

Control: forwarded -1 https://dev.mikutter.hachune.net/issues/1199
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: PGP signature

Processed: Re: Bug#894816: [mikutter] mikutter doesn't start with error

Processing control commands:

> forwarded -1 https://dev.mikutter.hachune.net/issues/1199
Bug #894816 [ruby-gtk2] [ruby-gtk2] mikutter doesn't start with error
Set Bug forwarded-to-address to 'https://dev.mikutter.hachune.net/issues/1199'.

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

Processed: Re: Bug#894816: [mikutter] mikutter doesn't start with error

Processing control commands:

> reassign -1 ruby-gtk2 3.2.3-1
Bug #894816 [mikutter] [mikutter] mikutter doesn't start with error
Bug reassigned from package 'mikutter' to 'ruby-gtk2'.
No longer marked as found in versions mikutter/3.6.5+dfsg-1.
Ignoring request to alter fixed versions of bug #894816 to the same values 
previously set
Bug #894816 [ruby-gtk2] [mikutter] mikutter doesn't start with error
Marked as found in versions ruby-gnome2/3.2.3-1.
> severity -1 grave
Bug #894816 [ruby-gtk2] [mikutter] mikutter doesn't start with error
Severity set to 'grave' from 'important'
> affects -1 mikutter
Bug #894816 [ruby-gtk2] [mikutter] mikutter doesn't start with error
Added indication that 894816 affects mikutter
> retitle -1 [ruby-gtk2] mikutter doesn't start with error
Bug #894816 [ruby-gtk2] [mikutter] mikutter doesn't start with error
Changed Bug title to '[ruby-gtk2] mikutter doesn't start with error' from 
'[mikutter] mikutter doesn't start with error'.

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

Bug#894338: nvidia-graphics-drivers: CVE-2018-6249, CVE-2018-6253: null pointer dereference and infinite recursion due to malformed shader

2018-04-04 Thread Luca Boccassi

On Wed, 2018-04-04 at 00:25 +0200, Andreas Beckmann wrote:
> On 2018-03-30 16:20, Luca Boccassi wrote:
> > It's due to the updated glx-alternative-foo sets the libGL.so.1
> > symlink
> > to Mesa, even when update-glx --glx nvidia is used:
> > 
> > lrwxrwxrwx 1 root root 48 Mar 30 15:02 /etc/alternatives/glx
> > --libGL.so.1-i386-linux-gnu -> /usr/lib/mesa-diverted/i386-linux-
> > gnu/libGL.so.1
> > lrwxrwxrwx 1 root root 50 Mar 30 15:02 /etc/alternatives/glx
> > --libGL.so.1-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-
> > linux-gnu/libGL.so.1
> 
> Is this with the libglvnd libgl1 from stretch-backports installed?
> Then
> this is intentional.
> If backports breaks after updating stable, let's fix backports, not
> stable,
> 
> > I guess that was done for glvnd? But this happens with the stretch-
> > backports version too, is that right?
> 
> I'm not sure what the problem is here exactly ...  and how to
> reproduce
> it in a minimal stretch chroot ...
> 
> > Changing those symlinks manually to the nvidia version fixes the
> > problem.
> 
> Pointing to what?

Gah, of course I had libglvnd from bpo. I always, always forget to
remove it when moving back and forth...

Sorry for the noise, works fine after removing those.

Do you need any help with these uploads? Would you like me to create
the tickets for the release team, or do the upload to unstable of 390?

-- 
Kind regards,
Luca Boccassi

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

Bug#886046: marked as done (soundconverter: Depends on gconf)

Your message dated Wed, 04 Apr 2018 23:51:32 +
with message-id 
and subject line Bug#886046: fixed in soundconverter 3.0.0-1
has caused the Debian Bug report #886046,
regarding soundconverter: Depends on gconf
to be marked as done.

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

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


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

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

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

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

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: soundconverter
Source-Version: 3.0.0-1

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated soundconverter 
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, 05 Apr 2018 01:27:34 +0200
Source: soundconverter
Binary: soundconverter
Architecture: source
Version: 3.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Sebastian Ramacher 
Description:
 soundconverter - GNOME application to convert audio files into other formats
Closes: 886046
Changes:
 soundconverter (3.0.0-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/changelog: Remove trailing whitespaces
 .
   [ Sebastian Ramacher ]
   * New upstream release.
 - Replace gconf with gsettings. (Closes: #886046)
   * debian/control:
 - Bump Standards-Version.
 - Drop now no longer needed dependency on gir1.2-gconf-2.0.
   * debian/: Bump debhelper compat to 11.
   * debian/copyright: Update copyright years.
   * debian/patches: Fix AppStream metadata location.
Checksums-Sha1:
 60a9c5ebc998cf656d1a658fa1b20691e9492054 2099 soundconverter_3.0.0-1.dsc
 4da218826b61d9fd9e7eb51973b664d9fbee453b 201548 
soundconverter_3.0.0.orig.tar.xz
 b5f2a3a4391d0a9060754731cbd8293e1d645e7e 6232 
soundconverter_3.0.0-1.debian.tar.xz
Checksums-Sha256:
 443803b4843e1be73d91593d09b586bb017422c187738168e9fbf630c6ff2d40 2099 
soundconverter_3.0.0-1.dsc
 ecb47732f279fc91f761601a56bada0ce8b8fe25e2e2935ca6b793e26f713df3 201548 
soundconverter_3.0.0.orig.tar.xz
 6f96b66e13e28c283a125da3c44d4f50d7ccd04b604e21094e323b6bdf5429df 6232 
soundconverter_3.0.0-1.debian.tar.xz
Files:
 667b76ca3f822a483e9088a88f61f759 2099 gnome optional soundconverter_3.0.0-1.dsc
 4bb4612c2876838c0babe12c1ef9f502 201548 gnome optional 
soundconverter_3.0.0.orig.tar.xz
 fde5f3ba886b06eb7ae650ef23b1af5e 6232 gnome optional 
soundconverter_3.0.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAlrFX6wACgkQafL8UW6n
GZNnzQ/+IX0F6EJLGnus3IfGaQkTOdI5j65AIpCBsK9Hx9Kwm4ysMcKEhvAwT4gV
mwbC9wElVICdxOMr+eXFEA7adkQ9cl2Rhzmv0MR23DKSrHA22SkllVz7lkjR72T3
TknHQeFV6p8ltST8eOaJp2ESdYx678oKXWrmiTWiFBvQZ+Jv9p8Yv7DKYPQ7e57D
OekUWH3qjKqUyQH393olCzLUkRWCb3o3l95IHb41qN0vGPEGco/k6tXriTNepx4D
wNgferaVdmMEg8cEtiu4/L9bh9Z5D9pAvwn1No/ZBcb8rQQTmhSxFtgmP+ggXd33
hSSyYp7Ln05Y12cqMnD9191n90ZhVLYmPqPuZYhE+nP09OXbpAI1Fkdk9Hw2gVTY
MQkmwzmCUlJRvZmzkEbtw4wFid8CmkAmdNkNpQBc+EkN7Xaq+w+eS47/8OdFYEIA
E5h/JPGva1t++7n5jB8ConAwKnagHWmGRzWvPPDDjk2tZRJvtDUeUVgGDMQNUUlO
wcyJhJQt61R9mihkNlvzYnp8rGX58fHNSefY80KSP//wqTH5ry0LK/mXRvd1bCIP
lxJLjh4RC43XPZcTZwDS+0Ine74o68xtFryxoAmBDiMqeRhzNVaRLfZSbycup/pF
n9ZAzr65HD9cmAsJ92wxpMTdK1JtUs0M/sq9jS0Wfa8ccb/kk/0=
=rEz3
-END PGP SIGNATURE End Message ---

Bug#894667: beep bug

2018-04-04 Thread rain1


Hello.

After analysis of the diff it in unclear what exactly the race condition 
bug is and how it would constitute a privileged escalation.


Please could somebody provide an explanation of what the race condition 
is, and how it is a security issue rather than just being a regular bug. 
so we can understand why the patch fixes it.


It seems that open/closing the console_device (set with -e) was done 
repeatedly in the -n case. It's possible that the race in question would 
be triggered if a SIGINT or SIGTERM was sent at the right time (which 
time)? possibly causing a double free. As the beep program just performs 
ioctl or writes a very simple struct to an fd it does not seem there is 
enough attacker control to actually do any sort of code execution with 
beep.


So this may not really be a security issue, just a minor improvement in 
the code. I welcome being corrected though.


(Note: we have looked at the satire website about the bug 
https://holeybeep.ninja and it does not provide any technical details of 
interest)


Cheers!

Bug#894856: appstream: Incomplete debian/copyright?

2018-04-04 Thread Chris Lamb

Source: appstream
Version: 0.12.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Matthias Klumpp 

Hi,

I just ACCEPTed appstream from NEW but noticed it was missing 
attribution in debian/copyright for at least Jan Grulich, 
Aleix Pol Gonzalez, Lucas Moura, etc.

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


Regards,

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

Bug#894699: marked as done (ros-rosinstall FTBFS with ros-wstool 0.1.17-1)

Your message dated Wed, 04 Apr 2018 21:27:30 +
with message-id 
and subject line Bug#894699: fixed in ros-rosinstall 0.7.8-2
has caused the Debian Bug report #894699,
regarding ros-rosinstall FTBFS with ros-wstool 0.1.17-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.)


-- 
894699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-rosinstall
Version: 0.7.7-6
Severity: serious

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

...
==
ERROR: test_info_only (test.local.test_rosws.RosWsTest)
--
Traceback (most recent call last):
  File "test/local/test_rosws.py", line 259, in test_info_only
self.assertEqual(0, cli.cmd_info(workspace, ['--only=localname']))
  File "rosinstall/rosws_cli.py", line 335, in cmd_info
localnames=args)
TypeError: get_info_table_raw_csv() takes exactly 4 arguments (3 given)

--
Ran 53 tests in 559.163s

FAILED (errors=1)
[ros] Fetching /tmp/tmp1OXbvj/ros (version None) to /tmp/tmp1OXbvj/ws7/ros
[ros] Done.
[gitrepo] Fetching /tmp/tmp1OXbvj/gitrepo (version None) to 
/tmp/tmp1OXbvj/ws7/gitrepo
[gitrepo] Done.
(Over-)Writing setup.sh, setup.bash, and setup.zsh in /tmp/tmp1OXbvj/ws7

rosinstall update complete.

Type 'source /tmp/tmp1OXbvj/ws7/setup.bash' to change into this environment. 
Add that source command to the bottom of your ~/.bashrc to set it up every time 
you log in.

If you are not using bash please see 
http://www.ros.org/wiki/rosinstall/NonBashShells 
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: cd 
/build/1st/ros-rosinstall-0.7.8/.pybuild/cpython2_2.7_rosinstall/build; 
python2.7 -m unittest discover -v 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:7: build] Error 25
--- End Message ---
--- Begin Message ---
Source: ros-rosinstall
Source-Version: 0.7.8-2

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

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

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated ros-rosinstall 
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: Wed, 04 Apr 2018 21:51:39 +0200
Source: ros-rosinstall
Binary: python-rosinstall python3-rosinstall
Architecture: source
Version: 0.7.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Description:
 python-rosinstall - Installer for Robot OS (Python 2)
 python3-rosinstall - Installer for Robot OS (Python 3)
Closes: 894699
Changes:
 ros-rosinstall (0.7.8-2) unstable; urgency=medium
 .
   * Add R³
   * http -> https
   * Add patch for get_info_table_raw_csv (Closes: #894699)
Checksums-Sha1:
 82a5d21b51596271aec0638a948e0b6d637a3782 2471 ros-rosinstall_0.7.8-2.dsc
 5ba2e9c2b75b556a36f61c7ae2814b9d792ae589 4460 
ros-rosinstall_0.7.8-2.debian.tar.xz
 70395485392950c704df29ea7a5427c96f06a374 7549 
ros-rosinstall_0.7.8-2_source.buildinfo
Checksums-Sha256:
 e1335af028c2abc4a12a58f91cdc246387b6b331ab84db4e64251794392c876e 2471 
ros-rosinstall_0.7.8-2.dsc
 5dbb115f2b34d7958ef2b33791d3f05f08bb8706871dcc53bcd085d2c9cfc1ac 4460 
ros-rosinstall_0.7.8-2.debian.tar.xz
 deb9997dc831137021738f98fe3712d107d39fc3afede4da514303551a76d9c9 7549 
ros-rosinstall_0.7.8-2_source.buildinfo
Files:
 b522a7dbd4e594a7225ec1437452dd4f 2471 python optional 
ros-rosinstall_0.7.8-2.dsc
 b53b9fa3074188cd6cb2a2d97d83cf5d 4460 python optional 
ros-rosinstall_0.7.8-2.debian.tar.xz
 77a43af926a3ddc08618019a145049df 7549 python optional 
ros-rosinstall_0.7.8-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAlrFLNgUHGpzcHJpY2tl

Bug#892548: dhelp: /usr/sbin/dhelp_parse broken with ruby 2.5

2018-04-04 Thread Коля Гурьев

tags 892548 - unreproducible
reassign 892548 libruby2.5
forcemerge 892099 892548
stop

It appears the bug with very similar issue was fixed in the libruby2.5
package so I merge these bugs. If your error still exists, let us know.

Processed: Re: Bug#892548: dhelp: /usr/sbin/dhelp_parse broken with ruby 2.5

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

> tags 892548 - unreproducible
Bug #892548 [dhelp] dhelp: /usr/sbin/dhelp_parse broken with ruby 2.5
Removed tag(s) unreproducible.
> reassign 892548 libruby2.5
Bug #892548 [dhelp] dhelp: /usr/sbin/dhelp_parse broken with ruby 2.5
Bug reassigned from package 'dhelp' to 'libruby2.5'.
No longer marked as found in versions dhelp/0.6.24.
Ignoring request to alter fixed versions of bug #892548 to the same values 
previously set
> forcemerge 892099 892548
Bug #892099 {Done: Antonio Terceiro } [libruby2.5] 
libruby2.5: missing dbm support
Bug #892548 [libruby2.5] dhelp: /usr/sbin/dhelp_parse broken with ruby 2.5
Severity set to 'important' from 'grave'
Marked Bug as done
Added indication that 892548 affects dhelp
Marked as fixed in versions ruby2.5/2.5.1-1.
Marked as found in versions ruby2.5/2.5.0-6.
Merged 892099 892548
> stop
Stopping processing here.

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

Bug#891434: the same on 2 Acer Aspire V13 PC's

2018-04-04 Thread Jean-Marc

On Wed, 07 Mar 2018 11:13:02 -0500 Rann Bar-On  wrote:
> Is this still the case with 2.02+dfsg1-3 or has it been fixed?

Yes, it is.

I experinced the same issue on 2 Acer Aspire V13 PC's.

Updating GRUB to 2.02+dfsg1-2 and to 2.02+dfsg1-3.

Both PC's left unbootable.

Rescued with an install image + re-installing GRUB with the option --removable.

I saved the logs if you are interested.

Regards,

Jean-Marc 


pgpP72B7xrsaE.pgp
Description: PGP signature

Processed: tagging 894829, bug 894829 is forwarded to https://github.com/puppetlabs/gettext-setup-gem/issues/64

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

> tags 894829 + confirmed upstream
Bug #894829 [src:ruby-gettext-setup] ruby-gettext-setup FTBFS: test failures
Added tag(s) confirmed and upstream.
> forwarded 894829 https://github.com/puppetlabs/gettext-setup-gem/issues/64
Bug #894829 [src:ruby-gettext-setup] ruby-gettext-setup FTBFS: test failures
Set Bug forwarded-to-address to 
'https://github.com/puppetlabs/gettext-setup-gem/issues/64'.
> thanks
Stopping processing here.

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

Bug#894840: clang: baseline cpu violation on i386

2018-04-04 Thread Sylvestre Ledru

severity 894840 normal
thanks

Hello,

On 04/04/2018 20:36, Andreas Beckmann wrote:
> Package: clang
> Version: baseline cpu violation on i386
> Severity: serious
> 
> Hi,
> 
> all clang versions (at least since wheezy) by default generate code for
> a cpu that is newer than the baseline cpu on i386. On clang-6.0 the
> default is apparently pentium4 which has sse2 (among other features),
> but that is not available on the baseline cpu, which is currently i686.
Sorry about that but this is by design and I am not planning to work on fixing 
that...

As this has been the case for a long time, it shows that it isn't a severe 
issue.

I think we (Debian) should instead have a discussion on having SSE2 as minimal 
req for intel-like cpu.
Other projects like Firefox or Chrome are making that a requirement too.

Cheers,
Sylvestre

Processed: Re: Bug#894840: clang: baseline cpu violation on i386

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

> severity 894840 normal
Bug #894840 [clang] clang: baseline cpu violation on i386
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#894763: libglib2.0-0: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy

Hi,

Michael Biebl wrote:
> >> As soon as you clean up the stray
> >> /lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1 and run ldconfig, the
> >> problem should go away?
> > 
> > No, because there's also a symlink to it which (according to the
> > timestamp) seem to have been created by maintainer scripts of this
> > package:
> > 
> > 6080 lrwxrwxrwx 1 root root 23 Apr  4 09:03 
> > /lib/arm-linux-gnueabihf/libglib-2.0.so.0 -> libglib-2.0.so.0.4200.1
> > 
> > Not sure how I should clean up that one. Can I safely delete it, too?
> 
> Running ldconfig should take care of removing the stray symlink.
> It was ldconfig which created the symlink, afaik.

Worked, thanks! (Both, emacs and gio-querymodules, work again.)

Feel free to close the bug report.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#894763: libglib2.0-0: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy

2018-04-04 Thread Michael Biebl

Am 04.04.2018 um 21:27 schrieb Axel Beckert:

>> As soon as you clean up the stray
>> /lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1 and run ldconfig, the
>> problem should go away?
> 
> No, because there's also a symlink to it which (according to the
> timestamp) seem to have been created by maintainer scripts of this
> package:
> 
> 6080 lrwxrwxrwx 1 root root 23 Apr  4 09:03 
> /lib/arm-linux-gnueabihf/libglib-2.0.so.0 -> libglib-2.0.so.0.4200.1
> 
> Not sure how I should clean up that one. Can I safely delete it, too?

Running ldconfig should take care of removing the stray symlink.
It was ldconfig which created the symlink, afaik.






signature.asc
Description: OpenPGP digital signature

Bug#894763: libglib2.0-0: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy

Hi Michael,

Michael Biebl wrote:
> Do you have an idea, where this file might have come from?

On a first thought: No. The package is no package I installed on
purpose, it came in by dependencies and I surely didn't fiddle around
with its configuration (if it has one).

On a second thought: I know that in the very beginning of that system
(i.e. during 2015) I had issues with the SD card the system runs off
and I at least replaced the SD card once, maybe twice. IIRC the
original SD card went readonly and I dd'ed its contents onto a new one
and ran fsck (offline). While that in theory could cause stray files,
IMHO especially dpkg is rather good in keeping things consistent.

So I slightly doubt that this is the cause for this issue. On the
other hand, it seems the best explanation currently available.

> So it looks like a local misconfiguration which went unnoticed so far as
> /lib/arm-linux-gnueabihf/libglib-2.0.so.0.5* took precedence over
> /lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1

I have no idea what kind of "configuration" could be involved here.

> I guess there is nothing really the libglib2.0-0 package can do about
> this. Do you agree?

If I'm the only one who happens to have this issue, I'm fine with
closing this as unreproducible.

> As soon as you clean up the stray
> /lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1 and run ldconfig, the
> problem should go away?

No, because there's also a symlink to it which (according to the
timestamp) seem to have been created by maintainer scripts of this
package:

6080 lrwxrwxrwx 1 root root 23 Apr  4 09:03 
/lib/arm-linux-gnueabihf/libglib-2.0.so.0 -> libglib-2.0.so.0.4200.1

Not sure how I should clean up that one. Can I safely delete it, too?

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#894842: RM: roboptim-core -- RoQA, unmaintained, RC-Buggy

2018-04-04 Thread Tobias Frost

Source: roboptim-core
Severity: serious

Dear Maintainer,

The package is RC-buggy since 2015 and seems to be unmaintained.
The last non-NMU upload was 2014.

Therefore the question whether it should be removed from Debian.
Popcon is almost zero.

If you think the package should remain in Debian, please fix the 
RC bugs and then close this bugs. If not, I will reassign the bug 
to ftp.debian.org in exactly 3 months from now for execution of the 
removal.

Thanks!
--
tobi

Bug#894763: libglib2.0-0: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy

2018-04-04 Thread Michael Biebl

Am 04.04.2018 um 21:06 schrieb Michael Biebl:
> Am 04.04.2018 um 20:20 schrieb Axel Beckert:
>> Hi,
>>
>> Simon McVittie wrote:
 This looks like there is a libglib-2.0.so.0 in /lib/arm-linux-gnueabihf/ 
 that shouldn't be there, and this takes precedence over the more recent
 one from the Debian package that gets installed to /usr/lib.
>>>
>>> My thoughts exactly. What's that doing there? I would have expected that
>>> removing the old libglib2.0-0 package would delete that.
>>>
>>> Please try:
>>>
>>> ls -il /lib/arm-linux-gnueabihf/libglib-2.0.so*
>>
>> 6080 lrwxrwxrwx 1 root root 23 Apr  4 09:03 
>> /lib/arm-linux-gnueabihf/libglib-2.0.so.0 -> libglib-2.0.so.0.4200.1
>> 1563 -rw-r--r-- 1 root root 814280 Nov 13  2014 
>> /lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1
> 
> Where is this file /lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1
> coming from?
> Does dpkg list it as owned by any package?

Sorry, somehow completely missed the following paragraph where you
answered that already.

Do you have an idea, where this file might have come from?

So it looks like a local misconfiguration which went unnoticed so far as
/lib/arm-linux-gnueabihf/libglib-2.0.so.0.5* took precedence over
/lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1

I guess there is nothing really the libglib2.0-0 package can do about
this. Do you agree?
As soon as you clean up the stray
/lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1 and run ldconfig, the
problem should go away?



signature.asc
Description: OpenPGP digital signature

Bug#894763: libglib2.0-0: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy

Hi,

Michael Biebl wrote:
> >> ls -il /lib/arm-linux-gnueabihf/libglib-2.0.so*
> > 
> > 6080 lrwxrwxrwx 1 root root 23 Apr  4 09:03 
> > /lib/arm-linux-gnueabihf/libglib-2.0.so.0 -> libglib-2.0.so.0.4200.1
> > 1563 -rw-r--r-- 1 root root 814280 Nov 13  2014 
> > /lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1
> 
> Where is this file /lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1
> coming from?

I don't know.

> Does dpkg list it as owned by any package?

Please read my previous mail a few lines further than you cited it.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#894763: libglib2.0-0: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy

2018-04-04 Thread Michael Biebl

Am 04.04.2018 um 20:20 schrieb Axel Beckert:
> Hi,
> 
> Simon McVittie wrote:
>>> This looks like there is a libglib-2.0.so.0 in /lib/arm-linux-gnueabihf/ 
>>> that shouldn't be there, and this takes precedence over the more recent
>>> one from the Debian package that gets installed to /usr/lib.
>>
>> My thoughts exactly. What's that doing there? I would have expected that
>> removing the old libglib2.0-0 package would delete that.
>>
>> Please try:
>>
>> ls -il /lib/arm-linux-gnueabihf/libglib-2.0.so*
> 
> 6080 lrwxrwxrwx 1 root root 23 Apr  4 09:03 
> /lib/arm-linux-gnueabihf/libglib-2.0.so.0 -> libglib-2.0.so.0.4200.1
> 1563 -rw-r--r-- 1 root root 814280 Nov 13  2014 
> /lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1

Where is this file /lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1
coming from?
Does dpkg list it as owned by any package?



signature.asc
Description: OpenPGP digital signature

Processed: limit source to debhelper, tagging 894573

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

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

> tags 894573 + pending
Bug #894573 [debhelper] savi: "make clean" fails with debhelper >= 11.1.5
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#894549: debhelper: dh_usrlocal may remove a direct subdirectory of /usr/local

2018-04-04 Thread Niels Thykier

On Wed, 04 Apr 2018 18:29:00 + Niels Thykier  wrote:
> On Mon, 2 Apr 2018 16:53:52 +0200 Nicolas Boulenguez
>  wrote:
> > Package: debhelper
> > Followup-For: Bug #894549
> > 
> > Hello.
> > 
> > This new diff should fix the same issues in dh_usrlocal.
> > The result is more readable in my opinion, hopefully preventing
> > similar errors in the future.
> > 
> > It should also be a bit more efficient: instead of sorting two huge
> > lists of paths all starting with "/usr/share/", it sorts once simple
> > names in each directory.
> > 
> > When a normal file is encountered, it displays an error instead of a
> > warning. This does not change much, as rmdir would fail with a less
> > explicit message when attempting to remove the containing directory.
> 
> Hi Nicolas,
> 
> Thanks for your finding and the patch.
> 
> While we are at the subject of making it more readable, perhaps I could
> ask you convert dh_usrlocal to use the "hashref" based autoscript?  That
> should avoid the need for the "\\\"-mess we currently have.
> 
> Also, many thanks for the other bugs you have filed recently.  I am very
> grateful that you have included patches in them. :)
> 
> Thanks,
> ~Niels
> 
> 

Just double checked this one:  I think there is a bug in your proposed
patch.  The "justdirs" is supposed to be in "opposite" order of "dirs"
("justdirs" are in "removal order" while "dirs" are in "creation order")
but as far as I can see that ordering is not preserved in the patch.

I think dh_usrlocal might be ready for some test cases to avoid future
breakage.  If you want to have a look at that, it would be appreciated
as well - otherwise, I will probably look at it when I review your
updated patch.

Thanks,
~Niels

Bug#894840: clang: baseline cpu violation on i386

Package: clang
Version: baseline cpu violation on i386
Severity: serious

Hi,

all clang versions (at least since wheezy) by default generate code for
a cpu that is newer than the baseline cpu on i386. On clang-6.0 the
default is apparently pentium4 which has sse2 (among other features),
but that is not available on the baseline cpu, which is currently i686.

>From clang on wheezy/i386 (but the result is equivalent on newer releases
and also on amd64 with -m32) - clang generates sse code for some floating
point arithmetic, while gcc generates x87 code:

$ echo 'double fma(double a, double b, double c) { return a * b + c; }' | clang 
-O2 -S -xc - -o-
.file   "-"
.text
.globl  fma
.align  16, 0x90
.type   fma,@function
fma:# @fma
# BB#0: 
subl$12, %esp
movsd   16(%esp), %xmm0
mulsd   24(%esp), %xmm0
addsd   32(%esp), %xmm0
movsd   %xmm0, (%esp)
fldl(%esp)
addl$12, %esp
ret
.Ltmp0: 
.size   fma, .Ltmp0-fma


.section".note.GNU-stack","",@progbits

$ echo 'double fma(double a, double b, double c) { return a * b + c; }' | gcc 
-O2 -S -xc - -o-
.file   ""
.text
.p2align 4,,15
.globl  fma
.type   fma, @function
fma:
.LFB0:  
.cfi_startproc
fldl12(%esp)
fmull   4(%esp)
faddl   20(%esp)
ret
.cfi_endproc
.LFE0:  
.size   fma, .-fma
.ident  "GCC: (Debian 4.7.2-5) 4.7.2"
.section.note.GNU-stack,"",@progbits


Andreas

Bug#894549: debhelper: dh_usrlocal may remove a direct subdirectory of /usr/local

2018-04-04 Thread Niels Thykier

On Mon, 2 Apr 2018 16:53:52 +0200 Nicolas Boulenguez
 wrote:
> Package: debhelper
> Followup-For: Bug #894549
> 
> Hello.
> 
> This new diff should fix the same issues in dh_usrlocal.
> The result is more readable in my opinion, hopefully preventing
> similar errors in the future.
> 
> It should also be a bit more efficient: instead of sorting two huge
> lists of paths all starting with "/usr/share/", it sorts once simple
> names in each directory.
> 
> When a normal file is encountered, it displays an error instead of a
> warning. This does not change much, as rmdir would fail with a less
> explicit message when attempting to remove the containing directory.

Hi Nicolas,

Thanks for your finding and the patch.

While we are at the subject of making it more readable, perhaps I could
ask you convert dh_usrlocal to use the "hashref" based autoscript?  That
should avoid the need for the "\\\"-mess we currently have.

Also, many thanks for the other bugs you have filed recently.  I am very
grateful that you have included patches in them. :)

Thanks,
~Niels

Processed: severity of 894549 is serious

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

> severity 894549 serious
Bug #894549 [debhelper] debhelper: dh_usrlocal may remove a direct subdirectory 
of /usr/local
Severity set to 'serious' from 'minor'
> thanks
Stopping processing here.

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

Bug#894763: libglib2.0-0: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy

Hi,

Simon McVittie wrote:
> > This looks like there is a libglib-2.0.so.0 in /lib/arm-linux-gnueabihf/ 
> > that shouldn't be there, and this takes precedence over the more recent
> > one from the Debian package that gets installed to /usr/lib.
> 
> My thoughts exactly. What's that doing there? I would have expected that
> removing the old libglib2.0-0 package would delete that.
> 
> Please try:
> 
> ls -il /lib/arm-linux-gnueabihf/libglib-2.0.so*

6080 lrwxrwxrwx 1 root root 23 Apr  4 09:03 
/lib/arm-linux-gnueabihf/libglib-2.0.so.0 -> libglib-2.0.so.0.4200.1
1563 -rw-r--r-- 1 root root 814280 Nov 13  2014 
/lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1

So while the symlink is rather new (corresponds to the time when I
upgraded the package again to answer your questions, i.e. it seems the
package upgrade time), the libglib-2.0.so.0.4200.1 is rather old on
the other hand. And dpkg doesn't seem to know that file:

$ dpkg -S /lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1
dpkg-query: no path found matching pattern 
/lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1

> ls -il /usr/lib/arm-linux-gnueabihf/libglib-2.0.so*

16493 lrwxrwxrwx 1 root root 23 Apr  1 17:59 
/usr/lib/arm-linux-gnueabihf/libglib-2.0.so.0 -> libglib-2.0.so.0.5600.0
 6859 -rw-r--r-- 1 root root 837824 Apr  1 17:59 
/usr/lib/arm-linux-gnueabihf/libglib-2.0.so.0.5600.0

> Since you were seeing these symbol lookup errors while packages are
> being configured,

JFTR: Not only then, also after the apt or aptitude run is finished,
i.e. I still see this:

$ emacs
emacs: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: 
undefined symbol: g_date_copy

> * assorted other packages are configured
>   - in your situation, we fail here and never get further

No. libglib2.0-0 never failed to upgrade or downgrade (in the past few
days). Just some elpa-* packages and it weren't enough to abort the
whole run.

Additionally, I was able to upgrade them successfully after
downgrading libglib2.0-0. Now they are upgraded and I've upgraded
libglib2.0-0 again (without any issues _during_ the upgrade as no
other affected packages were upgraded in the same run) and now Emacs
crashes again as before:

$ emacs
emacs: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: 
undefined symbol: g_date_copy

As does gio-querymodules:

$ LD_BIND_NOW=1 /usr/lib/arm-linux-gnueabihf/glib-2.0/gio-querymodules
/usr/lib/arm-linux-gnueabihf/glib-2.0/gio-querymodules: symbol lookup error: 
/usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy

> GLib maintainers following testing/unstable wouldn't have seen this
> failure mode, because we would be very likely to be upgrading from a
> version that is recent enough that it already has all the same symbols as
> the one in /lib; but it would be a problem for stretch -> buster upgrades.

JFTR: This is a Debian Sid installation which is usually dist-upgraded
at least every few days since early 2015 or so, i.e. not recently
upgraded from Stretch. There was "stretch" instead of "testing" in the
sources.list until recently, though. Noticed it when I wanted to
downgrade libglib2.0-0 to the version from testing. But fixing this
didn't make any difference as it didn't cause any previously
impossible upgrades or so to show up. And sid was always present in
the sources.list.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#894838: libroboptim-core-dev: Please change dependency from liblog4cxx10-dev to liblog4cxx-dev,

2018-04-04 Thread Tobias Frost

Package: libroboptim-core-dev
Version: 2.0-7.1
Severity: serious

Dear Maintainer,

As I plan to remove the transitional packages from log4cxx, please replace
the dependency to the new packages without the so-name embedded.

As robotim-core is anyway RC-buggy and not in testing, this bug will not delay
the upload of log4cxx, hence the bug is severity serious.

--
tobi

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

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

Versions of packages libroboptim-core-dev depends on:
pn  libboost-all-dev   
pn  libeigen3-dev  
pn  liblog4cxx10-dev   
ii  libltdl-dev2.4.6-2
pn  libroboptim-core2  
ii  pkg-config 0.29-4+b1

libroboptim-core-dev recommends no packages.

Versions of packages libroboptim-core-dev suggests:
pn  libroboptim-core-doc

Processed: limit source to debhelper, tagging 894835

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

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

> tags 894835 + pending
Bug #894835 [debhelper] dh_installxfonts: typo causes a misc:Depends on 
non-existing xfont-utils
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#877040: [Pkg-mozext-maintainers] Bug#877040: New upstream version, including transition to webext

2018-04-04 Thread Sean Whitton

Hello,

On Wed, Apr 04 2018, Michael Meskes wrote:

> As a first step I would love to see us migrate to salsa. The current git
> structure is different from what I usually use, so I have to dig into that.

README.source has some details but please feel free to ask me any
questions, since I came up with that structure (a long time ago..).

-- 
Sean Whitton

signature.asc
Description: PGP signature

Processed: severity of 894835 is serious

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

> severity 894835 serious
Bug #894835 [debhelper] dh_installxfonts: typo causes a misc:Depends on 
non-existing xfont-utils
Severity set to 'serious' from 'minor'
> thanks
Stopping processing here.

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

Processed: Re: pyzmq FTBFS: TestAsyncioAuthentication.test_null failure

Processing control commands:

> reassign -1 libzmq5 4.2.3-1
Bug #887819 [src:pyzmq] pyzmq FTBFS: TestAsyncioAuthentication.test_null failure
Bug reassigned from package 'src:pyzmq' to 'libzmq5'.
No longer marked as found in versions pyzmq/16.0.2-2.
Ignoring request to alter fixed versions of bug #887819 to the same values 
previously set
Bug #887819 [libzmq5] pyzmq FTBFS: TestAsyncioAuthentication.test_null failure
Marked as found in versions zeromq3/4.2.3-1.
> forwarded -1 https://github.com/zeromq/libzmq/pull/3018
Bug #887819 [libzmq5] pyzmq FTBFS: TestAsyncioAuthentication.test_null failure
Set Bug forwarded-to-address to 'https://github.com/zeromq/libzmq/pull/3018'.
> close -1 4.2.5-1
Bug #887819 [libzmq5] pyzmq FTBFS: TestAsyncioAuthentication.test_null failure
Marked as fixed in versions zeromq3/4.2.5-1.
Bug #887819 [libzmq5] pyzmq FTBFS: TestAsyncioAuthentication.test_null failure
Marked Bug as done

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

Bug#887819: pyzmq FTBFS: TestAsyncioAuthentication.test_null failure

2018-04-04 Thread Luca Boccassi

Control: reassign -1 libzmq5 4.2.3-1
Control: forwarded -1 https://github.com/zeromq/libzmq/pull/3018
Control: close -1 4.2.5-1

On Sat, 20 Jan 2018 09:40:31 +0200 Adrian Bunk  wrote:
> Source: pyzmq
> Version: 16.0.2-2
> Severity: serious
> Tags: buster sid
> 
> Some recent change in unstable makes pyzmq FTBFS:
> 
> https://tests.reproducible-builds.org/debian/history/pyzmq.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/py
zmq.html
> 
> ...
> === FAILURES
===
> _ TestAsyncioAuthentication.test_null
__
> 
> self = 
> 
> def test_null(self):
> """threaded auth - NULL"""
> # A default NULL connection should always succeed, and not
> # go through our authentication infrastructure at all.
> self.auth.stop()
> self.auth = None
> # use a new context, so ZAP isn't inherited
> self.context = self.Context()
> 
> server = self.socket(zmq.PUSH)
> client = self.socket(zmq.PULL)
> self.assertTrue(self.can_connect(server, client))
> 
> # By setting a domain we switch on authentication for NULL
sockets,
> # though no policies are configured yet. The client
connection
> # should still be allowed.
> server = self.socket(zmq.PUSH)
> server.zap_domain = b'global'
> client = self.socket(zmq.PULL)
> >   self.assertTrue(self.can_connect(server, client))
> E   AssertionError: False is not true
> 
> zmq/tests/test_auth.py:131: AssertionError
> - Captured stderr call --
---
> DEBUG:zmq.auth:Starting
> --- Captured stderr teardown 
---
> ERROR:asyncio:Task was destroyed but it is pending!
> task: 
wait_for=>
> === 1 failed, 221 passed, 9 skipped in 32.51 seconds
===
> E: pybuild pybuild:283: test: plugin distutils failed with: exit
code=1: cd /build/1st/pyzmq-16.0.2/.pybuild/pythonX.Y_3.6/build;
python3.6 -m pytest -v --ignore=zmq/tests/test_auth.py --
ignore=zmq/tests/test_security.py
> dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.6
--test-pytest returned exit code 13
> debian/rules:56: recipe for target 'override_dh_auto_test' failed
> make[1]: *** [override_dh_auto_test] Error 25

Hi,

This was a regression in libzmq5 4.2.3, fixed in 4.2.5 which is already
in sid/buster. Reassigning and closing for housekeeping.

https://github.com/zeromq/pyzmq/issues/1156
https://github.com/zeromq/libzmq/pull/3018

-- 
Kind regards,
Luca Boccassi

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

Bug#894832: CVE-2018-1002150

2018-04-04 Thread Moritz Muehlenhoff

Source: koji
Severity: grave
Tags: security

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

Cheers,
Moritz

Bug#894829: ruby-gettext-setup FTBFS: test failures

Source: ruby-gettext-setup
Version: 0.30-1
Severity: serious

Some recent change in unstable makes ruby-gettext-setup FTBFS:

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

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

RUBYLIB=/build/1st/ruby-gettext-setup-0.30/debian/ruby-gettext-setup/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-gettext-setup/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 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation

GettextSetup
  initialize
sets up correctly
  negotiate_locale
negotiates correctly
chooses the default locale when no match is found
chooses the language with the highest q value
ignores country variant
chooses the first value when q values are equal
  negotiate_locale!
sets the locale
  setting default_locale
allows setting the default locale
  clear
can clear the locale
  multiple locales
can aggregate locales across projects
can switch to loaded locale
  translation repository chain
chain is not nil
can translate without switching text domains
does not allow duplicate repositories
does allow multiple unique domains

GettextSetup::MetadataPot
  #metadata_path
finds the right metadata path
  #pot_string
generates a reasonable POT string
includes summary when provided
includes summary when provided
includes both summary and description when provided
  #load_metadata
loads metadata correctly
uses an empty hash if no metadata.json is found
  #generate_metadata_pot
works with everything supplied

GettextSetup::Pot
  string_changes?
should detect string addition
should detect string removal
should detect string changes
should not detect non-string changes
  generate_new_pot
fails when GettextSetup can't find a config.yaml
fatal: not a git repository (or any of the parent directories): .git
builds a POT file
fatal: not a git repository (or any of the parent directories): .git
builds a POT file with :header_only
  generate_new_po
fails when GettextSetup can't find a config.yaml
complains when no language is supplied
generates new PO file
merges PO files
  update_pot
fails when GettextSetup can't find a config.yaml
fatal: not a git repository (or any of the parent directories): .git
/usr/lib/ruby/vendor_ruby/gettext/tools/parser/ruby.rb:50:in `gsub': invalid 
byte sequence in US-ASCII (ArgumentError)
from /usr/lib/ruby/vendor_ruby/gettext/tools/parser/ruby.rb:50:in 
`on_default'
from /usr/lib/ruby/2.5.0/ripper/filter.rb:66:in `block in parse'
from /usr/lib/ruby/2.5.0/ripper/filter.rb:61:in `each'
from /usr/lib/ruby/2.5.0/ripper/filter.rb:61:in `parse'
from /usr/lib/ruby/vendor_ruby/gettext/tools/parser/ruby.rb:96:in 
`parse'
from /usr/lib/ruby/vendor_ruby/gettext/tools/parser/ruby.rb:297:in 
`parse_source'
from /usr/lib/ruby/vendor_ruby/gettext/tools/parser/ruby.rb:272:in 
`parse'
from /usr/lib/ruby/vendor_ruby/gettext/tools/parser/ruby.rb:189:in 
`parse'
from /usr/lib/ruby/vendor_ruby/gettext/tools/xgettext.rb:367:in `block 
in parse_path'
from /usr/lib/ruby/vendor_ruby/gettext/tools/xgettext.rb:360:in `each'
from /usr/lib/ruby/vendor_ruby/gettext/tools/xgettext.rb:360:in 
`parse_path'
from /usr/lib/ruby/vendor_ruby/gettext/tools/xgettext.rb:168:in `block 
in parse'
from /usr/lib/ruby/vendor_ruby/gettext/tools/xgettext.rb:166:in `each'
from /usr/lib/ruby/vendor_ruby/gettext/tools/xgettext.rb:166:in `parse'
from /usr/lib/ruby/vendor_ruby/gettext/tools/xgettext.rb:217:in 
`generate_pot'
from /usr/lib/ruby/vendor_ruby/gettext/tools/xgettext.rb:151:in `run'
from /usr/lib/ruby/vendor_ruby/gettext/tools/xgettext.rb:34:in `run'
from /usr/bin/rxgettext:24:in `'
Error parsing spec/lib/gettext-setup/gettext_setup_spec.rb
creates POT when absent (FAILED - 1)
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
/usr/lib/ruby/vendor_ruby/gettext/tools/parser/ruby.rb:50:in `gsub': invalid 
byte sequence in US-ASCII (ArgumentError)
from /usr/lib/ruby/vendor_ruby/gettext/tools/parser/ruby.rb:50:in 
`on_default'
from /usr/lib/ruby/2.5.0/ripper/filter.rb:66:in `block in parse'
from /usr/lib/ruby/2.5.0/ripper/filter.rb:61:in `each'
from

Bug#894641: marked as done (gradle FTBFS: error: BaseDirSelector is not abstract and does not override abstract method isSelected(Resource) in ResourceSelector)

Your message dated Wed, 04 Apr 2018 15:54:11 +
with message-id 
and subject line Bug#894641: fixed in gradle 3.4.1-5
has caused the Debian Bug report #894641,
regarding gradle FTBFS: error: BaseDirSelector is not abstract and does not 
override abstract method isSelected(Resource) in ResourceSelector
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.)


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

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

...
:docs:samples/build/1st/gradle-3.4.1/subprojects/core/src/main/java/org/gradle/api/internal/file/ant/BaseDirSelector.java:22:
 error: BaseDirSelector is not abstract and does not override abstract method 
isSelected(Resource) in ResourceSelector
public class BaseDirSelector implements FileSelector {
   ^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
--- End Message ---
--- Begin Message ---
Source: gradle
Source-Version: 3.4.1-5

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

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

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated gradle 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: Wed, 04 Apr 2018 17:25:28 +0200
Source: gradle
Binary: gradle libgradle-core-java libgradle-plugins-java gradle-doc
Architecture: source
Version: 3.4.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 gradle - Powerful build system for the JVM
 gradle-doc - Powerful build system for the JVM - Documentations
 libgradle-core-java - Powerful build system for the JVM - Core libraries
 libgradle-plugins-java - Powerful build system for the JVM - All plugins
Closes: 894641
Changes:
 gradle (3.4.1-5) unstable; urgency=medium
 .
   * Team upload.
   * Backported a fix to support the javac --module-source-path option
   * Fixed the build failure with Ant 1.10 (Closes: #894641)
   * Fixed a runtime error when Gradle is built with Java 9 and runs with Java 8
 (LP: #1760359)
Checksums-Sha1:
 4724d6546e705a77053813e459281f74b9ffcc2e 3465 gradle_3.4.1-5.dsc
 658c3d6074d98b1fb5a261255f7666495f6bfb74 46364 gradle_3.4.1-5.debian.tar.xz
 0819fb14ff05cff5dbf0f6fcf0cced4a3a2ce6cb 16047 gradle_3.4.1-5_source.buildinfo
Checksums-Sha256:
 787c4c4e132ebeb22b54afb5a665a43bbc6743a1d47b8381cc97f6ede9fb4eed 3465 
gradle_3.4.1-5.dsc
 1ab2a3bb8e88cc30fb6e17b67956449e9f9ae58541a0bbca9a7692f6f6e5b433 46364 
gradle_3.4.1-5.debian.tar.xz
 0c4b7438a4f310a5e0d90e694034b7e3144e7d031713730982e03dd118221534 16047 
gradle_3.4.1-5_source.buildinfo
Files:
 6bedebd188f33881921bf69e6ad12162 3465 java optional gradle_3.4.1-5.dsc
 17dfad41a656adc223ded30e2046cdbc 46364 java optional 
gradle_3.4.1-5.debian.tar.xz
 41fe6e8570e7a29dd85f1ecb9ada4034 16047 java optional 
gradle_3.4.1-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlrE8BUSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsJ6sQALfqBCOC9sJzz/SKh8iFlhhDfH+WMsYx
khB7CX4OnlD9dAVdi8rkx4/ps+x11zvuErbsAbdjWZ8cOc5ocedLdR1N7ZDtnE34
hHONi8uvM82nsgValbZF8tfrVBALN7ZLRA+wvxPd4GesYDsZ2kHpruX9ssqVT+rP
bDbPn4VdKe03xsWE2baUMFFbLs5LFsO7XWBuufaGhgbRADNCKS24KIbMv95mbJ76
3xYpB1dRK49JmAZ02UHr/ISc3XB0KMfYKogssIEaO+D/wW8NWsnOLmmR0GHj+pCi
Xn4Cy7Ry4g0ujTmIpSa6UHGwupdF0mdO3qUXZiSCKphSPT0n0ISUR4552KtF7QQH
2JW1JakxjABm9qow/Hq4wfwyNRML8kzqX5ST4uKxfWUXrdOq/wl9feKRcSIGqAMs
DsRVfZrae/3j4zkfzqq1I8dp40dWb10byRWu2KmQeqzRUHKKOhI/RAHc5EGEz2AX
/xpJ0ZxEj44xS4Yi0rdmtmdffzv80eI1Hnse1UIIHbFIRh/CilUhtwLfVczvJqxU
7kBrXGHt4hFL6KuOp3q59r/ZKaL5ez+5iBkaY4HDWOxEFKiT48zO5XaAKferGfGz

Bug#894075: marked as done (mypy: Missing dependencies)

Your message dated Wed, 04 Apr 2018 15:33:35 +
with message-id 
and subject line Bug#894075: fixed in mypy 0.580-2
has caused the Debian Bug report #894075,
regarding mypy: Missing dependencies
to be marked as done.

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

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


-- 
894075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mypy
Version: 0.570-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

presently, mypy doesn't work at all.

$ mypy
Traceback (most recent call last):
 File "/usr/bin/mypy", line 11, in 
   load_entry_point('mypy==0.570', 'console_scripts', 'mypy')()
 File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
587, in load_entry_point
   return get_distribution(dist).load_entry_point(group, name)
 File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
2800, in load_entry_point
   return ep.load()
 File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
2431, in load
   return self.resolve()
 File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
2437, in resolve
   module = __import__(self.module_name, fromlist=['__name__'], level=0)
 File "/usr/lib/python3/dist-packages/mypy/__main__.py", line 3, in 
   from mypy.main import main
 File "/usr/lib/python3/dist-packages/mypy/main.py", line 13, in 
   from mypy import build
 File "/usr/lib/python3/dist-packages/mypy/build.py", line 16, in 
   from distutils.sysconfig import get_python_lib
ModuleNotFoundError: No module named 'distutils.sysconfig'
salvo@serenity ~ $

Opening this as grave, since the program doesn't even start.

Best.



-- 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/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to it_IT.UTF-8), LANGUAGE=it (charmap=UTF-8) (ignored: LC_ALL set to 
it_IT.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mypy depends on:
ii  python3   3.6.4-1
ii  python3-mypy  0.570-1

mypy recommends no packages.

Versions of packages mypy suggests:
pn  mypy-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mypy
Source-Version: 0.580-2

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated mypy 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: Wed, 04 Apr 2018 13:41:34 +0200
Source: mypy
Binary: mypy mypy-doc python3-mypy
Architecture: source
Version: 0.580-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 mypy   - optional static typing for Python
 mypy-doc   - documentation for mypy
 python3-mypy - public modules for mypy (Python 3)
Closes: 894075
Changes:
 mypy (0.580-2) unstable; urgency=medium
 .
   * Team upload
   * Depends: python3-pkg-resources
 Closes: #894075
Checksums-Sha1:
 20cfb0851270fdcd66fc3aee54938bbd1c847e69 2226 mypy_0.580-2.dsc
 41eaf56d22a67d1b4593d7a63e1e8af598153b23 6564 mypy_0.580-2.debian.tar.xz
 97c1e90ac68a1f78874c4c4fb913a3bf833a8c30 8149 mypy_0.580-2_amd64.buildinfo
Checksums-Sha256:
 b153ed90b79f427a90b0f1e04041e5faa9acce161f723f6950ac2377d8f27fc4 2226 
mypy_0.580-2.dsc
 6d5bc06afdd7cd9ee4879d6c5e84eeefa57d320b95356b29ed5189843c2be229 6564 
mypy_0.580-2.debian.tar.xz
 afe949762c564b15ae7d422b68278504355483ec6ae05ffa031f7ca69bb95ab5 8149 
mypy_0.580-2_amd64.buildinfo
Files:
 ea40712fdc3a67f03016903d5eec062d 2226 utils optional mypy_0.580-2.dsc
 00134a5cc88cc478e29a6c8ab1def22e 6564 utils optional mypy_0.580-2.debian.tar.xz
 2db302716f9b398a936d74368ee6662e 8149 utils optional 
mypy_0.580-2_amd64.buildinfo

Processed: Pending fixes for bugs in the gradle package

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

> tag 894641 + pending
Bug #894641 [src:gradle] gradle FTBFS: error: BaseDirSelector is not abstract 
and does not override abstract method isSelected(Resource) in ResourceSelector
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#894641: Pending fixes for bugs in the gradle package

2018-04-04 Thread pkg-java-maintainers

tag 894641 + pending
thanks

Some bugs in the gradle package are closed in revision
6e9fe9e51798dccd12555b9dc6c3d302325023e9 in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/gradle.git/commit/?id=6e9fe9e

Commit message:

Fixed the build failure with Ant 1.10 (Closes: #894641)

Bug#888423: Can confirm on ARM64 too

2018-04-04 Thread Rohan Garg

Hey
We're noticing this exact same crash on ARM64 as well.

Cheers
Rohan Garg

Processed: unixodbc tags

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

> tags 422207 + pending
Bug #422207 [unixodbc-dev] unixodbc-dev: install odbc_config
Bug #852676 [unixodbc-dev] unixodbc missing odbc_config in unixodbc.install
Added tag(s) pending.
Added tag(s) pending.
> tags 675058 + pending
Bug #675058 [unixodbc] unixodbc: Multiple buffer overflow in unixODBC
Added tag(s) pending.
> tags 888968 + pending
Bug #888968 [unixodbc] Update to latest release
Added tag(s) pending.
> tags 891596 + pending
Bug #891596 [src:unixodbc] CVE-2018-7409
Added tag(s) pending.
> tags 893891 + pending
Bug #893891 [unixodbc] Please ship upstream manpages
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: duplicate and permission on serial port

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

> reopen 894770
Bug #894770 {Done: Geert Stappers } [arduino] arduino: 
serial communication/uploader not working
Bug #894769 {Done: Geert Stappers } [arduino] arduino: 
serial communication/uploader not working
Bug reopened
Ignoring request to alter fixed versions of bug #894770 to the same values 
previously set
Ignoring request to alter fixed versions of bug #894769 to the same values 
previously set
> stop
Stopping processing here.

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

Bug#880260: marked as done (datalad: FTBFS: Test failures)

Your message dated Wed, 4 Apr 2018 15:19:19 +0200
with message-id <51964151-d916-6eec-bba9-9d892f2e2...@debian.org>
and subject line Re: datalad: FTBFS: Test failures
has caused the Debian Bug report #880260,
regarding datalad: FTBFS: Test failures
to be marked as done.

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

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


-- 
880260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: datalad
Version: 0.4.1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20171030 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> out_refs.extend(RemoteReference.list_items(self.repo, remote=self.name))
>   File "/usr/lib/python2.7/dist-packages/git/util.py", line 932, in list_items
> out_list.extend(cls.iter_items(repo, *args, **kwargs))
>   File "/usr/lib/python2.7/dist-packages/git/refs/symbolic.py", line 613, in 
> _iter_items
> for sha, rela_path in cls._iter_packed_refs(repo):  # @UnusedVariable
>   File "/usr/lib/python2.7/dist-packages/git/refs/symbolic.py", line 97, in 
> _iter_packed_refs
> raise TypeError("PackingType of packed-Refs not understood: %r" % line)
> TypeError: PackingType of packed-Refs not understood: '# pack-refs with: 
> peeled fully-peeled sorted'
> 
> --
> Ran 616 tests in 165.156s
> 
> FAILED (SKIP=65, errors=90)
> E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
> /<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose -s -v datalad
> dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 
> --test-nose returned exit code 13
> debian/rules:27: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/10/30/datalad_0.4.1-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
On Mon, 30 Oct 2017 20:30:33 +0100 Lucas Nussbaum  wrote:
> Source: datalad
> Version: 0.4.1-1
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20171030 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 

the new release seems to be ok wrt failures

G.

> Relevant part (hopefully):
> > out_refs.extend(RemoteReference.list_items(self.repo, remote=self.name))
> >   File "/usr/lib/python2.7/dist-packages/git/util.py", line 932, in 
> > list_items
> > out_list.extend(cls.iter_items(repo, *args, **kwargs))
> >   File "/usr/lib/python2.7/dist-packages/git/refs/symbolic.py", line 613, 
> > in _iter_items
> > for sha, rela_path in cls._iter_packed_refs(repo):  # @UnusedVariable
> >   File "/usr/lib/python2.7/dist-packages/git/refs/symbolic.py", line 97, in 
> > _iter_packed_refs
> > raise TypeError("PackingType of packed-Refs not understood: %r" % line)
> > TypeError: PackingType of packed-Refs not understood: '# pack-refs with: 
> > peeled fully-peeled sorted'
> > 
> > --
> > Ran 616 tests in 165.156s
> > 
> > FAILED (SKIP=65, errors=90)
> > E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
> > /<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose -s -v 
> > datalad
> > dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 
> > --test-nose returned exit code 13
> > debian/rules:27: recipe for target 'override_dh_auto_test' failed
> 
> The full build log is available from:
>http://aws-logs.debian.net/2017/10/30/datalad_0.4.1-1_unstable.log
> 
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.
> 
> 



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

Processed: sane-backends: diff for NMU version 1.0.25-4.2

Processing control commands:

> tags 818544 + patch
Bug #818544 {Done: Jörg Frings-Fürst } [libsane-dev] 
libsane-dev: arch-dependent file in "Multi-Arch: same" package
Bug #874226 {Done: Jörg Frings-Fürst } [libsane-dev] 
libsane-dev is wrongly marked Multi-Arch: same
Bug #877691 {Done: Jörg Frings-Fürst } [libsane-dev] 
libsane-dev: File conflict causes multi-arch installation failure
Ignoring request to alter tags of bug #818544 to the same tags previously set
Ignoring request to alter tags of bug #874226 to the same tags previously set
Ignoring request to alter tags of bug #877691 to the same tags previously set
> tags 818544 + pending
Bug #818544 {Done: Jörg Frings-Fürst } [libsane-dev] 
libsane-dev: arch-dependent file in "Multi-Arch: same" package
Bug #874226 {Done: Jörg Frings-Fürst } [libsane-dev] 
libsane-dev is wrongly marked Multi-Arch: same
Bug #877691 {Done: Jörg Frings-Fürst } [libsane-dev] 
libsane-dev: File conflict causes multi-arch installation failure
Ignoring request to alter tags of bug #818544 to the same tags previously set
Ignoring request to alter tags of bug #874226 to the same tags previously set
Ignoring request to alter tags of bug #877691 to the same tags previously set
> tags 887032 + patch
Bug #887032 [src:sane-backends] sane-backends: FTBFS twice in a row
Ignoring request to alter tags of bug #887032 to the same tags previously set

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

Bug#887032: sane-backends: diff for NMU version 1.0.25-4.2

2018-04-04 Thread Mattia Rizzolo

Control: tags 818544 + patch
Control: tags 818544 + pending
Control: tags 887032 + patch

Dear maintainer,

I've sponsored an NMU prepered by Hugh McMaster for sane-backends
(versioned as 1.0.25-4.2) and uploaded it to DELAYED/5.
Please feel free to tell me if I should delay it longer.

Regards.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
diffstat for sane-backends-1.0.25 sane-backends-1.0.25

 changelog|   12 
 libsane-dev.doc-base |   16 
 rules|   35 ---
 3 files changed, 32 insertions(+), 31 deletions(-)

diff -Nru sane-backends-1.0.25/debian/changelog sane-backends-1.0.25/debian/changelog
--- sane-backends-1.0.25/debian/changelog	2017-05-21 10:04:48.0 +0200
+++ sane-backends-1.0.25/debian/changelog	2018-04-04 14:29:50.0 +0200
@@ -1,3 +1,15 @@
+sane-backends (1.0.25-4.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Enable successive package builds (Closes: #887032).
+  * Re-enable multi-arch installation of libsane-dev (Closes: #818544).
+- Do not install sane.ps and backend-writing.txt in libsane-dev, as they
+  are already installed in libsane-common.
+- Remove libsane-dev.doc-base, as it pointed only to sane.ps, which is
+  no longer installed in libsane-dev.
+
+ -- Hugh McMaster   Wed, 04 Apr 2018 22:29:50 +1000
+
 sane-backends (1.0.25-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru sane-backends-1.0.25/debian/libsane-dev.doc-base sane-backends-1.0.25/debian/libsane-dev.doc-base
--- sane-backends-1.0.25/debian/libsane-dev.doc-base	2017-05-21 10:04:48.0 +0200
+++ sane-backends-1.0.25/debian/libsane-dev.doc-base	1970-01-01 01:00:00.0 +0100
@@ -1,16 +0,0 @@
-Document: libsane-dev
-Title: SANE Standard
-Author: Andreas Beck and David Mosberger
-Abstract: SANE stands for "Scanner Access Now Easy" and is an application
- programming interface (API) that provides standardized access to any
- raster image scanner hardware (flatbed scanner, hand-held scanner,
- video- and still-cameras, frame-grabbers, etc.). The SANE standard is
- free and its discussion and development are open to everybody. The
- current source code is written to support several operating systems,
- including GNU/Linux, OS/2, Win32 and various Unices and is available
- under the GNU General Public License (commercial applications and
- backends are welcome, too, however).
-Section: Graphics
-
-Format: postscript
-Files: /usr/share/doc/libsane-dev/sane.ps.gz
diff -Nru sane-backends-1.0.25/debian/rules sane-backends-1.0.25/debian/rules
--- sane-backends-1.0.25/debian/rules	2017-05-21 10:04:48.0 +0200
+++ sane-backends-1.0.25/debian/rules	2018-04-01 15:45:25.0 +0200
@@ -31,8 +31,22 @@
 %:
 	dh $@ --parallel --with autotools_dev,systemd
 
+override_dh_auto_clean:
+	# Autoconf-generated files
+	$(RM) include/byteorder.h include/_stdint.h
+	# Add here commands to clean up after the build process.
+	[ ! -f Makefile ] || $(MAKE) distclean
+	$(RM) debian/libsane-common.install
+	$(RM) debian/libsane.udev
+	dh_auto_clean
+
+override_dh_autoreconf:
+	mkdir -p /tmp/sane-backends
+	cp $(CURDIR)/aclocal.m4 /tmp/sane-backends
+	cp -r $(CURDIR)/m4 /tmp/sane-backends
+	dh_autoreconf -X.m4
+
 override_dh_auto_configure:
-	autoconf
 	./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) \
 		--prefix=/usr \
 		--libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) \
@@ -56,14 +70,11 @@
 	(cd po && make sane-backends.pot)
 	$(MAKE)
 
-override_dh_auto_clean:
-	# Autoconf-generated files
-	$(RM) include/byteorder.h include/_stdint.h
-	# Add here commands to clean up after the build process.
-	[ ! -f Makefile ] || $(MAKE) distclean
-	$(RM) debian/libsane-common.install
-	$(RM) debian/libsane.udev
-	dh_auto_clean
+override_dh_auto_build:
+	dh_auto_build
+	cp -f /tmp/sane-backends/aclocal.m4 $(CURDIR)
+	cp -rf /tmp/sane-backends/m4 $(CURDIR)
+	rm -rf /tmp/sane-backends
 
 override_dh_auto_install-arch:
 	$(MAKE) install DESTDIR=$(CURDIR)/debian/tmp
@@ -90,12 +101,6 @@
 	mkdir -p $(CURDIR)/debian//sane-utils/usr/share/man/man5/
 	cp $(CURDIR)/doc/sane-umax_pp.man $(CURDIR)/debian/sane-utils/usr/share/man/man5/umax_pp.5
 
-override_dh_installdocs-arch:
-	dh_installdocs
-	# move files that belong to libsane-dev
-	mv debian/tmp/usr/share/doc/libsane/sane.ps debian/libsane-dev/usr/share/doc/libsane-dev/
-	mv debian/tmp/usr/share/doc/libsane/backend-writing.txt debian/libsane-dev/usr/share/doc/libsane-dev/
-
 override_dh_installdocs-indep:
 	dh_installdocs
 	# Platform-specific documentation


signature.asc
Description: PGP signature

Processed: sane-backends: diff for NMU version 1.0.25-4.2

Processing control commands:

> tags 818544 + patch
Bug #818544 {Done: Jörg Frings-Fürst } [libsane-dev] 
libsane-dev: arch-dependent file in "Multi-Arch: same" package
Bug #874226 {Done: Jörg Frings-Fürst } [libsane-dev] 
libsane-dev is wrongly marked Multi-Arch: same
Bug #877691 {Done: Jörg Frings-Fürst } [libsane-dev] 
libsane-dev: File conflict causes multi-arch installation failure
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
> tags 818544 + pending
Bug #818544 {Done: Jörg Frings-Fürst } [libsane-dev] 
libsane-dev: arch-dependent file in "Multi-Arch: same" package
Bug #874226 {Done: Jörg Frings-Fürst } [libsane-dev] 
libsane-dev is wrongly marked Multi-Arch: same
Bug #877691 {Done: Jörg Frings-Fürst } [libsane-dev] 
libsane-dev: File conflict causes multi-arch installation failure
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> tags 887032 + patch
Bug #887032 [src:sane-backends] sane-backends: FTBFS twice in a row
Added tag(s) patch.

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

Bug#873993: downgrading

2018-04-04 Thread Holger Levsen

control: severity -1 normal
# jdk8 is still available
thanks

-- 
cheers,
Holger


signature.asc
Description: PGP signature

Processed: downgrading

Processing control commands:

> severity -1 normal
Bug #873993 [src:munin] FTBFS with Java 9 due to -source/-target only
Severity set to 'normal' from 'serious'

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

Bug#877040: New upstream version, including transition to webext

2018-04-04 Thread Michael Meskes

On Thu, Mar 08, 2018 at 01:19:29PM -0600, david s wrote:
> I'm interested in potentially taking on maintenance of this package. I
> am new to Debian but I'd like to start contributing.

Great.

> To explore this possibility, I've created a proof-of-concept transition
> script. Please take a look at the attached script and let me know your
> thoughts and suggestions.

Excellent.

> Regarding the other part of this bug, it appears that some work has been
> done on #866997 to support webext. I plan to look into this and see if I
> can contribute to that as well.

Having done several webext packages already I should be able to help with that 
part. 

As a first step I would love to see us migrate to salsa. The current git
structure is different from what I usually use, so I have to dig into that.

Michael



-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL

Bug#893197: marked as done (jfractionlab FTBFS with openjdk-9)

Your message dated Wed, 04 Apr 2018 11:35:11 +
with message-id 
and subject line Bug#893197: fixed in jfractionlab 0.92-1
has caused the Debian Bug report #893197,
regarding jfractionlab FTBFS with openjdk-9
to be marked as done.

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

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


-- 
893197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jfractionlab
Version: 0.91-3
Severity: serious
Tags: buster sid

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

...
#compile java sources
find src/jfractionlab -name *.java -and -type f -print0 | xargs -0 
/usr/bin/javac -client -source 1.5 -target 1.5 -cp 
src:/usr/share/java/tablelayout.jar:/usr/share/java/java_uno.jar:/usr/share/java/juh.jar:/usr/share/java/jurt.jar:/usr/share/java/ridl.jar:/usr/share/java/unoloader.jar:/usr/share/java/unoil.jar
warning: [options] bootstrap class path not set in conjunction with -source 1.5
error: Source option 1.5 is no longer supported. Use 1.6 or later.
error: Target option 1.5 is no longer supported. Use 1.6 or later.
make: *** [debian/rules:21: build-stamp] Error 123
--- End Message ---
--- Begin Message ---
Source: jfractionlab
Source-Version: 0.92-1

We believe that the bug you reported is fixed in the latest version of
jfractionlab, 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.
José L. Redrejo Rodríguez  (supplier of updated 
jfractionlab 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: Wed, 04 Apr 2018 12:11:58 +0200
Source: jfractionlab
Binary: jfractionlab
Architecture: source all
Version: 0.92-1
Distribution: unstable
Urgency: medium
Maintainer: José L. Redrejo Rodríguez 
Changed-By: José L. Redrejo Rodríguez 
Description:
 jfractionlab - Educative program to practice fractions
Closes: 703516 893197
Changes:
 jfractionlab (0.92-1) unstable; urgency=medium
 .
   * New upstream version
   * debian/patches:
 - refreshed current patches
 - added fix_depecrated_java_method
   * debian/rules: fix java9 compilation (Closes: #893197)
   * debian/menu removed due to Debian Policy 9.6
   * added templates to /usr/share/jfractionlab/templates (Closes: #703516)
   * debian/control:
 - updated java dependencies
 - bumped standards version to 4.1.3.0
Checksums-Sha1:
 d791df3250ce89b9f398e8aa3cfd16874fdd416b 1833 jfractionlab_0.92-1.dsc
 6a637ab62238f10cb639f7ca10a2a6a2d62e914d 2273505 jfractionlab_0.92.orig.tar.gz
 7d72652ff7fd336e1060add4532817ca2e8a8c58 8500 jfractionlab_0.92-1.debian.tar.xz
 31d7f93c330bc158756d50d637e31ce862afb4ab 2800912 jfractionlab_0.92-1_all.deb
 44a9896e8ad33c41f9405a51eedc6a66dde985ca 10121 
jfractionlab_0.92-1_amd64.buildinfo
Checksums-Sha256:
 165d84abefbd12ea8d3ebc35dc34f31150d85f69c056ae65ba90e29e156b852f 1833 
jfractionlab_0.92-1.dsc
 b3f1c9c32f360f13c228f5eb03860a1e88d2ddc74a46d8c92a4242d474155e31 2273505 
jfractionlab_0.92.orig.tar.gz
 85eccee84237182f0e8da7b6e38ff6c8b1bf96035d0454a474696829d44bdb72 8500 
jfractionlab_0.92-1.debian.tar.xz
 91a5cee0e277401c42a34f113aad58cbb5663823a584d45c6d7c788a52a9ec74 2800912 
jfractionlab_0.92-1_all.deb
 489b9c3cd011edfdf19194c3f3ee21c567e0782e1fe7b5af8aa4a786d04e7f64 10121 
jfractionlab_0.92-1_amd64.buildinfo
Files:
 1145817f440feee649728f8daf3b003b 1833 math optional jfractionlab_0.92-1.dsc
 366ecbbecc7b3234745647343b8213a3 2273505 math optional 
jfractionlab_0.92.orig.tar.gz
 254efc4d34c03a6c8126b1e4490a1a85 8500 math optional 
jfractionlab_0.92-1.debian.tar.xz
 fb1becaf1d9013470f18ccb1de3af479 2800912 math optional 
jfractionlab_0.92-1_all.deb
 3ed739ce8f4c42b881ee4f78208e55c8 10121 math optional 
jfractionlab_0.92-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJaxLOzAAoJEF4Ir9Kh3lDpoYsP/2QisrstgKQI4kVl/dZs4hKw
morOi5W44rTbkWFuxZj+X3kPMixanQ2pEc54xMHTAHP8Yvdy6Iuq5SXezNQNGYJy
XmGOzh2tOLevVN+O2voHXXGSRLVxt45FK6QSAYadqWiI/CeoxNZIJyLEyuaSsiTo

Bug#894751: license missing

2018-04-04 Thread Andreas Tille

Hi Thorsten,

thanks for accepting in the first place.  That's extremely helpful due to
the chain of dependencies in new.

Kind regards

 Andreas.

On Tue, Apr 03, 2018 at 10:56:38PM +0200, Thorsten Alteholz wrote:
> Package: libbpp-core
> Version: 2.4.0-1
> Severity: serious
> thanks
> 
> Dear Maintainer,
> 
> as the CeCILL license is not part of /usr/share/common-licenses/, please add
> the full license text to your debian/copyright
> 
> Thanks!
>   Thorsten
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de

Bug#894797: node-foreground-child: FTBFS

2018-04-04 Thread Graham Inggs


Source: node-foreground-child
Version: 1.5.6-4
Severity: serious

Some recent change in unstable makes node-foreground-child FTBFS:

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

  ...
# Subtest: test/immortal-child.js
not ok 1 - should match pattern provided
  ---
  found:
out: ''
err: ''
code: null
signal: SIGINT
  pattern:
out: >-
  /^(child alive\n)*child SIGINT received\n(child 
alive\n)*child exit null

  SIGTERM\n$/
err: /^parent \d+\nchild \d+\n$/
code: null
signal: SIGTERM
  at:
line: 37
column: 7
file: test/immortal-child.js
type: ChildProcess
  stack: |
ChildProcess. (test/immortal-child.js:37:7)
  source: |
t.match(actual, expect)
  ...
1..1
# failed 1 test
# time=224.905ms

Bug#893948: marked as done (python-zeep FTBFS: TornadoAsyncTransportTest.test_load failure)

Your message dated Wed, 04 Apr 2018 10:53:41 +
with message-id 
and subject line Bug#893948: fixed in python-zeep 2.5.0-1
has caused the Debian Bug report #893948,
regarding python-zeep FTBFS: TornadoAsyncTransportTest.test_load 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.)


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

Some recent change in unstable makes python-zeep FTBFS:

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

...

=== FAILURES ===
_ TornadoAsyncTransportTest.test_load __

self = 
mock_httpclient_fetch = 

@pytest.mark.requests
@patch('tornado.httpclient.HTTPClient.fetch')
@gen_test
def test_load(self, mock_httpclient_fetch):
cache = stub(get=lambda url: None, add=lambda url, content: None)
response = 
HTTPResponse(HTTPRequest('http://tests.python-zeep.org/test.xml'), 200)
response.buffer = True
response._body = 'x'
mock_httpclient_fetch.return_value = response

transport = TornadoAsyncTransport(cache=cache)

>   result = transport.load('http://tests.python-zeep.org/test.xml')

tests/test_tornado_transport.py:30: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
zeep/transports.py:110: in load
content = self._load_remote_data(url)
zeep/tornado/transport.py:38: in _load_remote_data
client = httpclient.HTTPClient()
/usr/lib/python3/dist-packages/tornado/httpclient.py:81: in __init__
gen.coroutine(lambda: async_client_class(**kwargs)))
/usr/lib/python3/dist-packages/tornado/ioloop.py:577: in run_sync
self.start()
/usr/lib/python3/dist-packages/tornado/platform/asyncio.py:112: in start
self.asyncio_loop.run_forever()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = <_UnixSelectorEventLoop running=False closed=False debug=False>

def run_forever(self):
"""Run until stop() is called."""
self._check_closed()
if self.is_running():
raise RuntimeError('This event loop is already running')
if events._get_running_loop() is not None:
raise RuntimeError(
>   'Cannot run the event loop while another loop is running')
E   RuntimeError: Cannot run the event loop while another loop is 
running

/usr/lib/python3.6/asyncio/base_events.py:412: RuntimeError
-- Captured log call ---
selector_events.py  65 DEBUGUsing selector: EpollSelector
selector_events.py  65 DEBUGUsing selector: EpollSelector
selector_events.py  65 DEBUGUsing selector: EpollSelector
 1 failed, 410 passed in 57.41 seconds =
Exception ignored in: >
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/tornado/httpclient.py", line 85, in 
__del__
self.close()
  File "/usr/lib/python3/dist-packages/tornado/httpclient.py", line 89, in close
if not self._closed:
AttributeError: 'HTTPClient' object has no attribute '_closed'
E: pybuild pybuild:330: test: plugin distutils failed with: exit code=1: cd 
/build/1st/python-zeep-2.4.0/.pybuild/cpython3_3.6_zeep/build; python3.6 -m 
pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.6 returned 
exit code 13
make: *** [debian/rules:6: build] Error 25
--- End Message ---
--- Begin Message ---
Source: python-zeep
Source-Version: 2.5.0-1

We believe that the bug you reported is fixed in the latest version of
python-zeep, 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.
Mathias Behrle  (supplier of updated python-zeep 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

Bug#893421: swi-prolog FTBFS with openjdk-9

2018-04-04 Thread Benjamin Lorenz

The configure script of the swi-prolog jpl package only checks whether
lib/$arch/server or jre/lib/$arch/server exists but the $arch
subdirectory was removed in openjdk9. Because of the failed check the
LDFLAGS are missing the correct directories for libjava.so and related
libraries.
I have created a pull request to for this:
https://github.com/SWI-Prolog/packages-jpl/pull/8

I have tried this on i386 and the package now compiles but make check
then fails with the same errors as in #887155.

Regards,
Benjamin Lorenz

Bug#894795: kde-full currently uninstallable

2018-04-04 Thread Michael Karcher

Package: kde-full
Version: 5:100
Severity: serious

Dear Maintainer,

kde-full from meta-kde 5:100 depends on kdepim 4:17.12.xxx, but
meta-kde provides the packages kdepim in Version 4:17.08.xxx.
Two untested fixes (choose one!) have been provided at
  https://salsa.debian.org/qt-kde-team/kde/meta-kde/merge_requests/4
and
  https://salsa.debian.org/qt-kde-team/kde/meta-kde/merge_requests/3

I ran reportbug on a system with kdepim 5:99 installed (as 5:100 is
uninstallable), so the dependency list below does contain a kdepim
version that is in conflict with kde-full 5:100.

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

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

Versions of packages kde-full depends on:
ii  kde-plasma-desktop   5:100
ii  kde-standard 5:100
ii  kdeadmin 4:17.08.3+5.100
ii  kdeedu   4:17.08.3+5.100
ii  kdegames 4:17.08.3+5.100
ii  kdegraphics  4:17.08.3+5.100
ii  kdemultimedia4:17.08.3+5.100
ii  kdenetwork   4:17.08.3+5.100
ii  kdepim   4:17.08.3+5.100
ii  kdeutils 4:17.08.3+5.100
ii  plasma-workspace-wallpapers  4:5.12.1-1

Versions of packages kde-full recommends:
pn  kdeaccessibility  
pn  kdesdk
pn  kdetoys   
pn  kdewebdev 

Versions of packages kde-full suggests:
pn  calligra  
ii  xorg  1:7.7+19

-- no debconf information

Bug#894791: sbt-launcher-interface: FTBFS with openjdk-9

Package: sbt-launcher-interface
Version: 1.0.0-1
Severity: serious
Justification: fails to build from source

Hi,

sbt-launcher-interface FTBFS with openjdk-9 as the default jdk:

   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/sbt-launcher-interface-1.0.0'
git init
Initialized empty Git repository in /build/sbt-launcher-interface-1.0.0/.git/
mkdir -p /build/sbt-launcher-interface-1.0.0/debian/sbt_home/.ivy2/cache
cp -fr /build/sbt-launcher-interface-1.0.0/bootstrapdeps/* 
/build/sbt-launcher-interface-1.0.0/debian/sbt_home/.ivy2/cache/
mkdir /build/sbt-launcher-interface-1.0.0/debian/sbt_home/.sbt
echo "[repositories]" > 
/build/sbt-launcher-interface-1.0.0/debian/sbt_home/.sbt/repositories
echo "local" >> 
/build/sbt-launcher-interface-1.0.0/debian/sbt_home/.sbt/repositories
cp -frv /build/sbt-launcher-interface-1.0.0/bootstrapdeps-sources/. 
/build/sbt-launcher-interface-1.0.0/debian/sbt_home/.ivy2/cache/
'/build/sbt-launcher-interface-1.0.0/bootstrapdeps-sources/./org.scala-sbt/compiler-interface/srcs'
 -> 
'/build/sbt-launcher-interface-1.0.0/debian/sbt_home/.ivy2/cache/./org.scala-sbt/compiler-interface/srcs'
'/build/sbt-launcher-interface-1.0.0/bootstrapdeps-sources/./org.scala-sbt/compiler-interface/srcs/compiler-interface-0.13.12-sources.jar'
 -> '/build/sbt-launcher-interface-1.0.0/debian/sbt_home/.ivy2/cache/./org.
scala-sbt/compiler-interface/srcs/compiler-interface-0.13.12-sources.jar'
/build/sbt-launcher-interface-1.0.0/bootstrapsbt/bin/sbt -verbose -debug 
-sbt-dir /build/sbt-launcher-interface-1.0.0/debian/sbt_home/.sbt -ivy 
/build/sbt-launcher-interface-1.0.0/debian/sbt_home/.ivy2 "set offlin
e := true" -Dsbt.override.build.repos=true packageBin make-pom
[residual] arg = '-sbt-dir'
[residual] arg = '/build/sbt-launcher-interface-1.0.0/debian/sbt_home/.sbt'
[addJava] arg = 
'-Dsbt.ivy.home=/build/sbt-launcher-interface-1.0.0/debian/sbt_home/.ivy2'
[residual] arg = 'set offline := true'
[addJava] arg = '-Dsbt.override.build.repos=true'
[residual] arg = 'packageBin'
[residual] arg = 'make-pom'
[addJava] arg = 
'-Dsbt.global.base=/build/sbt-launcher-interface-1.0.0/debian/sbt_home/.sbt'
[residual] arg = 'set offline := true'
[residual] arg = 'packageBin'
[residual] arg = 'make-pom'
[process_args] java_version = '9.0.4'
# Executing command line:
java
-Xms1024m
-Xmx1024m
-XX:ReservedCodeCacheSize=128m
-XX:MaxMetaspaceSize=256m
-Dsbt.ivy.home=/build/sbt-launcher-interface-1.0.0/debian/sbt_home/.ivy2
-Dsbt.override.build.repos=true
-Dsbt.global.base=/build/sbt-launcher-interface-1.0.0/debian/sbt_home/.sbt
-jar
/build/sbt-launcher-interface-1.0.0/bootstrapsbt/bin/sbt-launch.jar
"set offline := true"
packageBin
make-pom

Getting org.scala-sbt sbt 0.13.12 ...
:: retrieving :: org.scala-sbt#boot-app
confs: [default]
49 artifacts copied, 0 already retrieved (17462kB/136ms)
Getting Scala 2.10.6 (for sbt)...
:: retrieving :: org.scala-sbt#boot-scala
confs: [default]
5 artifacts copied, 0 already retrieved (24494kB/35ms)
error: error while loading package, Missing dependency 'object java.lang.Object 
in compiler mirror', required by 
/build/sbt-launcher-interface-1.0.0/debian/sbt_home/.sbt/boot/scala-2.10.6/lib/scala-library.jar(scala/package.class)
error: error while loading package, Missing dependency 'object java.lang.Object 
in compiler mirror', required by 
/build/sbt-launcher-interface-1.0.0/debian/sbt_home/.sbt/boot/scala-2.10.6/lib/scala-library.jar(scala/runtime/package.class)
scala.reflect.internal.MissingRequirementError: object java.lang.Object in 
compiler mirror not found.
at 
scala.reflect.internal.MissingRequirementError$.signal(MissingRequirementError.scala:16)
at 
scala.reflect.internal.MissingRequirementError$.notFound(MissingRequirementError.scala:17)
at 
scala.reflect.internal.Mirrors$RootsBase.getModuleOrClass(Mirrors.scala:48)
at 
scala.reflect.internal.Mirrors$RootsBase.getModuleOrClass(Mirrors.scala:40)
at 
scala.reflect.internal.Mirrors$RootsBase.getModuleOrClass(Mirrors.scala:40)
at 
scala.reflect.internal.Mirrors$RootsBase.getModuleOrClass(Mirrors.scala:61)
at 
scala.reflect.internal.Mirrors$RootsBase.getClassByName(Mirrors.scala:99)
at 
scala.reflect.internal.Mirrors$RootsBase.getRequiredClass(Mirrors.scala:102)
at 
scala.reflect.internal.Definitions$DefinitionsClass.ObjectClass$lzycompute(Definitions.scala:264)
at 
scala.reflect.internal.Definitions$DefinitionsClass.ObjectClass(Definitions.scala:264)
at 
scala.reflect.internal.Definitions$DefinitionsClass.AnyRefClass$lzycompute(Definitions.scala:263)
at 
scala.reflect.internal.Definitions$DefinitionsClass.AnyRefClass(Definitions.scala:263)
at 
scala.reflect.internal.Definitions$DefinitionsClass.specialPolyClass(Definitions.scala:1120)
at 
scala.reflect.internal.Definitions$DefinitionsClass.RepeatedParamClass$lzycompute(Definitions.scala:407)
at

Processed: Re: Processed: Re: Bug#873993: fixed in munin 2.0.37-1

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

> notfound 873993 2.999.6-6
Bug #873993 [src:munin] FTBFS with Java 9 due to -source/-target only
Ignoring request to alter found versions of bug #873993 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#894789: tightvnc-java: FTBFS with openjdk-9

Source: tightvnc-java
Version: 1.2.7-9
Severity: serious
Tags: sid buster
Justification: fails to build from source

Hi,

tightvnc-java FTBFS with openjdk-9 as the default jdk:

 debian/rules build
dh build
   dh_update_autotools_config
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/tightvnc-java-1.2.7'
# Add here commands to compile the package.
/usr/bin/make
make[2]: Entering directory '/build/tightvnc-java-1.2.7'
javac -target 1.1 -source 1.3 -O VncViewer.java RfbProto.java AuthPanel.java 
VncCanvas.java OptionsFrame.java ClipboardFrame.java ButtonPanel.java 
DesCipher.java RecordingFrame.java SessionRecorder.java SocketFactory.java 
HTTPConnectSocketFactory.java HTTPConnectSocket.java ReloginPanel.java
warning: [options] bootstrap class path not set in conjunction with -source 1.3
error: Source option 1.3 is no longer supported. Use 1.6 or later.
error: Target option 1.1 is no longer supported. Use 1.6 or later.
Makefile:30: recipe for target 'VncViewer.class' failed
make[2]: *** [VncViewer.class] Error 2
make[2]: Leaving directory '/build/tightvnc-java-1.2.7'
debian/rules:16: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/build/tightvnc-java-1.2.7'
debian/rules:13: recipe for target 'build' failed
make: *** [build] Error 2


Andreas


tightvnc-java_1.2.7-9.log.gz
Description: application/gzip

Bug#894788: vnc-java: FTBFS with openjdk-9

Source: vnc-java
Version: 3.3.3r2-9
Severity: serious
Tags: sid buster
Justification: fails to build from source

Hi,

vnc-java FTBFS with openjdk-9 as the default jdk:

 debian/rules build
dh build
   dh_update_autotools_config
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/vnc-java-3.3.3r2'
# Add here commands to compile the package.
/usr/bin/make
make[2]: Entering directory '/build/vnc-java-3.3.3r2'
javac -source 1.3 -target 1.1 -O vncviewer.java rfbProto.java 
authenticationPanel.java vncCanvas.java optionsFrame.java clipboardFrame.java 
animatedMemoryImageSource.java DesCipher.java
warning: [options] bootstrap class path not set in conjunction with -source 1.3
error: Source option 1.3 is no longer supported. Use 1.6 or later.
error: Target option 1.1 is no longer supported. Use 1.6 or later.
makefile:25: recipe for target 'vncviewer.class' failed
make[2]: *** [vncviewer.class] Error 2
make[2]: Leaving directory '/build/vnc-java-3.3.3r2'
debian/rules:7: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/build/vnc-java-3.3.3r2'
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2


Andreas


vnc-java_3.3.3r2-9.log.gz
Description: application/gzip

Processed: Re: Bug#873993: fixed in munin 2.0.37-1

Processing control commands:

> reopen -1
Bug #873993 {Done: Holger Levsen } [src:munin] FTBFS with 
Java 9 due to -source/-target only
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions munin/2.0.37-1 and 2.999.6-6.

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

Bug#873993: fixed in munin 2.0.37-1

2018-04-04 Thread Holger Levsen

control: reopen -1
thanks

Hi Emmanuel,

On Wed, Apr 04, 2018 at 11:55:05AM +0200, Emmanuel Bourg wrote:
> >* Build-Depends-Indep: switch from default-jdk to openjdk-8-jdk as munin
> >  fails to build with java 9. Closes: #873993
> Unfortunately reverting to openjdk-8 isn't really the solution expected
> to move forward with the transition to openjdk-{9,10,11}.

agreed.

> Did you
> consider changing the JFLAGS variable as suggested by Markus?

very briefly, but then I didnt see anything about java 9 on
https://wiki.debian.org/Java and #873993 was severity normal, so I figured
this solution would be ok for the immediate future also because I really
wanted to get munin 2.0.37 into sid.

So, yeah, agreed, I've reopened this bug and would appreciate if you (java
folks) could update https://wiki.debian.org/Java for openjdk-{9,10,11}
eventually.

Thanks.

-- 
cheers,
Holger

signature.asc
Description: PGP signature

Bug#873993: fixed in munin 2.0.37-1

2018-04-04 Thread Emmanuel Bourg

Hi Holger,

On Thu, 29 Mar 2018 15:50:44 + Holger Levsen wrote:

>* Build-Depends-Indep: switch from default-jdk to openjdk-8-jdk as munin
>  fails to build with java 9. Closes: #873993

Unfortunately reverting to openjdk-8 isn't really the solution expected
to move forward with the transition to openjdk-{9,10,11}. Did you
consider changing the JFLAGS variable as suggested by Markus?

Emmanuel Bourg

Bug#894770: closed by Geert Stappers <stapp...@stappers.nl> (duplicate and permission on serial port)

2018-04-04 Thread kie

Hi Geert,

thanks for your prompt reply,
the user is already a member of the dialout group.

$ groups kie
  kie : kie dialout cdrom floppy sudo audio dip video plugdev netdev
 
The same problem occurs if I try running the program as root.

best rgds
Kie


On Wed, Apr 04, 2018 at 07:54:07AM +,
Debian Bug Tracking System (ow...@bugs.debian.org) wrote...

> This is an automatic notification regarding your Bug report
> which was filed against the arduino package:
> 
> #894770: arduino: serial communication/uploader not working
> 
> It has been closed by Geert Stappers .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Geert Stappers 
>  by
> replying to this email.
> 
> 
> -- 
> 894769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894769
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> Date: Wed, 4 Apr 2018 09:50:34 +0200
> From: Geert Stappers 
> To: 894769-d...@bugs.debian.org, 894...@bugs.debian.org
> Cc: 894770-submit...@bugs.debian.org
> Subject: duplicate and permission on serial port
> Message-ID: <20180404075034.gk26...@gpm.stappers.nl>
> User-Agent: Mutt/1.5.21 (2010-09-15)
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894769 and
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894770 are duplicates
> 
> Closing the oldest one in case of minor difference I didn't spot.
> 
> 
> My first guess on "the serial connection selection is greyed out"
> is permission on the serial port.  Advise: check it.
> Possible solution: please the user running arduino in the group
> that may read and write the serial port such as dailout.

> Date: Wed, 4 Apr 2018 05:17:35 +0100
> From: kie 
> To: Debian Bug Tracking System 
> Subject: arduino: serial communication/uploader not working
> Message-ID: <20180404041735.gb8...@onza.mythic-beasts.com>
> User-Agent: Mutt/1.5.23 (2014-03-12)
> 
> Package: arduino
> Version: 2:1.0.5+dfsg2-4.1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> normal use of arduino program
> however at the moment the serial connection selection is greyed out
> 
> connect to arduino via serial port not working, cannot upload code to arduino
> 
> get the following error
> java.lang.NullPointerException thrown while loading gnu.io.RXTXCommDriver
> 
> this is the same on two different machines running buster
> where serial upload was previously working without a problem
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.15.0-2-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
> LANGUAGE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages arduino depends on:
> ii  arduino-core   2:1.0.5+dfsg2-4.1
> ii  default-jre [java6-runtime]2:1.9-62
> ii  libjna-java4.5.1-1
> ii  librxtx-java   2.2pre2+dfsg1-1
> ii  openjdk-8-jre [java6-runtime]  8u162-b12-1
> ii  openjdk-9-jre [java6-runtime]  9.0.4+12-3
> 
> Versions of packages arduino recommends:
> ii  extra-xdg-menus  1.0-4
> ii  policykit-1  0.105-20
> 
> arduino suggests no packages.
> 
> -- no debconf information
> 
> 
> - End forwarded message -

Bug#894714: marked as done (python-dugong: please drop catchlog dependency)

Your message dated Wed, 04 Apr 2018 09:27:25 +
with message-id 
and subject line Bug#894714: fixed in python-dugong 3.7.2+dfsg-2
has caused the Debian Bug report #894714,
regarding python-dugong: please drop catchlog dependency
to be marked as done.

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

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


-- 
894714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-dugong
Version: 3.7.2+dfsg-1
Severity: serious
tags -1 patch


Hello, the effort to remove catchlog is ongoing,
catchlog now is broken, because of its merge into the main pytest package.

Please update the dependencies to reflect this status,
fixing the testsuite failures and removing the old cruft from the archive.

An example of patch is here:

diff -Nru python-dugong-3.7.2+dfsg/debian/changelog 
python-dugong-3.7.2+dfsg/debian/changelog
--- python-dugong-3.7.2+dfsg/debian/changelog   2018-02-11 16:09:49.0 
+
+++ python-dugong-3.7.2+dfsg/debian/changelog   2018-04-03 10:35:29.0 
+
@@ -1,3 +1,9 @@
+python-dugong (3.7.2+dfsg-1.1) unstable; urgency=medium
+
+  * Drop catchlog dependency, now merged into pytest (Closes: #-1)
+
+ -- Gianfranco Costamagna   Tue, 03 Apr 2018 
12:35:29 +0200
+
 python-dugong (3.7.2+dfsg-1) unstable; urgency=medium
 
   * python-dugong-doc is now Multi-Arch: foreign.
diff -Nru python-dugong-3.7.2+dfsg/debian/control 
python-dugong-3.7.2+dfsg/debian/control
--- python-dugong-3.7.2+dfsg/debian/control 2018-02-11 16:09:49.0 
+
+++ python-dugong-3.7.2+dfsg/debian/control 2018-04-03 10:35:16.0 
+
@@ -7,8 +7,7 @@
 Build-Depends: debhelper (>= 9),
python3-all,
python3-sphinx (>= 1.0.7+dfsg),
-   python3-pytest (>= 2.8.0),
-   python3-pytest-catchlog,
+   python3-pytest (>= 3.3.0),
dh-python,
python3-setuptools
 Standards-Version: 4.1.1
diff -Nru python-dugong-3.7.2+dfsg/debian/tests/control 
python-dugong-3.7.2+dfsg/debian/tests/control
--- python-dugong-3.7.2+dfsg/debian/tests/control   2018-02-11 
16:09:49.0 +
+++ python-dugong-3.7.2+dfsg/debian/tests/control   2018-04-03 
10:35:25.0 +
@@ -1,2 +1,2 @@
 Tests: upstream-standard
-Depends: python3-pytest, python3-dugong, python3-pytest-catchlog
+Depends: python3-pytest, python3-dugong


thanks!

Gianfranco





signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-dugong
Source-Version: 3.7.2+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Nikolaus Rath  (supplier of updated python-dugong 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: Wed, 04 Apr 2018 09:53:12 +0100
Source: python-dugong
Binary: python3-dugong python-dugong-doc
Architecture: source
Version: 3.7.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Nikolaus Rath 
Changed-By: Nikolaus Rath 
Description:
 python-dugong-doc - HTTP 1.1 client module for Python (documentation)
 python3-dugong - HTTP 1.1 client module for Python
Closes: 894714
Changes:
 python-dugong (3.7.2+dfsg-2) unstable; urgency=medium
 .
   * Drop pytest-catchlog dependency in favor of pytest >= 3.3. Closes:
 #894714.
Checksums-Sha1:
 dcba603fb047b5a04b4fd8218131ccd3ecbeb9a7 2611 python-dugong_3.7.2+dfsg-2.dsc
 b9640e60fe6ef0230f50b300dd4631821fa83530 133796 
python-dugong_3.7.2+dfsg-2.debian.tar.xz
Checksums-Sha256:
 04c342894e2cd19138049da98945728cf6a6fb68895f8b425960ab102c67d3b0 2611 
python-dugong_3.7.2+dfsg-2.dsc
 eb08d19dc5c7ca02e3a5d7809bb531f869473e47c82608d0496d2dfbceb28008 133796 
python-dugong_3.7.2+dfsg-2.debian.tar.xz
Files:
 2a526f715beaf63d3db883a53ab216f0 2611 python optional 
python-dugong_3.7.2+dfsg-2.dsc
 e6907f364203ac073b908e361c98ce1c 133796 python

Bug#894714: marked as done (python-dugong: please drop catchlog dependency)

Your message dated Wed, 04 Apr 2018 09:27:30 +
with message-id 
and subject line Bug#894714: fixed in python-dugong 3.7.2+dfsg-3
has caused the Debian Bug report #894714,
regarding python-dugong: please drop catchlog dependency
to be marked as done.

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

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


-- 
894714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-dugong
Version: 3.7.2+dfsg-1
Severity: serious
tags -1 patch


Hello, the effort to remove catchlog is ongoing,
catchlog now is broken, because of its merge into the main pytest package.

Please update the dependencies to reflect this status,
fixing the testsuite failures and removing the old cruft from the archive.

An example of patch is here:

diff -Nru python-dugong-3.7.2+dfsg/debian/changelog 
python-dugong-3.7.2+dfsg/debian/changelog
--- python-dugong-3.7.2+dfsg/debian/changelog   2018-02-11 16:09:49.0 
+
+++ python-dugong-3.7.2+dfsg/debian/changelog   2018-04-03 10:35:29.0 
+
@@ -1,3 +1,9 @@
+python-dugong (3.7.2+dfsg-1.1) unstable; urgency=medium
+
+  * Drop catchlog dependency, now merged into pytest (Closes: #-1)
+
+ -- Gianfranco Costamagna   Tue, 03 Apr 2018 
12:35:29 +0200
+
 python-dugong (3.7.2+dfsg-1) unstable; urgency=medium
 
   * python-dugong-doc is now Multi-Arch: foreign.
diff -Nru python-dugong-3.7.2+dfsg/debian/control 
python-dugong-3.7.2+dfsg/debian/control
--- python-dugong-3.7.2+dfsg/debian/control 2018-02-11 16:09:49.0 
+
+++ python-dugong-3.7.2+dfsg/debian/control 2018-04-03 10:35:16.0 
+
@@ -7,8 +7,7 @@
 Build-Depends: debhelper (>= 9),
python3-all,
python3-sphinx (>= 1.0.7+dfsg),
-   python3-pytest (>= 2.8.0),
-   python3-pytest-catchlog,
+   python3-pytest (>= 3.3.0),
dh-python,
python3-setuptools
 Standards-Version: 4.1.1
diff -Nru python-dugong-3.7.2+dfsg/debian/tests/control 
python-dugong-3.7.2+dfsg/debian/tests/control
--- python-dugong-3.7.2+dfsg/debian/tests/control   2018-02-11 
16:09:49.0 +
+++ python-dugong-3.7.2+dfsg/debian/tests/control   2018-04-03 
10:35:25.0 +
@@ -1,2 +1,2 @@
 Tests: upstream-standard
-Depends: python3-pytest, python3-dugong, python3-pytest-catchlog
+Depends: python3-pytest, python3-dugong


thanks!

Gianfranco





signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-dugong
Source-Version: 3.7.2+dfsg-3

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

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

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

Debian distribution maintenance software
pp.
Nikolaus Rath  (supplier of updated python-dugong 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: Wed, 04 Apr 2018 10:05:59 +0100
Source: python-dugong
Binary: python3-dugong python-dugong-doc
Architecture: source
Version: 3.7.2+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Nikolaus Rath 
Changed-By: Nikolaus Rath 
Description:
 python-dugong-doc - HTTP 1.1 client module for Python (documentation)
 python3-dugong - HTTP 1.1 client module for Python
Closes: 894714
Changes:
 python-dugong (3.7.2+dfsg-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
 .
 python-dugong (3.7.2+dfsg-2) unstable; urgency=medium
 .
   * Drop pytest-catchlog dependency in favor of pytest >= 3.3. Closes:
 #894714.
Checksums-Sha1:
 9b7ebee79cd6abf63b7d572d37aacfeb051522be 2586 python-dugong_3.7.2+dfsg-3.dsc
 c2f8ed27b5c54c63c0c7036dbef874a8e265d5bb 133860 
python-dugong_3.7.2+dfsg-3.debian.tar.xz
Checksums-Sha256:
 41b8d1a1d27d174be640b07ab2d14a4a990c7294f7f70b9a0c916f97da1f28c8 2586 
python-dugong_3.7.2+dfsg-3.dsc
 11da4d67193dd946d3fb7fe70e9ddd706eca37acd13b9bfa7fc3eebb526e596d 133860

Bug#894717: marked as done (s3ql: please drop catchlog dependency)

Your message dated Wed, 04 Apr 2018 09:28:25 +
with message-id 
and subject line Bug#894717: fixed in s3ql 2.26+dfsg-2
has caused the Debian Bug report #894717,
regarding s3ql: please drop catchlog dependency
to be marked as done.

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

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


-- 
894717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: s3ql
Version: 2.26+dfsg-1
Severity: serious
Tags: patch

Hello, the effort to remove catchlog is ongoing,
catchlog now is broken, because of its merge into the main pytest package.

Please update the dependencies to reflect this status,
fixing the testsuite failures and removing the old cruft from the archive.

An example of patch is here:

diff -Nru s3ql-2.26+dfsg/debian/changelog s3ql-2.26+dfsg/debian/changelog
--- s3ql-2.26+dfsg/debian/changelog 2018-03-04 11:39:35.0 +
+++ s3ql-2.26+dfsg/debian/changelog 2018-04-03 10:18:08.0 +
@@ -1,3 +1,9 @@
+s3ql (2.26+dfsg-1ubuntu1) bionic; urgency=medium
+
+  * Drop catchlog dependency, now integrated into pytest
+
+ -- Gianfranco Costamagna   Tue, 03 Apr 2018 
12:18:08 +0200
+
 s3ql (2.26+dfsg-1) unstable; urgency=medium
 
   * Added Depends: procps. Closes: #887375.
diff -Nru s3ql-2.26+dfsg/debian/control s3ql-2.26+dfsg/debian/control
--- s3ql-2.26+dfsg/debian/control   2018-03-04 11:39:25.0 +
+++ s3ql-2.26+dfsg/debian/control   2018-04-03 10:17:44.0 +
@@ -16,8 +16,7 @@
python3-crypto,
python3-requests,
python3-dugong (>= 3.4),
-   python3-pytest (>= 2.8.0),
-   python3-pytest-catchlog,
+   python3-pytest (>= 3.3.0),
python3-defusedxml,
cython3 (>= 0.23),
texlive-latex-base,
diff -Nru s3ql-2.26+dfsg/debian/tests/control 
s3ql-2.26+dfsg/debian/tests/control
--- s3ql-2.26+dfsg/debian/tests/control 2018-03-04 11:39:25.0 +
+++ s3ql-2.26+dfsg/debian/tests/control 2018-04-03 10:18:02.0 +
@@ -1,10 +1,10 @@
 Tests: upstream-standard
-Depends: python3-pytest, python3-pytest-catchlog, rsync, s3ql, fuse, psmisc
+Depends: python3-pytest, rsync, s3ql, fuse, psmisc
 
 # This is really the same test suite, but when run with root
 # access (or permission to mount fuse file systems), additional
 # tests will be run.
 Tests: upstream-with-fuse
-Depends: python3-pytest, python3-pytest-catchlog, rsync, s3ql, fuse, psmisc
+Depends: python3-pytest, rsync, s3ql, fuse, psmisc
 Restrictions: needs-root
 

thanks!

Gianfranco




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: s3ql
Source-Version: 2.26+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Nikolaus Rath  (supplier of updated s3ql 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: Wed, 04 Apr 2018 09:51:16 +0100
Source: s3ql
Binary: s3ql s3ql-dbg
Architecture: source
Version: 2.26+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Nikolaus Rath 
Changed-By: Nikolaus Rath 
Description:
 s3ql   - Full-featured file system for online data storage
 s3ql-dbg   - Full-featured file system for online data storage (debugging symb
Closes: 894717
Changes:
 s3ql (2.26+dfsg-2) unstable; urgency=medium
 .
   * Drop pytest-catchlog dependency in favor of pytest >= 3.3. Closes:
 #894717.
Checksums-Sha1:
 8e08c13b829fbd140455046d96228cdeac8ff46e 2894 s3ql_2.26+dfsg-2.dsc
 a8e3498accc1c21b63565d7102d58126cffe7464 13368 s3ql_2.26+dfsg-2.debian.tar.xz
Checksums-Sha256:
 e16107779a6131e4f619a5f3e6a7f2b2e347ab5cdc0aba7307897fb6b1cb62a0 2894 
s3ql_2.26+dfsg-2.dsc
 d3928b8dbfcc4139a85534c474767c0a4f36db1ae23a7b50966df531385c785f 13368 
s3ql_2.26+dfsg-2.debian.tar.xz
Files:
 28e108aa01b58eaff21181cb7cdadf02 2894 misc optional

Bug#894716: marked as done (python-llfuse: please really drop python-catchlog dependency)

Your message dated Wed, 04 Apr 2018 09:27:35 +
with message-id 
and subject line Bug#894716: fixed in python-llfuse 1.3.3+dfsg-3
has caused the Debian Bug report #894716,
regarding python-llfuse: please really drop python-catchlog dependency
to be marked as done.

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

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


-- 
894716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894716
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-llfuse
Version: 1.3.2+dfsg-2
Severity: serious
Tags: patch

Hello, the effort to remove catchlog is ongoing,
catchlog now is broken, because of its merge into the main pytest package.

Please update the dependencies to reflect this status,
fixing the testsuite failures and removing the old cruft from the archive.

An example of patch is here:

diff -Nru python-llfuse-1.3.3+dfsg/debian/changelog 
python-llfuse-1.3.3+dfsg/debian/changelog
--- python-llfuse-1.3.3+dfsg/debian/changelog   2018-03-31 11:51:40.0 
+
+++ python-llfuse-1.3.3+dfsg/debian/changelog   2018-04-03 10:36:53.0 
+
@@ -1,3 +1,9 @@
+python-llfuse (1.3.3+dfsg-1.1) unstable; urgency=medium
+
+  * Really drop catchlog depedency (Closes: #-1)
+
+ -- Gianfranco Costamagna   Tue, 03 Apr 2018 
12:36:53 +0200
+
 python-llfuse (1.3.3+dfsg-1) unstable; urgency=medium
 
   [ OndÅ™ej NovÃ½ ]
diff -Nru python-llfuse-1.3.3+dfsg/debian/control 
python-llfuse-1.3.3+dfsg/debian/control
--- python-llfuse-1.3.3+dfsg/debian/control 2018-03-31 11:50:14.0 
+
+++ python-llfuse-1.3.3+dfsg/debian/control 2018-04-03 10:36:31.0 
+
@@ -14,8 +14,7 @@
python3-all-dev,
python3-all-dbg,
python3-sphinx (>= 1.0.7+dfsg),
-   python-pytest (>= 2.8.0),
-   python-pytest-catchlog,
+   python-pytest (>= 3.3.0),
python-contextlib2,
python3-pytest (>= 3.3.0),
pkg-config,
diff -Nru python-llfuse-1.3.3+dfsg/debian/tests/control 
python-llfuse-1.3.3+dfsg/debian/tests/control
--- python-llfuse-1.3.3+dfsg/debian/tests/control   2018-03-31 
11:49:57.0 +
+++ python-llfuse-1.3.3+dfsg/debian/tests/control   2018-04-03 
10:36:49.0 +
@@ -1,10 +1,10 @@
 Tests: upstream-standard
-Depends: python3-pytest, python-pytest, python-llfuse, python3-llfuse, fuse, 
python3-pytest-catchlog, python-pytest-catchlog
+Depends: python3-pytest, python-pytest, python-llfuse, python3-llfuse, fuse
 
 # This is really the same test suite, but when run with root
 # access (or permission to mount fuse file systems), additional
 # tests will be run.
 Tests: upstream-with-fuse
-Depends: python3-pytest, python-pytest, python-llfuse, python3-llfuse, fuse, 
python3-pytest-catchlog, python-pytest-catchlog
+Depends: python3-pytest, python-pytest, python-llfuse, python3-llfuse, fuse
 Restrictions: needs-root
 


thanks!

Gianfranco




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-llfuse
Source-Version: 1.3.3+dfsg-3

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

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

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

Debian distribution maintenance software
pp.
Nikolaus Rath  (supplier of updated python-llfuse 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: Wed, 04 Apr 2018 09:47:38 +0100
Source: python-llfuse
Binary: python-llfuse python-llfuse-dbg python3-llfuse python3-llfuse-dbg 
python-llfuse-doc
Architecture: source
Version: 1.3.3+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Nikolaus Rath 
Changed-By: Nikolaus Rath 
Description:
 python-llfuse - Python bindings for the low-level FUSE API
 python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging 
symbols)
 python-llfuse-doc - Python bindings for the low-level FUSE API (documentation)
 python3-llfuse - Python 3 bindings for the low-level FUSE API
 python3-llfuse-dbg - Python

Bug#894677: glib2.0: FTBFS on i386: test error occurred

2018-04-04 Thread Simon McVittie

Control: tags -1 + patch pending

On Tue, 03 Apr 2018 at 11:24:38 +0100, Simon McVittie wrote:
> [This] is an intermittent failure present since before stretch. I could
> reproduce it on amd64 by running
> 
> /usr/lib/glib2.0/installed-tests/glib/gapplication --tap
> 
> several thousand times in a loop.

The attached patch seems to address it.
From: Simon McVittie 
Date: Wed, 4 Apr 2018 08:35:39 +0100
Subject: g_test_dbus_down: Ensure next test does not use old connection

There's a race condition somewhere in GTestDBus that can result in
the next test being started at a time when g_bus_get() would still
return the connection that is in the process of closing. This can
be reproduced reasonably reliably by running the gapplication test
10K times in a loop.

Instead of relying on waiting for the weak reference to be released,
we can force the issue by clearing it.

Bug: https://bugzilla.gnome.org/show_bug.cgi?id=768996
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894677
Forwarded: yes
---
 gio/gdbusconnection.c | 16 
 gio/gdbusprivate.h|  1 +
 gio/gtestdbus.c   |  1 +
 3 files changed, 18 insertions(+)

diff --git a/gio/gdbusconnection.c b/gio/gdbusconnection.c
index 6f7e5fe..2c74a73 100644
--- a/gio/gdbusconnection.c
+++ b/gio/gdbusconnection.c
@@ -7233,6 +7233,22 @@ _g_bus_get_singleton_if_exists (GBusType bus_type)
   return ret;
 }
 
+/* May be called from any thread. Must not hold message_bus_lock. */
+void
+_g_bus_forget_singleton (GBusType bus_type)
+{
+  GWeakRef *singleton;
+
+  G_LOCK (message_bus_lock);
+
+  singleton = message_bus_get_singleton (bus_type, NULL);
+
+  if (singleton != NULL)
+g_weak_ref_set (singleton, NULL);
+
+  G_UNLOCK (message_bus_lock);
+}
+
 /**
  * g_bus_get_sync:
  * @bus_type: a #GBusType
diff --git a/gio/gdbusprivate.h b/gio/gdbusprivate.h
index 6a6a080..625177b 100644
--- a/gio/gdbusprivate.h
+++ b/gio/gdbusprivate.h
@@ -143,6 +143,7 @@ void _g_dbus_object_proxy_remove_interface (GDBusObjectProxy *proxy,
 
 /* Implemented in gdbusconnection.c */
 GDBusConnection *_g_bus_get_singleton_if_exists (GBusType bus_type);
+void _g_bus_forget_singleton(GBusType bus_type);
 
 G_END_DECLS
 
diff --git a/gio/gtestdbus.c b/gio/gtestdbus.c
index 6eaf060..227f5b2 100644
--- a/gio/gtestdbus.c
+++ b/gio/gtestdbus.c
@@ -823,6 +823,7 @@ g_test_dbus_down (GTestDBus *self)
 _g_object_dispose_and_wait_weak_notify (connection);
 
   g_test_dbus_unset ();
+  _g_bus_forget_singleton (G_BUS_TYPE_SESSION);
   self->priv->up = FALSE;
 }

Processed: Re: Bug#894677: glib2.0: FTBFS on i386: test error occurred

Processing control commands:

> tags -1 + patch pending
Bug #894677 [src:glib2.0] FTBFS: Failed to register: The connection is closed; 
gio/tests/gapplication.c:572:test_quit: assertion failed: (activated)
Added tag(s) pending and patch.

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

Bug#893227: libbluray FTBFS with openjdk-9

2018-04-04 Thread Emmanuel Bourg

Hi Sebastian,

On Tue, 3 Apr 2018 17:07:38 +0200 Sebastian Ramacher wrote:

> Where can I find an official announcement that openjdk-8 will be dropped?

The Java Team intends to switch to OpenJDK 11 for Buster (11 is the next
Java LTS release). OpenJDK 8 isn't guaranteed to be supported upstream
beyond 2020 and thus shouldn't be used for Buster. The issue is, we
don't know yet if we'll manage to complete the transition to OpenJDK 11
in time for Buster, so as a last resort we may revert to OpenJDK 8.
We'll assess the situation before the freeze, but it's critical that
packages get fixed as soon as possible.

Emmanuel Bourg

Bug#859841: zurl: Please migrate to openssl1.1 in Buster

2018-04-04 Thread Jan Niehusmann

Current state of affairs:

- curl built against openssl 1.1 was uploaded to experimental
  
https://tracker.debian.org/news/937117/accepted-curl-7580-3-source-amd64-all-into-experimental-experimental/

- zurl built against that version of curl and openssl 1.1 was uploaded
  to experimental
  
https://tracker.debian.org/news/937630/accepted-zurl-191-2-source-amd64-into-experimental/

- transition was requested
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891872

It seems like now we are waiting for the package xmltooling:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891872#25

Any tests using the versions of zurl and curl from experimental are
welcome. I'm especially interested in any validation that it's indeed
not a problem to use zurl with openssl1.1 and a version of qt which is
still using openssl1.0.
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891872#20)

Jan

Bug#894758: marked as done (maildir-utils: Incomplete debian/copyright?)

Your message dated Wed, 4 Apr 2018 17:03:07 +0900
with message-id <20180404080307.gb25...@bulldog.preining.info>
and subject line Re: Bug#894758: maildir-utils: Incomplete debian/copyright?
has caused the Debian Bug report #894758,
regarding maildir-utils: Incomplete debian/copyright?
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.)

--
894758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894758
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: maildir-utils
Version: 1.0-2
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Norbert Preining

Hi,

I just ACCEPTed maildir-utils from NEW but noticed it was missing
attribution/licenses in debian/copyright for at least some of the
utilities under lib (eg. mu-flags.c) and perhaps some of the tests
under perl/t.

This is not at all exhaustive so please check over the entire
package carefully and address these on your next upload :)

Regards,

--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
--- End Message ---
--- Begin Message ---
> Ah, mea culpa. This was indeed plain oversight... on my part :-)

Ok, closing this bug. Thanks for the prompt feedback!

All the best

Norbert

--
PREINING Norbert http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13--- End Message ---

Bug#894763: libglib2.0-0: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy

2018-04-04 Thread Simon McVittie

On Wed, 04 Apr 2018 at 10:41:01 +0300, Adrian Bunk wrote:
> On Wed, Apr 04, 2018 at 09:10:31AM +0200, Axel Beckert wrote:
> >...
> > ~ → ldd /usr/lib/arm-linux-gnueabihf/glib-2.0/gio-querymodules
> > libgio-2.0.so.0 => /usr/lib/arm-linux-gnueabihf/libgio-2.0.so.0 
> > (0x76e3f000)
> > libgobject-2.0.so.0 => 
> > /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0 (0x76df7000)
> > libgmodule-2.0.so.0 => 
> > /usr/lib/arm-linux-gnueabihf/libgmodule-2.0.so.0 (0x76de4000)
> > libglib-2.0.so.0 => /lib/arm-linux-gnueabihf/libglib-2.0.so.0 
> > (0x76d0d000)
> >...
> 
> This looks like there is a libglib-2.0.so.0 in /lib/arm-linux-gnueabihf/ 
> that shouldn't be there, and this takes precedence over the more recent
> one from the Debian package that gets installed to /usr/lib.

My thoughts exactly. What's that doing there? I would have expected that
removing the old libglib2.0-0 package would delete that.

Please try:

ls -il /lib/arm-linux-gnueabihf/libglib-2.0.so*
ls -il /usr/lib/arm-linux-gnueabihf/libglib-2.0.so*

Since you were seeing these symbol lookup errors while packages are
being configured, I wonder whether we're seeing something like this:

* new libglib2.0-0 is unpacked
  - /usr/lib/arm-linux-gnueabihf/libglib-2.0.so.0 has been created
(it is hard-linked to
/usr/lib/arm-linux-gnueabihf/libglib-2.0.so.0.dpkg-new or something)
  - /lib/arm-linux-gnueabihf/libglib-2.0.so.0 has not yet been deleted
(it is hard-linked to
/lib/arm-linux-gnueabihf/libglib-2.0.so.0.dpkg-old or something)
* assorted other packages are unpacked
* assorted other packages are configured
  - in your situation, we fail here and never get further
* new libglib2.0-0 is configured
  - /lib/arm-linux-gnueabihf/libglib-2.0.so.0 should be deleted here

If that guess is correct, then we're going to have difficulty whenever we
migrate a library from a higher-precedence directory (/lib/MULTIARCH) to
a lower-precedence directory (/usr/lib/MULTIARCH), and we'd have the same
issue moving a non-multiarch library from /lib to /usr/lib. The multiarch
directories (from ld.so.conf.d) are higher-precedence than the non-multiarch
directories (hard-coded), so we only coincidentally avoided this for the
migration from non-multiarch to multiarch.

GLib maintainers following testing/unstable wouldn't have seen this
failure mode, because we would be very likely to be upgrading from a
version that is recent enough that it already has all the same symbols as
the one in /lib; but it would be a problem for stretch -> buster upgrades.

smcv

Bug#894770: duplicate and permission on serial port

2018-04-04 Thread Geert Stappers

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894769 and
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894770 are duplicates

Closing the oldest one in case of minor difference I didn't spot.


My first guess on "the serial connection selection is greyed out"
is permission on the serial port.  Advise: check it.
Possible solution: please the user running arduino in the group
that may read and write the serial port such as dailout.

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

Your message dated Wed, 4 Apr 2018 09:50:34 +0200
with message-id <20180404075034.gk26...@gpm.stappers.nl>
and subject line duplicate and permission on serial port
has caused the Debian Bug report #894769,
regarding arduino: serial communication/uploader not working
to be marked as done.

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

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


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

Dear Maintainer,

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

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

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

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

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

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

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

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

arduino suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894769 and
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894770 are duplicates

Closing the oldest one in case of minor difference I didn't spot.


My first guess on "the serial connection selection is greyed out"
is permission on the serial port.  Advise: check it.
Possible solution: please the user running arduino in the group
that may read and write the serial port such as dailout.--- End Message ---

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

Your message dated Wed, 4 Apr 2018 09:50:34 +0200
with message-id <20180404075034.gk26...@gpm.stappers.nl>
and subject line duplicate and permission on serial port
has caused the Debian Bug report #894769,
regarding arduino: serial communication/uploader not working
to be marked as done.

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

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


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

Dear Maintainer,

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

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

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

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

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

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

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

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

arduino suggests no packages.

-- no debconf information


- End forwarded message -
--- End Message ---
--- Begin Message ---
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894769 and
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894770 are duplicates

Closing the oldest one in case of minor difference I didn't spot.


My first guess on "the serial connection selection is greyed out"
is permission on the serial port.  Advise: check it.
Possible solution: please the user running arduino in the group
that may read and write the serial port such as dailout.--- End Message ---

Bug#894758: maildir-utils: Incomplete debian/copyright?

2018-04-04 Thread Chris Lamb

Hi Norbert,

> > attribution/licenses in debian/copyright for at least some of the
> > utilities under lib (eg. mu-flags.c) and perhaps some of the tests
> 
> Hmm, I am not completely convinced what you mean. in mu-flags.c the
> *name* is missing:

Ah, mea culpa. This was indeed plain oversight... on my part :-)


Best wishes,

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

Bug#894778: open-build-service requires ruby2.3 for building

Source: open-build-service
Version: 2.7.4-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/open-build-service.html

...
dh_auto_build
make -j16 -O
make[2]: Entering directory '/build/1st/open-build-service-2.7.4'
make -C docs/api/api apidocs
make[3]: Entering directory '/build/1st/open-build-service-2.7.4/docs/api/api'
make[3]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
make[3]: Leaving directory '/build/1st/open-build-service-2.7.4/docs/api/api'
make[3]: Entering directory '/build/1st/open-build-service-2.7.4/docs/api/api'
BUNDLE_GEMFILE=../../../src/api/Gemfile bundle exec ../restility/bin/rest_doc 
api.txt --html -o ../html
`/nonexistent/first-build` is not a directory.
Bundler will use `/tmp/bundler/home/pbuilder1' as your home directory 
temporarily.
/usr/bin/env: 'ruby2.3': No such file or directory
make[3]: *** [Makefile:8: apidocs] Error 127

Bug#894763: libglib2.0-0: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy

On Wed, Apr 04, 2018 at 09:10:31AM +0200, Axel Beckert wrote:
>...
> ~ → ldd /usr/lib/arm-linux-gnueabihf/glib-2.0/gio-querymodules
> libgio-2.0.so.0 => /usr/lib/arm-linux-gnueabihf/libgio-2.0.so.0 
> (0x76e3f000)
> libgobject-2.0.so.0 => 
> /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0 (0x76df7000)
> libgmodule-2.0.so.0 => 
> /usr/lib/arm-linux-gnueabihf/libgmodule-2.0.so.0 (0x76de4000)
> libglib-2.0.so.0 => /lib/arm-linux-gnueabihf/libglib-2.0.so.0 
> (0x76d0d000)
>...

This looks like there is a libglib-2.0.so.0 in /lib/arm-linux-gnueabihf/ 
that shouldn't be there, and this takes precedence over the more recent
one from the Debian package that gets installed to /usr/lib.

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: Merging duplicate report

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

> merge 894769 894770
Bug #894769 [arduino] arduino: serial communication/uploader not working
Bug #894770 [arduino] arduino: serial communication/uploader not working
Merged 894769 894770
> thanks
Stopping processing here.

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

Bug#894775: kgb-bot: FTBFS and Debci failure with git >= 2.16.3

Source: kgb-bot
Version: 1.46-1
Severity: serious

https://ci.debian.net/packages/k/kgb-bot/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kgb-bot.html

...
Test Summary Report
---
t/52-client-git.t(Wstat: 65024 Tests: 68 Failed: 0)
  Non-zero exit status: 254
  Parse errors: No plan found in TAP output
t/53-client-git-merges.t (Wstat: 1792 Tests: 21 Failed: 7)
  Failed tests:  10-11, 14, 16-17, 20-21
  Non-zero exit status: 7
  Parse errors: No plan found in TAP output
Files=26, Tests=293, 587 wallclock secs ( 1.83 usr  1.03 sys + 130.67 cusr 
97.37 csys = 230.90 CPU)
Result: FAIL
Failed 2/26 test programs. 7/293 subtests failed.
dh_auto_test: perl Build test --verbose 1 returned exit code 255
make[1]: *** [debian/rules:15: override_dh_auto_test] Error 2

Bug#894763: libglib2.0-0: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy

Hi Simon,

Simon McVittie wrote:
> > emacs25: symbol lookup error: 
> > /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: 
> > g_date_copy
[fast forward → TL;DR]

> In fact, running
> 
> LD_BIND_NOW=1 /usr/lib/arm-linux-gnueabihf/glib-2.0/gio-querymodules
> 
> and seeing whether it fails might also give interesting information.

It fails in the same way as emacs fails:

~ → LD_BIND_NOW=1 /usr/lib/arm-linux-gnueabihf/glib-2.0/gio-querymodules
/usr/lib/arm-linux-gnueabihf/glib-2.0/gio-querymodules: symbol lookup error: 
/usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy

Downgrading helps also here:

~ → LD_BIND_NOW=1 /usr/lib/arm-linux-gnueabihf/glib-2.0/gio-querymodules
Usage: gio-querymodules  [ ...]
Will update giomodule.cache in the listed directories

For completeness, following is the remainder of the questions with the
long answers. ;-)

> I would normally ask: if you run `ldd emacs25`, what does it say?

Ah, right. Should have done that in the initial mail:

~ → emacs25
emacs25: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: 
undefined symbol: g_date_copy
~ → ldd =emacs25
libtiff.so.5 => /usr/lib/arm-linux-gnueabihf/libtiff.so.5 (0x76ec3000)
libjpeg.so.62 => /usr/lib/arm-linux-gnueabihf/libjpeg.so.62 (0x76e8a000)
libpng16.so.16 => /usr/lib/arm-linux-gnueabihf/libpng16.so.16 
(0x76e59000)
libgif.so.7 => /usr/lib/arm-linux-gnueabihf/libgif.so.7 (0x76e43000)
libXpm.so.4 => /usr/lib/arm-linux-gnueabihf/libXpm.so.4 (0x76e27000)
libXaw3d.so.6 => /usr/lib/arm-linux-gnueabihf/libXaw3d.so.6 (0x76dd3000)
libXmu.so.6 => /usr/lib/arm-linux-gnueabihf/libXmu.so.6 (0x76db3000)
libXt.so.6 => /usr/lib/arm-linux-gnueabihf/libXt.so.6 (0x76d68000)
libSM.so.6 => /usr/lib/arm-linux-gnueabihf/libSM.so.6 (0x76d52000)
libICE.so.6 => /usr/lib/arm-linux-gnueabihf/libICE.so.6 (0x76d31000)
libXext.so.6 => /usr/lib/arm-linux-gnueabihf/libXext.so.6 (0x76d16000)
libX11.so.6 => /usr/lib/arm-linux-gnueabihf/libX11.so.6 (0x76c21000)
libX11-xcb.so.1 => /usr/lib/arm-linux-gnueabihf/libX11-xcb.so.1 
(0x76c0f000)
libxcb.so.1 => /usr/lib/arm-linux-gnueabihf/libxcb.so.1 (0x76be7000)
libXrender.so.1 => /usr/lib/arm-linux-gnueabihf/libXrender.so.1 
(0x76bd)
libXft.so.2 => /usr/lib/arm-linux-gnueabihf/libXft.so.2 (0x76bb2000)
libasound.so.2 => /usr/lib/arm-linux-gnueabihf/libasound.so.2 
(0x76afd000)
librsvg-2.so.2 => /usr/lib/arm-linux-gnueabihf/librsvg-2.so.2 
(0x76ac9000)
libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0x76a48000)
libgio-2.0.so.0 => /usr/lib/arm-linux-gnueabihf/libgio-2.0.so.0 
(0x7693a000)
libgdk_pixbuf-2.0.so.0 => 
/usr/lib/arm-linux-gnueabihf/libgdk_pixbuf-2.0.so.0 (0x7691)
libgobject-2.0.so.0 => /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0 
(0x768c8000)
libglib-2.0.so.0 => /lib/arm-linux-gnueabihf/libglib-2.0.so.0 
(0x767ef000)
libcairo.so.2 => /usr/lib/arm-linux-gnueabihf/libcairo.so.2 (0x76731000)
libMagickWand-6.Q16.so.5 => 
/usr/lib/arm-linux-gnueabihf/libMagickWand-6.Q16.so.5 (0x7664b000)
libMagickCore-6.Q16.so.5 => 
/usr/lib/arm-linux-gnueabihf/libMagickCore-6.Q16.so.5 (0x7643b000)
libacl.so.1 => /lib/arm-linux-gnueabihf/libacl.so.1 (0x76425000)
librt.so.1 => /lib/arm-linux-gnueabihf/librt.so.1 (0x7640f000)
libdbus-1.so.3 => /lib/arm-linux-gnueabihf/libdbus-1.so.3 (0x763ce000)
libXrandr.so.2 => /usr/lib/arm-linux-gnueabihf/libXrandr.so.2 
(0x763b7000)
libXinerama.so.1 => /usr/lib/arm-linux-gnueabihf/libXinerama.so.1 
(0x763a4000)
libXfixes.so.3 => /usr/lib/arm-linux-gnueabihf/libXfixes.so.3 
(0x7639)
libxml2.so.2 => /usr/lib/arm-linux-gnueabihf/libxml2.so.2 (0x7626d000)
libgpm.so.2 => /usr/lib/arm-linux-gnueabihf/libgpm.so.2 (0x76256000)
libtinfo.so.5 => /lib/arm-linux-gnueabihf/libtinfo.so.5 (0x7622b000)
libselinux.so.1 => /lib/arm-linux-gnueabihf/libselinux.so.1 (0x76201000)
libfreetype.so.6 => /usr/lib/arm-linux-gnueabihf/libfreetype.so.6 
(0x76185000)
libfontconfig.so.1 => /usr/lib/arm-linux-gnueabihf/libfontconfig.so.1 
(0x76146000)
libotf.so.0 => /usr/lib/arm-linux-gnueabihf/libotf.so.0 (0x76127000)
libm17n-core.so.0 => /usr/lib/arm-linux-gnueabihf/libm17n-core.so.0 
(0x760fa000)
libm17n-flt.so.0 => /usr/lib/arm-linux-gnueabihf/libm17n-flt.so.0 
(0x760e2000)
libgnutls.so.30 => /usr/lib/arm-linux-gnueabihf/libgnutls.so.30 
(0x75fdf000)
libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0x75fba000)
libz.so.1 => /lib/arm-linux-gnueabihf/libz.so.1 (0x75f98000)
libgomp.so.1 => /usr/lib/arm-linux-gnueabihf/libgomp.so.1 (0x75f68000)
libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0x75e7)
/lib/ld-linux-armhf.so.3 (0x76f3d000)

Bug#894751: marked as done (license missing)

Your message dated Wed, 04 Apr 2018 07:04:40 +
with message-id 
and subject line Bug#894751: fixed in libbpp-core 2.4.0-2
has caused the Debian Bug report #894751,
regarding license missing
to be marked as done.

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

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


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

Package: libbpp-core
Version: 2.4.0-1
Severity: serious
thanks

Dear Maintainer,

as the CeCILL license is not part of /usr/share/common-licenses/, please 
add the full license text to your debian/copyright


Thanks!
  Thorsten
--- End Message ---
--- Begin Message ---
Source: libbpp-core
Source-Version: 2.4.0-2

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libbpp-core 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: Wed, 04 Apr 2018 08:50:41 +0200
Source: libbpp-core
Binary: libbpp-core-dev libbpp-core4
Architecture: source
Version: 2.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libbpp-core-dev - Bio++ Core library development files
 libbpp-core4 - Bio++ Core library
Closes: 894751
Changes:
 libbpp-core (2.4.0-2) unstable; urgency=medium
 .
   * Provide full license text of CeCILL license
 Closes: #894751
Checksums-Sha1:
 bc3e7228fc28800ebf7ed1f2d99de1c081f418ac 2131 libbpp-core_2.4.0-2.dsc
 0d69585ff5fd3a11850419d241f93346cdd9b02e 32128 
libbpp-core_2.4.0-2.debian.tar.xz
 dc03f833198255253f245523a8c87a682de32b94 13595 
libbpp-core_2.4.0-2_source.buildinfo
Checksums-Sha256:
 c0bc48420eec3186b60ed32f638e1d45c2e36497e6d246e638cec42528926940 2131 
libbpp-core_2.4.0-2.dsc
 a247ecea7fe5b1396bcab3e6aa2a591cec7b1937b98ab7b9fa655dd70a0a37c9 32128 
libbpp-core_2.4.0-2.debian.tar.xz
 975e3e96a7f86066a26592105c846a712c3573b3894f8507eb1b951dd4e8ae23 13595 
libbpp-core_2.4.0-2_source.buildinfo
Files:
 87427e8db47f36a20462c0df31481e30 2131 science optional libbpp-core_2.4.0-2.dsc
 a9cb26793cb3bbd11ecbc05ec96b9cf5 32128 science optional 
libbpp-core_2.4.0-2.debian.tar.xz
 ca4c9151796210c499242f69204a3f8a 13595 science optional 
libbpp-core_2.4.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlrEdh8OHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtGbNQ//RtvTiY3AKKNAI406k47PIfDR0G1pi67pcMHK
0fLVNAUr4xl5/Elcsu63YOwcq68mCYY+N6KGkNyj2J6huOO6DqhJSb4Dv9tA8uQP
6VWR9OQajNCtW2nl/jVoTA83ecdso8Yh6Bi4oceRi6oRSoNK1mKhm8P9HUt86jHK
bGoJVhIqJBsroT/gHNmAXIOUEH+/nDNFJkZcP194Iokw/1+l5t6+IYdvUFU66kHv
gAPnMtwlC12kdf18mDb26lKtOuN/mN/V/yvA91Tuhhl4vZqA6Ok+0s8+yMNN60ul
hvHnDfYcppJi0mhKyB7KCrX0k7kZxRTezXdmZogjp/4pqITVhEwyjCRxg3ZB2OZM
e9MdJ8HmApr8MzKGbCuZtZfsdlE2OreHMipNU5g183CRjRB0iYI+Xsjp2qMUehq4
ViiKHKRWHYCsmTVoiHppIz8mZL9VcC8VIorpAPF9SGdF7Yz0TMJwSiEFMrQxKDig
n05ZxDciBjFNLzc6o3jdisKtqvgZL2Dtxn6DMrp0012WpeoH35XqGmnjqXbfkRA/
MCst6ZaUY3BDAC+EulM1iG7lZfl78oay4gn6XyokLVd1Ks9Anba+j+PQpaWe/0w3
SMzOOjh3E+hPuGdPFSIkDB1t6YI3ZSfXh5N9453n1oOM63bW3g4GQ1FjV4hzRo2M
4FcViIM=
=U5SG
-END PGP SIGNATURE End Message ---

Bug#894716: fixed in python-llfuse 1.3.3+dfsg-2

2018-04-04 Thread Gianfranco Costamagna

control: reopen -1
control: notfixed -1 1.3.3+dfsg-2

>* Fully drop pytest-catchlog dependency (previous upload only dropped
>  dependency for Python 3 by accident). Closes: #894716.

please drop it *completely* with the patch I gave you some messages ago.
(hint: debian/tests/control)

G.



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#894716: fixed in python-llfuse 1.3.3+dfsg-2