Bug#933992: Bug#934340: Please remove the dependency on obus and camlp4

[Stéphane Glondu]

Le 10/08/2019 à 16:59, Thomas Leonard a écrit :
> obus is only optional on systems that don't use D-BUS. It is needed on Debian.
> 
> https://github.com/ocaml-community/obus/blob/master/CHANGES.md says:
> 
> 1.2.0 (2019-07-04)
> - remove all Camlp4 dependencies
> 
> So I think Debian can just update to that.

Not at the moment. The new version depends on (at least) two NEW
packages (lwt_log and ppxlib), and the NEW queue backlog is pretty big now.

Moreover, lwt_log depends on lwt >= 4.0.0, but Debian has 2.7.1.
Updating lwt in Debian cannot be done IMHO without updating
ocaml-ctypes, which requires (at least) another NEW package (integers).

So I guess we'll have to remove obus and its reverse dependencies from
testing for a while.


Cheers,

-- 
Stéphane

Bug#934375: marked as pending in golang-github-anacrolix-missinggo

[Drew Parsons]

Control: tag -1 pending

Hello,

Bug #934375 in golang-github-anacrolix-missinggo 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-anacrolix-missinggo/commit/43b1fc689006fc4c9b0f17312e0b939129b98f4d


reorganise packages to split Go source from binary files

- make golang-github-anacrolix-missinggo-dev (Arch: all) with Go
source code and provides Go package Depends.

Closes: #934375.

- place binary files in golang-github-anacrolix-missinggo-bin


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/934375

Processed: Bug#934375 marked as pending in golang-github-anacrolix-missinggo

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #934375 [src:golang-github-anacrolix-missinggo] 
golang-github-anacrolix-ffprobe: FTBFS in sid (failing tests)
Added tag(s) pending.

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

Bug#934344: nvidia-kernel-dkms: nvidia kernel driver does not build with linux-5.2

[Mario Palomo]

On Sat, 10 Aug 2019 20:04:01 +0300 =?UTF-8?B?QW5kcmVpIERlbWVraG92?= <
and...@ipfran.ru> wrote:
> This bug seems to have a known origin:
https://garajau.com.br/2019/07/compiling-nvidia-418-on-kernel-52
>
> Best
> Andrei

Based on this I created the following patch, with which I was able to
regenerate the package nvidia-kernel-dkms_418.74-1_amd64.deb, and it worked
for me:

diff -Naurd
nvidia-graphics-drivers-418.74_OLD/debian/module/debian/patches/nvidia-uvm-put_user_pages.patch
nvidia-graphics-drivers-418.74_NEW/debian/module/debian/patches/nvidia-uvm-put_user_pages.patch
---
nvidia-graphics-drivers-418.74_OLD/debian/module/debian/patches/nvidia-uvm-put_user_pages.patch
1970-01-01 00:00:00.0 +
+++
nvidia-graphics-drivers-418.74_NEW/debian/module/debian/patches/nvidia-uvm-put_user_pages.patch
2019-08-11 03:43:01.517330332 +
@@ -0,0 +1,19 @@
+From linux 5.2.2 put_user_page is now being provided by the kernel and it
conflicts with the existing one by NVIDIA drivers.
+
+--- a/nvidia-uvm/uvm8_tools.c
 b/nvidia-uvm/uvm8_tools.c
+@@ -206,12 +206,14 @@ static bool
tracker_is_counter(uvm_tools_event_tracker_t *event_tracker)
+ return event_tracker != NULL && !event_tracker->is_queue;
+ }
+
++#if LINUX_VERSION_CODE < KERNEL_VERSION(5, 2, 2)
+ static void put_user_pages(struct page **pages, NvU64 page_count)
+ {
+ NvU64 i;
+ for (i = 0; i < page_count; i++)
+ put_page(pages[i]);
+ }
++#endif
+
+ static void unmap_user_pages(struct page **pages, void *addr, NvU64 size)
+ {
diff -Naurd nvidia-graphics-drivers-418.74_OLD/debian/module/debian/patches/
series.in nvidia-graphics-drivers-418.74_NEW/debian/module/debian/patches/
series.in
--- nvidia-graphics-drivers-418.74_OLD/debian/module/debian/patches/
series.in 2019-05-11 11:52:38.0 +
+++ nvidia-graphics-drivers-418.74_NEW/debian/module/debian/patches/
series.in 2019-08-11 03:42:26.321398133 +
@@ -8,3 +8,4 @@
 cc_version_check-gcc5.patch
 nvidia-use-ARCH.o_binary.patch
 nvidia-modeset-use-ARCH.o_binary.patch
+nvidia-uvm-put_user_pages.patch

Processed: Re: golang-github-anacrolix-ffprobe: FTBFS in sid (failing tests)

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:golang-github-anacrolix-missinggo
Bug #934375 [src:golang-github-anacrolix-ffprobe] 
golang-github-anacrolix-ffprobe: FTBFS in sid (failing tests)
Bug reassigned from package 'src:golang-github-anacrolix-ffprobe' to 
'src:golang-github-anacrolix-missinggo'.
No longer marked as found in versions golang-github-anacrolix-ffprobe/1.0.0-1.
Ignoring request to alter fixed versions of bug #934375 to the same values 
previously set

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

Bug#934375: golang-github-anacrolix-ffprobe: FTBFS in sid (failing tests)

[Drew Parsons]

Package: src:golang-github-anacrolix-ffprobe
Followup-For: Bug #934375
Control: reassign -1 src:golang-github-anacrolix-missinggo

The bug is in github.com/anacrolix/missinggo/leaktest
i.e. missinggo


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

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

Bug#934126: marked as done (malfunctions due to being confused about git repository)

[Debian Bug Tracking System]

Your message dated Sun, 11 Aug 2019 01:08:05 +
with message-id 
and subject line Bug#934126: fixed in dgit 9.7
has caused the Debian Bug report #934126,
regarding malfunctions due to being confused about git repository
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.)


-- 
934126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dgit
Version: 9.6
Control: fixed -1 9.5
Severity: serious

check_for_git always returns falseish for the Debian repos because of
a bug in dgit's handling of WWW::Curl's (correct) behaviour with
CURLOPT_NOBODY.

As a result, dgit fetch/clone sometimes fails to stitch in the earlier
dgit push history from dgit-repos:

One possible symptom is this something like this:

synthesised git commit from .dsc 16.3.0-2.1
3ace5cdf35eed10c4a0b83b3f2804882b6343840 
a330c7d56988941b518afbd479563698e3056d85 dgit repo server tip (last push) ? at 
/usr/bin/dgit line 3467.
main::__ANON__("3ace5cdf35eed10c4a0b83b3f2804882b6343840", "dgit repo 
server tip (last push)") called at /usr/bin/dgit line 3470
main::fetch_from_archive() called at /usr/bin/dgit line 3898
main::fetch_one() called at /usr/bin/dgit line 3918
main::dofetch() called at /usr/bin/dgit line 4886
main::cmd_fetch() called at /usr/bin/dgit line 7798

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
--- End Message ---
--- Begin Message ---
Source: dgit
Source-Version: 9.7

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

Debian distribution maintenance software
pp.
Ian Jackson  (supplier of updated dgit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 Aug 2019 01:11:01 +0100
Source: dgit
Binary: dgit git-debrebase git-debpush dgit-infrastructure
Architecture: source
Version: 9.7
Distribution: unstable
Urgency: medium
Maintainer: Ian Jackson 
Changed-By: Ian Jackson 
Description:
 dgit   - git interoperability with the Debian archive
 dgit-infrastructure - dgit server backend infrastructure
 git-debpush - client script for git pushing to Debian-style archives
 git-debrebase - rebasing git workflow tool for Debian packaging
Closes: 932699 933827 934126
Changes:
 dgit (9.7) unstable; urgency=medium
 .
   dgit general bugfixes:
   * Correctly test for presence of git repo on dgit git server.
 Fixes behaviour following mixed dgit/non-dgit uploads.  Closes:#934126.
 (Was badly broken by http fetching rework in dgit 9.6.)
   * Fix use on NFS, by closing a file which is going to be deleted.
 [Report and fix from Stéphane Glondu]  Closes:#933827.
 .
   dgit vcs-git bugfixes:
   * Strip [] (used eg by Debian Haskell Team).  Closes:#932699.
   * update-vcs-git: Cope if url is unchanged.
   * update-vcs-git: Strip -b (as it always should have done).
 .
   Test suite:
   * New facilities for http testing, including mock webservers.
   * New test cases for http, and for bugs fixed in this version.
   * Switch to using http git check in three existing tests.
   * Improve debian/tests/control generator.
   * Limited refactoring to support other changes.
 .
   Other minor changes:
   * dgit: Slightly more debugging for check_for_git with http[s]
   * changelog: Fix a typo in the entry for 9.6.
   * i18n (messages) updated, following message changes.
Checksums-Sha1:
 efd489b7573b6f4c8c9a6de75ce79be52069bb0f 1821 dgit_9.7.dsc
 2d5dd607e4d3fe84f84cb9a4392a6d522583e090 694276 dgit_9.7.tar.gz
Checksums-Sha256:
 7dd0a5d111dcde560d2e4be72ecb5dc3998bc00fb0da2effe8bfe2cdd799635e 1821 
dgit_9.7.dsc
 cefd614c641de8ed20deb445d70070bc010644e45bf2ab9ac640035e88ca1092 694276 
dgit_9.7.tar.gz
Files:
 f30ea7af742f5fe51a387974f6386450 1821 devel optional dgit_9.7.dsc
 bd7667c39326dd3bcb80498b58f4c92a 694276 devel optional dgit_9.7.tar.gz

-BEGIN PGP SIGNATURE-

Bug#934443: getdp build-depends on cruft package.

[peter green]

Package: getdp
Version:3.0.4+dfsg1-1
Severity: serious
Tags: patch, bullseye, sid

getdp build-depends on texlive-generic-recommended which is no longer built by 
texlive-base. Please update your build-dependency to texlive-plain-generic.

Bug#934442: python-gabbi (build-)depends on cruft package.

[peter green]

Package: python-gabbi
Version: 1.40.0-4
Severity: serious
Tags: bullseye, sid

python-gabbi (build-)depends on the python-jsonpath-rw-ext binary package which 
is no longer built by the corresponding source package.

It's probably time to drop python 2 support from this package.

Bug#933614: marked as done (logilab-common: Epydoc will be removed)

[Debian Bug Tracking System]

Your message dated Sat, 10 Aug 2019 23:35:11 +
with message-id 
and subject line Bug#933614: fixed in logilab-common 1.4.3-1
has caused the Debian Bug report #933614,
regarding logilab-common: Epydoc will be removed
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.)


-- 
933614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933614
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: logilab-common
Severity: serious
Justification: Policy 5.9.2

Hi,

This is one of 20+ packages in the archive that still depend on Epydoc.  I
have filed a bug with ftp.debian.org to have epydoc removed from unstable.
Besides its lack of support for Python 3, epydoc has been completely
unsupported upstream for close to a decade.  It really should have been removed
from the archive years ago.

I apologize for the late notice on this.  I filed bugs against all of the
dependencies I could find over 18 months ago, but the FTP Master list included
some additional packages.

If I don't hear back from you, I will NMU a version of your package that removes
the build dependency.  I will accomplish this by simply not building the API
documentation.  If you don't want me to do this, please reply and let me know
how you want me to proceed.

Thanks,

KEN
--- End Message ---
--- Begin Message ---
Source: logilab-common
Source-Version: 1.4.3-1

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated logilab-common package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 10 Aug 2019 19:20:32 -0400
Source: logilab-common
Architecture: source
Version: 1.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 933614
Changes:
 logilab-common (1.4.3-1) unstable; urgency=medium
 .
   * New upstream release
 - move from epydoc to sphinx; Closes: #933614
   * debian/control
 - bump Standards-Version to 4.4.0 (no changes needed)
Checksums-Sha1:
 2c3a7aab1297f0598b7f6ef4757ca17bda0b099e 2341 logilab-common_1.4.3-1.dsc
 a780738a97865d748b1b74ab3c5876c3c8017432 198506 
logilab-common_1.4.3.orig.tar.gz
 e0cb5426f5887fe07750d1e29dc25dcf4819c2b1 8140 
logilab-common_1.4.3-1.debian.tar.xz
 366e5b2e8ef1bf6bedeb996f15879cd0f4278160 6185 
logilab-common_1.4.3-1_source.buildinfo
Checksums-Sha256:
 c1fcb99e655ea26753ae9b9a753899ee687d96d8ad74c4e183d9b3138278a684 2341 
logilab-common_1.4.3-1.dsc
 ed94546f033d90650a3432a6786b1ba32d3c207f47fe8df58b195746655c88ff 198506 
logilab-common_1.4.3.orig.tar.gz
 060ed6edce0eed0708dc360c49363fb81752279c1915661c69e8318ec0a786e0 8140 
logilab-common_1.4.3-1.debian.tar.xz
 a39f850b7fc65f74e5d0fd968b4052b36f00995b9abe92f0dffb8bb7358ecd7b 6185 
logilab-common_1.4.3-1_source.buildinfo
Files:
 e96117251dd1cde29b0ecc97cb8189a1 2341 python optional 
logilab-common_1.4.3-1.dsc
 5f4f965c3f1b7b839f3bd7dd5e8e5d30 198506 python optional 
logilab-common_1.4.3.orig.tar.gz
 93553a04d3bb69bed5ec23fdf8e5 8140 python optional 
logilab-common_1.4.3-1.debian.tar.xz
 ebdfc33f2236ba31592ef06dd46f1c52 6185 python optional 
logilab-common_1.4.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl1PUVQACgkQh588mTgB
qU900BAAp1q+fcngZDhL+IauNx5ukLl5klIauE5bSYsKvegyBSARIXyFQNfxazbr
ZSY+4MSK1yBxNO5sw85XuubyWvYi9zm9PkUHjI47d+MnE8YT6jb2hfoEgz2HACT6
5PldX7Pq6RzoN/RYKtWpArFCJL2qzNBRXnoNTam1/PQTt4WIOHQXIwFaNOkXfkMZ
SbOPoxzDbAIeX/blq5lPoQg7CKrOKy6QO07tAjHBniKpfrT1304nOo7yfs2Fi+4r
LnVe3Fl7pgD7VY18G7TUiA9AkaDp/1tBH68aFd/jhWoTu0oVk9cdU+9sH4+Z4JJ/
r21ONnym0zOoUedQDsYRy1gGQAoM1XVaQbVEnjyYbzyaGAtlgU8GKMjTor8dt8Ji
Tc3GnYXXDF1p4rxvGGUnCzfyK5o+ckvwBSEOr2GONeJpLPa5eeJdOGoONikeeeF0
dbf7Asb7R+sqiRQF+sG4ZXpvsSMAMWOJydPePvx5Ig4lNCdyCl1g1rRGek+BUG6x
aXbHUY3y+ervpkuXS7jijM1c8/mPVtCGm5M71ASTi/TML4KRXZhxdx4qpy30702y
g2upmg3f48EUqkS0578pDNUbD3LPxzyS/Q2/tMT5007ho/jJ+8dTfnHECTPbPMw/
ibLGN8X7YBwxWeiOCvCmmpyGY2F2yGp8br8dA4+oYeiBOHNxyMs=
=XYcw
-END PGP SIGNATURE End Message ---

Bug#934441: python-etcd3gw (build-)depends on cruft package.

[peter green]

Package: python-etcd3gw
Version: 0.2.1-1
Severity: serious
Tags: patch, bullseye, sid

python-etcd3gw (build-)depends on the python-futurist binary package which is 
no longer built by the corresponding source package.

It's probably time to drop python 2 support from this package. I notice that 
ubuntu have already done so, their patch can be found at 
https://launchpadlibrarian.net/432629348/python-etcd3gw_0.2.1-1_0.2.1-1ubuntu1.diff.gz

Bug#916114: marked as done (xawtv FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Sat, 10 Aug 2019 23:22:02 +
with message-id 
and subject line Bug#916114: fixed in xawtv 3.106-1
has caused the Debian Bug report #916114,
regarding xawtv FTBFS with glibc 2.28
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.)


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

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

...
common/get_media_devices.c: In function 'fget_associated_device':
common/get_media_devices.c:522:14: warning: implicit declaration of function 
'major' [-Wimplicit-function-declaration]
  dev_major = major(f_status.st_rdev);
  ^
common/get_media_devices.c:523:14: warning: implicit declaration of function 
'minor'; did you mean 'mknod'? [-Wimplicit-function-declaration]
  dev_minor = minor(f_status.st_rdev);
  ^
