date:20200102

Your message dated Fri, 03 Jan 2020 07:35:00 +
with message-id 
and subject line Bug#947976: fixed in netcdf 1:4.7.3-1~exp2
has caused the Debian Bug report #947976,
regarding license problems
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.)


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

Package: netcdf
Version: 1:4.6.3-1~exp1
Severity: serious
User: alteh...@debian.org
Usertags: ftp
thanks

Hi,

our hardworking trainees added a note to your package:

 CODE_OF_CONDUCT.md not accounted for in d/copyright (it's CC-BY-4.0).

 Copyright for docs/auth.html wrong, and the file seems to be generated
 from auth.md -- can you confirm we can regenerate it with tools in the
 archive?

 What reason is there to think that docs\unidata_logo_cmyk.png is
 redistributible?

 Can docs/docmap.pdf be rebuilt?

 Are the .dmp, .hdf4 and .nc files in dap4_test/, hdf4_test/ and
 h5_test/ perhaps generated files?  Can they be regenerated?

 I think that it would be best to explicitly include the Unidata
 copyright line from COPYRIGHT in addition to the "University
 Corporation for Atmospheric Research/Unidata" line.

 debian/ copyright stanza out-of-date.


Please take care of these issues.

Thanks!
  Thorsten
--- End Message ---
--- Begin Message ---
Source: netcdf
Source-Version: 1:4.7.3-1~exp2

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated netcdf 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: Fri, 03 Jan 2020 07:58:32 +0100
Source: netcdf
Architecture: source
Version: 1:4.7.3-1~exp2
Distribution: experimental
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 947976
Changes:
 netcdf (1:4.7.3-1~exp2) experimental; urgency=medium
 .
   * Drop Name field from upstream metadata.
   * Update copyright file, changes:
 - Add license & copyright for CODE_OF_CONDUCT.md.
 (closes: #947976)
Checksums-Sha1:
 997e502fedd5cddd74ebf9831444d10328986879 2321 netcdf_4.7.3-1~exp2.dsc
 c1350dfc0d14acbe8792a4a59abf6ef25e5202c5 30908 
netcdf_4.7.3-1~exp2.debian.tar.xz
 0bd4fbb5471302c13b5496cf2ebe4fd75fad5185 10677 
netcdf_4.7.3-1~exp2_amd64.buildinfo
Checksums-Sha256:
 17eac4625fe31afa5d7788278bdb82a9f099907928a1f24730f350b85d4d21e9 2321 
netcdf_4.7.3-1~exp2.dsc
 c4440c5b464b9b1ccc687ffdddf8ef3bae6c635e4104cb0ed13153213a920a7b 30908 
netcdf_4.7.3-1~exp2.debian.tar.xz
 02968555b01421a1184bb4b33ef77b0ce2db8254f4c537cfc5d161417ece509e 10677 
netcdf_4.7.3-1~exp2_amd64.buildinfo
Files:
 6ee7489fc0d43e5f441cf9e6d4f1f6d3 2321 science optional netcdf_4.7.3-1~exp2.dsc
 e6dfb0b79c1757598899513b4d16aa70 30908 science optional 
netcdf_4.7.3-1~exp2.debian.tar.xz
 34ae69f7a6915e1736438d4d2d71d3b6 10677 science optional 
netcdf_4.7.3-1~exp2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAl4O7BQACgkQZ1DxCuiN
SvG+JhAAvztDYLvX+Yic2ydbrm5STVfXrX3i7Zp8cvdWls8jRvds4MKa97RohUsk
Z6ACvU7RS60tXvJlmwIQEjghLwvS/RuEPFOIqxDEUln9uEpbJWTf+7Gp7HofjgF9
IiDFKna5uJ1b7R3X4rV73m5veKcZpJlvswlh4HMgm75QaV1xMILVZOGZvu3aRQZN
neS9mw10A6MOYiLc+JrbrFTDjFwEACEiFwLxOXAIOawfQ8I8TweVQQpF3ABnKaD+
0wnOpjYfXPtscZBHEx7qOiplxsO3It0Dj4XmpCJxbfLODAgIPSmUDIl+OCLwQ9XM
LSnyS+gNMtnv13Zjv7BwJu+2SzTTnTGrL87c6k3g55phwaytAJLVJ5cHHsh28D1h
+rWjGZOs/+7wcfX+6jLisVV03h7THYQ4GTlT6hd7gztyk4OQaFM0oInZyGo8uWAv
jge0jSN/lxd4VIQREbe0vd3L9iiMuLBbKjkhh/VCLKyLIC0wgpmlHEQnqUuWkTp5
gKwrkjFAnK+Sa5TFIECIAKqkMtbUZzg2lhmdYXUt5mV3lyl+i7BCqA02xPPn0G3e
gfvjzIaTgMaSk5936iHM6Pzs7MoQT/u7iE/hSKFUsyiJ1O3OZ6QMVMSWL3U0KXOa
HZmjF80GBu4XA5Uqh/sfSP+x2RUvAsUVDqCb95TxeGHVqymrPKM=
=ULpl
-END PGP SIGNATURE End Message ---

Processed: Re: fcitx-configtool-gtk2: Depends on libunique

Processing control commands:

> tags -1 + pending
Bug #885815 [fcitx-config-gtk2] fcitx-configtool-gtk2: Depends on libunique
Added tag(s) pending.

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

Bug#885815: fcitx-configtool-gtk2: Depends on libunique

2020-01-02 Thread Changwoo Ryu

Control: tags -1 + pending

On Fri, 29 Dec 2017 21:45:12 -0500 Jeremy Bicha  wrote:
> Package: fcitx-configtool-gtk2
> Version: 0.4.9-1
> Severity: important
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: oldlibs libunique
> Tags: sid buster
>
> As announced [1], we do not intend to release Debian 10 "Buster" with
> the old libgnome (and related) libraries. These libraries have been
> deprecated and unmaintained for several years.
>
> Your package depends and or build-depends on libunique.
>
> Please consider dropping fcitx-configtool-gtk2 to help us achieve this
> goal.
>
> [1] https://lists.debian.org/debian-devel/2017/10/msg00299.html
>
> On behalf of the Debian GNOME team,
> Jeremy Bicha

Hello, Jeremy.

Your 0.4.10-3 upload two months ago has been auto-rejected as it refers
"orig.tar.gz" file instead of "orig.tar.xz". Could you upload again with
existing orig tarball?

Thanks,
Changwoo Ryu

Bug#943600: lazarus autopkgtest intermittedly fails due to EAccessViolation: Access violation

Hi all,

On 02-01-2020 19:29, Graham Inggs wrote:
> As of now, lazarus 2.0.6+dfsg-3 has failed its autopkgtests 2 out of
> 11 times on amd64 [1], and 3 out of 11 times on arm64 [2].
> 
> I am hesitant to re-open this bug as RC, as it potentially removes all
> packages built with lazarus for no good reason.
> 
> 
> [1] https://ci.debian.net/packages/l/lazarus/testing/amd64/
> [2] https://ci.debian.net/packages/l/lazarus/testing/arm64/

I propose we mark the test as flaky until somebody is able to completely
fix it or until the statistics have dramatically improved.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#947976: license problems

2020-01-02 Thread Sebastiaan Couwenberg

On 1/2/20 11:58 PM, Thorsten Alteholz wrote:
>  CODE_OF_CONDUCT.md not accounted for in d/copyright (it's CC-BY-4.0).

You really had to dig for that one.

>  Copyright for docs/auth.html wrong, and the file seems to be generated
>  from auth.md -- can you confirm we can regenerate it with tools in the
>  archive?

What makes you say the copyright is wrong? It falls under the "Files: *"
section, which is BSD-3-Clause after the relicensing from the NetCDF
license.

doxygen is used to generate the HTML docs, which is part of the build
process.

>  What reason is there to think that docs\unidata_logo_cmyk.png is
>  redistributible?

What reason is there to think that it isn't?

Unidata develops NetCDF and chose to include their logo in the source
tree to use it in the (generated) documentation.

>  Can docs/docmap.pdf be rebuilt?

Why do you care?

>  Are the .dmp, .hdf4 and .nc files in dap4_test/, hdf4_test/ and
>  h5_test/ perhaps generated files?  Can they be regenerated?

They are test data, they shouldn't be regenerated.

>  I think that it would be best to explicitly include the Unidata
>  copyright line from COPYRIGHT in addition to the "University
>  Corporation for Atmospheric Research/Unidata" line.

"2018 Unidata"

is already part of

"1988-2019, University Corporation for Atmospheric Research/Unidata"

I don't see why including the former is in any way better.

> Please take care of these issues.

I've added license & copyright for CODE_OF_CONDUCT.md, that is enough to
fix this issue in my opinion. If you also demand that I fix the pedantic
issues, I'll instead start working on removing netcdf and everything
that depends on it from Debian as I don't enjoy working on these
packages. I only do so because it's currently a dependency of gdal, but
that can be changed.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#948003: prometheus-squid-exporter FTBFS in testing/unstable


source: prometheus-squid-exporter
version: 1.4+ds-1
severity: serious
tags: bullseye, sid, ftbfs

prometheus-squid-exporter FTBFS in testing/unstable, I first noticed this on a 
raspbian autobuilder, but it's also happening on the reproducible builds tests, 
so it's not raspbian specific.


github.com/boynux/squid-exporter
# github.com/boynux/squid-exporter
src/github.com/boynux/squid-exporter/main.go:38:33: undefined: 
prometheus.Handler
dh_auto_build: cd build && go install 
-gcflags=all=\"-trimpath=/build/1st/prometheus-squid-exporter-1.4\+ds/build/src\" 
-asmflags=all=\"-trimpath=/build/1st/prometheus-squid-exporter-1.4\+ds/build/src\" -v -p 16 -tags  -ldflags 
" -X github.com/prometheus/common/version.Version=1.4+ds -X 
github.com/prometheus/common/version.Revision=1.4+ds-1 -X github.com/prometheus/common/version.Branch=debian/sid -X 
github.com/prometheus/common/version.BuildUser=pkg-go-maintain...@lists.alioth.debian.org -X 
github.com/prometheus/common/version.BuildDate=20190123-11:01:45 -X 
github.com/prometheus/common/version.GoVersion=go1.13.5" github.com/boynux/squid-exporter 
github.com/boynux/squid-exporter/collector github.com/boynux/squid-exporter/types returned exit code 2
make[1]: *** [debian/rules:28: override_dh_auto_build] Error 255

Bug#948002: prometheus-process-exporter FTBFS in testing/unstable


source: prometheus-process-exporter
version: 0.4.0+ds-1
severity: serious
tags: bullseye, sid, ftbfs

prometheus-process-exporter FTBFS in testing/unstable, I first noticed this on 
a raspbian autobuilder, but it's also happening on the reproducible builds 
tests, so it's not raspbian specific.


github.com/ncabatoff/process-exporter/vendor/github.com/ncabatoff/fakescraper
# github.com/ncabatoff/process-exporter/vendor/github.com/ncabatoff/fakescraper
src/github.com/ncabatoff/process-exporter/vendor/github.com/ncabatoff/fakescraper/fakescraper.go:38:2:
 undefined: prometheus.Handler
dh_auto_build: cd build && go install 
-gcflags=all=\"-trimpath=/build/1st/prometheus-process-exporter-0.4.0\+ds/build/src\" 
-asmflags=all=\"-trimpath=/build/1st/prometheus-process-exporter-0.4.0\+ds/build/src\" -v -p 15 
github.com/ncabatoff/process-exporter github.com/ncabatoff/process-exporter/cmd/process-exporter 
github.com/ncabatoff/process-exporter/config github.com/ncabatoff/process-exporter/proc returned exit code 2
make[1]: *** [debian/rules:14: override_dh_auto_build] Error 255

Bug#938844: marked as done (xgridfit: Python2 removal in sid/bullseye)

Your message dated Fri, 03 Jan 2020 06:35:10 +
with message-id 
and subject line Bug#938844: fixed in xgridfit 2.3-4
has caused the Debian Bug report #938844,
regarding xgridfit: Python2 removal in sid/bullseye
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.)


-- 
938844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xgridfit
Version: 2.3-3
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:xgridfit

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: xgridfit
Source-Version: 2.3-4

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated xgridfit 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: Fri, 03 Jan 2020 14:06:08 +0900
Source: xgridfit
Architecture: source
Version: 2.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: Hideki Yamane 
Closes: 938844
Changes:
 xgridfit (2.3-4) unstable; urgency=medium
 .
   * debian/control
 - use dh12
 - adjust dependency for python3 (Closes: #938844)
 - set Standards-Version: 4.4.1
 - Rules-Requires-Root: no
   * debian/patches
 - update patches
 - add 0006-use-2to3.patch
 - add 0007-also-specify-usr-not-usr-local.patch
 - add 0008-drop-empty-DESTDIR.patch
   * debian/rules
 - don't override dh_install
   * debian/salsa-ci.yml: add it
Checksums-Sha1:
 da523bec1ae92eeb8d1e323c47bdb862cc882c51 2050 xgridfit_2.3-4.dsc
 dff0634228d6214d5a5d3a68ba732de8114b0f9a 9116 xgridfit_2.3-4.debian.tar.xz
 bbf90d8801ffdcbd4b2e2a780f27932721596ecd 6184 xgridfit_2.3-4_amd64.buildinfo
Checksums-Sha256:

Bug#948001: go-dep FTBFS in testing/unstable


source: go-dep
version: 0.5.4-2
severity: serious
tags: bullseye, sid, ftbfs

go-dep FTBFS in testing/unstable, I first noticed this on a raspbian 
autobuilder, but it's also happening on the reproducible builds tests, so it's 
not raspbian specific.


make[1]: Entering directory '/build/1st/go-dep-0.5.4'
go: cannot find GOROOT directory: /usr/lib/go-1.8
*** Cannot use default go. Forcing go-1.8.
GOPATH=/build/1st/go-dep-0.5.4/obj-x86_64-linux-gnu go generate 
github.com/golang/dep
go: cannot find GOROOT directory: /usr/lib/go-1.8
make[1]: *** [debian/rules:23: override_dh_auto_build] Error 2

Bug#948000: packer FTBFS in testing/unstable


source: packer
version: 1.3.4+dfsg-4
severity: serious
tags: bullseye, sid, ftbfs

packer FTBFS in testing/unstable, I first noticed this on a raspbian 
autobuilder, but it's also happening on the reproducible builds tests, so it's 
not raspbian specific.

Note: I am aware there is an existing FTBFS bug tagged as unreproducible, but 
this seems to be a different issue from the one reported there.


github.com/hashicorp/packer/builder/parallels/pvm
# github.com/hashicorp/packer/builder/openstack
src/github.com/hashicorp/packer/builder/openstack/step_create_volume.go:128:22: 
not enough arguments in call to volumes.Delete
have (*gophercloud.ServiceClient, string)
want (*gophercloud.ServiceClient, string, volumes.DeleteOptsBuilder)
github.com/aws/aws-sdk-go/service/s3/s3iface
github.com/vmware/govmomi/vim25/mo
github.com/hashicorp/packer/provisioner/ansible
github.com/hashicorp/packer/provisioner/ansible-local
github.com/hashicorp/packer/provisioner/breakpoint
github.com/hashicorp/packer/builder/hyperv/iso
github.com/hashicorp/packer/builder/hyperv/vmcx
github.com/hashicorp/packer/provisioner/chef-client
github.com/hashicorp/packer/provisioner/chef-solo
github.com/hashicorp/packer/builder/virtualbox/iso
github.com/hashicorp/packer/builder/virtualbox/ovf
github.com/hashicorp/packer/provisioner/converge
github.com/hashicorp/packer/provisioner/file
github.com/hashicorp/packer/provisioner/powershell
github.com/hashicorp/packer/provisioner/puppet-masterless
github.com/hashicorp/packer/provisioner/puppet-server
github.com/hashicorp/packer/packer/rpc
github.com/hashicorp/packer/provisioner/salt-masterless
github.com/hashicorp/packer/provisioner/shell
github.com/hashicorp/packer/builder/vmware/iso
github.com/hashicorp/packer/builder/vmware/vmx
github.com/hashicorp/packer/provisioner/shell-local
github.com/hashicorp/packer/provisioner/windows-restart
github.com/hashicorp/packer/provisioner/windows-shell
# github.com/hashicorp/packer/packer/rpc
src/github.com/hashicorp/packer/packer/rpc/client.go:45:3: cannot use promoted 
field BasicHandle.DecodeOptions.RawToString in struct literal of type 
codec.MsgpackHandle
src/github.com/hashicorp/packer/packer/rpc/server.go:135:3: cannot use promoted 
field BasicHandle.DecodeOptions.RawToString in struct literal of type 
codec.MsgpackHandle
google.golang.org/api/internal
github.com/aws/aws-sdk-go/service/s3/s3manager
google.golang.org/api/option
google.golang.org/api/transport/http
github.com/vmware/govmomi/property
google.golang.org/api/storage/v1
google.golang.org/api/compute/v1
github.com/vmware/govmomi/session
github.com/vmware/govmomi/list
github.com/vmware/govmomi/task
github.com/vmware/govmomi
github.com/hashicorp/packer/builder/cloudstack
github.com/vmware/govmomi/object
github.com/aws/aws-sdk-go/service/ec2/ec2iface
github.com/vmware/govmomi/find
github.com/hashicorp/packer/post-processor/vsphere-template
github.com/hashicorp/packer/builder/amazon/common
github.com/hashicorp/packer/builder/amazon/ebs
github.com/hashicorp/packer/builder/amazon/ebsvolume
github.com/hashicorp/packer/builder/amazon/instance
github.com/hashicorp/packer/builder/amazon/ebssurrogate
github.com/hashicorp/packer/post-processor/amazon-import
github.com/hashicorp/packer/builder/amazon/chroot
github.com/hashicorp/packer/builder/docker
github.com/hashicorp/packer/post-processor/docker-import
github.com/hashicorp/packer/post-processor/docker-tag
github.com/hashicorp/packer/post-processor/docker-push
github.com/hashicorp/packer/post-processor/docker-save
github.com/hashicorp/packer/builder/googlecompute
github.com/hashicorp/packer/post-processor/googlecompute-export
github.com/hashicorp/packer/post-processor/googlecompute-import
dh_auto_build: cd obj-x86_64-linux-gnu && go install 
-gcflags=all=\"-trimpath=/build/1st/packer-1.3.4\+dfsg/obj-x86_64-linux-gnu/src\" 
-asmflags=all=\"-trimpath=/build/1st/packer-1.3.4\+dfsg/obj-x86_64-linux-gnu/src\" -v -p 15 
github.com/hashicorp/packer github.com/hashicorp/packer/builder/alicloud/ecs 
github.com/hashicorp/packer/builder/amazon/chroot github.com/hashicorp/packer/builder/amazon/common 
github.com/hashicorp/packer/builder/amazon/ebs github.com/hashicorp/packer/builder/amazon/ebssurrogate 
github.com/hashicorp/packer/builder/amazon/ebsvolume github.com/hashicorp/packer/builder/amazon/instance 
github.com/hashicorp/packer/builder/cloudstack github.com/hashicorp/packer/builder/digitalocean 
github.com/hashicorp/packer/builder/docker github.com/hashicorp/packer/builder/file 
github.com/hashicorp/packer/builder/googlecompute github.com/hashicorp/packer/builder/hyperv/common 
github.com/hashicorp/packer/builder/hyperv/iso github.com/hashicorp/packer/builder/hyperv/vmcx 
github.com/hashicorp/packer/builder/lxc github.com/hashicorp/packer/builder/lxd 
github.com/hashicorp/packer/builder/null github.com/hashicorp/packer/builder/openstack 
github.com/hashicorp/packer/builder/parallels/common github.com/hashicorp/packer/builder/parallels/iso

Bug#947999: prometheus-varnish-exporter FTBFS in testing/unstable


source: prometheus-varnish-exporter
version: 1.5-1
severity: serious
tags: bullseye, sid, ftbfs

prometheus-varnish-exporter FTBFS in testing/unstable, I first noticed this on 
a raspbian autobuilder, but it's also happening on the reproducible builds 
tests, so it's not raspbian specific.


github.com/jonnenauha/prometheus_varnish_exporter
dh_auto_test -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 15 
github.com/jonnenauha/prometheus_varnish_exporter
flag provided but not defined: -test.testlogfile
Usage of /tmp/go-build260258336/b001/prometheus_varnish_exporter.test:
   -N string
varnishstat -N value.
   -docker-container-name string
Docker container name to exec varnishstat in.
   -exit-on-errors
Exit process on scrape errors.
   -n string
varnishstat -n value.
   -no-exit
Deprecated: see -exit-on-errors
   -raw
Raw stdout logging without timestamps.
   -test
Test varnishstat availability, prints available metrics and exits.
   -varnishstat-path string
Path to varnishstat. (default "varnishstat")
   -verbose
Verbose logging.
   -version
Print version and exit
   -web.health-path string
Path under which to expose healthcheck. Disabled unless configured.
   -web.listen-address string
Address on which to expose metrics and web interface. (default ":9131")
   -web.telemetry-path string
Path under which to expose metrics. (default "/metrics")
   -with-go-metrics
Export go runtime and http handler metrics
FAILgithub.com/jonnenauha/prometheus_varnish_exporter   0.010s
FAIL
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 15 
github.com/jonnenauha/prometheus_varnish_exporter returned exit code 1

Bug#947998: notary FTBFS in testing/unstable


source: notary
version: 0.6.1~ds1-4
severity: serious
tags: bullseye, sid, ftbfs

notary FTBFS in testing/unstable, I first noticed this on a raspbian 
autobuilder, but it's also happening on the reproducible builds tests, so it's 
not raspbian specific.


github.com/theupdateframework/notary/utils
# github.com/theupdateframework/notary/utils
src/github.com/theupdateframework/notary/utils/http.go:112:24: not enough 
arguments in call to challenge.SetHeaders
have (http.ResponseWriter)
want (*http.Request, http.ResponseWriter)
github.com/theupdateframework/notary/server/snapshot
github.com/theupdateframework/notary/client
github.com/theupdateframework/notary/server/timestamp
github.com/theupdateframework/notary/tuf/testutils/interfaces
github.com/theupdateframework/notary/tuf/testutils
github.com/prometheus/client_golang/prometheus/promhttp
google.golang.org/grpc/internal/transport
github.com/docker/go-metrics
github.com/docker/distribution/metrics
github.com/docker/distribution/registry/storage/cache
github.com/docker/distribution/registry/storage/cache/memory
github.com/docker/distribution/registry/client
google.golang.org/grpc
github.com/docker/distribution/registry/client/auth
github.com/theupdateframework/notary/trustmanager/remoteks
github.com/theupdateframework/notary/proto
google.golang.org/grpc/health/grpc_health_v1
github.com/theupdateframework/notary/signer
github.com/theupdateframework/notary/signer/client
google.golang.org/grpc/health
github.com/theupdateframework/notary/signer/api
dh_auto_build: cd _build && go install 
-gcflags=all=\"-trimpath=/build/1st/notary-0.6.1\~ds1/_build/src\" 
-asmflags=all=\"-trimpath=/build/1st/notary-0.6.1\~ds1/_build/src\" -v -p 15 -tags pkcs11 
github.com/theupdateframework/notary github.com/theupdateframework/notary/client 
github.com/theupdateframework/notary/client/changelist github.com/theupdateframework/notary/cmd/escrow 
github.com/theupdateframework/notary/cmd/notary github.com/theupdateframework/notary/cmd/notary-server 
github.com/theupdateframework/notary/cmd/notary-signer github.com/theupdateframework/notary/cryptoservice 
github.com/theupdateframework/notary/passphrase github.com/theupdateframework/notary/proto 
github.com/theupdateframework/notary/server github.com/theupdateframework/notary/server/errors 
github.com/theupdateframework/notary/server/handlers github.com/theupdateframework/notary/server/snapshot 
github.com/theupdateframework/notary/server/storage github.com/theupdateframework/notary/server/timestamp 
github.com/theupdateframework/notary/signer github.com/theupdateframework/notary/signer/api 
github.com/theupdateframework/notary/signer/client github.com/theupdateframework/notary/signer/keydbstore 
github.com/theupdateframework/notary/storage github.com/theupdateframework/notary/storage/rethinkdb 
github.com/theupdateframework/notary/trustmanager 
github.com/theupdateframework/notary/trustmanager/remoteks 
github.com/theupdateframework/notary/trustmanager/yubikey github.com/theupdateframework/notary/trustpinning 
github.com/theupdateframework/notary/tuf github.com/theupdateframework/notary/tuf/data 
github.com/theupdateframework/notary/tuf/signed github.com/theupdateframework/notary/tuf/testutils 
github.com/theupdateframework/notary/tuf/testutils/interfaces 
github.com/theupdateframework/notary/tuf/testutils/keys github.com/theupdateframework/notary/tuf/utils 
github.com/theupdateframework/notary/tuf/validation github.com/theupdateframework/notary/utils 
github.com/theupdateframework/notary/version returned exit code 2
make[1]: *** [debian/rules:25: override_dh_auto_build] Error 255

Bug#947997: ncbi-entrez-direct FTBFS in testing/unstable


source: prometheus-blackbox-exporter
version: 0.13.0+ds-2
severity: serious
tags: bullseye, sid, ftbfs

prometheus-blackbox-exporter FTBFS in testing/unstable, I first noticed this on 
a raspbian autobuilder, but it's also happening on the reproducible builds 
tests, so it's not raspbian specific.


github.com/prometheus/blackbox_exporter/prober
# github.com/prometheus/blackbox_exporter/prober
src/github.com/prometheus/blackbox_exporter/prober/http.go:219:44: not enough arguments 
in call to "github.com/prometheus/common/config".NewClientFromConfig
have ("github.com/prometheus/common/config".HTTPClientConfig, string)
want ("github.com/prometheus/common/config".HTTPClientConfig, string, 
bool)
dh_auto_build: cd obj-x86_64-linux-gnu && go install 
-gcflags=all=\"-trimpath=/build/1st/prometheus-blackbox-exporter-0.13.0\+ds/obj-x86_64-linux-gnu/src\" 
-asmflags=all=\"-trimpath=/build/1st/prometheus-blackbox-exporter-0.13.0\+ds/obj-x86_64-linux-gnu/src\" -v 
-p 15 -ldflags " -X github.com/prometheus/common/version.Version=0.13.0+ds -X 
github.com/prometheus/common/version.Revision=0.13.0+ds-2 -X github.com/prometheus/common/version.Branch=debian/sid 
-X github.com/prometheus/common/version.BuildUser=pkg-go-maintain...@lists.alioth.debian.org -X 
github.com/prometheus/common/version.BuildDate=20190119-14:59:39 -X 
github.com/prometheus/common/version.GoVersion=go1.13.5" github.com/prometheus/blackbox_exporter 
github.com/prometheus/blackbox_exporter/config github.com/prometheus/blackbox_exporter/prober returned exit code 2
make[1]: *** [debian/rules:26: override_dh_auto_build] Error 255

Bug#947996: golang-github-mailru-easyjson FTBFS in testing/unstable


source: golang-github-mailru-easyjson
version: 0.0~git20161103.0.159cdb8-1.1
severity: serious
tags: bullseye, sid, ftbfs

golang-github-mailru-easyjson FTBFS in testing/unstable, I first noticed this 
on a raspbian autobuilder, but it's also happening on the reproducible builds 
tests, so it's not raspbian specific.


easyjson -all 
/build/1st/golang-github-mailru-easyjson-0.0~git20161103.0.159cdb8/obj-x86_64-linux-gnu/src/github.com/mailru/easyjson/tests/data.go
failed to initialize build cache at /nonexistent/first-build/.cache/go-build: 
mkdir /nonexistent: permission denied
Bootstrap failed: exit status 1

Bug#947995: ncbi-entrez-direct FTBFS in testing/unstable


source: ncbi-entrez-direct
version: 10.9.20190219+ds-1
severity: serious
tags: bullseye, sid, ftbfs

ncbi-entrez-direct FTBFS in testing/unstable, I first noticed this on a 
raspbian autobuilder, but it's also happening on the reproducible builds tests, 
so it's not raspbian specific.


go build -v -gccgoflags '-g -O2 
-ffile-prefix-map=/build/1st/ncbi-entrez-direct-10.9.20190219+ds=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
-Wl,-z,now -Wl,--as-needed' -o bin/xtract \
 xtract.go common.go
go build: when using gc toolchain, please pass compile flags using -gcflags, 
and linker flags using -ldflags
failed to initialize build cache at /nonexistent/first-build/.cache/go-build: 
mkdir /nonexistent: permission denied
make[1]: *** [debian/rules:84: override_dh_auto_build] Error 1

Bug#942343: marked as done (caja-extensions: please prepare for gssdp/gupnp 1.2 transition)

Your message dated Fri, 03 Jan 2020 05:49:16 +
with message-id 
and subject line Bug#942343: fixed in caja-extensions 1.22.1-2
has caused the Debian Bug report #942343,
regarding caja-extensions: please prepare for gssdp/gupnp 1.2 transition
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.)


-- 
942343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: caja-extensions
Version: 1.22.1-1
Severity: important

Dear Maintainer,

The gssdp/gupnp 1.2 transition will soon start. Please prepare an
updated package which is compatible with these in experimental.

This should be the relevant upstream commit you might want to
cherry-pick:
https://github.com/mate-desktop/caja-extensions/commit/45d85850235bbcb6b59b1443d22f0e8203cce566
Also update the build-dependencies to libgssdp-1.2-dev and
libgupnp-1.2-dev as needed.

Regards,
Andreas Henriksson
--- End Message ---
--- Begin Message ---
Source: caja-extensions
Source-Version: 1.22.1-2

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated caja-extensions 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 03 Jan 2020 06:33:18 +0100
Source: caja-extensions
Architecture: source
Version: 1.22.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian+Ubuntu MATE Packaging Team 
Changed-By: Mike Gabriel 
Closes: 942343
Changes:
 caja-extensions (1.22.1-2) unstable; urgency=medium
 .
   * debian/control:
 + Bump Standards-Version: to 4.4.1. No changes needed.
 + Add Rules-Requires-Root: field and set it to no.
 + Update B-D. Use gupnp-1.2 on Debian, as well. (Closes: #942343).
Checksums-Sha1:
 61dc85169b7ba84874dab123842617cbab30f5e8 2777 caja-extensions_1.22.1-2.dsc
 0f491345c797b2f82c8c6bbeb9d8ecf6618e26f8 8312 
caja-extensions_1.22.1-2.debian.tar.xz
 687bee7454c99786cee6a5ddb4046fb03afc0959 17066 
caja-extensions_1.22.1-2_source.buildinfo
Checksums-Sha256:
 30b24e44fce9fed3e2ac7c89cae6d6875320b179bddc95b9caf6d0972ca62ea5 2777 
caja-extensions_1.22.1-2.dsc
 4623c32a321a6f4d3a6144b543fa4a244cdbb30656961b976fd0b6aa635a18b7 8312 
caja-extensions_1.22.1-2.debian.tar.xz
 a61af5465022423124e0c6f4b886212745dd4470e5548402dd5c8ae2aa9bfdbf 17066 
caja-extensions_1.22.1-2_source.buildinfo
Files:
 34e96a426deb2d05341f4187df47e034 2777 x11 optional caja-extensions_1.22.1-2.dsc
 ae8b54fdd1ed722b025fe3138f901175 8312 x11 optional 
caja-extensions_1.22.1-2.debian.tar.xz
 151e66816062ab82af90119b5e782d42 17066 x11 optional 
caja-extensions_1.22.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl4O0i0VHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxaCUP/Au6Z0bfJGIJ1gZSQewWomZIP9/1
GHBZ0B8IvvfzYGhgQs88XA+wHColsImsXVb4LLFLiXpNU9IlDq5blmhus8gTVHEp
yzobvIWcKSoTR7eB6w+8QiJ1OBEezb6muPux0vPEQElLbTg+fZQDyE/7uvJ49KNM
kHqXh1whkn3bLCS/NKOTW6DKOJPAM3Z36WxAEL16poq3ERxx2VKdhS/NpBZ9wP0x
NtJJGZU2n+OPXN9iEFol8QUm22TCM55UEV8aUep8aw4ATaxN+aPMc/zLWM1y/INc
nJqcoa3mC85dRYzNMcbRwESNltxsyjs0UXXP1omWHb/UtoCCz23Cn+2axaJ+JRp5
vNDyAavQkbxMU9OKkeF/rs7Xun6UtSZE3AikL+W0pNu+XIQyuaeS2Zabepe7wKSi
WHpDF1nn/AtSXxUYgtvyZReugHcLWU7EyMAHK5E/MciLouiUSNxRHCsJv6oiBdWO
5uV6D7mlr/NV2aW5afvxRNvf8qCw12g67WxA6i8w9hfQ+JYO/KQUY1XSG8mfwM63
Hl6Y04UOrxsXSO5BWBdq+ldzaTbB7lWoLl/pVd/JVGEzxoMSGDNh/FM3rki2dZWp
wGBl8hN63YA4YVieijmWMLnpNO9ib8/VSlFiH/EyPBSSAihL+QYspTFKjW7IEwyJ
A1jN9DSe3054Rmj6
=BJxU
-END PGP SIGNATURE End Message ---

Bug#942343: marked as pending in caja-extensions

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian-mate-team/caja-extensions/commit/3fdcddb2f33a256fafa10a0759a24d3746cdd8df


debian/control: Update B-D. Use gupnp-1.2 on Debian, as well. (Closes: #942343).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/942343

Processed: Bug#942343 marked as pending in caja-extensions

Processing control commands:

> tag -1 pending
Bug #942343 [src:caja-extensions] caja-extensions: please prepare for 
gssdp/gupnp 1.2 transition
Added tag(s) pending.

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

Bug#941266: marked as done (netty: CVE-2019-16869)

Your message dated Fri, 03 Jan 2020 05:20:54 +
with message-id 
and subject line Bug#941266: fixed in netty 1:4.1.33-2
has caused the Debian Bug report #941266,
regarding netty: CVE-2019-16869
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.)


-- 
941266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netty
Version: 1:4.1.33-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/netty/netty/issues/9571

Hi,

The following vulnerability was published for netty.

CVE-2019-16869[0]:
| Netty before 4.1.42.Final mishandles whitespace before the colon in
| HTTP headers (such as a "Transfer-Encoding : chunked" line), which
| leads to HTTP request smuggling.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-16869
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16869
[1] https://github.com/netty/netty/issues/9571

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: netty
Source-Version: 1:4.1.33-2

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated netty package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 02 Jan 2020 20:47:57 +0100
Source: netty
Architecture: source
Version: 1:4.1.33-2
Distribution: unstable
Urgency: high
Maintainer: Debian Java Maintainers 

Changed-By: Salvatore Bonaccorso 
Closes: 941266
Changes:
 netty (1:4.1.33-2) unstable; urgency=high
 .
   * Team upload.
   * Correctly handle whitespaces in HTTP header names as defined by
 RFC7230#section-3.2.4 (CVE-2019-16869) (Closes: #941266)
Checksums-Sha1:
 dec7b6dba3b819a8fbe05e04e7f0d3c890f7e5ff 2463 netty_4.1.33-2.dsc
 9d7decd0b6ab95cface74821069a8a06916e33b6 13116 netty_4.1.33-2.debian.tar.xz
 cc8cd7b3428bf2ecddba27ffefa12d900b5589ba 14013 netty_4.1.33-2_amd64.buildinfo
Checksums-Sha256:
 299e7e07c56442b47c945bcd98e5bb446f0ffcbfe987a5ee97faa69548dfa4e7 2463 
netty_4.1.33-2.dsc
 a7f9b3e18b584501c9199626bf4aeec9804b5ffb3e457828b73768779415f992 13116 
netty_4.1.33-2.debian.tar.xz
 eea66a1fb0c9feee49e777b21336eab579e0582153541531a2ea5b0294e76b97 14013 
netty_4.1.33-2_amd64.buildinfo
Files:
 f16654d072ff6e05ccf8248fa26e3541 2463 java optional netty_4.1.33-2.dsc
 85270be51c6f7853ca70b928531d7cc7 13116 java optional 
netty_4.1.33-2.debian.tar.xz
 cd131ebd5490ce42ca318ff13a36b43f 14013 java optional 
netty_4.1.33-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAl4OyvcUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpYt7BAAmYyd1HNP7vxDzK3FgHk+mAiadwGY
JzvQ8YgFRgwf7TZHWD67Ouqb5tLcl72s+FOU4ECuvgj+YuSFQyoDr9+mjjl+AtSB
79lrdCzidtEsKCq4oJVWeUykJR0mPS49rA4ZpsKebpdJkbFlp/KdjUPbm/9Mne+w
CY/SyI/f36uYEArT1Ir3b3fhjhjtsvLIMG5gC/jZGrMMJR4QEW1wSVzLx7INUKX0
UZfyMmSfGL8lGjPx4WyarCY70JpIT2bTsVV8XVeO7WBvd4pcOJap44FawgiuGRj2
WSJJBQsrJumF6duRWsSB6Colh+EBdPc6lr9MGhkH3Rb9OaTlrDkH9gDNJ2z6hBO1
MwclSpQJx4r8f9fHCY8PPs2gkjAH9i64tbGnEDrb2IHyPMjEboyoLAukTgWDifQn
Mlz2oZth4A+KdBb+QFN9JjyZR9SznJHwjjjDda43qbYuqtie9aZ6jup/tyFBqZKY
ERoAqwg5s7GNDo1JGqoCaCRizCUi5pETHNogqLRcGaWYbbjEHuW5FE0l2eL3JnBQ
RP5s8J4ZIlQgYjLR4hNjnuGY8YkCaJCwzTZoZ6gbjSkopaNJYshuQVnnrZSO3Tnm
Rlm3V9eQqRZtnCYNgsmJ9//fIMBhkEkRRktrERAMHHKjyCebTDHRLWZestPbPrEI
32N44rRSgJKDfS0=
=bzze
-END PGP SIGNATURE End Message ---

Bug#941266: marked as pending in netty

2020-01-02 Thread Tony Mancill

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/netty/commit/64ec32d2b0a24f95128352dcdc97b3ae44986f1d


Add patch for CVE-2019-16869 (Closes: #941266)

Thank you to Salvatore Bonaccorso for the patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/941266

Processed: Bug#941266 marked as pending in netty

Processing control commands:

> tag -1 pending
Bug #941266 [src:netty] netty: CVE-2019-16869
Added tag(s) pending.

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

Bug#941266: netty: CVE-2019-16869

2020-01-02 Thread tony mancill

On Thu, Jan 02, 2020 at 11:38:08PM +0100, Salvatore Bonaccorso wrote:
> On Fri, Sep 27, 2019 at 01:12:04PM +0200, Salvatore Bonaccorso wrote:
> > Source: netty
> > Version: 1:4.1.33-1
> > Severity: important
> > Tags: security upstream
> > Forwarded: https://github.com/netty/netty/issues/9571
> > 
> > Hi,
> > 
> > The following vulnerability was published for netty.
> > 
> > CVE-2019-16869[0]:
> > | Netty before 4.1.42.Final mishandles whitespace before the colon in
> > | HTTP headers (such as a "Transfer-Encoding : chunked" line), which
> > | leads to HTTP request smuggling.
> 
> Attached is the proposed debdiff. I included the tests as well
> (altough those are not run).

Hi Salvatore,

The debdiff looks good to me; thank you for adapting the patch for the
current version in 4.1.33.  No need for an NMU.  I will apply your patch
and perform a team upload to unstable with only this change to make it
easier for backports/security uploads.

Thanks,
tony


signature.asc
Description: PGP signature

Bug#937648: marked as done (python-click: Python2 removal in sid/bullseye)

Your message dated Fri, 03 Jan 2020 04:19:58 +
with message-id 
and subject line Bug#937648: fixed in python-click 7.0-3
has caused the Debian Bug report #937648,
regarding python-click: Python2 removal in sid/bullseye
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.)


-- 
937648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-click
Version: 7.0-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:python-click

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: python-click
Source-Version: 7.0-3

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-click 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, 02 Jan 2020 22:56:09 -0500
Source: python-click
Architecture: source
Version: 7.0-3
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 937648
Changes:
 python-click (7.0-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat.
   * Bump Standards-Version to 4.4.1.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #937648
Checksums-Sha1:
 98361e8784bd4662542267d33c4bb88e5c1df5a8 2236 python-click_7.0-3.dsc
 2c7985c5c297f4522c39a3a77b11635a14dde42e 3812 python-click_7.0-3.debian.tar.xz
 ece52e8e4b3fe7ddcb1a847ada9b61d8b935775c 7349 
python-click_7.0-3_source.buildinfo
Checksums-Sha256:
 06c4e117f56d7810598ebbe96deef87310eefbbd115e5fa33a7605df8581669a 2236 
python-click_7.0-3.dsc
 cd3cd98eda1d71a8c2d19d0f50d420168d9839bb035ea45dfd8ad557eee76402 3812 
python-click_7.0-3.debian.tar.xz

Bug#938313: marked as done (qpid-proton: Python2 removal in sid/bullseye)

Your message dated Fri, 03 Jan 2020 04:04:15 +
with message-id 
and subject line Bug#938313: fixed in qpid-proton 0.22.0-3.3
has caused the Debian Bug report #938313,
regarding qpid-proton: Python2 removal in sid/bullseye
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.)


-- 
938313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938313
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qpid-proton
Version: 0.22.0-3.2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:qpid-proton

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: qpid-proton
Source-Version: 0.22.0-3.3

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated qpid-proton 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, 02 Jan 2020 22:49:44 -0500
Source: qpid-proton
Architecture: source
Version: 0.22.0-3.3
Distribution: unstable
Urgency: medium
Maintainer: Debian Middleware Maintainers 

Changed-By: Sandro Tosi 
Closes: 938313
Changes:
 qpid-proton (0.22.0-3.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #938313
Checksums-Sha1:
 b2e364510879ecddd97e62a119594a0aea3a1d9e 2772 qpid-proton_0.22.0-3.3.dsc
 5ffccdac74a8fe4d85b99257155802bbe68bf09b 7760 
qpid-proton_0.22.0-3.3.debian.tar.xz
 809e693acbe1d674c22c5684e561d8ecd30b724c 7927 
qpid-proton_0.22.0-3.3_source.buildinfo
Checksums-Sha256:
 3b051adf927d3e2039dfd7ab02b4142ba6c2477d433c64a2a938da8d15d7c13c 2772 
qpid-proton_0.22.0-3.3.dsc
 54e08cfeb43868edc38b22bd77b5e146cbb043e789adfe9ad5228fe9d6749039 7760 
qpid-proton_0.22.0-3.3.debian.tar.xz
 49346802aeb13a2fb50d653252470171d6aab7f80b08dcd57f1eb0ef403f6be1 7927

Processed: qpid-proton: diff for NMU version 0.22.0-3.3

Processing control commands:

> tags 938313 + patch
Bug #938313 [src:qpid-proton] qpid-proton: Python2 removal in sid/bullseye
Added tag(s) patch.

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

Bug#938313: qpid-proton: diff for NMU version 0.22.0-3.3

2020-01-02 Thread Sandro Tosi

Control: tags 938313 + patch


Dear maintainer,

I've prepared an NMU for qpid-proton (versioned as 0.22.0-3.3). The diff
is attached to this message.

Regards.

diff -Nru qpid-proton-0.22.0/debian/changelog qpid-proton-0.22.0/debian/changelog
--- qpid-proton-0.22.0/debian/changelog	2019-08-07 22:29:46.0 -0400
+++ qpid-proton-0.22.0/debian/changelog	2020-01-02 22:49:44.0 -0500
@@ -1,3 +1,10 @@
+qpid-proton (0.22.0-3.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #938313
+
+ -- Sandro Tosi   Thu, 02 Jan 2020 22:49:44 -0500
+
 qpid-proton (0.22.0-3.2) unstable; urgency=medium
 
   * Replace previous NMU with a new source-only upload.
diff -Nru qpid-proton-0.22.0/debian/control qpid-proton-0.22.0/debian/control
--- qpid-proton-0.22.0/debian/control	2019-08-07 20:44:02.0 -0400
+++ qpid-proton-0.22.0/debian/control	2020-01-02 22:48:39.0 -0500
@@ -11,8 +11,6 @@
doxygen,
libssl-dev,
pkg-config,
-   python-all,
-   python-all-dev,
python3-all,
python3-all-dev,
swig,
@@ -131,23 +129,6 @@
  .
  This package provides C++ developer documentation for Qpid Proton.
 
-Package: python-qpid-proton
-Architecture: any
-Section: python
-Depends: libqpid-proton11,
- ${misc:Depends},
- ${python:Depends},
- ${shlibs:Depends},
-Provides: ${python:Provides},
-Description: language bindings for Qpid Proton messaging framework - Python 2.7
- Qpid Proton is a high-performance, lightweight messaging library. It can be
- used in the widest range of messaging applications, including brokers, client
- libraries, routers, bridges, proxies, and more. Proton makes it trivial to
- integrate with the AMQP 1.0 ecosystem from any platform, environment, or
- language.
- .
- This package provides Python 2.7 language bindings for Qpid Proton.
-
 Package: python3-qpid-proton
 Architecture: any
 Section: python
diff -Nru qpid-proton-0.22.0/debian/python-qpid-proton.install qpid-proton-0.22.0/debian/python-qpid-proton.install
--- qpid-proton-0.22.0/debian/python-qpid-proton.install	2019-08-07 20:44:02.0 -0400
+++ qpid-proton-0.22.0/debian/python-qpid-proton.install	1969-12-31 19:00:00.0 -0500
@@ -1,3 +0,0 @@
-usr/lib/python2.7/dist-packages/_cproton.so
-usr/lib/python2.7/dist-packages/cproton.py
-usr/lib/python2.7/dist-packages/proton
diff -Nru qpid-proton-0.22.0/debian/rules qpid-proton-0.22.0/debian/rules
--- qpid-proton-0.22.0/debian/rules	2019-08-07 20:44:02.0 -0400
+++ qpid-proton-0.22.0/debian/rules	2020-01-02 22:49:12.0 -0500
@@ -21,11 +21,10 @@
 export DH_OPTIONS
 export DH_ALWAYS_EXCLUDE=LICENSE
 
-PYTHONS:=$(shell pyversions -vr)
 PYTHON3S:=$(shell py3versions -vr)
 
 %:
-	dh $@ --with python2,python3
+	dh $@ --with python3
 
 override_dh_auto_configure:
 	dh_auto_configure -- -DPROTON_DISABLE_RPATH=true -DNOBUILD_RUBY=on -DSYSINSTALL_BINDINGS=on
@@ -52,9 +51,6 @@
 	mkdir -p debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)
 	mv debian/tmp/usr/lib/lib*.so* debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)
 	set -e ; cd obj-$(DEB_BUILD_GNU_TYPE)/proton-c/bindings/python/dist ; \
-		for pyvers in $(PYTHONS); do \
-			python$$pyvers setup.py install --install-layout=deb --root $(CURDIR)/debian/tmp ; \
-		done ; \
 		for pyvers in $(PYTHON3S); do \
 			python$$pyvers setup.py install --install-layout=deb --root $(CURDIR)/debian/tmp ; \
 		done
diff -Nru qpid-proton-0.22.0/debian/tests/control qpid-proton-0.22.0/debian/tests/control
--- qpid-proton-0.22.0/debian/tests/control	2019-08-07 20:44:02.0 -0400
+++ qpid-proton-0.22.0/debian/tests/control	2020-01-02 22:49:35.0 -0500
@@ -1,5 +1,2 @@
-Test-Command: set -e ; for py in $(pyversions -r 2>/dev/null) ; do cd "$ADTTMP" ; echo "Testing with $py:" ; $py -c "import proton; print proton" ; done
-Depends: python-all, python-qpid-proton
-
 Test-Command: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$ADTTMP" ; echo "Testing with $py:" ; $py -c "import proton; print(proton)" ; done
 Depends: python3-all, python3-qpid-proton

Processed: py2removal RC severity updates - 2020-01-03 03:36:10.803568+00:00

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # for more details on this severity bump
> # python-jupyter-client is a module and has 0 external rdeps or not in testing
> severity 936772 serious
Bug #936772 [src:jupyter-client] jupyter-client: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#947907: uno-libs-private: Unmet dependencies

2020-01-02 Thread Felicia

On Thu, 02 Jan 2020 08:45:17 +0100 rene.engelh...@mailbox.org wrote:
>
> I know.
>
> Already fixed locally, needs a test build ...

>

Thanks :-)

Bug#945436: marked as done (rust-debcargo Build-Depends on package that doesn't exist: librust-git2-0.8+default-dev)

Your message dated Fri, 03 Jan 2020 01:34:54 +
with message-id 
and subject line Bug#945436: fixed in rust-debcargo 2.4.1-1
has caused the Debian Bug report #945436,
regarding rust-debcargo Build-Depends on package that doesn't exist: 
librust-git2-0.8+default-dev
to be marked as done.

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

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


-- 
945436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-debcargo
Version: 2.4.0-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainer,

Your package is part of the libgit2 transition and I scheduled binNMU's for
those. However, your package fails to build from source because it build
depends on a package that doesn't exist: librust-git2-0.8+default-dev.

Please fix the situation.

Paul

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3a5FYACgkQnFyZ6wW9
dQozzggAmhSeSixKxfOMIJRi3N5rHVf/dAGjr1ChnwYO6C3ENaNwWWQAu2kg4sPp
eTJ/Z/0pkfYyNgwzZoQmE+0irBODI/vR7TrV8Wg3tF+57jYVotW8drXyKBev2BuB
CeHdtdLyh6FdbhUVFm6iyzPsI1gOi3IXBm+9XxG8sABTVo1moAUKWKk6knAw3YVu
GTjoGLiCCjnMiEb+Pdm25BYQdKwxY+DdSjVrb7W6Pc5zDyv7D2z4iTqXHZD2V2he
2xWmuBIs2y5+nqL4fiMbO2615kFDCfsUWMI1lwVzoUKD3xxssd8/xKptntH70+8X
0NE4XaPAxWGy6t7sA6jzCpf3iVMbTA==
=iUOI
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: rust-debcargo
Source-Version: 2.4.1-1

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

Debian distribution maintenance software
pp.
Ximin Luo  (supplier of updated rust-debcargo 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: Fri, 03 Jan 2020 01:19:34 +
Source: rust-debcargo
Architecture: source
Version: 2.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Ximin Luo 
Closes: 945436 945499 945560 947088
Changes:
 rust-debcargo (2.4.1-1) unstable; urgency=medium
 .
   * Package debcargo 2.4.1 from crates.io using debcargo 2.4.1
   * Closes: #945436, #945499, #945560, #947088.
Checksums-Sha1:
 e023059efd60ebe89167a58708d4c5dda1b9237d 2320 rust-debcargo_2.4.1-1.dsc
 e6d9e644d029700e9105ab32f186080aa0cb90da 69549 rust-debcargo_2.4.1.orig.tar.gz
 69fa859c82efee89be086187169d8dd7d11a41e5 3140 
rust-debcargo_2.4.1-1.debian.tar.xz
 e42ee6ef639b085f9523cf28cfff7acbc372614e 6687 
rust-debcargo_2.4.1-1_source.buildinfo
Checksums-Sha256:
 35a394e61096389292e08ef32d10db116944e7eca2f8056ad18d50a28b3e1121 2320 
rust-debcargo_2.4.1-1.dsc
 76bbc737a8c47a2508dd0ef28e2f338521902c16620ff0cb22b2a51e9cc957fb 69549 
rust-debcargo_2.4.1.orig.tar.gz
 b8015f732add0ec17f611fafee0d80d50185c1940ce1801b82db8b2581c9e3b7 3140 
rust-debcargo_2.4.1-1.debian.tar.xz
 391a9ec3677ba9eb59f8a1103b01dd07c682d0828b4cee32af420b50d96f22b7 6687 
rust-debcargo_2.4.1-1_source.buildinfo
Files:
 abb373dbca9ec31452ca2158bf8dce31 2320 rust optional rust-debcargo_2.4.1-1.dsc
 b7205dc722744805264fd92ef0043d7d 69549 rust optional 
rust-debcargo_2.4.1.orig.tar.gz
 7ea203fb43b573b8867b04978ec865dc 3140 rust optional 
rust-debcargo_2.4.1-1.debian.tar.xz
 54854ea19126ebafa8349ff3399410a5 6687 rust optional 
rust-debcargo_2.4.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQReYinNQ9GpZ9TYcRrrH8jaRfspMAUCXg6WqQAKCRDrH8jaRfsp
MMShAP4tg+7e1+9zPUFiucTxgU4n/eqGa4n1NLeWFBn/W64RtAEA4rCyg5eYj+hB
udt4cjKuhw8M4fh0Mhd+OT9XU86togo=
=pYUN
-END PGP SIGNATURE End Message ---

Processed: reassign 942242 to src:psi4, fixed 942242 in 1:1.3.2-2, reassign 947193 to musl-dev,libcrypt-dev ...

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

> reassign 942242 src:psi4 1:1.2.1-2
Bug #942242 {Done: Michael Banck } [src:gau2grid, src:psi4] 
gau2grid breaks psi4 autopkgtest: Running test scf-property... FAILED
Bug reassigned from package 'src:gau2grid, src:psi4' to 'src:psi4'.
No longer marked as found in versions gau2grid/2.0.1-2 and psi4/1:1.2.1-2.
No longer marked as fixed in versions psi4/1:1.3.2-2.
Bug #942242 {Done: Michael Banck } [src:psi4] gau2grid 
breaks psi4 autopkgtest: Running test scf-property... FAILED
Marked as found in versions psi4/1:1.2.1-2.
> fixed 942242 1:1.3.2-2
Bug #942242 {Done: Michael Banck } [src:psi4] gau2grid 
breaks psi4 autopkgtest: Running test scf-property... FAILED
Marked as fixed in versions psi4/1:1.3.2-2.
> reassign 947193 musl-dev,libcrypt-dev
Bug #947193 [musl-dev,libcrypt1-dev] please coordinate the provider of crypt.h
Warning: Unknown package 'libcrypt1-dev'
Bug reassigned from package 'musl-dev,libcrypt1-dev' to 'musl-dev,libcrypt-dev'.
Ignoring request to alter found versions of bug #947193 to the same values 
previously set
Ignoring request to alter fixed versions of bug #947193 to the same values 
previously set
> tags 947805 - buster + bullseye
Bug #947805 [upnp-router-control] Please port to gupnp/gssdp 1.2
Removed tag(s) buster.
Bug #947805 [upnp-router-control] Please port to gupnp/gssdp 1.2
Added tag(s) bullseye.
> tags 945840 + sid bullseye
Bug #945840 {Done: plugwash } [ledger] 
/usr/bin/ledger: error while loading shared libraries: 
libboost_python27.so.1.67.0: cannot open shared object file: No such file or 
directory
Bug #946036 {Done: plugwash } [ledger] Broken by 
boost dropping Python 2 support
Added tag(s) sid and bullseye.
Added tag(s) bullseye and sid.
> tags 947499 + sid bullseye
Bug #947499 [libxcb-xinput-dev] libxcb-xinput-dev: Should depend on 
libxcb-xfixes0-dev
Added tag(s) bullseye and sid.
> reassign 947874 src:libdmapsharing 2.9.39-4
Bug #947874 [libdmapsharing-3.0-2] libdmapsharing-3.0-2: apt-get source -b 
libdmapsharing failed with dh_missing errors
Bug reassigned from package 'libdmapsharing-3.0-2' to 'src:libdmapsharing'.
No longer marked as found in versions libdmapsharing/2.9.39-4.
Ignoring request to alter fixed versions of bug #947874 to the same values 
previously set
Bug #947874 [src:libdmapsharing] libdmapsharing-3.0-2: apt-get source -b 
libdmapsharing failed with dh_missing errors
Marked as found in versions libdmapsharing/2.9.39-4.
> tags 947901 + sid bullseye
Bug #947901 [src:gnome-js-common] gnome-js-common: unmaintained upstream since 
around 2010
Added tag(s) sid and bullseye.
> tags 921502 + sid bullseye
Bug #921502 {Done: gregor herrmann } [latexdiff] latexdiff 
BD/Recommends texlive-generic-recommended
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
921502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921502
942242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942242
945840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945840
946036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946036
947193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947193
947499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947499
947805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947805
947874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947874
947901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#936113:

2020-01-02 Thread Samuel Henrique

As said by upstream at:
https://github.com/aircrack-ng/aircrack-ng/pull/2087

The issue is fixed in git and there' s gonna be a new release soon.

Sending this mail to reset the auto-rm clock so we can wait for the new
release without removing the package from testing,

Regards,

--
Samuel Henrique

Bug#945347: marked as done (radare2 FTBFS: meson.build:3:0: ERROR: ['/usr/bin/python3']> is not a valid python or it is missing setuptools)

Your message dated Fri, 3 Jan 2020 00:10:27 +
with message-id

and subject line
has caused the Debian Bug report #945347,
regarding radare2 FTBFS: meson.build:3:0: ERROR:
['/usr/bin/python3']> is not a valid python or it is missing setuptools
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.)

--
945347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: radare2
Version: 3.2.1+dfsg-5
Severity: serious
Tags: ftbfs

radare2 fails to build from source. A build notably says:

| meson.build:3:0: ERROR: ['/usr/bin/python3']>
is not a valid python or it is missing setuptools

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/radare2_3.2.1+dfsg-5.rbuild.log.gz
http://crossqa.debian.net/build/radare2_3.2.1+dfsg-5_armel_20191115204904.log

According to crossqa logs this seems to have started between June 22nd
and August 20th. Presumably something changed about the Python
ecosystem.

I understand that this might be fixed in the NEW upload, but I cannot
check and poking at ftp-master didn't help thus far. Please just close
the bug in case this is already fixed.

Helmut
--- End Message ---
--- Begin Message ---
I was able to reproduce the issue with 3.2.1+dfsg-5 and confirmed that
it's fixed in 3.9.0+dfsg-1, which was accepted in unstable just now.

Thanks for the report, Helmut.

--
Samuel Henrique
--- End Message ---

Bug#947969: ceph-mgr: indefinite queue growth causing commands to hang

2020-01-02 Thread Milan Kupcevic

On 2020-01-02 15:54, Bernd Zeimetz wrote:

> 
> any idea if this affects 14.2.4?
> 


Reports are pointing to 14.2.5, so far.

Also see https://tracker.ceph.com/issues/43317


Milan

Bug#947446: closed by Rene Engelhard (Bug#947446: fixed in libreoffice 1:6.4.0~rc1-3)

2020-01-02 Thread Rene Engelhard

notfound 947446 1:6.4.0~rc1-5
close 947446 1:6.4.0~rc1-3
thanks

On Thu, Jan 02, 2020 at 10:58:11PM +0100, Andreas Beckmann wrote:
> Control: reopen -1
> Control: found -1 1:6.4.0~rc1-5

Erm, no. Breaks:/Replaces: are present.

> it looks like ure is still shipping (some of) the files that were split 
> out to separate packages:

Yes. But this completely different to your bug which was about the
Breaks:/Replaces: being there at all. Your bug is fixed.

That the split was broken per se is an other matter, but there are
already 3 bugs wrt that:

#947907 [S|P|=] [ure] trying to overwrite '/usr/share/java/juh.jar', which is 
also in package libjuh-java
#947909 [S|P|=] [ure] ure is trying to overwrite '/usr/share/java/juh.jar', 
which is also in package libjuh-java 1:6.4.0~rc1-5
#947910 [S|P|=] [ure] ure uninstallable because of file conflict with 
libjuh-java

>   Selecting previously unselected package ure.
>   Preparing to unpack .../08-ure_6.4.0~rc1-5_amd64.deb ...
>   Unpacking ure (6.4.0~rc1-5) ...
>   dpkg: error processing archive 
> /tmp/apt-dpkg-install-p2iEE9/08-ure_6.4.0~rc1-5_amd64.deb (--unpack):
>trying to overwrite '/usr/share/java/juh.jar', which is also in package 
> libjuh-java 1:6.4.0~rc1-5
> 
> Similarily for libjurt-java, libridl-java, libunoloader-java in sid.

Yes.

> Don't forget to bump the B+R against ure to a version that is no longer
> shipping them.

https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/commit/7994273bbbe8014624b3e9001dfb7243ac18c6fd

Regards,

Rene

Processed: Re: Bug#947446: closed by Rene Engelhard (Bug#947446: fixed in libreoffice 1:6.4.0~rc1-3)

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

> notfound 947446 1:6.4.0~rc1-5
Bug #947446 [src:libreoffice] libreoffice: ure split lacks proper versioned 
Breaks+Replaces
No longer marked as found in versions libreoffice/1:6.4.0~rc1-5.
> close 947446 1:6.4.0~rc1-3
Bug #947446 [src:libreoffice] libreoffice: ure split lacks proper versioned 
Breaks+Replaces
Marked as fixed in versions libreoffice/1:6.4.0~rc1-3.
Bug #947446 [src:libreoffice] libreoffice: ure split lacks proper versioned 
Breaks+Replaces
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#947978: license problem

2020-01-02 Thread Thorsten Alteholz


Package: bind9
Version: 1:9.15.5-1
Severity: serious
User: alteh...@debian.org
Usertags: ftp
thanks

Hi,

our hardworking trainees added a note to your package:

 d/copyright mentions that this source is:
  License: MPL-2.0 and ISC and BSD-2-clause and BSD-3-clause
 However, LICENSE only says MPL-2.0. I see no indication that the majority
 of source files are quadruple-licensed. Rather, the majority seem to be
 only MPL-2.0.

 The directories lim/isccc/ and m4/ have a number of copyright holders not
 that are not mentioned in d/copyright.

 lib/irs/getnameinfo.c also has a copyright holder (WIDE Project) that is
 not mentioned in d/copyright.


Please take care of these issues.

Thanks!
  Thorsten

Bug#947976: license problems

2020-01-02 Thread Thorsten Alteholz


Package: netcdf
Version: 1:4.6.3-1~exp1
Severity: serious
User: alteh...@debian.org
Usertags: ftp
thanks

Hi,

our hardworking trainees added a note to your package:

 CODE_OF_CONDUCT.md not accounted for in d/copyright (it's CC-BY-4.0).

 Copyright for docs/auth.html wrong, and the file seems to be generated
 from auth.md -- can you confirm we can regenerate it with tools in the
 archive?

 What reason is there to think that docs\unidata_logo_cmyk.png is
 redistributible?

 Can docs/docmap.pdf be rebuilt?

 Are the .dmp, .hdf4 and .nc files in dap4_test/, hdf4_test/ and
 h5_test/ perhaps generated files?  Can they be regenerated?

 I think that it would be best to explicitly include the Unidata
 copyright line from COPYRIGHT in addition to the "University
 Corporation for Atmospheric Research/Unidata" line.

 debian/ copyright stanza out-of-date.


Please take care of these issues.

Thanks!
  Thorsten

Bug#947909: marked as pending in libreoffice

2020-01-02 Thread Rene Engelhard

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/commit/7994273bbbe8014624b3e9001dfb7243ac18c6fd


fix the URE/unoil/officebean jar splitout to actually work as expected (closes: 
#947909)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/947909

Processed: Bug#947909 marked as pending in libreoffice

Processing control commands:

> tag -1 pending
Bug #947909 [ure] ure is trying to overwrite '/usr/share/java/juh.jar', which 
is also in package libjuh-java 1:6.4.0~rc1-5
Bug #947907 [ure] trying to overwrite '/usr/share/java/juh.jar', which is also 
in package libjuh-java
Bug #947910 [ure] ure uninstallable because of file conflict with libjuh-java
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.

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

Processed: Re: Bug#941266: netty: CVE-2019-16869

Processing control commands:

> tags -1 + patch
Bug #941266 [src:netty] netty: CVE-2019-16869
Added tag(s) patch.

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

Bug#941266: netty: CVE-2019-16869

2020-01-02 Thread Salvatore Bonaccorso

Control: tags -1 + patch

On Fri, Sep 27, 2019 at 01:12:04PM +0200, Salvatore Bonaccorso wrote:
> Source: netty
> Version: 1:4.1.33-1
> Severity: important
> Tags: security upstream
> Forwarded: https://github.com/netty/netty/issues/9571
> 
> Hi,
> 
> The following vulnerability was published for netty.
> 
> CVE-2019-16869[0]:
> | Netty before 4.1.42.Final mishandles whitespace before the colon in
> | HTTP headers (such as a "Transfer-Encoding : chunked" line), which
> | leads to HTTP request smuggling.

Attached is the proposed debdiff. I included the tests as well
(altough those are not run).

Regards,
Salvatore
diff -Nru netty-4.1.33/debian/changelog netty-4.1.33/debian/changelog
--- netty-4.1.33/debian/changelog   2019-01-22 14:06:25.0 +0100
+++ netty-4.1.33/debian/changelog   2020-01-02 20:47:57.0 +0100
@@ -1,3 +1,11 @@
+netty (1:4.1.33-1.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Correctly handle whitespaces in HTTP header names as defined by
+RFC7230#section-3.2.4 (CVE-2019-16869) (Closes: #941266)
+
+ -- Salvatore Bonaccorso   Thu, 02 Jan 2020 20:47:57 +0100
+
 netty (1:4.1.33-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru 
netty-4.1.33/debian/patches/14-Correctly-handle-whitespaces-in-HTTP-header-names-as.patch
 
netty-4.1.33/debian/patches/14-Correctly-handle-whitespaces-in-HTTP-header-names-as.patch
--- 
netty-4.1.33/debian/patches/14-Correctly-handle-whitespaces-in-HTTP-header-names-as.patch
   1970-01-01 01:00:00.0 +0100
+++ 
netty-4.1.33/debian/patches/14-Correctly-handle-whitespaces-in-HTTP-header-names-as.patch
   2020-01-02 20:47:57.0 +0100
@@ -0,0 +1,98 @@
+From: Norman Maurer 
+Date: Fri, 20 Sep 2019 21:02:11 +0200
+Subject: Correctly handle whitespaces in HTTP header names as defined by
+ RFC7230#section-3.2.4 (#9585)
+Origin: 
https://github.com/netty/netty/commit/39cafcb05c99f2aa9fce7e6597664c9ed6a63a95
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2019-16869
+Bug-Debian: https://bugs.debian.org/941266
+Bug: https://github.com/netty/netty/issues/9571
+
+Motivation:
+
+When parsing HTTP headers special care needs to be taken when a whitespace is 
detected in the header name.
+
+Modifications:
+
+- Ignore whitespace when decoding response (just like before)
+- Throw exception when whitespace is detected during parsing
+- Add unit tests
+
+Result:
+
+Fixes https://github.com/netty/netty/issues/9571
+[Salvatore Bonaccorso: Backport to 4.1.33 for context changes in
+HttpObjectDecoder.java]
+---
+ .../handler/codec/http/HttpObjectDecoder.java| 16 +++-
+ .../codec/http/HttpRequestDecoderTest.java   | 14 ++
+ .../codec/http/HttpResponseDecoderTest.java  | 15 +++
+ 3 files changed, 44 insertions(+), 1 deletion(-)
+
+--- 
a/codec-http/src/main/java/io/netty/handler/codec/http/HttpObjectDecoder.java
 
b/codec-http/src/main/java/io/netty/handler/codec/http/HttpObjectDecoder.java
+@@ -736,7 +736,21 @@ public abstract class HttpObjectDecoder
+ nameStart = findNonWhitespace(sb, 0);
+ for (nameEnd = nameStart; nameEnd < length; nameEnd ++) {
+ char ch = sb.charAt(nameEnd);
+-if (ch == ':' || Character.isWhitespace(ch)) {
++// https://tools.ietf.org/html/rfc7230#section-3.2.4
++//
++// No whitespace is allowed between the header field-name and 
colon. In
++// the past, differences in the handling of such whitespace have 
led to
++// security vulnerabilities in request routing and response 
handling. A
++// server MUST reject any received request message that contains
++// whitespace between a header field-name and colon with a 
response code
++// of 400 (Bad Request). A proxy MUST remove any such whitespace 
from a
++// response message before forwarding the message downstream.
++if (ch == ':' ||
++// In case of decoding a request we will just continue 
processing and header validation
++// is done in the DefaultHttpHeaders implementation.
++//
++// In the case of decoding a response we will "skip" the 
whitespace.
++(!isDecodingRequest() && Character.isWhitespace(ch))) {
+ break;
+ }
+ }
+--- 
a/codec-http/src/test/java/io/netty/handler/codec/http/HttpRequestDecoderTest.java
 
b/codec-http/src/test/java/io/netty/handler/codec/http/HttpRequestDecoderTest.java
+@@ -320,4 +320,18 @@ public class HttpRequestDecoderTest {
+ assertTrue(request.decoderResult().cause() instanceof 
TooLongFrameException);
+ assertFalse(channel.finish());
+ }
++
++@Test
++public void testWhitespace() {
++EmbeddedChannel channel = new EmbeddedChannel(new 
HttpRequestDecoder());
++String requestStr = "GET /some/path HTTP/1.1\r\n" +
++

Processed: found 941266 in 1:4.1.7-2

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

> found 941266 1:4.1.7-2
Bug #941266 [src:netty] netty: CVE-2019-16869
Marked as found in versions netty/1:4.1.7-2.
> thanks
Stopping processing here.

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

Processed: bug 947510 is forwarded to https://github.com/zaf/Asterisk-eSpeak/issues/7

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

> forwarded 947510 https://github.com/zaf/Asterisk-eSpeak/issues/7
Bug #947510 [asterisk-espeak] Asterisk won't response for a while after run the 
TTS for the first time.
Set Bug forwarded-to-address to 
'https://github.com/zaf/Asterisk-eSpeak/issues/7'.
> thanks
Stopping processing here.

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

Bug#945392: marked as done (hyperkitty: autopkgtest failures)

Your message dated Thu, 02 Jan 2020 22:04:15 +
with message-id 
and subject line Bug#945392: fixed in hyperkitty 1.3.0-1.1
has caused the Debian Bug report #945392,
regarding hyperkitty: autopkgtest 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.)


-- 
945392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hyperkitty
Version: 1.3.0-1
Severity: serious
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

The autopkgtest for your package are failing, which prevent the testing 
migration of networkx.

The logging shows many exceptions like this:

 AttributeError: 'DiGraph' object has no attribute 'node'

See:

 
https://ci.debian.net/data/autopkgtest/testing/amd64/h/hyperkitty/3494471/log.gz

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: hyperkitty
Source-Version: 1.3.0-1.1

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated hyperkitty 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, 02 Jan 2020 16:17:27 -0500
Source: hyperkitty
Architecture: source
Version: 1.3.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Mailman Team 
Changed-By: Sandro Tosi 
Closes: 945392
Changes:
 hyperkitty (1.3.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/patches/MR201.patch
 - make hyperkitty compatible with networkx 2.4; Closes: #945392
Checksums-Sha1:
 542be18c29bde5b3021de8339670edd9d4bcad96 2851 hyperkitty_1.3.0-1.1.dsc
 92a39b573545673beb004eb83a77e64c61ac26f7 133536 
hyperkitty_1.3.0-1.1.debian.tar.xz
 4cd8e69846e0a4168da0e14fe4d1ea44ad717472 8242 
hyperkitty_1.3.0-1.1_source.buildinfo
Checksums-Sha256:
 b8d43b98ec636cfd163623c40ebc4256eddc1ee4b59583d68a7534607aeb127b 2851 
hyperkitty_1.3.0-1.1.dsc
 46b18f9017eef6068c95a1d4e3dc7d47f205775c51239d9d66dc3c3518a7564b 133536 
hyperkitty_1.3.0-1.1.debian.tar.xz
 57b3f5d911b831c17335daf3583208d73b8f7c8f5a4acd47c24a66ba52115467 8242 
hyperkitty_1.3.0-1.1_source.buildinfo
Files:
 bc480b75c05dfc3c773e78a8559be683 2851 python optional hyperkitty_1.3.0-1.1.dsc
 f57c5660482cc83ae69bdd50f9a99cee 133536 python optional 
hyperkitty_1.3.0-1.1.debian.tar.xz
 6ea0e409cb81217e2daf0c9df72bbe3b 8242 python optional 
hyperkitty_1.3.0-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl4OZqoACgkQh588mTgB
qU81DxAAzd6OagKsY2YZY4SmGOBBomMu4HcmoANxjxe6SiiKLl4t1mxCLS2XsNvU
1i7+C5deZ2IW0KpzBgCsDsp889sXpyGZzDjpwKdklx/Bh/I5l+Q62HUKKrBG7+FD
vNj99n2nzmtBaFBmUt9A57NXeYI5N7QIzkkylndQ8ZqHEJzoaTrHpYFTWss6+yqH
hPqjm3zscBvw+fJOc9rvZQvryjngC+drN+0d2/DP2vcZNNruxXA0LcMpaBlE3qz9
F8Gpn8g9osHupXy1FsWi5EP0wuXk1+ci8Mi3+Z1MqcEBN8m3ZdOf8rCdSgihy2tL
T/rek24U7y718aPCFAn0Wfcqw4jKOIlA7PBEnVcAzdh4aJlpCZxEsIblJKsTvDem
sjSzlkzaChh3TSDAXpehJyhbNMMsUSCcDArZpdwK3IFpA5XETCNvYTpaWbd2PWrt
FqDbv/YLkkZ+ltdciXSdF2ctRzO8rvMKk7RfxJ3jQqbqDr36jRLP9L6QwKui1jEl
lwoeB/Jfip7HoAbrNzIrief5p+SEx+r8ErqeVLb6rAaLGJWTnPGZxCo5zcxtUAPT
fS6bYt+IN2OB+woYyPWu/MnGjxpPq7mbDi7B5lGakAEaz0touAzAFs0Xj6o/PXpo
DwLnneQTwe10W83qwV0FtfIKvoeok6YAasj23SOrgGhQlheWTn0=
=00qv
-END PGP SIGNATURE End Message ---

Bug#947486: marked as done (golang-github-containers-image: FTBFS with test failures)

Your message dated Thu, 02 Jan 2020 22:04:06 +
with message-id 
and subject line Bug#947486: fixed in golang-github-containers-image 5.0.0-2
has caused the Debian Bug report #947486,
regarding golang-github-containers-image: FTBFS with 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.)


-- 
947486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-containers-image
Version: 5.0.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

golang-github-containers-image/experimental FTBFS in an up-to-date
minimal sid+experimental pbuilder environment:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/golang-github-containers-image-5.0.0'
mkdir -v -p debian/tmp
mkdir: created directory 'debian/tmp'
XDG_RUNTIME_DIR=/build/golang-github-containers-image-5.0.0/debian/tmp \
dh_auto_test
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 3 
github.com/containers/image github.com/containers/image/copy 
github.com/containers/image/directory 
github.com/containers/image/directory/explicitfilepath 
github.com/containers/image/docker github.com/containers/image/docker/archive 
github.com/containers/image/docker/daemon 
github.com/containers/image/docker/policyconfiguration 
github.com/containers/image/docker/reference 
github.com/containers/image/docker/tarfile github.com/containers/image/image 
github.com/containers/image/internal/pkg/keyctl 
github.com/containers/image/internal/testing/explicitfilepath-tmpdir 
github.com/containers/image/internal/testing/mocks 
github.com/containers/image/internal/tmpdir 
github.com/containers/image/manifest github.com/containers/image/oci 
github.com/containers/image/oci/archive 
github.com/containers/image/oci/internal github.com/containers/image/oci/layout 
github.com/containers/image/pkg/blobinfocache 
github.com/containers/image/pkg/blobinfocache/boltdb 
github.com/containers/image/pkg/blobinfocache/internal/prioritize 
github.com/containers/image/pkg/blobinfocache/internal/test 
github.com/containers/image/pkg/blobinfocache/memory 
github.com/containers/image/pkg/blobinfocache/none 
github.com/containers/image/pkg/compression 
github.com/containers/image/pkg/compression/internal 
github.com/containers/image/pkg/compression/types 
github.com/containers/image/pkg/docker/config 
github.com/containers/image/pkg/strslice 
github.com/containers/image/pkg/sysregistriesv2 
github.com/containers/image/pkg/tlsclientconfig 
github.com/containers/image/signature github.com/containers/image/storage 
github.com/containers/image/tarball github.com/containers/image/transports 
github.com/containers/image/transports/alltransports 
github.com/containers/image/types github.com/containers/image/version
?   github.com/containers/image [no test files]
[...]
=== RUN   TestSessionKeyring
--- FAIL: TestSessionKeyring (0.00s)
keyring_test.go:19: key has been revoked
=== RUN   TestUserKeyring
--- PASS: TestUserKeyring (0.00s)
=== RUN   TestLink
--- FAIL: TestLink (0.00s)
keyring_test.go:85: key has been revoked
=== RUN   TestUnlink
--- FAIL: TestUnlink (0.00s)
keyring_test.go:129: key has been revoked
=== RUN   TestReadKeyring
--- PASS: TestReadKeyring (0.00s)
=== RUN   TestDescribe
--- PASS: TestDescribe (0.00s)
FAIL
FAILgithub.com/containers/image/internal/pkg/keyctl 0.003s
?   github.com/containers/image/internal/testing/explicitfilepath-tmpdir
[no test files]
?   github.com/containers/image/internal/testing/mocks  [no test files]
?   github.com/containers/image/internal/tmpdir [no test files]
[...]
ok  github.com/containers/image/transports/alltransports0.036s
?   github.com/containers/image/types   [no test files]
?   github.com/containers/image/version [no test files]
FAIL
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 3 
github.com/containers/image github.com/containers/image/copy 
github.com/containers/image/directory 
github.com/containers/image/directory/explicitfilepath 
github.com/containers/image/docker github.com/containers/image/docker/archive 
github.com/containers/image/docker/daemon 
github.com/containers/image/docker/policyconfiguration 
github.com/containers/image/docker/reference 
github.com/containers/image/docker/tarfile github.com/containers/image/image 
github.com/containers/image/internal/pkg/keyctl 
github.com/containers/image/internal/testing/explicitfilepath-tmpdir 
github.com/containers/image/internal/testing/mocks

Bug#947446: closed by Rene Engelhard (Bug#947446: fixed in libreoffice 1:6.4.0~rc1-3)

2020-01-02 Thread Andreas Beckmann

Control: reopen -1
Control: found -1 1:6.4.0~rc1-5

Hi Rene,

it looks like ure is still shipping (some of) the files that were split 
out to separate packages:

  Selecting previously unselected package ure.
  Preparing to unpack .../08-ure_6.4.0~rc1-5_amd64.deb ...
  Unpacking ure (6.4.0~rc1-5) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-p2iEE9/08-ure_6.4.0~rc1-5_amd64.deb (--unpack):
   trying to overwrite '/usr/share/java/juh.jar', which is also in package 
libjuh-java 1:6.4.0~rc1-5

Similarily for libjurt-java, libridl-java, libunoloader-java in sid.

Don't forget to bump the B+R against ure to a version that is no longer
shipping them.

Andreas

Processed: Re: Bug#947446 closed by Rene Engelhard (Bug#947446: fixed in libreoffice 1:6.4.0~rc1-3)

Processing control commands:

> reopen -1
Bug #947446 {Done: Rene Engelhard } [src:libreoffice] 
libreoffice: ure split lacks proper versioned Breaks+Replaces
'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 libreoffice/1:6.4.0~rc1-3.
> found -1 1:6.4.0~rc1-5
Bug #947446 [src:libreoffice] libreoffice: ure split lacks proper versioned 
Breaks+Replaces
Marked as found in versions libreoffice/1:6.4.0~rc1-5.

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

Processed: Bug#947486 marked as pending in golang-github-containers-image

Processing control commands:

> tag -1 pending
Bug #947486 [src:golang-github-containers-image] 
golang-github-containers-image: FTBFS with test failures
Added tag(s) pending.

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

Bug#947486: marked as pending in golang-github-containers-image

2020-01-02 Thread Dmitry Smirnov

Control: tag -1 pending

Hello,

Bug #947486 in golang-github-containers-image reported by you has been fixed in 
the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/go-team/packages/golang-github-containers-image/commit/98b52421f2d7d97b51aef28bb1f875a6f811c818


"golang-github-coreos-bbolt-dev (>= 1.3.3~)" (Closes: #947486)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/947486

Bug#945392: hyperkitty: diff for NMU version 1.3.0-1.1

2020-01-02 Thread Sandro Tosi




Dear maintainer,

I've prepared an NMU for hyperkitty (versioned as 1.3.0-1.1). The diff
is attached to this message.

Regards.

diff -Nru hyperkitty-1.3.0/debian/changelog hyperkitty-1.3.0/debian/changelog
--- hyperkitty-1.3.0/debian/changelog	2019-10-27 08:21:44.0 -0400
+++ hyperkitty-1.3.0/debian/changelog	2020-01-02 16:17:27.0 -0500
@@ -1,3 +1,11 @@
+hyperkitty (1.3.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/MR201.patch
+- make hyperkitty compatible with networkx 2.4; Closes: #945392
+
+ -- Sandro Tosi   Thu, 02 Jan 2020 16:17:27 -0500
+
 hyperkitty (1.3.0-1) unstable; urgency=medium
 
   [ Jonas Meurer ]
diff -Nru hyperkitty-1.3.0/debian/patches/MR201.patch hyperkitty-1.3.0/debian/patches/MR201.patch
--- hyperkitty-1.3.0/debian/patches/MR201.patch	1969-12-31 19:00:00.0 -0500
+++ hyperkitty-1.3.0/debian/patches/MR201.patch	2020-01-02 16:16:44.0 -0500
@@ -0,0 +1,47 @@
+From c95c00276000f48f1ac2d211450f54454e74fe9c Mon Sep 17 00:00:00 2001
+From: Abhilash Raj 
+Date: Sun, 17 Nov 2019 19:17:45 -0800
+Subject: [PATCH] Fix for networkx 2.4
+
+---
+ hyperkitty/lib/analysis.py | 4 ++--
+ setup.py   | 2 +-
+ 2 files changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/hyperkitty/lib/analysis.py b/hyperkitty/lib/analysis.py
+index 87120fba..cfaba7a3 100644
+--- a/hyperkitty/lib/analysis.py
 b/hyperkitty/lib/analysis.py
+@@ -34,14 +34,14 @@ def compute_thread_order_and_depth(thread):
+ thread_pos = {"d": 0, "o": 0}  # depth, order
+ 
+ def walk_successors(msgid):
+-obj = graph.node[msgid]["obj"]
++obj = graph.nodes[msgid]["obj"]
+ obj.thread_depth = thread_pos["d"]
+ obj.thread_order = thread_pos["o"]
+ obj.save(update_fields=["thread_depth", "thread_order"])
+ thread_pos["d"] += 1
+ thread_pos["o"] += 1
+ for succ in sorted(graph.successors(msgid),
+-   key=lambda m: graph.node[m]["num"]):
++   key=lambda m: graph.nodes[m]["num"]):
+ walk_successors(succ)
+ thread_pos["d"] -= 1
+ for index, email in enumerate(thread.emails.order_by("date")):
+diff --git a/setup.py b/setup.py
+index 1844d7f7..48a30c95 100755
+--- a/setup.py
 b/setup.py
+@@ -46,7 +46,7 @@ REQUIRES = [
+ "django-compressor>=1.3",
+ "mailmanclient>=3.1.1",
+ "python-dateutil >= 2.0",
+-"networkx>=1.9.1",
++"networkx>=2.0",
+ "django-haystack>=2.8.0",
+ "django-extensions>=1.3.7",
+ "flufl.lock",
+-- 
+2.24.1
+
diff -Nru hyperkitty-1.3.0/debian/patches/series hyperkitty-1.3.0/debian/patches/series
--- hyperkitty-1.3.0/debian/patches/series	2019-10-27 07:55:34.0 -0400
+++ hyperkitty-1.3.0/debian/patches/series	2020-01-02 16:16:44.0 -0500
@@ -1,3 +1,4 @@
 0001_README_remove_embedded_images.patch
 0002_Use_python3_by_default.patch
 0003-run-sassc-at-build-time.patch
+MR201.patch

Bug#934949: clips: build-depends on removed package pdf2htmlex

Dear Javier,

On Sat, 17 Aug 2019 09:11:28 +0200 Ralf Treinen  wrote:
> Source: clips
> Version: pdf2htmlex
> Severity: serious
> Version: 6.30-4
> User: trei...@debian.org
> Usertags: edos-uninstallable
> 
> Hi,
> 
> clips build-depends on pdf2htmlex which was removed from unstable on
> 2019-04-01.

I expect that you didn't receive this message due to bug #881009. Can
you please fix your package? It didn't migrate to testing for over two
years.

Paul

signature.asc
Description: OpenPGP digital signature

Processed: py2removal blocks updates - 2020-01-02 21:36:22.264749+00:00

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # python-click
> block 937648 by 936731
Bug #937648 [src:python-click] python-click: Python2 removal in sid/bullseye
937648 was blocked by: 936779 936473 938672 936522 938227 937605 938408 936120 
937144
937648 was blocking: 937558 937695 938168 938355
Added blocking bug(s) of 937648: 936731
>
End of message, stopping processing here.

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

Bug#895967: marked as done (python3-flask-socketio: Traceback on import)

Your message dated Thu, 02 Jan 2020 21:20:15 +
with message-id 
and subject line Bug#895967: fixed in flask-socketio 4.2.1-1
has caused the Debian Bug report #895967,
regarding python3-flask-socketio: Traceback on import
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.)


-- 
895967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-flask-socketio
Version: 2.9.0-1
Severity: important

Dear Maintainer,

I was trying to use this package but it fails on import missing some
dependency.

>>> import flask_socketio
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/flask_socketio/__init__.py", line 16, in

import socketio
ModuleNotFoundError: No module named 'socketio'



-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-0.bpo.3-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_PE.utf8, LC_CTYPE=es_PE.utf8 (charmap=UTF-8), LANGUAGE=es_PE:es 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: flask-socketio
Source-Version: 4.2.1-1

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

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

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

Debian distribution maintenance software
pp.
Paulo Henrique de Lima Santana (phls)  (supplier of updated 
flask-socketio 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, 02 Jan 2020 22:32:06 +0300
Source: flask-socketio
Architecture: source
Version: 4.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Paulo Henrique de Lima Santana (phls) 
Changed-By: Paulo Henrique de Lima Santana (phls) 
Closes: 879631 895967 896360 943059
Changes:
 flask-socketio (4.2.1-1) unstable; urgency=medium
 .
   * New upstream version 4.2.1.
   * debian/control:
   - Added Conflicts field to remove gevent-socketio software.
   - Added 'Rules-Requires-Root: no' in source stanza.
   - Added Vcs-* fields for repository in salsa.
   - Build-Depends: removed python3-engineio and python-socketio, and added
 python3-socketio. (Closes: #879631, #895967, 896360, #943059).
   - Bumped Standards-Version to 4.4.1.
   - Bumped X-Python3-Version to 3.7.
   - Changed Maintainer's email.
   - New format to debhelper-compat and updated level to 12.
   * debian/copyright:
   - Changed Maintainer's email.
   - Listed all upstream files in copyright.
   - Updated upstream code and packaging copyrights years.
   * debian/manpages: created.
   * debian/upstream/metadata: created.
Checksums-Sha1:
 34783d92f8eb0c6f05192a39133992318eecbc06 2036 flask-socketio_4.2.1-1.dsc
 3147a0595e196812d33b813e2eaf79c45715ed46 14682 flask-socketio_4.2.1.orig.tar.gz
 11f19c038fa82ed007a8fd7823ce30ed283b82ea 17856 
flask-socketio_4.2.1-1.debian.tar.xz
 3953788773671d1e8898ec3d0c1aadd6efb4daf9 6190 
flask-socketio_4.2.1-1_source.buildinfo
Checksums-Sha256:
 e20afe27885fb1ca119cfbd658e36e85410b6b65ad0588e84b225423bcf9c4bd 2036 
flask-socketio_4.2.1-1.dsc
 2172dff1e42415ba480cee02c30c2fc833671ff326f1598ee3d69aa02cf768ec 14682 
flask-socketio_4.2.1.orig.tar.gz
 1ec13ce9180a1a39d4d7d3988f99a39f52c6251dd9ca96f693841b8c656644a5 17856 
flask-socketio_4.2.1-1.debian.tar.xz
 f1283ee86082462d5b398baa6c74b11cd725a273d73dcd8b726b0cdd391b56e8 6190 
flask-socketio_4.2.1-1_source.buildinfo
Files:
 b37f0bb4ab9afee39ad55931f8962489 2036 python optional 
flask-socketio_4.2.1-1.dsc
 b23222fb7dd2f0676d78bbe24153fd80 14682 python optional 
flask-socketio_4.2.1.orig.tar.gz
 89cfb8ab47701143db3620f105ff0423 17856 python optional 
flask-socketio_4.2.1-1.debian.tar.xz
 1ca16a0382e4677a6f811c3492eb7784 6190 python optional 
flask-socketio_4.2.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEQySpKy57hdp/nJxAxm0GtARDxFAFAl4OWaYACgkQxm0GtARD
xFCZig//fp1ejiV6Q2MuQ0PbYw0PFDSxvz+e0JFPx7TBa2e9VI+1+tw2MJK3uaj9

Bug#896360: marked as done (python3-flask-socketio: flask_socketio fails to import)

Your message dated Thu, 02 Jan 2020 21:20:15 +
with message-id 
and subject line Bug#896360: fixed in flask-socketio 4.2.1-1
has caused the Debian Bug report #896360,
regarding python3-flask-socketio: flask_socketio fails to import
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.)


-- 
896360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-flask-socketio
Version: 2.9.0-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-flask-socketio importing the module flask_socketio
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/flask_socketio/__init__.py", line 16, in 

import socketio
ModuleNotFoundError: No module named 'socketio'

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: flask-socketio
Source-Version: 4.2.1-1

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

Debian distribution maintenance software
pp.
Paulo Henrique de Lima Santana (phls)  (supplier of updated 
flask-socketio 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, 02 Jan 2020 22:32:06 +0300
Source: flask-socketio
Architecture: source
Version: 4.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Paulo Henrique de Lima Santana (phls) 
Changed-By: Paulo Henrique de Lima Santana (phls) 
Closes: 879631 895967 896360 943059
Changes:
 flask-socketio (4.2.1-1) unstable; urgency=medium
 .
   * New upstream version 4.2.1.
   * debian/control:
   - Added Conflicts field to remove gevent-socketio software.
   - Added 'Rules-Requires-Root: no' in source stanza.
   - Added Vcs-* fields for repository in salsa.
   - Build-Depends: removed python3-engineio and python-socketio, and added
 python3-socketio. (Closes: #879631, #895967, 896360, #943059).
   - Bumped Standards-Version to 4.4.1.
   - Bumped X-Python3-Version to 3.7.
   - Changed Maintainer's email.
   - New format to debhelper-compat and updated level to 12.
   * debian/copyright:
   - Changed Maintainer's email.
   - Listed all upstream files in copyright.
   - Updated upstream code and packaging copyrights years.
   * debian/manpages: created.
   * debian/upstream/metadata: created.
Checksums-Sha1:
 34783d92f8eb0c6f05192a39133992318eecbc06 2036 flask-socketio_4.2.1-1.dsc
 3147a0595e196812d33b813e2eaf79c45715ed46 14682 flask-socketio_4.2.1.orig.tar.gz
 11f19c038fa82ed007a8fd7823ce30ed283b82ea 17856 
flask-socketio_4.2.1-1.debian.tar.xz
 3953788773671d1e8898ec3d0c1aadd6efb4daf9 6190 
flask-socketio_4.2.1-1_source.buildinfo
Checksums-Sha256:
 e20afe27885fb1ca119cfbd658e36e85410b6b65ad0588e84b225423bcf9c4bd 2036 
flask-socketio_4.2.1-1.dsc
 2172dff1e42415ba480cee02c30c2fc833671ff326f1598ee3d69aa02cf768ec 14682 
flask-socketio_4.2.1.orig.tar.gz
 1ec13ce9180a1a39d4d7d3988f99a39f52c6251dd9ca96f693841b8c656644a5 17856 
flask-socketio_4.2.1-1.debian.tar.xz
 f1283ee86082462d5b398baa6c74b11cd725a273d73dcd8b726b0cdd391b56e8 6190 
flask-socketio_4.2.1-1_source.buildinfo
Files:
 b37f0bb4ab9afee39ad55931f8962489 2036 python optional 
flask-socketio_4.2.1-1.dsc
 b23222fb7dd2f0676d78bbe24153fd80 14682 python optional 
flask-socketio_4.2.1.orig.tar.gz
 89cfb8ab47701143db3620f105ff0423 17856 python optional 
flask-socketio_4.2.1-1.debian.tar.xz
 1ca16a0382e4677a6f811c3492eb7784 6190 python optional 
flask-socketio_4.2.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#921502: marked as done (latexdiff BD/Recommends texlive-generic-recommended)

Your message dated Thu, 02 Jan 2020 21:20:35 +
with message-id 
and subject line Bug#921502: fixed in latexdiff 1.3.0-2
has caused the Debian Bug report #921502,
regarding latexdiff BD/Recommends texlive-generic-recommended
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.)


-- 
921502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: latexdiff
Version: 1.3.0-1
Severity: normal
Tags: patch

This package should Recommends: texlive-plain-generic rather than
texlive-generic-recommended as texlive has changed the package name,
and texlive-generic-recommended is now just a transitional package.

Best wishes,

   Julian

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

Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages latexdiff depends on:
ii  perl  5.28.1-4

Versions of packages latexdiff recommends:
pn  texlive-generic-recommended  
ii  texlive-latex-base   2018.20190131-1
ii  texlive-latex-extra  2018.20190131-1
ii  texlive-latex-recommended2018.20190131-1

Versions of packages latexdiff suggests:
ii  cvs 2:1.12.13+real-26
ii  git 1:2.20.1-2
ii  mercurial   4.8.2-1
ii  rcs 5.9.4-4
ii  subversion  1.10.4-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: latexdiff
Source-Version: 1.3.0-2

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated latexdiff package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu,  2 Jan 2020 22:04:10 CET
Source: latexdiff
Binary: 
Architecture: source
Version: 1.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Description: 
Closes: 921502
Changes:
 latexdiff (1.3.0-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Peter Pentchev ]
   * Recommend texlive-plain-generic instead of texlive-generic-
 recommended.
 Reported by: Julian Gilbey 
 Closes: #921502
   * Add "Rules-Requires-Root: no" to the source control stanza.
 .
   [ gregor herrmann ]
   * Declare compliance with Debian Policy 4.4.1.
   * Bump debhelper-compat to 12.
   * debian/watch: use uscan version 4.
   * Set upstream metadata fields: Bug-Submit.
   * Remove obsolete fields Contact, Name from debian/upstream/metadata.
Checksums-Sha256: 
 b2bfbd34448724d1406829a6348e86a9359634dbb5868b4209b8efede779bc99 2173 
latexdiff_1.3.0-2.dsc
 8bd927df44ecf8d138e87c7d8859539841cfac8a12fc911c64c798c5be33622d 6228 
latexdiff_1.3.0-2.debian.tar.xz
 4b9b395d34b10d7f1b224f817c75ac79acfd82cca23530849cf8a05ff759 6982 
latexdiff_1.3.0-2_sourceonly.buildinfo
Checksums-Sha1: 
 b6a1299482eb26fdb278aab3dbafcf1132401892 2173 latexdiff_1.3.0-2.dsc
 1b21f0d25a8b03f1c9d24a04463d805b8e8f1127 6228 latexdiff_1.3.0-2.debian.tar.xz
 181d43a7e7b02b57fc5f33621572ee7f9db4d994 6982 
latexdiff_1.3.0-2_sourceonly.buildinfo
Files: 
 89ded1a71c5a962a7b47e6dd35be09f1 2173 tex optional latexdiff_1.3.0-2.dsc
 294c1d328a51608ad9e85b75f032291e 6228 tex optional 
latexdiff_1.3.0-2.debian.tar.xz
 0b3f04e5eb800063c2badf45e3017539 6982 - - 
latexdiff_1.3.0-2_sourceonly.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl4OWstfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZlag/+MRJTeU/dLYFCJF8Ye+iztpMhEHDlB2fWIBZRDj7lHDRWZ4hqhI73g7+S

Bug#896360: marked as done (python3-flask-socketio: flask_socketio fails to import)

Your message dated Thu, 02 Jan 2020 21:20:15 +
with message-id 
and subject line Bug#895967: fixed in flask-socketio 4.2.1-1
has caused the Debian Bug report #895967,
regarding python3-flask-socketio: flask_socketio fails to import
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.)


-- 
895967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-flask-socketio
Version: 2.9.0-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-flask-socketio importing the module flask_socketio
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/flask_socketio/__init__.py", line 16, in 

import socketio
ModuleNotFoundError: No module named 'socketio'

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: flask-socketio
Source-Version: 4.2.1-1

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

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

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

Debian distribution maintenance software
pp.
Paulo Henrique de Lima Santana (phls)  (supplier of updated 
flask-socketio 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, 02 Jan 2020 22:32:06 +0300
Source: flask-socketio
Architecture: source
Version: 4.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Paulo Henrique de Lima Santana (phls) 
Changed-By: Paulo Henrique de Lima Santana (phls) 
Closes: 879631 895967 896360 943059
Changes:
 flask-socketio (4.2.1-1) unstable; urgency=medium
 .
   * New upstream version 4.2.1.
   * debian/control:
   - Added Conflicts field to remove gevent-socketio software.
   - Added 'Rules-Requires-Root: no' in source stanza.
   - Added Vcs-* fields for repository in salsa.
   - Build-Depends: removed python3-engineio and python-socketio, and added
 python3-socketio. (Closes: #879631, #895967, 896360, #943059).
   - Bumped Standards-Version to 4.4.1.
   - Bumped X-Python3-Version to 3.7.
   - Changed Maintainer's email.
   - New format to debhelper-compat and updated level to 12.
   * debian/copyright:
   - Changed Maintainer's email.
   - Listed all upstream files in copyright.
   - Updated upstream code and packaging copyrights years.
   * debian/manpages: created.
   * debian/upstream/metadata: created.
Checksums-Sha1:
 34783d92f8eb0c6f05192a39133992318eecbc06 2036 flask-socketio_4.2.1-1.dsc
 3147a0595e196812d33b813e2eaf79c45715ed46 14682 flask-socketio_4.2.1.orig.tar.gz
 11f19c038fa82ed007a8fd7823ce30ed283b82ea 17856 
flask-socketio_4.2.1-1.debian.tar.xz
 3953788773671d1e8898ec3d0c1aadd6efb4daf9 6190 
flask-socketio_4.2.1-1_source.buildinfo
Checksums-Sha256:
 e20afe27885fb1ca119cfbd658e36e85410b6b65ad0588e84b225423bcf9c4bd 2036 
flask-socketio_4.2.1-1.dsc
 2172dff1e42415ba480cee02c30c2fc833671ff326f1598ee3d69aa02cf768ec 14682 
flask-socketio_4.2.1.orig.tar.gz
 1ec13ce9180a1a39d4d7d3988f99a39f52c6251dd9ca96f693841b8c656644a5 17856 
flask-socketio_4.2.1-1.debian.tar.xz
 f1283ee86082462d5b398baa6c74b11cd725a273d73dcd8b726b0cdd391b56e8 6190 
flask-socketio_4.2.1-1_source.buildinfo
Files:
 b37f0bb4ab9afee39ad55931f8962489 2036 python optional 
flask-socketio_4.2.1-1.dsc
 b23222fb7dd2f0676d78bbe24153fd80 14682 python optional 
flask-socketio_4.2.1.orig.tar.gz
 89cfb8ab47701143db3620f105ff0423 17856 python optional 
flask-socketio_4.2.1-1.debian.tar.xz
 1ca16a0382e4677a6f811c3492eb7784 6190 python optional 
flask-socketio_4.2.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#895967: marked as done (python3-flask-socketio: Traceback on import)

Your message dated Thu, 02 Jan 2020 21:20:15 +
with message-id 
and subject line Bug#879631: fixed in flask-socketio 4.2.1-1
has caused the Debian Bug report #879631,
regarding python3-flask-socketio: Traceback on import
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.)


-- 
879631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-flask-socketio
Version: 2.9.0-1
Severity: important

Dear Maintainer,

I was trying to use this package but it fails on import missing some
dependency.

>>> import flask_socketio
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/flask_socketio/__init__.py", line 16, in

import socketio
ModuleNotFoundError: No module named 'socketio'



-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-0.bpo.3-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_PE.utf8, LC_CTYPE=es_PE.utf8 (charmap=UTF-8), LANGUAGE=es_PE:es 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: flask-socketio
Source-Version: 4.2.1-1

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

Debian distribution maintenance software
pp.
Paulo Henrique de Lima Santana (phls)  (supplier of updated 
flask-socketio 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, 02 Jan 2020 22:32:06 +0300
Source: flask-socketio
Architecture: source
Version: 4.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Paulo Henrique de Lima Santana (phls) 
Changed-By: Paulo Henrique de Lima Santana (phls) 
Closes: 879631 895967 896360 943059
Changes:
 flask-socketio (4.2.1-1) unstable; urgency=medium
 .
   * New upstream version 4.2.1.
   * debian/control:
   - Added Conflicts field to remove gevent-socketio software.
   - Added 'Rules-Requires-Root: no' in source stanza.
   - Added Vcs-* fields for repository in salsa.
   - Build-Depends: removed python3-engineio and python-socketio, and added
 python3-socketio. (Closes: #879631, #895967, 896360, #943059).
   - Bumped Standards-Version to 4.4.1.
   - Bumped X-Python3-Version to 3.7.
   - Changed Maintainer's email.
   - New format to debhelper-compat and updated level to 12.
   * debian/copyright:
   - Changed Maintainer's email.
   - Listed all upstream files in copyright.
   - Updated upstream code and packaging copyrights years.
   * debian/manpages: created.
   * debian/upstream/metadata: created.
Checksums-Sha1:
 34783d92f8eb0c6f05192a39133992318eecbc06 2036 flask-socketio_4.2.1-1.dsc
 3147a0595e196812d33b813e2eaf79c45715ed46 14682 flask-socketio_4.2.1.orig.tar.gz
 11f19c038fa82ed007a8fd7823ce30ed283b82ea 17856 
flask-socketio_4.2.1-1.debian.tar.xz
 3953788773671d1e8898ec3d0c1aadd6efb4daf9 6190 
flask-socketio_4.2.1-1_source.buildinfo
Checksums-Sha256:
 e20afe27885fb1ca119cfbd658e36e85410b6b65ad0588e84b225423bcf9c4bd 2036 
flask-socketio_4.2.1-1.dsc
 2172dff1e42415ba480cee02c30c2fc833671ff326f1598ee3d69aa02cf768ec 14682 
flask-socketio_4.2.1.orig.tar.gz
 1ec13ce9180a1a39d4d7d3988f99a39f52c6251dd9ca96f693841b8c656644a5 17856 
flask-socketio_4.2.1-1.debian.tar.xz
 f1283ee86082462d5b398baa6c74b11cd725a273d73dcd8b726b0cdd391b56e8 6190 
flask-socketio_4.2.1-1_source.buildinfo
Files:
 b37f0bb4ab9afee39ad55931f8962489 2036 python optional 
flask-socketio_4.2.1-1.dsc
 b23222fb7dd2f0676d78bbe24153fd80 14682 python optional 
flask-socketio_4.2.1.orig.tar.gz
 89cfb8ab47701143db3620f105ff0423 17856 python optional 
flask-socketio_4.2.1-1.debian.tar.xz
 1ca16a0382e4677a6f811c3492eb7784 6190 python optional 
flask-socketio_4.2.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEQySpKy57hdp/nJxAxm0GtARDxFAFAl4OWaYACgkQxm0GtARD
xFCZig//fp1ejiV6Q2MuQ0PbYw0PFDSxvz+e0JFPx7TBa2e9VI+1+tw2MJK3uaj9

Bug#895967: marked as done (python3-flask-socketio: Traceback on import)

Your message dated Thu, 02 Jan 2020 21:20:15 +
with message-id 
and subject line Bug#896360: fixed in flask-socketio 4.2.1-1
has caused the Debian Bug report #896360,
regarding python3-flask-socketio: Traceback on import
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.)


-- 
896360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-flask-socketio
Version: 2.9.0-1
Severity: important

Dear Maintainer,

I was trying to use this package but it fails on import missing some
dependency.

>>> import flask_socketio
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/flask_socketio/__init__.py", line 16, in

import socketio
ModuleNotFoundError: No module named 'socketio'



-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-0.bpo.3-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_PE.utf8, LC_CTYPE=es_PE.utf8 (charmap=UTF-8), LANGUAGE=es_PE:es 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: flask-socketio
Source-Version: 4.2.1-1

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

Debian distribution maintenance software
pp.
Paulo Henrique de Lima Santana (phls)  (supplier of updated 
flask-socketio 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, 02 Jan 2020 22:32:06 +0300
Source: flask-socketio
Architecture: source
Version: 4.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Paulo Henrique de Lima Santana (phls) 
Changed-By: Paulo Henrique de Lima Santana (phls) 
Closes: 879631 895967 896360 943059
Changes:
 flask-socketio (4.2.1-1) unstable; urgency=medium
 .
   * New upstream version 4.2.1.
   * debian/control:
   - Added Conflicts field to remove gevent-socketio software.
   - Added 'Rules-Requires-Root: no' in source stanza.
   - Added Vcs-* fields for repository in salsa.
   - Build-Depends: removed python3-engineio and python-socketio, and added
 python3-socketio. (Closes: #879631, #895967, 896360, #943059).
   - Bumped Standards-Version to 4.4.1.
   - Bumped X-Python3-Version to 3.7.
   - Changed Maintainer's email.
   - New format to debhelper-compat and updated level to 12.
   * debian/copyright:
   - Changed Maintainer's email.
   - Listed all upstream files in copyright.
   - Updated upstream code and packaging copyrights years.
   * debian/manpages: created.
   * debian/upstream/metadata: created.
Checksums-Sha1:
 34783d92f8eb0c6f05192a39133992318eecbc06 2036 flask-socketio_4.2.1-1.dsc
 3147a0595e196812d33b813e2eaf79c45715ed46 14682 flask-socketio_4.2.1.orig.tar.gz
 11f19c038fa82ed007a8fd7823ce30ed283b82ea 17856 
flask-socketio_4.2.1-1.debian.tar.xz
 3953788773671d1e8898ec3d0c1aadd6efb4daf9 6190 
flask-socketio_4.2.1-1_source.buildinfo
Checksums-Sha256:
 e20afe27885fb1ca119cfbd658e36e85410b6b65ad0588e84b225423bcf9c4bd 2036 
flask-socketio_4.2.1-1.dsc
 2172dff1e42415ba480cee02c30c2fc833671ff326f1598ee3d69aa02cf768ec 14682 
flask-socketio_4.2.1.orig.tar.gz
 1ec13ce9180a1a39d4d7d3988f99a39f52c6251dd9ca96f693841b8c656644a5 17856 
flask-socketio_4.2.1-1.debian.tar.xz
 f1283ee86082462d5b398baa6c74b11cd725a273d73dcd8b726b0cdd391b56e8 6190 
flask-socketio_4.2.1-1_source.buildinfo
Files:
 b37f0bb4ab9afee39ad55931f8962489 2036 python optional 
flask-socketio_4.2.1-1.dsc
 b23222fb7dd2f0676d78bbe24153fd80 14682 python optional 
flask-socketio_4.2.1.orig.tar.gz
 89cfb8ab47701143db3620f105ff0423 17856 python optional 
flask-socketio_4.2.1-1.debian.tar.xz
 1ca16a0382e4677a6f811c3492eb7784 6190 python optional 
flask-socketio_4.2.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEQySpKy57hdp/nJxAxm0GtARDxFAFAl4OWaYACgkQxm0GtARD
xFCZig//fp1ejiV6Q2MuQ0PbYw0PFDSxvz+e0JFPx7TBa2e9VI+1+tw2MJK3uaj9

Bug#879631: marked as done (python3-flask-socketio: missing dependency)

Your message dated Thu, 02 Jan 2020 21:20:15 +
with message-id 
and subject line Bug#895967: fixed in flask-socketio 4.2.1-1
has caused the Debian Bug report #895967,
regarding python3-flask-socketio: missing 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.)


-- 
895967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-flask-socketio
Version: 2.9.0-1
Severity: serious

Dear Maintainer,

This package lacks a dependency on the upstream "python-socketio" [0],
which provides a "socketio" module.  Please do not confuse it with the
Debian package of the same name, which also provides a "socketio": that
package is actually "gevent-socketio" [1] and incompatible with
python3-flask-socketio [2].

  0: https://github.com/miguelgrinberg/python-socketio/
  1: https://github.com/abourget/gevent-socketio
  2: From flask_socketio/__init__.py:
   if gevent_socketio_found:
   print('The gevent-socketio package is incompatible with this version 
of '
 'the Flask-SocketIO extension. Please uninstall it, and then '
 'install the latest version of python-socketio in its place.')
   sys.exit(1)

It seems that the required package is not currently packaged in Debian,
unfortunately.  As is, python3-flask-socketio is useless.  Further
justification for "serious" severity: Debian policy manual section 3.5
[3].

  3: https://www.debian.org/doc/debian-policy/#dependencies

Cheers.

PS: The package tracker at  says:

  action needed
  Problems while searching for a new upstream version


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

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

Versions of packages python3-flask-socketio depends on:
ii  python3   3.6.3-1
ii  python3-engineio  1.6.1-1
ii  python3-flask 0.12.2-2

python3-flask-socketio recommends no packages.

python3-flask-socketio suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: flask-socketio
Source-Version: 4.2.1-1

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

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

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

Debian distribution maintenance software
pp.
Paulo Henrique de Lima Santana (phls)  (supplier of updated 
flask-socketio 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, 02 Jan 2020 22:32:06 +0300
Source: flask-socketio
Architecture: source
Version: 4.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Paulo Henrique de Lima Santana (phls) 
Changed-By: Paulo Henrique de Lima Santana (phls) 
Closes: 879631 895967 896360 943059
Changes:
 flask-socketio (4.2.1-1) unstable; urgency=medium
 .
   * New upstream version 4.2.1.
   * debian/control:
   - Added Conflicts field to remove gevent-socketio software.
   - Added 'Rules-Requires-Root: no' in source stanza.
   - Added Vcs-* fields for repository in salsa.
   - Build-Depends: removed python3-engineio and python-socketio, and added
 python3-socketio. (Closes: #879631, #895967, 896360, #943059).
   - Bumped Standards-Version to 4.4.1.
   - Bumped X-Python3-Version to 3.7.
   - Changed Maintainer's email.
   - New format to debhelper-compat and updated level to 12.
   * debian/copyright:
   - Changed Maintainer's email.
   - Listed all upstream files in copyright.
   - Updated upstream code and packaging copyrights years.
   * debian/manpages: created.
   * debian/upstream/metadata: created.
Checksums-Sha1:
 34783d92f8eb0c6f05192a39133992318eecbc06 2036 flask-socketio_4.2.1-1.dsc
 3147a0595e196812d33b813e2eaf79c45715ed46 14682

Bug#879631: marked as done (python3-flask-socketio: missing dependency)

Your message dated Thu, 02 Jan 2020 21:20:15 +
with message-id 
and subject line Bug#896360: fixed in flask-socketio 4.2.1-1
has caused the Debian Bug report #896360,
regarding python3-flask-socketio: missing 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.)


-- 
896360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-flask-socketio
Version: 2.9.0-1
Severity: serious

Dear Maintainer,

This package lacks a dependency on the upstream "python-socketio" [0],
which provides a "socketio" module.  Please do not confuse it with the
Debian package of the same name, which also provides a "socketio": that
package is actually "gevent-socketio" [1] and incompatible with
python3-flask-socketio [2].

  0: https://github.com/miguelgrinberg/python-socketio/
  1: https://github.com/abourget/gevent-socketio
  2: From flask_socketio/__init__.py:
   if gevent_socketio_found:
   print('The gevent-socketio package is incompatible with this version 
of '
 'the Flask-SocketIO extension. Please uninstall it, and then '
 'install the latest version of python-socketio in its place.')
   sys.exit(1)

It seems that the required package is not currently packaged in Debian,
unfortunately.  As is, python3-flask-socketio is useless.  Further
justification for "serious" severity: Debian policy manual section 3.5
[3].

  3: https://www.debian.org/doc/debian-policy/#dependencies

Cheers.

PS: The package tracker at  says:

  action needed
  Problems while searching for a new upstream version


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

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

Versions of packages python3-flask-socketio depends on:
ii  python3   3.6.3-1
ii  python3-engineio  1.6.1-1
ii  python3-flask 0.12.2-2

python3-flask-socketio recommends no packages.

python3-flask-socketio suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: flask-socketio
Source-Version: 4.2.1-1

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

Debian distribution maintenance software
pp.
Paulo Henrique de Lima Santana (phls)  (supplier of updated 
flask-socketio 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, 02 Jan 2020 22:32:06 +0300
Source: flask-socketio
Architecture: source
Version: 4.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Paulo Henrique de Lima Santana (phls) 
Changed-By: Paulo Henrique de Lima Santana (phls) 
Closes: 879631 895967 896360 943059
Changes:
 flask-socketio (4.2.1-1) unstable; urgency=medium
 .
   * New upstream version 4.2.1.
   * debian/control:
   - Added Conflicts field to remove gevent-socketio software.
   - Added 'Rules-Requires-Root: no' in source stanza.
   - Added Vcs-* fields for repository in salsa.
   - Build-Depends: removed python3-engineio and python-socketio, and added
 python3-socketio. (Closes: #879631, #895967, 896360, #943059).
   - Bumped Standards-Version to 4.4.1.
   - Bumped X-Python3-Version to 3.7.
   - Changed Maintainer's email.
   - New format to debhelper-compat and updated level to 12.
   * debian/copyright:
   - Changed Maintainer's email.
   - Listed all upstream files in copyright.
   - Updated upstream code and packaging copyrights years.
   * debian/manpages: created.
   * debian/upstream/metadata: created.
Checksums-Sha1:
 34783d92f8eb0c6f05192a39133992318eecbc06 2036 flask-socketio_4.2.1-1.dsc
 3147a0595e196812d33b813e2eaf79c45715ed46 14682

Bug#896360: marked as done (python3-flask-socketio: flask_socketio fails to import)

Your message dated Thu, 02 Jan 2020 21:20:15 +
with message-id 
and subject line Bug#879631: fixed in flask-socketio 4.2.1-1
has caused the Debian Bug report #879631,
regarding python3-flask-socketio: flask_socketio fails to import
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.)


-- 
879631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-flask-socketio
Version: 2.9.0-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-flask-socketio importing the module flask_socketio
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/flask_socketio/__init__.py", line 16, in 

import socketio
ModuleNotFoundError: No module named 'socketio'

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: flask-socketio
Source-Version: 4.2.1-1

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

Debian distribution maintenance software
pp.
Paulo Henrique de Lima Santana (phls)  (supplier of updated 
flask-socketio 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, 02 Jan 2020 22:32:06 +0300
Source: flask-socketio
Architecture: source
Version: 4.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Paulo Henrique de Lima Santana (phls) 
Changed-By: Paulo Henrique de Lima Santana (phls) 
Closes: 879631 895967 896360 943059
Changes:
 flask-socketio (4.2.1-1) unstable; urgency=medium
 .
   * New upstream version 4.2.1.
   * debian/control:
   - Added Conflicts field to remove gevent-socketio software.
   - Added 'Rules-Requires-Root: no' in source stanza.
   - Added Vcs-* fields for repository in salsa.
   - Build-Depends: removed python3-engineio and python-socketio, and added
 python3-socketio. (Closes: #879631, #895967, 896360, #943059).
   - Bumped Standards-Version to 4.4.1.
   - Bumped X-Python3-Version to 3.7.
   - Changed Maintainer's email.
   - New format to debhelper-compat and updated level to 12.
   * debian/copyright:
   - Changed Maintainer's email.
   - Listed all upstream files in copyright.
   - Updated upstream code and packaging copyrights years.
   * debian/manpages: created.
   * debian/upstream/metadata: created.
Checksums-Sha1:
 34783d92f8eb0c6f05192a39133992318eecbc06 2036 flask-socketio_4.2.1-1.dsc
 3147a0595e196812d33b813e2eaf79c45715ed46 14682 flask-socketio_4.2.1.orig.tar.gz
 11f19c038fa82ed007a8fd7823ce30ed283b82ea 17856 
flask-socketio_4.2.1-1.debian.tar.xz
 3953788773671d1e8898ec3d0c1aadd6efb4daf9 6190 
flask-socketio_4.2.1-1_source.buildinfo
Checksums-Sha256:
 e20afe27885fb1ca119cfbd658e36e85410b6b65ad0588e84b225423bcf9c4bd 2036 
flask-socketio_4.2.1-1.dsc
 2172dff1e42415ba480cee02c30c2fc833671ff326f1598ee3d69aa02cf768ec 14682 
flask-socketio_4.2.1.orig.tar.gz
 1ec13ce9180a1a39d4d7d3988f99a39f52c6251dd9ca96f693841b8c656644a5 17856 
flask-socketio_4.2.1-1.debian.tar.xz
 f1283ee86082462d5b398baa6c74b11cd725a273d73dcd8b726b0cdd391b56e8 6190 
flask-socketio_4.2.1-1_source.buildinfo
Files:
 b37f0bb4ab9afee39ad55931f8962489 2036 python optional 
flask-socketio_4.2.1-1.dsc
 b23222fb7dd2f0676d78bbe24153fd80 14682 python optional 
flask-socketio_4.2.1.orig.tar.gz
 89cfb8ab47701143db3620f105ff0423 17856 python optional 
flask-socketio_4.2.1-1.debian.tar.xz
 1ca16a0382e4677a6f811c3492eb7784 6190 python optional 
flask-socketio_4.2.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#879631: marked as done (python3-flask-socketio: missing dependency)

Your message dated Thu, 02 Jan 2020 21:20:15 +
with message-id 
and subject line Bug#879631: fixed in flask-socketio 4.2.1-1
has caused the Debian Bug report #879631,
regarding python3-flask-socketio: missing 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.)


-- 
879631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-flask-socketio
Version: 2.9.0-1
Severity: serious

Dear Maintainer,

This package lacks a dependency on the upstream "python-socketio" [0],
which provides a "socketio" module.  Please do not confuse it with the
Debian package of the same name, which also provides a "socketio": that
package is actually "gevent-socketio" [1] and incompatible with
python3-flask-socketio [2].

  0: https://github.com/miguelgrinberg/python-socketio/
  1: https://github.com/abourget/gevent-socketio
  2: From flask_socketio/__init__.py:
   if gevent_socketio_found:
   print('The gevent-socketio package is incompatible with this version 
of '
 'the Flask-SocketIO extension. Please uninstall it, and then '
 'install the latest version of python-socketio in its place.')
   sys.exit(1)

It seems that the required package is not currently packaged in Debian,
unfortunately.  As is, python3-flask-socketio is useless.  Further
justification for "serious" severity: Debian policy manual section 3.5
[3].

  3: https://www.debian.org/doc/debian-policy/#dependencies

Cheers.

PS: The package tracker at  says:

  action needed
  Problems while searching for a new upstream version


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

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

Versions of packages python3-flask-socketio depends on:
ii  python3   3.6.3-1
ii  python3-engineio  1.6.1-1
ii  python3-flask 0.12.2-2

python3-flask-socketio recommends no packages.

python3-flask-socketio suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: flask-socketio
Source-Version: 4.2.1-1

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

Debian distribution maintenance software
pp.
Paulo Henrique de Lima Santana (phls)  (supplier of updated 
flask-socketio 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, 02 Jan 2020 22:32:06 +0300
Source: flask-socketio
Architecture: source
Version: 4.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Paulo Henrique de Lima Santana (phls) 
Changed-By: Paulo Henrique de Lima Santana (phls) 
Closes: 879631 895967 896360 943059
Changes:
 flask-socketio (4.2.1-1) unstable; urgency=medium
 .
   * New upstream version 4.2.1.
   * debian/control:
   - Added Conflicts field to remove gevent-socketio software.
   - Added 'Rules-Requires-Root: no' in source stanza.
   - Added Vcs-* fields for repository in salsa.
   - Build-Depends: removed python3-engineio and python-socketio, and added
 python3-socketio. (Closes: #879631, #895967, 896360, #943059).
   - Bumped Standards-Version to 4.4.1.
   - Bumped X-Python3-Version to 3.7.
   - Changed Maintainer's email.
   - New format to debhelper-compat and updated level to 12.
   * debian/copyright:
   - Changed Maintainer's email.
   - Listed all upstream files in copyright.
   - Updated upstream code and packaging copyrights years.
   * debian/manpages: created.
   * debian/upstream/metadata: created.
Checksums-Sha1:
 34783d92f8eb0c6f05192a39133992318eecbc06 2036 flask-socketio_4.2.1-1.dsc
 3147a0595e196812d33b813e2eaf79c45715ed46 14682

Processed: Re: autoconf BD on texlive-generic-recommended which isn't build anymore and isn't in bullseye

Processing control commands:

> tags -1 patch
Bug #947950 [src:autoconf] autoconf BD on texlive-generic-recommended which 
isn't build anymore and isn't in bullseye
Added tag(s) patch.

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

Bug#947969: ceph-mgr: indefinite queue growth causing commands to hang

2020-01-02 Thread Bernd Zeimetz

Hi,

> ceph-mgr queue on large clusters grows indefinitely pushing cpu utilization
> to 100% and causing command execution to hang. For more info see:
>   
>   https://tracker.ceph.com/issues/43364

any idea if this affects 14.2.4?


Bernd


-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Bug#947950: autoconf BD on texlive-generic-recommended which isn't build anymore and isn't in bullseye

Control: tags -1 patch

On 02-01-2020 18:43, Paul Gevers wrote:
> I intent to prepare an NMU and upload it to DELAYED/15 or so, please let
> me know if you will handle this yourself.

I have uploaded the attached changes to DELAYED/15.

Paul
diff --git a/debian/changelog b/debian/changelog
index 9917e79..ece0b6c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+autoconf (2.69-11.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build-Depend on texlive-plain-generic instead of
+texlive-generic-recommended Closes: #947950
+
+ -- Paul Gevers   Thu, 02 Jan 2020 21:24:24 +0100
+
 autoconf (2.69-11) unstable; urgency=medium
 
   * debian/patches/mmap-leak-fix.patch: New patch from upstream commit
diff --git a/debian/control b/debian/control
index 2a7cab4..74653c2 100644
--- a/debian/control
+++ b/debian/control
@@ -4,7 +4,7 @@ Priority: optional
 Maintainer: Ben Pfaff 
 Standards-Version: 3.9.3
 Build-Depends-Indep: texinfo (>= 4.6), m4 (>= 1.4.13),
- texlive-base, texlive-generic-recommended, texlive-latex-base,
+ texlive-base, texlive-plain-generic, texlive-latex-base,
  texlive-latex-recommended, texlive-fonts-recommended, help2man, cm-super
 Build-Depends: debhelper (>= 7.0.50~)
 Homepage: http://www.gnu.org/software/autoconf/


signature.asc
Description: OpenPGP digital signature

Bug#947969: ceph-mgr: indefinite queue growth causing commands to hang

2020-01-02 Thread Milan Kupcevic

Package: ceph-mgr
Version: 14.2.5-1
Severity: serious
Tags: upstream
Forwarded: https://tracker.ceph.com/issues/43364

ceph-mgr queue on large clusters grows indefinitely pushing cpu utilization
to 100% and causing command execution to hang. For more info see:
  
  https://tracker.ceph.com/issues/43364


Milan

Processed: severity of 947964 is serious

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

> severity 947964 serious
Bug #947964 [src:gatb-core] gatb-core: hardcoded libcppunit-1.14-0 (and 
libhdf5-103) dependency instead of shlibs:Depends
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: re: python-click: Python2 removal in sid/bullseye

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

> unblock 937648 by 936731
Bug #937648 [src:python-click] python-click: Python2 removal in sid/bullseye
937648 was blocked by: 936779 936120 936522 936473 937605 938227 938672 938408 
936731 937144
937648 was blocking: 937558 937695 938168 938355
Removed blocking bug(s) of 937648: 936731
> thanks
Stopping processing here.

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

Processed: severity of 941266 is grave

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

> severity 941266 grave
Bug #941266 [src:netty] netty: CVE-2019-16869
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#929954: marked as done ([python-reportlab] 3.5.21-1 breaks rst2pdf)

Your message dated Thu, 02 Jan 2020 18:35:28 +
with message-id 
and subject line Bug#929954: fixed in rst2pdf 0.95-1
has caused the Debian Bug report #929954,
regarding [python-reportlab] 3.5.21-1 breaks rst2pdf
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.)


-- 
929954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-reportlab
Version: 3.5.21-1
Severity: grave

--- Please enter the report below this line. ---
Dear maintainer,

Since last update of python-reportlab to 3.2.21-1, rst2pdf is unusable :

$ rst2pdf test.rst -o test.pdf
Traceback (most recent call last):
  File "/usr/bin/rst2pdf", line 11, in 
load_entry_point('rst2pdf==0.93.dev0', 'console_scripts', 'rst2pdf')()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line
489, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line
2793, in load_entry_point
return ep.load()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line
2411, in load
return self.resolve()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line
2417, in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python2.7/dist-packages/rst2pdf/createpdf.py", line 85, in

from rst2pdf import flowables
  File "/usr/lib/python2.7/dist-packages/rst2pdf/flowables.py", line 875,
in 
if reportlab.Version == '2.1':
NameError: name 'reportlab' is not defined

I use a minimal rst test.rst file :

#

Tests

#


This is just a test.


Installing testing 3.5.13-1 version of python-reportlab works.


I'm not sure on which package to report this bug, python-reportlab or
rst2pdf.


Regards,


Sébastien KALT


 --- System information. ---
Architecture:
Kernel: Linux 4.19.0-5-amd64

Debian Release: 10.0
980 unstable ftp.fr.debian.org
970 testing ftp.fr.debian.org
500 testing-debug debug.mirrors.debian.org
500 stable dl.google.com
500 oldstable ftp.fr.debian.org
1 experimental-debug debug.mirrors.debian.org

--- Package information. ---
Depends (Version) | Installed
-+-==
python-pil | 5.4.1-2
python:any (<< 2.8) |
python:any (>= 2.7~) |
python-reportlab-accel (>= 3.5.21-1) | 3.5.21-1


Recommends (Version) | Installed
==-+-===
python-renderpm |


Suggests (Version) | Installed
-+-===
pdf-viewer |
python-egenix-mxtexttools (>= 2.0.6-3.1) |
python-reportlab-doc |
--- End Message ---
--- Begin Message ---
Source: rst2pdf
Source-Version: 0.95-1

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated rst2pdf 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, 02 Jan 2020 13:21:05 -0500
Source: rst2pdf
Binary: rst2pdf
Architecture: source all
Version: 0.95-1
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Sandro Tosi 
Description:
 rst2pdf- ReportLab-based reStructuredText to PDF renderer
Closes: 876681 929954 938416
Changes:
 rst2pdf (0.95-1) unstable; urgency=medium
 .
   [ Elena Grandi ]
   * Drop fix_invariant_dates.patch merged upstream.
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
   * d/control: Fix wrong Vcs-*.
 .
   [ Sandro Tosi ]
   * New upstream release; Closes: #929954
   * debian/control
 - add myself to Uploaders; will help out with this package; Closes: #876681
 - add fontconfig, jinja2, matplotlib, smartypants, six to b-d, needed by 
doc
 - update Homepage field
   * debian/copyright
 - add myself to Debian packaging contributions
 - update upstream copyright notice (by running `cme update dpkg-copyright`
   and then manually fixing it)
   * Switch to python3; Closes: #938416
   *

Bug#943600: [Pkg-pascal-devel] Bug#943600: Bug#943600: lazarus autopkgtest intermittedly fails due to EAccessViolation: Access violation

2020-01-02 Thread Graham Inggs

As of now, lazarus 2.0.6+dfsg-3 has failed its autopkgtests 2 out of
11 times on amd64 [1], and 3 out of 11 times on arm64 [2].

I am hesitant to re-open this bug as RC, as it potentially removes all
packages built with lazarus for no good reason.


[1] https://ci.debian.net/packages/l/lazarus/testing/amd64/
[2] https://ci.debian.net/packages/l/lazarus/testing/arm64/

Processed: Bug#929954 marked as pending in pdfposter

Processing control commands:

> tag -1 pending
Bug #929954 [rst2pdf] [python-reportlab] 3.5.21-1 breaks rst2pdf
Added tag(s) pending.

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

Processed: Re: khotkeys FTBFS

Processing control commands:

> forwarded -1 
> https://salsa.debian.org/qt-kde-team/kde/khotkeys/merge_requests/2
Bug #946327 [src:khotkeys] khotkeys FTBFS: error: no matching function for call 
to ‘KDialog::KDialog(QWidget*&)’
Set Bug forwarded-to-address to 
'https://salsa.debian.org/qt-kde-team/kde/khotkeys/merge_requests/2'.
> tags -1 patch
Bug #946327 [src:khotkeys] khotkeys FTBFS: error: no matching function for call 
to ‘KDialog::KDialog(QWidget*&)’
Added tag(s) patch.

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

Bug#929954: marked as pending in pdfposter

2020-01-02 Thread Sandro Tosi

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/applications/rst2pdf/commit/be3c2f27c57af94364424dcb745e6a4ebbfb7ef9


New upstream release; Closes: #929954


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/929954

Bug#946327: khotkeys FTBFS

2020-01-02 Thread John Scott

Control: forwarded -1 
https://salsa.debian.org/qt-kde-team/kde/khotkeys/merge_requests/2
Control: tags -1 patch

This is fixed in KHotKeys 5.15.1. Alternatively, I've submitted a merge request
to enable a potential new upload of 5.14.5 with the patch.


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

Processed: Re: Processed (with 1 error): Re: Bug #921502 in latexdiff marked as pending

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

> # Oops
> severity 921502 serious
Bug #921502 [latexdiff] latexdiff BD/Recommends texlive-generic-recommended
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#947950: autoconf BD on texlive-generic-recommended which isn't build anymore and isn't in bullseye

Source: autoconf
Version: 2.69-11
Severity: serious
Tags: ftbfs sid bullseye

Somewhere around August 2019, the texlive-base package has stopped
building the transitional package texlive-generic-recommended. This is
an issue for your package as it build-depends on it. Please update the
building of your package to use texlive-plain-generic instead.

Unfortunately the migration software doesn't detected this kind of
situation yet, so your package also FTBFS in bullseye since 2019-08-31.

I intent to prepare an NMU and upload it to DELAYED/15 or so, please let
me know if you will handle this yourself.

Paul



signature.asc
Description: OpenPGP digital signature

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

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

> #
> # bts-link upstream status pull for source package src:phamm
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #924731 (http://bugs.debian.org/924731)
> # Bug title: phamm: CVE-2018-20806: Reflected XSS in Phamm login page
> #  * https://github.com/lota/phamm/issues/24
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 924731 + fixed-upstream
Bug #924731 [src:phamm] phamm: CVE-2018-20806: Reflected XSS in Phamm login page
Added tag(s) fixed-upstream.
> usertags 924731 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 924731 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#947683: marked as done (x2gothinclient-minidesktop: diversion removal misses '--rename')

Your message dated Thu, 02 Jan 2020 16:19:52 +
with message-id 
and subject line Bug#947683: fixed in x2gothinclient 1.5.0.1-2
has caused the Debian Bug report #947683,
regarding x2gothinclient-minidesktop: diversion removal misses '--rename'
to be marked as done.

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

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


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

Hi,

during a test with piuparts I noticed your package modifies files from
another package in /usr. This is so wrong, I'm not even bothered to look
up the part of policy this violates ;-P

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

4m16.9s INFO: Warning: Package purging left files on system:
  /etc/systemd/system/display-manager.service -> 
/lib/systemd/system/lightdm.service not owned
  /etc/systemd/user/ owned by: systemd
  /usr/lib/x2go/ owned by: x2gothinclient-common
  /usr/lib/x2go/x2goclient   not owned
  /usr/share/applications/x2goclient.desktop.disabled-by-x2gotce not 
owned
  /usr/share/doc/perl-base/  owned by: perl-base
  /usr/share/fonts/opentype/ owned by: fonts-cantarell
  /usr/share/fonts/opentype/cantarell/   owned by: fonts-cantarell
  /var/lib/systemd/deb-systemd-user-helper-masked/   not owned

4m16.9s ERROR: FAIL: After purging files have disappeared:
  /usr/bin/x2goclientowned by: x2gothinclient-minidesktop, x2goclient
  /usr/lib/x86_64-linux-gnu/gio/ owned by: glib-networking:amd64, 
gvfs:amd64, dconf-gsettings-backend:amd64
  /usr/lib/x86_64-linux-gnu/gio/modules/ owned by: 
glib-networking:amd64, gvfs:amd64, dconf-gsettings-backend:amd64
  /usr/share/applications/x2goclient.desktop owned by: x2goclient

4m17.0s ERROR: FAIL: Installation and purging test.

The diversions are created with --rename, so the files are moved aside,
but diversion removal lacks --rename, and the files are not restored.


cheers,

Andreas


x2goclient=4.1.2.1-2_x2gothinclient-minidesktop=1.5.0.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: x2gothinclient
Source-Version: 1.5.0.1-2

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated x2gothinclient 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, 02 Jan 2020 16:49:39 +0100
Source: x2gothinclient
Architecture: source
Version: 1.5.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Remote Maintainers 
Changed-By: Mike Gabriel 
Closes: 947618 947683 947785
Changes:
 x2gothinclient (1.5.0.1-2) unstable; urgency=medium
 .
   * debian/patches:
 + Add 0002_Add-close-disconnect-cmdline-option-to-X2Go-Client-s.patch and
   0003_Add-close-disconnect-cmdline-option-to-X2Go-Client-s.patch.
   Use --close-connect as x2goclient cmdline parameter (Closes: #947785).
 + Add 0004_management-share-etc-x2gothinclient-displaymanager_s.patch.
   Correct wrong file name in --background cmdline option for X2Go Client
   in display-manager mode. (Closes: #947618).
   * debian/x2gothinclient-minidesktop.postrm:
 + Do dpkg-divert --remove with --rename option. (Closes: #947683).
Checksums-Sha1:
 22e9df8fc7a9befb6f1a7e322f044fa69d3ea5a3 2973 x2gothinclient_1.5.0.1-2.dsc
 47ae98d196fa6c4848588a61df2fd4fb7c4ef17b 26232 
x2gothinclient_1.5.0.1-2.debian.tar.xz
 28caf63396994503dc8ee305f2f6b143926c4497 11218 
x2gothinclient_1.5.0.1-2_source.buildinfo
Checksums-Sha256:
 cbf89c9574f34e26063e3a9cdd22a6b1eaba3944c93fc9bac36e4a780492f1d0 2973 
x2gothinclient_1.5.0.1-2.dsc
 9167a9e68e93c96704ee0902099a7ec9a8eba24d6bcb6ef6d818f21786a60c33 26232 
x2gothinclient_1.5.0.1-2.debian.tar.xz
 49b67f1e92b62f532b6b32dd0691132e7aa59f9b1c0e865a352215cd63c9f0f7 11218 
x2gothinclient_1.5.0.1-2_source.buildinfo
Files:

Processed: tagging 943621

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

> tags 943621 + fixed
Bug #943621 {Done: Piotr Ożarowski } [src:uvloop] uvloop 
needs an update for python 3.8
Added tag(s) fixed.
> thanks
Stopping processing here.

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

Bug#947907: Same here

2020-01-02 Thread Felicia P

Also experiencing this same bug.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux bullseye/sid
Release:    unstable
Codename:   sid


ii  ure  6.4.0~rc1-4    amd64   LibreOffice UNO runtime environment



0xCEC1B8C7E51FC983.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Processed: tagging 871656

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

> tags 871656 + pending fixed-upstream
Bug #871656 [apt-offline] apt-offline: Does not validate Packages or .deb files 
in bundle
Added tag(s) pending and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#947683: marked as pending in x2gothinclient

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian-remote-team/x2gothinclient/commit/3e9b6d1584c2977a15032c760ef5c04766c3a101


debian/x2gothinclient-minidesktop.postrm: Do dpkg-divert --remove with --rename 
option. (Closes: #947683).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/947683

Processed: Bug#947683 marked as pending in x2gothinclient

Processing control commands:

> tag -1 pending
Bug #947683 [x2gothinclient-minidesktop] x2gothinclient-minidesktop: diversion 
removal misses '--rename'
Added tag(s) pending.

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

Bug#947263: python3-iniparse: missing Breaks+Replaces: python-iniparse

2020-01-02 Thread Emmanuel Arias

Hi,

I attach a patch to fix the Breaks missed.

Please consider applied it
thanks!


Cheers,
Arias Emmanuel
@eamanu
yaerobi.com
From 64ac2053b609627c08f49cb4e0609e40c5e534ae Mon Sep 17 00:00:00 2001
From: Emmanuel Arias 
Date: Thu, 2 Jan 2020 12:45:59 -0300
Subject: [PATCH] d/control: add Breaks (<< 0.4-2.3) missed (Closes: #947263)

---
 debian/changelog | 7 +++
 debian/control   | 1 +
 2 files changed, 8 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index dfdd027..80996e4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+python-iniparse (0.4-4) UNRELEASED; urgency=medium
+
+  * Team upload
+  * d/control: add Breaks (<< 0.4-2.3) missed (Closes: #947263)
+
+ -- Emmanuel Arias   Thu, 02 Jan 2020 12:46:59 -0300
+
 python-iniparse (0.4-3) unstable; urgency=medium
 
   * Maintain under DPMT.
diff --git a/debian/control b/debian/control
index b4d6560..1dfa28c 100644
--- a/debian/control
+++ b/debian/control
@@ -17,6 +17,7 @@ Rules-Requires-Root: no
 Package: python3-iniparse
 Architecture: all
 Depends: ${misc:Depends}, ${python3:Depends}, python3-six
+Breaks: python-iniparse (<< 0.4-2.3)
 Replaces: python-iniparse (<< 0.4-2.3)
 Description: access and modify configuration data in INI files (Python 3)
  iniparse is a INI parser for Python which is:
-- 
2.20.1

Bug#925852: marked as done (vfu: ftbfs with GCC-9)

Your message dated Thu, 02 Jan 2020 15:35:12 +
with message-id 
and subject line Bug#925852: fixed in vfu 4.18-1
has caused the Debian Bug report #925852,
regarding vfu: ftbfs with GCC-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.)


-- 
925852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:vfu
Version: 4.16+repack-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/vfu_4.16+repack-1_unstable_gcc9.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp install-stamp
# Add here commands to clean up after the build process.
cd yascreen; /usr/bin/make clean
make[1]: Entering directory '/<>/vfu-4.16+repack/yascreen'
rm -f yastest yastest.shared yastest.o yascreen.o libyascreen.a libyascreen.so 
libyascreen.so.0 libyascreen.so.0.0.0
make[1]: Leaving directory '/<>/vfu-4.16+repack/yascreen'
cd vslib;  /usr/bin/make clean
make[1]: Entering directory '/<>/vfu-4.16+repack/vslib'
rm -f libvslib.a
rm -rf .OBJ.libvslib.a
rm -f libvscon.a
rm -rf .OBJ.libvscon.a
rm -f libvscony.a
rm -rf .OBJ.libvscony.a
rm -f test
rm -rf .OBJ.test
make[1]: Leaving directory '/<>/vfu-4.16+repack/vslib'
cd vfu;/usr/bin/make clean
make[1]: Entering directory '/<>/vfu-4.16+repack/vfu'
rm -f vfu
rm -rf .OBJ.vfu
rm -f vfu.yas
rm -rf .OBJ.vfu.yas
make[1]: Leaving directory '/<>/vfu-4.16+repack/vfu'
dh_clean
dpkg-buildpackage: warning: debian/rules must be updated to support the 
'build-arch' and 'build-indep' targets (at least 'build-arch' seems to be 
missing)
 debian/rules build
dh_testdir
cd yascreen && /usr/bin/make
make[1]: Entering directory '/<>/vfu-4.16+repack/yascreen'
cc -Wall -O3 -I. --std=gnu89 -flto  -o yascreen.o -c yascreen.c
gcc-ar r libyascreen.a yascreen.o
/usr/bin/ar: creating libyascreen.a
gcc-ranlib libyascreen.a
cc -Wall -O3 -I. --std=gnu89 -flto  -o libyascreen.so.0.0.0 yascreen.c -fPIC 
-lrt -shared
strip libyascreen.so.0.0.0
ln -fs libyascreen.so.0.0.0 libyascreen.so.0
ln -fs libyascreen.so.0 libyascreen.so
cc -Wall -O3 -I. --std=gnu89 -flto  -o yastest.o -c yastest.c
cc -Wall -O3 -I. --std=gnu89 -flto  -o yastest yastest.o yascreen.o -lrt
strip yastest
cc -Wall -O3 -I. --std=gnu89 -flto  -o yastest.shared yastest.o libyascreen.so 
-lrt -L. -lyascreen
strip yastest.shared
make[1]: Leaving directory '/<>/vfu-4.16+repack/yascreen'
cd vslib && /usr/bin/make
make[1]: Entering directory '/<>/vfu-4.16+repack/vslib'
mkdir -p .OBJ.libvslib.a
g++  -I. -O2-c clusters.cpp -o .OBJ.libvslib.a/clusters.o
g++  -I. -O2-c dlog.cpp -o .OBJ.libvslib.a/dlog.o
g++  -I. -O2-c eval.cpp -o .OBJ.libvslib.a/eval.o
In file included from eval.cpp:11:
./vstring.h:275:19: error: friend declaration of 'VString& str_copy(VString&, 
const char*, int, int)' specifies default arguments and isn't a definition 
[-fpermissive]
  275 |   friend VString& str_copy  ( VString& target, const char* source, int 
pos = 0, int len = -1 ); // returns `len' chars from `pos'
  |   ^~~~
In file included from eval.cpp:11:
./vstring.h:289:19: error: friend declaration of

Bug#947683: x2gothinclient-minidesktop: diversion removal misses '--rename'


Hi Andreas,

On  Do 02 Jan 2020 16:25:20 CET, Andreas Beckmann wrote:


On 02/01/2020 15.24, Mike Gabriel wrote:

My question about this bug report now is: do you see your bug report
fixed after I have added the --rename option to dpkg-divert? Or is the
bug more about policy and you are asking me to find another solution for
what I am doing with the diversion?


The --rename should be enough. My expectation is "uninstalling (purging)
the package should restore the former state". And if your "fiddling with
/usr" does not interfere with upgrades (diversions should work fine
here), I don't see any policy violations ;-).



Fair enough. Thanks for the feedback.

Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpAGpqOQL0gS.pgp
Description: Digitale PGP-Signatur

Bug#944473: marked as done (build-dependency not satisfiable in sid)

Your message dated Thu, 02 Jan 2020 15:25:14 +
with message-id 
and subject line Bug#944473: fixed in botch 0.22-2
has caused the Debian Bug report #944473,
regarding build-dependency not satisfiable in sid
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.)


-- 
944473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: botch
Version: 0.21-8
Tags: ftbfs
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

botch build-depends on libcdt5 << 2.40.1.0~ but the current version
of libcdt5 in sid is 2.42.2-3.

-Ralf.
--- End Message ---
--- Begin Message ---
Source: botch
Source-Version: 0.22-2

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

Debian distribution maintenance software
pp.
Johannes 'josch' Schauer  (supplier of updated botch 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, 02 Jan 2020 15:02:44 +0100
Source: botch
Architecture: source
Version: 0.22-2
Distribution: unstable
Urgency: medium
Maintainer: Johannes 'josch' Schauer 
Changed-By: Johannes 'josch' Schauer 
Closes: 944473 946817
Changes:
 botch (0.22-2) unstable; urgency=medium
 .
   * Add patch as workaround for bug #946980. On 32bit architectures, botch
 will now not attempt using parmap for parallelization (closes: #946817)
   * Fixup last changelog entry that forgot a closes: #944473
Checksums-Sha1:
 a31ba30372deffcbd8c923dff611be86d35ec87e 2913 botch_0.22-2.dsc
 3a2a26b391636a6e69e1485b7f79f36704b5dbba 18912 botch_0.22-2.debian.tar.xz
 76d79a84586b3883738ee408544dbb9367b7ee35 10044 botch_0.22-2_amd64.buildinfo
Checksums-Sha256:
 af645e8b082ece4baf19b4213bae0e8a70d0b1239bca3df1ca1ae6be431abad1 2913 
botch_0.22-2.dsc
 442ff2c274c28bba0fb494536c63f599932b16d3b6ee6f1b85a073704e949451 18912 
botch_0.22-2.debian.tar.xz
 63545536637d7c6478eebc96dd76d2fc7a8fe7aa0d4207fb7f9dd7562eae5844 10044 
botch_0.22-2_amd64.buildinfo
Files:
 6bd7483735c0ee9324780f0dd14ba58b 2913 utils optional botch_0.22-2.dsc
 879d52ea4c33aa76b323383464e0515c 18912 utils optional 
botch_0.22-2.debian.tar.xz
 8e83078c28fd6ed5c92aa59c22ff1e43 10044 utils optional 
botch_0.22-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAl4OBH8ACgkQ8sulx4+9
g+HhLw//Qv0LJHOoyTE7902QxrNjrS33v2fLSJhQWQNg+xaugLZad3LrB3+gDXDz
K7x9tb0GFezKNIp1QorUUGWxZJXYCib3aqfxnRyJuytt7WzTHD7YlcogroLJm+PN
uN9ntvgk7RCxZjoeUxbK3xdi0NaYmNrqwl+JHpJsny0p46jZU7UXT/HeAxDTQsXj
mfnya0tnQjXi6SvyTuX+Hn3GVP6yaWRzsZ7WjWiH7p9XP3vOtAQwk65fQFJNNFW0
LcYGyAqx+Vz2JrzxPUGpYZu1BkimkHSCJl1ATepDpkqQkffYbi3j4FcbhdF0Qkv/
K7HLbcoq674VAiOciiDksvPY6C72Sk/PDi4v/T/J/RSQBIGd0aUMztxPdUtBSz8+
18X85jZovzsq+3AocMvixPt624HSJkRN6srR8YvLgwgjxJzZM/msM0tsWFDhqNkw
ufxb5GPDiRWvq2RJnXSf0CFCmhviRLuRQ/HrogkumElJBP5AoloxJoEKyKkMbjXo
1YXXr18cDjKKb7U47oNMoZvhgFrUVkIMij8kzUd00NhqOnpV8qgdv4v8SFw6qwzG
MPPsp3DO8WkesIQbiuA2qHG/5iKDZM3zUIQ6w9HUPFfVa/yreA6x98QmpV9vqwyv
AHU5805/nKUBbv4pNNieUlvBaRuqeRRXYqkJojelf6WEiq9d9/4=
=ui3N
-END PGP SIGNATURE End Message ---

Bug#947683: x2gothinclient-minidesktop: diversion removal misses '--rename'

2020-01-02 Thread Andreas Beckmann

On 02/01/2020 15.24, Mike Gabriel wrote:
> My question about this bug report now is: do you see your bug report
> fixed after I have added the --rename option to dpkg-divert? Or is the
> bug more about policy and you are asking me to find another solution for
> what I am doing with the diversion?

The --rename should be enough. My expectation is "uninstalling (purging)
the package should restore the former state". And if your "fiddling with
/usr" does not interfere with upgrades (diversions should work fine
here), I don't see any policy violations ;-).

Andreas

Bug#946817: marked as done (botch ftbfs, fails tests on 32bit archs)

Your message dated Thu, 02 Jan 2020 15:25:14 +
with message-id 
and subject line Bug#946817: fixed in botch 0.22-2
has caused the Debian Bug report #946817,
regarding botch ftbfs, fails tests on 32bit archs
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.)


-- 
946817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:botch
Version: 0.22-1
Severity: serious
Tags: sid bullseye

botch ftbfs, fails tests on all 32bit archs.
--- End Message ---
--- Begin Message ---
Source: botch
Source-Version: 0.22-2

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

Debian distribution maintenance software
pp.
Johannes 'josch' Schauer  (supplier of updated botch 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, 02 Jan 2020 15:02:44 +0100
Source: botch
Architecture: source
Version: 0.22-2
Distribution: unstable
Urgency: medium
Maintainer: Johannes 'josch' Schauer 
Changed-By: Johannes 'josch' Schauer 
Closes: 944473 946817
Changes:
 botch (0.22-2) unstable; urgency=medium
 .
   * Add patch as workaround for bug #946980. On 32bit architectures, botch
 will now not attempt using parmap for parallelization (closes: #946817)
   * Fixup last changelog entry that forgot a closes: #944473
Checksums-Sha1:
 a31ba30372deffcbd8c923dff611be86d35ec87e 2913 botch_0.22-2.dsc
 3a2a26b391636a6e69e1485b7f79f36704b5dbba 18912 botch_0.22-2.debian.tar.xz
 76d79a84586b3883738ee408544dbb9367b7ee35 10044 botch_0.22-2_amd64.buildinfo
Checksums-Sha256:
 af645e8b082ece4baf19b4213bae0e8a70d0b1239bca3df1ca1ae6be431abad1 2913 
botch_0.22-2.dsc
 442ff2c274c28bba0fb494536c63f599932b16d3b6ee6f1b85a073704e949451 18912 
botch_0.22-2.debian.tar.xz
 63545536637d7c6478eebc96dd76d2fc7a8fe7aa0d4207fb7f9dd7562eae5844 10044 
botch_0.22-2_amd64.buildinfo
Files:
 6bd7483735c0ee9324780f0dd14ba58b 2913 utils optional botch_0.22-2.dsc
 879d52ea4c33aa76b323383464e0515c 18912 utils optional 
botch_0.22-2.debian.tar.xz
 8e83078c28fd6ed5c92aa59c22ff1e43 10044 utils optional 
botch_0.22-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAl4OBH8ACgkQ8sulx4+9
g+HhLw//Qv0LJHOoyTE7902QxrNjrS33v2fLSJhQWQNg+xaugLZad3LrB3+gDXDz
K7x9tb0GFezKNIp1QorUUGWxZJXYCib3aqfxnRyJuytt7WzTHD7YlcogroLJm+PN
uN9ntvgk7RCxZjoeUxbK3xdi0NaYmNrqwl+JHpJsny0p46jZU7UXT/HeAxDTQsXj
mfnya0tnQjXi6SvyTuX+Hn3GVP6yaWRzsZ7WjWiH7p9XP3vOtAQwk65fQFJNNFW0
LcYGyAqx+Vz2JrzxPUGpYZu1BkimkHSCJl1ATepDpkqQkffYbi3j4FcbhdF0Qkv/
K7HLbcoq674VAiOciiDksvPY6C72Sk/PDi4v/T/J/RSQBIGd0aUMztxPdUtBSz8+
18X85jZovzsq+3AocMvixPt624HSJkRN6srR8YvLgwgjxJzZM/msM0tsWFDhqNkw
ufxb5GPDiRWvq2RJnXSf0CFCmhviRLuRQ/HrogkumElJBP5AoloxJoEKyKkMbjXo
1YXXr18cDjKKb7U47oNMoZvhgFrUVkIMij8kzUd00NhqOnpV8qgdv4v8SFw6qwzG
MPPsp3DO8WkesIQbiuA2qHG/5iKDZM3zUIQ6w9HUPFfVa/yreA6x98QmpV9vqwyv
AHU5805/nKUBbv4pNNieUlvBaRuqeRRXYqkJojelf6WEiq9d9/4=
=ui3N
-END PGP SIGNATURE End Message ---

Bug#947944: xen: Several CVEs open for xen (CVE-2018-12207 CVE-2019-11135 CVE-2019-18420 CVE-2019-18421 CVE-2019-18422 CVE-2019-18423 CVE-2019-18424 CVE-2019-18425 CVE-2019-19577 CVE-2019-19578 CVE-

2020-01-02 Thread Salvatore Bonaccorso

Source: xen
Version: 4.11.1+92-g6c33308a8d-2
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

There are several CVEs open for xen up to unstable, compiling a list
from the information from the security-tracker it looks those below.

Any progress in getting those fixed at least for unstable already?

CVE-2018-12207[0]:
| Improper invalidation for page table updates by a virtual guest
| operating system for multiple Intel(R) Processors may allow an
| authenticated user to potentially enable denial of service of the host
| system via local access.


CVE-2019-11135[1]:
| TSX Asynchronous Abort condition on some CPUs utilizing speculative
| execution may allow an authenticated user to potentially enable
| information disclosure via a side channel with local access.


CVE-2019-18420[2]:
| An issue was discovered in Xen through 4.12.x allowing x86 PV guest OS
| users to cause a denial of service via a VCPUOP_initialise hypercall.
| hypercall_create_continuation() is a variadic function which uses a
| printf-like format string to interpret its parameters. Error handling
| for a bad format character was done using BUG(), which crashes Xen.
| One path, via the VCPUOP_initialise hypercall, has a bad format
| character. The BUG() can be hit if VCPUOP_initialise executes for a
| sufficiently long period of time for a continuation to be created.
| Malicious guests may cause a hypervisor crash, resulting in a Denial
| of Service (DoS). Xen versions 4.6 and newer are vulnerable. Xen
| versions 4.5 and earlier are not vulnerable. Only x86 PV guests can
| exploit the vulnerability. HVM and PVH guests, and guests on ARM
| systems, cannot exploit the vulnerability.


CVE-2019-18421[3]:
| An issue was discovered in Xen through 4.12.x allowing x86 PV guest OS
| users to gain host OS privileges by leveraging race conditions in
| pagetable promotion and demotion operations. There are issues with
| restartable PV type change operations. To avoid using shadow
| pagetables for PV guests, Xen exposes the actual hardware pagetables
| to the guest. In order to prevent the guest from modifying these page
| tables directly, Xen keeps track of how pages are used using a type
| system; pages must be "promoted" before being used as a pagetable, and
| "demoted" before being used for any other type. Xen also allows for
| "recursive" promotions: i.e., an operating system promoting a page to
| an L4 pagetable may end up causing pages to be promoted to L3s, which
| may in turn cause pages to be promoted to L2s, and so on. These
| operations may take an arbitrarily large amount of time, and so must
| be re-startable. Unfortunately, making recursive pagetable promotion
| and demotion operations restartable is incredibly complicated, and the
| code contains several races which, if triggered, can cause Xen to drop
| or retain extra type counts, potentially allowing guests to get write
| access to in-use pagetables. A malicious PV guest administrator may be
| able to escalate their privilege to that of the host. All x86 systems
| with untrusted PV guests are vulnerable. HVM and PVH guests cannot
| exercise this vulnerability.


CVE-2019-18422[4]:
| An issue was discovered in Xen through 4.12.x allowing ARM guest OS
| users to cause a denial of service or gain privileges by leveraging
| the erroneous enabling of interrupts. Interrupts are unconditionally
| unmasked in exception handlers. When an exception occurs on an ARM
| system which is handled without changing processor level, some
| interrupts are unconditionally enabled during exception entry. So
| exceptions which occur when interrupts are masked will effectively
| unmask the interrupts. A malicious guest might contrive to arrange for
| critical Xen code to run with interrupts erroneously enabled. This
| could lead to data corruption, denial of service, or possibly even
| privilege escalation. However a precise attack technique has not been
| identified.


CVE-2019-18423[5]:
| An issue was discovered in Xen through 4.12.x allowing ARM guest OS
| users to cause a denial of service via a XENMEM_add_to_physmap
| hypercall. p2m-max_mapped_gfn is used by the functions
| p2m_resolve_translation_fault() and p2m_get_entry() to sanity check
| guest physical frame. The rest of the code in the two functions will
| assume that there is a valid root table and check that with BUG_ON().
| The function p2m_get_root_pointer() will ignore the unused top bits of
| a guest physical frame. This means that the function p2m_set_entry()
| will alias the frame. However, p2m-max_mapped_gfn will be updated
| using the original frame. It would be possible to set
| p2m-max_mapped_gfn high enough to cover a frame that would lead
| p2m_get_root_pointer() to return NULL in p2m_get_entry() and
| p2m_resolve_translation_fault(). Additionally, the sanity check on
| p2m-max_mapped_gfn is off-by-one allowing "highest mapped + 1" to
| be considered valid. However, p2m_get_root_pointer() will return

Bug#930774: any idea when guile-2.2 will be fixed ?

2020-01-02 Thread shirish शिरीष

at bottom :-

On 02/01/2020, Rob Browning  wrote:
> shirish शिरीष  writes:
>
>> Just saw this, any idea when this FTFBS will be fixed. Somebody even
>> shared a patch, maybe that fixes the issue.
>
> I'll plan to investigate this weekend.  (I've been unfortunately
> preoccupied with python 3 related messes for a while.)
>

Ah, thank you fixing any python 3 messes as well. Well aware of the
transition happening. Haven't hit any major road-blocks yet, so all is
good :)

> Thanks
> --
> Rob Browning
> rlb @defaultvalue.org and @debian.org
> GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
> GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com

E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C

Bug#947683: x2gothinclient-minidesktop: diversion removal misses '--rename'


Hi Andreas,

On  So 29 Dez 2019 03:59:07 CET, Andreas Beckmann wrote:


Package: x2gothinclient-minidesktop
Version: 1.5.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package modifies files from
another package in /usr. This is so wrong, I'm not even bothered to look
up the part of policy this violates ;-P


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


4m16.9s INFO: Warning: Package purging left files on system:
  /etc/systemd/system/display-manager.service ->  
/lib/systemd/system/lightdm.service not owned

  /etc/systemd/user/ owned by: systemd
  /usr/lib/x2go/ owned by: x2gothinclient-common
  /usr/lib/x2go/x2goclient   not owned
  /usr/share/applications/x2goclient.desktop.disabled-by-x2gotce  
not owned

  /usr/share/doc/perl-base/  owned by: perl-base
  /usr/share/fonts/opentype/ owned by: fonts-cantarell
  /usr/share/fonts/opentype/cantarell/   owned by: fonts-cantarell
  /var/lib/systemd/deb-systemd-user-helper-masked/   not owned

4m16.9s ERROR: FAIL: After purging files have disappeared:
  /usr/bin/x2goclientowned by: x2gothinclient-minidesktop, x2goclient
  /usr/lib/x86_64-linux-gnu/gio/ owned by:  
glib-networking:amd64, gvfs:amd64, dconf-gsettings-backend:amd64
  /usr/lib/x86_64-linux-gnu/gio/modules/ owned by:  
glib-networking:amd64, gvfs:amd64, dconf-gsettings-backend:amd64

  /usr/share/applications/x2goclient.desktop owned by: x2goclient

4m17.0s ERROR: FAIL: Installation and purging test.

The diversions are created with --rename, so the files are moved aside,
but diversion removal lacks --rename, and the files are not restored.


cheers,

Andreas


Thanks for reporting this!

As x2gothinclient is a meta wrapper for x2goclient (and closely tied  
to it) and used on machines in a thin client environment, I went down  
the "fiddle with files in /usr of another package" path.


My question about this bug report now is: do you see your bug report  
fixed after I have added the --rename option to dpkg-divert? Or is the  
bug more about policy and you are asking me to find another solution  
for what I am doing with the diversion?


Thanks+Greets,
Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgp3xpyBDhl4k.pgp
Description: Digitale PGP-Signatur

Bug#945920: Random Chromium crashes

2020-01-02 Thread Christopher Obbard

Hi,
This is also occurring on two machines for me. The crashes are random
but will happen after about 10 minutes of use, quite annoying...

Thanks!
Chris

On Tue, 31 Dec 2019 18:27:13 +0100 (CET) Thorsten Bonow
 wrote:
> On Mon, 30 Dec 2019 13:50:36 -0800 Eloston 
> wrote:
>
> [...]
>
> > $ ./debian/rules get-orig-source
>
> Hi,
>
> this fails for me:
>
> [...]
> test ! -e debian || rm -rf debian
> cp -r ../debian ./
> cp: cannot stat '../debian': No such file or directory
> make: *** [debian/rules:212: get-orig-source] Error 1
> ./debian/rules get-orig-source  441.08s user 24.95s system 92% cpu
> 8:25.08 total
>
> Files and directories:
> $ ll
> total 12K
> drwxr-sr-x 50 toto staff 4.0K Dec 31 14:40 chromium-79.0.3945.79
> -rw-r--r--  1 toto staff 2.9K Dec 31 14:30
> chromium-build-deps_79.0.3945.79-1_all.deb
> -rw-r--r--  1 toto staff 3.6K Dec 31 12:28 enable-tracing.patch
> $ pwd
> /usr/local/src/chromium/chromium-c88b97a6dc183a6a7f8a05aee9e99957285a9371
>
>
> Regards,
> Toto
>
> --
> Sent from my GNU Emacs running on GNU/Linux
>
>

Bug#947939: etcd FTBFS in testing/unstable


Source: etcd
Version: 3.2.26+dfsg-4
Severity: serious

Etcd FTBFS in testing/unstable, I first noticed this on a raspbian autobuilder, 
but it's also happening on the
reproducible builds service for all architectures, so it's not raspbian specific

The only think I see in the log that looks like an error is


src/github.com/coreos/etcd/etcdserver/api/etcdhttp/base.go:57:26: undefined: 
prometheus.Handler


But I am far from sure if this is the real issue or not, I am not an expert in 
reading golang build logs.

Processed: Re: python3-iniparse: missing Breaks+Replaces: python-iniparse

Processing control commands:

> found -1 0.4-3
Bug #947263 {Done: Andrej Shadura } [python3-iniparse] 
python3-iniparse: missing Breaks+Replaces: python-iniparse
Marked as found in versions python-iniparse/0.4-3; no longer marked as fixed in 
versions python-iniparse/0.4-3 and reopened.

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

Bug#947263: python3-iniparse: missing Breaks+Replaces: python-iniparse

2020-01-02 Thread Andreas Beckmann

Followup-For: Bug #947263
Control: found -1 0.4-3

Hi,

python3-iniparse now has
  Replaces: python-iniparse (<< 0.4-2.3)
but the corresponding Breaks is still missing.
This allows partial upgrade paths where python-iniparse is kept
installed (but crippled, because it lost some files). If
python3-iniparse gets removed afterwards, python-iniparse is still
installed and able to satisfy dependencies, but broken.


Andreas

Bug#937552: marked as done (pysvn: Python2 removal in sid/bullseye)

Your message dated Thu, 02 Jan 2020 12:04:10 +
with message-id 
and subject line Bug#937552: fixed in pysvn 1.9.9-2.1
has caused the Debian Bug report #937552,
regarding pysvn: Python2 removal in sid/bullseye
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.)


-- 
937552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pysvn
Version: 1.9.9-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:pysvn

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: pysvn
Source-Version: 1.9.9-2.1

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated pysvn package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 28 Dec 2019 11:03:00 +
Source: pysvn
Architecture: source
Version: 1.9.9-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Peter Michael Green 
Closes: 937552
Changes:
 pysvn (1.9.9-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Fix clean target
   [Gianfranco Costamagna]
   * Drop python2 package (Closes: #937552)
Checksums-Sha1:
 f5c257079cc97e7473689fa1bf3d7b58261c4a07 2187 pysvn_1.9.9-2.1.dsc
 aac5053c48b02c170a6cefdc7f67773f6705804f 8752 pysvn_1.9.9-2.1.debian.tar.xz
 7f2d7d6550edd8fd276d37411657f634fb31dcfe 7759 pysvn_1.9.9-2.1_source.buildinfo
Checksums-Sha256:
 4f3b1e213bae7931128e728727170e0d08da88d6b9f5bb565169d2559821a18a 2187 
pysvn_1.9.9-2.1.dsc
 61d5bde5f845516907494346eaa76a42b277441b2a6e7b42ee8ea57fa14f8127 8752 
pysvn_1.9.9-2.1.debian.tar.xz
 89c6516d2a0adb0318437a12bdf8dbc06582645c26b52247e63d844c153fcdc7 7759 
pysvn_1.9.9-2.1_source.buildinfo
Files:
 41ef1387e3bf95c126baf92ff3392ec0

Bug#943454: marked as done (python-jellyfish: autopkgtest fails if more than one supported python version)