...
gcc -Wl,-z,relro -Wl,-z,now -ldl -Wl,-E -o console/webcam console/webcam.o 
console/ftp.o common/parseconfig.o libng/libng.a -lpthread -ljpeg -lm -ldl
/usr/bin/ld: libng/libng.a(get_media_devices.o): in function 
`fget_associated_device':
./common/get_media_devices.c:522: undefined reference to `major'
/usr/bin/ld: ./common/get_media_devices.c:523: undefined reference to `minor'
collect2: error: ld returned 1 exit status
make[1]: *** [mk/Compile.mk:75: console/streamer] Error 1
--- End Message ---
--- Begin Message ---
Source: xawtv
Source-Version: 3.106-1

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

Debian distribution maintenance software
pp.
Dmitry Eremin-Solenikov  (supplier of updated xawtv 
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: Sun, 11 Aug 2019 00:50:14 +0300
Source: xawtv
Architecture: source
Version: 3.106-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Dmitry Eremin-Solenikov 
Closes: 916114
Changes:
 xawtv (3.106-1) unstable; urgency=medium
 .
   [ Maximiliano Curia ]
   * New upstream release (3.106). (Closes: #916114)
   * Rediff patches
 .
   [ Dmitry Eremin-Solenikov ]
   * d/control: adopt by Debian Multimedia team
   * d/control: bump Standards-Version to 4.4.0 (no changes needed)
   * d/patches: add patch to fix make distclean
   * d/watch: switch to https
   * d/patches: add patch to honour CPPFLAGS to make hardening work
   * d/patches: several more spelling fixes
   * d/xawtv-plugin-qt.lintian-overrides: remove unused override
   * d/xawtv-plugins.lintian-overrides: remove unused override
   * d/conrol: extend package descriptions
   * d/xawtv.templates: remove unused xawtv/makedev template
   * d/control: drop Conflicts with suidmanager, it is gone long ago
   * d/gbp.conf: add configuration file
Checksums-Sha1:
 35d17776e6ca479f4130e8bdc6d1f93165af1ea0 2956 xawtv_3.106-1.dsc
 68059cbd8cc6f9262cb6e5be0bd79bd19efffe03 547036 xawtv_3.106.orig.tar.gz
 6839412ca00704749f246ed91203763f1fdf4807 42480 xawtv_3.106-1.debian.tar.xz
Checksums-Sha256:
 f874dbe8af5e0beef6fc12dab6f082a598c4730f10d6b41fbefef5264aa852d4 2956 
xawtv_3.106-1.dsc
 e1c8b82d06a7552626267a7e8ee1d85d90b064474f7536b7e139860fce762b2c 547036 
xawtv_3.106.orig.tar.gz
 e83741842a059db63ed3385854a78547dcb4bad20a240a09f5ac7cf1f17843e5 42480 
xawtv_3.106-1.debian.tar.xz
Files:
 41c0468eb132752cc16daf80d754637c 2956 video optional xawtv_3.106-1.dsc
 02457b6fab27bc39c2159721654da380 547036 video optional xawtv_3.106.orig.tar.gz
 e0f7c4fffa03037d8827699610a3ec13 42480 video optional 
xawtv_3.106-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl1PQt0ACgkQafL8UW6n
GZMhABAAhhlBvw6mKrvroYEDtdZRRQw9C/gI6z7datluL2+JXCuv6+4r3BMnLlDs
kzlillCU7ORrBiRa9AguvkGTQ9BAeA91Qhh3DBzzjZ4iJDsnj3vTzaW9AkObyTgs
TJ06fT2NO9AO80yHpByU5DN7ZMIwRXfN3PxILcR7Iy7yjpObvtTQ87+6z3WS/aaH
jusMsMlqXxgFXP085iobEenV+uriq8tsxQXTC2kz3B50WnwQt/DYIrv41jgt7BZy
Bq9o4PNBa5CFkuOP+DRpH1NEr+HdkeF5SLI6DyyL84KQqv2LIb2laiWJOe3uzpd6

Processed: Bug#933614 marked as pending in logilab-common

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #933614 [src:logilab-common] logilab-common: Epydoc will be removed
Added tag(s) pending.

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

Bug#934363: marked as done (r-cran-ggplot2: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Sat, 10 Aug 2019 23:21:34 +
with message-id 
and subject line Bug#934363: fixed in r-cran-ggplot2 3.2.0+dfsg-2
has caused the Debian Bug report #934363,
regarding r-cran-ggplot2: autopkgtest regression
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.)


-- 
934363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-ggplot2
Version: 3.2.0+dfsg-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Since the upload of 3.2.0+dfsg-1, r-cran-ggplot2 has been failings its
own autopkgtests [1] with the following error:

> library(testthat)
> library(ggplot2)
>
> test_check("ggplot2")
Error in loadNamespace(name) : there is no package called 'vdiffr'
Calls: test_check ... loadNamespace -> withRestarts -> withOneRestart
-> doWithOneRestart
Execution halted

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-ggplot2/unstable/amd64/
--- End Message ---
--- Begin Message ---
Source: r-cran-ggplot2
Source-Version: 3.2.0+dfsg-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-cran-ggplot2 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, 10 Aug 2019 23:41:07 +0200
Source: r-cran-ggplot2
Binary: r-cran-ggplot2
Architecture: source
Version: 3.2.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Description:
 r-cran-ggplot2 - implementation of the Grammar of Graphics
Closes: 934363
Changes:
 r-cran-ggplot2 (3.2.0+dfsg-2) unstable; urgency=medium
 .
   * Do not run test requiring package r-cran-vdiffr
 Closes: #934363
   * debhelper-compat 12
   * Standards-Version: 4.4.0
Checksums-Sha1:
 fd95e8f95aa65e23893b41cc23788d049f578b1a 2388 r-cran-ggplot2_3.2.0+dfsg-2.dsc
 a306dbee11934e7d2b0a95af009a389bc9082363 3868 
r-cran-ggplot2_3.2.0+dfsg-2.debian.tar.xz
Checksums-Sha256:
 6e0ad06fb81a93bfd78af168f1a2501ce87f673ebcc2e2c15b83902b96b10829 2388 
r-cran-ggplot2_3.2.0+dfsg-2.dsc
 827092512e397c2347b0c6b1563c20d90d4446142ed83166fe5f0dc70f698f6f 3868 
r-cran-ggplot2_3.2.0+dfsg-2.debian.tar.xz
Files:
 c9c89191e1712ddc17f61d2cdf5536ef 2388 gnu-r optional 
r-cran-ggplot2_3.2.0+dfsg-2.dsc
 7f4a4291922a427ebbc5ac14adc0fa37 3868 gnu-r optional 
r-cran-ggplot2_3.2.0+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl1POxMRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtE5ehAAi2AVPpU+DPfSR33bc/vN0GMfrxX0jQpF
oahtvHVGUc8x+l/SBw++ryeEL1xauVu8C5kMOM1i6kYRJIKuGHqINGMwi7kv385+
jGvfgjlawzpGb9aPaAIFZga2wOcF6K/uIee01n+JPjJF3MzJw4Pzfp1AkaCAOdT4
K2ohqEFNEZecDZ75korISytv/0dAZw6SeZufl90/T3R9YbZjNoJ5ZnzYgigyAJJl
t6mzkyw5l1PON9bZqrOyREtAnUEQxhKus+eLj8D4MOk5eEREHb4T/UDQU9svr+wc
sOTi5Ft6UUKPlwx291lgiZoeYp3fYDwzdxwcsE4z7kUgJQbiJGBxwMp+FA/3zJr9
j8gat9QD4autALX6xPFeb6FmrueAcx07/4feU6Vjk4i4H/GZuQFfirYi1S0/ttL4
6rUkbQr4mj1II3SmGQe2bhHURomOTFm5tE0TIdJ5cAZbUW+cAoPNsHH1h+6dcpFX
1uxyj+sL0sqLm8yvM53Q33Es/0pchGP6N6zkteNp8ioyr2gethnK0E/BT4N6BCqr
zeS2MgotJtsnNj8aujyJw0F1qSC3oGeqXfGQ2GgCUxcrc+dUL7gMRJKhQLrpb3Ww
UpO4kUFxjeX+Sr0xuupqWMaVBU99YqOW7MZGWLnW1CWHj5LldRX6lpiUGyXZlEAU
+L1FBKB5PsE=
=0aza
-END PGP SIGNATURE End Message ---

Bug#933614: marked as pending in logilab-common

[Sandro Tosi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/logilab-common/commit/3c788bbf5b855e47842abda1c21e4a3ddb5a8437


move from epydoc to sphinx; Closes: #933614


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/933614

Bug#933614: Last remaining dependency for epydoc

[Sandro Tosi]

working on it right now

On Sat, Aug 10, 2019 at 3:03 PM Kenneth Pronovici  wrote:
>
> Hi Sandro,
>
> I just wanted to let you know that this is the last package remaining
> in the archive with a dependency or a build dependency on epydoc.
> Whenever you have a timeline for migrating to your new upstream
> release, please drop a note in here, just so everyone knows what to
> expect.  I appreciate the help.
>
> Thanks!
>
> KEN
>
> --
> Kenneth J. Pronovici 



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#932247: marked as done (ALTER TABLE statements causing "relation already exists" errors when some indexes exist)

[Debian Bug Tracking System]

Your message dated Sat, 10 Aug 2019 23:06:11 +
with message-id 
and subject line Bug#932247: fixed in postgresql-11 11.5-1+deb10u1
has caused the Debian Bug report #932247,
regarding ALTER TABLE statements causing "relation already exists" errors when 
some indexes exist
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.)


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

Hi there!

I've hit a bug with a new installation of puppetdb on buster (e.g. I've
re-created my puppetmaster vagrant box) where puppetdb would fail to start,
erroring out on an SQL upgrade of the database schema during the first service
start.

I'll include the error log lower down since it's pretty long.

I've found a bug report on pupperware (puppet packaged up in docker containers)
that describes exactly the same problem, identifies a faulty postgresql 9.6.x
version and seems to point to an upstream bug report that contains a fix.

https://github.com/puppetlabs/pupperware/issues/82

Since in buster we're using postgresql-11, we've had to identify which version
had introduced the problem. I'm not sure about the exact minor version of
postgres, but for certain when downgrading the debian package to postgres-11
version 11.3-1, then puppetdb is able to start and complete its schema upgrade.
So the bug must have been introduced somewhere between 11.3 and 11.4

The upstream bug report says that there might be a fix for puppetdb available:

https://tickets.puppetlabs.com/browse/PDB-4422

It might be interesting to test applying the fix from the most appropriate
branch (I'm not sure whether 6.0 or 6.3 makes more sense) and then test a new
install with postgresql-11 version 11.4-1 to see if it goes through the schema
upgrade successfully.

Here's the puppetdb log that shows the error happening during the first run of
a new puppetdb 6.2.0-3 install with postgresql-11 version 11.4-1:


--8<8<--
2019-07-15T05:11:14.759-04:00 INFO  [p.p.c.services] PuppetDB version 6.2.0
2019-07-15T05:11:14.760-04:00 WARN  [c.z.h.HikariConfig] The 
initializationFailFast propery is deprecated, see initializationFailTimeout
2019-07-15T05:11:14.761-04:00 INFO  [c.z.h.HikariDataSource] PDBMigrationsPool 
- Starting...
2019-07-15T05:11:14.763-04:00 INFO  [c.z.h.HikariDataSource] PDBMigrationsPool 
- Start completed.
2019-07-15T05:11:15.098-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 28
2019-07-15T05:11:15.564-04:00 INFO  [p.p.s.migrate] Applied database migration 
version 28 in 465 ms
2019-07-15T05:11:15.564-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 29
2019-07-15T05:11:15.865-04:00 INFO  [p.p.s.migrate] Applied database migration 
version 29 in 301 ms
2019-07-15T05:11:15.865-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 30
2019-07-15T05:11:15.870-04:00 INFO  [p.p.s.migrate] Applied database migration 
version 30 in 5 ms
2019-07-15T05:11:15.870-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 31
2019-07-15T05:11:15.897-04:00 INFO  [p.p.s.migrate] Applied database migration 
version 31 in 26 ms
2019-07-15T05:11:15.897-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 32
2019-07-15T05:11:15.916-04:00 INFO  [p.p.s.migrate] Applied database migration 
version 32 in 19 ms
2019-07-15T05:11:15.917-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 33
2019-07-15T05:11:15.940-04:00 INFO  [p.p.s.migrate] Applied database migration 
version 33 in 23 ms
2019-07-15T05:11:15.940-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 34
2019-07-15T05:11:15.992-04:00 INFO  [p.p.s.migrate] Applied database migration 
version 34 in 52 ms
2019-07-15T05:11:15.992-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 35
2019-07-15T05:11:15.993-04:00 INFO  [p.p.s.migrate] Applied database migration 
version 35 in 1 ms
2019-07-15T05:11:15.993-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 36
2019-07-15T05:11:15.995-04:00 INFO  [p.p.s.migrate] Applied database migration 
version 36 in 2 ms
2019-07-15T05:11:15.995-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 37
2019-07-15T05:11:15.997-04:00 INFO  [p.p.s.migrate] Applied database migration 
version 37 in 2 ms
2019-07-15T05:11:15.997-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 38
2019-07-15T05:11:15.999-04:00 INFO  

Bug#933368: marked as done (postgresql: Purging postgresql 9.6 removes content of data_directory without any warning)

[Debian Bug Tracking System]

Your message dated Sat, 10 Aug 2019 23:07:27 +
with message-id 
and subject line Bug#933368: fixed in postgresql-9.6 9.6.15-0+deb9u1
has caused the Debian Bug report #933368,
regarding postgresql: Purging postgresql 9.6 removes content of data_directory 
without any warning
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.)


-- 
933368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933368
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql
Version: 11+200+deb10u1
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

After updating to Debian Buster and postgresql 11 I purged all
postgresql 9.6 packages. Because of this all databases that were in the
data directory specified unser data_directory to be deleted without any
warning. This is not what I expected to happen and lead to data loss.
Apt help message and man page says only that config files are removed,
what I wanted to happen, but says nothing about data. When purging other
packages like mysql-server/mariadb-server the user is asked whether he
wants data to be removed or not. I made an update of MariaDB and other
server software some time ago and got that question, so I expected
PostgreSQL to also show it to me, but that didn't happen.

If it is normal behaviour for packages to remove data when purged, I
think that it should be clearly stated in the help and man. Since it
isn't and other packages don't do that, I think that it is a very
serious issue with the postgresql package.

Michel Le Bihan

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

Kernel: Linux 4.9.0-7-amd64 (SMP w/1 CPU core)
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)

Versions of packages postgresql depends on:
ii  postgresql-11  11.4-1

postgresql recommends no packages.

Versions of packages postgresql suggests:
pn  postgresql-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: postgresql-9.6
Source-Version: 9.6.15-0+deb9u1

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated postgresql-9.6 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, 08 Aug 2019 15:55:21 +0200
Source: postgresql-9.6
Binary: libpq-dev libpq5 libecpg6 libecpg-dev libecpg-compat3 libpgtypes3 
postgresql-9.6 postgresql-9.6-dbg postgresql-client-9.6 
postgresql-server-dev-9.6 postgresql-doc-9.6 postgresql-contrib-9.6 
postgresql-plperl-9.6 postgresql-plpython-9.6 postgresql-plpython3-9.6 
postgresql-pltcl-9.6
Architecture: source
Version: 9.6.15-0+deb9u1
Distribution: stretch-security
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
Changed-By: Christoph Berg 
Description:
 libecpg-compat3 - older version of run-time library for ECPG programs
 libecpg-dev - development files for ECPG (Embedded PostgreSQL for C)
 libecpg6   - run-time library for ECPG programs
 libpgtypes3 - shared library libpgtypes for PostgreSQL 9.6
 libpq-dev  - header files for libpq5 (PostgreSQL library)
 libpq5 - PostgreSQL C client library
 postgresql-9.6 - object-relational SQL database, version 9.6 server
 postgresql-9.6-dbg - debug symbols for postgresql-9.6
 postgresql-client-9.6 - front-end programs for PostgreSQL 9.6
 postgresql-contrib-9.6 - additional facilities for PostgreSQL
 postgresql-doc-9.6 - documentation for the PostgreSQL database management 
system
 postgresql-plperl-9.6 - PL/Perl procedural language for PostgreSQL 9.6
 postgresql-plpython-9.6 - PL/Python procedural language for PostgreSQL 9.6
 postgresql-plpython3-9.6 - PL/Python 3 procedural language for PostgreSQL 9.6
 postgresql-pltcl-9.6 - PL/Tcl procedural language for PostgreSQL 9.6
 postgresql-server-dev-9.6 - development files for PostgreSQL 9.6 server-side 
programming
Closes: 911940 

Bug#923567: marked as done (strong vote against deleting cluster on package purge)

[Debian Bug Tracking System]

Your message dated Sat, 10 Aug 2019 23:07:27 +
with message-id 
and subject line Bug#933368: fixed in postgresql-9.6 9.6.15-0+deb9u1
has caused the Debian Bug report #933368,
regarding strong vote against deleting cluster on package purge
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.)


-- 
933368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933368
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql
Version: 9.6+181+deb9u2

I am creating this bugreport because of a mishap that now has happened
twice to me and I think it does not actually have to happen and maybe
the behavior of the package should be changed.

1) At home I once tried a document management system for my private
home paper work. It worked great until I did a debian upgrade of the
server. Everything worked fine and I also --purge all removed
packages. Then all of sudden the database was gone. After noticing that
I should not have --purge the old version of postgresql I found out
that I had no backups. Since then I work with paper again. Of course it
is my fault, but ...

2) Yesterday at work I did a massive upgrade of all kinds of virtual
machines at the same time. A lot of different services like mail,
fileserver, etc. So again I ran into the pitfall that purging old
packages deletes my postgresql cluster. Of course I have backups but
the work of one day is lost and all employees are very happy of course.
Yes I know it is my fault, but ...


Here are the arguments I have against cleaning up the actual cluster
files when --purge postgresql

a) Compare postgresql to samba or nfs-kernel-server. When purging these
packages, the files on the filesystem which the server was serving will
certainly not be removed. But on postgresql they are.

b) What is worse? Having files not owned by a corresponding package
in /var/lib/postgresql or losing a complete database on system upgrade?

c) Compare this to for example ruby gems. When doing gem install xxx as
root, you will get files in /var/lib/gems/version/... Now when
upgrading the system you will get a new ruby version and when
installing gems, a new version directory will be built. The old one
just stays there and nobody ever deletes it. Especially not the old
ruby packages when you --purge them.



I am sure I am not the only one who fell in this --purge trap. To say
it again, of course it is my own fault, but still I think that the
package should not delete the cluster on --purge. Please rethink that
decision.



Thanks
Erik
--- End Message ---
--- Begin Message ---
Source: postgresql-9.6
Source-Version: 9.6.15-0+deb9u1

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated postgresql-9.6 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, 08 Aug 2019 15:55:21 +0200
Source: postgresql-9.6
Binary: libpq-dev libpq5 libecpg6 libecpg-dev libecpg-compat3 libpgtypes3 
postgresql-9.6 postgresql-9.6-dbg postgresql-client-9.6 
postgresql-server-dev-9.6 postgresql-doc-9.6 postgresql-contrib-9.6 
postgresql-plperl-9.6 postgresql-plpython-9.6 postgresql-plpython3-9.6 
postgresql-pltcl-9.6
Architecture: source
Version: 9.6.15-0+deb9u1
Distribution: stretch-security
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
Changed-By: Christoph Berg 
Description:
 libecpg-compat3 - older version of run-time library for ECPG programs
 libecpg-dev - development files for ECPG (Embedded PostgreSQL for C)
 libecpg6   - run-time library for ECPG programs
 libpgtypes3 - shared library libpgtypes for PostgreSQL 9.6
 libpq-dev  - header files for libpq5 (PostgreSQL library)
 libpq5 - PostgreSQL C client library
 postgresql-9.6 - object-relational SQL database, version 9.6 server
 postgresql-9.6-dbg - debug symbols for postgresql-9.6
 postgresql-client-9.6 - front-end programs for PostgreSQL 9.6
 postgresql-contrib-9.6 - additional facilities for PostgreSQL
 postgresql-doc-9.6 - documentation for the PostgreSQL 

Bug#932247: marked as done (ALTER TABLE statements causing "relation already exists" errors when some indexes exist)

[Debian Bug Tracking System]

Your message dated Sat, 10 Aug 2019 23:07:27 +
with message-id 
and subject line Bug#932247: fixed in postgresql-9.6 9.6.15-0+deb9u1
has caused the Debian Bug report #932247,
regarding ALTER TABLE statements causing "relation already exists" errors when 
some indexes exist
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.)


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

Hi there!

I've hit a bug with a new installation of puppetdb on buster (e.g. I've
re-created my puppetmaster vagrant box) where puppetdb would fail to start,
erroring out on an SQL upgrade of the database schema during the first service
start.

I'll include the error log lower down since it's pretty long.

I've found a bug report on pupperware (puppet packaged up in docker containers)
that describes exactly the same problem, identifies a faulty postgresql 9.6.x
version and seems to point to an upstream bug report that contains a fix.

https://github.com/puppetlabs/pupperware/issues/82

Since in buster we're using postgresql-11, we've had to identify which version
had introduced the problem. I'm not sure about the exact minor version of
postgres, but for certain when downgrading the debian package to postgres-11
version 11.3-1, then puppetdb is able to start and complete its schema upgrade.
So the bug must have been introduced somewhere between 11.3 and 11.4

The upstream bug report says that there might be a fix for puppetdb available:

https://tickets.puppetlabs.com/browse/PDB-4422

It might be interesting to test applying the fix from the most appropriate
branch (I'm not sure whether 6.0 or 6.3 makes more sense) and then test a new
install with postgresql-11 version 11.4-1 to see if it goes through the schema
upgrade successfully.

Here's the puppetdb log that shows the error happening during the first run of
a new puppetdb 6.2.0-3 install with postgresql-11 version 11.4-1:


--8<8<--
2019-07-15T05:11:14.759-04:00 INFO  [p.p.c.services] PuppetDB version 6.2.0
2019-07-15T05:11:14.760-04:00 WARN  [c.z.h.HikariConfig] The 
initializationFailFast propery is deprecated, see initializationFailTimeout
2019-07-15T05:11:14.761-04:00 INFO  [c.z.h.HikariDataSource] PDBMigrationsPool 
- Starting...
2019-07-15T05:11:14.763-04:00 INFO  [c.z.h.HikariDataSource] PDBMigrationsPool 
- Start completed.
2019-07-15T05:11:15.098-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 28
2019-07-15T05:11:15.564-04:00 INFO  [p.p.s.migrate] Applied database migration 
version 28 in 465 ms
2019-07-15T05:11:15.564-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 29
2019-07-15T05:11:15.865-04:00 INFO  [p.p.s.migrate] Applied database migration 
version 29 in 301 ms
2019-07-15T05:11:15.865-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 30
2019-07-15T05:11:15.870-04:00 INFO  [p.p.s.migrate] Applied database migration 
version 30 in 5 ms
2019-07-15T05:11:15.870-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 31
2019-07-15T05:11:15.897-04:00 INFO  [p.p.s.migrate] Applied database migration 
version 31 in 26 ms
2019-07-15T05:11:15.897-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 32
2019-07-15T05:11:15.916-04:00 INFO  [p.p.s.migrate] Applied database migration 
version 32 in 19 ms
2019-07-15T05:11:15.917-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 33
2019-07-15T05:11:15.940-04:00 INFO  [p.p.s.migrate] Applied database migration 
version 33 in 23 ms
2019-07-15T05:11:15.940-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 34
2019-07-15T05:11:15.992-04:00 INFO  [p.p.s.migrate] Applied database migration 
version 34 in 52 ms
2019-07-15T05:11:15.992-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 35
2019-07-15T05:11:15.993-04:00 INFO  [p.p.s.migrate] Applied database migration 
version 35 in 1 ms
2019-07-15T05:11:15.993-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 36
2019-07-15T05:11:15.995-04:00 INFO  [p.p.s.migrate] Applied database migration 
version 36 in 2 ms
2019-07-15T05:11:15.995-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 37
2019-07-15T05:11:15.997-04:00 INFO  [p.p.s.migrate] Applied database migration 
version 37 in 2 ms
2019-07-15T05:11:15.997-04:00 INFO  [p.p.s.migrate] Applying database migration 
version 38
2019-07-15T05:11:15.999-04:00 INFO  

Processed: Re: Bug#918619: [pkg-go] Bug#918619: golang-github-go-errors-errors FTBFS with Go 1.11

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #918619 [src:golang-github-go-errors-errors] golang-github-go-errors-errors 
FTBFS with Go 1.11
Severity set to 'important' from 'serious'
> tags -1 + buster
Bug #918619 [src:golang-github-go-errors-errors] golang-github-go-errors-errors 
FTBFS with Go 1.11
Added tag(s) buster.

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

Bug#918619: [pkg-go] Bug#918619: golang-github-go-errors-errors FTBFS with Go 1.11

[Anthony Fok]

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

Hope my Debian BTS Control pseudo-header commands work this time.  :-)

On Sat, Aug 10, 2019 at 4:17 PM Anthony Fok  wrote:
> severity 918619 important
> tags 918619 + buster
> thanks
>
> On Mon, Jan 7, 2019 at 12:39 PM Adrian Bunk  wrote:
> >
> > Source: golang-github-go-errors-errors
> > Version: 1.0.1-1
> > Severity: serious
> > Tags: ftbfs
> >
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-go-errors-errors.html
> >
> > ...
> > === RUN   TestStackFormat
> > --- FAIL: TestStackFormat (0.00s)
> > error_test.go:33: Stack trace does not contain source line: 'a: b(5)'
> > error_test.go:34: 
> > /build/1st/golang-github-go-errors-errors-1.0.1/obj-x86_64-linux-gnu/src/github.com/go-errors/errors/error_test.go:21
> >  (0x4f5f35)
> > TestStackFormat.func1: e, expected := Errorf("hi"), 
> > callers()
> > /usr/lib/go-1.11/src/runtime/asm_amd64.s:522 (0x455b3b)
> > call32: CALLFN(·call32, 32)
> > /usr/lib/go-1.11/src/runtime/panic.go:513 (0x429df9)
> > gopanic: reflectcall(nil, unsafe.Pointer(d.fn), 
> > deferArgs(d), uint32(d.siz), uint32(d.siz))
> > 
> > /build/1st/golang-github-go-errors-errors-1.0.1/obj-x86_64-linux-gnu/src/github.com/go-errors/errors/error_test.go:245
> >  (0x4f38ff)
> > TestStackFormat: panic('a')
> > /usr/lib/go-1.11/src/testing/testing.go:827 (0x4b573f)
> > tRunner: fn(t)
> > /usr/lib/go-1.11/src/runtime/asm_amd64.s:1333 (0x4576d1)
> > goexit: BYTE$0x90   // NOP
>
> Pleasantly surprisingly, this error no longer occurs with Go 1.12.
> As bullseye (testing) and sid (unstable) have already moved to golang-1.12,
> this FTBFS bug is now only confined to Debian 10 "buster" (stable),
> thus I think it is appropriate to downgrade this bug's severity from
> "serious" to "important" so as not to block testing migration to bullseye.
>
> Cheers,
> Anthony Fok

Bug#918619: [pkg-go] Bug#918619: golang-github-go-errors-errors FTBFS with Go 1.11

[Anthony Fok]

severity 918619 important
tags 918619 + buster
thanks

On Mon, Jan 7, 2019 at 12:39 PM Adrian Bunk  wrote:
>
> Source: golang-github-go-errors-errors
> Version: 1.0.1-1
> Severity: serious
> Tags: ftbfs
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-go-errors-errors.html
>
> ...
> === RUN   TestStackFormat
> --- FAIL: TestStackFormat (0.00s)
> error_test.go:33: Stack trace does not contain source line: 'a: b(5)'
> error_test.go:34: 
> /build/1st/golang-github-go-errors-errors-1.0.1/obj-x86_64-linux-gnu/src/github.com/go-errors/errors/error_test.go:21
>  (0x4f5f35)
> TestStackFormat.func1: e, expected := Errorf("hi"), callers()
> /usr/lib/go-1.11/src/runtime/asm_amd64.s:522 (0x455b3b)
> call32: CALLFN(·call32, 32)
> /usr/lib/go-1.11/src/runtime/panic.go:513 (0x429df9)
> gopanic: reflectcall(nil, unsafe.Pointer(d.fn), deferArgs(d), 
> uint32(d.siz), uint32(d.siz))
> 
> /build/1st/golang-github-go-errors-errors-1.0.1/obj-x86_64-linux-gnu/src/github.com/go-errors/errors/error_test.go:245
>  (0x4f38ff)
> TestStackFormat: panic('a')
> /usr/lib/go-1.11/src/testing/testing.go:827 (0x4b573f)
> tRunner: fn(t)
> /usr/lib/go-1.11/src/runtime/asm_amd64.s:1333 (0x4576d1)
> goexit: BYTE$0x90   // NOP

Pleasantly surprisingly, this error no longer occurs with Go 1.12.
As bullseye (testing) and sid (unstable) have already moved to golang-1.12,
this FTBFS bug is now only confined to Debian 10 "buster" (stable),
thus I think it is appropriate to downgrade this bug's severity from
"serious" to "important" so as not to block testing migration to bullseye.

Cheers,
Anthony Fok

Processed: severity of 923240 is normal

[Debian Bug Tracking System]

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

> severity 923240 normal
Bug #923240 [policykit-1] policykit-1: Please support alternative logind 
implementations
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#933958: marked as done (golang-1.12: ftbfs with golang-1.12)

[Debian Bug Tracking System]

Your message dated Sat, 10 Aug 2019 20:47:03 +
with message-id 
and subject line Bug#933958: fixed in golang-1.11 1.11.12-3
has caused the Debian Bug report #933958,
regarding golang-1.12: ftbfs with golang-1.12
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.)


-- 
933958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933958
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:golang-1.12
Version: 1.12.7-2
Severity: serious

As golang defaults has been upgrade to golang-1.12.
With the test of build golang-1.12, I meet the same problem on
amd64 as currently mipsel.

failed to initialize build cache at
/sbuild-nonexistent/.cache/go-build: mkdir /sbuild-nonexistent:
permission denied

https://buildd.debian.org/status/fetch.php?pkg=golang-1.12=mipsel=1.12.7-2=1564842229=0

-- 
YunQiang Su
--- End Message ---
--- Begin Message ---
Source: golang-1.11
Source-Version: 1.11.12-3

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

Debian distribution maintenance software
pp.
Anthony Fok  (supplier of updated golang-1.11 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, 10 Aug 2019 13:44:21 -0600
Source: golang-1.11
Binary: golang-1.11 golang-1.11-doc golang-1.11-go golang-1.11-src
Architecture: source all amd64
Version: 1.11.12-3
Distribution: unstable
Urgency: medium
Maintainer: Go Compiler Team 
Changed-By: Anthony Fok 
Description:
 golang-1.11 - Go programming language compiler - metapackage
 golang-1.11-doc - Go programming language - documentation
 golang-1.11-go - Go programming language compiler, linker, compiled stdlib
 golang-1.11-src - Go programming language - source files
Closes: 933958
Changes:
 golang-1.11 (1.11.12-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Dr. Tobias Quathamer ]
   * Use dh_missing instead of deprecated dh_install --fail-missing
   * Do not run dh_dwz, there is no debugging information
   * Use debhelper-compat (= 12)
   * Set GOCACHE to fix a FTBFS. (Closes: #933958)
 .
   [ Anthony Fok ]
   * Cherry-pick above Debian fixes in golang-1.12 versions 1.12.7-2 and
 1.12.7-3 by Dr. Tobias Quathamer back to golang-1.11
Checksums-Sha1:
 88087b7ac868d36bb39758925b429a7e92a5a692 2596 golang-1.11_1.11.12-3.dsc
 1c67afb45dd89031654ba17650d92368229cdc4b 29792 
golang-1.11_1.11.12-3.debian.tar.xz
 00a77ce7161bcd3dbbb0cc3b38b6ad59a17560a8 2516800 
golang-1.11-doc_1.11.12-3_all.deb
 fd50aeaee1a38a8d476a45c9d53b7257a2181d28 41901780 
golang-1.11-go_1.11.12-3_amd64.deb
 513563d1130f4efc1c2f98a7495bfb3b444bd335 12993296 
golang-1.11-src_1.11.12-3_amd64.deb
 e230ab069a81d3dd60001b77c4afe997219ab4da 24036 golang-1.11_1.11.12-3_all.deb
 2504c6f6bd3cc229621f8954c8e392da97199813 6619 
golang-1.11_1.11.12-3_amd64.buildinfo
Checksums-Sha256:
 1fff842cc06ae56b9befc569e155d01f5f45b4c1c3a38173d99b396929ada4af 2596 
golang-1.11_1.11.12-3.dsc
 d0d5bfdae58e51baa50598ccb15d033fb428a77545c6f96fbcdd01f2194cf29a 29792 
golang-1.11_1.11.12-3.debian.tar.xz
 1ed3ba9c5a578c3181874ba41158a1b28bc24c35de86455f67edb5fd8489919c 2516800 
golang-1.11-doc_1.11.12-3_all.deb
 58161b73838d22ae5fec99793f9ca0fc7f56c6ae5f78bb274fc730402dfdce97 41901780 
golang-1.11-go_1.11.12-3_amd64.deb
 7b2b640040ff40c14121fb7a06a1b8ac3f1dfa22741f9d7001a82cf94b4b631d 12993296 
golang-1.11-src_1.11.12-3_amd64.deb
 aa814d51d45b82c5dd2379f469b57152a4887d83c4d615f64ec783bbe549acff 24036 
golang-1.11_1.11.12-3_all.deb
 3f17da8a9c41cde8ceb685046e9098dd5e62c8dae2818948497b8d10de7de5e6 6619 
golang-1.11_1.11.12-3_amd64.buildinfo
Files:
 ab5702fc65b1aacb8005945e60106392 2596 devel optional golang-1.11_1.11.12-3.dsc
 7416f732e8866d6cc334917b90a3a4cc 29792 devel optional 
golang-1.11_1.11.12-3.debian.tar.xz
 838f2d9551a54e297e677b9e84743d15 2516800 doc optional 
golang-1.11-doc_1.11.12-3_all.deb
 942605b522a3c3e6445eec735221fd27 41901780 devel optional 
golang-1.11-go_1.11.12-3_amd64.deb
 62bb4794ebb1d1970c30002343daee46 12993296 devel optional 
golang-1.11-src_1.11.12-3_amd64.deb
 f7a884ca40217f61d70f5b317b546ea1 24036 

Bug#933708: marked as done (libgrpc-dev,libgpr3-dev: both packages ship libgpr.a)

[Debian Bug Tracking System]

Your message dated Sat, 10 Aug 2019 20:47:40 +
with message-id 
and subject line Bug#933708: fixed in grpc 1.22.0-2
has caused the Debian Bug report #933708,
regarding libgrpc-dev,libgpr3-dev: both packages ship libgpr.a
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.)


-- 
933708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933708
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgrpc-dev,libgpr3-dev
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 1.17.2-1
Control: found -1 2019-1

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Selecting previously unselected package libgpr3-dev.
  Preparing to unpack .../37-libgpr3-dev_2019-1_amd64.deb ...
  Unpacking libgpr3-dev (2019-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-xYMFQ0/37-libgpr3-dev_2019-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libgpr.a', which is also in 
package libgrpc-dev:amd64 1.17.2-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-xYMFQ0/37-libgpr3-dev_2019-1_amd64.deb


cheers,

Andreas


libgrpc-dev=1.17.2-1_libgpr3-dev=2019-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: grpc
Source-Version: 1.22.0-2

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated grpc 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: Sat, 10 Aug 2019 13:40:28 +
Source: grpc
Architecture: source
Version: 1.22.0-2
Distribution: experimental
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 933708
Changes:
 grpc (1.22.0-2) experimental; urgency=medium
 .
   * Unbreak upstream install foreach.
   * Conflict libgrpc-dev with libgpr3-dev as well (closes: #933708).
Checksums-Sha1:
 4145dd5e3f233f9e5ef6f9b38d853a0c41d7d2e9 2984 grpc_1.22.0-2.dsc
 1bad9c398876febdd9e0f789765d824e6da5a5bc 14660 grpc_1.22.0-2.debian.tar.xz
Checksums-Sha256:
 0615c7db1fe5939918249cf11b3041feeb369c4413ad411589cd4c5117459671 2984 
grpc_1.22.0-2.dsc
 00871c41010ed8fad37a2ae4e96b8b25b7fcea480de9fb5ba1bf21a862fd15e0 14660 
grpc_1.22.0-2.debian.tar.xz
Files:
 51433db476564738574ababbcf1aed82 2984 libs optional grpc_1.22.0-2.dsc
 c17ab3f9055258d05505f5a60f49bece 14660 libs optional 
grpc_1.22.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl1PHMsACgkQ3OMQ54ZM
yL/SyRAAhizffWSk8ei8s/+Lp1NI4bVxwtQVX7ik6eehZWWWAUM/d3AoS5eebgzk
w6UoZ+9Fr5UCoIaosuuhXwGaglhloRP9W3+lPhuOg7k++QFDI6FIMgcdVsUrylxy
4XhwjX7RqmxqAjYyW4OUr9QvBhsTNTA9JZz6RH3CGXgrUBeijqh2C2gOINoFjrfW
oRzlfWY2NixgG0d3e3pp2LNDdH6HnswH+rwh5FUYNoRZ1CLreAjD1b1Yf9z5qeVI
K+ql4Tms147JhrwCwg8JTOlpgVWGkqHkQ/Kn5dxjlyEADdOHtNoiAb4Jz4lJk3k5
476tAvywmJRrnbUCLJ74A+omie/B8nlqCr9ZDK+98gSp5yzn3RFXLYMO4vbqtgM3
/PP/2Rpg3gASNPYsnVpvzbaB2PMIXLIFvYlPi+OI5HIyBeoDCZ36N60Gwrjdg/ND
NuSrfaSUzp8JUjhERAEUOzBV0js9f6l3orngPunvmjPyQca4yemmTAmgfzkzLFLJ
GcGyi3Azuktyj7VJ8XnEfWnhoEjrjf5zUpJa0IzbhIZW+7ecbEP+LEzhuwNIczGY
ueEWK/1XE8p8oEQ+Po/rFUmLeTt7AZSEJbJCGnKU7gZ3Jpx5+8hvoBB9nQHin5vn
6p4p+7lsTQJbL02L4AW5gj1TytOz8jT/QNnh33D76g3/FnK8ZMs=
=eFbp
-END PGP SIGNATURE End Message ---

Bug#933616: marked as done (openvdb: Epydoc will be removed)

[Debian Bug Tracking System]

Your message dated Sat, 10 Aug 2019 19:09:52 +
with message-id 
and subject line Bug#933616: fixed in openvdb 5.2.0-5.1
has caused the Debian Bug report #933616,
regarding openvdb: Epydoc will be removed
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.)


-- 
933616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openvdb
Severity: serious
Justification: Policy 5.9.2

Hi,

This is one of 20+ packages in the archive that still depend on Epydoc.  I
have filed a bug with ftp.debian.org to have epydoc removed from unstable.
Besides its lack of support for Python 3, epydoc has been completely
unsupported upstream for close to a decade.  It really should have been removed
from the archive years ago.

I apologize for the late notice on this.  I filed bugs against all of the
dependencies I could find over 18 months ago, but the FTP Master list included
some additional packages.

If I don't hear back from you, I will NMU a version of your package that removes
the build dependency.  I will accomplish this by simply not building the API
documentation.  If you don't want me to do this, please reply and let me know
how you want me to proceed.

Thanks,

KEN
--- End Message ---
--- Begin Message ---
Source: openvdb
Source-Version: 5.2.0-5.1

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

Debian distribution maintenance software
pp.
Kenneth J. Pronovici  (supplier of updated openvdb 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, 02 Aug 2019 19:14:40 +
Source: openvdb
Architecture: source
Version: 5.2.0-5.1
Distribution: unstable
Urgency: medium
Maintainer: Mathieu Malaterre 
Changed-By: Kenneth J. Pronovici 
Closes: 933616
Changes:
 openvdb (5.2.0-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Eliminate dependency on epydoc, which will be removed (closes: #933616)
 - Update debian/control to remove Build-Depends-Indep: python-epydoc
 - Update debian/rules to no longer build epydoc documentation
Checksums-Sha1:
 e807f78c641e9aba9182f6e49c5685c27ca603de 2530 openvdb_5.2.0-5.1.dsc
 cca45dce2d33e8e003d3474a17292c48adf93abe 15296 openvdb_5.2.0-5.1.debian.tar.xz
 96b6a657c0b70c7fc1fb53818db1ec99ef3f411a 11010 
openvdb_5.2.0-5.1_source.buildinfo
Checksums-Sha256:
 a3c91802af2591dacba58fe69b26cf97128561da17427d85f736b11646725f8f 2530 
openvdb_5.2.0-5.1.dsc
 8004469e22918db049605fdbd38722e60cbfdbc31dacfeaee2c440182081efcf 15296 
openvdb_5.2.0-5.1.debian.tar.xz
 e550dbff20f69e6ad64880896c420ec40dfeed1a44c55342c378de11c0d7 11010 
openvdb_5.2.0-5.1_source.buildinfo
Files:
 308f9e18eb0411e1f3f3d0298da8b12e 2530 libs optional openvdb_5.2.0-5.1.dsc
 0c860493aa90c111e9edd64422c287d4 15296 libs optional 
openvdb_5.2.0-5.1.debian.tar.xz
 ae4255255c9964c9dfeafb9344f96df2 11010 libs optional 
openvdb_5.2.0-5.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECkY/XOB9CXm1xckHERkoku/XWTQFAl1Liq8ACgkQERkoku/X
WTTdIA//VM5upEz4GM15C3jJWT1Gz6KnXEEznZvjDac6+Qs9iFEIM59+P4IuFB5N
89nA5ZEaEAmN/qNtx7SVLpfaGHHyeC7LoCY8Mjtb1ukd05dFCqxmyglg41310+IP
u5ENxzemVcp4gTanW/vM4Dq2Dlv1T8cS0J/FC/D61VhYVFkwNY7UjCjlAUIXyv+i
w540cw4xyrwEop0qB6LmgmguSF4v05iZH5b+K/27Cd6Mupasxb27BouzoUaeM2b8
s7FmJ8G4Jf/ThVf1AnvynI+3RD5zE9vmdYAwP5zs1C6sSqqg+tJwtFb1vpVHhjl8
poZpqcqeUz5ncPXFdiNMBzIufC0ki83adJS/d9RaY1wUmKwccVcTDg3KeVuCrjJj
Ika7X2vjls5+R32UmVZEQX+qNLQJkgjH05Rmr3lcSnj6GlhJszS+iDXYqWyony2p
O5LisNX1ZT7qvoQgTWZS9MJr6+ZLPIA4Nbufq3piFsuuitx4RYt8vxNYs6NhmgFL
jyubLQl8QAD/1yao+Pt2s/T4ySk47xe9DIR8OFdVTPNiFyHmmmCoa8cgVfDakFZM
065zJQNQtiTUjIyT681UiB/GmdHv1wWT+7GdhFLvLjKR4MGth+9eqoNyXcu0R90F
QiIrY+y6eiH/0QA+NKemK9CpyGb1K1z/ksPHvybBM0cRsXhkxRc=
=RTmW
-END PGP SIGNATURE End Message ---

Bug#934215: qtbase5-dev: trying to overwrite shared ....png which is different from other instances of the package

[Lisandro Damián Nicanor Pérez Meyer]

Hi!

El sáb., 10 ago. 2019 15:28, Dmitry Shachnev  escribió:

> Hi all,
>
> On Thu, Aug 08, 2019 at 02:10:39PM -0300, Lisandro Damián Nicanor Pérez
> Meyer wrote:
> > > I had to use dpkg --force-overwrite to work around it, which showed the
> > > additional messages:
> > >
> > > Preparing to unpack .../qtbase5-dev_5.11.3+dfsg1-2+b1_i386.deb ...
> > > Unpacking qtbase5-dev:i386 (5.11.3+dfsg1-2+b1) over (5.11.3+dfsg1-2)
> ...
> > > dpkg: warning: overriding problem because --force enabled:
> > > dpkg: warning: trying to overwrite shared
> '/usr/share/qt5/doc/global/template/images/Qt-logo.png', which is different
> from other instances of package qtbase5-dev:i386
> > > dpkg: warning: overriding problem because --force enabled:
> > > dpkg: warning: trying to overwrite shared
> '/usr/share/qt5/doc/global/template/images/ico_out.png', which is different
> from other instances of package qtbase5-dev:i386
> > > dpkg: warning: overriding problem because --force enabled:
> > > dpkg: warning: trying to overwrite shared
> '/usr/share/qt5/doc/global/template/style/list_arrow.png', which is
> different from other instances of package qtbase5-dev:i386
> > > dpkg: warning: overriding problem because --force enabled:
> > > dpkg: warning: trying to overwrite shared
> '/usr/share/qt5/doc/global/template/style/list_expand.png', which is
> different from other instances of package qtbase5-dev:i386
> > >
> > > Usually, for a multiarch issue, the +b1 in the version number would
> make me suspicious, but maybe not here, the image seems to contain a
> creation time.
> >
> > So we have two issues here:
> >
> > - On one side those images should not have a creation date due to
> >  reproducibility. Actually this has never happened before and buildds
> might
> >  have built everything in deifferent dates.
> > - On the other I wonder why I left those files there. This comes from
> 2015,
> >  so I'll have to dig into it further.
>
> The issue is caused by dh_strip_nondeterminism changing PNG metadata
> timestamps to dates from binNMUs, which are different on amd64 and i386.
>
> I have just filed a bug against debhelper and described this issue in
> more detail, see https://bugs.debian.org/934405.
>
> As a workaround, we should tell dh_strip_nondeterminism to ignore these
> files using its -X option. I will be able to do that in a couple of days.
>

That's a part of it. I sincerely don't remember why I kept those files
there instead than -doc.

>

Bug#933614: Last remaining dependency for epydoc

[Kenneth Pronovici]

Hi Sandro,

I just wanted to let you know that this is the last package remaining
in the archive with a dependency or a build dependency on epydoc.
Whenever you have a timeline for migrating to your new upstream
release, please drop a note in here, just so everyone knows what to
expect.  I appreciate the help.

Thanks!

KEN

-- 
Kenneth J. Pronovici 

Bug#934215: qtbase5-dev: trying to overwrite shared ....png which is different from other instances of the package

[Dmitry Shachnev]

Hi all,

On Thu, Aug 08, 2019 at 02:10:39PM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> > I had to use dpkg --force-overwrite to work around it, which showed the
> > additional messages:
> >
> > Preparing to unpack .../qtbase5-dev_5.11.3+dfsg1-2+b1_i386.deb ...
> > Unpacking qtbase5-dev:i386 (5.11.3+dfsg1-2+b1) over (5.11.3+dfsg1-2) ...
> > dpkg: warning: overriding problem because --force enabled:
> > dpkg: warning: trying to overwrite shared 
> > '/usr/share/qt5/doc/global/template/images/Qt-logo.png', which is different 
> > from other instances of package qtbase5-dev:i386
> > dpkg: warning: overriding problem because --force enabled:
> > dpkg: warning: trying to overwrite shared 
> > '/usr/share/qt5/doc/global/template/images/ico_out.png', which is different 
> > from other instances of package qtbase5-dev:i386
> > dpkg: warning: overriding problem because --force enabled:
> > dpkg: warning: trying to overwrite shared 
> > '/usr/share/qt5/doc/global/template/style/list_arrow.png', which is 
> > different from other instances of package qtbase5-dev:i386
> > dpkg: warning: overriding problem because --force enabled:
> > dpkg: warning: trying to overwrite shared 
> > '/usr/share/qt5/doc/global/template/style/list_expand.png', which is 
> > different from other instances of package qtbase5-dev:i386
> >
> > Usually, for a multiarch issue, the +b1 in the version number would make me 
> > suspicious, but maybe not here, the image seems to contain a creation time.
>
> So we have two issues here:
>
> - On one side those images should not have a creation date due to
>  reproducibility. Actually this has never happened before and buildds might
>  have built everything in deifferent dates.
> - On the other I wonder why I left those files there. This comes from 2015,
>  so I'll have to dig into it further.

The issue is caused by dh_strip_nondeterminism changing PNG metadata
timestamps to dates from binNMUs, which are different on amd64 and i386.

I have just filed a bug against debhelper and described this issue in
more detail, see https://bugs.debian.org/934405.

As a workaround, we should tell dh_strip_nondeterminism to ignore these
files using its -X option. I will be able to do that in a couple of days.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#934390: marked as done (totem, nautilus: not co-installable in unstable)

[Debian Bug Tracking System]

Your message dated Sat, 10 Aug 2019 18:13:06 +
with message-id 
and subject line Bug#934390: fixed in totem 3.32.0-2
has caused the Debian Bug report #934390,
regarding totem, nautilus: not co-installable in unstable
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.)


-- 
934390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: totem,nautilus
Version: 3.30.0-4,3.32.3-1
Severity: serious
Tags: sid
Justification: GNOME team member opinion
Affects: gnome-core

nautilus (>= 3.32.1-1) Breaks/Replaces totem (<< 3.31.91-1), making
gnome-core non-installable in unstable. I think this should be considered
RC. It can be addressed by uploading either totem 3.32 (formerly in
experimental) or 3.33 (now in experimental) to unstable.

I'll look at whether totem 3.32 is ready to upload to unstable.

smcv
--- End Message ---
--- Begin Message ---
Source: totem
Source-Version: 3.32.0-2

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated totem 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, 10 Aug 2019 18:15:26 +0100
Source: totem
Architecture: source
Version: 3.32.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 934390
Changes:
 totem (3.32.0-2) unstable; urgency=medium
 .
   * Team upload
   * d/gbp.conf: Select debian/unstable, upstream/3.32.x branches
   * Upload to unstable to restore co-installability with nautilus 3.32.x
 (Closes: #934390)
 .
 totem (3.32.0-1) experimental; urgency=medium
 .
   * New upstream release
   * Build-Depend on dh-sequence-gir, dh-sequence-gnome, & dh-sequence-python3
 .
 totem (3.31.91-1) experimental; urgency=medium
 .
   * New upstream development release
   * Drop totem-plugin-gromit and totem-plugin-zeitgeist: No longer provided
   * debian/totem-plugins.install: ontop plugin is no longer provided
   * debian/totem.install: Nautilus 3.32 now handles showing audio/video
 properties itself
   * Bump minimum meson to 0.46.0
   * Drop obsolete Build-Depends:
 - intltool, libnautilus-extension-dev, libx11-dev, libxrandr-dev,
   libxxf86vm-dev, valac, x11proto-core-dev
   * Use xvfb for build tests
   * Drop obsolete make-gromit-and-zeitgeist-plugins-builtin.patch
Checksums-Sha1:
 15aa0e6ec67f3ab0a338ac90227e89bf9a3224c8  totem_3.32.0-2.dsc
 0ac0c4a8cfdeeba6277fe2d5ba10ff3989d77a4c 25608 totem_3.32.0-2.debian.tar.xz
Checksums-Sha256:
 35c86199885584ce31b1366c40b66a845975d3ebadd23ac63148ff06a3195579  
totem_3.32.0-2.dsc
 7c232293a082a85c6a2ff6df25e7f1b0cba376dc272131d609357b2a2779ecec 25608 
totem_3.32.0-2.debian.tar.xz
Files:
 b43889ea30a468d55c47a3a6b877b197  video optional totem_3.32.0-2.dsc
 74cef014a0a00977c4d1813852a5f1a9 25608 video optional 
totem_3.32.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl1PAbUQHHNtY3ZAZGVi
aWFuLm9yZwAKCRDgWuFHj4FMT3eiD/9SzcrIphzle8mxzD2g0VywKZY9FMD0sTCX
InYUhB+mzeOBgOOXf9372eWdfx6lYFjRObKBVAsyXfLCKLO14Vx3Xli086vxagFQ
/yAOFbWsRq98apL14JLKMlVD5bOr2/4ockzuVUlo5YftMPWNuPXL+vlcS2mR2rDw
kDKBBwSLqu0eJ5o3edtjpfFJBGhiv9pjK1UExtiN9I8NThQ1DGVwR4VNmvAMGw3M
tqbqOxlqDglc1qffzeprBrEALnMm3omF9N9uOAC2OXPCktIhSxAvWgoj/Y644Fp8
UPYg0ZI+HNPwWEafRO5nUqEWkxdYOE+Kxi84yrsp1AS6VYPGANG0Kjr0qQ1xiKSI
oMaGPc+CTSGe0D5Wj5WSYnlBJo2yXi5OCmPgmXC6j0egGaG73ktdyoNh7y1vnngy
jtwK7ATdzCYsB6jKV21apocsaXvh4SBQVNmUyzEXmojOOag1xO3dx091fyZdg6V7
Tt6RXYF/TYUb56bWmSgZvrfDZNQZMTMKRH6VRWDowU40UVV+wllNP2+q9FkEvx56
QUmKB5+9K1XgFaWcPsuByQgse361NIIWDoyHa/9uwShXP64mcqjPlquzfcQ6Y7ZY
KN+b1JsvJkUyFGdlnWd927X0XhPZT/kWSvvblJef0UNZOxJ70/8TR6FV3hOY3RAC
ugZoBQF0vg==
=IQan
-END PGP SIGNATURE End Message ---

Processed: Merging 934215 934265

[Debian Bug Tracking System]

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

> severity 934215 serious
Bug #934215 [qtbase5-dev] qtbase5-dev: trying to overwrite shared png which 
is different from other instances of the package
Severity set to 'serious' from 'normal'
> merge 934215 934265
Bug #934215 [qtbase5-dev] qtbase5-dev: trying to overwrite shared png which 
is different from other instances of the package
Bug #934265 [qtbase5-dev] qtbase5-dev: different archs ship different version 
of Qt-logo.png
Merged 934215 934265
> thanks
Stopping processing here.

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

Processed: limit source to dgit, tagging 933827, tagging 934126

[Debian Bug Tracking System]

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

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

> tags 933827 + pending
Bug #933827 [dgit] "dgit fetch" fails with "cannot remove directory for ..."
Added tag(s) pending.
> tags 934126 + pending
Bug #934126 [dgit] malfunctions due to being confused about git repository
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#926521: marked as done (libgps changed API of gps_read)

[Debian Bug Tracking System]

Your message dated Sat, 10 Aug 2019 17:19:48 +
with message-id 
and subject line Bug#934377: Removed package(s) from unstable
has caused the Debian Bug report #926521,
regarding libgps changed API of gps_read
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.)


-- 
926521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: obdgpslogger
Version: 0.16-1.4

Hi,
libgps changed the gps_read implementation in [0].
The change is easily done, I checked it against the gpsd build in
experimental and it works.

Upstream only has an SVN and no bug management.
I wondered if i should send a mail to their ML [1] pointing to this
bug later on.
But actually this only applies when debian/patches/gpsd_v3 is applied.
So not affecting outdated upstream atm.

I found no salsa entry for this package, so I'll attach a debdiff here
once I have a bug number.

[0]: https://git.savannah.gnu.org/cgit/gpsd.git/commit/?id=6bba8b329
[1]: http://icculus.org/mailman/listinfo/obdgpslogger

-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
--- End Message ---
--- Begin Message ---
Version: 0.16-1.3+rm

Dear submitter,

as the package obdgpslogger has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/934377

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#934344: nvidia-kernel-dkms: nvidia kernel driver does not build with linux-5.2

[Andrei Demekhov]

This bug seems to have a known origin:  
https://garajau.com.br/2019/07/compiling-nvidia-418-on-kernel-52

Best
Andrei

Processed: Re: monkeysphere: FTBFS randomly (failing tests)

[Debian Bug Tracking System]

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

> tags 934034 + patch
Bug #934034 [src:monkeysphere] monkeysphere: FTBFS in stretch (failing tests)
Added tag(s) patch.
> tags 861457 - patch
Bug #861457 [src:monkeysphere] monkeysphere: FTBFS randomly (failing tests)
Removed tag(s) patch.
> thanks
Stopping processing here.

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

Bug#934034: monkeysphere: FTBFS randomly (failing tests)

[Chris Lamb]

tags 934034 + patch
tags 861457 - patch
thanks

[Adding 934...@bugs.debian.org to CC]

Hi Santiago,

> Maybe you mean #934034 instead of #861457?

Wrong bug indeed. Fixing...


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   ` tests/keytrans.orig 2019-08-10 16:57:43.645067702 +0100
+++ tests/keytrans  2019-08-10 16:57:48.157103304 +0100
@@ -137,9 +137,9 @@
 cat >"$TEMPDIR"/expectedout <"$TEMPDIR"/expectedout <"$TEMPDIR"/expectedout <

Bug#934034: monkeysphere: FTBFS in stretch

[Santiago Vila]

Hi.

I confirm that the patch by Chris Lamb fixes the build failure.

For completeness I would also make the build-dependency on gnupg to be
versioned.

Thanks.

Bug#932108: nextcloud-desktop-cmd: Missing nextcloud-desktop-common leads to error "Cannot load system exclude list[...]"

[Calogero Lo Leggio]

Hi,

I think it's sufficient to add 'nextcloud-desktop-common' in the
nextcloud-desktop-cmd dependencies


$ diff -u control.old control

--- control.old    2019-05-17 04:35:50.0 +0200
+++ control    2019-08-10 18:58:11.490413351 +0200
@@ -122,6 +122,7 @@
 Architecture: any
 Depends: libnextcloudsync0 (= ${binary:Version}),
  libqt5sql5-sqlite,
+ nextcloud-desktop-common,
  nextcloud-desktop-l10n,
  ${misc:Depends},
  ${shlibs:Depends}





signature.asc
Description: OpenPGP digital signature

Bug#873501: marked as done (kivy FTBFS with Cython 0.26)

[Debian Bug Tracking System]

Your message dated Sat, 10 Aug 2019 16:19:56 +
with message-id 
and subject line Bug#873501: fixed in kivy 1.10.1-1
has caused the Debian Bug report #873501,
regarding kivy FTBFS with Cython 0.26
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.)


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

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

...
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/local/include/SDL2 -I/usr/include/SDL2 -I/usr/include/python2.7 -c 
kivy/core/text/_text_sdl2.c -o 
build/temp.linux-amd64-2.7/kivy/core/text/_text_sdl2.o
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-qMUuQf/python2.7-2.7.13=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 build/temp.linux-amd64-2.7/kivy/core/text/_text_sdl2.o -lGL 
-lSDL2 -lSDL2_ttf -lSDL2_image -lSDL2_mixer -o 
/build/1st/kivy-1.9.1/.pybuild/pythonX.Y_2.7/build/kivy/core/text/_text_sdl2.so 
-L/usr/local/include/SDL2 -L/usr/include/SDL2 -lm
cythoning kivy/graphics/opengl.pyx to kivy/graphics/opengl.c
 
 Error compiling Cython file:
 
 ...
 def glCheckFramebufferStatus(GLenum target):
 '''See: `glCheckFramebufferStatus() on Kronos website
 
`_
 '''
 cdef GLenum result
 result = c_opengl.CheckFramebufferStatus(target)
 ^
 
 
 kivy/graphics/opengl.pyx:544:21: cimported module has no attribute 
'CheckFramebufferStatus'
building 'kivy.graphics.opengl' extension
creating build/temp.linux-amd64-2.7/kivy/graphics
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/python2.7 -c kivy/graphics/opengl.c -o 
build/temp.linux-amd64-2.7/kivy/graphics/opengl.o
kivy/graphics/opengl.c:1:2: error: #error Do not use this file, it is the 
result of a failed Cython compilation.
 #error Do not use this file, it is the result of a failed Cython compilation.
  ^
 error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:283: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 
dh_auto_build: pybuild --build -i python{version} -p 2.7 returned exit code 13
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 25
--- End Message ---
--- Begin Message ---
Source: kivy
Source-Version: 1.10.1-1

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

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

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated kivy 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: Sat, 10 Aug 2019 17:28:45 +0200
Source: kivy
Architecture: source
Version: 1.10.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Closes: 873501
Changes:
 kivy (1.10.1-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Manas Kashyap ]
   * Upstream Release (Closes: #873501)
 .
   [ Vincent Cheng ]
   * Update watch file.
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/watch: Use https protocol
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove 

Bug#931507: kernel-wedge: HDA sound board detection takes 60s in d-i

[Samuel Thibault]

Ben Hutchings, le sam. 10 août 2019 16:24:47 +0100, a ecrit:
> I thought you also wanted us to add i915 to the installer though?

It was just another way of fixing the problem with no source change:
instead of waiting for the load of a non-available module, that module
could just be shipped.

Samuel

Bug#934194: iwd: Missing directory prevents starting on initial install

[Andreas Henriksson]

Control: forwarded -1 https://lists.01.org/pipermail/iwd/2019-August/006853.html

I've submitted a patch upstream that should adress this issue. Lets give
them some time to review and comment on it...

Regards,
Andreas Henriksson

Processed: Re: Bug#934194: iwd: Missing directory prevents starting on initial install

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://lists.01.org/pipermail/iwd/2019-August/006853.html
Bug #934194 [iwd] iwd: Missing directory prevents starting on initial install
Set Bug forwarded-to-address to 
'https://lists.01.org/pipermail/iwd/2019-August/006853.html'.

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

Bug#934390: totem, nautilus: not co-installable in unstable

[Simon McVittie]

Package: totem,nautilus
Version: 3.30.0-4,3.32.3-1
Severity: serious
Tags: sid
Justification: GNOME team member opinion
Affects: gnome-core

nautilus (>= 3.32.1-1) Breaks/Replaces totem (<< 3.31.91-1), making
gnome-core non-installable in unstable. I think this should be considered
RC. It can be addressed by uploading either totem 3.32 (formerly in
experimental) or 3.33 (now in experimental) to unstable.

I'll look at whether totem 3.32 is ready to upload to unstable.

smcv

Bug#931507: kernel-wedge: HDA sound board detection takes 60s in d-i

[Ben Hutchings]

On Sat, 2019-08-10 at 00:29 +0200, Samuel Thibault wrote:
> close 931507 5.2.7-1
> thanks
> 
> Hello,
> 
> The patch was included in the 5.2.7 stable release.
> 
> Is a 4.19 kernel.org update planned to be uploaded before 10.1? If not,
> could we include the patch in the package in time for 10.1?

Yes we will update to a new 4.19.y release.

I thought you also wanted us to add i915 to the installer though?  Did
you open a separate bug for that?

Ben.

-- 
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein




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

Processed: tagging 934383, severity of 934383 is important

[Debian Bug Tracking System]

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

> tags 934383 - ipv6
Bug #934383 [debian-installer] debian-install: Package fails attempting to 
access USB WiFi
Removed tag(s) ipv6.
> severity 934383 important
Bug #934383 [debian-installer] debian-install: Package fails attempting to 
access USB WiFi
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#934340: Please remove the dependency on obus and camlp4

[Thomas Leonard]

On Sat, 10 Aug 2019 at 01:54, Stéphane Glondu  wrote:
>
> Source: zeroinstall-injector
> Version: 2.12.3-2
> Severity: serious
>
> Dear Maintainer,
>
> zeroinstall-injector build depends on obus, which is affected by
> [1]. According to [2], it is an optional dependency. Please provide a
> version of zeroinstall-injector without the dependency on obus.

obus is only optional on systems that don't use D-BUS. It is needed on Debian.

https://github.com/ocaml-community/obus/blob/master/CHANGES.md says:

1.2.0 (2019-07-04)
- remove all Camlp4 dependencies

So I think Debian can just update to that.

> It also seems that the latest upstream version of zeroinstall-injector
> is buildable without camlp4. Please drop the dependency in the Debian
> package as well.

I don't believe there is a dependency in the Debian package at the
moment (except indirectly via Debian's old version of obus).
According to 
https://github.com/0install/0install-debian/commit/dbea82da611eb9091cf36cbf8668dd40b8915057
the direct dependency was removed on Sun, 19 Nov 2017.

> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933992
> [2] https://opam.ocaml.org/packages/0install/


-- 
talex5 (GitHub/Twitter)http://roscidus.com/blog/
GPG: 5DD5 8D70 899C 454A 966D  6A51 7513 3C8F 94F6 E0CC

Bug#933774: marked as done (python3-pulp: Empty package)

[Debian Bug Tracking System]

Your message dated Sat, 10 Aug 2019 14:55:08 +
with message-id 
and subject line Bug#933774: fixed in python-pulp 1.6.0+dfsg1-4
has caused the Debian Bug report #933774,
regarding python3-pulp: Empty package
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.)


-- 
933774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pulp
Version: 1.6.0+dfsg1-3
Severity: normal

Dear Maintainer,

The package only contains:

/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/python3-pulp
/usr/share/doc/python3-pulp/changelog.Debian.gz
/usr/share/doc/python3-pulp/changelog.gz
/usr/share/doc/python3-pulp/copyright



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

Kernel: Linux 4.19.0-5-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), 
LANGUAGE=zh_CN.UTF-8:zh_TW.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-pulp depends on:
ii  coinor-cbc 2.9.9+repack1-1
ii  python3-pyparsing  2.2.0+dfsg1-2

python3-pulp recommends no packages.

python3-pulp suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python-pulp
Source-Version: 1.6.0+dfsg1-4

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-pulp 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: Sat, 10 Aug 2019 15:33:55 +0200
Source: python-pulp
Architecture: source
Version: 1.6.0+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Ondřej Nový 
Closes: 933774
Changes:
 python-pulp (1.6.0+dfsg1-4) unstable; urgency=medium
 .
   * Team upload.
   * Use pybuild for building package (Closes: #933774).
   * Enable autopkgtest-pkg-python testsuite.
   * Bump debhelper compat level to 12.
   * Bump standards version to 4.4.0 (no changes).
Checksums-Sha1:
 1637f5949b12d8b75c509e953aef24487c1ed581 2160 python-pulp_1.6.0+dfsg1-4.dsc
 b1cf28e91afb68124d11a63b929a484e1b86f328 12096 
python-pulp_1.6.0+dfsg1-4.debian.tar.xz
 9b7c76438c07b2ad17033d8603439261e5c5779e 6476 
python-pulp_1.6.0+dfsg1-4_amd64.buildinfo
Checksums-Sha256:
 bde2b1dab63f612d50a4d6674be0120a0e419cff3a3c96236b189578b106ad10 2160 
python-pulp_1.6.0+dfsg1-4.dsc
 668990b9a8f56397c9ab8f8e2bee8cae1a42dd5070acca64d88a322114fa4232 12096 
python-pulp_1.6.0+dfsg1-4.debian.tar.xz
 6f4e12ed6a583d470c5ed38a256acf63963d95664a8a8ab39c8a2c499f817611 6476 
python-pulp_1.6.0+dfsg1-4_amd64.buildinfo
Files:
 808f8f7fce80bb80df9e302897894d60 2160 python optional 
python-pulp_1.6.0+dfsg1-4.dsc
 8855bcd34498a37d963c63337fecc03d 12096 python optional 
python-pulp_1.6.0+dfsg1-4.debian.tar.xz
 1781a75618811e398c11ed1b0781c7b3 6476 python optional 
python-pulp_1.6.0+dfsg1-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAl1OyC4ACgkQNXMSVZ0e
Bkvwig/9GUV53bj+mp7wIF0IosruwwpSqUBrBZNQ5Q0akM9qaccJV2nwX0lPJG7i
rjViTNfMvCTtdvf7HzWfnbHwzrFpERfL44RgMqllSIxz8xNaw6V1gQ732os5nvYf
P17/jdsxZWq+6qcZw0yL2MmHmQyxtJUrv+71gKLJLsHqWl8LWMf3DwO7MeXdFkT6
3/t7Z4uQMZWXamojyFLlMrk0ui5nFjRgfZdbjOoUyEa0pl9ncUbLVzrkok3oc8uh
04D9Hxtpm2yOoL3kooT/igHGP1MCg+c5koBHZ/CfgVc4NflFUgeJ7Js/u47/Ji16
gCD0IG9oVJwrKSiDPwES70WyC7+f2QS9Z2v4G0Xom3tenxO/u5VP2yyRynIp/S2b
yhp99rCLPLSSt94WvaBDI8t1VDumN69g6G8oXK6HV7txmPDfQgvobu1GQWlpd3mI
JmKBadjpep1w6Ov54ErTomrNxrTtRvb2vKSrYYDIdavjxZP/M+VvWQonjNl2QQCI
CeoUJijw8mUyFYd3y3nkTW1LM+B6E4GBLkkwMWO1QW3nvrA8jMlK4ihaMbkCmg8A
5mezof6WAFNsUVM4LxSA7GEiYEmCZNA9WUCjY9xv9B8Y0/Q3CxgnsSp9IEb60IY6
f+vCVnE8gU+P/ku2Af0jAJNfu3+j2/CSwzjN5bNsLydBqmC70KA=
=2Yel
-END PGP SIGNATURE End Message ---

Bug#934384: libvma: FTBFS: some symbols or patterns disappeared

[Niko Tyni]

Source: libvma
Version: 8.8.1.really.8.7.7-1
Severity: serious
Tags: ftbfs

This package fails to build on current sid/amd64.

>From my build log:

  dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
  dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
  dpkg-gensymbols: warning: debian/libvma8/DEBIAN/symbols doesn't match 
completely debian/libvma8.symbols
  --- debian/libvma8.symbols (libvma8_8.8.1.really.8.7.7-1_amd64)
  +++ dpkg-gensymbolsBhlY4G   2019-08-10 14:41:41.948238949 +
  @@ -542,7 +542,7 @@
_ZN12sockinfo_tcp2rxE9rx_call_tP5ioveclPiP8sockaddrPjP6msghdr@Base 
8.8.1.really.8.7.7
_ZN12sockinfo_tcp2txE9tx_call_tPK5iovecliPK8sockaddrj@Base 
8.8.1.really.8.7.7

_ZN12sockinfo_tcp30create_flow_tuple_key_from_pcbER10flow_tupleP7tcp_pcb@Base 
8.8.1.really.8.7.7
  - _ZN12sockinfo_tcp30return_reuse_buffers_postponedEv@Base 8.8.1.really.8.7.7
  +#MISSING: 8.8.1.really.8.7.7-1# 
_ZN12sockinfo_tcp30return_reuse_buffers_postponedEv@Base 8.8.1.really.8.7.7
_ZN12sockinfo_tcp4bindEPK8sockaddrj@Base 8.8.1.really.8.7.7
_ZN12sockinfo_tcp5fcntlEim@Base 8.8.1.really.8.7.7
_ZN12sockinfo_tcp5ioctlEmm@Base 8.8.1.really.8.7.7
  [...]
  dh_makeshlibs: failing due to earlier errors
  make: *** [debian/rules:15: binary] Error 255
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

-- 
Niko Tyni   nt...@debian.org

Processed: block iwd from testing migration

[Debian Bug Tracking System]

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

> severity 934194 serious
Bug #934194 [iwd] iwd: Missing directory prevents starting on initial install
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: Re: Bug#934383: debian-install: Package fails attempting to access USB WiFi

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 debian-installer
Bug #934383 [debian-install] debian-install: Package fails attempting to access 
USB WiFi
Warning: Unknown package 'debian-install'
Bug reassigned from package 'debian-install' to 'debian-installer'.
No longer marked as found in versions debian-10.0.0-amd64-netinst.iso.
Ignoring request to alter fixed versions of bug #934383 to the same values 
previously set

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

Bug#934383: debian-install: Package fails attempting to access USB WiFi

[andreimpopescu]

Control: reassign -1 debian-installer

On Sb, 10 aug 19, 09:50:50, William Melgaard wrote:
> Package: debian-install
> Version: debian-10.0.0-amd64-netinst.iso
> Severity: serious
> Tags: ipv6
> Justification: 2
> 
> Dear Maintainer,
> 
> 
> 
>* What led up to the situation?
> Attemting to install Buster with an USB WiFi dongle
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
> When the installer reached the "Detect Network Hardware", it entered a loop 
> of alternating white & black screen
>* What outcome did you expect instead?
> Identify the presence of a Panda PAU06 Wifi dongle, RT5372, requiring Debian 
> package rt2800us
> 
> 
> 
> -- System Information:
> Debian Release: 10.0
>   APT prefers stable
>   APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
> (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled

-- 
Looking after bugs reported against inexistent or removed packages


signature.asc
Description: PGP signature

Bug#934383: debian-install: Package fails attempting to access USB WiFi

[William Melgaard]

Package: debian-install
Version: debian-10.0.0-amd64-netinst.iso
Severity: serious
Tags: ipv6
Justification: 2

Dear Maintainer,



   * What led up to the situation?
Attemting to install Buster with an USB WiFi dongle
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
When the installer reached the "Detect Network Hardware", it entered a loop of 
alternating white & black screen
   * What outcome did you expect instead?
Identify the presence of a Panda PAU06 Wifi dongle, RT5372, requiring Debian 
package rt2800us



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

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

Bug#933020: libvirt: diff for NMU version 5.0.0-4.1

[Jonathan Wiltshire]

Control: tags 933020 + patch
Control: tags 933020 + pending


Dear maintainer,

I've prepared an NMU for libvirt (versioned as 5.0.0-4.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

diff -Nru libvirt-5.0.0/debian/changelog libvirt-5.0.0/debian/changelog
--- libvirt-5.0.0/debian/changelog	2019-06-17 18:05:40.0 +0100
+++ libvirt-5.0.0/debian/changelog	2019-08-10 13:31:18.0 +0100
@@ -1,3 +1,11 @@
+libvirt (5.0.0-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build-depend on libglusterfs-dev for required libgfapi headers
+(Closes: #933020)
+
+ -- Jonathan Wiltshire   Sat, 10 Aug 2019 13:31:18 +0100
+
 libvirt (5.0.0-4) unstable; urgency=medium
 
   * [0fdc2af] Fix multiple CVEs related to privilege escalations on R/O
diff -Nru libvirt-5.0.0/debian/control libvirt-5.0.0/debian/control
--- libvirt-5.0.0/debian/control	2019-06-17 18:05:40.0 +0100
+++ libvirt-5.0.0/debian/control	2019-08-10 13:31:18.0 +0100
@@ -54,6 +54,7 @@
  librados-dev [linux-any],
 # for --with-storage-gluster
  glusterfs-common (>= 3.4.0),
+ libglusterfs-dev,
 # for --with-wireshark-dissector
  libwireshark-dev (>= 1.11.3),
  libwiretap-dev,

Processed: libvirt: diff for NMU version 5.0.0-4.1

[Debian Bug Tracking System]

Processing control commands:

> tags 933020 + patch
Bug #933020 [src:libvirt] libvirt ftbfs in unstable (configure fails)
Added tag(s) patch.
> tags 933020 + pending
Bug #933020 [src:libvirt] libvirt ftbfs in unstable (configure fails)
Added tag(s) pending.

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

Processed: Bug#933774 marked as pending in python-pulp

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #933774 [python3-pulp] python3-pulp: Empty package
Added tag(s) pending.

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

Bug#933774: marked as pending in python-pulp

[Ondřej Nový]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/python/python-pulp/commit/4bb5548650e050af50ea88b797184a4be87d87bc


Use pybuild for building package (Closes: #933774).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/933774

Bug#934382: cvxopt: FTBFS on non-amd64 architectures

[Esa Peuha]

Source: cvxopt
Version: 1.2.3+dfsg-1
Severity: serious

As shown by buildd logs [1], compiling src/C/umfpack.c fails on all
architectures except amd64 because umfpack.h is not found. This is
because line 61 of setup.py tests whether any files matching
/usr/lib/x86_64-linux-gnu/libsuitesparse* exist, which is false on
non-amd64 Debian buildds even when libsuitesparse-dev is installed.

[1] https://buildd.debian.org/status/package.php?p=cvxopt

Processed: python3-pulp: Empty package

[Debian Bug Tracking System]

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

> severity 933774 grave
Bug #933774 [python3-pulp] python3-pulp: Empty package
Severity set to 'grave' from 'normal'
>
End of message, stopping processing here.

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

Bug#934376: marked as done (gstreamer1.0-pocketsphinx: fails to load due to incompatible version)

[Debian Bug Tracking System]

Your message dated Sat, 10 Aug 2019 12:49:29 +
with message-id 
and subject line Bug#934376: fixed in pocketsphinx 0.8+5prealpha+1-4
has caused the Debian Bug report #934376,
regarding gstreamer1.0-pocketsphinx: fails to load due to incompatible version
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.)


-- 
934376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934376
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gstreamer1.0-pocketsphinx
Version: 0.8+5prealpha+1-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After installing the package, the `pocketsphinx` plugin fails to load.

It appears that the plugin is incompatible with the version of gstreamer
available in `testing`:

```
GST_DEBUG=4 gst-inspect-1.0 
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstpocketsphinx.so
[...]
0:00:00.063752136 31079 0x5645debd2c00 WARN  GST_PLUGIN_LOADING 
gstplugin.c:486:gst_plugin_register_func: plugin 
"/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstpocketsphinx.so" has 
incompatible version (plugin: 1.16, gst: 1,14), not loading
Could not load plugin file: File 
"/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstpocketsphinx.so" appears to be a 
GStreamer plugin, but it failed to initialize
```

To summarize: gstreamer is currently 1.14 in testing but 1.16 in unstable;
the pocketsphinx module is built using gstreamer 1.16; gstreamer 1.14
refuses to load a plugin built with gstreamer 1.16.

After installing the version of gstreamer available in unstable, the
plugin loads properly.

I suppose this could be fixed by updating the dependencies to match the
package's actual build dependencies, for example
  libgstreamer1.0-0 (>=1.16.0)
but I assume there may be better ways to do this.

Best regards,
Stéphane

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

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

Versions of packages gstreamer1.0-pocketsphinx depends on:
ii  libc6   2.28-10
ii  libglib2.0-02.60.6-1
ii  libgstreamer-plugins-base1.0-0  1.14.4-2
ii  libgstreamer1.0-0   1.14.4-1
ii  libpocketsphinx30.8+5prealpha+1-3
ii  libsphinxbase3  0.8+5prealpha+1-4

gstreamer1.0-pocketsphinx recommends no packages.

gstreamer1.0-pocketsphinx suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pocketsphinx
Source-Version: 0.8+5prealpha+1-4

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated pocketsphinx 
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: Sat, 10 Aug 2019 14:33:50 +0200
Source: pocketsphinx
Binary: gstreamer1.0-pocketsphinx gstreamer1.0-pocketsphinx-dbgsym 
libpocketsphinx-dev libpocketsphinx3 libpocketsphinx3-dbgsym pocketsphinx 
pocketsphinx-dbgsym pocketsphinx-en-us python3-pocketsphinx 
python3-pocketsphinx-dbgsym
Architecture: source
Version: 0.8+5prealpha+1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team 
Changed-By: Samuel Thibault 
Description:
 gstreamer1.0-pocketsphinx - Speech recognition tool - GStreamer plugin
 libpocketsphinx-dev - Speech recognition tool - front-end library development 
files
 libpocketsphinx3 - Speech recognition tool - front-end library
 pocketsphinx - Speech recognition tool
 pocketsphinx-en-us - Speech recognition tool - US English language model
 python3-pocketsphinx - Speech recognition tool - Python3 bindings
Closes: 934376
Changes:
 pocketsphinx (0.8+5prealpha+1-4) unstable; urgency=medium
 .
   * control: Set Vcs-* to salsa.debian.org.
   * control: Bump Standards-Version 

Processed: tagging 934376

[Debian Bug Tracking System]

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

> tags 934376 + pending
Bug #934376 [gstreamer1.0-pocketsphinx] gstreamer1.0-pocketsphinx: fails to 
load due to incompatible version
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#934026: python-django: CVE-2019-14232 CVE-2019-14233 CVE-2019-14234 CVE-2019-14235

[Chris Lamb]

Hi Sébastien,

> > +python-django (1:1.10.7-2+deb9u5) stretch-security; urgency=high
> > [...]
> > +python-django (1:1.11.23-1~deb10u1) buster-security; urgency=high
> 
> Thanks, these both look good; please upload to security-master.

Both uploaded to security-master.


Regards,

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

Bug#934376: gstreamer1.0-pocketsphinx: fails to load due to incompatible version

[Stéphane Alnet]

Package: gstreamer1.0-pocketsphinx
Version: 0.8+5prealpha+1-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After installing the package, the `pocketsphinx` plugin fails to load.

It appears that the plugin is incompatible with the version of gstreamer
available in `testing`:

```
GST_DEBUG=4 gst-inspect-1.0 
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstpocketsphinx.so
[...]
0:00:00.063752136 31079 0x5645debd2c00 WARN  GST_PLUGIN_LOADING 
gstplugin.c:486:gst_plugin_register_func: plugin 
"/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstpocketsphinx.so" has 
incompatible version (plugin: 1.16, gst: 1,14), not loading
Could not load plugin file: File 
"/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstpocketsphinx.so" appears to be a 
GStreamer plugin, but it failed to initialize
```

To summarize: gstreamer is currently 1.14 in testing but 1.16 in unstable;
the pocketsphinx module is built using gstreamer 1.16; gstreamer 1.14
refuses to load a plugin built with gstreamer 1.16.

After installing the version of gstreamer available in unstable, the
plugin loads properly.

I suppose this could be fixed by updating the dependencies to match the
package's actual build dependencies, for example
  libgstreamer1.0-0 (>=1.16.0)
but I assume there may be better ways to do this.

Best regards,
Stéphane

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

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

Versions of packages gstreamer1.0-pocketsphinx depends on:
ii  libc6   2.28-10
ii  libglib2.0-02.60.6-1
ii  libgstreamer-plugins-base1.0-0  1.14.4-2
ii  libgstreamer1.0-0   1.14.4-1
ii  libpocketsphinx30.8+5prealpha+1-3
ii  libsphinxbase3  0.8+5prealpha+1-4

gstreamer1.0-pocketsphinx recommends no packages.

gstreamer1.0-pocketsphinx suggests no packages.

-- no debconf information

Bug#934375: golang-github-anacrolix-ffprobe: FTBFS in sid (failing tests)

[Santiago Vila]

Package: src:golang-github-anacrolix-ffprobe
Version: 1.0.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=all=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" 
-asmflags=all=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -v -p 1 
github.com/anacrolix/ffprobe
errors
internal/cpu
internal/bytealg
internal/race
runtime/internal/atomic
runtime/internal/sys
runtime/internal/math
runtime
sync/atomic
sync
io
unicode
unicode/utf8
bytes
bufio
encoding
math/bits
math
strconv
reflect
encoding/binary
encoding/base64
sort
internal/fmtsort
syscall
time
internal/poll
internal/syscall/unix
internal/testlog
os
fmt
strings
unicode/utf16
encoding/json
log
context
path/filepath
os/exec
github.com/anacrolix/ffprobe
   dh_auto_test -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/anacrolix/ffprobe
# github.com/anacrolix/ffprobe
package github.com/anacrolix/ffprobe (test)
imports github.com/anacrolix/missinggo/leaktest
imports github.com/bradfitz/iter: cannot find package 
"github.com/bradfitz/iter" in any of:
/usr/lib/go-1.12/src/github.com/bradfitz/iter (from $GOROOT)
/<>/obj-x86_64-linux-gnu/src/github.com/bradfitz/iter 
(from $GOPATH)
FAILgithub.com/anacrolix/ffprobe [setup failed]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/anacrolix/ffprobe returned exit code 1
make: *** [debian/rules:4: build-indep] Error 255
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-anacrolix-ffprobe.html

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

Thanks.

Bug#934374: de4dot: FTBFS in sid (failing tests)

[Santiago Vila]

Package: src:de4dot
Version: 3.1.41592.3405-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with cli
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
xbuild /property:Configuration=Release /property:TargetFrameworkVersion="v4.5" 
/target:de4dot

 xbuild tool is deprecated and will be removed in future updates, use 
 msbuild instead 

XBuild Engine Version 14.0
Mono, Version 5.18.0.240
Copyright (C) 2005-2013 Various Mono authors


[... snipped ...]

GenericArgsSubstitutor.cs(65,17): error CS0246: The type or namespace 
name `IField' could not be found. Are you missing an assembly reference?
GenericArgsSubstitutor.cs(75,17): error CS0246: The type or namespace 
name `FieldSig' could not be found. Are you missing an assembly reference?
GenericArgsSubstitutor.cs(81,17): error CS0246: The type or namespace 
name `FieldSig' could not be found. Are you missing an assembly reference?
GenericArgsSubstitutor.cs(87,17): error CS0246: The type or namespace 
name `IMethod' could not be found. Are you missing an assembly reference?
GenericArgsSubstitutor.cs(102,17): error CS0246: The type or namespace 
name `MethodSpec' could not be found. Are you missing an assembly reference?
GenericArgsSubstitutor.cs(111,17): error CS0246: The type or namespace 
name `GenericInstMethodSig' could not be found. Are you missing an assembly 
reference?
GenericArgsSubstitutor.cs(117,17): error CS0246: The type or namespace 
name `GenericInstMethodSig' could not be found. Are you missing an assembly 
reference?
GenericArgsSubstitutor.cs(123,17): error CS0246: The type or namespace 
name `IMethodDefOrRef' could not be found. Are you missing an assembly 
reference?
GenericArgsSubstitutor.cs(129,17): error CS0246: The type or namespace 
name `IMethodDefOrRef' could not be found. Are you missing an assembly 
reference?
GenericArgsSubstitutor.cs(133,17): error CS0246: The type or namespace 
name `IMethodDefOrRef' could not be found. Are you missing an assembly 
reference?
GenericArgsSubstitutor.cs(138,17): error CS0246: The type or namespace 
name `IMethodDefOrRef' could not be found. Are you missing an assembly 
reference?
GenericArgsSubstitutor.cs(155,32): error CS0246: The type or namespace 
name `TypeSig' could not be found. Are you missing an assembly reference?
GenericArgsSubstitutor.cs(161,32): error CS0246: The type or namespace 
name `TypeSig' could not be found. Are you missing an assembly reference?
GenericArgsSubstitutor.cs(161,60): error CS0246: The type or namespace 
name `TypeSig' could not be found. Are you missing an assembly reference?
GenericArgsSubstitutor.cs(167,3): error CS0246: The type or namespace 
name `TypeSig' could not be found. Are you missing an assembly reference?
GenericArgsSubstitutor.cs(172,3): error CS0246: The type or namespace 
name `TypeSig' could not be found. Are you missing an assembly reference?
GenericArgsSubstitutor.cs(286,3): error CS0246: The type or namespace 
name `MethodSig' could not be found. Are you missing an assembly reference?
GenericArgsSubstitutor.cs(302,3): error CS0246: The type or namespace 
name `GenericInstMethodSig' could not be found. Are you missing an assembly 
reference?
GenericArgsSubstitutor.cs(309,3): error CS0246: The type or namespace 
name `FieldSig' could not be found. Are you missing an assembly reference?
Instr.cs(26,3): error CS0246: The type or namespace name `Instruction' 
could not be found. Are you missing an assembly reference?
Instr.cs(28,10): error CS0246: The type or namespace name `OpCode' 
could not be found. Are you missing `System.Reflection.Emit' using directive?
Instr.cs(37,16): error CS0246: The type or namespace name `Instruction' 
could not be found. Are you missing an assembly reference?
Instr.cs(41,10): error CS0246: The type or namespace name `Instruction' 
could not be found. Are you missing an assembly reference?
Instr.cs(47,17): error CS0246: The type or namespace name `Local' could 
not be found. Are you missing an assembly reference?
Instr.cs(51,36): error CS0246: The type or namespace name `OpCode' 
could not be found. Are you missing `System.Reflection.Emit' using directive?
Instr.cs(154,42): error CS0246: The type or namespace name `OpCode' 
could not be found. Are you missing `System.Reflection.Emit' using directive?
InstructionListParser.cs(26,9): error CS0246: The type or namespace 
name `Instruction' could not be found. Are you missing an assembly reference?
InstructionListParser.cs(27,9): error CS0246: The type or namespace 
name 

Bug#915336: marked as done (python-pyramid-chameleon downloads from the internet during the build)

[Debian Bug Tracking System]

Your message dated Sat, 10 Aug 2019 10:19:30 +
with message-id 
and subject line Bug#915336: fixed in python-pyramid-chameleon 0.3-3
has caused the Debian Bug report #915336,
regarding python-pyramid-chameleon downloads from the internet during the build
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.)


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

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

...
sphinx-build -b html -d _build/doctrees  -W . _build/html
Running Sphinx v1.7.9
loading pickled environment... not yet created
loading intersphinx inventory from 
http://docs.pylonsproject.org/projects/pyramid/en/latest/objects.inv...

Warning, treated as error:
failed to reach any of the inventories with the following issues:
make[2]: *** [Makefile:30: html] Error 2
--- End Message ---
--- Begin Message ---
Source: python-pyramid-chameleon
Source-Version: 0.3-3

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-pyramid-chameleon 
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: Sat, 10 Aug 2019 11:59:34 +0200
Source: python-pyramid-chameleon
Architecture: source
Version: 0.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Closes: 915336
Changes:
 python-pyramid-chameleon (0.3-3) unstable; urgency=medium
 .
   * Team upload.
   * Disable intersphinx mapping (Closes: #915336)
Checksums-Sha1:
 d4dfd03fd5a72e9b46de39c71e27467d5a8be233 2442 
python-pyramid-chameleon_0.3-3.dsc
 3e9e78434c10bb55aa5e1099b1542d8aab8a1f8b 4304 
python-pyramid-chameleon_0.3-3.debian.tar.xz
 26b13ec3a42cd9a8ae137c8ac5fe2e14ac77f1be 8153 
python-pyramid-chameleon_0.3-3_amd64.buildinfo
Checksums-Sha256:
 03a46e2c36c46142ae840b3d9edfdf6c14f69069ad126f46f67394c8634ca54a 2442 
python-pyramid-chameleon_0.3-3.dsc
 2ecc9440946cb2ead96dbfacc20cf34478a5b9cdcbfdb14bbaf89cb755bd9931 4304 
python-pyramid-chameleon_0.3-3.debian.tar.xz
 854b8e1e26ea3301a6825759a6b16df16394d034ff474a47270b2d74d9896f5e 8153 
python-pyramid-chameleon_0.3-3_amd64.buildinfo
Files:
 d7ca38f13aee00649ad873de4bdee5f7 2442 python optional 
python-pyramid-chameleon_0.3-3.dsc
 fc56ed8d040cb0d88db43cb90ecee9eb 4304 python optional 
python-pyramid-chameleon_0.3-3.debian.tar.xz
 62a8b2dc560c06fb12d52926979196cb 8153 python optional 
python-pyramid-chameleon_0.3-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAl1OlisACgkQNXMSVZ0e
BktmQQ//UeC1pm+DUT1gG2gazjdzNV5cj06TeGGcJhnEFc/3lyzI96VCYfezpsv8
or/E6qxKBM/wWsYB1gbdp3goLiNj+rzw4BtcDE2HFsl5HC1plCoCU3RL/Aubexur
LK/rp59vv0u9HBAyIfH4H3MH8jS6npSt0EKi/n3yW69Zot9dkppTcEFonOk3Jb8m
zZPqK1h1fZCZ0KMua3GN+AX2HoNukZ+czkskGd7XRYdDH/LiJiIf1C76jebGzQm+
u6+agLnRYTg5w5MEXQZ9d3EMYFGej/syzKh0AqGcfwX6sYdKdTimI1MBQo4GtGBe
U8/zZZxFgkX1Nkh8HcTwAw349m82nEwzbH276WdCgihinCdX/gXYGEMC5ZmCq2tT
n0+NVG2EhYAB9CUH7EKMDU5CxdyaPEjn0ow7T4Q8t7YFc6b0tMbgwlevaHkELuVS
Md+ZSe7jA8HyNaaoxeqmBJHAxv8Fn+yAhOXGvAvC3Qz5NQ3gAzrxQq1SC3CWPLlK
y55oZQCZl2sAaOk4XlhoL7EW0OSP/ZT6gOWhCb4lex4U685hvGsnOlMVot+t+FKb
4PObhPiuzsxABBdnX43wyPYuhd8Zz6MTR/W1y5gfvsu2YT6Pyaz57OjkODTD44Dd
5ZCTFciAm4fYefvYSKl/VYB7xNAqDnIolA/gyHRDVQIX9KkuO/M=
=ESHS
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#923240: policykit-1: Please support alternative logind implementations

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - moreinfo
Bug #923240 [policykit-1] policykit-1: Please support alternative logind 
implementations
Removed tag(s) moreinfo.

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

Bug#923240: policykit-1: Please support alternative logind implementations

[Mark Hindley]

Control: tags -1 - moreinfo

Simon,

Many thanks for this.

On Fri, Aug 09, 2019 at 02:35:13PM +0100, Simon McVittie wrote:
> Control: tags -1 + moreinfo
> 
> On Mon, 25 Feb 2019 at 10:58:49 +, Mark Hindley wrote:
> > For desktops to be installable on such systems, policykit-1 needs to depend 
> > on
> > the newly approved virtual packages default-logind and logind. In the latest
> > upload of src:systemd, libpam-systemd provides default-logind.
> 
> Sorry for the delay in getting back to you on this. Non-critical changes
> to important components like policykit-1 did not seem like a good idea
> during the buster release freeze.

Yes, I understand that. It also seems to me that now, early in the bullseye
cycle, is a good time for such changes.

> Does polkit work correctly on systems that use elogind, without any
> further source or binary changes? It is not enough that a logind-like
> service is merely installed and monitoring sessions: to keep polkit's
> core functionality working, it has to be able to query logind's state
> via libsystemd.so.0 APIs.

Yes, it works in my testing. I have had a number of other reports of success too
with a variety of desktops (xfce, mate, budgie, cinnamon and even gnome).

Since #923244 was resolved in version 241.1-1+debian1, libelogind0 is ABI
compatible with libsystemd0 and exposes the same symbols for runtime linking,
although providing a subset of functionality. This is explained fully in the
libelogind0 package description: sd-login(3), sd-bus(3) and sd-id128(3) APIs are
implemented in full with most other functions returning -ENOSYS. libelogind0
also provides a libsystemd.so symlink so that applications compiled against
systemd work with libelogind0 at runtime.
 
> For example, when polkitd calls sd_pid_get_session(), if the system is
> using elogind, the API call needs to return whether pid is part of an
> elogind session.
> 
> Please could you describe how this is meant to work on systems that use
> elogind? Which packages are meant to be installed to make this work?
> 
> For comparison, here is how it works on systemd systems:
> 
> - libpam_systemd is invoked on login and logout
> - libpam_systemd communicates with systemd-logind to update its knowledge
>   of login sessions
> - polkitd is linked to libsystemd.so.0, which is provided by libsystemd0
> - libsystemd0 communicates with systemd-logind via D-Bus, or by reading
>   files in /run/systemd that are considered private to the combination
>   of systemd-logind and libsystemd0 (mainly /run/systemd/seats and
>   /run/systemd/sessions, I think)
> 
> Which parts of that architecture get replaced when using elogind?

In exactly the same way. libpam-elogind is invoked at login/logout and updates
elogind's record of sessions. polkitd calls functions in libelogind.so via its
libsystemd.so symlink to retrieve information on users, sessions and their
related processes.

> When a bug is reported in policykit-1 on a system that is using elogind,
> does the reportbug-generated message template indicate that? Is there
> someone among the elogind maintainers who can help with such bugs if
> they appear to be integration issues between policykit-1 and elogind?
> 
> (If the reportbug-generated message template with your proposed patch
> doesn't currently indicate systemd-logind vs. elogind, it should be
> possible to fix that by putting appropriate runes in
> debian/policykit-1.bug-control.)

I will be very happy to work to resolve issues related to elogind and its
integration with other packages. You are correct that a reportbug template
including that information would be useful.

> > There is a separate issue about backend support for elogind. I will
> > open a separate bug for that.
> 
> Does that separate bug exist, or has the question of backend support
> become irrelevant due to changes in the design of how elogind fits into
> Debian since you opened this bug?

Yes that was #923244 which has now been solved by runtime ABI compatibility
rather than the original suggestion of alternative backend packages.

> On Fri, 09 Aug 2019 at 14:15:17 +0200, Svante Signell wrote:
> > Please explain your decision on why desktops for other
> > init systems are excluded (even in sid).
> 
> Please don't assume that the absence of action is a deliberate decision.
> All of policykit-1's maintainers (both upstream and in Debian) mostly
> work on other things and don't have a huge amount of time available for
> policykit-1. This makes us reluctant to risk creating the possibility
> of non-functional combinations of packages that will take more of our
> time to debug.

I understand. To help prevent that libelogind0 conflicts with systemd itself so
that the non-functional situation of systemd with libelogind0 is not possible.

Thanks and best wishes.

Mark

Bug#933580: marked as done (etc/network/if-up.d/hostname causes loss of dynamic v4 IP address)

[Debian Bug Tracking System]

Your message dated Sat, 10 Aug 2019 10:08:09 +
with message-id 
and subject line Bug#933580: fixed in debian-edu-config 2.10.66
has caused the Debian Bug report #933580,
regarding etc/network/if-up.d/hostname causes loss of dynamic v4 IP address
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.)


-- 
933580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-edu-config
Version: 2.10.65
Severity: important

On workstations and separate LTSP servers with a dynamically allocated 
v4 IP address the network setup is broken. The IP address goes away 
after some time (20 to 30 minutes) and never comes back.

This is due to etc/network/if-up.d/hostname which intends to immediately 
update the hostname on reboot in case it has been changed. This 
mechanism doesn't work any more and needs to be implemented differently.

Wolfgang


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: debian-edu-config
Source-Version: 2.10.66

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

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated debian-edu-config 
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: Sat, 10 Aug 2019 11:41:47 +0200
Source: debian-edu-config
Architecture: source
Version: 2.10.66
Distribution: unstable
Urgency: medium
Maintainer: Debian Edu Developers 
Changed-By: Holger Levsen 
Closes: 926933 928756 929964 930122 931366 931413 931680 932828 933183 933580
Changes:
 debian-edu-config (2.10.66) unstable; urgency=medium
 .
   [ Wolfgang Schweer ]
   * Adjust ltsp-build-client/Debian-custom/001-ltsp-setting. (Closes: #928756)
 - Use PXE option 'ipappend 2' for LTSP client boot. This option makes sure
   that all DHCP server information is getting through to LTSP clients.
   (LTSP used this option before, but switched to 'ipappend 3' during the
   Buster development cycle to ease setups with ProxyDHCP.)
   * Adjust share/debian-edu-config/sudo-ldap.conf. (Closes: #929964)
 - Fix sudo-ldap configuration. (The LDAP URI is needed on LDAP clients.)
   * Set environment variable to deal with Firefox profile. (Closes: #930122)
 This is a workaround for bug #930125, preventing firefox-esr startup issues
 if the mozilla profile is on an NFS share).
 - Ship share/debian-edu-config/edu-firefox-nfs with NSS_SDB_USE_CACHE="yes"
   as content. Thanks to Mike Gabriel for spotting the issue and providing
   this information.
 - Add instructions to cf3/cf.workarounds to link the 'edu-firefox-nfs' file
   to appropriate files below '/etc/X11/Xsession.d' and '/etc/profile.d'.
   * Adjust cf3/cf.homes: Set correct LTSP chroot path. (Closes: #931680)
 - While the reported arch is i686, LTSP uses i386. Set arch accordingly.
   * Adjust share/debian-edu-config/tools/kerberos-kdc-init. (Closes: #931366)
 - Remove outdated (and now wrong) logging section.
   * Add LDAP server certificate to the initial LTSP NBD image. (Closes: 
#932828)
 - etc/ltsp/ltsp-build-client.conf: Don't create the image by default.
 - cf3/edu.cf: Define new class 'ltspimages'.
 - cf3/cf.finalize: Add code to include the LDAP server certificate for all
   possible use cases, to generate the image and to adjust various rights.
   * Provide Debian Edu RootCA certificate for download. (Closes: #933183)
 - Adjust share/debian-edu-config/tools/create-debian-edu-certs to copy the
   rootCA file to the web server directory at certificate generation time.
 - Adjust cf3/cf.finalize to care for the rootCA file as well.
 - Adjust cf3/cf.workarounds to copy the rootCA file to the web server
   directory upon main server upgrade.
   * Fix loss of dynamically allocated v4 IP address. (Closes: #933580)
 - Drop etc/network/if-up.d/hostname. This script doesn't work anymore due
   to changed behaviour of the ifupdown/dhclient/systemd 

Bug#933751: mini-buildd (build-)depends on cruft package.

[Stephan Sürken]

Hi Peter,

On Fri, 2019-08-02 at 22:11 +0100, Peter Michael Green wrote:
> Package: mini-buildd
> Version: 1.0.41
> Severity: serious
> 
> python-mini-buildd depends on and the mini-buildd source package 
> build-depends on the python-django-registration binary package which
> is 
> no longer built by the python-django-registration source package.

yes, or 'python2 django', for that matter ;). I guess it will be
removed from testing soon:

http://mini-buildd.installiert.net/articles/10x-maintenance-moved-to-hellfield-archive.html

> I notice this already seems to be fixed in experimental, are there
> any 
> blockers for uploading the experimental version to unstable?

The branch uploaded to experimental is development, and should not be
used for production.

I am pressing for a release asap (~months), then everything will be
fine again ;).

Hth!

S

Bug#934351: virtualbox-dkms: Fails to build modules

[Hilmar Preuße]

Am 10.08.2019 um 10:42 teilte Gianfranco Costamagna mit:
> On Sat, 10 Aug 2019 09:06:32 +0200 =?UTF-8?Q?Hilmar_Preu=c3=9fe?= 
>  wrote:

Hi Gianfranco,

>> Dear Maintainer,
>>
>> I'm filing that bug as grave as currently the package is in state iF.
>>
>>* What led up to the situation?
>>
>> I tried to install the package, compilation of vboxvideo module fails.
>> See latest E-Mail of #934010 and #929399.
>>
> 
> I can't care less about an RC linux version that is not stable, not
> even in Debian.
> 

I'm note sure why you speak about an RC kernel. This is the 5.2 kernel,
which is in unstable since yesterday.

> Go install virtualbox-guest-source, fix and build it with
> module-assistant, install the deb and make it work.
> 

Thanks for the pointer! I could fix the vbox_ttm.c using the usual method:

- #include 
+ #include 

Not sure, why upstream does not apply the patch.

> After you did that, send the patch upstream and or in Debian, and
> I'll have a look.
> 

Regards,
  Hilmar
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

Bug#934370: r-cran-fs: autopkgtest regression

[Graham Inggs]

Source: r-cran-fs
Version: 1.3.1+dfsg-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Since the upload of 1.3.1+dfsg-1, r-cran-fs has been failing its own
autopkgtests [1] with the following error:

+   test_check("reprex")
+ }
-- 1. Failure: make_filebase() works from absolute infile, outfile (@test-filepa
fs::path_dir(x) not equal to path_temp().
Classes differ: character is not fs_path/character

-- 2. Failure: make_filebase() works from absolute infile, outfile (@test-filepa
fs::path_dir(x) not equal to path_temp().
Classes differ: character is not fs_path/character

== testthat results  ===
OK: 25 SKIPPED: 55 FAILED: 2
1. Failure: make_filebase() works from absolute infile, outfile
(@test-filepaths.R#25)
2. Failure: make_filebase() works from absolute infile, outfile
(@test-filepaths.R#29)

Error: testthat unit tests failed
Execution halted

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-fs/unstable/amd64/

Bug#903529: marked as done (python3-ws4py fails to install with Python 3.7 as supported version)

[Debian Bug Tracking System]

Your message dated Sat, 10 Aug 2019 09:08:05 +
with message-id 
and subject line Bug#903529: fixed in python-ws4py 0.4.2+dfsg1-3
has caused the Debian Bug report #903529,
regarding python3-ws4py fails to install with Python 3.7 as supported version
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.)


-- 
903529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-ws4py
Version: 0.4.2+dfsg1-2
Severity: grave
Control: block 902788 by -1

Setting up python3-ws4py (0.4.2+dfsg1-2) ...
  File "/usr/lib/python3/dist-packages/ws4py/async_websocket.py", line 87
asyncio.async(closeit())
^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/ws4py/server/tulipserver.py", line 43
f = asyncio.async(self.handle_initial_handshake())
^
SyntaxError: invalid syntax

dpkg: error processing package python3-ws4py (--configure):
 installed python3-ws4py package post-installation script subprocess returned 
error exit status 1
--- End Message ---
--- Begin Message ---
Source: python-ws4py
Source-Version: 0.4.2+dfsg1-3

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

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

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

Debian distribution maintenance software
pp.
William Grzybowski  (supplier of updated python-ws4py 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, 18 Jul 2019 16:40:13 -0300
Source: python-ws4py
Architecture: source
Version: 0.4.2+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: William Grzybowski 
Closes: 903529
Changes:
 python-ws4py (0.4.2+dfsg1-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
 .
   [ William Grzybowski ]
   * d/patches: Add to fix compatibility with Python 3.7. (Closes: #903529)
   * d/compat: no longer required for debhelper 12.
   * d/control: Update debhelper to version 12.
   * d/control: Update Standards-Version to 4.4.0.
   * d/rules: install docs and examples correctly for debhelper 12.
Checksums-Sha1:
 95bc2fef99fca3c23cf63af998e6c918915a87f2 2510 python-ws4py_0.4.2+dfsg1-3.dsc
 5dfb34c0e9583305dfc9a8034d62a0ecd9527960 6140 
python-ws4py_0.4.2+dfsg1-3.debian.tar.xz
 b1d2e1f5a89a4d5064d0d1615d10898ba780a749 9893 
python-ws4py_0.4.2+dfsg1-3_amd64.buildinfo
Checksums-Sha256:
 ae91ed38a046d3fb048ecc9d3cf0cc77c189db33e5e770ae7ca983b3ef506043 2510 
python-ws4py_0.4.2+dfsg1-3.dsc
 36be4af53ed7391810e188fe2a20ab07164f35f62f019a7d8d6bed3977a654d2 6140 
python-ws4py_0.4.2+dfsg1-3.debian.tar.xz
 911e8e9fd20020d6846cf691e106f547efa71dae9ba6fd421d0b8011e611a53c 9893 
python-ws4py_0.4.2+dfsg1-3_amd64.buildinfo
Files:
 43604716f1a8053098cc1874f18298be 2510 python optional 
python-ws4py_0.4.2+dfsg1-3.dsc
 aa8c6ff2f19a2c470c129a1fc195ff18 6140 python optional 
python-ws4py_0.4.2+dfsg1-3.debian.tar.xz
 f114451f7a3f57a4ad6b439f37ac5954 9893 python optional 
python-ws4py_0.4.2+dfsg1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAl1OhYEACgkQNXMSVZ0e
BkvIFw//b+opy8Lp918VBZ0K8JTBRu6b3U98ikgFRyxlS9cYMOv5eApakbFPDdr8
qizNCiGEH4WiAMaGrcykwhcjtM72k8BhXF9BGQ92bqbPMSxAtTS11igp5lF8LYHr
1dtswNjaqZsTH/g+Igzv0u4R+2ixNAdhzGPa+CGWMzEPgJbYfcMI1i7fRGBSmxCZ
GAo3eeghPNIwHJeWzqPAA9UewlSjiLORygzALzsM2kLF6NyNP3iracSaaawoIjkp
2nxcpsph5yGgDMrEtHsu1w/7ihBs7Zl77+TnC/hAP6AxGr2RElNXOqcS2c+r63vh
b3EGh4xD/xHdo5lYK9D7gg4IGfe9RItAfzj3XJfgoeS7S83tO1dZFp3qOUeIVSaX
387V6bA8v0tT4y0BfkLaMmaaytrUMMCdLHTmQGkw39cA1pRhnstvWP64cKf/Z2Of
s7A1Gxmwi8C2Lavog+AI14tu1MzPRQiUb0BLYUH3LIkPpgIJ8HMSv5aDoJbfJi5K
Ozeu3Yn0yYZNMWnmh2s6iusOYCiQFPYhGdjZwWtmaHuEQgBlLf89ylAHBEk3vdV6
BVnAm+peGWerW0pPQn3/qKbCRxIQQKoUDXyD9xZiwVFtH2YI3O0teaaPl3R5WWTU
DPtCLbkke6S8rNN9BXUvEYJN2W/EuDlcPErKqSA2NLfawLO9IQs=
=B67L

Bug#934351: marked as done (virtualbox-dkms: Fails to build modules)

[Debian Bug Tracking System]

Your message dated Sat, 10 Aug 2019 10:42:42 +0200
with message-id <86354b01-b34d-9fee-5b11-28b155bc0...@debian.org>
and subject line Re: virtualbox-dkms: Fails to build modules
has caused the Debian Bug report #934351,
regarding virtualbox-dkms: Fails to build modules
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.)


-- 
934351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virtualbox-guest-dkms
Version: 6.0.10-dfsg-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I'm filing that bug as grave as currently the package is in state iF.

   * What led up to the situation?

I tried to install the package, compilation of vboxvideo module fails.
See latest E-Mail of #934010 and #929399.

Attached is my make.log.

   * What outcome did you expect instead?

Modules should compile fine.

Hilmar

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/1 CPU core)
Kernel taint flags: TAINT_WARN, 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

Versions of packages virtualbox-guest-dkms depends on:
ii  dkms  2.7.1-2

virtualbox-guest-dkms recommends no packages.

virtualbox-guest-dkms suggests no packages.

-- no debconf information

-- 
sigfault
#206401 http://counter.li.org
DKMS make.log for virtualbox-guest-6.0.10 for kernel 5.2.0-2-amd64 (x86_64)
Sat 10 Aug 2019 08:25:14 AM CEST
make: Entering directory '/usr/src/linux-headers-5.2.0-2-amd64'
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/VBoxGuest-linux.o
  CC [M]  /var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/VBoxGuest.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/VBoxGuestR0LibGenericRequest.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/VBoxGuestR0LibHGCMInternal.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/VBoxGuestR0LibInit.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/VBoxGuestR0LibPhysHeap.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/VBoxGuestR0LibVMMDev.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/alloc-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/initterm-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/memobj-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/mpnotification-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/powernotification-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/alloc-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/assert-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/initterm-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/memuserkernel-r0drv-linux.o
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/memuserkernel-r0drv-linux.o:
 warning: objtool: rtR0MemKernelCopyLnxWorker()+0x12: redundant CLD
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/mp-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/mpnotification-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/process-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/semevent-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/semeventmulti-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/semfastmutex-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/semmutex-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/spinlock-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/thread-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/thread2-r0drv-linux.o
  CC [M]  

Processed: Re: nvidia-kernel-dkms: nvidia kernel driver does not build with linux-5.2

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #934344 [nvidia-kernel-dkms] nvidia-kernel-dkms: nvidia kernel driver does 
not build with linux-5.2
Severity set to 'serious' from 'important'

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

Processed: Re: python-httptools: Please adjust for http-parser 2.9

[Debian Bug Tracking System]

Processing control commands:

> tags 933684 + patch
Bug #933684 [src:python-httptools] python-httptools: Please adjust for 
http-parser 2.9
Ignoring request to alter tags of bug #933684 to the same tags previously set
> tags 933684 + pending
Bug #933684 [src:python-httptools] python-httptools: Please adjust for 
http-parser 2.9
Added tag(s) pending.

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

Bug#933684: python-httptools: Please adjust for http-parser 2.9

[Christoph Biedl]

Control: tags 933684 + patch
Control: tags 933684 + pending

Dear maintainer,

I've prepared an NMU for python-httptools (versioned as 0.0.11-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

Christoph
diff -Nru python-httptools-0.0.11/debian/changelog 
python-httptools-0.0.11/debian/changelog
--- python-httptools-0.0.11/debian/changelog2018-10-20 20:49:40.0 
+0200
+++ python-httptools-0.0.11/debian/changelog2019-08-01 21:46:59.0 
+0200
@@ -1,3 +1,11 @@
+python-httptools (0.0.11-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Cherry-pick "Fix a unittest" to fix build error with
+http-parser 2.9 (Closes: #933684)
+
+ -- Christoph Biedl   Thu, 01 Aug 2019 
21:46:59 +0200
+
 python-httptools (0.0.11-1) unstable; urgency=low
 
   * Initial release (Closes: #911498).
diff -Nru python-httptools-0.0.11/debian/control 
python-httptools-0.0.11/debian/control
--- python-httptools-0.0.11/debian/control  2018-10-20 20:49:40.0 
+0200
+++ python-httptools-0.0.11/debian/control  2019-08-01 21:46:59.0 
+0200
@@ -8,7 +8,7 @@
  cython3,
  debhelper (>= 11),
  dh-python,
- libhttp-parser-dev,
+ libhttp-parser-dev (>= 2.9.2),
  python3-all-dev,
  python3-pytest,
  python3-setuptools,
diff -Nru 
python-httptools-0.0.11/debian/patches/cherry-pick.v0.0.11-6-gebcc0fd.fix-a-unittest.patch
 
python-httptools-0.0.11/debian/patches/cherry-pick.v0.0.11-6-gebcc0fd.fix-a-unittest.patch
--- 
python-httptools-0.0.11/debian/patches/cherry-pick.v0.0.11-6-gebcc0fd.fix-a-unittest.patch
  1970-01-01 01:00:00.0 +0100
+++ 
python-httptools-0.0.11/debian/patches/cherry-pick.v0.0.11-6-gebcc0fd.fix-a-unittest.patch
  2019-08-01 21:46:59.0 +0200
@@ -0,0 +1,21 @@
+Subject: Fix a unittest
+Origin: v0.0.11-6-gebcc0fd 

+Upstream-Author: Yury Selivanov 
+Date: Mon Feb 25 14:55:35 2019 -0500
+Bug-Debian: https://bugs.debian.org/933684
+Comment: Picked only the relevant hunk of that commit
+
+--- a/tests/test_parser.py
 b/tests/test_parser.py
+@@ -582,9 +582,8 @@
+ (None, None, None, b'/a/b/c', b'b=1&', None, None))
+ 
+ def test_parser_url_2(self):
+-self.assertEqual(
+-self.parse(b''),
+-(None, None, None, None, None, None, None))
++with self.assertRaises(httptools.HttpParserInvalidURLError):
++self.parse(b'')
+ 
+ def test_parser_url_3(self):
+ with self.assertRaises(httptools.HttpParserInvalidURLError):
diff -Nru python-httptools-0.0.11/debian/patches/series 
python-httptools-0.0.11/debian/patches/series
--- python-httptools-0.0.11/debian/patches/series   2018-10-20 
20:49:40.0 +0200
+++ python-httptools-0.0.11/debian/patches/series   2019-08-01 
21:46:59.0 +0200
@@ -2,3 +2,4 @@
 0002-Use-http_parser.h-from-distribution-installation.patch
 0003-Fix-unit-tests-on-invalid-data-after-connection-clos.patch
 0004-Do-not-install-package-data.patch
+cherry-pick.v0.0.11-6-gebcc0fd.fix-a-unittest.patch


signature.asc
Description: PGP signature

Bug#934363: r-cran-ggplot2: autopkgtest regression

[Graham Inggs]

Source: r-cran-ggplot2
Version: 3.2.0+dfsg-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Since the upload of 3.2.0+dfsg-1, r-cran-ggplot2 has been failings its
own autopkgtests [1] with the following error:

> library(testthat)
> library(ggplot2)
>
> test_check("ggplot2")
Error in loadNamespace(name) : there is no package called 'vdiffr'
Calls: test_check ... loadNamespace -> withRestarts -> withOneRestart
-> doWithOneRestart
Execution halted

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-ggplot2/unstable/amd64/

Bug#934360: r-cran-boolnet: autopkgtest regression

[Graham Inggs]

Source: r-cran-boolnet
Version: 2.1.5-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Since the upload of 2.1.5-1, r-cran-boolnet has been failings its own
autopkgtests [1] with the following error:

>   Stangle("BoolNet_package_vignette.Snw.Rnw")
Writing to file BoolNet_package_vignette.Snw.R
>   source("BoolNet_package_vignette.R.Rnw", echo=TRUE)
Error in file(filename, "r", encoding = encoding) :
  cannot open the connection
Calls: source -> file
In addition: Warning message:
In file(filename, "r", encoding = encoding) :
  cannot open file 'BoolNet_package_vignette.R.Rnw': No such file or directory
Execution halted

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-boolnet/unstable/amd64/

Bug#934026: python-django: CVE-2019-14232 CVE-2019-14233 CVE-2019-14234 CVE-2019-14235

[Sébastien Delafond]

On 08/08 11:02, Chris Lamb wrote:
> +python-django (1:1.10.7-2+deb9u5) stretch-security; urgency=high
> [...]
> +python-django (1:1.11.23-1~deb10u1) buster-security; urgency=high

Thanks, these both look good; please upload to security-master.

Cheers,

-- 
Seb

Bug#934351: virtualbox-dkms: Fails to build modules

[Hilmar Preuße]

Package: virtualbox-guest-dkms
Version: 6.0.10-dfsg-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I'm filing that bug as grave as currently the package is in state iF.

   * What led up to the situation?

I tried to install the package, compilation of vboxvideo module fails.
See latest E-Mail of #934010 and #929399.

Attached is my make.log.

   * What outcome did you expect instead?

Modules should compile fine.

Hilmar

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/1 CPU core)
Kernel taint flags: TAINT_WARN, 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

Versions of packages virtualbox-guest-dkms depends on:
ii  dkms  2.7.1-2

virtualbox-guest-dkms recommends no packages.

virtualbox-guest-dkms suggests no packages.

-- no debconf information

-- 
sigfault
#206401 http://counter.li.org
DKMS make.log for virtualbox-guest-6.0.10 for kernel 5.2.0-2-amd64 (x86_64)
Sat 10 Aug 2019 08:25:14 AM CEST
make: Entering directory '/usr/src/linux-headers-5.2.0-2-amd64'
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/VBoxGuest-linux.o
  CC [M]  /var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/VBoxGuest.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/VBoxGuestR0LibGenericRequest.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/VBoxGuestR0LibHGCMInternal.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/VBoxGuestR0LibInit.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/VBoxGuestR0LibPhysHeap.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/VBoxGuestR0LibVMMDev.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/alloc-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/initterm-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/memobj-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/mpnotification-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/powernotification-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/alloc-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/assert-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/initterm-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/memuserkernel-r0drv-linux.o
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/memuserkernel-r0drv-linux.o:
 warning: objtool: rtR0MemKernelCopyLnxWorker()+0x12: redundant CLD
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/mp-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/mpnotification-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/process-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/semevent-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/semeventmulti-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/semfastmutex-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/semmutex-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/spinlock-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/thread-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/thread2-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/time-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/timer-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/linux/RTLogWriteDebugger-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/r0drv/generic/semspinmutex-r0drv-generic.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/common/alloc/alloc.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/common/err/RTErrConvertFromErrno.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/common/err/RTErrConvertToErrno.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/common/err/errinfo.o
  CC [M]  /var/lib/dkms/virtualbox-guest/6.0.10/build/vboxguest/common/log/log.o
  CC [M]